[Dx-packages] [Bug 1314095] Re: Unity Lockscreen in 14.04 can't unlock when using LDAP account
Hello sponsors, Please consider uploading the attached nslcd patch to trusty-proposed to resolve this bug. Thank you! ** Description changed: + SRU justification: + + [Impact] + + * Summary: in Trusty, when libnss-ldapd is used, LDAP users are not able + to unlock the Unity lockscreen. Utopic and later are not affected. Some + workarounds are listed in comment #29. + + * nslcd in Trusty and earlier does not permit unprivileged users to read + shadow entries. When invoked by the Unity lockscreen, running as the + logged-in user, pam_unix returns PAM_AUTHINFO_UNAVAIL in pam_acct_mgmt + when it tries to get password expiry information from shadow. This leads + to an authorization failure, so Unity refuses to unlock the screen. + pam_ldap is not consulted for pam_acct_mgmt after pam_unix fails because + its rule is in the Additional section. + + * In Utopic and later, nslcd returns partial shadow entries to + unprivileged users. This is enough for the expiry check in pam_unix to + succeed, so the screen can be unlocked. See + http://bugs.debian.org/706913 for a discussion of the upstream fix. + + * This proposed SRU backports the upstream solution to Trusty's nslcd. + This is a change of behaviour for shadow queries from unprivileged + users, compared to the current package. An alternative, more targeted + fix would be to change Unity to ignore AUTHINFO_UNAVAIL results from + pam_acct_mgmt, like gnome-screensaver already does (see comment #29). + The nslcd change is a more general fix for not just Unity, but any PAM- + using program run by an unprivileged user. + + [Test Case] + + * Install and configure libnss-ldapd. Ensure ldap is enabled for at + least the passwd and shadow services in /etc/nsswitch.conf. + + * Log into Unity as an LDAP user, lock the screen, and then try to + unlock it again. + + [Regression Potential] + + * The patch is minimal, was written by the upstream author, and was + backported (adjusting for whitespace changes) to Trusty. The change has + already been released in Utopic and will be included in Debian Jessie as + well. + + * Regression testing should include checking that shadow queries, both + by name and for listing all users, are unchanged when issued as root. + + [Other Info] + + * Packages for testing are available in ppa:rtandy/lp1314095 + + Original description: + My setup is: Ubuntu 14.04 LTS, ldap accounts, krb5 authentication, Lightdm, Unity session ldap+krb5 is configured using nss-ldapd and nslcd. It works fine. getent passwd and getent shadow works fine. I am able to login in console without any problems. I was able to login in lightdm. Then I used the lock screen. I could not disable the lock screen using my password. I rebooted my computer. Now: After logging in through lightdm, the unity lockscreen locks the screen immediately and I can not disable it using my password. From my short inspection of auth.log and unix_chkpwd sources it seems, that unix_chkpwd works fine when called from lightdm and fails to get user info when called from unity lockscreen. - lsb_release -rd Description: Ubuntu 14.04 LTS Release: 14.04 apt-cache policy unity lightdm libpam-modules unity: - Installed: 7.2.0+14.04.20140416-0ubuntu1 - Candidate: 7.2.0+14.04.20140416-0ubuntu1 - Version table: - *** 7.2.0+14.04.20140416-0ubuntu1 0 - 500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages - 100 /var/lib/dpkg/status + Installed: 7.2.0+14.04.20140416-0ubuntu1 + Candidate: 7.2.0+14.04.20140416-0ubuntu1 + Version table: + *** 7.2.0+14.04.20140416-0ubuntu1 0 + 500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages + 100 /var/lib/dpkg/status lightdm: - Installed: 1.10.0-0ubuntu3 - Candidate: 1.10.0-0ubuntu3 - Version table: - *** 1.10.0-0ubuntu3 0 - 500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages - 100 /var/lib/dpkg/status + Installed: 1.10.0-0ubuntu3 + Candidate: 1.10.0-0ubuntu3 + Version table: + *** 1.10.0-0ubuntu3 0 + 500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages + 100 /var/lib/dpkg/status libpam-modules: - Installed: 1.1.8-1ubuntu2 - Candidate: 1.1.8-1ubuntu2 - Version table: - *** 1.1.8-1ubuntu2 0 - 500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages - 100 /var/lib/dpkg/status + Installed: 1.1.8-1ubuntu2 + Candidate: 1.1.8-1ubuntu2 + Version table: + *** 1.1.8-1ubuntu2 0 + 500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages + 100 /var/lib/dpkg/status Contents of /var/log/auth.log: Apr 29 06:49:27 localhost lightdm: pam_succeed_if(lightdm:auth): requirement user ingroup nopasswdlogin not met by user user Apr 29 06:49:31 localhost lightdm: pam_unix(lightdm:auth): authentication failure; logname= uid=0 euid=0 tty=:2 ruser= rhost= user=user Apr 29 06:49:31 localhost
[Dx-packages] [Bug 1362341] Re: OneTime alarms are not automatically dismissed or delete after they are triggered
** Changed in: ubuntu-clock-app Status: Fix Committed = Fix Released ** Changed in: ubuntu-clock-app (Ubuntu) Status: New = Fix Released -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-datetime in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1362341 Title: OneTime alarms are not automatically dismissed or delete after they are triggered Status in the base for Ubuntu mobile products: Fix Released Status in The Date and Time Indicator: Fix Released Status in Clock application for Ubuntu devices: Fix Released Status in indicator-datetime package in Ubuntu: Fix Released Status in ubuntu-clock-app package in Ubuntu: Fix Released Status in indicator-datetime package in Ubuntu RTM: Fix Released Bug description: Steps to reproduce: 1. Create a one time alarm to ring in a few minutes 2. Let the alarm ring 3. Dismiss the alarm What happens: The OneTime alarm is still shown as enabled and as a result shows the wrong status in the clock app. The alarm is no longer shown in the indicator-datetime. What should happen: The OneTime alarm is either disabled or deleted from the alarm model. The clock app cannot disable the alarm since most likely the clock app is not even open at the time the alarm is triggered. Since the alarm is no longer shown in the indicator-datetime, my intuition tells me that indicator-datetime and EDS did its job. Its now up to the SDK Alarms API to update the alarm model correctly. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1362341/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1314095] Re: Unity Lockscreen in 14.04 can't unlock when using LDAP account
Hi, Grzegorz Gutowski (gzegzol) wrote on 2014-04-29: Without suid it seems that call (with correct username) to getspnam in function get_account_info in file passverify.c in pam/modules/pam_unix returns NULL. I don't understand this behaviour. I wrote a simple c program that calls getspnam and it works as expected when called from unprivileged user. A call to getspnam(3) as an unprivileged user returns NULL; that's expected. (nss_compat returns errno = EACCESS since we can't read /etc/shadow; nss_ldapd returns errno = ENOENT as a generic not found code.) The unix_chkpwd helper is sgid to shadow so that it can read /etc/shadow, but nss_ldapd still returns ENOENT to shadow queries. If we make unix_chkpwd suid, then nss_ldapd returns real shadow results; but this is only a workaround (and a potentially dangerous one, at that). What I see happening when I attempt to unlock the screen: - the auth stack is fine; - in the account stack, pam_unix returns PAM_AUTHINFO_UNAVAIL (from unix_chkpwd), and it falls into pam_deny after that (since pam_ldap is Additional). gnome-screensaver works only because it actually ignores the result from the account stack and proceeds anyway: http://bazaar.launchpad.net /~ubuntu-branches/ubuntu/trusty/gnome-screensaver/trusty/view/head:/src /gs-auth-pam.c#L519 Some possible workarounds are: - chmod u+s /sbin/unix_chkpwd (potentially dangerous, not recommended); - dpkg-reconfigure libnss-ldapd and disable the shadow service (then pam_unix doesn't try consulting it); - use libnss-ldap instead of libnss-ldapd, since it allows everyone to read shadow entries; - use libnss-sss instead of libnss-ldapd, since it does not support the shadow service at all (in trusty, at least); - make libpam-ldapd's account rule Primary instead of Additional (but this was already done and subsequently reverted by its maintainer in 0.8.8-1 and 0.8.8-2). I'm not sure why some people reported experiencing this bug when using libnss-ldap or libnss-sss. I'd want to review their PAM and NSS setups in that case. This is all about trusty so far... still have to look at utopic/vivid. -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1314095 Title: Unity Lockscreen in 14.04 can't unlock when using LDAP account Status in Unity: Confirmed Status in unity package in Ubuntu: Confirmed Bug description: My setup is: Ubuntu 14.04 LTS, ldap accounts, krb5 authentication, Lightdm, Unity session ldap+krb5 is configured using nss-ldapd and nslcd. It works fine. getent passwd and getent shadow works fine. I am able to login in console without any problems. I was able to login in lightdm. Then I used the lock screen. I could not disable the lock screen using my password. I rebooted my computer. Now: After logging in through lightdm, the unity lockscreen locks the screen immediately and I can not disable it using my password. From my short inspection of auth.log and unix_chkpwd sources it seems, that unix_chkpwd works fine when called from lightdm and fails to get user info when called from unity lockscreen. lsb_release -rd Description: Ubuntu 14.04 LTS Release: 14.04 apt-cache policy unity lightdm libpam-modules unity: Installed: 7.2.0+14.04.20140416-0ubuntu1 Candidate: 7.2.0+14.04.20140416-0ubuntu1 Version table: *** 7.2.0+14.04.20140416-0ubuntu1 0 500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status lightdm: Installed: 1.10.0-0ubuntu3 Candidate: 1.10.0-0ubuntu3 Version table: *** 1.10.0-0ubuntu3 0 500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status libpam-modules: Installed: 1.1.8-1ubuntu2 Candidate: 1.1.8-1ubuntu2 Version table: *** 1.1.8-1ubuntu2 0 500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status Contents of /var/log/auth.log: Apr 29 06:49:27 localhost lightdm: pam_succeed_if(lightdm:auth): requirement user ingroup nopasswdlogin not met by user user Apr 29 06:49:31 localhost lightdm: pam_unix(lightdm:auth): authentication failure; logname= uid=0 euid=0 tty=:2 ruser= rhost= user=user Apr 29 06:49:31 localhost lightdm: pam_krb5(lightdm:auth): user user authenticated as user@NETWORK Apr 29 06:49:32 localhost lightdm[15604]: pam_unix(lightdm-greeter:session): session closed for user lightdm Apr 29 06:49:37 localhost unix_chkpwd[15825]: check pass; user unknown Apr 29 06:49:37 localhost unix_chkpwd[15825]: password check failed for user (user) Apr 29 06:49:37 localhost compiz: pam_unix(lightdm:auth): authentication failure; logname= uid=1001 euid=1001 tty= ruser= rhost= user=user Apr 29 06:49:37 localhost compiz: pam_krb5(lightdm:auth): user user authenticated
[Dx-packages] [Bug 269904] Re: Screen refresh problems with nvidia cards
I'd been experiencing this bug for a few days now. It stared after installing the proprietary NVIDIA driver. It was SUPER annoying. But I installed compiz from trusty-proposed and it plagues me no longer! Before, this bug would show itself once every few minutes. But now, it's been about 4 hours with no sign of it! And I haven't noticed any new bugs either. Not sure what info you all need, but here's some: ryan@charles:~$ compiz --version Compiz 0.9.11.3 ryan@charles:~$ cat /proc/driver/nvidia/version NVRM version: NVIDIA UNIX x86_64 Kernel Module 340.29 Thu Jul 31 20:23:19 PDT 2014 GCC version: gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1) Let me know if you need any more info. And thank you so much. -- You received this bug notification because you are a member of DX Packages, which is subscribed to compiz-plugins-main in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/269904 Title: Screen refresh problems with nvidia cards Status in Compiz: Fix Released Status in Compiz 0.9.11 series: In Progress Status in Compiz Core: New Status in Compiz Core 0.9.8 series: New Status in compiz package in Ubuntu: Fix Released Status in compiz-fusion-plugins-main package in Ubuntu: Fix Released Status in compiz-plugins-main package in Ubuntu: Fix Released Status in compiz source package in Precise: New Status in compiz-plugins-main source package in Precise: Confirmed Status in compiz source package in Trusty: Fix Committed Status in compiz-plugins-main source package in Trusty: Invalid Status in compiz source package in Intrepid: Fix Released Status in compiz-plugins-main source package in Intrepid: Won't Fix Status in compiz-fusion-plugins-main package in Debian: Fix Released Bug description: [Impact] Users of Nvidia gfx using the proprietary driver may see screen corruption during certain operations. [Test Case] * Install an Nvidia graphics adapter and the proprietary driver. * Observe the graphics corrupt. * Install the version of Compiz with this fix. * Observe corruption is gone. [Regression Potential] The patch for this was provided by Nvidia. There could be some corner cases users hit that may cause other issues. That said, enough testing has been done to confidently say that the gains provided by this fix far outweigh any corner cases. --- Original Description: == Proposed compiz-fusion-plugins-main patch == See comment 234 by Anders Kaseorg and attached compiz-fusion-plugins-main_0.8.2-0ubuntu2.debdiff. == Original report == Binary package hint: compiz I'm using latest compiz on intrepid. Since jockey-gtk does not work on my box (I already filed a bug), I manually installed nvidia-glx-177 and added the driver → nvidia line to xorg.conf. Now I seem to be having some screen refresh problems when using compiz: parts of the screen are refreshed, but others aren't. That means nautilus doesn't show files or folders until I move the cursor over them, firefox doesn't show webpages properly until I scroll down, and so on. Please, tell me if there is any additional info I can provide to find out the cause. To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/269904/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1314095] Re: Unity Lockscreen in 14.04 can't unlock when using LDAP account
** Changed in: nss-pam-ldapd (Debian) Status: Unknown = Fix Released -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1314095 Title: Unity Lockscreen in 14.04 can't unlock when using LDAP account Status in Unity: Confirmed Status in nss-pam-ldapd package in Ubuntu: New Status in unity package in Ubuntu: Confirmed Status in nss-pam-ldapd package in Debian: Fix Released Bug description: My setup is: Ubuntu 14.04 LTS, ldap accounts, krb5 authentication, Lightdm, Unity session ldap+krb5 is configured using nss-ldapd and nslcd. It works fine. getent passwd and getent shadow works fine. I am able to login in console without any problems. I was able to login in lightdm. Then I used the lock screen. I could not disable the lock screen using my password. I rebooted my computer. Now: After logging in through lightdm, the unity lockscreen locks the screen immediately and I can not disable it using my password. From my short inspection of auth.log and unix_chkpwd sources it seems, that unix_chkpwd works fine when called from lightdm and fails to get user info when called from unity lockscreen. lsb_release -rd Description: Ubuntu 14.04 LTS Release: 14.04 apt-cache policy unity lightdm libpam-modules unity: Installed: 7.2.0+14.04.20140416-0ubuntu1 Candidate: 7.2.0+14.04.20140416-0ubuntu1 Version table: *** 7.2.0+14.04.20140416-0ubuntu1 0 500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status lightdm: Installed: 1.10.0-0ubuntu3 Candidate: 1.10.0-0ubuntu3 Version table: *** 1.10.0-0ubuntu3 0 500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status libpam-modules: Installed: 1.1.8-1ubuntu2 Candidate: 1.1.8-1ubuntu2 Version table: *** 1.1.8-1ubuntu2 0 500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status Contents of /var/log/auth.log: Apr 29 06:49:27 localhost lightdm: pam_succeed_if(lightdm:auth): requirement user ingroup nopasswdlogin not met by user user Apr 29 06:49:31 localhost lightdm: pam_unix(lightdm:auth): authentication failure; logname= uid=0 euid=0 tty=:2 ruser= rhost= user=user Apr 29 06:49:31 localhost lightdm: pam_krb5(lightdm:auth): user user authenticated as user@NETWORK Apr 29 06:49:32 localhost lightdm[15604]: pam_unix(lightdm-greeter:session): session closed for user lightdm Apr 29 06:49:37 localhost unix_chkpwd[15825]: check pass; user unknown Apr 29 06:49:37 localhost unix_chkpwd[15825]: password check failed for user (user) Apr 29 06:49:37 localhost compiz: pam_unix(lightdm:auth): authentication failure; logname= uid=1001 euid=1001 tty= ruser= rhost= user=user Apr 29 06:49:37 localhost compiz: pam_krb5(lightdm:auth): user user authenticated as user@NETWORK Apr 29 06:49:37 localhost unix_chkpwd[15826]: could not obtain user info (user) Apr 29 06:49:37 localhost unix_chkpwd[15827]: could not obtain user info (user) Apr 29 06:49:37 localhost compiz: pam_succeed_if(lightdm:auth): requirement user ingroup nopasswdlogin not met by user user cat /etc/pam.d/common-auth account requiredpam_unix.so authrequiredpam_group.so auth [success=2 default=ignore] pam_unix.so try_first_pass nullok_secure auth [success=1 default=ignore] pam_krb5.so try_first_pass minimum_uid=200 authrequisite pam_deny.so authrequiredpam_permit.so authoptionalpam_afs_session.so minimum_uid=200 authoptionalpam_ecryptfs.so unwrap authoptionalpam_cap.so cat /etc/pam.d/common-account account requiredpam_unix.so cat /etc/pam.d/lightdm authrequisite pam_nologin.so authsufficient pam_succeed_if.so user ingroup nopasswdlogin @include common-auth authoptionalpam_gnome_keyring.so @include common-account session [success=ok ignore=ignore module_unknown=ignore default=bad] pam_selinux.so close authoptionalpam_group.so session requiredpam_limits.so @include common-session session [success=ok ignore=ignore module_unknown=ignore default=bad] pam_selinux.so open session optionalpam_gnome_keyring.so auto_start session requiredpam_env.so readenv=1 session requiredpam_env.so readenv=1 user_readenv=1 envfile=/etc/default/locale @include common-password To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1314095/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 269904] Re: Screen refresh problems with nvidia cards
** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of DX Packages, which is subscribed to compiz-plugins-main in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/269904 Title: Screen refresh problems with nvidia cards Status in Compiz: Fix Released Status in Compiz 0.9.11 series: In Progress Status in Compiz Core: New Status in Compiz Core 0.9.8 series: New Status in compiz package in Ubuntu: Fix Released Status in compiz-fusion-plugins-main package in Ubuntu: Fix Released Status in compiz-plugins-main package in Ubuntu: Fix Released Status in compiz source package in Precise: New Status in compiz-plugins-main source package in Precise: Confirmed Status in compiz source package in Trusty: Fix Committed Status in compiz-plugins-main source package in Trusty: Invalid Status in compiz source package in Intrepid: Fix Released Status in compiz-plugins-main source package in Intrepid: Won't Fix Status in compiz-fusion-plugins-main package in Debian: Fix Released Bug description: [Impact] Users of Nvidia gfx using the proprietary driver may see screen corruption during certain operations. [Test Case] * Install an Nvidia graphics adapter and the proprietary driver. * Observe the graphics corrupt. * Install the version of Compiz with this fix. * Observe corruption is gone. [Regression Potential] The patch for this was provided by Nvidia. There could be some corner cases users hit that may cause other issues. That said, enough testing has been done to confidently say that the gains provided by this fix far outweigh any corner cases. --- Original Description: == Proposed compiz-fusion-plugins-main patch == See comment 234 by Anders Kaseorg and attached compiz-fusion-plugins-main_0.8.2-0ubuntu2.debdiff. == Original report == Binary package hint: compiz I'm using latest compiz on intrepid. Since jockey-gtk does not work on my box (I already filed a bug), I manually installed nvidia-glx-177 and added the driver → nvidia line to xorg.conf. Now I seem to be having some screen refresh problems when using compiz: parts of the screen are refreshed, but others aren't. That means nautilus doesn't show files or folders until I move the cursor over them, firefox doesn't show webpages properly until I scroll down, and so on. Please, tell me if there is any additional info I can provide to find out the cause. To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/269904/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1314095] Re: Unity Lockscreen in 14.04 can't unlock when using LDAP account
Ahh, right. So this is almost certainly the change that fixed it for utopic: - nslcd will now return partial shadow information to non-root users to avoid authorisation problems with setgid shadow authentication helpers with some PAM stacks (closes: #706913) I bet backporting that to trusty will resolve this. ** Also affects: nss-pam-ldapd (Ubuntu) Importance: Undecided Status: New ** Bug watch added: Debian Bug tracker #706913 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=706913 ** Also affects: nss-pam-ldapd (Debian) via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=706913 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1314095 Title: Unity Lockscreen in 14.04 can't unlock when using LDAP account Status in Unity: Confirmed Status in nss-pam-ldapd package in Ubuntu: New Status in unity package in Ubuntu: Confirmed Status in nss-pam-ldapd package in Debian: Unknown Bug description: My setup is: Ubuntu 14.04 LTS, ldap accounts, krb5 authentication, Lightdm, Unity session ldap+krb5 is configured using nss-ldapd and nslcd. It works fine. getent passwd and getent shadow works fine. I am able to login in console without any problems. I was able to login in lightdm. Then I used the lock screen. I could not disable the lock screen using my password. I rebooted my computer. Now: After logging in through lightdm, the unity lockscreen locks the screen immediately and I can not disable it using my password. From my short inspection of auth.log and unix_chkpwd sources it seems, that unix_chkpwd works fine when called from lightdm and fails to get user info when called from unity lockscreen. lsb_release -rd Description: Ubuntu 14.04 LTS Release: 14.04 apt-cache policy unity lightdm libpam-modules unity: Installed: 7.2.0+14.04.20140416-0ubuntu1 Candidate: 7.2.0+14.04.20140416-0ubuntu1 Version table: *** 7.2.0+14.04.20140416-0ubuntu1 0 500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status lightdm: Installed: 1.10.0-0ubuntu3 Candidate: 1.10.0-0ubuntu3 Version table: *** 1.10.0-0ubuntu3 0 500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status libpam-modules: Installed: 1.1.8-1ubuntu2 Candidate: 1.1.8-1ubuntu2 Version table: *** 1.1.8-1ubuntu2 0 500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status Contents of /var/log/auth.log: Apr 29 06:49:27 localhost lightdm: pam_succeed_if(lightdm:auth): requirement user ingroup nopasswdlogin not met by user user Apr 29 06:49:31 localhost lightdm: pam_unix(lightdm:auth): authentication failure; logname= uid=0 euid=0 tty=:2 ruser= rhost= user=user Apr 29 06:49:31 localhost lightdm: pam_krb5(lightdm:auth): user user authenticated as user@NETWORK Apr 29 06:49:32 localhost lightdm[15604]: pam_unix(lightdm-greeter:session): session closed for user lightdm Apr 29 06:49:37 localhost unix_chkpwd[15825]: check pass; user unknown Apr 29 06:49:37 localhost unix_chkpwd[15825]: password check failed for user (user) Apr 29 06:49:37 localhost compiz: pam_unix(lightdm:auth): authentication failure; logname= uid=1001 euid=1001 tty= ruser= rhost= user=user Apr 29 06:49:37 localhost compiz: pam_krb5(lightdm:auth): user user authenticated as user@NETWORK Apr 29 06:49:37 localhost unix_chkpwd[15826]: could not obtain user info (user) Apr 29 06:49:37 localhost unix_chkpwd[15827]: could not obtain user info (user) Apr 29 06:49:37 localhost compiz: pam_succeed_if(lightdm:auth): requirement user ingroup nopasswdlogin not met by user user cat /etc/pam.d/common-auth account requiredpam_unix.so authrequiredpam_group.so auth [success=2 default=ignore] pam_unix.so try_first_pass nullok_secure auth [success=1 default=ignore] pam_krb5.so try_first_pass minimum_uid=200 authrequisite pam_deny.so authrequiredpam_permit.so authoptionalpam_afs_session.so minimum_uid=200 authoptionalpam_ecryptfs.so unwrap authoptionalpam_cap.so cat /etc/pam.d/common-account account requiredpam_unix.so cat /etc/pam.d/lightdm authrequisite pam_nologin.so authsufficient pam_succeed_if.so user ingroup nopasswdlogin @include common-auth authoptionalpam_gnome_keyring.so @include common-account session [success=ok ignore=ignore module_unknown=ignore default=bad] pam_selinux.so close authoptionalpam_group.so session requiredpam_limits.so @include common-session session [success=ok ignore=ignore
Re: [Dx-packages] [Bug 1414617] Volume Dialog Does't Appear
The error is quite repeable on this device, however, there are lots of errors starting to occur on the latest RTM so it might be a device wide issue. Log attached. n Thursday, 12 February 2015 16:00:50 UTC, Ted Gould wrote: I'm not seeing that. Can you attach your indicator-sound and unit y8 logs from ~/.cache/upstart/ please? ** Changed in: indicator-sound (Ubuntu) Status: New = Incomplete ** Attachment added: unity8.log https://bugs.launchpad.net/bugs/1414617/+attachment/4318137/+files/unity8.log -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-sound in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1414617 Title: Volume Dialog Does't Appear Status in indicator-sound package in Ubuntu: Incomplete Status in unity8 package in Ubuntu: Opinion Bug description: The volume dialog fails to appear on screen but the volume is adjusted. I have tried a number of restarts without change. Are any logs or debug information I can provide? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/1414617/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1302462] Re: network icon disappeared in xubuntu
As mentioned in comment #15, a misconfiguration is the main cause for this particular problem. We need to test the fix from bug 1411959 and eventually backport it to 14.04. ** Package changed: xfce4-panel (Ubuntu) = indicator-application (Ubuntu) -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-application in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1302462 Title: network icon disappeared in xubuntu Status in indicator-application package in Ubuntu: Incomplete Bug description: Following the latest Xubuntu 14.04 updates, the network icon disapperead from the xfce panel. I tried the workaround mentioned on https://wiki.ubuntu.com/Xubuntu/Roadmap/Specifications/Trusty/Gtk3Indicators (As a workaround, put INDICATOR_ALLOW_NO_WATCHERS=yes in /etc/environment and reboot) but it didn't fix anything. I can bring the icon into the panel by running sudo nm-applet, unfortunately this still isn't functional since any interactive dialog needed by NetworkManager (for example a wifi password dialog) will never display, and therefore connecting will fail. (I filed this bug against xfce4-panel, but there might be a better choice) ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xfce4-panel 4.11.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-22.44-generic 3.13.8 Uname: Linux 3.13.0-22-generic x86_64 ApportVersion: 2.14-0ubuntu1 Architecture: amd64 CurrentDesktop: XFCE Date: Fri Apr 4 12:11:51 2014 InstallationDate: Installed on 2014-03-01 (33 days ago) InstallationMedia: Xubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140225) ProcEnviron: LANGUAGE=fr_FR TERM=xterm PATH=(custom, no user) LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: xfce4-panel UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-application/+bug/1302462/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1351555] Re: Webapps don't integrating in Unity
Is there any workaround? Or how i can practicipate on this issue? -- You received this bug notification because you are a member of DX Packages, which is subscribed to libunity-webapps in Ubuntu. https://bugs.launchpad.net/bugs/1351555 Title: Webapps don't integrating in Unity Status in WebApps: libunity: Confirmed Status in libunity-webapps package in Ubuntu: Confirmed Bug description: Such list of tested webapps aren't making any Unity integration since 14.04: YouTube; vkcom; YandexMusic; GMail; lastfm Althoug they are working in 13.10 as expected. They no more openning in default browser, but they do in webbrowser-app, even when installed by default browser. It's both correct for firefox, chromium and opera(other user says) Distributor ID: Ubuntu Description: Ubuntu 14.04.1 LTS Release: 14.04 Codename: trusty Firefox version: 31.0 Chromium version: Chromium 34.0.1847.116 Ubuntu 14.04 aura Opera: ??? ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity-webapps-service 2.5.0~+14.04.20140409-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2 Uname: Linux 3.13.0-29-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CurrentDesktop: Unity Date: Sat Aug 2 10:58:47 2014 ExecutablePath: /usr/lib/libunity-webapps/unity-webapps-service SourcePackage: libunity-webapps UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/libunity-webapps/+bug/1351555/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1302462] [NEW] network icon disappeared in xubuntu
You have been subscribed to a public bug: Following the latest Xubuntu 14.04 updates, the network icon disapperead from the xfce panel. I tried the workaround mentioned on https://wiki.ubuntu.com/Xubuntu/Roadmap/Specifications/Trusty/Gtk3Indicators (As a workaround, put INDICATOR_ALLOW_NO_WATCHERS=yes in /etc/environment and reboot) but it didn't fix anything. I can bring the icon into the panel by running sudo nm-applet, unfortunately this still isn't functional since any interactive dialog needed by NetworkManager (for example a wifi password dialog) will never display, and therefore connecting will fail. (I filed this bug against xfce4-panel, but there might be a better choice) ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xfce4-panel 4.11.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-22.44-generic 3.13.8 Uname: Linux 3.13.0-22-generic x86_64 ApportVersion: 2.14-0ubuntu1 Architecture: amd64 CurrentDesktop: XFCE Date: Fri Apr 4 12:11:51 2014 InstallationDate: Installed on 2014-03-01 (33 days ago) InstallationMedia: Xubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140225) ProcEnviron: LANGUAGE=fr_FR TERM=xterm PATH=(custom, no user) LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: xfce4-panel UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: indicator-application (Ubuntu) Importance: Critical Status: Incomplete ** Tags: amd64 apport-bug trusty -- network icon disappeared in xubuntu https://bugs.launchpad.net/bugs/1302462 You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-application in Ubuntu. -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1421396] [NEW] Volume notification does not show if phone is muted
You have been subscribed to a public bug: Steps to reproduce 1. Turn the volume all the way down (to mute) 2. Wait for the volume notification to disappear 3. Press volume decrease key again Expected behavior: volume notification appears, and gives user feedback that phone is muted Actual behavior: volume notification does not appear ** Affects: indicator-sound (Ubuntu) Importance: Undecided Assignee: Josh Arenson (josharenson) Status: New -- Volume notification does not show if phone is muted https://bugs.launchpad.net/bugs/1421396 You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-sound in Ubuntu. -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1378048] Re: Make music controls work in the sound indicator
seems like this is not in the backlog yet so pushing out ** Changed in: canonical-devices-system-image Milestone: ww09-2015 = ww11-2015 ** Changed in: canonical-devices-system-image Assignee: Canonical Devices Products (canonical-devices-products-team) = Michael Frey (mfrey) -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-sound in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1378048 Title: Make music controls work in the sound indicator Status in the base for Ubuntu mobile products: Confirmed Status in indicator-sound package in Ubuntu: Invalid Status in media-hub package in Ubuntu: Confirmed Status in media-hub package in Ubuntu RTM: Confirmed Bug description: Steps: 1. Play an album in the music player 2. Pull down sound indicator 3. Click forward button Observed: the music does not advance Expected: the music advances To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1378048/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1388235] Re: [indicators] Battery icon turns red at 30%
** Changed in: canonical-devices-system-image Milestone: ww07-2015 = ww09-2015 ** Changed in: canonical-devices-system-image Assignee: (unassigned) = Thomas Strehl (strehl-t) -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-power in Ubuntu. https://bugs.launchpad.net/bugs/1388235 Title: [indicators] Battery icon turns red at 30% Status in the base for Ubuntu mobile products: In Progress Status in Ubuntu UX bugs: Triaged Status in indicator-power package in Ubuntu: In Progress Status in ubuntu-themes package in Ubuntu: In Progress Bug description: This seems a bit pessimistic since the phone still has a great deal of capacity and time left, perhaps 15 or 20% is a better threshold To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1388235/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1393024] Re: Graphical corruption with hidpi scaling
** Also affects: compiz Importance: Undecided Status: New -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1393024 Title: Graphical corruption with hidpi scaling Status in Compiz: New Status in Unity: Incomplete Status in unity package in Ubuntu: Incomplete Bug description: With a hidpi scaling greater or equal than 2 there is graphical corruption of the window borders in gtk3 apps. Steps to reproduce: 1. Set hidpi scaling to 2. 2. Enlarge a window for nautilus or eye of gnome. Probably it is necessary to do resize the window more than one time to spot the problem. 3. See corrupted window border on the right and/or the bottom. Expected behavior: Clean rendering Ubuntu 14.10 64 Bit Compiz 0.9.12+14.10.20140918-0ubuntu1 Unity 7.3.1+14.10.20141016-0ubuntu1 ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: unity 7.3.1+14.10.20141016-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4 Uname: Linux 3.16.0-24-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus.0: Error: [Errno 21] Ist ein Verzeichnis: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 331.89 Tue Jul 1 13:30:18 PDT 2014 GCC version: gcc version 4.9.1 (Ubuntu 4.9.1-16ubuntu6) .tmp.unity.support.test.0: ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Sat Nov 15 16:36:40 2014 DistUpgraded: Fresh install DistroCodename: utopic DistroVariant: ubuntu GraphicsCard: NVIDIA Corporation GK106 [GeForce GTX 660] [10de:11c0] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Device [1458:354e] InstallationDate: Installed on 2014-11-12 (2 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) MachineType: Gigabyte Technology Co., Ltd. GA-990FXA-D3 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-24-generic root=UUID=2a652086-a4da-44ed-ae7f-7b994401ef8b ro quiet splash SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/30/2012 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F7 dmi.board.name: GA-990FXA-D3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF7:bd05/30/2012:svnGigabyteTechnologyCo.,Ltd.:pnGA-990FXA-D3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-990FXA-D3:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: GA-990FXA-D3 dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz 1:0.9.12+14.10.20140918-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.56-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.0-0ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.0-0ubuntu3 version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A version.xserver-xorg-core: xserver-xorg-core 2:1.16.0-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.914-1~exp1ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2 xserver.bootTime: Sat Nov 15 15:00:14 2014 xserver.configfile: default xserver.errors: open /dev/fb0: No such file or directory xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.16.0-1ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1393024/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1385331] Re: Notification LED stays on when no messages in notification center
** Changed in: canonical-devices-system-image Milestone: ww07-2015 = ww09-2015 ** Changed in: canonical-devices-system-image Assignee: (unassigned) = Thomas Strehl (strehl-t) -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-messages in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1385331 Title: Notification LED stays on when no messages in notification center Status in the base for Ubuntu mobile products: In Progress Status in indicator-messages package in Ubuntu: Confirmed Status in qmenumodel package in Ubuntu: Fix Released Status in unity8 package in Ubuntu: Fix Released Status in qmenumodel package in Ubuntu RTM: Fix Released Status in unity8 package in Ubuntu RTM: Fix Released Bug description: Observed the notification LED staying on even though there were no notifications in the indicators and the notification icon was greyed out. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1385331/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1387691] Re: Media Player should not be visible in the app scope and launcher
pushing out as no way it lands this week ** Changed in: canonical-devices-system-image Milestone: ww09-2015 = ww11-2015 ** Changed in: canonical-devices-system-image Assignee: (unassigned) = Bill Filler (bfiller) -- You received this bug notification because you are a member of DX Packages, which is subscribed to url-dispatcher in Ubuntu. https://bugs.launchpad.net/bugs/1387691 Title: Media Player should not be visible in the app scope and launcher Status in the base for Ubuntu mobile products: In Progress Status in Ubuntu UX bugs: Fix Committed Status in mediaplayer-app package in Ubuntu: In Progress Status in unity8 package in Ubuntu: Invalid Status in url-dispatcher package in Ubuntu: In Progress Status in mediaplayer-app package in Ubuntu RTM: In Progress Status in url-dispatcher package in Ubuntu RTM: In Progress Bug description: The mediaplayer is an 'auxiliary app' in the current design approach. That means that its purpouse it playback media launched by other apps (e.g Messaging) or scopes (e.g. Videos). It should not be launched from the App scopes. However, the 'Update' section System Settings should still display it when an update to mediaplayer is available. Current behaviour - Mediaplayer app displayed in App Scope, Launcher and Settings Desired behaviour - Mediaplayer app not displayed in App Scope or Launcher - Mediaplayer displayed in Settings Update To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1387691/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1375017] Re: battery indicator does not show actual status
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: indicator-power (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-power in Ubuntu. https://bugs.launchpad.net/bugs/1375017 Title: battery indicator does not show actual status Status in indicator-power package in Ubuntu: Confirmed Bug description: Battery tray indicator does not change actual status in a real time. It changes only after reboot. And still unchanged until next reboot. Nothing affects it, nor draining, nor charging. ProblemType: Bug Architecture: x86_64 Description: Ubuntu 14.04.1 LTS Release: 14.04 indicator-power: Installed: 12.10.6+14.04.20140411-0ubuntu1 Candidate: 12.10.6+14.04.20140411-0ubuntu1 Version table: *** 12.10.6+14.04.20140411-0ubuntu1 0 500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status 12.10.6+13.10.20131008-0ubuntu1 0 500 http://archive.ubuntu.com/ubuntu/ saucy/main amd64 Packages compiz: Installed: 1:0.9.11.2+14.04.20140714-0ubuntu1 Candidate: 1:0.9.11.2+14.04.20140714-0ubuntu1 Version table: *** 1:0.9.11.2+14.04.20140714-0ubuntu1 0 500 http://archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:0.9.11+14.04.20140409-0ubuntu1 0 500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 1:0.9.10+13.10.20131011-0ubuntu1 0 500 http://archive.ubuntu.com/ubuntu/ saucy/main amd64 Packages unity: Installed: 7.2.2+14.04.20140714-0ubuntu1.1 Candidate: 7.2.2+14.04.20140714-0ubuntu1.1 Version table: *** 7.2.2+14.04.20140714-0ubuntu1.1 0 500 http://archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu/ trusty-security/main amd64 Packages 500 http://security.ubuntu.com/ubuntu/ trusty-security/main amd64 Packages 100 /var/lib/dpkg/status 7.2.2+14.04.20140714-0ubuntu1systray1 0 500 http://ppa.launchpad.net/timekiller/unity-systrayfix/ubuntu/ trusty/main amd64 Packages 7.2.0+14.04.20140416-0ubuntu1 0 500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 7.1.2+13.10.20131014.1-0ubuntu1 0 500 http://archive.ubuntu.com/ubuntu/ saucy/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-power/+bug/1375017/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1407709] Re: Google Maps and Here Maps should handle custom intent:// URLs
** Changed in: canonical-devices-system-image Milestone: ww07-2015 = ww09-2015 ** Changed in: canonical-devices-system-image Assignee: (unassigned) = David Barth (dbarth) -- You received this bug notification because you are a member of DX Packages, which is subscribed to url-dispatcher in Ubuntu. https://bugs.launchpad.net/bugs/1407709 Title: Google Maps and Here Maps should handle custom intent:// URLs Status in the base for Ubuntu mobile products: In Progress Status in The Webapps-core project: Fix Released Status in Web Browser App: Fix Released Status in url-dispatcher package in Ubuntu: Fix Released Status in webbrowser-app package in Ubuntu: Fix Released Status in url-dispatcher package in Ubuntu RTM: In Progress Status in webbrowser-app package in Ubuntu RTM: In Progress Bug description: ubuntu-rtm image 184 The maps apps in the system should register and respond to appropriate urls from the browser (not sure of the format, map:// or directions:// - need to check) Steps to reproduce: 1) open browser 2) type Asai Belmont MA in the url bar and press enter 3) this will do a google search for the resturant 4) click on the Directions button Expected result: - One of the maps apps should open displaying directions for the resturant Actual results: - no app is launched To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1407709/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1421396] Re: Volume notification does not show if phone is muted
** Package changed: unity8 (Ubuntu) = indicator-sound (Ubuntu) ** Changed in: indicator-sound (Ubuntu) Assignee: Josh Arenson (josharenson) = (unassigned) -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-sound in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1421396 Title: Volume notification does not show if phone is muted Status in indicator-sound package in Ubuntu: New Bug description: Steps to reproduce 1. Turn the volume all the way down (to mute) 2. Wait for the volume notification to disappear 3. Press volume decrease key again Expected behavior: volume notification appears, and gives user feedback that phone is muted Actual behavior: volume notification does not appear To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/1421396/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1393843] [NEW] Log in prompt appears twice or three times after suspend
You have been subscribed to a public bug: Hi, since my update to 14.04.1 LTS I experience difficulties with unlocking my screen after waking up my maschine. After logging the desktio is shown only for a short moment, following another screen lock. I have to unlock the screen again then. This happens after every suspend, sometimes even three times. I am happy to provide additional data. cheers ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: lightdm 1.10.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8 Uname: Linux 3.13.0-39-generic i686 ApportVersion: 2.14.1-0ubuntu3.5 Architecture: i386 CurrentDesktop: Unity Date: Tue Nov 18 17:03:00 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2013-01-13 (673 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release i386 (20121017.2) LightdmConfig: [SeatDefaults] user-session=ubuntu greeter-session=unity-greeter allow-guest=true ProcEnviron: LANGUAGE=de_DE PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: lightdm UpgradeStatus: Upgraded to trusty on 2014-09-14 (64 days ago) ** Affects: unity-greeter Importance: Undecided Status: New ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 trusty -- Log in prompt appears twice or three times after suspend https://bugs.launchpad.net/bugs/1393843 You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1388235] Re: [indicators] Battery icon turns red at 30%
** Branch linked: lp:ubuntu/vivid-proposed/indicator-power ** Branch linked: lp:ubuntu/vivid-proposed/ubuntu-themes -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-power in Ubuntu. https://bugs.launchpad.net/bugs/1388235 Title: [indicators] Battery icon turns red at 30% Status in the base for Ubuntu mobile products: In Progress Status in Ubuntu UX bugs: Triaged Status in indicator-power package in Ubuntu: In Progress Status in ubuntu-themes package in Ubuntu: In Progress Bug description: This seems a bit pessimistic since the phone still has a great deal of capacity and time left, perhaps 15 or 20% is a better threshold To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1388235/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 832458] Re: ccsm crashed with KeyError in compizconfig.Plugin.ApplyStringExtensions (src/compizconfig.c:6780)(): '\xd0\t\x9b\n\x01'
** Changed in: compiz-compizconfig-python Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/832458 Title: ccsm crashed with KeyError in compizconfig.Plugin.ApplyStringExtensions (src/compizconfig.c:6780)(): '\xd0\t\x9b\n\x01' Status in Compiz Configuration Library - Python Bindings: Fix Released Status in Unity: Fix Released Status in compizconfig-python package in Ubuntu: Fix Released Status in unity package in Ubuntu: Fix Released Bug description: ubuntu11.10 alpha 3 kernel 3.0.9 window border disappeared suddenly and when i try to rest it from ccsm to back again the bug came out just like that TESTCASE: Open CCSM It wont crash ProblemType: Crash DistroRelease: Ubuntu 11.10 Package: compizconfig-settings-manager 0.9.5.92-0ubuntu1 ProcVersionSignature: Ubuntu 3.0.0-9.14-generic 3.0.3 Uname: Linux 3.0.0-9-generic i686 NonfreeKernelModules: wl Architecture: i386 Date: Wed Aug 24 04:25:08 2011 ExecutablePath: /usr/bin/ccsm InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release i386 (20101007) InterpreterPath: /usr/bin/python2.7 PackageArchitecture: all ProcCmdline: /usr/bin/python /usr/bin/ccsm PythonArgs: ['/usr/bin/ccsm'] SourcePackage: compizconfig-settings-manager Title: ccsm crashed with KeyError in compizconfig.Plugin.ApplyStringExtensions (src/compizconfig.c:6780)(): '\xd0\t\x9b\n\x01' UpgradeStatus: Upgraded to oneiric on 2011-08-19 (4 days ago) UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare To manage notifications about this bug go to: https://bugs.launchpad.net/compiz-compizconfig-python/+bug/832458/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 820080] Re: broken fallback icons for indicators
** Changed in: libappindicator/0.4 Status: Fix Committed = Fix Released ** Changed in: unity-foundations Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of DX Packages, which is subscribed to libappindicator in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/820080 Title: broken fallback icons for indicators Status in Libappindicator: Fix Released Status in libappindicator 0.4 series: Fix Released Status in libappindicator 0.5 series: Fix Released Status in Unity Foundations: Fix Released Status in jockey package in Ubuntu: Invalid Status in libappindicator package in Ubuntu: Fix Released Bug description: Starting Xubuntu, etc sessions with indicators (like bluetooth-applet or nm-applet) using libappindicator; if you remove the indicator widget from the panel, indicators will fallback to using legacy GtkTrayIcons. However, this appears to fail to load the icons that go with them. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: libgtk-3-0 3.1.10-0ubuntu1 ProcVersionSignature: Ubuntu 3.0.0-7.9-generic 3.0.0 Uname: Linux 3.0.0-7-generic x86_64 Architecture: amd64 Date: Tue Aug 2 17:52:06 2011 InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Alpha amd64 (20110715) ProcEnviron: LANGUAGE=fr_CA:fr PATH=(custom, user) LANG=fr_CA.UTF-8 SHELL=/bin/zsh SourcePackage: gtk+3.0 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/libappindicator/+bug/820080/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1313446] Re: window disappears on toggle shade
On my setup Ctrl+Alt+s is a keyboard shortcut for this broken Toggle shaded state thing. I've been really confused why windows keep ghosting and dying and sometimes taking down compiz with them when I try Ctrl+Alt+s. This shortcut is needed in Emacs, for instance. If this bug affects everyone and it is in fact a default shortcut key for everyone, can you at least disable the keyboard shortcut by default so you're not hijacking useful keypresses and treating them as a shortcut to break everything? -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1313446 Title: window disappears on toggle shade Status in Unity: Confirmed Status in unity package in Ubuntu: Confirmed Bug description: I used Unity Tweak Tool to enable Toggle Shade using middle click. When I click to top of the window, it rolls up and disappears. A ghost outline of the window appears and the only way to get the window back is by using Alt-tab. Sometimes, when reselecting the window using Alt-tab, Ubuntu freezes (crashes) and an internal error is generated. It seems to be related to Compiz but I'm not sure. An error report was generated and sent. Description: Ubuntu 14.04 LTS (64-bit) Release: 14.04 unity-tweak-tool 0.0.6ubuntu1 I expected the window would roll up and I'd be left with the window's top bar like with previous versions of Ubuntu. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1313446/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1176348] Re: title bar pop up menus corrupt display
[Expired for Unity because there has been no activity for 60 days.] ** Changed in: unity Status: Incomplete = Expired -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1176348 Title: title bar pop up menus corrupt display Status in Unity: Expired Status in unity package in Ubuntu: Expired Bug description: To reproduce: 1. Right click on window title bar. What should happen: Menu with window management functions appears. What happens instead: A rectangle the size of the menu appears. It contains a copy of the window contents. It cannot be interacted with in any way, and always appears above normal windows. It cannot be removed from the screen and appears on all desktops. Screenshot attached. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: unity 7.0.0daily13.04.18~13.04-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8 Uname: Linux 3.8.0-19-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 313.30 Wed Mar 27 16:56:45 PDT 2013 GCC version: gcc version 4.7.3 (Ubuntu/Linaro 4.7.3-1ubuntu1) .tmp.unity.support.test.0: ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Sat May 4 15:12:13 2013 DistUpgraded: Fresh install DistroCodename: raring DistroVariant: ubuntu DkmsStatus: nvidia-313-updates, 313.30, 3.8.0-19-generic, x86_64: installed virtualbox, 4.2.10, 3.8.0-19-generic, x86_64: installed GraphicsCard: NVIDIA Corporation GT215 [GeForce GT 240] [10de:0ca3] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Device [1458:34e2] InstallationDate: Installed on 2013-04-26 (7 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MachineType: System manufacturer System Product Name MarkForUpload: True ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-19-generic root=UUID=52fbfaf1-aa35-45f8-9a1c-b867ce923edd ro quiet splash SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/25/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0704 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M4A79XTD EVO dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0X dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0704:bd11/25/2009:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A79XTDEVO:rvrRevX.0X:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz 1:0.9.9~daily13.04.18.1~13.04-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.43-0ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.1.1-0ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.1.1-0ubuntu3 version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A version.xserver-xorg-core: xserver-xorg-core 2:1.13.3-0ubuntu6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2b2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.1.0-0ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.6-0ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.7-0ubuntu1 xserver.bootTime: Sat Apr 27 02:50:07 2013 xserver.configfile: default xserver.errors: open /dev/dri/card0: No such file or directory open /dev/fb0: No such file or directory xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.13.3-0ubuntu6 To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1176348/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1176667] Re: Dash does not find files if they have underscores preceding or following in their names
[Expired for unity (Ubuntu) because there has been no activity for 60 days.] ** Changed in: unity (Ubuntu) Status: Incomplete = Expired -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1176667 Title: Dash does not find files if they have underscores preceding or following in their names Status in Unity: Expired Status in unity package in Ubuntu: Expired Bug description: So if a search for a file name with a keyword source it does not find the file that is named Open_source_inschools. However if I put an underscore before or after source like in _source the file is displayed in the Dash. Using Raring Ringtail. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: unity 7.0.0daily13.04.18~13.04-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-19.30-generic 3.8.8 Uname: Linux 3.8.0-19-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.9.2-0ubuntu8 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Sun May 5 23:31:15 2013 InstallationDate: Installed on 2013-04-26 (9 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release i386 (20130424) MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=hr_HR.UTF-8 SHELL=/bin/bash SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1176667/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1176562] Re: Unity previews of jpg/jpeg files are upside down
[Expired for unity (Ubuntu) because there has been no activity for 60 days.] ** Changed in: unity (Ubuntu) Status: Incomplete = Expired -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1176562 Title: Unity previews of jpg/jpeg files are upside down Status in Unity: Expired Status in unity package in Ubuntu: Expired Bug description: Some JPG and JPEG files are displayed normally when thumbnails, but are rendered upside down when displayed in Unity previews. To reproduce: 1: Open a JPG image normally. 2: Open the dash. It should appear under recent files, displayed correctly. 3: Right-click it. The preview opens, and the image is displayed upside down. See attached screenshots. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: unity 7.0.0daily13.04.18~13.04-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-19.30-generic 3.8.8 Uname: Linux 3.8.0-19-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus.0: Error: [Errno 21] Er en filkatalog: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 310.44 Wed Mar 27 14:51:30 PDT 2013 GCC version: gcc version 4.7.3 (Ubuntu/Linaro 4.7.3-1ubuntu1) .tmp.unity.support.test.0: ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Sun May 5 17:14:07 2013 DistUpgraded: Fresh install DistroCodename: raring DistroVariant: ubuntu DkmsStatus: nvidia-310, 310.44, 3.8.0-19-generic, x86_64: installed virtualbox, 4.2.10, 3.8.0-19-generic, x86_64: installed GraphicsCard: NVIDIA Corporation GF104 [GeForce GTX 460] [10de:0e22] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ZOTAC International (MCO) Ltd. Device [19da:2166] InstallationDate: Installed on 2013-04-20 (15 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130420) MachineType: System manufacturer System Product Name MarkForUpload: True ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-19-generic root=UUID=7be9e12c-c012-4d62-8f5e-ffe0e56cc0e0 ro quiet splash SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/04/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1709 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P7H55-M PRO dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1709:bd01/04/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP7H55-MPRO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz 1:0.9.9~daily13.04.18.1~13.04-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.43-0ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.1.1-0ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.1.1-0ubuntu3 version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A version.xserver-xorg-core: xserver-xorg-core 2:1.13.3-0ubuntu6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2b2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.1.0-0ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.6-0ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.7-0ubuntu1 xserver.bootTime: Sun May 5 16:02:08 2013 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputMicrosft Microsoft Wireless Desktop Receiver 3.1 KEYBOARD, id 8 inputMicrosft Microsoft Wireless Desktop Receiver 3.1 KEYBOARD, id 9 inputLogitech Unifying Device. Wireless PID:101a MOUSE, id 10 xserver.errors: open /dev/dri/card0: No such file or directory open /dev/fb0: No such file or directory xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.13.3-0ubuntu6 To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1176562/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help :
[Dx-packages] [Bug 1176348] Re: title bar pop up menus corrupt display
[Expired for unity (Ubuntu) because there has been no activity for 60 days.] ** Changed in: unity (Ubuntu) Status: Incomplete = Expired -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1176348 Title: title bar pop up menus corrupt display Status in Unity: Expired Status in unity package in Ubuntu: Expired Bug description: To reproduce: 1. Right click on window title bar. What should happen: Menu with window management functions appears. What happens instead: A rectangle the size of the menu appears. It contains a copy of the window contents. It cannot be interacted with in any way, and always appears above normal windows. It cannot be removed from the screen and appears on all desktops. Screenshot attached. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: unity 7.0.0daily13.04.18~13.04-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8 Uname: Linux 3.8.0-19-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 313.30 Wed Mar 27 16:56:45 PDT 2013 GCC version: gcc version 4.7.3 (Ubuntu/Linaro 4.7.3-1ubuntu1) .tmp.unity.support.test.0: ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Sat May 4 15:12:13 2013 DistUpgraded: Fresh install DistroCodename: raring DistroVariant: ubuntu DkmsStatus: nvidia-313-updates, 313.30, 3.8.0-19-generic, x86_64: installed virtualbox, 4.2.10, 3.8.0-19-generic, x86_64: installed GraphicsCard: NVIDIA Corporation GT215 [GeForce GT 240] [10de:0ca3] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Device [1458:34e2] InstallationDate: Installed on 2013-04-26 (7 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MachineType: System manufacturer System Product Name MarkForUpload: True ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-19-generic root=UUID=52fbfaf1-aa35-45f8-9a1c-b867ce923edd ro quiet splash SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/25/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0704 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M4A79XTD EVO dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0X dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0704:bd11/25/2009:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A79XTDEVO:rvrRevX.0X:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz 1:0.9.9~daily13.04.18.1~13.04-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.43-0ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.1.1-0ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.1.1-0ubuntu3 version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A version.xserver-xorg-core: xserver-xorg-core 2:1.13.3-0ubuntu6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2b2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.1.0-0ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.6-0ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.7-0ubuntu1 xserver.bootTime: Sat Apr 27 02:50:07 2013 xserver.configfile: default xserver.errors: open /dev/dri/card0: No such file or directory open /dev/fb0: No such file or directory xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.13.3-0ubuntu6 To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1176348/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1176616] Re: Launcher is not working properly
[Expired for unity (Ubuntu) because there has been no activity for 60 days.] ** Changed in: unity (Ubuntu) Status: Incomplete = Expired -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1176616 Title: Launcher is not working properly Status in Unity: Expired Status in unity package in Ubuntu: Expired Bug description: On the desktop the launcher appears and works properly. However if there is a full size window open, the launcher just only pops up for a moment and quickly disappears. Also it is unable to click on the icons on the poping-up launcher instead you can only click on the things that is visible under the launcher. In case the window is not full size (i.e you can see the desktop while you have a window open on the screen) the launcher seems to be working fine most of the time. Sometimes however when there is/are window(s) open (not full size) launcher will not appear unless you click inside the open window anywhere. Then you can try the launcher again and it will appear this time. Ubuntu 13.04 upgraded from 12.10 64-bit AMD Phenom(tm) II X4 965 Processor × 4 Gallium 0.4 on AMD RS880 ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: unity 7.0.0daily13.04.18~13.04-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-19.30-generic 3.8.8 Uname: Linux 3.8.0-19-generic x86_64 ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Sun May 5 18:29:21 2013 InstallationDate: Installed on 2012-11-01 (185 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) MarkForUpload: True SourcePackage: unity UpgradeStatus: Upgraded to raring on 2013-05-04 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1176616/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1176562] Re: Unity previews of jpg/jpeg files are upside down
[Expired for Unity because there has been no activity for 60 days.] ** Changed in: unity Status: Incomplete = Expired -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1176562 Title: Unity previews of jpg/jpeg files are upside down Status in Unity: Expired Status in unity package in Ubuntu: Expired Bug description: Some JPG and JPEG files are displayed normally when thumbnails, but are rendered upside down when displayed in Unity previews. To reproduce: 1: Open a JPG image normally. 2: Open the dash. It should appear under recent files, displayed correctly. 3: Right-click it. The preview opens, and the image is displayed upside down. See attached screenshots. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: unity 7.0.0daily13.04.18~13.04-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-19.30-generic 3.8.8 Uname: Linux 3.8.0-19-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus.0: Error: [Errno 21] Er en filkatalog: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 310.44 Wed Mar 27 14:51:30 PDT 2013 GCC version: gcc version 4.7.3 (Ubuntu/Linaro 4.7.3-1ubuntu1) .tmp.unity.support.test.0: ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Sun May 5 17:14:07 2013 DistUpgraded: Fresh install DistroCodename: raring DistroVariant: ubuntu DkmsStatus: nvidia-310, 310.44, 3.8.0-19-generic, x86_64: installed virtualbox, 4.2.10, 3.8.0-19-generic, x86_64: installed GraphicsCard: NVIDIA Corporation GF104 [GeForce GTX 460] [10de:0e22] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ZOTAC International (MCO) Ltd. Device [19da:2166] InstallationDate: Installed on 2013-04-20 (15 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130420) MachineType: System manufacturer System Product Name MarkForUpload: True ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-19-generic root=UUID=7be9e12c-c012-4d62-8f5e-ffe0e56cc0e0 ro quiet splash SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/04/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1709 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P7H55-M PRO dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1709:bd01/04/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP7H55-MPRO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz 1:0.9.9~daily13.04.18.1~13.04-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.43-0ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.1.1-0ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.1.1-0ubuntu3 version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A version.xserver-xorg-core: xserver-xorg-core 2:1.13.3-0ubuntu6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2b2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.1.0-0ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.6-0ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.7-0ubuntu1 xserver.bootTime: Sun May 5 16:02:08 2013 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputMicrosft Microsoft Wireless Desktop Receiver 3.1 KEYBOARD, id 8 inputMicrosft Microsoft Wireless Desktop Receiver 3.1 KEYBOARD, id 9 inputLogitech Unifying Device. Wireless PID:101a MOUSE, id 10 xserver.errors: open /dev/dri/card0: No such file or directory open /dev/fb0: No such file or directory xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.13.3-0ubuntu6 To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1176562/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1173283] Re: App icon removed from launcher but not from dconf value after installation and unlock from launcher
[Expired for Unity because there has been no activity for 60 days.] ** Changed in: unity Status: Incomplete = Expired -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1173283 Title: App icon removed from launcher but not from dconf value after installation and unlock from launcher Status in Unity: Expired Status in unity package in Ubuntu: Expired Bug description: On Ubuntu 13.04, after installing an application through the Software Center or Application Lense, the applications icon gets put into the launcher. If I unlock the icon from the launcher before logging out, the icon disappears from the launcher but its .desktop file stays in the favorites dconf value. This causes the icon to reappear after a reboot. If removing the icon from the launcher after a reboot, everything works as expected. How to reproduce: 1) Install an application through Software Center/Application Lense 2) Wait until the app is installed 3) Right-click the newly installed icon in the launcher and unlock it. 4) Check com.canonical.unity.launcher.favorites in dconf-editor and see if the .desktop file is still in the list. Screenshot attached. Notice the wifi-radar.desktop entry in the list, even though the icon is gone from the launcher. SIDENOTE: Shouldn't newly installed apps be put above running apps? (additional bug report needed?) ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: unity 7.0.0daily13.04.18~13.04-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8 Uname: Linux 3.8.0-19-generic x86_64 ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Fri Apr 26 18:29:53 2013 MarkForUpload: True SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1173283/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1176667] Re: Dash does not find files if they have underscores preceding or following in their names
[Expired for Unity because there has been no activity for 60 days.] ** Changed in: unity Status: Incomplete = Expired -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1176667 Title: Dash does not find files if they have underscores preceding or following in their names Status in Unity: Expired Status in unity package in Ubuntu: Expired Bug description: So if a search for a file name with a keyword source it does not find the file that is named Open_source_inschools. However if I put an underscore before or after source like in _source the file is displayed in the Dash. Using Raring Ringtail. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: unity 7.0.0daily13.04.18~13.04-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-19.30-generic 3.8.8 Uname: Linux 3.8.0-19-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.9.2-0ubuntu8 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Sun May 5 23:31:15 2013 InstallationDate: Installed on 2013-04-26 (9 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release i386 (20130424) MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=hr_HR.UTF-8 SHELL=/bin/bash SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1176667/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1173283] Re: App icon removed from launcher but not from dconf value after installation and unlock from launcher
[Expired for unity (Ubuntu) because there has been no activity for 60 days.] ** Changed in: unity (Ubuntu) Status: Incomplete = Expired -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1173283 Title: App icon removed from launcher but not from dconf value after installation and unlock from launcher Status in Unity: Expired Status in unity package in Ubuntu: Expired Bug description: On Ubuntu 13.04, after installing an application through the Software Center or Application Lense, the applications icon gets put into the launcher. If I unlock the icon from the launcher before logging out, the icon disappears from the launcher but its .desktop file stays in the favorites dconf value. This causes the icon to reappear after a reboot. If removing the icon from the launcher after a reboot, everything works as expected. How to reproduce: 1) Install an application through Software Center/Application Lense 2) Wait until the app is installed 3) Right-click the newly installed icon in the launcher and unlock it. 4) Check com.canonical.unity.launcher.favorites in dconf-editor and see if the .desktop file is still in the list. Screenshot attached. Notice the wifi-radar.desktop entry in the list, even though the icon is gone from the launcher. SIDENOTE: Shouldn't newly installed apps be put above running apps? (additional bug report needed?) ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: unity 7.0.0daily13.04.18~13.04-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8 Uname: Linux 3.8.0-19-generic x86_64 ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Fri Apr 26 18:29:53 2013 MarkForUpload: True SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1173283/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1388235] Re: [indicators] Battery icon turns red at 30%
This bug was fixed in the package ubuntu-themes - 14.04+15.04.20150212-0ubuntu1 --- ubuntu-themes (14.04+15.04.20150212-0ubuntu1) vivid; urgency=medium [ Matthieu James ] * Added battery icons for more charge levels: 10%, 30%, 50%, 70% and 90%. (LP: #1388235) -- CI Train Bot ci-train-...@canonical.com Thu, 12 Feb 2015 22:46:11 + ** Changed in: ubuntu-themes (Ubuntu) Status: In Progress = Fix Released -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-power in Ubuntu. https://bugs.launchpad.net/bugs/1388235 Title: [indicators] Battery icon turns red at 30% Status in the base for Ubuntu mobile products: In Progress Status in Ubuntu UX bugs: Triaged Status in indicator-power package in Ubuntu: Fix Released Status in ubuntu-themes package in Ubuntu: Fix Released Bug description: This seems a bit pessimistic since the phone still has a great deal of capacity and time left, perhaps 15 or 20% is a better threshold To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1388235/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1252121] Re: missing PrepareForSleep signal after resuming, causing networking to stay disabled
This works fine for me, with wicd on Ubuntu Utopic. Actually, I don't see why someone (justin parker?) marked wicd as being affected, because I don't see anyone mentioning wicd in this report, and neither in https://bugs.launchpad.net/ubuntu/+source/systemd- shim/+bug/1184262 and neither in any of the duplicates. Marked as Invalid, just let me know if there's a real issue with wicd here. -- You received this bug notification because you are a member of DX Packages, which is subscribed to systemd-shim in Ubuntu. https://bugs.launchpad.net/bugs/1252121 Title: missing PrepareForSleep signal after resuming, causing networking to stay disabled Status in NetworkManager: New Status in wicd: Invalid Status in systemd-shim package in Ubuntu: Confirmed Status in systemd-shim source package in Saucy: Won't Fix Status in systemd-shim source package in Trusty: Confirmed Bug description: As per request from bug #1184262, this is a new report, along with dbus (to be attached) ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: systemd-services 204-0ubuntu19 Uname: Linux 3.12.0-custom x86_64 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Date: Sun Nov 17 20:24:41 2013 MarkForUpload: True SourcePackage: systemd UpgradeStatus: Upgraded to saucy on 2013-10-17 (31 days ago) SRU INFORMATION: FIX: https://github.com/desrt/systemd-shim/commit/9e1ebe3ab (in trusty already) Regression potential: Low. Flushing the session bus was introduced in version 4 and is obviously bogus as in a system D-BUS service there is no session bus. This causes lots of confusing error messages and unnecessary overhead like trying to start dbus-launch. Flushing the system bus is low-risk, in most cases it's a no-op and it would otherwise prevent losing signals after waking up. No known regressions. TEST CASE: Run several suspend/resume cycles with the lid, session indicator menu, and verify that the network comes back up. It is known that this fix is necessary but not sufficient, so it is not expected to fix all cases. But it should not make things worse, so if network now does not come up any more on a machine where it previously worked this would count as failure/regression. To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1252121/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1252121] Re: missing PrepareForSleep signal after resuming, causing networking to stay disabled
This works fine for me, with wicd on Ubuntu Utopic. Actually, I don't see why someone (justin parker?) marked wicd as being affected, because I don't see anyone mentioning wicd in this report, and neither in https://bugs.launchpad.net/ubuntu/+source/systemd- shim/+bug/1184262 and neither in any of the duplicates. Marked as Invalid, just let me know if there's a real issue with wicd here. -- You received this bug notification because you are a member of DX Packages, which is subscribed to systemd-shim in Ubuntu. https://bugs.launchpad.net/bugs/1252121 Title: missing PrepareForSleep signal after resuming, causing networking to stay disabled Status in NetworkManager: New Status in wicd: Invalid Status in systemd-shim package in Ubuntu: Confirmed Status in systemd-shim source package in Saucy: Won't Fix Status in systemd-shim source package in Trusty: Confirmed Bug description: As per request from bug #1184262, this is a new report, along with dbus (to be attached) ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: systemd-services 204-0ubuntu19 Uname: Linux 3.12.0-custom x86_64 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Date: Sun Nov 17 20:24:41 2013 MarkForUpload: True SourcePackage: systemd UpgradeStatus: Upgraded to saucy on 2013-10-17 (31 days ago) SRU INFORMATION: FIX: https://github.com/desrt/systemd-shim/commit/9e1ebe3ab (in trusty already) Regression potential: Low. Flushing the session bus was introduced in version 4 and is obviously bogus as in a system D-BUS service there is no session bus. This causes lots of confusing error messages and unnecessary overhead like trying to start dbus-launch. Flushing the system bus is low-risk, in most cases it's a no-op and it would otherwise prevent losing signals after waking up. No known regressions. TEST CASE: Run several suspend/resume cycles with the lid, session indicator menu, and verify that the network comes back up. It is known that this fix is necessary but not sufficient, so it is not expected to fix all cases. But it should not make things worse, so if network now does not come up any more on a machine where it previously worked this would count as failure/regression. To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1252121/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1252121] Re: missing PrepareForSleep signal after resuming, causing networking to stay disabled
** Changed in: wicd Status: New = Incomplete ** Changed in: wicd Importance: Undecided = Medium ** Changed in: wicd Assignee: (unassigned) = Tom Van Braeckel (tomvanbraeckel) ** Changed in: wicd Status: Incomplete = Invalid -- You received this bug notification because you are a member of DX Packages, which is subscribed to systemd-shim in Ubuntu. https://bugs.launchpad.net/bugs/1252121 Title: missing PrepareForSleep signal after resuming, causing networking to stay disabled Status in NetworkManager: New Status in wicd: Invalid Status in systemd-shim package in Ubuntu: Confirmed Status in systemd-shim source package in Saucy: Won't Fix Status in systemd-shim source package in Trusty: Confirmed Bug description: As per request from bug #1184262, this is a new report, along with dbus (to be attached) ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: systemd-services 204-0ubuntu19 Uname: Linux 3.12.0-custom x86_64 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Date: Sun Nov 17 20:24:41 2013 MarkForUpload: True SourcePackage: systemd UpgradeStatus: Upgraded to saucy on 2013-10-17 (31 days ago) SRU INFORMATION: FIX: https://github.com/desrt/systemd-shim/commit/9e1ebe3ab (in trusty already) Regression potential: Low. Flushing the session bus was introduced in version 4 and is obviously bogus as in a system D-BUS service there is no session bus. This causes lots of confusing error messages and unnecessary overhead like trying to start dbus-launch. Flushing the system bus is low-risk, in most cases it's a no-op and it would otherwise prevent losing signals after waking up. No known regressions. TEST CASE: Run several suspend/resume cycles with the lid, session indicator menu, and verify that the network comes back up. It is known that this fix is necessary but not sufficient, so it is not expected to fix all cases. But it should not make things worse, so if network now does not come up any more on a machine where it previously worked this would count as failure/regression. To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1252121/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1289002] Re: unity-scope-loader crashed with SIGSEGV in g_desktop_app_info_get_is_hidden()
*** This bug is a duplicate of bug 1206729 *** https://bugs.launchpad.net/bugs/1206729 ** This bug is no longer a duplicate of bug 1212540 unity-scope-loader crashed with SIGSEGV in g_desktop_app_info_get_is_hidden() ** This bug has been marked a duplicate of bug 1206729 gnome-shell crashed with SIGSEGV in g_desktop_app_info_get_is_hidden() -- You received this bug notification because you are a member of DX Packages, which is subscribed to libunity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1289002 Title: unity-scope-loader crashed with SIGSEGV in g_desktop_app_info_get_is_hidden() Status in libunity package in Ubuntu: New Bug description: Alacarte crashes when saving a command to a custom menu launcher. The name and logo can be saved, but as soon as a command is typed and saved the crash occurs. Last 14.04 LTS. Worked before last update 03/06/2014 3:15 CDT. ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: libunity9 7.1.4+14.04.20140210-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-16.36-generic 3.13.5 Uname: Linux 3.13.0-16-generic x86_64 ApportVersion: 2.13.2-0ubuntu5 Architecture: amd64 CrashCounter: 1 CurrentDesktop: Unity Date: Thu Mar 6 15:27:20 2014 ExecutablePath: /usr/bin/unity-scope-loader InstallationDate: Installed on 2014-03-06 (0 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140304) ProcCmdline: /usr/bin/unity-scope-loader applications/applications.scope applications/scopes.scope commands.scope ProcEnviron: XDG_RUNTIME_DIR=set SHELL=/bin/bash LANGUAGE=en_US PATH=(custom, no user) LANG=en_US.UTF-8 SegvAnalysis: Segfault happened at: 0x7f7406317d90 g_desktop_app_info_get_is_hidden: movzbl 0xc0(%rdi),%eax PC (0x7f7406317d90) ok source 0xc0(%rdi) (0x00c0) not located in a known VMA region (needed readable region)! destination %eax ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: libunity StacktraceTop: g_desktop_app_info_get_is_hidden () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 ?? () from /usr/lib/libgnome-menu-3.so.0 ?? () from /usr/lib/libgnome-menu-3.so.0 gmenu_tree_load_sync () from /usr/lib/libgnome-menu-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/unity/unity-scope-applications.so Title: unity-scope-loader crashed with SIGSEGV in g_desktop_app_info_get_is_hidden() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libunity/+bug/1289002/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1236304] Re: unity-scope-loader crashed with SIGSEGV in g_desktop_app_info_get_is_hidden()
*** This bug is a duplicate of bug 1206729 *** https://bugs.launchpad.net/bugs/1206729 ** This bug is no longer a duplicate of bug 1212540 unity-scope-loader crashed with SIGSEGV in g_desktop_app_info_get_is_hidden() ** This bug has been marked a duplicate of bug 1206729 gnome-shell crashed with SIGSEGV in g_desktop_app_info_get_is_hidden() -- You received this bug notification because you are a member of DX Packages, which is subscribed to libunity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1236304 Title: unity-scope-loader crashed with SIGSEGV in g_desktop_app_info_get_is_hidden() Status in libunity package in Ubuntu: New Bug description: searching for an application when this error came up ProblemType: Crash DistroRelease: Ubuntu 13.10 Package: libunity9 7.1.2+13.10.20131003-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-11.17-generic 3.11.3 Uname: Linux 3.11.0-11-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.12.5-0ubuntu1 Architecture: amd64 Date: Mon Oct 7 12:11:47 2013 ExecutablePath: /usr/bin/unity-scope-loader InstallationDate: Installed on 2013-10-02 (4 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Beta amd64 (20131002) MarkForUpload: True ProcCmdline: /usr/bin/unity-scope-loader applications/applications.scope applications/scopes.scope commands.scope applications/runningapps.scope ProcEnviron: XDG_RUNTIME_DIR=set SHELL=/bin/bash LANGUAGE=en_GB:en PATH=(custom, no user) LANG=en_GB.UTF-8 SegvAnalysis: Segfault happened at: 0x7f08a396cab0 g_desktop_app_info_get_is_hidden: movzbl 0xc0(%rdi),%eax PC (0x7f08a396cab0) ok source 0xc0(%rdi) (0x00c0) not located in a known VMA region (needed readable region)! destination %eax ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: libunity StacktraceTop: g_desktop_app_info_get_is_hidden () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 ?? () from /usr/lib/libgnome-menu-3.so.0 ?? () from /usr/lib/libgnome-menu-3.so.0 gmenu_tree_load_sync () from /usr/lib/libgnome-menu-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/unity/unity-scope-applications.so Title: unity-scope-loader crashed with SIGSEGV in g_desktop_app_info_get_is_hidden() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libunity/+bug/1236304/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1213519] Re: unity-scope-loader crashed with SIGSEGV in g_desktop_app_info_get_is_hidden()
*** This bug is a duplicate of bug 1206729 *** https://bugs.launchpad.net/bugs/1206729 ** This bug is no longer a duplicate of bug 1212540 unity-scope-loader crashed with SIGSEGV in g_desktop_app_info_get_is_hidden() ** This bug has been marked a duplicate of bug 1206729 gnome-shell crashed with SIGSEGV in g_desktop_app_info_get_is_hidden() -- You received this bug notification because you are a member of DX Packages, which is subscribed to libunity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1213519 Title: unity-scope-loader crashed with SIGSEGV in g_desktop_app_info_get_is_hidden() Status in libunity package in Ubuntu: New Bug description: Occurred as I opened the dash. ProblemType: Crash DistroRelease: Ubuntu 13.10 Package: libunity9 7.0.11+13.10.20130816.2-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-2.5-generic 3.11.0-rc5 Uname: Linux 3.11.0-2-generic x86_64 ApportVersion: 2.12-0ubuntu3 Architecture: amd64 Date: Sat Aug 17 21:51:27 2013 EcryptfsInUse: Yes ExecutablePath: /usr/bin/unity-scope-loader InstallationDate: Installed on 2013-08-09 (9 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MarkForUpload: True ProcCmdline: /usr/bin/unity-scope-loader applications/applications.scope applications/scopes.scope commands.scope ProcEnviron: XDG_RUNTIME_DIR=set SHELL=/bin/bash LANGUAGE=en_US PATH=(custom, no user) LANG=en_US.UTF-8 SegvAnalysis: Segfault happened at: 0x7ff818721210 g_desktop_app_info_get_is_hidden: movzbl 0xc0(%rdi),%eax PC (0x7ff818721210) ok source 0xc0(%rdi) (0x00c0) not located in a known VMA region (needed readable region)! destination %eax ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: libunity StacktraceTop: g_desktop_app_info_get_is_hidden () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 ?? () from /usr/lib/libgnome-menu-3.so.0 ?? () from /usr/lib/libgnome-menu-3.so.0 gmenu_tree_load_sync () from /usr/lib/libgnome-menu-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/unity/unity-scope-applications.so Title: unity-scope-loader crashed with SIGSEGV in g_desktop_app_info_get_is_hidden() UpgradeStatus: Upgraded to saucy on 2013-08-09 (8 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libunity/+bug/1213519/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1236730] Re: unity-scope-loader crashed with SIGSEGV in g_desktop_app_info_get_is_hidden()
*** This bug is a duplicate of bug 1206729 *** https://bugs.launchpad.net/bugs/1206729 ** This bug is no longer a duplicate of bug 1212540 unity-scope-loader crashed with SIGSEGV in g_desktop_app_info_get_is_hidden() ** This bug has been marked a duplicate of bug 1206729 gnome-shell crashed with SIGSEGV in g_desktop_app_info_get_is_hidden() -- You received this bug notification because you are a member of DX Packages, which is subscribed to libunity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1236730 Title: unity-scope-loader crashed with SIGSEGV in g_desktop_app_info_get_is_hidden() Status in libunity package in Ubuntu: New Bug description: unity crashes after logging out ProblemType: Crash DistroRelease: Ubuntu 13.10 Package: libunity9 7.1.2+13.10.20131003-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-11.17-generic 3.11.3 Uname: Linux 3.11.0-11-generic x86_64 ApportVersion: 2.12.5-0ubuntu1 Architecture: amd64 Date: Sun Oct 6 16:53:36 2013 ExecutablePath: /usr/bin/unity-scope-loader ExecutableTimestamp: 1380778629 InstallationDate: Installed on 2013-08-15 (52 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MarkForUpload: True ProcCmdline: /usr/bin/unity-scope-loader applications/applications.scope applications/scopes.scope commands.scope applications/runningapps.scope ProcCwd: / ProcEnviron: XDG_RUNTIME_DIR=set SHELL=/bin/bash LANGUAGE=sk_SK PATH=(custom, no user) LANG=sk_SK.UTF-8 SegvAnalysis: Segfault happened at: 0x7f21046c8ab0 g_desktop_app_info_get_is_hidden: movzbl 0xc0(%rdi),%eax PC (0x7f21046c8ab0) ok source 0xc0(%rdi) (0x00c0) not located in a known VMA region (needed readable region)! destination %eax ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: libunity StacktraceTop: g_desktop_app_info_get_is_hidden () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 ?? () from /usr/lib/libgnome-menu-3.so.0 ?? () from /usr/lib/libgnome-menu-3.so.0 gmenu_tree_load_sync () from /usr/lib/libgnome-menu-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/unity/unity-scope-applications.so Title: unity-scope-loader crashed with SIGSEGV in g_desktop_app_info_get_is_hidden() UpgradeStatus: Upgraded to saucy on 2013-10-05 (0 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libunity/+bug/1236730/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1212540] Re: unity-scope-loader crashed with SIGSEGV in g_desktop_app_info_get_is_hidden()
*** This bug is a duplicate of bug 1206729 *** https://bugs.launchpad.net/bugs/1206729 ** This bug has been marked a duplicate of bug 1206729 gnome-shell crashed with SIGSEGV in g_desktop_app_info_get_is_hidden() -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity-lens-applications in Ubuntu. https://bugs.launchpad.net/bugs/1212540 Title: unity-scope-loader crashed with SIGSEGV in g_desktop_app_info_get_is_hidden() Status in unity-lens-applications package in Ubuntu: Confirmed Bug description: Launched PPA-supplied Netflix application from Unity menu, received crash report. ProblemType: Crash DistroRelease: Ubuntu 13.10 Package: libunity9 7.0.10+13.10.20130809.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-2.5-generic 3.11.0-rc5 Uname: Linux 3.11.0-2-generic x86_64 ApportVersion: 2.12-0ubuntu3 Architecture: amd64 Date: Thu Aug 15 01:29:00 2013 ExecutablePath: /usr/bin/unity-scope-loader InstallationDate: Installed on 2012-11-02 (285 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) MarkForUpload: True ProcCmdline: /usr/bin/unity-scope-loader applications/applications.scope applications/scopes.scope commands.scope ProcEnviron: XDG_RUNTIME_DIR=set SHELL=/bin/bash LANGUAGE=en_US PATH=(custom, no user) LANG=en_US.UTF-8 SegvAnalysis: Segfault happened at: 0x7f205e3ef210 g_desktop_app_info_get_is_hidden: movzbl 0xc0(%rdi),%eax PC (0x7f205e3ef210) ok source 0xc0(%rdi) (0x00c0) not located in a known VMA region (needed readable region)! destination %eax ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: libunity StacktraceTop: g_desktop_app_info_get_is_hidden () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 ?? () from /usr/lib/libgnome-menu-3.so.0 ?? () from /usr/lib/libgnome-menu-3.so.0 gmenu_tree_load_sync () from /usr/lib/libgnome-menu-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/unity/unity-scope-applications.so Title: unity-scope-loader crashed with SIGSEGV in g_desktop_app_info_get_is_hidden() UpgradeStatus: Upgraded to saucy on 2013-08-14 (1 days ago) UserGroups: adm backup cdrom dialout dip disk kismet kvm libvirtd lpadmin netdev plugdev sambashare sudo tty video www-data To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-lens-applications/+bug/1212540/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1283437] Re: unity-scope-loader crashed with SIGSEGV in g_desktop_app_info_get_is_hidden()
*** This bug is a duplicate of bug 1206729 *** https://bugs.launchpad.net/bugs/1206729 ** This bug is no longer a duplicate of bug 1212540 unity-scope-loader crashed with SIGSEGV in g_desktop_app_info_get_is_hidden() ** This bug has been marked a duplicate of bug 1206729 gnome-shell crashed with SIGSEGV in g_desktop_app_info_get_is_hidden() -- You received this bug notification because you are a member of DX Packages, which is subscribed to libunity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1283437 Title: unity-scope-loader crashed with SIGSEGV in g_desktop_app_info_get_is_hidden() Status in libunity package in Ubuntu: New Bug description: I used the quick search DoubleCommander ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: libunity9 7.1.4+14.04.20140210-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-12.32-generic 3.13.4 Uname: Linux 3.13.0-12-generic x86_64 ApportVersion: 2.13.2-0ubuntu5 Architecture: amd64 CurrentDesktop: Unity Date: Sat Feb 22 17:17:46 2014 ExecutablePath: /usr/bin/unity-scope-loader InstallationDate: Installed on 2014-02-22 (0 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140221) ProcCmdline: /usr/bin/unity-scope-loader applications/applications.scope applications/scopes.scope commands.scope ProcEnviron: XDG_RUNTIME_DIR=set SHELL=/bin/bash LANGUAGE=ru PATH=(custom, user) LANG=ru_RU.UTF-8 SegvAnalysis: Segfault happened at: 0x7fbb2b735d20 g_desktop_app_info_get_is_hidden: movzbl 0xc0(%rdi),%eax PC (0x7fbb2b735d20) ok source 0xc0(%rdi) (0x00c0) not located in a known VMA region (needed readable region)! destination %eax ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: libunity StacktraceTop: g_desktop_app_info_get_is_hidden () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 ?? () from /usr/lib/libgnome-menu-3.so.0 ?? () from /usr/lib/libgnome-menu-3.so.0 gmenu_tree_load_sync () from /usr/lib/libgnome-menu-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/unity/unity-scope-applications.so Title: unity-scope-loader crashed with SIGSEGV in g_desktop_app_info_get_is_hidden() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm bumblebee cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libunity/+bug/1283437/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1421192] Re: Initial boot wizard does not include timezone
FWIW, we'd probably rather set the time (and timezone) automagically on boot, either from GSM or over WiFi. Whether we then want to give the user the option to change the auto-detected TZ remains to be determined. ** Also affects: ubuntu-ux Importance: Undecided Status: New ** Also affects: indicator-datetime (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-datetime in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1421192 Title: Initial boot wizard does not include timezone Status in Ubuntu UX bugs: New Status in indicator-datetime package in Ubuntu: New Status in unity8 package in Ubuntu: New Bug description: During the initial boot the Ubuntu phone asks information regarding various things like language, passcode etc. Timezone or date/time is not asked, it always defaults to UTC+0. This confirmed with Ubuntu 14.10(r16) and 15.04(r01) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1421192/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1421192] Re: Initial boot wizard does not include timezone
It has been defaulting to UTC+0 although I live in Finland, that's UTC+2. -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-datetime in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1421192 Title: Initial boot wizard does not include timezone Status in Ubuntu UX bugs: New Status in indicator-datetime package in Ubuntu: New Status in unity8 package in Ubuntu: New Bug description: During the initial boot the Ubuntu phone asks information regarding various things like language, passcode etc. Timezone or date/time is not asked, it always defaults to UTC+0. This confirmed with Ubuntu 14.10(r16) and 15.04(r01) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1421192/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1358340] Re: [Indicators] Complete greeter profiles
For the record, the latest version of unity8 in vivid (8.02+15.04.20150211-0ubuntu1) internally supports greeter profiles. I'm waiting on the design for System Settings before flipping the switch inside to start using it. -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-datetime in Ubuntu. Matching subscriptions: dx-packages, dx-packages, dx-packages https://bugs.launchpad.net/bugs/1358340 Title: [Indicators] Complete greeter profiles Status in The Date and Time Indicator: Invalid Status in The Messaging Menu: Fix Released Status in Transfer Indicator: Fix Released Status in Ubuntu UX bugs: Fix Released Status in The Unity 8 shell: Fix Released Status in gsettings-ubuntu-touch-schemas package in Ubuntu: Fix Released Status in indicator-datetime package in Ubuntu: Invalid Status in indicator-messages package in Ubuntu: Fix Released Status in indicator-sound package in Ubuntu: Fix Released Status in indicator-transfer package in Ubuntu: Fix Released Status in ubuntu-system-settings package in Ubuntu: Fix Released Status in unity8 package in Ubuntu: In Progress Status in unity8 package in Ubuntu RTM: New Bug description: A recent change in the interest of security removed access to the indicators when the phone is locked and the greeter is showing. This was an accentual change based on a misunderstanding There had been a plan to support media playback control via the sound indicator. Without this the user must unlock the phone in order to simply pause the music or change songs, etc. Desired resolution: - Revert the change that caused this issue - Add a switch to System Settings to enable security conscious user to switch off Launcher and Greeter access while the phone is locked. This setting should *always* be off by default. https://wiki.ubuntu.com/SecurityAndPrivacySettings#Locking To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-datetime/+bug/1358340/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1421247] [NEW] Fonts are inconsistent size on HiDPI
Public bug reported: On a recent update the font sizes changed on various applications. On Thunderbiard they are VERY_LARGE however on installing Unity tweek tool and resetting the font sizes nothing altered. Title bars are rather large font also. varying size fonts on applications ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.4+14.04.20141217-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-45.74-generic 3.13.11-ckt13 Uname: Linux 3.13.0-45-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.6 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Thu Feb 12 14:52:53 2015 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu EcryptfsInUse: Yes GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:2218] InstallationDate: Installed on 2014-12-20 (53 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) MachineType: LENOVO 20A7002WUS ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-45-generic root=UUID=217b58b6-13d8-4975-9033-fd99e4fa55ea ro quiet splash vt.handoff=7 SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/20/2014 dmi.bios.vendor: LENOVO dmi.bios.version: GRET42WW (1.19 ) dmi.board.asset.tag: Not Available dmi.board.name: 20A7002WUS dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGRET42WW(1.19):bd11/20/2014:svnLENOVO:pn20A7002WUS:pvrThinkPadX1Carbon2nd:rvnLENOVO:rn20A7002WUS:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 20A7002WUS dmi.product.version: ThinkPad X1 Carbon 2nd dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.11.3+14.04.20141104-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.56-1~ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.3 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1.4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Thu Feb 12 14:33:09 2015 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id1049 vendor LGD xserver.version: 2:1.15.1-0ubuntu2.6 ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 trusty ubuntu ** Attachment added: screen size of font sizes https://bugs.launchpad.net/bugs/1421247/+attachment/4318011/+files/Screenshot%20from%202015-02-12%2014%3A52%3A35.png -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1421247 Title: Fonts are inconsistent size on HiDPI Status in unity package in Ubuntu: New Bug description: On a recent update the font sizes changed on various applications. On Thunderbiard they are VERY_LARGE however on installing Unity tweek tool and resetting the font sizes nothing altered. Title bars are rather large font also. varying size fonts on applications ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.4+14.04.20141217-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-45.74-generic 3.13.11-ckt13 Uname: Linux 3.13.0-45-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.6 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Thu Feb 12 14:52:53 2015 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu EcryptfsInUse: Yes GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:2218] InstallationDate: Installed on 2014-12-20 (53 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) MachineType: LENOVO 20A7002WUS ProcKernelCmdLine:
[Dx-packages] [Bug 1421192] Re: Initial boot wizard does not include timezone
Yeah, what I described we're not doing yet, but I believe that should be the goal. I remember in one of my previous phones I had to set up the time, date and timezone just for it then to be corrected by GSM... Felt like a waste of my time, really. -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-datetime in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1421192 Title: Initial boot wizard does not include timezone Status in Ubuntu UX bugs: New Status in indicator-datetime package in Ubuntu: New Status in unity8 package in Ubuntu: New Bug description: During the initial boot the Ubuntu phone asks information regarding various things like language, passcode etc. Timezone or date/time is not asked, it always defaults to UTC+0. This confirmed with Ubuntu 14.10(r16) and 15.04(r01) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1421192/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1414617] Re: Volume Dialog Does't Appear
I'm not seeing that. Can you attach your indicator-sound and unity8 logs from ~/.cache/upstart/ please? ** Changed in: indicator-sound (Ubuntu) Status: New = Incomplete -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-sound in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1414617 Title: Volume Dialog Does't Appear Status in indicator-sound package in Ubuntu: Incomplete Status in unity8 package in Ubuntu: Opinion Bug description: The volume dialog fails to appear on screen but the volume is adjusted. I have tried a number of restarts without change. Are any logs or debug information I can provide? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/1414617/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
