User-Agent: Mozilla/5.0 (X11; U; Linux i686; de; rv:1.9.1.5) Gecko/20091105 Fedora/3.5.5-1.fc12 Firefox/3.5.5 In a single head configuration, all systray icons are shown (see first screenshot). When activating a secondary display via xrandr and restarting xfce-panel ("xfce-panel -r", to get this expanded on the secondary display), all icons in the systray disappear (see second screenshot). However, the applications are still there, so you have to guess, which app is at which position. Switching back to single head and restarting xfce-panel will show the icons again. Reproducible: Always Steps to Reproduce: 1. start X in single head 2. activate secondary display via xrandr and restart xfce-panel 3. systray icons disappear Actual Results: systray icons disappear Expected Results: systray icons shown
Created attachment 378947 [details] systray showing icons in single head
Created attachment 378949 [details] systray not showing icons in dual head
Odd. What versions of xfwm4 and xfce4-panel do you have there? Does it do the same if you use the native Xfce display applet to start the other monitor? I wonder if this some more strange fallout from xfce bug 5795.
xfwm4-4.6.1-5.fc12.i686 xfce4-panel-4.6.2-1.fc12.i686 activating the second monitor via xfce display applet does not work since this shows only one (e.g. the internal primary) display.
Sorry for the delay here. Do you have autohide enabled? If you start a new app that would display in the systray, does it show up? Or remain blank? Anything in ~/.xsession-errors?
Due to a midori bug Kevin existentially reassigned this bug to 0xFFFF. Changing it back to xfce4-panel.
Autohide is disabled. New apps will not show (they do exist, but no icon). And unfortunately nothing related in .xsession-errors, except: (xfce4-panel:5199): Gdk-CRITICAL **: gdk_screen_get_monitor_geometry: assertion `monitor_num < screen_x11->n_monitors' failed xfce4-panel-Message: Starte xfce4-panel neu... (xfce4-cpugraph-plugin:5868): Gtk-CRITICAL **: gtk_container_set_border_width: assertion `GTK_IS_CONTAINER (container)' failed ** Message: NM disappeared ** Message: NM appeared
I've seen something strange. OpenOffice has problems showing some GUI elements beyond a certain screen position. See attached screenshot. In OOCalc, all table cells will be show correctly, but in context menues, icons and text labels will be cut off. The position where these elements gets cut off is about 1240 pixels (respectively 2640 pixels, since this is the secondary screen and one would add the 1400 pixels from the primary screen). xfce4-panel's systray, which does not show icons, is also beyond these 1240 pixels. If i move the systray to a position below the 1240 pixles, then all the icons will be shown. If i move the systray to a position somewhere around 1240 pixels, only the first icons will be shown (see screenshot) So i think, this could be relatod to some underlying libraries (e.g. gtk??), Xorg, radeon-driver etc.
Created attachment 384592 [details] OpenOffice context menu cut off
Created attachment 384595 [details] Systray icons shown partly
What video card make/model/driver do you have there? This is a weird issue... ;)
from lspci: 01:00.0 VGA compatible controller: ATI Technologies Inc M24GL [Mobility FireGL V3200] (rev 80) Xorg driver is radeon from: xorg-x11-drv-ati-6.13.0-0.11.20091119git437113124.fc12.i686
Is composite on? 'xfconf-query -c xfwm4 -p /general/use_compositing' will tell you if it is or not. Does toggling it make any difference?
Oh, can you also attach a /var/log/Xorg.0.log and a output of 'xrandr -q' ? Thanks.
composite is off. However, switching composite on has some effect. The systray icons will show now, also icons and labels from popup-menues in OpenOffice. But now, dropdown shadows from windows and popups are cut off at the above-mentioned position. See screenshot. I will also attach Xorg log and xrandr output.
Created attachment 385358 [details] dropdown shadow cut off when composite is turned on
Created attachment 385359 [details] Xorg log
Created attachment 385360 [details] xrandr output
Moving this over to the ati driver, as it's a driver bug.
does the latest -ati in updates fix this? it should have a -20 in it.
yes. latest xorg-x11-drv-ati fixes this. thanks a lot.