Bug 433968 - Failed to contact bugs.kde.org: bugs.kde.org: Socket operation timed out
Summary: Failed to contact bugs.kde.org: bugs.kde.org: Socket operation timed out
Status: RESOLVED WORKSFORME
Alias: None
Product: frameworks-kio
Classification: Frameworks and Libraries
Component: HTTP (show other bugs)
Version: unspecified
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: KIO Bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-03-04 19:52 UTC by Tony
Modified: 2022-07-12 00:52 UTC (History)
4 users (show)

See Also:
Latest Commit:
Version Fixed In:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Tony 2021-03-04 19:52:51 UTC 
SUMMARY

When connected to two different wifi networks, one of them not having internet access, drkonqi fails to connect to bugs.kde.org showing this message "Failed to contact bugs.kde.org: bugs.kde.org: Socket operation timed out"

In order for it to wrong correctly and being able to stablish a connection i need to disconnect from the one without internet access.

STEPS TO REPRODUCE
1. Connect to two wifi networks, one with internet access the other without. Creating and connecting to a "Wired ethernet (shared)" without internet access also works.
2. Trigger drkonqui. I did following the steps from bug 432891.
3. Fallow drkonqi steps until it needs to stablish a network connection.

OBSERVED RESULT
On the 3rd step in the crash reporting assistant, where drkonqi needs to stablish a network connection, it fails to do so.

EXPECTED RESULT
Proper connection to bugs.kde.org

ADDITIONAL INFORMATION

In this log "wlp2s0" is the one with no internet access. It did not even try with the one that does has it.

Mar 04 15:18:35 Joder-PC NetworkManager[859]: <info>  [1614885515.8111] device (wlp2s0): supplicant interface state: completed -> disconnected
Mar 04 15:18:35 Joder-PC NetworkManager[859]: <info>  [1614885515.8111] device (p2p-dev-wlp2s0): supplicant management interface state: completed -> disconnected
Mar 04 15:18:35 Joder-PC drkonqi[29741]: org.kde.drkonqi.bugzilla: ProtocolException: "bugs.kde.org: Socket operation timed out" 149 "bugs.kde.org: Socket operation timed out" "bugs.kde.org: Socket operation t>
Mar 04 15:18:35 Joder-PC drkonqi[29741]: org.kde.drkonqi: "bugs.kde.org: Socket operation timed out"
Mar 04 15:18:35 Joder-PC NetworkManager[859]: <info>  [1614885515.8908] device (wlp2s0): supplicant interface state: disconnected -> scanning
Mar 04 15:18:35 Joder-PC NetworkManager[859]: <info>  [1614885515.8908] device (p2p-dev-wlp2s0): supplicant management interface state: disconnected -> scanning
Mar 04 15:18:36 Joder-PC kernel: wlp2s0: authenticate with 4c:bc:98:02:35:70
Mar 04 15:18:36 Joder-PC NetworkManager[859]: <info>  [1614885516.6165] device (wlp2s0): supplicant interface state: scanning -> authenticating
Mar 04 15:18:36 Joder-PC NetworkManager[859]: <info>  [1614885516.6166] device (p2p-dev-wlp2s0): supplicant management interface state: scanning -> authenticating
Mar 04 15:18:36 Joder-PC kernel: wlp2s0: send auth to 4c:bc:98:02:35:70 (try 1/3)
Mar 04 15:18:36 Joder-PC NetworkManager[859]: <info>  [1614885516.6969] device (wlp2s0): supplicant interface state: authenticating -> associating
Mar 04 15:18:36 Joder-PC NetworkManager[859]: <info>  [1614885516.6969] device (p2p-dev-wlp2s0): supplicant management interface state: authenticating -> associating
Mar 04 15:18:36 Joder-PC kernel: wlp2s0: authenticated
Mar 04 15:18:36 Joder-PC kernel: wlp2s0: associate with 4c:bc:98:02:35:70 (try 1/3)
Mar 04 15:18:36 Joder-PC kernel: wlp2s0: RX AssocResp from 4c:bc:98:02:35:70 (capab=0x411 status=0 aid=1)
Mar 04 15:18:36 Joder-PC kernel: wlp2s0: associated
Mar 04 15:18:36 Joder-PC NetworkManager[859]: <info>  [1614885516.7111] device (wlp2s0): supplicant interface state: associating -> 4way_handshake
Mar 04 15:18:36 Joder-PC NetworkManager[859]: <info>  [1614885516.7111] device (p2p-dev-wlp2s0): supplicant management interface state: associating -> 4way_handshake
Mar 04 15:18:36 Joder-PC NetworkManager[859]: <info>  [1614885516.7112] device (wlp2s0): DHCPv4 lease renewal requested
Mar 04 15:18:36 Joder-PC NetworkManager[859]: <info>  [1614885516.7375] dhcp4 (wlp2s0): canceled DHCP transaction
Mar 04 15:18:36 Joder-PC NetworkManager[859]: <info>  [1614885516.7375] dhcp4 (wlp2s0): state changed bound -> done
Mar 04 15:18:36 Joder-PC NetworkManager[859]: <info>  [1614885516.7379] dhcp4 (wlp2s0): activation: beginning transaction (timeout in 45 seconds)
Mar 04 15:18:36 Joder-PC NetworkManager[859]: <info>  [1614885516.7380] device (wlp2s0): DHCPv6 lease renewal requested
Mar 04 15:18:36 Joder-PC NetworkManager[859]: <info>  [1614885516.7381] dhcp6 (wlp2s0): canceled DHCP transaction
Mar 04 15:18:36 Joder-PC NetworkManager[859]: <info>  [1614885516.7381] dhcp6 (wlp2s0): state changed bound -> done
Mar 04 15:18:36 Joder-PC NetworkManager[859]: <info>  [1614885516.7384] dhcp6 (wlp2s0): activation: beginning transaction (timeout in 45 seconds)
Mar 04 15:18:36 Joder-PC NetworkManager[859]: <info>  [1614885516.7391] device (wlp2s0): supplicant interface state: 4way_handshake -> completed
Mar 04 15:18:36 Joder-PC NetworkManager[859]: <info>  [1614885516.7392] device (p2p-dev-wlp2s0): supplicant management interface state: 4way_handshake -> completed
Mar 04 15:18:36 Joder-PC NetworkManager[859]: <info>  [1614885516.7798] dhcp6 (wlp2s0): state changed unknown -> bound
Mar 04 15:18:36 Joder-PC dbus-daemon[827]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.5' (uid=0 pid=859 com>
Mar 04 15:18:36 Joder-PC systemd[1]: Starting Network Manager Script Dispatcher Service...
Comment 1 Alois Wohlschlager 2021-03-04 20:11:22 UTC 
This might be a network setup issue. Please provide output of the "ip route" command. Do other apps connecting to the internet work?
Comment 2 Tony 2021-03-04 20:47:29 UTC 
(In reply to Alois Wohlschlager from comment #1)
> This might be a network setup issue. Please provide output of the "ip route"
> command. Do other apps connecting to the internet work?

Yes they do, telegram, steam browsers, in fact i posted this report while connected to both networks.

default via 192.168.0.1 dev wlp0s18f2u5 proto dhcp metric 600 
default via 192.168.100.1 dev wlp2s0 proto dhcp metric 20601 
192.168.0.0/21 dev wlp0s18f2u5 proto kernel scope link src 192.168.2.20 metric 600 
192.168.100.0/24 dev wlp2s0 proto kernel scope link src 192.168.100.100 metric 601 
192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 linkdown
Comment 3 Harald Sitter 2021-03-07 22:34:29 UTC 
network IO runs through KIO. Moving bug.
Comment 4 Michael 2021-10-30 13:57:14 UTC 
I have a similar issue which might be related.
Hyperlinks in a program like Konsole, Discord, and most other programs with clickable hyperlinks often open a "Error - KIO Client" window with "<hostname>: Socket operation timed out".
Commonly happens with youtube.com hyperlinks.
However I only have a single wired connection. Everything else works, the same links that fail in KIO work perfectly fine within a browser, curl, wget etc. 

ip route:
 default via 10.0.0.1 dev enp4s0 proto dhcp metric 100 
 10.0.0.0/24 dev enp4s0 proto kernel scope link src 10.0.0.80 metric 100 

I'm using Fedora 35 KDE Spin however I also had this issue before updating.
Comment 5 Tony 2022-07-12 00:52:39 UTC 
Long time since i got this, plus can't reproduce with the recent changes made to drkonqui.