sillysloft / fluxbox

Fluxbox Window Manager (Mirror)
http://fluxbox.org/news/
Other
0 stars 1 forks source link

Restarting fluxbox fails to display systray icons #682

Open sillysloft opened 17 years ago

sillysloft commented 17 years ago

Fluxbox fails to display systray icons after restarting. Using the menu entry [restart] fluxbox restarts and not all the systray icons are restored.

Steps to reproduce the bug:

Start Azureus and enable system tray (Tools > Options > Interface > Enable System tray) restart azureus if required. Make sure the icon shows up in the tray area.

Start Psi (example) and enable docklet (Psi > Options > Application > Enable Docklet). Make sure the icon shows up in the tray area.

Restart fluxbox with the "Restart" entrance in the menu.

Psi icon still shows up but Azureus doesn't. Both programs are still running. To make Azureus window appear, start the program again.

This happened under 1.0_rc2 but not on 0.9.15.1

$ fluxbox -i Fluxbox version: 1.0rc2-gentoo-r2 Compiled: Jan 12 2007 00:50:44 Compiler: GCC Compiler version: 3.4.6 (Gentoo 3.4.6-r1, ssp-3.4.5-1.0, pie-8.7.9)

Defaults: menu: /usr/share/fluxbox/menu style: /usr/share/fluxbox/styles/Clean keys: /usr/share/fluxbox/keys init: /usr/share/fluxbox/init nls: /usr/share/fluxbox/nls

Compiled options (- => disabled): -DEBUG EWMH -GNOME IMLIB2 -KDE NLS REMEMBER RENDER SHAPE SLIT TOOLBAR XFT -XINERAMA XMB XPM

Reported by: darking

sillysloft commented 17 years ago

Logged In: NO

Same with me. Seems only KDE tray icons survive (for me korgac, kpowersave and amarok) and GNOME/GTK ones do not (e.g. liferea and seahorse-agent, the latter effectively killing outgoing SSH connection attempts...).

Original comment by: nobody

sillysloft commented 17 years ago

Logged In: YES user_id=1538990 Originator: NO

Are you _sure_ this didn't happen on 0.9.15.1? This should have nothing to do with fluxbox, as it is up to the application to request docking when a new systemtray appears.

Original comment by: mark-t

sillysloft commented 17 years ago

Original comment by: mark-t

sillysloft commented 17 years ago

Original comment by: darking

sillysloft commented 17 years ago

Logged In: YES user_id=1142349 Originator: YES

Right now I'm not sure it didn't. At that time I think I checked both versions, but I can't remember exactly... You say that it's more likely to be an application problem. Maybe something changed with azureus and it now has this behavior. If I have some free time I will try to rollback to the older version and see if the problem happens there too.

Original comment by: darking

sillysloft commented 17 years ago

Original comment by: rathnor

sillysloft commented 17 years ago

Logged In: YES user_id=603593 Originator: NO

please try with latest svn, i believe this should be fixed.

Original comment by: rathnor

sillysloft commented 17 years ago

Logged In: YES user_id=1312539 Originator: NO

This Tracker item was closed automatically by the system. It was previously set to a Pending status, and the original submitter did not respond within 14 days (the time period specified by the administrator of this Tracker).

Original comment by: sf-robot

sillysloft commented 17 years ago

Original comment by: sf-robot