DockbarX 0.41 doesn't work very correctly in dual-monitor mode

I'm seeing this too after switching to a multi-monitor setup (NVIDIA TwinView).

The OP's screen shot is a bit busy, so I'll describe what I'm seeing. I have a primary display with a GNOME panel at the top and DockBarX on it. I have a secondary display located to the left.

Hovering the mouse over an application icon on DockBarX results in the window list menu appearing in the upper right hand corner of the display on the left, rather than below the application icon.

Other observations:

When this is happening, it is more difficult than usual to get the DockBarX context menu (the one with Preferences) to appear. Right-clicking on the "sweet spot" just does nothing.

If you launch a second instance of DockBarX, it behaves correctly. If you can get the context menu to appear on the original instance, you can remove it and be left with one working instance.

What happens if you reload dockbarx? Change the theme from dbx_preference if you can't get to the context menu (double right-clicking might work though).

Do you have any errors in ~/.dockbarx/log/dockbarx.log after this happened?

Could it be that dockbarx is initialized before twinview is? I don't know much about twinveiw.

@Thai
Do you use twinview as well or do you use some different dual monitor setup?

Matias Särs wrote:
> What happens if you reload dockbarx?

No change. I killed and restarted it multiple times in an attempt to get
it to work. It wasn't until I tried two simultaneous docks that I was
successful.

> Change the theme from dbx_preference...

I'm using Gaia currently.

I could test a different theme. (If I recall, any theme customizations
are lost when you switch themes, right?)

> Do you have any errors in ~/.dockbarx/log/dockbarx.log after this
> happened?

I think the lines below correspond with the instance that had problems.
I can try clearing the log and reproduce the issue later.

There's a whole slew of errors logged further down in the log, but I
think those all happened after I had worked around the problem.

ERROR | 2011-02-21 12:52:05,287 | /usr/bin/dockbarx_factory:76: Warning:
g_set_prgname() called multiple times
  "dockbar applet", "0", dockbar_factory)
INFO | 2011-02-21 12:52:05,310 | DockbarX 0.43
INFO | 2011-02-21 12:52:05,310 | DockbarX init
INFO | 2011-02-21 12:52:05,733 | DockbarX reload
DEBUG | 2011-02-21 12:52:05,861 | Opened window matched with gio app on
id: firefox
DEBUG | 2011-02-21 12:52:05,866 | Opened window matched with gio app on
id: twinkle
DEBUG | 2011-02-21 12:52:05,872 | Opened window matched with gio app on
id: roxterm
DEBUG | 2011-02-21 12:52:05,917 | Opened window matched with gio app on
id: pidgin
DEBUG | 2011-02-21 12:52:05,950 | Opened window matched with gio app on
id: vinagre
DEBUG | 2011-02-21 12:52:05,955 | Opened window matched with gio app on
id: gnome-system-monitor
DEBUG | 2011-02-21 12:52:05,960 | Opened window matched with gio app on
id: gnome-panel
ERROR | 2011-02-21 12:52:09,181 |
/usr/lib/pymodules/python2.6/dockbarx/iconfactory.py:265:
DeprecationWarning:
PyArray_FromDimsAndDataAndDescr: use PyArray_NewFromDescr.
  for row in pb.get_pixels_array():
DEBUG | 2011-02-21 12:54:24,683 | Opened window matched with gio app on
id: nvidia-settings
DEBUG | 2011-02-21 13:05:17,939 | Opened window matched with gio app on
id: dbx_preference
DEBUG | 2011-02-21 13:09:50,191 | Opened window matched with gio app on
id: gnome-about
DEBUG | 2011-02-21 17:50:42,523 | Opened window matched with gio app on
id: gwibber-accounts
DEBUG | 2011-02-21 18:00:02,634 | Opened window matched with gio app on
id: gwibber-accounts
DEBUG | 2011-02-21 18:09:43,208 | Opened window matched with gio app on
id: gwibber
DEBUG | 2011-02-21 18:14:04,918 | Opened window matched with gio app on
executable: gnome-terminal
DEBUG | 2011-02-21 18:15:42,306 | Opened window matched with gio app on
id: gwibber-accounts
DEBUG | 2011-02-21 18:24:52,366 | Opened window matched with gio app on
id: gwibber-accounts
ERROR | 2011-02-21 20:16:05,723 | Traceback (most recent call last):
ERROR | 2011-02-21 20:16:05,723 | File
"/usr/lib/pymodules/python2.6/dockbarx/windowbutton.py", line 185, in _
_on_window_icon_changed
ERROR | 2011-02-21 20:16:05,754 |
self.button.set_icon(window.get_mini_icon(), window.get_icon())
ERROR | 2011-02-21 20:16:05,755 | File
"/usr/lib/pymodules/python2.6/dockbarx/cairowidgets.py", line 581, in s
et_icon
ERROR | 2011-02-21 20:16:05,778 | pixbuf =
self.make_minimized_icon(icon)
ERROR | 2011-02-2...

Hi,

I have also this problem with the 0.39 version of dockbarX on ubuntu 10.04 x64.

I use an intel graphic card with open source drivers so I don't think the bug is related with Nvidia drivers.

Thanks

I have the same problem. A workaround is to restart gnome-panel:

gnome-panel --replace

I use DockbarX from the PPA (Version 0.43) and Ubuntu Natty.

Matias Särs wrote:
> What happens if you reload dockbarx?

Update on my prior comment...I found that if I select the "Refresh" option from the applet's context menu, it resolves the problem.

Yes, right-clicking the dockbarx applet and selecting "Refresh" indeed makes the menus appear at the right positions again. And its simpler than restarting gnome-panel.

Ok, I finally got a fix committed for this bug. DockbarX now checks which monitor it's on when every time it needs that info instead of just checking once when DockbarX is starting/reloading. Hopefully that will do the trick. I also hope this fix doesn't slow down anything. I don't think that checking for monitor number for a window should use that many CPU cycles, but who knows?

I also noticed that VirtualBox 4.0.8 (perhaps older versions as well?) allows me to simulate dual screen so I will probably be better at fixing dualscreen bugs in the feature.

Can anyone confirm that the bug is properly fixed?

Yes, for me this bug is fixed in version 0.44 from the dockbar-main PPA.

Thank you very much!