DockbarX appears to lock-up and has rendering problems
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
DockbarX |
Fix Committed
|
Undecided
|
Unassigned |
Bug Description
Using 0.90.3-
Within the last few weeks (month?) I've noticed that after running for a while (perhaps a week) something degrades, and when I mouse over an item on Dockbar's dock, no pop-up menu will appear. Likewise for right click. I'll sometimes see a rendering artefact coincident with this that appears like a transparent rectangle extending across my desktop that is sized and positioned to match where a pop-up menu would appear (though at the moment one is appearing on the far right of my screen, some distance from the dock). I can slide windows beneath this transparent box, but the image within the box remains frozen, and attempting to click on anything covered by the box does nothing.
The transparent area does seem to appear in response to an action that should display a pop-up menu. After restarting Dockbar there is no transparent area. Hovering the mouse over a docked item that has a long window list results in the transparent area happening again.
This has happened a couple of times in the past month. Sending an interrupt (ctrl-c in the console) to Dockbar had the effect of fixing the problem the first few times it happened. At the moment, killing and restarting it isn't helping. Dockbar displays, but is unresponsive.
In the process table I see:
~% ps aux | fgrep -i doc
tmetro 6394 59.0 0.7 364868 45228 pts/9 Rs+ 01:40 0:27 /usr/bin/python /usr/bin/dockx
tmetro 6398 0.0 0.0 130896 5108 ? S 01:41 0:00 /usr/lib/
Killing dockmanager-daemon has no effect. Killing dockx works, but as above, the restart doesn't fix it.
Any other related process that should be killed/restarted? Is there a Dbus interface that's hanging or something?
I'm running Dockbar from the console, but don't see anything interesting logged. Just:
DockbarX 0.90
DockbarX init
DockbarX reload
Xlib.protocol.
Prior to the initial lock-up I saw:
(Pidgin:7425): LIBDBUSMENU-
(Pidgin:7425): LIBDBUSMENU-
** (totem-
** (totem-
** (totem-
** (totem-
** (totem-
** Message: Error: Could not demultiplex stream.
matroska-
Got a seek error
totem-video-
Traceback (most recent call last):
File "/usr/bin/
self.
File "/usr/bin/
model, iter = selection.
AttributeError: 'NoneType' object has no attribute 'get_selected'
(totem:3107): GLib-GObject-
Executing: pidgin
It would seem that if I launch Nautilus from Dockbar, it logically is a child of Dockbar, and then anything I launch from Nautilus, like double-clicking on a video to launch Totem, becomes a child as well, and the console from thioe children are being seen mixed in with Dockbar messages.
That likely means the messages above are irrelevant, though I seem to recall that there was a totem issue the last time this happened.
Looks like the version of Dockbar I'm using hasn't changed since November, so the problem must be the result of interaction with something else that changed on my system.
I see while this is happening dockx is using up 80% CPU. After a restart it goes back to zero, but spikes again after a mouse over.
Ah...I think I found it...specifically mousing over my Firefox icon triggers the problem. If I avoid that icon the dock remains interactive.
I currently have 49 browser windows, plus the bookmark manager open. Perhaps I'm exceeding some limit on the menu size?