This is a very obscure problem.
On system A, xfce runs fine.
System B is a 1:1 copy of system A. Same hardware, same software (harddrive imaged).
When XFCE is started on system B, a dialog appears complaining that the
systemtray is already running. The system hangs then until I manually kill
xfce-mcs-manager. Then the panel starts, but without tray.
When I now log out and in again, the message doesn't appear any longer. But the
tray is gone.
When trying to add the tray again, there is a message claiming that this was
I've no idea what the reason might be but I'm really curious. I tried to strace
to xfce-panel while adding the systray plugin, but I didn't see anything useful.
I'll happily do any debugging you might need. Working with gdb and a version
compiled with debugging flags is possible. Just tell me what you need exactly.
Steps to Reproduce:
Usually the reason for this dialog is if there is a systemtray active in the
taskbar. Could you check the taskbar settings dialog?
The taskbar is not running at all. Please note that the *identical*
configuration works on another system. I copied it using dd.
Hmm, ok. It sounds like some sort of race condition to me. Could you maybe send
me a copy of your ~/.config/xfce4/panel/contents.xml ? or attach it to this bug?
I don't really know what would be the best way to find the cause of this behaviour.
Created attachment 288
copied while xfce is running
The bugs seems to be a panel issue but a systray plugin issue. A fix could be
adding an extra check on insert_control() from panel/controls.c when it checks
if the item is systray and its running, if so prompt the proper message. Maybe
other items that are one-instance ran can use this in the future.
Please comment so this is reassigned to xfce4-panel.
I have no idea what is going on. I would be interested to know if this still happens with xfce 4.4 beta2. Maybe someone can try that?
The system was moved to /dev/null a couple of months ago, I'm afraid I can't help anymore.
(In reply to comment #7)
> The system was moved to /dev/null a couple of months ago, I'm afraid I can't
> help anymore.
Ok, no problem. Thanks for responding.
No-one else reported this, so I'll just close it. Thanks for reporting, though.