Hi Yves,
> Em seg., 2 de out. de 2023 às 09:25, Yves-Alexis Perez
> escreveu:
>>
>> On Sun, Oct 01, 2023 at 08:58:32PM -0300, Adilson dos Santos Dantas wrote:
>> > Hi.
>> >
>> > Here are the logs with and without the "logind-check-graphical=false"
>> > option.
>> >
>> > With this opinion, a
Em seg., 2 de out. de 2023 às 16:30, Yves-Alexis Perez
escreveu:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> On Mon, 2023-10-02 at 16:09 -0300, Adilson dos Santos Dantas wrote:
> > Ok. Running the command "loginctl show-seat seat0" with lightdm 1.26.0-8
> and
> > this option above:
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Mon, 2023-10-02 at 16:09 -0300, Adilson dos Santos Dantas wrote:
> Ok. Running the command "loginctl show-seat seat0" with lightdm 1.26.0-8 and
> this option above:
> Id=seat0
> CanTTY=yes
> CanGraphical=no
> Sessions=
> IdleHint=yes
>
Em seg., 2 de out. de 2023 às 15:48, Yves-Alexis Perez
escreveu:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> On Mon, 2023-10-02 at 15:33 +0200, Yves-Alexis Perez wrote:
> > At that point I don't think it's a problem in LightDM and I don't really
> > think it's a good idea to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Mon, 2023-10-02 at 15:33 +0200, Yves-Alexis Perez wrote:
> At that point I don't think it's a problem in LightDM and I don't really
> think it's a good idea to generalize the workaround (and divert from
> upstream).
Just to be sure, can you test
On Mon, Oct 02, 2023 at 09:47:38AM -0300, Adilson dos Santos Dantas wrote:
> Here are the results of 'loginctl show-seat seat0' from both
> 'login-check-grafical' options.
>
> logind-check-graphical=true
> loginctl show-seat seat0
> Id=seat0
> CanTTY=yes
> CanGraphical=no
> Sessions=
>
Here are the results of 'loginctl show-seat seat0' from both
'login-check-grafical' options.
logind-check-graphical=true
loginctl show-seat seat0
Id=seat0
CanTTY=yes
CanGraphical=no
Sessions=
IdleHint=yes
IdleSinceHint=0
IdleSinceHintMonotonic=0
logind-check-graphical=false
loginctl show-seat
On Sun, Oct 01, 2023 at 08:58:32PM -0300, Adilson dos Santos Dantas wrote:
> Hi.
>
> Here are the logs with and without the "logind-check-graphical=false"
> option.
>
> With this opinion, a new seat is added and no seat is added when this
> option is commented.
Thanks for the log. I'm unsure
Hi.
Here are the logs with and without the "logind-check-graphical=false"
option.
With this opinion, a new seat is added and no seat is added when this
option is commented.
Regards,
Adilson
Em dom., 1 de out. de 2023 às 11:22, Yves-Alexis Perez
escreveu:
> -BEGIN PGP SIGNED
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Tue, 2023-08-08 at 01:25 -0500, Steev Klimaszewski wrote:
> I'm running into a very similar issue as the original submitter,
> however, when I'm running into it, I am *not* using the nVidia binary
> driver, but I am using a custom 5.15.44 kernel
I tested this solution from Steev Klimaszewski and it worked.
So we have a workaround for this problem.
Maybe it can be used with sddm. But I need to see where the configuration
is to do that.
Best regards,
Adilson
--
Adilson dos Santos Dantas
http://www.adilson.net.br
Hi Yves,
I'm running into a very similar issue as the original submitter,
however, when I'm running into it, I am *not* using the nVidia binary
driver, but I am using a custom 5.15.44 kernel for a Raspberry Pi.
What I found after digging for quite a while, was that, yes,
downgrading to 1.26 would
Yes, I was able to upgrade lightdm to 1.32 after I reinstalled xserver-xorg. I
don't think it was lightdm causing the issue itself, it was due to xserver-xorg
and xinit being removed during the a system upgrade. Once I had those
re-installed everything is working great again.
Thanks for the
control: severity -1 important
control: retitle -1 lightdm 1.32 fails to start X on nvidia binary driver
On Thu, Jun 22, 2023 at 01:10:41AM -0300, Adilson dos Santos Dantas wrote:
> I tested with the nouveau driver and it worked.
>
> Maybe there is something between 1.26 and 1.32 that conflicts
I tested with the nouveau driver and it worked.
Maybe there is something between 1.26 and 1.32 that conflicts with nvidia
driver.
And it is also similar to #996503 which affects sddm and it worked too with
nouveau.
I tried to fix this by removing some module options from
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Wed, 2023-06-21 at 09:40 -0300, Adilson dos Santos Dantas wrote:
> These messages are when I stop lightdm.
Ah ok.
> >
> >
> > Also is there something peculiar about your hardware (Nvidia/AMD GPU for
> > example?) or software (specific
Em qua., 21 de jun. de 2023 às 03:33, Yves-Alexis Perez
escreveu:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> On Tue, 2023-06-20 at 20:37 -0300, Adilson dos Santos Dantas wrote:
> > I tried to use 1.32 again and it only
> > generates /var/log/lightdm/lightdm.log. It doesn't generate
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Wed, 2023-06-21 at 01:59 +, solneman33 wrote:
> I downgraded to xkb-data=2.35.1-1 lightdm=1.26.0-8 from testing repo and
> reinstalled xserver-xorg and xinit. That resolved the issue for me on both
> machines.
>
> I've never reported a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Tue, 2023-06-20 at 20:37 -0300, Adilson dos Santos Dantas wrote:
> I tried to use 1.32 again and it only
> generates /var/log/lightdm/lightdm.log. It doesn't generate seat0-
> greeter.log and x-0.lo. From the log attached below, one difference
I was able to reproduce with two of my machines running unstable.
xserver-xorg and xinit were removed during the upgrade and I wasn't aware.
I downgraded to xkb-data=2.35.1-1 lightdm=1.26.0-8 from testing repo and
reinstalled xserver-xorg and xinit. That resolved the issue for me on both
Hi Yves-Alexis,
I tried to use 1.32 again and it only generates /var/log/lightdm/lightdm.log.
It doesn't generate seat0-greeter.log and x-0.lo. From the log attached
below, one difference is that 1.26 starts seat0 and 1.32 does not start it.
I got an X session from 1.26 and X does not even start
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Tue, 2023-06-20 at 12:45 +0200, Carlos Laviola wrote:
> Package: lightdm
> Followup-For: Bug #1038611
>
> Can't reproduce, starts up just fine for me.
>
> Could you perhaps include the logs from `/var/log/lightdm/´?
Hi Adilson,
I'm running
Package: lightdm
Followup-For: Bug #1038611
Can't reproduce, starts up just fine for me.
Could you perhaps include the logs from `/var/log/lightdm/´?
-- System Information:
Debian Release: trixie/sid
APT prefers stable-security
APT policy: (500, 'stable-security'), (500,
Package: lightdm
Version: 1.32.0-2
Severity: grave
Justification: renders package unusable
Dear Maintainer,
After upgrading lightdm to the latest upstream version (1.32.0-2) fails to
start X session leading only to console mode.
Downgrading to 1.26.0-8, from testing, fixes this bug.
--
24 matches
Mail list logo
