[Touch-packages] [Bug 1614942] Re: "GLib-CRITICAL" messages keep appearing in log file
Unfortunately, this bug is unlikely to be fixed upstream: "ConsoleKit is currently not actively maintained. The focus has shifted to the built-in seat/user/session management of Software/systemd called systemd-logind!" https://www.freedesktop.org/wiki/Software/ConsoleKit/ -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to consolekit in Ubuntu. https://bugs.launchpad.net/bugs/1614942 Title: "GLib-CRITICAL" messages keep appearing in log file Status in consolekit package in Ubuntu: Triaged Bug description: At regular intervals, errors appear in the log files from consolekit: Aug 19 12:57:27 machine console-kit-daemon[3997]: console-kit-daemon[3997]: GLib-CRITICAL: Source ID 1118 was not found when attempting to remove it Aug 19 12:57:27 machine console-kit-daemon[3997]: console-kit-daemon[3997]: GLib-CRITICAL: Source ID 1118 was not found when attempting to remove it Aug 19 12:57:27 machine console-kit-daemon[3997]: GLib-CRITICAL: Source ID 1118 was not found when attempting to remove it Aug 19 12:57:27 machine console-kit-daemon[3997]: GLib-CRITICAL: Source ID 1118 was not found when attempting to remove it ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: consolekit 0.4.6-5 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 Date: Fri Aug 19 13:09:22 2016 InstallationDate: Installed on 2012-03-26 (1606 days ago) InstallationMedia: Mythbuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) SourcePackage: consolekit UpgradeStatus: Upgraded to xenial on 2016-07-27 (23 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/consolekit/+bug/1614942/+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 1264368] Re: GLib-CRITICAL **: Source ID was not found when attempting to remove it - warning when leaving Network menu of g-c-c
The message is emitted by glib: https://gitlab.gnome.org/GNOME/glib/commit/a919be3d39150328874ff647fb2c2be7af3df996 The commit log description is: "gmain: Warn when g_source_remove() fails". So why is it calling g_critical() instead of g_warning()? Obviously, it's not a critical error, if people are able to live with these annoying messages for five years with no obvious ill effects. Critical errors are often routed to /dev/console, and it's clearly inappropriate to escalate these messages that high. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to consolekit in Ubuntu. https://bugs.launchpad.net/bugs/1264368 Title: GLib-CRITICAL **: Source ID was not found when attempting to remove it - warning when leaving Network menu of g-c-c Status in AndroidSDK: New Status in Banshee: New Status in gnome-control-center: Incomplete Status in GParted: Unknown Status in notification-daemon: New Status in anjuta package in Ubuntu: Confirmed Status in consolekit package in Ubuntu: Confirmed Status in f-spot package in Ubuntu: Confirmed Status in gnome-control-center package in Ubuntu: Triaged Status in gnome-mplayer package in Ubuntu: Confirmed Status in putty package in Ubuntu: Confirmed Bug description: Steps to recreate: 1. Open gnome-control-center in terminal. 2. Go to Network. 3. Go back to All preferences. 4. Notice that in terminal there is a warning: $ gnome-control-center (gnome-control-center:13519): GLib-CRITICAL **: Source ID 166 was not found when attempting to remove it ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: gnome-control-center 1:3.6.3-0ubuntu49 ProcVersionSignature: Ubuntu 3.12.0-7.15-generic 3.12.4 Uname: Linux 3.12.0-7-generic x86_64 ApportVersion: 2.12.7-0ubuntu3 Architecture: amd64 CurrentDesktop: GNOME Date: Thu Dec 26 21:03:52 2013 InstallationDate: Installed on 2013-10-15 (71 days ago) InstallationMedia: Ubuntu-GNOME 13.10 "Saucy Salamander" - Release amd64 (20131015) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: Upgraded to trusty on 2013-11-05 (51 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/androidsdk/+bug/1264368/+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 619003] Re: GdkPixbuf-WARNING **: Cannot open pixbuf loader module file '/usr/lib/gdk-pixbuf-2.0/2.10.0/loaders.cache'
I got this message on trusty 14.04: Processing triggers for hicolor-icon-theme (0.13-1) ... (gtk-update-icon-cache-3.0:31711): GdkPixbuf-WARNING **: Cannot open pixbuf loader module file '/usr/lib/x86_64-linux-gnu/gdk- pixbuf-2.0/2.10.0/loaders.cache': No such file or directory This likely means that your installation is broken. Try running the command gdk-pixbuf-query-loaders > /usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders.cache to make things work again for the time being. As instructed, I tried and got: # gdk-pixbuf-query-loaders > /usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders.cache The program 'gdk-pixbuf-query-loaders' is currently not installed. You can install it by typing: apt-get install libgdk-pixbuf2.0-dev Taking that hint, if I install libgdk-pixbuf2.0-dev first, then hicolor-icon-theme.postinst no longer complains. So, maybe /usr/bin/gdk-pixbuf-query-loaders belongs in the libgdk-pixbuf2.0 rather than the libgdk-pixbuf2.0-dev package. Furthermore, libgtk-3-bin (which owns the /usr/bin/gtk-update-icon-cache-3.0 command that hicolor-icon-theme.postinst calls) should declare a dependency on it. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdk-pixbuf in Ubuntu. https://bugs.launchpad.net/bugs/619003 Title: GdkPixbuf-WARNING **: Cannot open pixbuf loader module file '/usr/lib /gdk-pixbuf-2.0/2.10.0/loaders.cache' Status in gdk-pixbuf package in Ubuntu: Confirmed Status in gdk-pixbuf package in Debian: New Bug description: During installation of updated version of libgdk-pixbuf2.0-0 on August 10th 2010, the apt term.log contained multiple (>300) copies of the following warning: (gtk-update-icon-cache:4729): GdkPixbuf-WARNING **: Cannot open pixbuf loader module file '/usr/lib/gdk-pixbuf-2.0/2.10.0/loaders.cache': No such file or directory Nevertheless, the file complained about exists, and is readable in gedit. ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: libgdk-pixbuf2.0-0 2.21.6-2ubuntu5 ProcVersionSignature: Ubuntu 2.6.35-15.21-generic 2.6.35.1 Uname: Linux 2.6.35-15-generic x86_64 Architecture: amd64 CheckboxSubmission: 363004b1d940f0fc558ab8c98655a145 CheckboxSystem: b845c366ea09c60efa3a45c1b5b21525 Date: Mon Aug 16 18:13:29 2010 InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta amd64 (20100318) ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gdk-pixbuf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdk-pixbuf/+bug/619003/+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 911622] Re: [12.04] GdkPixbuf-WARNING **: Cannot open pixbuf loader module file '/usr/lib/i386-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders.cache': Datei oder Verzeichnis nicht gefund
*** This bug is a duplicate of bug 619003 *** https://bugs.launchpad.net/bugs/619003 ** This bug has been marked a duplicate of bug 619003 GdkPixbuf-WARNING **: Cannot open pixbuf loader module file '/usr/lib/gdk-pixbuf-2.0/2.10.0/loaders.cache' -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdk-pixbuf in Ubuntu. https://bugs.launchpad.net/bugs/911622 Title: [12.04] GdkPixbuf-WARNING **: Cannot open pixbuf loader module file '/usr/lib/i386-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders.cache': Datei oder Verzeichnis nicht gefunden (file not found) Status in gdk-pixbuf package in Ubuntu: Confirmed Bug description: after the latest dist-upgrade on 12.04 there are a lot of these messages (Datei oder Verzeichnis not found == file not found) GdkPixbuf-WARNING **: Cannot open pixbuf loader module file '/usr/lib/i386-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders.cache': Datei oder Verzeichnis nicht gefunden ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: libgdk-pixbuf2.0-0 2.25.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-7.13-generic 3.2.0-rc7 Uname: Linux 3.2.0-7-generic i686 ApportVersion: 1.90-0ubuntu1 Architecture: i386 Date: Wed Jan 4 07:30:55 2012 EcryptfsInUse: Yes InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110426) ProcEnviron: PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: gdk-pixbuf UpgradeStatus: Upgraded to precise on 2011-12-04 (30 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdk-pixbuf/+bug/911622/+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 1350393] Re: Recent accountsservice update causes login window to hang
@Gunnar, 0.6.35-0ubuntu7.2 may be improve performance in some cases, but it does nothing to avoid the infinite hang that I characterized in comment #4. The fact that it calls user_language_validate() just once in the context of an LDAP user when the LDAP client isn't fully ready will cause accounts-daemon to fail completely. Therefore, your revised patch should make no difference to the failure mode I described. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to accountsservice in Ubuntu. https://bugs.launchpad.net/bugs/1350393 Title: Recent accountsservice update causes login window to hang Status in Light Display Manager: New Status in accountsservice package in Ubuntu: Incomplete Bug description: Hi, The recent 0.6.35-0ubuntu7.1 update (see https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1290785) seems to have removed the UID_MAX check, which could be used to hide users from the login window. In a large organization where many thousands of users are present on our systems, we relied on the UID_MAX setting in /etc/login.defs to prevent accounts-daemon from trying to frob all our accounts. accounts-daemon's performance is so poor, that not having the UID_MAX check causes lightdm to hang for 5-10mins while accounts-daemon tries to look for something in every users home folder. I've already done things like set the login window to require the user to enter their username and password rather than list all users, but the login window still hangs while accounts-daemon is doing its thing. The behavior I see, is: 1) just after boot, there's a black screen, right after the plymouth splash disappears, for 2-3 minutes before lightdm appears 2) You type a username into the username field and press 'Tab' 3) lightdm appears to hang for 5-10mins before the cursor moves to the password field. During this time, I see an accounts-daemon spawn for each user on the system, sequentially (in alphabetical order). Once the last user's accounts-daemon process finishes, the cursor moves to the password field. This not only happens on first boot, but every time a user logs out and the system returns to the login window. Any chance we can have the UID_MAX check back? Or some equivalent? This is causing a serious problem for us! Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1350393/+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 1350393] Re: Recent accountsservice update causes login window to hang
This may be a duplicate of bug 996791. https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/996791 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to accountsservice in Ubuntu. https://bugs.launchpad.net/bugs/1350393 Title: Recent accountsservice update causes login window to hang Status in Light Display Manager: New Status in accountsservice package in Ubuntu: Incomplete Bug description: Hi, The recent 0.6.35-0ubuntu7.1 update (see https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1290785) seems to have removed the UID_MAX check, which could be used to hide users from the login window. In a large organization where many thousands of users are present on our systems, we relied on the UID_MAX setting in /etc/login.defs to prevent accounts-daemon from trying to frob all our accounts. accounts-daemon's performance is so poor, that not having the UID_MAX check causes lightdm to hang for 5-10mins while accounts-daemon tries to look for something in every users home folder. I've already done things like set the login window to require the user to enter their username and password rather than list all users, but the login window still hangs while accounts-daemon is doing its thing. The behavior I see, is: 1) just after boot, there's a black screen, right after the plymouth splash disappears, for 2-3 minutes before lightdm appears 2) You type a username into the username field and press 'Tab' 3) lightdm appears to hang for 5-10mins before the cursor moves to the password field. During this time, I see an accounts-daemon spawn for each user on the system, sequentially (in alphabetical order). Once the last user's accounts-daemon process finishes, the cursor moves to the password field. This not only happens on first boot, but every time a user logs out and the system returns to the login window. Any chance we can have the UID_MAX check back? Or some equivalent? This is causing a serious problem for us! Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1350393/+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 996791] Re: Xubuntu 12.04 extremely slow login
I suspect that this bug is a duplicate of https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1350393 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to accountsservice in Ubuntu. https://bugs.launchpad.net/bugs/996791 Title: Xubuntu 12.04 extremely slow login Status in accountsservice package in Ubuntu: Confirmed Bug description: The core issue is that /usr/lib/accountsservice/accounts-daemon doesn't accept dbus messages on boot. The symptom to this problem is that, after successfulling entering your login information, the system takes about 85 seconds to boot. The real issue occuring is that /usr/lib/accountsservice/accounts- daemon isn't being started correctly by ligthdm. The accounts-daemon wont accept dbus requests, and so the dbus timeout is hit during boot. Before I start, here is a run down on my machine/setup: Intel I7. Xubuntu 12.04. Encrypted home drive. Running compiz. Enabling the log files on lightdm, the follow warnings are displayed (Notice the times): [+11.58s] DEBUG: Greeter quit [+36.60s] WARNING: Could not call SetXSession: Timeout was reached [+61.63s] WARNING: Could not call FindUserByName: Timeout was reached [+61.63s] DEBUG: Dropping privileges to uid 1000 [+61.63s] DEBUG: Restoring privileges [+86.65s] WARNING: Could not call FindUserByName: Timeout was reached If the /usr/lib/accountsservices/accounts-daemon is restarted, after the lightdm login screen is displayed, but before a login, then xfce will start immediately. Otherwise boot times take about 87 seconds. Also, it was found that the program d-feet, is unable to retrive valid methods from /usr/lib/accountsservices/accounts-daemon before it is restarted. After the deamon is restarted, all dbus methods are visuable and communicate correctly. For descussion on the problem, and a temporary fix, see the following thread: http://ubuntuforums.org/showthread.php?t=1970326 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/996791/+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 1350393] Re: Recent accountsservice update causes login window to hang
Why lightdm behaves the way it does… In common/user-list.c, load_users() calls load_passwd_file(). The intended code path is is for load_passwd_file() to make use of the org.freedesktop.Accounts.ListCachedUsers DBus call.[1] However, due to the accounts-daemon failure[2], it falls back on the slow code path, which calls load_passwd_file(), which then calls make_passwd_user() for every single user.[3] That results in a check for the existence of ~/.face and ~/.face.icon for potentially thousands of LDAP users, possibly with NFS-mounted home directories! [1]: https://bazaar.launchpad.net/~lightdm-team/lightdm/1.10/view/1995/common/user-list.c#L908 [2]: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1350393/comments/4 [3]: https://bazaar.launchpad.net/~lightdm-team/lightdm/1.10/view/1995/common/user-list.c#L264 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to accountsservice in Ubuntu. https://bugs.launchpad.net/bugs/1350393 Title: Recent accountsservice update causes login window to hang Status in Light Display Manager: New Status in accountsservice package in Ubuntu: Confirmed Bug description: Hi, The recent 0.6.35-0ubuntu7.1 update (see https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1290785) seems to have removed the UID_MAX check, which could be used to hide users from the login window. In a large organization where many thousands of users are present on our systems, we relied on the UID_MAX setting in /etc/login.defs to prevent accounts-daemon from trying to frob all our accounts. accounts-daemon's performance is so poor, that not having the UID_MAX check causes lightdm to hang for 5-10mins while accounts-daemon tries to look for something in every users home folder. I've already done things like set the login window to require the user to enter their username and password rather than list all users, but the login window still hangs while accounts-daemon is doing its thing. The behavior I see, is: 1) just after boot, there's a black screen, right after the plymouth splash disappears, for 2-3 minutes before lightdm appears 2) You type a username into the username field and press 'Tab' 3) lightdm appears to hang for 5-10mins before the cursor moves to the password field. During this time, I see an accounts-daemon spawn for each user on the system, sequentially (in alphabetical order). Once the last user's accounts-daemon process finishes, the cursor moves to the password field. This not only happens on first boot, but every time a user logs out and the system returns to the login window. Any chance we can have the UID_MAX check back? Or some equivalent? This is causing a serious problem for us! Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1350393/+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 1350393] Re: Recent accountsservice update causes login window to hang
I have found something close to a root cause, and I observe this hang 100% of the time under the following conditions: 1. Packages libnss-ldap_264-2.2ubuntu4.14.04.1 and accountsservice_0.6.35-0ubuntu7.1 are installed. 2. /etc/nsswitch.conf contains "passwd: files ldap" 3. An LDAP user has logged in recently, as recorded in /var/log/wtmp. 4. dbus and lightdm are started on boot. In lightdm_10.10.5-0ubuntu1, user-list.c makes a DBus call for the method org.freedesktop.Accounts.ListCachedUsers.[1] This call times out. You can confirm that ListCachedUsers fails by running `/usr/sbin /dbus-send --system --print-reply --dest=org.freedesktop.Accounts /org/freedesktop/Accounts org.freedesktop.Accounts.ListCachedUsers`. DBus tries to dispatch the message to accounts-daemon. However, accounts-daemon isn't listening for requests because it hasn't fully started up yet. Rather, it is stuck in the user_locale_validate() function, waiting for the /usr/share/language-tools/language-validate shell script to complete.[2] Note that the language-validate mechanism is an Ubuntu customization, not present in the upstream accountsservice 0.6.35. The language-validate shell script runs not as root, but as an LDAP user. Bash never gets a chance to execute its first command, since it gets stuck during initialization with a getpwuid() call for that LDAP user that never returns. (To see that, I suggest hacking user_language_validate() to insert an ltrace or strace.) There is a race condition: this early in the boot process, libnss-ldap lookups just hang. On the other hand, libnss-ldapd, which bills itself as the successor fork to libnss-ldap,[3] does not suffer from such a problem. Unfortunately, if you install ldap-auth-config_0.5.3, it will tend to pull in libnss-ldap as an automatic dependency rather than libnss- ldapd.[4] In summary, executing `killall language-validate` after boot serves as a workaround, as it lets accounts-daemon continue its initialization. Running `service dbus restart` is a more forceful workaround, as it lets accounts-daemon launch after conditions are ready for LDAP lookups. The problem occurs with libnss-ldap_264-2.2ubuntu4.14.04.1, and it goes away when libnss-ldapd_0.8.13-3 is installed instead. That, to me, is the most sensible solution. [1]: http://bazaar.launchpad.net/~lightdm-team/lightdm/1.10/view/1995/common/user-list.c#L887 [2]: http://bazaar.launchpad.net/~robert-ancell/accountsservice/lp1290785/view/head:/debian/patches/0010-set-language.patch#L60 [3]: http://arthurdejong.org/nss-pam-ldapd/ [4]: http://packages.ubuntu.com/trusty/ldap-auth-client -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to accountsservice in Ubuntu. https://bugs.launchpad.net/bugs/1350393 Title: Recent accountsservice update causes login window to hang Status in Light Display Manager: New Status in accountsservice package in Ubuntu: Confirmed Bug description: Hi, The recent 0.6.35-0ubuntu7.1 update (see https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1290785) seems to have removed the UID_MAX check, which could be used to hide users from the login window. In a large organization where many thousands of users are present on our systems, we relied on the UID_MAX setting in /etc/login.defs to prevent accounts-daemon from trying to frob all our accounts. accounts-daemon's performance is so poor, that not having the UID_MAX check causes lightdm to hang for 5-10mins while accounts-daemon tries to look for something in every users home folder. I've already done things like set the login window to require the user to enter their username and password rather than list all users, but the login window still hangs while accounts-daemon is doing its thing. The behavior I see, is: 1) just after boot, there's a black screen, right after the plymouth splash disappears, for 2-3 minutes before lightdm appears 2) You type a username into the username field and press 'Tab' 3) lightdm appears to hang for 5-10mins before the cursor moves to the password field. During this time, I see an accounts-daemon spawn for each user on the system, sequentially (in alphabetical order). Once the last user's accounts-daemon process finishes, the cursor moves to the password field. This not only happens on first boot, but every time a user logs out and the system returns to the login window. Any chance we can have the UID_MAX check back? Or some equivalent? This is causing a serious problem for us! Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1350393/+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
