Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 226941 - An unhandled exeption occurred, Componet: Software Updater
An unhandled exeption occurred, Componet: Software Updater
Product: Fedora
Classification: Fedora
Component: yum (Show other bugs)
x86_64 Linux
medium Severity medium
: ---
: ---
Assigned To: Jeremy Katz
Depends On:
  Show dependency treegraph
Reported: 2007-02-02 00:36 EST by foxfire
Modified: 2014-01-21 17:57 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2007-04-25 15:14:18 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Traceback for Bug 226941 (2.45 KB, text/plain)
2007-02-05 20:33 EST, foxfire
no flags Details
fedora-core (1.03 KB, application/octet-stream)
2007-02-06 02:29 EST, foxfire
no flags Details
fedora-development (1.71 KB, application/octet-stream)
2007-02-06 02:30 EST, foxfire
no flags Details
fedora-extras (981 bytes, application/octet-stream)
2007-02-06 02:31 EST, foxfire
no flags Details
fedora-extras-development (1.46 KB, application/octet-stream)
2007-02-06 02:32 EST, foxfire
no flags Details
fedora-legacy (517 bytes, application/octet-stream)
2007-02-06 02:33 EST, foxfire
no flags Details
fedora-updates (1.01 KB, application/octet-stream)
2007-02-06 02:34 EST, foxfire
no flags Details
fedora-updates-testing (1.09 KB, application/octet-stream)
2007-02-06 02:35 EST, foxfire
no flags Details
freshrpms (354 bytes, application/octet-stream)
2007-02-06 02:36 EST, foxfire
no flags Details
livna (1.77 KB, application/octet-stream)
2007-02-06 02:36 EST, foxfire
no flags Details
livna-devel (1.86 KB, application/octet-stream)
2007-02-06 02:37 EST, foxfire
no flags Details
livna-testing (1.96 KB, application/octet-stream)
2007-02-06 02:38 EST, foxfire
no flags Details
yum.conf (466 bytes, text/plain)
2007-02-06 02:39 EST, foxfire
no flags Details

  None (edit)
Description foxfire 2007-02-02 00:36:05 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv: Gecko/20061219 Fedora/ Firefox/ pango-text

Description of problem:
This has happened on a few occasions, usually a re-boot helps, this time upon second re-boot the problem still exists. Before it happend on this occasion, I forgot to disconnect modem internet connection when powering down computer the session before, upon re-boot, I got an error trying to connect to the internet with kppp telling me there was another instance running and told me to delete the pid something in /root/.kde somewhere, I quit kppp and tried again with success without deleting this pid thing. Then got this exception when using GUI software updater, shut everything down and re-booted and got same problem. This is the first time it happened twice in a row.
I have forgot to disconnect modem connection in the past also, not sure if this software updater issue happened after those instances, but got a gut feeling it was some situation. Crash dump file is attached.

Version-Release number of selected component (if applicable):

How reproducible:
Didn't try

Steps to Reproduce:
1.Using GUI software updater to check for updates

Actual Results:
The crash

Expected Results:
It should have gone through the scan for updates

Additional info:
Comment 1 Jeremy Katz 2007-02-05 15:50:01 EST
Can you provide the traceback you received?
Comment 2 foxfire 2007-02-05 20:33:40 EST
Created attachment 147422 [details]
Traceback for Bug 226941
Comment 3 Seth Vidal 2007-02-05 23:54:18 EST
Can you post your config file(/etc/yum.conf)  and your /etc/yum.repos.d/*.repo
files? I think one of them has a typo in it that is causing the problem you're
Comment 4 foxfire 2007-02-06 02:29:18 EST
Created attachment 147436 [details]
Comment 5 foxfire 2007-02-06 02:30:36 EST
Created attachment 147437 [details]
Comment 6 foxfire 2007-02-06 02:31:07 EST
Created attachment 147438 [details]
Comment 7 foxfire 2007-02-06 02:32:45 EST
Created attachment 147439 [details]
Comment 8 foxfire 2007-02-06 02:33:23 EST
Created attachment 147440 [details]
Comment 9 foxfire 2007-02-06 02:34:04 EST
Created attachment 147441 [details]
Comment 10 foxfire 2007-02-06 02:35:29 EST
Created attachment 147442 [details]
Comment 11 foxfire 2007-02-06 02:36:00 EST
Created attachment 147443 [details]
Comment 12 foxfire 2007-02-06 02:36:46 EST
Created attachment 147444 [details]
Comment 13 foxfire 2007-02-06 02:37:51 EST
Created attachment 147445 [details]
Comment 14 foxfire 2007-02-06 02:38:35 EST
Created attachment 147446 [details]
Comment 15 foxfire 2007-02-06 02:39:32 EST
Created attachment 147447 [details]
Comment 16 foxfire 2007-02-06 02:50:25 EST
I had tried to update a couple times after submiting the bug to no avail either
through GUI or CLI, I also noticed as I shut down that copy of Fedora (as I have
two newer one since), that yum updatesd showed (failed). The attachments are
from affected copy.
Comment 17 Seth Vidal 2007-02-06 08:55:54 EST
in your yum.conf you have:

# PUT YOUR REPOS HERE OR IN separate files named file.repo
# in /etc/yum.repos.d
name=Fedora Core $releasever - $basearch - ATrpms

see the 'space' in front of [atrpms]

get rid of the space. see if it works.

Comment 18 foxfire 2007-02-06 14:41:13 EST
Yes that appears to be the animal that you need to hunt down, I took out the
space and used the GUI, it did the scan and presented a list. I quit to come to
this third copy of Fedora to retrieve rpms in the caches to avoid
re-downloading. I had just imported that key not to long before this event
(bug), I got the import information at this site:
I also noticed there is a notice (warning) at the top of the page, not sure if I
seen it when I was there last. So now I will transfer the rpms to their
respective caches and try to update it, if I say no more here, everything's cool.
Comment 19 foxfire 2007-02-06 17:56:39 EST
After looking back at past steps, it appears I may have set up atrpms repo from
http://atrpms.net/install.html as I also noticed a new atrpm cache folder, also
noticed a atrpm update as I applied updates.


Note You need to log in before you can comment on or make changes to this bug.