Bug 327551 - pirut crashes repeatedly
Summary: pirut crashes repeatedly
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: pirut
Version: 7
Hardware: i386
OS: Linux
low
low
Target Milestone: ---
Assignee: Jeremy Katz
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2007-10-11 12:28 UTC by michael
Modified: 2007-11-30 22:12 UTC (History)
1 user (show)

Fixed In Version: 1.3.23
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2007-10-17 12:13:28 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
crash report (2.00 KB, text/plain)
2007-10-11 12:28 UTC, michael
no flags Details
yum.log (4.79 KB, text/plain)
2007-10-17 09:18 UTC, michael
no flags Details

Description michael 2007-10-11 12:28:06 UTC
Description of problem:
 cannot run pirut  from Gnome (Applications-Add/Remove software)

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


How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 1 michael 2007-10-11 12:28:06 UTC
Created attachment 224251 [details]
crash report

Comment 2 Jeremy Katz 2007-10-16 18:14:54 UTC
An updated pirut packages is available in the Fedora 7 Updates Testing
repository which should help to resolve this problem.  Can you install this
package by running
   yum --enablerepo=updates-testing update pirut
and then see if you still can reproduce this problem?

Comment 3 michael 2007-10-17 09:17:39 UTC
I just tried to repro the problem prior to getting said 'updates testing' and
wasn't able to. I'm unsure what's changed on my system - still on pirut
1.3.9-1.fc7.noarch and I think these yum.log entries (attached) are since the
initial report (I'm BST which is GMT+1):



Comment 4 michael 2007-10-17 09:18:08 UTC
Created attachment 229731 [details]
yum.log

Comment 5 Jeremy Katz 2007-10-17 12:13:28 UTC
It's likely something which only occurs occasionally.  But the new pirut reworks
the initialization a bit so that we can catch the exception when it occurs and
allow you to retry.


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