xfce4-session troubles with conf ?

[iSteve]

Benedikt Meurer wrote:
> iSteve wrote:
> 
>> Of the interesting things in the file...
>>
>> ** (xfce4-session:710): WARNING **: client 
>> 117f000001000107390970300000007100006 timed out
>> /usr/lib/mozilla-firebird/MozillaFirebird-bin: error while loading 
>> shared libraries: libxpcom.so: cannot open shared object file: No such 
>> file or directory
> 
> 
> Ok, heres the answer: Firebird registers a restart command of 
> /usr/lib/mozilla-firebird/MozillaFirebird-bin, but this binary expects 
> some run-time linker settings (actually environment variables) to be set 
> in order to work (usually theres a script called Firebird or Phoenix 
> that sets LD_LIBRARY_PATH to $MOZILLA_HOME/lib or something like that). 
> So no wonder here. Firebird should be fixed to register the script 
> instead of the binary itself.

OK, sort of thought so
> 
>> ** (xfce4-session:710): WARNING **: client 
>> 117f000001000107390896000000007100001 timed out
>> ** (xfce4-session:710): WARNING **: client 
>> 117f000001000107390970300000007100006 timed out
>> ** (xfce4-session:710): WARNING **: client 
>> 117f000001000107394532200000007100025 timed out
>> ** (xfce4-session:710): WARNING **: client 
>> 117f000001000107394658500000007100027 timed out
>>

^^^ just adding, the xterms run fine, but it takes a hellofa time :)

>> these four seems to be 3 xterms and 1 licq:), while licq won't run and 
>> xterm will.
>> ... and xchat, xterms, mozilla firebird and thunderbird are with uid, 
>> xmms is with user Unknown (?:), licq.real is with user isteve, vmware 
>> isn't listed at all.
> 
> 
> As already said, xmms is buggy. The licq problem looks similar to the 
> Firebird problem, to verify it, try to launch "licq.real" from command 
> line. VMWare is known to not being session aware at all.

licq then runs perfectly (I want to get rid of it anyway in the favor of 
  gaim, but I lack visible list and user status info in it:)
> 
> The xterm thingy: Danny, wasn't there some Xresource setting to unbreak 
> xterm in terms of session management?

I'm very interested ... but rather than changing xresources, shouldn't 
this issue be fixed within session manager ?
> 
> regards,
> Benedikt
>