[Bug 309047] New: KDE should warn the user if connection to localhost fails
Stephan Beyer
stephan.beyer at uni-jena.de
Fri Oct 26 14:53:18 BST 2012
https://bugs.kde.org/show_bug.cgi?id=309047
Bug ID: 309047
Severity: minor
URL: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=69140
6
Version: unspecified
Priority: NOR
Assignee: unassigned-bugs at kde.org
Summary: KDE should warn the user if connection to localhost
fails
Classification: Unclassified
OS: Linux
Reporter: stephan.beyer at uni-jena.de
Hardware: Debian testing
Status: UNCONFIRMED
Component: general
Product: unknown
If the lo loopback interface (needed to connect to 127.0.0.1) is down, KDE is
unusable: KDE startup takes 4 minutes and a lot of KDE programs takes minutes
to start.
The reason is that those KDE programs want to connect to 127.0.0.1 and if
localhost is not available, the connect()s just timeout and everything goes on.
I think that - at least - at the KDE startup one process (kdeinit?) should say
"Hey, I am unable to connect to localhost. This should not happen! Please check
your system, something is wrong. KDE does not work well under this
circumstances."
A warning like this would have saved me a lot of time.
Best
Stephan
Reproducible: Always
Steps to Reproduce:
1. ifdown lo (or, if ifdown is not available, something like ifconfig lo down
should do it)
2. look for an activity for the next 10 minutes
3. start KDE
Actual Results:
KDE startup took 4 minutes and running several KDE programs takes a lot of
time. A list of such KDE programs can be found in the Debian bug report (see
link).
Expected Results:
Either KDE should just work[tm] or it should provide a warning that the system
is f**ked up because localhost connection fails.
--
You are receiving this mail because:
You are the assignee for the bug.
More information about the Unassigned-bugs
mailing list