andyholmes
commented
4 years ago Sorry, I'm going to needa bit more information. How can I reproduce this? Are you using Wayland or X11? Are there any errors in the log?
Closed uniquePWD closed 4 years ago
andyholmes
commented
4 years ago Sorry, I'm going to needa bit more information. How can I reproduce this? Are you using Wayland or X11? Are there any errors in the log?
uniquePWD
commented
4 years ago I'm on X11. I'm not seeing any errors in the log. All I know is that when I disable GSConnect, my system stops playing up.
andyholmes
commented
4 years ago Okay, since I can't reproduce this I'll have to wait until someone experiencing it can give me an example of how to recreate the problem.
uniquePWD
commented
4 years ago I enabled this again and once again my system was unusable. I know I'm offering useful information, but it's worth noting in case someone is able to track down why.
uniquePWD
commented
4 years ago So I finally managed to fix this. I'm not sure if it's a Pixel 4 Problem, an Android 10 problem, a GSConnect problem or KDE Connect problem. But disabling the SFTP permission under Advanced in GSConnect for my Pixel 4 XL fixes the issue.
cc @andyholmes
andyholmes
commented
4 years ago I still can't reproduce this with the SFTP plugin. Can you try to generate a support log while using this feature? Without some logging to point me in the right direction, there's not much I can do about this.
uniquePWD
commented
4 years ago I still can't reproduce this with the SFTP plugin. Can you try to generate a support log while using this feature? Without some logging to point me in the right direction, there's not much I can do about this.
Is this helpful?
GSConnect Version: 30
GSConnect Install: user
GJS: 15803
XDG_SESSION_TYPE: x11
GDMSESSION: gnome
--------------------------------------------------------------------------------
-- Logs begin at Sat 2019-07-06 19:05:08 BST, end at Tue 2019-12-10 20:59:45 GMT. --
Dec 10 20:59:05 org.gnome.Shell.Extensions.GSConnect[2107]: [/service/protocol/lan.js:_onIdentity:313]: {
"id": 1576011546246,
"type": "kdeconnect.identity",
"body": {
"deviceId": "933274a6d03d0611",
"deviceName": "Illion-SHIELD",
"protocolVersion": 7,
"deviceType": "tablet",
"incomingCapabilities": [
"kdeconnect.telephony.request_mute",
"kdeconnect.contacts.request_vcards_by_uid",
"kdeconnect.notification.request",
"kdeconnect.share.request.update",
"kdeconnect.sftp.request",
"kdeconnect.battery.request",
"kdeconnect.notification",
"kdeconnect.ping",
"kdeconnect.share.request",
"kdeconnect.mpris",
"kdeconnect.sms.request_conversations",
"kdeconnect.photo.request",
"kdeconnect.sms.request",
"kdeconnect.runcommand",
"kdeconnect.clipboard.connect",
"kdeconnect.findmyphone.request",
"kdeconnect.mpris.request",
"kdeconnect.clipboard",
"kdeconnect.telephony.request",
"kdeconnect.notification.reply",
"kdeconnect.systemvolume",
"kdeconnect.sms.request_conversation",
"kdeconnect.contacts.request_all_uids_timestamps",
"kdeconnect.mousepad.request",
"kdeconnect.mousepad.keyboardstate",
"kdeconnect.notification.action"
],
"outgoingCapabilities": [
"kdeconnect.mousepad.echo",
"kdeconnect.sms.messages",
"kdeconnect.runcommand.request",
"kdeconnect.mpris.request",
"kdeconnect.notification.request",
"kdeconnect.photo",
"kdeconnect.clipboard",
"kdeconnect.notification",
"kdeconnect.ping",
"kdeconnect.sftp",
"kdeconnect.contacts.response_uids_timestamps",
"kdeconnect.mpris",
"kdeconnect.share.request",
"kdeconnect.presenter",
"kdeconnect.contacts.response_vcards",
"kdeconnect.mousepad.request",
"kdeconnect.telephony",
"kdeconnect.mousepad.keyboardstate",
"kdeconnect.clipboard.connect",
"kdeconnect.systemvolume.request",
"kdeconnect.battery",
"kdeconnect.findmyphone.request"
],
"tcpPort": 1716,
"tcpHost": "192.168.0.20"
}
}
Dec 10 20:59:05 org.gnome.Shell.Extensions.GSConnect[2107]: [/service/protocol/lan.js:open:733]: "lan://192.168.0.20:1716 (c300454b-5942-417c-90ad-e156b6ea4179)"
Dec 10 20:59:05 org.gnome.Shell.Extensions.GSConnect[2107]: [/service/protocol/lan.js:attach:784]: "lan://192.168.0.20:1716 (bfe27f13-a74b-4e99-a7e9-8a3ace1315f7) => lan://192.168.0.20:1716 (c300454b-5942-417c-90ad-e156b6ea4179)"
Dec 10 20:59:05 org.gnome.Shell.Extensions.GSConnect[2107]: [/service/protocol/lan.js:close:750]: "lan://192.168.0.20:1716 (bfe27f13-a74b-4e99-a7e9-8a3ace1315f7)"
Dec 10 20:59:05 org.gnome.Shell.Extensions.GSConnect[2107]: [/service/device.js:_setConnected:312]: "Connected to Illion-SHIELD (933274a6d03d0611)"
Dec 10 20:59:12 gnome-shell[1772]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x8400007
Dec 10 20:59:12 dbus-broker-launch[1674]: Noticed file-system modification, trigger reload.
Dec 10 20:59:12 dbus-broker-launch[1674]: Service file '/usr/share/dbus-1/services/org.gnome.evolution.dataserver.AddressBook.service' is not named after the D-Bus name 'org.gnome.evolution.dataserver.AddressBook10'.
Dec 10 20:59:12 dbus-broker-launch[1674]: Service file '/usr/share/dbus-1/services/org.gnome.evolution.dataserver.Calendar.service' is not named after the D-Bus name 'org.gnome.evolution.dataserver.Calendar8'.
Dec 10 20:59:12 dbus-broker-launch[1674]: Service file '/usr/share/dbus-1/services/org.gnome.evolution.dataserver.UserPrompter.service' is not named after the D-Bus name 'org.gnome.evolution.dataserver.UserPrompter0'.
Dec 10 20:59:12 dbus-broker-launch[1674]: Service file '/usr/share/dbus-1/services/org.gnome.evolution.dataserver.Sources.service' is not named after the D-Bus name 'org.gnome.evolution.dataserver.Sources5'.
Dec 10 20:59:12 dbus-broker-launch[1674]: Policy to allow eavesdropping in /usr/share/dbus-1/session.conf +31: Eavesdropping is deprecated and ignored
Dec 10 20:59:12 dbus-broker-launch[1674]: Policy to allow eavesdropping in /usr/share/dbus-1/session.conf +33: Eavesdropping is deprecated and ignored
Dec 10 20:59:12 systemd[1639]: Starting Tracker metadata database store and lookup manager...
Dec 10 20:59:12 systemd[1639]: Started Tracker metadata database store and lookup manager.
Dec 10 20:59:12 gnome-shell[1772]: Ignoring search provider /usr/share/gnome-shell/search-providers/firefox-search-provider.ini: missing DesktopId
Dec 10 20:59:12 gnome-shell-ext[36580]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Dec 10 20:59:12 gnome-shell-ext[36580]: The offending signal was destroy on Gjs_ExtensionRow 0x55c248bd6690.
Dec 10 20:59:12 org.gnome.tweaks.desktop[1772]: == Stack trace for context 0x55c248b081a0 ==
Dec 10 20:59:12 gnome-shell-ext[36580]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Dec 10 20:59:12 org.gnome.tweaks.desktop[1772]: == Stack trace for context 0x55c248b081a0 ==
Dec 10 20:59:12 gnome-shell-ext[36580]: The offending signal was destroy on Gjs_ExtensionRow 0x55c2492c9390.
Dec 10 20:59:12 org.gnome.tweaks.desktop[1772]: == Stack trace for context 0x55c248b081a0 ==
Dec 10 20:59:12 gnome-shell-ext[36580]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Dec 10 20:59:12 gnome-shell-ext[36580]: The offending signal was destroy on Gjs_ExtensionRow 0x55c2492da330.
Dec 10 20:59:12 org.gnome.tweaks.desktop[1772]: == Stack trace for context 0x55c248b081a0 ==
Dec 10 20:59:12 gnome-shell-ext[36580]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Dec 10 20:59:12 gnome-shell-ext[36580]: The offending signal was destroy on Gjs_ExtensionRow 0x55c2492da630.
Dec 10 20:59:12 org.gnome.tweaks.desktop[1772]: == Stack trace for context 0x55c248b081a0 ==
Dec 10 20:59:12 gnome-shell-ext[36580]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Dec 10 20:59:12 gnome-shell-ext[36580]: The offending signal was destroy on Gjs_ExtensionRow 0x55c248fc72f0.
Dec 10 20:59:12 org.gnome.tweaks.desktop[1772]: == Stack trace for context 0x55c248b081a0 ==
Dec 10 20:59:12 gnome-shell-ext[36580]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Dec 10 20:59:12 org.gnome.tweaks.desktop[1772]: == Stack trace for context 0x55c248b081a0 ==
Dec 10 20:59:12 gnome-shell-ext[36580]: The offending signal was destroy on Gjs_ExtensionRow 0x55c248fc7ef0.
Dec 10 20:59:12 gnome-shell-ext[36580]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Dec 10 20:59:12 org.gnome.tweaks.desktop[1772]: == Stack trace for context 0x55c248b081a0 ==
Dec 10 20:59:12 gnome-shell-ext[36580]: The offending signal was destroy on Gjs_ExtensionRow 0x55c2492da930.
Dec 10 20:59:12 org.gnome.tweaks.desktop[1772]: == Stack trace for context 0x55c248b081a0 ==
Dec 10 20:59:12 gnome-shell-ext[36580]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Dec 10 20:59:12 org.gnome.tweaks.desktop[1772]: == Stack trace for context 0x55c248b081a0 ==
Dec 10 20:59:12 gnome-shell-ext[36580]: The offending signal was destroy on Gjs_ExtensionRow 0x55c248fc75f0.
Dec 10 20:59:12 gnome-shell-ext[36580]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Dec 10 20:59:12 gnome-shell-ext[36580]: The offending signal was destroy on Gjs_ExtensionRow 0x55c248bd6c90.
Dec 10 20:59:12 gnome-shell-ext[36580]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Dec 10 20:59:12 gnome-shell-ext[36580]: The offending signal was destroy on Gjs_ExtensionRow 0x55c2492dac30.
Dec 10 20:59:12 gnome-shell-ext[36580]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Dec 10 20:59:12 gnome-shell-ext[36580]: The offending signal was destroy on Gjs_ExtensionRow 0x55c248bd6990.
Dec 10 20:59:12 gnome-shell-ext[36580]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Dec 10 20:59:12 gnome-shell-ext[36580]: The offending signal was destroy on Gjs_ExtensionRow 0x55c248bd6f90.
Dec 10 20:59:12 gnome-shell-ext[36580]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Dec 10 20:59:12 gnome-shell-ext[36580]: The offending signal was destroy on Gjs_ExtensionRow 0x55c248fc78f0.
Dec 10 20:59:12 gnome-shell-ext[36580]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Dec 10 20:59:12 gnome-shell-ext[36580]: The offending signal was destroy on Gjs_ExtensionRow 0x55c248bd6390.
Dec 10 20:59:12 gnome-shell-ext[36580]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Dec 10 20:59:12 gnome-shell-ext[36580]: The offending signal was destroy on Gjs_ExtensionRow 0x55c2492daf30.
Dec 10 20:59:12 gnome-shell-ext[36580]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
Dec 10 20:59:12 gnome-shell-ext[36580]: The offending signal was destroy on Gjs_ExtensionRow 0x55c248fc7bf0.
Dec 10 20:59:12 systemd[1639]: Starting Tracker metadata extractor...
Dec 10 20:59:12 gnome-shell[1772]: Ignoring search provider /usr/share/gnome-shell/search-providers/firefox-search-provider.ini: missing DesktopId
Dec 10 20:59:12 systemd[1639]: Started Tracker metadata extractor.
Dec 10 20:59:22 systemd[1639]: tracker-extract.service: Succeeded.
Dec 10 20:59:30 org.gnome.Shell.Extensions.GSConnect[2107]: [/service/protocol/lan.js:_onIdentity:313]: {
"id": 1576011571153,
"type": "kdeconnect.identity",
"body": {
"deviceId": "933274a6d03d0611",
"deviceName": "Illion-SHIELD",
"protocolVersion": 7,
"deviceType": "tablet",
"incomingCapabilities": [
"kdeconnect.telephony.request_mute",
"kdeconnect.contacts.request_vcards_by_uid",
"kdeconnect.notification.request",
"kdeconnect.share.request.update",
"kdeconnect.sftp.request",
"kdeconnect.battery.request",
"kdeconnect.notification",
"kdeconnect.ping",
"kdeconnect.share.request",
"kdeconnect.mpris",
"kdeconnect.sms.request_conversations",
"kdeconnect.photo.request",
"kdeconnect.sms.request",
"kdeconnect.runcommand",
"kdeconnect.clipboard.connect",
"kdeconnect.findmyphone.request",
"kdeconnect.mpris.request",
"kdeconnect.clipboard",
"kdeconnect.telephony.request",
"kdeconnect.notification.reply",
"kdeconnect.systemvolume",
"kdeconnect.sms.request_conversation",
"kdeconnect.contacts.request_all_uids_timestamps",
"kdeconnect.mousepad.request",
"kdeconnect.mousepad.keyboardstate",
"kdeconnect.notification.action"
],
"outgoingCapabilities": [
"kdeconnect.mousepad.echo",
"kdeconnect.sms.messages",
"kdeconnect.runcommand.request",
"kdeconnect.mpris.request",
"kdeconnect.notification.request",
"kdeconnect.photo",
"kdeconnect.clipboard",
"kdeconnect.notification",
"kdeconnect.ping",
"kdeconnect.sftp",
"kdeconnect.contacts.response_uids_timestamps",
"kdeconnect.mpris",
"kdeconnect.share.request",
"kdeconnect.presenter",
"kdeconnect.contacts.response_vcards",
"kdeconnect.mousepad.request",
"kdeconnect.telephony",
"kdeconnect.mousepad.keyboardstate",
"kdeconnect.clipboard.connect",
"kdeconnect.systemvolume.request",
"kdeconnect.battery",
"kdeconnect.findmyphone.request"
],
"tcpPort": 1716,
"tcpHost": "192.168.0.20"
}
}
Dec 10 20:59:30 org.gnome.Shell.Extensions.GSConnect[2107]: [/service/protocol/lan.js:open:733]: "lan://192.168.0.20:1716 (af7c936c-7a38-4057-a826-8fe315929d95)"
Dec 10 20:59:31 org.gnome.Shell.Extensions.GSConnect[2107]: [/service/protocol/lan.js:attach:784]: "lan://192.168.0.20:1716 (c300454b-5942-417c-90ad-e156b6ea4179) => lan://192.168.0.20:1716 (af7c936c-7a38-4057-a826-8fe315929d95)"
Dec 10 20:59:31 org.gnome.Shell.Extensions.GSConnect[2107]: [/service/protocol/lan.js:close:750]: "lan://192.168.0.20:1716 (c300454b-5942-417c-90ad-e156b6ea4179)"
Dec 10 20:59:31 org.gnome.Shell.Extensions.GSConnect[2107]: [/service/device.js:_setConnected:312]: "Connected to Illion-SHIELD (933274a6d03d0611)"
Dec 10 20:59:38 gnome-shell[1772]: value "-1.000000" of type 'gfloat' is invalid or out of range for property 'width' of type 'gfloat'
Dec 10 20:59:38 gnome-shell[1772]: value "-1.000000" of type 'gfloat' is invalid or out of range for property 'height' of type 'gfloat'
Dec 10 20:59:38 gnome-shell[1772]: value "-1.000000" of type 'gfloat' is invalid or out of range for property 'width' of type 'gfloat'
Dec 10 20:59:38 gnome-shell[1772]: value "-1.000000" of type 'gfloat' is invalid or out of range for property 'height' of type 'gfloat'
Dec 10 20:59:41 org.gnome.Shell.Extensions.GSConnect[2107]: [/service/protocol/core.js:receive/<:283]: Illion-G6: {
"id": 1575936442315,
"type": "kdeconnect.battery",
"body": {
"currentCharge": 90,
"isCharging": true,
"thresholdEvent": 0
}
}
Dec 10 20:59:42 org.gnome.Shell.Extensions.GSConnect[2107]: [/service/protocol/core.js:send:329]: Illion-P4XL: {
"id": 1576011582206,
"type": "kdeconnect.share.request",
"body": {
"filename": "Tales_of_Herding_Gods_876-885.epub",
"open": false
},
"payloadSize": 126477,
"payloadTransferInfo": {
"port": 1739
}
}
Dec 10 20:59:42 org.gnome.Shell.Extensions.GSConnect[2107]: [/service/protocol/lan.js:close:750]: "lan://192.168.0.41:1739 (c7f8e312-8f91-41f7-ac81-02aa5b1ed250)"
Dec 10 20:59:42 tracker-store[36601]: OK
Dec 10 20:59:42 systemd[1639]: tracker-store.service: Succeeded.
Dec 10 20:59:45 org.gnome.Shell.Extensions.GSConnect[2107]: [/service/protocol/lan.js:_onIdentity:313]: {
"id": 1576011586012,
"type": "kdeconnect.identity",
"body": {
"deviceId": "933274a6d03d0611",
"deviceName": "Illion-SHIELD",
"protocolVersion": 7,
"deviceType": "tablet",
"incomingCapabilities": [
"kdeconnect.telephony.request_mute",
"kdeconnect.contacts.request_vcards_by_uid",
"kdeconnect.notification.request",
"kdeconnect.share.request.update",
"kdeconnect.sftp.request",
"kdeconnect.battery.request",
"kdeconnect.notification",
"kdeconnect.ping",
"kdeconnect.share.request",
"kdeconnect.mpris",
"kdeconnect.sms.request_conversations",
"kdeconnect.photo.request",
"kdeconnect.sms.request",
"kdeconnect.runcommand",
"kdeconnect.clipboard.connect",
"kdeconnect.findmyphone.request",
"kdeconnect.mpris.request",
"kdeconnect.clipboard",
"kdeconnect.telephony.request",
"kdeconnect.notification.reply",
"kdeconnect.systemvolume",
"kdeconnect.sms.request_conversation",
"kdeconnect.contacts.request_all_uids_timestamps",
"kdeconnect.mousepad.request",
"kdeconnect.mousepad.keyboardstate",
"kdeconnect.notification.action"
],
"outgoingCapabilities": [
"kdeconnect.mousepad.echo",
"kdeconnect.sms.messages",
"kdeconnect.runcommand.request",
"kdeconnect.mpris.request",
"kdeconnect.notification.request",
"kdeconnect.photo",
"kdeconnect.clipboard",
"kdeconnect.notification",
"kdeconnect.ping",
"kdeconnect.sftp",
"kdeconnect.contacts.response_uids_timestamps",
"kdeconnect.mpris",
"kdeconnect.share.request",
"kdeconnect.presenter",
"kdeconnect.contacts.response_vcards",
"kdeconnect.mousepad.request",
"kdeconnect.telephony",
"kdeconnect.mousepad.keyboardstate",
"kdeconnect.clipboard.connect",
"kdeconnect.systemvolume.request",
"kdeconnect.battery",
"kdeconnect.findmyphone.request"
],
"tcpPort": 1716,
"tcpHost": "192.168.0.20"
}
}
Dec 10 20:59:45 org.gnome.Shell.Extensions.GSConnect[2107]: [/service/protocol/lan.js:open:733]: "lan://192.168.0.20:1716 (e583a02a-6950-4093-bf34-5c3f1e249054)"
Dec 10 20:59:45 org.gnome.Shell.Extensions.GSConnect[2107]: [/service/protocol/lan.js:attach:784]: "lan://192.168.0.20:1716 (af7c936c-7a38-4057-a826-8fe315929d95) => lan://192.168.0.20:1716 (e583a02a-6950-4093-bf34-5c3f1e249054)"
Dec 10 20:59:45 org.gnome.Shell.Extensions.GSConnect[2107]: [/service/protocol/lan.js:close:750]: "lan://192.168.0.20:1716 (af7c936c-7a38-4057-a826-8fe315929d95)"
Dec 10 20:59:45 org.gnome.Shell.Extensions.GSConnect[2107]: [/service/device.js:_setConnected:312]: "Connected to Illion-SHIELD (933274a6d03d0611)"Hmm, well there's no messages here about the SFTP plugin, or anything indicating that something has gone wrong. So nothing that can help me track down the problem, sorry.
knard
commented
4 years ago I'm experiencing the same issue on both wayland and X11. I'm experiencing it since recently. maybe since last gnome update I have 3.34.4. here are some logs :
GSConnect Version: 31
GSConnect Install: user
GJS: 15805
XDG_SESSION_TYPE: x11
GDMSESSION: gnome-xorg
--------------------------------------------------------------------------------
[0;1;39mHint: You are currently not seeing messages from other users and the system.[0m
[0;1;39m Users in groups 'adm', 'systemd-journal', 'wheel' can see all messages.[0m
[0;1;39m Pass -q to turn off this notice.[0m
-- Logs begin at Wed 2019-10-09 21:55:42 CEST, end at Mon 2020-02-24 23:41:21 CET. --
févr. 24 23:41:21 gnome-shell[66450]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x4a00007
févr. 24 23:41:21 dbus-daemon[13505]: [session uid=1000 pid=13505] Reloaded configuration
févr. 24 23:41:21 gnome-shell-ext[115834]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
févr. 24 23:41:21 gnome-shell-ext[115834]: The offending signal was destroy on Gjs_ExtensionRow 0x556f7dc858d0.
févr. 24 23:41:21 org.gnome.tweaks.desktop[115834]: == Stack trace for context 0x556f7d2e31a0 ==
févr. 24 23:41:21 gnome-shell-ext[115834]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
févr. 24 23:41:21 org.gnome.tweaks.desktop[115834]: == Stack trace for context 0x556f7d2e31a0 ==
févr. 24 23:41:21 gnome-shell-ext[115834]: The offending signal was destroy on Gjs_ExtensionRow 0x556f7dd19350.
févr. 24 23:41:21 gnome-shell-ext[115834]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
févr. 24 23:41:21 org.gnome.tweaks.desktop[115834]: == Stack trace for context 0x556f7d2e31a0 ==
févr. 24 23:41:21 gnome-shell-ext[115834]: The offending signal was destroy on Gjs_ExtensionRow 0x556f7da50650.
févr. 24 23:41:21 gnome-shell-ext[115834]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
févr. 24 23:41:21 org.gnome.tweaks.desktop[115834]: == Stack trace for context 0x556f7d2e31a0 ==
févr. 24 23:41:21 gnome-shell-ext[115834]: The offending signal was destroy on Gjs_ExtensionRow 0x556f7dcc4c80.
févr. 24 23:41:21 gnome-shell-ext[115834]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
févr. 24 23:41:21 org.gnome.tweaks.desktop[115834]: == Stack trace for context 0x556f7d2e31a0 ==
févr. 24 23:41:21 gnome-shell-ext[115834]: The offending signal was destroy on Gjs_ExtensionRow 0x556f7dcc4380.
févr. 24 23:41:21 gnome-shell-ext[115834]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
févr. 24 23:41:21 org.gnome.tweaks.desktop[115834]: == Stack trace for context 0x556f7d2e31a0 ==
févr. 24 23:41:21 gnome-shell-ext[115834]: The offending signal was destroy on Gjs_ExtensionRow 0x556f7dc852d0.
févr. 24 23:41:21 gnome-shell-ext[115834]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
févr. 24 23:41:21 gnome-shell-ext[115834]: The offending signal was destroy on Gjs_ExtensionRow 0x556f7dc85bd0.
févr. 24 23:41:21 org.gnome.tweaks.desktop[115834]: == Stack trace for context 0x556f7d2e31a0 ==
févr. 24 23:41:21 gnome-shell-ext[115834]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
févr. 24 23:41:21 org.gnome.tweaks.desktop[115834]: == Stack trace for context 0x556f7d2e31a0 ==
févr. 24 23:41:21 gnome-shell-ext[115834]: The offending signal was destroy on Gjs_ExtensionRow 0x556f7dc49930.
févr. 24 23:41:21 gnome-shell-ext[115834]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
févr. 24 23:41:21 org.gnome.tweaks.desktop[115834]: == Stack trace for context 0x556f7d2e31a0 ==
févr. 24 23:41:21 gnome-shell-ext[115834]: The offending signal was destroy on Gjs_ExtensionRow 0x556f7da50950.
févr. 24 23:41:21 gnome-shell-ext[115834]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
févr. 24 23:41:21 org.gnome.tweaks.desktop[115834]: == Stack trace for context 0x556f7d2e31a0 ==
févr. 24 23:41:21 gnome-shell-ext[115834]: The offending signal was destroy on Gjs_ExtensionRow 0x556f7dd19650.
févr. 24 23:41:21 gnome-shell-ext[115834]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
févr. 24 23:41:21 org.gnome.tweaks.desktop[115834]: == Stack trace for context 0x556f7d2e31a0 ==
févr. 24 23:41:21 gnome-shell-ext[115834]: The offending signal was destroy on Gjs_ExtensionRow 0x556f7dcf7c90.
févr. 24 23:41:21 org.gnome.tweaks.desktop[115834]: == Stack trace for context 0x556f7d2e31a0 ==
févr. 24 23:41:21 gnome-shell-ext[115834]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
févr. 24 23:41:21 gnome-shell-ext[115834]: The offending signal was destroy on Gjs_ExtensionRow 0x556f7dc49330.
févr. 24 23:41:21 org.gnome.tweaks.desktop[115834]: == Stack trace for context 0x556f7d2e31a0 ==
févr. 24 23:41:21 gnome-shell-ext[115834]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
févr. 24 23:41:21 gnome-shell-ext[115834]: The offending signal was destroy on Gjs_ExtensionRow 0x556f7dcc4980.
févr. 24 23:41:21 gnome-shell-ext[115834]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
févr. 24 23:41:21 org.gnome.tweaks.desktop[115834]: == Stack trace for context 0x556f7d2e31a0 ==
févr. 24 23:41:21 gnome-shell-ext[115834]: The offending signal was destroy on Gjs_ExtensionRow 0x556f7dc49c30.
févr. 24 23:41:21 gnome-shell-ext[115834]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
févr. 24 23:41:21 org.gnome.tweaks.desktop[115834]: == Stack trace for context 0x556f7d2e31a0 ==
févr. 24 23:41:21 gnome-shell-ext[115834]: The offending signal was destroy on Gjs_ExtensionRow 0x556f7dc49630.
févr. 24 23:41:21 org.gnome.tweaks.desktop[115834]: == Stack trace for context 0x556f7d2e31a0 ==
févr. 24 23:41:21 gnome-shell-ext[115834]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
févr. 24 23:41:21 gnome-shell-ext[115834]: The offending signal was destroy on Gjs_ExtensionRow 0x556f7dcf7f90.
févr. 24 23:41:21 org.gnome.tweaks.desktop[115834]: == Stack trace for context 0x556f7d2e31a0 ==
févr. 24 23:41:21 gnome-shell-ext[115834]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
févr. 24 23:41:21 gnome-shell-ext[115834]: The offending signal was destroy on Gjs_ExtensionRow 0x556f7da50c50.
févr. 24 23:41:21 gnome-shell-ext[115834]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
févr. 24 23:41:21 org.gnome.tweaks.desktop[115834]: == Stack trace for context 0x556f7d2e31a0 ==
févr. 24 23:41:21 gnome-shell-ext[115834]: The offending signal was destroy on Gjs_ExtensionRow 0x556f7da50f50.
févr. 24 23:41:21 org.gnome.tweaks.desktop[115834]: == Stack trace for context 0x556f7d2e31a0 ==
févr. 24 23:41:21 gnome-shell-ext[115834]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
févr. 24 23:41:21 gnome-shell-ext[115834]: The offending signal was destroy on Gjs_ExtensionRow 0x556f7dc855d0.
févr. 24 23:41:21 org.gnome.tweaks.desktop[115834]: == Stack trace for context 0x556f7d2e31a0 ==
févr. 24 23:41:21 gnome-shell-ext[115834]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
févr. 24 23:41:21 gnome-shell-ext[115834]: The offending signal was destroy on Gjs_ExtensionRow 0x556f7dcf7690.
févr. 24 23:41:21 org.gnome.tweaks.desktop[115834]: == Stack trace for context 0x556f7d2e31a0 ==
févr. 24 23:41:21 gnome-shell-ext[115834]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
févr. 24 23:41:21 gnome-shell-ext[115834]: The offending signal was destroy on Gjs_ExtensionRow 0x556f7dc49f30.
févr. 24 23:41:21 org.gnome.tweaks.desktop[115834]: == Stack trace for context 0x556f7d2e31a0 ==
févr. 24 23:41:21 gnome-shell-ext[115834]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
févr. 24 23:41:21 gnome-shell-ext[115834]: The offending signal was destroy on Gjs_ExtensionRow 0x556f7da50350.
févr. 24 23:41:21 gnome-shell-ext[115834]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
févr. 24 23:41:21 gnome-shell-ext[115834]: The offending signal was destroy on Gjs_ExtensionRow 0x556f7dcc4680.
févr. 24 23:41:21 gnome-shell-ext[115834]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
févr. 24 23:41:21 gnome-shell-ext[115834]: The offending signal was destroy on Gjs_ExtensionRow 0x556f7dc85ed0.
févr. 24 23:41:21 gnome-shell-ext[115834]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
févr. 24 23:41:21 gnome-shell-ext[115834]: The offending signal was destroy on Gjs_ExtensionRow 0x556f7dcf7990.
févr. 24 23:41:21 gnome-shell-ext[115834]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
févr. 24 23:41:21 gnome-shell-ext[115834]: The offending signal was destroy on Gjs_ExtensionRow 0x556f7dcf7390.
févr. 24 23:41:21 gnome-shell-ext[115834]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
févr. 24 23:41:21 gnome-shell-ext[115834]: The offending signal was destroy on Gjs_ExtensionRow 0x556f7dcc4f80.
févr. 24 23:41:21 dbus-daemon[13505]: [session uid=1000 pid=13505] Activating via systemd: service name='org.freedesktop.Tracker1' unit='tracker-store.service' requested by ':1.48' (uid=1000 pid=13823 comm="/usr/lib/tracker-miner-fs ")
févr. 24 23:41:21 systemd[582]: Starting Tracker metadata database store and lookup manager...
févr. 24 23:41:21 dbus-daemon[13505]: [session uid=1000 pid=13505] Successfully activated service 'org.freedesktop.Tracker1'
févr. 24 23:41:21 systemd[582]: Started Tracker metadata database store and lookup manager.
févr. 24 23:41:21 dbus-daemon[13505]: [session uid=1000 pid=13505] Activating via systemd: service name='org.freedesktop.Tracker1.Miner.Extract' unit='tracker-extract.service' requested by ':1.48' (uid=1000 pid=13823 comm="/usr/lib/tracker-miner-fs ")
févr. 24 23:41:21 systemd[582]: Starting Tracker metadata extractor...
févr. 24 23:41:21 dbus-daemon[13505]: [session uid=1000 pid=13505] Successfully activated service 'org.freedesktop.Tracker1.Miner.Extract'
févr. 24 23:41:21 systemd[582]: Started Tracker metadata extractor.if you need any info don't hesitate to ask
andyholmes
commented
4 years ago In order to find out why this is happening, or if it's GSConnect's fault, I need some information on how to reproduce it.
The original reporter stated this was related to the SFTP plugin, but I have no logs indicating what might be going wrong with that plugin. Since I can't reproduce this myself, there's just nothing I can do unless someone experiencing the bug can provide some hint as to what the problem is.
uniquePWD
commented
4 years ago I can't recall how I fixed this, but ensure that all other extensions are up to date
knard
commented
4 years ago @andyholmes I don't think the log can show anything because the application seems to work "correctly" except that everything is very slow. I can see that gnome-shell process and gjs processes are taking a lot of cpu but except that nothing else. I think that it can be related to the gnome version. I'm on archlinux and the problem appear few days ago and I have upgraded to a newer version of gnome. I'll try to investigate if I can narrow the issue to something more specific.
@pwd-github all other extensions are up to date
andyholmes
commented
4 years ago The most recent updates for gnome-shell (3.34.4) and gjs (1.58.5) are both pretty minimal, nothing that should affect GSConnect at all.
Since I'm also running the latest versions of both of these, so there's not much else I can do without some hint as to where to look or what triggers this behaviour.
knard
commented
4 years ago I don't think the issue was related to gsconnect. Yesterday evening the mailnag extension was the problem and today everything is fine. So.... I don't know what to think.
ferdnyc
commented
4 years ago Given that both users who were experiencing this issue have reported they're no longer having the same problem, and because nothing ever conclusively pointed to GSConnect as the source of the high CPU load, I'm going to close this. But please feel free to reopen if you have any further updates on this issue, or open a new issue if you experience any other problems.
Describe the bug When using GSConnect 30, CPU usage is up to 100% or there abouts.
A clear and concise description of what the bug is.
Steps To Reproduce:
Expected behavior Previous versions didn't have this issue.
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem. You can drag-and-drop or cut-and-paste images directly into this edit window, to include them in your report.
Support Log
Please generate a support log (Instructions) and paste any messages related to this issue between the two ``` lines below.
System Details (please complete the following information):
GSConnect environment (if applicable):
Additional Notes:
Add any addtional information about the problem or your system.