[Touch-packages] [Bug 1292324] Re: Support non-root X
Robert, I know you weren't interested in this but would review patches if needed. Could you point people to the right directions on where to drop privileges before running X server and stuff like that? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1292324 Title: Support non-root X Status in Light Display Manager: Triaged Status in lightdm package in Ubuntu: Triaged Status in lightdm package in Debian: Confirmed Status in lightdm package in Fedora: Unknown Bug description: Support running X as an unprivileged user. Currently X servers are run as root means a large complex process has access to services it might not need (i.e. potential security and stability problems). It would be nice to run each X server as either an unprivileged user or in the session they are being used in. Logind provides a system for sharing access to the display and input devices so this can be done - this seems like the most likely implementation of non-root X. For more information see Hans de Goede request: http://lists.freedesktop.org/archives/lightdm/2014-March/000539.html To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1292324/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1292324] Re: Support non-root X
** Bug watch added: Debian Bug tracker #809067 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=809067 ** Also affects: lightdm (Debian) via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=809067 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1292324 Title: Support non-root X Status in Light Display Manager: Triaged Status in lightdm package in Ubuntu: Triaged Status in lightdm package in Debian: Unknown Bug description: Support running X as an unprivileged user. Currently X servers are run as root means a large complex process has access to services it might not need (i.e. potential security and stability problems). It would be nice to run each X server as either an unprivileged user or in the session they are being used in. Logind provides a system for sharing access to the display and input devices so this can be done - this seems like the most likely implementation of non-root X. For more information see Hans de Goede request: http://lists.freedesktop.org/archives/lightdm/2014-March/000539.html To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1292324/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1516831] Re: XDMCP Request packet with no addresses crashes LightDM
** CVE added: http://www.cve.mitre.org/cgi- bin/cvename.cgi?name=2015-8316 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1516831 Title: XDMCP Request packet with no addresses crashes LightDM Status in Light Display Manager: Fix Released Status in Light Display Manager 1.14 series: Fix Released Status in Light Display Manager 1.16 series: Fix Released Status in lightdm package in Ubuntu: Fix Committed Status in lightdm source package in Wily: Fix Committed Bug description: [Impact] If LightDM receives an XDMCP Request packet with no addresses then it will attempt to access a negative index into an array and crash. This only occurs if the XDMCP server is enabled. [Test Case] 1. Enable XDMCP in lightdm.conf: [XDMCPServer] enabled=true 2. Start LightDM 3. Send an XDMCP Request without an empty addresses field (valid XDMCP servers do not send this). Expected result: The request is ignored. Observed result: LightDM crashes. To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1516831/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1370852] Re: Scans all user accounts when not required
Actually sorry, that's wrong, it's unrelated, it's due to our own patch setting USERS_DIR to /var/lib/lightdm (I don't really understand why, but that's off-topic for this bug). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1370852 Title: Scans all user accounts when not required Status in Light Display Manager: Fix Released Status in Light Display Manager 1.10 series: Fix Released Status in “lightdm” package in Ubuntu: Fix Released Status in “lightdm” source package in Trusty: In Progress Status in “lightdm” source package in Utopic: Fix Released Bug description: [Impact] When AccountsService is not present on startup LightDM scans all the user accounts and attempts to access the dmrc file for each user. It does not use any information from the dmrc files. If you have many users and/or the dmrc files are on a slow filesystem this creates a big startup delay. [Test Case] 1. Start LightDM on a system that doesn't have AccountsService and has many users Expected result: LightDM starts quickly Observed result: LightDM takes a long time to start [Regression potential] Low. We now only access the dmrc files when information from them i s required (lazy load). Tested with regression tests. To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1370852/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1370852] Re: Scans all user accounts when not required
It seems that this change actually broke .dmrc files on Debian. I'm currently investigating, but it seems that the files (~/.dmrc and /var/cache/lightdm/dmrc/user.dmrc) are not updated anymore with the selected session. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1370852 Title: Scans all user accounts when not required Status in Light Display Manager: Fix Released Status in Light Display Manager 1.10 series: Fix Released Status in “lightdm” package in Ubuntu: Fix Released Status in “lightdm” source package in Trusty: In Progress Status in “lightdm” source package in Utopic: Fix Released Bug description: [Impact] When AccountsService is not present on startup LightDM scans all the user accounts and attempts to access the dmrc file for each user. It does not use any information from the dmrc files. If you have many users and/or the dmrc files are on a slow filesystem this creates a big startup delay. [Test Case] 1. Start LightDM on a system that doesn't have AccountsService and has many users Expected result: LightDM starts quickly Observed result: LightDM takes a long time to start [Regression potential] Low. We now only access the dmrc files when information from them i s required (lazy load). Tested with regression tests. To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1370852/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1212408] Re: lightdm/gdm needs to set $XDG_CURRENT_DESKTOP
It seems that gdm now supports setting XDG_CURRENT_DESKTOP but uses the DesktopNames [1] property. It might make sense to migrate LightDM to uses that too. [1] https://bugzilla.gnome.org/show_bug.cgi?id=727546 ** Bug watch added: GNOME Bug Tracker #727546 https://bugzilla.gnome.org/show_bug.cgi?id=727546 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1212408 Title: lightdm/gdm needs to set $XDG_CURRENT_DESKTOP Status in Light Display Manager: Fix Released Status in “gdm” package in Ubuntu: Fix Released Status in “gnome-session” package in Ubuntu: Fix Released Status in “lightdm” package in Ubuntu: Fix Released Bug description: Since the switch to upstart, some processes in the user environment, such as gnome-screensaver, now get launched without $XDG_CURRENT_DESKTOP being set. This is currently causing screen locking issues. This used to get set by gnome-session, but it is no longer high enough in the process tree to set it for the complete user session. Consensus in #ubuntu-desktop was that lightdm should be setting it. To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1212408/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 799069] Re: xf86OpenConsole: setpgid failed
Seems we don't use the patch since long, and it seems to work fine even with plymouth. Sorry for the delay. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/799069 Title: xf86OpenConsole: setpgid failed Status in “lightdm” package in Ubuntu: Fix Released Bug description: Binary package hint: lightdm Oneiric i386 on nvidia (xorg-edgers) got logged into xorg.log: xf86OpenConsole: setpgid failed: Operation not permitted xf86OpenConsole: setsid failed: Operation not permitted i've found similar issue reported but against xdm/slim/wdm: Bug #585853 #19 post seems to point the real problem: - This appears to be caused by the lightdm package not integrating with upstart. - The plymouth process which holds the console open is waiting for a signal that the lightdm job is starting up, so that it can let go of the console; but the lightdm package doesn't have an upstart job, so there's no signal sent, which means the plymouth and lightdm processes are fighting over the console. Note: need to check that the above comments are correct ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: lightdm 0.4.0-0ubuntu5 ProcVersionSignature: Ubuntu 3.0-1.2-generic-pae 3.0.0-rc3 Uname: Linux 3.0-1-generic-pae i686 NonfreeKernelModules: nvidia Architecture: i386 Date: Sat Jun 18 09:26:09 2011 ProcEnviron: LANGUAGE=fr_FR:fr:en_GB:en PATH=(custom, no user) LANG=fr_FR.utf8 LC_MESSAGES=fr_FR.utf8 SHELL=/bin/bash SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/799069/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
