Version-Release number of selected component: gnome-shell-3.25.3-1.fc27 Additional info: reporter: libreport-2.9.1 backtrace_rating: 3 cmdline: /usr/bin/gnome-shell crash_function: g_type_check_instance_cast executable: /usr/bin/gnome-shell journald_cursor: s=e1bd67538d274b379c4f9364f9ea161f;i=56c8;b=b58657aba7684b0e99d31d9adcb4f9d6;m=2ba85a530;t=553f5c2cf2ead;x=d1bda9180343793d kernel: 4.12.0-1.fc27.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 g_type_check_instance_cast at gtype.c:4057 #1 st_label_set_text at st/st-label.c:331 #2 object_set_property at gobject.c:1423 #3 g_object_setv at gobject.c:2229 #4 g_object_set_property at gobject.c:2513 #5 set_g_param_from_prop at gi/object.cpp:448 #6 object_instance_set_prop at gi/object.cpp:527 #7 js::CallJSPropertyOpSetter at /usr/src/debug/mozilla-esr38/js/src/jscntxtinlines.h:310 #8 js::Shape::set at /usr/src/debug/mozilla-esr38/js/src/vm/Shape-inl.h:62 #9 NativeSet at /usr/src/debug/mozilla-esr38/js/src/vm/NativeObject.cpp:2154
Created attachment 1295801 [details] File: backtrace
Created attachment 1295802 [details] File: cgroup
Created attachment 1295803 [details] File: core_backtrace
Created attachment 1295804 [details] File: cpuinfo
Created attachment 1295805 [details] File: dso_list
Created attachment 1295806 [details] File: environ
Created attachment 1295807 [details] File: exploitable
Created attachment 1295808 [details] File: limits
Created attachment 1295809 [details] File: maps
Created attachment 1295810 [details] File: open_fds
Created attachment 1295811 [details] File: proc_pid_status
Created attachment 1295812 [details] File: var_log_messages
This bug appears to have been reported against 'rawhide' during the Fedora 27 development cycle. Changing version to '27'.
*** Bug 1489784 has been marked as a duplicate of this bug. ***
Similar problem has been detected: Input on lock-screen -> gnome-shell crashes. reporter: libreport-2.9.2 backtrace_rating: 4 cmdline: /usr/bin/gnome-shell crash_function: g_type_check_instance_cast executable: /usr/bin/gnome-shell journald_cursor: s=39e8bb7d91064fe6ab09b4318eeceeda;i=13c494;b=3d7baf0194384913b893509117442e57;m=85ab422c0;t=559ecf22d4f63;x=5dbab8dbabe3cc6d 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
Created attachment 1330305 [details] File: backtrace
Similar problem has been detected: Looks like Gnome-Shell crashed after screen had been switched off due to inactivity time-out. reporter: libreport-2.9.2 backtrace_rating: 3 cmdline: /usr/bin/gnome-shell crash_function: g_type_check_instance_cast executable: /usr/bin/gnome-shell journald_cursor: s=db7456fcb7bc46659d47bba6796c3df1;i=110897b;b=6af5122c029e4ff4b8fc62abf6d32803;m=2f164697;t=559fcf5aa1be0;x=1a005429158ea425 kernel: 4.13.3-300.fc27.x86_64 package: gnome-shell-3.26.0-2.fc27 reason: gnome-shell killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
Similar problem has been detected: Failed after a mouse movement while screen was switched off due to inactivity timeout. reporter: libreport-2.9.2 backtrace_rating: 3 cmdline: /usr/bin/gnome-shell crash_function: g_type_check_instance_cast executable: /usr/bin/gnome-shell journald_cursor: s=db7456fcb7bc46659d47bba6796c3df1;i=110ab20;b=6af5122c029e4ff4b8fc62abf6d32803;m=1aadeaf13;t=559fe7172845c;x=2dd1bd6044fb5529 kernel: 4.13.3-300.fc27.x86_64 package: gnome-shell-3.26.0-2.fc27 reason: gnome-shell killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
Similar problem has been detected: Used dconf Editor to reset settings in /desktop/ reporter: libreport-2.9.2 backtrace_rating: 4 cmdline: /usr/bin/gnome-shell crash_function: g_type_check_instance_cast executable: /usr/bin/gnome-shell journald_cursor: s=3d45c74a2b5e42bfbc78cd984d66938b;i=60f21;b=214a76bfbb9046e682446f2844f4ab9a;m=2ef9017c;t=55a084d10ec68;x=bb8fa6138e6be077 kernel: 4.13.0-rc5+ 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: 1Boot system 2login user 3Use browser 4Let autotimeout lock user 5Relog after 30 minutes with incorrect password (typing error) 6Login with good password 7 GnomeshellCrash note 8 Prepare this report Filesystem is lvm reporter: libreport-2.9.2 backtrace_rating: 4 cmdline: /usr/bin/gnome-shell crash_function: g_type_check_instance_cast executable: /usr/bin/gnome-shell journald_cursor: s=407a30b03a6440b9858d96d9cf808e99;i=23cb;b=3e0e455f1a344c3dac7733664c967089;m=897a9d85e;t=55a3fee688242;x=eecbbd0f1726a319 kernel: 4.13.3-301.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: was logged off, after having executed sudo dnf update then returned to log into system (yes, with btrfs file system) Gnome-shell crashed and now this report. Software wise, I know not why reporter: libreport-2.9.2 backtrace_rating: 4 cmdline: /usr/bin/gnome-shell crash_function: g_type_check_instance_cast executable: /usr/bin/gnome-shell journald_cursor: s=13f42cfdd1d640b381c5413951c9ae50;i=9148;b=a53e0748ac5f4cb0a8d9afa3dc26b4f3;m=3b91949a;t=55a4934e3bbcd;x=603d2f313fb066e0 kernel: 4.13.3-301.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: It seems to occur frequently when the Firefox windows is activated. reporter: libreport-2.9.2 backtrace_rating: 4 cmdline: /usr/bin/gnome-shell crash_function: g_type_check_instance_cast executable: /usr/bin/gnome-shell journald_cursor: s=f8abd916041f40d1819fbeadfe641150;i=cdda;b=70819a29f270496fa86509bc1298afad;m=44323e91d;t=55ae3b6aa1e8c;x=6de4bc4405a18418 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
*** Bug 1499383 has been marked as a duplicate of this bug. ***
Similar problem has been detected: installed gnome-radio extension. Could no longer continue. When I opened the login after password, lost the mouse, keyboard and monitor. However, a background download was operating (disk light blinking). Only recourse, --reboot. reporter: libreport-2.9.2 backtrace_rating: 4 cmdline: /usr/bin/gnome-shell crash_function: g_type_check_instance_cast executable: /usr/bin/gnome-shell journald_cursor: s=513a884a4e3749c1a2731c08365cabe6;i=186d;b=d7a913fe44974cc3a2afa61118f88da1;m=754825c;t=55aeb9b488083;x=79f7005ad96745d3 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: First Login after reboot reporter: libreport-2.9.2 backtrace_rating: 4 cmdline: /usr/bin/gnome-shell crash_function: g_type_check_instance_cast executable: /usr/bin/gnome-shell journald_cursor: s=381fc9ffe2404d2180fef759d664a291;i=4a75;b=ca6a52a1167a4764b01bee7f94ccb0ba;m=ff78034;t=55af763ed8c40;x=6fd6ad89d499823e 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: The crash happened after login. reporter: libreport-2.9.2 backtrace_rating: 3 cmdline: /usr/bin/gnome-shell crash_function: g_type_check_instance_cast executable: /usr/bin/gnome-shell journald_cursor: s=f8abd916041f40d1819fbeadfe641150;i=13d1a;b=4e087b4251d247d9bdd1a21cb9468a38;m=4b353c5a;t=55b3fab6e2255;x=a022f5b65b4a8d27 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: Crashed as soon as I logged in. This happened a second time as well. On the third attempt I was able to log in. reporter: libreport-2.9.2 backtrace_rating: 4 cmdline: /usr/bin/gnome-shell crash_function: g_type_check_instance_cast executable: /usr/bin/gnome-shell journald_cursor: s=ffd1fcb7f7e246809945573038370d87;i=5586bb5;b=44634868fe4740e79c16f7a6a06fbfb0;m=156fde0fc;t=55b4208911d93;x=f0d2548e497643a8 kernel: 4.12.9-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: Input on lock-screen -> gnome-shell crashes 1. Launch apps ( gnome-terminal, firefox, chromium ) 2. Super key + L 3. Input reporter: libreport-2.9.2 backtrace_rating: 4 cmdline: /usr/bin/gnome-shell crash_function: g_type_check_instance_cast executable: /usr/bin/gnome-shell journald_cursor: s=39e8bb7d91064fe6ab09b4318eeceeda;i=1519fe;b=e06e1aa70f474509b262e38abf6c8a0b;m=a96c98d;t=55b4de37496df;x=698a2ee81e342895 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: Crash uppon login. reporter: libreport-2.9.2 backtrace_rating: 4 cmdline: /usr/bin/gnome-shell crash_function: g_type_check_instance_cast executable: /usr/bin/gnome-shell journald_cursor: s=ffd1fcb7f7e246809945573038370d87;i=5587cda;b=44634868fe4740e79c16f7a6a06fbfb0;m=428920af9;t=55b44da254791;x=1b593d2a207b2605 kernel: 4.12.9-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 logged in after a fresh reboot, session immediately crashed. The following login was fine. reporter: libreport-2.9.2 backtrace_rating: 4 cmdline: /usr/bin/gnome-shell crash_function: g_type_check_instance_cast executable: /usr/bin/gnome-shell journald_cursor: s=2ff631a66afd403d8e8fe0a534e20e41;i=1080a5;b=821591fdcb8244dca4aceaae4c3076df;m=28b9b4c;t=55b4cf2f15e51;x=9ae990dfa7642906 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: logging into desktop after powerup reporter: libreport-2.9.2 backtrace_rating: 3 cmdline: /usr/bin/gnome-shell crash_function: g_type_check_instance_cast executable: /usr/bin/gnome-shell journald_cursor: s=f1f65ceb95b24819993eec52eb9348c4;i=128c42;b=d22922f980694f2998e1edc764927bc3;m=3f2e88b;t=55be2e9b13f26;x=1c48013bb0f1d7ca 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
*** Bug 1504154 has been marked as a duplicate of this bug. ***
Similar problem has been detected: browsering using Firefox, clicked a link with the mouse and Gnome crashed. Gnome has crashed multiple times since updating to Kernel 4.13.8 reporter: libreport-2.9.2 backtrace_rating: 3 cmdline: /usr/bin/gnome-shell crash_function: g_type_check_instance_cast executable: /usr/bin/gnome-shell journald_cursor: s=1a791cd0e0e84a698dbedc65db7103cf;i=6481;b=89891cf60da248779d905b54f2cfb090;m=190b185d8;t=55bf3b458f0b7;x=d9b7ab14e6f18ce0 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: I was about to update an extension (OpenWeather) via Chrome. reporter: libreport-2.9.2 backtrace_rating: 4 cmdline: /usr/bin/gnome-shell crash_function: g_type_check_instance_cast executable: /usr/bin/gnome-shell journald_cursor: s=0d60703ecda54602bf85f51c567ac5f5;i=b9a5;b=22b70aa7e5774610b334f3d32829c96f;m=44141bdc5;t=55c4a257a29a1;x=9b1ed538a7bc2190 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: I've noticed this happens quite a bit. Typically it will happen when I'm signed into my account and have several applications open (on a typical day it's Rambox, Pidgin, Thunderbird, Google Chrome, and several xterms) and I lock my screen to step away for a moment. When I come back, I go to log back in, but I'm presented with a new login that creates a new session. When I get logged back in, I'm given a "Gnome Crashed" notification. It's not always and not consistent, I don't know how to recreate the issue. reporter: libreport-2.9.2 backtrace_rating: 3 cmdline: /usr/bin/gnome-shell crash_function: g_type_check_instance_cast executable: /usr/bin/gnome-shell journald_cursor: s=cf75c2bd03764dbc8f46b1eaaa04a500;i=5fd241;b=08d2f73ceb2e483a8fec20e78481ef06;m=14ed92a577;t=55c6111db7533;x=33c953c21cc7448c 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: using the desktop reporter: libreport-2.9.2 backtrace_rating: 4 cmdline: /usr/bin/gnome-shell crash_function: g_type_check_instance_cast executable: /usr/bin/gnome-shell journald_cursor: s=a71a9453ab40440197d1c7bf5bff41e8;i=cd3;b=6b1dc1cd6661410095d0d355c93030b5;m=2b754b4;t=55c6219661aeb;x=26af61e086d68a98 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: Logging in reporter: libreport-2.9.2 backtrace_rating: 3 cmdline: /usr/bin/gnome-shell crash_function: g_type_check_instance_cast executable: /usr/bin/gnome-shell journald_cursor: s=f1f65ceb95b24819993eec52eb9348c4;i=135b07;b=a3aa261378be490f8cebf0e39a34e254;m=7352a73;t=55c8e555299ad;x=469e2e6e8523c43e 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 1507572 has been marked as a duplicate of this bug. ***
Similar problem has been detected: crashed when logging in bringing out of suspend reporter: libreport-2.9.2 backtrace_rating: 3 cmdline: /usr/bin/gnome-shell crash_function: g_type_check_instance_cast executable: /usr/bin/gnome-shell journald_cursor: s=41ac3691c3354df5b9074d7a687af9ec;i=ce86;b=73ac6aafd11a41ff8315830028be9838;m=4b82d6177;t=55ccc5b811f72;x=303a4e92d5690bba 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 1507789 has been marked as a duplicate of this bug. ***
The crash has occurred several times after: 1. USB plugs in. 2. Login after resuming from sleep. 3. New Bluetooth connection. Note that I'm using Btrfs.
*** Bug 1507983 has been marked as a duplicate of this bug. ***
Similar problem has been detected: Steps: 1. Fresh installation of Fedora 27 beta1. 2. Click to open a LUKS encrypted partition in Nautilus. (for me this partition is located in a usb hard drive) Current Behaviour: Crash. reporter: libreport-2.9.2 backtrace_rating: 3 cmdline: /usr/bin/gnome-shell crash_function: g_type_check_instance_cast executable: /usr/bin/gnome-shell journald_cursor: s=5667cf2b4d17457b9050c4664780980a;i=28e1;b=82b33b542f0e4d91a468574fb0931a8d;m=2613e8eb;t=55cd44990eefd;x=430a0ee1c2353c4e 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 1508320 has been marked as a duplicate of this bug. ***
Similar problem has been detected: First power-on logon reporter: libreport-2.9.2 backtrace_rating: 3 cmdline: /usr/bin/gnome-shell crash_function: g_type_check_instance_cast executable: /usr/bin/gnome-shell journald_cursor: s=f8599e7f88644b79a4bef5f25d1eacb4;i=18fea;b=44b49d0c1cd746fbb461db2ffd8ed14e;m=2f3e166e;t=55cebc2cdbcfe;x=cfb1c81630bf8c6e 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: Powered on, started Gparted. During execution of gparted, (xorg ) Shell crashed, taking gparted with it. reporter: libreport-2.9.2 backtrace_rating: 3 cmdline: /usr/bin/gnome-shell crash_function: g_type_check_instance_cast executable: /usr/bin/gnome-shell journald_cursor: s=513d500c948a4fde9a588fec333f9dd5;i=e239;b=25ee6f946e6f4b508e873a718daf1326;m=2640fbb5;t=55cf0105c9745;x=479a8b1214d201e4 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 am using /home as a btrfs file system. The gnome version is as listed If I replace /home with a /ext4 file system or embedded within lvm or xfs everything works. If I know why gnome-shell does not like btrfs, I would know the cause of the problem reporter: libreport-2.9.2 backtrace_rating: 3 cmdline: /usr/bin/gnome-shell crash_function: g_type_check_instance_cast executable: /usr/bin/gnome-shell journald_cursor: s=f8599e7f88644b79a4bef5f25d1eacb4;i=1fedd;b=91f704e19bb74ec493c2efd61ed9a707;m=4d17ee0;t=55d203b6ecbdc;x=3cd04d0bd966c6 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: Gnome-shell crashed just after I have tried to logi back in. reporter: libreport-2.9.2 backtrace_rating: 3 cmdline: /usr/bin/gnome-shell crash_function: g_type_check_instance_cast executable: /usr/bin/gnome-shell journald_cursor: s=45963494ef5e46ec9cec47d2a8a1c79c;i=3a739;b=6e124a8abb954ac3ab7015f4cb5ec5aa;m=33293052e;t=55d52d3c0afe7;x=37359b49fd947d4f 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: logging into desktop after turning system on reporter: libreport-2.9.2 backtrace_rating: 3 cmdline: /usr/bin/gnome-shell crash_function: g_type_check_instance_cast executable: /usr/bin/gnome-shell journald_cursor: s=f1f65ceb95b24819993eec52eb9348c4;i=141a04;b=5c7e1d6f96bc42a480bdbda4e472f869;m=43a6c4a;t=55d57a626df17;x=954f0f979f14fc95 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: After I've logged in gnome-shell has crashed. reporter: libreport-2.9.2 backtrace_rating: 3 cmdline: /usr/bin/gnome-shell crash_function: g_type_check_instance_cast executable: /usr/bin/gnome-shell journald_cursor: s=45963494ef5e46ec9cec47d2a8a1c79c;i=3d4e8;b=6e124a8abb954ac3ab7015f4cb5ec5aa;m=6de17956d;t=55d62da552292;x=4cb4f314274d5dfe 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: Red Hat Bugzilla – Bug 1464294 Read my operational debugging. reporter: libreport-2.9.3 backtrace_rating: 3 cmdline: /usr/bin/gnome-shell crash_function: g_type_check_instance_cast executable: /usr/bin/gnome-shell journald_cursor: s=188b6376635e4b05bd330fbbd1710c2e;i=b083;b=ea30ecffad5b427b9520188455eeb258;m=e25fe30;t=55d7d378f3ce5;x=60d614b8fe88a6bf kernel: 4.13.11-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: It happened while running sudo dnf update reporter: libreport-2.9.2 backtrace_rating: 3 cmdline: /usr/bin/gnome-shell crash_function: g_type_check_instance_cast executable: /usr/bin/gnome-shell journald_cursor: s=a08f5da2e5e64785a9921a87c9627436;i=f091;b=bf667fa6287a457988a2742df5d47b50;m=2751d8d32;t=55d7ecd4311f8;x=8cc716a0be50a6e0 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
Proposed as a Blocker for 27-final by Fedora user superdanby using the blocker tracking app because: Using btrfs makes Gnome crash on several occasions. This is a violation of default panel functionality.
*** Bug 1511470 has been marked as a duplicate of this bug. ***
*** Bug 1511474 has been marked as a duplicate of this bug. ***
-1 blocker. I don't like crashes, but this looks like the previous situation where we have a number of different bugs from different causes getting lumped into one, making it look like one big severe problem when really there are probably many different causes.
Well, in this case the backtraces do look more similar to me. Several of the system logs show something like: Jul 10 15:31:04 localhost.localdomain gnome-shell[1451]: g_value_set_object: assertion 'G_IS_OBJECT (v_object)' failed also. To ask some standard questions: does anyone have a reliable reproducer for this? And can affected folks say whether they have any extensions enabled?
Marking as CommonBugs...note the intent here is to add an entry covering this and several other crasher bugs, noting that we aren't yet clear on precisely what circumstances are known to cause crashes, but anyone experiencing recurring crashes may wish to switch to X11 to mitigate the effect of them.
Bug 1494586 and Bug 1489554 (which are probably duplicates or related, but not sure without usable JS backtrace) seem to indicate that this is at least partially caused by shell extensions, in particular Pomodoro timer.
Note that upstream decided Leslie's case was related to this extension: https://github.com/zpydr/gnome-shell-extension-taskbar Leslie claims it's related to multiple extensions that have settings when using btrfs, but I'm not sure that's proven.
(In reply to Fedora Blocker Bugs Application from comment #53) > Using btrfs makes Gnome crash on several occasions. This is a violation of > default panel functionality. I still doubt this is related to btrfs at all. I don't have any indication why any code path should be different if gnome-shell is running on a machine with btrfs. (In reply to Adam Williamson from comment #57) > To ask some standard questions: does anyone have a reliable reproducer for > this? And can affected folks say whether they have any extensions enabled? Reproducer: No Extensions: Yes, these: https://extensions.gnome.org/extension/7/removable-drive-menu/ https://extensions.gnome.org/extension/650/shade-inactive-windows/ https://extensions.gnome.org/extension/826/suspend-button/ https://extensions.gnome.org/extension/1064/system-monitor/ https://extensions.gnome.org/extension/1031/topicons/ https://extensions.gnome.org/extension/302/windowoverlay-icons/ (In reply to J. Haas from comment #59) > Bug 1494586 and Bug 1489554 (which are probably duplicates or related, but > not sure without usable JS backtrace) seem to indicate that this is at least > partially caused by shell extensions, in particular Pomodoro timer. In my case there is no pomodoro timer (and never has been).
Christian: well, the factors pointing to btrfs so far are: * Either two or three reporters mention that they use it (depends if superdanby is the same person as Leslie or 陳鐸元) * Leslie claims that the crashes only happen when he's using btrfs; if he uses the same extensions but no btrfs, no crashes It'd be good to have more data from more reporters, of course. *Are* you using btrfs, in point of fact?
Discussed at 2017-11-09 Final Go/No-Go meeting, acting as a blocker review meeting: https://meetbot-raw.fedoraproject.org/fedora-meeting-1/2017-11-09/f27-final-and-server-beta-go-no-go-meeting.2017-11-09-18.02.html . Rejected as a blocker: we are concerned about this bug, but it was nominated too late for us to be able to be at all certain it's sufficiently severe and commonly-encountered to constitute a release blocker. We at least know it does not affect any of those in the meeting (many of whom run Shell on F27), and some reports indicate it's not specific to F27 either (it also seems to affect earlier releases). If it does turn out to only affect systems using btrfs in combination with certain extensions, that certainly wouldn't be significant enough to qualify for blocker status.
I have never used btrfs (all of my fs are ext4) and I was experiencing this error. Currently, after disabling most of my extensions, both this one and bug 1494586 happens rarely.
Lukasz: thanks. You say you disabled "most" of your extensions - which ones are still enabled? Can you run without those as well for a bit, and see if crashes still happen at all?
(In reply to Adam Williamson from comment #62) > It'd be good to have more data from more reporters, of course. *Are* you > using btrfs, in point of fact? Yes, I am running my Fedora system on a btrfs partition.
Adam: I am currently using (as I mentioned in the other bug): - Do not disturb button - Kstatusnotifieritem/appindicator support - Topicons (not Plus) - User themes And I didn't have a gnome-shell related crash for over a week till yesterday. When I was testing other extensions yesterday, I got the error from bug 1494586 after disabling Pomodoro and enabling Recent items. However the crash could be caused by interaction between any of these extensions, so it does not prove anything. Before disabling other extensions bug 1494586 was happening multiple times a day and this one every few days. If I can provide more info, please let me know.
As I have said, Fresh installation of Fedora 27 beta1, then Click to open a LUKS encrypted partition in Nautilus. (for me this partition is located in a usb hard drive) will cause the crash. I am not using btrfs. The system is installed in ext4 partition. The LUCKS partition is also ext4.
(In reply to Adam Williamson from comment #57) > Well, in this case the backtraces do look more similar to me. Several of the > system logs show something like: > > Jul 10 15:31:04 localhost.localdomain gnome-shell[1451]: g_value_set_object: > assertion 'G_IS_OBJECT (v_object)' failed > > also. > > To ask some standard questions: does anyone have a reliable reproducer for > this? And can affected folks say whether they have any extensions enabled? Reproducer: No. Extensions enabled: https://extensions.gnome.org/extension/212/advanced-volume-mixer/ https://extensions.gnome.org/extension/15/alternatetab/ https://extensions.gnome.org/extension/6/applications-menu/ https://extensions.gnome.org/extension/1130/dim-desktop-70/ https://extensions.gnome.org/extension/1253/extended-gestures/ https://extensions.gnome.org/extension/1230/gmail-message-tray/ https://extensions.gnome.org/extension/545/hide-top-bar/ https://extensions.gnome.org/extension/600/launch-new-instance/ https://extensions.gnome.org/extension/8/places-status-indicator/ https://extensions.gnome.org/extension/352/middle-click-to-close-in-overview/ https://extensions.gnome.org/extension/905/refresh-wifi-connections/ https://extensions.gnome.org/extension/355/status-area-horizontal-spacing/ https://extensions.gnome.org/extension/826/suspend-button/ https://extensions.gnome.org/extension/120/system-monitor/ https://extensions.gnome.org/extension/570/todotxt/ https://extensions.gnome.org/extension/19/user-themes/ Using these extensions in F26 didn't cause any problem for me. I'll disable them and see if Gnome still crashes. (In reply to Adam Williamson from comment #62) > * Either two or three reporters mention that they use it (depends if > superdanby is the same person as Leslie or 陳鐸元) I'm superdanby. Sorry for making a fuss here. QAQ
The upstream bug has a patch to fix crashes caused by setting the label on invalid StLabel objects.
Please refer to 1464294 for similar (more detailed results of testing) For F27 or F27 beta, I allow / to be on btrfs and /home onto ext4. That works.
Similar problem has been detected: qbittorrent was running in the background and VLC was in the forgroung reporter: libreport-2.9.3 backtrace_rating: 3 cmdline: /usr/bin/gnome-shell crash_function: g_type_check_instance_cast executable: /usr/bin/gnome-shell journald_cursor: s=e6c276588b2f4a9d87303a3a2f621c53;i=37b3;b=5b043518aac44616aa62f1627674797d;m=422cfcf4e;t=55def1dfbbeb2;x=647bb1133630297f kernel: 4.13.11-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 1513505 has been marked as a duplicate of this bug. ***
*** Bug 1513630 has been marked as a duplicate of this bug. ***
*** Bug 1514228 has been marked as a duplicate of this bug. ***
Similar problem has been detected: when input password to login, the desktop crashed. and back to input password, many times may successed login reporter: libreport-2.9.3 backtrace_rating: 3 cmdline: /usr/bin/gnome-shell crash_function: g_type_check_instance_cast executable: /usr/bin/gnome-shell journald_cursor: s=36a08f1e07c144b0918bc34d0120dd51;i=1254b1;b=5323fbc5527e49ceac8e1dff7c414ecc;m=23191c0;t=55e23c49ace71;x=483ca361247b1226 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
*** Bug 1514299 has been marked as a duplicate of this bug. ***
Similar problem has been detected: - Wake the laptop from Hibernation (no front-desk program running) - start shortly after each other: Evolution, Empathy - screen freezes, turns shortly blank, next thing is I had to re-login again. reporter: libreport-2.9.3 backtrace_rating: 3 cmdline: /usr/bin/gnome-shell crash_function: g_type_check_instance_cast executable: /usr/bin/gnome-shell journald_cursor: s=01d0dc94c90e46c89e4dc8a349600c0c;i=52c89;b=d90f55878c30419b8580864a32d37b2e;m=51664a6cb;t=55e256d5f2de3;x=bbe91ad721db4cb1 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
*** Bug 1514452 has been marked as a duplicate of this bug. ***
Similar problem has been detected: My box slept for several hours. It happened when I waked it up. reporter: libreport-2.9.3 backtrace_rating: 3 cmdline: /usr/bin/gnome-shell crash_function: g_type_check_instance_cast executable: /usr/bin/gnome-shell journald_cursor: s=947e232a54144d599e996635ce560362;i=be5bc;b=72369d3c14ce4863b51d10e146aa7f88;m=2d20689ef;t=55e30777af440;x=5169a5b80f0d934a 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
*** Bug 1514757 has been marked as a duplicate of this bug. ***
Similar problem has been detected: Got logged out, while working, with no warning and no reason. reporter: libreport-2.9.3 backtrace_rating: 3 cmdline: /usr/bin/gnome-shell crash_function: g_type_check_instance_cast executable: /usr/bin/gnome-shell journald_cursor: s=77cddd2acadb4029b268eb922988d356;i=3cf58;b=f7e001c1106b48fea54519e490f39ee2;m=267137cb7;t=55e4af2c338bf;x=eed8ab323f5d399a 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'm not getting these crashes after removing the todo extension. https://extensions.gnome.org/extension/570/todotxt/
(In reply to 陳鐸元 from comment #83) > I'm not getting these crashes after removing the todo extension. > > https://extensions.gnome.org/extension/570/todotxt/ I never had that extension installed (but do have a lot others).
*** Bug 1517104 has been marked as a duplicate of this bug. ***
*** Bug 1517433 has been marked as a duplicate of this bug. ***
Similar problem has been detected: When returning from the lock screen, GNOME SHELL (3.26.2) crashes. fedora 27 reporter: libreport-2.9.3 backtrace_rating: 4 cmdline: /usr/bin/gnome-shell crash_function: g_type_check_instance_cast executable: /usr/bin/gnome-shell journald_cursor: s=a4cdfe0cfbbe4005a3d4a9d94e5e0c4d;i=2f1a0f;b=7bfd270ef0084098a7ce492472ab7ba9;m=9609d76d;t=55ed63a25e41c;x=7ad6ba1febcc95cf 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: It crashed right after returning from the lock screen. This problem seems to occur only on machines with Geforece. reporter: libreport-2.9.3 backtrace_rating: 4 cmdline: /usr/bin/gnome-shell crash_function: g_type_check_instance_cast executable: /usr/bin/gnome-shell journald_cursor: s=a4cdfe0cfbbe4005a3d4a9d94e5e0c4d;i=31d527;b=0ed3dec9f81b48c6ac4b1da77d3e5470;m=21f7661d6;t=55f00f8b32ba0;x=86ca0c9a2f206a0d 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
(In reply to fedora.mydns.jp from comment #88) > It crashed right after returning from the lock screen. > This problem seems to occur only on machines with Geforece. You mean GeForce? I have an Intel graphic card. Regards Tibor
Those who are still encountering the crash, I suggest you try to do a fresh reinstall using the most recent release iso. Previously I reproduced the crash with the beta release. Now I installed using the iso downloaded today but no longer encounter crash.
(In reply to Kevin Suo from comment #90) > Those who are still encountering the crash, I suggest you try to do a > fresh reinstall using the most recent release iso. > > Previously I reproduced the crash with the beta release. Now I installed > using the iso downloaded today but no longer encounter crash. Why would a fresh reinstall be any different from an updated system? That does not make any sense to me. Maybe you just don't have the same extensions installed. Anyway, a fix has been committed upstream 8 days ago and will land in gnome-shell 3.26.3 which has not been released yet.
Indeed you are correct. I encountered the crash again some minutes ago with the same crash report but different operation.
Similar problem has been detected: Gnome shell crashed when I try to login after screen lock. reporter: libreport-2.9.3 backtrace_rating: 3 cmdline: /usr/bin/gnome-shell crash_function: g_type_check_instance_cast executable: /usr/bin/gnome-shell journald_cursor: s=b3b5c7964edf41b5a2db7c91805ec310;i=3631;b=504c01be40f74dc69c56a05ff216d0b1;m=6f80b56b5;t=55f1bb07a7be3;x=d28769729b504836 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 1518805 has been marked as a duplicate of this bug. ***
Similar problem has been detected: Gnome shell crashed and returned to the login screen when I tried to type in a Firefox text field. reporter: libreport-2.9.3 backtrace_rating: 3 cmdline: /usr/bin/gnome-shell crash_function: g_type_check_instance_cast executable: /usr/bin/gnome-shell journald_cursor: s=b3b5c7964edf41b5a2db7c91805ec310;i=4171;b=f023751bf7ea40f588da3a4f46b17684;m=fe97e65;t=55f29bfec5dbb;x=2a0a8610c044b64d 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: the desktop suddenly went dark and it logged out. it happened 2 times and I send this error after the 2nd time. reporter: libreport-2.9.3 backtrace_rating: 3 cmdline: /usr/bin/gnome-shell crash_function: g_type_check_instance_cast executable: /usr/bin/gnome-shell journald_cursor: s=13af5b927c5849c1aa40cfad899c1762;i=13337;b=736872a2dce744498a81386a9a411cd1;m=2d3d7e9749;t=55f32cebf2494;x=34bd6c85752e3115 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 1519682 has been marked as a duplicate of this bug. ***
*** Bug 1519997 has been marked as a duplicate of this bug. ***
Similar problem has been detected: I was typing with ibus-chewing at a web page. Reproducible: always Reproduce steps: 1. I try to log in www.sanmin.com.tw account (in traditional Chinese) 2. click on the "Password" box and start typing, gnome-shell crashs Expected result: 1. it should works fine when typing the password reporter: libreport-2.9.3 backtrace_rating: 4 cmdline: /usr/bin/gnome-shell crash_function: g_type_check_instance_cast executable: /usr/bin/gnome-shell journald_cursor: s=091a8da86f3547bca76d7d70e23a06fe;i=15216c;b=b2fd78451a2d4fe5948b00909ef365dc;m=4b78d457;t=55f566ff1d00f;x=c99af25085b80fa8 kernel: 4.13.16-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 logged in and out a couple of times rapidly (due to a video issue that prevents proper display of the shell on my particular hardware) and on the last log in, the error popup appeared. reporter: libreport-2.9.3 backtrace_rating: 3 cmdline: /usr/bin/gnome-shell crash_function: g_type_check_instance_cast executable: /usr/bin/gnome-shell journald_cursor: s=0880ee6b3f274b45a484f05e49368444;i=3ad06;b=bed546ed4c17454eb424123f7649c79a;m=58bfa94730;t=55f633968cb6d;x=4735727ae71d40e9 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 1520159 has been marked as a duplicate of this bug. ***
Similar problem has been detected: I don't have any step to reproduce. The laptop was running for several days, has been suspended and restarted multiple times. I had mostly Eclipse IDE and Firefox running (both with not so many tabs), and then it froze and Fedora automatically restarted the session (I had to re-login, re-open apps...) reporter: libreport-2.9.3 backtrace_rating: 4 cmdline: /usr/bin/gnome-shell crash_function: g_type_check_instance_cast executable: /usr/bin/gnome-shell journald_cursor: s=46fb57c8100448398e1a455ad4c2d1be;i=b4b3;b=9b747755e67c458db7b769317f74c437;m=228b540f4e;t=55f80c5422189;x=d7e489f6cceaa40c 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
*** Bug 1520960 has been marked as a duplicate of this bug. ***
*** Bug 1521146 has been marked as a duplicate of this bug. ***
Similar problem has been detected: - Updated the computer and rebooted the machine. - Logged in, logged out, then logged back in to test GDM (one of the updates in testing). ABRT message appeared. reporter: libreport-2.9.3 backtrace_rating: 3 cmdline: /usr/bin/gnome-shell crash_function: g_type_check_instance_cast executable: /usr/bin/gnome-shell journald_cursor: s=c572cea8be064750ae2aa102584d4bb4;i=18170;b=6582c92f6b004bda9a21436b3e5516f4;m=b1a07160;t=55facbbb38123;x=8226acd05af8c803 kernel: 4.14.3-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: Log in to shell session, then lock screen or close laptop lid. Wait a minute then move mouse/press a key/open lid to wake up the device. The lock screen showed for a second, then flickered, then I was back to a log in prompt (not unlock prompt; the button below the text field says "Sign in") and on log in, none of previously running programs were still running. reporter: libreport-2.9.3 backtrace_rating: 3 cmdline: /usr/bin/gnome-shell crash_function: g_type_check_instance_cast executable: /usr/bin/gnome-shell journald_cursor: s=4fb39a84b7704766a69ffea1d77e9313;i=42bf8;b=a0556b2028134a41a911f667d86ced70;m=321540e;t=55fb19ee57746;x=c1acfa76d29d1de0 kernel: 4.13.16-302.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 1523942 has been marked as a duplicate of this bug. ***
*** Bug 1524205 has been marked as a duplicate of this bug. ***
*** Bug 1525857 has been marked as a duplicate of this bug. ***
*** Bug 1526707 has been marked as a duplicate of this bug. ***
*** Bug 1526744 has been marked as a duplicate of this bug. ***
Similar problem has been detected: I simply started the computer this morning then there were two notification, one about gnome shell crash and the other about xorg-x11-server reporter: libreport-2.9.3 backtrace_rating: 3 cmdline: /usr/bin/gnome-shell crash_function: g_type_check_instance_cast executable: /usr/bin/gnome-shell journald_cursor: s=700054ced43748258ff5a0dd3e758106;i=1be047;b=a6b1564cb45e48ed855eb7fbeb1ba8ad;m=320247df;t=56083e619f1ca;x=dfff751878215af4 kernel: 4.14.5-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: Just running eclipse and spotify reporter: libreport-2.9.3 backtrace_rating: 4 cmdline: /usr/bin/gnome-shell crash_function: g_type_check_instance_cast executable: /usr/bin/gnome-shell journald_cursor: s=7539e11211c24fadae8ba467ab96cc17;i=1be608;b=d50e1f1217744ea3b678fcb9f25d205b;m=b8dbee8e63;t=56096232c273c;x=7e48f280231fb0cd kernel: 4.13.16-302.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 1527241 has been marked as a duplicate of this bug. ***
*** Bug 1527245 has been marked as a duplicate of this bug. ***
Similar problem has been detected: was in standby, wakeup -> session was closed reporter: libreport-2.9.3 backtrace_rating: 3 cmdline: /usr/bin/gnome-shell crash_function: g_type_check_instance_cast executable: /usr/bin/gnome-shell journald_cursor: s=c6d1fa7afa7746ce8bab7737f53d1ef3;i=219f4;b=849277c5bc364a03b45ae735fd5bdcc3;m=25ad9ebbd;t=560b4851be472;x=e571730ed52da473 kernel: 4.14.3-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 1527805 has been marked as a duplicate of this bug. ***
Similar problem has been detected: After some quite time, I started empathy. reporter: libreport-2.9.3 backtrace_rating: 3 cmdline: /usr/bin/gnome-shell crash_function: g_type_check_instance_cast executable: /usr/bin/gnome-shell journald_cursor: s=cd07e3d4b71a4b87a5e058b76d4048f5;i=1e275;b=c66bc4de119e4ee08fa8109968556252;m=63e45bc73;t=560c66367474f;x=4fec72c1edd13e11 kernel: 4.14.6-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: 1. Leave it on the lock screen for several tens of minutes. 2. I crashed trying to release the lock. reporter: libreport-2.9.3 backtrace_rating: 3 cmdline: /usr/bin/gnome-shell crash_function: g_type_check_instance_cast executable: /usr/bin/gnome-shell journald_cursor: s=a4cdfe0cfbbe4005a3d4a9d94e5e0c4d;i=3e97f9;b=1d856fe237244b088b8c455fa3932153;m=3cf3cb021;t=560d367756075;x=273dcce956ed06a1 kernel: 4.14.6-300.fc27.x86_64 package: gnome-shell-3.26.2-2.fc27 reason: gnome-shell killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
*** Bug 1528208 has been marked as a duplicate of this bug. ***
Same problem. gnome-shell-3.26.2-2.fc27.x86_64 Linux tak 4.14.6-300.fc27.x86_64 #1 SMP Thu Dec 14 15:31:24 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux Relevant thread from gdb trace: Thread 1 (Thread 0x7fe33de9df80 (LWP 10014)): #0 0x00007fe33d2e15a2 in g_type_check_instance_cast () at /lib64/libgobject-2.0.so.0 #1 0x00007fe33aa16278 in st_label_set_text () at /usr/lib64/gnome-shell/libst-1.0.so #2 0x00007fe33d2c321e in g_object_setv () at /lib64/libgobject-2.0.so.0 #3 0x00007fe33d2c41ae in g_object_set_property () at /lib64/libgobject-2.0.so.0 #4 0x00007fe33bfaf4b7 in () at /lib64/libgjs.so.0 #5 0x00007fe3338a8d92 in NativeSetExistingDataProperty(JSContext*, JS::Handle<js::NativeObject*>, JS::Handle<js::Shape*>, JS::Handle<JS::Value>, JS::Handle<JS::Value>, JS::ObjectOpResult&) [clone .isra.970] () at /lib64/libmozjs-52.so.0 #6 0x00007fe3338bf352 in js::NativeSetProperty(JSContext*, JS::Handle<js::NativeObject*>, JS::Handle<jsid>, JS::Handle<JS::Value>, JS::Handle<JS::Value>, js::QualifiedBool, JS::ObjectOpResult&) () at /lib64/libmozjs-52.so.0 #7 0x00007fe3338cc4ae in js::SetProperty(JSContext*, JS::Handle<JSObject*>, JS::Handle<jsid>, JS::Handle<JS::Value>, JS::Handle<JS::Value>, JS::ObjectOpResult&) () at /lib64/libmozjs-52.so.0 #8 0x00007fe3338aeb0b in Interpret(JSContext*, js::RunState&) () at /lib64/libmozjs-52.so.0 #9 0x00007fe3338ba9f6 in js::RunScript(JSContext*, js::RunState&) () at /lib64/libmozjs-52.so.0 #10 0x00007fe3338bafcf in js::InternalCallOrConstruct(JSContext*, JS::CallArgs const&, js::MaybeConstruct) () at /lib64/libmozjs-52.so.0 #11 0x00007fe3338bb2a9 in js::Call(JSContext*, JS::Handle<JS::Value>, JS::Handle<JS::Value>, js::AnyInvokeArgs const&, JS::MutableHandle<JS::Value>) () at /lib64/libmozjs-52.so.0 #12 0x00007fe3336a92dd in js::jit::InvokeFunction(JSContext*, JS::Handle<JSObject*>, bool, unsigned int, JS::Value*, JS::MutableHandle<JS::Value>) () at /lib64/libmozjs-52.so.0 #13 0x0000350bf2a0c3c6 in () #14 0x0000000000000000 in () Traces from other crashes, same system, same package versions: Thread 1 (Thread 0x7f47a8213f80 (LWP 17288)): #0 0x00007f47a76575a2 in g_type_check_instance_cast () at /lib64/libgobject-2.0.so.0 #1 0x00007f47a4d8c278 in st_label_set_text () at /usr/lib64/gnome-shell/libst-1.0.so #2 0x00007f47a763921e in g_object_setv () at /lib64/libgobject-2.0.so.0 #3 0x00007f47a763a1ae in g_object_set_property () at /lib64/libgobject-2.0.so.0 #4 0x00007f47a63254b7 in () at /lib64/libgjs.so.0 #5 0x00007f479dc1ed92 in NativeSetExistingDataProperty(JSContext*, JS::Handle<js::NativeObject*>, JS::Handle<js::Shape*>, JS::Handle<JS::Value>, JS::Handle<JS::Value>, JS::ObjectOpResult&) [clone .isra.970] () at /lib64/libmozjs-52.so.0 #6 0x00007f479dc35352 in js::NativeSetProperty(JSContext*, JS::Handle<js::NativeObject*>, JS::Handle<jsid>, JS::Handle<JS::Value>, JS::Handle<JS::Value>, js::QualifiedBool, JS::ObjectOpResult&) () at /lib64/libmozjs-52.so.0 #7 0x00007f479dc424ae in js::SetProperty(JSContext*, JS::Handle<JSObject*>, JS::Handle<jsid>, JS::Handle<JS::Value>, JS::Handle<JS::Value>, JS::ObjectOpResult&) () at /lib64/libmozjs-52.so.0 #8 0x00007f479de534a2 in js::jit::DoSetPropFallback(JSContext*, js::jit::BaselineFrame*, js::jit::ICSetProp_Fallback*, JS::Handle<JS::Value>, JS::Handle<JS::Value>, JS::MutableHandle<JS::Value>) () at /lib64/libmozjs-52.so.0 #9 0x00002d73567eac06 in () #10 0x0000000000000000 in () Several other traces that look the same as well.
Similar problem has been detected: At reboot reporter: libreport-2.9.3 backtrace_rating: 3 cmdline: /usr/bin/gnome-shell crash_function: g_type_check_instance_cast executable: /usr/bin/gnome-shell journald_cursor: s=674c51bec2e64fa3ab4058e4dc5aaeb7;i=3233f;b=e2aaaf49eaa3425b8f8c888ff29e2774;m=32d960b0;t=560e290d70d90;x=c7a610250f67b2a5 kernel: 4.14.6-300.fc27.x86_64 package: gnome-shell-3.26.2-2.fc27 reason: gnome-shell killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
Similar problem has been detected: Ran software update to most recent software as of 12/22/2017. Rebooted after update. At login in screen, I entered my credentials. When Gnome DE started, I received a different error (previously reported). I then rebooted again. Again, at login in screen, I entered my credentials. When Gnome DE started, I received this error. reporter: libreport-2.9.3 backtrace_rating: 3 cmdline: /usr/bin/gnome-shell crash_function: g_type_check_instance_cast executable: /usr/bin/gnome-shell journald_cursor: s=bfdd3156de764bce8333934b3d9bb87d;i=4d840;b=4c6347e196b9496bb0630a8111bd61e7;m=3c35b48;t=560f3e2eac350;x=a24f2fc08d91c040 kernel: 4.14.7-300.fc27.x86_64 package: gnome-shell-3.26.2-2.fc27 reason: gnome-shell killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
Similar problem has been detected: unlocked gnome screensaver, screensaver went away and directly followed by crash. reporter: libreport-2.9.3 backtrace_rating: 4 cmdline: /usr/bin/gnome-shell crash_function: g_type_check_instance_cast executable: /usr/bin/gnome-shell journald_cursor: s=81ac07b108f440569c1839cad2d1a71f;i=15fc7;b=ef10129c17f9422dae79682c989de6ae;m=240081ac4;t=560fff15593ee;x=57cf9850dd72ad5 kernel: 4.14.7-300.fc27.x86_64 package: gnome-shell-3.26.2-2.fc27 reason: gnome-shell killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
*** Bug 1528939 has been marked as a duplicate of this bug. ***
Similar problem has been detected: It crashed immediately after using "ibus restart" command. reporter: libreport-2.9.3 backtrace_rating: 3 cmdline: /usr/bin/gnome-shell crash_function: g_type_check_instance_cast executable: /usr/bin/gnome-shell journald_cursor: s=a4cdfe0cfbbe4005a3d4a9d94e5e0c4d;i=425509;b=73fdfe4c038341a4aff0dbaeacf81ac9;m=2e560f5a;t=561312425a509;x=f74f90b711afedfc kernel: 4.14.8-300.fc27.x86_64 package: gnome-shell-3.26.2-2.fc27 reason: gnome-shell killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
Similar problem has been detected: Gnome Shell crashed on wake up reporter: libreport-2.9.3 backtrace_rating: 3 cmdline: /usr/bin/gnome-shell crash_function: g_type_check_instance_cast executable: /usr/bin/gnome-shell journald_cursor: s=b8ce7adacd234e2eb39194c64a7ccb20;i=b41f;b=fae9308dcb0944b997da231d170f7d1a;m=1a3501a0d;t=5613d3da102b9;x=ac3f2ffbb87d50c8 kernel: 4.14.8-300.fc27.x86_64 package: gnome-shell-3.26.2-2.fc27 reason: gnome-shell killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
Similar problem has been detected: Immediately after power on, with no intervening action, except parhaps 10 minutes delay, the logon crashed gnome-shell. reporter: libreport-2.9.3 backtrace_rating: 3 cmdline: /usr/bin/gnome-shell crash_function: g_type_check_instance_cast executable: /usr/bin/gnome-shell journald_cursor: s=674c51bec2e64fa3ab4058e4dc5aaeb7;i=59a39;b=19f76035f16e447b9bf7c4475a89988a;m=7633a11e;t=5615945e97fa2;x=5f2a12bbf9516665 kernel: 4.14.8-300.fc27.x86_64 package: gnome-shell-3.26.2-2.fc27 reason: gnome-shell killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
Similar problem has been detected: Initial gnome login reporter: libreport-2.9.3 backtrace_rating: 3 cmdline: /usr/bin/gnome-shell crash_function: g_type_check_instance_cast executable: /usr/bin/gnome-shell journald_cursor: s=33ed7df679db49ff806ca782b3330df0;i=577b4;b=db0e2ef5b394493da8b8bae6f137fe69;m=1e2c3a7;t=56179b3223902;x=49fb00007b319381 kernel: 4.14.8-300.fc27.x86_64 package: gnome-shell-3.26.2-3.fc27 reason: gnome-shell killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
Similar problem has been detected: Creating bootable USB using fedora media writer reporter: libreport-2.9.3 backtrace_rating: 3 cmdline: /usr/bin/gnome-shell crash_function: g_type_check_instance_cast executable: /usr/bin/gnome-shell journald_cursor: s=16f1bbb70c714caaaf88ec9bf310f452;i=78f57;b=b04aa3c87df5453d9f9d9b94f9229814;m=10dc1cabf;t=5621ef1d53b54;x=8d14bbd7c571d07b kernel: 4.14.11-300.fc27.x86_64 package: gnome-shell-3.26.2-3.fc27 reason: gnome-shell killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
Similar problem has been detected: This happened straight after booting and the first attempt to log in. reporter: libreport-2.9.3 backtrace_rating: 3 cmdline: /usr/bin/gnome-shell crash_function: g_type_check_instance_cast executable: /usr/bin/gnome-shell journald_cursor: s=4a460b7e56c14857bb1df4b4869f629d;i=fd72;b=20e78734729a41dfaa8fe3a8d766b731;m=35dc022;t=5622489470efd;x=9279a547434934b6 kernel: 4.14.11-300.fc27.x86_64 package: gnome-shell-3.26.2-3.fc27 reason: gnome-shell killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
*** Bug 1532187 has been marked as a duplicate of this bug. ***
Similar problem has been detected: I'm not sure if it is reproducable. Just login, open firefox, thunderbird, gajim. Some minutes later -- crash reporter: libreport-2.9.3 backtrace_rating: 4 cmdline: /usr/bin/gnome-shell crash_function: g_type_check_instance_cast executable: /usr/bin/gnome-shell journald_cursor: s=0d345df1252e4f98baae2d12eecbfdb0;i=496bd;b=8f176087125b45188497f1c5fe184336;m=aab8062a;t=56247e2370bbc;x=69351e8336f61add kernel: 4.14.11-300.fc27.x86_64 package: gnome-shell-3.26.2-3.fc27 reason: gnome-shell killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
Similar problem has been detected: I pressed return to close the screensaver . Gnome crashed. Then the screensaver appeared again. I pressed enter to close the screensaver again. Gnome crashed again, this time ending the X11 session. reporter: libreport-2.9.3 backtrace_rating: 4 cmdline: /usr/bin/gnome-shell crash_function: g_type_check_instance_cast executable: /usr/bin/gnome-shell journald_cursor: s=6d2d3dbf0c7d43cbb56fbff5df7478c1;i=bc1b6;b=ffbfb8ac3a7f4b1797e835e08bfeda36;m=9be6d0f3;t=562821d98522a;x=af5d0b70ba8721c1 kernel: 4.14.11-300.fc27.x86_64 package: gnome-shell-3.26.2-3.fc27 reason: gnome-shell killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
*** Bug 1534495 has been marked as a duplicate of this bug. ***
*** Bug 1534740 has been marked as a duplicate of this bug. ***
*** Bug 1534946 has been marked as a duplicate of this bug. ***
Same crashes for me - seems to have something to do with having my andorid phone plugged into USB (charge only mode). When plugged/unplugged, gnome session will most likely crash soon (usually next lock/unlock). It is pretty annoying as I loose the whole gnome session on each crash :-( { "signal": 11 , "executable": "/usr/bin/gnome-shell" , "stacktrace": [ { "crash_thread": true , "frames": [ { "address": 139957566084557 , "build_id": "232687371f3320fdc67450a3d0d04974c82563c5" , "build_id_offset": 218573 , "function_name": "g_type_check_instance_cast" , "file_name": "/lib64/libgobject-2.0.so.0" } , { "address": 139957523309176 , "build_id": "237979d3c7140165b69d8d496088b34ce8f2d133" , "build_id_offset": 131704 , "function_name": "st_label_set_text" , "file_name": "/usr/lib64/gnome-shell/libst-1.0.so" } , { "address": 139957472464158 , "build_id": "d7a5f1be0e9a258038b4eae99d24015dd1956870" , "build_id_offset": 23838 , "function_name": "ffi_call_unix64" , "file_name": "/lib64/libffi.so.6" } , { "address": 139957472462479 , "build_id": "d7a5f1be0e9a258038b4eae99d24015dd1956870" , "build_id_offset": 22159 , "function_name": "ffi_call" , "file_name": "/lib64/libffi.so.6" } , { "address": 139957545922264 , "build_id": "81706a1cf21a14d06dcc5c2210bdcea6bff4dc23" , "build_id_offset": 208600 , "file_name": "/lib64/libgjs.so.0" }
I've disabled the mediaplayer extensions [1] and not a single crash since (1.5 week ago). Before that, I had several per week. https://github.com/JasonLG1979/gnome-shell-extensions-mediaplayer/
*** Bug 1536488 has been marked as a duplicate of this bug. ***
Upstream has a bug fix. Can we please have a bugfix release?
Just for the record, the upstream bug report seams to be: https://bugzilla.gnome.org/show_bug.cgi?id=788931 It is currently in FIXED status.
*** Bug 1536786 has been marked as a duplicate of this bug. ***
Hello Owen, I can confirm the fix is valid on my Fedora27 workstation. This issue makes Fedora27 as workstation not usable. Would you be able to proceed the backport to Fedora27 soon? Best Regards, Keigo Noha
*** Bug 1536948 has been marked as a duplicate of this bug. ***
gnome-shell-3.26.2-4.fc27 has been submitted as an update to Fedora 27. https://bodhi.fedoraproject.org/updates/FEDORA-2018-b7004c69d2
Similar problem has been detected: I typed in a TAB in a firefox window, to move the input focus, and it segfaulted on me. reporter: libreport-2.9.3 backtrace_rating: 3 cmdline: /usr/bin/gnome-shell crash_function: g_type_check_instance_cast executable: /usr/bin/gnome-shell journald_cursor: s=3561bbc55aa4488380340ad53b165b9f;i=11b66;b=5e750348b09e43c999de6064e061bd4f;m=36290911;t=5636b0589d6ca;x=1b7d10e724fdee6c kernel: 4.14.13-300.fc27.x86_64 package: gnome-shell-3.26.2-3.fc27 reason: gnome-shell killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
gnome-shell-3.26.2-4.fc27 has been pushed to the Fedora 27 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2018-b7004c69d2
*** Bug 1537931 has been marked as a duplicate of this bug. ***
*** Bug 1523526 has been marked as a duplicate of this bug. ***
gnome-shell-3.26.2-3.fc27 crashes to login screen(both Wayland and Xorg sessions) when I plug the smartphone using the USB cable. Disabling the extension: https://extensions.gnome.org/extension/8/places-status-indicator/ Now works fine.
For what it's worth: The updated package referenced in comment 146 fixed all crahses for me so far. Didn't disable any extension.
*** Bug 1539292 has been marked as a duplicate of this bug. ***
Arne: Silvio: as mentioned earlier in the thread, there is an issue where some GNOME bugs are incorrectly considered duplicates. Arne, if the update fixed your crashes, you very likely *were* suffering from this issue. Silvio, if an extension is involved and this update doesn't fix your problem, you very likely are *not* suffering from this issue, but a different bug; it might be best to file a new bug, with (ideally) your traceback and at least the system logs from around the time of the crash, and we may be able to figure out what's happening to you. Thanks, and sorry for the trouble.
(In reply to Silvio Marazzato from comment #151) > gnome-shell-3.26.2-3.fc27 crashes to login screen(both Wayland and Xorg > sessions) when I plug the smartphone using the USB cable. > Disabling the extension: > https://extensions.gnome.org/extension/8/places-status-indicator/ > Now works fine. I suffer from the crash with this extension also, when plugin the usb or umount it from witin file manager. I noticed that when it crashes, no crash reports are generated nor reported automatically. I see there is an update to this extension (and some others), but I am not to get updates to any of the gnome extensions from the Gnome Software or dnf. Yes this is a different issue.
gnome-shell-3.26.2-4.fc27 has been pushed to the Fedora 27 stable repository. If problems still persist, please make note of it in this bug report.
With gnome-shell-3.26.2-4.fc27 the problem with the places-status-indicator plugging external USB storage persists. Is not possible to collect report using the Fedora 27 provided tool due to corrupted data(there is a Python3 problem).
I can confirm that Places Status Indicator seems to be the (or at least, a) trigger to this bug. Any filesystem mount/unmount through nautilus, gnome disks or automount makes the shell crash if said extension is active.
I can also confirm that the problem persists with Installed Packages Name : gnome-shell Version : 3.26.2 Release : 4.fc27 Further, I don't have the "Places Status Indicator" extension installed and it happens anyways, usually triggered in Nautilus when "ejecting" a remote sshfs mount, not every single time but often enough to ruin the Wayland user experience and force the use of X11
p.s. I did notice that the crash triggered from a Nautilus 'eject of remote sshfs mount' tends to happen more often after a suspend/resume or hibernate/resume cycle.
*** Bug 1549475 has been marked as a duplicate of this bug. ***
*** Bug 1551211 has been marked as a duplicate of this bug. ***
Similar problem has been detected: tried to login reporter: libreport-2.9.3 backtrace_rating: 3 cmdline: /usr/bin/gnome-shell crash_function: g_type_check_instance_cast executable: /usr/bin/gnome-shell journald_cursor: s=4e549e8fd5ef487fbf373de3edf2f802;i=2e2bd;b=d5a3785496b94cef9688c5f3e1bbad56;m=27092181;t=5671ee7afca4e;x=6c5ddd4bfe8cef93 kernel: 4.15.7-300.fc27.x86_64 package: gnome-shell-3.26.2-4.fc27 reason: gnome-shell killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
*** Bug 1558832 has been marked as a duplicate of this bug. ***
Similar problem has been detected: When I was using Intellij and firefox along with my terminal reporter: libreport-2.9.3 backtrace_rating: 3 cmdline: /usr/bin/gnome-shell crash_function: g_type_check_instance_cast executable: /usr/bin/gnome-shell journald_cursor: s=e397452c54a248359c2daee383a8c6b5;i=5fb2;b=c43659e31d7449309fcbfb57bbd657cd;m=3f977586;t=56a75b0256431;x=bf1effadc57fa242 kernel: 4.13.16-302.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 1626731 has been marked as a duplicate of this bug. ***