|  | | Re: Re: sipgate plasmoid unstable (?)
Mar 28 2011 on content Sipgate-plasmoid |
Many thanks for the quick fix. I was hoping KDE downloads the update for me, but it did not :O(
I downloaded then the entire package 114887-sipgate-plasmoid.zip and replaced /home/rd/.kde/share/apps/plasma/plasmoids/sipgate-plasmoid but with that, the plasmoid did not even start anymore.
Do you know the proper way to update a plasmoid? If there is none or not clear, did you maybe just update a single file, which I could replace? |
| | | Re: Re: sipgate plasmoid unstable (?)
Mar 27 2011 on content Sipgate-plasmoid |
Hi hefee,
thanks for the quick reply.
I fixed the permission issue for the .xsession-errors file.
I am running Debian 6.0.1 (stable/squeeze).
KDE in there is 4.4.5, python is 2.6.6
Let me know if you need more information ( http://packages.qa.debian.org/ might help as well) |
| | | sipgate plasmoid unstable (?)
Mar 27 2011 on content Sipgate-plasmoid |
Hello,
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
self.pyapplet.init()
File "/home/rd/.kde/share/apps/plasma/plasmoids/sipgate-plasmoid/contents/code/main.py", line 98, in init
self.readConfig()
File "/home/rd/.kde/share/apps/plasma/plasmoids/sipgate-plasmoid/contents/code/main.py", line 117, in readConfig
self.updateMessages()
File "/home/rd/.kde/share/apps/plasma/plasmoids/sipgate-plasmoid/contents/code/main.py", line 141, in updateMessages
messages=self.server.getNewMessages()
File "/home/rd/.kde/share/apps/plasma/plasmoids/sipgate-plasmoid/contents/code/anbieter/sipgate.py", line 129, in getNewMessages
self.__connect()
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
verbose=self.__verbose
File "/usr/lib/python2.6/xmlrpclib.py", line 1243, in request
headers
xmlrpclib.ProtocolError: <ProtocolError for rdorsch:None@samurai.sipgate.net/RPC2: 401 Authorization Required>
I cannot say for sure that the sipgate plasmoid 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:
http://bokomoko.de/~rd/sipgate-plasmoid/
Any insight what is the problem, if not the sipgate plasmoid, is very welcome. |
| |
Search people
Current visitors
New users
Birthdays
Most active users
Back
|
|
