Summary: | gdesklets causes Python-Error instead of starting | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Benjamin Judas (RETIRED) <beejay> |
Component: | [OLD] GNOME | Assignee: | Gentoo Linux Gnome Desktop Team <gnome> |
Status: | VERIFIED WORKSFORME | ||
Severity: | normal | ||
Priority: | Normal | ||
Version: | 1.4 | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | Output of emerge --verbose /usr/portage/gnome-extra/gdesklets-core/gdesklets-core-0.22.1.ebuild |
Description
Benjamin Judas (RETIRED)
![]() I merged gdesklets-core from Portage. I specified the ebuild directly since I don't use ~x86. When I start the daemon at first, I get a Python error so gdesklets won't startup. I installed gdesklets on my Notebook the same way (by specifiying the ebuild directly) and gdesklets just works fine. I can't see any differences between my Notebook and my Desktop-PC and now I'm stuck and don't have another idea. This is the error I get: benni@antares ~ $ gdesklets gDesklets 0.22.1 Copyright © 2003 Martin Grimme, Christian Meyer, Jesse Andrews This software is licensed under the terms of the GNU GPL. Traceback (most recent call last): File "/usr/bin/gdesklets", line 30, in ? starter.start_displays() File "/usr/share/gdesklets/main/Starter.py", line 197, in start_displays self.__on_watch(None, displays) File "/usr/share/gdesklets/main/Starter.py", line 88, in __on_watch self.__add_display(id, displays[id]) File "/usr/share/gdesklets/main/Starter.py", line 105, in __add_display dsp = self.__create_display(id, path) File "/usr/share/gdesklets/main/Starter.py", line 139, in __create_display display = self.__factory.create_display(id, data) File "/usr/share/gdesklets/factory/DisplayFactory.py", line 54, in create_display sax.parseString(data, self) File "/usr/lib/python2.2/site-packages/_xmlplus/sax/__init__.py", line 47, in parseString parser.parse(inpsrc) File "/usr/lib/python2.2/site-packages/_xmlplus/sax/expatreader.py", line 107, in parse self.reset() File "/usr/lib/python2.2/site-packages/_xmlplus/sax/expatreader.py", line 236, in reset self._parser = expat.ParserCreate(intern = self._interning) TypeError: 'intern' is an invalid keyword argument for this function benni@antares ~ $ I already tried to compile the "original" Package from the gdesklets-website but I get the same error. If you need any additional Information or ressources please feel free to file a request. Thanks in advance Benjamin "beejay" Judas could you please add your version of python and emerge info ? thanks. self._parser = expat.ParserCreate(None, " ", intern=self._interning) is the function i have in the .py, but it's on a slightly different line to yours. Sorry, I could have thought about including this information ;) Ok, I took a look into the gdesklets-core ebuild, these are the RDEPENDs: RDEPEND=">=dev-lang/python-2.2 >=gnome-base/gconf-2 >=dev-python/pygtk-1.99.14 >=dev-python/gnome-python-1.99.14 >=x11-libs/gtk+-2" And these are the installed Versions: dev-lang/python-2.2.3-r1 gnome-base/gconf-2.4.0.1 dev-python/pygtk-1.99.16 dev-python/gnome-python-1.99.16 x11-libs/gtk+-2.2.4-r1 I'll now go on and change the code - maybe it works. Changing the Sourcecode didn't change anything - error is still present. Changed line back to original Version. Created attachment 19196 [details]
Output of emerge --verbose /usr/portage/gnome-extra/gdesklets-core/gdesklets-core-0.22.1.ebuild
This is the --verbose output when I emerge the package (I cannot see anything
suspicious -- but I'm not the specialist ;) )
do you have dev-libs/expat installed ? Solved! It wasn't expat. I saw someting about xml in the output of the python-error. So I did an "emerge search xml" | grep py. I found pyxml in the resulting output. An "emerge -p pyxml" showed that pyxml was _very_ outdated. The installed Version was pyxml-0.7.1 and the upgrade was Version 0.8.2 ("x86"-Tree). I updated and now everything runs fine. I don't know when pyxml had been installed originally and why it was never included in an "emerge -u world". Well, this bug is now solved for me. Thanks for your help obz - I suggest to close this one. Regards, Benjamin "beejay" Judas This was definitely the solution -- closing this bug |