[Dx-packages] [Bug 1293638] Re: quick alt+letter sequence interpretted as open HUD.
*** This bug is a duplicate of bug 1292623 *** https://bugs.launchpad.net/bugs/1292623 ** This bug has been marked a duplicate of bug 1292623 Alt-F pops up the HUD -- 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/1293638 Title: quick alt+letter sequence interpretted as open HUD. Status in “unity” package in Ubuntu: New Bug description: When I press alt + a letter (or any other letter) in quick succession the HUD opens (and the key combination is sent to the focused application). ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.1.2+14.04.20140313-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6 Uname: Linux 3.13.0-17-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Mon Mar 17 16:39:02 2014 InstallationDate: Installed on 2014-01-26 (49 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140124) 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/1293638/+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 1293410] Re: Lockscreen kicks in after resuming and unlocking
likely a duplicate of bug #1291088 ** 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/1293410 Title: Lockscreen kicks in after resuming and unlocking Status in “unity” package in Ubuntu: New Bug description: Every time I resume my laptop with latest unity I get presented with the new lockscreen, so I enter the password and unlock the screen, but a few seconds after that it locks again and I have to type the password again and unlock. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.1.2+14.04.20140313-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 NonfreeKernelModules: nvidia wl ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Mon Mar 17 09:09:41 2014 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/1293410/+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 1292935] Re: New Lockscreen inhibits putting the screens to sleep.
** 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/1292935 Title: New Lockscreen inhibits putting the screens to sleep. Status in “unity” package in Ubuntu: Triaged Bug description: Ok, so since the new lockscreen landed in Trusty, I've been observing inconsistent behavior with the power settings on my screens. I managed to do a little bit of troubleshooting and this is what I discovered: My power settings are set such that the screens turn off prior to the screen locking (5 minutes and 10 minutes respectively but I don't think the times are relevant). If I walk away from my computer and leave it unlocked, the screens will successfully power down, and the next time I come back then the lock screen will appear when I wake up the screens. This part is good. If I type Ctrl-Alt-L, the screen locks, but it keeps the screens on, even for extended periods of time (eg, overnight. On several occaisions I've locked my screen, gone to bed, and then woken up to discover both my screens powered on at maximum brightness just displaying that sexy lockscreen). Oddly, when I unlock the screens in this state, what will happen is that just a few seconds after unlocking, some kind of timer will trigger and say oh yeah, time to power down the screens! so even though I *just unlocked my desktop*, both screens power down for about 5 seconds and then turn back on, and *then* they fade to black and snap back to maximum brightness. It's very discordant. So, the workaround for me is don't lock the screen, and that's probably fine at home, but obviously that's not a viable solution in any kind of security context, eg in an office. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.1.2+14.04.20140313-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: Sat Mar 15 10:56:14 2014 InstallationDate: Installed on 2013-12-06 (99 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2013-12-06 (99 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1292935/+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 1292623] Re: Alt-F pops up the HUD
** Changed in: unity (Ubuntu) Importance: Undecided = High ** Also affects: unity Importance: Undecided Status: New ** Changed in: unity Importance: Undecided = High ** Changed in: unity Milestone: None = 7.2.0 -- 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/1292623 Title: Alt-F pops up the HUD Status in Unity: New Status in “unity” package in Ubuntu: Confirmed Bug description: When releasing both Alt and F quickly, and Alt slightly before I believe, this annoying 'Pelase type your command' thing pops up. (Even though my app 'did' get a proper Alt-F and popped up its own menu) ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.1.2+14.04.20140313-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6 Uname: Linux 3.13.0-17-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Fri Mar 14 13:04:47 2014 InstallationDate: Installed on 2013-08-06 (220 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha amd64 (20130805) SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2014-02-20 (22 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1292623/+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 1292067] Re: Locking screen animation shows launcher being revealed incorrectly
** Tags added: lockscreen ** 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/1292067 Title: Locking screen animation shows launcher being revealed incorrectly Status in Unity: New Status in “unity” package in Ubuntu: New Bug description: I have the Unity launcher set to autohide. When I lock the screen using the Super+L shortcut, I notice that the launcher is shown appearing when the fade in animation is happening. This doesn't happen while locking the screen using the session indicator menu. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.1.2+14.04.20140312-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: Thu Mar 13 16:38:33 2014 InstallationDate: Installed on 2013-09-18 (176 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha amd64 (20130802) SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2014-02-27 (14 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1292067/+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 1292451] Re: screensaver re-locks itself after unlocking if the configured screen-off timer goes off while screen is locked
** Also affects: unity Importance: Undecided Status: New ** Tags added: lockscreen ** Changed in: unity Milestone: None = 7.2.0 ** Changed in: unity Importance: Undecided = High -- 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/1292451 Title: screensaver re-locks itself after unlocking if the configured screen- off timer goes off while screen is locked Status in Unity: New Status in “gnome-screensaver” package in Ubuntu: New Status in “unity” package in Ubuntu: New Bug description: Steps to reproduce: 1. Set screen-off timeout to 1 minute 2. Configure screen to lock immediately when screen goes off. 3. Lock screen manually (Ctrl+Alt+L) 4. Wait for 1 minute 5. Notice that screen doesn't turn off 6. Unlock screen 7. Wait a couple of seconds (~10 or so) 8. Notice that screen re-locks itself. 9. Repeat steps 6-7 and notice that the screen doesn't re-lock itself this time. There are two bugs described here: 1. Screen does not shut off if the screen is locked manually before the idle timer (see step 5). 2. Screen re-locks itself after unlocking if the idle timer goes off while the screen is locked (see step 7). ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: gnome-screensaver 3.6.1-0ubuntu11 Uname: Linux 3.13.4-hyper1 x86_64 ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Fri Mar 14 18:19:26 2014 GnomeSessionIdleInhibited: No GnomeSessionInhibitors: None GsettingsGnomeSession: org.gnome.desktop.session session-name 'ubuntu' org.gnome.desktop.session idle-delay uint32 300 SourcePackage: gnome-screensaver UpgradeStatus: Upgraded to trusty on 2014-03-03 (10 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1292451/+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 1292647] Re: Esc does not clear the password input field in the unity lock screen
** Changed in: unity (Ubuntu) Importance: Undecided = Low -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1292647 Title: Esc does not clear the password input field in the unity lock screen Status in “unity” package in Ubuntu: New Bug description: When hitting the escape key in the Unity lock screen password prompt, the password prompt is not cleared, whereas it used to be cleared in the old gnome-screensaver, as well as the lightdm login screen. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.1.2+14.04.20140312-0ubuntu1 Uname: Linux 3.13.4-hyper1 x86_64 ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CompizPlugins: [core,composite,opengl,copytex,compiztoolbox,decor,vpswitch,extrawm,text,resize,ring,screenshot,place,commands,put,mousepoll,move,gnomecompat,annotate,blur,clone,widget,regex,imgpng,animation,obs,workarounds,neg,bicubic,resizeinfo,grid,expo,session,wall,showmouse,ezoom,unitymtgrabhandles,fade,scale,scalefilter,showdesktop,scaleaddon,unityshell] CurrentDesktop: Unity Date: Fri Mar 14 22:29:30 2014 SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2014-03-03 (11 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1292647/+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 1292078] Re: New lock screen is shown on ctrl+alt+l rather than blanking the screen
** Tags added: lockscreen ** 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/1292078 Title: New lock screen is shown on ctrl+alt+l rather than blanking the screen Status in Unity: New Status in “unity” package in Ubuntu: New Bug description: On screen lock the screen used to fade to black now instead it displays the unity lock screen. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.1.2+14.04.20140312-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6 Uname: Linux 3.13.0-17-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Thu Mar 13 15:56:06 2014 InstallationDate: Installed on 2014-01-10 (62 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140109) SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1292078/+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 1293646] [NEW] Doesn't list all events for selected day
Public bug reported: Using current trusty: - configure a calendar with some events - click on a day with one of those - check that the events of the day are correctly listed Sometimes events are missing, it seems to be the one which happen earlier in the day that the current time. It would suggest the code is checking starting at the current hour and not at midnight for the selected day ** Affects: indicator-datetime (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-datetime in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1293646 Title: Doesn't list all events for selected day Status in “indicator-datetime” package in Ubuntu: New Bug description: Using current trusty: - configure a calendar with some events - click on a day with one of those - check that the events of the day are correctly listed Sometimes events are missing, it seems to be the one which happen earlier in the day that the current time. It would suggest the code is checking starting at the current hour and not at midnight for the selected day To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1293646/+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 1293646] Re: Doesn't list all events for selected day
** Changed in: indicator-datetime (Ubuntu) Status: New = Triaged ** Changed in: indicator-datetime (Ubuntu) Importance: Undecided = Medium ** Changed in: indicator-datetime (Ubuntu) Assignee: (unassigned) = Charles Kerr (charlesk) -- 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/1293646 Title: Doesn't list all events for selected day Status in “indicator-datetime” package in Ubuntu: Triaged Bug description: Using current trusty: - configure a calendar with some events - click on a day with one of those - check that the events of the day are correctly listed Sometimes events are missing, it seems to be the one which happen earlier in the day that the current time. It would suggest the code is checking starting at the current hour and not at midnight for the selected day To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1293646/+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 1293659] [NEW] Unity locks screen after unlocking
Public bug reported: After locking the computer I wanted to unlock the computer again. Once entering the desktop the screen gets locked without doing anything after several seconds. Unlocking for the second time gives no problem. However, when locking the screen again, the same problem occurs again. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.1.2+14.04.20140313-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6 Uname: Linux 3.13.0-17-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-16ubuntu6) .tmp.unity.support.test.0: ApportVersion: 2.13.3-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: Mon Mar 17 17:26:30 2014 DistUpgraded: 2014-03-14 17:04:08,335 DEBUG enabling apt cron job DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: bbswitch, 0.7, 3.13.0-17-generic, x86_64: installed nvidia-331-updates, 331.38, 3.13.0-17-generic, x86_64: installed virtualbox, 4.3.6, 3.11.0-18-generic, x86_64: installed virtualbox, 4.3.6, 3.13.0-17-generic, x86_64: installed 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-06-15 (275 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) JockeyStatus: kmod:nvidia_304_updates - NVIDIA legacy binary driver - version 304.117 (Proprietary, Disabled, Not in use) kmod:nvidia_331 - NVIDIA binary driver - version 331.38 (Proprietary, Disabled, Not in use) kmod:nvidia_331_updates - nvidia_331_updates (Proprietary, Enabled, Not in use) kmod:nvidia_304 - NVIDIA legacy binary driver - version 304.117 (Proprietary, Disabled, Not in use) MachineType: Hewlett-Packard HP EliteBook 8560w ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-17-generic root=UUID=4e34beb2-745f-4a18-8d61-eff5a31a069d ro quiet splash pcie_aspm=force SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2014-03-14 (3 days ago) dmi.bios.date: 07/25/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68SVD Ver. F.03 dmi.board.name: 1631 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 01.35 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68SVDVer.F.03:bd07/25/2011:svnHewlett-Packard:pnHPEliteBook8560w:pvrA0001D02:rvnHewlett-Packard:rn1631:rvrKBCVersion01.35: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.20140310-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: Mon Mar 17 12:44:06 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 ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 trusty 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/1293659 Title: Unity locks screen after unlocking Status in “unity” package in Ubuntu: New Bug description: After locking the computer I wanted to unlock the computer again. Once entering the desktop the screen gets locked without doing anything after several seconds. Unlocking for the second time gives no problem. However, when locking the screen again, the same problem occurs again. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.1.2+14.04.20140313-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6 Uname: Linux 3.13.0-17-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory:
[Dx-packages] [Bug 1293672] [NEW] [regression] Windows are not drawn when resuming from locked screen
Public bug reported: When unlocking the screen, any window that is restored from a minimized state is not drawn (it is just black). [Steps to reproduce] 1. Open a window 2. Minimize the window 3. Lock the screen 4. Unlock the screen 5. Restore the window [What should happen] * The window content should be drawn as expected. [What happens] * The window is not drawn. See attachment [Workaround] * Any window action will paint the window again, for example re-sizing, minimizing and restoring again, but not moving the window. * Opening the unity dash or HUD also works. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.1.2+14.04.20140313-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6 Uname: Linux 3.13.0-17-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-16ubuntu6) .tmp.unity.support.test.0: ApportVersion: 2.13.3-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: Mon Mar 17 17:18:44 2014 DistUpgraded: 2014-03-14 11:39:48,168 DEBUG enabling apt cron job DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: bbswitch, 0.7, 3.11.0-18-generic, x86_64: installed bbswitch, 0.7, 3.13.0-17-generic, x86_64: installed nvidia-331-updates, 331.38, 3.13.0-17-generic, x86_64: installed 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 (115 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-17-generic root=UUID=0668e908-5441-4ad5-ae8f-9eb19d0b27a6 ro quiet splash SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2014-03-14 (3 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.20140310-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: Mon Mar 17 15:19:40 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 ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 trusty 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/1293672 Title: [regression] Windows are not drawn when resuming from locked screen Status in “unity” package in Ubuntu: New Bug description: When unlocking the screen, any window that is restored from a minimized state is not drawn (it is just black). [Steps to reproduce] 1. Open a window 2. Minimize the window 3. Lock the screen 4. Unlock the screen 5. Restore the window [What should happen] * The window content should be drawn as expected. [What happens] * The window is not drawn. See attachment [Workaround] * Any window action will paint the window again, for example re-sizing, minimizing and restoring again, but not moving the window. * Opening the unity dash or HUD also works. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.1.2+14.04.20140313-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6
[Dx-packages] [Bug 1293677] [NEW] FFE: Export data to accounts service
Public bug reported: To support having a user control of the media player and volume on the greeter data needs to be exported by the sound indicator into the accounts service so that it can be read by the greeter user. This will then be used on the greeter to show the relevant data to the user when that user is selected on the greeter. A user on the Unity7 desktop today should not notice any change from these merges as they'll only be visible on a phone with the Unity 8 greeter. ** Affects: indicator-sound (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-sound in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1293677 Title: FFE: Export data to accounts service Status in “indicator-sound” package in Ubuntu: New Bug description: To support having a user control of the media player and volume on the greeter data needs to be exported by the sound indicator into the accounts service so that it can be read by the greeter user. This will then be used on the greeter to show the relevant data to the user when that user is selected on the greeter. A user on the Unity7 desktop today should not notice any change from these merges as they'll only be visible on a phone with the Unity 8 greeter. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/1293677/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
Re: [Dx-packages] [Bug 1291468] Re: clock applet won't display events for selected date/directs to wrong date on evolution calendar
This bug is now fixed for me! Thanks! On Wed, Mar 12, 2014 at 8:11 PM, Charles Kerr charles.k...@canonical.comwrote: Some of this report is a duplicate of bug #1290171, which is already in progress. However, the Directs to date one day before bug isn't covered in 1290171, and I'm able to reproduce that issue. Short answer: looks like the fix is to convert localtime to GMT before passing it to evolution. Longer answer: indicator-datetime invokes evolution like this: $ evolution calendar:///?startdate=20140325 ...and if I test that manually from the command line, I get the same issue of Evolution popping up a calendar to March 24. However if I pass that in UTC to evolution, it works correctly. I'm in GMT-5, so if I do this: $ evolution calendar:///?startdate=20140325T05Z then it pops up correctly. If I shift it less than 5 hours, it still shows up on March 24: $ evolution calendar:///?startdate=20140325T04Z ** Summary changed: - clock applet won't display events for selected date/directs to wrong date on evolution calendar + double-clicking on a calendar day opens Evolution to the day *before* the double-clicked day -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1291468 Title: double-clicking on a calendar day opens Evolution to the day *before* the double-clicked day Status in indicator-datetime package in Ubuntu: In Progress Bug description: I have Evolution set as my default calendar. In the clock/calendar applet, it displays the 5 next upcoming events on my calendar and an option to add an event. These events are accurate and up to date from today's date. However, if I select another date on the calendar, it will not change to show events from that date. It always displays current upcoming events. Also, if I click on any upcoming event listed, or if I double-click on a date on the calendar, I am directed to the date one day before the date selected. Clicking Add Event opens the Evolution calendar and selects the current date and time. I can begin typing and it will create an event in the selected calendar. Works as expected. 1) Ubuntu 14.04 LTS (beta) 2) a) indicator-datetime 13.10.0+14.04.20140311.1-0ubuntu1 b) Evolution 3.10.4 3) EXPECTED a) Select date on calendar - expected to see upcoming events for that date b) Double-click date on calendar OR click event - expected to be directed to that date or event 4) HAPPENED a) No change/displays upcoming events relative to current date b) Directs to date one day before ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: indicator-datetime 13.10.0+14.04.20140311.1-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 CurrentDesktop: Unity Date: Wed Mar 12 11:29:34 2014 ExecutablePath: /usr/lib/x86_64-linux-gnu/indicator-datetime/indicator-datetime-service InstallationDate: Installed on 2014-03-10 (1 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140310) ProcEnviron: PATH=(custom, no user) LANGUAGE=en_US XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash 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/1291468/+subscriptions -- 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/1291468 Title: double-clicking on a calendar day opens Evolution to the day *before* the double-clicked day Status in “indicator-datetime” package in Ubuntu: In Progress Bug description: I have Evolution set as my default calendar. In the clock/calendar applet, it displays the 5 next upcoming events on my calendar and an option to add an event. These events are accurate and up to date from today's date. However, if I select another date on the calendar, it will not change to show events from that date. It always displays current upcoming events. Also, if I click on any upcoming event listed, or if I double-click on a date on the calendar, I am directed to the date one day before the date selected. Clicking Add Event opens the Evolution calendar and selects the current date and time. I can begin typing and it will create an event in the selected calendar. Works as expected. 1) Ubuntu 14.04 LTS (beta) 2) a) indicator-datetime 13.10.0+14.04.20140311.1-0ubuntu1 b) Evolution 3.10.4 3) EXPECTED a) Select date on calendar - expected to see upcoming events for that date b) Double-click date on
[Dx-packages] [Bug 1287464] Re: Fake decorations on spread flickers the first time they've been selected
** Changed in: unity Status: In Progress = Fix Committed ** Changed in: unity (Ubuntu) Status: In Progress = Fix Released -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1287464 Title: Fake decorations on spread flickers the first time they've been selected Status in Unity: Fix Committed Status in “unity” package in Ubuntu: Fix Released Bug description: Selecting the first time a window in unity spread might cause some flickering of the window decoration To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1287464/+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 1283786] Re: The title of unfocused maximized window remains in panel when it's closed with LIM enabled
** Changed in: unity (Ubuntu) Status: In Progress = Fix Released ** Changed in: unity Status: In Progress = Fix Committed -- 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/1283786 Title: The title of unfocused maximized window remains in panel when it's closed with LIM enabled Status in Unity: Fix Committed Status in “unity” package in Ubuntu: Fix Released Bug description: Steps to reproduce: 0. Have menus to be in window title bars. 1. Open a window that's maximized. 2. Open and focus a window that's unmaximized. 3. Use the controls in panel to close or minimize the maximized window. What happens: The title of the maximized window is still in the top bar. What should happen: The title should disappear. See the attached screenshot for a bogus 'Untitled 1 - LibreOffice Writer' in the panel. 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 .tmp.unity.support.test.0: ApportVersion: 2.13.2-0ubuntu5 Architecture: amd64 CasperVersion: 1.337 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: Sun Feb 23 20:09:04 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:1587] NVIDIA Corporation GF108M [GeForce GT 635M] [10de:0de3] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:1587] LiveMediaBuild: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140223) MachineType: ASUSTeK COMPUTER INC. K56CM ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi file=/cdrom/preseed/username.seed boot=casper quiet splash -- SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/19/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: K56CM.209 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: K56CM 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.:bvrK56CM.209:bd11/19/2012:svnASUSTeKCOMPUTERINC.:pnK56CM:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnK56CM:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: K56CM dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. 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.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: Sun Feb 23 20:00:05 2014 xserver.configfile: default xserver.errors: Failed to load module nvidia (module does not exist, 0) Failed to load module nvidia (module does not exist, 0) NOUVEAU(G0): [XvMC] Failed to initialize extension. xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 17900 vendor AUO xserver.version: 2:1.15.0-1ubuntu6 To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1283786/+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 1283156] Re: menus switch to window title when window is unmaximized
** Changed in: unity Status: In Progress = Fix Committed -- 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/1283156 Title: menus switch to window title when window is unmaximized Status in Unity: Fix Committed Status in “unity” package in Ubuntu: Fix Released Bug description: When running with Application Menu set to In top bar, applications menus switch to the window title bar when a window is unmaximized, until a different window gets focus. Steps to reproduce: 1- Launch gnome-terminal 2- hover mouse on window title bar to make sure there is no menu 3- maximize gnome-terminal 4- unmaximize gnome-terminal 5- hover mouse on window title...notice that the application menus appear in window title bar 6- Click on another window to take focus away from gnome-terminal 7-Click on gnome-terminal again 8- Hover mouse on window title, menu is now gone 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 ApportVersion: 2.13.2-0ubuntu5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Fri Feb 21 12:38:20 2014 InstallationDate: Installed on 2013-11-26 (86 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2014-01-17 (34 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1283156/+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 1287745] Re: Some more Autopilot Panel tests need fixing
** Changed in: unity Status: In Progress = Fix Committed -- 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/1287745 Title: Some more Autopilot Panel tests need fixing Status in Unity: Fix Committed Status in “unity” package in Ubuntu: Fix Released Bug description: In drilling down on some more Autopilot test failures, some Panel tests will fail, either 100% of the time or occasionally. 1. Some Panel tests will fail if the previous test leaves the system with only the Launcher on the primary monitor. 2. test_window_buttons_show_when_holding_show_menu_key can fail due to a race when pressing and releasing the Alt key. This sometimes opens the Hud during the test which is not expected. 3. test_hovering_indicators_on_multiple_monitors fails due to a change in how multi-monitor Panels are handled. The test needs fixed to account for the new behavior. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1287745/+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 1290171] Re: appointments don't change when you click on a calendar date
This bug is now fixed for me! Thanks! -- 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/1290171 Title: appointments don't change when you click on a calendar date Status in “indicator-datetime” package in Ubuntu: In Progress Bug description: In the desktop's Coming Events section, we should update the event/alarm entries based on the date clicked on in the Monthly Calendar section. In indicator-datetime-13.10.0+14.04.20140227.1-0ubuntu1, the events are tied to the current clock time and do not change when you click on another date in the calendar. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1290171/+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 1272168] Re: Whenlogging out Orca does not read the session logout screen.
** Changed in: unity Status: In Progress = Fix Committed -- 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/1272168 Title: Whenlogging out Orca does not read the session logout screen. Status in Unity: Fix Committed Status in “unity” package in Ubuntu: Fix Released Bug description: Using Unity and selecting logout a window appears and Orca only reads out 'session manager'. A flat review using Orca navigational keys reveals the 'Do you want to logout text' But this should be read out automatically with the logout and cancel buttons accessible to the keyboarde with the tab key. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: indicator-session 12.10.5+14.04.20131125-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-3.18-generic 3.13.0-rc8 Uname: Linux 3.13.0-3-generic x86_64 ApportVersion: 2.13.1-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Fri Jan 24 16:22:17 2014 InstallationDate: Installed on 2013-11-14 (70 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20131113) SourcePackage: indicator-session UpgradeStatus: No upgrade log present (probably fresh install) upstart.indicator-session.log: ** (process:9903): WARNING **: /build/buildd/indicator-session-12.10.5+14.04.20131125/src/backend-dbus/actions.c:705 run_outside_app: Failed to execute child process gnome-control-center (No such file or directory) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1272168/+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 1286158] Re: Window spread of only 1 window is off centered
** Changed in: unity Status: In Progress = Fix Committed ** Also affects: unity (Ubuntu) Importance: Undecided Status: New ** Changed in: unity (Ubuntu) Status: New = 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/1286158 Title: Window spread of only 1 window is off centered Status in Unity: Fix Committed Status in “unity” package in Ubuntu: Fix Released Bug description: I noticed when using the window spread, if there is only 1 application in the workspace, that window is off centered in the spread. If there are 2 or more windows in the workspace, the spread places the windows correctly. 1 Window Spread Screenshot: http://i.imgur.com/HDJXZ4L.png 2 Window Spread Screenshot: http://i.imgur.com/y6mfn5q.jpg As a result, the 1 window is overlapping over the top panel. System Information: Unity: 7.1.2+14.04.20140220-0ubuntu1 Compiz: 1:0.9.11+14.04.20140218-0ubuntu1 Ubuntu 14.04 To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1286158/+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 1266464] Re: HUD Super and Alt shortcuts works through locked screen
** Changed in: unity Status: In Progress = Fix Released ** Changed in: unity Status: Fix Released = Fix Committed ** Also affects: unity (Ubuntu) Importance: Undecided Status: New ** Changed in: unity (Ubuntu) Status: New = Fix Released -- You received this bug notification because you are a member of DX Packages, which is subscribed to hud in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1266464 Title: HUD Super and Alt shortcuts works through locked screen Status in Unity: Fix Committed Status in “hud” package in Ubuntu: Invalid Status in “unity” package in Ubuntu: Fix Released Bug description: To reproduce: 1. Lock screen (e.g. using Ctrl+Alt+L or corresponding option in menu). 2. Press Super (or Alt) key. 3. Enter password to unlock desktop. Expected behaviour: nothing on desktop should be changed. Observed behaviour: HUD menu pupped up, as if Alt or Super were pressed on desktop. I mark this bug report as security issue, because not sure is Super and Alt keys are only shortcuts that being passed to desktop, if other keys can be passed to desktop in any way it would be possible to run some command through HUD. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: hud 13.10.1+13.10.20131031-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-15.23-generic 3.11.10 Uname: Linux 3.11.0-15-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 CheckboxSubmission: 3d16077c4fdd6a017d47f6e3dc4f3c54 CheckboxSystem: b633b4f40868d491c2ae5b50030ce6f3 Date: Mon Jan 6 17:18:05 2014 InstallationDate: Installed on 2014-01-01 (4 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) MarkForUpload: True SourcePackage: hud UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1266464/+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 1108956] Re: The dash closes when trying to switch from Command lens to home lens
** Changed in: unity Status: In Progress = Triaged ** Changed in: unity (Ubuntu) Status: In Progress = 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/1108956 Title: The dash closes when trying to switch from Command lens to home lens Status in Ayatana Design: Fix Committed Status in Unity: Triaged Status in “unity” package in Ubuntu: Confirmed Bug description: When I open the command lens by pressing ALT+F2, if I press Super the dash is closed. It should not be closed, it should switch to the home lens instead. This is the suite of the bug 1019457 To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/1108956/+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 878836] Re: [FFe] Unity Greeter - Use Unity Greeter to fulfil lock screen as well as login functions
** Changed in: unity Status: In Progress = Fix Committed -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-session in Ubuntu. Matching subscriptions: dx-packages, dx-packages https://bugs.launchpad.net/bugs/878836 Title: [FFe] Unity Greeter - Use Unity Greeter to fulfil lock screen as well as login functions Status in Ayatana Design: Fix Committed Status in The Session Menu: Fix Released Status in Light Display Manager: Triaged Status in Unity: Fix Committed Status in “gnome-screensaver” package in Ubuntu: Fix Released Status in “indicator-session” package in Ubuntu: Fix Released Status in “lightdm” package in Ubuntu: Triaged Status in “unity” package in Ubuntu: Fix Released Status in “unity-greeter” package in Ubuntu: Triaged Status in “indicator-session” source package in Precise: Fix Released Bug description: Use Unity Greeter to fulfil lock screen as well as login functions. Desired Solution: - Replace the current lock screen with the Unity Greeter - perhaps use 'light locker', see http://www.webupd8.org/2013/08/lightdm-session-locker-light-locker.html - also see https://plus.google.com/u/0/106086509626546157534/posts/5hQVYARYCkh [FFe] This is a FFe to implement in unity a lockscreen that looks like unity-greeter inside unity. The code for unity was ready before FF, but to improve PAM support we had to delay it See more at https://code.launchpad.net/~andyrock/unity/lockscreen/+merge/206291 To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/878836/+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 925454] Re: Spread - use the same layout as the alt-tab
** Changed in: unity Status: In Progress = Fix Committed -- 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/925454 Title: Spread - use the same layout as the alt-tab Status in Ayatana Design: Fix Committed Status in Unity: Fix Committed Status in “unity” package in Ubuntu: Fix Released Bug description: The spread should use the same layout as the alt-tab spread for consistency. Its possible ,see this branch: https://code.launchpad.net/~smspillaz/unity/unity.scale_layout To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/925454/+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 915265] Re: [regression] Unity launcher on-screen corruption on resume from suspend with nVidia proprietary driver
The issue is back in 14.04. This is a regression from 13.10, where the problem did not occur. See the attached screenshot. Requesting to re-open this bug. -- 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/915265 Title: [regression] Unity launcher on-screen corruption on resume from suspend with nVidia proprietary driver Status in OEM Priority Project: Fix Released Status in OEM Priority Project oneiric series: Won't Fix Status in OEM Priority Project precise series: Fix Released Status in Unity: Fix Released Status in Unity 6.0 series: Fix Released Status in Unity Distro Priority: Fix Released Status in “unity” package in Ubuntu: Fix Released Status in “unity” source package in Oneiric: Won't Fix Status in “unity” source package in Precise: Fix Released Bug description: [Impact] This bug basically makes NVidia machines unusable after suspend. This is causing problems for users and OEMs that want to use 11.10 alike. [Development Fix] https://bazaar.launchpad.net/~unity-team/unity/trunk/revision/2205 [Test Case] . To reproduce: 1) Suspend 2) Resume 2a) login, if necessary. Note that the login screen (lightdm) displays properly 3) Notice the corrupted launcher 4) Mouse over the launcher; the launcher redraws and the corruption goes away [Regression Potential] Low. We have tested the fix in the development version that we're planning on releasing in April 26th and have found no problems. With the big diff, the regression potential might be a bit bigger for precise. == Original Report == The unity launcher is reliably corrupted upon resume from suspend with some (all?) NVidia hardware with the proprietary NVidia driver. All other visual elements seem to draw correctly, it's just the unity launcher that has this problem. The launcher looks fine after it redraws (for example, if you mouse over it). The problem is not reproducible on Intel or AMD graphics hardware, and I'm told (by Ted Gould) that it doesn't affect the nouveau driver. I have not tested the nouveau driver myself. This problem been reported several times in the comments of bug 676166, I'm filing this separate bug for clarity since 676166 is overloaded. To reproduce: 1) Suspend 2) Resume 2a) login, if necessary. Note that the login screen (lightdm) displays properly 3) Notice the corrupted launcher 4) Mouse over the launcher; the launcher redraws and the corruption goes away The problem affects 11.10, and is not fixed by upgrading to more recent unity, compiz, or nvidia drivers from oneiric-updates or even the most recent SRU candidates not yet in oneiric-proposed. Currently I have the following installed and the problem still exists: ii nvidia-common 1:0.2.35.1 Find obsolete NVIDIA drivers ii nvidia-current280.13-0ubuntu6 NVIDIA binary Xorg driver, kernel module and VDPAU library ii nvidia-current-updates285.05.09-0ubuntu0.1 NVIDIA binary Xorg driver, kernel module and VDPAU library ii nvidia-settings 280.13-0ubuntu2.1 Tool of configuring the NVIDIA graphics driver ii nvidia-settings-updates 285.05.09-0ubuntu0.1 Tool of configuring the NVIDIA graphics driver Unity SRU candidate (not yet in -proposed): ii unity 4.28.0-0ubuntu1~ppa1 Interface designed for efficiency of space and interaction. Compiz SRU candidate (not yet in -proposed): ii compiz 1:0.9.6+bzr20110929-0ubuntu6.1~oneiric1OpenGL window and compositing manager ii compiz-core 1:0.9.6+bzr20110929-0ubuntu6.1~oneiric1OpenGL window and compositing manager Hardware is a MacbookPro 3,1 w/ NVidia 8600M GT. I'm using the amd64 build of 11.10. lspci -vvnn output for graphics card: 01:00.0 VGA compatible controller [0300]: nVidia Corporation G84 [GeForce 8600M GT] [10de:0407] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Apple Computer Inc. Device [106b:00a0] Physical Slot: 1 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 0 Interrupt: pin A routed to IRQ 16 Region 0: Memory at d200 (32-bit, non-prefetchable) [size=16M] Region 1: Memory at c000 (64-bit, prefetchable) [size=256M] Region 3: Memory at d000 (64-bit, non-prefetchable) [size=32M] Region 5: I/O ports at 5000 [size=128] [virtual] Expansion ROM at d300
[Dx-packages] [Bug 1292174] Re: [trusty] webapp launches, container remains blank
** Branch linked: lp:~abreu-alexandre/unity-webapps-qml/fix-desktop- file-gen ** Branch linked: lp:~abreu-alexandre/unity-chromium-extension/fix-icon- launcher-pining-when-reenabling-webapp -- 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/1292174 Title: [trusty] webapp launches, container remains blank Status in WebApps: libunity: New Status in Unity WebApps QML component: Triaged Status in The Webapps-core project: New Status in “libunity-webapps” package in Ubuntu: New Status in “unity-webapps-qml” package in Ubuntu: New Bug description: After installation of webapp via either chromium or firefox, attempt to launch webapp other than Amazon renders no page. Tested on unity-webapps-launchpad, unity-webapps-googleplus, unity- webapps-facebookmessenger. Expected result: webapp launches properly within container and corresponding web page displays. Actual result: webapp launches within container and remains blank, no web page displays. Example image attached. To manage notifications about this bug go to: https://bugs.launchpad.net/libunity-webapps/+bug/1292174/+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 1291461] Re: Lockscreen: keyboard layout switching shortcuts not working
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/1291461 Title: Lockscreen: keyboard layout switching shortcuts not working Status in Unity: New Status in “unity” package in Ubuntu: Confirmed Bug description: New Unity Lockscreen has the same problem as the old one from Gnome: the chosen keyboard shortcut is not switching keyboard layouts on it, the only way is to use mouse. Steps to reproduce: 1. To make things uncomfortable, switch layout to Russian or any other with your favourite shortcut(i am using alt-shift) 2. Lock the screen with ctrl-alt-l 3. Try to change layout back to English to enter password Expected: Layput should change and you should be able to login without touching anything but keyboard. What's happening: Nothing, doesn't react on the keyboard shortcut, you have to change layout using indicator on top panel. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1291461/+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 1292446] Re: lockscreen: on autolock on suspend the fade does not complete before suspend leaving desktop partially visible for a short period on resume
Thanks for the information Mateusz. -- 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/1292446 Title: lockscreen: on autolock on suspend the fade does not complete before suspend leaving desktop partially visible for a short period on resume Status in Unity: New Status in “unity” package in Ubuntu: Confirmed Bug description: When auto-locking as part of a suspend operation the lock screen still fades to opaque, this takes seconds and mid fade the suspend occurs. This means that on waking the machine the fade is still occurring and the desktop is partially visible potentially exposing information protected by the lock. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.1.2+14.04.20140313-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: Fri Mar 14 10:02:52 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2013-06-20 (266 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha amd64 (20130618) SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2013-11-10 (123 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1292446/+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
MIR request for Oxide gives some background: bug #1293681. Essentially, Oxide is the Chromium Content API wrapped with bindings for Ubuntu. The Chromium Content API contains Blink, V8, etc and is subject to main new security vulnerabilities. The Oxide bindings are written in such a way that we are able to pull new upstream Chromium Content API versions without changing the Oxide API, offering us the ability to track upstream Chromium for security fixes. Oxide is the solution for providing security support to the webapp container for the LTS and we really cannot use webapp-container without it. -- 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: New Status in Unity WebApps QML component: New Status in “libunity-webapps” package in Ubuntu: New Status in “oxide-qt” package in Ubuntu: New 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 1292237] Re: hud-service crashed with SIGSEGV in data()
** Branch unlinked: lp:~charlesk/hud/lp-1292237 -- You received this bug notification because you are a member of DX Packages, which is subscribed to hud in Ubuntu. https://bugs.launchpad.net/bugs/1292237 Title: hud-service crashed with SIGSEGV in data() Status in “hud” package in Ubuntu: Triaged Bug description: Don't know how it happened, crash warning just poped up... ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: hud 13.10.1+14.04.20140218.2-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 CurrentDesktop: Unity Date: Thu Mar 13 22:45:46 2014 ExecutablePath: /usr/lib/x86_64-linux-gnu/hud/hud-service InstallationDate: Installed on 2013-02-03 (403 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) ProcCmdline: /usr/lib/x86_64-linux-gnu/hud/hud-service SegvAnalysis: Segfault happened at: 0x7f31049cadc1 _ZNK7QAction4textEv+1:mov 0x8(%rsi),%rsi PC (0x7f31049cadc1) ok source 0x8(%rsi) (0x0008) not located in a known VMA region (needed readable region)! destination %rsi ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: hud StacktraceTop: QAction::text() const () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 ?? () ?? () hud::service::ItemStore::search(QString const, QListhud::service::Result) () hud::service::QueryImpl::refresh() () Title: hud-service crashed with SIGSEGV in QAction::text() UpgradeStatus: Upgraded to trusty on 2014-02-13 (28 days ago) UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo www-data To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hud/+bug/1292237/+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 1262323] Re: Keywords not shown in HUD
** Changed in: hud Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of DX Packages, which is subscribed to hud in Ubuntu. https://bugs.launchpad.net/bugs/1262323 Title: Keywords not shown in HUD Status in Unity HUD: Fix Released Status in “hud” package in Ubuntu: Fix Released Bug description: When using the HUD in the Gallery there are no keywords shown on the right hand column. For instance, Delete has the keyword of Trash that isn't visible. To manage notifications about this bug go to: https://bugs.launchpad.net/hud/+bug/1262323/+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 1262320] Re: Initial items not effected by usage
** Changed in: hud Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of DX Packages, which is subscribed to hud in Ubuntu. https://bugs.launchpad.net/bugs/1262320 Title: Initial items not effected by usage Status in Unity HUD: Fix Released Status in “hud” package in Ubuntu: Fix Released Bug description: The HUD spec says that the first five shown items on the device should be the most frequently used items by the user. The list of items is not changing based on usage currently. To manage notifications about this bug go to: https://bugs.launchpad.net/hud/+bug/1262320/+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 1262326] Re: Unable to search using keywords
** Changed in: hud Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of DX Packages, which is subscribed to hud in Ubuntu. https://bugs.launchpad.net/bugs/1262326 Title: Unable to search using keywords Status in Unity HUD: Fix Released Status in “hud” package in Ubuntu: Fix Released Bug description: In the gallery there is a keyword associated with Delete that is Trash. Searching for trash doesn't bring up the delete action. To manage notifications about this bug go to: https://bugs.launchpad.net/hud/+bug/1262326/+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 1262316] Re: HUD application paths need to match confinement
** Changed in: hud
Status: Fix Committed = Fix Released
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to hud in Ubuntu.
https://bugs.launchpad.net/bugs/1262316
Title:
HUD application paths need to match confinement
Status in Unity HUD:
Fix Released
Status in “hud” package in Ubuntu:
Fix Released
Bug description:
The application paths are:
/com/canonical/hud/application/[int]
And they need to be:
/com/canonical/hud/applications/${DBUS_APP_ID}
Where that is gotten from sanitizing the app id similar to how libnih
does it.
This can be seen by using a confined app on the phone (Notes for
example) and seeing that its HUD entries don't get propagated.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hud/+bug/1262316/+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 1262318] Re: Color Balance in Gallery doesn't work
** Changed in: hud Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of DX Packages, which is subscribed to hud in Ubuntu. https://bugs.launchpad.net/bugs/1262318 Title: Color Balance in Gallery doesn't work Status in Unity HUD: Fix Released Status in “hud” package in Ubuntu: Fix Released Bug description: Installed HUD from trunk. Went to the camera and took a picture of my lovely desk. Then opened it in the gallery. Opened the hud and searched for C where there are Crop and Color Balance available. Touching Color Balance doesn't seem to do anything, but selecting Crop takes you to crop the image. To manage notifications about this bug go to: https://bugs.launchpad.net/hud/+bug/1262318/+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 1254949] Re: Introspecting com.canonical.Unity.WindowStack returns invalid XML
** Changed in: hud Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of DX Packages, which is subscribed to hud in Ubuntu. https://bugs.launchpad.net/bugs/1254949 Title: Introspecting com.canonical.Unity.WindowStack returns invalid XML Status in Unity HUD: Fix Released Status in “hud” package in Ubuntu: Fix Released Bug description: I came across this when working on autopilot vis. There is an XML parsing error when trying to parse the xml that is returned when introspecting, over dbus, the object /com/canonical/Unity/WindowStack on bus com.canonical.Unity.WindowStack. The resulting xml can be seen here: http://pastebin.ubuntu.com/6476952/ it was generated via this script: http://pastebin.ubuntu.com/6476976/ The error appears on line 30 character 30; I guess the '' and '' are considered invalid. (the offending line: annotation value=QListWindowInfo name=org.qtproject.QtDBus.QtTypeName.Out0/) To manage notifications about this bug go to: https://bugs.launchpad.net/hud/+bug/1254949/+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 1292237] Re: hud-service crashed with SIGSEGV in data()
*** This bug is a duplicate of bug 1292586 *** https://bugs.launchpad.net/bugs/1292586 After talking it over with Pete, it sounds like this crash is probably caused by the async dbus calls issue fixed in Bug #1292586. Please upgrade your system to that version of hud when it is released. If you still encounter the crash, please file a new report. ** This bug has been marked a duplicate of bug 1292586 HUD crashing due to async API that looks sync in libdbusmenu-qt -- You received this bug notification because you are a member of DX Packages, which is subscribed to hud in Ubuntu. https://bugs.launchpad.net/bugs/1292237 Title: hud-service crashed with SIGSEGV in data() Status in “hud” package in Ubuntu: Triaged Bug description: Don't know how it happened, crash warning just poped up... ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: hud 13.10.1+14.04.20140218.2-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 CurrentDesktop: Unity Date: Thu Mar 13 22:45:46 2014 ExecutablePath: /usr/lib/x86_64-linux-gnu/hud/hud-service InstallationDate: Installed on 2013-02-03 (403 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) ProcCmdline: /usr/lib/x86_64-linux-gnu/hud/hud-service SegvAnalysis: Segfault happened at: 0x7f31049cadc1 _ZNK7QAction4textEv+1:mov 0x8(%rsi),%rsi PC (0x7f31049cadc1) ok source 0x8(%rsi) (0x0008) not located in a known VMA region (needed readable region)! destination %rsi ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: hud StacktraceTop: QAction::text() const () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 ?? () ?? () hud::service::ItemStore::search(QString const, QListhud::service::Result) () hud::service::QueryImpl::refresh() () Title: hud-service crashed with SIGSEGV in QAction::text() UpgradeStatus: Upgraded to trusty on 2014-02-13 (28 days ago) UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo www-data To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hud/+bug/1292237/+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 1179742] Re: HUD default shortcut (ALT) is way too used by other programs and it creates conflicts
** Tags added: needs-design ** Also affects: ayatana-design Importance: Undecided Status: New ** Changed in: hud (Ubuntu) Status: New = Incomplete -- You received this bug notification because you are a member of DX Packages, which is subscribed to hud in Ubuntu. https://bugs.launchpad.net/bugs/1179742 Title: HUD default shortcut (ALT) is way too used by other programs and it creates conflicts Status in Ayatana Design: New Status in “hud” package in Ubuntu: Incomplete Bug description: All programs use ALT key for some action: open menu, Firefox uses ALT+number to fast go to a tab, etc. and HUD also uses ALT key. This creates not only confusion, but also dozen of HUD accessed by mistake. It is quite anoying. My suggestion is to use some other key or key combination for this. I know it is easy to change (http://askubuntu.com/questions/122209/how- do-i-modify-or-disable-the-huds-use-of-the-alt-key), but why could it not be done GREAT by default? Most users do not want to change settings to have a well configured system :) Thanks! ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: hud 13.04.0daily13.04.03-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-19.30-generic 3.8.8 Uname: Linux 3.8.0-19-generic x86_64 ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 Date: Tue May 14 03:45:48 2013 InstallationDate: Installed on 2013-04-25 (18 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MarkForUpload: True SourcePackage: hud UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/1179742/+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 1293606] [NEW] print icon frozen
You have been subscribed to a public bug: In Xubuntu 13.10, the printer icon freeze when a print job is queue. It doesn't respond to click or any other interacion. ** Affects: indicator-printers (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment -- print icon frozen https://bugs.launchpad.net/bugs/1293606 You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-printers 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 1266298] Re: Launcher does not report status of item to Orca
** Changed in: unity Milestone: None = 7.2.0 ** Changed in: unity Status: In Progress = Fix Committed -- 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/1266298 Title: Launcher does not report status of item to Orca Status in Unity: Fix Committed Status in “unity” package in Ubuntu: Fix Released Bug description: When Orca has focus in the Launcher the status of an item such as Files '2 windows' open is not reported. Expected behaviour is to hear Orca speak if the item is openned and if any how many instances as in Unity-2d. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.1.2+14.04.20131106.1-0ubuntu2 ProcVersionSignature: Ubuntu 3.12.0-2.7-generic 3.12.0 Uname: Linux 3.12.0-2-generic x86_64 ApportVersion: 2.12.7-0ubuntu4 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Mon Jan 6 09:54:59 2014 InstallationDate: Installed on 2013-11-14 (52 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20131113) SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1266298/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
Re: [Dx-packages] [Bug 1201180] Re: Pressing power button turns off the PC ignoring the presence of another session manager
Hi, May I try it on Kubuntu 14.04 beta ?? Thank you. Date: Mon, 17 Mar 2014 14:21:33 + From: t...@ewetel.net To: axe...@hotmail.com Subject: [Bug 1201180] Re: Pressing power button turns off the PC ignoring the presence of another session manager daniel’s KDE Patch works for me, too! (Kubuntu 13.10) -- You received this bug notification because you are subscribed to a duplicate bug report (1124149). https://bugs.launchpad.net/bugs/1201180 Title: Pressing power button turns off the PC ignoring the presence of another session manager To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1201180/+subscriptions -- 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/1201180 Title: Pressing power button turns off the PC ignoring the presence of another session manager Status in “gnome-session” package in Ubuntu: Fix Released Status in “kde-workspace” package in Ubuntu: Triaged Status in “systemd” package in Ubuntu: Fix Released Status in “systemd-shim” package in Ubuntu: Invalid Bug description: In saucy the PC powers down as soon as I press the power button, it seems that systemd is calling poweroff, but I'm not sure if it's doing that in response of some other event (i.e. as callback of a dbus call): root 4998 0.0 0.0 177932 2104 ?Sl 20:41 0:00 /usr/lib/x86_64-linux-gnu/systemd-shim root 5012 0.0 0.0 4440 624 ?S20:41 0:00 \_ sh -c /sbin/poweroff root 5013 0.0 0.0 4440 628 ?S20:41 0:00 \_ /bin/sh /sbin/shutdown -h -P now In any case the caller or systemd itself should be aware that there's a session-manager running and that it shouldn't actually directly power off the system then. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1201180/+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 917115] Re: dbusmenu trunk fails to build
** Changed in: unity Status: In Progress = Invalid ** Changed in: unity (Ubuntu) Status: In Progress = Invalid ** Changed in: unity-jhbuild Status: In Progress = Fix Released -- You received this bug notification because you are a member of DX Packages, which is subscribed to libdbusmenu in Ubuntu. Matching subscriptions: dx-packages, dx-packages https://bugs.launchpad.net/bugs/917115 Title: dbusmenu trunk fails to build Status in DBus Menu: Fix Released Status in Unity: Invalid Status in Unity JHBuild: Fix Released Status in “libdbusmenu” package in Ubuntu: Fix Released Status in “unity” package in Ubuntu: Invalid Bug description: I just did a 'bzr branch lp:dbusmenu cd dbusmenu ./autogen.sh --prefix=/usr make' and libdbusmenu-gtk fails to compile with: make[3]: Entering directory `/home/kamstrup/tmp/dbusmenu/libdbusmenu-gtk' CC libdbusmenu_gtk3_la-client.lo CC libdbusmenu_gtk3_la-genericmenuitem.lo genericmenuitem.c: In function 'set_label': genericmenuitem.c:244:4: error: 'gtk_hbox_new' is deprecated (declared at /usr/include/gtk-3.0/gtk/deprecated/gtkhbox.h:64): Use 'gtk_box_new' instead [-Werror=deprecated-declarations] genericmenuitem.c: In function 'genericmenuitem_set_image': genericmenuitem.c:460:4: error: 'gtk_hbox_new' is deprecated (declared at /usr/include/gtk-3.0/gtk/deprecated/gtkhbox.h:64): Use 'gtk_box_new' instead [-Werror=deprecated-declarations] cc1: all warnings being treated as errors make[3]: *** [libdbusmenu_gtk3_la-genericmenuitem.lo] Error 1 To manage notifications about this bug go to: https://bugs.launchpad.net/libdbusmenu/+bug/917115/+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 1293606] Re: print icon frozen
** Package changed: ubuntu = indicator-printers (Ubuntu) -- 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/1293606 Title: print icon frozen Status in “indicator-printers” package in Ubuntu: New Bug description: In Xubuntu 13.10, the printer icon freeze when a print job is queue. It doesn't respond to click or any other interacion. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-printers/+bug/1293606/+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 1022743] Re: Hardcoded Unity shortcuts responsible for several problems
** Changed in: compiz Status: In Progress = Opinion ** Changed in: unity Status: In Progress = Opinion ** Changed in: unity (Ubuntu) Status: In Progress = Opinion -- 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/1022743 Title: Hardcoded Unity shortcuts responsible for several problems Status in Compiz: Opinion Status in Unity: Opinion Status in “unity” package in Ubuntu: Opinion Bug description: 1. All the hardcoded Unity shortcuts (like Alt+Space, Ctrl+Tab or Super+Tab for example) are not shared with Compiz and the CCSM, so it is possible to double-bind the same keycombinations already used by Unity to other functions without CCSM even showing a warning about it... 2. There are conflicts with hardcoded Unity keycombinations, which are still adjustable via CCSM. Example: You are unable to change the shortcut for the Window Menu (Alt+Space), although the option is there (CCSM-General-Key Bindings-Window Menu) Changing the shortcut to anything else makes it snap back to Alt+Space. It is not possible to change the Mouse-shortcut, nor to use Alt+Button3 (Alt+rightMouseButton) for anything else than showing the window menu. Disabling the shortcut is also not possible. 3. If one can not assign hardcoded keybindings/key-mousebindings to anything else and is not able to disable them either, and one wants to use any program that utilizes the same keycombinations/key-mousecombinations (e.g. a game), it would not be possible to play it, because it would always bring up the hardcoded functions, no matter what... Examples: Alt+Space will always bring up the window menu (window accessibility), Alt+Button3 (RMB) also To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1022743/+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 1290171] Re: appointments don't change when you click on a calendar date
You're welcome! :-) It looks like there's a related regression in Bug #1293646, but for bookkeeping reasons I'm going to treat that bug separately. -- 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/1290171 Title: appointments don't change when you click on a calendar date Status in “indicator-datetime” package in Ubuntu: In Progress Bug description: In the desktop's Coming Events section, we should update the event/alarm entries based on the date clicked on in the Monthly Calendar section. In indicator-datetime-13.10.0+14.04.20140227.1-0ubuntu1, the events are tied to the current clock time and do not change when you click on another date in the calendar. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1290171/+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 1291468] Re: double-clicking on a calendar day opens Evolution to the day *before* the double-clicked day
** Changed in: indicator-datetime (Ubuntu) Status: In Progress = Fix Released -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-datetime in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1291468 Title: double-clicking on a calendar day opens Evolution to the day *before* the double-clicked day Status in “indicator-datetime” package in Ubuntu: Fix Released Bug description: I have Evolution set as my default calendar. In the clock/calendar applet, it displays the 5 next upcoming events on my calendar and an option to add an event. These events are accurate and up to date from today's date. However, if I select another date on the calendar, it will not change to show events from that date. It always displays current upcoming events. Also, if I click on any upcoming event listed, or if I double-click on a date on the calendar, I am directed to the date one day before the date selected. Clicking Add Event opens the Evolution calendar and selects the current date and time. I can begin typing and it will create an event in the selected calendar. Works as expected. 1) Ubuntu 14.04 LTS (beta) 2) a) indicator-datetime 13.10.0+14.04.20140311.1-0ubuntu1 b) Evolution 3.10.4 3) EXPECTED a) Select date on calendar - expected to see upcoming events for that date b) Double-click date on calendar OR click event - expected to be directed to that date or event 4) HAPPENED a) No change/displays upcoming events relative to current date b) Directs to date one day before ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: indicator-datetime 13.10.0+14.04.20140311.1-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 CurrentDesktop: Unity Date: Wed Mar 12 11:29:34 2014 ExecutablePath: /usr/lib/x86_64-linux-gnu/indicator-datetime/indicator-datetime-service InstallationDate: Installed on 2014-03-10 (1 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140310) ProcEnviron: PATH=(custom, no user) LANGUAGE=en_US XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash 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/1291468/+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 1292154] Re: Unity ignores disable-lock-screen desktop key (leads to unlockable guest sessions)
I don't understand. You sould use CtrlAltF8 to go back to guest session. F7 is the first session so yeah it should be locked. Btw my guest session does not lock. Also please open another bug for the first comment. -- 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/1292154 Title: Unity ignores disable-lock-screen desktop key (leads to unlockable guest sessions) Status in Unity: Confirmed Status in “unity” package in Ubuntu: Confirmed Bug description: If I enter a guest session from the login screen, switch to console mode and switch back, I'm taken back to the guest session as expected. If I enter a guest session from the system menu within a regular session, switch to console mode and switch back, I'm taken to the interface for unlocking the regular session. Expected behavior: I should be taken to the guest session in the latter case as well. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1292154/+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 991310] Re: Counters and progress bars on the launcher are blurred if the launcher icon size is set to an odd number of pixels
** Changed in: unity-control-center (Ubuntu) Assignee: George Karavasilev (kokoto-java) = (unassigned) ** No longer affects: unity ** No longer affects: 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/991310 Title: Counters and progress bars on the launcher are blurred if the launcher icon size is set to an odd number of pixels Status in “unity-control-center” package in Ubuntu: Fix Released Bug description: Using Ubuntu 12.04 Unity version: 5.10.0-0ubuntu6 Many apologies if this is in the wrong place. Steps to reproduce this bug: Change the size of icons in the Unity launcher through the appearance settings. If the size is set to an ODD number of pixels then the counters and progress bars that are used by some applications in the launcher are blurred. When the size is set to an EVEN number then there is no problem. See attached screenshots Obviously its not really much of an issue as what's one pixel between friends, you can just pick an even value, but perhaps it would look better to just restrict the values to even numbers? Or perhaps its just my system, if so sorry for wasting anyones time. I'll include some screenshots for reference. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: unity 5.10.0-0ubuntu6 ProcVersionSignature: Ubuntu 3.2.0-24.37-generic 3.2.14 Uname: Linux 3.2.0-24-generic x86_64 ApportVersion: 2.0.1-0ubuntu7 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: Sun Apr 29 17:40:17 2012 InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Beta amd64 (20120328) ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, user) LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-control-center/+bug/991310/+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 1179742] Re: HUD default shortcut (ALT) is way too used by other programs and it creates conflicts
Oh, yes, I am forced to disable the shortcut because I like using ALT+key shorcuts in programs. Even Terminal has copy/paste with ALT. -- You received this bug notification because you are a member of DX Packages, which is subscribed to hud in Ubuntu. https://bugs.launchpad.net/bugs/1179742 Title: HUD default shortcut (ALT) is way too used by other programs and it creates conflicts Status in Ayatana Design: New Status in “hud” package in Ubuntu: Incomplete Bug description: All programs use ALT key for some action: open menu, Firefox uses ALT+number to fast go to a tab, etc. and HUD also uses ALT key. This creates not only confusion, but also dozen of HUD accessed by mistake. It is quite anoying. My suggestion is to use some other key or key combination for this. I know it is easy to change (http://askubuntu.com/questions/122209/how- do-i-modify-or-disable-the-huds-use-of-the-alt-key), but why could it not be done GREAT by default? Most users do not want to change settings to have a well configured system :) Thanks! ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: hud 13.04.0daily13.04.03-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-19.30-generic 3.8.8 Uname: Linux 3.8.0-19-generic x86_64 ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 Date: Tue May 14 03:45:48 2013 InstallationDate: Installed on 2013-04-25 (18 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MarkForUpload: True SourcePackage: hud UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/1179742/+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 1292154] Re: Unity ignores disable-lock-screen desktop key (leads to unlockable guest sessions)
On 2014-03-17 21:06, Andrea Azzarone wrote: I don't understand. You sould use CtrlAltF8 to go back to guest session. F7 is the first session so yeah it should be locked. Ok, thanks, so it was my mistake. Then we can consider the issue in the bug description as invalid. -- 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/1292154 Title: Unity ignores disable-lock-screen desktop key (leads to unlockable guest sessions) Status in Unity: Confirmed Status in “unity” package in Ubuntu: Confirmed Bug description: If I enter a guest session from the login screen, switch to console mode and switch back, I'm taken back to the guest session as expected. If I enter a guest session from the system menu within a regular session, switch to console mode and switch back, I'm taken to the interface for unlocking the regular session. Expected behavior: I should be taken to the guest session in the latter case as well. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1292154/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1245473] Re: Binding ctrl+shift, alt+shift, etc for switching keyboard layout makes shortcuts with ctrl+shift, etc not working in any program
Did a fresh install of latest (2013-03-16) Ubuntu 14.04 image, set Ctrl+Shift as layout switch. I unable to copy test with Ctrl+Shift+arrows, copy and paste text in gnome-terminal with Ctrl+Shift+C/V. Tested on GNOME FlashBack session (Metacity, Compiz). But I can do this way on Unity session. Please fix this bug before Ubuntu 14.04 final release. ** Tags added: trusty-desktop -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1245473 Title: Binding ctrl+shift, alt+shift, etc for switching keyboard layout makes shortcuts with ctrl+shift, etc not working in any program Status in Gnome Settings Daemon: Won't Fix Status in “gnome-settings-daemon” package in Ubuntu: Confirmed Status in “unity” package in Ubuntu: Confirmed Bug description: Tried only with ctrl+shift, maybe behaves the same for other modifier key combinations when used as shortcut for switching layouts. - Set ctrl+shift as shortcut for switching keyboard layouts - Try to use ctrl+shift+v, ctrl+shift+c in Terminal -- it doesn't work (actually Terminal window loses focus when ctrl+shift is pressed, and layout is switched) ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: gnome-settings-daemon 3.8.5-0ubuntu11.1 ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6 Uname: Linux 3.11.0-13-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Date: Mon Oct 28 16:40:02 2013 InstallationDate: Installed on 2013-10-23 (5 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) MarkForUpload: True SourcePackage: gnome-settings-daemon UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-settings-daemon/+bug/1245473/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1226962] Re: Hotkeys not functional in non-latin keyboard layout in 13.10 and 14.04
I installed today's daily image (2013-03-16). I unable to start gnome-terminal in GNOME FlashBack session (Metacity) with Ctrl+Alt+t on non-latin (cyriliic layout Ctrl+Alt+е). But I can start in Unity and GNOME FlashBack (Compiz) sessions. Please fix this bug before Ubuntu 14.04 final release. ** Tags added: trusty-desktop -- 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/1226962 Title: Hotkeys not functional in non-latin keyboard layout in 13.10 and 14.04 Status in LibreOffice Productivity Suite: Confirmed Status in IBus: New Status in Indicator keyboard: Fix Released Status in Inkscape: A Vector Drawing Tool: New Status in Mutter: Fix Released Status in The OpenOffice.org Suite: New Status in Unity: Fix Committed Status in “gnome-settings-daemon” package in Ubuntu: In Progress Status in “indicator-keyboard” package in Ubuntu: Fix Released Status in “unity” package in Ubuntu: Fix Released Status in “unity-settings-daemon” package in Ubuntu: Fix Released Status in “gnome-settings-daemon” package in Fedora: Unknown Bug description: New keyboard layout changer in Ubuntu 13.10 introduce old-new bug. Any system or application hotkey witch use char (for example: ctrl+alt+t for terminal or ctrl+t for new tab in browser) become unfunctional when selected non-latin keyboard layout. Hotkeys with F1-12, numbers and other non-character buttons works perfectly. Window manager hotkeys not affected by this bug. All hotkeys in system parameters-keyboard-hotkeys-windows works perfect with any keyboard layout. Workaround for some system hotkeys and two layouts (english and non- latin): rebind all hotkeys in your local layout. For example instead of ctrl+alt+t use ctrl+alt+τ (greek tau). That hotkey still work with english layout. If you use english and two different non-latin layouts this workaround helps only with one of them. -- For other layout switching problems introduced in Ubuntu 13.10 you can see bug 1218322. -- To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1226962/+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 1292154] Re: Unity ignores disable-lock-screen desktop key (leads to unlockable guest sessions)
Yeah just update the decription. The option bug is still valid. -- 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/1292154 Title: Unity ignores disable-lock-screen desktop key (leads to unlockable guest sessions) Status in Unity: Confirmed Status in “unity” package in Ubuntu: Confirmed Bug description: If I enter a guest session from the login screen, switch to console mode and switch back, I'm taken back to the guest session as expected. If I enter a guest session from the system menu within a regular session, switch to console mode and switch back, I'm taken to the interface for unlocking the regular session. Expected behavior: I should be taken to the guest session in the latter case as well. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1292154/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1245473] Re: Binding ctrl+shift, alt+shift, etc for switching keyboard layout makes shortcuts with ctrl+shift, etc not working in any program
Ctrl+Shift+PrintScreen is broken too if layout switching is set to Ctrl+Shift. -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1245473 Title: Binding ctrl+shift, alt+shift, etc for switching keyboard layout makes shortcuts with ctrl+shift, etc not working in any program Status in Gnome Settings Daemon: Won't Fix Status in “gnome-settings-daemon” package in Ubuntu: Confirmed Status in “unity” package in Ubuntu: Confirmed Bug description: Tried only with ctrl+shift, maybe behaves the same for other modifier key combinations when used as shortcut for switching layouts. - Set ctrl+shift as shortcut for switching keyboard layouts - Try to use ctrl+shift+v, ctrl+shift+c in Terminal -- it doesn't work (actually Terminal window loses focus when ctrl+shift is pressed, and layout is switched) ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: gnome-settings-daemon 3.8.5-0ubuntu11.1 ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6 Uname: Linux 3.11.0-13-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Date: Mon Oct 28 16:40:02 2013 InstallationDate: Installed on 2013-10-23 (5 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) MarkForUpload: True SourcePackage: gnome-settings-daemon UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-settings-daemon/+bug/1245473/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1291410] Re: Sound indicator volume slider not updated
The described bug behavior has been visible on the phone not desktop. -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-sound in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1291410 Title: Sound indicator volume slider not updated Status in “indicator-sound” package in Ubuntu: New Bug description: The sound indicator volume slider is not updated when using HW keys after moving the slider manually (slide). Volume still changes but slider stays with same value. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/1291410/+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 1293672] Re: [regression] Windows are not drawn when resuming from locked screen
** Also affects: unity Importance: Undecided Status: New ** Changed in: unity Importance: Undecided = Medium ** Changed in: unity Assignee: (unassigned) = Andrea Azzarone (andyrock) ** Changed in: unity (Ubuntu) Assignee: (unassigned) = Andrea Azzarone (andyrock) ** Changed in: unity Milestone: None = 7.2.1 ** Changed in: unity Status: New = In Progress ** Changed in: unity (Ubuntu) Status: New = In Progress ** Branch linked: lp:~andyrock/unity/lp-1291402 -- 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/1293672 Title: [regression] Windows are not drawn when resuming from locked screen Status in Unity: In Progress Status in “unity” package in Ubuntu: In Progress Bug description: When unlocking the screen, any window that is restored from a minimized state is not drawn (it is just black). [Steps to reproduce] 1. Open a window 2. Minimize the window 3. Lock the screen 4. Unlock the screen 5. Restore the window [What should happen] * The window content should be drawn as expected. [What happens] * The window is not drawn. See attachment [Workaround] * Any window action will paint the window again, for example re-sizing, minimizing and restoring again, but not moving the window. * Opening the unity dash or HUD also works. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.1.2+14.04.20140313-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6 Uname: Linux 3.13.0-17-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-16ubuntu6) .tmp.unity.support.test.0: ApportVersion: 2.13.3-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: Mon Mar 17 17:18:44 2014 DistUpgraded: 2014-03-14 11:39:48,168 DEBUG enabling apt cron job DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: bbswitch, 0.7, 3.11.0-18-generic, x86_64: installed bbswitch, 0.7, 3.13.0-17-generic, x86_64: installed nvidia-331-updates, 331.38, 3.13.0-17-generic, x86_64: installed 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 (115 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-17-generic root=UUID=0668e908-5441-4ad5-ae8f-9eb19d0b27a6 ro quiet splash SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2014-03-14 (3 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.20140310-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: Mon Mar 17 15:19:40 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/unity/+bug/1293672/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to :
[Dx-packages] [Bug 1292442] Re: lockscreen: menus interactable but render behind the lockscreen
** Changed in: unity (Ubuntu) Assignee: (unassigned) = Brandon Schaefer (brandontschaefer) ** Changed in: unity Status: Triaged = In Progress ** Changed in: unity (Ubuntu) Status: Triaged = In Progress ** Branch linked: lp:~brandontschaefer/unity/fullscreen-lockfix -- 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/1292442 Title: lockscreen: menus interactable but render behind the lockscreen Status in Unity: In Progress Status in “unity” package in Ubuntu: In Progress Bug description: With the latest unity update the lock screen is now in front of the indicator menus which are rendered on click, but behind the lock panel. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.1.2+14.04.20140313-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: Fri Mar 14 09:55:44 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2013-06-20 (266 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha amd64 (20130618) SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2013-11-10 (123 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1292442/+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 1293839] [NEW] Icon turns red, but no feedback in the menu for the reason
Public bug reported: I believe the session icon turns red due to online account issues, but that item in the menu isn't highlighted (I believe it was some time ago), so there's nothing to indicate what the red means. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: indicator-session 12.10.5+14.04.20140311.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 NonfreeKernelModules: nvidia wl ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Tue Mar 18 00:12:46 2014 SourcePackage: indicator-session UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: indicator-session (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug third-party-packages trusty -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-session in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1293839 Title: Icon turns red, but no feedback in the menu for the reason Status in “indicator-session” package in Ubuntu: New Bug description: I believe the session icon turns red due to online account issues, but that item in the menu isn't highlighted (I believe it was some time ago), so there's nothing to indicate what the red means. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: indicator-session 12.10.5+14.04.20140311.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 NonfreeKernelModules: nvidia wl ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Tue Mar 18 00:12:46 2014 SourcePackage: indicator-session UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-session/+bug/1293839/+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 1293841] [NEW] Indicators on lockscreen can be invoked, but no menus visible
Public bug reported: I can click on the indicators in the new lockscreen and the icons are highlighted, but none of the menus are visible. Also, when highlighted, the real indicator icons bleed through to the lockscreen, i.e. my session indicator is red due to an online accounts issue - when on lockscreen it's white again, but when clicked it goes red. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.1.2+14.04.20140313-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 NonfreeKernelModules: nvidia wl ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Tue Mar 18 00:15:59 2014 SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug lockscreen third-party-packages trusty -- 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/1293841 Title: Indicators on lockscreen can be invoked, but no menus visible Status in “unity” package in Ubuntu: New Bug description: I can click on the indicators in the new lockscreen and the icons are highlighted, but none of the menus are visible. Also, when highlighted, the real indicator icons bleed through to the lockscreen, i.e. my session indicator is red due to an online accounts issue - when on lockscreen it's white again, but when clicked it goes red. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.1.2+14.04.20140313-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 NonfreeKernelModules: nvidia wl ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Tue Mar 18 00:15:59 2014 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/1293841/+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 1293843] [NEW] Indicators shift around when going into lockscreen
Public bug reported: When I lock my screen, the indicators seem to sometimes shift places for a split second - it looks like sound indicator disappears for a moment. This might be an artifact of the cross-fade between real and lockscreen indicators, which doesn't seem correct, as the icons look like they're fading out until 3/4ths of the transition just to fade back in the last 1/4th of the time. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.1.2+14.04.20140313-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 NonfreeKernelModules: nvidia wl ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Tue Mar 18 00:20:36 2014 SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug lockscreen third-party-packages trusty -- 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/1293843 Title: Indicators shift around when going into lockscreen Status in “unity” package in Ubuntu: New Bug description: When I lock my screen, the indicators seem to sometimes shift places for a split second - it looks like sound indicator disappears for a moment. This might be an artifact of the cross-fade between real and lockscreen indicators, which doesn't seem correct, as the icons look like they're fading out until 3/4ths of the transition just to fade back in the last 1/4th of the time. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.1.2+14.04.20140313-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 NonfreeKernelModules: nvidia wl ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Tue Mar 18 00:20:36 2014 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/1293843/+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 1292174] Re: [trusty] webapp launches, container remains blank
** Also affects: unity-firefox-extension Importance: Undecided Status: New ** Also affects: unity-firefox-extension (Ubuntu) Importance: Undecided Status: New ** Also affects: unity-chromium-extension Importance: Undecided Status: New ** Also affects: unity-chromium-extension (Ubuntu) Importance: Undecided Status: New -- 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/1292174 Title: [trusty] webapp launches, container remains blank Status in WebApps: libunity: New Status in Chromium extension: Unity Integration: New Status in Firefox extension: Unity Integration: New Status in Unity WebApps QML component: Triaged Status in The Webapps-core project: New Status in “libunity-webapps” package in Ubuntu: New Status in “unity-chromium-extension” package in Ubuntu: New Status in “unity-firefox-extension” package in Ubuntu: New Status in “unity-webapps-qml” package in Ubuntu: New Bug description: After installation of webapp via either chromium or firefox, attempt to launch webapp other than Amazon renders no page. Tested on unity-webapps-launchpad, unity-webapps-googleplus, unity- webapps-facebookmessenger. Expected result: webapp launches properly within container and corresponding web page displays. Actual result: webapp launches within container and remains blank, no web page displays. Example image attached. To manage notifications about this bug go to: https://bugs.launchpad.net/libunity-webapps/+bug/1292174/+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 1292174] Re: [trusty] webapp launches, container remains blank
Recent update to webbrowser-app seems to have fixed issue with unity- webapps-facebookmessenger and unity-webapps-launchpad. -- 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/1292174 Title: [trusty] webapp launches, container remains blank Status in WebApps: libunity: New Status in Chromium extension: Unity Integration: New Status in Firefox extension: Unity Integration: New Status in Unity WebApps QML component: Triaged Status in The Webapps-core project: New Status in “libunity-webapps” package in Ubuntu: New Status in “unity-chromium-extension” package in Ubuntu: New Status in “unity-firefox-extension” package in Ubuntu: New Status in “unity-webapps-qml” package in Ubuntu: New Bug description: After installation of webapp via either chromium or firefox, attempt to launch webapp other than Amazon renders no page. Tested on unity-webapps-launchpad, unity-webapps-googleplus, unity- webapps-facebookmessenger. Expected result: webapp launches properly within container and corresponding web page displays. Actual result: webapp launches within container and remains blank, no web page displays. Example image attached. To manage notifications about this bug go to: https://bugs.launchpad.net/libunity-webapps/+bug/1292174/+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 1292178] Re: New shortcut hint conflicts with startup dialog in guest sessions
** No longer affects: 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/1292178 Title: New shortcut hint conflicts with startup dialog in guest sessions Status in “lightdm” package in Ubuntu: Fix Released Bug description: The new shortcut hint shows up by default every time you enter a guest session. Personally I think that this in itself is unnecessary, but there is also a design conflict. There is now a simple zenity dialog that shows up by default at the start of a guest session. It warns the guest about the fact that they can't save stuff in $HOME and expect it to stay. That dialog is thought to become in focus, but then there is the shortcut hint... The result does not give a pleasant impression. I think that the shortcut hint feature should not apply to guest sessions. Guess this could be fixed either in unity or in lightdm; adding tasks for both packages for now. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1292178/+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 1292442] Re: lockscreen: menus interactable but render behind the lockscreen
Now it's even harder to switch languages because of bug #1291461. No keyboard shortcuts and a half-working indicator -- 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/1292442 Title: lockscreen: menus interactable but render behind the lockscreen Status in Unity: Triaged Status in “unity” package in Ubuntu: Triaged Bug description: With the latest unity update the lock screen is now in front of the indicator menus which are rendered on click, but behind the lock panel. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.1.2+14.04.20140313-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: Fri Mar 14 09:55:44 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2013-06-20 (266 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha amd64 (20130618) SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2013-11-10 (123 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1292442/+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 1039291] Re: No keyboard focus after alt-tab, title bar blank
*** This bug is a duplicate of bug 1035628 *** https://bugs.launchpad.net/bugs/1035628 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/1039291 Title: No keyboard focus after alt-tab, title bar blank Status in “unity” package in Ubuntu: Confirmed Bug description: When I alt-tab between windows, occasionally (maybe 1 out of 10 or 15 times) when I finish, the window is left in a state where it has no keyboard focus, and the title bar is blank. It still appears to have mouse focus (hovering over an element which changes the pointer works, for example), and when I click into the window, keyboard focus is restored. This also appears to happen (again, occasionally) when pressing alt to get to the HUD, then alt again to dismiss it. This only started happening recently, and may be a regression from a unity/compiz update. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: unity 5.14.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-29.46-generic 3.2.24 Uname: Linux 3.2.0-29-generic x86_64 ApportVersion: 2.0.1-0ubuntu12 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: Mon Aug 20 17:31:42 2012 InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 (20120425) ProcEnviron: TERM=xterm PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1039291/+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 1035628] Re: Alt+Tab/Alt+grave brings other window to the front but loses focus entirely.
I upgrade to precise a couple of days ago. I do have this bug, but I don’t use unity! I use the static-app-switcher with compiz and gnome- panel. Is it a general switcher-trap and only unities switcher was fixed? -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1035628 Title: Alt+Tab/Alt+grave brings other window to the front but loses focus entirely. Status in Unity: Fix Released Status in Unity 5.0 series: Fix Released Status in Unity 6.0 series: Fix Released Status in “unity” package in Ubuntu: Fix Released Status in “unity” source package in Precise: Fix Released Bug description: [Impact] Focus losing possibility when alt-`/alt-tab:ing. [Test Case] Alt+Tab doesn't lose window focus - This tests ensures that a racing condition is not possible anymore when alt+tabing. Setup: #. Have 2 windows of different types open. (gedit, nautilus) Actions: #. Press quicky Alt+Tab. (so that the switcher window is not shown) #. Repeat 10 times. Expected Results: No window loses focuses at all. The panel should alway show the title of the window. [Regression Potential] Application switching in general. --- SRU TESTCASE: 1. open two terminals 2. quickly press alt-` a couple of times so that the switcher appears What should happen: no matter how many times you alt-` the focus should never be lost i.e. unity panel should not look like comment#6 -Original Report- Ever since upgrading to Unity 5.14.0-0ubuntu1 a few days ago, my alt+tabs have been constantly breaking. I use alt+tab quickly, fast enough to never see the switcher. The issue is that a good percentage of the time, the window is brought to the front and the focus is momentarily flickered onto the desired window but then the focus is entirely lost: Nothing is in the titlebar and any input goes nowhere. I don't recall any problems with the version previous to this update pushed (5.12-0ubuntu1.1) video demonstrating the bug: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1035628/+attachment/3258477/+files/bug.webm Alt+` also loses focus regularly, even if there is only one window. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: unity 5.14.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-29.46-generic 3.2.24 Uname: Linux 3.2.0-29-generic x86_64 ApportVersion: 2.0.1-0ubuntu12 Architecture: amd64 CheckboxSubmission: 9dfa225a100a6da71689692d7002e544 CheckboxSystem: 2954e74ba17fb0e37fc942cd1d9fab4e 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: Sat Aug 11 09:01:20 2012 InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 (20120425) SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1035628/+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 1035628] Re: Alt+Tab/Alt+grave brings other window to the front but loses focus entirely.
...unity’s switcher was fixed? -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1035628 Title: Alt+Tab/Alt+grave brings other window to the front but loses focus entirely. Status in Unity: Fix Released Status in Unity 5.0 series: Fix Released Status in Unity 6.0 series: Fix Released Status in “unity” package in Ubuntu: Fix Released Status in “unity” source package in Precise: Fix Released Bug description: [Impact] Focus losing possibility when alt-`/alt-tab:ing. [Test Case] Alt+Tab doesn't lose window focus - This tests ensures that a racing condition is not possible anymore when alt+tabing. Setup: #. Have 2 windows of different types open. (gedit, nautilus) Actions: #. Press quicky Alt+Tab. (so that the switcher window is not shown) #. Repeat 10 times. Expected Results: No window loses focuses at all. The panel should alway show the title of the window. [Regression Potential] Application switching in general. --- SRU TESTCASE: 1. open two terminals 2. quickly press alt-` a couple of times so that the switcher appears What should happen: no matter how many times you alt-` the focus should never be lost i.e. unity panel should not look like comment#6 -Original Report- Ever since upgrading to Unity 5.14.0-0ubuntu1 a few days ago, my alt+tabs have been constantly breaking. I use alt+tab quickly, fast enough to never see the switcher. The issue is that a good percentage of the time, the window is brought to the front and the focus is momentarily flickered onto the desired window but then the focus is entirely lost: Nothing is in the titlebar and any input goes nowhere. I don't recall any problems with the version previous to this update pushed (5.12-0ubuntu1.1) video demonstrating the bug: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1035628/+attachment/3258477/+files/bug.webm Alt+` also loses focus regularly, even if there is only one window. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: unity 5.14.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-29.46-generic 3.2.24 Uname: Linux 3.2.0-29-generic x86_64 ApportVersion: 2.0.1-0ubuntu12 Architecture: amd64 CheckboxSubmission: 9dfa225a100a6da71689692d7002e544 CheckboxSystem: 2954e74ba17fb0e37fc942cd1d9fab4e 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: Sat Aug 11 09:01:20 2012 InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 (20120425) SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1035628/+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 1035628] Re: Alt+Tab/Alt+grave brings other window to the front but loses focus entirely.
I have unity 5.20.0 from precise-updates installed, but as I said, I don’t have the Unity Plugin activated for compiz. -- 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/1035628 Title: Alt+Tab/Alt+grave brings other window to the front but loses focus entirely. Status in Unity: Fix Released Status in Unity 5.0 series: Fix Released Status in Unity 6.0 series: Fix Released Status in “unity” package in Ubuntu: Fix Released Status in “unity” source package in Precise: Fix Released Bug description: [Impact] Focus losing possibility when alt-`/alt-tab:ing. [Test Case] Alt+Tab doesn't lose window focus - This tests ensures that a racing condition is not possible anymore when alt+tabing. Setup: #. Have 2 windows of different types open. (gedit, nautilus) Actions: #. Press quicky Alt+Tab. (so that the switcher window is not shown) #. Repeat 10 times. Expected Results: No window loses focuses at all. The panel should alway show the title of the window. [Regression Potential] Application switching in general. --- SRU TESTCASE: 1. open two terminals 2. quickly press alt-` a couple of times so that the switcher appears What should happen: no matter how many times you alt-` the focus should never be lost i.e. unity panel should not look like comment#6 -Original Report- Ever since upgrading to Unity 5.14.0-0ubuntu1 a few days ago, my alt+tabs have been constantly breaking. I use alt+tab quickly, fast enough to never see the switcher. The issue is that a good percentage of the time, the window is brought to the front and the focus is momentarily flickered onto the desired window but then the focus is entirely lost: Nothing is in the titlebar and any input goes nowhere. I don't recall any problems with the version previous to this update pushed (5.12-0ubuntu1.1) video demonstrating the bug: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1035628/+attachment/3258477/+files/bug.webm Alt+` also loses focus regularly, even if there is only one window. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: unity 5.14.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-29.46-generic 3.2.24 Uname: Linux 3.2.0-29-generic x86_64 ApportVersion: 2.0.1-0ubuntu12 Architecture: amd64 CheckboxSubmission: 9dfa225a100a6da71689692d7002e544 CheckboxSystem: 2954e74ba17fb0e37fc942cd1d9fab4e 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: Sat Aug 11 09:01:20 2012 InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 (20120425) SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1035628/+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 1293394] [NEW] [regression] cannot change volume using indicator anymore
Public bug reported: After upgrading to 14.04, I cannot change the sound using the indicator anymore. Changing the volume or muting output does not have any effect. When going to sound settings, changing the output volume also has no effect. However, changing the sound per application under the tab Applications *does* work, so I can still work around it like that. Everything worked fine in 13.10. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: indicator-sound 12.10.2+14.04.20140313-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6 Uname: Linux 3.13.0-17-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Mon Mar 17 08:58:12 2014 InstallationDate: Installed on 2013-11-22 (114 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) SourcePackage: indicator-sound UpgradeStatus: Upgraded to trusty on 2014-03-14 (2 days ago) ** Affects: indicator-sound (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug regression-proposed trusty -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-sound in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1293394 Title: [regression] cannot change volume using indicator anymore Status in “indicator-sound” package in Ubuntu: New Bug description: After upgrading to 14.04, I cannot change the sound using the indicator anymore. Changing the volume or muting output does not have any effect. When going to sound settings, changing the output volume also has no effect. However, changing the sound per application under the tab Applications *does* work, so I can still work around it like that. Everything worked fine in 13.10. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: indicator-sound 12.10.2+14.04.20140313-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6 Uname: Linux 3.13.0-17-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Mon Mar 17 08:58:12 2014 InstallationDate: Installed on 2013-11-22 (114 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) SourcePackage: indicator-sound UpgradeStatus: Upgraded to trusty on 2014-03-14 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/1293394/+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 1293398] [NEW] [regression] indicator menus do not open in lock screen
Public bug reported: It is now possible to click on the indicators in the lockscreen. However, they do not fold open properly. In fact, the indicator itself looks like it was clicked, but the entire menu below it does not show up. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.1.2+14.04.20140313-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6 Uname: Linux 3.13.0-17-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Mon Mar 17 08:57:56 2014 InstallationDate: Installed on 2013-11-22 (114 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2014-03-14 (2 days ago) ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- 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/1293398 Title: [regression] indicator menus do not open in lock screen Status in “unity” package in Ubuntu: New Bug description: It is now possible to click on the indicators in the lockscreen. However, they do not fold open properly. In fact, the indicator itself looks like it was clicked, but the entire menu below it does not show up. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.1.2+14.04.20140313-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6 Uname: Linux 3.13.0-17-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Mon Mar 17 08:57:56 2014 InstallationDate: Installed on 2013-11-22 (114 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2014-03-14 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1293398/+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 1293412] [NEW] Chrome(ium) cannot keep up with new window resizing behavior
Public bug reported: Some applications are too slow to keep up with the new window resizing behavior. This makes the whole process look ugly, because the window gets filled with the black background from the window decoration. I suspect this happens with those applications that need to re-render something that takes time, in this case, websites. Is it possible to revert to the old behavior for such programs? See attached video for a demonstration. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.1.2+14.04.20140313-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6 Uname: Linux 3.13.0-17-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-16ubuntu6) .tmp.unity.support.test.0: ApportVersion: 2.13.3-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: Mon Mar 17 09:13:30 2014 DistUpgraded: 2014-03-14 11:39:48,168 DEBUG enabling apt cron job DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: bbswitch, 0.7, 3.11.0-18-generic, x86_64: installed bbswitch, 0.7, 3.13.0-17-generic, x86_64: installed nvidia-331-updates, 331.38, 3.13.0-17-generic, x86_64: installed 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 (114 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-17-generic root=UUID=0668e908-5441-4ad5-ae8f-9eb19d0b27a6 ro quiet splash SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2014-03-14 (2 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.20140310-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: Mon Mar 17 07:43:27 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 ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 trusty ubuntu ** Attachment added: Screencast 2014-03-17 09:12:59.mp4 https://bugs.launchpad.net/bugs/1293412/+attachment/4027888/+files/Screencast%202014-03-17%2009%3A12%3A59.mp4 -- 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/1293412 Title: Chrome(ium) cannot keep up with new window resizing behavior Status in “unity” package in Ubuntu: New Bug description: Some applications are too slow to keep up with the new window resizing behavior. This makes the whole process look ugly, because the window gets filled with the black background from the window decoration. I suspect this happens with those applications that need to re-render something that takes time, in this case, websites. Is it possible to revert to the old behavior for such programs? See attached video for a demonstration. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.1.2+14.04.20140313-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6 Uname: Linux 3.13.0-17-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus.0:
[Dx-packages] [Bug 1293410] [NEW] Lockscreen kicks in after resuming and unlocking
Public bug reported: Every time I resume my laptop with latest unity I get presented with the new lockscreen, so I enter the password and unlock the screen, but a few seconds after that it locks again and I have to type the password again and unlock. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.1.2+14.04.20140313-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 NonfreeKernelModules: nvidia wl ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Mon Mar 17 09:09:41 2014 SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug third-party-packages trusty -- 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/1293410 Title: Lockscreen kicks in after resuming and unlocking Status in “unity” package in Ubuntu: New Bug description: Every time I resume my laptop with latest unity I get presented with the new lockscreen, so I enter the password and unlock the screen, but a few seconds after that it locks again and I have to type the password again and unlock. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.1.2+14.04.20140313-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 NonfreeKernelModules: nvidia wl ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Mon Mar 17 09:09:41 2014 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/1293410/+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 1292748] Re: Sync d-conf 0.19.91-1 (main) from Debian experimental (main)
** Changed in: d-conf (Ubuntu) Assignee: (unassigned) = Iain Lane (laney) -- You received this bug notification because you are a member of DX Packages, which is subscribed to d-conf in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1292748 Title: Sync d-conf 0.19.91-1 (main) from Debian experimental (main) Status in “d-conf” package in Ubuntu: New Bug description: Please sync d-conf 0.19.91-1 (main) from Debian experimental (main) Explanation of the Ubuntu delta and why it can be dropped: * New upstream release - dconf compile: always write little endian - file-db: don't install match rules on no bus (fixes gdbus assertion) - update dconf(1) manpage for 'dconf compile' * Install the appdata into dconf-editor * New upstream release - engine: issue warnings about missing files only once per source - engine: grok the WritabilityNotify signal from D-Bus - gsettings: handle writability changes correctly - engine: assorted fixes for issues found during testing - portability: only link to -ldl if it is required - add support for 'file-db' to profiles: this is an absolute path to a immutable dconf database file - add support for finding profiles in XDG_DATA_DIRS if they are not in /etc - add 'dconf compile' command for building dconf databases from keyfiles in arbitrary locations (like from the build system of a project that may want to install a file-db) - editor: add a section separator to the app menu for consistency - Add support for the new GSettingsBackend.read_user_value() API * Bump GLib dep to 2.39.1 * Rewrite debian/patches/01_env_path.patch a bit to work with new codebase. Should be droppable soon, ideally. * Use dh_install --fail-missing All changes fixed in debian. New upstream bugfix release Upstream changelog: - fix an unlikely failure in the fuzz testing of gvdb - fix a thread safety issue with file-db Changelog entries since current trusty version 0.19.90-0ubuntu1: d-conf (0.19.91-1) experimental; urgency=medium [ Iain Lane ] * Update Vcs-* URLs for experimental * Run with dh_install --fail-missing * Install the appdata file * New upstream release 0.19.91 [ Andreas Henriksson ] * New upstream release 0.19.90. * Bump glib build-dependency to 2.39.1 according to configure.ac * Update debian/patches/01_env_path.patch to apply again. * Update debian/libdconf1.symbols with one added symbol. -- Iain Lane la...@debian.org Mon, 10 Mar 2014 11:11:00 + To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/d-conf/+bug/1292748/+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 1292748] Re: Sync d-conf 0.19.91-1 (main) from Debian experimental (main)
heheh, this was indeed my intention; syncing -- You received this bug notification because you are a member of DX Packages, which is subscribed to d-conf in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1292748 Title: Sync d-conf 0.19.91-1 (main) from Debian experimental (main) Status in “d-conf” package in Ubuntu: New Bug description: Please sync d-conf 0.19.91-1 (main) from Debian experimental (main) Explanation of the Ubuntu delta and why it can be dropped: * New upstream release - dconf compile: always write little endian - file-db: don't install match rules on no bus (fixes gdbus assertion) - update dconf(1) manpage for 'dconf compile' * Install the appdata into dconf-editor * New upstream release - engine: issue warnings about missing files only once per source - engine: grok the WritabilityNotify signal from D-Bus - gsettings: handle writability changes correctly - engine: assorted fixes for issues found during testing - portability: only link to -ldl if it is required - add support for 'file-db' to profiles: this is an absolute path to a immutable dconf database file - add support for finding profiles in XDG_DATA_DIRS if they are not in /etc - add 'dconf compile' command for building dconf databases from keyfiles in arbitrary locations (like from the build system of a project that may want to install a file-db) - editor: add a section separator to the app menu for consistency - Add support for the new GSettingsBackend.read_user_value() API * Bump GLib dep to 2.39.1 * Rewrite debian/patches/01_env_path.patch a bit to work with new codebase. Should be droppable soon, ideally. * Use dh_install --fail-missing All changes fixed in debian. New upstream bugfix release Upstream changelog: - fix an unlikely failure in the fuzz testing of gvdb - fix a thread safety issue with file-db Changelog entries since current trusty version 0.19.90-0ubuntu1: d-conf (0.19.91-1) experimental; urgency=medium [ Iain Lane ] * Update Vcs-* URLs for experimental * Run with dh_install --fail-missing * Install the appdata file * New upstream release 0.19.91 [ Andreas Henriksson ] * New upstream release 0.19.90. * Bump glib build-dependency to 2.39.1 according to configure.ac * Update debian/patches/01_env_path.patch to apply again. * Update debian/libdconf1.symbols with one added symbol. -- Iain Lane la...@debian.org Mon, 10 Mar 2014 11:11:00 + To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/d-conf/+bug/1292748/+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 1291461] Re: Lockscreen: keyboard layout switching shortcuts not working
As workaround you can use Alt+F10 to access to the indicators via 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/1291461 Title: Lockscreen: keyboard layout switching shortcuts not working Status in Unity: New Status in “unity” package in Ubuntu: New Bug description: New Unity Lockscreen has the same problem as the old one from Gnome: the chosen keyboard shortcut is not switching keyboard layouts on it, the only way is to use mouse. Steps to reproduce: 1. To make things uncomfortable, switch layout to Russian or any other with your favourite shortcut(i am using alt-shift) 2. Lock the screen with ctrl-alt-l 3. Try to change layout back to English to enter password Expected: Layput should change and you should be able to login without touching anything but keyboard. What's happening: Nothing, doesn't react on the keyboard shortcut, you have to change layout using indicator on top panel. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1291461/+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 1047517] Re: compiz crashed with SIGSEGV in g_mount_spec_to_dbus_with_path() ... from unity::IconLoader::Impl::IconLoaderTask::LoaderJobFunc()
** Changed in: unity Milestone: None = 7.2.0 -- 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/1047517 Title: compiz crashed with SIGSEGV in g_mount_spec_to_dbus_with_path() ... from unity::IconLoader::Impl::IconLoaderTask::LoaderJobFunc() Status in Unity: Confirmed Status in “unity” package in Ubuntu: Confirmed Bug description: Unity crashed when i was trying the Preview. ProblemType: Crash DistroRelease: Ubuntu 12.10 Package: unity 6.4.0-0ubuntu4 ProcVersionSignature: Ubuntu 3.5.0-13.14-generic 3.5.3 Uname: Linux 3.5.0-13-generic i686 ApportVersion: 2.5.1-0ubuntu7 Architecture: i386 CrashCounter: 1 Date: Fri Sep 7 18:49:48 2012 ExecutablePath: /usr/bin/compiz InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release i386 (20120423) ProcCmdline: compiz ProcEnviron: PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0xb0d448c2 g_mount_spec_to_dbus_with_path+50: mov0x4(%eax),%ebp PC (0xb0d448c2) ok source 0x4(%eax) (0x0005) not located in a known VMA region (needed readable region)! destination %ebp ok Stack memory exhausted (SP below stack segment) SegvReason: reading NULL VMA Signal: 11 SourcePackage: unity StacktraceTop: g_mount_spec_to_dbus_with_path () from /usr/lib/i386-linux-gnu/gvfs/libgvfscommon.so ?? () from /usr/lib/i386-linux-gnu/gio/modules/libgvfsdbus.so ?? () from /usr/lib/i386-linux-gnu/gio/modules/libgvfsdbus.so ?? () from /usr/lib/i386-linux-gnu/gio/modules/libgvfsdbus.so ?? () from /usr/lib/i386-linux-gnu/gio/modules/libgvfsdbus.so Title: compiz crashed with SIGSEGV in g_mount_spec_to_dbus_with_path() UpgradeStatus: Upgraded to quantal on 2012-09-07 (0 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1047517/+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 1047517] Re: compiz crashed with SIGSEGV in g_mount_spec_to_dbus_with_path() ... from unity::IconLoader::Impl::IconLoaderTask::LoaderJobFunc()
** Changed in: unity Assignee: (unassigned) = Michal Hruby (mhr3) -- 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/1047517 Title: compiz crashed with SIGSEGV in g_mount_spec_to_dbus_with_path() ... from unity::IconLoader::Impl::IconLoaderTask::LoaderJobFunc() Status in Unity: Confirmed Status in “unity” package in Ubuntu: Confirmed Bug description: Unity crashed when i was trying the Preview. ProblemType: Crash DistroRelease: Ubuntu 12.10 Package: unity 6.4.0-0ubuntu4 ProcVersionSignature: Ubuntu 3.5.0-13.14-generic 3.5.3 Uname: Linux 3.5.0-13-generic i686 ApportVersion: 2.5.1-0ubuntu7 Architecture: i386 CrashCounter: 1 Date: Fri Sep 7 18:49:48 2012 ExecutablePath: /usr/bin/compiz InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release i386 (20120423) ProcCmdline: compiz ProcEnviron: PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0xb0d448c2 g_mount_spec_to_dbus_with_path+50: mov0x4(%eax),%ebp PC (0xb0d448c2) ok source 0x4(%eax) (0x0005) not located in a known VMA region (needed readable region)! destination %ebp ok Stack memory exhausted (SP below stack segment) SegvReason: reading NULL VMA Signal: 11 SourcePackage: unity StacktraceTop: g_mount_spec_to_dbus_with_path () from /usr/lib/i386-linux-gnu/gvfs/libgvfscommon.so ?? () from /usr/lib/i386-linux-gnu/gio/modules/libgvfsdbus.so ?? () from /usr/lib/i386-linux-gnu/gio/modules/libgvfsdbus.so ?? () from /usr/lib/i386-linux-gnu/gio/modules/libgvfsdbus.so ?? () from /usr/lib/i386-linux-gnu/gio/modules/libgvfsdbus.so Title: compiz crashed with SIGSEGV in g_mount_spec_to_dbus_with_path() UpgradeStatus: Upgraded to quantal on 2012-09-07 (0 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1047517/+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 1201180] Re: Pressing power button turns off the PC ignoring the presence of another session manager
I can confirm the bug in Kubuntu 13.10, the attached patch works for me. (The trouble seems to be that /usr/bin/qdbus links to /usr/bin/qtchooser which does not seem to work as expected.) -- 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/1201180 Title: Pressing power button turns off the PC ignoring the presence of another session manager Status in “gnome-session” package in Ubuntu: Fix Released Status in “kde-workspace” package in Ubuntu: Triaged Status in “systemd” package in Ubuntu: Fix Released Status in “systemd-shim” package in Ubuntu: Invalid Bug description: In saucy the PC powers down as soon as I press the power button, it seems that systemd is calling poweroff, but I'm not sure if it's doing that in response of some other event (i.e. as callback of a dbus call): root 4998 0.0 0.0 177932 2104 ?Sl 20:41 0:00 /usr/lib/x86_64-linux-gnu/systemd-shim root 5012 0.0 0.0 4440 624 ?S20:41 0:00 \_ sh -c /sbin/poweroff root 5013 0.0 0.0 4440 628 ?S20:41 0:00 \_ /bin/sh /sbin/shutdown -h -P now In any case the caller or systemd itself should be aware that there's a session-manager running and that it shouldn't actually directly power off the system then. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1201180/+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 1201180] Re: Pressing power button turns off the PC ignoring the presence of another session manager
** Patch added: Patch for powerbtn.sh which checks for qdbus availabilities. https://bugs.launchpad.net/ubuntu/+source/systemd-shim/+bug/1201180/+attachment/4028115/+files/powerbtn.sh.patch -- 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/1201180 Title: Pressing power button turns off the PC ignoring the presence of another session manager Status in “gnome-session” package in Ubuntu: Fix Released Status in “kde-workspace” package in Ubuntu: Triaged Status in “systemd” package in Ubuntu: Fix Released Status in “systemd-shim” package in Ubuntu: Invalid Bug description: In saucy the PC powers down as soon as I press the power button, it seems that systemd is calling poweroff, but I'm not sure if it's doing that in response of some other event (i.e. as callback of a dbus call): root 4998 0.0 0.0 177932 2104 ?Sl 20:41 0:00 /usr/lib/x86_64-linux-gnu/systemd-shim root 5012 0.0 0.0 4440 624 ?S20:41 0:00 \_ sh -c /sbin/poweroff root 5013 0.0 0.0 4440 628 ?S20:41 0:00 \_ /bin/sh /sbin/shutdown -h -P now In any case the caller or systemd itself should be aware that there's a session-manager running and that it shouldn't actually directly power off the system then. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1201180/+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 1293497] Re: window title has incorrect subpixel antialias on high-dpi screen
** Attachment added: screenshot https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1293497/+attachment/4028149/+files/unity-high-dpi-subpixel.png -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1293497 Title: window title has incorrect subpixel antialias on high-dpi screen Status in “unity” package in Ubuntu: New Bug description: On a high-dpi screen, the window title has a blurry color-shift (especially noticeable in Radiance) which seems to be caused by sub- pixel aliasing. It is so big that it doesn't achieve the purpose of sub-pixel aliasing. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.1.2+14.04.20140313-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6 Uname: Linux 3.13.0-17-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.13.3-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: Mon Mar 17 11:41:32 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: virtualbox, 4.3.6, 3.13.0-12-generic, x86_64: installed virtualbox, 4.3.6, 3.13.0-15-generic, x86_64: installed virtualbox, 4.3.6, 3.13.0-17-generic, x86_64: installed EcryptfsInUse: Yes GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:3978] InstallationDate: Installed on 2014-02-02 (42 days ago) InstallationMedia: Ubuntu-GNOME 14.04 Trusty Tahr - Alpha amd64 (20140201) MachineType: LENOVO 20266 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-17-generic.efi.signed root=UUID=4bfb3686-b9f7-487d-81f6-eceb41097ad9 ro quiet splash vt.handoff=7 SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/31/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 76CN31WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Yoga2 dmi.board.vendor: LENOVO dmi.board.version: 31900058STD dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Yoga 2 Pro dmi.modalias: dmi:bvnLENOVO:bvr76CN31WW:bd10/31/2013:svnLENOVO:pn20266:pvrLenovoYoga2Pro:rvnLENOVO:rnYoga2:rvr31900058STD:cvnLENOVO:ct10:cvrLenovoYoga2Pro: dmi.product.name: 20266 dmi.product.version: Lenovo Yoga 2 Pro dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.11+14.04.20140310-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.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: Mon Mar 17 09:43:54 2014 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 16970 vendor SDC xserver.version: 2:1.15.0-1ubuntu7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1293497/+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 1293497] [NEW] window title has incorrect subpixel antialias on high-dpi screen
Public bug reported: On a high-dpi screen, the window title has a blurry color-shift (especially noticeable in Radiance) which seems to be caused by sub- pixel aliasing. It is so big that it doesn't achieve the purpose of sub- pixel aliasing. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.1.2+14.04.20140313-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6 Uname: Linux 3.13.0-17-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.13.3-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: Mon Mar 17 11:41:32 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: virtualbox, 4.3.6, 3.13.0-12-generic, x86_64: installed virtualbox, 4.3.6, 3.13.0-15-generic, x86_64: installed virtualbox, 4.3.6, 3.13.0-17-generic, x86_64: installed EcryptfsInUse: Yes GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:3978] InstallationDate: Installed on 2014-02-02 (42 days ago) InstallationMedia: Ubuntu-GNOME 14.04 Trusty Tahr - Alpha amd64 (20140201) MachineType: LENOVO 20266 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-17-generic.efi.signed root=UUID=4bfb3686-b9f7-487d-81f6-eceb41097ad9 ro quiet splash vt.handoff=7 SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/31/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 76CN31WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Yoga2 dmi.board.vendor: LENOVO dmi.board.version: 31900058STD dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Yoga 2 Pro dmi.modalias: dmi:bvnLENOVO:bvr76CN31WW:bd10/31/2013:svnLENOVO:pn20266:pvrLenovoYoga2Pro:rvnLENOVO:rnYoga2:rvr31900058STD:cvnLENOVO:ct10:cvrLenovoYoga2Pro: dmi.product.name: 20266 dmi.product.version: Lenovo Yoga 2 Pro dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.11+14.04.20140310-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.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: Mon Mar 17 09:43:54 2014 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 16970 vendor SDC xserver.version: 2:1.15.0-1ubuntu7 ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 third-party-packages trusty 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/1293497 Title: window title has incorrect subpixel antialias on high-dpi screen Status in “unity” package in Ubuntu: New Bug description: On a high-dpi screen, the window title has a blurry color-shift (especially noticeable in Radiance) which seems to be caused by sub- pixel aliasing. It is so big that it doesn't achieve the purpose of sub-pixel aliasing. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.1.2+14.04.20140313-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6 Uname: Linux 3.13.0-17-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.13.3-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: Mon Mar 17 11:41:32 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: virtualbox, 4.3.6, 3.13.0-12-generic, x86_64: installed virtualbox, 4.3.6, 3.13.0-15-generic, x86_64: installed virtualbox, 4.3.6, 3.13.0-17-generic, x86_64: installed EcryptfsInUse: Yes GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:3978] InstallationDate: Installed on 2014-02-02 (42 days ago) InstallationMedia: Ubuntu-GNOME 14.04 Trusty Tahr - Alpha amd64 (20140201)
[Dx-packages] [Bug 1292748] Re: Sync d-conf 0.19.91-1 (main) from Debian experimental (main)
This bug was fixed in the package d-conf - 0.19.91-1 Sponsored for Jackson Doak (noskcaj) --- d-conf (0.19.91-1) experimental; urgency=medium [ Iain Lane ] * Update Vcs-* URLs for experimental * Run with dh_install --fail-missing * Install the appdata file * New upstream release 0.19.91 [ Andreas Henriksson ] * New upstream release 0.19.90. * Bump glib build-dependency to 2.39.1 according to configure.ac * Update debian/patches/01_env_path.patch to apply again. * Update debian/libdconf1.symbols with one added symbol. -- Iain Lane la...@debian.org Mon, 10 Mar 2014 11:11:00 + ** Changed in: d-conf (Ubuntu) Status: New = Fix Released -- You received this bug notification because you are a member of DX Packages, which is subscribed to d-conf in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1292748 Title: Sync d-conf 0.19.91-1 (main) from Debian experimental (main) Status in “d-conf” package in Ubuntu: Fix Released Bug description: Please sync d-conf 0.19.91-1 (main) from Debian experimental (main) Explanation of the Ubuntu delta and why it can be dropped: * New upstream release - dconf compile: always write little endian - file-db: don't install match rules on no bus (fixes gdbus assertion) - update dconf(1) manpage for 'dconf compile' * Install the appdata into dconf-editor * New upstream release - engine: issue warnings about missing files only once per source - engine: grok the WritabilityNotify signal from D-Bus - gsettings: handle writability changes correctly - engine: assorted fixes for issues found during testing - portability: only link to -ldl if it is required - add support for 'file-db' to profiles: this is an absolute path to a immutable dconf database file - add support for finding profiles in XDG_DATA_DIRS if they are not in /etc - add 'dconf compile' command for building dconf databases from keyfiles in arbitrary locations (like from the build system of a project that may want to install a file-db) - editor: add a section separator to the app menu for consistency - Add support for the new GSettingsBackend.read_user_value() API * Bump GLib dep to 2.39.1 * Rewrite debian/patches/01_env_path.patch a bit to work with new codebase. Should be droppable soon, ideally. * Use dh_install --fail-missing All changes fixed in debian. New upstream bugfix release Upstream changelog: - fix an unlikely failure in the fuzz testing of gvdb - fix a thread safety issue with file-db Changelog entries since current trusty version 0.19.90-0ubuntu1: d-conf (0.19.91-1) experimental; urgency=medium [ Iain Lane ] * Update Vcs-* URLs for experimental * Run with dh_install --fail-missing * Install the appdata file * New upstream release 0.19.91 [ Andreas Henriksson ] * New upstream release 0.19.90. * Bump glib build-dependency to 2.39.1 according to configure.ac * Update debian/patches/01_env_path.patch to apply again. * Update debian/libdconf1.symbols with one added symbol. -- Iain Lane la...@debian.org Mon, 10 Mar 2014 11:11:00 + To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/d-conf/+bug/1292748/+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 1292154] Re: Unity ignores disable-lock-screen desktop key (leads to unlockable guest sessions)
** Changed in: unity Assignee: (unassigned) = Andrea Azzarone (andyrock) -- 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/1292154 Title: Unity ignores disable-lock-screen desktop key (leads to unlockable guest sessions) Status in Unity: Confirmed Status in “unity” package in Ubuntu: Confirmed Bug description: If I enter a guest session from the login screen, switch to console mode and switch back, I'm taken back to the guest session as expected. If I enter a guest session from the system menu within a regular session, switch to console mode and switch back, I'm taken to the interface for unlocking the regular session. Expected behavior: I should be taken to the guest session in the latter case as well. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1292154/+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 1256872] Re: shouldn't open battery statistics dialog on the greeter
The fix was included in the most recent trusty update ** Changed in: indicator-power (Ubuntu) Status: In Progress = Fix Released ** Changed in: indicator-power Status: In Progress = Fix Released -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-power in Ubuntu. https://bugs.launchpad.net/bugs/1256872 Title: shouldn't open battery statistics dialog on the greeter Status in The Power Indicator: Fix Released Status in “indicator-power” package in Ubuntu: Fix Released Bug description: Using current trusty on a laptop: - boot your computer (or try switching user) - on the unity greeter, click on the power indicator - select the battery in the indicator - the gpm statistics dialog is spawned, it shouldn't To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-power/+bug/1256872/+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
The workaround that I found was to disable flipping in nvidia-settings but this shouldn't be a permanent fix because it potentially degrades OpenGL performance: Option NoFlip boolean Disable OpenGL flipping; see Chapter 17 for a description. Default: OpenGL will swap by flipping when possible. [...] o Flipping: When OpenGL flipping is enabled, OpenGL can perform buffer swaps by changing which buffer the DAC scans out rather than copying the back buffer contents to the front buffer; this is generally a much higher performance mechanism and allows tearless swapping during the vertical retrace (when __GL_SYNC_TO_VBLANK is set). The conditions under which OpenGL can flip are slightly complicated, but in general: on GeForce or newer hardware, OpenGL can flip when a single full screen unobscured OpenGL application is running, and __GL_SYNC_TO_VBLANK is enabled. Additionally, OpenGL can flip on Quadro hardware even when an OpenGL window is partially obscured or not full screen or __GL_SYNC_TO_VBLANK is not enabled. -- 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: New 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
[Dx-packages] [Bug 1293394] Re: [regression] cannot change volume using indicator anymore
Thank you for your bug report, if different UIs have the same issue it's likely an issue with pulseaudio rather though. Does it happen in a consistent way (e.g after a fresh boot) ** Changed in: indicator-sound (Ubuntu) Importance: Undecided = Low -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-sound in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1293394 Title: [regression] cannot change volume using indicator anymore Status in “indicator-sound” package in Ubuntu: New Bug description: After upgrading to 14.04, I cannot change the sound using the indicator anymore. Changing the volume or muting output does not have any effect. When going to sound settings, changing the output volume also has no effect. However, changing the sound per application under the tab Applications *does* work, so I can still work around it like that. Everything worked fine in 13.10. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: indicator-sound 12.10.2+14.04.20140313-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6 Uname: Linux 3.13.0-17-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Mon Mar 17 08:58:12 2014 InstallationDate: Installed on 2013-11-22 (114 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) SourcePackage: indicator-sound UpgradeStatus: Upgraded to trusty on 2014-03-14 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/1293394/+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 1291530] Re: Icon doesn't turn red when sound is played while muted
** Branch linked: lp:~larsu/indicator-sound/lp1291530 ** Changed in: indicator-sound (Ubuntu) Status: New = In Progress -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-sound in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1291530 Title: Icon doesn't turn red when sound is played while muted Status in “indicator-sound” package in Ubuntu: In Progress Bug description: The spec states If sound is muted and an application tried to play sound in the past five seconds, a red speaker with a cross (audio-volume-muted-panel). that's not happening in trusty To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/1291530/+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 1293394] Re: [regression] cannot change volume using indicator anymore
Sebastien, this is a permanent issue and always happens. Also happens with the function keys (FN + F10 / F11) on my keyboard. I will try whether it also occurs in other DEs but Unity. -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-sound in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1293394 Title: [regression] cannot change volume using indicator anymore Status in “indicator-sound” package in Ubuntu: New Bug description: After upgrading to 14.04, I cannot change the sound using the indicator anymore. Changing the volume or muting output does not have any effect. When going to sound settings, changing the output volume also has no effect. However, changing the sound per application under the tab Applications *does* work, so I can still work around it like that. Everything worked fine in 13.10. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: indicator-sound 12.10.2+14.04.20140313-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6 Uname: Linux 3.13.0-17-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Mon Mar 17 08:58:12 2014 InstallationDate: Installed on 2013-11-22 (114 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) SourcePackage: indicator-sound UpgradeStatus: Upgraded to trusty on 2014-03-14 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/1293394/+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 390508] Re: notifyOSD ignores the expire timeout parameter
Vanessa, since you ask, those are four more examples of illogical
reasoning. The first is a straw man: no we won't do that and we won't
tell you about it. Nobody has suggested that. Everyone agrees that the
man page does not match reality. As unknown and Holger have pointed out,
notify-send can't be *sure* that the the server will ignore the timeout
-- mate-notification-daemon implements it, at least -- but both Notify
OSD and Gnome Shell do ignore it, so it is ignored for most users. That
is a bug, but it is not a bug in Notify OSD, it is a bug in the man
page. It's roughly the equivalent of a Web reference describing HTML's
blink element without mentioning that the browsers used by most people
now ignore it.
The second is assuming the question: we have proven it with this thread
alone. As I said earlier, the cases described in this report are cases
for which *any* asynchronous notification system wouldn't work reliably
-- whether they had developer-configurable timeouts or not. The
notification your app triggered might be queued behind a dozen from
other apps, and therefore not appear until a full minute after you
wanted it to.
The third is an invalid premise: Linux is community based, anyone can
contribute, the features that people want get in. Features people want
are often rejected from Linux. For example, there is no user-switchable
option to choose BFS or any other process scheduler, because to quote
Linus Torvalds, such an option would be really bad for users in that it
forces the user to make some particular choice that the user is usually
not even aware of. The same is true for most other components of
Ubuntu, including the notification server; their designers often say no
to things. But just as with the kernel, you are welcome to install or
compile your own.
And the fourth is a sunk cost fallacy: We've wasted so many days and
weeks on this topic, it needs to be addressed. The word count in this
bug report is not evidence of anything except people's awe-inspiring
willingness to post comments instead of fixing a man page.
Finally, since you asked, Ubuntu 12.04 experiences a crash or similar
error, on average, once every 25 days, 13.10 once every 14 days, and
Trusty currently once every 11 days. The equivalent figures for Windows
are not public.
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to notify-osd in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/390508
Title:
notifyOSD ignores the expire timeout parameter
Status in One Hundred Papercuts:
Invalid
Status in Message Web:
New
Status in “notify-osd” package in Ubuntu:
Won't Fix
Bug description:
Binary package hint: libnotify-bin
adyroman@panther:~/libnotify-0.4.5/tools$ lsb_release -rd
Description: Ubuntu 9.04
Release: 9.04
adyroman@panther:~/libnotify-0.4.5/tools$
adyroman@panther:~/libnotify-0.4.5/tools$ apt-cache policy libnotify-bin
libnotify-bin:
Installed: 0.4.5-0ubuntu1
Candidate: 0.4.5-0ubuntu1
Version table:
*** 0.4.5-0ubuntu1 0
500 http://ro.archive.ubuntu.com jaunty/universe Packages
100 /var/lib/dpkg/status
adyroman@panther:~/libnotify-0.4.5/tools$
adyroman@panther:~/libnotify-0.4.5/tools$ cat notify-send.c | grep
expire_timeout
static glong expire_timeout = NOTIFY_EXPIRES_DEFAULT;
{ expire-time, 't', 0,G_OPTION_ARG_INT, expire_timeout,
notify_notification_set_timeout(notify, expire_timeout);
adyroman@panther:~/libnotify-0.4.5/tools$
To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/390508/+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 1201180] Re: Pressing power button turns off the PC ignoring the presence of another session manager
The attachment Patch for powerbtn.sh which checks for qdbus availabilities. seems to be a patch. If it isn't, please remove the patch flag from the attachment, remove the patch tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team. [This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issues please contact him.] ** Tags added: patch -- 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/1201180 Title: Pressing power button turns off the PC ignoring the presence of another session manager Status in “gnome-session” package in Ubuntu: Fix Released Status in “kde-workspace” package in Ubuntu: Triaged Status in “systemd” package in Ubuntu: Fix Released Status in “systemd-shim” package in Ubuntu: Invalid Bug description: In saucy the PC powers down as soon as I press the power button, it seems that systemd is calling poweroff, but I'm not sure if it's doing that in response of some other event (i.e. as callback of a dbus call): root 4998 0.0 0.0 177932 2104 ?Sl 20:41 0:00 /usr/lib/x86_64-linux-gnu/systemd-shim root 5012 0.0 0.0 4440 624 ?S20:41 0:00 \_ sh -c /sbin/poweroff root 5013 0.0 0.0 4440 628 ?S20:41 0:00 \_ /bin/sh /sbin/shutdown -h -P now In any case the caller or systemd itself should be aware that there's a session-manager running and that it shouldn't actually directly power off the system then. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1201180/+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 1292586] Re: HUD crashing due to async API that looks sync in libdbusmenu-qt
This bug was fixed in the package hud - 13.10.1+14.04.20140314-0ubuntu1 --- hud (13.10.1+14.04.20140314-0ubuntu1) trusty; urgency=low [ Pete Woods ] * Make legacy queries return no results with an empty search string (LP: #1276569) * Tweak search parameters following advice from Jussi (LP: #1276569) * Use new DBusMenu API to make dbusmenu calls sync (LP: #1292586) * Support multiple GMenuCollectors for each window, and multiple QtGActionGroups for each QtGMenuModel. (LP: #1288025) -- Ubuntu daily release ps-jenk...@lists.canonical.com Fri, 14 Mar 2014 16:37:38 + ** Changed in: hud (Ubuntu) Status: New = Fix Released -- You received this bug notification because you are a member of DX Packages, which is subscribed to hud in Ubuntu. https://bugs.launchpad.net/bugs/1292586 Title: HUD crashing due to async API that looks sync in libdbusmenu-qt Status in Unity HUD: In Progress Status in “hud” package in Ubuntu: Fix Released Bug description: HUD is crashing because libdbusmenu-qt is running the event loop during what appears to be a synchronous method call. To manage notifications about this bug go to: https://bugs.launchpad.net/hud/+bug/1292586/+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 1288025] Re: HUD entries don't get activated with gmenumodel
This bug was fixed in the package hud - 13.10.1+14.04.20140314-0ubuntu1 --- hud (13.10.1+14.04.20140314-0ubuntu1) trusty; urgency=low [ Pete Woods ] * Make legacy queries return no results with an empty search string (LP: #1276569) * Tweak search parameters following advice from Jussi (LP: #1276569) * Use new DBusMenu API to make dbusmenu calls sync (LP: #1292586) * Support multiple GMenuCollectors for each window, and multiple QtGActionGroups for each QtGMenuModel. (LP: #1288025) -- Ubuntu daily release ps-jenk...@lists.canonical.com Fri, 14 Mar 2014 16:37:38 + ** Changed in: hud (Ubuntu) Status: New = Fix Released -- You received this bug notification because you are a member of DX Packages, which is subscribed to hud in Ubuntu. https://bugs.launchpad.net/bugs/1288025 Title: HUD entries don't get activated with gmenumodel Status in Unity HUD: In Progress Status in “evince” package in Ubuntu: Invalid Status in “hud” package in Ubuntu: Fix Released Bug description: 1. Open evince 2. tap alt to get the HUD 3. type menu item name (eg open). Note that all the evince menu items seem to be available in the HUD 4. press enter 5. nothing happens ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: evince 3.10.3-0ubuntu9 ProcVersionSignature: Ubuntu 3.13.0-15.35-generic 3.13.5 Uname: Linux 3.13.0-15-generic x86_64 ApportVersion: 2.13.2-0ubuntu5 Architecture: amd64 CurrentDesktop: Unity Date: Wed Mar 5 13:28:59 2014 InstallationDate: Installed on 2013-06-22 (255 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha amd64 (20130621) SourcePackage: evince UpgradeStatus: Upgraded to trusty on 2013-12-05 (89 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/hud/+bug/1288025/+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 1276569] Re: hud flaky or problematic autopilot tests detected in cu2d (02/2014)
This bug was fixed in the package hud - 13.10.1+14.04.20140314-0ubuntu1 --- hud (13.10.1+14.04.20140314-0ubuntu1) trusty; urgency=low [ Pete Woods ] * Make legacy queries return no results with an empty search string (LP: #1276569) * Tweak search parameters following advice from Jussi (LP: #1276569) * Use new DBusMenu API to make dbusmenu calls sync (LP: #1292586) * Support multiple GMenuCollectors for each window, and multiple QtGActionGroups for each QtGMenuModel. (LP: #1288025) -- Ubuntu daily release ps-jenk...@lists.canonical.com Fri, 14 Mar 2014 16:37:38 + ** Changed in: hud (Ubuntu) Status: New = Fix Released -- You received this bug notification because you are a member of DX Packages, which is subscribed to hud in Ubuntu. https://bugs.launchpad.net/bugs/1276569 Title: hud flaky or problematic autopilot tests detected in cu2d (02/2014) Status in Unity HUD: In Progress Status in “hud” package in Ubuntu: Fix Released Bug description: It seems things have improved well after the latest fixes (bug #1244704), but there are still a couple of failing tests. One on nvidia and three on intel. Attaching autopilot logs. QA lab links http://q-jenkins.ubuntu-ci:8080/job/autopilot-trusty-daily_release/label=autopilot-nvidia/1309/ http://q-jenkins.ubuntu-ci:8080/job/autopilot-trusty-daily_release/label=qa-intel-4000/1309/ unity.tests.test_hud.HudBehaviorTests.test_no_initial_values unity.tests.test_hud.HudBehaviorTests.test_gedit_save unity.tests.test_hud.HudBehaviorTests.test_hud_does_not_open_when_fullscreen_window To manage notifications about this bug go to: https://bugs.launchpad.net/hud/+bug/1276569/+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 1293306] Re: Selecting Restart shows Shutdown button selected
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/1293306 Title: Selecting Restart shows Shutdown button selected Status in “unity” package in Ubuntu: Confirmed Bug description: 1) Ubuntu Trusty Tahr (development branch) Release: 14.04 2) unity: Installed: 7.1.2+14.04.20140313-0ubuntu1 Candidate: 7.1.2+14.04.20140313-0ubuntu1 Version table: *** 7.1.2+14.04.20140313-0ubuntu1 0 500 http://nz.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status 3) When I click the cog (top right of panel) and then select 'Restart' I expect to see the restart button highlighted as default choice. 4) Instead, the 'Shutdown' button is highlighted. For a mouse user, it appears only slightly contrary that the default option is the opposite choice. If restarting via keyboard however, the user, having selected Restart, cannot just push enter, which would be the undesired outcome. Instead they must push the arrow key to select Restart and then push enter. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.1.2+14.04.20140313-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: Mon Mar 17 15:42:49 2014 InstallationDate: Installed on 2014-03-13 (3 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140301) 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/1293306/+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 1286784] Re: Inconsistent scrollwheel launcher behavior for window switching.
** Changed in: unity Status: In Progress = Fix Committed -- 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/1286784 Title: Inconsistent scrollwheel launcher behavior for window switching. Status in Ayatana Design: Fix Committed Status in Unity: Fix Committed Status in “unity” package in Ubuntu: Fix Released Bug description: Background: I believe it first landed in 13.04 that scrolling the mouse wheel over launcher icons would flip through multiple windows of that app or do nothing if that app was not open. IMO, this is exactly what Unity was missing that I couldn't put a finger on for myself and I love it!! This worked exactly as described there for all lauchers regardless of what app was focused. Apparently, working on unfocused apps was unintentional but at this point it has been in use in the wild for a while. This unintended feature has recently been removed in the fix for #1263786 and #1267888. Current Sitution: The recurring theory in this scrollwheel discussion has been that whatever scrolling in one direction does, scrolling in the opposite direction should undo. The primary focus of this bug is just to define where such opposite scrolling needs fixing. But it must also be pointed out that fixing these behaviors resolves some complaints against the aforementioned unintended feature making its removal unnecessary. And a consistent approach to this could also solve some other hotly requested use cases. 1. Single App Use Case 1.1. Steps to Reproduce 1.1.1. Open 4 Terminals. They should naturally position into the 4 corners so let's refer to them as NorthWest, NorthEast, SouthWest, SouthEast (NW, NE, SW, SE). 1.1.2. Click through them all to force a Z order. Of course the Z order will be the opposite of the click order so I click through them intentionally backwards bottom to top and right to left: SE, SW, NE, NW. My Z order is now NW, NE, SW, SE; NW is the focused window. 1.1.3. Mouseover Terminal Launcher and Scrollwheel Down Repeatedly, eventually coming to rest on NW again as the focused window. This proceeds through and loops the Z order as expected: NW, NE, SW, SE, ... NW 1.1.4. Mouseover Terminal Launcher and Scrollwheel Up Repeatedly, eventually coming to rest again on NW. This reverses through and loops the Z order as expected: SE, SW, NE, NW ... NW 1.1.5 Mouseover Terminal Launcher and Scrollwheel Down 1 notch and then Up 1 notch. 1.2. Expected Results: Down Goes from NW to NE and Up goes back from NE to NW. Z order should remain unchanged: NW, NE, SW, SE. 1.3. Actual Results: Down Goes from NW to NE and Up goes from NE to SE. 1.4. Reasoning: The Up abrubtly terminates the Down process causing NE to gain focus and leaving the new Z order NE, NW, SW, SE. Now the new Up process immediately processes from the bottom of the Z order to SE. Presumably if this Up process is completed here and SE gains focus the Z order ends at SE, NE, NW, SW. This can be confirmed by swicthing direction again and scrolling down repeatedly. 1.5. Preferred Fix: Scrollwheel Up and Down should proceed through the Z order but should not be independent. In other words, an App Launcher Scrolling Event on the focused should grab and freeze the Z order of all App windows and scroll through the them, up or down, until all scrolling is done. 1.6. Alternative Fix: If Scrolling were changed to proceed through some sort of spacial relationship instead of Z order it would not matter if they were independent. However, behavior for windows of identical geometry would then be undefined. 1.7. Alternative Fix: If Scrolling were changed to always proceed through the order shown in the Launcher context menu it would not matter. This would also most closely resemble previous mouse wheel behavior on the old Gnome 2 window list panel. Presumably this ordering is defined by window creation order or age. 2. Multitasking Use Case 2.1 Steps to Reproduce 2.1.1. Same as 1.1.1. Open 4 Terminals. 2.1.2. Same as 1.1.2. Force Z Order NW, NE, SW, SE. 2.1.3. Click Other Launcher. Other App (Firefox in my case) is opened/focused. The effects of later steps are easiest to noticed when this other App is maximized. 2.1.4. Click Terminal Launcher. As expected NW Terminal is focused; all other terminals remain below Other App (OA). Z Order is NW, OA. 2.1.5. Scrollweel Down Repeatedly. This is a part of the genius of the whole Scrollwheel feature!! As expected, this cycles through the terminals in Z order but always keeps Other app immediately below the topmost terminal. The end-user effect of this behavior is cycling through the terminal windows 1 at a time and never losing sight that the other app _should_ end up as the next most recent overall window. After 1 notch of scroll Z order is NE, OA.
[Dx-packages] [Bug 1288957] Re: Add option to restore behavior of using mouse scrollwheel to focus app windows
** Changed in: unity Status: In Progress = Fix Committed -- 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/1288957 Title: Add option to restore behavior of using mouse scrollwheel to focus app windows Status in Unity: Fix Committed Status in “unity” package in Ubuntu: Fix Released Bug description: The fixes for bug #1263786 and bug #1267888 has caused headaches for users who were used to focusing inactive windows using the scrollwheel on the Launcher icon of opened apps. We should have an option in the CCSM Unity plugin that will allow users to restore this behavior if they want that behavior back. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1288957/+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 1073990] Re: AP test should be written as a unit test
** Changed in: unity Status: In Progress = Fix Committed -- 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/1073990 Title: AP test should be written as a unit test Status in Unity: Fix Committed Status in “unity” package in Ubuntu: Fix Released Bug description: The AP test: unity.tests.launcher.test_icon_behavior.LauncherIconsTests.test_icon_shows_on_quick_application_reopen Relies on opening, closing, and re-opening an application within a very short period of time. This is not easy to do within autopilot - this functionality should be tested as a unit test, rather than as an autopilot test. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1073990/+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 1282261] Re: hud-service crashed with signal 7 in Columbus::Trie::append()
** Information type changed from Private to Public -- You received this bug notification because you are a member of DX Packages, which is subscribed to hud in Ubuntu. https://bugs.launchpad.net/bugs/1282261 Title: hud-service crashed with signal 7 in Columbus::Trie::append() Status in Libcolumbus, a small, fast, error tolerant matcher: New Status in “hud” package in Ubuntu: New Bug description: Random bug. Not aware of what caused it past heavy workload. ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: hud 13.10.1+14.04.20140218.2-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-88.8-mptcp Uname: Linux 3.11.0-88-mptcp x86_64 NonfreeKernelModules: ufsd ApportVersion: 2.13.2-0ubuntu5 Architecture: amd64 CurrentDesktop: Unity Date: Wed Feb 19 15:39:52 2014 ExecutablePath: /usr/lib/x86_64-linux-gnu/hud/hud-service InstallationDate: Installed on 2014-02-12 (7 days ago) InstallationMedia: It ProcCmdline: /usr/lib/x86_64-linux-gnu/hud/hud-service ProcEnviron: PATH=(custom, no user) LANGUAGE=en_CA:en XDG_RUNTIME_DIR=set LANG=en_CA.UTF-8 SHELL=/bin/bash Signal: 7 SourcePackage: hud StacktraceTop: Columbus::Trie::append(char const*, int) () from /usr/lib/x86_64-linux-gnu/libcolumbus.so.1 Columbus::Trie::addNewNode(unsigned int) () from /usr/lib/x86_64-linux-gnu/libcolumbus.so.1 Columbus::Trie::addNewSibling(unsigned int, unsigned int, unsigned short) () from /usr/lib/x86_64-linux-gnu/libcolumbus.so.1 Columbus::Trie::insertWord(Columbus::Word const, unsigned int) () from /usr/lib/x86_64-linux-gnu/libcolumbus.so.1 Columbus::WordStore::getID(Columbus::Word const) () from /usr/lib/x86_64-linux-gnu/libcolumbus.so.1 Title: hud-service crashed with signal 7 in Columbus::Trie::append() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm bumblebee cdrom dip fuse lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/libcolumbus/+bug/1282261/+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 968533] Re: Alt-tab to Firefox sends Firefox to 100% CPU; unity-panel-service to 80% CPU and hud-service to 20-80% CPU
Is anyone still experiencing this bug in 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, dx-packages https://bugs.launchpad.net/bugs/968533 Title: Alt-tab to Firefox sends Firefox to 100% CPU; unity-panel-service to 80% CPU and hud-service to 20-80% CPU Status in Unity: Confirmed Status in “indicator-appmenu” package in Ubuntu: Confirmed Status in “unity” package in Ubuntu: Confirmed Bug description: I've been seeing UI hangs after switching tabs in Firefox, and switching from other applications to Firefox. It can take 3-8 seconds to change *tab*. During this time the CPU is maxed out; typical output from 'top' during this period shows 'hud- service' and 'unity-panel-service' combined using about the same CPU as Firefox itself: 100 10.4 26:07.73 firefox 53 0.6 6:14.86 hud-service 38 1.5 6:42.14 unity-panel-service I suspect that the change is causing a (an inefficient) re-index related to updated menu structures. (Eg. something like the history menu, although I can't see what it is as don't currently have a menu bar). To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/968533/+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
