Red Hat Bugzilla – Bug 241390
pirut gives stack trace when behind network proxy
Last modified: 2007-11-30 17:12:05 EST
Description of problem:
On a fresh install of Fedora, there is no (obvious) way to get pirut to work
from behind a network proxy. All simple paths lead to Python stack traces
Version-Release number of selected component (if applicable):
Fedora 7, test 4
Steps to Reproduce:
1. Install Fedora (fresh from the ISO) on a machine behind a proxy
2. Login as a regular user
3. Run Applications/'Add/Remove Software' from the menus
4. Watch the python stack trace
5. Say "hmmm...must not have my proxy info". Enter it from the menus
6. Retry running
7. Ooh...another stack trace.
8. Conclude that the privileged software update apps don't honor the end-user
preferences for network proxies
9. Realize there is no GUI to set those preferences for root
Python stack traces. Get same from "System Tools/Software Updater"
System updates and new software
Why are we giving stack traces instead of an error message that would let the
user enter proxy information?
Created attachment 155464 [details]
Stack trace from pirut
Manually adding a proxy=... line to /etc/yum.conf is the workaround to "make
things work", but really doesn't excuse a stack trace instead of an error
message with a dialog to fix the problem
This should be handled properly with yum 3.2.0 -- can you try and see if that helps?
It helps, but incompletely.
With yum 3.2 (yum-3.2.0-1.fc7) you get a semi-friendly error message ("Unable
to retrieve software information" Unable to retrieve software information.
This could be caused by not having a network connection available. There is a
details pull down which just says "None"). But you still get no indication of
how to fix it. Clicking OK in this dialog closes the app, instead of leaving
you in a state where you can update your settings
Yep, that's (unfortunately) the way we can handle things right now. Hopefully
some of the infrastructure around PolicyKit and the like will start to make it
easier to do even more.
And fwiw, the end-user preferences should now be honored in F7, but require a
log-out and relogin to fully take effect
Fair 'nuff. Thanks for looking into it