Red Hat Bugzilla – Bug 217817
Reporting unhandled exception from yumex
Last modified: 2014-01-21 17:56:28 EST
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:
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).
Created attachment 142461 [details]
Dump file that was asked to be saved
except the crash dump doesn't mention yum.
reassigning to yumex
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.
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.
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 ***