Red Hat Bugzilla – Bug 253370
unhandled exception in pirut
Last modified: 2007-11-30 17:12:13 EST
Description of problem:
Pirut encountered an unhandled exception after prompting for a reboot.
Version-Release number of selected component (if applicable):
One out of two times?
Steps to Reproduce:
1. The yum-updatesd service daemon discovers updates are available.
2. Select Apply.
3. After "Downloading software", "Updating software", etc. phases
complete, since a kernel update was included, the dialog titled
"Reboot recommended" displays:
Due to the updates installed, it is recommended
that you reboot your system. You can either reboot
now or choose to do so at a later time.
Reboot later Reboot now
4. Select "Reboot now"
A dialog titled "Exception Occurred" displays:
An unhandled exception has occurred. This is most likely
a bug. Please save the crash dump and file a detailed bug
report against pirut ....
Just quietly reboot without additional manual intervention.
One of the packages being updated in this transaction was pirut, from:
This happened during a second run of pirut. The first run was
processing 169 package updates, and in its "Updating software"
phase it progressed to "Updating wireless tools" ... and then
made no further progress. No new activity was recorded in
/etc/log/yum.log for more than an hour, while neither the pup nor
puplet processes accumulated any more CPU time (per System Monitor).
So resorted to System, Shutdown, Restart, and pirut proclaims
87 package updates are available, and after processing them (using
the previously downloaded package data), the exception noted above
Created attachment 161794 [details]
The crash dump traceback produced by pirut.
This may be an unrelated failure, will move to a separate bug if so
advised. Later, upon selection of one additional package to install,
select Apply, and very quickly in the "Downloading packages" phase
rewarded with another unhandled exception.
Created attachment 161809 [details]
The crash dump traceback produced by pirut when Downloading.
The first is a dupe of bug 252328; the second, I just fixed in CVS