The xfce4-panel starts up totally transparent with composite extention enabled. Although if i kill the panel and start it manually from a terminal the transparency setting is correct. So I'm not sure if this is a problem with either: 1) xfce4-session, which perhaps starts the panel incorrectly at login 2) xfwm4, which is the composite manager? 3) xfce4-panel I have tried with various setting in my ~/.config/xfce4/transparency and I've also tried copying that file to $installprefix/etc/xdg/xfce4/transparency but neither solved the problem. It seems to me as if transparency file is not read at all at start up. Also when the panel is totally transparent it does not turn solid when i move the mouse over it. But I can right click on where I know the panel is and bring up the panel menu, also the panel buttons seems to work eventhough invisible. Reproducible: Always Steps to Reproduce: 1. Enable composite extention 2. Log in to Xfce 3. Right click where the panel ought to be Actual Results: Panel is totally transparent and does not turn solid when mouse is over. Expected Results: Panel should be semi-transparent and turn solid on mouse over. ~/.config/xfce4/transparency: panel=50 iconbox=0
Heh, cool, is that it? I have the same, but thought the panel just didn't show up. I'm fairly sure it is something I broke, but it may also be xfwm4. Thanks.
I don't see the sympoms you are referring to. Sometimes for me the panel just seems to hang and only kill -9 gets rid of it. Anyway, what happens if you run 'pkill -USR1 xfce4-panel' from a terminal? Does it restart properly?
(In reply to comment #2) > I don't see the sympoms you are referring to. Sometimes for me the panel just > seems to hang and only kill -9 gets rid of it. > > Anyway, what happens if you run 'pkill -USR1 xfce4-panel' from a terminal? Does > it restart properly? Yup pkill -USR1 xfce4-panel restarts the panel okay. But now, running with the latest SVN the problem has expanded. The transparency now covers all windows, I can see that the windows are there because the mouse cursor changes and I can issue commands from a terminal. The only thing that isn't totally transparent are menus. However I think I found out where the problem recides, in xfdesktop. doing a killall -9 xfdesktop fixes the totally transparent windows, so it seems that with xfwm4's composite manager activated xfdesktop is somehow drawn on top of everything. The really odd thing though is that I can still focus windows and stuff eventhough xfdesktop seems to be drawn above everything else. And yea restarting xfdesktop after killing it also restores the problem.
(In reply to comment #3) > (In reply to comment #2) > > I don't see the sympoms you are referring to. Sometimes for me the panel just > > seems to hang and only kill -9 gets rid of it. > > > > Anyway, what happens if you run 'pkill -USR1 xfce4-panel' from a terminal? Does > > it restart properly? > > Yup pkill -USR1 xfce4-panel restarts the panel okay. But now, running with the > latest SVN the problem has expanded. The transparency now covers all windows, I > can see that the windows are there because the mouse cursor changes and I can > issue commands from a terminal. The only thing that isn't totally transparent > are menus. However I think I found out where the problem recides, in xfdesktop. > doing a killall -9 xfdesktop fixes the totally transparent windows, so it seems > that with xfwm4's composite manager activated xfdesktop is somehow drawn on top > of everything. The really odd thing though is that I can still focus windows and > stuff eventhough xfdesktop seems to be drawn above everything else. And yea > restarting xfdesktop after killing it also restores the problem. Update: Tested some more and it seems I was wrong. Perhaps my system is messed up but after I killed xfdesktop I tried to change the root window background with both xsetroot and feh, neither worked. After a while nautilus worked and drew me a background image however it was also magically placed above all windows.
Hmm, this sounds very, very strange indeed. Olivier, do you have any ideas about this?
Well I seems this was my bad, did a rm -rf ~/.config and now it seems to work fine. I figure there was a change in the config files somewhere that messed things up.
Hehe, I like it if people fix their own bugs ;-) Thanks.