Bug 476344 - could not create GladeXML object during pirut update
Summary: could not create GladeXML object during pirut update
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: pirut
Version: rawhide
Hardware: i386
OS: Linux
low
medium
Target Milestone: ---
Assignee: Jeremy Katz
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-12-13 10:24 UTC by Gaétan
Modified: 2009-01-05 05:06 UTC (History)
2 users (show)

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

Attachments (Terms of Use)
error message (668 bytes, text/plain)
2008-12-13 10:26 UTC, Gaétan 		no flags Details
View All

Description Gaétan 2008-12-13 10:24:08 UTC 
Description of problem:
Error during yum update.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:
Component: pirut
Summary: TB933f1c56 DetailsDialog.py:38:__init__:RuntimeError: could not create GladeXML object

Traceback (most recent call last):
  File "/usr/sbin/pup", line 427, in _apply
  File "/usr/lib/python2.5/site-packages/pirut/DetailsDialog.py", line 38, in __init__
RuntimeError: could not create GladeXML object

Local variables in innermost frame:
parent: <gtk.Window object at 0x89c639c (GtkWindow at 0x8a0f0e0)>
text: Mise à jour effectuée avec succès.
self: <pirut.DetailsDialog.PirutDetailsDialog instance at 0xcdb738c>
buttons: <enum GTK_BUTTONS_NONE of type GtkButtonsType>
type: <enum GTK_MESSAGE_INFO of type GtkMessageType>
secondary: None

Expected results:
no error !

Additional info:
Comment 1 Gaétan 2008-12-13 10:26:43 UTC 
Created attachment 326809 [details]
error message

file generated when update process asked for saving error.
Comment 2 Jeremy Katz 2008-12-15 14:50:18 UTC 
What's the output of 
  rpm -q pirut yum fedora-release
  rpm -V pirut
Comment 3 Jeremy Katz 2009-01-05 05:06:20 UTC 
Closing due to inactivity; please reopen if you have further information to add to this report.
Note You need to log in before you can comment on or make changes to this bug.