python script engines problem w/ Gmail plasmoid, KDEmod

DarksideEE7 · 2009-10-08 17:21:43

Today after booting my netbook with Arch x86 and KDEmod I noticed that my Gmail plasmoid failed to load, citing that it "could not create a python script engine" for the plasmoid.
Another thing I noticed is that I normally am prompted to enter my kwallet password for the plasma workspace after starting X.

First I reinstalled python and pyqt (I saw that pyqt was updated last night), and that didn't solve it.
I then reinstalled the kdemod version of kwallet, logged out and started X again.......no luck.
I tried disabling kwallet and enabling it with no luck either.

I haven't seen anyone else having these problems just yet, so if anyone has any ideas please let me know.
Thanks in advance.

DarksideEE7 · 2009-10-08 22:53:50

Anyone? This thing is driving me crazy. I'm all but certain that it's a problem with kwallet.....however I don't know how to fix it.

I tried creating another user and copying my xinitrc file to ~/, then starting X and installing the plasmoid. I got the same result So it's not a user thing.
EDIT:
Looks like sip was updated along with pyqt last night, so I just reinstalled with no luck.

Last edited by DarksideEE7 (2009-10-08 23:35:02)

DarksideEE7 · 2009-10-09 01:36:04

Another update:
I upgraded my wife's PC that runs Arch x86_64 with kdemod and the Gmail plasmoid is broken as well. The packages that were upgraded on both PCs are here:

[2009-10-08 11:27] synchronizing package lists
[2009-10-08 11:27] starting full system upgrade
[2009-10-08 11:38] upgraded module-init-tools (3.10-1 -> 3.10-2)
[2009-10-08 11:38] upgraded ortp (0.15.0-1 -> 0.16.1-1)
[2009-10-08 11:38] upgraded sip (4.8.2-1 -> 4.9.0-1)
[2009-10-08 11:38] upgraded pyqt (4.5.4-1 -> 4.6.0-1)
[2009-10-08 11:38] upgraded sdparm (1.03-2 -> 1.04-1)

EDIT:
I just checked my x86 Arch build running in Virtualbox under VIsta x64 and the Gmail plasmoid is working. I'm going to upgrade my system and see if it breaks it............all but guarantee it will.

Ok so I went down each python related package that could have broken the plasmoid last night, logging out of KDE and starting X, and the package that broke this plasmoid is:
sip 4.9.0-1
I started with python and it worked fine after that.

So.......thoughts?

Last edited by DarksideEE7 (2009-10-09 02:19:52)

Amnon82 · 2009-10-09 21:08:34

I rebuilded all needed kdemod-pkgs. It should work now ...

zuargo · 2009-10-10 02:48:41

I had the same problem but with a plasmoid called Plasmacon: http://kde-look.org/content/show.php?content=108120

I downgrade the pyqt package from the 4.6.0-1 version to the 4.5.4-1 version, this allowed me downgrade the sip package from the 4.9.0-1 version to the 4.8.2-1 version.

The plasmoid worked if I launched it from a terminal using the plasmoidviewer command:

$ plasmoidviewer Plasmacon

but if I launched it graphically (right clic on the desktop > Add graphical elements...), gave the same error "Failed to create a python script engine for the graphic element plasmacon".

Then I restarted the system and Plasmacon worked launching it of both ways.

Maybe I must report all this as a bug in the archlinux's bugtracker, what do you think?

Last edited by zuargo (2009-10-10 02:53:27)

DarksideEE7 · 2009-10-10 03:04:07

zuargo wrote:

I had the same problem but with a plasmoid called Plasmacon: http://kde-look.org/content/show.php?content=108120
I downgrade the pyqt package from the 4.6.0-1 version to the 4.5.4-1 version, this allowed me downgrade the sip package from the 4.9.0-1 version to the 4.8.2-1 version.
The plasmoid worked if I launched it from a terminal using the plasmoidviewer command:
$ plasmoidviewer Plasmacon
but if I launched it graphically (right clic on the desktop > Add graphical elements...), gave the same error "Failed to create a python script engine for the graphic element plasmacon".
Then I restarted the system and Plasmacon worked launching it of both ways.
Maybe I must report all this as a bug in the archlinux's bugtracker, what do you think?

Nope, then packages that Amnon rebuilt fixed the problem. Make sure that you have the Stuttgart repo (instead of the rit.edu American, it only syncs every 24 hours) and just:
sudo pacman -Syu
You should get ~400MB worth of DLs and 1GB installed. This fixed the plasmoid for me.

zuargo · 2009-10-10 05:22:58

right, you have every reason, that fixed the problem.

Thanks a lot Amnon and darkside

DarksideEE7 · 2009-10-10 05:52:06

zuargo wrote:

right, you have every reason, that fixed the problem.
Thanks a lot Amnon and darkside

Glad to help:)

mogra · 2009-11-08 00:31:29

Sorry to revive an old topic. I am getting this same error recently and have updated since Ammon's post. Any idea?

DarksideEE7 · 2009-11-08 00:39:56

mogra wrote:

Sorry to revive an old topic. I am getting this same error recently and have updated since Ammon's post. Any idea?

I'm not having any problems atm on any of my systems running the gmail plasmoid.

Arch Linux

#1 2009-10-08 17:21:43

python script engines problem w/ Gmail plasmoid, KDEmod

#2 2009-10-08 22:53:50

Re: python script engines problem w/ Gmail plasmoid, KDEmod

#3 2009-10-09 01:36:04

Re: python script engines problem w/ Gmail plasmoid, KDEmod

#4 2009-10-09 21:08:34

Re: python script engines problem w/ Gmail plasmoid, KDEmod

#5 2009-10-10 02:48:41

Re: python script engines problem w/ Gmail plasmoid, KDEmod

#6 2009-10-10 03:04:07

Re: python script engines problem w/ Gmail plasmoid, KDEmod

#7 2009-10-10 05:22:58

Re: python script engines problem w/ Gmail plasmoid, KDEmod

#8 2009-10-10 05:52:06

Re: python script engines problem w/ Gmail plasmoid, KDEmod

#9 2009-11-08 00:31:29

Re: python script engines problem w/ Gmail plasmoid, KDEmod

#10 2009-11-08 00:39:56

Re: python script engines problem w/ Gmail plasmoid, KDEmod

Board footer