Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#45081 - [lightdm-gtk-greeter] lightdm-gtk-greeter should be configured with --enable-kill-on-sigterm
Attached to Project:
Community Packages
Opened by Andrey Vihrov (andreyv) - Monday, 25 May 2015, 17:19 GMT
Last edited by Maxime Gauduin (Alucryd) - Tuesday, 26 May 2015, 06:50 GMT
Opened by Andrey Vihrov (andreyv) - Monday, 25 May 2015, 17:19 GMT
Last edited by Maxime Gauduin (Alucryd) - Tuesday, 26 May 2015, 06:50 GMT
|
DetailsDescription:
As the title says. This is needed to prevent lightdm-gtk-greeter from leaving many instances running after screen unlock. See: https://bbs.archlinux.org/viewtopic.php?id=196255 https://bugs.launchpad.net/lightdm-gtk-greeter/+bug/1445461 Package version: community/lightdm-gtk-greeter 1:2.0.1-1 Steps to reproduce: * Use GTK 3.16 * Lock/unlock the screen multiple times * Check loginctl output |
This task depends upon
Closed by Maxime Gauduin (Alucryd)
Tuesday, 26 May 2015, 06:50 GMT
Reason for closing: Fixed
Additional comments about closing: 1:2.0.1-2
Tuesday, 26 May 2015, 06:50 GMT
Reason for closing: Fixed
Additional comments about closing: 1:2.0.1-2