[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: kpanel in Squeeze not coming up reliably


many thanks for your reply. I followed your .xsession-errors suggestion, after 
I saw a broken KDE startup today again. As you mentioned, it is not easy to do 
that, the .xsession-errors file is 1.6 MB long (!).

Since my post and your reply are some days back and self-contained 

I observe from time to time, that during the start of my KDE session, the 
panel, all plasmoid, the screen background, etc. die. Essentially I see only 
windows from the previous session, nothing else.

When I compare .xsession-errors from such a broken startup with a good 
startup, I see these additional entries there (I see these rarely, therefore I 
have only one testcase so far):

Traceback (most recent call last):
File "/usr/share/kde4/apps/plasma_scriptengine_python/pyappletscript.py", line 
75, in init
File "/home/rd/.kde/share/apps/plasma/plasmoids/sipgate-
plasmoid/contents/code/main.py", line 98, in init
File "/home/rd/.kde/share/apps/plasma/plasmoids/sipgate-
plasmoid/contents/code/main.py", line 117, in readConfig
File "/home/rd/.kde/share/apps/plasma/plasmoids/sipgate-
plasmoid/contents/code/main.py", line 141, in updateMessages
File "/home/rd/.kde/share/apps/plasma/plasmoids/sipgate-
plasmoid/contents/code/anbieter/sipgate.py", line 129, in getNewMessages
File "/home/rd/.kde/share/apps/plasma/plasmoids/sipgate-
plasmoid/contents/code/anbieter/sipgate.py", line 75, in __connect
self.__send_method(self.samurai.ClientIdentify, args_identify)
File "/home/rd/.kde/share/apps/plasma/plasmoids/sipgate-
plasmoid/contents/code/anbieter/sipgate.py", line 83, in __send_method
xmlrpc_result = func(args)
File "/usr/lib/python2.6/xmlrpclib.py", line 1199, in __call__
return self.__send(self.__name, args)
File "/usr/lib/python2.6/xmlrpclib.py", line 1489, in __request
File "/usr/lib/python2.6/xmlrpclib.py", line 1243, in request
xmlrpclib.ProtocolError: <ProtocolError for 
rdorsch:None@samurai.sipgate.net/RPC2: 401 Authorization Required>

I cannot say for sure that the sipgate plasmoid http://kde-
look.org/content/show.php/Sipgate-plasmoid?content=114887 is the reason that 
the startup of the session is broken, but at least I see the difference above 
in the .xsession-errors file.

The complete .xsession-errors files (good start and broken start) are here:


Any insight what is the problem, if not the sipgate plasmoid, is very welcome.

For now, I remove the sipgate plasmoid and check if the startup becomes more 


Am Montag, 7. Februar 2011 schrieb Adrian von Bidder:
> On Sunday 06 February 2011 18.34:14 Rainer Dorsch wrote:
> > I checked, /var/log/kdm.log and /var/log/Xorg.0.log,
> The first place I always check is ~/.xsession-errors, which is
> stdout/stderr of most things that are started via the X session. OTOH it's
> quit hard to check since it's spammed by too many things usually.  A clean
> up task force would be needed ;-)
> cheers
> -- vbi

Rainer Dorsch
Lärchenstr. 6
D-72135 Dettenhausen
email: rdorsch@web.de
jabber: rdorsch@jabber.org
GPG Fingerprint: 5966 C54C 2B3C 42CC 1F4F  8F59 E3A8 C538 7519 141E
Full GPG key: http://pgp.mit.edu/

Attachment: signature.asc
Description: This is a digitally signed message part.

Reply to: