https://bugs.kde.org/show_bug.cgi?id=433968
Bug ID: 433968
Summary: Failed to contact bugs.kde.org: bugs.kde.org: Socket
operation timed out
Product: drkonqi
Version: unspecified
Platform: openSUSE RPMs
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: plasma-b...@kde.org
Reporter: jodr...@live.com
Target Milestone: ---
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...
--
You are receiving this mail because:
You are watching all bug changes.
