Arch Linux

Dedal

Member

Registered: 2015-04-18

Posts: 10

Gnome - stack traces in a journal

Has any anyone noticed weird messages and stack traces in a journal log especially after opening/closing nautiluis or any gtk application? This is what I get on gnome DE with nvidia:

gnome-shell[765]: Object Clutter.Clone (0x563e256dce60), has been already finalized. Impossible to get any property from it.
org.gnome.Shell.desktop[765]: == Stack trace for context 0x563e1fde5170 ==
org.gnome.Shell.desktop[765]: #0 0x7ffd9cc35100 I   resource:///org/gnome/shell/ui/tweener.js:73 (0x7f531c4ddef0 @ 9)
org.gnome.Shell.desktop[765]: #1 0x7ffd9cc351a0 b   resource:///org/gnome/shell/ui/tweener.js:105 (0x7f531c4df230 @ 36)
org.gnome.Shell.desktop[765]: #2 0x7ffd9cc35240 b   resource:///org/gnome/shell/ui/tweener.js:92 (0x7f531c4df098 @ 52)
...
Object Meta.WindowActor (0x563e27eb47b0), has been already finalized. Impossible to get any property from it.
...
Object .Gjs_DashItemContainer (0x563e25a58c10), has been already finalized. Impossible to get any property from it.
...

I disabled all extensions but it didnt really help, any clues?

bulletmark

Member

From: Brisbane, Australia

Registered: 2013-10-22

Posts: 653

Re: Gnome - stack traces in a journal

Yes, it is not related to extensions. Those log messages appear to have started since these updates:

2018-01-21 07:07 libtasn1    4.12-2 -> 4.13-1
2018-01-21 07:07 gnutls      3.5.16-1 -> 3.5.17-1
2018-01-21 07:07 gjs         1:1.50.2-1 -> 1:1.50.3-1
2018-01-21 07:07 mutter      3.26.2+31+gbf91e2b4c-1 -> 3.26.2+43+g77dd1bf63-1
2018-01-21 07:07 gnome-shell 3.26.2+9+ga3736d3a3-1 -> 3.26.2+14+g64c857e3f-1
2018-01-21 07:07 libraw      0.18.6-1 -> 0.18.7-1

PS: Happens on both my intel graphics PC and laptop since those updates.

Last edited by bulletmark (2018-01-24 21:47:59)

Toolybird

Member

Registered: 2017-09-30

Posts: 72

Re: Gnome - stack traces in a journal

Yes, it's due to the gjs package update.

The messages (while scary) appear to be warnings only as everything continues to work. But still very annoying to have the journal spammed liked this.

Debian is also affected so this is likely an upstream issue:

https://bugs.debian.org/cgi-bin/bugrepo … bug=887082

I love being on the bleeding edge with Arch but sometimes wonder if the devs are pushing the envelope too hard.

Leeo97one

Member

From: France

Registered: 2017-07-29

Posts: 8

Re: Gnome - stack traces in a journal

Good to know I'm not the only one to see that x)
I hope for a quick fix.

Last edited by Leeo97one (2018-01-26 17:55:52)

Inixi

Member

Registered: 2016-10-15

Posts: 54

Re: Gnome - stack traces in a journal

Hello,
Same here. I couldn't figure out what package causes that...
Do these stack traces have to do with gnome-shell randomly crashes when trying to:
- get computer to sleep
- attempting to lock the session
- attempting to sign in to already started session
?

---

2020 ASUS Zephyrus G14

phw

Member

Registered: 2013-05-27

Posts: 318

Re: Gnome - stack traces in a journal

This seems to be related to https://bugzilla.gnome.org/show_bug.cgi?id=788931 and the fixes for it in https://gitlab.gnome.org/GNOME/gjs/merg … s/22/diffs

Due to some changes gnome shell used to crash recently when extensions were trying to access already destroyed objects. This change now makes sure gnome shell does not crash anymore but logs out invalid access so the affected code can be identified. Looks like this logs different kind of invalid access, not only the ones that lead to hard crashes.

Let's hope the developers will fix up the afftected code and thus remove the warnings

UPDATE: There are already some pull requests dealing with these issues: https://gitlab.gnome.org/GNOME/gnome-sh … requests/4 , https://gitlab.gnome.org/GNOME/gnome-sh … equests/11

Last edited by phw (2018-01-29 11:55:51)

Vlad3

Member

Registered: 2018-02-02

Posts: 9

Re: Gnome - stack traces in a journal

Related:
- https://bbs.archlinux.org/viewtopic.php?id=234127
- https://bugs.archlinux.org/task/57222

Toolybird

Member

Registered: 2017-09-30

Posts: 72

Re: Gnome - stack traces in a journal

Well, I was hoping Gnome 3.28 would fix this incredibly annoying issue.. apparently not.

Still getting MASSIVE amounts of debug spew in the journal. Everytime I switch workspaces using keyboard shortcuts, another bazillion lines get added to the journal.

Cannot understand why more folks are not screaming about this. Upstream are aware but apparently do not care.

bulletmark

Member

From: Brisbane, Australia

Registered: 2013-10-22

Posts: 653

Re: Gnome - stack traces in a journal

Yep, it was one of the first things I checked after booting with GNOME 3.28 and was saddened to see it still there also

Last edited by bulletmark (2018-03-26 03:42:54)

Toolybird

Member

Registered: 2017-09-30

Posts: 72

Re: Gnome - stack traces in a journal

This thing is so aggravating it forced me to learn the ABS and build my own gjs package with the offending lines patched out.

At least some good has come out of it

citecite

Member

Registered: 2018-03-29

Posts: 8

Re: Gnome - stack traces in a journal

This thing is so aggravating it forced me to learn the ABS and build my own gjs package with the offending lines patched out.

Would you be willing to post a diff?

Toolybird

Member

Registered: 2017-09-30

Posts: 72

Re: Gnome - stack traces in a journal

Would you be willing to post a diff?

Sure thing. Here's the minimal patch that reduces about 90% of the log spam in my case:

https://ptpb.pw/-6tX

mxfm

Member

Registered: 2015-10-23

Posts: 163

Re: Gnome - stack traces in a journal

Journal spamming was one of the reasons I abandoned Gnome completely and deleted all packages in January. Interesting to hear that Gnome devs were unable to fix such trivial issue for three months.

EDIT:

My solution to the discussed problem (as to many other Gnome problems) was pacman -Rns gnome-shell gnome-desktop and to install other DE.

Last edited by mxfm (2018-03-31 05:27:42)

jmmec

Member

Registered: 2016-12-23

Posts: 7

Re: Gnome - stack traces in a journal

My solution to the discussed problem (as to many other Gnome problems) was pacman -Rns gnome-shell gnome-desktop and to install other DE.

Thanks, am going to do the same.

storrgie

Member

Registered: 2016-06-03

Posts: 19

Re: Gnome - stack traces in a journal

It is quite disappointing.

For those who want a less drastic solution, the major portion of the logspam is coming from a tweener.js. Turn off animations and this will abate somewhat.

Toolybird

Member

Registered: 2017-09-30

Posts: 72

Re: Gnome - stack traces in a journal

Further research turned up a Fedora patch which looks a lot saner to me. It hides the log spam behind a DEBUG env var which is how it should have been done in the first place.

It still applies to latest gjs, but with offset.

Am running it now. Solves the problem completely. I think Arch should consider applying this.

https://src.fedoraproject.org/rpms/gjs/ … cals.patch

johnnynyquist

Member

Registered: 2016-01-25

Posts: 27

Re: Gnome - stack traces in a journal

It is quite disappointing.

For those who want a less drastic solution, the major portion of the logspam is coming from a tweener.js. Turn off animations and this will abate somewhat.

Can you post a howto for n00bz? I have 'animations' switched off at the top of gnome-tweaks and I'm still getting tweener messages every time I twiddle my pinky finger.

bulletmark

Member

From: Brisbane, Australia

Registered: 2013-10-22

Posts: 653

Re: Gnome - stack traces in a journal

Yep, it was one of the first things I checked after booting with GNOME 3.28 and was saddened to see it still there also

GNOME updated to 3.28.1 yesterday and I am very sad to see these stack traces still in my journal. How the heck have the GNOME devs not addressed this?!

johnnynyquist

Member

Registered: 2016-01-25

Posts: 27

Re: Gnome - stack traces in a journal

Yep, it was one of the first things I checked after booting with GNOME 3.28 and was saddened to see it still there also

GNOME updated to 3.28.1 yesterday and I am very sad to see these stack traces still in my journal. How the heck have the GNOME devs not addressed this?!

Part of the problem may be that it is not reported.  The bug linked above in phw's post (https://bugzilla.gnome.org/show_bug.cgi?id=788931) is both fixed and not related.  The error originally posted has the phrase "has been already finalized". When I do a search on Gnome bugzilla for "BoxLayout finalized", I get zilch. When I search for "GenericContainer finalized" I get two bugs that seem unrelated and are both status NEW. Could it be the bug hasn't been filed? Can anyone find this on Gnome's bugzilla?

If not, I nominate @Toolybird to file the bug since they has a fix already.

Leeo97one

Member

From: France

Registered: 2017-07-29

Posts: 8

Re: Gnome - stack traces in a journal

Mmmh I see a report here: https://gitlab.gnome.org/GNOME/gnome-shell/issues/1

johnnynyquist

Member

Registered: 2016-01-25

Posts: 27

Re: Gnome - stack traces in a journal

Mmmh I see a report here: https://gitlab.gnome.org/GNOME/gnome-shell/issues/1

Indeed... https://gitlab.gnome.org/GNOME/gnome-sh … requests/4 looks like it's in the pipeline.