Feisty: Konqueror stops working when switching network interfaces

Bug #112068 reported by Vsevolod Krishchenko
8
Affects Status Importance Assigned to Milestone
knetworkmanager (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: konqueror

When I switching from eth1 (wi-fi/dhcp) to eth0 (wire/dhcp), konqueror stops working with network.

Everything other works just fine (firefox, ping, traceroute, apt-get etc).
ifconfig looks ok (only eth0 presents) and route -n show normal table:
(I'm using openvpn/tun0 to access my office network)
seva@fcs:~$ route -n
Kernel IP routeing table
Destination Gateway Genmask Flags Metric Ref Use Iface
10.4.0.6 0.0.0.0 255.255.255.255 UH 0 0 0 tun0
10.4.0.1 10.4.0.6 255.255.255.255 UGH 0 0 0 tun0
192.168.0.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
192.168.45.0 10.4.0.6 255.255.255.0 UG 0 0 0 tun0
0.0.0.0 192.168.0.1 0.0.0.0 UG 0 0 0 eth0

Ping works just fine:
seva@fcs:~$ ping kubuntu.com
PING kubuntu.com (82.211.81.158) 56(84) bytes of data.
64 bytes from arctowski.ubuntu.com (82.211.81.158): icmp_seq=1 ttl=46 time=87.9 ms
etc..

Firefox is ok too (i'm using it right now)

But konqueror does not want to browse net:
An error occurred while loading http://kubuntu.com:
Could not connect to host http://kubuntu.com/.
or
An error occurred while loading http://82.211.81.158:
Could not connect to host http://82.211.81.158/.

As far as I remember It will start working whe i'll switch to eth1 again.

Revision history for this message
Vsevolod Krishchenko (mstu) wrote :

Oh, I forgot to mention that this problem appeared when I upgraded my system to feisty.
And I got knetworkmanager running.

Revision history for this message
Michael D. Stemle, Jr. (manchicken) wrote :

I've been trying to get my suspend/resume to work again for some time. I recently discovered that linuxant's driverloader (version 2.36) was the problem for me on this 2.6.20 kernel. I tried just switching back to bcm43xx driver in 2.6.20, and it seems like I can suspend/resume again, but there are other issues.

All this to say that when I came back from suspend, konqueror wouldn't talk over the network. Pinging worked, telnet to port 80 worked, Firefox (both 64 and 32 bit) worked, konversation worked, kopete worked, but konqueror did not work.

I didn't even change interface names. When I was under driverloader it was eth1, and now that I'm under bcm43xx it's still eth1.

Changed in knetworkmanager:
status: Unconfirmed → Confirmed
Revision history for this message
Michael D. Stemle, Jr. (manchicken) wrote :

Sorry to side-track, my issue seems very similar, but it would appear that the suspend/resume is what was killing konqueror. These two issues may very well be related, but no, this is not the same issue that was initially reported. Just in case anybody feels like investigating the possible similarity I'll attach my lsmod.

Revision history for this message
Vsevolod Krishchenko (mstu) wrote :

Some additional observations.

1. Kopete connects to ICQ and works fine.
But clicking on any http-link in message cause next message to appear:
Could not connect to host http://someuser.livejournal.com/bla-bla.html.

2. fish:// works fine with konqueror and krusader! Only http fails.

So I'm sure it is NOT a problem with knetworkmanager. It looks like only kde http client failed. Please change target package if I'm right.

Revision history for this message
Michael D. Stemle, Jr. (manchicken) wrote :

I'm unconfirming since the issue I experienced was different from the issue that was initially reported. This is not because I was unable to reproduce it.

Changed in knetworkmanager:
status: Confirmed → Unconfirmed
Revision history for this message
DannyR (dannyr) wrote :

I have a similar problem. I use only wifi on rausb0 (which is detected, but cannot be connected to, by kNetworkManager) but do have an eth0 interface. Everything but Konqueror has no trouble connecting to the internet (although things like fish:// work). This doesn't affect any other KDE apps like kopete.

Revision history for this message
Silvio Gissi (silvio-gissi) wrote :

Could you please check if you shutdown the KNetworkManager the problems goes away?

Revision history for this message
DannyR (dannyr) wrote : Re: [Bug 112068] Re: Feisty: Konqueror stops working when switching network interfaces

It does

On 7/4/07, Silvio Gissi <email address hidden> wrote:
>
> Could you please check if you shutdown the KNetworkManager the problems
> goes away?
>
> --
> Feisty: Konqueror stops working when switching network interfaces
> https://bugs.launchpad.net/bugs/112068
> You received this bug notification because you are a direct subscriber
> of the bug.
>

Revision history for this message
Silvio Gissi (silvio-gissi) wrote :

Marked as duplicated of #86680.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Bug attachments

Remote bug watches

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