[Maverick] XFCE system tray became unusable after libgtk upgrade
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Xfce4 Panel |
Confirmed
|
Unknown
|
|||
gtk+2.0 (Ubuntu) |
Invalid
|
Low
|
Unassigned | ||
xfce4-panel (Ubuntu) |
Fix Released
|
High
|
Unassigned |
Bug Description
After upgrade to libgtk2.0-0 2.21.0-1ubuntu2, XFCE system tray stopped working. No icons are visible, and CPU load is 100% while tray is displayed (task manager attributes most of this load to X server). Workaround is to downgrade libgtk2.0-0 to version 2.20.1-0ubuntu1.
Architecture: amd64
Linux 2.6.34-3-generic
xserver-xorg 1:7.5+5ubuntu1
xserver-
libxfce4util4 4.6.2-1ubuntu1
libxfcegui4-4 4.6.4-1
libexo-0.3-0 0.3.107-1ubuntu1
xfce4-panel 4.6.4-1
WORKAROUND:
When installing Maverick Meerkat, the systray appears in the middle of the screen, with three icons flashing constantly. This prevents the installation from the live environment, and makes the desktop pretty much unusable after any installation completes.
To use the system after starting, open Applications -> System -> System Monitor. It will take a few seconds to minutes to open due to those flashing windows/icons. Hilight and kill the following Processes:
gnome-volume-
nm-applet
update0-notifier
xfce4-power-manager
Now you should be able to use the system as usual until the next login.
tags: | added: maverick xubuntu |
summary: |
- System tray became unusable after upgrade to xfce4-panel 4.6.4-1 + [Maverick] System tray became unusable after upgrade to xfce4-panel + 4.6.4-1 |
tags: | added: iso-testing |
description: | updated |
description: | updated |
summary: |
- [Maverick] XFCE system tray became unusable after upgrade to libgtk2.0-0 - 2.21.0-1ubuntu2 + [Maverick] XFCE system tray became unusable after libgtk upgrade |
Changed in xfce4-panel (Ubuntu): | |
status: | Confirmed → Triaged |
importance: | Undecided → High |
Changed in xfce4-panel: | |
status: | Unknown → Confirmed |
Changed in gtk+2.0 (Ubuntu): | |
status: | Incomplete → Invalid |
I've found that this bug is actually triggered by upgrade of libgtk2.0-0, not xfce4-panel. Version 2.21.0-1ubuntu2 is affected, and version 2.20.1-0ubuntu1 isn't.