Can't connect to phone
Describe the bug
I just got GSConnect installed, and I went through all of the connection and help instructions, but my device will not show up.
Steps to reproduce
- Open GSConnect settings on computer
- Open KDE Connect app on phone
- Check for devices on both
Expected behavior
A device would appear on at least one of them
GSConnect version
62
Installed from
GNOME Extensions website
GNOME Shell version
48
Linux distribution/release
EndeavourOS/Arch Rolling
Paired device(s)
Samsung Galaxy S22
KDE Connect app version
1.33.4
Plugin(s)
No response
Support log
GSConnect: 62 (user)
GJS: 18402
Session: wayland
OS: EndeavourOS
--------------------------------------------------------------------------------
May 07 17:52:03 floorp.desktop[2604]: console.warn: "This Event is registered in System: [object KeyboardEvent]"
May 07 17:52:04 floorp.desktop[2604]: console.warn: "This Event is registered in System: [object KeyboardEvent]"
May 07 17:52:04 floorp.desktop[2604]: console.warn: "This Event is registered in System: [object KeyboardEvent]"
May 07 17:52:05 floorp.desktop[2604]: console.warn: "This Event is registered in System: [object KeyboardEvent]"
May 07 17:52:05 floorp.desktop[2604]: console.warn: "This Event is registered in System: [object KeyboardEvent]"
May 07 17:52:05 floorp.desktop[2604]: console.warn: "This Event is registered in System: [object KeyboardEvent]"
May 07 17:52:05 floorp.desktop[2604]: console.warn: "This Event is registered in System: [object KeyboardEvent]"
May 07 17:52:05 floorp.desktop[2604]: console.warn: "This Event is registered in System: [object KeyboardEvent]"
May 07 17:52:06 floorp.desktop[2604]: console.warn: "This Event is registered in System: [object KeyboardEvent]"
May 07 17:52:13 systemd[1399]: dbus-:[email protected]: Unit process 3685 (gnome-control-c) remains running after unit stopped.
May 07 17:52:13 systemd[1399]: dbus-:[email protected]: Consumed 3.539s CPU time, 111.5M memory peak.
May 07 17:52:16 gnome-control-c[3685]: Trying to close CcSystemDetailsWindow 0x5f35c7704b90 that's not presented
Screenshots
No response
Notes
I'm using a Samsung Galaxy S22 with latest software, EndeavourOS system is fully updated, and I made sure that the firewall on the computer opened the necessary ports
+1
i'm having the same problem. gsconnect 62, fedora 42, gnome 48.
GSConnect: 62 (user)
GJS: 18201
Session: wayland
OS: Fedora Linux 42 (Workstation Edition)
--------------------------------------------------------------------------------
May 19 23:38:20 systemd[1]: openvpn@mullvad_us_sea.service: start operation timed out. Terminating.
May 19 23:38:20 openvpn[36331]: 2025-05-19 23:38:20 event_wait : Interrupted system call (fd=-1,code=4)
May 19 23:38:20 openvpn[36331]: 2025-05-19 23:38:20 net_route_v4_del: 10.0.0.0/8 via 10.16.0.1 dev [NULL] table 0 metric -1
May 19 23:38:20 openvpn[36331]: 2025-05-19 23:38:20 Closing TUN/TAP interface
May 19 23:38:20 openvpn[36331]: 2025-05-19 23:38:20 net_addr_v4_del: 10.16.0.20 dev tun0
May 19 23:38:20 avahi-daemon[860]: Withdrawing address record for 10.16.0.20 on tun0.
May 19 23:38:20 avahi-daemon[860]: Leaving mDNS multicast group on interface tun0.IPv4 with address 10.16.0.20.
May 19 23:38:20 openvpn[36331]: 2025-05-19 23:38:20 net_addr_v6_del: fdda:d0d0:cafe:1302::1012/64 dev tun0
May 19 23:38:20 avahi-daemon[860]: Interface tun0.IPv4 no longer relevant for mDNS.
May 19 23:38:20 avahi-daemon[860]: Withdrawing address record for fdda:d0d0:cafe:1302::1012 on tun0.
May 19 23:38:20 avahi-daemon[860]: Leaving mDNS multicast group on interface tun0.IPv6 with address fdda:d0d0:cafe:1302::1012.
May 19 23:38:20 avahi-daemon[860]: Joining mDNS multicast group on interface tun0.IPv6 with address fe80::d467:9306:5e3c:ed35.
May 19 23:38:20 avahi-daemon[860]: Registering new address record for fe80::d467:9306:5e3c:ed35 on tun0.*.
May 19 23:38:20 avahi-daemon[860]: Interface tun0.IPv6 no longer relevant for mDNS.
May 19 23:38:20 avahi-daemon[860]: Leaving mDNS multicast group on interface tun0.IPv6 with address fe80::d467:9306:5e3c:ed35.
May 19 23:38:20 avahi-daemon[860]: Withdrawing address record for fe80::d467:9306:5e3c:ed35 on tun0.
May 19 23:38:20 openvpn[36331]: 2025-05-19 23:38:20 /etc/openvpn/update-resolv-conf tun0 1500 0 10.16.0.20 255.255.0.0 init
May 19 23:38:20 NetworkManager[1011]: <info> [1747723100.8848] device (tun0): state change: activated -> unmanaged (reason 'unmanaged', managed-type: 'removed')
May 19 23:38:20 audit[36507]: AVC avc: denied { execute } for pid=36507 comm="resolvconf" name="systemctl" dev="nvme0n1p2" ino=171165 scontext=system_u:system_r:openvpn_t:s0 tcontext=system_u:object_r:systemd_systemctl_exec_t:s0 tclass=file permissive=0
May 19 23:38:20 audit[36507]: AVC avc: denied { execute } for pid=36507 comm="resolvconf" name="systemctl" dev="nvme0n1p2" ino=171165 scontext=system_u:system_r:openvpn_t:s0 tcontext=system_u:object_r:systemd_systemctl_exec_t:s0 tclass=file permissive=0
May 19 23:38:20 systemd[1]: Starting NetworkManager-dispatcher.service - Network Manager Script Dispatcher Service...
May 19 23:38:20 openvpn[36536]: The service command supports only basic LSB actions (start, stop, restart, try-restart, reload, reload-or-restart, try-reload-or-restart, force-reload, status, condrestart). For other actions, please try to use systemctl.
May 19 23:38:20 audit[36541]: AVC avc: denied { getattr } for pid=36541 comm="resolvconf" path="/run/avahi-daemon/pid" dev="tmpfs" ino=3071 scontext=system_u:system_r:openvpn_t:s0 tcontext=system_u:object_r:avahi_var_run_t:s0 tclass=file permissive=0
May 19 23:38:20 systemd[1]: Started NetworkManager-dispatcher.service - Network Manager Script Dispatcher Service.
May 19 23:38:20 audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
May 19 23:38:20 openvpn[36331]: 2025-05-19 23:38:20 SIGTERM[hard,] received, process exiting
May 19 23:38:20 systemd[1]: openvpn@mullvad_us_sea.service: Failed with result 'timeout'.
May 19 23:38:20 systemd[1]: Failed to start openvpn@mullvad_us_sea.service - OpenVPN service for mullvad_us_sea.
May 19 23:38:20 audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=openvpn@mullvad_us_sea comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'
May 19 23:38:21 systemd[1]: openvpn@mullvad_us_sea.service: Scheduled restart job, restart counter is at 285.
May 19 23:38:21 systemd[1]: Starting openvpn@mullvad_us_sea.service - OpenVPN service for mullvad_us_sea...
May 19 23:38:21 audit[36561]: AVC avc: denied { create } for pid=36561 comm="openvpn" scontext=system_u:system_r:openvpn_t:s0 tcontext=system_u:system_r:openvpn_t:s0 tclass=netlink_generic_socket permissive=0
May 19 23:38:21 openvpn[36561]: 2025-05-19 23:38:21 Note: Kernel support for ovpn-dco missing, disabling data channel offload.
May 19 23:38:21 openvpn[36561]: 2025-05-19 23:38:21 WARNING: file '/etc/openvpn/mullvad_userpass.txt' is group or others accessible
May 19 23:38:21 openvpn[36561]: 2025-05-19 23:38:21 OpenVPN 2.6.14 x86_64-redhat-linux-gnu [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [PKCS11] [MH/PKTINFO] [AEAD] [DCO]
May 19 23:38:21 openvpn[36561]: 2025-05-19 23:38:21 library versions: OpenSSL 3.2.4 11 Feb 2025, LZO 2.10
May 19 23:38:21 openvpn[36561]: 2025-05-19 23:38:21 DCO version: N/A
May 19 23:38:21 openvpn[36561]: 2025-05-19 23:38:21 NOTE: the current --script-security setting may allow this configuration to call user-defined scripts
May 19 23:38:21 openvpn[36561]: 2025-05-19 23:38:21 TCP/UDP: Preserving recently used remote address: [AF_INET]198.54.131.34:1302
May 19 23:38:21 openvpn[36561]: 2025-05-19 23:38:21 Socket Buffers: R=[212992->425984] S=[212992->425984]
May 19 23:38:21 openvpn[36561]: 2025-05-19 23:38:21 UDPv4 link local: (not bound)
May 19 23:38:21 openvpn[36561]: 2025-05-19 23:38:21 UDPv4 link remote: [AF_INET]198.54.131.34:1302
May 19 23:38:21 openvpn[36561]: 2025-05-19 23:38:21 TLS: Initial packet from [AF_INET]198.54.131.34:1302, sid=aa2c6adb 651c52c8
May 19 23:38:21 openvpn[36561]: 2025-05-19 23:38:21 WARNING: this configuration may cache passwords in memory -- use the auth-nocache option to prevent this
May 19 23:38:21 openvpn[36561]: 2025-05-19 23:38:21 VERIFY OK: depth=2, C=SE, ST=Gotaland, L=Gothenburg, O=Amagicom AB, OU=Mullvad, CN=Mullvad Root CA v2, [email protected]
May 19 23:38:21 openvpn[36561]: 2025-05-19 23:38:21 VERIFY OK: depth=1, C=SE, ST=Gotaland, O=Amagicom AB, OU=Mullvad, CN=Mullvad Intermediate CA v7, [email protected]
May 19 23:38:21 openvpn[36561]: 2025-05-19 23:38:21 VERIFY KU OK
May 19 23:38:21 openvpn[36561]: 2025-05-19 23:38:21 Validating certificate extended key usage
May 19 23:38:21 openvpn[36561]: 2025-05-19 23:38:21 ++ Certificate has EKU (str) TLS Web Server Authentication, expects TLS Web Server Authentication
May 19 23:38:21 openvpn[36561]: 2025-05-19 23:38:21 VERIFY EKU OK
May 19 23:38:21 openvpn[36561]: 2025-05-19 23:38:21 VERIFY OK: depth=0, C=SE, ST=Gotaland, O=Amagicom AB, OU=Mullvad, CN=us-sea-ovpn-101.mullvad.net, [email protected]
May 19 23:38:21 openvpn[36561]: 2025-05-19 23:38:21 Control Channel: TLSv1.3, cipher TLSv1.3 TLS_CHACHA20_POLY1305_SHA256, peer certificate: 4096 bits RSA, signature: RSA-SHA256, peer temporary key: 253 bits X25519
May 19 23:38:21 openvpn[36561]: 2025-05-19 23:38:21 [us-sea-ovpn-101.mullvad.net] Peer Connection Initiated with [AF_INET]198.54.131.34:1302
May 19 23:38:21 openvpn[36561]: 2025-05-19 23:38:21 TLS: move_session: dest=TM_ACTIVE src=TM_INITIAL reinit_src=1
May 19 23:38:21 openvpn[36561]: 2025-05-19 23:38:21 TLS: tls_multi_process: initial untrusted session promoted to trusted
May 19 23:38:22 openvpn[36561]: 2025-05-19 23:38:22 SENT CONTROL [us-sea-ovpn-101.mullvad.net]: 'PUSH_REQUEST' (status=1)
May 19 23:38:22 openvpn[36561]: 2025-05-19 23:38:22 PUSH: Received control message: 'PUSH_REPLY,dhcp-option DNS 10.16.0.1,redirect-gateway def1 bypass-dhcp,route-ipv6 0000::/2,route-ipv6 4000::/2,route-ipv6 8000::/2,route-ipv6 C000::/2,route-gateway 10.16.0.1,topology subnet,socket-flags TCP_NODELAY,ifconfig-ipv6 fdda:d0d0:cafe:1302::1006/64 fdda:d0d0:cafe:1302::,ifconfig 10.16.0.8 255.255.0.0,peer-id 7,cipher AES-256-GCM,protocol-flags cc-exit tls-ekm dyn-tls-crypt,tun-mtu 1500'
May 19 23:38:22 openvpn[36561]: 2025-05-19 23:38:22 Options error: option 'dhcp-option' cannot be used in this context ([PUSH-OPTIONS])
May 19 23:38:22 openvpn[36561]: 2025-05-19 23:38:22 Options error: option 'redirect-gateway' cannot be used in this context ([PUSH-OPTIONS])
May 19 23:38:22 openvpn[36561]: 2025-05-19 23:38:22 Options error: option 'route-ipv6' cannot be used in this context ([PUSH-OPTIONS])
May 19 23:38:22 openvpn[36561]: 2025-05-19 23:38:22 Options error: option 'route-ipv6' cannot be used in this context ([PUSH-OPTIONS])
May 19 23:38:22 openvpn[36561]: 2025-05-19 23:38:22 Options error: option 'route-ipv6' cannot be used in this context ([PUSH-OPTIONS])
May 19 23:38:22 openvpn[36561]: 2025-05-19 23:38:22 Options error: option 'route-ipv6' cannot be used in this context ([PUSH-OPTIONS])
May 19 23:38:22 openvpn[36561]: 2025-05-19 23:38:22 OPTIONS IMPORT: --socket-flags option modified
May 19 23:38:22 openvpn[36561]: 2025-05-19 23:38:22 NOTE: setsockopt TCP_NODELAY=1 failed
May 19 23:38:22 openvpn[36561]: 2025-05-19 23:38:22 OPTIONS IMPORT: --ifconfig/up options modified
May 19 23:38:22 openvpn[36561]: 2025-05-19 23:38:22 OPTIONS IMPORT: route-related options modified
May 19 23:38:22 openvpn[36561]: 2025-05-19 23:38:22 OPTIONS IMPORT: tun-mtu set to 1500
May 19 23:38:22 openvpn[36561]: 2025-05-19 23:38:22 net_route_v4_best_gw query: dst 0.0.0.0
May 19 23:38:22 openvpn[36561]: 2025-05-19 23:38:22 net_route_v4_best_gw result: via 192.168.12.1 dev wlp3s0
May 19 23:38:22 openvpn[36561]: 2025-05-19 23:38:22 ROUTE_GATEWAY 192.168.12.1/255.255.255.0 IFACE=wlp3s0 HWADDR=ea:6c:2a:13:52:ce
May 19 23:38:22 openvpn[36561]: 2025-05-19 23:38:22 TUN/TAP device tun0 opened
May 19 23:38:22 openvpn[36561]: 2025-05-19 23:38:22 net_iface_mtu_set: mtu 1500 for tun0
May 19 23:38:22 openvpn[36561]: 2025-05-19 23:38:22 net_iface_up: set tun0 up
May 19 23:38:22 openvpn[36561]: 2025-05-19 23:38:22 net_addr_v4_add: 10.16.0.8/16 dev tun0
May 19 23:38:22 avahi-daemon[860]: Joining mDNS multicast group on interface tun0.IPv6 with address fe80::2220:8750:2097:b38c.
May 19 23:38:22 avahi-daemon[860]: New relevant interface tun0.IPv6 for mDNS.
May 19 23:38:22 openvpn[36561]: 2025-05-19 23:38:22 net_iface_mtu_set: mtu 1500 for tun0
May 19 23:38:22 openvpn[36561]: 2025-05-19 23:38:22 net_iface_up: set tun0 up
May 19 23:38:22 openvpn[36561]: 2025-05-19 23:38:22 net_addr_v6_add: fdda:d0d0:cafe:1302::1006/64 dev tun0
May 19 23:38:22 openvpn[36561]: 2025-05-19 23:38:22 /etc/openvpn/update-resolv-conf tun0 1500 0 10.16.0.8 255.255.0.0 init
May 19 23:38:22 avahi-daemon[860]: Registering new address record for fe80::2220:8750:2097:b38c on tun0.*.
May 19 23:38:22 avahi-daemon[860]: Joining mDNS multicast group on interface tun0.IPv4 with address 10.16.0.8.
May 19 23:38:22 avahi-daemon[860]: New relevant interface tun0.IPv4 for mDNS.
May 19 23:38:22 avahi-daemon[860]: Registering new address record for 10.16.0.8 on tun0.IPv4.
May 19 23:38:22 NetworkManager[1011]: <info> [1747723102.3255] manager: (tun0): new Tun device (/org/freedesktop/NetworkManager/Devices/303)
May 19 23:38:22 avahi-daemon[860]: Leaving mDNS multicast group on interface tun0.IPv6 with address fe80::2220:8750:2097:b38c.
May 19 23:38:22 avahi-daemon[860]: Joining mDNS multicast group on interface tun0.IPv6 with address fdda:d0d0:cafe:1302::1006.
May 19 23:38:22 avahi-daemon[860]: Registering new address record for fdda:d0d0:cafe:1302::1006 on tun0.*.
May 19 23:38:22 avahi-daemon[860]: Withdrawing address record for fe80::2220:8750:2097:b38c on tun0.
May 19 23:38:22 audit[36582]: AVC avc: denied { execute } for pid=36582 comm="resolvconf" name="systemctl" dev="nvme0n1p2" ino=171165 scontext=system_u:system_r:openvpn_t:s0 tcontext=system_u:object_r:systemd_systemctl_exec_t:s0 tclass=file permissive=0
May 19 23:38:22 audit[36582]: AVC avc: denied { execute } for pid=36582 comm="resolvconf" name="systemctl" dev="nvme0n1p2" ino=171165 scontext=system_u:system_r:openvpn_t:s0 tcontext=system_u:object_r:systemd_systemctl_exec_t:s0 tclass=file permissive=0
May 19 23:38:22 NetworkManager[1011]: <info> [1747723102.3559] device (tun0): state change: unmanaged -> unavailable (reason 'connection-assumed', managed-type: 'external')
May 19 23:38:22 NetworkManager[1011]: <info> [1747723102.3585] device (tun0): state change: unavailable -> disconnected (reason 'connection-assumed', managed-type: 'external')
May 19 23:38:22 NetworkManager[1011]: <info> [1747723102.3595] device (tun0): Activation: starting connection 'tun0' (e6f240e1-b839-4aab-8b3a-22aa75e022fd)
May 19 23:38:22 NetworkManager[1011]: <info> [1747723102.3675] device (tun0): state change: disconnected -> prepare (reason 'none', managed-type: 'external')
May 19 23:38:22 NetworkManager[1011]: <info> [1747723102.3687] device (tun0): state change: prepare -> config (reason 'none', managed-type: 'external')
May 19 23:38:22 NetworkManager[1011]: <info> [1747723102.3689] device (tun0): state change: config -> ip-config (reason 'none', managed-type: 'external')
May 19 23:38:22 NetworkManager[1011]: <info> [1747723102.3691] device (tun0): state change: ip-config -> ip-check (reason 'none', managed-type: 'external')
May 19 23:38:22 NetworkManager[1011]: <info> [1747723102.3749] device (tun0): state change: ip-check -> secondaries (reason 'none', managed-type: 'external')
May 19 23:38:22 NetworkManager[1011]: <info> [1747723102.3754] device (tun0): state change: secondaries -> activated (reason 'none', managed-type: 'external')
May 19 23:38:22 NetworkManager[1011]: <info> [1747723102.3765] device (tun0): Activation: successful, device activated.
May 19 23:38:22 systemd[1]: iscsi.service: Unit cannot be reloaded because it is inactive.
May 19 23:38:22 openvpn[36561]: 2025-05-19 23:38:22 net_route_v4_add: 10.0.0.0/8 via 10.16.0.1 dev [NULL] table 0 metric -1
May 19 23:38:22 openvpn[36561]: 2025-05-19 23:38:22 Initialization Sequence Completed
May 19 23:38:22 openvpn[36561]: 2025-05-19 23:38:22 Data Channel: cipher 'AES-256-GCM', peer-id: 7
May 19 23:38:22 openvpn[36561]: 2025-05-19 23:38:22 Timers: ping 10, ping-restart 60
May 19 23:38:22 openvpn[36561]: 2025-05-19 23:38:22 Protocol options: protocol-flags cc-exit tls-ekm dyn-tls-crypt
May 19 23:38:32 systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully.
May 19 23:38:32 audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
NOTHING is being logged by the way. As it was "logging" I changed the name of my device in the extension and clicked the refresh button like five times and you can't see any of it in the log. I also tried manually adding the device via IP from both ends without success.
Hey, Fedora 42 user here. So I tried to install the whole thing from Git and also try to debug it. I found that installing OpenSSL Package works. you should give it a shot first.
Hey, Fedora 42 user here. So I tried to install the whole thing from Git and also try to debug it. I found that installing OpenSSL Package works. you should give it a shot first.
I'm on arch. I can confirm that having openssl installed, and installing gsconnect trough package manager (or building it manually) works. Although, installing it trough the Extensions Manager doesn't work, even with openssl.
Hmm, I should probably take a look deeper (since I'm installing an extension from the source and tested it and uninstalling it and reinstalling it back from the GNOME Extensions Store without restarting the GNOME Shell)
Same problem. Using Arch with Gnome 48 and cannot get my device to be discovered.
When I was using KDE for my DE, it would detect no issue with the same setup.
Same problem. Using Arch with Gnome 48 and cannot get my device to be discovered.
When I was using KDE for my DE, it would detect no issue with the same setup.
Try this (since in my fresh install of Arch it does work).
Uninstall the extension. Restart your PC and Reinstall it back.
Same problem. Using Arch with Gnome 48 and cannot get my device to be discovered. When I was using KDE for my DE, it would detect no issue with the same setup.
Try this (since in my fresh install of Arch it does work).
Uninstall the extension. Restart your PC and Reinstall it back.
I've tried everything over the last week with zero luck. I also tried setting it up on Fedora and same issue.
I tried it again on one of my KDE DE systems and works fine on there.
Same problem. Using Arch with Gnome 48 and cannot get my device to be discovered. When I was using KDE for my DE, it would detect no issue with the same setup.
Try this (since in my fresh install of Arch it does work). Uninstall the extension. Restart your PC and Reinstall it back.
I've tried everything over the last week with zero luck. I also tried setting it up on Fedora and same issue.
I tried it again on KDE DE and works fine on there.
I haven’t used that device in some time now, but if I recall correctly there is a troubleshooting doc somewhere on this GitHub page that fixed my issue; I would look wherever you can find troubleshooting steps and if that solves it I’ll close the issue. It may have been an OpenSSL thing as mentioned by @BenjaminFosters.
Howdy folks, I know it's been a long time. How's the GSConnect right now?
@BenjaminFosters
Works fine. Just keep in mind, you might need to install openssl package on your distro in order for it to connect.