Missing Icons in system tray when Compiz is used...

Bug #111232 reported by ksamvel
14
Affects Status Importance Assigned to Milestone
compiz (Ubuntu)
New
Undecided
Unassigned

Bug Description

Hi,

I have Kubuntu 7.10 installed on my laptop (fresh install) with compiz effects used. Everything seems to be fine except that for some reason after boot up some icons in system tray simply do not show up. For example I have KNetworkManager running automatically and used as my network tool but icon is not there and if I start an application from terminal it opens currently running one... unfortunately system tray does not change its behavior. Or here is another example: Kopete. It connects automatically but sometimes system tray does not reflect program status: icon simply is not there. I start Kopete manually and currently running program is opened.

So, what I do to get Icon in Taskbar:
  1. Kill application
  2. Run it again. [only then icon shows up].

Described bug takes place not very frequently but sometimes it happens (with occupancy of at least once a week) and drives me crazy.

Is it known bug? Does anybody experience the same issues? How can it be solved?

ksamvel (ksamdev)
description: updated
Revision history for this message
dumas33 (danas-augutis) wrote : Re: Missing Icons in system tray when Beryl is used...

I think it is same issue
https://bugs.launchpad.net/ubuntu/+source/beryl-core/+bug/104439

Beryl starts after these programs. You need to change start order for beryl. It should start before session is loaded

Revision history for this message
William Grant (wgrant) wrote : Beryl has been removed from Gutsy

Beryl is replaced by Compiz Fusion, so has been removed from Gutsy.

  status invalid
  subscribe

Changed in beryl-core:
status: New → Invalid
Revision history for this message
Vangelis Tasoulas (cyberang3l) wrote : Re: Missing Icons in system tray when Beryl is used...

This problem still exists on Kubuntu gutsy using compiz.

Changed in beryl-core:
status: Invalid → New
description: updated
Revision history for this message
simarillion (simarillion) wrote :

Same issue with kubuntu and compiz

Also tried starting compiz via script in /usr/bin:

#!/bin/bash
compiz &
sleep 5
emerald --replace || kwin --replace

and edited ~/.profile :
export KDEWM=startcompiz

without success.

Revision history for this message
Vangelis Tasoulas (cyberang3l) wrote :

A workaround that is working for me, is to create a two lines script and place it under your ~/.kde/Autostart folder.
I have created this file:
/.kde/Autostart/compiz

with the following content:

#!/bin/bash
sleep 5
compiz --replace

Don`t forget to make it executable :)

Revision history for this message
chris613 (chris-2byteconsulting) wrote :

Also on kubuntu 7.10

Vangelis' fix works sometimes, as does changing KDEWM as simarillion suggests. It's not reliable unless I make the sleep even longer, though, it's clearly a race condition between the system tray processes and compiz startup. Has anyone found a solid workaround for this that doesn't involve long sleep times? Can we somehow delay starting session processes until after compiz is done starting up?

Revision history for this message
Travis Watkins (amaranth) wrote :

Random guess at what is going on. An app with an rgba colormap can't embed in an rgb app and vice versa. I'm guessing the panel starts with an rgb colormap because compiz hasn't started at that point and then the notification icons automatically get an rgba colormap through Qt (I doubt they'd set one manually). In this case XEmbed fails and you get applets popped out. Does this only happen with Qt apps or does something like pidgin have this problem too?

Revision history for this message
KasimirK (berlin) wrote :

One way to solve this problem that has worked for me:
Instead of running compiz by putting it into /home/<user>/.kde/Autostart, add a new file called /usr/share/autostart/compiz.desktop (see attachment)

Then edit the file /usr/share/autostart/panel.desktop: You need to change the line
        X-KDE-autostart-after=kdesktop
to read
        X-KDE-autostart-after=compiz

This should run compiz before running any application with a tray icon, thus ensuring that all trayicons are there.

Revision history for this message
gbtest85 (gbtest85) wrote :

I had the same problem on a Fujitsu Siemens M1437G, kubuntu 7.10 + ati + xgl + compiz...

The solution of KasimirK worked fine for me.

Revision history for this message
jacoor (jacek-jacoor) wrote :

Well, the thing is still happening on hadry, especially with Kmix - after restarting or rebooting usually works fine...

Revision history for this message
jacoor (jacek-jacoor) wrote :

 KasimirK solution works great, u don't try to use autostart script for disabling touchpad
(script in /home/user/.kde/Autostart with /usr/bin/syndaemon -d -i1 - disables touchpad while typing).
The problem is that with this script i could not get kmix tray icon to show up automagically in tray after restart/reboot.
The solution is to modify the above script by adding sleep 10 before syndaemon.
Hope it helps somebody (it drived me crazy to change volume by keys...)

Revision history for this message
montevjl (montevjl) wrote :

9.04 running, english, kernel updated, gnome, compiz installed. FS 14xx Amilo (creepy).

When booting up, on my profile, a message comes up saying that there is no system tray and it will exit. Click OK, and I am left with desktop. Then :
- I right click on desktop, call for the change desktop background, go to "visual effect" and click for anything (normal, extra, custom...), accept the changes. Screen refreshes and "everything" goes back to normal, systray and its icons.
but... I have to do it every time :-) !

So, from forums, bug reporting, and ... experience... I understand that it probably has something to do with "Compiz".

Before I ransack my computer (do it often...) , can anyone give me a glimpse of what to do or install (I tried Compiz earlier, but didn't get rid of the problem).... mny tks.

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.