[Dx-packages] [Bug 1338903] [NEW] [Trusty] notification-daemon crashed when starting the session
Public bug reported: While starting the session, apport came up with a crash, stating that the notification-daemon had crashed. My internet connection was not ready, so I started the wireless connection, which was ready in little time, and when I clicked on Continue in Aprport, well, apport crashed and didn't re appear to offer to send a bug about itself. So I headed to /var/crash and found a long file with lots of information, which I am bringing here now, for good use. System: $ uname -a Linux gazelle 3.13.0-30-generic #55-Ubuntu SMP Fri Jul 4 21:40:53 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux $ cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=14.04 DISTRIB_CODENAME=trusty DISTRIB_DESCRIPTION=Ubuntu 14.04 LTS $ Environment, Openbox. The other information should be in the crash report attached. Regards, Mélodie ** Affects: notification-daemon (Ubuntu) Importance: Undecided Status: New ** Attachment added: _usr_lib_notification-daemon_notification-daemon.1000.crash https://bugs.launchpad.net/bugs/1338903/+attachment/4147830/+files/_usr_lib_notification-daemon_notification-daemon.1000.crash -- You received this bug notification because you are a member of DX Packages, which is subscribed to notification-daemon in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1338903 Title: [Trusty] notification-daemon crashed when starting the session Status in “notification-daemon” package in Ubuntu: New Bug description: While starting the session, apport came up with a crash, stating that the notification-daemon had crashed. My internet connection was not ready, so I started the wireless connection, which was ready in little time, and when I clicked on Continue in Aprport, well, apport crashed and didn't re appear to offer to send a bug about itself. So I headed to /var/crash and found a long file with lots of information, which I am bringing here now, for good use. System: $ uname -a Linux gazelle 3.13.0-30-generic #55-Ubuntu SMP Fri Jul 4 21:40:53 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux $ cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=14.04 DISTRIB_CODENAME=trusty DISTRIB_DESCRIPTION=Ubuntu 14.04 LTS $ Environment, Openbox. The other information should be in the crash report attached. Regards, Mélodie To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/notification-daemon/+bug/1338903/+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 1338939] [NEW] Alarms go off 3 times on mako and flo
Public bug reported: Sync your calendar to Ubuntu device Have events in your calendar. Wait for an a event Alarm goes off. Listen to the gently plucked harp. Press the dismiss button on the popup Wait a short while. Alarm goes off again. Get annoyed at the harp Press the dismiss button on the popup Wait a short while Alarm goes off again Shout at phone. I would expect the alarm to go off once. ** Affects: indicator-datetime (Ubuntu) Importance: High Status: Confirmed ** Tags: avengers flo mako manta u113 ** Summary changed: - Alarms go off 3 times on mako and flo on + Alarms go off 3 times on mako and flo ** Description changed: Sync your calendar to Ubuntu device Have events in your calendar. Wait for an a event Alarm goes off. Listen to the gently plucked harp. Press the dismiss button on the popup Wait a short while. Alarm goes off again. Get annoyed at the harp Press the dismiss button on the popup Wait a short while Alarm goes off again Shout at phone. + + I would expect the alarm to go off once. -- 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/1338939 Title: Alarms go off 3 times on mako and flo Status in “indicator-datetime” package in Ubuntu: Confirmed Bug description: Sync your calendar to Ubuntu device Have events in your calendar. Wait for an a event Alarm goes off. Listen to the gently plucked harp. Press the dismiss button on the popup Wait a short while. Alarm goes off again. Get annoyed at the harp Press the dismiss button on the popup Wait a short while Alarm goes off again Shout at phone. I would expect the alarm to go off once. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1338939/+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 1338939] Re: Alarms go off 3 times on mako and flo
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: indicator-datetime (Ubuntu) Status: New = Confirmed -- 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/1338939 Title: Alarms go off 3 times on mako and flo Status in “indicator-datetime” package in Ubuntu: Confirmed Bug description: Sync your calendar to Ubuntu device Have events in your calendar. Wait for an a event Alarm goes off. Listen to the gently plucked harp. Press the dismiss button on the popup Wait a short while. Alarm goes off again. Get annoyed at the harp Press the dismiss button on the popup Wait a short while Alarm goes off again Shout at phone. I would expect the alarm to go off once. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1338939/+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 1338939] Re: Alarms go off 3 times on mako and flo
** Tags added: avengers flo mako manta u113 ** Changed in: indicator-datetime (Ubuntu) Importance: Undecided = High -- 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/1338939 Title: Alarms go off 3 times on mako and flo Status in “indicator-datetime” package in Ubuntu: Confirmed Bug description: Sync your calendar to Ubuntu device Have events in your calendar. Wait for an a event Alarm goes off. Listen to the gently plucked harp. Press the dismiss button on the popup Wait a short while. Alarm goes off again. Get annoyed at the harp Press the dismiss button on the popup Wait a short while Alarm goes off again Shout at phone. I would expect the alarm to go off once. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1338939/+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 1311503] Re: compiz crashes with segfault error in libnux-graphics
I've upgraded to 14.10 which doesn't have these problems. -- You received this bug notification because you are a member of DX Packages, which is subscribed to nux in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1311503 Title: compiz crashes with segfault error in libnux-graphics Status in “nux” package in Ubuntu: Confirmed Bug description: When I login compiz crashes with a segfault error in libnux-graphics. My screen turns blue (with nouveau driver) or with white blocks (nvidia current driver). In dmesg the following messages are shown: [ 808.965220] compiz[7568]: segfault at b0 ip 7f9246244a0f sp 7fff0a7a1450 error 4 in libnux-graphics-4.0.so.0.6.0[7f92461f8000+cb000] [ 813.851368] compiz[7722]: segfault at b0 ip 7f34215bca0f sp 7fffe2e356d0 error 4 in libnux-graphics-4.0.so.0.6.0[7f342157+cb000] I only get this error with my Nvidia GTX 460 card. I do not get these errors with my radeon and intel video cards (my other pc and laptop). All running latest Trusty 14.04. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nux/+bug/1311503/+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 1305586] Re: Lock screen is unusable when some windows have a keyboard/mouse grab
I confirm what Simon Buchan wrote in his comment. - I start VirtualBox with Ubuntu 12.04.4 LTS as guest, fullscreen - Wait for Unity lockscreen (timeout set to 1 minute for testing) - Keyboard input does not seem to respond, mouse works fine. Now there is other workaround to get input not going to the VM but to lockscreen text box. I just need to switch off fullscreen for the VM with keyboard shortcut Host + F (by default Right Ctrl + F) and then open indicators and finally switch to the lockscreen password text box. I have only one monitor. @Simon this particular problem might be resolved with the Unity SRU update. Christopher Townsend mentioned in comment #23 that the Compiz SRU doesn't resolve all the problems and that Unity SRU has still some fixes which should make this bettter. -- 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/1305586 Title: Lock screen is unusable when some windows have a keyboard/mouse grab Status in Compiz: Fix Committed Status in Compiz 0.9.11 series: In Progress Status in Unity: Fix Released Status in Unity 7.2 series: In Progress Status in “compiz” package in Ubuntu: Fix Released Status in “unity” package in Ubuntu: Fix Released Status in “compiz” source package in Trusty: Fix Committed Status in “unity” source package in Trusty: Confirmed Bug description: [Impact] Some windows will grab the keyboard/mouse and when the lockscreen kicks in, this window will still have the grab and thusly, ou can enter your password in the lockscreen. [Test case] 1. Open a window that will hold the grab, such as the ssh password dialog. 2. Wait for the lock screen to activate. 3. Enter your password to unlock the screen. [Regression potential] This particular fix doesn't fix all cases, but does fix it for some. That said, no new regressions are expected. * Debdiff is found at https://launchpadlibrarian.net/178439518/compiz- trusty-sru-2.debdiff * Original Description: My screen just timed out and locked when a password prompt which had a grab was displaying. I couldn't type my password or interact with the indicators. gnome-screensaver just refuses to lock in this situation, perhaps unity could do the same unless it's possible to remove and readd the grabs yourself, but I don't think XLib lets you do that (you can only remove your own grabs AFAIK). TEMPORARY WORKAROUND TO LOGIN AGAIN: Click on the guest session Once the guest session is started log out This takes you back to the lightdm session screen you can then login to your user session and it be in the same state ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140409-0ubuntu1 [origin: unknown] ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8 Uname: Linux 3.13.0-23-generic x86_64 ApportVersion: 2.14.1-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CrashDB: unity CurrentDesktop: Unity Date: Thu Apr 10 09:39:45 2014 InstallationDate: Installed on 2012-10-07 (549 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Beta amd64 (20121007) SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2013-05-07 (338 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1305586/+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
I have this behaviour on an LTSP client (ubuntu 14.04), chmod u+s /sbin/unix_chkpwd does not appear resolve it and I am using sssd to authenticate to ldap The screen-lock doesn't work by default in LTSP, I had to activate it with unity-tweak-tool. But it is useless since unlock doesn't work. -- 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: Incomplete Status in “unity” package in Ubuntu: Incomplete 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
[Dx-packages] [Bug 1305586] Re: Lock screen is unusable when some windows have a keyboard/mouse grab
@Simon, that's exactly what Mateusz says: the problem you're talking about is fixed in the unity SRU, the verification process we're currently doing is only for Compiz, which has a change that improves us to solve this issue, in some cases (like the one mentioned in verification process), but not in all the ones. For all the cases to be handled, you'll need to update unity with the proposed version that will be available in few days. -- 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/1305586 Title: Lock screen is unusable when some windows have a keyboard/mouse grab Status in Compiz: Fix Committed Status in Compiz 0.9.11 series: In Progress Status in Unity: Fix Released Status in Unity 7.2 series: In Progress Status in “compiz” package in Ubuntu: Fix Released Status in “unity” package in Ubuntu: Fix Released Status in “compiz” source package in Trusty: Fix Committed Status in “unity” source package in Trusty: Confirmed Bug description: [Impact] Some windows will grab the keyboard/mouse and when the lockscreen kicks in, this window will still have the grab and thusly, ou can enter your password in the lockscreen. [Test case] 1. Open a window that will hold the grab, such as the ssh password dialog. 2. Wait for the lock screen to activate. 3. Enter your password to unlock the screen. [Regression potential] This particular fix doesn't fix all cases, but does fix it for some. That said, no new regressions are expected. * Debdiff is found at https://launchpadlibrarian.net/178439518/compiz- trusty-sru-2.debdiff * Original Description: My screen just timed out and locked when a password prompt which had a grab was displaying. I couldn't type my password or interact with the indicators. gnome-screensaver just refuses to lock in this situation, perhaps unity could do the same unless it's possible to remove and readd the grabs yourself, but I don't think XLib lets you do that (you can only remove your own grabs AFAIK). TEMPORARY WORKAROUND TO LOGIN AGAIN: Click on the guest session Once the guest session is started log out This takes you back to the lightdm session screen you can then login to your user session and it be in the same state ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140409-0ubuntu1 [origin: unknown] ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8 Uname: Linux 3.13.0-23-generic x86_64 ApportVersion: 2.14.1-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CrashDB: unity CurrentDesktop: Unity Date: Thu Apr 10 09:39:45 2014 InstallationDate: Installed on 2012-10-07 (549 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Beta amd64 (20121007) SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2013-05-07 (338 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1305586/+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 1245473] Re: Binding ctrl+shift, alt+shift, etc for switching keyboard layout makes shortcuts with ctrl+shift, etc not working in any program
** Project changed: gnome-settings-daemon = gnome-shell -- 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/1245473 Title: Binding ctrl+shift, alt+shift, etc for switching keyboard layout makes shortcuts with ctrl+shift, etc not working in any program Status in GNOME Shell: Won't Fix Status in “gnome-settings-daemon” package in Ubuntu: Confirmed Status in “unity” package in Ubuntu: Confirmed Status in “gnome-settings-daemon” package in ALT Linux: Unknown Status in “gnome-settings-daemon” package in Debian: New Status in “gnome-settings-daemon” package in Fedora: Unknown Status in “gnome-settings-daemon” package in openSUSE: Confirmed Bug description: Tried only with ctrl+shift, maybe behaves the same for other modifier key combinations when used as shortcut for switching layouts. - Set ctrl+shift as shortcut for switching keyboard layouts - Try to use ctrl+shift+v, ctrl+shift+c in Terminal -- it doesn't work (actually Terminal window loses focus when ctrl+shift is pressed, and layout is switched) -- For other layout switching problems introduced in Ubuntu 13.10 you can see bug 1218322. -- ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: gnome-settings-daemon 3.8.5-0ubuntu11.1 ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6 Uname: Linux 3.11.0-13-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Date: Mon Oct 28 16:40:02 2013 InstallationDate: Installed on 2013-10-23 (5 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) MarkForUpload: True SourcePackage: gnome-settings-daemon UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1245473/+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
Re: [Dx-packages] [Aims] [Bug 1314095] Re: Unity Lockscreen in 14.04 can't unlock when using LDAP account
Hi Are you getting the unix_chkpwd error in the logs like this? May 27 09:07:11 muizenberg unix_chkpwd[4186]: check pass; user unknown May 27 09:07:11 muizenberg unix_chkpwd[4186]: password check failed for user (jan) May 27 09:07:11 muizenberg unix_chkpwd[4187]: could not obtain user info (jan) Another commenter said sssd does not exhibit this bug. It sounds like something else causing similar behaviour. Regards, Jan On 8 July 2014 11:42, Joost Ringoot jo...@ringoot.org wrote: I have this behaviour on an LTSP client (ubuntu 14.04), chmod u+s /sbin/unix_chkpwd does not appear resolve it and I am using sssd to authenticate to ldap The screen-lock doesn't work by default in LTSP, I had to activate it with unity-tweak-tool. But it is useless since unlock doesn't work. -- You received this bug notification because you are a member of AIMS, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1314095 Title: Unity Lockscreen in 14.04 can't unlock when using LDAP account Status in Unity: Incomplete Status in unity package in Ubuntu: Incomplete 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
[Dx-packages] [Bug 1338671] Re: Changing amount of workspaces does not affect on its icon on launcher panel
** Changed in: unity (Ubuntu) Importance: Undecided = Low -- 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/1338671 Title: Changing amount of workspaces does not affect on its icon on launcher panel Status in “unity” package in Ubuntu: New Bug description: After changing amount of unity workspaces to any amount not equal to 2x2 - icon on launcher panel still shows 2x2 and moving between workspaces doesn't affect this icon. I know that there is no standard way to change amount of workspaces from Appearance/Behavior settings, but users can change amount of workspaces easily through Unity Tweak Tool for example. Obviously that this icon implemented wrong or hardcoded if it not use it's own settings. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1338671/+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 1296814] Re: When Unity.Session is available, use its API for logging out
This has been fixed and released in the underlying component packages. ** Changed in: unity8-desktop-session (Ubuntu) Status: In Progress = Fix Released -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-session in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1296814 Title: When Unity.Session is available, use its API for logging out Status in The Session Menu: Fix Released Status in Unity: New Status in “indicator-session” package in Ubuntu: Fix Released Status in “unity8-desktop-session” package in Ubuntu: Fix Released Bug description: The session indicator always uses gnome-session to end the session (log out), but gnome-session is not guaranteed to be available under, for example, a Unity8 desktop preview session. It should use Upstart where available. To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-session/+bug/1296814/+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 727166] Re: zeitgeist-daemon crashed with DBusException in call_blocking(): org.freedesktop.DBus.Error.Disconnected: Connection is closed
This bug was fixed in the package zeitgeist - 0.9.14-2.2ubuntu2 --- zeitgeist (0.9.14-2.2ubuntu2) utopic; urgency=medium * Don't build-depend on valadoc or pass --enable-docs; they're in Universe. -- Iain Lane iain.l...@canonical.com Tue, 08 Jul 2014 12:36:53 +0100 ** Changed in: zeitgeist (Ubuntu) Status: Expired = Fix Released -- You received this bug notification because you are a member of DX Packages, which is subscribed to zeitgeist in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/727166 Title: zeitgeist-daemon crashed with DBusException in call_blocking(): org.freedesktop.DBus.Error.Disconnected: Connection is closed Status in “zeitgeist” package in Ubuntu: Fix Released Bug description: Binary package hint: zeitgeist 11.04目前为止，很棒！同时，问题真多，ubuntu one这个不算什么严重的，最严重的是 安装NV驱动时，重新启动后100%会进入不了系统，一直停留在进入登录界面之前的那一个画面（我最少试验过8次，全如此，所以不敢安装NV的驱动了，包括Unity等的特效自然就使用不了了，希望解决，谢谢！！！） ProblemType: Crash DistroRelease: Ubuntu 11.04 Package: zeitgeist-core 0.5.2-0ubuntu1 ProcVersionSignature: Ubuntu 2.6.38-5.32-generic 2.6.38-rc6 Uname: Linux 2.6.38-5-generic x86_64 Architecture: amd64 Date: Tue Mar 1 21:19:23 2011 ExecutablePath: /usr/bin/zeitgeist-daemon InstallationMedia: Ubuntu 11.04 Natty Narwhal - Alpha amd64 (20101202) InterpreterPath: /usr/bin/python2.7 PackageArchitecture: all ProcCmdline: /usr/bin/python /usr/bin/zeitgeist-daemon ProcEnviron: SHELL=/bin/bash LANGUAGE=zh_CN:zh:en_GB:en LANG=zh_CN.UTF-8 PythonArgs: ['/usr/bin/zeitgeist-daemon'] SourcePackage: zeitgeist Title: zeitgeist-daemon crashed with DBusException in call_blocking(): org.freedesktop.DBus.Error.Disconnected: Connection is closed UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zeitgeist/+bug/727166/+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 1339124] [NEW] Event alarm triggers twice at the event time
Public bug reported: Mako running 116 Expected: Alarm for an event happens 10 mins before the event Actual: Alarm goes off at the event, gets dismissed, then goes off again right after ** Affects: ubuntu-calendar-app Importance: High Status: New ** Affects: indicator-datetime (Ubuntu) Importance: High Status: Confirmed ** Also affects: indicator-datetime (Ubuntu) Importance: Undecided Status: New ** Changed in: indicator-datetime (Ubuntu) Importance: Undecided = High -- 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/1339124 Title: Event alarm triggers twice at the event time Status in Calendar application for Ubuntu devices: New Status in “indicator-datetime” package in Ubuntu: Confirmed Bug description: Mako running 116 Expected: Alarm for an event happens 10 mins before the event Actual: Alarm goes off at the event, gets dismissed, then goes off again right after To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-calendar-app/+bug/1339124/+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 1339124] Re: Event alarm triggers twice at the event time
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: indicator-datetime (Ubuntu) Status: New = Confirmed -- 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/1339124 Title: Event alarm triggers twice at the event time Status in Calendar application for Ubuntu devices: New Status in “indicator-datetime” package in Ubuntu: Confirmed Bug description: Mako running 116 Expected: Alarm for an event happens 10 mins before the event Actual: Alarm goes off at the event, gets dismissed, then goes off again right after To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-calendar-app/+bug/1339124/+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 1043997] Re: Music lens preview does not show play/pause status
** Changed in: unity Status: In Progress = 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/1043997 Title: Music lens preview does not show play/pause status Status in Unity: Fix Released Status in “unity” package in Ubuntu: Fix Released Bug description: [Impact] The music lens preview only allows for play. It does not show status or allow for pause as indicated by the unity manual-test. See screenshot-music-preview. [Test Case] From unity/manual-tests/Preview.txt: Preview Music Play note: Should be automated. This tests the dash music preview track play Setup: #. Open music lens (Super+M) #. Enter arbitrary search string and ensure a result is available. #. Open a preview for a result which contains tracks. Actions: #. Play first track. Expected Result: Music Player daemon will start playing track and update status of the track in the preview to playing as well as update it's progress. [Observed Results] Music player shows no track status. [Test Case 2] Preview Music Pause note: Should be automated. This tests the dash preview preview navigate right animation Setup: #. Open music lens (Super+M) #. Enter arbitrary search string and ensure a result is available. #. Open a preview for a result which contains tracks. #. Play first track. Actions: #. Pause playing track. Expected Result: Music Player daemon will pause the playing track and update it's status to paused. Progress will stop incresing. [Observed Results] There was no pause control through the preview. [Packages under test] From ppa:unity-team/release: - bamf - 0.2.122+bzr482ubuntu0+437 - compiz - 1:0.9.8.0-0ubuntu1~test8 - nux - 3.2.0+bzr651ubuntu0+361 - unity - 6.2.0+bzr2633ubuntu0+762 [Hardware config] Nvidia hardware with nouveau driver. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: unity 6.2.0+bzr2633ubuntu0+762 [origin: LP-PPA-unity-team-release] ProcVersionSignature: Ubuntu 3.5.0-13.14-generic 3.5.3 Uname: Linux 3.5.0-13-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.5.1-0ubuntu3 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CrashDB: unity Date: Thu Aug 30 13:25:47 2012 EcryptfsInUse: Yes InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Alpha amd64 (20120627) ProcEnviron: TERM=xterm PATH=(custom, user) LANG=en_US.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/1043997/+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 977804] Re: Unity crashes when many windows are opened (intel_do_flush_locked failed: No space left on device)
Happens still to me an arch linux, with Intel Corporation Mobile 945GM, and Gnome-Shell 3.12.2. Has is ever been fixed? -- 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/977804 Title: Unity crashes when many windows are opened (intel_do_flush_locked failed: No space left on device) Status in Unity: Confirmed Status in “mesa” package in Ubuntu: Confirmed Status in “unity” package in Ubuntu: Confirmed Status in Debian GNU/Linux: New Status in “mesa” package in Fedora: Unknown Bug description: Unity 5.8.0 (Ubuntu 12.04 Beta) crashes (or hanged up) on Fujitsu-Siemens S7020 (Intel 915GM Express Chipset) very often during attempt to use Dash or switch between applications when many winsows are opened with following error: intel_do_flush_locked failed: No space left on device ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: unity 5.8.0-0ubuntu2 ProcVersionSignature: Ubuntu 3.2.0-22.35-generic-pae 3.2.14 Uname: Linux 3.2.0-22-generic-pae i686 .tmp.unity.support.test.0: ApportVersion: 2.0-0ubuntu4 Architecture: i386 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CompositorRunning: compiz Date: Tue Apr 10 11:25:45 2012 DistUpgraded: Fresh install DistroCodename: precise DistroVariant: ubuntu InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Alpha i386 (20120314) MachineType: FUJITSU SIEMENS LIFEBOOK S7020 PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-22-generic-pae root=UUID=e6a4deb8-3e53-4afb-aed8-997537309262 ro quiet splash vt.handoff=7 SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/16/2005 dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd. dmi.bios.version: Version 1.07 dmi.board.name: FJNB19C dmi.board.vendor: FUJITSU dmi.board.version: CP234410-02 dmi.chassis.type: 10 dmi.chassis.vendor: FUJITSU SIEMENS dmi.chassis.version: S7020 dmi.modalias: dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.07:bd09/16/2005:svnFUJITSUSIEMENS:pnLIFEBOOKS7020:pvr:rvnFUJITSU:rnFJNB19C:rvrCP234410-02:cvnFUJITSUSIEMENS:ct10:cvrS7020: dmi.product.name: LIFEBOOK S7020 dmi.sys.vendor: FUJITSU SIEMENS version.compiz: compiz 1:0.9.7.4-0ubuntu3 version.libdrm2: libdrm2 2.4.32-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 8.0.2-0ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 8.0.2-0ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.11.4-0ubuntu10 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.0-0ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.14.99~git20111219.aacbd629-0ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.17.0-1ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:0.0.16+git20111201+b5534a1-1build2 To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/977804/+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 1295794] Re: nautilus opens a new window if clicked on its unity icon even when another nautilus window is open with ntfs drive folder open
*** This bug is a duplicate of bug 1170647 *** https://bugs.launchpad.net/bugs/1170647 Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: unity (Ubuntu) Status: New = Confirmed -- 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/1295794 Title: nautilus opens a new window if clicked on its unity icon even when another nautilus window is open with ntfs drive folder open Status in “unity” package in Ubuntu: Confirmed Bug description: I could not make the title shorter and clearer, please forgive. How to reproduce this bug: On a freshly booted system running Ubuntu 14.04 having unity as its desktop-manager and having at least one NTFS partition on its internal hard disk, do the following: 1) Open a nautilus window and mount an NTFS partition and keep any of the folders on the NTFS partition open in this window. 2) Now open any other application(I opened firefox) and then go back to the nautilus window by pressing on nautilus' unity icon(which should have a small arrow to the left of the nautilus icon, indicating it is already open). Do not use Alt+Tab to go back to nautilus- this works fine. 3) This will open a new nautilus window with the home folder(or whichever is the default path to open when a new nautilus window is opened) and bring the originally opened folder on the NTFS partition. What I expected to happen? Clicking on an already opened nautilus window will open(bring to foreground) the folder on the NTFS partition. What actually happened? A new window with my home folder as its default opening path, opened, giving me two nautilus windows opened. lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu Trusty Tahr (development branch) Release: 14.04 Codename: trusty apt-cache policy nautilus nautilus: Installed: 1:3.10.1-0ubuntu8 Candidate: 1:3.10.1-0ubuntu8 Version table: *** 1:3.10.1-0ubuntu8 0 500 http://in.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status --- ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 InstallationDate: Installed on 2014-03-17 (7 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140316) Package: unity 7.1.2+14.04.20140320.1-0ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 3.13.0-19.39-generic 3.13.6 Tags: trusty Uname: Linux 3.13.0-19-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip kvm libvirtd lpadmin plugdev sambashare sudo www-data _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1295794/+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 1290785] Re: Users with UID 60000 are invisible in login and Settings-User unless /etc/login.defs updated
The trusty version is uploaded to the archive and is awaiting an archive administrator to push it through. Then it will need to go through the SRU process: https://wiki.ubuntu.com/StableReleaseUpdates -- You received this bug notification because you are a member of DX Packages, which is subscribed to accountsservice in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1290785 Title: Users with UID 6 are invisible in login and Settings-User unless /etc/login.defs updated Status in “accountsservice” package in Ubuntu: Fix Released Status in “accountsservice” source package in Trusty: Triaged Bug description: [Impact] Users of Ubuntu 14.04 LTS with UID 6 will not show in the greeter or system settings without editing UID_MAX in /etc/login.defs. This was not required in 12.04 LTS. In 12.04 LTS users were only hidden if they had UID UID_MIN. In 13.10 this was changed to UID UID_MIN or UID UID_MAX. [Test Case] 1. Create a user with a UID UID_MAX: $ adduser --uid 60001 big-uid 2. Restart system Expected result: big-uid is shown in the greeter. Once logged in big-uid is shown in system settings. Observed result: big-uid is not shown in the greeter (14.04 LTS, 14.10) big-uid is not shown in system settings (13.10, 14.04LTS, 14.10) [Regression Potential] This could cause users that were previously hidden to be shown. This seems unlikely to be a problem as all system created user accounts are less than UID_MIN and there doesn't seem be a convention to use accounts UID_MAX for this case. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1290785/+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 1324114] Re: Unity kills running compiz, even if it belongs to a different Unity session
This bug was fixed in the package unity - 7.3.0+14.10.20140708-0ubuntu1 --- unity (7.3.0+14.10.20140708-0ubuntu1) utopic; urgency=low [ Ubuntu daily release ] * New rebuild forced [ Stephen M. Webb ] * reduce the scope of the kill command when restarting compiz (LP: #1324114) [ Eleni Maria Stea ] * Changed the PreviewStyle.h/cpp to use em sizes (RawPixel). * Added scale factor to Preview (base class), preview container and to the components they contain. * Scaled the ApplicationPreview and the containing widgets and components. * Scaled GenericPreview and its widgets. * scaled ErrorPreview * Scaled MoviePreview and widgets [ Pawel Szubert ] * reduce the scope of the kill command when restarting compiz (LP: #1324114) -- Ubuntu daily release ps-jenk...@lists.canonical.com Tue, 08 Jul 2014 14:35:37 + ** Changed in: unity (Ubuntu) Status: In Progress = 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/1324114 Title: Unity kills running compiz, even if it belongs to a different Unity session Status in Unity: In Progress Status in Unity 7.2 series: Triaged Status in “unity” package in Ubuntu: Fix Released Status in “unity” source package in Trusty: Triaged Bug description: Hi! I'm trying to get a setup with two different Unity desktop sessions running at the same time. One for the local desktop, one for a remote desktop. This almost works, except that when starting the second Unity session, the compiz process that belongs to the first one is killed because of this code in /usr/bin/unity: # kill a previous compiz if was there (this is a hack as compiz can # sometimes get stuck and not exit on --replace) subprocess.call ([pkill, -9, compiz]) Commenting this line makes both desktop sessions work fine. This kill is far too harsh. If you want to kill compiz, you should make sure that you are killing it in the same DISPLAY as the session that you are about to start, and not just every possible compiz process that is running. Please consider either removing the kill or making it apply only to processes in the same DISPLAY. Thanks. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1324114/+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 1305586] Re: Lock screen is unusable when some windows have a keyboard/mouse grab
Ahh, missed comment #23, thrown off by the verification-needed tags :). Sorry for the noise, I'll keep watching. -- 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/1305586 Title: Lock screen is unusable when some windows have a keyboard/mouse grab Status in Compiz: Fix Committed Status in Compiz 0.9.11 series: In Progress Status in Unity: Fix Released Status in Unity 7.2 series: In Progress Status in “compiz” package in Ubuntu: Fix Released Status in “unity” package in Ubuntu: Fix Released Status in “compiz” source package in Trusty: Fix Committed Status in “unity” source package in Trusty: Confirmed Bug description: [Impact] Some windows will grab the keyboard/mouse and when the lockscreen kicks in, this window will still have the grab and thusly, ou can enter your password in the lockscreen. [Test case] 1. Open a window that will hold the grab, such as the ssh password dialog. 2. Wait for the lock screen to activate. 3. Enter your password to unlock the screen. [Regression potential] This particular fix doesn't fix all cases, but does fix it for some. That said, no new regressions are expected. * Debdiff is found at https://launchpadlibrarian.net/178439518/compiz- trusty-sru-2.debdiff * Original Description: My screen just timed out and locked when a password prompt which had a grab was displaying. I couldn't type my password or interact with the indicators. gnome-screensaver just refuses to lock in this situation, perhaps unity could do the same unless it's possible to remove and readd the grabs yourself, but I don't think XLib lets you do that (you can only remove your own grabs AFAIK). TEMPORARY WORKAROUND TO LOGIN AGAIN: Click on the guest session Once the guest session is started log out This takes you back to the lightdm session screen you can then login to your user session and it be in the same state ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140409-0ubuntu1 [origin: unknown] ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8 Uname: Linux 3.13.0-23-generic x86_64 ApportVersion: 2.14.1-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CrashDB: unity CurrentDesktop: Unity Date: Thu Apr 10 09:39:45 2014 InstallationDate: Installed on 2012-10-07 (549 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Beta amd64 (20121007) SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2013-05-07 (338 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1305586/+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 1314939] Re: Some elements in UI don't honor UI scale settings anymore
[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/1314939 Title: Some elements in UI don't honor UI scale settings anymore Status in Unity: Incomplete Status in “unity” package in Ubuntu: Expired Bug description: My laptop is connected to an external monitor which I use as primary display. After few normal routines of suspend and wakeup everyday, I notice some UI elements in Unity don't respect UI scale settings anymore when my laptop wakes up and resume my login session and Unity even ignore the settings completely when I adjust around the UI scale in Display applet. Please see screenshot links below http://i.imgur.com/y1ZXmCL.png http://i.imgur.com/wCmtNZ2.png http://i.imgur.com/XVbshir.png http://i.imgur.com/7va9taj.png ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140423-0ubuntu1.2 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic i686 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3 Architecture: i386 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 May 1 15:51:33 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: vboxhost, 4.3.10, 3.13.0-24-generic, i686: installed EcryptfsInUse: Yes GraphicsCard: Intel Corporation Atom Processor D4xx/D5xx/N4xx/N5xx Integrated Graphics Controller [8086:a011] (prog-if 00 [VGA controller]) Subsystem: Intel Corporation Device [8086:a001] Subsystem: Intel Corporation Device [8086:a001] InstallationDate: Installed on 2014-04-01 (29 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Daily i386 (20140331) MachineType: Intel Corporation Pine Trail - M CRB ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic root=UUID=cb7acec2-e0c5-4138-beb9-da46e06eaa8e ro quiet splash vt.handoff=7 SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/29/2010 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.asset.tag: PTL Nanjing dmi.board.name: Pine Trail - M CRB dmi.board.vendor: Intel Corporation dmi.board.version: Revision A dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd07/29/2010:svnIntelCorporation:pnPineTrail-MCRB:pvrRevisionA:rvnIntelCorporation:rnPineTrail-MCRB:rvrRevisionA:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: Pine Trail - M CRB dmi.product.version: Revision A dmi.sys.vendor: Intel Corporation version.compiz: compiz 1:0.9.11+14.04.20140409-0ubuntu1 version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-4ubuntu5 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-4ubuntu5 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2 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 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Tue Apr 29 20:07:51 2014 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 268 vendor ACR xserver.version: 2:1.15.1-0ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1314939/+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 1313014] Re: Menus in bustle don't work in 14.04
[Expired for bustle (Ubuntu) because there has been no activity for 60 days.] ** Changed in: bustle (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/1313014 Title: Menus in bustle don't work in 14.04 Status in “bustle” package in Ubuntu: Expired Status in “unity” package in Ubuntu: Expired Bug description: Using Unity Desktop in Ubuntu 14.04, the application menu in bustle does not work. You can click the menu itmes and nothing happens. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bustle/+bug/1313014/+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 1313014] Re: Menus in bustle don't work in 14.04
[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/1313014 Title: Menus in bustle don't work in 14.04 Status in “bustle” package in Ubuntu: Expired Status in “unity” package in Ubuntu: Expired Bug description: Using Unity Desktop in Ubuntu 14.04, the application menu in bustle does not work. You can click the menu itmes and nothing happens. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bustle/+bug/1313014/+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 1313067] Re: Screen lock though deselected
[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/1313067 Title: Screen lock though deselected Status in Unity: Expired Status in “unity” package in Ubuntu: Expired Bug description: Screen lock is disabled, Screen timeout to 5 minutes. After Screen is off unity always ask for my password to activate ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140416-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-15.25-generic 3.11.10 Uname: Linux 3.11.0-15-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.38 Wed Jan 8 19:32:30 PST 2014 GCC version: gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1) .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CompizPlugins: [core,crashhandler,composite,opengl,decor,compiztoolbox,gnomecompat,regex,animation,grid,mousepoll,snap,vpswitch,wall,workarounds,dbus,screenshot,resize,place,move,imgpng,fade,expo,ezoom,session,notification,unitymtgrabhandles,scale,unityshell,bench] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Sat Apr 26 13:25:15 2014 DistUpgraded: 2014-04-18 16:40:52,576 DEBUG enabling apt cron job DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: bbswitch, 0.7, 3.11.0-15-generic, x86_64: installed nvidia-331-updates, 331.38, 3.11.0-15-generic, x86_64: installed vboxhost, 4.3.10, 3.11.0-15-generic, x86_64: installed vboxhost, 4.3.10, 3.11.0-19-generic, x86_64: installed vboxhost, 4.3.10, 3.13.0-24-generic, x86_64: installed GraphicsCard: NVIDIA Corporation GT218 [GeForce 210] [10de:0a65] (rev a2) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:8354] InstallationDate: Installed on 2013-12-12 (134 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) LightdmGreeterLog: ** (lightdm-gtk-greeter:3688): WARNING **: Failed to load user background: Datei »/home/jff/Bilder/Hintergründe/65514_1600x1200-wallpaper-cb1364321978.jpg« konnte nicht geöffnet werden: Keine Berechtigung LightdmGreeterLogOld: ** (lightdm-gtk-greeter:3958): WARNING **: Failed to load user background: Datei »/home/jff/Bilder/Hintergründe/65514_1600x1200-wallpaper-cb1364321978.jpg« konnte nicht geöffnet werden: Keine Berechtigung MachineType: MSI MS-7640 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.11.0-15-generic root=UUID=9df67def-e517-4b71-962d-1dd8b1b4293b ro quiet splash SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2014-04-18 (7 days ago) dmi.bios.date: 10/09/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V11.13 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: 990FXA-GD80 (MS-7640) dmi.board.vendor: MSI dmi.board.version: 2.2 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 2.2 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV11.13:bd10/09/2012:svnMSI:pnMS-7640:pvr2.2:rvnMSI:rn990FXA-GD80(MS-7640):rvr2.2:cvnMSI:ct3:cvr2.2: dmi.product.name: MS-7640 dmi.product.version: 2.2 dmi.sys.vendor: MSI version.compiz: compiz 1:0.9.11+14.04.20140409-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-4ubuntu5 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-4ubuntu5 version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2 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 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Sat Apr 26 07:29:41 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.15.1-0ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1313067/+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 1313067] Re: Screen lock though deselected
[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/1313067 Title: Screen lock though deselected Status in Unity: Expired Status in “unity” package in Ubuntu: Expired Bug description: Screen lock is disabled, Screen timeout to 5 minutes. After Screen is off unity always ask for my password to activate ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140416-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-15.25-generic 3.11.10 Uname: Linux 3.11.0-15-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.38 Wed Jan 8 19:32:30 PST 2014 GCC version: gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1) .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CompizPlugins: [core,crashhandler,composite,opengl,decor,compiztoolbox,gnomecompat,regex,animation,grid,mousepoll,snap,vpswitch,wall,workarounds,dbus,screenshot,resize,place,move,imgpng,fade,expo,ezoom,session,notification,unitymtgrabhandles,scale,unityshell,bench] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Sat Apr 26 13:25:15 2014 DistUpgraded: 2014-04-18 16:40:52,576 DEBUG enabling apt cron job DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: bbswitch, 0.7, 3.11.0-15-generic, x86_64: installed nvidia-331-updates, 331.38, 3.11.0-15-generic, x86_64: installed vboxhost, 4.3.10, 3.11.0-15-generic, x86_64: installed vboxhost, 4.3.10, 3.11.0-19-generic, x86_64: installed vboxhost, 4.3.10, 3.13.0-24-generic, x86_64: installed GraphicsCard: NVIDIA Corporation GT218 [GeForce 210] [10de:0a65] (rev a2) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:8354] InstallationDate: Installed on 2013-12-12 (134 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) LightdmGreeterLog: ** (lightdm-gtk-greeter:3688): WARNING **: Failed to load user background: Datei »/home/jff/Bilder/Hintergründe/65514_1600x1200-wallpaper-cb1364321978.jpg« konnte nicht geöffnet werden: Keine Berechtigung LightdmGreeterLogOld: ** (lightdm-gtk-greeter:3958): WARNING **: Failed to load user background: Datei »/home/jff/Bilder/Hintergründe/65514_1600x1200-wallpaper-cb1364321978.jpg« konnte nicht geöffnet werden: Keine Berechtigung MachineType: MSI MS-7640 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.11.0-15-generic root=UUID=9df67def-e517-4b71-962d-1dd8b1b4293b ro quiet splash SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2014-04-18 (7 days ago) dmi.bios.date: 10/09/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V11.13 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: 990FXA-GD80 (MS-7640) dmi.board.vendor: MSI dmi.board.version: 2.2 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 2.2 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV11.13:bd10/09/2012:svnMSI:pnMS-7640:pvr2.2:rvnMSI:rn990FXA-GD80(MS-7640):rvr2.2:cvnMSI:ct3:cvr2.2: dmi.product.name: MS-7640 dmi.product.version: 2.2 dmi.sys.vendor: MSI version.compiz: compiz 1:0.9.11+14.04.20140409-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-4ubuntu5 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-4ubuntu5 version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2 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 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Sat Apr 26 07:29:41 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.15.1-0ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1313067/+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 1313067] Re: Screen lock though deselected
Hi, org.gnome.desktop.screensaver lock-enabled is false Jörg ** Changed in: unity Status: Expired = Confirmed ** Changed in: unity (Ubuntu) Status: Expired = Confirmed -- 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/1313067 Title: Screen lock though deselected Status in Unity: Confirmed Status in “unity” package in Ubuntu: Confirmed Bug description: Screen lock is disabled, Screen timeout to 5 minutes. After Screen is off unity always ask for my password to activate ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140416-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-15.25-generic 3.11.10 Uname: Linux 3.11.0-15-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.38 Wed Jan 8 19:32:30 PST 2014 GCC version: gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1) .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CompizPlugins: [core,crashhandler,composite,opengl,decor,compiztoolbox,gnomecompat,regex,animation,grid,mousepoll,snap,vpswitch,wall,workarounds,dbus,screenshot,resize,place,move,imgpng,fade,expo,ezoom,session,notification,unitymtgrabhandles,scale,unityshell,bench] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Sat Apr 26 13:25:15 2014 DistUpgraded: 2014-04-18 16:40:52,576 DEBUG enabling apt cron job DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: bbswitch, 0.7, 3.11.0-15-generic, x86_64: installed nvidia-331-updates, 331.38, 3.11.0-15-generic, x86_64: installed vboxhost, 4.3.10, 3.11.0-15-generic, x86_64: installed vboxhost, 4.3.10, 3.11.0-19-generic, x86_64: installed vboxhost, 4.3.10, 3.13.0-24-generic, x86_64: installed GraphicsCard: NVIDIA Corporation GT218 [GeForce 210] [10de:0a65] (rev a2) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:8354] InstallationDate: Installed on 2013-12-12 (134 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) LightdmGreeterLog: ** (lightdm-gtk-greeter:3688): WARNING **: Failed to load user background: Datei »/home/jff/Bilder/Hintergründe/65514_1600x1200-wallpaper-cb1364321978.jpg« konnte nicht geöffnet werden: Keine Berechtigung LightdmGreeterLogOld: ** (lightdm-gtk-greeter:3958): WARNING **: Failed to load user background: Datei »/home/jff/Bilder/Hintergründe/65514_1600x1200-wallpaper-cb1364321978.jpg« konnte nicht geöffnet werden: Keine Berechtigung MachineType: MSI MS-7640 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.11.0-15-generic root=UUID=9df67def-e517-4b71-962d-1dd8b1b4293b ro quiet splash SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2014-04-18 (7 days ago) dmi.bios.date: 10/09/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V11.13 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: 990FXA-GD80 (MS-7640) dmi.board.vendor: MSI dmi.board.version: 2.2 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 2.2 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV11.13:bd10/09/2012:svnMSI:pnMS-7640:pvr2.2:rvnMSI:rn990FXA-GD80(MS-7640):rvr2.2:cvnMSI:ct3:cvr2.2: dmi.product.name: MS-7640 dmi.product.version: 2.2 dmi.sys.vendor: MSI version.compiz: compiz 1:0.9.11+14.04.20140409-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-4ubuntu5 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-4ubuntu5 version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2 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 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Sat Apr 26 07:29:41 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.15.1-0ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1313067/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe :
