Bug 217817

Summary: Reporting unhandled exception from yumex
Product: [Fedora] Fedora Reporter: Austin <aa_sb_0>
Component: yumexAssignee: Tim Lauridsen <tim.lauridsen>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: medium    
Version: 6   
Target Milestone: ---   
Target Release: ---   
Hardware: noarch   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2006-12-18 07:54:46 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
Dump file that was asked to be saved none

Description Austin 2006-11-30 03:08:20 UTC 
Description of problem: Yumex crashed whilst trying to perform an update, with
the error message that yum had crashed with an unhandled exception. Thus, I'm
reporting against yum, not yumex. (Feel free to shift if necessary)


Version-Release number of selected component (if applicable): 3.0.1-2.fc6


How reproducible: Unsure. 


Steps to Reproduce:
1.
2.
3.
  
Actual results: Crash and was caught by some application, where I was asked to
save the dump file and report it here.


Expected results: For it to update selected components, and not crash.


Additional info: See attached dump file. I apologise that I didn't pay more
attention to the problem when it occured (I was doing 6 things at once).
Comment 1 Austin 2006-11-30 03:08:21 UTC 
Created attachment 142461 [details]
Dump file that was asked to be saved
Comment 2 Seth Vidal 2006-11-30 03:53:09 UTC 
except the crash dump doesn't mention yum.

reassigning to yumex
Comment 3 Tim Lauridsen 2006-11-30 10:30:40 UTC 
Seth is right, this has nothing to do with yum :)

I is some kind of null pointer problem in a treeview, i will take a deeper look.
Comment 4 Austin 2006-11-30 23:23:12 UTC 
I noticed this in this morning's logwatch:

Deprecated pam module:
    deprecated module pam_stack called from service yumex: 3 Time(s)

These lines were found in /var/log/secure

I'm unsure if they're related, or just information for another bug.
Comment 5 Tim Lauridsen 2006-12-18 07:54:46 UTC 
The traceback should be fixed in yumex 1.2.1, to be released very soon.
I will look into the pam_stack issue.

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