Description of problem: Happened a few times - when I try opening a URL in gnome-terminal [or alpine in gnome-terminal] - but not always in this mode Switched to gnome/xorg to see if it persists.. Version-Release number of selected component: gnome-shell-3.26.0-1.fc27 Additional info: reporter: libreport-2.9.2 backtrace_rating: 4 cmdline: /usr/bin/gnome-shell crash_function: g_type_check_instance_is_fundamentally_a executable: /usr/bin/gnome-shell journald_cursor: s=8f8e47ec971d47b6b78a34c104875c8c;i=36e59;b=e17c541889ae4c62b8f259358c6c8493;m=760dec9a6;t=559c7356a7bcf;x=ffd6db739d35c001 kernel: 4.13.3-300.fc27.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 g_type_check_instance_is_fundamentally_a at gtype.c:4025 #1 g_value_set_object at gobject.c:3864 #2 object_get_property at gobject.c:1378 #3 g_object_get_property at gobject.c:2575 #4 get_prop_from_g_param at gi/object.cpp:297 #5 object_instance_get_prop(JSContext*, JS::HandleObject, JS::HandleId, JS::MutableHandleValue) at gi/object.cpp:414 #6 js::CallJSPropertyOp(JSContext*, bool (*)(JSContext*, JS::Handle<JSObject*>, JS::Handle<jsid>, JS::MutableHandle<JS::Value>), JS::Handle<JSObject*>, JS::Handle<jsid>, JS::MutableHandle<JS::Value>) at /usr/src/debug/mozjs38-38.8.0-6.fc27.x86_64/jscntxtinlines.h:297 #7 GetNonexistentProperty(JSContext*, js::HandleNativeObject, JS::HandleId, IsNameLookup, JS::MutableHandleValue) at /usr/src/debug/mozjs38-38.8.0-6.fc27.x86_64/vm/NativeObject.cpp:1765 #8 NativeGetPropertyInline<(js::AllowGC)1> at /usr/src/debug/mozjs38-38.8.0-6.fc27.x86_64/vm/NativeObject.cpp:1891 #9 js::NativeGetProperty(JSContext*, JS::Handle<js::NativeObject*>, JS::Handle<JSObject*>, JS::Handle<jsid>, JS::MutableHandle<JS::Value>) at /usr/src/debug/mozjs38-38.8.0-6.fc27.x86_64/vm/NativeObject.cpp:1909 Potential duplicate: bug 1485465
Created attachment 1329619 [details] File: backtrace
Created attachment 1329620 [details] File: cgroup
Created attachment 1329621 [details] File: core_backtrace
Created attachment 1329622 [details] File: cpuinfo
Created attachment 1329623 [details] File: dso_list
Created attachment 1329624 [details] File: environ
Created attachment 1329625 [details] File: exploitable
Created attachment 1329626 [details] File: limits
Created attachment 1329627 [details] File: maps
Created attachment 1329628 [details] File: open_fds
Created attachment 1329629 [details] File: proc_pid_status
Created attachment 1329630 [details] File: var_log_messages
It happened again [in gnome/xorg] while filing this report via abrt - when I clicked on this bugzilla url - that abrt created. Atleast gnome/xorg restarts gnome-shell without logging me out - like gnome/wayland.
Similar problem has been detected: When I clicked on a bugzilla url in ABRT reporter: libreport-2.9.2 backtrace_rating: 4 cmdline: /usr/bin/gnome-shell crash_function: g_type_check_instance_is_fundamentally_a executable: /usr/bin/gnome-shell journald_cursor: s=8f8e47ec971d47b6b78a34c104875c8c;i=37a43;b=e17c541889ae4c62b8f259358c6c8493;m=7d4a6870a;t=559c859454cc1;x=d9ddb73e4a3e4a41 kernel: 4.13.3-300.fc27.x86_64 package: gnome-shell-3.26.0-1.fc27 reason: gnome-shell killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
Similar problem has been detected: open url from gnome-terminal reporter: libreport-2.9.2 backtrace_rating: 4 cmdline: /usr/bin/gnome-shell crash_function: g_type_check_instance_is_fundamentally_a executable: /usr/bin/gnome-shell journald_cursor: s=8f8e47ec971d47b6b78a34c104875c8c;i=395ca;b=2cc1406351b14e56ad9f3c7907eb6e51;m=5982b5f02;t=559cfeda2e562;x=f52b16258d8c061a kernel: 4.13.3-300.fc27.x86_64 package: gnome-shell-3.26.0-1.fc27 reason: gnome-shell killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
Similar problem has been detected: crashes when opening a url from gnome-terminal/alpine reporter: libreport-2.9.2 backtrace_rating: 4 cmdline: /usr/bin/gnome-shell crash_function: g_type_check_instance_is_fundamentally_a executable: /usr/bin/gnome-shell journald_cursor: s=8f8e47ec971d47b6b78a34c104875c8c;i=3fae5c;b=8cbbba997d004f399109f18b19b085fc;m=25b6ace5bc;t=55aa667388085;x=5d190ec6ff47a83a kernel: 4.13.4-300.fc27.x86_64 package: gnome-shell-3.26.0-1.fc27 reason: gnome-shell killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
If I'm the only one with this problem - wondering if some local setup is triggering this issue for me..
Similar problem has been detected: It seems to occur sometimes when notifications are going to be shown. reporter: libreport-2.9.2 backtrace_rating: 4 cmdline: /usr/bin/gnome-shell crash_function: g_type_check_instance_is_fundamentally_a executable: /usr/bin/gnome-shell journald_cursor: s=f8abd916041f40d1819fbeadfe641150;i=6002;b=56037773ae0e4049a703cc4839cfba34;m=75f9caebb;t=55ac904b7bc76;x=7a36ca04bf0f3ad9 kernel: 4.13.4-300.fc27.x86_64 package: gnome-shell-3.26.0-1.fc27 reason: gnome-shell killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
I've had this a couple of times now. Twice when I went to view notifications in the clock, possibly just as another one popped up. At least a few more times when I didn't. gnome/wayland, so it logs me out multiple times per day.
Similar problem has been detected: suspend, unsuspend reporter: libreport-2.9.2 backtrace_rating: 4 cmdline: /usr/bin/gnome-shell crash_function: g_type_check_instance_is_fundamentally_a executable: /usr/bin/gnome-shell journald_cursor: s=636cf4b8127d438dabca251aaf14f836;i=3a8afb;b=ea6f04095b2f427197d3b48c0f393ac0;m=fb90a035;t=55adc064a8c99;x=51c2fbc3e74bd4b kernel: 4.13.4-300.fc27.x86_64 package: gnome-shell-3.26.0-1.fc27 reason: gnome-shell killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
Similar problem has been detected: Did nothing (I was away from my desk) reporter: libreport-2.9.2 backtrace_rating: 4 cmdline: /usr/bin/gnome-shell crash_function: g_type_check_instance_is_fundamentally_a executable: /usr/bin/gnome-shell journald_cursor: s=636cf4b8127d438dabca251aaf14f836;i=3af98e;b=ea6f04095b2f427197d3b48c0f393ac0;m=3dc11c297;t=55adee6cbaefc;x=10e2ad437fe42ecc kernel: 4.13.4-300.fc27.x86_64 package: gnome-shell-3.26.0-1.fc27 reason: gnome-shell killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
I have now had this while away from my desk, which points to: - notifications - time At the same time when I logged in I had "NaN new messages" notification, which also points to notifications being broken. Further, I've had it crash at least three times by clicking on the clock to show notifications. I've now switched notification popups off in settings, hoping it will help.
Similar problem has been detected: gnome-shell crashed 6 times, in completely different scenarios. I close all applications and disable the extensions, but gnome-shell crashed againg reporter: libreport-2.9.2 backtrace_rating: 4 cmdline: /usr/bin/gnome-shell crash_function: g_type_check_instance_is_fundamentally_a executable: /usr/bin/gnome-shell journald_cursor: s=842283a1e816492f89972582f4772fca;i=36fff;b=08a7afb550ca45cca044d395cc613621;m=209ca8b3d;t=55adfc772df5b;x=3760537bffc80c kernel: 4.13.4-300.fc27.x86_64 package: gnome-shell-3.26.0-1.fc27 reason: gnome-shell killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
So gnome-shell also crashes with all notifications off. With all notifications off, though, I still get some notifications, for example: selinux/AVC notifications in the clock/calendar. This might be because sealert is a tray icon application.
Similar problem has been detected: I was away from the keyboard. reporter: libreport-2.9.2 backtrace_rating: 4 cmdline: /usr/bin/gnome-shell crash_function: g_type_check_instance_is_fundamentally_a executable: /usr/bin/gnome-shell journald_cursor: s=f8abd916041f40d1819fbeadfe641150;i=f8e8;b=74df68940b41494987ef1231d9c93543;m=2cbed589f;t=55b0c326bbab9;x=bdd550be1cce53f kernel: 4.13.5-300.fc27.x86_64 package: gnome-shell-3.26.0-1.fc27 reason: gnome-shell killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
I can fairly reliably crash gnome-shell doing: 1. suspend & unsuspend 2. immediately run: notify-send --expire-time=1000 Hello World It's not necessary to be a notification. Both portal logins (browsers?) and shell context menus have triggered the crash. It's not necessary to suspend & unsuspend, but that does greatly increase the repeatability.
Still an issue with gnome-shell-3.26.1-1.fc27.x86_64
Similar problem has been detected: open a new window reporter: libreport-2.9.2 backtrace_rating: 4 cmdline: /usr/bin/gnome-shell crash_function: g_type_check_instance_is_fundamentally_a executable: /usr/bin/gnome-shell journald_cursor: s=636cf4b8127d438dabca251aaf14f836;i=4049a2;b=89ca6e9bf1344e1aaa196e8157b70b6b;m=3798ecfd9;t=55b44d1978de4;x=a2e37ce1ca0b119 kernel: 4.12.14-300.fc26.x86_64 package: gnome-shell-3.26.1-1.fc27 reason: gnome-shell killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
Similar problem has been detected: It seems that it crashed after notification from firefox. reporter: libreport-2.9.2 backtrace_rating: 3 cmdline: /usr/bin/gnome-shell crash_function: g_type_check_instance_is_fundamentally_a executable: /usr/bin/gnome-shell journald_cursor: s=f8abd916041f40d1819fbeadfe641150;i=15cfc;b=45d482a733e74f869afb2bb53d931f10;m=55d233803;t=55b4bbc4c89c1;x=69ab50e14bc3ad43 kernel: 4.13.5-300.fc27.x86_64 package: gnome-shell-3.26.1-1.fc27 reason: gnome-shell killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
Similar problem has been detected: It happend randomly. Juste use Gnome and the Shell crash some times. reporter: libreport-2.9.2 backtrace_rating: 4 cmdline: /usr/bin/gnome-shell crash_function: g_type_check_instance_is_fundamentally_a executable: /usr/bin/gnome-shell journald_cursor: s=11b5629936314432b0e00e46bc06d00c;i=2028f4;b=4c8375797fb5475699be02a141890094;m=4ccd048d8;t=55b5cd42ac346;x=ed2dae42ccff22a6 kernel: 4.13.5-300.fc27.x86_64 package: gnome-shell-3.26.1-1.fc27 reason: gnome-shell killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
Two days ago, I restored gnome settings to it's Defaults (remove ~/.gnome* and ~/.config/gconf directories), and I had no crash since that.
Similar problem has been detected: as usual - opening a url from alpine reporter: libreport-2.9.2 backtrace_rating: 4 cmdline: /usr/bin/gnome-shell crash_function: g_type_check_instance_is_fundamentally_a executable: /usr/bin/gnome-shell journald_cursor: s=8f8e47ec971d47b6b78a34c104875c8c;i=40e5c7;b=488e596c16b2499b9c91a46b26bd570a;m=55ca160f4;t=55b6f7679fc13;x=936ea4db8cb82391 kernel: 4.13.6-300.fc27.x86_64 package: gnome-shell-3.26.1-1.fc27 reason: gnome-shell killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
(In reply to Haghighi from comment #31) > Two days ago, I restored gnome settings to it's Defaults (remove ~/.gnome* > and ~/.config/gconf directories), and I had no crash since that. I've removed the above config files - and still got a crash
*** Bug 1502735 has been marked as a duplicate of this bug. ***
Similar problem has been detected: very specifically a notification (gnome-terminal completed a process while gnome-terminal wasn't focused.) That notification does not appear in the notification list (the calendar list, it still has two other prior notifications.) I've since tried disabling gnome-shell extensions and various settings, and it still happens. On Wayland it means a logout every few hours. On Xorg it's not as severe. reporter: libreport-2.9.2 backtrace_rating: 4 cmdline: /usr/bin/gnome-shell crash_function: g_type_check_instance_is_fundamentally_a executable: /usr/bin/gnome-shell journald_cursor: s=636cf4b8127d438dabca251aaf14f836;i=4114f7;b=89ca6e9bf1344e1aaa196e8157b70b6b;m=275232141a;t=55baae77e0cd4;x=2146c2c2714e2385 kernel: 4.12.14-300.fc26.x86_64 package: gnome-shell-3.26.1-1.fc27 reason: gnome-shell killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
Similar problem has been detected: I didn't do anything particular. Though most often it seems to crash when I've gone to look at email via Evolution. Though I don't think that that is exclusively the way it dies. reporter: libreport-2.9.2 backtrace_rating: 4 cmdline: /usr/bin/gnome-shell crash_function: g_type_check_instance_is_fundamentally_a executable: /usr/bin/gnome-shell journald_cursor: s=1f98cce21bf141d1af03fb013e989723;i=dedec;b=4168dc4e977b46a6ab0ac8f80d29999d;m=56372cb24;t=55bb1bbd00a2b;x=f1c4a5aa9cc7fc6e kernel: 4.13.6-300.fc27.x86_64 package: gnome-shell-3.26.1-1.fc27 reason: gnome-shell killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
I can say it just crashed after I submitted that report when I clicked on a collapsible widget in google chrome.
Similar problem has been detected: just using the desktop on fedora 27beta, I randomly get these crashes... reporter: libreport-2.9.2 backtrace_rating: 4 cmdline: /usr/bin/gnome-shell crash_function: g_type_check_instance_is_fundamentally_a executable: /usr/bin/gnome-shell journald_cursor: s=a5480301e9144345ba87de1e87fc4915;i=d5da;b=381db9959cc447889bc11d64ba46cffb;m=8306350bc;t=55bd1b806478a;x=87d886d231a44e45 kernel: 4.13.5-300.fc27.x86_64 package: gnome-shell-3.26.1-1.fc27 reason: gnome-shell killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
Similar problem has been detected: just using the desktop reporter: libreport-2.9.2 backtrace_rating: 4 cmdline: /usr/bin/gnome-shell crash_function: g_type_check_instance_is_fundamentally_a executable: /usr/bin/gnome-shell journald_cursor: s=a5480301e9144345ba87de1e87fc4915;i=e91a;b=381db9959cc447889bc11d64ba46cffb;m=e47cc0668;t=55be4b68c5662;x=1f2bdafceb0e3577 kernel: 4.13.5-300.fc27.x86_64 package: gnome-shell-3.26.1-1.fc27 reason: gnome-shell killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
Similar problem has been detected: I opened a window for an extension in Google Chrome and Gnome Shell crashed reporter: libreport-2.9.2 backtrace_rating: 3 cmdline: /usr/bin/gnome-shell crash_function: g_type_check_instance_is_fundamentally_a executable: /usr/bin/gnome-shell journald_cursor: s=3351daeebce04255bdb16187ecb972e6;i=2196;b=b89442ce02bc4f87895ee2328ba5a1e2;m=c7024370;t=55bf1e95a32cf;x=30fe171c1f1d95aa kernel: 4.13.8-300.fc27.x86_64 package: gnome-shell-3.26.1-1.fc27 reason: gnome-shell killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
Similar problem has been detected: Gnome-shell crashed when I inserted a SDcard. It also happened in the past out of the blue. It happened also when I was using vlc player. reporter: libreport-2.9.2 backtrace_rating: 3 cmdline: /usr/bin/gnome-shell crash_function: g_type_check_instance_is_fundamentally_a executable: /usr/bin/gnome-shell journald_cursor: s=338a747b718e409d9592f7cf05807cb3;i=56929;b=9cffc84178c446b4bedf5d27e3de1be8;m=bfdf258c;t=55c0f458c9e77;x=d632a0ea307cdfab kernel: 4.13.8-300.fc27.x86_64 package: gnome-shell-3.26.1-1.fc27 reason: gnome-shell killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
crashes still persist wtih gnome-shell-3.26.1-2.fc27.x86_64
Similar problem has been detected: open new window reporter: libreport-2.9.2 backtrace_rating: 3 cmdline: /usr/bin/gnome-shell crash_function: g_type_check_instance_is_fundamentally_a executable: /usr/bin/gnome-shell journald_cursor: s=636cf4b8127d438dabca251aaf14f836;i=41c6d1;b=89ca6e9bf1344e1aaa196e8157b70b6b;m=44373b2bdc;t=55c46bdd98fc9;x=8d2e7af12a203ade kernel: 4.12.14-300.fc26.x86_64 package: gnome-shell-3.26.1-2.fc27 reason: gnome-shell killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
Similar problem has been detected: I have started Firefox. reporter: libreport-2.9.2 backtrace_rating: 3 cmdline: /usr/bin/gnome-shell crash_function: g_type_check_instance_is_fundamentally_a executable: /usr/bin/gnome-shell journald_cursor: s=4ed6f4c10cb34f11bc4458f726a9ed21;i=f4eb;b=056b7438321446d683d28c1fd39234fe;m=1cef7824;t=55c4f0d36993a;x=d572578fea54f8b3 kernel: 4.13.8-300.fc27.x86_64 package: gnome-shell-3.26.1-2.fc27 reason: gnome-shell killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
Similar problem has been detected: Issue appeard after system hibernated and I started one youtube video in Chrome reporter: libreport-2.9.2 backtrace_rating: 3 cmdline: /usr/bin/gnome-shell crash_function: g_type_check_instance_is_fundamentally_a executable: /usr/bin/gnome-shell journald_cursor: s=338a747b718e409d9592f7cf05807cb3;i=74abe;b=40bb613ae1bb40e3b820af3f740ec3af;m=a3c2800c7;t=55c54c8543058;x=9af9cf318da4676a kernel: 4.13.8-300.fc27.x86_64 package: gnome-shell-3.26.1-2.fc27 reason: gnome-shell killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
Similar problem has been detected: System woke up from hibernation. reporter: libreport-2.9.2 backtrace_rating: 3 cmdline: /usr/bin/gnome-shell crash_function: g_type_check_instance_is_fundamentally_a executable: /usr/bin/gnome-shell journald_cursor: s=e293d208285744e7b6f263e67e661713;i=e84;b=e9056844814c44b7a8cf0446481e0903;m=3fd8f1c;t=55c5f3d3594a7;x=2b960c7a9cd15f0f kernel: 4.13.8-300.fc27.x86_64 package: gnome-shell-3.26.1-2.fc27 reason: gnome-shell killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
Similar problem has been detected: open a new firefox window, some I/O load. reporter: libreport-2.9.2 backtrace_rating: 4 cmdline: /usr/bin/gnome-shell crash_function: g_type_check_instance_is_fundamentally_a executable: /usr/bin/gnome-shell journald_cursor: s=636cf4b8127d438dabca251aaf14f836;i=42929e;b=8506f95cc9184dc6bd623a496ccb25fa;m=8c1d8f2fd;t=55c6b1c31510e;x=4603a62f5a441de0 kernel: 4.12.14-300.fc26.x86_64 package: gnome-shell-3.26.1-2.fc27 reason: gnome-shell killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
Similar problem has been detected: handbrake finished a queue and displayed a notification reporter: libreport-2.9.2 backtrace_rating: 4 cmdline: /usr/bin/gnome-shell crash_function: g_type_check_instance_is_fundamentally_a executable: /usr/bin/gnome-shell journald_cursor: s=636cf4b8127d438dabca251aaf14f836;i=42aeba;b=8506f95cc9184dc6bd623a496ccb25fa;m=b16ebe008;t=55c6edd321365;x=5e819c9397a36c29 kernel: 4.12.14-300.fc26.x86_64 package: gnome-shell-3.26.1-2.fc27 reason: gnome-shell killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
Similar problem has been detected: Probably some notification was about to be shown (a command completed in a terminal). reporter: libreport-2.9.2 backtrace_rating: 3 cmdline: /usr/bin/gnome-shell crash_function: g_type_check_instance_is_fundamentally_a executable: /usr/bin/gnome-shell journald_cursor: s=e293d208285744e7b6f263e67e661713;i=2438;b=e9056844814c44b7a8cf0446481e0903;m=1181784897;t=55c7786b4a0e0;x=5d40c3f915d87d69 kernel: 4.13.8-300.fc27.x86_64 package: gnome-shell-3.26.1-2.fc27 reason: gnome-shell killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
Similar problem has been detected: It crashed just after login. reporter: libreport-2.9.2 backtrace_rating: 3 cmdline: /usr/bin/gnome-shell crash_function: g_type_check_instance_is_fundamentally_a executable: /usr/bin/gnome-shell journald_cursor: s=e293d208285744e7b6f263e67e661713;i=3505;b=a05a45eeb3534586bc318682d445aafd;m=45d6329;t=55c796265ced1;x=49452766e2282038 kernel: 4.13.9-300.fc27.x86_64 package: gnome-shell-3.26.1-2.fc27 reason: gnome-shell killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
I don't know if my bug 1506706 is a duplicate of this or not, but I've a lot of frequent GNOME Shell crashes recently. Please check it and close the other one if it's a duplicate. I tried to upload a coredump file and everything.
(In reply to Anass Ahmed from comment #51) > I don't know if my bug 1506706 is a duplicate of this or not, but I've a lot > of frequent GNOME Shell crashes recently. It looks the same to me. Recently a similar (but not exact) bug got fixed that had to do with *closing* maximised windows, so there are multiple bugs. That was fixed by upgrading mutter and mozillajs, IIRC. > Please check it and close the other one if it's a duplicate. I tried to > upload a coredump file and everything. I recommend running under Xorg and not Wayland until this is resolved, so that you don't lose data every few hours. It will also allow for more abrt core dump uploads. If you don't need notifications, turning them all off will also reduce -- but not prevent -- crashes.
(In reply to Berend De Schouwer from comment #52) > I recommend running under Xorg and not Wayland until this is resolved, so > that you don't lose data every few hours. Just in case your comments weren't strictly for his bug. I'm using xorg at the moment based on 'loginctl show-session <id> -p Type'
*** Bug 1507148 has been marked as a duplicate of this bug. ***
Similar problem has been detected: Started VMware Workstation. reporter: libreport-2.9.2 backtrace_rating: 3 cmdline: /usr/bin/gnome-shell crash_function: g_type_check_instance_is_fundamentally_a executable: /usr/bin/gnome-shell journald_cursor: s=e293d208285744e7b6f263e67e661713;i=792d;b=a05a45eeb3534586bc318682d445aafd;m=65bb502d8;t=55c8f709ea9c8;x=a9179ef673b7b82 kernel: 4.13.9-300.fc27.x86_64 package: gnome-shell-3.26.1-2.fc27 reason: gnome-shell killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
Similar problem has been detected: It occurred on a notification from Firefox, reporter: libreport-2.9.2 backtrace_rating: 3 cmdline: /usr/bin/gnome-shell crash_function: g_type_check_instance_is_fundamentally_a executable: /usr/bin/gnome-shell journald_cursor: s=e293d208285744e7b6f263e67e661713;i=d553;b=9b2803c3e53346a9a68dcc708b677e83;m=4614f6efb;t=55cb65819337c;x=4763b4ffe0827361 kernel: 4.13.9-300.fc27.x86_64 package: gnome-shell-3.26.1-2.fc27 reason: gnome-shell killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
(In reply to Berend De Schouwer from comment #52) > It looks the same to me. > > Recently a similar (but not exact) bug got fixed that had to do with > *closing* maximised windows, so there are multiple bugs. That was fixed by > upgrading mutter and mozillajs, IIRC. This bug never reached Fedora 27 as far as I know, the 3.26.1 release reached us after this bug was fixed. Arch people was hit really hard by it because they Arch decided to jump to it. > I recommend running under Xorg and not Wayland until this is resolved, so > that you don't lose data every few hours. > > It will also allow for more abrt core dump uploads. > > If you don't need notifications, turning them all off will also reduce -- > but not prevent -- crashes. I can't stand running Xorg right now after running Wayland stable for 3 consequent releases! :) (In reply to Łukasz Faber from comment #56) > Similar problem has been detected: > > It occurred on a notification from Firefox, This confirms my correlation in my bug, but it's one of the reasons to trigger the crash. However, I disabled a lot of extensions (the only extension I have enabled right now is EasyScreenCast) and autostart apps, and things got more stable right now.
(In reply to Anass Ahmed from comment #57) > (In reply to Berend De Schouwer from comment #52) > > It looks the same to me. > > > > Recently a similar (but not exact) bug got fixed that had to do with > > *closing* maximised windows, so there are multiple bugs. That was fixed by > > upgrading mutter and mozillajs, IIRC. > > This bug never reached Fedora 27 as far as I know, the 3.26.1 release > reached us after this bug was fixed. Arch people was hit really hard by it > because they Arch decided to jump to it. This did reach F27Beta. #1476603. It was fixed almost immediately. > > I recommend running under Xorg and not Wayland until this is resolved, so > > that you don't lose data every few hours. > > > > It will also allow for more abrt core dump uploads. > > > > If you don't need notifications, turning them all off will also reduce -- > > but not prevent -- crashes. > > I can't stand running Xorg right now after running Wayland stable for 3 > consequent releases! :) I prefer Wayland, but I can't afford losing data every few hours. With all extensions off it's about once a day, usually very soon after login or suspend.
Similar problem has been detected: I run dnf update in a terminal, but is random... reporter: libreport-2.9.2 backtrace_rating: 4 cmdline: /usr/bin/gnome-shell crash_function: g_type_check_instance_is_fundamentally_a executable: /usr/bin/gnome-shell journald_cursor: s=2725404aec1041a8b96c951e4ec8e7f4;i=661e;b=0d62ce29f2274e0a9a673da422ae2c26;m=1ccd7dca24;t=55cc47e01c485;x=6294dfd1bd8c5c8f kernel: 4.13.5-300.fc27.x86_64 package: gnome-shell-3.26.1-2.fc27 reason: gnome-shell killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
Similar problem has been detected: running a command on the terminal, any command, seems to be random... now I'm using Tilix terminal and looks more stable... reporter: libreport-2.9.2 backtrace_rating: 4 cmdline: /usr/bin/gnome-shell crash_function: g_type_check_instance_is_fundamentally_a executable: /usr/bin/gnome-shell journald_cursor: s=2725404aec1041a8b96c951e4ec8e7f4;i=68d3;b=0d62ce29f2274e0a9a673da422ae2c26;m=1cf731d473;t=55cc4a7b5ced4;x=d8049eed1bb28347 kernel: 4.13.5-300.fc27.x86_64 package: gnome-shell-3.26.1-2.fc27 reason: gnome-shell killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
Similar problem has been detected: I was using tilix instead of gnome terminal, was more stable... but crashed after some hours... reporter: libreport-2.9.2 backtrace_rating: 4 cmdline: /usr/bin/gnome-shell crash_function: g_type_check_instance_is_fundamentally_a executable: /usr/bin/gnome-shell journald_cursor: s=2725404aec1041a8b96c951e4ec8e7f4;i=7b25;b=0d62ce29f2274e0a9a673da422ae2c26;m=20e2020ad2;t=55cc892860534;x=32258fdbf3368198 kernel: 4.13.5-300.fc27.x86_64 package: gnome-shell-3.26.1-2.fc27 reason: gnome-shell killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
Similar problem has been detected: I started android studion and crashed while it was indexing. reporter: libreport-2.9.2 backtrace_rating: 3 cmdline: /usr/bin/gnome-shell crash_function: g_type_check_instance_is_fundamentally_a executable: /usr/bin/gnome-shell journald_cursor: s=338a747b718e409d9592f7cf05807cb3;i=a303c;b=b875042f03734c23a965d8b46c961853;m=bddc14e03;t=55cd5a9865819;x=6e0f2073e51c4c83 kernel: 4.13.9-300.fc27.x86_64 package: gnome-shell-3.26.1-2.fc27 reason: gnome-shell killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
Similar problem has been detected: I was using VLC reporter: libreport-2.9.2 backtrace_rating: 3 cmdline: /usr/bin/gnome-shell crash_function: g_type_check_instance_is_fundamentally_a executable: /usr/bin/gnome-shell journald_cursor: s=338a747b718e409d9592f7cf05807cb3;i=a86c0;b=b875042f03734c23a965d8b46c961853;m=11b09dfa85;t=55cdb7c63049a;x=ee82b6a72561d8eb kernel: 4.13.9-300.fc27.x86_64 package: gnome-shell-3.26.1-2.fc27 reason: gnome-shell killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
Similar problem has been detected: I was updating. Commands used: sudo dnf clean all gnome-shell crashed while running sudo dnf update reporter: libreport-2.9.2 backtrace_rating: 3 cmdline: /usr/bin/gnome-shell crash_function: g_type_check_instance_is_fundamentally_a executable: /usr/bin/gnome-shell journald_cursor: s=338a747b718e409d9592f7cf05807cb3;i=b9f46;b=08645b599cd04d18bf4809d6432b5e85;m=e083fa4fa;t=55d0285be5f81;x=c7818bdd33781750 kernel: 4.13.9-300.fc27.x86_64 package: gnome-shell-3.26.1-2.fc27 reason: gnome-shell killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
Similar problem has been detected: start a new firefox window reporter: libreport-2.9.2 backtrace_rating: 4 cmdline: /usr/bin/gnome-shell crash_function: g_type_check_instance_is_fundamentally_a executable: /usr/bin/gnome-shell journald_cursor: s=636cf4b8127d438dabca251aaf14f836;i=449f75;b=8506f95cc9184dc6bd623a496ccb25fa;m=4d3ecbc71f;t=55d0c6ae597da;x=39ebdf9e189b1359 kernel: 4.12.14-300.fc26.x86_64 package: gnome-shell-3.26.1-2.fc27 reason: gnome-shell killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
I've experienced this issue - session crashed several times in one day. Have since reverted to F26 so that I can get work done! Unsetting 'needinfo' flag due to the numerous crash reports that have come in. I see this upstream bug report also: https://bugzilla.gnome.org/show_bug.cgi?id=789484
Proposed as a Blocker for 27-final by Fedora user anassahmed using the blocker tracking app because: All applications that can be launched using the standard graphical mechanism of a release-blocking desktop after a default installation of that desktop must start successfully and withstand a basic functionality test.
Possibly related is Bug 1469129, which has a similar stacktrace and many more reports.
*** Bug 1506706 has been marked as a duplicate of this bug. ***
Discussed during the 2017-11-06 blocker review meeting: [1] The decision to classify this bug as a RejectedBlocker was made as it does not affect every install, and neither a reliable reproducer nor a clear cause analysis have been found yet. As this is being raised very late in the cycle, we feel we can only block the release on it with definite information indicating it will affect a broad range of users. [1] https://meetbot.fedoraproject.org/fedora-blocker-review/2017-11-06/f27-blocker-review.2017-11-06-17.00.txt
(In reply to Geoffrey Marr from comment #70) > Discussed during the 2017-11-06 blocker review meeting: [1] > > The decision to classify this bug as a RejectedBlocker was made as it does > not affect every install, and neither a reliable reproducer nor a clear > cause analysis have been found yet. As this is being raised very late in the > cycle, we feel we can only block the release on it with definite information > indicating it will affect a broad range of users. Is comment #26 not reliable enough for a reproducer? If it's not every install, what more information do you need to track it down?
I can not reproduce with comment #26. What do you mean by immediately? Even after disabling the screen lock after suspend and just hitting enter to start the command as fast as possible, I can't get it to crash. It just shows the notification.
(In reply to Berend De Schouwer from comment #71) > Is comment #26 not reliable enough for a reproducer? No crash here with "systemctl suspend && notify-send --expire-time=1000 Hello World". Even when I disable screen locking.
I still go through unlock, focus terminal, etc. There's no rush. I suspect it is related to load or I/O, so it has to be within a few seconds (not milliseconds) of unlock before the machine settles down. So I suspect we're chasing a hardware or configuration problem. So, here goes: - Video: (I don't know which one is actually in use, no games are running) - Intel HD 5500 - AMD Radeon M255 - Display: - local panel - hdmi external - everything @ 1920x1080 - Drivers: - i915 - amdgpu (I get both amdgpu and i915 warnings in dmesg, not necessarily at the same time as this bug.) - Protocol: - X11 - Wayland - gnome-shell - tried without extensions - multiple workspaces - filesystem (got mentioned in one of the other bugs, so I'll try and be complete) - ext4 on luks on lvm (or is that lvm on luks?) How do I get a "blank" / "new user" gnome-shell configuration? How do I clear out F24/25/26 cruft? (I don't want to throw /home away, though...)
The correlation was strong with notifications (also it happened with other events) when I filed my bug 1506706. I disabled all GNOME Shell extensions and the experience became more stable since. My machine only crashed twice after that when I was trying to record using EasyScreenCast extension (which sends a notification BTW) on a multi-head setup upon trying to select the secondary monitor as the selected monitor for recording. I'm gonna re-enable my extensions again now, and find a proper reliable re-producer. I'm using a very "standard" laptop with a very "standard" installation: Just Intel CPU/GPU, no NVIDIA or AMD, using non-encrypted ext4 for both / and /home, most of the time on a single screen, all under Wayland.
Similar problem has been detected: Clicked on a notification in the notification panel. reporter: libreport-2.9.2 backtrace_rating: 3 cmdline: /usr/bin/gnome-shell crash_function: g_type_check_instance_is_fundamentally_a executable: /usr/bin/gnome-shell journald_cursor: s=32023ca4c76b445b9cd2d355fc80cc95;i=a249b;b=16dece0648fb449fa62959043936864a;m=21b785475;t=55d646ea9fa69;x=3a9a339fb86485cd kernel: 4.13.9-300.fc27.x86_64 package: gnome-shell-3.26.1-2.fc27 reason: gnome-shell killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
We're back with them crashes again after re-enabling extensions. I'm trying to figure out a producer, but I'm suspecting TopIconsPlus is a prime candidate, though the crashes happened without it before.
I do not use TopIconsPlus and also have these crashes. Currently, with only the following extensions enabled, Gnome is quite stable: - Do not disturb button - Kstatusnotifieritem/appindicator support - Topicons (not Plus) - User themes I cannot pinpoint the exact extension, but I had much more crashes with the following additional extensions enabled: - Openweather - Places status indicator - Pomodoro - Recent items - Removable drive menu Most of them were installed from Fedora repos, not from extensions.gnome.org.
(In reply to Anass Ahmed from comment #77) > but I'm suspecting TopIconsPlus is a prime candidate I don't think so. I've used TopIcons Plus (and Openweather) for some time now without any issues. However I've just installed - Places status indicator - Pomodoro - Recent items - Removable drive menu as they were mentioned in comment #78 and the shell almost immediately crashed. It was however reported as Bug 1489554 and not this one. These are all probably related however
Similar problem has been detected: Within minutes of resuming from a suspended state or locked screen, gnome-shell crashes and displays a login prompt. reporter: libreport-2.9.2 backtrace_rating: 3 cmdline: /usr/bin/gnome-shell crash_function: g_type_check_instance_is_fundamentally_a executable: /usr/bin/gnome-shell journald_cursor: s=a44e943c3cac433aa0a04c536491e2a4;i=91e7;b=10f1d87ac9834af98506907667f8d720;m=24a35b0ce1;t=55d66ba988be4;x=3c377bdfc4129d0c kernel: 4.13.9-300.fc27.x86_64 package: gnome-shell-3.26.1-2.fc27 reason: gnome-shell killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
I don't know if this is related to notifications. I've had more crashes unrelated to notifications than anything else. Unless the crash is happening because GNOME is trying to display a notification. I don't have anything but the stock extensions that would come with a default install. I get crashes while browsing websites. I've had crashes switching windows with mouse or alt-tab. I've had crashes while coding via PHPStorm... To me there is no consistency in the crash whatsoever. Also I've checked via loginctl and I'm using x11.
I've got more than a bunch of crashes of the same error when I tried to unlock the device after enabling this list of extensions (most of them are from GNOME extensions website): - TopIcons Plus. - Text Translator. - Caffeine. - Dash to Dock. - Impatience. - EasyScreenCast. - Sound Input & Output Device Chooser. - Media Player Indicator. - Status Area Horizontal Spacing. From Repositories: - GPaste. - Pomodoro. It's literally something with GNOME extensions, I've just crashed GNOME while typing the above list as I found an update for an extension in GNOME Tweaks and I clicked "Update", then it crashed!!
I've enabled and disabled extensions, and for me: 1. enable TopIconsPlus 2. enable Pomodoro 3. suspend 4. notify-send 5. ... crash Disabling either of TopIconsPlus or Pomodoro stops the crashes. It's not necessary to disable both. Are they competing for a resource? They are both on the top-right corner. I'll have to run it for longer to confirm that this isn't a statistical fluke. I do plan to do so. Note: Pomodoro depends on a helper app /usr/bin/gnome-pomodoro that doesn't stop when you disable the extensions. You may need to logout/login.
(In reply to Berend De Schouwer from comment #83) > I'll have to run it for longer to confirm that this isn't a statistical > fluke. I do plan to do so. So it was a statistical fluke :) It also crashes with only pomodoro.
Possible related: https://github.com/codito/gnome-pomodoro/issues/314
(In reply to Berend De Schouwer from comment #84) > (In reply to Berend De Schouwer from comment #83) > > I'll have to run it for longer to confirm that this isn't a statistical > > fluke. I do plan to do so. > > So it was a statistical fluke :) > > It also crashes with only pomodoro. I started to suspect that it happens to any extension that adds its icon to the GNOME Shell top panel.
I realized I had pomodoro installed so removed it on the 7th. I can't recall a crash since then. I'll pay more attention.
(In reply to Berend De Schouwer from comment #84) > It also crashes with only pomodoro. Definitely sounds like related to pomodoro then. As I wrote before, with topicons (plus) alone or other extensions in the top right corner (like clipboard indicator), gnome-shell is completely stable. A lot of the people who reproduced chrashes here recently had pomodoro installed. The question of course is why can an extension bring down the whole gnome shell? I thought they run in some sort of JavaScript sandbox?
I've had crashes with pomodoro but not topicons, and topicons but not pomodoro. Since disabling both of these, my system has not crashed. I do have other extensions running however, e.g. system-monitor
"The question of course is why can an extension bring down the whole gnome shell? I thought they run in some sort of JavaScript sandbox?" No, there isn't a 'sandbox' (AFAIK). Extensions can hook into the shell in all kinds of ways. A large chunk of the Shell itself is written in Javascript.
I've just had one gnome-shell segfault when pomodoro was definitely not running. Running: - topiconsplus - freon (installed specifically to have another extension that eats panel space) - openweather
I've enabled all extensions (including TopIcons Plus) and disabled Pomodoro. Let's see what happens next?!
*** Bug 1511984 has been marked as a duplicate of this bug. ***
Similar problem has been detected: run dnf update reporter: libreport-2.9.2 backtrace_rating: 3 cmdline: /usr/bin/gnome-shell crash_function: g_type_check_instance_is_fundamentally_a executable: /usr/bin/gnome-shell journald_cursor: s=a08f5da2e5e64785a9921a87c9627436;i=177a3;b=9d43d1ccac324923b2175046e724ba65;m=5d4670a42;t=55da30b179597;x=eff87eee8fee7178 kernel: 4.13.9-300.fc27.x86_64 package: gnome-shell-3.26.1-2.fc27 reason: gnome-shell killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
Similar problem has been detected: Gnome3 crashed and appeared to not be associated with any particular discrete event. reporter: libreport-2.9.2 backtrace_rating: 3 cmdline: /usr/bin/gnome-shell crash_function: g_type_check_instance_is_fundamentally_a executable: /usr/bin/gnome-shell journald_cursor: s=f510075169a34c83810ac479ad376f0c;i=180a0;b=78865cd49ffc4ba7af3f1412ee053a22;m=1d3fd2a315;t=55d8a38b772e9;x=7c037fbfa59407f4 kernel: 4.13.9-300.fc27.x86_64 package: gnome-shell-3.26.1-2.fc27 reason: gnome-shell killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
*** Bug 1512692 has been marked as a duplicate of this bug. ***
re-enabling pomodoro definitely increases crashes frequency (multiple times per day vs. once every three days.) Should the component change?
Similar problem has been detected: Just log in and click control(?) menu - wanted to restart - than crash reporter: libreport-2.9.3 backtrace_rating: 3 cmdline: /usr/bin/gnome-shell crash_function: g_type_check_instance_is_fundamentally_a executable: /usr/bin/gnome-shell journald_cursor: s=77d908ac7e0047c088e5c5c70d2f0a70;i=55ad7;b=11a255cc39854c77bdaccfa70f00e59e;m=499075a;t=55df48a9f4c0b;x=6e49e7394c763f21 kernel: 4.13.12-300.fc27.x86_64 package: gnome-shell-3.26.2-1.fc27 reason: gnome-shell killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
I disabled Pomodoro last week and I haven't had a GNOME crash since.
*** Bug 1513253 has been marked as a duplicate of this bug. ***
I also had Pomodoro enabled. Disabling it now to see if it helps.
Similar problem has been detected: Switched from Files to Slack Desktop App. Files on 2nd screen and Slack on 3rd. All of that may or may not be useful. reporter: libreport-2.9.3 backtrace_rating: 3 cmdline: /usr/bin/gnome-shell crash_function: g_type_check_instance_is_fundamentally_a executable: /usr/bin/gnome-shell journald_cursor: s=0a751592111f41fca9e092b1d281d5d4;i=1e717;b=75f005cb737f456e88902587c791575f;m=170fd0378f;t=55e0bd350d8e3;x=70f4efa2821396b9 kernel: 4.13.12-300.fc27.x86_64 package: gnome-shell-3.26.2-1.fc27 reason: gnome-shell killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
Similar problem has been detected: Crash on login after reboot. reporter: libreport-2.9.3 backtrace_rating: 4 cmdline: /usr/bin/gnome-shell crash_function: g_type_check_instance_is_fundamentally_a executable: /usr/bin/gnome-shell journald_cursor: s=641819a56db04ff0805a1e6416de1235;i=268423;b=7e21cb939f0e47caa5cbb254c8dcbdc7;m=2a0b755;t=55e0bee41b38d;x=7fbb2e86b07ed85c kernel: 4.13.12-300.fc27.x86_64 package: gnome-shell-3.26.2-1.fc27 reason: gnome-shell killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
"Should the component change?" Well, I don't think we have the pomodoro extension packaged. But it would definitely be a good idea to report this to the upstream tracker for the pomodoro extension, assuming it has one and this has not already been reported.
(In reply to Adam Williamson from comment #104) > "Should the component change?" > > Well, I don't think we have the pomodoro extension packaged. But it would > definitely be a good idea to report this to the upstream tracker for the > pomodoro extension, assuming it has one and this has not already been > reported. There is an upstream report (comment 85) See also: Name : gnome-shell-extension-pomodoro Version : 0.13.3 Release : 1.fc27 Architecture: x86_64 Install Date: Wed 04 Oct 2017 14:06:20 SAST Group : Unspecified Size : 7181355 License : GPLv3+ Signature : RSA/SHA256, Fri 22 Sep 2017 14:41:20 SAST, Key ID f55e7430f5282ee4 Source RPM : gnome-shell-extension-pomodoro-0.13.3-1.fc27.src.rpm Build Date : Fri 22 Sep 2017 14:29:36 SAST Build Host : buildvm-08.phx2.fedoraproject.org Relocations : (not relocatable) Packager : Fedora Project Vendor : Fedora Project URL : http://gnomepomodoro.org/ Summary : A time management utility for GNOME Description : This GNOME utility helps to manage time according to Pomodoro Technique. It intends to improve productivity and focus by taking short breaks.
I disabled pomodoro awhile ago. It is much more stable. However I think I had one crash while pomodoro was uninstalled. Better than one or two a day. I should also point out I had pomodoro installed but wasn't using it.
*** Bug 1514243 has been marked as a duplicate of this bug. ***
*** Bug 1514322 has been marked as a duplicate of this bug. ***
Similar problem has been detected: Session was locked I had to Input my password twice, because it showed lockscreen again after first unlock. After second unlock whole session crashed thought it was Xorg session. reporter: libreport-2.9.3 backtrace_rating: 4 cmdline: /usr/bin/gnome-shell crash_function: g_type_check_instance_is_fundamentally_a executable: /usr/bin/gnome-shell journald_cursor: s=641819a56db04ff0805a1e6416de1235;i=26cc10;b=d8fb52bc3d4a43e782f58c13a53f098f;m=8f71b4dcf;t=55e2bbeea2d12;x=d250aa67cbeb8cb3 kernel: 4.13.12-300.fc27.x86_64 package: gnome-shell-3.26.2-1.fc27 reason: gnome-shell killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
Similar problem has been detected: Was just launching virt-manager for the first time, Although this appears to happen on lots of actions and seems to be when using gnome shell on wayland reporter: libreport-2.9.2 backtrace_rating: 3 cmdline: /usr/bin/gnome-shell crash_function: g_type_check_instance_is_fundamentally_a executable: /usr/bin/gnome-shell journald_cursor: s=5ff197a9a5644d4983c34cf08c957771;i=d88;b=9158966107e74dd7a946f570bfd90cc7;m=1763bd713;t=55e2c6c4e1f8d;x=f7c0093084bb8e36 kernel: 4.13.9-300.fc27.x86_64 package: gnome-shell-3.26.1-1.fc27 reason: gnome-shell killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
*** Bug 1514735 has been marked as a duplicate of this bug. ***
*** Bug 1514789 has been marked as a duplicate of this bug. ***
*** Bug 1514855 has been marked as a duplicate of this bug. ***
*** Bug 1515135 has been marked as a duplicate of this bug. ***
Looks like last pomodoro update fixed the issue for me.
*** Bug 1515390 has been marked as a duplicate of this bug. ***
*** Bug 1515491 has been marked as a duplicate of this bug. ***
I don't have Pomodoro installed and still experience multiple crashes per day.
*** Bug 1515515 has been marked as a duplicate of this bug. ***
(In reply to Viktor from comment #115) > Looks like last pomodoro update fixed the issue for me. Version 0.13.3 or 0.13.4? Gnome-shell version?
(In reply to George Sapkin from comment #118) > I don't have Pomodoro installed and still experience multiple crashes per > day. Any other extensions?
Upstream bug https://github.com/codito/gnome-pomodoro/issues/320 is reported fixed with 0.13.4. I tried to submit a Bodhi build request, but I *think* that failed. Can anyone that's CC-ed submit it?
I am using the Pomodoro and TopIcons Plus extentions for the Gnome Shell.
Similar problem has been detected: I opened FeedReader, clicked on Local RSS and gnome crashed. FeedReader used to only crash itself before when I tried clicking on Local RSS, it seems the problem is now more severe. reporter: libreport-2.9.3 backtrace_rating: 4 cmdline: /usr/bin/gnome-shell crash_function: g_type_check_instance_is_fundamentally_a executable: /usr/bin/gnome-shell journald_cursor: s=890623c7e3fa421d80dfbb0dbf8e8b83;i=44018;b=37f6eda5e8ad481b993eb4614078dd56;m=186f4989a;t=55e805fc93d13;x=79173b606268e924 kernel: 4.13.13-300.fc27.x86_64 package: gnome-shell-3.26.2-1.fc27 reason: gnome-shell killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
*** Bug 1515988 has been marked as a duplicate of this bug. ***
(In reply to Berend De Schouwer from comment #120) > (In reply to Viktor from comment #115) > > Looks like last pomodoro update fixed the issue for me. > > Version 0.13.3 or 0.13.4? > > Gnome-shell version? Fedora 27 pomodoro 0.13.4 GNOME Shell 3.26.2 2 days without any problems
(In reply to Berend De Schouwer from comment #121) > (In reply to George Sapkin from comment #118) > > Any other extensions? Looks like disabling most extensions made it stable. I'm trying to enable them one by one to see if I can isolate this reliably. So far Dash to Dock seems like one of the culprits.
It seems to be related to notifications rather than a particular extension. I get crashes from the mpdris extension too, for example. It could be limited to notifications generated by extensions, but I haven't been able to check that bit reliably yet. Using the DND extension to disable notification seems to prevent crashes, but since the crashes do not happen each time anyway, I can't yet be certain.
Mat Booth has kindly built a later Pomodoro on Bodhi: https://bodhi.fedoraproject.org/updates/FEDORA-2017-9103272c93 (f26) https://bodhi.fedoraproject.org/updates/FEDORA-2017-337c3be857 (f27) Try it out and leave some karma. Be sure to logout/login since it leaves a process hanging. If you haven't got Pomodoro installed, try and find out which other extensions cause this. Note that some extensions need a logout/login.
(In reply to Ankur Sinha (FranciscoD) from comment #128) > It seems to be related to notifications rather than a particular extension. > I get crashes from the mpdris extension too, for example. It could be > limited to notifications generated by extensions, but I haven't been able to > check that bit reliably yet. gnome-shell 3.26 now has mpdris built in (under the calendar/main notification) so you might want to try that instead of an add-on extension.
*** Bug 1516635 has been marked as a duplicate of this bug. ***
*** Bug 1516797 has been marked as a duplicate of this bug. ***
Similar problem has been detected: Clicked on a window bar of a terminal. Old laptop, second screen connected via VGA cable. reporter: libreport-2.9.3 backtrace_rating: 4 cmdline: /usr/bin/gnome-shell crash_function: g_type_check_instance_is_fundamentally_a executable: /usr/bin/gnome-shell journald_cursor: s=8ae93118f8f9412d9920ee2f92eb5e7b;i=2f2b7;b=3408fa147c314d3db501510231d019c5;m=4d7e9841c;t=55ea5b96b3340;x=a709479bf53f4fd5 kernel: 4.13.13-300.fc27.x86_64 package: gnome-shell-3.26.2-1.fc27 reason: gnome-shell killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
Similar problem has been detected: On thinkpad T460s, open lid to wake up from sleep. Enter credentials to get back into gnome session. Previous session is revealed for a brief moment then gnome crashes. Screen returns to login. reporter: libreport-2.9.3 backtrace_rating: 3 cmdline: /usr/bin/gnome-shell crash_function: g_type_check_instance_is_fundamentally_a executable: /usr/bin/gnome-shell journald_cursor: s=c1e22546dd79409f82e4785277599146;i=1579;b=bfbdcb0f1b464967ae7ae38bf7736b0f;m=2a4002b75;t=55eab337a79a7;x=1d680c8ca3f2e3f7 kernel: 4.13.13-300.fc27.x86_64 package: gnome-shell-3.26.2-1.fc27 reason: gnome-shell killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
Similar problem has been detected: Using Thunderbird in Fedora 27 causes either xwayland or gnome-shell to crash. reporter: libreport-2.9.3 backtrace_rating: 4 cmdline: /usr/bin/gnome-shell crash_function: g_type_check_instance_is_fundamentally_a executable: /usr/bin/gnome-shell journald_cursor: s=ffeeea0a1d04494f8377576163d8911a;i=ddb66;b=00fd472eee424da6b286ff30cad33cf5;m=3aa34706f9;t=55eb6774e196d;x=45b00f0411d2948f kernel: 4.13.13-300.fc27.x86_64 package: gnome-shell-3.26.2-1.fc27 reason: gnome-shell killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
A feedback. I deactivated all the gnome-shell extensions I had added, such as alternate tab and pomodoro. I only kept the "dash to dock" extension enabled. Everything seems to turn well now, I have not received any crashes.
Similar problem has been detected: I believe notifications are killing gnome-shell, wayland, etc, among other critical UI supporting services. reporter: libreport-2.9.3 backtrace_rating: 4 cmdline: /usr/bin/gnome-shell crash_function: g_type_check_instance_is_fundamentally_a executable: /usr/bin/gnome-shell journald_cursor: s=890623c7e3fa421d80dfbb0dbf8e8b83;i=46406;b=0e46d6cc1b1249c8a1bf4cce0aeacf7f;m=381f47ba9;t=55ebd96572a3f;x=f54f14e04aca49f9 kernel: 4.13.13-300.fc27.x86_64 package: gnome-shell-3.26.2-1.fc27 reason: gnome-shell killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
*** Bug 1517471 has been marked as a duplicate of this bug. ***
Similar problem has been detected: I tried to play a song in the Spotify App. reporter: libreport-2.9.3 backtrace_rating: 4 cmdline: /usr/bin/gnome-shell crash_function: g_type_check_instance_is_fundamentally_a executable: /usr/bin/gnome-shell journald_cursor: s=890623c7e3fa421d80dfbb0dbf8e8b83;i=47cbe;b=0e46d6cc1b1249c8a1bf4cce0aeacf7f;m=b2b9c160d;t=55ed5d725ac4d;x=eb4fe7f507096c45 kernel: 4.13.13-300.fc27.x86_64 package: gnome-shell-3.26.2-1.fc27 reason: gnome-shell killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
Similar problem has been detected: Clicked on a liferea link to open it in the browser (Firefox). The shell crashed immediately after that. reporter: libreport-2.9.3 backtrace_rating: 3 cmdline: /usr/bin/gnome-shell crash_function: g_type_check_instance_is_fundamentally_a executable: /usr/bin/gnome-shell journald_cursor: s=65a48a09af28426d85244563a1460abe;i=1f260;b=9b4cc11d9dce42ca98a39a752439e3b6;m=88af2cbf;t=55ed6eac6019d;x=92e1407c02f5c976 kernel: 4.13.15-300.fc27.x86_64 package: gnome-shell-3.26.2-1.fc27 reason: gnome-shell killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
*** Bug 1518643 has been marked as a duplicate of this bug. ***
Similar problem has been detected: This particular crash happened after right-clicking on an app icon in the Dash, and clicking on Remove from Favorites. Similar crashes happen usually on or after opening a shell popup, the other day opening the Notifications caused it. reporter: libreport-2.9.3 backtrace_rating: 3 cmdline: /usr/bin/gnome-shell crash_function: g_type_check_instance_is_fundamentally_a executable: /usr/bin/gnome-shell journald_cursor: s=3c0f1a7caf8e424d9cbe7f323cb0f6e3;i=1198b;b=5bcbd00e794c442f8d950f209a13523a;m=46dda8421;t=55f9902d1a5d0;x=111336afbd599f8 kernel: 4.13.15-300.fc27.x86_64 package: gnome-shell-3.26.2-1.fc27 reason: gnome-shell killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
Similar problem has been detected: I hit it multiple times, when clicking on time on the gnome desktop I use 2 monitors, when switching between them, I hit this crash How to reproduce. In my environment, I have a external display for my laptop. I turn off my laptop display while I am working on the external display. With this environment in place, I am seeing this problem atleast 2 times a day. reporter: libreport-2.9.3 backtrace_rating: 3 cmdline: /usr/bin/gnome-shell crash_function: g_type_check_instance_is_fundamentally_a executable: /usr/bin/gnome-shell journald_cursor: s=34e8ef2f8c52444bb6f9134d720140cb;i=b96;b=db0ea552d1c346718f189d5af2d65adb;m=7b0f406a;t=560e458451b17;x=b09b183a489f4063 kernel: 4.13.13-300.fc27.x86_64 package: gnome-shell-3.26.2-1.fc27 reason: gnome-shell killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
Same problem Happened twice when logging into shell from lock screen. Fedora 28 Gnome 3.28.2 Jun 12 16:25:28 localhost.localdomain abrt-notification[20790]: Process 1760 (gnome-shell) crashed in g_type_check_instance_is_fundamentally_a() Jun 12 16:25:28 localhost.localdomain gnome-shell[1016]: Object Clutter.Clone (0x56239e96ea80), has been already finalized. Impossible to get any property from it. Jun 12 16:25:20 localhost.localdomain systemd-coredump[20510]: Process 1760 (gnome-shell) of user 1000 dumped core. Stack trace of thread 1760: #0 0x00007f42524d73d3 g_type_check_instance_is_fundamentally_a (libgobject-2.0.so.0) #1 0x00007f42524b7987 g_object_ref (libgobject-2.0.so.0) #2 0x00007f424fbfcb05 st_theme_get_custom_stylesheets (libst-1.0.so) #3 0x00007f424ceff03e ffi_call_unix64 (libffi.so.6) #4 0x00007f424cefe9ff ffi_call (libffi.so.6) #5 0x00007f4251198321 n/a (libgjs.so.0) #6 0x00007f42511999e8 n/a (libgjs.so.0) #7 0x00007f424876aae5 n/a (libmozjs-52.so.0) #8 0x00007f4248764e2a n/a (libmozjs-52.so.0) #9 0x00007f424876a55d n/a (libmozjs-52.so.0) #10 0x00007f424876a92a n/a (libmozjs-52.so.0) #11 0x00007f424876ac0d n/a (libmozjs-52.so.0) #12 0x00007f4248556e85 n/a (libmozjs-52.so.0) #13 0x00000ae2d73e43c6 n/a (n/a) #14 0x00007f424847267d n/a (libmozjs-52.so.0) #15 0x00007f4248769ae2 n/a (libmozjs-52.so.0) #16 0x00007f424876a55d n/a (libmozjs-52.so.0) #17 0x00007f424876a92a n/a (libmozjs-52.so.0) #18 0x00007f424876ac0d n/a (libmozjs-52.so.0) #19 0x00007f42485f7e18 _Z20JS_CallFunctionValueP9JSContextN2JS6HandleIP8JSObjectEENS2_INS1_5ValueEEERKNS1_16> #20 0x00007f42511bc0f4 gjs_call_function_value (libgjs.so.0) #21 0x00007f42511931f1 gjs_closure_invoke (libgjs.so.0) #22 0x00007f42511b01ee n/a (libgjs.so.0) #23 0x00007f42524b2add g_closure_invoke (libgobject-2.0.so.0) #24 0x00007f42524cfed0 n/a (libgobject-2.0.so.0) #25 0x00007f42521d41cb n/a (libglib-2.0.so.0) #26 0x00007f42521d78ad g_main_context_dispatch (libglib-2.0.so.0) #27 0x00007f42521d7c78 n/a (libglib-2.0.so.0) #28 0x00007f42521d7fa2 g_main_loop_run (libglib-2.0.so.0) #29 0x00007f42506bdde0 meta_run (libmutter-2.so.0) #30 0x000055d3874bb4d8 n/a (gnome-shell) #31 0x00007f425005318b __libc_start_main (libc.so.6) #32 0x000055d3874bb62a n/a (gnome-shell)
This message is a reminder that Fedora 27 is nearing its end of life. On 2018-Nov-30 Fedora will stop maintaining and issuing updates for Fedora 27. 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 '27'. 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 27 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.
Fedora 27 changed to end-of-life (EOL) status on 2018-11-30. Fedora 27 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.