Bug 275671

Summary: Pirut crashed and will no longer run
Product: [Fedora] Fedora Reporter: Leslie Brooks <no_cats2000>
Component: pirutAssignee: Jeremy Katz <katzj>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: medium    
Version: 8CC: james.antill
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2007-09-04 17:47:40 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
The crash log none

Description Leslie Brooks 2007-09-04 00:27:07 UTC 
Description of problem:  I installed and launched, Pirut ran automatically and
told me there were some hundred updates.  I closed the notification window while
I looked at new features and adjusted some preferences, then clicked on the
Pirut icon and asked it to show me a list of the updates.  It appeared to be
working (lots of network activity) but no UI appeared for several minutes, then
a crash dialog appeared.

After rebooting Pirut no longer runs automatically; when I tried to launch
either Pup or Pirut I got an 'Unable to run due to a configuration error'
message.  I got that two or three times (after more than one reboot) but after
the latest reboot it doesn't give me any dialog box or UI; it just hangs at the
command line after I enter the Root password.

Version-Release number of selected component (if applicable):
pirut-1.3.9-1.fc8.src.rpm

How reproducible:
I think I will have to re-install to try; please let me know if you want me to
do that.

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


Expected results:


Additional info:
Comment 1 Leslie Brooks 2007-09-04 00:27:07 UTC 
Created attachment 185461 [details]
The crash log
Comment 2 Jeremy Katz 2007-09-04 17:47:40 UTC 

*** This bug has been marked as a duplicate of 251836 ***