Lost all background transparency in dockbarx 0.24.0

Bug #507692 reported by Josh
34
This bug affects 7 people
Affects Status Importance Assigned to Milestone
DockbarX
Fix Released
Undecided
Unassigned

Bug Description

After changing display settings for vga output the dock has lost all transparency and just has a white background. After trying to change dockbar settings and themes and other display settings in Ubuntu 9.04 nothing has returned the transparency.

This is only happening in dockbarx and not the normal dockbar. I have looked for support for this problem but haven't found anyone else who has had this problem so I am posting it here because it may be a bug.

Revision history for this message
Josh (joshbarker2) wrote :
Revision history for this message
Marcin Koziol (marcin-koziol-outi) wrote :

I want to confirm the bug. This happened after the latest update (ubuntu 9.10) unfortunately can't recall what packages was updated. Effect as above.

Revision history for this message
Michaël Vanderheeren (michael-vanderheeren) wrote :

Please when possible provide us with your update log. It can be found here:

Synaptic > File > History

Revision history for this message
Matias Särs (msevens) wrote :

Does changing gtk or metacity theme help?

Revision history for this message
Josh (joshbarker2) wrote :

I haven't updated to 9.10 yet and the dock looked fine until I tried to output through vga to my tv and it didn't work right and when I set it back to my laptop screen is when it looked like this now it wont change back.

Changing the gtk or metacity themes doesn't help.

Heres the update log for the day this happened:

Commit Log for Thu Jan 14 23:44:18 2010

Upgraded the following packages:
transmission-common (1.51-0ubuntu3) to 1.51-0ubuntu3.1
transmission-gtk (1.51-0ubuntu3) to 1.51-0ubuntu3.1

Commit Log for Thu Jan 14 23:42:22 2010

Installed the following packages:
libxcb-shape0 (1.1.93-0ubuntu3.1)
libxcb-shm0 (1.1.93-0ubuntu3.1)
libxcb-xv0 (1.1.93-0ubuntu3.1)
libxine1 (1.1.16.3-0ubuntu1)
libxine1-bin (1.1.16.3-0ubuntu1)
libxine1-console (1.1.16.3-0ubuntu1)
libxine1-ffmpeg (1.1.16.3-0ubuntu1)
libxine1-gnome (1.1.16.3-0ubuntu1)
libxine1-misc-plugins (1.1.16.3-0ubuntu1)
libxine1-x (1.1.16.3-0ubuntu1)
totem-xine (2.26.1-0ubuntu5.1)

Revision history for this message
Michaël Vanderheeren (michael-vanderheeren) wrote :

It's obviously not due to your update which has only things for either video or the gtk bittorrent client. Did you already reboot your computer (trivial question maybe, but you never know). It seems that something in the driver and gtk caused it. Does removing Dockbar and adding it again help?

Revision history for this message
Marcin Koziol (marcin-koziol-outi) wrote :

This is my update log:

19 jan.
cairo-dock (2.1.3-0beta1-20100105-0ubuntu1~ppa0~karmic) to 2.1.3-0rc1-20100116-0ubuntu1~ppa0~karmic
cairo-dock-core (2.1.3-0beta1-20100105-0ubuntu1~ppa0~karmic) to 2.1.3-0rc1-20100116-0ubuntu1~ppa0~karmic
cairo-dock-data (2.1.3-0beta1-20100105-0ubuntu1~ppa0~karmic) to 2.1.3-0rc1-20100116-0ubuntu1~ppa0~karmic
cairo-dock-plug-ins (2.1.3-0beta1-20100105-0ubuntu1~ppa0~karmic) to 2.1.3-0rc1-20100116-0ubuntu1~ppa0~karmic
cairo-dock-plug-ins-data (2.1.3-0beta1-20100105-0ubuntu1~ppa0~karmic) to 2.1.3-0rc1-20100116-0ubuntu1~ppa0~karmic
cairo-dock-plug-ins-integration (2.1.3-0beta1-20100105-0ubuntu1~ppa0~karmic) to 2.1.3-0rc1-20100116-0ubuntu1~ppa0~karmic
kdepimlibs-data (4:4.3.2-0ubuntu1) to 4:4.3.2-0ubuntu1.1
kdepimlibs5 (4:4.3.2-0ubuntu1) to 4:4.3.2-0ubuntu1.1
libpulse-browse0 (1:0.9.19-0ubuntu4) to 1:0.9.19-0ubuntu4.1
libpulse-mainloop-glib0 (1:0.9.19-0ubuntu4) to 1:0.9.19-0ubuntu4.1
libpulse0 (1:0.9.19-0ubuntu4) to 1:0.9.19-0ubuntu4.1
libpurple-bin (1:2.6.2-1ubuntu7) to 1:2.6.2-1ubuntu7.1
libpurple0 (1:2.6.2-1ubuntu7) to 1:2.6.2-1ubuntu7.1
libthai-data (0.1.12-1) to 0.1.12-1ubuntu0.2
libthai0 (0.1.12-1) to 0.1.12-1ubuntu0.2
pidgin (1:2.6.2-1ubuntu7) to 1:2.6.2-1ubuntu7.1
pidgin-data (1:2.6.2-1ubuntu7) to 1:2.6.2-1ubuntu7.1
pulseaudio (1:0.9.19-0ubuntu4) to 1:0.9.19-0ubuntu4.1
pulseaudio-esound-compat (1:0.9.19-0ubuntu4) to 1:0.9.19-0ubuntu4.1
pulseaudio-module-bluetooth (1:0.9.19-0ubuntu4) to 1:0.9.19-0ubuntu4.1
pulseaudio-module-gconf (1:0.9.19-0ubuntu4) to 1:0.9.19-0ubuntu4.1
pulseaudio-module-udev (1:0.9.19-0ubuntu4) to 1:0.9.19-0ubuntu4.1
pulseaudio-module-x11 (1:0.9.19-0ubuntu4) to 1:0.9.19-0ubuntu4.1
pulseaudio-module-zeroconf (1:0.9.19-0ubuntu4) to 1:0.9.19-0ubuntu4.1
pulseaudio-utils (1:0.9.19-0ubuntu4) to 1:0.9.19-0ubuntu4.1
rhythmbox (0.12.5-0ubuntu5.1) to 0.12.5-0ubuntu5.2
software-center (1.0.2) to 1.0.3

18 jan.

google-chrome-unstable (4.0.288.1-r35555) to 4.0.295.0-r35884
libssl-dev (0.9.8g-16ubuntu3) to 0.9.8g-16ubuntu3.1
libssl0.9.8 (0.9.8g-16ubuntu3) to 0.9.8g-16ubuntu3.1
openssl (0.9.8g-16ubuntu3) to 0.9.8g-16ubuntu3.1
php5-cli (5.2.10.dfsg.1-2ubuntu6.3) to 5.2.10.dfsg.1-2ubuntu6.4
php5-common (5.2.10.dfsg.1-2ubuntu6.3) to 5.2.10.dfsg.1-2ubuntu6.4
php5-gd (5.2.10.dfsg.1-2ubuntu6.3) to 5.2.10.dfsg.1-2ubuntu6.4
transmission-common (1.75-0ubuntu2.1) to 1.75-0ubuntu2.2
transmission-gtk (1.75-0ubuntu2.1) to 1.75-0ubuntu2.2

IMHO none of this packages can affect dockbar...

Revision history for this message
Josh (joshbarker2) wrote :

I have removed everything for it then reinstalled it back in and still nothing changed. I also rebooted after removing and after reinstalling it back in.

Revision history for this message
Matias Särs (msevens) wrote :

Ok, maybe there's an error message (you never know)...

kill dockbarx with "killall dockbarx.py" and write "dockbarx.py" in an terminal before choosing to restart dockbarx from the dialog message that pops up.

Revision history for this message
Marcin Koziol (marcin-koziol-outi) wrote :

Hmm there is nothing about this bug (i think..)

~$ kill 16572
dialog pops up
~$ dockbarx.py

** (dockbarx.py:16591): WARNING **: Trying to register gtype 'WnckWindowState' as flags when in fact it is of type 'GEnum'

** (dockbarx.py:16591): WARNING **: Trying to register gtype 'WnckWindowActions' as flags when in fact it is of type 'GEnum'

** (dockbarx.py:16591): WARNING **: Trying to register gtype 'WnckWindowMoveResizeMask' as flags when in fact it is of type 'GEnum'
/usr/bin/dockbarx.py:4435: Warning: g_set_prgname() called multiple times
  "dockbar applet", "0", dockbar_factory)

and nothigh happens

Revision history for this message
Marcin Koziol (marcin-koziol-outi) wrote :

Ok, something strange...

after several restarts of dockbarx and gnome panel AND these updates i have transparency:

Commit Log for Thu Jan 21 08:49:44 2010

Updated:
bind9-host (1:9.6.1.dfsg.P1-3ubuntu0.2) to 1:9.6.1.dfsg.P1-3ubuntu0.3
dnsutils (1:9.6.1.dfsg.P1-3ubuntu0.2) to 1:9.6.1.dfsg.P1-3ubuntu0.3
gnome-power-manager (2.28.1-0ubuntu1) to 2.28.1-0ubuntu1.1
gzip (1.3.12-8ubuntu1) to 1.3.12-8ubuntu1.1
libbind9-50 (1:9.6.1.dfsg.P1-3ubuntu0.2) to 1:9.6.1.dfsg.P1-3ubuntu0.3
libdns53 (1:9.6.1.dfsg.P1-3ubuntu0.2) to 1:9.6.1.dfsg.P1-3ubuntu0.3
libexpat1 (2.0.1-4ubuntu1) to 2.0.1-4ubuntu1.1
libexpat1-dev (2.0.1-4ubuntu1) to 2.0.1-4ubuntu1.1
libgssapi-krb5-2 (1.7dfsg~beta3-1ubuntu0.3) to 1.7dfsg~beta3-1ubuntu0.4
libgssrpc4 (1.7dfsg~beta3-1ubuntu0.3) to 1.7dfsg~beta3-1ubuntu0.4
libisc50 (1:9.6.1.dfsg.P1-3ubuntu0.2) to 1:9.6.1.dfsg.P1-3ubuntu0.3
libisccc50 (1:9.6.1.dfsg.P1-3ubuntu0.2) to 1:9.6.1.dfsg.P1-3ubuntu0.3
libisccfg50 (1:9.6.1.dfsg.P1-3ubuntu0.2) to 1:9.6.1.dfsg.P1-3ubuntu0.3
libk5crypto3 (1.7dfsg~beta3-1ubuntu0.3) to 1.7dfsg~beta3-1ubuntu0.4
libkadm5srv6 (1.7dfsg~beta3-1ubuntu0.3) to 1.7dfsg~beta3-1ubuntu0.4
libkdb5-4 (1.7dfsg~beta3-1ubuntu0.3) to 1.7dfsg~beta3-1ubuntu0.4
libkrb5-3 (1.7dfsg~beta3-1ubuntu0.3) to 1.7dfsg~beta3-1ubuntu0.4
libkrb5-dev (1.7dfsg~beta3-1ubuntu0.3) to 1.7dfsg~beta3-1ubuntu0.4
libkrb5support0 (1.7dfsg~beta3-1ubuntu0.3) to 1.7dfsg~beta3-1ubuntu0.4
liblwres50 (1:9.6.1.dfsg.P1-3ubuntu0.2) to 1:9.6.1.dfsg.P1-3ubuntu0.3
quassel (0.5.0-0ubuntu1) to 0.5.0-0ubuntu1.1
quassel-data (0.5.0-0ubuntu1) to 0.5.0-0ubuntu1.1

Installed
libkadm5clnt6 (1.7dfsg~beta3-1ubuntu0.4)

Revision history for this message
Josh (joshbarker2) wrote :

This is what it says. It looks like something to do with my theme but it still does the same thing even when i change the theme an restart the bar.

acer@acer-laptop:~$ killall dockbarx.py
acer@acer-laptop:~$ dockbarx.py
/home/acer/.themes/Win7.Basic.02/gtk-2.0/panel.rc:7: Unable to locate image file in pixmap_path: "Panel/panel-bg.png"
/home/acer/.themes/Win7.Basic.02/gtk-2.0/panel.rc:61: Unable to locate image file in pixmap_path: "Panel/panelbutton.png"
/home/acer/.themes/Win7.Basic.02/gtk-2.0/panel.rc:64: Background image options specified without filename
/home/acer/.themes/Win7.Basic.02/gtk-2.0/gtkrc:77: Unable to locate image file in pixmap_path: "Handles/handle-v.png"
/home/acer/.themes/Win7.Basic.02/gtk-2.0/gtkrc:80: Overlay image options specified without filename
/home/acer/.themes/Win7.Basic.02/gtk-2.0/gtkrc:85: Unable to locate image file in pixmap_path: "Handles/handle-h.png"
/home/acer/.themes/Win7.Basic.02/gtk-2.0/gtkrc:88: Overlay image options specified without filename
/home/acer/.themes/Win7.Basic.02/gtk-2.0/gtkrc:1690: Unable to locate image file in pixmap_path: "Handles/handle-v.png"
/home/acer/.themes/Win7.Basic.02/gtk-2.0/gtkrc:1693: Overlay image options specified without filename
/home/acer/.themes/Win7.Basic.02/gtk-2.0/gtkrc:1697: Unable to locate image file in pixmap_path: "Handles/handle-h.png"
/home/acer/.themes/Win7.Basic.02/gtk-2.0/gtkrc:1700: Overlay image options specified without filename

Revision history for this message
Marcin Koziol (marcin-koziol-outi) wrote :

I found something else:

I have thunderbird 3 from original binary package from mozilla in /opt/thunderbird. I have created shortcut in some folder in my home, so i d'n'd the shortcut to button of running thunderbird. After login/logout the transparency is gone but thunderbird entry is still present in gconf. I remove that entry and right-click->refresh applet then transparency is back.

Revision history for this message
Matias Särs (msevens) wrote :

Well, the problem seems to be with your gtk theme after all. Do you get the same errors with other themes?

Revision history for this message
Matias Särs (msevens) wrote :

That last comment was for Josh. Your errors doesn't seem to be realated.

@Marcin
Odd, that sounds like a bug that _should_ give some kind of error message. You don't get any more in your output in the terminal?

Revision history for this message
Marcin Koziol (marcin-koziol-outi) wrote :

@Matias
How to get any output?

mojzesz@mojzesz-desktop:~$ killall dockbarx.py
[poup still visible]
mojzesz@mojzesz-desktop:~$ dockbarx.py

** (dockbarx.py:4087): WARNING **: Trying to register gtype 'WnckWindowState' as flags when in fact it is of type 'GEnum'

** (dockbarx.py:4087): WARNING **: Trying to register gtype 'WnckWindowActions' as flags when in fact it is of type 'GEnum'

** (dockbarx.py:4087): WARNING **: Trying to register gtype 'WnckWindowMoveResizeMask' as flags when in fact it is of type 'GEnum'
/usr/bin/dockbarx.py:4435: Warning: g_set_prgname() called multiple times
  "dockbar applet", "0", dockbar_factory)

and that's all

Revision history for this message
Marcin Koziol (marcin-koziol-outi) wrote :

oh
it takes some time:

dockbar init
Traceback (most recent call last):
  File "/usr/bin/dockbarx.py", line 4422, in dockbar_factory
    dockbar = DockBar(applet)
  File "/usr/bin/dockbarx.py", line 3770, in __init__
    self.reload()
  File "/usr/bin/dockbarx.py", line 3853, in reload
    self.add_launcher(res_class, path)
  File "/usr/bin/dockbarx.py", line 4148, in add_launcher
    self.groups.add_group(res_class, GroupButton(self, launcher=launcher), path)
  File "/usr/bin/dockbarx.py", line 1977, in __init__
    self.button.drag_source_set_icon_pixbuf(self.icon_factory.find_icon_pixbuf(32))
  File "/usr/bin/dockbarx.py", line 681, in find_icon_pixbuf
    if self.icontheme.has_icon('application-default-icon'):
AttributeError: IconFactory instance has no attribute 'icontheme'

** (dockbarx.py:4087): WARNING **: need to free the control here
Traceback (most recent call last):
  File "/usr/bin/dockbarx.py", line 2479, in on_sizealloc
    self.update_state()
  File "/usr/bin/dockbarx.py", line 2063, in update_state
    pixbuf = self.icon_factory.pixbuf_update(self.state_type)
  File "/usr/bin/dockbarx.py", line 445, in pixbuf_update
    pixbuf = f(pixbuf, **args)
  File "/usr/bin/dockbarx.py", line 611, in command_get_icon
    self.pixbuf = self.find_icon_pixbuf(size)
  File "/usr/bin/dockbarx.py", line 681, in find_icon_pixbuf
    if self.icontheme.has_icon('application-default-icon'):
AttributeError: IconFactory instance has no attribute 'icontheme'
Traceback (most recent call last):
  File "/usr/bin/dockbarx.py", line 2479, in on_sizealloc
    self.update_state()
  File "/usr/bin/dockbarx.py", line 2063, in update_state
    pixbuf = self.icon_factory.pixbuf_update(self.state_type)
  File "/usr/bin/dockbarx.py", line 445, in pixbuf_update
    pixbuf = f(pixbuf, **args)
  File "/usr/bin/dockbarx.py", line 611, in command_get_icon
    self.pixbuf = self.find_icon_pixbuf(size)
  File "/usr/bin/dockbarx.py", line 681, in find_icon_pixbuf
    if self.icontheme.has_icon('application-default-icon'):
AttributeError: IconFactory instance has no attribute 'icontheme'
/usr/bin/dockbarx.py:953: DeprecationWarning: PyArray_FromDimsAndDataAndDescr: use PyArray_NewFromDescr.
  for row in pixbuf.get_pixels_array():
Executing firefox
/usr/bin/dockbarx.py:967: DeprecationWarning: PyArray_FromDimsAndDataAndDescr: use PyArray_NewFromDescr.
  rows = pixbuf.get_pixels_array()
/usr/bin/dockbarx.py:968: DeprecationWarning: PyArray_FromDimsAndDataAndDescr: use PyArray_NewFromDescr.
  mask_rows = mask.get_pixels_array()

Revision history for this message
Matias Särs (msevens) wrote :

Ok, That's better. Marcin's bug was fixed and committed to the bzr branch almost a month ago. It will be include in the next release (which should be a week away or so), but you should try it out anyway just to be sure it's the same bug.

Revision history for this message
Josh (joshbarker2) wrote :

Sorry for taking so long to respond again.

I have tried with other original ubuntu themes and it doesn't give me any errors or anything else back in the terminal like before, but Its still the same result with the other themes.

Im really not sure what it us that Marcin did to get his working so I can try it to see if it will fix mine the same way.

Revision history for this message
Marcin Koziol (marcin-koziol-outi) wrote :

still the same in bzr version.

Revision history for this message
Matias Särs (msevens) wrote :

Do you get the same error message as well or did that disappear?

Revision history for this message
Sandro (alessandro-mascia) wrote :

I had the same problem on karmic. I added a new panel with a new dockbarx and the transparency works. The old dockbarx on the first panel doesn't has transparency, even wen you move it to the new panel.

Revision history for this message
jackjacks (jackerjacks) wrote :

Ubu 9.10 problem not solved for me. Dont know how to fix it. Any idea?

Revision history for this message
JPtja (jpvd) wrote :

I only can say that I've got the same problem..

Revision history for this message
Matias Särs (msevens) wrote :

A possible fix ported from vanilla dockbar is included in the last commit. Please test it and tell me if it works!

Changed in dockbar:
status: New → Fix Committed
Revision history for this message
Matias Särs (msevens) wrote :

And another fix committed. This one should work for pixmap based gtk themes like new wave as well. Tell me if it works.

Revision history for this message
Eemil Lagerspetz (eemil-lagerspetz) wrote :

gnome-panel transparency (panel preferences - solid color - opacity slider adjusting) with dockbarx-24.1 did not work with new wave; dockbarx and a majority of panel elements remained opaque. With the current committed version, dockbarx is properly transparent.

Matias Särs (msevens)
Changed in dockbar:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.