Red Hat Bugzilla – Bug 1546059
Stack traces in journal
Last modified: 2018-05-17 10:43:23 EDT
+++ This bug was initially created as a clone of Bug #1545659 +++
Description of problem:
Every time I open new window or close a window, there is a new stack trace of org.gnome.Shell.desktop in journal log and /var/log/messages.
As this is a common task, these msgs spams system logs.
org.gnome.Shell.desktop: == Stack trace for context 0xb25170 ==
org.gnome.Shell.desktop: #0 0xf5ec78 i resource:///org/gnome/shell/ui/tweener.js:73 (0x7f611c1ddef0 @ 9)
org.gnome.Shell.desktop: #1 0xf5ebf8 i resource:///org/gnome/shell/ui/tweener.js:105 (0x7f611c1df230 @ 36)
org.gnome.Shell.desktop: #2 0xf5eb70 i resource:///org/gnome/shell/ui/tweener.js:92 (0x7f611c1df098 @ 52)
org.gnome.Shell.desktop: #3 0x7ffcac399610 b resource:///org/gnome/gjs/modules/tweener/tweener.js:203 (0x7f611c1e9cd0 @ 54)
org.gnome.Shell.desktop: #4 0x7ffcac399760 b resource:///org/gnome/gjs/modules/tweener/tweener.js:332 (0x7f611c1e9d58 @ 1626)
org.gnome.Shell.desktop: #5 0x7ffcac399810 b resource:///org/gnome/gjs/modules/tweener/tweener.js:345 (0x7f611c1e9de0 @ 100)
org.gnome.Shell.desktop: #6 0x7ffcac3998a0 b resource:///org/gnome/gjs/modules/tweener/tweener.js:360 (0x7f611c1e9e68 @ 10)
org.gnome.Shell.desktop: #7 0x7ffcac399990 b resource:///org/gnome/gjs/modules/signals.js:126 (0x7f611c1e2b38 @ 386)
org.gnome.Shell.desktop: #8 0x7ffcac399a40 b resource:///org/gnome/shell/ui/tweener.js:208 (0x7f611c1df808 @ 159)
org.gnome.Shell.desktop: #9 0x7ffcac399aa0 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f611c1c2bc0 @ 71)
org.gnome.Shell.desktop: #10 0x7ffcac399aa0 I resource:///org/gnome/shell/ui/tweener.js:183 (0x7f611c1df780 @ 20)
org.gnome.Shell.desktop: #11 0x7ffcac399b70 b self-hosted:917 (0x7f611c1ee5e8 @ 394)
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Open firefox
2. Open new window Ctrl-n
3. Close window
4. journalctl -b -a
Multiple Stack traces of gnome-shell
No stack traces
--- Additional comment from Jiri Koten on 2018-02-15 07:57:46 EST ---
And also when switching between windows.
gnome-shell: Object Shell.GenericContainer (0x536f450), has been already finalized. Impossible to set any property to it.
org.gnome.Shell.desktop: #9 0x7ffe80ee4110 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7fddb05c2bc0 @ 71)
org.gnome.Shell.desktop: #10 0x7ffe80ee4110 I resource:///org/gnome/shell/ui/tweener.js:183 (0x7fddb05df780 @ 20)
org.gnome.Shell.desktop: #11 0x7ffe80ee41e0 b self-hosted:917 (0x7fddb05ee5e8 @ 394)
--- Additional comment from Jiri Koten on 2018-02-15 08:55:51 EST ---
It's caused by the gjs update to 1.50.4.
I'm not able to reproduce with gjs-1.50.2-3.el7.
Let's fix this for 7.5 by patching out the traces from gjs and downgrading the g_criticals to g_debug, which still enables app writers to see the errors, but doesn't spam the system journal.
Created attachment 1397088 [details]
Avoid emitting critical warnings for finalized objects
Here's a patch to the package file that does this -- attaching it here for reference. halfline was talking about keeping the gjs_dumpstack() calls as well, but doing it conditionally only when debugging is enabled, and if it works we'll probably go with that instead.
Created attachment 1397147 [details]
object: only print stacktraces when debugging enabled
We have a bunch of corruption right now spamming the
This commit gets rid of the spam unless G_MESSAGES_DEBUG
Provided blocker "+" for tpelka
I can confirm that stack traces for critical warnings are only printed when G_MESSAGES_DEBUG is set.
This also happens in Fedora 27. Should I open a new bug or can the description be widened to be not RHEL specific?
$ rpm -q gjs gnome-shell
Christian, it's expected in Fedora at the moment. The best thing you can do is file the traces you see upstream here:
so they can be fixed one by one !
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.