Gnome-shell-extension-gsconnect: Notifications from phone don't appear on desktop any more
Describe the bug
Hi. Notifications from my phone to the desktop have recently stopped working.
I can still send messages and ring it from the desktop, but I only get notifications for low battery and incoming calls. If I miss the call, the notification goes away and doesn't hang around in GNOME's notification dropdown.
Nothing has changed on my phone from the time it was working (the same Android version and the same KDE Connect version).
Expected behavior
Notifications should have continued to appear and remain in GNOME's notification area.
System Details (please complete the following information):
- GSConnect version: 28
- Installed from: GNOME Extensions website
- GNOME/Shell version: 3.34
- Distro/Release: Ubuntu 19.10
Additional Notes:
I recently upgraded from Ubuntu 19.04 to 19.10. I tried unsuccessfully to re-pair my phone to GSConnect. It connected but I still don't get notifications.
atylmo
All 8 comments
Hi, can you please reproduce the problem following the steps described in Generate Support Log so we can figure out why this is happening?
EDIT: there's an Android app I use sometimes called Fake Notifications you can use, so you don't have to wait to get one. Probably there are others too.
andyholmes
on 5 Nov 2019
Sure. I'm sorry I didn't include it earlier. I was trying to figure out that very problem :) I actually had a similar app installed and did a log with it but I didn't know if it would be worth anything since I made the notification on the phone (so it might have been instantly marked as viewed and not show up on my laptop).
Thanks for the app link! Here's what I get making a notification with it:
GSConnect Version: 28
GSConnect Install: user
GJS: 15801
XDG_SESSION_TYPE: x11
GDMSESSION: ubuntu
--------------------------------------------------------------------------------
-- Logs begin at Mon 2019-10-07 12:31:39 EDT, end at Fri 2019-11-08 21:05:33 EST. --
Nov 08 21:04:33 xdg-desktop-por[1385]: Failed to get application states: GDBus.Error:org.freedesktop.portal.Error.Failed: Could not get window list: GDBus.Error:org.freedesktop.DBus.Error.AccessDenied: App introspection not allowed
Nov 08 21:04:45 org.gnome.Shell.Extensions.GSConnect[1851]: [/service/protocol/core.js:send:321]: TCL: {
"id": 1573265085646,
"type": "kdeconnect.systemvolume",
"body": {
"sinkList": [
{
"name": "alsa_output.pci-0000_00_1f.3.analog-stereo",
"description": "Speakers (Built-in Audio Analog Stereo)",
"muted": false,
"volume": 13399,
"maxVolume": 65536
}
]
}
}
Nov 08 21:04:45 org.gnome.Shell.Extensions.GSConnect[1851]: [/service/protocol/core.js:send:321]: TCL: {
"id": 1573265085740,
"type": "kdeconnect.systemvolume",
"body": {
"sinkList": [
{
"name": "alsa_output.pci-0000_00_1f.3.analog-stereo",
"description": "Speakers (Built-in Audio Analog Stereo)",
"muted": false,
"volume": 13399,
"maxVolume": 65536
}
]
}
}
Nov 08 21:04:50 org.gnome.Shell.Extensions.GSConnect[1851]: [/service/protocol/core.js:send:321]: TCL: {
"id": 1573265090748,
"type": "kdeconnect.systemvolume",
"body": {
"sinkList": [
{
"name": "alsa_output.pci-0000_00_1f.3.analog-stereo",
"description": "Speakers (Built-in Audio Analog Stereo)",
"muted": false,
"volume": 13399,
"maxVolume": 65536
}
]
}
}
Nov 08 21:05:33 xdg-desktop-por[1385]: Failed to get application states: GDBus.Error:org.freedesktop.portal.Error.Failed: Could not get window list: GDBus.Error:org.freedesktop.DBus.Error.AccessDenied: App introspection not allowed`
Just to add, I did some more testing and I can get laptop notifications on my phone.
atylmo
on 9 Nov 2019
Hmm, from your logs it doesn't look like GSConnect is receiving any notification packets. I'm assuming you kept the Generate Support Log dialog open while you sent these notifications.
If that's true, this is probably an issue in the Android app. I would double check the plugin is enabled in the app, then try clearing the app's cache (but not data since I think that will unpair) and then force-quit and restart. Let me know if that helps.
andyholmes
on 9 Nov 2019
Well I'll be darned. It was the cache. I wouldn't have thought to do that. It totally works now. Thank you! :)
I wonder why that happened. The only thing I've done to my phone was take out the SD card.
atylmo
on 9 Nov 2019
I wonder why that happened.
So hard to say, as frustrating as that is. It's just sort of the nature of the beast, really. (After all, if these bugs were _predictable_ and easy to pinpoint, they'd have been fixed ages ago. The ones that still linger are the ones that are tough to track down and get a handle on.)
Could've been a KDE Connect app update on Android, always a possibility of something transient going wrong during that process. Or, the upgrade to GSConnect 28 might've confused the app, if they were connected at the time. ¯\_(ツ)_/¯
Personally I've resigned myself to never knowing, for the most part. I feel like 20% would be an overestimate of how often I'm actually able to pinpoint a triggering event for issues like that, on my own phone. Fortunately they're infrequent enough that... meh.
ferdnyc
on 9 Nov 2019
Remember when I said it worked? Well... it's stopped again. :grimacing: I got it working, so I thought, "Hey, it would be neat to have notifications on the desktop make a sound so I won't miss a text."
So I installed python-dbus to run this: https://github.com/dbazile/gaudible
And now it won't sync again. I tried clearing the app cache, force-stopping, and rebooting my laptop. The app keeps crashing and after clearing its data I get authentication errors from GSConnect. In KDE Connect my laptop keeps appearing and disappearing. If I manage to tap on it I get to "Request Pairing" and then it hangs on the loading circle after I tap to pair it.
I thought this was on the app side but I removed and installed a newer version and it does the same thing. Hmm.
Sigh. I have a bad habit of breaking things that don't need fixing.
GSConnect Version: 28
GSConnect Install: user
GJS: 15801
XDG_SESSION_TYPE: x11
GDMSESSION: ubuntu
--------------------------------------------------------------------------------
-- Logs begin at Mon 2019-10-07 14:58:11 EDT, end at Sat 2019-11-09 18:14:27 EST. --
Nov 09 18:14:02 gjs[5770]: JS ERROR: AuthenticationError
_authenticate@/home/ty1904/.local/share/gnome-shell/extensions/[email protected]/service/protocol/lan.js:594:29
async*_clientEncryption@/home/ty1904/.local/share/gnome-shell/extensions/[email protected]/service/protocol/lan.js:620:16
accept@/home/ty1904/.local/share/gnome-shell/extensions/[email protected]/service/protocol/lan.js:719:38
async*_onIncomingChannel@/home/ty1904/.local/share/gnome-shell/extensions/[email protected]/service/protocol/lan.js:175:19
Async*@/home/ty1904/.local/share/gnome-shell/extensions/[email protected]/service/daemon.js:1149:2
Nov 09 18:14:07 gjs[5770]: JS ERROR: AuthenticationError
_authenticate@/home/ty1904/.local/share/gnome-shell/extensions/[email protected]/service/protocol/lan.js:594:29
async*_clientEncryption@/home/ty1904/.local/share/gnome-shell/extensions/[email protected]/service/protocol/lan.js:620:16
accept@/home/ty1904/.local/share/gnome-shell/extensions/[email protected]/service/protocol/lan.js:719:38
async*_onIncomingChannel@/home/ty1904/.local/share/gnome-shell/extensions/[email protected]/service/protocol/lan.js:175:19
Async*@/home/ty1904/.local/share/gnome-shell/extensions/[email protected]/service/daemon.js:1149:2
Nov 09 18:14:12 gjs[5770]: JS ERROR: AuthenticationError
_authenticate@/home/ty1904/.local/share/gnome-shell/extensions/[email protected]/service/protocol/lan.js:594:29
async*_clientEncryption@/home/ty1904/.local/share/gnome-shell/extensions/[email protected]/service/protocol/lan.js:620:16
accept@/home/ty1904/.local/share/gnome-shell/extensions/[email protected]/service/protocol/lan.js:719:38
async*_onIncomingChannel@/home/ty1904/.local/share/gnome-shell/extensions/[email protected]/service/protocol/lan.js:175:19
Async*@/home/ty1904/.local/share/gnome-shell/extensions/[email protected]/service/daemon.js:1149:2
Nov 09 18:14:17 gjs[5770]: JS ERROR: AuthenticationError
_authenticate@/home/ty1904/.local/share/gnome-shell/extensions/[email protected]/service/protocol/lan.js:594:29
async*_clientEncryption@/home/ty1904/.local/share/gnome-shell/extensions/[email protected]/service/protocol/lan.js:620:16
accept@/home/ty1904/.local/share/gnome-shell/extensions/[email protected]/service/protocol/lan.js:719:38
async*_onIncomingChannel@/home/ty1904/.local/share/gnome-shell/extensions/[email protected]/service/protocol/lan.js:175:19
Async*@/home/ty1904/.local/share/gnome-shell/extensions/[email protected]/service/daemon.js:1149:2
Nov 09 18:14:18 dbus-daemon[992]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service' requested by ':1.309' (uid=1000 pid=5827 comm="gjs /home/ty1904/.local/share/gnome-shell/extensio" label="unconfined")
Nov 09 18:14:18 systemd[1]: Starting Hostname Service...
Nov 09 18:14:19 dbus-daemon[992]: [system] Successfully activated service 'org.freedesktop.hostname1'
Nov 09 18:14:19 systemd[1]: Started Hostname Service.
Nov 09 18:14:19 xdg-desktop-por[1388]: Failed to get application states: GDBus.Error:org.freedesktop.portal.Error.Failed: Could not get window list: GDBus.Error:org.freedesktop.DBus.Error.AccessDenied: App introspection not allowed
Nov 09 18:14:22 gjs[5770]: JS ERROR: AuthenticationError
_authenticate@/home/ty1904/.local/share/gnome-shell/extensions/[email protected]/service/protocol/lan.js:594:29
async*_clientEncryption@/home/ty1904/.local/share/gnome-shell/extensions/[email protected]/service/protocol/lan.js:620:16
accept@/home/ty1904/.local/share/gnome-shell/extensions/[email protected]/service/protocol/lan.js:719:38
async*_onIncomingChannel@/home/ty1904/.local/share/gnome-shell/extensions/[email protected]/service/protocol/lan.js:175:19
Async*@/home/ty1904/.local/share/gnome-shell/extensions/[email protected]/service/daemon.js:1149:2
Nov 09 18:14:27 org.gnome.Shell.Extensions.GSConnect[5770]: [/service/protocol/lan.js:accept:714]: "lan://192.168.1.2:1716 (a74bb300-670c-4b77-8138-18c6f7ab6709)"
Nov 09 18:14:27 gjs[5770]: JS ERROR: AuthenticationError
_authenticate@/home/ty1904/.local/share/gnome-shell/extensions/[email protected]/service/protocol/lan.js:594:29
async*_clientEncryption@/home/ty1904/.local/share/gnome-shell/extensions/[email protected]/service/protocol/lan.js:620:16
accept@/home/ty1904/.local/share/gnome-shell/extensions/[email protected]/service/protocol/lan.js:719:38
async*_onIncomingChannel@/home/ty1904/.local/share/gnome-shell/extensions/[email protected]/service/protocol/lan.js:175:19
Async*@/home/ty1904/.local/share/gnome-shell/extensions/[email protected]/service/daemon.js:1149:2
Nov 09 18:14:27 org.gnome.Shell.Extensions.GSConnect[5770]: [/service/protocol/lan.js:close:750]: "lan://192.168.1.2:1716 (a74bb300-670c-4b77-8138-18c6f7ab6709)"
Nov 09 18:14:27 org.gnome.Shell.Extensions.GSConnect[5770]: [/service/protocol/lan.js:_authenticate:594]:
_authenticate@/home/ty1904/.local/share/gnome-shell/extensions/[email protected]/service/protocol/lan.js:594:29
async*_clientEncryption@/home/ty1904/.local/share/gnome-shell/extensions/[email protected]/service/protocol/lan.js:620:16
accept@/home/ty1904/.local/share/gnome-shell/extensions/[email protected]/service/protocol/lan.js:719:38
async*_onIncomingChannel@/home/ty1904/.local/share/gnome-shell/extensions/[email protected]/service/protocol/lan.js:175:19
Async*@/home/ty1904/.local/share/gnome-shell/extensions/[email protected]/service/daemon.js:1149:2
GSConnect thinks you're still paired, but because you've cleared the data instead of just the cache. So the app generated a new certificate and GSConnect is rejecting it because it doesn't match the certificate it's expecting.
You'll have to unpair the device in GSConnect and repair. Actually, it's probably easier just to wipe the certificate key and make sure it's unpaired:
dconf reset /org/gnome/shell/extensions/gsconnect/device/YOUR_DEVICE_ID/certificate-pem
dconf reset /org/gnome/shell/extensions/gsconnect/device/YOUR_DEVICE_ID/paired
You can also do that in dconf-editor if a GUI is easier for you.
andyholmes
on 10 Nov 2019
Ah. :) Sorry, I know you said not to do that but I kind of panicked when I broke it.
We're back in business! Sorry for the trouble. I incredibly appreciate your dedication to this project. Responding to bug reports within an hour on a weekend :)
atylmo
on 10 Nov 2019
Related issues
ricvelozo
·
4Comments
sk0gen
·
4Comments
neumannjan
·
3Comments
paulo8448
·
4Comments
Noobsai
·
4Comments
Most helpful comment
Well I'll be darned. It was the cache. I wouldn't have thought to do that. It totally works now. Thank you! :)
I wonder why that happened. The only thing I've done to my phone was take out the SD card.