![]() Administrator ![]()
|
Given that you are using the Factory repository, you may need to refresh it, as the packages may have already been updated again.
KDE Sysadmin
[img]content/bcooksley_sig.png[/img] |
![]() Registered Member ![]()
|
I believe that I refreshed my repos, but I'll try again to make sure. I'm not sure if I refreshed after installing the extra KDE repo. I checked my wife's PC (running Linux Mint x86_64) and she has all of the files needed. I tried the python clock and it worked fine.... Anyhow I'll give it a shot and see how it goes. Thanks for the help. |
![]() Administrator ![]()
|
This could also be a bug in the openSUSE packaging of the Python script engine, if ensuring you have the latest packages doesn't fix the problem.
KDE Sysadmin
[img]content/bcooksley_sig.png[/img] |
![]() Registered Member ![]()
|
I agree. I install Arch Linux on my netbook, and all of my python plasmoids work fine....so it must be some problem with openSUSE's python libraries. It works fine in Arch and on my wife's rig with Linux Mint x86_64.
I couldn't get the gmail plasmoid working on openSUSE or Fedora 10. Go figure. |
![]() Registered Member ![]()
|
Confirm this problem on Kubuntu Jaunty with KDE 4.3 beta 2 KDE4 from PPA:
After that I see empty plasmoid with error "Could not create a python ScriptEngine for the ...". The plasma python files are exists on my system:
plasma-scriptengine-python package is installed, version 4:4.2.90-0ubuntu1~jaunty1~ppa2 How I can turn on traceback for give more info what KDE cannot found? |
![]() Administrator ![]()
|
KDE may be assuming it will be Python 2.4.
KDE Sysadmin
[img]content/bcooksley_sig.png[/img] |
![]() Registered Member ![]()
|
How I can view which version of Python (2.4 or 2.6) is assuming by KDE?
I have the python-qt4 package in dependencies of kde, that depend on python (< 2.7), python (>= 2.5) and have a python 2.6.2-0ubuntu1 installed. Maybe I need install any additional python package? P.S. I have updated to KDE 4.3 RC1 (4.2.95-0ubuntu1~jaunty1~ppa1) but this issue isn't solved on it. |
![]() Administrator ![]()
|
Another possibility is that the Desktop file for the Python script engine is damaged or missing, or PyKDE has not been installed.
|
![]() Registered Member ![]()
|
Installing PyQt4-devel solved the problem of not being able to use any applet written in python for me.
The error Could not create Scriptengine for python (Kann python-Skript-Treiber nicht starten.). This error was caused be the symbol error posted in this topic. So this may be a solution to most of us...
42: There is no other answer. There are only different ways to express it.
0x2A 0o52 0b101010 |
![]() Registered Member ![]()
|
Hi,
I've got python-qt and python-qt4 installed but am still unable to launch these widgets. I'm running openSUSE 11.1 with KDE 4.1.3. On a different computer I have openSUSE 11.0 with KDE 4.3.1 and they work fine there. Any other ideas? Thanks, David. |
![]() Administrator ![]()
|
The Plasma API has changed significantly since KDE 4.1.3. Please update to KDE 4.3.
KDE Sysadmin
[img]content/bcooksley_sig.png[/img] |
![]() Registered Member ![]()
|
I have now bought a new computer and upgraded to openSUSE 11.2 and KDE 4.4.3. All working well now.
|
![]() Registered Member ![]()
|
I have the same problem on Ubuntu 11.04 x64 with KDE 4.6.5, cannot see widgets installed from the web, the following message is displayed: Could not create a python ScriptEngine for the "X" widget.
Please help, BTW I installed python-qt4 from apt. Same results. Regards, Jorge |
![]() Registered Member ![]()
|
I am using KDE 4.7.3 on Linux Mint 12 (Lisa)
I was having similar error while trying to add python widgets like facebook etc. I looked around and found that the package plasma-scriptengine was not installed by default. Once I installed that package (using package manager apt), the issue got resolved. So, KDE installed on Linux Mint works fine as far as this issue is concerned. |
![]() Registered Member ![]()
|
I am using Xubuntu 14.04 and KDE latest version (4.x something, according to this ubuntu, i don't exactly which). This error was fixed for me by installing '
'. In my case,
fixed the problem. I got some information from this answer. https://bbs.archlinux.org/viewtopic.php?pid=709009#p709009 I hope this helps some ubuntu/Debian Guys. ![]() ![]() ![]() ![]() |
Registered users: Bing [Bot], Google [Bot], Sogou [Bot]