abrt version: 1.1.5 architecture: i686 cmdline: python /usr/bin/printer-applet component: kdeutils executable: /usr/bin/printer-applet kernel: 2.6.35-0.41.rc5.git1.fc14.i686 package: kdeutils-printer-applet-6:4.4.92-1.fc14 reason: posixpath.py:119:dirname:AttributeError: 'QString' object has no attribute 'rfind' release: Fedora release 14 (Rawhide) time: 1279392903 uid: 500 backtrace ----- posixpath.py:119:dirname:AttributeError: 'QString' object has no attribute 'rfind' Traceback (most recent call last): File "/usr/bin/printer-applet", line 1163, in <module> applet = JobManager() File "/usr/bin/printer-applet", line 241, in __init__ uic.loadUi(APPDIR + '/' + "printer-applet.ui", self.mainWindow) File "/usr/lib/python2.6/site-packages/PyQt4/uic/__init__.py", line 177, in loadUi return DynamicUILoader().loadUi(uifile, baseinstance) File "/usr/lib/python2.6/site-packages/PyQt4/uic/Loader/loader.py", line 24, in loadUi return self.parse(filename, os.path.dirname(filename)) File "/usr/lib/python2.6/posixpath.py", line 119, in dirname i = p.rfind('/') + 1 AttributeError: 'QString' object has no attribute 'rfind' Local variables in innermost frame: p: PyQt4.QtCore.QString(u'/usr/share/kde4/apps/printer-applet/printer-applet.ui')
Created attachment 432620 [details] File: backtrace
Pretty obvious what's going wrong here: the kdeutils printer-applet is trying to pass a QString to a function (os.path.dirname) that expects a regular Python string. It needs to be converted to a Python string first.
Package: kdeutils-printer-applet-6:4.4.92-1.fc14 Architecture: i686 OS Release: Fedora release 14 (Rawhide) How to reproduce ----- 1. Boot 2. --- 3. This error. Comment ----- I have a warning about printer-applet every time I log in
I reported this bug to the upstream bugzilla [1] and attached there a patch that fixes this issue. [1] https://bugs.kde.org/show_bug.cgi?id=245289
Package: kdeutils-printer-applet-6:4.4.92-1.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Rawhide) How to reproduce ----- 1. log into computer 2. get abort backtrace 3. Comment ----- log in to desktop
Package: kdeutils-printer-applet-6:4.4.92-1.fc14 Architecture: i686 OS Release: Fedora release 14 (Rawhide) How to reproduce ----- 1. Start KDE 2. Login (Printer is switched off) 3. Crash happens.
Package: kdeutils-printer-applet-6:4.4.95-1.fc14 Architecture: i686 OS Release: Fedora release 14 (Rawhide) How to reproduce ----- just log into kde
Sorry, I failed to notice the patch attached upstream. http://bugs.kde.org/attachment.cgi?id=49356 let's get that integrated asap, and once confirmed fixed, into kde svn.
Package: kdeutils-printer-applet-6:4.4.95-1.fc14.py27 Architecture: i686 OS Release: Fedora release 14 (Rawhide) How to reproduce ----- 1. Occurs at boot into Fedora Rawhide Comment ----- Occurs with Rawhide fresh install and also with upgrade from 13
This bug appears to have been reported against 'rawhide' during the Fedora 14 development cycle. Changing version to '14'. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
This issue was fixed upstream, see: https://bugs.kde.org/show_bug.cgi?id=245289
Package: kdeutils-printer-applet-6:4.4.95-1.fc14.py27 Architecture: x86_64 OS Release: Fedora release 15 (Rawhide) How to reproduce ----- 1. Just login into KDE :-) 2. 3.
Package: kdeutils-printer-applet-6:4.4.92-1.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Rawhide) How to reproduce ----- 1. Boot system 2. Login to KDE 3. abrt shows crash Comment ----- Simply logged in to KDE
This is fixed in 4.5.0.
just a note, this hits F14 Alpha RC3 KDE live, since the fixed package didn't make it into the RC3 spin. -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
Oh joy. :-( Darn, I forgot about that! I don't think we should pull in all of 4.5.0 into the alpha. We could build a package with a backported patch, but of course this would require another alpha RC compose. Grrr…
And it seems a desktop that actually works properly is only required for Final according to the release criteria.
Yes, this issue by itself doesn't constitute an Alpha blocker. We will have an RC4, we might consider taking a fix for this if it's very small and simple. The compose is planned to happen tomorrow (likely afternoon). (The theory of the Alpha desktop release criteria, btw, is that as long as you can run a browser to read about what's broken and an updater to get the fixes, then that's damn well good enough for an Alpha :). As I did say repeatedly via email, though, the criteria are always open to revision and I'd love to have feedback from the SIGs on what they'd like to see in them.) -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
-- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
-- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
*** Bug 633951 has been marked as a duplicate of this bug. ***