[Dx-packages] [Bug 737811] Re: qt development apps icons look ugly
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: qt4-x11 (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/737811 Title: qt development apps icons look ugly Status in Unity: Invalid Status in “qt4-x11” package in Ubuntu: Confirmed Status in “unity” package in Ubuntu: Invalid Bug description: It's related to bug #732988, where qtcreator icon has been updated to match a proper resolution. So qt designer/assistant/linguist icons should be fixed. ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: qt4-designer 4:4.7.2-0ubuntu4 ProcVersionSignature: Ubuntu 2.6.38-7.35-generic 2.6.38 Uname: Linux 2.6.38-7-generic i686 Architecture: i386 Date: Fri Mar 18 21:32:32 2011 InstallationMedia: Ubuntu 11.04 Natty Narwhal - Alpha i386 (20110318) ProcEnviron: LANGUAGE=it_IT:en LANG=it_IT.UTF-8 SHELL=/bin/bash SourcePackage: qt4-x11 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/737811/+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 737811] Re: qt development apps icons look ugly
** Tags removed: i386 natty ** Tags added: precise -- 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/737811 Title: qt development apps icons look ugly Status in Unity: Invalid Status in “qt4-x11” package in Ubuntu: Confirmed Status in “unity” package in Ubuntu: Invalid Bug description: It's related to bug #732988, where qtcreator icon has been updated to match a proper resolution. So qt designer/assistant/linguist icons should be fixed. ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: qt4-designer 4:4.7.2-0ubuntu4 ProcVersionSignature: Ubuntu 2.6.38-7.35-generic 2.6.38 Uname: Linux 2.6.38-7-generic i686 Architecture: i386 Date: Fri Mar 18 21:32:32 2011 InstallationMedia: Ubuntu 11.04 Natty Narwhal - Alpha i386 (20110318) ProcEnviron: LANGUAGE=it_IT:en LANG=it_IT.UTF-8 SHELL=/bin/bash SourcePackage: qt4-x11 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/737811/+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 1244237] Re: Ubuntu 13.04 Unity desktop background smears when dragging windows
It's now Thursday morning and I worked at home yesterday. When I powered on my work PC this morning I did not have the problem, though my desktop background is blank/black (it should be an image). I checked my mail and opened Firefox, and periodically checked my desktop and all was fine - no smearing. Then I opened Nemo and the smearing started right away. The reason I mention the bit about working at home yesterday is that I'm pretty sure that if I reboot (even shutdown and boot), I will get the smearing straight away even without starting Nemo. It only seems to be smear free if my PC is powered off at least over night. I doesn't make sense to me but there it is. -- 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/1244237 Title: Ubuntu 13.04 Unity desktop background smears when dragging windows Status in “unity” package in Ubuntu: Confirmed Bug description: In the last week I have found that my desktop background is not refreshed when I drag windows across the screen. This also happens when windows are minimised or closed. It is especially noticeable when compiz animations are used as the window shrink/blur remains on areas of the screen where only the background shows. It has been reported on AskUbuntu with the title of 'Unity desktop smears (doesn't refresh) and shows no wallpaper' and one contributor says it doesn't happen with Cinnamon (though their post was deleted as not being an answer, as was mine). My wallpaper does not show either, even after I changed it, and it used to. My hardware it AMD A10-5700 with 7660D graphics on Ubuntu 13.04 with latest updates. I am using the fglrx-updates driver. Others (on AskUbuntu) tried different graphics drivers but it didn't help. I have not tried with 13.10. Screen shot attached. Thanks. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: unity 7.0.0daily13.06.19~13.04-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-32.47-generic 3.8.13.10 Uname: Linux 3.8.0-32-generic x86_64 NonfreeKernelModules: fglrx .tmp.unity.support.test.0: ApportVersion: 2.9.2-0ubuntu8.3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Thu Oct 24 14:46:12 2013 DistUpgraded: Fresh install DistroCodename: raring DistroVariant: ubuntu DkmsStatus: fglrx-updates, 9.012, 3.8.0-32-generic, x86_64: installed virtualbox, 4.2.10, 3.8.0-32-generic, x86_64: installed EcryptfsInUse: Yes GraphicsCard: Advanced Micro Devices [AMD] nee ATI Trinity [Radeon HD 7660D] [1002:9901] (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. Device [1462:7721] InstallationDate: Installed on 2013-04-06 (200 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Alpha amd64 (20130402.1) JockeyStatus: kmod:fglrx - Video driver for the AMD graphics accelerators (Proprietary, Disabled, Not in use) kmod:fglrx_updates - ATI Fire GL (Proprietary, Enabled, Not in use) MachineType: MSI MS-7721 MarkForUpload: True ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-32-generic root=UUID=be7626d6-266e-4846-b338-8aa982b96cee ro quiet splash vt.handoff=7 SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/14/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V10.2 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: FM2-A85XMA-P33 (MS-7721) dmi.board.vendor: MSI dmi.board.version: 3.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 3.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV10.2:bd12/14/2012:svnMSI:pnMS-7721:pvr3.0:rvnMSI:rnFM2-A85XMA-P33(MS-7721):rvr3.0:cvnMSI:ct3:cvr3.0: dmi.product.name: MS-7721 dmi.product.version: 3.0 dmi.sys.vendor: MSI version.compiz: compiz 1:0.9.9~daily13.06.19~13.04-0ubuntu1 version.fglrx-installer: fglrx-installer N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.43-0ubuntu1.1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.1.4-0ubuntu0.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.1.4-0ubuntu0.1 version.xserver-xorg-core: xserver-xorg-core 2:1.13.3-0ubuntu6.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2b2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.1.0-0ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.6-0ubuntu4.3 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.7-0ubuntu1 xserver.bootTime: Thu Oct 24 08:57:21 2013 xserver.configfile: default xserver.devices:
[Dx-packages] [Bug 664647] Re: All menu item text is invisible in Adobe Reader
A small addition to the script. You need to put quotes $ @. Otherwise, the file path with spaces not open. And then the decision will be the following: root@marys-ubuntu:/opt/Adobe/Reader9/bin# mv acroread acroread-real root@marys-ubuntu:/opt/Adobe/Reader9/bin# nano acroread root@marys-ubuntu:/opt/Adobe/Reader9/bin# chmod 755 acroread Where acroread is env UBUNTU_MENUPROXY=0 /opt/Adobe/Reader9/bin/acroread-real $@ Thanks to #20 author!!! -- You received this bug notification because you are a member of DX Packages, which is subscribed to appmenu-gtk in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/664647 Title: All menu item text is invisible in Adobe Reader Status in Application menu module for GTK+: Confirmed Status in Unity Foundations: Confirmed Status in “acroread” package in Ubuntu: Confirmed Status in “appmenu-gtk” package in Ubuntu: Invalid Bug description: indicator-appmenu 0.0.13-0ubuntu1, Ubuntu 10.10 beta appmenu-gtk 0.2.0-0ubuntu1, Ubuntu 11.04 1. Launch Adobe Reader. 2. Open any menu. What you see: All items present, and all separators visible, but the item text is invisible. https://launchpadlibrarian.net/59735690/acroread.png What you should see: The menu items are visible. To manage notifications about this bug go to: https://bugs.launchpad.net/appmenu-gtk/+bug/664647/+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 1120223] Re: Multi-monitor: Mousepointer hangs when passing between monitors, although no Launcher is there (regression)
The problem still happens to me also on Ubuntu 13.10... -- 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/1120223 Title: Multi-monitor: Mousepointer hangs when passing between monitors, although no Launcher is there (regression) Status in Unity: Confirmed Status in “unity” package in Ubuntu: Confirmed Bug description: [How to reproduce] 1. Have a dual screen left-right config, with the Launcher just visible on your main (left) monitor 2. Make your mousepointer move between first and second display multiple times [What you would expect] You should feel no barrier when doing that, as there is no Launcher on the right screen. [What actually happens] The mousepointer sometimes hangs, when moving between those screens (both directions are affected, left-right right-left). Note: It always hangs once you stay longer than 1 second on each monitor. It also starts blocking after one second if you move between your screens rapidly. Workaround (without hacking the code): Edit unityshell.xml (best copy it to ~/.compiz-1/metadata) and change edge_passed_disabled_ms default and max settings to 9, which means your pointer will hang once in 250 hours/once every 10 days after the barrier has been broken. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1120223/+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 1165420] Re: Unable to access indicators from HUD
This is clearly a bug and not a design decision (at least, if this is the same issue as #1102493, which I think it is, and which has been marked as a duplicate). Note that the problem is not that you cannot access a non-focused application with the HUD - the problem is that *only* the messaging indicator is inaccessible through the HUD. Since other indicators _are_ accessible, this clearly is not a design decision. (Note for example that it is also impossible to bring up a chat window though the HUD with someone who started an Empathy conversation with you and thus is listed in the messaging menu.) ** Also affects: indicator-messages Importance: Undecided Status: New ** Changed in: hud Status: Incomplete = Confirmed ** Changed in: hud (Ubuntu) Status: Incomplete = Confirmed ** Changed in: indicator-messages Status: New = Confirmed ** Changed in: ayatana-design Status: New = Confirmed -- 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/1165420 Title: Unable to access indicators from HUD Status in Ayatana Design: Confirmed Status in Unity HUD: Confirmed Status in The Messaging Menu: Confirmed Status in “hud” package in Ubuntu: Confirmed Bug description: In Ubuntu 12.10 I was able to use HUD to access Messaging menu and Gwibber's Update Status option there, making status updates to Twitter easy and fast. I could also use HUD to change my status in Empathy from Available to Busy and vice-versa. In Ubuntu 13.04 Beta HUD no longer finds the Update Status option when typing Update Status or Update Also writing Available Away or Busy no longer gives any results. Other indicators however are accessible and I can use HUD to Suspend my computer or to view Skype status or Ubuntu one indicator options. Repeating: 1. Press alt key to start HUD 2. Write Update status or Available What was expected: HUD should have shown options ether from Gwibber to Update Status or Empathy to change status to Available both available from the messaging indicator. What happened: HUD didn't find any results. Notes: I have Ubuntu 13.04 Beta 64bit upgraded from Ubuntu 12.10 64bits and I'm using proprietary fglrx drivers. To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/1165420/+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 1246662] [NEW] Gnome Shell won't lock and ask for password when sssd auth is used
Public bug reported: I use sssd to authenticate users, and due to a change introduced in accountsservice on unlock, the desktop is shown immediately wqith no password entry. Upstream has a patch here: https://bugzilla.gnome.org/show_bug.cgi?id=708997 Please apply ASAP. I tested the patch with a dpkg-buildpackage local install. It works. ** Affects: accountsservice Importance: Unknown Status: Unknown ** Affects: accountsservice (Ubuntu) Importance: Undecided Status: New ** Bug watch added: GNOME Bug Tracker #708997 https://bugzilla.gnome.org/show_bug.cgi?id=708997 ** Also affects: accountsservice via https://bugzilla.gnome.org/show_bug.cgi?id=708997 Importance: Unknown Status: Unknown ** Summary changed: - Gnme Shell won't lock and ask for password when sssd auth is used + Gnome Shell won't lock and ask for password when sssd auth is used -- You received this bug notification because you are a member of DX Packages, which is subscribed to accountsservice in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1246662 Title: Gnome Shell won't lock and ask for password when sssd auth is used Status in D-Bus interfaces for querying and manipulating user account information: Unknown Status in “accountsservice” package in Ubuntu: New Bug description: I use sssd to authenticate users, and due to a change introduced in accountsservice on unlock, the desktop is shown immediately wqith no password entry. Upstream has a patch here: https://bugzilla.gnome.org/show_bug.cgi?id=708997 Please apply ASAP. I tested the patch with a dpkg-buildpackage local install. It works. To manage notifications about this bug go to: https://bugs.launchpad.net/accountsservice/+bug/1246662/+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 1245136] Re: Super+Space and Shift+Super+Space hotkeys for keyboard layout switching do not work in Saucy and Unity session
Installed all latest updates (gnome-control-center 1:3.6.3-0ubuntu45, gnome-settings-daemon3.8.5-0ubuntu11.1) and bug is still here. It also exists in Guest session. -- 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/1245136 Title: Super+Space and Shift+Super+Space hotkeys for keyboard layout switching do not work in Saucy and Unity session Status in “unity” package in Ubuntu: Incomplete Bug description: On clean Ubuntu 13.10 install with enabled proposed updates Super+Space and Shift+Super+Space are default options for keyboard layout change. But they do not work in Unity session. -- For other layout switching problems introduced in Ubuntu 13.10 you can see bug 1218322. -- ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: unity 7.1.2+13.10.20131014.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6 Uname: Linux 3.11.0-13-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.12.5-0ubuntu2.1 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Sun Oct 27 12:39:30 2013 InstallationDate: Installed on 2013-10-20 (6 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release i386 (20131016.1) MarkForUpload: True 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/1245136/+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 1079810] Re: indicator-sound under XFCE: No way to change device
What is the official workaround for people who have multiple sound devices? There must be a lot of people in this situation (i.e. everyone with USB headphones). -- 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/1079810 Title: indicator-sound under XFCE: No way to change device Status in “indicator-sound” package in Ubuntu: Won't Fix Bug description: When using indicator-sound under XFCE, there is no discernable way for a user to change the device whose volume it represents/controls. If you select 'Preferences', as you would to make this change when using Unity, you are taken to pavucontrol - which has no way to select a device for the control. To manually work around this, you must issue 'sudo gnome-control- center sound' (The sound, bluetooth, and other control center apps don't appear to be visible/accessible without sudo) and change the device. Either indicator-sound should dynamically iterate the devices and give you a chance to select them from its context menu, or pavucontrol needs a way to to change the device, or preferences should fire off the equivalent of 'sudo gnome-control-center sound' (preferably in a way that the user doesn't have to enter their password just to get to the sound preferences). I think the first of the three options is the best, because you wouldn't even need to show the devices in the menu if there were only one - and it would speed up access for people with multiple devices not only under XFCE but under Unity as well. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/1079810/+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 1246662] Re: Gnome Shell won't lock and ask for password when sssd auth is used
** Changed in: accountsservice Status: Unknown = New ** Changed in: accountsservice Importance: Unknown = High -- You received this bug notification because you are a member of DX Packages, which is subscribed to accountsservice in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1246662 Title: Gnome Shell won't lock and ask for password when sssd auth is used Status in D-Bus interfaces for querying and manipulating user account information: New Status in “accountsservice” package in Ubuntu: New Bug description: I use sssd to authenticate users, and due to a change introduced in accountsservice on unlock, the desktop is shown immediately wqith no password entry. Upstream has a patch here: https://bugzilla.gnome.org/show_bug.cgi?id=708997 Please apply ASAP. I tested the patch with a dpkg-buildpackage local install. It works. To manage notifications about this bug go to: https://bugs.launchpad.net/accountsservice/+bug/1246662/+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 1222667] Re: indicator-datetime time stays at 12:10
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: indicator-datetime (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-datetime in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1222667 Title: indicator-datetime time stays at 12:10 Status in “indicator-datetime” package in Ubuntu: Confirmed Bug description: indicator-datetime is showing 12:10 PM regardless of the time of day or what date outputs in CLI ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: indicator-datetime 13.10.0+13.10.20130903-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-5.11-generic 3.11.0 Uname: Linux 3.11.0-5-generic x86_64 ApportVersion: 2.12.1-0ubuntu3 Architecture: amd64 Date: Sun Sep 8 23:37:32 2013 EcryptfsInUse: Yes InstallationDate: Installed on 2013-07-27 (44 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MarkForUpload: True SourcePackage: indicator-datetime UpgradeStatus: Upgraded to saucy on 2013-07-27 (44 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1222667/+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 1003950] Re: launcher does not show minimized update manager while clicked
I am seeing this bug on Ubuntu 13.10. This was upgraded from 13.04, on an acer laptop with intel 945GM graphics. This bug has been present over several upgrades of Ubuntu/Unity already. -- 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/1003950 Title: launcher does not show minimized update manager while clicked Status in Unity: Fix Released Status in Unity 5.0 series: Confirmed Status in Unity 6.0 series: Confirmed Status in “unity” package in Ubuntu: Fix Released Status in “unity” source package in Precise: Confirmed Status in “unity” source package in Quantal: Confirmed Bug description: Update manager is showing up in the dock but I can click on the icon all day and nothing happens. Similarly if I do Super-S or Super-W it doesn't show up anywhere. Even if I alt-tab to the application nothing shows up. This happens only when update manager runs on its own. If I kill it and then launch it myself it comes to the foreground just fine. I'm not 100% sure whether this is a unity, compiz, or update-manager bug but so far my bet is on unity. =Original Report= Bug #877444 is showing again in latest updates, please re-open it. This is the exact same problem. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1003950/+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 1195291] Re: unity-panel-service crashed with SIGSEGV in g_closure_invoke()
Since the bug status is invalid for the Ubuntu package, it is also for the One Hundred Papercuts project. ** Changed in: hundredpapercuts Status: Confirmed = Invalid ** Changed in: hundredpapercuts Assignee: Papercuts Ninja (papercuts-ninja) = (unassigned) -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-sound in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1195291 Title: unity-panel-service crashed with SIGSEGV in g_closure_invoke() Status in One Hundred Papercuts: Invalid Status in “indicator-sound” package in Ubuntu: Invalid Bug description: It seems sound indicator crashed when I was moving my mouse pointer from one indicator to another. This failure has also caused other indicators not to show the menu content until Apport reported sound- indicator crash (~2 seconds). ProblemType: Crash DistroRelease: Ubuntu 13.10 Package: indicator-sound 12.10.2daily13.06.07-0ubuntu1 ProcVersionSignature: Ubuntu 3.9.0-7.15-generic 3.9.7 Uname: Linux 3.9.0-7-generic x86_64 ApportVersion: 2.10.2-0ubuntu2 Architecture: amd64 CrashCounter: 1 Date: Thu Jun 27 14:16:35 2013 ExecutablePath: /usr/lib/unity/unity-panel-service InstallationDate: Installed on 2013-06-16 (10 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha amd64 (20130615) MarkForUpload: True ProcCmdline: /usr/lib/unity/unity-panel-service SegvAnalysis: Segfault happened at: 0x7f761e95b986:cmp%rax,(%rdx) PC (0x7f761e95b986) ok source %rax ok destination (%rdx) (0x) not located in a known VMA region (needed writable region)! SegvReason: writing unknown VMA Signal: 11 SourcePackage: indicator-sound StacktraceTop: ?? () from /usr/lib/indicators3/7/libsoundmenu.so g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_emit () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: unity-panel-service crashed with SIGSEGV in g_closure_invoke() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1195291/+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 1195291] Re: unity-panel-service crashed with SIGSEGV in g_closure_invoke()
Since the bug priority is high for the Ubuntu package, it is also for the One Hundred Papercuts project. ** Changed in: hundredpapercuts Importance: Undecided = High -- 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/1195291 Title: unity-panel-service crashed with SIGSEGV in g_closure_invoke() Status in One Hundred Papercuts: Invalid Status in “indicator-sound” package in Ubuntu: Invalid Bug description: It seems sound indicator crashed when I was moving my mouse pointer from one indicator to another. This failure has also caused other indicators not to show the menu content until Apport reported sound- indicator crash (~2 seconds). ProblemType: Crash DistroRelease: Ubuntu 13.10 Package: indicator-sound 12.10.2daily13.06.07-0ubuntu1 ProcVersionSignature: Ubuntu 3.9.0-7.15-generic 3.9.7 Uname: Linux 3.9.0-7-generic x86_64 ApportVersion: 2.10.2-0ubuntu2 Architecture: amd64 CrashCounter: 1 Date: Thu Jun 27 14:16:35 2013 ExecutablePath: /usr/lib/unity/unity-panel-service InstallationDate: Installed on 2013-06-16 (10 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha amd64 (20130615) MarkForUpload: True ProcCmdline: /usr/lib/unity/unity-panel-service SegvAnalysis: Segfault happened at: 0x7f761e95b986:cmp%rax,(%rdx) PC (0x7f761e95b986) ok source %rax ok destination (%rdx) (0x) not located in a known VMA region (needed writable region)! SegvReason: writing unknown VMA Signal: 11 SourcePackage: indicator-sound StacktraceTop: ?? () from /usr/lib/indicators3/7/libsoundmenu.so g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_emit () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: unity-panel-service crashed with SIGSEGV in g_closure_invoke() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1195291/+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 1003950] Re: launcher does not show minimized update manager while clicked
It's remained broken here as well through-out the 13.10 cycle. Here it's fglrx. -- 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/1003950 Title: launcher does not show minimized update manager while clicked Status in Unity: Fix Released Status in Unity 5.0 series: Confirmed Status in Unity 6.0 series: Confirmed Status in “unity” package in Ubuntu: Fix Released Status in “unity” source package in Precise: Confirmed Status in “unity” source package in Quantal: Confirmed Bug description: Update manager is showing up in the dock but I can click on the icon all day and nothing happens. Similarly if I do Super-S or Super-W it doesn't show up anywhere. Even if I alt-tab to the application nothing shows up. This happens only when update manager runs on its own. If I kill it and then launch it myself it comes to the foreground just fine. I'm not 100% sure whether this is a unity, compiz, or update-manager bug but so far my bet is on unity. =Original Report= Bug #877444 is showing again in latest updates, please re-open it. This is the exact same problem. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1003950/+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 830348] Re: desktop contents briefly visible on resume from suspend before lock dialog
I have this bug still on 13.10 64bit. Run Samsung Laptop with ssd, so the monitor will only show up shortly, but still enoght time to see what website I was visiting. -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity-2d in Ubuntu. https://bugs.launchpad.net/bugs/830348 Title: desktop contents briefly visible on resume from suspend before lock dialog Status in Compiz: New Status in Unity 2D: Confirmed Status in “gnome-screensaver” package in Ubuntu: Incomplete Status in “unity-2d” package in Ubuntu: Confirmed Bug description: This seems like a recent regression on Oneiric (or perhaps I haven't noticed it before): On resume from suspend, the contents of the desktop are often briefly visible before being hidden behind the lock screen. This is a security problem if there happens to be sensitive information on the screen. =Analysis from mdeslaur= This is likely what happens: 1- Something grabs mouse: ie: virtual machine window, or GTK menu in an application or an indicator 2- Screensaver attempts to start, but cannot get exclusive lock on mouse 3- DPMS turns monitor black 4- User moves mouse, which turns the screen back on 5- Mouse movement causes mouse to get ungrabbed by vm window or gtk menu 6- Screensaver can now grab mouse, and starts This is all related to the fact that X does not have an API that will let the screensaver tell an application to release mouse and keyboard grabs. To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/830348/+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 1070421] Re: Unable to remove icon from menuitem
** Changed in: qutim Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-messages in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1070421 Title: Unable to remove icon from menuitem Status in The Messaging Menu: Fix Released Status in Multiplatform instant messenger: Fix Released Status in “indicator-messages” package in Ubuntu: Fix Released Status in “indicator-messages” source package in Quantal: Fix Committed Bug description: Impact: It's not possible to remove icons once added Test Case: - download the file from comment #4 - Compile with: gcc reproduce-lp1070421.c -o testcase `pkg-config --cflags --libs messaging-menu` - Something happened will appear below the Empathy entry in the messaging menu. Without the fix to this bug, an icon-not-found icon will be displayed. With the fix, no icon should appear. Regression Potential: Limited, it makes work a case which was broken, if the fix is not correct it would keep not working --- At the moment if I create some Messaging Menu menuitem with no icon (GIcon *icon = NULL), it is created with no icon, as it is supposed to be. Then I set some icon with messaging_menu_app_set_source_icon, and later I want to remove it. I call messaging_menu_app_set_source_icon again, providing NULL as pointer to icon, and icon is not removed, but is set to some icon-not-found icon (I don't know real name for that icon). So the only way to remove icon from source is to completely remove it and create again. I suppose that it is a bug. To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-messages/+bug/1070421/+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 1244237] Re: Ubuntu 13.04 Unity desktop background smears when dragging windows
Mmm, I have 12.04 at home on my laptop and have not had the problem, I will check and see that kernel level it is, though I normally apply updates when they are offered. I have experimented a little more today. I powered off and waited a few minutes, then on again and no smearing, even having started Nemo. And I even got my desktop image. About an hour ago Evolution got stuck so I closed all my apps, logged out and back in again and got smearing. I can tell because the Unity side bar and edges of the screen sometime have a line around or at one edge. Just now I powered off again, and went to make coffee. When I came back I switched on again and no smearing (but no desktop image, just black). Let me just start Nemo ... argh, smearing is back! Still not convinced it has anything to do with Nemo though. -- 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/1244237 Title: Ubuntu 13.04 Unity desktop background smears when dragging windows Status in “unity” package in Ubuntu: Confirmed Bug description: In the last week I have found that my desktop background is not refreshed when I drag windows across the screen. This also happens when windows are minimised or closed. It is especially noticeable when compiz animations are used as the window shrink/blur remains on areas of the screen where only the background shows. It has been reported on AskUbuntu with the title of 'Unity desktop smears (doesn't refresh) and shows no wallpaper' and one contributor says it doesn't happen with Cinnamon (though their post was deleted as not being an answer, as was mine). My wallpaper does not show either, even after I changed it, and it used to. My hardware it AMD A10-5700 with 7660D graphics on Ubuntu 13.04 with latest updates. I am using the fglrx-updates driver. Others (on AskUbuntu) tried different graphics drivers but it didn't help. I have not tried with 13.10. Screen shot attached. Thanks. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: unity 7.0.0daily13.06.19~13.04-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-32.47-generic 3.8.13.10 Uname: Linux 3.8.0-32-generic x86_64 NonfreeKernelModules: fglrx .tmp.unity.support.test.0: ApportVersion: 2.9.2-0ubuntu8.3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Thu Oct 24 14:46:12 2013 DistUpgraded: Fresh install DistroCodename: raring DistroVariant: ubuntu DkmsStatus: fglrx-updates, 9.012, 3.8.0-32-generic, x86_64: installed virtualbox, 4.2.10, 3.8.0-32-generic, x86_64: installed EcryptfsInUse: Yes GraphicsCard: Advanced Micro Devices [AMD] nee ATI Trinity [Radeon HD 7660D] [1002:9901] (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. Device [1462:7721] InstallationDate: Installed on 2013-04-06 (200 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Alpha amd64 (20130402.1) JockeyStatus: kmod:fglrx - Video driver for the AMD graphics accelerators (Proprietary, Disabled, Not in use) kmod:fglrx_updates - ATI Fire GL (Proprietary, Enabled, Not in use) MachineType: MSI MS-7721 MarkForUpload: True ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-32-generic root=UUID=be7626d6-266e-4846-b338-8aa982b96cee ro quiet splash vt.handoff=7 SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/14/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V10.2 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: FM2-A85XMA-P33 (MS-7721) dmi.board.vendor: MSI dmi.board.version: 3.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 3.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV10.2:bd12/14/2012:svnMSI:pnMS-7721:pvr3.0:rvnMSI:rnFM2-A85XMA-P33(MS-7721):rvr3.0:cvnMSI:ct3:cvr3.0: dmi.product.name: MS-7721 dmi.product.version: 3.0 dmi.sys.vendor: MSI version.compiz: compiz 1:0.9.9~daily13.06.19~13.04-0ubuntu1 version.fglrx-installer: fglrx-installer N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.43-0ubuntu1.1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.1.4-0ubuntu0.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.1.4-0ubuntu0.1 version.xserver-xorg-core: xserver-xorg-core 2:1.13.3-0ubuntu6.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2b2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.1.0-0ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.6-0ubuntu4.3 version.xserver-xorg-video-nouveau:
[Dx-packages] [Bug 1165420] Re: Unable to access indicators from HUD
Yes, this is a bug, but not one in the messaging menu. The messaging service exports a menu which is shown by the panel. The HUD can access the same model on the bus, but doesn't. ** No longer affects: indicator-messages -- 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/1165420 Title: Unable to access indicators from HUD Status in Ayatana Design: Confirmed Status in Unity HUD: Confirmed Status in “hud” package in Ubuntu: Confirmed Bug description: In Ubuntu 12.10 I was able to use HUD to access Messaging menu and Gwibber's Update Status option there, making status updates to Twitter easy and fast. I could also use HUD to change my status in Empathy from Available to Busy and vice-versa. In Ubuntu 13.04 Beta HUD no longer finds the Update Status option when typing Update Status or Update Also writing Available Away or Busy no longer gives any results. Other indicators however are accessible and I can use HUD to Suspend my computer or to view Skype status or Ubuntu one indicator options. Repeating: 1. Press alt key to start HUD 2. Write Update status or Available What was expected: HUD should have shown options ether from Gwibber to Update Status or Empathy to change status to Available both available from the messaging indicator. What happened: HUD didn't find any results. Notes: I have Ubuntu 13.04 Beta 64bit upgraded from Ubuntu 12.10 64bits and I'm using proprietary fglrx drivers. To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/1165420/+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 1199877] Re: unity-panel-service memory leak and 100% CPU usage
** Branch linked: lp:indicator-appmenu -- 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/1199877 Title: unity-panel-service memory leak and 100% CPU usage Status in The Ubuntu Power Consumption Project: New Status in Unity: In Progress Status in Unity 7.1 series: In Progress Status in “gtk+3.0” package in Ubuntu: In Progress Status in “unity” package in Ubuntu: Triaged Status in “gtk+3.0” source package in Saucy: In Progress Status in “unity” source package in Saucy: Triaged Bug description: Impact: high CPU/memory usage from unity-panel-service Test case: Open a large image in the GIMP and activate a lot of items from the global menu. Using shortcuts is enough and faster to reproduce this bug (I've always used Ctrl+A and Ctrl+Shift+A). Memory usage of unity- panel-service increases steadily and it uses a lot of CPU shortly after activating the menu items in a short time. Regression potential: check that the menus are stable/working as they should - Just going about my business on Ubuntu Raring amd64 on an x230 and I heard the fan kick into action. top showed me that unity-panel-service was consuming all the free cycles on one of my CPUs. I killed it before my machine overheated, so I didn't attach a debugger to see why it was totally pegging out a CPU. I'm not sure if this adds any context, but I was using a LibreOffice spreadsheet and I could not insert a table because the menu had lost it's mind, and then I observed the overly loaded CPU a very short while after that. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-consumption/+bug/1199877/+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 1199877] Re: unity-panel-service memory leak and 100% CPU usage
** Branch linked: lp:~bregma/indicator-appmenu/lp-1199877 -- 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/1199877 Title: unity-panel-service memory leak and 100% CPU usage Status in The Application Menu: Fix Committed Status in Application Menu Indicator 13.10 series: In Progress Status in The Ubuntu Power Consumption Project: New Status in Unity: In Progress Status in Unity 7.1 series: In Progress Status in “gtk+3.0” package in Ubuntu: In Progress Status in “indicator-appmenu” package in Ubuntu: Fix Committed Status in “unity” package in Ubuntu: Triaged Status in “gtk+3.0” source package in Saucy: In Progress Status in “indicator-appmenu” source package in Saucy: In Progress Status in “unity” source package in Saucy: Triaged Bug description: Impact: high CPU/memory usage from unity-panel-service Test case: Open a large image in the GIMP and activate a lot of items from the global menu. Using shortcuts is enough and faster to reproduce this bug (I've always used Ctrl+A and Ctrl+Shift+A). Memory usage of unity- panel-service increases steadily and it uses a lot of CPU shortly after activating the menu items in a short time. Regression potential: check that the menus are stable/working as they should - Just going about my business on Ubuntu Raring amd64 on an x230 and I heard the fan kick into action. top showed me that unity-panel-service was consuming all the free cycles on one of my CPUs. I killed it before my machine overheated, so I didn't attach a debugger to see why it was totally pegging out a CPU. I'm not sure if this adds any context, but I was using a LibreOffice spreadsheet and I could not insert a table because the menu had lost it's mind, and then I observed the overly loaded CPU a very short while after that. To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-appmenu/+bug/1199877/+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 664647] Re: All menu item text is invisible in Adobe Reader
This is still broken in ubuntu 13.10 + acroread 9.5.5 -- You received this bug notification because you are a member of DX Packages, which is subscribed to appmenu-gtk in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/664647 Title: All menu item text is invisible in Adobe Reader Status in Application menu module for GTK+: Confirmed Status in Unity Foundations: Confirmed Status in “acroread” package in Ubuntu: Confirmed Status in “appmenu-gtk” package in Ubuntu: Invalid Bug description: indicator-appmenu 0.0.13-0ubuntu1, Ubuntu 10.10 beta appmenu-gtk 0.2.0-0ubuntu1, Ubuntu 11.04 1. Launch Adobe Reader. 2. Open any menu. What you see: All items present, and all separators visible, but the item text is invisible. https://launchpadlibrarian.net/59735690/acroread.png What you should see: The menu items are visible. To manage notifications about this bug go to: https://bugs.launchpad.net/appmenu-gtk/+bug/664647/+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 1199877] Re: unity-panel-service memory leak and 100% CPU usage
Hello Colin, or anyone else affected, Accepted gtk+3.0 into saucy-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/gtk+3.0/3.8.6-0ubuntu2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Tags added: verification-needed -- 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/1199877 Title: unity-panel-service memory leak and 100% CPU usage Status in The Application Menu: Fix Committed Status in Application Menu Indicator 13.10 series: In Progress Status in The Ubuntu Power Consumption Project: New Status in Unity: Invalid Status in “gtk+3.0” package in Ubuntu: In Progress Status in “indicator-appmenu” package in Ubuntu: In Progress Status in “unity” package in Ubuntu: Invalid Status in “gtk+3.0” source package in Saucy: Fix Committed Status in “indicator-appmenu” source package in Saucy: In Progress Bug description: Impact: high CPU/memory usage from unity-panel-service Test case: Open a large image in the GIMP and activate a lot of items from the global menu. Using shortcuts is enough and faster to reproduce this bug (I've always used Ctrl+A and Ctrl+Shift+A). Memory usage of unity- panel-service increases steadily and it uses a lot of CPU shortly after activating the menu items in a short time. Regression potential: check that the menus are stable/working as they should - Just going about my business on Ubuntu Raring amd64 on an x230 and I heard the fan kick into action. top showed me that unity-panel-service was consuming all the free cycles on one of my CPUs. I killed it before my machine overheated, so I didn't attach a debugger to see why it was totally pegging out a CPU. I'm not sure if this adds any context, but I was using a LibreOffice spreadsheet and I could not insert a table because the menu had lost it's mind, and then I observed the overly loaded CPU a very short while after that. To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-appmenu/+bug/1199877/+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 1199877] Re: unity-panel-service memory leak and 100% CPU usage
** Changed in: indicator-appmenu (Ubuntu) Status: Fix Committed = In Progress -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages, dx-packages https://bugs.launchpad.net/bugs/1199877 Title: unity-panel-service memory leak and 100% CPU usage Status in The Application Menu: Fix Committed Status in Application Menu Indicator 13.10 series: In Progress Status in The Ubuntu Power Consumption Project: New Status in Unity: Invalid Status in “gtk+3.0” package in Ubuntu: In Progress Status in “indicator-appmenu” package in Ubuntu: In Progress Status in “unity” package in Ubuntu: Invalid Status in “gtk+3.0” source package in Saucy: Fix Committed Status in “indicator-appmenu” source package in Saucy: In Progress Bug description: Impact: high CPU/memory usage from unity-panel-service Test case: Open a large image in the GIMP and activate a lot of items from the global menu. Using shortcuts is enough and faster to reproduce this bug (I've always used Ctrl+A and Ctrl+Shift+A). Memory usage of unity- panel-service increases steadily and it uses a lot of CPU shortly after activating the menu items in a short time. Regression potential: check that the menus are stable/working as they should - Just going about my business on Ubuntu Raring amd64 on an x230 and I heard the fan kick into action. top showed me that unity-panel-service was consuming all the free cycles on one of my CPUs. I killed it before my machine overheated, so I didn't attach a debugger to see why it was totally pegging out a CPU. I'm not sure if this adds any context, but I was using a LibreOffice spreadsheet and I could not insert a table because the menu had lost it's mind, and then I observed the overly loaded CPU a very short while after that. To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-appmenu/+bug/1199877/+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 1199877] Re: unity-panel-service memory leak and 100% CPU usage
** Also affects: indicator-appmenu (Ubuntu) Importance: Undecided Status: New ** Changed in: indicator-appmenu (Ubuntu) Status: New = Fix Committed ** Changed in: indicator-appmenu (Ubuntu Saucy) Status: New = In Progress ** Also affects: indicator-appmenu Importance: Undecided Status: New ** Also affects: indicator-appmenu/13.10 Importance: Undecided Status: New ** Changed in: indicator-appmenu Status: New = Fix Committed ** Changed in: indicator-appmenu/13.10 Status: New = In Progress ** Changed in: unity Milestone: 7.2.0 = None ** Changed in: unity/7.1 Milestone: 7.1.2 = None ** Changed in: unity (Ubuntu) Assignee: Stephen M. Webb (bregma) = (unassigned) ** No longer affects: unity (Ubuntu Saucy) ** Changed in: unity (Ubuntu) Status: Triaged = Invalid ** Changed in: unity/7.1 Assignee: Stephen M. Webb (bregma) = (unassigned) ** No longer affects: unity/7.1 ** Changed in: unity Status: In Progress = Invalid ** Changed in: unity Assignee: Stephen M. Webb (bregma) = (unassigned) ** Changed in: indicator-appmenu/13.10 Assignee: (unassigned) = Stephen M. Webb (bregma) ** Changed in: indicator-appmenu/13.10 Importance: Undecided = High ** Changed in: indicator-appmenu Importance: Undecided = High ** Changed in: indicator-appmenu (Ubuntu) Importance: Undecided = High ** Changed in: indicator-appmenu (Ubuntu Saucy) 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, dx-packages https://bugs.launchpad.net/bugs/1199877 Title: unity-panel-service memory leak and 100% CPU usage Status in The Application Menu: Fix Committed Status in Application Menu Indicator 13.10 series: In Progress Status in The Ubuntu Power Consumption Project: New Status in Unity: Invalid Status in “gtk+3.0” package in Ubuntu: In Progress Status in “indicator-appmenu” package in Ubuntu: In Progress Status in “unity” package in Ubuntu: Invalid Status in “gtk+3.0” source package in Saucy: Fix Committed Status in “indicator-appmenu” source package in Saucy: In Progress Bug description: Impact: high CPU/memory usage from unity-panel-service Test case: Open a large image in the GIMP and activate a lot of items from the global menu. Using shortcuts is enough and faster to reproduce this bug (I've always used Ctrl+A and Ctrl+Shift+A). Memory usage of unity- panel-service increases steadily and it uses a lot of CPU shortly after activating the menu items in a short time. Regression potential: check that the menus are stable/working as they should - Just going about my business on Ubuntu Raring amd64 on an x230 and I heard the fan kick into action. top showed me that unity-panel-service was consuming all the free cycles on one of my CPUs. I killed it before my machine overheated, so I didn't attach a debugger to see why it was totally pegging out a CPU. I'm not sure if this adds any context, but I was using a LibreOffice spreadsheet and I could not insert a table because the menu had lost it's mind, and then I observed the overly loaded CPU a very short while after that. To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-appmenu/+bug/1199877/+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 1199877] Re: unity-panel-service memory leak and 100% CPU usage
** Changed in: gtk+3.0 (Ubuntu Saucy) 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, dx-packages https://bugs.launchpad.net/bugs/1199877 Title: unity-panel-service memory leak and 100% CPU usage Status in The Application Menu: Fix Committed Status in Application Menu Indicator 13.10 series: In Progress Status in The Ubuntu Power Consumption Project: New Status in Unity: Invalid Status in “gtk+3.0” package in Ubuntu: In Progress Status in “indicator-appmenu” package in Ubuntu: In Progress Status in “unity” package in Ubuntu: Invalid Status in “gtk+3.0” source package in Saucy: Fix Committed Status in “indicator-appmenu” source package in Saucy: In Progress Bug description: Impact: high CPU/memory usage from unity-panel-service Test case: Open a large image in the GIMP and activate a lot of items from the global menu. Using shortcuts is enough and faster to reproduce this bug (I've always used Ctrl+A and Ctrl+Shift+A). Memory usage of unity- panel-service increases steadily and it uses a lot of CPU shortly after activating the menu items in a short time. Regression potential: check that the menus are stable/working as they should - Just going about my business on Ubuntu Raring amd64 on an x230 and I heard the fan kick into action. top showed me that unity-panel-service was consuming all the free cycles on one of my CPUs. I killed it before my machine overheated, so I didn't attach a debugger to see why it was totally pegging out a CPU. I'm not sure if this adds any context, but I was using a LibreOffice spreadsheet and I could not insert a table because the menu had lost it's mind, and then I observed the overly loaded CPU a very short while after that. To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-appmenu/+bug/1199877/+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 1240141] Re: List of client scopes is not up-to-date
Fix committed into lp:libunity at revision None, scheduled for release in libunity, milestone 7.0.0 -- You received this bug notification because you are a member of DX Packages, which is subscribed to libunity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1240141 Title: List of client scopes is not up-to-date Status in LibUnity: Fix Committed Status in “libunity” package in Ubuntu: Fix Released Bug description: The list of scopes in /usr/share/unity/client-scopes.json is not up- to-date with that's provided by the packages, there's just three differences, but we should still fix it, so the server gets correct information. To manage notifications about this bug go to: https://bugs.launchpad.net/libunity/+bug/1240141/+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 1199877] Re: unity-panel-service memory leak and 100% CPU usage
Fix committed into lp:indicator-appmenu/13.10 at revision None, scheduled for release in indicator-appmenu, milestone Unknown -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages, dx-packages https://bugs.launchpad.net/bugs/1199877 Title: unity-panel-service memory leak and 100% CPU usage Status in The Application Menu: Fix Committed Status in Application Menu Indicator 13.10 series: In Progress Status in The Ubuntu Power Consumption Project: New Status in Unity: Invalid Status in “gtk+3.0” package in Ubuntu: In Progress Status in “indicator-appmenu” package in Ubuntu: In Progress Status in “unity” package in Ubuntu: Invalid Status in “gtk+3.0” source package in Saucy: Fix Committed Status in “indicator-appmenu” source package in Saucy: In Progress Bug description: Impact: high CPU/memory usage from unity-panel-service Test case: Open a large image in the GIMP and activate a lot of items from the global menu. Using shortcuts is enough and faster to reproduce this bug (I've always used Ctrl+A and Ctrl+Shift+A). Memory usage of unity- panel-service increases steadily and it uses a lot of CPU shortly after activating the menu items in a short time. Regression potential: check that the menus are stable/working as they should - Just going about my business on Ubuntu Raring amd64 on an x230 and I heard the fan kick into action. top showed me that unity-panel-service was consuming all the free cycles on one of my CPUs. I killed it before my machine overheated, so I didn't attach a debugger to see why it was totally pegging out a CPU. I'm not sure if this adds any context, but I was using a LibreOffice spreadsheet and I could not insert a table because the menu had lost it's mind, and then I observed the overly loaded CPU a very short while after that. To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-appmenu/+bug/1199877/+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 664647] Re: All menu item text is invisible in Adobe Reader
** Branch linked: lp:~charlesk/unity-gtk-module/lp-664647 ** Branch linked: lp:~charlesk/unity-gtk-module/lp-664647 -- You received this bug notification because you are a member of DX Packages, which is subscribed to appmenu-gtk in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/664647 Title: All menu item text is invisible in Adobe Reader Status in Application menu module for GTK+: Confirmed Status in Unity Foundations: Confirmed Status in Unity GTK+ module: In Progress Status in “acroread” package in Ubuntu: Confirmed Status in “appmenu-gtk” package in Ubuntu: Invalid Bug description: indicator-appmenu 0.0.13-0ubuntu1, Ubuntu 10.10 beta appmenu-gtk 0.2.0-0ubuntu1, Ubuntu 11.04 1. Launch Adobe Reader. 2. Open any menu. What you see: All items present, and all separators visible, but the item text is invisible. https://launchpadlibrarian.net/59735690/acroread.png What you should see: The menu items are visible. To manage notifications about this bug go to: https://bugs.launchpad.net/appmenu-gtk/+bug/664647/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1246812] Re: Can open Evolution in greeter mode
** Also affects: indicator-datetime Importance: Undecided Status: New ** Changed in: indicator-datetime Status: New = In Progress ** Changed in: indicator-datetime Importance: Undecided = High ** Changed in: indicator-datetime 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/1246812 Title: Can open Evolution in greeter mode Status in The Date and Time Indicator: In Progress Status in “indicator-datetime” package in Ubuntu: New Status in “indicator-datetime” source package in Saucy: New Status in “indicator-datetime” source package in Trusty: New Bug description: You can open evolution from the greeter. To reproduce: 1. Boot to Unity Greeter 2. Click date in the datetime indicator Expected result: Nothing happens Observed result: Evolution first run dialog opens To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-datetime/+bug/1246812/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1199877] Re: unity-panel-service memory leak and 100% CPU usage
** Changed in: indicator-appmenu/13.10 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, dx-packages https://bugs.launchpad.net/bugs/1199877 Title: unity-panel-service memory leak and 100% CPU usage Status in The Application Menu: Fix Committed Status in Application Menu Indicator 13.10 series: Fix Committed Status in The Ubuntu Power Consumption Project: New Status in Unity: Invalid Status in “gtk+3.0” package in Ubuntu: In Progress Status in “indicator-appmenu” package in Ubuntu: In Progress Status in “unity” package in Ubuntu: Invalid Status in “gtk+3.0” source package in Saucy: Fix Committed Status in “indicator-appmenu” source package in Saucy: In Progress Bug description: Impact: high CPU/memory usage from unity-panel-service Test case: Open a large image in the GIMP and activate a lot of items from the global menu. Using shortcuts is enough and faster to reproduce this bug (I've always used Ctrl+A and Ctrl+Shift+A). Memory usage of unity- panel-service increases steadily and it uses a lot of CPU shortly after activating the menu items in a short time. Regression potential: check that the menus are stable/working as they should - Just going about my business on Ubuntu Raring amd64 on an x230 and I heard the fan kick into action. top showed me that unity-panel-service was consuming all the free cycles on one of my CPUs. I killed it before my machine overheated, so I didn't attach a debugger to see why it was totally pegging out a CPU. I'm not sure if this adds any context, but I was using a LibreOffice spreadsheet and I could not insert a table because the menu had lost it's mind, and then I observed the overly loaded CPU a very short while after that. To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-appmenu/+bug/1199877/+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 664647] Re: All menu item text is invisible in Adobe Reader
Fix committed into lp:unity-gtk-module at revision None, scheduled for release in unity-gtk-module, milestone Unknown ** Changed in: unity-gtk-module Status: In Progress = Fix Committed -- You received this bug notification because you are a member of DX Packages, which is subscribed to appmenu-gtk in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/664647 Title: All menu item text is invisible in Adobe Reader Status in Application menu module for GTK+: Confirmed Status in Unity Foundations: Confirmed Status in Unity GTK+ module: Fix Committed Status in “acroread” package in Ubuntu: Confirmed Status in “appmenu-gtk” package in Ubuntu: Invalid Bug description: indicator-appmenu 0.0.13-0ubuntu1, Ubuntu 10.10 beta appmenu-gtk 0.2.0-0ubuntu1, Ubuntu 11.04 1. Launch Adobe Reader. 2. Open any menu. What you see: All items present, and all separators visible, but the item text is invisible. https://launchpadlibrarian.net/59735690/acroread.png What you should see: The menu items are visible. To manage notifications about this bug go to: https://bugs.launchpad.net/appmenu-gtk/+bug/664647/+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 1246536] Re: segfault in menu_hidden()
** Branch linked: lp:~larsu/ido/lp1246536 -- 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/1246536 Title: segfault in menu_hidden() Status in Sound Menu: New Status in “indicator-sound” package in Ubuntu: New Bug description: Using saucy stable, happened a few times today while using the slider, muting/unmuting, using play multimedia key/mpris to start/stop rhythmbox #0 menu_hidden (menu=0x96882c0, scale=0x97b8110) at idoscalemenuitem.c:640 #1 0xb6e454d3 in g_cclosure_marshal_VOID__VOID (closure=0x97b5818, return_value=0x0, n_param_values=1, param_values=0xbff2e970, invocation_hint=0xbff2e91c, marshal_data=0x0) at /build/buildd/glib2.0-2.38.1/./gobject/gmarshal.c:85 #2 0xb6e438ae in g_closure_invoke (closure=0x97b5818, return_value=return_value@entry=0x0, n_param_values=1, param_values=param_values@entry=0xbff2e970, invocation_hint=invocation_hint@entry=0xbff2e91c) at /build/buildd/glib2.0-2.38.1/./gobject/gclosure.c:777 #3 0xb6e55df9 in signal_emit_unlocked_R (node=node@entry=0x9562ec8, detail=0, instance=0x96882c0, emission_return=emission_return@entry=0x0, instance_and_params=0xbff2e970) at /build/buildd/glib2.0-2.38.1/./gobject/gsignal.c:3586 #4 0xb6e5d753 in g_signal_emit_valist (instance=instance@entry=0x96882c0, signal_id=signal_id@entry=5, detail=detail@entry=0, var_args=var_args@entry=0xbff2eaac h\027;\267) at /build/buildd/glib2.0-2.38.1/./gobject/gsignal.c:3330 #5 0xb6e5d9e3 in g_signal_emit (instance=instance@entry=0x96882c0, signal_id=5, detail=detail@entry=0) at /build/buildd/glib2.0-2.38.1/./gobject/gsignal.c:3386 #6 0xb73b1820 in gtk_widget_hide (widget=widget@entry=0x96882c0) at /tmp/gtk+3/build-area/gtk+3.0-3.8.6/./gtk/gtkwidget.c:4268 #7 0xb7278678 in gtk_menu_popdown (menu=menu@entry=0x96882c0) at /tmp/gtk+3/build-area/gtk+3.0-3.8.6/./gtk/gtkmenu.c:1848 #8 0xb727877d in gtk_menu_deactivate (menu_shell=0x96882c0) at /tmp/gtk+3/build-area/gtk+3.0-3.8.6/./gtk/gtkmenu.c:4546 #9 0xb6e454d3 in g_cclosure_marshal_VOID__VOID (closure=0x956c640, return_value=0x0, n_param_values=1, param_values=0xbff2ec90, invocation_hint=0xbff2ec3c, marshal_data=0xb7278700 gtk_menu_deactivate) at /build/buildd/glib2.0-2.38.1/./gobject/gmarshal.c:85 #10 0xb6e423d4 in g_type_class_meta_marshal (closure=0x956c640, return_value=0x0, n_param_values=1, param_values=0xbff2ec90, invocation_hint=0xbff2ec3c, marshal_data=0x1ec) at /build/buildd/glib2.0-2.38.1/./gobject/gclosure.c:970 #11 0xb6e438ae in g_closure_invoke (closure=closure@entry=0x956c640, return_value=return_value@entry=0x0, n_param_values=1, param_values=param_values@entry=0xbff2ec90, invocation_hint=invocation_hint@entry=0xbff2ec3c) at /build/buildd/glib2.0-2.38.1/./gobject/gclosure.c:777 #12 0xb6e5549c in signal_emit_unlocked_R (node=node@entry=0x956d3b8, detail=0, instance=0x96882c0, emission_return=emission_return@entry=0x0, instance_and_params=0xbff2ec90) at /build/buildd/glib2.0-2.38.1/./gobject/gsignal.c:3516 #13 0xb6e5d753 in g_signal_emit_valist (instance=instance@entry=0x96882c0, signal_id=signal_id@entry=82, detail=detail@entry=0, var_args=var_args@entry=0xbff2edcc ) at /build/buildd/glib2.0-2.38.1/./gobject/gsignal.c:3330 #14 0xb6e5d9e3 in g_signal_emit (instance=instance@entry=0x96882c0, signal_id=82, detail=detail@entry=0) at /build/buildd/glib2.0-2.38.1/./gobject/gsignal.c:3386 #15 0xb7282923 in gtk_menu_shell_deactivate (menu_shell=0x96882c0) at /tmp/gtk+3/build-area/gtk+3.0-3.8.6/./gtk/gtkmenushell.c:616 #16 0xb7283202 in gtk_menu_shell_activate_item ( menu_shell=menu_shell@entry=0x96882c0, menu_item=menu_item@entry=0x962a0b8, force_deactivate=force_deactivate@entry=1) at /tmp/gtk+3/build-area/gtk+3.0-3.8.6/./gtk/gtkmenushell.c:1433 #17 0xb7283626 in gtk_menu_shell_button_release (widget=0x96882c0, event=0x9648650) at /tmp/gtk+3/build-area/gtk+3.0-3.8.6/./gtk/gtkmenushell.c:842 #18 0xb7276ce9 in gtk_menu_button_release (widget=0x96882c0, event=0x9648650) at /tmp/gtk+3/build-area/gtk+3.0-3.8.6/./gtk/gtkmenu.c:3391 #19 0xb7267ee6 in _gtk_marshal_BOOLEAN__BOXEDv (closure=0x9563f18, return_value=0xbff2efa8, instance=0x96882c0, args=0xbff2f07c P\206d\t\234\360\362\277\070\243U\t\020\312V\t, marshal_data=0xb7276c60 gtk_menu_button_release, n_params=1, param_types=0x9563f30) at /tmp/gtk+3/build-area/gtk+3.0-3.8.6/./gtk/gtkmarshalers.c:130 #20 0xb6e42287 in g_type_class_meta_marshalv (closure=0x9563f18, return_value=0xbff2efa8, instance=0x96882c0, args=0xbff2f07c
[Dx-packages] [Bug 1246536] Re: segfault in menu_hidden()
** Branch linked: lp:~larsu/ido/lp1246536-13.10 ** 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/1246536 Title: segfault in menu_hidden() Status in Sound Menu: New Status in “indicator-sound” package in Ubuntu: In Progress Bug description: Using saucy stable, happened a few times today while using the slider, muting/unmuting, using play multimedia key/mpris to start/stop rhythmbox #0 menu_hidden (menu=0x96882c0, scale=0x97b8110) at idoscalemenuitem.c:640 #1 0xb6e454d3 in g_cclosure_marshal_VOID__VOID (closure=0x97b5818, return_value=0x0, n_param_values=1, param_values=0xbff2e970, invocation_hint=0xbff2e91c, marshal_data=0x0) at /build/buildd/glib2.0-2.38.1/./gobject/gmarshal.c:85 #2 0xb6e438ae in g_closure_invoke (closure=0x97b5818, return_value=return_value@entry=0x0, n_param_values=1, param_values=param_values@entry=0xbff2e970, invocation_hint=invocation_hint@entry=0xbff2e91c) at /build/buildd/glib2.0-2.38.1/./gobject/gclosure.c:777 #3 0xb6e55df9 in signal_emit_unlocked_R (node=node@entry=0x9562ec8, detail=0, instance=0x96882c0, emission_return=emission_return@entry=0x0, instance_and_params=0xbff2e970) at /build/buildd/glib2.0-2.38.1/./gobject/gsignal.c:3586 #4 0xb6e5d753 in g_signal_emit_valist (instance=instance@entry=0x96882c0, signal_id=signal_id@entry=5, detail=detail@entry=0, var_args=var_args@entry=0xbff2eaac h\027;\267) at /build/buildd/glib2.0-2.38.1/./gobject/gsignal.c:3330 #5 0xb6e5d9e3 in g_signal_emit (instance=instance@entry=0x96882c0, signal_id=5, detail=detail@entry=0) at /build/buildd/glib2.0-2.38.1/./gobject/gsignal.c:3386 #6 0xb73b1820 in gtk_widget_hide (widget=widget@entry=0x96882c0) at /tmp/gtk+3/build-area/gtk+3.0-3.8.6/./gtk/gtkwidget.c:4268 #7 0xb7278678 in gtk_menu_popdown (menu=menu@entry=0x96882c0) at /tmp/gtk+3/build-area/gtk+3.0-3.8.6/./gtk/gtkmenu.c:1848 #8 0xb727877d in gtk_menu_deactivate (menu_shell=0x96882c0) at /tmp/gtk+3/build-area/gtk+3.0-3.8.6/./gtk/gtkmenu.c:4546 #9 0xb6e454d3 in g_cclosure_marshal_VOID__VOID (closure=0x956c640, return_value=0x0, n_param_values=1, param_values=0xbff2ec90, invocation_hint=0xbff2ec3c, marshal_data=0xb7278700 gtk_menu_deactivate) at /build/buildd/glib2.0-2.38.1/./gobject/gmarshal.c:85 #10 0xb6e423d4 in g_type_class_meta_marshal (closure=0x956c640, return_value=0x0, n_param_values=1, param_values=0xbff2ec90, invocation_hint=0xbff2ec3c, marshal_data=0x1ec) at /build/buildd/glib2.0-2.38.1/./gobject/gclosure.c:970 #11 0xb6e438ae in g_closure_invoke (closure=closure@entry=0x956c640, return_value=return_value@entry=0x0, n_param_values=1, param_values=param_values@entry=0xbff2ec90, invocation_hint=invocation_hint@entry=0xbff2ec3c) at /build/buildd/glib2.0-2.38.1/./gobject/gclosure.c:777 #12 0xb6e5549c in signal_emit_unlocked_R (node=node@entry=0x956d3b8, detail=0, instance=0x96882c0, emission_return=emission_return@entry=0x0, instance_and_params=0xbff2ec90) at /build/buildd/glib2.0-2.38.1/./gobject/gsignal.c:3516 #13 0xb6e5d753 in g_signal_emit_valist (instance=instance@entry=0x96882c0, signal_id=signal_id@entry=82, detail=detail@entry=0, var_args=var_args@entry=0xbff2edcc ) at /build/buildd/glib2.0-2.38.1/./gobject/gsignal.c:3330 #14 0xb6e5d9e3 in g_signal_emit (instance=instance@entry=0x96882c0, signal_id=82, detail=detail@entry=0) at /build/buildd/glib2.0-2.38.1/./gobject/gsignal.c:3386 #15 0xb7282923 in gtk_menu_shell_deactivate (menu_shell=0x96882c0) at /tmp/gtk+3/build-area/gtk+3.0-3.8.6/./gtk/gtkmenushell.c:616 #16 0xb7283202 in gtk_menu_shell_activate_item ( menu_shell=menu_shell@entry=0x96882c0, menu_item=menu_item@entry=0x962a0b8, force_deactivate=force_deactivate@entry=1) at /tmp/gtk+3/build-area/gtk+3.0-3.8.6/./gtk/gtkmenushell.c:1433 #17 0xb7283626 in gtk_menu_shell_button_release (widget=0x96882c0, event=0x9648650) at /tmp/gtk+3/build-area/gtk+3.0-3.8.6/./gtk/gtkmenushell.c:842 #18 0xb7276ce9 in gtk_menu_button_release (widget=0x96882c0, event=0x9648650) at /tmp/gtk+3/build-area/gtk+3.0-3.8.6/./gtk/gtkmenu.c:3391 #19 0xb7267ee6 in _gtk_marshal_BOOLEAN__BOXEDv (closure=0x9563f18, return_value=0xbff2efa8, instance=0x96882c0, args=0xbff2f07c P\206d\t\234\360\362\277\070\243U\t\020\312V\t, marshal_data=0xb7276c60 gtk_menu_button_release, n_params=1, param_types=0x9563f30) at /tmp/gtk+3/build-area/gtk+3.0-3.8.6/./gtk/gtkmarshalers.c:130 #20 0xb6e42287 in g_type_class_meta_marshalv (closure=0x9563f18,
[Dx-packages] [Bug 1245495] Re: Rhythmbox controls and track info broken
All of the problems I reported are continuous, they always happen as described and never function properly. The translucent popup notifications are fine, they show track info and album art as expected. The problem with track info and album art is that it is _never_ displayed in the sound menu since installing 13.10. Here is the output of the command that you asked for: ben@xameroth:~$ gdbus call --session --dest org.mpris.MediaPlayer2.rhythmbox --object-path /org/mpris/MediaPlayer2 --method org.freedesktop.DBus.Properties.GetAll 'org.mpris.MediaPlayer2.Player' Error: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.mpris.MediaPlayer2.rhythmbox was not provided by any .service files Can I provide any more information for you? -- 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/1245495 Title: Rhythmbox controls and track info broken Status in Sound Menu: Triaged Status in “indicator-sound” package in Ubuntu: Triaged Bug description: A Rhythmbox section appears in the indicator menu as it should but there are several glitches: When RB isn't running click on the icon in the indicator RB starts as expected :-) When RB is running click on the icon in the indicator RB icon wiggles in launcher but window doesn't come to focus :-( Track info and album art appears in notifications, but is never shown in the sound menu. Regardless of whether RB is running: Sound menu track controls (prev, play/pause, next) do nothing. The play/pause button has a dotted orange ring, which turns to an orange square on mouseover (see screenshots). Ubuntu 13.10 64-bit unity: 7.1.2+13.10.20131014.1-0ubuntu1 indicator-sound: 12.10.2+13.10.20131011-0ubuntu1 rhythmbox: 2.99.1-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-sound/+bug/1245495/+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 1245495] Re: Rhythmbox controls and track info broken
It seems like Rhythmbox wasn't running while you executed that command. If it wasn't, could you please try again with Rhythmbox running? -- 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/1245495 Title: Rhythmbox controls and track info broken Status in Sound Menu: Triaged Status in “indicator-sound” package in Ubuntu: Triaged Bug description: A Rhythmbox section appears in the indicator menu as it should but there are several glitches: When RB isn't running click on the icon in the indicator RB starts as expected :-) When RB is running click on the icon in the indicator RB icon wiggles in launcher but window doesn't come to focus :-( Track info and album art appears in notifications, but is never shown in the sound menu. Regardless of whether RB is running: Sound menu track controls (prev, play/pause, next) do nothing. The play/pause button has a dotted orange ring, which turns to an orange square on mouseover (see screenshots). Ubuntu 13.10 64-bit unity: 7.1.2+13.10.20131014.1-0ubuntu1 indicator-sound: 12.10.2+13.10.20131011-0ubuntu1 rhythmbox: 2.99.1-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-sound/+bug/1245495/+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 1246842] [NEW] libdbusmenu fails to build from source because of test failures
Public bug reported: To reproduce: sudo apt-get build-dep libdbusmenu apt-get source libdbusmenu cd libdbusmenu* fakeroot dpkg-buildpackage Result: nearly all of the tests fail to run properly: make[5]: Entering directory `/home/al/Source/test/libdbusmenu-12.10.3+13.10.20130913/builddir/gtk2/tests' PASS: test-glib-objects-test FAIL: test-glib-events FAIL: test-glib-events-nogroup FAIL: test-glib-layout FAIL: test-glib-properties FAIL: test-glib-proxy PASS: test-glib-simple-items FAIL: test-glib-submenu Each test hangs for about 10 minutes before failing. All of the error logs are the same: DBus daemon: unix:abstract=/tmp/dbus-AwSfBXRDlN,guid=c42d750fb322fd07af809069527290f0 Client: Started with PID: 27013 Server: Started with PID: 27014 (process:27013): LIBDBUSMENU-GLIB-WARNING **: Unable to get session bus: Error sending credentials: Error sending message: Operation not permitted ** (process:27014): ERROR **: Unable to get name 'org.dbusmenu.test' on DBus Server: Exited with status 133 Client: ** (process:27013): DEBUG: Death timer. Oops. Got to: 0 Client: ** (process:27013): DEBUG: Quiting as we're a failure Client: Exited with status 256 Client: Shutting down Server: Shutting down DBus daemon: Shutdown ** Affects: libdbusmenu (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of DX Packages, which is subscribed to libdbusmenu in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1246842 Title: libdbusmenu fails to build from source because of test failures Status in “libdbusmenu” package in Ubuntu: New Bug description: To reproduce: sudo apt-get build-dep libdbusmenu apt-get source libdbusmenu cd libdbusmenu* fakeroot dpkg-buildpackage Result: nearly all of the tests fail to run properly: make[5]: Entering directory `/home/al/Source/test/libdbusmenu-12.10.3+13.10.20130913/builddir/gtk2/tests' PASS: test-glib-objects-test FAIL: test-glib-events FAIL: test-glib-events-nogroup FAIL: test-glib-layout FAIL: test-glib-properties FAIL: test-glib-proxy PASS: test-glib-simple-items FAIL: test-glib-submenu Each test hangs for about 10 minutes before failing. All of the error logs are the same: DBus daemon: unix:abstract=/tmp/dbus-AwSfBXRDlN,guid=c42d750fb322fd07af809069527290f0 Client: Started with PID: 27013 Server: Started with PID: 27014 (process:27013): LIBDBUSMENU-GLIB-WARNING **: Unable to get session bus: Error sending credentials: Error sending message: Operation not permitted ** (process:27014): ERROR **: Unable to get name 'org.dbusmenu.test' on DBus Server: Exited with status 133 Client: ** (process:27013): DEBUG: Death timer. Oops. Got to: 0 Client: ** (process:27013): DEBUG: Quiting as we're a failure Client: Exited with status 256 Client: Shutting down Server: Shutting down DBus daemon: Shutdown To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdbusmenu/+bug/1246842/+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 1245495] Re: Rhythmbox controls and track info broken
I tried again while Rhytmbox was running but it gives the same output: ben@xameroth:~$ gdbus call --session --dest org.mpris.MediaPlayer2.rhythmbox --object-path /org/mpris/MediaPlayer2 --method org.freedesktop.DBus.Properties.GetAll 'org.mpris.MediaPlayer2.Player' Error: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.mpris.MediaPlayer2.rhythmbox was not provided by any .service files -- 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/1245495 Title: Rhythmbox controls and track info broken Status in Sound Menu: Triaged Status in “indicator-sound” package in Ubuntu: Triaged Bug description: A Rhythmbox section appears in the indicator menu as it should but there are several glitches: When RB isn't running click on the icon in the indicator RB starts as expected :-) When RB is running click on the icon in the indicator RB icon wiggles in launcher but window doesn't come to focus :-( Track info and album art appears in notifications, but is never shown in the sound menu. Regardless of whether RB is running: Sound menu track controls (prev, play/pause, next) do nothing. The play/pause button has a dotted orange ring, which turns to an orange square on mouseover (see screenshots). Ubuntu 13.10 64-bit unity: 7.1.2+13.10.20131014.1-0ubuntu1 indicator-sound: 12.10.2+13.10.20131011-0ubuntu1 rhythmbox: 2.99.1-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-sound/+bug/1245495/+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 1244285] Re: Date/time sometimes doesn’t appear in menu bar, settings greyed out (Ubuntu 13.10)
** Summary changed: - in Ubuntu 13.10, the date and time is sometimes not appearing in the system tray + Date/time sometimes doesn’t appear in menu bar, settings greyed out (Ubuntu 13.10) ** Description changed: it does not happen often, and when it happens, just a log out and re-log in is enough to restore it. + + http://askubuntu.com/questions/357266/how-to-show-time-in- + ubuntu-13-10/357280 -- 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/1244285 Title: Date/time sometimes doesn’t appear in menu bar, settings greyed out (Ubuntu 13.10) Status in “indicator-datetime” package in Ubuntu: Confirmed Bug description: it does not happen often, and when it happens, just a log out and re- log in is enough to restore it. http://askubuntu.com/questions/357266/how-to-show-time-in- ubuntu-13-10/357280 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1244285/+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 1246842] Re: libdbusmenu fails to build from source because of test failures
** Description changed: To reproduce: sudo apt-get build-dep libdbusmenu apt-get source libdbusmenu cd libdbusmenu* fakeroot dpkg-buildpackage Result: nearly all of the tests fail to run properly: make[5]: Entering directory `/home/al/Source/test/libdbusmenu-12.10.3+13.10.20130913/builddir/gtk2/tests' PASS: test-glib-objects-test FAIL: test-glib-events FAIL: test-glib-events-nogroup FAIL: test-glib-layout FAIL: test-glib-properties FAIL: test-glib-proxy PASS: test-glib-simple-items FAIL: test-glib-submenu Each test hangs for about 10 minutes before failing. All of the error logs are the same: DBus daemon: unix:abstract=/tmp/dbus-AwSfBXRDlN,guid=c42d750fb322fd07af809069527290f0 Client: Started with PID: 27013 Server: Started with PID: 27014 (process:27013): LIBDBUSMENU-GLIB-WARNING **: Unable to get session bus: Error sending credentials: Error sending message: Operation not permitted ** (process:27014): ERROR **: Unable to get name 'org.dbusmenu.test' on DBus Server: Exited with status 133 Client: ** (process:27013): DEBUG: Death timer. Oops. Got to: 0 Client: ** (process:27013): DEBUG: Quiting as we're a failure Client: Exited with status 256 Client: Shutting down Server: Shutting down DBus daemon: Shutdown + + The json test does not eventually die like the others, instead it just + hangs forever (over 2.5 hours now.) The log files contains: + + DBus daemon: unix:abstract=/tmp/dbus-Irf6GdrlbB,guid=fc747bdf7ec70802e385b3625272912d + Server: Started with PID: 27081 + + ** (process:27081): ERROR **: Unable to get name 'org.dbusmenu.test' on DBus + Server: Exited with status 133 ** Tags added: ftbds ** Tags removed: ftbds ** Tags added: ftbfs -- You received this bug notification because you are a member of DX Packages, which is subscribed to libdbusmenu in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1246842 Title: libdbusmenu fails to build from source because of test failures Status in “libdbusmenu” package in Ubuntu: New Bug description: To reproduce: sudo apt-get build-dep libdbusmenu apt-get source libdbusmenu cd libdbusmenu* fakeroot dpkg-buildpackage Result: nearly all of the tests fail to run properly: make[5]: Entering directory `/home/al/Source/test/libdbusmenu-12.10.3+13.10.20130913/builddir/gtk2/tests' PASS: test-glib-objects-test FAIL: test-glib-events FAIL: test-glib-events-nogroup FAIL: test-glib-layout FAIL: test-glib-properties FAIL: test-glib-proxy PASS: test-glib-simple-items FAIL: test-glib-submenu Each test hangs for about 10 minutes before failing. All of the error logs are the same: DBus daemon: unix:abstract=/tmp/dbus-AwSfBXRDlN,guid=c42d750fb322fd07af809069527290f0 Client: Started with PID: 27013 Server: Started with PID: 27014 (process:27013): LIBDBUSMENU-GLIB-WARNING **: Unable to get session bus: Error sending credentials: Error sending message: Operation not permitted ** (process:27014): ERROR **: Unable to get name 'org.dbusmenu.test' on DBus Server: Exited with status 133 Client: ** (process:27013): DEBUG: Death timer. Oops. Got to: 0 Client: ** (process:27013): DEBUG: Quiting as we're a failure Client: Exited with status 256 Client: Shutting down Server: Shutting down DBus daemon: Shutdown The json test does not eventually die like the others, instead it just hangs forever (over 2.5 hours now.) The log files contains: DBus daemon: unix:abstract=/tmp/dbus-Irf6GdrlbB,guid=fc747bdf7ec70802e385b3625272912d Server: Started with PID: 27081 ** (process:27081): ERROR **: Unable to get name 'org.dbusmenu.test' on DBus Server: Exited with status 133 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdbusmenu/+bug/1246842/+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 1212337] Re: accounts-daemon crashed with SIGSEGV in dbus_connection_send()
** Description changed: Hi. There appeared some problems with 'accountsservice' -- a D-Bus interface for user account query and manipulation, that honestly have occurred day-to-day. ### PROBLEM DESCRIPTION: A few weeks ago after login as a normal user, 'accountsservice' (used for querying and manipulating user account informations) crashed. On the beginning it was a random incident. After a few days, 'accountsservice' crashed each time after every user logs on. I think, that's all what I can write, to try to describe this issue, because everything seems to be okay -- no system freezing or slowdowns, no problems after packages update/upgrade etc. ### DETAILED INFORMATIONS: == * ProblemType: Crash * Uname: Linux 3.2.0-51-generic-pae i686 * Architecture: i386 * DistroRelease: Ubuntu 12.04 (Xubuntu 12.04 variant) * Package: accountsservice 0.6.15-2ubuntu9.6 * ApportVersion: 2.0.1-0ubuntu17.4 * NonfreeKernelModules: nvidia * Segfault happened at: 0xb76bb7c3: mov0x10(%eax),%eax * Executable Path (ProcCmdline): /usr/lib/accountsservice/accounts-daemon Also '/var/log/apport.log' file contain some informations about this issue. Everything is in a attached log file. - ### WHAT HAVE HAD AN IMPACT ON THIS ISSUE? - == - I have no ideas, why it started to happen. Only one thing, which I've done for a few weeks before problems with 'accountsservice' was 'conky-all' install. Nothing more, nothing less -- no serious administrative tasks were performed (except e.g. kernel or programs updates via APT utility or UpdateManager, but it seems to be obvious). - ,-[ $ lsb_release -rd ] | Description:Ubuntu 12.04.3 LTS | Release:12.04 `- + + ### WHAT HAVE HAD AN IMPACT ON THIS ISSUE? + == + I have no ideas, why it started to happen. Only one thing, which I've done for a few weeks before problems with 'accountsservice' was 'conky-all' install. Nothing more, nothing less -- no serious administrative tasks were performed (except e.g. kernel or programs updates via APT utility or UpdateManager, but it seems to be obvious). ### APPENDIX: = I would like to notice, that this issue still occurs, after next point Xubuntu update -- from 12.04.2 to 12.04.3 version. So for now, kernel version is; 3.2.0-55-generic-pae. Anything related with this bug, when all of this started to happen, remains unchanged. One more, important, thing to mention is that - in my case - 'accountsservices' crashed even after a fresh Xubuntu 12.04 install. For more info, please see comment #12. Best regards. -- You received this bug notification because you are a member of DX Packages, which is subscribed to accountsservice in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1212337 Title: accounts-daemon crashed with SIGSEGV in dbus_connection_send() Status in “accountsservice” package in Ubuntu: Fix Released Status in “accountsservice” source package in Precise: Confirmed Bug description: Hi. There appeared some problems with 'accountsservice' -- a D-Bus interface for user account query and manipulation, that honestly have occurred day-to-day. ### PROBLEM DESCRIPTION: A few weeks ago after login as a normal user, 'accountsservice' (used for querying and manipulating user account informations) crashed. On the beginning it was a random incident. After a few days, 'accountsservice' crashed each time after every user logs on. I think, that's all what I can write, to try to describe this issue, because everything seems to be okay -- no system freezing or slowdowns, no problems after packages update/upgrade etc. ### DETAILED INFORMATIONS: == * ProblemType: Crash * Uname: Linux 3.2.0-51-generic-pae i686 * Architecture: i386 * DistroRelease: Ubuntu 12.04 (Xubuntu 12.04 variant) * Package: accountsservice 0.6.15-2ubuntu9.6 * ApportVersion: 2.0.1-0ubuntu17.4 * NonfreeKernelModules: nvidia * Segfault happened at: 0xb76bb7c3: mov0x10(%eax),%eax * Executable Path (ProcCmdline): /usr/lib/accountsservice/accounts-daemon Also '/var/log/apport.log' file contain some informations about this issue. Everything is in a attached log file. ,-[ $ lsb_release -rd ] | Description:Ubuntu 12.04.3 LTS | Release:12.04 `- ### WHAT HAVE HAD AN IMPACT ON THIS ISSUE? == I have no ideas, why it started to happen. Only one thing, which I've done for a few weeks before problems with 'accountsservice' was 'conky-all' install. Nothing more, nothing less -- no serious administrative tasks were performed (except e.g. kernel or programs updates via APT utility or UpdateManager, but it seems to be obvious). ### APPENDIX:
[Dx-packages] [Bug 1199877] Re: unity-panel-service memory leak and 100% CPU usage
I don't see the CPU being pegged and it isn't leaking memory so badly. There is still some memory leakage. I ran health-check (from my PPA, ppa:colin-king/white) against it for over 10 minutes using applications such as LibreOffice, Gimp, Firefox and still observed quite a lot of brks() occurring: Heap Change via brk(): PIDbrk Count Change (K) Rate (K/second) 3222 unity-panel-service 14318612 29.10 (growing moderately fast) so, that's 18Mb in 640 seconds, or about 29K a second. I did reboot my machine before testing and double checked that I was running the package from -proposed. Attached is a report from health-check with the full details. ** Attachment added: leak.log https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1199877/+attachment/3897066/+files/leak.log -- 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/1199877 Title: unity-panel-service memory leak and 100% CPU usage Status in The Application Menu: Fix Committed Status in Application Menu Indicator 13.10 series: Fix Committed Status in The Ubuntu Power Consumption Project: New Status in Unity: Invalid Status in “gtk+3.0” package in Ubuntu: In Progress Status in “indicator-appmenu” package in Ubuntu: In Progress Status in “unity” package in Ubuntu: Invalid Status in “gtk+3.0” source package in Saucy: Fix Committed Status in “indicator-appmenu” source package in Saucy: In Progress Bug description: Impact: high CPU/memory usage from unity-panel-service Test case: Open a large image in the GIMP and activate a lot of items from the global menu. Using shortcuts is enough and faster to reproduce this bug (I've always used Ctrl+A and Ctrl+Shift+A). Memory usage of unity- panel-service increases steadily and it uses a lot of CPU shortly after activating the menu items in a short time. Regression potential: check that the menus are stable/working as they should - Just going about my business on Ubuntu Raring amd64 on an x230 and I heard the fan kick into action. top showed me that unity-panel-service was consuming all the free cycles on one of my CPUs. I killed it before my machine overheated, so I didn't attach a debugger to see why it was totally pegging out a CPU. I'm not sure if this adds any context, but I was using a LibreOffice spreadsheet and I could not insert a table because the menu had lost it's mind, and then I observed the overly loaded CPU a very short while after that. To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-appmenu/+bug/1199877/+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 1199877] Re: unity-panel-service memory leak and 100% CPU usage
By the look of things, after all the submenus are rendered the memory consumed by unity-panel-service seems to stabilize, so I am guessing it cache's the menus because after several invocations of the the applications I can't see a great deal more memory being allocated. Is this the intention? If so, how much will it cache over the life time of a session? -- 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/1199877 Title: unity-panel-service memory leak and 100% CPU usage Status in The Application Menu: Fix Committed Status in Application Menu Indicator 13.10 series: Fix Committed Status in The Ubuntu Power Consumption Project: New Status in Unity: Invalid Status in “gtk+3.0” package in Ubuntu: In Progress Status in “indicator-appmenu” package in Ubuntu: In Progress Status in “unity” package in Ubuntu: Invalid Status in “gtk+3.0” source package in Saucy: Fix Committed Status in “indicator-appmenu” source package in Saucy: In Progress Bug description: Impact: high CPU/memory usage from unity-panel-service Test case: Open a large image in the GIMP and activate a lot of items from the global menu. Using shortcuts is enough and faster to reproduce this bug (I've always used Ctrl+A and Ctrl+Shift+A). Memory usage of unity- panel-service increases steadily and it uses a lot of CPU shortly after activating the menu items in a short time. Regression potential: check that the menus are stable/working as they should - Just going about my business on Ubuntu Raring amd64 on an x230 and I heard the fan kick into action. top showed me that unity-panel-service was consuming all the free cycles on one of my CPUs. I killed it before my machine overheated, so I didn't attach a debugger to see why it was totally pegging out a CPU. I'm not sure if this adds any context, but I was using a LibreOffice spreadsheet and I could not insert a table because the menu had lost it's mind, and then I observed the overly loaded CPU a very short while after that. To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-appmenu/+bug/1199877/+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 1052024] Re: Week 38 - keynav mode quicklist exit fails to work when mouse is used to right click and choose an option
** Changed in: unity Assignee: (unassigned) = Marco Trevisan (Treviño) (3v1n0) ** 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/1052024 Title: Week 38 - keynav mode quicklist exit fails to work when mouse is used to right click and choose an option Status in Unity: Triaged Status in “unity” package in Ubuntu: Triaged Bug description: Ubuntu 12.10 Quantal with ppa:unity-team/staging Issue:- Right click using mouse on dash icon in keynav mode fails to exit keynav mode and does not activate the option chosen by the user. Only if the user clicks anywhere on the screen, the chosen option gets activated. For example:- In keynav mode, right click on dash and click on Applications. This will not exit keynav mode and will not open applications lens. Only when the user click somewhere on the screen, keynav mode exits and applications lens is opened. Action: - Press Alt+F1 to enter keynav mode - now right click on dash icon, click on any options in the quicklist ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: unity 6.4.0+bzr2684ubuntu0+778 [origin: LP-PPA-unity-team-staging] ProcVersionSignature: Ubuntu 3.5.0-14.19-generic 3.5.3 Uname: Linux 3.5.0-14-generic i686 ApportVersion: 2.5.1-0ubuntu7 Architecture: i386 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CrashDB: unity Date: Mon Sep 17 16:27:38 2012 InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Alpha i386 (20120713.1) ProcEnviron: LANGUAGE=en_GB:en TERM=xterm PATH=(custom, no 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/unity/+bug/1052024/+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 1199877] Re: unity-panel-service memory leak and 100% CPU usage
Colin so far there is only the GTK+ 3 uploaded for proposed and this bug is linked also against indicator-appmenu. You could download the updated indicator-appmenu package from the SRU staging ppa. https://launchpad.net/~ubuntu-unity/+archive/sru-staging -- 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/1199877 Title: unity-panel-service memory leak and 100% CPU usage Status in The Application Menu: Fix Committed Status in Application Menu Indicator 13.10 series: Fix Committed Status in The Ubuntu Power Consumption Project: New Status in Unity: Invalid Status in “gtk+3.0” package in Ubuntu: In Progress Status in “indicator-appmenu” package in Ubuntu: In Progress Status in “unity” package in Ubuntu: Invalid Status in “gtk+3.0” source package in Saucy: Fix Committed Status in “indicator-appmenu” source package in Saucy: In Progress Bug description: Impact: high CPU/memory usage from unity-panel-service Test case: Open a large image in the GIMP and activate a lot of items from the global menu. Using shortcuts is enough and faster to reproduce this bug (I've always used Ctrl+A and Ctrl+Shift+A). Memory usage of unity- panel-service increases steadily and it uses a lot of CPU shortly after activating the menu items in a short time. Regression potential: check that the menus are stable/working as they should - Just going about my business on Ubuntu Raring amd64 on an x230 and I heard the fan kick into action. top showed me that unity-panel-service was consuming all the free cycles on one of my CPUs. I killed it before my machine overheated, so I didn't attach a debugger to see why it was totally pegging out a CPU. I'm not sure if this adds any context, but I was using a LibreOffice spreadsheet and I could not insert a table because the menu had lost it's mind, and then I observed the overly loaded CPU a very short while after that. To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-appmenu/+bug/1199877/+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 932486] Re: showing quicklist from launcher keynav mode focuses last application
** Changed in: unity Milestone: None = 7.2.0 ** Changed in: unity Assignee: (unassigned) = Marco Trevisan (Treviño) (3v1n0) -- 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/932486 Title: showing quicklist from launcher keynav mode focuses last application Status in Unity: Confirmed Status in “unity” package in Ubuntu: Confirmed Bug description: To reproduce: 0) Have at least one application window open 1) Enter launcher keynav mode with Alt+F1 * Note that when entering keynav mode, the application loses focus. THe triangle to the right of it's launcher icon is no longer drawn, and the window title is not displayed in the panel. 2) Select a launcher icon with the Up or Down keys. 3) Show the quicklist by pressing Right. * Note that the application becomes active again - it's window title is drawn to the panel, and the triangle to the right of the launcher icon is drawn again. 4) Collapse the quicklist by pressing Left. * The app loses focus again. This seems like inconsistent behavior to me... either the app should never lose focus when we enter keynav mode, or should not be activated when we show a quicklist. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/932486/+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 1243069] Re: Launcher does not reveal when autohide is on
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/1243069 Title: Launcher does not reveal when autohide is on Status in “unity” package in Ubuntu: Confirmed Bug description: I use a dual screen setup and autohide with the launcher on the left. After the 13.10 upgrade the autohide feature is broken : - The launcher does not reveal anymore with the mouse (it reveals with the keyboard shortcut). - I can't move the mouse to the second monitor : the cursor is stuck on the right border of the left monitor. If I move the mouse top right and move fast I can pass to the second monitor) I tried different settings in ccsm in vain. I could not find any similar issues report except this one : http://askubuntu.com/questions/363205/13-10-auto-hidelauncher-breaks- multiple-monitor-setup ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: unity 7.1.2+13.10.20131014.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.12.5-0ubuntu2 Architecture: amd64 CompizPlugins: [core,bailer,detection,composite,opengl,decor,compiztoolbox,regex,place,move,gnomecompat,imgpng,grid,resize,mousepoll,session,vpswitch,snap,animation,workarounds,expo,wall,ezoom,staticswitcher,fade,scale,unityshell] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Tue Oct 22 09:19:09 2013 DistUpgraded: 2013-10-18 12:53:39,653 DEBUG enabling apt cron job DistroCodename: saucy DistroVariant: ubuntu DkmsStatus: virtualbox, 4.2.16, 3.11.0-12-generic, x86_64: installed virtualbox, 4.2.16, 3.8.0-31-generic, x86_64: installed GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Cedar [Radeon HD 5000/6000/7350/8350 Series] [1002:68f9] (prog-if 00 [VGA controller]) Subsystem: Dell Radeon HD 6350 [1028:2126] InstallationDate: Installed on 2011-06-08 (866 days ago) InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release amd64 (20110427.1) MachineType: Dell Inc. OptiPlex 990 MarkForUpload: True ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic root=UUID=c4c9bb00-bea9-47e8-9175-82937fe761ef ro radeon.agpmode=-1 quiet splash i915.semaphores=1 vt.handoff=7 SourcePackage: unity UpgradeStatus: Upgraded to saucy on 2013-10-18 (3 days ago) dmi.bios.date: 11/24/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A10 dmi.board.name: 06D7TR dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 6 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA10:bd11/24/2011:svnDellInc.:pnOptiPlex990:pvr01:rvnDellInc.:rn06D7TR:rvrA00:cvnDellInc.:ct6:cvr: dmi.product.name: OptiPlex 990 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.10+13.10.20131011-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.46-1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.2.1-1ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.2.1-1ubuntu3 version.xserver-xorg-core: xserver-xorg-core 3:1.12.4+git20121105-makson1~ppa2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 2:2.7.3+git20120928~quantal2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 2:6.14.6+git20120928~quantal1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 3:2.20.8+git20120928~quantal2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 2:1.0.2+git20120928~quantal1 xserver.bootTime: Mon Oct 21 15:19:46 2013 xserver.configfile: /etc/X11/xorg.conf xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputDell Dell USB Keyboard KEYBOARD, id 8 inputUSB Optical MouseMOUSE, id 9 xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 3:1.12.4+git20121105-makson1~ppa2 xserver.video_driver: radeon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1243069/+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 1246536] Re: segfault in menu_hidden()
** Description changed: + Impact: indicator-sound is segfaulting the unity-panel-service sometimes + + Test Case: + - install the current GTK version from saucy-proposed + - use the indicator-sound slider and the play multimedia key to start/stop rhythmbox + - the indicator should be stable + + Regression potential: try desktop indicators and make sure they keep + working + + --- + Using saucy stable, happened a few times today while using the slider, muting/unmuting, using play multimedia key/mpris to start/stop rhythmbox #0 menu_hidden (menu=0x96882c0, scale=0x97b8110) at idoscalemenuitem.c:640 - #1 0xb6e454d3 in g_cclosure_marshal_VOID__VOID (closure=0x97b5818, - return_value=0x0, n_param_values=1, param_values=0xbff2e970, - invocation_hint=0xbff2e91c, marshal_data=0x0) - at /build/buildd/glib2.0-2.38.1/./gobject/gmarshal.c:85 - #2 0xb6e438ae in g_closure_invoke (closure=0x97b5818, - return_value=return_value@entry=0x0, n_param_values=1, - param_values=param_values@entry=0xbff2e970, - invocation_hint=invocation_hint@entry=0xbff2e91c) - at /build/buildd/glib2.0-2.38.1/./gobject/gclosure.c:777 - #3 0xb6e55df9 in signal_emit_unlocked_R (node=node@entry=0x9562ec8, detail=0, - instance=0x96882c0, emission_return=emission_return@entry=0x0, - instance_and_params=0xbff2e970) - at /build/buildd/glib2.0-2.38.1/./gobject/gsignal.c:3586 - #4 0xb6e5d753 in g_signal_emit_valist (instance=instance@entry=0x96882c0, - signal_id=signal_id@entry=5, detail=detail@entry=0, - var_args=var_args@entry=0xbff2eaac h\027;\267) - at /build/buildd/glib2.0-2.38.1/./gobject/gsignal.c:3330 - #5 0xb6e5d9e3 in g_signal_emit (instance=instance@entry=0x96882c0, - signal_id=5, detail=detail@entry=0) - at /build/buildd/glib2.0-2.38.1/./gobject/gsignal.c:3386 + #1 0xb6e454d3 in g_cclosure_marshal_VOID__VOID (closure=0x97b5818, + return_value=0x0, n_param_values=1, param_values=0xbff2e970, + invocation_hint=0xbff2e91c, marshal_data=0x0) + at /build/buildd/glib2.0-2.38.1/./gobject/gmarshal.c:85 + #2 0xb6e438ae in g_closure_invoke (closure=0x97b5818, + return_value=return_value@entry=0x0, n_param_values=1, + param_values=param_values@entry=0xbff2e970, + invocation_hint=invocation_hint@entry=0xbff2e91c) + at /build/buildd/glib2.0-2.38.1/./gobject/gclosure.c:777 + #3 0xb6e55df9 in signal_emit_unlocked_R (node=node@entry=0x9562ec8, detail=0, + instance=0x96882c0, emission_return=emission_return@entry=0x0, + instance_and_params=0xbff2e970) + at /build/buildd/glib2.0-2.38.1/./gobject/gsignal.c:3586 + #4 0xb6e5d753 in g_signal_emit_valist (instance=instance@entry=0x96882c0, + signal_id=signal_id@entry=5, detail=detail@entry=0, + var_args=var_args@entry=0xbff2eaac h\027;\267) + at /build/buildd/glib2.0-2.38.1/./gobject/gsignal.c:3330 + #5 0xb6e5d9e3 in g_signal_emit (instance=instance@entry=0x96882c0, + signal_id=5, detail=detail@entry=0) + at /build/buildd/glib2.0-2.38.1/./gobject/gsignal.c:3386 #6 0xb73b1820 in gtk_widget_hide (widget=widget@entry=0x96882c0) - at /tmp/gtk+3/build-area/gtk+3.0-3.8.6/./gtk/gtkwidget.c:4268 + at /tmp/gtk+3/build-area/gtk+3.0-3.8.6/./gtk/gtkwidget.c:4268 #7 0xb7278678 in gtk_menu_popdown (menu=menu@entry=0x96882c0) - at /tmp/gtk+3/build-area/gtk+3.0-3.8.6/./gtk/gtkmenu.c:1848 + at /tmp/gtk+3/build-area/gtk+3.0-3.8.6/./gtk/gtkmenu.c:1848 #8 0xb727877d in gtk_menu_deactivate (menu_shell=0x96882c0) - at /tmp/gtk+3/build-area/gtk+3.0-3.8.6/./gtk/gtkmenu.c:4546 - #9 0xb6e454d3 in g_cclosure_marshal_VOID__VOID (closure=0x956c640, - return_value=0x0, n_param_values=1, param_values=0xbff2ec90, - invocation_hint=0xbff2ec3c, marshal_data=0xb7278700 gtk_menu_deactivate) - at /build/buildd/glib2.0-2.38.1/./gobject/gmarshal.c:85 - #10 0xb6e423d4 in g_type_class_meta_marshal (closure=0x956c640, - return_value=0x0, n_param_values=1, param_values=0xbff2ec90, - invocation_hint=0xbff2ec3c, marshal_data=0x1ec) - at /build/buildd/glib2.0-2.38.1/./gobject/gclosure.c:970 - #11 0xb6e438ae in g_closure_invoke (closure=closure@entry=0x956c640, - return_value=return_value@entry=0x0, n_param_values=1, - param_values=param_values@entry=0xbff2ec90, - invocation_hint=invocation_hint@entry=0xbff2ec3c) - at /build/buildd/glib2.0-2.38.1/./gobject/gclosure.c:777 - #12 0xb6e5549c in signal_emit_unlocked_R (node=node@entry=0x956d3b8, detail=0, - instance=0x96882c0, emission_return=emission_return@entry=0x0, - instance_and_params=0xbff2ec90) - at /build/buildd/glib2.0-2.38.1/./gobject/gsignal.c:3516 - #13 0xb6e5d753 in g_signal_emit_valist (instance=instance@entry=0x96882c0, - signal_id=signal_id@entry=82, detail=detail@entry=0, - var_args=var_args@entry=0xbff2edcc ) - at /build/buildd/glib2.0-2.38.1/./gobject/gsignal.c:3330 - #14 0xb6e5d9e3 in g_signal_emit (instance=instance@entry=0x96882c0,
[Dx-packages] [Bug 1125442] Re: Always Visible and On Top Windows Steal Focus on Workspace Switch
This affects Saucy too! same symptoms... To add to the symptoms, this also occurs when selecting an application (already launched, so just to switch to it, via unity launcher) other than the Always on top/visable on all workspaces application, when it must switch workspaces to focus the selected app... Instead of focusing the selected app, once the workspace is switched it will focus the Always on top/visable on all workspaces window instead. This has been a security risk for me (let's try that approach :D , ok I know I can just disable the visable on all workspaces or always on top to fix BUT) as I've accidently provided my domain password to coworkers because of this issue. (IM client is my Always on top/visable on all workspaces so when I go to switch to my RDP session and I'm in a hurry, I just type out password and hit enter w/out thinking about it, so find I just IM'd my password to last my convo VERY annoying, as I've had to drop what I'm doing and change my password)! I have confirmed the symptoms are present no matter what application I set to Always on top/visable on all workspaces... -- 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/1125442 Title: Always Visible and On Top Windows Steal Focus on Workspace Switch Status in Ayatana Design: New Status in “unity” package in Ubuntu: Confirmed Status in “unity” source package in Precise: Confirmed Status in “unity” source package in Quantal: Confirmed Status in “unity” source package in Raring: Confirmed Bug description: 1. Open any application (e.g. TextEditor) 2. Right click the title bar 2a. Select Always on Visible Workspace 3. Right click the title bar 3a. Select Always on Top 4. Open a different application (e.g. Terminal) 5. Ensure that window has focus 6. Switch workspaces (Notice: the first application now has focus) 7. Return to first workspace (Notice: the second application does not regain focus) Expected: The initial application should not have ever regained focus, and certainly the second application should have it when returning to that workspace. antarus@mach ~ $ lsb_release -rd Description:Ubuntu 12.04.1 LTS Release:12.04 antarus@mach ~ $ apt-cache policy unity unity: Installed: 5.18.0-0ubuntu2 Candidate: 5.18.0-0ubuntu2 Version table: To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/1125442/+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 1242339] Re: window-stack-bridge crashed with SIGSEGV in data()
This bug was fixed in the package hud - 13.10.1+13.10.20131024-0ubuntu1 --- hud (13.10.1+13.10.20131024-0ubuntu1) saucy; urgency=low [ Pete Woods ] * Fix the ref counting of application sources The application sources are now entirely owned by the application-list's hash table. [ Ted Gould ] * Add apport dependencies to the package hook. (LP: #1233994) * Don't show disabled items in search results. (LP: #1192646) * Don't crash if we get asked about a window we don't know about, return a null list. (LP: #1242339) [ Ubuntu daily release ] * Automatic snapshot from revision 341 -- Ubuntu daily release ps-jenk...@lists.canonical.com Thu, 24 Oct 2013 16:12:43 + ** Changed in: hud (Ubuntu Saucy) 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/1242339 Title: window-stack-bridge crashed with SIGSEGV in data() Status in Unity HUD: Fix Committed Status in “hud” package in Ubuntu: Confirmed Status in “hud” source package in Saucy: Fix Released Bug description: [Impact] High impoact on our users, this is one of the highest reported issues on errors.ubuntu.com: https://errors.ubuntu.com/problem/80ec348bd203ad9f5b91a956c463234dce72d2e7 [Test case] Use Unity, switch between applications and try to access menus via the HUD. [Rgression potential] This changes behavior in the window properties retrieval. Regression potential is low since this would simply return an empty set (rather than crashing) should the window not be identifyable. --- Just working in eclipse ProblemType: Crash DistroRelease: Ubuntu 13.10 Package: hud 13.10.1+13.10.20131014-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.12.5-0ubuntu2 Architecture: i386 Date: Sun Oct 20 20:11:13 2013 ExecutablePath: /usr/lib/i386-linux-gnu/hud/window-stack-bridge InstallationDate: Installed on 2012-05-14 (523 days ago) InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release i386 (20111012) MarkForUpload: True ProcCmdline: /usr/lib/i386-linux-gnu/hud/window-stack-bridge ProcEnviron: PATH=(custom, no user) LANGUAGE=ru XDG_RUNTIME_DIR=set LANG=ru_RU.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0xb73110d7 _ZN22QDBusAbstractInterface25asyncCallWithArgumentListERK7QStringRK5QListI8QVariantE+23: mov0x4(%edi),%esi PC (0xb73110d7) ok source 0x4(%edi) (0x0004) not located in a known VMA region (needed readable region)! destination %esi ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: hud StacktraceTop: QDBusAbstractInterface::asyncCallWithArgumentList(QString const, QListQVariant const) () from /usr/lib/i386-linux-gnu/libQt5DBus.so.5 BamfWindow::xProp(QString const) () BamfWindowStack::GetWindowProperties(unsigned int, QString const, QStringList const) () WindowStackAdaptor::GetWindowProperties(unsigned int, QString const, QStringList const) () ?? () Title: window-stack-bridge crashed with SIGSEGV in QDBusAbstractInterface::asyncCallWithArgumentList() UpgradeStatus: Upgraded to saucy on 2013-10-19 (1 days ago) UserGroups: adm lpadmin nopasswdlogin sambashare sudo upstart.window-stack-bridge.log: QDBusConnection: name 'org.ayatana.bamf' had owner '' but we thought it was ':1.14' Error getting parents for /org/ayatana/bamf/window/75613984 QDBusError(org.freedesktop.DBus.Error.UnknownMethod, Интерфейс «org.ayatana.bamf.view» для пути /org/ayatana/bamf/window/75613984 объекта не найден) Error getting parents for /org/ayatana/bamf/window/75614083 QDBusError(org.freedesktop.DBus.Error.UnknownMethod, Интерфейс «org.ayatana.bamf.view» для пути /org/ayatana/bamf/window/75614083 объекта не найден) To manage notifications about this bug go to: https://bugs.launchpad.net/hud/+bug/1242339/+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 1192646] Re: shouldn't list inactive items
This bug was fixed in the package hud - 13.10.1+13.10.20131024-0ubuntu1 --- hud (13.10.1+13.10.20131024-0ubuntu1) saucy; urgency=low [ Pete Woods ] * Fix the ref counting of application sources The application sources are now entirely owned by the application-list's hash table. [ Ted Gould ] * Add apport dependencies to the package hook. (LP: #1233994) * Don't show disabled items in search results. (LP: #1192646) * Don't crash if we get asked about a window we don't know about, return a null list. (LP: #1242339) [ Ubuntu daily release ] * Automatic snapshot from revision 341 -- Ubuntu daily release ps-jenk...@lists.canonical.com Thu, 24 Oct 2013 16:12:43 + ** Changed in: hud (Ubuntu Saucy) 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/1192646 Title: shouldn't list inactive items Status in Unity HUD: Fix Committed Status in Unity HUD 13.10 series: In Progress Status in “hud” package in Ubuntu: Fix Released Status in “hud” source package in Saucy: Fix Released Bug description: [Impact] All Ubuntu users using Unity and the HUD. [Test case] - start gedit - open the hud - look for undo It lists the undo item from the edit menu, it shouldn't since there is nothing to undo and the menu item is greyed out. [Regression potential] Since this changes how menu items are identified on whether or not they need to be shown, there could be unforeseen issues where menu items that should be appearing and used to be appearing are now hidden and considered unavailable. Items that just recently became available may not be visible in the hud. To manage notifications about this bug go to: https://bugs.launchpad.net/hud/+bug/1192646/+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 1233994] Re: hud apport hook fails with: File /usr/share/apport/package-hooks/source_hud.py, line 4, in add_info NameError: global name 'apport' is not defined
This bug was fixed in the package hud - 13.10.1+13.10.20131024-0ubuntu1 --- hud (13.10.1+13.10.20131024-0ubuntu1) saucy; urgency=low [ Pete Woods ] * Fix the ref counting of application sources The application sources are now entirely owned by the application-list's hash table. [ Ted Gould ] * Add apport dependencies to the package hook. (LP: #1233994) * Don't show disabled items in search results. (LP: #1192646) * Don't crash if we get asked about a window we don't know about, return a null list. (LP: #1242339) [ Ubuntu daily release ] * Automatic snapshot from revision 341 -- Ubuntu daily release ps-jenk...@lists.canonical.com Thu, 24 Oct 2013 16:12:43 + ** Changed in: hud (Ubuntu Saucy) 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/1233994 Title: hud apport hook fails with: File /usr/share/apport/package- hooks/source_hud.py, line 4, in add_info NameError: global name 'apport' is not defined Status in Unity HUD: Fix Released Status in “hud” package in Ubuntu: Fix Released Status in “hud” source package in Saucy: Fix Released Bug description: From the command line run: $ ubuntu-bug hud The following error is displayed on the terminal ERROR: hook /usr/share/apport/package-hooks/source_hud.py crashed: Traceback (most recent call last): File /usr/lib/python3/dist-packages/apport/report.py, line 197, in _run_hook symb['add_info'](report, ui) TypeError: add_info() takes 1 positional argument but 2 were given During handling of the above exception, another exception occurred: Traceback (most recent call last): File /usr/lib/python3/dist-packages/apport/report.py, line 202, in _run_hook symb['add_info'](report) File /usr/share/apport/package-hooks/source_hud.py, line 4, in add_info if not apport.packaging.is_distro_package(report['Package'].split()[0]): NameError: global name 'apport' is not defined ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: hud 13.10.1+13.10.20130918-0ubuntu1 Uname: Linux 3.4.0-3-mako armv7l ApportVersion: 2.12.5-0ubuntu1 Architecture: armhf Date: Wed Oct 2 06:05:00 2013 InstallationDate: Installed on 2013-10-01 (0 days ago) InstallationMedia: Ubuntu Saucy Salamander (development branch) - armhf (20131001.3) MarkForUpload: True ProcEnviron: TERM=linux PATH=(custom, no user) SourcePackage: hud UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/hud/+bug/1233994/+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 1244688] Re: /usr/lib/i386-linux-gnu/hud/hud-service:5:name_lost_cb:actually_do_call:do_call:ffi_call_SYSV:ffi_call
** Also affects: hud (Ubuntu Saucy) Importance: Undecided Status: New -- 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/1244688 Title: /usr/lib/i386-linux-gnu/hud/hud- service:5:name_lost_cb:actually_do_call:do_call:ffi_call_SYSV:ffi_call Status in “hud” package in Ubuntu: Fix Released Status in “hud” source package in Saucy: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding hud. This problem was most recently seen with version 13.10.1+13.10.20131014-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/23bafefb567e15de49e41a1fda7e468768652425 contains more details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hud/+bug/1244688/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1170647] Re: Clicking on Nautilus’ launcher icon opens new window instead of restoring the minimized one when browsing external drives/locations
Recently I've found that this bug also affects process windows while copying from an external drive - those windows cannot be accessed by clicking on nautilus' icon. Sometimes it gets focus when I click on external drive icon, sometimes it doesn't. Strange. -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1170647 Title: Clicking on Nautilus’ launcher icon opens new window instead of restoring the minimized one when browsing external drives/locations Status in “bamf” package in Ubuntu: Triaged Status in “nautilus” package in Ubuntu: Triaged Status in “unity” package in Ubuntu: Triaged Bug description: Sometimes left clicking the nautilus launcher icon doesn't bring up a minimized nautilus window. Instead of restoring the window a new instance of nautilus is showing up. Steps to reproduce: 1. Open a nautilus window by clicking on the launcher icon. 2. Navigate to a symlinked directory whose target is located on a different harddrive (for example: a symlink to a folder on a sd-card). 3. Minimize the nautilus window. 4. Try to bring up that window again by clicking the launcher icon. What happens: 1. A new instance (window) of nautilus is opened. 2. There's no obvious way to access the first window again. The only way is ALT+TAB. What schould happen: If a nautilus window is already open and minimized clicking the launcher icon should bring up that window. This was the behavior of nautilus windows in Ubuntu 12.10 (quantal). Ubuntu 13.04 Raring Ringtail (development branch) nautilus 3.6.3-0ubuntu16 unity 7.0.0daily13.04.18~13.04-0ubuntu1 ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: nautilus 1:3.6.3-0ubuntu16 ProcVersionSignature: Ubuntu 3.8.0-18.28-generic 3.8.6 Uname: Linux 3.8.0-18-generic i686 ApportVersion: 2.9.2-0ubuntu8 Architecture: i386 Date: Fri Apr 19 11:33:13 2013 EcryptfsInUse: Yes GsettingsChanges: b'org.gnome.nautilus.window-state' b'geometry' b'814x493+136+38' b'org.gnome.nautilus.window-state' b'sidebar-width' b'182' InstallationDate: Installed on 2011-07-23 (635 days ago) InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release i386 (20110426) MarkForUpload: True SourcePackage: nautilus UpgradeStatus: Upgraded to raring on 2013-04-14 (4 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bamf/+bug/1170647/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1199877] Re: unity-panel-service memory leak and 100% CPU usage
Installed indicator-appmenu 13.01.0+13.10.20131031-0ubuntu1, rebooted, quick test again, still see: Change in memory (K/second): PID Process TypeSize RSS PSS 3170 unity-panel-service Stack 0.00 0.19 0.19 (growing slowly) 3170 unity-panel-service Heap 98.56237.46237.46 (growing fast) 3170 unity-panel-service Mapped 5.99 4.91 1.95 (growing moderately fast) Heap Change via brk(): PIDbrk Count Change (K) Rate (K/Sec) 3170 unity-panel-service 618292 97.02 (growing moderately fast) Memory Change via mmap() and munmap(): PID mmaps munmaps Change (K) Rate (K/Sec) 3170 unity-panel-service15 15 0 0.00 (no change) -- 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/1199877 Title: unity-panel-service memory leak and 100% CPU usage Status in The Application Menu: Fix Committed Status in Application Menu Indicator 13.10 series: Fix Committed Status in The Ubuntu Power Consumption Project: New Status in Unity: Invalid Status in “gtk+3.0” package in Ubuntu: In Progress Status in “indicator-appmenu” package in Ubuntu: In Progress Status in “unity” package in Ubuntu: Invalid Status in “gtk+3.0” source package in Saucy: Fix Committed Status in “indicator-appmenu” source package in Saucy: In Progress Bug description: Impact: high CPU/memory usage from unity-panel-service Test case: Open a large image in the GIMP and activate a lot of items from the global menu. Using shortcuts is enough and faster to reproduce this bug (I've always used Ctrl+A and Ctrl+Shift+A). Memory usage of unity- panel-service increases steadily and it uses a lot of CPU shortly after activating the menu items in a short time. Regression potential: check that the menus are stable/working as they should - Just going about my business on Ubuntu Raring amd64 on an x230 and I heard the fan kick into action. top showed me that unity-panel-service was consuming all the free cycles on one of my CPUs. I killed it before my machine overheated, so I didn't attach a debugger to see why it was totally pegging out a CPU. I'm not sure if this adds any context, but I was using a LibreOffice spreadsheet and I could not insert a table because the menu had lost it's mind, and then I observed the overly loaded CPU a very short while after that. To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-appmenu/+bug/1199877/+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 1243654] Re: window-stack-bridge crashed with SIGSEGV in BamfWindow::windowId()
** Description changed: + SRU for saucy. + + [Impact] + + A crash in certain situations. + + [Test Case] + + A crasher, no clear test case. Ensure errors.ubuntu.com stops reporting + this. + + [Regression Potential] + + Low, a null safe guard added in three places. + ProblemType: Crash DistroRelease: Ubuntu 13.10 Package: hud 13.10.1+13.10.20131014-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 ApportVersion: 2.12.5-0ubuntu2 Architecture: amd64 CrashCounter: 1 Date: Wed Oct 23 13:44:21 2013 ExecutablePath: /usr/lib/x86_64-linux-gnu/hud/window-stack-bridge InstallationDate: Installed on 2012-11-10 (346 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) MarkForUpload: True ProcCmdline: /usr/lib/x86_64-linux-gnu/hud/window-stack-bridge SegvAnalysis: Segfault happened at: 0x409b70 _ZN10BamfWindow8windowIdEv: mov 0x24(%rdi),%eax PC (0x00409b70) ok source 0x24(%rdi) (0x0024) not located in a known VMA region (needed readable region)! destination %eax ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: hud StacktraceTop: BamfWindow::windowId() () BamfWindowStack::ActiveWindowChanged(QString const, QString const) () ?? () QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 OrgAyatanaBamfMatcherInterface::ActiveWindowChanged(QString const, QString const) () Title: window-stack-bridge crashed with SIGSEGV in BamfWindow::windowId() UpgradeStatus: Upgraded to saucy on 2013-10-18 (4 days ago) UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo upstart.hud.log: (process:1812): hudapplicationsource-WARNING **: Unable to export application 'python2' skeleton on path '/com/canonical/hud/applications/python2': An object is already exported for the interface com.canonical.hud.Application at /com/canonical/hud/applications/python2 upstart.window-stack-bridge.log: Could not get desktop file for /org/ayatana/bamf/window/75497480 -- 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/1243654 Title: window-stack-bridge crashed with SIGSEGV in BamfWindow::windowId() Status in “hud” package in Ubuntu: Fix Released Status in “hud” source package in Saucy: New Bug description: SRU for saucy. [Impact] A crash in certain situations. [Test Case] A crasher, no clear test case. Ensure errors.ubuntu.com stops reporting this. [Regression Potential] Low, a null safe guard added in three places. ProblemType: Crash DistroRelease: Ubuntu 13.10 Package: hud 13.10.1+13.10.20131014-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 ApportVersion: 2.12.5-0ubuntu2 Architecture: amd64 CrashCounter: 1 Date: Wed Oct 23 13:44:21 2013 ExecutablePath: /usr/lib/x86_64-linux-gnu/hud/window-stack-bridge InstallationDate: Installed on 2012-11-10 (346 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) MarkForUpload: True ProcCmdline: /usr/lib/x86_64-linux-gnu/hud/window-stack-bridge SegvAnalysis: Segfault happened at: 0x409b70 _ZN10BamfWindow8windowIdEv: mov 0x24(%rdi),%eax PC (0x00409b70) ok source 0x24(%rdi) (0x0024) not located in a known VMA region (needed readable region)! destination %eax ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: hud StacktraceTop: BamfWindow::windowId() () BamfWindowStack::ActiveWindowChanged(QString const, QString const) () ?? () QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 OrgAyatanaBamfMatcherInterface::ActiveWindowChanged(QString const, QString const) () Title: window-stack-bridge crashed with SIGSEGV in BamfWindow::windowId() UpgradeStatus: Upgraded to saucy on 2013-10-18 (4 days ago) UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo upstart.hud.log: (process:1812): hudapplicationsource-WARNING **: Unable to export application 'python2' skeleton on path '/com/canonical/hud/applications/python2': An object is already exported for the interface com.canonical.hud.Application at /com/canonical/hud/applications/python2 upstart.window-stack-bridge.log: Could not get desktop file for /org/ayatana/bamf/window/75497480 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hud/+bug/1243654/+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 1244688] Re: /usr/lib/i386-linux-gnu/hud/hud-service:5:name_lost_cb:actually_do_call:do_call:ffi_call_SYSV:ffi_call
** Description changed: + SRU for saucy. + + [Impact] + + A reported crash in certain situations. + + [Test Case] + + A crasher, no clear test case. Ensure errors.ubuntu.com stops reporting + this. + + [Regression Potential] + + Low, doing graceful exiting instead of abort. + The Ubuntu Error Tracker has been receiving reports about a problem regarding hud. This problem was most recently seen with version 13.10.1+13.10.20131014-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/23bafefb567e15de49e41a1fda7e468768652425 contains more details. -- 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/1244688 Title: /usr/lib/i386-linux-gnu/hud/hud- service:5:name_lost_cb:actually_do_call:do_call:ffi_call_SYSV:ffi_call Status in “hud” package in Ubuntu: Fix Released Status in “hud” source package in Saucy: New Bug description: SRU for saucy. [Impact] A reported crash in certain situations. [Test Case] A crasher, no clear test case. Ensure errors.ubuntu.com stops reporting this. [Regression Potential] Low, doing graceful exiting instead of abort. The Ubuntu Error Tracker has been receiving reports about a problem regarding hud. This problem was most recently seen with version 13.10.1+13.10.20131014-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/23bafefb567e15de49e41a1fda7e468768652425 contains more details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hud/+bug/1244688/+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 1199877] Re: unity-panel-service memory leak and 100% CPU usage
I have installed the packages from saucy-proposed (and indicator-appmenu manually). I'm fairly sure the main problem is fixed. I have pinned a terminal running top to the top, and made some test with Sublime Text 3. Opening Sublime makes unity-panel-service use a full core for a good few seconds. Accessing the menu does moderately increase CPU usage for unity-panel-service while it is accessed. Closing the menu makes unity- panel-service use a full core for 1-2 seconds. Same when Sublime is closed. Switching focus back and forth between gnome-terminal and Sublime makes unity-panel-service use a full core for 1-2 seconds. I haven't noticed any prolonged periods of CPU usage, as was the case before. -- 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/1199877 Title: unity-panel-service memory leak and 100% CPU usage Status in The Application Menu: Fix Committed Status in Application Menu Indicator 13.10 series: Fix Committed Status in The Ubuntu Power Consumption Project: New Status in Unity: Invalid Status in “gtk+3.0” package in Ubuntu: In Progress Status in “indicator-appmenu” package in Ubuntu: In Progress Status in “unity” package in Ubuntu: Invalid Status in “gtk+3.0” source package in Saucy: Fix Committed Status in “indicator-appmenu” source package in Saucy: In Progress Bug description: Impact: high CPU/memory usage from unity-panel-service Test case: Open a large image in the GIMP and activate a lot of items from the global menu. Using shortcuts is enough and faster to reproduce this bug (I've always used Ctrl+A and Ctrl+Shift+A). Memory usage of unity- panel-service increases steadily and it uses a lot of CPU shortly after activating the menu items in a short time. Regression potential: check that the menus are stable/working as they should - Just going about my business on Ubuntu Raring amd64 on an x230 and I heard the fan kick into action. top showed me that unity-panel-service was consuming all the free cycles on one of my CPUs. I killed it before my machine overheated, so I didn't attach a debugger to see why it was totally pegging out a CPU. I'm not sure if this adds any context, but I was using a LibreOffice spreadsheet and I could not insert a table because the menu had lost it's mind, and then I observed the overly loaded CPU a very short while after that. To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-appmenu/+bug/1199877/+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 1244483] Re: Top panel doesn't refresh. Applets and menu freeze and are not responsive
*** This bug is a duplicate of bug 1199877 *** https://bugs.launchpad.net/bugs/1199877 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/1244483 Title: Top panel doesn't refresh. Applets and menu freeze and are not responsive Status in “unity” package in Ubuntu: Confirmed Bug description: I'm mostly posting this because someone in #ubuntu told me to, and no one seems to have any good ideas as to what's causing it or how to debug it. It seems that randomly my top panel freezes. I can tell typically because my clock stops at a particular time and doesn't advance. Randomly this then unfreezes later, but while it's frozen if I click on any of my applets or on any of the menus in the top panel (for a particular application) nothing happens. I don't get a drop down menu of options, or any additional information about the applet. This means that while my panel is frozen, I'm unable to shut down my computer (aside from using the command line) or perform any tasks that don't have a keyboard short cut and require the menus for the application. Let me know if I can provide anymore information. Assuming the logs I have are time stamped one happened today (10-24-13) around 3:34:43PM (I remember because I read the clock a lot around then to see if it was un-frozen). ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: unity 7.1.2+13.10.20131014.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-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 319.60 Wed Sep 25 14:28:26 PDT 2013 GCC version: gcc version 4.8.1 (Ubuntu/Linaro 4.8.1-10ubuntu8) .tmp.unity.support.test.0: ApportVersion: 2.12.5-0ubuntu2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Thu Oct 24 18:26:51 2013 DistUpgraded: Fresh install DistroCodename: saucy DistroVariant: ubuntu DkmsStatus: nvidia-319-updates, 319.60, 3.11.0-12-generic, x86_64: installed GraphicsCard: NVIDIA Corporation GF119M [NVS 4200M] [10de:1056] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0494] InstallationDate: Installed on 2013-10-20 (4 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) JockeyStatus: kmod:nvidia_319_updates - nvidia_319_updates (Proprietary, Enabled, Not in use) kmod:nvidia_304 - NVIDIA binary Xorg driver, kernel module and VDPAU library (Proprietary, Disabled, Not in use) kmod:nvidia_304_updates - NVIDIA binary Xorg driver, kernel module and VDPAU library (Proprietary, Disabled, Not in use) kmod:nvidia_319 - NVIDIA binary Xorg driver, kernel module and VDPAU library (Proprietary, Disabled, Not in use) MachineType: Dell Inc. Latitude E6520 MarkForUpload: True ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.11.0-12-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/11/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A06 dmi.board.asset.tag: 1285245 dmi.board.name: 0J4TFW dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.asset.tag: 1285245 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA06:bd07/11/2011:svnDellInc.:pnLatitudeE6520:pvr01:rvnDellInc.:rn0J4TFW:rvrA01:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6520 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.10+13.10.20131011-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.46-1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.2.1-1ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.2.1-1ubuntu3 version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A version.xserver-xorg-core: xserver-xorg-core 2:1.14.3-3ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.2.0-0ubuntu10 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.904-0ubuntu2 version.xserver-xorg-video-nouveau:
[Dx-packages] [Bug 775434] Re: Keyboard shortcut - Make Unity keyboard shortcuts configurable
** Changed in: unity-2d (Ubuntu) Status: Confirmed = Won't Fix ** Changed in: unity-2d Status: Triaged = Won't Fix ** 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/775434 Title: Keyboard shortcut - Make Unity keyboard shortcuts configurable Status in Ayatana Design: Fix Committed Status in Unity: Triaged Status in Unity 2D: Won't Fix Status in “unity” package in Ubuntu: Triaged Status in “unity-2d” package in Ubuntu: Won't Fix Bug description: Currently Unity provides about two dozen keyboard shortcuts which are completely hardcoded. It is essenetial from a productivity standpoint for the user to be able to configure any of those. It was possible with Metacity / Compiz through the Keyboard Shortcuts window. The same interface could be used for Unity for updating its configuration and possibly featuring few Unity-specific keybindings. Desired resolution: - All the unity keyboard shortcuts (defined in the following document, https://docs.google.com/a/canonical.com/document/d/1jqeKtIJwqLtl58Wk_fqjr9Rrgxn9zsouCYOo-cZsLSE/edit?hl=en_GB ) should be present and configurable using the 'Keyboard/Shortcuts' panel in 'System Settings' - Any keyboard shortcuts that are not supported by Unity should be removed. Review the following keyboard shortcut bugs before fixing this bug: - F10 shortcut is used to show menu and this is wrong (#878492) - Ctrl Alt Del doesn't do what most people typing it would expect (#890747) - Unity window placement shortcuts require a numpad (#751050) - Add keyboard shortcut hint overlay that is displayed when a user presses and holds the Super key (#855532) - The grid keybindings are behaving inconsistently (#878820) - Make Unity keyboard shortcuts configurable (#775434) - Shortcuts need to updated as part of the 12.04 upgrade (#891757) - Unity should also use Super-L to lock screen by default (#830709) - Improvements to Launcher reveal when Super is pressed behaviour (#905342) To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/775434/+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 1197213] Re: Heads up display does not work in 13.10
I'm having the same problem with every single application under Ubuntu 13.10 64bit... Why is that these type of bugs, of essential functional get to the final release! I'm so mad that Ubuntu decided to ditch the majority of its desktop user just so they can pursue a while dream of Ubuntu Touch... so frustrated! -- 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/1197213 Title: Heads up display does not work in 13.10 Status in “hud” package in Ubuntu: Confirmed Bug description: The Heads up display feature does not work in ubuntu 13.10. the interface invokes on pressing the alt key. But it does nothing when the first few letters or the entire text is typed. Please fix this bug as soon as possible Thanks and Have a nice day :) ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: hud 13.10.1+13.10.20130702-0ubuntu1 ProcVersionSignature: Ubuntu 3.10.0-2.9-generic 3.10.0 Uname: Linux 3.10.0-2-generic i686 ApportVersion: 2.10.2-0ubuntu3 Architecture: i386 Date: Wed Jul 3 06:46:22 2013 EcryptfsInUse: Yes InstallationDate: Installed on 2013-05-21 (42 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Alpha i386 (20130101) MarkForUpload: True ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_IN SHELL=/bin/bash SourcePackage: hud UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hud/+bug/1197213/+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 1192646] Re: shouldn't list inactive items
** Changed in: hud (Ubuntu Saucy) Importance: Undecided = High -- 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/1192646 Title: shouldn't list inactive items Status in Unity HUD: Fix Committed Status in Unity HUD 13.10 series: In Progress Status in “hud” package in Ubuntu: Fix Released Status in “hud” source package in Saucy: Fix Released Bug description: [Impact] All Ubuntu users using Unity and the HUD. [Test case] - start gedit - open the hud - look for undo It lists the undo item from the edit menu, it shouldn't since there is nothing to undo and the menu item is greyed out. [Regression potential] Since this changes how menu items are identified on whether or not they need to be shown, there could be unforeseen issues where menu items that should be appearing and used to be appearing are now hidden and considered unavailable. Items that just recently became available may not be visible in the hud. To manage notifications about this bug go to: https://bugs.launchpad.net/hud/+bug/1192646/+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 1197213] Re: Heads up display does not work in 13.10
After following the second part of this guide, I can say that HUD is working fine now. You just have to reset unity, the icons won't be reset, just size and behaivor. Here's the workaround: http://www.webupd8.org/2012/10/how-to-reset-compiz-and-unity-in- ubuntu.html -- 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/1197213 Title: Heads up display does not work in 13.10 Status in “hud” package in Ubuntu: Confirmed Bug description: The Heads up display feature does not work in ubuntu 13.10. the interface invokes on pressing the alt key. But it does nothing when the first few letters or the entire text is typed. Please fix this bug as soon as possible Thanks and Have a nice day :) ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: hud 13.10.1+13.10.20130702-0ubuntu1 ProcVersionSignature: Ubuntu 3.10.0-2.9-generic 3.10.0 Uname: Linux 3.10.0-2-generic i686 ApportVersion: 2.10.2-0ubuntu3 Architecture: i386 Date: Wed Jul 3 06:46:22 2013 EcryptfsInUse: Yes InstallationDate: Installed on 2013-05-21 (42 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Alpha i386 (20130101) MarkForUpload: True ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_IN SHELL=/bin/bash SourcePackage: hud UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hud/+bug/1197213/+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 1246842] Re: tests fail when building with fakeroot
** Summary changed: - libdbusmenu fails to build from source because of test failures + tests fail when building with fakeroot -- You received this bug notification because you are a member of DX Packages, which is subscribed to libdbusmenu in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1246842 Title: tests fail when building with fakeroot Status in “libdbusmenu” package in Ubuntu: New Bug description: To reproduce: sudo apt-get build-dep libdbusmenu apt-get source libdbusmenu cd libdbusmenu* fakeroot dpkg-buildpackage Result: nearly all of the tests fail to run properly: make[5]: Entering directory `/home/al/Source/test/libdbusmenu-12.10.3+13.10.20130913/builddir/gtk2/tests' PASS: test-glib-objects-test FAIL: test-glib-events FAIL: test-glib-events-nogroup FAIL: test-glib-layout FAIL: test-glib-properties FAIL: test-glib-proxy PASS: test-glib-simple-items FAIL: test-glib-submenu Each test hangs for about 10 minutes before failing. All of the error logs are the same: DBus daemon: unix:abstract=/tmp/dbus-AwSfBXRDlN,guid=c42d750fb322fd07af809069527290f0 Client: Started with PID: 27013 Server: Started with PID: 27014 (process:27013): LIBDBUSMENU-GLIB-WARNING **: Unable to get session bus: Error sending credentials: Error sending message: Operation not permitted ** (process:27014): ERROR **: Unable to get name 'org.dbusmenu.test' on DBus Server: Exited with status 133 Client: ** (process:27013): DEBUG: Death timer. Oops. Got to: 0 Client: ** (process:27013): DEBUG: Quiting as we're a failure Client: Exited with status 256 Client: Shutting down Server: Shutting down DBus daemon: Shutdown The json test does not eventually die like the others, instead it just hangs forever (over 2.5 hours now.) The log files contains: DBus daemon: unix:abstract=/tmp/dbus-Irf6GdrlbB,guid=fc747bdf7ec70802e385b3625272912d Server: Started with PID: 27081 ** (process:27081): ERROR **: Unable to get name 'org.dbusmenu.test' on DBus Server: Exited with status 133 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdbusmenu/+bug/1246842/+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 1073114] Re: Shopping Lens Does Not Respect User Privacy
http://www.heise.de/open/meldung/Big-Brother-Award-Austria-fuer-Mark- Shuttleworth-2034943.html -- You received this bug notification because you are a member of DX Packages, which is subscribed to libunity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1073114 Title: Shopping Lens Does Not Respect User Privacy Status in “libunity” package in Ubuntu: Confirmed Status in “unity-lens-shopping” package in Ubuntu: Confirmed Status in “libunity” source package in Quantal: Confirmed Status in “unity-lens-shopping” source package in Quantal: Confirmed Status in “libunity” source package in Raring: Confirmed Status in “unity-lens-shopping” source package in Raring: Confirmed Bug description: See this from the Electronic Frontier Foundation (EFF), a well respected international non-profit digital rights advocacy and legal organization (as described on Wikipedia): https://www.eff.org/deeplinks/2012/10/privacy-ubuntu-1210-amazon-ads- and-data-leaks Obviously, despite some improvements that have came late in the 12.10 development cycle, there are still serious privacy concerns with the unity shopping lens. To be more precise, here are the main problems to be fixed according to EFF: - Disable Include online search results by default. - Explain in detail what Canonical does with search queries and IP addresses, how long it stores them, and in what circumstances it gives them to third parties. - Make the Search Results tab of the Privacy settings let users toggle on and off specific online search results, as some users might want Amazon products in their search results, but never anything from Facebook. Here is another related bug: #1055952 Direct data leaking to Amazon: https://bugs.launchpad.net/ubuntu/+source/unity-lens- shopping/+bug/1055952 ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: unity-lens-shopping 6.8.0-0ubuntu1 Uname: Linux 3.5.6-030506-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.6.1-0ubuntu6 Architecture: amd64 Date: Tue Oct 30 06:35:38 2012 InstallationDate: Installed on 2012-02-12 (260 days ago) InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012) MarkForUpload: True SourcePackage: unity-lens-shopping UpgradeStatus: Upgraded to quantal on 2012-09-28 (31 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libunity/+bug/1073114/+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 906231] Re: Unity rendered behind windows
I'm having this exact problem in Saucy amd64 (compiz 0.9.10). I have no clue about what triggered it. Should I reopen the bug? compiz1:0.9.10+13.10.20 all unity 7.1.2+13.10.20131 amd64 unity-services7.1.2+13.10.20131 amd64 ** Attachment added: dash in background.png https://bugs.launchpad.net/unity/+bug/906231/+attachment/3897285/+files/dash%20in%20background.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/906231 Title: Unity rendered behind windows Status in Compiz: Fix Released Status in Compiz 0.9.9 series: Fix Committed Status in Unity: Invalid Status in Unity 5.0 series: Invalid Status in Unity 6.0 series: Invalid Status in “compiz” package in Ubuntu: Fix Released Status in “unity” package in Ubuntu: Invalid Bug description: Confirmed in Ubuntu 11.10, 12.04 and 12.10... Unity randomly goes behind other windows, which should never happen. ORIGINAL DESCRIPTION: Unity's Dock disappears behind all other windows, as you can see from the attached screenshot (making the dock just visible through the shortcut Command+W). Once it has disappeared, the only workaround is to close all applications/restart the desktop to be able to access dock icons or launch any applications through text search, since everything has disappeared to an inaccessible layer. To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/906231/+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
