[Bug 338996] [NEW] most simple plasma script does not run

Isma Ismail_k at web.de
Sat Mar 7 00:07:32 UTC 2009


Public bug reported:

In Jaunty (9.04):
When I try to run the most simple python plasmoid example from http://techbase.kde.org/Development/Tutorials/Plasma/Python/GettingStarted
I get following output in terminal:
---------------------------------------------------------------------------------------
plasmoidviewer hello-python
plasmoidviewer(7723) KServiceFactory::findServiceByDesktopPath: "findServiceByDesktopPath:  not found"
Traceback (most recent call last):
  File "/usr/share/kde4/apps/plasma_scriptengine_python/pyappletscript.py", line 21, in <module>
    from PyKDE4.plasma import Plasma
ImportError: No module named PyKDE4.plasma
Error in sys.excepthook:
Traceback (most recent call last):
  File "/usr/lib/python2.5/site-packages/apport_python_hook.py", line 77, in apport_excepthook
    pr['PythonArgs'] = '%r' % sys.argv
AttributeError: 'module' object has no attribute 'argv'

Original exception was:
Traceback (most recent call last):
  File "/usr/share/kde4/apps/plasma_scriptengine_python/pyappletscript.py", line 21, in <module>
    from PyKDE4.plasma import Plasma
ImportError: No module named PyKDE4.plasma
----------------------------------------------------------------------------------------------------
And the window which should show the plasmoid says: Could not create a python scriptengine for hello-python.

The needed files all seem to be installed.

Propably the Problem is that some Packages are compiled with python 2.5 like:
python-kde4
and some with python 2.6 libraries??? (like python-plasma)

Version of python-plasma: 4.2.1a-0ubuntu2
Version of python-kde4: 4.2.1-0ubuntu2
Installed python versions: 2.6.1 ,  2.5.4-1ubuntu2 and 3.0, I cold not remove 2.5 without breaking dependencies

** Affects: kdebase-workspace (Ubuntu)
     Importance: Undecided
         Status: New

-- 
most simple plasma script does not run
https://bugs.launchpad.net/bugs/338996
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to kdebase-workspace in ubuntu.




More information about the kubuntu-bugs mailing list