FS#58211 - [gnome-shell] gjs spams journal with stack traces

Attached to Project: Arch Linux
Opened by Patrick Lühne (patrick.luehne) - Thursday, 12 April 2018, 17:09 GMT
Last edited by Jan de Groot (JGC) - Thursday, 16 January 2020, 10:02 GMT
Task Type Bug Report
Category Upstream Bugs
Status Closed
Assigned To Jan de Groot (JGC)
Jan Alexander Steffens (heftig)
Architecture x86_64
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 2
Private No

Details

# Description

For some time now, gjs continuously spams my journal with stack traces, most of them concerning tweener.js. Find attached one instance of these stack traces.

These stack traces are logged every time I switch windows with Alt+Tab, which amounts to a lot of unwanted output messages.

I’m using Gnome Shell without any extensions on Wayland.

Note that others have reported the same issue before through other channels, such as the [Arch forum](https://bbs.archlinux.org/viewtopic.php?id=233858).

That specific thread also discusses a patch to gjs from the Fedora folks. I wonder whether it would make sense to apply this patch in the Arch gjs package as long as this hasn’t been fixed upstream.

# Additional Information

* gnome-shell 3.28.0-1 (all packages up-to-date as of writing this report)
* gjs stack trace attached

# Steps to Reproduce

* journalctl -f
* switch windows with Alt+Tab
* inspect recorded journal additions
   log (3.2 KiB)
This task depends upon

Closed by  Jan de Groot (JGC)
Thursday, 16 January 2020, 10:02 GMT
Reason for closing:  Fixed
Additional comments about closing:  Upstream reports are closed, assuming fixed.
Comment by Jan de Groot (JGC) - Thursday, 12 April 2018, 17:49 GMT
gnome-shell needs a fix, not gjs.
Comment by Patrick Lühne (patrick.luehne) - Thursday, 12 April 2018, 18:05 GMT
@Jan de Groot: That’s a fair point. Let’s close this ticket, and sorry for the spam.
Comment by Patrick Lühne (patrick.luehne) - Friday, 13 April 2018, 14:18 GMT
@Doug Newgard: Thanks for moving this to gnome-shell instead of closing it :).

Apparently, this issue is already being tracked upstream as issues #1 and #11 [1, 2]. Not sure whether it would make sense to already apply the proposed changes in merge request #4 [3] as a patch to this package …

[1] https://gitlab.gnome.org/GNOME/gnome-shell/issues/1
[2] https://gitlab.gnome.org/GNOME/gnome-shell/issues/11
[3] https://gitlab.gnome.org/GNOME/gnome-shell/merge_requests/4/diffs
Comment by mattia (nTia89) - Tuesday, 05 November 2019, 20:53 GMT
I can no more repoduce the issue and upstream bugs have been closed.
Can we close this issue?

Loading...