[Dx-packages] [Bug 1308850] Re: Dash is visible on top of the lockscreen after screen monitor auto locks
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: unity (Ubuntu Trusty) 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/1308850 Title: Dash is visible on top of the lockscreen after screen monitor auto locks Status in Unity: Fix Committed Status in “unity” package in Ubuntu: In Progress Status in “unity” source package in Trusty: Confirmed Bug description: [Impact] This is 100% reproducible on my side with an updated 14.04 I have a laptop that after 3 minutes of inactivity shutdown the screen and lock-it. If I press the SUPER button to activate the dash and then I wait 3 minutes for auto screen locking the screen become black. After that when I move the mouse to go to lockscreen and unlock my session, I see the dash on top of the lockscreen. I can digit my password and unlock the laptop pressing enter but I cannot see the username, box, dots etc I think that the screenshot attached explain very whell what I'm writing. I think that this is a security problem because as you can see from my screenshot other people can see my personal data (file and folders) without authorization. [Test Case] (1) Make sure the screen lock is enabled and has a reasonable timeout set. (2) Use the Super button to activate the Dash. (3) Wait for the screen lock timeout so the lockscreen / screensaver comes up. (4) Move the mouse or press a shift key to display the lockscreen. (5) The Dash should not appear on top of the lockscreen. [Regression Potential] None. The fix is to explicitly undisplay the dash when the screen is locked. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1308850/+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 1222339] Re: Adding Indicator applet appmenu to a panel in gnome classic/fallback causes all items in the panel to disappear
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: indicator-applet (Ubuntu Trusty) Status: New = Confirmed -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-applet in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1222339 Title: Adding Indicator applet appmenu to a panel in gnome classic/fallback causes all items in the panel to disappear Status in Unity GTK+ module: New Status in “gnome-panel” package in Ubuntu: Confirmed Status in “indicator-applet” package in Ubuntu: Confirmed Status in “gnome-panel” source package in Trusty: Fix Committed Status in “indicator-applet” source package in Trusty: Confirmed Bug description: Adding Indicator applet appmenu to a panel in gnome classic/fallback causes all items in the panel to disappear. Alt+right-click - delete on the upper left of the panel causes everything to be fixed. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: indicator-applet-appmenu 12.10.2+13.10.20130822.5-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-4.9-generic 3.11.0-rc7 Uname: Linux 3.11.0-4-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.12.1-0ubuntu3 Architecture: amd64 Date: Sun Sep 8 00:10:38 2013 InstallationDate: Installed on 2013-06-11 (89 days ago) InstallationMedia: Ubuntu-Server 13.04 Raring Ringtail - Release amd64 (20130423.1) MarkForUpload: True SourcePackage: indicator-applet UpgradeStatus: Upgraded to saucy on 2013-09-07 (0 days ago) [Test Case] 1. install gnome-session-flashback. 2. login in session. 3. add indicator-applet-appmenu to gnome-panel. at this point menu-bar will dissapear. 4. remove indicator-applet-appmenu from panel to get menu-bar back. [Regression Potential] I think there is no regression potential. Same fix is used for external applets built with libpanel-applet library. To manage notifications about this bug go to: https://bugs.launchpad.net/unity-gtk-module/+bug/1222339/+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 1222339] Re: Adding Indicator applet appmenu to a panel in gnome classic/fallback causes all items in the panel to disappear
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-panel (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-applet in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1222339 Title: Adding Indicator applet appmenu to a panel in gnome classic/fallback causes all items in the panel to disappear Status in Unity GTK+ module: New Status in “gnome-panel” package in Ubuntu: Confirmed Status in “indicator-applet” package in Ubuntu: Confirmed Status in “gnome-panel” source package in Trusty: Fix Committed Status in “indicator-applet” source package in Trusty: Confirmed Bug description: Adding Indicator applet appmenu to a panel in gnome classic/fallback causes all items in the panel to disappear. Alt+right-click - delete on the upper left of the panel causes everything to be fixed. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: indicator-applet-appmenu 12.10.2+13.10.20130822.5-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-4.9-generic 3.11.0-rc7 Uname: Linux 3.11.0-4-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.12.1-0ubuntu3 Architecture: amd64 Date: Sun Sep 8 00:10:38 2013 InstallationDate: Installed on 2013-06-11 (89 days ago) InstallationMedia: Ubuntu-Server 13.04 Raring Ringtail - Release amd64 (20130423.1) MarkForUpload: True SourcePackage: indicator-applet UpgradeStatus: Upgraded to saucy on 2013-09-07 (0 days ago) [Test Case] 1. install gnome-session-flashback. 2. login in session. 3. add indicator-applet-appmenu to gnome-panel. at this point menu-bar will dissapear. 4. remove indicator-applet-appmenu from panel to get menu-bar back. [Regression Potential] I think there is no regression potential. Same fix is used for external applets built with libpanel-applet library. To manage notifications about this bug go to: https://bugs.launchpad.net/unity-gtk-module/+bug/1222339/+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 1308850] Re: Dash is visible on top of the lockscreen after screen monitor auto locks
Just enabled trusty-proposed and installed updated unity giovanni@jellyfish:~$ apt-cache show unity Package: unity Status: install ok installed Priority: optional Section: gnome Installed-Size: 5996 Maintainer: Ubuntu Developers ubuntu-devel-disc...@lists.ubuntu.com Architecture: amd64 Version: 7.2.0+14.04.20140423-0ubuntu1 [...] I confirm that the fix is working and I cannot reproduce the bug anymore. Tks Giovanni -- 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/1308850 Title: Dash is visible on top of the lockscreen after screen monitor auto locks Status in Unity: Fix Committed Status in “unity” package in Ubuntu: In Progress Status in “unity” source package in Trusty: Confirmed Bug description: [Impact] This is 100% reproducible on my side with an updated 14.04 I have a laptop that after 3 minutes of inactivity shutdown the screen and lock-it. If I press the SUPER button to activate the dash and then I wait 3 minutes for auto screen locking the screen become black. After that when I move the mouse to go to lockscreen and unlock my session, I see the dash on top of the lockscreen. I can digit my password and unlock the laptop pressing enter but I cannot see the username, box, dots etc I think that the screenshot attached explain very whell what I'm writing. I think that this is a security problem because as you can see from my screenshot other people can see my personal data (file and folders) without authorization. [Test Case] (1) Make sure the screen lock is enabled and has a reasonable timeout set. (2) Use the Super button to activate the Dash. (3) Wait for the screen lock timeout so the lockscreen / screensaver comes up. (4) Move the mouse or press a shift key to display the lockscreen. (5) The Dash should not appear on top of the lockscreen. [Regression Potential] None. The fix is to explicitly undisplay the dash when the screen is locked. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1308850/+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 1308850] Re: Dash is visible on top of the lockscreen after screen monitor auto locks
Very nice! That 7.2.0-14 seems to have fixed the suspend-resume dash locking up! -- 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/1308850 Title: Dash is visible on top of the lockscreen after screen monitor auto locks Status in Unity: Fix Committed Status in “unity” package in Ubuntu: In Progress Status in “unity” source package in Trusty: Confirmed Bug description: [Impact] This is 100% reproducible on my side with an updated 14.04 I have a laptop that after 3 minutes of inactivity shutdown the screen and lock-it. If I press the SUPER button to activate the dash and then I wait 3 minutes for auto screen locking the screen become black. After that when I move the mouse to go to lockscreen and unlock my session, I see the dash on top of the lockscreen. I can digit my password and unlock the laptop pressing enter but I cannot see the username, box, dots etc I think that the screenshot attached explain very whell what I'm writing. I think that this is a security problem because as you can see from my screenshot other people can see my personal data (file and folders) without authorization. [Test Case] (1) Make sure the screen lock is enabled and has a reasonable timeout set. (2) Use the Super button to activate the Dash. (3) Wait for the screen lock timeout so the lockscreen / screensaver comes up. (4) Move the mouse or press a shift key to display the lockscreen. (5) The Dash should not appear on top of the lockscreen. [Regression Potential] None. The fix is to explicitly undisplay the dash when the screen is locked. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1308850/+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 1291362] Re: Apps locked to launcher only launch once per session on dual monitor system.
Huge thanks for the fix! I can't even tell you how annoying was face this bug every day and start most programs through dash... Now, after installing updates from proposed repository and reboot it works just perfect ! Sad I can't shake your hand :) I will test more and if there will be problems, post comment here. -- 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/1291362 Title: Apps locked to launcher only launch once per session on dual monitor system. Status in Unity: Fix Committed Status in “unity” package in Ubuntu: In Progress Status in “unity” source package in Trusty: Confirmed Bug description: [Impact] Users having the Launcher only on a monitor that is not the left-most monitor can only open the application once. This can lead to much frustration and a restart of the system in order to open the application again using the Launcher. [Test Case] * Have a multi-monitor setup. * Using System Settings, go to Displays. * Under General options, click the drop down for Launcher placement and select the right-most monitor. * Click an icon to open a application. Close that application and click the icon again. * The application should open again with this fix. [Regression Potential] None identified. Original Description: In Trusty: On a dual monitor system with the launcher on the right hand screen, an application that has been locked to launcher, (including those there by default) can only be clicked on once per session to actually launch the application. After that it's unresponsive to clicks, although right-click actions work. Seems to affect all apps, including Files. To repeat, for any application not already on the launcher bar: Launch the application using the dash. Right-click on its launcher icon and select Lock to Launcher Quit the application. Click on its launcher icon. It should launch again. Quit it again. Click on its launcher icon again. It won't work this time. It looks like dragging would work, but its operation as a launcher will not. NB: I haven't installed any hacks eg: click-to-minimise. Seen this on two systems upgraded from saucy to trusty. (One with AMD graphics, one with Intel, so I doubt that's relevant either.) ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.1.2+14.04.20140311-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6 Uname: Linux 3.13.0-17-generic x86_64 ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Wed Mar 12 13:10:56 2014 InstallationDate: Installed on 2014-03-08 (3 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2014-03-10 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1291362/+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 1308750] Re: When unity crashes while in the lockscreen, it is by passed.
impossible to login without a keyboard, that is, using only the mouse -- 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/1308750 Title: When unity crashes while in the lockscreen, it is by passed. Status in Unity: Fix Released Status in “unity” package in Ubuntu: Fix Released Bug description: To reproduce: 1) Open the lockscreen (Super+L) 2) Hold Enter down wait . *Crash* Expected: *No crash* Stacktrace: http://paste.ubuntu.com/7263684/ To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1308750/+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 1308750] Re: When unity crashes while in the lockscreen, it is by passed.
On the new login screen is impossible to login without a keyboard, then estispolzuya mouse only. I have the usual case - 2nd screen TV, only the mouse and virtual keyboard. -- 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/1308750 Title: When unity crashes while in the lockscreen, it is by passed. Status in Unity: Fix Released Status in “unity” package in Ubuntu: Fix Released Bug description: To reproduce: 1) Open the lockscreen (Super+L) 2) Hold Enter down wait . *Crash* Expected: *No crash* Stacktrace: http://paste.ubuntu.com/7263684/ To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1308750/+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 1291362] Re: Apps locked to launcher only launch once per session on dual monitor system.
** 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 unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1291362 Title: Apps locked to launcher only launch once per session on dual monitor system. Status in Unity: Fix Committed Status in “unity” package in Ubuntu: In Progress Status in “unity” source package in Trusty: Confirmed Bug description: [Impact] Users having the Launcher only on a monitor that is not the left-most monitor can only open the application once. This can lead to much frustration and a restart of the system in order to open the application again using the Launcher. [Test Case] * Have a multi-monitor setup. * Using System Settings, go to Displays. * Under General options, click the drop down for Launcher placement and select the right-most monitor. * Click an icon to open a application. Close that application and click the icon again. * The application should open again with this fix. [Regression Potential] None identified. Original Description: In Trusty: On a dual monitor system with the launcher on the right hand screen, an application that has been locked to launcher, (including those there by default) can only be clicked on once per session to actually launch the application. After that it's unresponsive to clicks, although right-click actions work. Seems to affect all apps, including Files. To repeat, for any application not already on the launcher bar: Launch the application using the dash. Right-click on its launcher icon and select Lock to Launcher Quit the application. Click on its launcher icon. It should launch again. Quit it again. Click on its launcher icon again. It won't work this time. It looks like dragging would work, but its operation as a launcher will not. NB: I haven't installed any hacks eg: click-to-minimise. Seen this on two systems upgraded from saucy to trusty. (One with AMD graphics, one with Intel, so I doubt that's relevant either.) ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.1.2+14.04.20140311-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6 Uname: Linux 3.13.0-17-generic x86_64 ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Wed Mar 12 13:10:56 2014 InstallationDate: Installed on 2014-03-08 (3 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2014-03-10 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1291362/+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 1170647] Re: Clicking on Nautilus’ launcher icon opens new window instead of restoring the minimized one when browsing external drives/locations
I had the same problem in 13.10 and still exists in 14.04 32bit. When just one window is opened and minimised, clicking on nautilus icon on launchbar will opens a new window instead of maximising the minimized window. It really doesn't matter which folder is opened. It always happens. -- 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/1170647 Title: Clicking on Nautilus’ launcher icon opens new window instead of restoring the minimized one when browsing external drives/locations Status in “bamf” package in Ubuntu: Triaged Status in “nautilus” package in Ubuntu: Triaged Status in “unity” package in Ubuntu: Triaged Bug description: Sometimes left clicking the nautilus launcher icon doesn't bring up a minimized nautilus window. Instead of restoring the window a new instance of nautilus is showing up. Steps to reproduce: 1. Open a nautilus window by clicking on the launcher icon. 2. Navigate to a symlinked directory whose target is located on a different harddrive (for example: a symlink to a folder on a sd-card). 3. Minimize the nautilus window. 4. Try to bring up that window again by clicking the launcher icon. What happens: 1. A new instance (window) of nautilus is opened. 2. There's no obvious way to access the first window again. The only way is ALT+TAB. What schould happen: If a nautilus window is already open and minimized clicking the launcher icon should bring up that window. This was the behavior of nautilus windows in Ubuntu 12.10 (quantal). Ubuntu 13.04 Raring Ringtail (development branch) nautilus 3.6.3-0ubuntu16 unity 7.0.0daily13.04.18~13.04-0ubuntu1 ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: nautilus 1:3.6.3-0ubuntu16 ProcVersionSignature: Ubuntu 3.8.0-18.28-generic 3.8.6 Uname: Linux 3.8.0-18-generic i686 ApportVersion: 2.9.2-0ubuntu8 Architecture: i386 Date: Fri Apr 19 11:33:13 2013 EcryptfsInUse: Yes GsettingsChanges: b'org.gnome.nautilus.window-state' b'geometry' b'814x493+136+38' b'org.gnome.nautilus.window-state' b'sidebar-width' b'182' InstallationDate: Installed on 2011-07-23 (635 days ago) InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release i386 (20110426) MarkForUpload: True SourcePackage: nautilus UpgradeStatus: Upgraded to raring on 2013-04-14 (4 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bamf/+bug/1170647/+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 1291362] Re: Apps locked to launcher only launch once per session on dual monitor system.
working here also. -- 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/1291362 Title: Apps locked to launcher only launch once per session on dual monitor system. Status in Unity: Fix Committed Status in “unity” package in Ubuntu: In Progress Status in “unity” source package in Trusty: Confirmed Bug description: [Impact] Users having the Launcher only on a monitor that is not the left-most monitor can only open the application once. This can lead to much frustration and a restart of the system in order to open the application again using the Launcher. [Test Case] * Have a multi-monitor setup. * Using System Settings, go to Displays. * Under General options, click the drop down for Launcher placement and select the right-most monitor. * Click an icon to open a application. Close that application and click the icon again. * The application should open again with this fix. [Regression Potential] None identified. Original Description: In Trusty: On a dual monitor system with the launcher on the right hand screen, an application that has been locked to launcher, (including those there by default) can only be clicked on once per session to actually launch the application. After that it's unresponsive to clicks, although right-click actions work. Seems to affect all apps, including Files. To repeat, for any application not already on the launcher bar: Launch the application using the dash. Right-click on its launcher icon and select Lock to Launcher Quit the application. Click on its launcher icon. It should launch again. Quit it again. Click on its launcher icon again. It won't work this time. It looks like dragging would work, but its operation as a launcher will not. NB: I haven't installed any hacks eg: click-to-minimise. Seen this on two systems upgraded from saucy to trusty. (One with AMD graphics, one with Intel, so I doubt that's relevant either.) ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.1.2+14.04.20140311-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6 Uname: Linux 3.13.0-17-generic x86_64 ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Wed Mar 12 13:10:56 2014 InstallationDate: Installed on 2014-03-08 (3 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2014-03-10 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1291362/+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 1291362] Re: Apps locked to launcher only launch once per session on dual monitor system.
The proposed fix works for me too. -- 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/1291362 Title: Apps locked to launcher only launch once per session on dual monitor system. Status in Unity: Fix Committed Status in “unity” package in Ubuntu: In Progress Status in “unity” source package in Trusty: Confirmed Bug description: [Impact] Users having the Launcher only on a monitor that is not the left-most monitor can only open the application once. This can lead to much frustration and a restart of the system in order to open the application again using the Launcher. [Test Case] * Have a multi-monitor setup. * Using System Settings, go to Displays. * Under General options, click the drop down for Launcher placement and select the right-most monitor. * Click an icon to open a application. Close that application and click the icon again. * The application should open again with this fix. [Regression Potential] None identified. Original Description: In Trusty: On a dual monitor system with the launcher on the right hand screen, an application that has been locked to launcher, (including those there by default) can only be clicked on once per session to actually launch the application. After that it's unresponsive to clicks, although right-click actions work. Seems to affect all apps, including Files. To repeat, for any application not already on the launcher bar: Launch the application using the dash. Right-click on its launcher icon and select Lock to Launcher Quit the application. Click on its launcher icon. It should launch again. Quit it again. Click on its launcher icon again. It won't work this time. It looks like dragging would work, but its operation as a launcher will not. NB: I haven't installed any hacks eg: click-to-minimise. Seen this on two systems upgraded from saucy to trusty. (One with AMD graphics, one with Intel, so I doubt that's relevant either.) ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.1.2+14.04.20140311-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6 Uname: Linux 3.13.0-17-generic x86_64 ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Wed Mar 12 13:10:56 2014 InstallationDate: Installed on 2014-03-08 (3 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2014-03-10 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1291362/+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 815996] Re: Desktop occasionally freezes/locks up when switching workspaces
Confirm for 14.04. It happens almost every time I'm moving a VirtualBox virtual machine window. I have found no way to get out of it other than reboot. -- 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/815996 Title: Desktop occasionally freezes/locks up when switching workspaces Status in Compiz: Confirmed Status in Compiz Main Plugins: Confirmed Status in Compiz Desktop Wall Plugin: Confirmed Status in “compiz-plugins-main” package in Ubuntu: Confirmed Bug description: I'm assuming the issue is related to Compiz, but I'm not 100% sure. When I'm switching workspaces, it occasionally locks up (becoming more frequent). Most of the time, I'm going from the current one down (Ctrl+Alt+Down Arrow), and it freezes mid slide. Typically, I'm able to correct things by backing out to a terminal then returning (Ctrl+Alt+F1, pause, Alt+F7), but sometimes when I return the dual screen setup acts as one large screen (windows are stretched to the full width of both screens) and many of the windows collect on the first workspace. Ubuntu 11.04 (Classic) All packages up-to-date. If there are any logs/etc that would be helpful, let me know. --- Architecture: amd64 CompizPlugins: [core,bailer,detection,composite,opengl,decor,grid,imgpng,snap,compiztoolbox,resize,place,regex,move,gnomecompat,animation,vpswitch,mousepoll,workarounds,session,expo,wall,ezoom,fade,switcher,scale] DistroCodename: natty DistroRelease: Ubuntu 11.04 DistroVariant: ubuntu InstallationMedia: Ubuntu 10.04 LTS Lucid Lynx - Release amd64 (20100429) InstallationMedia_: Ubuntu 10.04 LTS Lucid Lynx - Release amd64 (20100429) NonfreeKernelModules: nvidia Package: compiz 1:0.9.4+bzr20110606-0ubuntu1~natty2 PackageArchitecture: all ProcEnviron: LANGUAGE=en_US:en PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.38-10.46-generic 2.6.38.7 ProcVersionSignature_: Ubuntu 2.6.38-10.46-generic 2.6.38.7 Tags: natty natty ubuntu Uname: Linux 2.6.38-10-generic x86_64 UnreportableReason: Please work this issue through technical support channels first. UpgradeStatus: Upgraded to natty on 2011-05-02 (84 days ago) UserGroups: adm admin audio cdrom dialout dip fuse lpadmin netdev plugdev sambashare To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/815996/+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] [NEW] Unity Lockscreen in 14.04 can't unlock when using LDAP account
Public bug reported: 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 ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: lockscreen -- 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” package in Ubuntu: New 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
[Dx-packages] [Bug 1313910] Re: can launch evolution from the greeter in 13.10
*** This bug is a duplicate of bug 1246812 *** https://bugs.launchpad.net/bugs/1246812 ** This bug has been marked a duplicate of bug 1246812 Can open Evolution in greeter mode -- 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/1313910 Title: can launch evolution from the greeter in 13.10 Status in “indicator-datetime” package in Ubuntu: New Bug description: In Ubuntu 13.10, indicator-datetime will launch evolution from the greeter. Steps to reproduce: 1- apt-get install evolution 2- From greeter, click on calendar header Expected results: - Nothing happening Actual results: - evolution is launched ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: indicator-datetime 13.10.0+13.10.20131023.2-0ubuntu1 ProcVersionSignature: User Name 3.11.0-19.33-generic 3.11.10.5 Uname: Linux 3.11.0-19-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 Date: Mon Apr 28 16:39:17 2014 InstallationDate: Installed on 2014-01-31 (87 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) MarkForUpload: True SourcePackage: indicator-datetime UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1313910/+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 1311211] Re: Bluetooth icon has a padlock emblem when paired with device
Heh, that's currently an open question in the spec. I agree it's probably a good idea, but a padlock doesn't make sense as the emblem. ** Changed in: indicator-bluetooth (Ubuntu) Assignee: (unassigned) = Matthew Paul Thomas (mpt) -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-bluetooth in Ubuntu. https://bugs.launchpad.net/bugs/1311211 Title: Bluetooth icon has a padlock emblem when paired with device Status in “indicator-bluetooth” package in Ubuntu: Confirmed Bug description: indicator-bluetooth 0.0.6+14.04.20140207-0ubuntu2, Ubuntu 14.04 There is some situation -- I don't know what -- in which the Bluetooth icon in the menu bar appears with a padlock emblem. This is not mentioned anywhere in the design specification. https://wiki.ubuntu.com/Bluetooth#PC Either the code is wrong, or the spec is wrong. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-bluetooth/+bug/1311211/+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 1314126] [NEW] Ubuntu logo from login screen remains visible on desktop after login
Public bug reported: Steps to reproduce: * Log in to Ubuntu (Unity) session from login screen What should happen: * On login screen: desktop background appears as background, dots are overlayed, Ubuntu logo is overlayed * Once logged in: desktop background appears as background, no dots, no Ubuntu logo What happens instead: * Once logged in: desktop background appears, Ubuntu logo is overlayed Further notes: * I disabled the dots on the login screen, so I'm not sure if they appear, I'm pretty sure not * I am pretty sure that the logo was appearing on the desktop from when I first installed 14.04, it has remained after changing the background and disabling the dots * I have confirmed that the background image itself does not contain the logo ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Affects: unity-greeter (Ubuntu) Importance: Undecided Status: New ** Tags: desktop greeter ** Also affects: unity-greeter (Ubuntu) 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/1314126 Title: Ubuntu logo from login screen remains visible on desktop after login Status in “unity” package in Ubuntu: New Status in “unity-greeter” package in Ubuntu: New Bug description: Steps to reproduce: * Log in to Ubuntu (Unity) session from login screen What should happen: * On login screen: desktop background appears as background, dots are overlayed, Ubuntu logo is overlayed * Once logged in: desktop background appears as background, no dots, no Ubuntu logo What happens instead: * Once logged in: desktop background appears, Ubuntu logo is overlayed Further notes: * I disabled the dots on the login screen, so I'm not sure if they appear, I'm pretty sure not * I am pretty sure that the logo was appearing on the desktop from when I first installed 14.04, it has remained after changing the background and disabling the dots * I have confirmed that the background image itself does not contain the logo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1314126/+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 1313522] [NEW] There is hibernate option even without an active swap partition
You have been subscribed to a public bug: In Ubuntu 13.10 and 14.04 the hibernate option will always be displayed in the system dropdown menu, even if there is no active swap partition. Click the hibernate option will perform the hibernate operation but will fail during the process. As a contrast, in Ubuntu 13.04 and earlier releases the hibernate option is visible only if there is active swap partition. ** Affects: oem-priority Importance: Critical Status: New ** Affects: systemd-shim (Ubuntu) Importance: Undecided Status: Triaged -- There is hibernate option even without an active swap partition https://bugs.launchpad.net/bugs/1313522 You received this bug notification because you are a member of DX Packages, which is subscribed to systemd-shim 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 1313522] Re: There is hibernate option even without an active swap partition
Nevermind, pm-utils isn't checking available swap at all. In the past, upower did that, but now systemd and systemd-shim would need to pick that up. ** Package changed: pm-utils (Ubuntu) = systemd-shim (Ubuntu) ** Changed in: systemd-shim (Ubuntu) Status: Incomplete = Triaged -- 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/1313522 Title: There is hibernate option even without an active swap partition Status in OEM Priority Project: New Status in “systemd-shim” package in Ubuntu: Triaged Bug description: In Ubuntu 13.10 and 14.04 the hibernate option will always be displayed in the system dropdown menu, even if there is no active swap partition. Click the hibernate option will perform the hibernate operation but will fail during the process. As a contrast, in Ubuntu 13.04 and earlier releases the hibernate option is visible only if there is active swap partition. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1313522/+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 1313522] Re: There is hibernate option even without an active swap partition
Checked deeper, src/login/logind-action.c() calls can_sleep(), which in version 204 does not yet check for swap. So we need to backport the checks in src/shared/sleep-config.c from later versions. ** Package changed: systemd-shim (Ubuntu) = systemd (Ubuntu) ** Changed in: systemd (Ubuntu) Importance: Undecided = Medium ** Changed in: systemd (Ubuntu) Status: Triaged = In Progress -- 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/1313522 Title: There is hibernate option even without an active swap partition Status in OEM Priority Project: New Status in “systemd” package in Ubuntu: In Progress Bug description: In Ubuntu 13.10 and 14.04 the hibernate option will always be displayed in the system dropdown menu, even if there is no active swap partition. Click the hibernate option will perform the hibernate operation but will fail during the process. As a contrast, in Ubuntu 13.04 and earlier releases the hibernate option is visible only if there is active swap partition. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1313522/+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
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/1314095 Title: Unity Lockscreen in 14.04 can't unlock when using LDAP account 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 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/ubuntu/+source/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 987060] Re: massive memory leak in unity-panel-service and hud-service when invoking the hud on Firefox profiles with large amounts of bookmarks
Same symptoms for me like Guus Geluk, but on Ubuntu 14.04. -- 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/987060 Title: massive memory leak in unity-panel-service and hud-service when invoking the hud on Firefox profiles with large amounts of bookmarks Status in The Application Menu: Confirmed Status in Unity: Won't Fix Status in “unity” package in Ubuntu: Confirmed Bug description: unity-panel-service and hud-service quickly racks up memory and CPU usage until I kill it when invoking the HUD on Firefox. It's taking anywhere from a few minutes to half an hour, but it sometimes makes the system completely unusable. 1. run Firefox 12.0 in the foreground 2. hit Alt to bring up HUD 3. type any text 4. select one proposal from HUD 5. wait for unity-panel-service and hud-service to fill up the remaining RAM and swap space. This is due to a high number of bookmarks in a user profile (hundreds). To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-appmenu/+bug/987060/+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 1312775] Re: Ignore comments in /etc/timezone
** Changed in: indicator-datetime (Ubuntu) Status: New = Triaged ** Changed in: indicator-datetime (Ubuntu) Importance: Undecided = Medium -- 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/1312775 Title: Ignore comments in /etc/timezone Status in “indicator-datetime” package in Ubuntu: Triaged Bug description: If there is a comment in /etc/timezone the comment is displayed in the indicator and the timezone is ignored. In the screenshot attached the timezone on the 1rst line is Europe/Paris but the clock indicates UTC and the name of the timezone is the full content of /etc/timezone. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: indicator-datetime 13.10.0+14.04.20140415.3-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Fri Apr 25 16:23:11 2014 InstallationDate: Installed on 2013-09-03 (233 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha amd64 (20130902) SourcePackage: indicator-datetime UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1312775/+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 1312337] Re: 14.04LTS - Printer Icon in System Tray does not display when a document is printing
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: indicator-printers (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-printers in Ubuntu. https://bugs.launchpad.net/bugs/1312337 Title: 14.04LTS - Printer Icon in System Tray does not display when a document is printing Status in “indicator-printers” package in Ubuntu: Confirmed Bug description: I've just upgraded from 13.10 and when I print a document from any print source the system tray icon does not display. I have indicator-printers and system-config-printer installed. Can you help? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-printers/+bug/1312337/+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 1313885] Re: lock screen bypass
This bug was fixed in the package unity - 7.2.0+14.04.20140423-0ubuntu1.1 --- unity (7.2.0+14.04.20140423-0ubuntu1.1) trusty-security; urgency=medium * SECURITY UPDATE: lock screen bypass (LP: #1313885) - debian/patches/lp1313885.patch: improve lockscreen logic in lockscreen/LockScreenController.cpp, lockscreen/LockScreenShield.*, plugins/unityshell/src/unityshell.*. -- Marc Deslauriers marc.deslauri...@ubuntu.com Mon, 28 Apr 2014 22:29:13 -0400 ** Changed in: unity (Ubuntu Trusty) 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/1313885 Title: lock screen bypass Status in Unity: In Progress Status in “unity” package in Ubuntu: In Progress Status in “unity” source package in Trusty: Fix Released Status in “unity” source package in Utopic: In Progress Bug description: I found a bug allowing a user to bypass the new lock screen of Ubuntu 14.04 1 - When the screen is locked just right click multiple times on the indicator bar (for example on the battery indicator), then shortcuts are available. 2 - Press ALT+F2 3 - you can execute the command you whant on behalf of the logged user. Here is a video demonstrating this bug : http://www.youtube.com/watch?v=d4UUB0sI5Fc lsb_release -rd Description: Ubuntu 14.04 LTS Release: 14.04 Ubuntu version updated the 04/28/2014 apt-cache policy unity 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://fr.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1313885/+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 1308850] Re: Dash is visible on top of the lockscreen after screen monitor auto locks
** 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 unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1308850 Title: Dash is visible on top of the lockscreen after screen monitor auto locks Status in Unity: Fix Committed Status in “unity” package in Ubuntu: In Progress Status in “unity” source package in Trusty: Confirmed Bug description: [Impact] This is 100% reproducible on my side with an updated 14.04 I have a laptop that after 3 minutes of inactivity shutdown the screen and lock-it. If I press the SUPER button to activate the dash and then I wait 3 minutes for auto screen locking the screen become black. After that when I move the mouse to go to lockscreen and unlock my session, I see the dash on top of the lockscreen. I can digit my password and unlock the laptop pressing enter but I cannot see the username, box, dots etc I think that the screenshot attached explain very whell what I'm writing. I think that this is a security problem because as you can see from my screenshot other people can see my personal data (file and folders) without authorization. [Test Case] (1) Make sure the screen lock is enabled and has a reasonable timeout set. (2) Use the Super button to activate the Dash. (3) Wait for the screen lock timeout so the lockscreen / screensaver comes up. (4) Move the mouse or press a shift key to display the lockscreen. (5) The Dash should not appear on top of the lockscreen. [Regression Potential] None. The fix is to explicitly undisplay the dash when the screen is locked. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1308850/+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 1308850] Re: Dash is visible on top of the lockscreen after screen monitor auto locks
This was fixed by this security update: http://www.ubuntu.com/usn/usn-2184-1/ ** Changed in: unity (Ubuntu Trusty) Status: Confirmed = 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/1308850 Title: Dash is visible on top of the lockscreen after screen monitor auto locks Status in Unity: Fix Committed Status in “unity” package in Ubuntu: In Progress Status in “unity” source package in Trusty: Fix Released Bug description: [Impact] This is 100% reproducible on my side with an updated 14.04 I have a laptop that after 3 minutes of inactivity shutdown the screen and lock-it. If I press the SUPER button to activate the dash and then I wait 3 minutes for auto screen locking the screen become black. After that when I move the mouse to go to lockscreen and unlock my session, I see the dash on top of the lockscreen. I can digit my password and unlock the laptop pressing enter but I cannot see the username, box, dots etc I think that the screenshot attached explain very whell what I'm writing. I think that this is a security problem because as you can see from my screenshot other people can see my personal data (file and folders) without authorization. [Test Case] (1) Make sure the screen lock is enabled and has a reasonable timeout set. (2) Use the Super button to activate the Dash. (3) Wait for the screen lock timeout so the lockscreen / screensaver comes up. (4) Move the mouse or press a shift key to display the lockscreen. (5) The Dash should not appear on top of the lockscreen. [Regression Potential] None. The fix is to explicitly undisplay the dash when the screen is locked. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1308850/+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 1313885] Re: lock screen bypass
http://www.ubuntu.com/usn/usn-2184-1/ -- 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/1313885 Title: lock screen bypass Status in Unity: In Progress Status in “unity” package in Ubuntu: In Progress Status in “unity” source package in Trusty: Fix Released Status in “unity” source package in Utopic: In Progress Bug description: I found a bug allowing a user to bypass the new lock screen of Ubuntu 14.04 1 - When the screen is locked just right click multiple times on the indicator bar (for example on the battery indicator), then shortcuts are available. 2 - Press ALT+F2 3 - you can execute the command you whant on behalf of the logged user. Here is a video demonstrating this bug : http://www.youtube.com/watch?v=d4UUB0sI5Fc lsb_release -rd Description: Ubuntu 14.04 LTS Release: 14.04 Ubuntu version updated the 04/28/2014 apt-cache policy unity 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://fr.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1313885/+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 1291362] Re: Apps locked to launcher only launch once per session on dual monitor system.
The fix for this issue was included as part of today's security update: http://www.ubuntu.com/usn/usn-2184-1/ As such, I am closing this bug. Thanks! ** Changed in: unity (Ubuntu Trusty) Status: Confirmed = 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/1291362 Title: Apps locked to launcher only launch once per session on dual monitor system. Status in Unity: Fix Committed Status in “unity” package in Ubuntu: In Progress Status in “unity” source package in Trusty: Fix Released Bug description: [Impact] Users having the Launcher only on a monitor that is not the left-most monitor can only open the application once. This can lead to much frustration and a restart of the system in order to open the application again using the Launcher. [Test Case] * Have a multi-monitor setup. * Using System Settings, go to Displays. * Under General options, click the drop down for Launcher placement and select the right-most monitor. * Click an icon to open a application. Close that application and click the icon again. * The application should open again with this fix. [Regression Potential] None identified. Original Description: In Trusty: On a dual monitor system with the launcher on the right hand screen, an application that has been locked to launcher, (including those there by default) can only be clicked on once per session to actually launch the application. After that it's unresponsive to clicks, although right-click actions work. Seems to affect all apps, including Files. To repeat, for any application not already on the launcher bar: Launch the application using the dash. Right-click on its launcher icon and select Lock to Launcher Quit the application. Click on its launcher icon. It should launch again. Quit it again. Click on its launcher icon again. It won't work this time. It looks like dragging would work, but its operation as a launcher will not. NB: I haven't installed any hacks eg: click-to-minimise. Seen this on two systems upgraded from saucy to trusty. (One with AMD graphics, one with Intel, so I doubt that's relevant either.) ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.1.2+14.04.20140311-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6 Uname: Linux 3.13.0-17-generic x86_64 ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Wed Mar 12 13:10:56 2014 InstallationDate: Installed on 2014-03-08 (3 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2014-03-10 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1291362/+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 987060] Re: massive memory leak in unity-panel-service and hud-service when invoking the hud on Firefox profiles with large amounts of bookmarks LTS 12.04 14.04
** Summary changed: - massive memory leak in unity-panel-service and hud-service when invoking the hud on Firefox profiles with large amounts of bookmarks + massive memory leak in unity-panel-service and hud-service when invoking the hud on Firefox profiles with large amounts of bookmarks LTS 12.04 14.04 -- 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/987060 Title: massive memory leak in unity-panel-service and hud-service when invoking the hud on Firefox profiles with large amounts of bookmarks LTS 12.04 14.04 Status in The Application Menu: Confirmed Status in Unity: Won't Fix Status in “unity” package in Ubuntu: Confirmed Bug description: unity-panel-service and hud-service quickly racks up memory and CPU usage until I kill it when invoking the HUD on Firefox. It's taking anywhere from a few minutes to half an hour, but it sometimes makes the system completely unusable. 1. run Firefox 12.0 in the foreground 2. hit Alt to bring up HUD 3. type any text 4. select one proposal from HUD 5. wait for unity-panel-service and hud-service to fill up the remaining RAM and swap space. This is due to a high number of bookmarks in a user profile (hundreds). To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-appmenu/+bug/987060/+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 1246812] Re: Can open Evolution in greeter mode
** Changed in: indicator-datetime (Ubuntu Saucy) Assignee: (unassigned) = Marc Deslauriers (mdeslaur) -- 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/1246812 Title: Can open Evolution in greeter mode Status in The Date and Time Indicator: Fix Released Status in “indicator-datetime” package in Ubuntu: Fix Released Status in “indicator-datetime” source package in Saucy: Triaged Status in “indicator-datetime” source package in Trusty: Fix Released Bug description: You can open evolution from the greeter. To reproduce: 1. Boot to Unity Greeter 2. Click date in the datetime indicator Expected result: Nothing happens Observed result: Evolution first run dialog opens To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-datetime/+bug/1246812/+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 1283979] Re: moving windows causes the top bar and the launcher bar to flicker
Silviu, the workaround does stop the flickering, however it introduces a different issue. After opening the unity launcher and closing it dragging any window at the top of the screen near the launcher causes bad tearing/glitching. Ubuntu/Unity 14.04 is pretty much unusable right now on a nvidia 770 and 760 as the opensource drivers do not perform well with these video cards. -- 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/1283979 Title: moving windows causes the top bar and the launcher bar to flicker Status in “unity” package in Ubuntu: Confirmed Bug description: As the title says, when I grab a window and move it around the top bar and the launcher disappear and then re-appear. Unity does not crash. During the move these elements flicker on and off. It looks more like a graphical glitch. This seems to have started after I got the packages that introduced the anti-aliased window corners. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.1.2+14.04.20140220-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-11.31-generic 3.13.3 Uname: Linux 3.13.0-11-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 331.38 Wed Jan 8 19:32:30 PST 2014 GCC version: gcc version 4.8.2 (Ubuntu 4.8.2-16ubuntu1) .tmp.unity.support.test.0: ApportVersion: 2.13.2-0ubuntu5 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: Mon Feb 24 09:49:18 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu GraphicsCard: NVIDIA Corporation GK106 [GeForce GTX 660] [10de:11c0] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:843b] InstallationDate: Installed on 2014-02-13 (10 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140111) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-11-generic root=UUID=c59b4ac8-ab41-40df-aa23-ee39891ed79c ro quiet splash SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/27/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1104 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8P67 LE 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.:bvr1104:bd10/27/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8P67LE: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.11+14.04.20140218-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~rc1-1ubuntu4 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0~rc1-1ubuntu4 version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A version.xserver-xorg-core: xserver-xorg-core 2:1.15.0-1ubuntu6 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-1ubuntu2 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: Mon Feb 24 09:44:57 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.0-1ubuntu6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1283979/+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 1290535] Re: [FFE] Webapps support for the new Oxide container
** Changed in: unity-webapps-qml Status: New = Fix Released ** Changed in: libunity-webapps (Ubuntu) Status: New = Fix Released ** Changed in: libunity-webapps Status: New = Fix Released -- 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/1290535 Title: [FFE] Webapps support for the new Oxide container Status in WebApps: libunity: Fix Released Status in Unity WebApps QML component: Fix Released Status in “libunity-webapps” package in Ubuntu: Fix Released Status in “oxide-qt” package in Ubuntu: New Status in “unity-webapps-qml” package in Ubuntu: Fix Released Status in “webbrowser-app” package in Ubuntu: New Bug description: This is a feature freeze exception request to integrate the following feature in the upcoming Ubuntu 14.04 release. The overall web application support in Ubuntu currently relies on various components and a web container(s) in particular. So far we have been using Firefox and Chromium, by way of browser extensions, to detect, host and integrate web applications in Ubuntu. On mobile devices however, we have already switched to using our own webapp container, based on webbrowser-app. The integration itself has been present as an option since 13.10. However we have been using the QtWebkit engine so far. This request is to also enable and use our webapp-container by defaullt, with the Oxide engine, on the desktop edition. The change impacts a set of packages linked to this bug report. NOTE: This request is not complete and serves to let the release team know of the impact and scope of changes, while the individual MPs with fixes are being consolidated. It will be updated at the beginning of next week when the landing silo is ready for a potential landing. To manage notifications about this bug go to: https://bugs.launchpad.net/libunity-webapps/+bug/1290535/+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 1313885] Re: lock screen bypass
reboot did not fix it. -- 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/1313885 Title: lock screen bypass Status in Unity: In Progress Status in “unity” package in Ubuntu: In Progress Status in “unity” source package in Trusty: Fix Released Status in “unity” source package in Utopic: In Progress Bug description: I found a bug allowing a user to bypass the new lock screen of Ubuntu 14.04 1 - When the screen is locked just right click multiple times on the indicator bar (for example on the battery indicator), then shortcuts are available. 2 - Press ALT+F2 3 - you can execute the command you whant on behalf of the logged user. Here is a video demonstrating this bug : http://www.youtube.com/watch?v=d4UUB0sI5Fc lsb_release -rd Description: Ubuntu 14.04 LTS Release: 14.04 Ubuntu version updated the 04/28/2014 apt-cache policy unity 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://fr.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1313885/+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 1313885] Re: lock screen bypass
I can still bypass the logscreen by rightclicking the indicators. In order to reproduce: Open a Terminal Press CTRL+ALT+L to lock the screen right click the indicators some times type and you will enter into the terminal not the password field The easiest way to reproduce this is to play some music with mplayer in the terminal. If you can stop the music, skip a song etc. with your keys press CTRL+c to quit mplayer. Now you can type whatever you want and it will be executed. This probably affects other Programs. I can even switch the terminal with the default shortcuts. I guess i could also start one with CTRL+ALT+T but i need to confirm that. I just installed the fix above. Have not rebooted though. So that might fix it. -- 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/1313885 Title: lock screen bypass Status in Unity: In Progress Status in “unity” package in Ubuntu: In Progress Status in “unity” source package in Trusty: Fix Released Status in “unity” source package in Utopic: In Progress Bug description: I found a bug allowing a user to bypass the new lock screen of Ubuntu 14.04 1 - When the screen is locked just right click multiple times on the indicator bar (for example on the battery indicator), then shortcuts are available. 2 - Press ALT+F2 3 - you can execute the command you whant on behalf of the logged user. Here is a video demonstrating this bug : http://www.youtube.com/watch?v=d4UUB0sI5Fc lsb_release -rd Description: Ubuntu 14.04 LTS Release: 14.04 Ubuntu version updated the 04/28/2014 apt-cache policy unity 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://fr.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1313885/+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 1313885] Re: lock screen bypass
Confirmed that CTRL+ALT+T for a new terminal works. -- 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/1313885 Title: lock screen bypass Status in Unity: In Progress Status in “unity” package in Ubuntu: In Progress Status in “unity” source package in Trusty: Fix Released Status in “unity” source package in Utopic: In Progress Bug description: I found a bug allowing a user to bypass the new lock screen of Ubuntu 14.04 1 - When the screen is locked just right click multiple times on the indicator bar (for example on the battery indicator), then shortcuts are available. 2 - Press ALT+F2 3 - you can execute the command you whant on behalf of the logged user. Here is a video demonstrating this bug : http://www.youtube.com/watch?v=d4UUB0sI5Fc lsb_release -rd Description: Ubuntu 14.04 LTS Release: 14.04 Ubuntu version updated the 04/28/2014 apt-cache policy unity 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://fr.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1313885/+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 1313885] Re: lock screen bypass
@azul: please file a new bug, that is likely a different issue. -- 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/1313885 Title: lock screen bypass Status in Unity: In Progress Status in “unity” package in Ubuntu: In Progress Status in “unity” source package in Trusty: Fix Released Status in “unity” source package in Utopic: In Progress Bug description: I found a bug allowing a user to bypass the new lock screen of Ubuntu 14.04 1 - When the screen is locked just right click multiple times on the indicator bar (for example on the battery indicator), then shortcuts are available. 2 - Press ALT+F2 3 - you can execute the command you whant on behalf of the logged user. Here is a video demonstrating this bug : http://www.youtube.com/watch?v=d4UUB0sI5Fc lsb_release -rd Description: Ubuntu 14.04 LTS Release: 14.04 Ubuntu version updated the 04/28/2014 apt-cache policy unity 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://fr.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1313885/+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 1301206] Re: [regression] Black frame around windows and buttons censored
I have the same issue with GeForce 9800M GTS/PCIe/SSE2 using NVIDIA binary driver - version 331.38 from nvidia-331 (proprietary,tested) An alternate way of getting rid of the black bars is to go to a console (e.g. Ctrl + Alt +F1) and come back (i.e. Ctrl + Alt + F7) -- 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/1301206 Title: [regression] Black frame around windows and buttons censored Status in “unity” package in Ubuntu: Confirmed Bug description: After suspend, I had a rather enjoyable bug today. Windows are framed in black, and the window buttons are censored out. Pictures speak more than a thousand words, so please check the screenshot. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.1.2+14.04.20140328.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-20.42-generic 3.13.7 Uname: Linux 3.13.0-20-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 331.38 Wed Jan 8 19:32:30 PST 2014 GCC version: gcc version 4.8.2 (Ubuntu 4.8.2-17ubuntu2) .tmp.unity.support.test.0: ApportVersion: 2.14-0ubuntu1 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: Wed Apr 2 09:22:18 2014 DistUpgraded: 2014-03-14 11:39:48,168 DEBUG enabling apt cron job DistroCodename: trusty DistroVariant: ubuntu GraphicsCard: NVIDIA Corporation GF108GLM [Quadro 1000M] [10de:0dfa] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:1631] InstallationDate: Installed on 2013-11-22 (130 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) MachineType: Hewlett-Packard HP EliteBook 8560w ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-20-generic root=UUID=0668e908-5441-4ad5-ae8f-9eb19d0b27a6 ro quiet splash SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2014-03-14 (18 days ago) dmi.bios.date: 06/11/2012 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68SVD Ver. F.27 dmi.board.name: 1631 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 01.3B dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68SVDVer.F.27:bd06/11/2012:svnHewlett-Packard:pnHPEliteBook8560w:pvrA0001D02:rvnHewlett-Packard:rn1631:rvrKBCVersion01.3B:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP EliteBook 8560w dmi.product.version: A0001D02 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.11+14.04.20140328-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-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-1ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A version.xserver-xorg-core: xserver-xorg-core 2:1.15.0-1ubuntu7 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 1 18:09:13 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.0-1ubuntu7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1301206/+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
When I add suid root to unix_chkpwd binary: chmod u+s /sbin/unix_chkpwd then everything works as expected: both lightdm and unity lockscreen are accepting my password. 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. When unix_chkpwd (both suid root and not) is called by lightdm, then it always works good. -- 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” 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 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
[Dx-packages] [Bug 1313877] Re: Launcher icons randomly change color
I can now reproduce the bug consistently: - Restart compiz (compiz --replace): Icon backgrounds are now white - Switch to a different window using Alt-Tab switcher: Icon backgrounds are now green-yellow -- 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/1313877 Title: Launcher icons randomly change color Status in “unity” package in Ubuntu: New Bug description: There are 2 applications in my Launcher (Smuxi and Rhythmbox, from official repositories) that randomly change their background color every few hours, or sometimes every few minutes (if I had to guess). There are two different states for these icons, of which I have attached screenshots. The background is either green-yellow (which I believe is the correct color), or plain white. This never happened with any other icons in my launcher. Please fix, it's driving me nuts :( I'm guessing that either the background algorithm is non-deterministic for some reason, or you have an uninitialized variable somewhere? ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140416-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.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] CurrentDesktop: Unity Date: Mon Apr 28 21:03:06 2014 InstallationDate: Installed on 2014-04-25 (3 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1313877/+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 1314294] [NEW] You can get access to Terminal from lock screen by bypassing it with right click on indicators
Public bug reported: As the title says you can bypass lock screen by right clicking on indicators several times and if you had Terminal window opened and focused you can issue commands. How to reproduce: 1. Open Terminal and play some music with mplayer 2. Lock the screen using one of the shortcuts (Super+L or Ctrl+Alt+L) 3. Right click a couple times on keyboard indicator 4. Now you can use Ctrl+C shortcut to stop your mplayer playing music in Terminal and issue any command you want. You can also open another Terminal window. I had no problem to start this way synaptic with synaptic-pkexec command and then typing my password. This all went to Unity under lock screen. ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: lockscreen ** Tags added: lockscreen -- 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/1314294 Title: You can get access to Terminal from lock screen by bypassing it with right click on indicators Status in “unity” package in Ubuntu: New Bug description: As the title says you can bypass lock screen by right clicking on indicators several times and if you had Terminal window opened and focused you can issue commands. How to reproduce: 1. Open Terminal and play some music with mplayer 2. Lock the screen using one of the shortcuts (Super+L or Ctrl+Alt+L) 3. Right click a couple times on keyboard indicator 4. Now you can use Ctrl+C shortcut to stop your mplayer playing music in Terminal and issue any command you want. You can also open another Terminal window. I had no problem to start this way synaptic with synaptic-pkexec command and then typing my password. This all went to Unity under lock screen. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1314294/+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 1313885] Re: lock screen bypass
@azul and @Marc I reported a new bug for the problem discovered by azul. https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1314294 -- 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/1313885 Title: lock screen bypass Status in Unity: In Progress Status in “unity” package in Ubuntu: In Progress Status in “unity” source package in Trusty: Fix Released Status in “unity” source package in Utopic: In Progress Bug description: I found a bug allowing a user to bypass the new lock screen of Ubuntu 14.04 1 - When the screen is locked just right click multiple times on the indicator bar (for example on the battery indicator), then shortcuts are available. 2 - Press ALT+F2 3 - you can execute the command you whant on behalf of the logged user. Here is a video demonstrating this bug : http://www.youtube.com/watch?v=d4UUB0sI5Fc lsb_release -rd Description: Ubuntu 14.04 LTS Release: 14.04 Ubuntu version updated the 04/28/2014 apt-cache policy unity 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://fr.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1313885/+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 1314247] Re: lock screen bypass with ctrl+alt+t
** Information type changed from Private Security to Public Security -- 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/1314247 Title: lock screen bypass with ctrl+alt+t Status in Unity: New Status in “unity” package in Ubuntu: Confirmed Status in “unity” source package in Trusty: Confirmed Status in “unity” source package in Utopic: Confirmed Bug description: I can still bypass the logscreen by rightclicking the indicators some times and then pressing CTRL+ALT+t. I lock the screen with CTRL+ALT+L. Then i rightclick on the indicators ( volume, calendar, shutdown) a few times. I have not yet figured out if one of them is the cause... But pressing CTRL+ALT+T shortly after some of those events will open a terminal that i can type into and that will execute commands. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1314247/+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 1314247] Re: lock screen bypass with ctrl+alt+t
Yes, we've managed to reproduce this, and are working on a fix. Thanks. ** Also affects: unity (Ubuntu Utopic) Importance: Undecided Status: Confirmed ** Also affects: unity (Ubuntu Trusty) Importance: Undecided Status: New ** Changed in: unity (Ubuntu Trusty) Status: New = Confirmed ** Changed in: unity (Ubuntu Trusty) Importance: Undecided = Critical ** Changed in: unity (Ubuntu Utopic) Importance: Undecided = Critical ** Changed in: unity (Ubuntu Trusty) Assignee: (unassigned) = Marco Trevisan (Treviño) (3v1n0) ** Also affects: unity 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/1314247 Title: lock screen bypass with ctrl+alt+t Status in Unity: New Status in “unity” package in Ubuntu: Confirmed Status in “unity” source package in Trusty: Confirmed Status in “unity” source package in Utopic: Confirmed Bug description: I can still bypass the logscreen by rightclicking the indicators some times and then pressing CTRL+ALT+t. I lock the screen with CTRL+ALT+L. Then i rightclick on the indicators ( volume, calendar, shutdown) a few times. I have not yet figured out if one of them is the cause... But pressing CTRL+ALT+T shortly after some of those events will open a terminal that i can type into and that will execute commands. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1314247/+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 1314294] Re: You can get access to Terminal from lock screen by bypassing it with right click on indicators
*** This bug is a duplicate of bug 1314247 *** https://bugs.launchpad.net/bugs/1314247 ** This bug has been marked a duplicate of bug 1314247 lock screen bypass with ctrl+alt+t -- 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/1314294 Title: You can get access to Terminal from lock screen by bypassing it with right click on indicators Status in “unity” package in Ubuntu: New Bug description: As the title says you can bypass lock screen by right clicking on indicators several times and if you had Terminal window opened and focused you can issue commands. How to reproduce: 1. Open Terminal and play some music with mplayer 2. Lock the screen using one of the shortcuts (Super+L or Ctrl+Alt+L) 3. Right click a couple times on keyboard indicator 4. Now you can use Ctrl+C shortcut to stop your mplayer playing music in Terminal and issue any command you want. You can also open another Terminal window. I had no problem to start this way synaptic with synaptic-pkexec command and then typing my password. This all went to Unity under lock screen. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1314294/+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 1314247] Re: lock screen bypass with ctrl+alt+t
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/1314247 Title: lock screen bypass with ctrl+alt+t Status in Unity: New Status in “unity” package in Ubuntu: Confirmed Status in “unity” source package in Trusty: Confirmed Status in “unity” source package in Utopic: Confirmed Bug description: I can still bypass the logscreen by rightclicking the indicators some times and then pressing CTRL+ALT+t. I lock the screen with CTRL+ALT+L. Then i rightclick on the indicators ( volume, calendar, shutdown) a few times. I have not yet figured out if one of them is the cause... But pressing CTRL+ALT+T shortly after some of those events will open a terminal that i can type into and that will execute commands. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1314247/+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 1314248] Re: lock screen bypass with open terminal
*** This bug is a duplicate of bug 1314247 *** https://bugs.launchpad.net/bugs/1314247 ** Information type changed from Private Security to Public Security ** This bug has been marked a duplicate of bug 1314247 lock screen bypass with ctrl+alt+t -- 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/1314248 Title: lock screen bypass with open terminal Status in “unity” package in Ubuntu: New Bug description: In order to reproduce: Open a Terminal Press CTRL+ALT+L to lock the screen right click the indicators some times type and you will enter into the terminal not the password field The easiest way to reproduce this is to play some music with mplayer in the terminal. If you can stop the music, skip a song etc. with your keys press CTRL+c to quit mplayer. Now you can type whatever you want and it will be executed. This probably affects other Programs. I can even switch the terminal with the default shortcuts. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1314248/+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 1314247] Re: lock screen bypass with ctrl+alt+t
** Changed in: unity Status: New = In Progress ** Changed in: unity Assignee: (unassigned) = Marco Trevisan (Treviño) (3v1n0) ** Changed in: unity Importance: Undecided = Critical ** Changed in: unity Milestone: None = 7.2.1 -- 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/1314247 Title: lock screen bypass with ctrl+alt+t Status in Unity: In Progress Status in “unity” package in Ubuntu: Confirmed Status in “unity” source package in Trusty: Confirmed Status in “unity” source package in Utopic: Confirmed Bug description: I can still bypass the logscreen by rightclicking the indicators some times and then pressing CTRL+ALT+t. I lock the screen with CTRL+ALT+L. Then i rightclick on the indicators ( volume, calendar, shutdown) a few times. I have not yet figured out if one of them is the cause... But pressing CTRL+ALT+T shortly after some of those events will open a terminal that i can type into and that will execute commands. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1314247/+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 1314247] Re: lock screen bypass with ctrl+alt+t
** Branch linked: lp:~3v1n0/unity/menus-grab-races-fix -- 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/1314247 Title: lock screen bypass with ctrl+alt+t Status in Unity: In Progress Status in “unity” package in Ubuntu: Confirmed Status in “unity” source package in Trusty: Confirmed Status in “unity” source package in Utopic: Confirmed Bug description: I can still bypass the logscreen by rightclicking the indicators some times and then pressing CTRL+ALT+t. I lock the screen with CTRL+ALT+L. Then i rightclick on the indicators ( volume, calendar, shutdown) a few times. I have not yet figured out if one of them is the cause... But pressing CTRL+ALT+T shortly after some of those events will open a terminal that i can type into and that will execute commands. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1314247/+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 1314247] Re: lock screen bypass with ctrl+alt+t
** Changed in: unity (Ubuntu Trusty) Status: Confirmed = In Progress -- 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/1314247 Title: lock screen bypass with ctrl+alt+t Status in Unity: In Progress Status in “unity” package in Ubuntu: Confirmed Status in “unity” source package in Trusty: In Progress Status in “unity” source package in Utopic: Confirmed Bug description: I can still bypass the logscreen by rightclicking the indicators some times and then pressing CTRL+ALT+t. I lock the screen with CTRL+ALT+L. Then i rightclick on the indicators ( volume, calendar, shutdown) a few times. I have not yet figured out if one of them is the cause... But pressing CTRL+ALT+T shortly after some of those events will open a terminal that i can type into and that will execute commands. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1314247/+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 1314294] Re: You can get access to Terminal from lock screen by bypassing it with right click on indicators
*** This bug is a duplicate of bug 1314247 *** https://bugs.launchpad.net/bugs/1314247 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/1314294 Title: You can get access to Terminal from lock screen by bypassing it with right click on indicators Status in “unity” package in Ubuntu: Confirmed Bug description: As the title says you can bypass lock screen by right clicking on indicators several times and if you had Terminal window opened and focused you can issue commands. How to reproduce: 1. Open Terminal and play some music with mplayer 2. Lock the screen using one of the shortcuts (Super+L or Ctrl+Alt+L) 3. Right click a couple times on keyboard indicator 4. Now you can use Ctrl+C shortcut to stop your mplayer playing music in Terminal and issue any command you want. You can also open another Terminal window. I had no problem to start this way synaptic with synaptic-pkexec command and then typing my password. This all went to Unity under lock screen. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1314294/+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 1296694] Re: No OSD when adjusting brightness and volume
Maybe this is a feature(?) of Gnome3.12. Here is another thread without any clue or solution about that issue: http://ubuntuforums.org/showthread.php?t=2210251 -- 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/1296694 Title: No OSD when adjusting brightness and volume Status in “notification-daemon” package in Ubuntu: Confirmed Bug description: I am using Ubuntu Gnome 14.04 with everything functioning so far, but after (?) installing evolution, the OSD does not show up anymore when I adjust the brightness and volume. Both functions perfectly fine, but the OSD is missing now. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: notification-daemon 0.7.6-1 ProcVersionSignature: Ubuntu 3.13.0-19.39-generic 3.13.6 Uname: Linux 3.13.0-19-generic x86_64 ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Mar 24 13:30:18 2014 InstallationDate: Installed on 2014-03-04 (20 days ago) InstallationMedia: Ubuntu-GNOME 14.04 Trusty Tahr - Alpha amd64 (20140226) SourcePackage: notification-daemon UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/notification-daemon/+bug/1296694/+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 732653] Re: Menus are hidden by default
Seriously, i don't understand how one can find auto-hiding of the global menu useful. If you say that this is useful when you move windows, think how many times per hour you move your IDE, browser etc,... and how may times you seek an entry in the menu. And finally, the global menu is similar to the one in Apple's OS X. Does it auto-hide? No. And ... I haven't heard of many people complaining about this. -- 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/732653 Title: Menus are hidden by default Status in Ayatana Design: Confirmed Status in Unity: Confirmed Status in “unity” package in Ubuntu: Triaged Status in “unity-2d” package in Ubuntu: Triaged Bug description: Ubuntu 11.04, Ubuntu 11.10, Ubuntu 12.04 1. Log in to Unity, and try to connect to a server: File Connect to Server. 2. Launch Firefox, and try to select an item from the Bookmarks menu. What happens: 1. The File menu, and the rest of Nautilus's menus, are hidden by default. - Unless you mouse over it, the menu bar is blank. - When you mouse over it, the menus appear. 2. The Bookmarks menu, and the rest of Firefox's menus, are hidden by default. - Unless you mouse over it, the menu bar contains only the text Firefox Web Browser, which isn't useful at all (especially, but not only, since the real name of the application -- Mozilla Firefox -- is already present in the window title bar). - When you mouse over it, the menus appear, partly but not completely replacing the previous text: Firefox W File Edit View…. What should happen: Menus should be visible by default, so that you can know that they exist without scrubbing the screen, and so that you can see where a menu is each time you aim for it. The current behavior has led some people (including, this week, one of my design colleagues) to conclude that Ubuntu applications don't have menus when they do. For example http://www.techrepublic.com/blog/opensource/gnome-shell-vs-ubuntu- unity-which-desktop-wins/2291: One of the most handy menu entries in GNOME (for me at least) is the Connect to Server entry in the Places menu. This allows the user to connect to nearly any type of server quickly and easily. The user can even connect to a Windows Share from here. In Unity - you won’t find that. In fact, you will be hard pressed to find any means to connect to a server in Ubuntu Unity. In bug 720424, Jono Bacon reported that when we did some developer tools usability testing last week and on some other occasions when I have had someone use Unity, I have noticed that some folks don't realize there is a menu there as it is not visible. This was confirmed by usability testing of Ubuntu 11.04, where 2 out of the 10 people who needed to use a menu item could not find the menus at all -- and of the 8 who did find them, 7 did so only when the window was maximized. https://lists.ubuntu.com/archives/ubuntu- desktop/2011-April/002970.html (Usability testing results of Ubuntu 11.10 or 12.04 have never been published, but this part of the design did not change.) Do not confuse this bug with bug 682788, which is about adding an option for visibility. Adding any options would not fix this bug, which is about menus being hidden *by default*. - Desired change: Implement the 'Enhanced Menu' project for 12.10. This project will address the issues described in this bug and also issues described in the duplicates of this bus. Note the 'official' bug that tracks the implementation of this project is bug #682788 The following options will be added to 'System Settings/Appearance': --- Menus Location: Global/Local Visibility: Hidden/Always displayed --- More details to follow during the 12.10 cycle... ;-) To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/732653/+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 1308317] Re: applications in full-screen do not align properly after minimization
** Description changed: This is a problem with mouse-clicking sections of the firefox window that are unresponsive. I'll try to describe the problem. Firefox is open and set to fullscreen/maximize. You press the minimize button to send Firefox to the launcher. After opening firefox, by clicking on the launcher icon, firefox returns to fullscreen/maximize and appears normal. However, the tabs at the top are unclickable. The mouse button is an I-beam - or text-editing cursor - instead of a pointer when hovering over the tabs. Clicking changes the position of the I-beam in the text url below. This happens without regard to which programs are open, or whether or not anything else is open. This happens 100% of the time. It seems as though the firefox window is adjusting to maximize and leave room for the menubar at the top, but the GUI does not anticipate the menu bar. There is about a 10 pixel discrepancy between where the mouse points, and where it registers. This also occurs with browser, Chromium. + + This problem does not occur when switching between windows with + maximized browsers, only when a browser opened from launcher after being + minimized. This video should help shed light on the problem: http://tinypic.com/r/2jfcepi/8 I'm running Ubuntu 14.04 beta. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu2 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: Tue Apr 15 22:01:26 2014 DistUpgraded: 2014-04-04 13:01:59,967 DEBUG enabling apt cron job DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:100d] InstallationDate: Installed on 2014-03-02 (45 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) MachineType: ASUSTeK COMPUTER INC. K46CA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic.efi.signed root=UUID=b5739d9f-9c22-4526-8ff5-d851de39247a ro quiet splash vt.handoff=7 SourcePackage: xserver-xorg-video-intel UpgradeStatus: Upgraded to trusty on 2014-04-04 (11 days ago) dmi.bios.date: 10/16/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: K46CA.309 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: K46CA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrK46CA.309:bd10/16/2012:svnASUSTeKCOMPUTERINC.:pnK46CA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnK46CA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: K46CA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. 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.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu1 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 15 11:10:07 2014 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 12348 vendor AUO xserver.version: 2:1.15.1-0ubuntu1 -- 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/1308317 Title: applications in full-screen do not align properly after minimization Status in “unity” package in Ubuntu: Confirmed Bug description: This is a problem with mouse-clicking sections of the firefox window that are unresponsive. I'll try to describe the problem. Firefox is open and set to fullscreen/maximize. You press the minimize button to send Firefox to the launcher. After opening firefox, by clicking on the launcher icon, firefox returns to
[Dx-packages] [Bug 1112061] Re: unity forgets focus-follows-mouse setting across update and reboot
Same behavior in Trusty 14.04 -- 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/1112061 Title: unity forgets focus-follows-mouse setting across update and reboot Status in “gnome-settings-daemon” package in Ubuntu: Confirmed Status in “unity” package in Ubuntu: Confirmed Bug description: I had gone roughly two weeks without rebooting my 12.10 installation. After applying updates that included a new kernel today, I rebooted to finish the updates. Unity forgot my focus-follows-mouse setting across the updates and reboot. Thanks ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: unity 6.12.0-0ubuntu0.2 ProcVersionSignature: Ubuntu 3.5.0-23.35-generic 3.5.7.2 Uname: Linux 3.5.0-23-generic x86_64 ApportVersion: 2.6.1-0ubuntu10 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] Date: Thu Jan 31 18:57:02 2013 InstallationDate: Installed on 2012-10-18 (105 days ago) InstallationMedia: Ubuntu 12.04.1 LTS Precise Pangolin - Release amd64 (20120823.1) MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: unity UpgradeStatus: Upgraded to quantal on 2013-01-20 (12 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1112061/+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 815996] Re: Desktop occasionally freezes/locks up when switching workspaces
I am also having the problem with 14.04 and it happens regularly. I have a newer AMD Cpu (R9 270x) Problem happens very quickly when watching video using pipelight. I'll test out the Windows Key+Esc. Such a work around would be very helpful until the bug is fixed. -- 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/815996 Title: Desktop occasionally freezes/locks up when switching workspaces Status in Compiz: Confirmed Status in Compiz Main Plugins: Confirmed Status in Compiz Desktop Wall Plugin: Confirmed Status in “compiz-plugins-main” package in Ubuntu: Confirmed Bug description: I'm assuming the issue is related to Compiz, but I'm not 100% sure. When I'm switching workspaces, it occasionally locks up (becoming more frequent). Most of the time, I'm going from the current one down (Ctrl+Alt+Down Arrow), and it freezes mid slide. Typically, I'm able to correct things by backing out to a terminal then returning (Ctrl+Alt+F1, pause, Alt+F7), but sometimes when I return the dual screen setup acts as one large screen (windows are stretched to the full width of both screens) and many of the windows collect on the first workspace. Ubuntu 11.04 (Classic) All packages up-to-date. If there are any logs/etc that would be helpful, let me know. --- Architecture: amd64 CompizPlugins: [core,bailer,detection,composite,opengl,decor,grid,imgpng,snap,compiztoolbox,resize,place,regex,move,gnomecompat,animation,vpswitch,mousepoll,workarounds,session,expo,wall,ezoom,fade,switcher,scale] DistroCodename: natty DistroRelease: Ubuntu 11.04 DistroVariant: ubuntu InstallationMedia: Ubuntu 10.04 LTS Lucid Lynx - Release amd64 (20100429) InstallationMedia_: Ubuntu 10.04 LTS Lucid Lynx - Release amd64 (20100429) NonfreeKernelModules: nvidia Package: compiz 1:0.9.4+bzr20110606-0ubuntu1~natty2 PackageArchitecture: all ProcEnviron: LANGUAGE=en_US:en PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.38-10.46-generic 2.6.38.7 ProcVersionSignature_: Ubuntu 2.6.38-10.46-generic 2.6.38.7 Tags: natty natty ubuntu Uname: Linux 2.6.38-10-generic x86_64 UnreportableReason: Please work this issue through technical support channels first. UpgradeStatus: Upgraded to natty on 2011-05-02 (84 days ago) UserGroups: adm admin audio cdrom dialout dip fuse lpadmin netdev plugdev sambashare To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/815996/+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 1307048] Re: calendar icon wrong colour (compared to clock) for upcoming appointments
** Branch linked: lp:~ubuntu-branches/ubuntu/utopic/unity8/utopic- proposed -- 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/1307048 Title: calendar icon wrong colour (compared to clock) for upcoming appointments Status in “indicator-datetime” package in Ubuntu: Invalid Status in “unity8” package in Ubuntu: In Progress Bug description: Have appointments sync via calendar, note that pulling down indicator reveals icon which is black-on-grey whereas clock items appear white-on-grey. Calendar icons are hard to see compared to clock items. See photo. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1307048/+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
Make sure your gsettings get org.gnome.desktop.screensaver lock-enabled is false... We honour that setting, and unless some other service will require a Lock, this should never happen in idle. -- 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: New Status in “unity” package in Ubuntu: New 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 :
[Dx-packages] [Bug 1303462] Re: [Regression] Window titlebars placed behind panel
This bug also affects Image Viewer. When pictures are opened and then the page maximised the maximise, minimise, close buttons slip up under the top panel and cannot be accessed. -- 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/1303462 Title: [Regression] Window titlebars placed behind panel Status in Compiz: Triaged Status in Unity: Invalid Status in “unity” package in Ubuntu: Triaged Bug description: Windows with a height of (Display Height - Panel Height) get placed at y=0 (behind the top panel) which means window titlebars are not reachable without alt-moving the window. I assume this happens with windows that want to resize themselves if their height exceeds the display resolution. Reproducable on my 1366x768 screen with LibreOffice and a Qt 5 desktop application I'm working on. TEMPORARY WORKAROUND: Use the Cntrl+SuperKey+Right or Left Arrow Key This will resize your currently focused window to occupy the Right (Left) half of the screen. The Title Bar should now be visible, so you need to drag it and resize it at your prefered position. This will save the new position in place of the previously hidden state. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140403-0ubuntu1 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' CurrentDesktop: Unity Date: Sun Apr 6 21:45:41 2014 InstallationDate: Installed on 2014-04-04 (2 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Daily amd64 (20140404) SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1303462/+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 1098959] Re: 12.10 Bluetooth Battery Indicator Interferes with Bluetooth Mouse Moves
Same problem seen on Ubuntu 14.04 64 bit on a Toshiba Satellite S855-5378 (different machine, same generic bt mouse) with built-in bluetooth. The bt mouse will connect, but status never shows paired. The mouse works maybe 30 seconds while the bt mouse battery is discovered, then mouse stops working when the battery indicator finishes what it is doing. -- 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/1098959 Title: 12.10 Bluetooth Battery Indicator Interferes with Bluetooth Mouse Moves Status in Gnome Powermanager: New Status in “indicator-power” package in Ubuntu: Confirmed Bug description: A fully updated (Jan 11, 2013) Ubuntu 12.10 allows the bluetooth mouse to connect but fails to move the cursor. The bluetooth battery indicator is created and works. If bluetooth is turned on just before mouse connection is attempted (before the battery indicator shows the mouse battery), sometimes there is mouse cursor movement for a fraction of a second. One time, a mouse onnection succeeded, and at that time, the battery indicator for the mouse no longer reported the current battery state (switching batteries of different charges no longer accurately indicated the battery charge). hcidump reports the mouse moves, but the cursor does nothing, nor do clicks. ** The mouse does work if the battery indicator is killed soon after boot before bluetooth is turned on.** Taking a wild guess, the bluetooth battery indicator handler is not re-queueing the mouse moves it sees while looking for the battery info. Additionally, the mouse handler, when it rarely gets a position before the battery handler is not re-queuing the battery messages. Equipment: HP V3000, with Nvidia 6150 running driver version 304.51, root on 8G usb. Bus 002 Device 002: ID 03f0:171d Hewlett-Packard Bluetooth 2.0 Interface [Broadcom BCM2045], Generic Bluetooth mouse Broadcom 4311 wireless running the b43 driver with the firmware supplied from package firmware-b43-installer. xorg.conf file was originally absent, but copying one from my 12.04 installation made no difference. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: indicator-power 12.10.2-0ubuntu1 ProcVersionSignature: Ubuntu 3.5.0-21.32-generic 3.5.7.1 Uname: Linux 3.5.0-21-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.6.1-0ubuntu9 Architecture: i386 Date: Sat Jan 12 12:03:51 2013 MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: indicator-power UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-power/+bug/1098959/+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 1311388] Re: Unity Lock Screen appearance does not respect RTL languages
** Changed in: unity Assignee: (unassigned) = Andrea Azzarone (andyrock) ** Changed in: unity Status: New = Triaged ** Changed in: unity (Ubuntu) Status: New = Confirmed ** Changed in: unity Milestone: None = 7.2.1 -- 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/1311388 Title: Unity Lock Screen appearance does not respect RTL languages Status in Unity: Triaged Status in “unity” package in Ubuntu: Confirmed Bug description: When logging into Ubuntu using an RTL system language like Hebrew or Arabic, the password box appears on the right hand side of the screen, which is correct. However if you go away from the computer and the computer gets locked; or if you put the computer on standby and then resume it, the unlock screen uses the standard LTR layout with the password box on the left hand side instead of moving the password box to the right hand side to match the login screen. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity-greeter 14.04.9-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic i686 ApportVersion: 2.14.1-0ubuntu3 Architecture: i386 CurrentDesktop: Unity Date: Wed Apr 23 00:29:27 2014 SourcePackage: unity-greeter UpgradeStatus: Upgraded to trusty on 2014-04-19 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1311388/+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 1303462] Re: [Regression] Window titlebars placed behind panel
the best workaround I have come up with is: - install compizconfig-settings-manager from the software center - run compizconfig-settings-manager - go to place windows - go to fix windows placement tab - create new (windows with fixed positions) - window postion: class= the program that is loading in the wrong position - X=65 - Y=55 then close repeat as needed for all program causing problems and adjust X Y based on you launcher and panel scaling. some time you have to restart for the setting to take effect. hope this helps cheers! Whitaar -- 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/1303462 Title: [Regression] Window titlebars placed behind panel Status in Compiz: Triaged Status in Unity: Invalid Status in “unity” package in Ubuntu: Triaged Bug description: Windows with a height of (Display Height - Panel Height) get placed at y=0 (behind the top panel) which means window titlebars are not reachable without alt-moving the window. I assume this happens with windows that want to resize themselves if their height exceeds the display resolution. Reproducable on my 1366x768 screen with LibreOffice and a Qt 5 desktop application I'm working on. TEMPORARY WORKAROUND: Use the Cntrl+SuperKey+Right or Left Arrow Key This will resize your currently focused window to occupy the Right (Left) half of the screen. The Title Bar should now be visible, so you need to drag it and resize it at your prefered position. This will save the new position in place of the previously hidden state. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140403-0ubuntu1 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' CurrentDesktop: Unity Date: Sun Apr 6 21:45:41 2014 InstallationDate: Installed on 2014-04-04 (2 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Daily amd64 (20140404) SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1303462/+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 1303572] [NEW] Korean Characters are not displayed on Unity, but Question Marks are.
You have been subscribed to a public bug: On Ubuntu 14.04 beta2, as well as the finally released version Ubuntu 14.04, Korean letters are not showed for program(directories, files, etc) titles on Unity(Dash). Please see the attached picture. ** Affects: unity (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: korean trusty -- Korean Characters are not displayed on Unity, but Question Marks are. https://bugs.launchpad.net/bugs/1303572 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 1303572] Re: Korean Characters are not displayed on Unity, but Question Marks are.
** Package changed: ubuntu = unity (Ubuntu) -- 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/1303572 Title: Korean Characters are not displayed on Unity, but Question Marks are. Status in “unity” package in Ubuntu: Confirmed Bug description: On Ubuntu 14.04 beta2, as well as the finally released version Ubuntu 14.04, Korean letters are not showed for program(directories, files, etc) titles on Unity(Dash). Please see the attached picture. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1303572/+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