dockbarx applet force closes

[Copernicvs]

i got an update from the http://ppa.launchpad.net/dockbar-main/ppa/ubuntu repository yesterday evening for dockbarx, and after reboot, the gnome panel fails to load dockbax applet. i get the message:

The panel encountered a problem while loading "OAFIID:GNOME_DockBarXApplet".

there was another update this morning, but also didn't solve the problem. tried completely removing and then resinstalling the software, but still fails to start.

using linux mint 9, kernel 2.6.35-5.6 and dockbarx 0.39.5.1-0~ppa1

[Matias Särs (msevens)]

This is probably a dubplicate of bug #606568, please confirm if that's the case.

[Matias Särs (msevens)]

If you are unsure of how to confirm, just run dockbarx in window and post the output.

dockbarx_factory.py run-in-window

[John Doe (gehkacken02)]

same problem.
updated yesterday, now it wont load anymore.
ubuntu 10.04

[John Doe (gehkacken02)]

Version: 0.39.5.1-0~ppa1

[Matias Särs (msevens)]

dockbarx_factory.py run-in-window

[MDCore (mdcore)]

When I run that command in the console I get this:

* (dockbarx_factory.py:2758): WARNING **: Trying to register gtype 'WnckWindowState' as enum when in fact it is of type 'GFlags'

** (dockbarx_factory.py:2758): WARNING **: Trying to register gtype 'WnckWindowActions' as enum when in fact it is of type 'GFlags'

** (dockbarx_factory.py:2758): WARNING **: Trying to register gtype 'WnckWindowMoveResizeMask' as enum when in fact it is of type 'GFlags'
Traceback (most recent call last):
  File "/usr/bin/dockbarx_factory.py", line 26, in <module>
    import dockbarx.dockbar
  File "/usr/lib/python2.6/dockbarx/dockbar.py", line 36, in <module>
    from groupbutton import *
  File "/usr/lib/python2.6/dockbarx/groupbutton.py", line 39, in <module>
    import zg
  File "/usr/lib/python2.6/dockbarx/zg.py", line 40, in <module>
    result_type=datamodel.ResultType.MostRecentSubjects,
NameError: name 'datamodel' is not defined

[MDCore (mdcore)]

Following the commands here:
https://bugs.launchpad.net/dockbar/+bug/606568

fixed this for me. I recommend closing this bug as a duplicate of #606568