Package: lightdm-gtk-greeter
Version: 2.0.9-1
Severity: normal
lightdm-gtk-greeter 2.0.9-1 has
Recommends: [...], polkitd | policykit-1
policykit-1 is now a transitional package. lightdm-gtk-greeter should
not recommend it (even in an OR dependency), otherwise apt or aptitude
cannot propose it
Package: light-locker
Version: 1.8.0-3
Severity: important
light-locker disconnects the bluetooth devices when locking.
This is just a screen locker. Locking should not affect bluetooth.
-- System Information:
Debian Release: trixie/sid
APT prefers unstable-debug
APT policy: (500, 'unstable-
Package: lightdm-gtk-greeter
Version: 2.0.8-2+b1
Severity: wishlist
I have a 15" laptop with a 4K screen, i.e. with a very high DPI.
With the gdm3 display manager, the font size was OK by default.
But when I switched to lightdm, the fonts became tiny and difficult
to read. For obvious accessibili
Control: reassign -1 systemd 251-2
On 2022-05-25 20:43:50 +0200, Yves-Alexis Perez wrote:
> I've quickly tried here and didn't have any issue, but if it's
> hardware- dependent it's likely the reason why neither Michael nor
> me have been able to reproduce (whether gdm3 or lightdm).
I'm reassigni
On 2022-05-25 13:35:27 +0200, Michael Biebl wrote:
> I'm not really familiar with lightdm and I don't see any such issue
> with gdm3.
Well, this doesn't mean anything. I've just looked at what I obtain
on another machine (my laptop), which also now has systemd 251-2:
May 24 10:26:21 zira systemd[
On 2022-01-25 11:28:14 +0100, Yves-Alexis Perez wrote:
> I guess it is, yes. Could you try without that Xorg configuration, to be sure?
> I'm not really familiar with the NVIDIA driver configuration file (in my case
> I'm using the XRandr configuration using Xfce display profiles) so maybe
> there'
Something that may be important: in my /etc/X11/xorg.conf file,
I have:
Section "Screen"
Identifier "Screen0"
Device "Device0"
Monitor"Monitor0"
DefaultDepth24
Option "Stereo" "0"
Option "metamodes" "DP-3: nvidia-auto-select +0+0, DP-
On 2022-01-24 18:52:28 +0100, Vincent Lefevre wrote:
> On 2022-01-24 18:32:43 +0100, Yves-Alexis Perez wrote:
> > out of curiosity, did you try to move the mouse (and bring it “back” to the
> > main screen) and see if the login dialog appears? My main setup also uses a
> >
On 2022-01-24 18:32:43 +0100, Yves-Alexis Perez wrote:
> out of curiosity, did you try to move the mouse (and bring it “back” to the
> main screen) and see if the login dialog appears? My main setup also uses a
> dual screen (docked laptop with an external screen), and I didn't (yet)
> experienced
On 2022-01-20 13:59:21 +0100, Vincent Lefevre wrote:
> The second point is that there is a race condition in the detection of
> the monitors on startup, so that the behavior varies.
>
> This issue is actually also now reproducible with systemd 250.2, but
> the systemd version s
On 2022-01-20 13:59:21 +0100, Vincent Lefevre wrote:
> This issue is actually also now reproducible with systemd 250.2, but
> the systemd version seems to have an effect of the possible behaviors
> (A, B and C below):
>
> With systemd 250.2:
> A. 2 monitors detected, the gree
nitor setup"
in the title)
On 2022-01-20 09:54:00 +0100, Michael Biebl wrote:
> Am 20.01.22 um 05:08 schrieb Vincent Lefevre:
> > Package: systemd
> > Version: 250.3-1
> > Severity: critical
> > Justification: breaks unrelated software
> >
> > The upgr
Package: lightdm-gtk-greeter
Version: 2.0.8-2
Severity: normal
I have a laptop with two 4K external monitors (bigger than the laptop
screen). Just after boot, only the laptop screen is active, and
everything is OK (well, except that I would prefer an external monitor
to be detected automatically,
ith this bug).
> On Wed, 2020-05-20 at 19:35 +0200, Vincent Lefevre wrote:
> >
> > Both locking and logging out trigger the lightdm login prompt,
> > so that I suppose that this is the same issue, and it was not
> > light-locker that was suspending the system, but lightdm.
>
Control: forcemerge 961132 961124
Control: reassign 961132 lightdm 1.26.0-7
Control: retitle -1 lightdm: with the nvidia driver, lightdm suspends the
system when locking or logging out
On 2020-05-20 15:58:11 +0200, Vincent Lefevre wrote:
> Package: light-locker
> Version: 1.8.0-3
>
Package: light-locker
Version: 1.8.0-3
Severity: important
With the nvidia driver, light-locker suspends the system when locking.
In the journalctl logs, I get a line like
May 20 09:16:43 zira systemd-logind[785]: Suspending...
and according to the systemd maintainer, this is light-locker's faul
On 2020-01-27 19:11:49 +0100, Yves-Alexis Perez wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> On Mon, 2020-01-27 at 10:54 +0100, Vincent Lefevre wrote:
> > It was the kernel from Debian/unstable at the time I reported the
> > bug, and it still occurred
On 2020-01-25 12:53:58 +0100, Yves-Alexis Perez wrote:
> On Mon, 2020-01-20 at 12:03 +0100, Vincent Lefevre wrote:
> > > In case this might depend on the driver, I was using the nvidia
> > > driver (and I still use it on this machine).
> >
> > My laptop uses t
On 2020-01-20 12:58:41 +0100, Vincent Lefevre wrote:
> On 2020-01-20 12:03:30 +0100, Vincent Lefevre wrote:
> > I'm going to turn on the debug messages to see whether there is a
> > difference when the problem occurs.
>
> Unfortunately, light-locker does not output an
On 2020-01-20 12:03:30 +0100, Vincent Lefevre wrote:
> I'm going to turn on the debug messages to see whether there is a
> difference when the problem occurs.
Unfortunately, light-locker does not output any debug message
when the screensaver stops (whether or not the bug has occurred)
Control: retitle -1 light-locker: screen sometimes black on screensaver
deactivation
On 2019-09-12 03:46:03 +0200, Vincent Lefevre wrote:
> On 2019-09-11 20:17:48 -0400, Christopher David Howie wrote:
> > I also experience this problem. It is intermittent, making it difficult
> &g
Control: forcemerge 932047 -1
On 2019-09-10 17:55:06 +0100, Mark Hindley wrote:
> I believe this is the same as the bug I submitted #932047.
>
> You might like to try the pam configuration fix I have there?
Indeed, that's the same issue, and your configuration fix solves
the problem for me. Than
On 2019-09-11 20:17:48 -0400, Christopher David Howie wrote:
> I also experience this problem. It is intermittent, making it difficult
> to reproduce, and it may or may not depend on specific hardware.
I think I have never reproduced this problem on any machine
(including the same machine, which
Package: lightdm
Version: 1.26.0-5
Severity: important
I have a machine still using sysvinit, and systemd-shim has been
replaced by elogind for such machines. The dependencies have been
updated in lightdm 1.26.0-4. But after the upgrade (which did not
output any warning about a regression), Restar
Package: lightdm
Version: 1.26.0-4
Severity: minor
I have the following issue with a machine using sysvinit (I don't
think that sysvinit is the culprit, just that it makes the problem
visible). This has occurred for several months now (perhaps after
the upgrade from 1.18.3 to 1.26, but I'm not sur
Package: light-locker
Version: 1.8.0-2
Severity: important
After being idle, the screen was automatically locked.
A bit later, I entered my password to unlock, but I got a black
screen, then after some time, the lightdm prompt again. I tried
two other times. Same problem. I eventually rebooted th
On 2014-01-17 09:55:22 +0100, Yves-Alexis Perez wrote:
> The greeter doesn't set anything, it gets the menu selection and gives
> it to lightdm.
A problem is that the greeter forces the first menu entry to be
selected by default instead of having a "nothing selected" state.
I reported the followi
Control: found -1 2.0.4-1
On 2015-07-03 17:38:57 +0200, Vincent Lefevre wrote:
> I've attached a patch that adds such an option. If I use:
>
> icon-size=64
>
> I get icons with acceptable size on my laptop.
New version of the patch attached, for lightdm-gtk-greeter 2
28 matches
Mail list logo
