Bug 532262 - [abrt] gtk import error
Summary: [abrt] gtk import error
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: system-config-printer
Version: rawhide
Hardware: i686
OS: Linux
low
medium
Target Milestone: ---
Assignee: Tim Waugh
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:b28c0171
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-10-31 22:22 UTC by Mario Chacon
Modified: 2010-08-02 19:56 UTC (History)
26 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2009-11-01 12:25:20 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (6.48 KB, text/plain)
2009-10-31 22:22 UTC, Mario Chacon
no flags Details

Description Mario Chacon 2009-10-31 22:22:05 UTC
abrt detected a crash.


How to reproduce
-----
1.
2.
3.


Additional information
======


Attached files
----
backtrace

cmdline
-----
python /usr/share/system-config-printer/applet.py 


component
-----
system-config-printer


executable
-----
/usr/share/system-config-printer/applet.py


kernel
-----
2.6.31.5-96.fc12.i686


package
-----
system-config-printer-1.1.13-3.fc12


uuid
-----
b28c0171

Comment 1 Mario Chacon 2009-10-31 22:22:09 UTC
Created attachment 366983 [details]
File: backtrace

Comment 2 Tim Waugh 2009-11-01 12:25:20 UTC
The problem is that pygtk2 is not installed.  However, system-config-printer requires 'pygtk2 >= 2.4.0', so your installation has broken dependencies.

Comment 3 Tim Waugh 2009-11-23 10:42:26 UTC
Was this with a fresh installation or an upgrade?  What does 'rpm -q pygtk2' say?  What about 'rpm -V pygtk2'?

Comment 4 Ari Feinberg 2009-11-23 11:37:44 UTC
Upgrade from F11

# rpm -q pygtk2
pygtk2-2.16.0-1.fc12.i686

rpm -V returned nothing.

Comment 5 Tim Waugh 2009-11-23 12:12:04 UTC
What does this say?:

python -c 'import gtk'

Comment 6 Ari Feinberg 2009-11-23 13:52:26 UTC
python -c 'import gtk' returned nothing

Comment 7 Tim Waugh 2009-11-23 14:19:33 UTC
And are you still seeing the original problem?

Comment 8 Robert Haas 2010-03-19 01:10:01 UTC
This same crash showed up in my "Automatic Bug Reporting Tool".  It's a fresh install of FC12, so if my installation is broken, uh, it's not my fault?  Probably?

Comment 9 Tim Waugh 2010-03-19 10:13:05 UTC
Well, what does 'python -c import gtk' say for you?

Comment 10 Robert Haas 2010-03-19 23:25:38 UTC
[rhaas@rhaas ~]$ python -c import gtk
  File "<string>", line 1
    import
         ^
SyntaxError: invalid syntax
[rhaas@rhaas ~]$ python -c 'import gtk'
[rhaas@rhaas ~]$

Comment 11 Tim Waugh 2010-03-20 10:23:01 UTC
And are you still seeing the problem?  Does it recur?

Comment 12 Robert Haas 2010-03-20 10:50:36 UTC
No, to my knowledge it only happened the one time.  I don't actually remember it occurring; I just saw the report in the automatic bug reporting tool.

Comment 13 Frank Murphy 2010-08-01 09:43:09 UTC
I'm getting this now in F14 with abrt, brought me here.

pygtk2-2.17.0-6.fc14.i686

~$ python -c import gtk
  File "<string>", line 1
    import
         ^
SyntaxError: invalid syntax


Fresh upgrade, from Fresh F13 LiveISO (XFCE)

Happens on reboot twice now, will check the F14.x64 and Rawhide shortly

Comment 14 Jiri Popelka 2010-08-02 08:54:37 UTC
I think there are some pygtk2 problems in rawhide at the moment.

Comment 15 Frank Murphy 2010-08-02 08:59:29 UTC
(In reply to comment #14)
> I think there are some pygtk2 problems in rawhide at the moment.    

This is F14-Branched I reported against.
Basically I have no printers.

Comment 16 Jiri Popelka 2010-08-02 09:56:21 UTC
Yes, F-14 (bug #618944).
Can you update to pygtk2-2.17.0-7.fc14 and try it (python -c 'import gtk') again ?

Comment 17 Frank Murphy 2010-08-02 10:44:49 UTC
No joy.
updated pygtk from supplied link, did python -c 'import gtk'

similar crash still happens alert also:
https://bugzilla.redhat.com/show_bug.cgi?id=620151

Comment 18 Michael Schwendt 2010-08-02 19:56:02 UTC
I was about to submit a crash in system-config-printer, but ABRT said it would be a dupe of this. Hard to believe, because the details are different. Failure to import pynotify. Hence I filed bug 620544 manually.


Note You need to log in before you can comment on or make changes to this bug.