You are not logged in.
Pages: 1
When launching "journalctl -f" I saw that every second or so, a new entry appear in the log, it's something like:
gnome-shell[7659]: Object St.Button (0x556ee3a73dd0), has been already deallocated — impossible to get any property from it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs.
gnome-shell[7659]: == Stack trace for context 0x556edfc723f0 ==
gnome-shell[7659]: #0 556ee3ec6d40 i resource:///org/gnome/shell/ui/workspace.js:695 (7f740326db80 @ 15)
gnome-shell[7659]: #1 556ee3ec6c80 i self-hosted:975 (7f740332cb80 @ 392)
always the same message and stack trace. Do you know what's going wrong?
I was wondering if there was a way to silence this message otherwise. I've found a request for this functionality (https://github.com/systemd/systemd/issues/4089) but I couldn't whether it's been implemented and if so, how?
At the moment I have set stringent limits on logging in order to save space, but of course the ideal would be to solve the issue creating these messages.
Edit: I don't have any extension :
$ gsettings get org.gnome.shell enabled-extensions
@as []
Update:
The log didn't reoccur. I have tried to trigger it by launching all the programs and functionalities I was using when this was happening, one by one, but nothing happened. I don't know where it came from.
I'll keep an eye on it and see if this reoccurs.
Last edited by charlie (2019-10-10 07:37:08)
Offline
I'm seeing exactly the same here, and saw the same thing a few days ago. My log message is identical to OP and is repeating approximately twice a second. I will try to reproduce... currently wondering if it is caused by a suspend/resume cycle because it certainly wasn't doing it yesterday.
Offline
I'm glad to see that I'm not alone. It happened again today. I had an issue with the sound: no sound, couldn't figure out what was happening and this constant logging didn't help. Rebooted the computer in order to stop the messages, sound was back. Didn't investigate further. Right now, things seem to work fine, no logs.
Also, I had suspended and resumed the computer before I realized that the logs were filling again with those messages. So maybe you're right, it could be related to suspend/resume.
EDIT: just checked today logs. I suspended at 10:40 then resumed at 12:20, the messages appeared at 12:21, 20 seconds after the last resume-related message :
oct. 17 12:20:48 systemd[1]: NetworkManager-dispatcher.service: Succeeded.
oct. 17 12:20:48 audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res>
oct. 17 12:20:48 kernel: audit: type=1131 audit(1571311248.640:151): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hos>
oct. 17 12:20:56 wpa_supplicant[481]: wlp3s0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-56 noise=9999 txrate=400000
oct. 17 12:21:13 gnome-shell[960]: Object St.Button (0x55a6f23888a0), has been already deallocated — impossible to get any property from it. This might be caused by the object having been destroyed>
oct. 17 12:21:13 gnome-shell[960]: == Stack trace for context 0x55a6eba09530 ==
oct. 17 12:21:13 gnome-shell[960]: #0 55a6f098b7b0 i resource:///org/gnome/shell/ui/workspace.js:695 (7f5e0f66eee0 @ 15)
oct. 17 12:21:13 gnome-shell[960]: #1 7ffd438c9f10 b self-hosted:975 (7f5e1802bee0 @ 392)
oct. 17 12:21:14 gnome-shell[960]: Object St.Button (0x55a6f23888a0), has been already deallocated — impossible to get any property from it. This might be caused by the object having been destroyed>
oct. 17 12:21:14 gnome-shell[960]: == Stack trace for context 0x55a6eba09530 ==
oct. 17 12:21:14 gnome-shell[960]: #0 55a6f098b7b0 i resource:///org/gnome/shell/ui/workspace.js:695 (7f5e0f66eee0 @ 15)
oct. 17 12:21:14 gnome-shell[960]: #1 7ffd438c9f10 b self-hosted:975 (7f5e1802bee0 @ 392)
oct. 17 12:21:15 gnome-shell[960]: Object St.Button (0x55a6f23888a0), has been already deallocated — impossible to get any property from it. This might be caused by the object having been destroyed>
oct. 17 12:21:15 gnome-shell[960]: == Stack trace for context 0x55a6eba09530 ==
oct. 17 12:21:15 gnome-shell[960]: #0 55a6f098b7b0 i resource:///org/gnome/shell/ui/workspace.js:695 (7f5e0f66eee0 @ 15)
oct. 17 12:21:15 gnome-shell[960]: #1 7ffd438c9f10 b self-hosted:975 (7f5e1802bee0 @ 392)Also I don't know if this is related but during the resume process there is this message:
oct. 17 12:20:27 gdm[460]: GLib: Source ID 87 was not found when attempting to remove itAnd I don't know if this is relevant but when shutting down:
oct. 17 15:01:33 systemd-logind[453]: System is powering down.
...
oct. 17 15:01:34 systemd[1]: Stopped Load/Save Random Seed.
oct. 17 15:01:34 audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-random-seed comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=succe>
oct. 17 15:01:34 gnome-shell[960]: Window manager warning: META_CURRENT_TIME used to choose focus window; focus window may not be correct.
oct. 17 15:01:34 gnome-shell[960]: JS ERROR: TypeError: actor.get_meta_window(...) is null
_destroyWindowDone@resource:///org/gnome/shell/ui/windowManager.js:1804:26
onStopped@resource:///org/gnome/shell/ui/windowManager.js:1774:34
_makeEaseCallback/<@resource:///org/gnome/shell/ui/environment.js:72:13
_easeActor/<@resource:///org/gnome/shell/ui/environment.js:128:56
oct. 17 15:01:34 gnome-shell[960]: JS ERROR: TypeError: actor.get_meta_window(...) is null
_destroyWindowDone@resource:///org/gnome/shell/ui/windowManager.js:1804:26
onStopped@resource:///org/gnome/shell/ui/windowManager.js:1774:34
_makeEaseCallback/<@resource:///org/gnome/shell/ui/environment.js:72:13
_easeActor/<@resource:///org/gnome/shell/ui/environment.js:128:56
oct. 17 15:01:34 gnome-shell[960]: JS ERROR: TypeError: actor.get_meta_window(...) is null
_destroyWindowDone@resource:///org/gnome/shell/ui/windowManager.js:1804:26
onStopped@resource:///org/gnome/shell/ui/windowManager.js:1774:34
_makeEaseCallback/<@resource:///org/gnome/shell/ui/environment.js:72:13
_easeActor/<@resource:///org/gnome/shell/ui/environment.js:128:56
oct. 17 15:01:34 mkinitcpio[6804]: ==> Starting build: none
oct. 17 15:01:34 gnome-shell[960]: 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 sig>
oct. 17 15:01:34 gnome-shell[960]: == Stack trace for context 0x55a6eba09530 ==
oct. 17 15:01:34 gnome-shell[960]: The offending signal was destroy on Gjs_BaseIcon 0x55a6f395d5e0.
oct. 17 15:01:34 gnome-shell[960]: 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 sig>
oct. 17 15:01:34 gnome-shell[960]: == Stack trace for context 0x55a6eba09530 ==
oct. 17 15:01:34 gnome-shell[960]: The offending signal was destroy on Gjs_BaseIcon 0x55a6f3954bc0.
oct. 17 15:01:34 gnome-shell[960]: 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 sig>
oct. 17 15:01:34 gnome-shell[960]: The offending signal was destroy on Gjs_BaseIcon 0x55a6f394c510.
oct. 17 15:01:34 gnome-shell[960]: == Stack trace for context 0x55a6eba09530 ==
oct. 17 15:01:34 gnome-shell[960]: 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 sig>
oct. 17 15:01:34 gnome-shell[960]: The offending signal was destroy on Gjs_BaseIcon 0x55a6f3944d10.
oct. 17 15:01:34 gnome-shell[960]: == Stack trace for context 0x55a6eba09530 ==
...
oct. 17 15:01:34 gnome-shell[960]: 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 sig>
oct. 17 15:01:34 gnome-shell[960]: The offending signal was destroy on Gjs_BaseIcon 0x55a6edf07110.
oct. 17 15:01:34 gnome-shell[960]: == Stack trace for context 0x55a6eba09530 ==
oct. 17 15:01:34 gnome-shell[960]: 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 sig>
oct. 17 15:01:34 gnome-shell[960]: The offending signal was destroy on Gjs_BaseIcon 0x55a6edf18660.
oct. 17 15:01:34 gnome-shell[960]: == Stack trace for context 0x55a6eba09530 ==
oct. 17 15:01:34 gnome-shell[960]: 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 sig>
oct. 17 15:01:34 gnome-shell[960]: The offending signal was destroy on Gjs_BaseIcon 0x55a6edeb8030.
oct. 17 15:01:34 gnome-shell[960]: == Stack trace for context 0x55a6eba09530 ==
oct. 17 15:01:34 systemd[889]: gsd-keyboard.service: Succeeded.
oct. 17 15:01:34 systemd[889]: Stopped GNOME Keyboard handling.
oct. 17 15:01:34 systemd[889]: gsd-wacom.service: Succeeded.
oct. 17 15:01:34 systemd[889]: Stopped GNOME Wacom handling.
oct. 17 15:01:34 systemd[889]: gsd-media-keys.service: Succeeded.
oct. 17 15:01:34 systemd[889]: Stopped GNOME Media keys handling.
...
oct. 17 15:01:35 systemd[1]: Shutting down.
oct. 17 15:01:35 kernel: printk: systemd-shutdow: 43 output lines suppressed due to ratelimiting
oct. 17 15:01:35 systemd-shutdown[1]: Syncing filesystems and block devices.
oct. 17 15:01:36 systemd-shutdown[1]: Sending SIGTERM to remaining processes...
oct. 17 15:01:36 systemd-journald[279]: Journal stoppedLast edited by charlie (2019-10-17 21:07:57)
Offline
When launching "journalctl -f" I saw that every second or so, a new entry appear in the log, it's something like:
gnome-shell[7659]: Object St.Button (0x556ee3a73dd0), has been already deallocated — impossible to get any property from it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs.
gnome-shell[7659]: == Stack trace for context 0x556edfc723f0 ==
gnome-shell[7659]: #0 556ee3ec6d40 i resource:///org/gnome/shell/ui/workspace.js:695 (7f740326db80 @ 15)
gnome-shell[7659]: #1 556ee3ec6c80 i self-hosted:975 (7f740332cb80 @ 392)always the same message and stack trace. Do you know what's going wrong?
I'll keep an eye on it and see if this reoccurs.
Same here on my Lenovo x230T (yes with a touch, maybe relevant). On my office machine (Tuxedo) these log entries do not appear, both daily updated archlinux machines.
Disabling/Removing all non-sytem-extension did not help.
Offline
https://gitlab.gnome.org/GNOME/gnome-shell/issues/1704 should be fixed by mutter 3.34.1+26+gc0037305e-1 in testing.
Offline
Pages: 1