Ubuntu
kdebase package

Konqueror refuses to resolve localhost and 127.0.0.1 in some cases

Bug #112244 reported by Ryan Zeigler
4
Affects Status Importance Assigned to Milestone
kdebase (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: konqueror

Basically, I was doing some fun little tests with apache on my laptop and I was doing them in a place where there was no internet to connect too. If KNetworkManager is running and I attempt to visit either http://localhost/ or http://127.0.0.1/ I get a host not found error, which is incorrect. If I quit from KNetworkManager Konqueror works as expected.

My assumption is that konqueror has somehow been patched to check knetworkmanager before resolving addresses, and it should probably make sure that localhost isn't being requested before just saying the page can't be found.

Revision history for this message
Michel D'HOOGE (michel-dhooge) wrote :

I can confirm that - even though I never realised it was due to KNM!

Changed in kdebase:
status: Unconfirmed → Confirmed
Revision history for this message
Frode M. Døving (frode) wrote :

This can be fixed by disabling "Network Status Daemon" from the 'Service Manager' in 'System Settings -> Advanced'.
Uncheck the checkbox and hit the 'Stop' button.

You can also uninstall the 'networkstatus' package if you want to.
- Frode

Revision history for this message
Ysanne (anna-foeglein) wrote :

Is this bug going to be fixed in any way? It seems to be open for almost a year now, without improvement...

I can confirm that the problem still persists in April 2008. The 'networkstatus' package is installed, but the 'Network Status Daemon' is not listed in the 'Service Manager'.

The behaviour of konqueror pretty much kills the point of having at least one working network interface, namely lo, under any circumstances. Accessing local services should work independently of network access. (Practical example: Web development on local Apache server while not hooked up to the internet.)

Are there any good reasons for not letting KDE applications access local services when there's no external network available? What's the correct place for this bug to be filed, in order to restore standard *nix behaviour?

Revision history for this message
Ysanne (anna-foeglein) wrote :

Sorry, correction: Network Status Daemon was running, I confused the German translations of the KDE Service Manager and System Service Manager.

Revision history for this message
Adam Brightmore (sinister-ray) wrote :

I have also suffered from this problem. It was rather annoying as I was due to demonstrate (on my laptop which wasn't connected to a network) a PHP/MySQL project I'd been working on and had to use Firefox after being embarrassed by Konqueror. Don't get me wrong Konqueror is my favourite browser (hence why I went to it first) but as it's the only web browser installed in Kubuntu by default this could course big problems for users. I was only saved as I had Firefox installed for cross browser testing.

P.S. Here's an interesting article on this with a few possible workarounds too.
http://movingparts.net/2007/11/07/kde-networkmanager-workaround/

Revision history for this message
Harald Sitter (apachelogger) wrote :

Is this still an issue in Kubuntu Intrepid?

Changed in kdebase:
status: Confirmed → Incomplete
Revision history for this message
Jonathan Thomas (echidnaman) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

Changed in kdebase:
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.