Debian Sid: gnome-shell Stack trace und executable stack
Verfasst: 16.06.2020 09:47:59
Mein Debian Sid verhält sich zur Zeit etwas komisch. Wenn ich mich aus dem Terminal als root abgemeldet habe, dann bin ich trotzdem noch angemeldet gewesen, erst nach dem zweiten "exit" bin ich abgemeldet. Da tritt aber nicht immer so auf.
Außerdem flutet irgendetwas das journal mit stack trace. Ich vermute es könnte mit der Erweiterung Dash-to-Dock zu tun haben. Seitdem ich gestern Abend die Erweiterungen komplett deaktiviert habe tritt das nicht mehr auf. Dafür erscheint nun:
Kann mir jemand erklären was es damit auf sich hat:
Code: Alles auswählen
root@user:~# nano /etc/default/grub
root@user:~# exit
Abgemeldet
root@user:~#
Code: Alles auswählen
Jun 16 08:39:47 user gnome-shell[862]: meta_window_set_stack_position_no_sync: assertion 'window->stack_position >= 0' failed
Code: Alles auswählen
Jun 09 11:36:32 user gnome-shell[853]: 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.
Jun 09 11:36:32 user gnome-shell[853]: == Stack trace for context 0x5607d83a6490 ==
Jun 09 11:36:32 user gnome-shell[853]: == Stack trace for context 0x5607d83a6490 ==
Jun 09 11:36:32 user gnome-shell[853]: == Stack trace for context 0x5607d83a6490 ==
Jun 09 11:36:32 user gnome-shell[853]: == Stack trace for context 0x5607d83a6490 ==
Jun 09 11:36:32 user gnome-shell[853]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x5607daea3120.
Jun 09 11:36:32 user gnome-shell[853]: == Stack trace for context 0x5607d83a6490 ==
Jun 09 11:36:32 user gnome-shell[853]: == Stack trace for context 0x5607d83a6490 ==
Jun 09 11:36:32 user gnome-shell[853]: == Stack trace for context 0x5607d83a6490 ==
Jun 09 11:36:32 user gnome-shell[853]: == Stack trace for context 0x5607d83a6490 ==
Jun 09 11:36:32 user gnome-shell[853]: == Stack trace for context 0x5607d83a6490 ==
Jun 09 11:36:32 user gnome-shell[853]: 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.
Jun 09 11:36:32 user gnome-shell[853]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x5607d96ae790.
Jun 09 11:36:32 user gnome-shell[853]: 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
Code: Alles auswählen
kern :warn : [ 11.115866] process '/usr/bin/fstype' started with executable stack
