[Bug 1882410] Re: toggling down object GInotifyFileMonitor that's already queued to toggle up ... GNOME Shell crashed with signal 5
** Changed in: gjs Status: Unknown => Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gjs in Ubuntu. https://bugs.launchpad.net/bugs/1882410 Title: toggling down object GInotifyFileMonitor that's already queued to toggle up ... GNOME Shell crashed with signal 5 To manage notifications about this bug go to: https://bugs.launchpad.net/gjs/+bug/1882410/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1882410] Re: toggling down object GInotifyFileMonitor that's already queued to toggle up ... GNOME Shell crashed with signal 5
The Hirsute Hippo has reached End of Life, so this bug will not be fixed for that release. ** Changed in: gjs (Ubuntu Hirsute) Status: Fix Committed => Won't Fix -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gjs in Ubuntu. https://bugs.launchpad.net/bugs/1882410 Title: toggling down object GInotifyFileMonitor that's already queued to toggle up ... GNOME Shell crashed with signal 5 To manage notifications about this bug go to: https://bugs.launchpad.net/gjs/+bug/1882410/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1882410] Re: toggling down object GInotifyFileMonitor that's already queued to toggle up ... GNOME Shell crashed with signal 5
Hello themusicgod1, or anyone else affected, Accepted gjs into hirsute-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/gjs/1.68.1-1~ubuntu0.21.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- hirsute to verification-done-hirsute. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-hirsute. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: gjs (Ubuntu Hirsute) Status: New => Fix Committed ** Tags added: verification-needed verification-needed-hirsute -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gjs in Ubuntu. https://bugs.launchpad.net/bugs/1882410 Title: toggling down object GInotifyFileMonitor that's already queued to toggle up ... GNOME Shell crashed with signal 5 To manage notifications about this bug go to: https://bugs.launchpad.net/gjs/+bug/1882410/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1882410] Re: toggling down object GInotifyFileMonitor that's already queued to toggle up ... GNOME Shell crashed with signal 5
** Description changed:
+ [ Impact ]
+
+ Gnome shell crashes when unexpected references happens on other threads
+
+ [ Test case ]
+
+ Createa file called modify.py:
+
+ #!/usr/bin/env python3
+
+ import time
+ import random
+
+ while True:
+ time.sleep(0.001)
+ with open('/tmp/testfile', 'w') as f:
+ f.write(str(random.random()))
+
+
+ Create a file called crash-me.js:
+
+ #!/usr/bin/gjs
+
+ const {GLib, Gio} = imports.gi;
+ const watchFile = Gio.file_new_for_path('/tmp/testfile');
+ const fileMonitor = watchFile.monitor(Gio.FileMonitorFlags.NONE, null);
+ fileMonitor.connect('changed', () => {});
+
+ GLib.MainLoop.new(null, false).run();
+
+
+ Open two terminals and run (in each):
+ $ python3 modify.py
+ $ gjs crash-me.js
+
+ gjs should run for some minutes without crashing.
+
+ [ Regression potential ]
+
+ gjs may use memory or not free correctly created objects
+
+
+ ---
+
https://errors.ubuntu.com/problem/a6a50b0ae57f939286a1782a5fc9c45a296d2215
---
A couple of times a day, I'm noticing all of the window dressing
suddenly disappear from all of my open applications, then a second or
two later returning. Opening up /var/log/syslog I see:
Jun 6 20:45:53 eva gnome-shell[335243]: Window manager warning: Invalid
WM_TRANSIENT_FOR window 0x4a00015 specified for 0x4a00518.
Jun 6 20:46:40 eva gnome-shell[335243]: Window manager warning: Invalid
WM_TRANSIENT_FOR window 0x4a00015 specified for 0x4a0051f.
Jun 6 20:47:40 eva gnome-shell[335243]: toggling down object
GInotifyFileMonitor that's already queued to toggle down
Jun 6 20:47:40 eva gnome-shell[335243]: GNOME Shell crashed with signal 5
Jun 6 20:47:40 eva gnome-shell[335243]: == Stack trace for context
0x557e3a0446a0 ==
Jun 6 20:47:40 eva systemd[25554]: gnome-shell-x11.service: Main process
exited, code=dumped, status=5/TRAP
Jun 6 20:47:40 eva systemd[25554]: gnome-shell-x11.service: Failed with
result 'core-dump'.
Jun 6 20:47:40 eva systemd[25554]: gnome-shell-x11.service: Scheduled
restart job, restart counter is at 3.
Jun 6 20:47:40 eva systemd[25554]: Stopped target GNOME X11 Session
(session: ubuntu).
Jun 6 20:47:40 eva systemd[25554]: Stopping GNOME X11 Session (session:
ubuntu).
Jun 6 20:47:40 eva systemd[25554]: Stopped target GNOME X11 Session.
Jun 6 20:47:40 eva systemd[25554]: Stopping GNOME X11 Session.
Jun 6 20:47:40 eva systemd[25554]: Stopped target GNOME Shell on X11.
Jun 6 20:47:40 eva systemd[25554]: Stopping GNOME Shell on X11.
Jun 6 20:47:40 eva systemd[25554]: Stopped GNOME Shell on X11.
Jun 6 20:47:40 eva systemd[25554]: Starting GNOME Shell on X11...
Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): EDID
vendor "ACI", prod id 8434
Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0):
Using hsync ranges from config file
Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0):
Using vrefresh ranges from config file
Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0):
Printing DDC gathered Modelines:
Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0):
Modeline "1600x900"x0.0 108.00 1600 1624 1704 1800 900 901 904 1000 +hsync
+vsync (60.0 kHz eP)
Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0):
Modeline "800x600"x0.0 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync
(37.9 kHz e)
Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0):
Modeline "800x600"x0.0 36.00 800 824 896 1024 600 601 603 625 +hsync +vsync
(35.2 kHz e)
Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0):
Modeline "640x480"x0.0 31.50 640 656 720 840 480 481 484 500 -hsync -vsync
(37.5 kHz e)
Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0):
Modeline "640x480"x0.0 31.50 640 664 704 832 480 489 492 520 -hsync -vsync
(37.9 kHz e)
Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0):
Modeline "640x480"x0.0 30.24 640 704 768 864 480 483 486 525 -hsync -vsync
(35.0 kHz e)
Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0):
Modeline "640x480"x0.0 25.18 640 656 752 800 480 490 492 525 -hsync -vsync
(31.5 kHz e)
Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0):
Modeline "720x400"x0.0 28.32 720 738 846 900 400 412 414 449 -hsync +vsync
(31.5 kHz e)
Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0):
Modeline "1024x768"x0.0 78.75 1024 1040 1136 1312 768 769 772 800 +hsync
+vsync (60.0 kHz e)
Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0):
Modeline "1024x768"x0.0 75.00 1024 1048 1184 1328 768 771 777 806 -hsync
-vsync (56.5 kHz e)
Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0):
Modeline "1024x768"x0.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync
-vsync
[Bug 1882410] Re: toggling down object GInotifyFileMonitor that's already queued to toggle up ... GNOME Shell crashed with signal 5
This bug was fixed in the package gjs - 1.68.0-2 --- gjs (1.68.0-2) experimental; urgency=medium * debian/patches: Cherry-pick upstream memory fixes -- Marco Trevisan (Treviño) Wed, 05 May 2021 05:53:50 +0200 ** Changed in: gjs (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gjs in Ubuntu. https://bugs.launchpad.net/bugs/1882410 Title: toggling down object GInotifyFileMonitor that's already queued to toggle up ... GNOME Shell crashed with signal 5 To manage notifications about this bug go to: https://bugs.launchpad.net/gjs/+bug/1882410/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1882410] Re: toggling down object GInotifyFileMonitor that's already queued to toggle up ... GNOME Shell crashed with signal 5
** Changed in: gjs (Ubuntu) Status: Confirmed => Fix Committed ** Changed in: gjs (Ubuntu) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) ** Changed in: gjs (Ubuntu) Importance: Undecided => Medium ** No longer affects: gnome-shell (Ubuntu) ** Tags added: fixed-in-1.68.1 fixed-upstream -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1882410 Title: toggling down object GInotifyFileMonitor that's already queued to toggle up ... GNOME Shell crashed with signal 5 To manage notifications about this bug go to: https://bugs.launchpad.net/gjs/+bug/1882410/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1882410] Re: toggling down object GInotifyFileMonitor that's already queued to toggle up ... GNOME Shell crashed with signal 5
I would like to confirm that this bug happens to me as well on Ubuntu 20.04.1. I've been able to reproduce it consistently when downloading two or more big (1GB+) files at the same time from google drive on chrome to the Desktop folder. Downloading the files one at a time or to a different folder doesn't seem to trigger the bug, at least for me -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1882410 Title: toggling down object GInotifyFileMonitor that's already queued to toggle up ... GNOME Shell crashed with signal 5 To manage notifications about this bug go to: https://bugs.launchpad.net/gjs/+bug/1882410/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1882410] Re: toggling down object GInotifyFileMonitor that's already queued to toggle up ... GNOME Shell crashed with signal 5
I've had the "Desktop Icons" disabled for a while now, and it doesn't solve the problem but it feels like it is less frequent. It most often happens when I open a new terminal. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1882410 Title: toggling down object GInotifyFileMonitor that's already queued to toggle up ... GNOME Shell crashed with signal 5 To manage notifications about this bug go to: https://bugs.launchpad.net/gjs/+bug/1882410/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1882410] Re: toggling down object GInotifyFileMonitor that's already queued to toggle up ... GNOME Shell crashed with signal 5
You can also try disabling the 'Desktop Icons' extension in the 'Extensions' app. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1882410 Title: toggling down object GInotifyFileMonitor that's already queued to toggle up ... GNOME Shell crashed with signal 5 To manage notifications about this bug go to: https://bugs.launchpad.net/gjs/+bug/1882410/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1882410] Re: toggling down object GInotifyFileMonitor that's already queued to toggle up ... GNOME Shell crashed with signal 5
The crash appears to be relatively rare globally: 20.04: 602 times 20.10: 52 times I hope I was wrong thinking that this might be caused by the desktop- icons extension. Please start by uninstalling all extensions except those three that are shipped with Ubuntu. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1882410 Title: toggling down object GInotifyFileMonitor that's already queued to toggle up ... GNOME Shell crashed with signal 5 To manage notifications about this bug go to: https://bugs.launchpad.net/gjs/+bug/1882410/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1882410] Re: toggling down object GInotifyFileMonitor that's already queued to toggle up ... GNOME Shell crashed with signal 5
Is there any workaround to this issue? This is a huge productivity killer for me. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1882410 Title: toggling down object GInotifyFileMonitor that's already queued to toggle up ... GNOME Shell crashed with signal 5 To manage notifications about this bug go to: https://bugs.launchpad.net/gjs/+bug/1882410/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1882410] Re: toggling down object GInotifyFileMonitor that's already queued to toggle up ... GNOME Shell crashed with signal 5
** Tags added: groovy -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1882410 Title: toggling down object GInotifyFileMonitor that's already queued to toggle up ... GNOME Shell crashed with signal 5 To manage notifications about this bug go to: https://bugs.launchpad.net/gjs/+bug/1882410/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1882410] Re: toggling down object GInotifyFileMonitor that's already queued to toggle up ... GNOME Shell crashed with signal 5
Tracking in: https://errors.ubuntu.com/problem/a6a50b0ae57f939286a1782a5fc9c45a296d2215 ** Description changed: + https://errors.ubuntu.com/problem/a6a50b0ae57f939286a1782a5fc9c45a296d2215 + + --- + A couple of times a day, I'm noticing all of the window dressing suddenly disappear from all of my open applications, then a second or two later returning. Opening up /var/log/syslog I see: Jun 6 20:45:53 eva gnome-shell[335243]: Window manager warning: Invalid WM_TRANSIENT_FOR window 0x4a00015 specified for 0x4a00518. Jun 6 20:46:40 eva gnome-shell[335243]: Window manager warning: Invalid WM_TRANSIENT_FOR window 0x4a00015 specified for 0x4a0051f. Jun 6 20:47:40 eva gnome-shell[335243]: toggling down object GInotifyFileMonitor that's already queued to toggle down Jun 6 20:47:40 eva gnome-shell[335243]: GNOME Shell crashed with signal 5 Jun 6 20:47:40 eva gnome-shell[335243]: == Stack trace for context 0x557e3a0446a0 == Jun 6 20:47:40 eva systemd[25554]: gnome-shell-x11.service: Main process exited, code=dumped, status=5/TRAP Jun 6 20:47:40 eva systemd[25554]: gnome-shell-x11.service: Failed with result 'core-dump'. Jun 6 20:47:40 eva systemd[25554]: gnome-shell-x11.service: Scheduled restart job, restart counter is at 3. Jun 6 20:47:40 eva systemd[25554]: Stopped target GNOME X11 Session (session: ubuntu). Jun 6 20:47:40 eva systemd[25554]: Stopping GNOME X11 Session (session: ubuntu). Jun 6 20:47:40 eva systemd[25554]: Stopped target GNOME X11 Session. Jun 6 20:47:40 eva systemd[25554]: Stopping GNOME X11 Session. Jun 6 20:47:40 eva systemd[25554]: Stopped target GNOME Shell on X11. Jun 6 20:47:40 eva systemd[25554]: Stopping GNOME Shell on X11. Jun 6 20:47:40 eva systemd[25554]: Stopped GNOME Shell on X11. Jun 6 20:47:40 eva systemd[25554]: Starting GNOME Shell on X11... Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): EDID vendor "ACI", prod id 8434 Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Using hsync ranges from config file Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Using vrefresh ranges from config file Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Printing DDC gathered Modelines: Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Modeline "1600x900"x0.0 108.00 1600 1624 1704 1800 900 901 904 1000 +hsync +vsync (60.0 kHz eP) Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Modeline "800x600"x0.0 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz e) Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Modeline "800x600"x0.0 36.00 800 824 896 1024 600 601 603 625 +hsync +vsync (35.2 kHz e) Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Modeline "640x480"x0.0 31.50 640 656 720 840 480 481 484 500 -hsync -vsync (37.5 kHz e) Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Modeline "640x480"x0.0 31.50 640 664 704 832 480 489 492 520 -hsync -vsync (37.9 kHz e) Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Modeline "640x480"x0.0 30.24 640 704 768 864 480 483 486 525 -hsync -vsync (35.0 kHz e) Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Modeline "640x480"x0.0 25.18 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz e) Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Modeline "720x400"x0.0 28.32 720 738 846 900 400 412 414 449 -hsync +vsync (31.5 kHz e) Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Modeline "1024x768"x0.0 78.75 1024 1040 1136 1312 768 769 772 800 +hsync +vsync (60.0 kHz e) Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Modeline "1024x768"x0.0 75.00 1024 1048 1184 1328 768 771 777 806 -hsync -vsync (56.5 kHz e) Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Modeline "1024x768"x0.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz e) Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Modeline "832x624"x0.0 57.28 832 864 928 1152 624 625 628 667 -hsync -vsync (49.7 kHz e) Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Modeline "800x600"x0.0 49.50 800 816 896 1056 600 601 604 625 +hsync +vsync (46.9 kHz e) Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Modeline "800x600"x0.0 50.00 800 856 976 1040 600 637 643 666 +hsync +vsync (48.1 kHz e) Jun 6 20:47:40 eva /usr/lib/gdm3/gdm-x-session[25623]: (II) modeset(0): Modeline "1152x864"x0.0 108.00 1152 1216 1344 1600 864 865 868 900 +hsync +vsync (67.5 kHz e) Jun 6 20:47:40 eva gsd-media-keys[26011]: Failed to grab accelerators:
[Bug 1882410] Re: toggling down object GInotifyFileMonitor that's already queued to toggle up ... GNOME Shell crashed with signal 5
This is happening to me a few times every day lately. I do not have any icons on the desktop. #0 __GI_raise (sig=) at ../sysdeps/unix/sysv/linux/raise.c:50 #1 0x556612c6552a in dump_gjs_stack_on_signal_handler (signo=5) at ../src/main.c:421 #2 0x7f17472b6210 in () at /lib/x86_64-linux-gnu/libc.so.6 #3 _g_log_abort (breakpoint=1) at ../../../glib/gmessages.c:554 #4 0x7f17480f8159 in g_log_default_handler (log_domain=, log_level=, message=, unused_data=) at ../../../glib/gmessages.c:3123 #5 0x556612c655ee in default_log_handler (log_domain=0x7f1747836e20 "Gjs", log_level=6, message=0x55661bb3aca0 "toggling down object GInotifyFileMonitor that's already queued to toggle up\n", data=0x0) at ../src/main.c:363 #6 0x7f17480f839c in g_logv (log_domain=0x7f1747836e20 "Gjs", log_level=G_LOG_LEVEL_ERROR, format=, args=args@entry=0x7ffc2bb6e820) at ../../../glib/gmessages.c:1350 #7 0x7f17480f8583 in g_log (log_domain=log_domain@entry=0x7f1747836e20 "Gjs", log_level=log_level@entry=G_LOG_LEVEL_ERROR, format=format@entry=0x7f174783c308 "toggling down object %s that's already queued to toggle %s\n") at ../../../glib/gmessages.c:1415 #8 0x7f17477e40a7 in wrapped_gobj_toggle_notify(void*, GObject*, gboolean) (gobj=0x556615cd10b0 [GInotifyFileMonitor], is_last_ref=) at ../gi/object.cpp:1274 #9 0x7f17477f7058 in ToggleQueue::handle_toggle(void (*)(_GObject*, ToggleQueue::Direction)) (this=0x7f17478a14a0 , handler=0x7f17477e3f20 ) at ../gi/toggle.cpp:125 #10 0x7f17477f70df in ToggleQueue::idle_handle_toggle(void*) (data=0x7f17478a14a0 ) at ../gi/toggle.cpp:69 #11 0x7f17480f0e8e in g_main_dispatch (context=0x5566149c1350) at ../../../glib/gmain.c:3309 #12 g_main_context_dispatch (context=context@entry=0x5566149c1350) at ../../../glib/gmain.c:3974 #13 0x7f17480f1240 in g_main_context_iterate (context=0x5566149c1350, block=block@entry=1, dispatch=dispatch@entry=1, self=) at ../../../glib/gmain.c:4047 #14 0x7f17480f1533 in g_main_loop_run (loop=0x556614e05dc0) at ../../../glib/gmain.c:4241 #15 0x7f174751aaf0 in meta_run () at /lib/x86_64-linux-gnu/libmutter-6.so.0 #16 0x556612c64d7d in main (argc=, argv=) at ../src/main.c:634 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1882410 Title: toggling down object GInotifyFileMonitor that's already queued to toggle up ... GNOME Shell crashed with signal 5 To manage notifications about this bug go to: https://bugs.launchpad.net/gjs/+bug/1882410/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1882410] Re: toggling down object GInotifyFileMonitor that's already queued to toggle up ... GNOME Shell crashed with signal 5
Certainly most instances of GInotifyFileMonitor would be in the Desktop Icons extension. Still annoying we can't get a stack trace. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1882410 Title: toggling down object GInotifyFileMonitor that's already queued to toggle up ... GNOME Shell crashed with signal 5 To manage notifications about this bug go to: https://bugs.launchpad.net/gjs/+bug/1882410/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1882410] Re: toggling down object GInotifyFileMonitor that's already queued to toggle up ... GNOME Shell crashed with signal 5
Now...maybe this is jumping the gun a little. But after disabling desktop icons I just spent a bunch of time on mnemosyne (which was triggering this)...and it didn't trigger. Maybe I lucked out and just didn't trigger it...but it's awfully suspicious that it didn't trigger. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1882410 Title: toggling down object GInotifyFileMonitor that's already queued to toggle up ... GNOME Shell crashed with signal 5 To manage notifications about this bug go to: https://bugs.launchpad.net/gjs/+bug/1882410/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1882410] Re: toggling down object GInotifyFileMonitor that's already queued to toggle up ... GNOME Shell crashed with signal 5
Seems it was reported here too: https://gitlab.gnome.org/GNOME/gjs/-/issues/297 ** Also affects: gjs (Ubuntu) Importance: Undecided Status: New ** Bug watch added: gitlab.gnome.org/GNOME/gjs/-/issues #297 https://gitlab.gnome.org/GNOME/gjs/-/issues/297 ** Also affects: gjs via https://gitlab.gnome.org/GNOME/gjs/-/issues/297 Importance: Unknown Status: Unknown ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => Confirmed ** Changed in: gjs (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1882410 Title: toggling down object GInotifyFileMonitor that's already queued to toggle up ... GNOME Shell crashed with signal 5 To manage notifications about this bug go to: https://bugs.launchpad.net/gjs/+bug/1882410/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1882410] Re: toggling down object GInotifyFileMonitor that's already queued to toggle up ... GNOME Shell crashed with signal 5
done. we'll see if it reproduces -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1882410 Title: toggling down object GInotifyFileMonitor that's already queued to toggle up ... GNOME Shell crashed with signal 5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1882410/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
