Bug 538285 - [abrt] crash detected in yum-utils-1.1.24-2.fc12
Summary: [abrt] crash detected in yum-utils-1.1.24-2.fc12
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: yum-utils
Version: 12
Hardware: i686
OS: Linux
low
medium
Target Milestone: ---
Assignee: Seth Vidal
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:767963cc
: 538286 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-11-18 06:05 UTC by markhuomian
Modified: 2014-01-21 23:12 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-01-12 21:07:53 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
File: backtrace (2.79 KB, text/plain)
2009-11-18 06:05 UTC, markhuomian 		no flags Details
View All

Description markhuomian 2009-11-18 06:05:33 UTC 
abrt detected a crash.

Attached file: backtrace
cmdline: /usr/bin/python /usr/bin/yumdownloader --enablerepo=*debuginfo* --quiet libcanberra-debuginfo-0.22-1.fc12.i686 
component: yum-utils
executable: /usr/bin/yumdownloader
kernel: 2.6.31.5-127.fc12.i686.PAE
package: yum-utils-1.1.24-2.fc12
uuid: 767963cc
Comment 1 markhuomian 2009-11-18 06:05:36 UTC 
Created attachment 370014 [details]
File: backtrace
Comment 2 seth vidal 2009-11-18 16:48:48 UTC 
*** Bug 538286 has been marked as a duplicate of this bug. ***
Comment 3 seth vidal 2009-11-18 17:39:34 UTC 
what version of python-urlgrabber is installed?
Comment 4 markhuomian 2009-12-03 02:37:06 UTC 
Installed Packages
python-urlgrabber.noarch                                3.9.1-4.fc12                                @updates-testing(In reply to comment #3)
> what version of python-urlgrabber is installed?  

Installed Packages
python-urlgrabber.noarch                                3.9.1-4.fc12                                @updates-testing
Comment 5 seth vidal 2009-12-03 02:42:50 UTC 
does the problem still persist, now?
Comment 6 markhuomian 2009-12-03 04:43:25 UTC 
(In reply to comment #5)
> does the problem still persist, now?  

after last night's updating, not yet
Note You need to log in before you can comment on or make changes to this bug.