Description of problem:
system-config-packages hangs forever if I call it before any proxy is
configured, behind a restrictive firewall. When I interrupt its call (Ctrl+C)
in the console, I get a backtrace.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Set up your system in a restricted network, but don't configure proxies.
2. Call system-config-packages from a root shell with a DISPLAY.
3. Wait; or: Try to press cancel in the GUI.
4. Press Ctrl+C in the root shell.
"Retrieving software information" forever. GUI does not update display.
Pressing "Cancel" is to no avail
Can press cancel, and/or get info that no server (which one anyway? mirror
list) is accessable.
Second time 'round, Ctrl+C didn't work. Ctrl+Z and kill %1 worked, no traceback
Sorry, I couldn't find a related previous bug report, and I was too lazy to
check through 50+ pirut bug reports, none of which matched any of my keywords.
Created attachment 255311 [details]
traceback from system-config-packages / pirut
It's likely waiting on the socket timeout. There's not really anything else we
can do. Proxies are generally not detectable by client apps.
Well, I nevertheless have two things to gripe about:
a) It took more than one second, and never actually timed out.
b) I couldn't press cancel. The app was totally blocked.
I was hoping the backtrace would give more insight, but I guess if it's just
waiting for a connection at this point...
In comment #3, I wrote:
> a) It took more than one second, and never actually timed out.
One minute I meant. ;-)
This message is a reminder that Fedora 8 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 8. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora
'version' of '8'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version prior to Fedora 8's end of life.
Bug Reporter: Thank you for reporting this issue and we are sorry that
we may not be able to fix it before Fedora 8 is end of life. If you
would still like to see this bug fixed and are able to reproduce it
against a later version of Fedora please change the 'version' of this
bug to the applicable version. If you are unable to change the version,
please add a comment here and someone will do it for you.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
The process we are following is described here:
Closed as NOONECARED, em, INSUFFICIENT_DATA due to F8 EOL.
I'll reopen if I observe this again with F10 - if we ever upgrade to F10 within the company/project (where I have the firewall+proxy).