Version-Release number of selected component: gnome-shell-3.24.2-1.fc26 Additional info: reporter: libreport-2.9.1 backtrace_rating: 4 cmdline: /usr/bin/gnome-shell crash_function: _g_log_abort executable: /usr/bin/gnome-shell journald_cursor: s=cc9ca00405a94009974f04b2d80bb434;i=41f0;b=69c64675504348c5ae3350a6857e6b55;m=67c6c68b;t=55320e434578f;x=8d920ec305779e52 kernel: 4.11.7-300.fc26.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 _g_log_abort at gmessages.c:549 #1 g_log_default_handler at gmessages.c:3036 #2 default_log_handler at main.c:303 #5 object_instance_finalize at gi/object.cpp:1658 #6 JSObject::finalize at /usr/src/debug/mozilla-esr38/js/src/jsobjinlines.h:42 #7 js::gc::Arena::finalize<JSObject> at /usr/src/debug/mozilla-esr38/js/src/jsgc.cpp:497 #8 FinalizeTypedArenas<JSObject> at /usr/src/debug/mozilla-esr38/js/src/jsgc.cpp:557 #9 FinalizeArenas(js::FreeOp *, js::gc::ArenaHeader **, js::gc::SortedArenaList &, enum AllocKind, struct SliceBudget &, js::gc::ArenaLists::KeepArenasEnum) at /usr/src/debug/mozilla-esr38/js/src/jsgc.cpp:600 #10 js::gc::ArenaLists::forceFinalizeNow at /usr/src/debug/mozilla-esr38/js/src/jsgc.cpp:2758 #11 js::gc::ArenaLists::finalizeNow at /usr/src/debug/mozilla-esr38/js/src/jsgc.cpp:2741 This is a private, duplicate bug report of bug 1402492. The report has been created because Bugzilla cannot grant access to a comment for a specific group.
Created attachment 1293373 [details] File: backtrace
Created attachment 1293374 [details] File: cgroup
Created attachment 1293375 [details] File: core_backtrace
Created attachment 1293376 [details] File: cpuinfo
Created attachment 1293377 [details] File: dso_list
Created attachment 1293378 [details] File: environ
Created attachment 1293379 [details] File: limits
Created attachment 1293380 [details] File: maps
Created attachment 1293381 [details] File: open_fds
Created attachment 1293382 [details] File: proc_pid_status
Created attachment 1293383 [details] File: var_log_messages
*** This bug has been marked as a duplicate of bug 1402492 ***
*** Bug 1469727 has been marked as a duplicate of this bug. ***
*** Bug 1496990 has been marked as a duplicate of this bug. ***
This clearly was not in fact a duplicate of #1402492; rather, like #1510059 and #1469813 , #1370073 is a case where we're getting all sorts of unrelated crashes filed as dupes due to the _g_log_abort codepath - see https://bugzilla.redhat.com/show_bug.cgi?id=1509086 for more on that. The critical error here is "Finalizing proxy for an object that's scheduled to be unrooted: Gio.Subprocess". We have several other bugs with the same critical error: https://bugzilla.redhat.com/show_bug.cgi?id=1467320 https://bugzilla.redhat.com/show_bug.cgi?id=1517479 https://bugzilla.redhat.com/show_bug.cgi?id=1514732 https://bugzilla.redhat.com/show_bug.cgi?id=1522921 https://bugzilla.redhat.com/show_bug.cgi?id=1523323 However, I'm not yet sure if they all have the same cause, so I'm not marking them as duplicates for now. If you are still encountering this crash, some more information would help: is there a reliable way to trigger it? What extensions do you have enabled? Do you have the 'pipewire' service enabled? Thanks a lot!
*** Bug 1471936 has been marked as a duplicate of this bug. ***
*** Bug 1472488 has been marked as a duplicate of this bug. ***
*** Bug 1473665 has been marked as a duplicate of this bug. ***
*** Bug 1473927 has been marked as a duplicate of this bug. ***
*** Bug 1473974 has been marked as a duplicate of this bug. ***
*** Bug 1475098 has been marked as a duplicate of this bug. ***
*** Bug 1476034 has been marked as a duplicate of this bug. ***
*** Bug 1476691 has been marked as a duplicate of this bug. ***
*** Bug 1478374 has been marked as a duplicate of this bug. ***
*** Bug 1479333 has been marked as a duplicate of this bug. ***
*** Bug 1479729 has been marked as a duplicate of this bug. ***
*** Bug 1493730 has been marked as a duplicate of this bug. ***
*** Bug 1482330 has been marked as a duplicate of this bug. ***
*** Bug 1483134 has been marked as a duplicate of this bug. ***
*** Bug 1483345 has been marked as a duplicate of this bug. ***
*** Bug 1483619 has been marked as a duplicate of this bug. ***
*** Bug 1485681 has been marked as a duplicate of this bug. ***
*** Bug 1485754 has been marked as a duplicate of this bug. ***
*** Bug 1486491 has been marked as a duplicate of this bug. ***
*** Bug 1489482 has been marked as a duplicate of this bug. ***
*** Bug 1489869 has been marked as a duplicate of this bug. ***
*** Bug 1490025 has been marked as a duplicate of this bug. ***
*** Bug 1490637 has been marked as a duplicate of this bug. ***
*** Bug 1491080 has been marked as a duplicate of this bug. ***
*** Bug 1491524 has been marked as a duplicate of this bug. ***
*** Bug 1491660 has been marked as a duplicate of this bug. ***
*** Bug 1494244 has been marked as a duplicate of this bug. ***
*** Bug 1496980 has been marked as a duplicate of this bug. ***
*** Bug 1524066 has been marked as a duplicate of this bug. ***
*** Bug 1510815 has been marked as a duplicate of this bug. ***
*** Bug 1514983 has been marked as a duplicate of this bug. ***
I checked through all the attachments to this bug and I'm pretty sure there is no sensitive data there, so I've made this report public. (abrt defaults to making private any report which contains any of several keywords, and these are extremely prone to false positives; there was really no need for this report to be private). This will make it easier to get it fixed, and for other reporters of the same bug to know what's going on. I left the var_log_messages attachment private because it does reveal an email address belonging to the user.
I've filed this upstream for gjs at https://gitlab.gnome.org/GNOME/gjs/issues/26 .
*** Bug 1527200 has been marked as a duplicate of this bug. ***
Similar problem has been detected: I logged in via ssh from a recently updated Fedora 26 environment to a Kubuntu 16.04.3 box. I had installed ethereumwallet on the ubuntu box. I tried to run ethereumwallet via ssh (of course, I was using -X when sshing in to the ubuntu box). Gnome crashed on the fedora box, all my sessions were killed and I was sent back to the gnome login prompt (the window where you have to "click" your username and then enter your password). The error received was that gnome-shell had received SIGTRAP. Regards. reporter: libreport-2.9.1 backtrace_rating: 4 cmdline: /usr/bin/gnome-shell crash_function: _g_log_abort executable: /usr/bin/gnome-shell journald_cursor: s=697ffd35ef8149d7b2d7629beaa2b940;i=c118;b=97ac4d9cc87b4d6fa83172d948da091e;m=4af29bf0;t=561a6a41bb515;x=c79a989ca6b28936 kernel: 4.14.8-200.fc26.x86_64 package: gnome-shell-3.24.3-2.fc26 reason: gnome-shell killed by SIGTRAP rootdir: / runlevel: N 5 type: CCpp uid: 1000
*** Bug 1523323 has been marked as a duplicate of this bug. ***
*** Bug 1532400 has been marked as a duplicate of this bug. ***
*** Bug 1536741 has been marked as a duplicate of this bug. ***
Abandoned Linux for too many problems.... CPU Intel Core I7-4510U too many problems with Mesa driver and Qualcomm network card Atheros AR956x Wireless network Adapter, which with the latest kernel not even connect!!!!!
*** Bug 1550204 has been marked as a duplicate of this bug. ***
With great regret passed momentarily to Windows 10 in that with an ATI R5 M230 with Open notebook driver warmed up too and every time I ran the fan was shooting at 1000, creating a crash..... Wifi and network no longer connect with latest kernels..... Hardware isn't ' recent, however I don't think it should create all these problems.... I have an Asus laptop with an I7-4510U Hopefully within a year Fedora come back to shine!!!!!
Similar problem has been detected: -- Occurred at the same time as BUG 1502182 -- -- https://bugzilla.redhat.com/show_bug.cgi?id=1502182 -- -- so same description / comment: -- Happens constantly with kernel 4.15.3-200.fc26.x86_64 and 4.15.4-200.fc26.x86_64 and just once 4.14.16-200.fc26.x86_64 Problem occurs when logging in on graphical environment and quickly starting transmission 2.92 (fedora package) and amule 3.3.1 (rpmfusion package) after eachother. Does not occur when starting in different order and when keeping more time in between starting the mentioned programs. reporter: libreport-2.9.1 backtrace_rating: 4 cmdline: /usr/bin/gnome-shell crash_function: _g_log_abort executable: /usr/bin/gnome-shell journald_cursor: s=7f3f0cc9ec7c4dabad647f6201f2fd43;i=14db7;b=a29f621786694b848730f44871d6f566;m=8fb7fb6;t=56690cd720ff9;x=9c611b3c1392d50a kernel: 4.15.4-200.fc26.x86_64 package: gnome-shell-3.24.3-2.fc26 reason: gnome-shell killed by SIGTRAP rootdir: / runlevel: N 5 type: CCpp uid: 1000
-- correction to comment 57 -- Transmission has nothing to do with it. It only goes wrong with aMule. At fresh reboot or running (from textonly tty): init 3 init 5 and logging in and opening aMule as one of the first programs gnome-shell crashes). Created a new user account and problem does not occur when following the same steps. There must be some legacy or corrupted settings in my old user account then which i have been using since Fedora 18. Weird thing though: After aMule is succesfully started from the new user account, it also starts in the old user account. Also weird that the problem does not occur when kernel 4.14.16-200.fc26.x86_64 is booted. After renaming .aMule directory under old user account (starting with completely new aMule settings like that) problem still occurs. So are there some legacy or corrupted gnome settings that i need to remove?
-- addition to comment 57 -- BUG 1502182 does not repeat together with problem in this BUG
Problem for me is gone. Amule was reinstalled for another reason and a few updates from the fedora updates repo.
This message is a reminder that Fedora 26 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 26. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '26'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 26 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Similar problem has been detected: When I keep the Computer at sleep and login again the gnome shell crashes and all my running applications are closed. reporter: libreport-2.9.1 backtrace_rating: 4 cmdline: /usr/bin/gnome-shell crash_function: _g_log_abort executable: /usr/bin/gnome-shell journald_cursor: s=c057b0828dff4d009d91153cf311f792;i=9e66;b=24f708704de2478d9df41d52494a2566;m=93e5b6926;t=56b8378b45e51;x=a417c32ffb069043 kernel: 4.15.17-200.fc26.x86_64 package: gnome-shell-3.24.3-2.fc26 reason: gnome-shell killed by SIGTRAP rootdir: / runlevel: N 5 type: CCpp uid: 1000
Fedora 26 changed to end-of-life (EOL) status on 2018-05-29. Fedora 26 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.