Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#12114 - guidance-power-manager crashes on start

Attached to Project: Arch Linux
Opened by Bart (n0rdik0) - Thursday, 13 November 2008, 22:46 GMT
Last edited by Allan McRae (Allan) - Wednesday, 26 November 2008, 21:09 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To No-one
Architecture All
Severity Low
Priority Normal
Reported Version None
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

Description: guidance-power-manager refuses to start, error:
n0rdik0@telstar ~ $ guidance-power-manager
Traceback (most recent call last):
File "/usr/bin/guidance-power-manager", line 29, in <module>
from PyKDE4.kdecore import KAboutData, KCmdLineArgs, KConfig, i18n, i18nc, i18np, ki18n, ki18nc, KGlobal, KStandardDirs,KLocalizedString
ImportError: Bad magic number in /usr/lib/python2.5/site-packages/PyQt4/__init__.pyc
n0rdik0@telstar ~ $

Tried to reinstall, didn't help.

Additional info:
* package version(s)
guidance-power-manager 4.1.3-1 (kde-extragear)
pyqt 4.4.3-2
python 2.6-2


* config and/or log files etc.


Steps to reproduce:
start guidance-power-manager
This task depends upon

Closed by  Allan McRae (Allan)
Wednesday, 26 November 2008, 21:09 GMT
Reason for closing:  Fixed
Comment by Leonardo (sud_crow) - Friday, 14 November 2008, 02:39 GMT
I can confirm this.

I took almost two weeks on upgrading to python 2.6, and this broke after. So I guess it has to do with the rebuild of the package.

Regards,
Leonardo
Comment by Allan McRae (Allan) - Friday, 14 November 2008, 03:24 GMT
Apparently /usr/lib/python2.5/site-packages/PyQt4/__init__.pyc gets let behind on the pyqt upgrade. Delete it.
Comment by Jan de Groot (JGC) - Friday, 14 November 2008, 07:32 GMT
Can't we delete the .pyc files on post_upgrade? This bug keeps appearing everytime.
Comment by Bart (n0rdik0) - Friday, 14 November 2008, 08:20 GMT
Deleting __init__.pyc has this effect:

n0rdik0@telstar ~ $ guidance-power-manager
/usr/lib/python2.6/site-packages/PyQt4/uic/Compiler/qobjectcreator.py:2: DeprecationWarning: the sets module is deprecated
from sets import Set as set # Python 2.3 compatibility
Traceback (most recent call last):
File "/usr/bin/guidance-power-manager", line 36, in <module>
from powermanage import *
File "/usr/share/apps/guidance-power-manager/powermanage.py", line 27, in <module>
import xf86misc
ImportError: Bad magic number in /usr/lib/python2.5/site-packages/xf86misc.pyc
n0rdik0@telstar ~ $

Do I rm this file too?
Comment by Allan McRae (Allan) - Friday, 14 November 2008, 08:51 GMT
yes. We do need to deal with these pyc file better on upgrade...
Comment by Bart (n0rdik0) - Friday, 14 November 2008, 10:42 GMT
Ok, once removed those two files, guidance-power-manager runs ok. Thanks guys!
Comment by Aaron Griffin (phrakture) - Wednesday, 26 November 2008, 17:52 GMT
Hmmm, closable? Or do we want to figure out a sane way to deal with the pyc files?
Comment by Allan McRae (Allan) - Wednesday, 26 November 2008, 21:09 GMT
I am working on a policy to deal with .pyc/.pyo files better for the next big python upgrade and have got it on my wiki TODO list so it will not get lost. This is closable.

Loading...