Bug 1489554 - [abrt] gnome-shell: g_type_check_instance_cast(): gnome-shell killed by SIGSEGV
Summary: [abrt] gnome-shell: g_type_check_instance_cast(): gnome-shell killed by SIGSEGV
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-shell
Version: 27
Hardware: x86_64
OS: Unspecified
urgent
urgent
Target Milestone: ---
Assignee: Owen Taylor
QA Contact: Fedora Extras Quality Assurance
URL: https://retrace.fedoraproject.org/faf...
Whiteboard: abrt_hash:2df99fa9b8f311e7ea909bbe5b3...
: 1508810 1512335 1514292 1514821 1514958 1515501 1515879 1516316 1518007 1523385 1524069 1524337 1525243 1526011 1526332 1526727 1527668 1528298 1528405 1528937 1529000 1529128 1529604 1530110 1533195 1535563 1536497 1536578 1537427 1538724 1539683 1540177 1543145 1543715 1546057 1546767 1546980 1547211 1548184 1549581 1551222 1551242 1551507 1551847 1554795 1555917 1557724 1560202 1560359 1562533 1562698 1564646 1564785 1565194 1566368 1567584 1567605 1569224 1571378 1571434 1572311 1573159 1574727 1575273 1593061 1594303 1607746 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-09-07 17:41 UTC by Doaxan
Modified: 2018-12-09 20:52 UTC (History)
110 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-11-30 19:55:13 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (141.28 KB, text/plain)
2017-09-07 17:42 UTC, Doaxan
no flags Details
File: cgroup (289 bytes, text/plain)
2017-09-07 17:42 UTC, Doaxan
no flags Details
File: core_backtrace (41.67 KB, text/plain)
2017-09-07 17:42 UTC, Doaxan
no flags Details
File: cpuinfo (1.16 KB, text/plain)
2017-09-07 17:42 UTC, Doaxan
no flags Details
File: dso_list (27.11 KB, text/plain)
2017-09-07 17:42 UTC, Doaxan
no flags Details
File: environ (1.94 KB, text/plain)
2017-09-07 17:42 UTC, Doaxan
no flags Details
File: exploitable (82 bytes, text/plain)
2017-09-07 17:42 UTC, Doaxan
no flags Details
File: limits (1.29 KB, text/plain)
2017-09-07 17:42 UTC, Doaxan
no flags Details
File: maps (169.26 KB, text/plain)
2017-09-07 17:42 UTC, Doaxan
no flags Details
File: open_fds (6.66 KB, text/plain)
2017-09-07 17:42 UTC, Doaxan
no flags Details
File: proc_pid_status (1.28 KB, text/plain)
2017-09-07 17:42 UTC, Doaxan
no flags Details
File: var_log_messages (14.28 KB, text/plain)
2017-09-07 17:42 UTC, Doaxan
no flags Details

Description Doaxan 2017-09-07 17:41:48 UTC
Version-Release number of selected component:
gnome-shell-3.25.91-1.fc27

Additional info:
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=268b56a70fa344c09004aaf593274a92;i=8f564;b=5001ab43ed4e4654afe368c636de410d;m=25220411;t=5589ceda542b6;x=c5a983cae810da0c
kernel:         4.13.0-0.rc7.git0.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 ../src/st/st-label.c:331
 #2 ffi_call_unix64 at ../src/x86/unix64.S:76
 #3 ffi_call at ../src/x86/ffi64.c:525
 #4 gjs_invoke_c_function(JSContext*, Function*, JS::HandleObject, JS::HandleValueArray const&, mozilla::Maybe<JS::MutableHandle<JS::Value> >, GIArgument*) at gi/function.cpp:1026
 #5 function_call(JSContext*, unsigned int, JS::Value*) at gi/function.cpp:1343
 #6 js::CallJSNative(JSContext*, bool (*)(JSContext*, unsigned int, JS::Value*), JS::CallArgs const&) at /usr/src/debug/mozjs38-38.8.0-6.fc27.x86_64/jscntxtinlines.h:226
 #7 js::Invoke(JSContext*, JS::CallArgs, js::MaybeConstruct) at /usr/src/debug/mozjs38-38.8.0-6.fc27.x86_64/vm/Interpreter.cpp:498
 #8 Interpret(JSContext*, js::RunState&) at /usr/src/debug/mozjs38-38.8.0-6.fc27.x86_64/vm/Interpreter.cpp:2602
 #9 js::RunScript(JSContext*, js::RunState&) at /usr/src/debug/mozjs38-38.8.0-6.fc27.x86_64/vm/Interpreter.cpp:448

Comment 1 Doaxan 2017-09-07 17:42:00 UTC
Created attachment 1323358 [details]
File: backtrace

Comment 2 Doaxan 2017-09-07 17:42:02 UTC
Created attachment 1323359 [details]
File: cgroup

Comment 3 Doaxan 2017-09-07 17:42:06 UTC
Created attachment 1323360 [details]
File: core_backtrace

Comment 4 Doaxan 2017-09-07 17:42:08 UTC
Created attachment 1323361 [details]
File: cpuinfo

Comment 5 Doaxan 2017-09-07 17:42:11 UTC
Created attachment 1323362 [details]
File: dso_list

Comment 6 Doaxan 2017-09-07 17:42:13 UTC
Created attachment 1323363 [details]
File: environ

Comment 7 Doaxan 2017-09-07 17:42:15 UTC
Created attachment 1323364 [details]
File: exploitable

Comment 8 Doaxan 2017-09-07 17:42:17 UTC
Created attachment 1323365 [details]
File: limits

Comment 9 Doaxan 2017-09-07 17:42:23 UTC
Created attachment 1323366 [details]
File: maps

Comment 10 Doaxan 2017-09-07 17:42:25 UTC
Created attachment 1323367 [details]
File: open_fds

Comment 11 Doaxan 2017-09-07 17:42:28 UTC
Created attachment 1323368 [details]
File: proc_pid_status

Comment 12 Doaxan 2017-09-07 17:42:31 UTC
Created attachment 1323369 [details]
File: var_log_messages

Comment 13 Leslie Satenstein 2017-10-18 00:12:08 UTC
Similar problem has been detected:

With btrfs and extensions for
TaskBar@zpydr
caffeine 
Gno-Menu
radio.com

When installing these extensions to Fedora 27, where the user selected  anaconda to use btrfs, these extensions (and others)
crash the user.  In some cases, the logon prompt is presented, and in others, the logon results in loss of keyboard and screen.
The only recovery in the latter case is to reboot, log in via command line, and remove the offending extension.

HOWEVER
Moving the /home directory to ext4  or to xfs (from btrfs) allows the above extensions to install cleanly and to function as designed.
It is discouraging to not have this issue resolved.  

My "GUESS" is that the ~/.config/dconf/user file is being corrupted, when maintained with btrfs, but is OK when maintained with ext4 or xfs.

As an end-user I have been chasing this bug ever since Fediora27 nightlies began to be released for testing.


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=03fedd19f14f4307928d900254dec7e8;i=241c;b=69ada6a6a8b64c41a3649e24cf2c7aa4;m=2be3b48b;t=55bc6bed6cb8d;x=df38e5c8d2691373
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

Comment 14 Leslie Satenstein 2017-10-18 00:24:55 UTC
Please see 1496283   1469129 

I believe that ~/.config/dconf/user  is being corrupted when gnome-shell is on btrfs.

Comment 15 Leslie Satenstein 2017-10-24 04:07:44 UTC
Still a problem.  Cannot have /home onto a btrfs system and be sure that gnome-shell will start or that extensions will not crash.

Comment 16 Dominik Drazyk 2017-11-02 09:41:11 UTC
*** Bug 1508810 has been marked as a duplicate of this bug. ***

Comment 17 Jonathan Haas 2017-11-07 16:00:23 UTC
Similar problem has been detected:

Batch disabling shell extensions through gnome-tweak tool (including Pomodoro, Recent Items, Removable Drive Menu, Places Status indicator, TopIcons Plus)

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=1bc7b3faa0404365a719ac4013abff94;i=18ad3b;b=27b6cacf18104e6c8dcfb46ce6a45713;m=6925ad7b5;t=55d668f050d97;x=badecb7d70958e30
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

Comment 18 Jonathan Haas 2017-11-07 16:07:32 UTC
I have home (and root) on ext4 partitions btw., so this is probably not btrfs related.

Comment 19 Jonathan Haas 2017-11-10 08:11:03 UTC
This is a duplicate of 1469129.

Comment 20 jan p. springer 2017-11-12 22:26:57 UTC
*** Bug 1512335 has been marked as a duplicate of this bug. ***

Comment 21 Mark Tinberg 2017-11-15 05:24:28 UTC
Similar problem has been detected:

Seemed to occur during initial login to Wayland session, I got dumped back to the GDM screen, second login attempt worked just fine

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=acf543ae9e76423da65d40ee9eeaaf74;i=12e5a;b=ad5d76ceecee4844a27f7d245570601a;m=66fa802;t=55dfe8b7f1561;x=e7f4d642127a1efc
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

Comment 22 Patrick 2017-11-17 00:37:04 UTC
*** Bug 1514292 has been marked as a duplicate of this bug. ***

Comment 23 Richard Ruhland 2017-11-18 18:15:47 UTC
*** Bug 1514821 has been marked as a duplicate of this bug. ***

Comment 24 Granata Giovanni 2017-11-19 17:31:55 UTC
*** Bug 1514958 has been marked as a duplicate of this bug. ***

Comment 25 Andreas T. 2017-11-19 20:15:22 UTC
Similar problem has been detected:

Gnome-Shell crashes after login, especially after wake up from sleep mode. Might require 2 to 3 further logins to work 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=1d0216a33d364811ad690ccda3397e15;i=41eda;b=7aa4ea098d17409ab6a44453035e28b7;m=2d4aed3f4;t=55e5a280c42e2;x=56984f65d06d47bc
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

Comment 26 Brad 2017-11-20 22:51:57 UTC
*** Bug 1515501 has been marked as a duplicate of this bug. ***

Comment 27 Luca 2017-11-21 14:27:55 UTC
*** Bug 1515879 has been marked as a duplicate of this bug. ***

Comment 28 Andreas T. 2017-11-21 20:28:42 UTC
Similar problem has been detected:

Login to Gnome-Shell, showed two cursors for a few seconds, than crashed and showed login screen 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=1d0216a33d364811ad690ccda3397e15;i=48460;b=669428a257314ad9a1d224fecd0b4dd4;m=2dc3cb788;t=55e83e9cc04f5;x=56b725e6df2e5289
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

Comment 29 to.to.to.ben 2017-11-22 13:06:29 UTC
*** Bug 1516316 has been marked as a duplicate of this bug. ***

Comment 30 Mark Tinberg 2017-11-27 21:42:46 UTC
*** Bug 1518007 has been marked as a duplicate of this bug. ***

Comment 31 Tomáš Vlček 2017-11-30 08:54:25 UTC
Similar problem has been detected:

I plugged in USB memory stick. The system freezed and gnome-shell crashed.

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=28c235c577ab4853add237ed8e3582c7;i=20bc;b=df52c989f23e495799b2b04310747bd7;m=bf68f24f;t=55f2f4df2aed0;x=f5cb8a00d5f3a45d
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

Comment 32 Tomáš Vlček 2017-12-01 15:27:33 UTC
Similar problem has been detected:

I plugged in a memory card. System freezed and gnome-shell crashed.

BTW, the same happens with USB stick, when mounting or unmounting it.

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=28c235c577ab4853add237ed8e3582c7;i=6693;b=f7c31a4e6d5342fa8651d0bb420b7c02;m=10a526d3b;t=55f484f8964a2;x=2d51bbba3dc60ca8
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

Comment 33 Jonathan Haas 2017-12-05 08:39:05 UTC
Similar problem has been detected:

Happened directly after login

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=1bc7b3faa0404365a719ac4013abff94;i=1a4ede;b=d3918fccd8e147f69d5b014420188cfa;m=2b31377;t=55f939c518543;x=f32380eed1ead501
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

Comment 34 Tomáš Vlček 2017-12-07 08:58:13 UTC
Similar problem has been detected:

I plugged in USB memory stick. System freezed and gnome-shell crashed....

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=28c235c577ab4853add237ed8e3582c7;i=19465;b=33b5672396c34e438016d1831e57f079;m=b1055e0e;t=55fbbe3790dad;x=fe2825f537a711d0
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

Comment 35 dirk.stiehler 2017-12-07 20:54:19 UTC
*** Bug 1523385 has been marked as a duplicate of this bug. ***

Comment 36 Jan Ischebeck 2017-12-08 10:59:51 UTC
Similar problem has been detected:

Open USB Drive using File Explorer

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=b8a9cc6d77fd48f08087f1809360aac8;i=2544;b=a07fab33464b46a085652c76a3e954c1;m=2b7fb3879;t=55fd1da2f9d22;x=5fcb90573a950ac5
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

Comment 37 coreyhineline 2017-12-09 20:46:56 UTC
*** Bug 1524069 has been marked as a duplicate of this bug. ***

Comment 38 marcvw 2017-12-11 09:47:47 UTC
*** Bug 1524337 has been marked as a duplicate of this bug. ***

Comment 39 bugzilla 2017-12-12 21:27:45 UTC
*** Bug 1525243 has been marked as a duplicate of this bug. ***

Comment 40 Jim 2017-12-13 08:33:24 UTC
Similar problem has been detected:

gnome-shell has continuously crashing on me when I return after locking my workstation.  I regurlarly update my fedora system and gnome-shell has been crashing and unstable for the past three week.

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=b45661f7d4e1453d8d4d92a484ca711d;i=17b1557;b=b7fc9aa74d984749839102b6799b6d87;m=32296d3;t=5603487f782f3;x=4751089c815e0694
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

Comment 41 Andreas T. 2017-12-13 12:13:47 UTC
(In reply to Jim from comment #40)
Had exactly the same problems. After deactivating all Gnome extensions it didn't crash anymore.  I still try to find out which extension caused the trouble, by reactivating it one by one - but haven't found it yet (it takes some time, as it doesn't crash instantly :)

Comment 42 Tomáš Vlček 2017-12-14 08:18:04 UTC
Similar problem has been detected:

I plugged in USB memory stick.

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=28c235c577ab4853add237ed8e3582c7;i=2392c3;b=b1e9880730f449e68b98718d7f5df867;m=181c50f53;t=56016a1bdcce1;x=2b155fd8926f3648
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

Comment 43 Andreas T. 2017-12-14 12:11:37 UTC
(In reply to Andreas T. from comment #41)
> (In reply to Jim from comment #40)
> Had exactly the same problems. After deactivating all Gnome extensions it
> didn't crash anymore.  I still try to find out which extension caused the
> trouble, by reactivating it one by one - but haven't found it yet (it takes
> some time, as it doesn't crash instantly :)

I think I found the extension in question. After activating "Dash to Dock" the crashes reoccurred. Although the journal doesn't list it's name in the logs. Perhaps you can give it a try.

Comment 44 amol.h 2017-12-14 15:34:40 UTC
*** Bug 1526011 has been marked as a duplicate of this bug. ***

Comment 45 jose.miguel.perez.hernandez 2017-12-14 17:41:50 UTC
Similar problem has been detected:

Crashed just after first login on a freshly rebooted system. Second time logins ok

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=89c7a3fa45f24f0381e05cff3943e2f1;i=56602f;b=37d67e5d70104e10851fe1224f78603d;m=b9c9dfd;t=5605044ae4e9b;x=6dfc7a1b032d2af0
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:            1002

Comment 46 Jim 2017-12-15 00:16:14 UTC
(In reply to Andreas T. from comment #43)
> (In reply to Andreas T. from comment #41)
> > (In reply to Jim from comment #40)
> > Had exactly the same problems. After deactivating all Gnome extensions it
> > didn't crash anymore.  I still try to find out which extension caused the
> > trouble, by reactivating it one by one - but haven't found it yet (it takes
> > some time, as it doesn't crash instantly :)
> 
> I think I found the extension in question. After activating "Dash to Dock"
> the crashes reoccurred. Although the journal doesn't list it's name in the
> logs. Perhaps you can give it a try.

I've disabled my Dash to Dock gnome extension and will give that an initial try.  I'll reply back with the results later.

Thanks for the feedback, Andreas T.!!

Comment 47 Jim 2017-12-15 05:15:20 UTC
Similar problem has been detected:

In the middle of normal use at my workstation, gnome-shell just borkded!  WTF?! :P  Probably Alt-Tab'ng from one window to another when BLAM!  BTW, gnome-shell has been crashing daily on me.  Rarely in this manner, I recently disabled the gnome extension "Dash to Dock", but have others running.

gnome extensions running:
  "Applications menu"
  "Coverflow alt-tab"
  "Dynamic panel transparency"
  "Gnome shell extension reloader"
  "Hide top bar"
  "Launch new instance"
  "No topleft hot corner"
  "Pixel saver"
  "Services systemd"
  "Topicons plus"
  "User themes"
  "Vpn indicator"
  "Volume mixer"
  "Workspace switch wraparound"

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=b45661f7d4e1453d8d4d92a484ca711d;i=17e8599;b=c2dc0c29fed045cea6733604522bc0c4;m=4590d7c16;t=56059dc675a27;x=f06dad48a67f952c
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

Comment 48 Doug Hutcheson 2017-12-15 09:00:45 UTC
*** Bug 1526332 has been marked as a duplicate of this bug. ***

Comment 49 Mark Tinberg 2017-12-15 15:44:26 UTC
I had been getting weekly if not daily crashes as well, but I haven't had one in maybe a week.  I disabled all extensions, but Dash to Dock was not one I was using so while it maybe be triggered by that extension it's not exclusive to it, or there are several different problems that present similar tracebacks.

I had the following installed and have marked which I remember being enabled.

$ ls .local/share/gnome-shell/extensions/ -1
?? dash-to-dock.com (This directory has no files, must have uninstalled at some point, dir mtime is from June 2017)
* emoji-selector
? github.notifications.gmail.com
* notifications-alert-on-user-menu.com
* no-title-bar.com
? pidgin@muffinmad
* sound-output-device-chooser
* system-monitor.gmail.com
* TopIcons
? TwitchLive_Panel.de
* update-extensions.com
* vscode-search-provider

$ ls /usr/share/gnome-shell/extensions/ -1
alternate-tab.github.com
* apps-menu.github.com
* background-logo
launch-new-instance.github.com
* places-menu.github.com
user-theme.github.com
window-list.github.com

Comment 50 Theodor van Nahl 2017-12-16 10:49:50 UTC
Similar problem has been detected:

I was just trying to login from gdm after boot.

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=32c29aed8ed14b99ab1149ed4b4afe2a;i=4b84;b=1908ac113e5645a7896164332f655cee;m=33b3bed;t=5607257c18e45;x=62d7a1d5a6e4128d
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

Comment 51 crius 2017-12-16 19:38:02 UTC
*** Bug 1526727 has been marked as a duplicate of this bug. ***

Comment 52 Doug Hutcheson 2017-12-17 06:43:59 UTC
I disabled all shell extensions and no longer have a problem. Like others above, I will attempt to identify to extension causing the problem and will report here if I do. I don't use Dash to Dock and do use a fully ext4 file system.

Comment 53 Casey Stone 2017-12-19 20:45:54 UTC
*** Bug 1527668 has been marked as a duplicate of this bug. ***

Comment 54 Casey Stone 2017-12-19 20:55:47 UTC
Regarding Casey Stone report:

I use standard EXT4 file system, and Application Theme Arc-Darker-solid, cursor Adwaita, icons Fedora, shell Default.

Fedora 26 seemed more stable to me than 27 has so far.

Comment 55 Tomáš Vlček 2017-12-21 07:38:58 UTC
Similar problem has been detected:

I umounted Google Drive in Nautilus. This happens regularly: either when mounting anything or umounting.

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=28c235c577ab4853add237ed8e3582c7;i=2586b3;b=4b6e68f1133640a6808f983da5544dd2;m=7982ca05;t=560d4a391746d;x=c5ffcc018dc6584d
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

Comment 56 slecrenski 2017-12-21 13:40:30 UTC
*** Bug 1528298 has been marked as a duplicate of this bug. ***

Comment 57 Casey Stone 2017-12-21 19:08:31 UTC
*** Bug 1528405 has been marked as a duplicate of this bug. ***

Comment 58 Casey Stone 2017-12-23 10:27:29 UTC
Hello ... regarding my duplicate bugs here 1528405 and 1527668, I believe it was "my fault" in that I had not manually updated a couple of shell extensions I was using, installed during the time of FC25. I had three in use:

nohotcorner.fr
system-monitor.gmail.com
vpn-indicator.com

I updated (or possibly re-installed the same version, hard to know) the first two and disabled vpn-indicator and I have not seen the crashing since then. Sorry for the false accusations about Fedora 27 Gnome shell being crashy inherently.

Comment 59 Tomáš Vlček 2017-12-24 15:52:35 UTC
Similar problem has been detected:

I plugged in a pendrive... This happens regularly: sometimes it works and sometimes it doesn't work.

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=28c235c577ab4853add237ed8e3582c7;i=26050e;b=8d69436088fd44e686c21e206b61845c;m=2629db167;t=56117e19ea1c6;x=327b6b04a14176be
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

Comment 60 jun 2017-12-25 08:57:18 UTC
*** Bug 1528937 has been marked as a duplicate of this bug. ***

Comment 61 jan p. springer 2017-12-25 19:09:16 UTC
*** Bug 1529000 has been marked as a duplicate of this bug. ***

Comment 62 dark147123 2017-12-26 15:14:25 UTC
*** Bug 1529128 has been marked as a duplicate of this bug. ***

Comment 63 Ariel 2017-12-28 22:19:57 UTC
*** Bug 1529604 has been marked as a duplicate of this bug. ***

Comment 64 Ariel 2017-12-28 22:26:36 UTC
In my case this seems connected to gnome virtual filesystems, the crash is always triggered from nautilus - every time, when starting file browsing of an sFTP share, or when disconnecting it, description below. 
F27 on Wayland is totally unusable due to the crashes (a few times each day). With Xorg, at least the apps/session do survive this mess.
This had never happened on previous fedoras I've used (all the way back to F19)


Gnome shell crashed when nautilus connected to an SFTP share in a different server, I have a
 favorites link in nautilus like so:

sftp://user.1.8/home/user

In this instance, I middle clicked in nautilus on this favorite and gnome shell crashes. I have several of these
and this happens  a couple times each day (but it's not consistent, once Shell crashes, it won't crash again for
a few hours).

Also, gnome shell crashes often when I try to "Eject" in nautilus one of these shares. Nautilus itself never crashes, 
only  the shell crashes. Because of all these daily Shell crashes I had to switch from Wayland to Xorg.

This started to happen after the upgrade to Fedora 27. I never happened before. I've been using Fedora since F19 or so

Version-Release number of selected component:
gnome-shell-3.26.2-3.fc27

Comment 65 vsdemail 2018-01-02 04:48:40 UTC
*** Bug 1530110 has been marked as a duplicate of this bug. ***

Comment 66 Tomáš Vlček 2018-01-07 21:26:45 UTC
Similar problem has been detected:

I plugged in an USB stick.

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=28c235c577ab4853add237ed8e3582c7;i=26a73f;b=47c0e52df36e474bb651da476818a24a;m=cad04096;t=5623623033abd;x=eb39d56e2930d06
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

Comment 67 Kåre Løvgren 2018-01-10 17:13:43 UTC
*** Bug 1533195 has been marked as a duplicate of this bug. ***

Comment 68 Charalampos Stratakis 2018-01-15 10:20:58 UTC
Similar problem has been detected:

As soon as I logged in and opened a terminal, gnome-shell crashed.

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=8fc9f45dea9340ccbafe06ec66124ddc;i=7218b;b=1ebb6a185f62459e820857dc73968634;m=eb0909a;t=562cde2417c83;x=6f1e1f0ee127b633
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

Comment 69 Charalampos Stratakis 2018-01-15 10:23:45 UTC
(In reply to Ariel from comment #64)

> F27 on Wayland is totally unusable due to the crashes (a few times each
> day). With Xorg, at least the apps/session do survive this mess.
> This had never happened on previous fedoras I've used (all the way back to
> F19)

That is exactly what I'm experiencing as well with F27 unfortunately.

Comment 70 Dermot Williams 2018-01-17 15:51:23 UTC
*** Bug 1535563 has been marked as a duplicate of this bug. ***

Comment 71 Alexandre Franke 2018-01-18 20:27:21 UTC
Similar problem has been detected:

100% reproducible. I suspend my laptop (Thinkpad T400) by closing the lid. Later I open the lid, the laptop resumes and after about 10 seconds the Shell crashes (whether I unlock or not).

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=211f83a9e8744683977a6cc9ba3f03cd;i=2689;b=4a1c0e69f1e64aa0ac6b010f5e529217;m=da31a0d;t=56312977ea9c0;x=de28a394947c85f7
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

Comment 72 Erle Pereira 2018-01-19 05:35:32 UTC
Similar problem has been detected:

The XServer (XWayland) crashes, seemingly randomly. I have noticed relating to the following event types, but it is hard to reproduce exactly.
I do suspect it to be related at times to my HDMI connection (via a displayport adapter), but I cannot currently say that for sure.
the following steps seems to to be the most reliable way to reproduce
1. Login to workstation via GDM, plugin it the display port, it sometimes crashes , restarts the Xserver and brings you back to the login screen.

2. Leave the workstation to automatically lock after the specified amount of time. It (fairly frequently) crashes, restarts the Xserver, and you need to login again (All previously open applications are obviously closed).

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=379a72ec99134a77a5c45f68c91a79e3;i=3d5fc;b=f6f7ce80347d4b1395152a9ec59b0f8f;m=fcf7ee9;t=5631a1366dc3a;x=1cf5d7d69e08decf
kernel:         4.13.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

Comment 73 Olivier Fourdan 2018-01-19 07:49:54 UTC
From the backtrace (attachment 1323360 [details]), could be upstream bug https://bugzilla.gnome.org/show_bug.cgi?id=788931 for which the fix (commit 3b4be770 in branch gnome-3-26 of gnome-shell) is not in gnome-shell 3.26.2

Comment 74 Olivier Fourdan 2018-01-19 08:08:52 UTC
(In reply to Erle Pereira from comment #72)
> The XServer (XWayland) crashes, seemingly randomly. I have noticed relating
> to the following event types, but it is hard to reproduce exactly.

Xwayland is just a Wayland client, when the Wayland compositor (gnome-shell) crashes, the Wayland clients die. So in this case, Xwayland is not really crashing, it's just lost its connection to the Wayland compositor.

Comment 75 eric.le-boennec 2018-01-19 14:09:14 UTC
*** Bug 1536497 has been marked as a duplicate of this bug. ***

Comment 76 simone celia 2018-01-19 16:52:10 UTC
*** Bug 1536578 has been marked as a duplicate of this bug. ***

Comment 77 mesel 2018-01-23 08:08:46 UTC
*** Bug 1537427 has been marked as a duplicate of this bug. ***

Comment 78 johannes.hidding 2018-01-25 10:17:46 UTC
Similar problem has been detected:

Spontaneous crash of gnome-shell. Possibly related to Bug 1517833

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=f1b42606fc5247a6a8bbf1fa5cb8012b;i=31b8;b=4f74a44c7c9c423884170cf8646f0eae;m=7af2e2bc1;t=56396e2acd377;x=a1480653c7f903b7
kernel:         4.14.14-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

Comment 79 Garrett Mitchener 2018-01-25 16:48:42 UTC
*** Bug 1538724 has been marked as a duplicate of this bug. ***

Comment 80 Garrett Mitchener 2018-01-25 16:52:24 UTC
I see something similar when I plug in an Android tablet.
I'll experiment with shell extensions.

Comment 81 Garrett Mitchener 2018-01-25 16:58:55 UTC
I disabled all extensions using Tweaks, and plugged in my tablet: no crash.

I enabled Dash to Dock, plugged in my tablet: Gnome crashes. But this time, no ABRT notification for some reason...

Comment 82 Garrett Mitchener 2018-01-25 22:25:50 UTC
I get the same crash if I put a blank CD into my CD burner.

After some further experiments, I think it may be that having any extensions enabled affects the crash.

With all extensions disabled, I'm not getting the crash.

Comment 83 marcvw 2018-01-29 12:33:19 UTC
*** Bug 1539683 has been marked as a duplicate of this bug. ***

Comment 84 jose.miguel.perez.hernandez 2018-01-29 17:56:24 UTC
Similar problem has been detected:

Wayland crashes whenever you plug in an iphone on an usb port

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=7e40cc67ac964fa9a8281064be51878c;i=12ae7c4;b=db0811cd32b44ac484234186918e0d61;m=5b46fb82;t=563ed83bb564b;x=b249599b1434540f
kernel:         4.14.14-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:            1002

Comment 85 Garrett Mitchener 2018-01-29 20:59:47 UTC
It looks like the Places status indicator extension may be triggering the crash. See https://forums.fedoraforum.org/showthread.php?317036-strange-login-problem-caused-by-Android-tablet-connected-via-USB and https://forums.fedoraforum.org/showthread.php?317040-F27-Gnome-shell-crashes-when-a-external-USB-HDD-is-connected-or-disconnected

The second forum post includes a list of packages that were updated just before the crash started happening. Gnome-shell isn't listed. Among the ones there, I guess I'd start looking at gjs-1.50.3-1.fc27.x86_64.

Comment 86 Sumit Srivastava 2018-01-30 12:30:01 UTC
*** Bug 1540177 has been marked as a duplicate of this bug. ***

Comment 87 Tomas Mlcoch 2018-02-03 22:09:20 UTC
Similar problem has been detected:

When I attach a flash disk, Gnome Shell always crashes and restarts (opened windows remain opened).
When I click to "eject" in Nautilus and want to remove the flash disc, Gnome Shell crashes again and usually unlog me (all windows are lost).

Relevant snippet from journald:
...
úno 03 22:43:00 deepspace kernel: usb 1-1.2: new high-speed USB device number 12 using ehci-pci
úno 03 22:43:00 deepspace kernel: usb 1-1.2: New USB device found, idVendor=058f, idProduct=6387
úno 03 22:43:00 deepspace kernel: usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
úno 03 22:43:00 deepspace kernel: usb 1-1.2: Product: Mass Storage
úno 03 22:43:00 deepspace kernel: usb 1-1.2: Manufacturer: Generic
úno 03 22:43:00 deepspace kernel: usb 1-1.2: SerialNumber: 8D05C181
úno 03 22:43:00 deepspace kernel: usb-storage 1-1.2:1.0: USB Mass Storage device detected
úno 03 22:43:00 deepspace kernel: scsi host6: usb-storage 1-1.2:1.0
úno 03 22:43:00 deepspace mtp-probe[10773]: checking bus 1, device 12: "/sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.2"
úno 03 22:43:00 deepspace mtp-probe[10773]: bus: 1, device: 12 was not an MTP device
úno 03 22:43:01 deepspace kernel: scsi 6:0:0:0: Direct-Access     Generic  Flash Disk       8.07 PQ: 0 ANSI: 4
úno 03 22:43:01 deepspace kernel: sd 6:0:0:0: Attached scsi generic sg2 type 0
úno 03 22:43:01 deepspace kernel: sd 6:0:0:0: [sdb] 15976448 512-byte logical blocks: (8.18 GB/7.62 GiB)
úno 03 22:43:01 deepspace kernel: sd 6:0:0:0: [sdb] Write Protect is off
úno 03 22:43:01 deepspace kernel: sd 6:0:0:0: [sdb] Mode Sense: 23 00 00 00
úno 03 22:43:01 deepspace kernel: sd 6:0:0:0: [sdb] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
úno 03 22:43:01 deepspace kernel:  sdb:
úno 03 22:43:01 deepspace kernel: sd 6:0:0:0: [sdb] Attached SCSI removable disk
úno 03 22:43:01 deepspace polkitd[962]: Unregistered Authentication Agent for unix-session:4 (system bus name :1.131, object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8) (disconnected from bus)
úno 03 22:43:01 deepspace udisksd[2126]: Mounted /dev/sdb at /run/media/tojaj/AE7D-5BA3 on behalf of uid 1000
úno 03 22:43:01 deepspace gnome-session[9668]: gnome-session-binary[9668]: WARNING: App 'org.gnome.Shell.desktop' exited with code 1
úno 03 22:43:01 deepspace gnome-session-binary[9668]: WARNING: App 'org.gnome.Shell.desktop' exited with code 1
...

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=f56282f2b1244d549a821afb1f44558b;i=f1a7;b=487e120627444dbbaaca04f02f58c6ab;m=2f13ffe53;t=56455c4b5bacc;x=16f099494d63f19e
kernel:         4.14.14-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

Comment 88 Jindřich Káňa 2018-02-07 20:37:34 UTC
*** Bug 1543145 has been marked as a duplicate of this bug. ***

Comment 89 Fred Weigel 2018-02-08 15:32:14 UTC
Similar problem has been detected:

Select Gnome on Xorg, attempt 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=d62695cf5ae0495b9994a8ab6d3b46b7;i=806c2;b=62ce826d83054ca799b07aeb699da044;m=45c0c39c;t=564b4ebb65e34;x=9e29097913872dbb
kernel:         4.14.16-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

Comment 90 #AntiSec 2018-02-09 04:46:56 UTC
*** Bug 1543715 has been marked as a duplicate of this bug. ***

Comment 91 dobs 2018-02-16 08:39:11 UTC
*** Bug 1546057 has been marked as a duplicate of this bug. ***

Comment 92 Glauco Stephan 2018-02-19 14:41:42 UTC
*** Bug 1546767 has been marked as a duplicate of this bug. ***

Comment 93 Or Schiro 2018-02-20 09:20:27 UTC
*** Bug 1546980 has been marked as a duplicate of this bug. ***

Comment 94 Or Schiro 2018-02-20 09:23:08 UTC
I can confirm that it is possibly related to Xorg. I received this crash when switching from Wayland to Xorg.

Comment 95 Alexandre Franke 2018-02-20 09:25:52 UTC
Happens with Wayland for me. I disabled the only extension I was using (https://extensions.gnome.org/extension/570/todotxt/) and the problem is gone though.

Comment 96 Kyle Taylor 2018-02-20 18:17:43 UTC
*** Bug 1547211 has been marked as a duplicate of this bug. ***

Comment 97 John Vaudrey 2018-02-20 22:33:00 UTC
Similar problem has been detected:

There is nothing specific i can add, sometimes this happens when only firefox is running, other times it could be when nothing is running and it just locks up.

i have had it happen a couple of times following a suspend

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=2793c8fdae884e32982b45f65ede9639;i=1b057;b=3c16913a5d5a40ccbb86610d31783002;m=a44532a;t=565ac09c10471;x=24d88682a7b66bdc
kernel:         4.15.3-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

Comment 98 Or Schiro 2018-02-21 12:10:28 UTC
Happened to me just now.

Uninstalled this extension on extensions.gnome.org/local

https://extensions.gnome.org/extension/1201/extend-panel-menu/

Comment 99 Charalampos Stratakis 2018-02-22 14:27:46 UTC
Similar problem has been detected:

Was having gitk open from a terminal window and when I clicked ctrl+shift+t to open a new tab of the terminal on the same folder my session crashed.

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=8fc9f45dea9340ccbafe06ec66124ddc;i=f867c;b=3cb57ef6943e4107ae50240abfec4ad2;m=3a20ae818;t=565cdbd6e6eae;x=2e4dbbcf72b41d8b
kernel:         4.15.3-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

Comment 100 Oscar 2018-02-22 23:07:05 UTC
*** Bug 1548184 has been marked as a duplicate of this bug. ***

Comment 101 dizzy 2018-02-23 09:40:48 UTC
Same problem as Ariel reported (Comment #64), crash happens (see bellow) most likely (appx. 6 out of 10 attempts) when one of the following occurs:
- mount/umount sftp via nautilus
- plug/unplug my android phone on USB (USB file sharing enabled)

So it seems to be somehow related to gvfs (but that's only my guess). Maybe it has something to do with applications actually running, because it usually doesn't happen after fresh login. So there are only few apps that were up every time it crashed:
- Toolbox from JetBrains (https://www.jetbrains.com/toolbox/app/) - it resides in status tray
- RubyMine (from JetBrains again)
- Gnome Terminal
- Evolution
- Pidgin
- InSync (https://www.insynchq.com/) - tray app too

Crash details:
reason: gnome-shell killed by SIGSEGV
crash_function: g_type_check_instance_cast
package: gnome-shell-3.26.2-4.fc27
kernel: 4.15.3-300.fc27.x86_64

Comment 102 Jan Ischebeck 2018-02-24 16:30:18 UTC
Error also occurs, when only executing a mount command on the console.

Comment 103 Dermot Williams 2018-02-26 12:11:35 UTC
I've been having this problem for several months now on both Ubuntu and (more relevantly) Fedora. As with @dizzy, it doesn't happen after a fresh login - it usually takes a few hours before the 'right' conditions exist. At which point it almost always happens as soon as I mount something - either by plugging in a USB key or mounting a remote drive via CIFS, SFTP etc.

In my case it appears to have been caused by the todo.txt extension (https://extensions.gnome.org/extension/570/todotxt/). I've disabled that extension (though I haven't uninstalled it) and haven't had any problems. I've actually been logged in since the 21st Feb (5 days), which is the last time I had this problem - and when I disabled todo.txt extension.

Relevant lines from my journal might be:

Feb 21 13:26:15 nettor org.gnome.Shell.desktop[1934]: #12 0x555ce9436900 i   /home/dermot/.local/share/gnome-shell/extensions/todo.txt.gmail.com/extension.js:603 (0x7f446b490098 @ 62)
Feb 21 13:26:15 nettor org.gnome.Shell.desktop[1934]: #14 0x7ffedf4cf680 b   /home/dermot/.local/share/gnome-shell/extensions/todo.txt.gmail.com/third_party/logDecorator/logDecorator.js:27 (0x7f446b4d6120 @ 212)

Comment 104 Laurent Meunier 2018-02-27 07:00:41 UTC
Similar problem has been detected:

1. Start a Gnome Session
2. Open Nautilus (optional)
3. plug an USB key (or mount any remote FS - like SSHFS or Samba)
4. Gnome-shell crashes and is automaticaly restarted

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=92996b03518d47a7bce54aecc7d88011;i=def44;b=ce0ff8fee87344cd85067c3bb6cee3a0;m=8ae0c7bdf;t=5662c08d9a4f2;x=7202a41da320c440
kernel:         4.15.3-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

Comment 105 atab 2018-02-27 13:07:07 UTC
*** Bug 1549581 has been marked as a duplicate of this bug. ***

Comment 106 Shashikanth317 2018-03-02 10:55:24 UTC
Similar problem has been detected:

Was using Atom txt editor and bunch of gnome extensions running in background and all of sudden, it crashed and closed my user session.
This happened previously on multiple instances.

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=dbae39ee3af14d96b660cf1fe60c4932;i=18eaf;b=a39162c0446b4d948532f8bafd504382;m=24fac4ba3;t=5666ba4c6f1bd;x=89245591bbd3e7b4
kernel:         4.15.4-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

Comment 107 jrweare 2018-03-03 14:58:53 UTC
*** Bug 1551222 has been marked as a duplicate of this bug. ***

Comment 108 sinholt 2018-03-03 21:02:16 UTC
*** Bug 1551242 has been marked as a duplicate of this bug. ***

Comment 109 sogal 2018-03-05 10:16:47 UTC
*** Bug 1551507 has been marked as a duplicate of this bug. ***

Comment 110 Syquus 2018-03-05 10:20:22 UTC
Similar problem has been detected:

This has been happening since over a year ago. At least all 6 released kernels for FC27 suffer from the same. Not constant to reproduce. But Today I realized that AFTER a kernel update, the first boot at least it CRASHES Gnome Shell / Suspends the machine. I press power button and then USB Power comes back, and display shows the Gnome DESKTOP unlocked

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=862cc4ead636477783800926afd84ba8;i=119926;b=aaf796b73a9149abbfc0e38edb970232;m=33eee84;t=566a76eef2ac1;x=996409ab37b9fef2
kernel:         4.15.6-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

Comment 111 Syquus 2018-03-05 14:09:08 UTC
Similar problem has been detected:

After upgrading to kernel 4.14.6-300 (through dnf pkg manager) on every fresh start, machine suspends after Login/Password screen.

If I press the Power button on the Lenovo Yoga 260 Laptop, Displays & USB devices resume and the session is on the desktop. Already unlocked.

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=862cc4ead636477783800926afd84ba8;i=11cab0;b=10770fe1bf7d45b991233280bf870eb8;m=2d248c9;t=566aac233401e;x=bdaf7d97861af2d1
kernel:         4.15.6-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

Comment 112 Garrett Mitchener 2018-03-05 18:41:52 UTC
I've noticed that gnome shell is a lot more unstable when I leave a USB Wacom tablet plugged in. I wonder if some part of the Yoga's hardware is seen as a tablet device that's always connected, and maybe that is triggering the same bugs?

If that's the case and these bugs are left unfixed, then in a year or two, gnome will be unusable on any new laptop, because the trend is to build touch sensors and stylus functionality into all new laptops...

Comment 113 Nicholas 2018-03-06 01:35:03 UTC
*** Bug 1551847 has been marked as a duplicate of this bug. ***

Comment 114 Wes Gelpi 2018-03-13 12:05:55 UTC
*** Bug 1554795 has been marked as a duplicate of this bug. ***

Comment 115 Gil Forcada 2018-03-14 20:16:12 UTC
*** Bug 1555917 has been marked as a duplicate of this bug. ***

Comment 116 pranjalsharma1729 2018-03-18 02:34:23 UTC
*** Bug 1557724 has been marked as a duplicate of this bug. ***

Comment 117 David Sastre Medina 2018-03-23 11:23:51 UTC
I'm experiencing intermittent crashes with a specific extension (https://github.com/neffo/earth-view-wallpaper-gnome-extension).
Current version of gnome-shell is:

$ rpm -q gnome-shell
gnome-shell-3.26.2-4.fc27.x86_64

Some of these crashes have been recorded by coredumpctl:

$ coredumpctl gdb
           PID: 2812 (gnome-shell)
           UID: 1001 (david)
           GID: 1001 (david)
        Signal: 11 (SEGV)
     Timestamp: Thu 2018-03-22 18:27:37 CET (47s ago)
  Command Line: /usr/bin/gnome-shell
    Executable: /usr/bin/gnome-shell
 Control Group: /user.slice/user-1001.slice/session-2.scope
          Unit: session-2.scope
         Slice: user-1001.slice
       Session: 2
     Owner UID: 1001 (david)
       Boot ID: ee053c33ac134b2c8956113e8632a42d
    Machine ID: 3a32b095360149338272104f81d89454
      Hostname: laptop
       Storage: /var/lib/systemd/coredump/core.gnome-shell.1001.ee053c33ac134b2c8956113e8632a42d.2812.1521739657000000.lz4
       Message: Process 2812 (gnome-shell) of user 1001 dumped core.
                
                Stack trace of thread 2812:
                #0  0x00007f861b4f15a2 g_type_check_instance_cast (libgobject-2.0.so.0)
                #1  0x00007f8618c53278 st_label_set_text (libst-1.0.so)
                #2  0x00007f8615bd5d1e ffi_call_unix64 (libffi.so.6)
                #3  0x00007f8615bd568f ffi_call (libffi.so.6)
                #4  0x00007f861a1b5f78 gjs_invoke_c_function (libgjs.so.0)
                #5  0x00007f861a1b7854 function_call (libgjs.so.0)
                #6  0x00007f8611b010ec _ZN2js12CallJSNativeEP9JSContextPFbS1_jPN2JS5ValueEERKNS2_8CallArgsE (libmozjs-52.so.0)
                #7  0x00007f8611afb5c8 _ZN2js13CallFromStackEP9JSContextRKN2JS8CallArgsE (libmozjs-52.so.0)
                #8  0x00007f8611b00956 _ZN2js9RunScriptEP9JSContextRNS_8RunStateE (libmozjs-52.so.0)
                #9  0x00007f8611b00f2f _ZN2js23InternalCallOrConstructEP9JSContextRKN2JS8CallArgsENS_14MaybeConstructE (libmozjs-52.so.0)
                #10 0x00007f8611b01209 _ZN2js4CallEP9JSContextN2JS6HandleINS2_5ValueEEES5_RKNS_13AnyInvokeArgsENS2_13MutableHandleIS4_EE (libmozjs-52.so.0)
                #11 0x00007f86118ef23d _ZN2js3jit14InvokeFunctionEP9JSContextN2JS6HandleIP8JSObjectEEbjPNS3_5ValueENS3_13MutableHandleIS8_EE (libmozjs-52.so.0)
                #12 0x00003e2c019043c6 n/a (n/a)
                #13 0x00007f86118064ed EnterIon (libmozjs-52.so.0)
                #14 0x00007f8611affec9 Interpret (libmozjs-52.so.0)
                #15 0x00007f8611b00956 _ZN2js9RunScriptEP9JSContextRNS_8RunStateE (libmozjs-52.so.0)
                #16 0x00007f8611b00f2f _ZN2js23InternalCallOrConstructEP9JSContextRKN2JS8CallArgsENS_14MaybeConstructE (libmozjs-52.so.0)
                #17 0x00007f8611b01209 _ZN2js4CallEP9JSContextN2JS6HandleINS2_5ValueEEES5_RKNS_13AnyInvokeArgsENS2_13MutableHandleIS4_EE (libmozjs-52.so.0)
                #18 0x00007f86118ef23d _ZN2js3jit14InvokeFunctionEP9JSContextN2JS6HandleIP8JSObjectEEbjPNS3_5ValueENS3_13MutableHandleIS8_EE (libmozjs-52.so.0)
                #19 0x00003e2c019043c6 n/a (n/a)

GNU gdb (GDB) Fedora 8.0.1-36.fc27
Copyright (C) 2017 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-redhat-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from /usr/bin/gnome-shell...Reading symbols from /usr/lib/debug/usr/bin/gnome-shell-3.26.2-4.fc27.x86_64.debug...done.
done.
[New LWP 2812]
[New LWP 2814]
[New LWP 2817]
[New LWP 2901]
[New LWP 13940]
[New LWP 2904]
[New LWP 2909]
[New LWP 2815]
[New LWP 2905]
[New LWP 2910]
[New LWP 2907]
[New LWP 2903]
[New LWP 2906]
[New LWP 2908]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
Core was generated by `/usr/bin/gnome-shell'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  g_type_check_instance_cast (type_instance=0x55682a70bcf0, iface_type=93905804765472) at gtype.c:4057
4057		  node = lookup_type_node_I (type_instance->g_class->g_type);
[Current thread is 1 (Thread 0x7f861c0beac0 (LWP 2812))]
>>> list
4052	      if (type_instance->g_class)
4053		{
4054		  TypeNode *node, *iface;
4055		  gboolean is_instantiatable, check;
4056		  
4057		  node = lookup_type_node_I (type_instance->g_class->g_type);
4058		  is_instantiatable = node && node->is_instantiatable;
4059		  iface = lookup_type_node_I (iface_type);
4060		  check = is_instantiatable && iface && type_node_conforms_to_U (node, iface, TRUE, FALSE);
4061		  if (check)
>>> bt
#0  g_type_check_instance_cast (type_instance=0x55682a70bcf0, iface_type=93905804765472) at gtype.c:4057
#1  0x00007f8618c53278 in st_label_set_text (label=0x55682a70b810, text=0x556830956fb0 "View in Google Maps") at ../src/st/st-label.c:331
#2  0x00007f8615bd5d1e in ffi_call_unix64 () at ../src/x86/unix64.S:76
#3  0x00007f8615bd568f in ffi_call (cif=cif@entry=0x5568281bd818, fn=<optimized out>, rvalue=<optimized out>, rvalue@entry=0x7ffd5972f838, avalue=avalue@entry=0x7ffd5972f730) at ../src/x86/ffi64.c:525
#4  0x00007f861a1b5f78 in gjs_invoke_c_function (context=context@entry=0x55682654a430, function=function@entry=0x5568281bd800, obj=..., obj@entry=..., args=..., js_rval=..., r_value=r_value@entry=0x0) at gi/function.cpp:1033
#5  0x00007f861a1b7854 in function_call (context=context@entry=0x55682654a430, js_argc=1, vp=0x5568266949d8) at gi/function.cpp:1351
#6  0x00007f8611b010ec in js::CallJSNative (args=..., native=0x7f861a1b76f0 <function_call(JSContext*, unsigned int, JS::Value*)>, cx=0x55682654a430) at /usr/src/debug/mozjs52-52.6.0-1.fc27.x86_64/jscntxtinlines.h:239
#7  js::InternalCallOrConstruct (cx=0x55682654a430, args=..., construct=js::NO_CONSTRUCT) at /usr/src/debug/mozjs52-52.6.0-1.fc27.x86_64/vm/Interpreter.cpp:447
#8  0x00007f8611afb5c8 in js::CallFromStack (args=..., cx=<optimized out>) at /usr/src/debug/mozjs52-52.6.0-1.fc27.x86_64/vm/Interpreter.cpp:510
#9  Interpret (cx=0x55682654a430, state=...) at /usr/src/debug/mozjs52-52.6.0-1.fc27.x86_64/vm/Interpreter.cpp:2922
#10 0x00007f8611b00956 in js::RunScript (cx=cx@entry=0x55682654a430, state=...) at /usr/src/debug/mozjs52-52.6.0-1.fc27.x86_64/vm/Interpreter.cpp:405
#11 0x00007f8611b00f2f in js::InternalCallOrConstruct (cx=cx@entry=0x55682654a430, args=..., construct=construct@entry=js::NO_CONSTRUCT) at /usr/src/debug/mozjs52-52.6.0-1.fc27.x86_64/vm/Interpreter.cpp:477
#12 0x00007f8611b011a9 in InternalCall (cx=cx@entry=0x55682654a430, args=...) at /usr/src/debug/mozjs52-52.6.0-1.fc27.x86_64/vm/Interpreter.cpp:504
#13 0x00007f8611b01209 in js::Call (cx=cx@entry=0x55682654a430, fval=..., thisv=..., args=..., rval=rval@entry=...) at /usr/src/debug/mozjs52-52.6.0-1.fc27.x86_64/vm/Interpreter.cpp:523
#14 0x00007f86118ef23d in js::jit::InvokeFunction (cx=0x55682654a430, obj=..., constructing=<optimized out>, argc=<optimized out>, argv=0x7ffd59730570, rval=...) at /usr/src/debug/mozjs52-52.6.0-1.fc27.x86_64/jit/VMFunctions.cpp:114
#15 0x00003e2c019043c6 in ?? ()
#16 0x00007f85e450bf01 in ?? ()
#17 0x00007ffd59730520 in ?? ()
#18 0xfff9000000000000 in ?? ()
#19 0x00007f8612beaf80 in ?? () from /lib64/libmozjs-52.so.0
#20 0x00007f85f80739a0 in ?? ()
#21 0x00003e2c01bfe7c5 in ?? ()
#22 0x0000000000006820 in ?? ()
#23 0x00007f85cce9cd00 in ?? ()
#24 0x0000000000000000 in ?? ()

https://developer.gnome.org/gobject/stable/gobject-Type-Information.html#G-TYPE-CHECK-INSTANCE-CAST:CAPS
https://github.com/GNOME/glib/blob/master/gobject/gtype.c#L4057

Comment 118 Oswaldo Casasola 2018-03-24 20:14:53 UTC
*** Bug 1560202 has been marked as a duplicate of this bug. ***

Comment 119 Oswaldo Casasola 2018-03-26 02:16:33 UTC
*** Bug 1560359 has been marked as a duplicate of this bug. ***

Comment 120 Andrea Greco 2018-03-30 14:47:02 UTC
Similar problem has been detected:

Try open minicom in gnome-terminal, cause crash.
No more information

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=505674270f364f49acacd70d4d5095f2;i=2a5ec4;b=fce110dcc0a2449e943cd03e25d6c228;m=3ee49fcb2;t=568a19a1647f2;x=d46a212c18a7415e
kernel:         4.15.12-301.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

Comment 121 Lumi Schallenberg 2018-03-31 18:00:53 UTC
*** Bug 1562533 has been marked as a duplicate of this bug. ***

Comment 122 herve.gaucher 2018-03-31 19:25:55 UTC
Similar problem has been detected:

Redemarrage de gnome systématique après introduction d'un périphérique sur un port USB

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=d23ffd9654c043c48000f9398814cbbc;i=133f5a;b=be3485e5df92445f952f7d1258ccff55;m=157f58a49;t=568b9ede595e1;x=dcdf1ffc0d70f6b4
kernel:         4.15.13-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

Comment 123 Joseph 2018-04-02 07:17:58 UTC
*** Bug 1562698 has been marked as a duplicate of this bug. ***

Comment 124 Jack McMahon 2018-04-02 11:36:14 UTC
Similar problem has been detected:

Running on HP Pavilion laptop 7200U CPU. Upon returning from closed lid, gnome-shell  seemed to start mutiple times then displayed crash message.
Otherwise, only chromium and firefox and a terminal window had been been 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=b3e781ed0e414fbb91ec5d4450fdf1aa;i=1b66b;b=802708d52310401b8512127199c95360;m=471a82cdb;t=568dbb6b95c0d;x=abc361fdc24daf
kernel:         4.15.10-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

Comment 125 Jack McMahon 2018-04-03 09:39:06 UTC
This crash happens multiple times a day, since I started using Fedora 27 again March 25. Booting from USB HDD. Why is this bug so hard to fix?

Comment 126 Phil 2018-04-05 06:43:17 UTC
Getting this crash most of the time doing a dnf upgrade which is highly cpu intensive.
1. open terminal
2. become root
3. dnf --refresh -y upgrade
4. between installation and cleanup phases gnome-shell and all applications (browser, mail client, whatever) stop responding
5. when finished, gnome-shell segfaults

Comment 127 xzj8b3 2018-04-06 19:07:09 UTC
*** Bug 1564646 has been marked as a duplicate of this bug. ***

Comment 128 Keefer Rourke 2018-04-07 21:20:24 UTC
*** Bug 1564785 has been marked as a duplicate of this bug. ***

Comment 129 gudbugsarwontfix 2018-04-09 15:09:11 UTC
*** Bug 1565194 has been marked as a duplicate of this bug. ***

Comment 130 John Mellor 2018-04-09 23:12:25 UTC
Similar problem has been detected:

rpm cleanup removed the backgrounds, so I installed 2 Gnome online background downloaders - APOD and Wallhaven.  Desktop crashes multiple times/day since that point.

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=f902860ed9834095898e9d6122e7da74;i=1d69aa;b=2f1c4544123644de962af9bfb8352e99;m=c2e7431b;t=5697265b46be2;x=f43e2fe5ccd3fbf4
kernel:         4.15.14-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

Comment 131 xzj8b3 2018-04-10 14:31:18 UTC
The bug continues to show up and often finds problems in the reporting.... Also known several extensions to create misguides with Gnome-Shell, it would take more controls on third-party extensions!!!!!!

Comment 132 Mikel P. 2018-04-12 03:18:14 UTC
Similar problem has been detected:

was using android studio and it just crashed me to a VT withlots of ^@^@^@

this has happened to me many times and what happens is it starts getting real laggy,
mouse jumping around when i move it and briefly flashes into the ^@^@ VT sometimes
until it finally crashes eventually

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=f2daf8d04f054ee2b502e86e7a4a4cbd;i=204db;b=9b58073a2f874afeb936f0f7be7b0c57;m=219356306e;t=5699d5825db3e;x=ed94d922ea3d3806
kernel:         4.15.14-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

Comment 133 gadille 2018-04-12 07:49:07 UTC
*** Bug 1566368 has been marked as a duplicate of this bug. ***

Comment 134 mesel 2018-04-15 05:42:43 UTC
*** Bug 1567584 has been marked as a duplicate of this bug. ***

Comment 135 iakovos Gurulian 2018-04-15 12:01:08 UTC
*** Bug 1567605 has been marked as a duplicate of this bug. ***

Comment 136 iakovos Gurulian 2018-04-16 07:10:58 UTC
(In reply to Dermot Williams from comment #103)
> I've been having this problem for several months now on both Ubuntu and
> (more relevantly) Fedora. As with @dizzy, it doesn't happen after a fresh
> login - it usually takes a few hours before the 'right' conditions exist. At
> which point it almost always happens as soon as I mount something - either
> by plugging in a USB key or mounting a remote drive via CIFS, SFTP etc.
> 
> In my case it appears to have been caused by the todo.txt extension
> (https://extensions.gnome.org/extension/570/todotxt/). I've disabled that
> extension (though I haven't uninstalled it) and haven't had any problems.
> I've actually been logged in since the 21st Feb (5 days), which is the last
> time I had this problem - and when I disabled todo.txt extension.
> 
> Relevant lines from my journal might be:
> 
> Feb 21 13:26:15 nettor org.gnome.Shell.desktop[1934]: #12 0x555ce9436900 i  
> /home/dermot/.local/share/gnome-shell/extensions/todo.txt.gmail.
> com/extension.js:603 (0x7f446b490098 @ 62)
> Feb 21 13:26:15 nettor org.gnome.Shell.desktop[1934]: #14 0x7ffedf4cf680 b  
> /home/dermot/.local/share/gnome-shell/extensions/todo.txt.gmail.
> com/third_party/logDecorator/logDecorator.js:27 (0x7f446b4d6120 @ 212)

I am also using todo.txt. Probably the problem is there. Anyone else using it?

Comment 137 iakovos Gurulian 2018-04-16 07:14:41 UTC
Here is a bug report at todo.txt: https://bitbucket.org/bartl/todo-txt-gnome-shell-extension/issues/104/gnome-shell-crashing-when-mounting-volume

It seems to be affecting many people using it.

Comment 138 Standa Laznicka 2018-04-16 07:25:26 UTC
Hold on, are you saying I can write an extension that can make gnome-shell access a memory segment it does not necessarily controls? Interesting...

Comment 139 Ariel 2018-04-16 12:56:26 UTC
> I am also using todo.txt. Probably the problem is there. Anyone else using it?

Also using the todo extension! The Shell crashes multiple times a day, normally when unmounting sshfs pr USB drives. It's concerning that this little javascript extension has been able to keep crashing the shell and making wayland unusable for 6 months now

Hoping that some more resiliency to misbehaving extensions can be added to the shell. Much needed - if wayland is to become a real alternative to xorg this seems to be the first step

Comment 140 Phil 2018-04-16 17:49:18 UTC
I have the following extensions running:
- caffeine
- clipboard indicator
- frippery bottom panel
- fripery move clock
- taskbar
- topicons plus

but _no_ "todo". The crash also occurs with all extensions disabled.

Comment 141 iakovos Gurulian 2018-04-17 10:50:09 UTC
(In reply to Phil from comment #140)
> I have the following extensions running:
> - caffeine
> - clipboard indicator
> - frippery bottom panel
> - fripery move clock
> - taskbar
> - topicons plus
> 
> but _no_ "todo". The crash also occurs with all extensions disabled.

For me, after removing todo.txt the problem stopped occurring. I have tried multiple USB devices on different ports and so far so good.

Comment 142 r.lopesdasilva 2018-04-17 14:11:11 UTC
Similar problem has been detected:

I was uploading some photos to my OneDrive, using Firefox.
At same time, I was watching a video in another Firefox tab.
Sundenly it just closed everything an returned to login screen on Gnome.

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=9d4362e6642942349b37685c76811efc;i=d622;b=13645c8d5f7e427085f587022f75bfce;m=50cef3334;t=56a0bbaf9eba2;x=d45daf9133ef7804
kernel:         4.15.16-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

Comment 143 dizzy 2018-04-18 08:39:26 UTC
hi again - using todo.txt, but disabling it didn't help. Maybe there are some other extensions causing the crash. But - correct me, if I am wrong - if a single extension can crash the whole Gnome session, this indicates either (or both):
- huge bug in implementation
- huge problem in design of the whole UI

Please don't get me wrong - I like Gnome, RedHat and I really appreciate what you guys are doing, but this makes the whole thing unusable for real work :-(

Comment 144 andreas 2018-04-18 20:09:13 UTC
*** Bug 1569224 has been marked as a duplicate of this bug. ***

Comment 145 Daniel Miranda 2018-04-19 14:34:19 UTC
I'm seeing the same crash with GNOME 3.28.1 in Fedora 28, and I don't have (and never had) the todo.txt extension. Of the extensions other have mentioned, I use Topicons Plus, Clipboard Indicator and Dash to Dock.

Comment 146 Louis van Dyk 2018-04-19 21:27:39 UTC
Similar problem has been detected:

I had Nemo file manager open.  
I right clicked on the Seagate 6GB Backup External USB drive, and clicked "Safely Remove".
Nemo quit, the screen froze, and Gnome-Shell restarted.

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=bb2d1908bfe74f409a4fe238589830c4;i=162d851;b=30c5a2b3b4cd4a2a8abfaac5d1e950f0;m=2d16f19830;t=56a367640f1fc;x=58501fc2f2901730
kernel:         4.15.10-200.fc26.x86_64
package:        gnome-shell-3.26.2-4.fc27
reason:         gnome-shell killed by SIGSEGV
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000

Comment 147 Georg Sauthoff 2018-04-21 13:41:18 UTC
Crazy how some random gnome shell extension should be able to crash gnome shell, although it's written in a supposedly safe language (JavaScript).

I was clicking on play in the radio extension when the gnome shell crashed (clicking on play worked ~ 100 times before, though):

#0  0x00007f893cbb75a2 in g_type_check_instance_cast ()
    at /lib64/libgobject-2.0.so.0
#1  0x00007f893a319278 in st_label_set_text ()
    at /usr/lib64/gnome-shell/libst-1.0.so
#2  0x00007f893729bd1e in ffi_call_unix64 () at /lib64/libffi.so.6
#3  0x00007f893729b68f in ffi_call () at /lib64/libffi.so.6
#4  0x00007f893b87bf78 in  () at /lib64/libgjs.so.0
#5  0x00007f893b87d854 in  () at /lib64/libgjs.so.0
#6  0x00007f89331c2c1c in js::InternalCallOrConstruct(JSContext*, JS::CallArgs const&, js::MaybeConstruct) () at /lib64/libmozjs-52.so.0
#7  0x00007f89331bd0f2 in Interpret(JSContext*, js::RunState&) ()
    at /lib64/libmozjs-52.so.0
#8  0x00007f89331c2486 in js::RunScript(JSContext*, js::RunState&) ()
    at /lib64/libmozjs-52.so.0
#9  0x00007f89331c2a5f in js::InternalCallOrConstruct(JSContext*, JS::CallArgs const&, js::MaybeConstruct) () at /lib64/libmozjs-52.so.0
#10 0x00007f89331c2d39 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
#11 0x00007f8932fafefd in js::jit::InvokeFunction(JSContext*, JS::Handle<JSObject*>, bool, unsigned int, JS::Value*, JS::MutableHandle<JS::Value>) ()
    at /lib64/libmozjs-52.so.0

GDB keeps telling me to run  dnf debuginfo-install gnome-shell-3.26.2-4.fc27.x86_64, but doing so doesn't make this hint go away and the backtrace stays without source locations as above.

The crashing gnome-shell version:

gnome-shell-3.26.2-4.fc27.x86_64

The gnome-shell extensions I had enabled at the time of crashing:

Locally installed:

LogOutButton.ac.za
caffeine
datetime-format.com
radio.com
sound-output-device-chooser
world_clock_lite

Systemwide installed (via rpm):

TopIcons
drive-menu.github.com
refresh-wifi
suspend-button@laserb

Comment 148 xzj8b3 2018-04-22 16:23:07 UTC
AlternateTab 
Appfolders Management extension 
Auto Move Windows 
Clipboard Indicator 
Coverflow Alt-Tab 
cpufreq 
Dash to Dock 
Force Quit 
Freon 
GSConnect 
Keep awake! 
Media Player Indicator Quick Toggler 
Show IP 
Tilix DropDown 
Wikipedia Search Provider 

My Extensions....

Detected however already several problems in extensions I removed by signaling to developers the problems they created, as a problem with the Italian language (I found the shell in English after their installation)

It would really need more control over extensions or I think similar problems will always occur in Gnome-Shell as besides you are always presented and it is a pity because it is becoming in my opinion a nice desktop!!!!!

Comment 149 Abhishek Gupta 2018-04-23 08:16:44 UTC
Similar problem has been detected:

I was trying to force start gnome wayland 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=1b1a4a6d66754086970924cf9a647308;i=6d5452;b=c350f408d52946ed98c263801884ba85;m=1fd5154c;t=56a7f56a8dece;x=ed090824e3e18202
kernel:         4.15.17-300.fc27.x86_64
package:        gnome-shell-3.26.2-5.fc27
reason:         gnome-shell killed by SIGSEGV
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000

Comment 150 Jack McMahon 2018-04-23 11:21:15 UTC
(In reply to Jack McMahon from comment #124)
> Similar problem has been detected:
> 
> Running on HP Pavilion laptop 7200U CPU. Upon returning from closed lid,
> gnome-shell  seemed to start mutiple times then displayed crash message.
> Otherwise, only chromium and firefox and a terminal window had been been
> 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=b3e781ed0e414fbb91ec5d4450fdf1aa;i=1b66b;
> b=802708d52310401b8512127199c95360;m=471a82cdb;t=568dbb6b95c0d;
> x=abc361fdc24daf
> kernel:         4.15.10-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

I failed to mention previously that on-screen keyboard appears whenever the touch screen is touched and disappears when touchpad or physical keyboard is used. But a crash is not happening when typing or any touchpad activity.

Comment 151 Jack McMahon 2018-04-23 11:21:48 UTC
(In reply to Jack McMahon from comment #124)
> Similar problem has been detected:
> 
> Running on HP Pavilion laptop 7200U CPU. Upon returning from closed lid,
> gnome-shell  seemed to start mutiple times then displayed crash message.
> Otherwise, only chromium and firefox and a terminal window had been been
> 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=b3e781ed0e414fbb91ec5d4450fdf1aa;i=1b66b;
> b=802708d52310401b8512127199c95360;m=471a82cdb;t=568dbb6b95c0d;
> x=abc361fdc24daf
> kernel:         4.15.10-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

I failed to mention previously that on-screen keyboard appears whenever the touch screen is touched and disappears when touchpad or physical keyboard is used. But a crash is not happening when typing or any touchpad activity.

Comment 152 Jack McMahon 2018-04-23 11:23:12 UTC
(In reply to Jack McMahon from comment #124)
> Similar problem has been detected:
> 
> Running on HP Pavilion laptop 7200U CPU. Upon returning from closed lid,
> gnome-shell  seemed to start mutiple times then displayed crash message.
> Otherwise, only chromium and firefox and a terminal window had been been
> 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=b3e781ed0e414fbb91ec5d4450fdf1aa;i=1b66b;
> b=802708d52310401b8512127199c95360;m=471a82cdb;t=568dbb6b95c0d;
> x=abc361fdc24daf
> kernel:         4.15.10-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

I failed to mention previously that on-screen keyboard appears whenever the touch screen is touched and disappears when touchpad or physical keyboard is used. But a crash is not happening when typing or any touchpad activity.

Comment 153 dizzy 2018-04-24 08:21:45 UTC
Some kind of update seems to have arrived (FC27) recently, which is causing the same crash after a fresh new logon. So from now on, you don't have to work hours and hours on the machine to see the UI crash. It seems to me, that the crash appears when you log on and start an application "too early" - without waiting for the system to "settle" (for example - it takes few seconds until the network come up completely).
Maybe something with system notification (according to the stack trace) - it shouldn't be hard to reproduce. Can I do something to help with it?

Comment 154 redguy41 2018-04-24 15:59:01 UTC
*** Bug 1571378 has been marked as a duplicate of this bug. ***

Comment 155 joao.lima 2018-04-24 19:05:04 UTC
*** Bug 1571434 has been marked as a duplicate of this bug. ***

Comment 156 Michael 2018-04-25 11:39:57 UTC
This bug seems to be a use-after-free caused by the quirks of calling a C function from within gnomeJS. I'm the developer of the extension mentioned in comment 117 above (GoogleEarthWallpaper.com), and I've seen this same bug reported multiple times (and in other extensions). It's been a pain to diagnose, but let me try.

It appears to be caused by setting GtkLabel text to the value of a local function variable or a dynamically generated string.

For example, the line causing the crash in the comment above is this:

> this.extLinkItem.label.set_text(_("View in ")+providerNames[provider]);

In this case this.extLinkItem is a PanelMenuItem, and this code is within a class function. Passing a local variable to set_text() also causes the crash.

We can avoid the segfault by creating a new class variable (this.provider_text), and setting the text of the label in this fashion:

> this.provider_text = _("View in ") + providerNames[provider];
> this.extLinkItem.label.set_text(this.provider_text);

Note that nothing else has changed except the string (or rather reference) passed to set_text() will continue to exist even after a garbage collection has run. Obviously local variables will be GCed after they go out of scope. This work around could also be done with a global variable, I guess.

This seems to occur most frequently in the moments immediately after the screen is unlocked (when active extensions get a enable() call). Likely lots of ram being allocated and freed in this time, so more likely to segfault.

I don't know the specifics of how GNOME-shell works (other than it's it's multithreaded), but if the label update is deferred or delayed, the GJS garbage collection could see a local function variable with zero references (within *JS*) and free it before set_text has completed. (This last part is wild speculation.)

Comment 157 Jose Mantilla 2018-04-26 02:29:07 UTC
Similar problem has been detected:

After log in sometimes appear the screen stay loading the desktop -- gnome shell -- and log out automatically go back to the user screen, after some times the gnome-shell works fine.

I use Fedora 27 with the last updates though this happens after the some months.

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=8f7bc125a5e7451b82c2c0357f143c2f;i=107896;b=ce4e37d6f0124e98befa65c9a4902b55;m=3352e08;t=56ab6e9f38b49;x=327c9f3ee6abe2ef
kernel:         4.15.17-300.fc27.x86_64
package:        gnome-shell-3.26.2-5.fc27
reason:         gnome-shell killed by SIGSEGV
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000

Comment 158 simone celia 2018-04-26 16:14:25 UTC
*** Bug 1572311 has been marked as a duplicate of this bug. ***

Comment 159 Evgeniy Kravchenko 2018-04-26 20:08:15 UTC
Similar problem has been detected:

I left the laptop with opened Firefox with youtube. It was on battery power. When i came back the error has already occured.

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=67feebd3558d4fefb5aaeb0b2da1e890;i=fa4;b=7cf7dba5d8ad424683397e6d071b14d7;m=225ae5a92;t=56ac5c4df391d;x=6c5439d0575744a8
kernel:         4.15.17-300.fc27.x86_64
package:        gnome-shell-3.26.2-5.fc27
reason:         gnome-shell killed by SIGSEGV
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000

Comment 160 Ariel 2018-04-27 05:17:26 UTC
While the reports in this thread are probably related to various different issues, the issue I had in particular: Shell crashing every time I mount/unmount an sftp directory in nautilus, is confirmed to be due to the extension todo.txt

I use a lot of extensions:

AlternateTab by fmuellner
Dash to Dock by michele_g
Freon by UshakovVasilii
gTile by scherepanov
Hibernate Status Button by p91paul
OpenWeather by jens
system-monitor by Cerin
TopIcons Plus by phocean
Transparent Top Bar by jpec
User Themes by fmuellner
Volume Mixer by alexhofbauer

and was using todo.txt as well
Since disabling todo.txt a week ago I havent experienced a single crash. Before that, the shell used to crash a few times per session.

There is a bug opened with the extension:

https://bitbucket.org/bartl/todo-txt-gnome-shell-extension/issues/104/gnome-shell-crashing-when-mounting-volume

Comment 161 Mirek Svoboda 2018-04-30 08:20:13 UTC
This issue happens on FC28 too, gnome-shell-3.28.1-1. It's disturbing that the problem has not been caught by abrt and automatic reporting thus did not happen.

Excerpt from journal:
Process 1805 (gnome-shell) of user 1000 dumped core.
                                            
                                            Stack trace of thread 1805:
                                            #0  0x00007f1005e65440 g_type_check_instance_cast (libgobject-2.0.so.0)
                                            #1  0x00007f10035832f0 st_label_set_text (libst-1.0.so)
                                            #2  0x00007f100088f03e ffi_call_unix64 (libffi.so.6)
                                            #3  0x00007f100088e9ff ffi_call (libffi.so.6)
                                            #4  0x00007f1004b27601 n/a (libgjs.so.0)
                                            #5  0x00007f1004b28cc8 n/a (libgjs.so.0)
                                            #6  0x00007f0ffc143335 _ZN2js23InternalCallOrConstructEP9JSContextRKN2JS8CallArgsENS_14MaybeConstructE (libmozjs-52.so.0)
                                            #7  0x00007f0ffc13d67a _ZL9InterpretP9JSContextRN2js8RunStateE (libmozjs-52.so.0)
                                            #8  0x00007f0ffc142dad _ZN2js9RunScriptEP9JSContextRNS_8RunStateE (libmozjs-52.so.0)
                                            #9  0x00007f0ffc14317a _ZN2js23InternalCallOrConstructEP9JSContextRKN2JS8CallArgsENS_14MaybeConstructE (libmozjs-52.so.0)
                                            #10 0x00007f0ffc14345d _ZN2js4CallEP9JSContextN2JS6HandleINS2_5ValueEEES5_RKNS_13AnyInvokeArgsENS2_13MutableHandleIS4_EE (libmozjs-52.so.0)
                                            #11 0x00007f0ffbf2f915 _ZN2js3jit14InvokeFunctionEP9JSContextN2JS6HandleIP8JSObjectEEbjPNS3_5ValueENS3_13MutableHandleIS8_EE (libmozjs-52.so.0)
                                            #12 0x00002538e22ed3c6 n/a (n/a)
                                            #13 0x00007f0ffbe4b1ad _ZN2js3jit9IonCannonEP9JSContextRNS_8RunStateE (libmozjs-52.so.0)
                                            #14 0x00007f0ffc142328 _ZL9InterpretP9JSContextRN2js8RunStateE (libmozjs-52.so.0)
                                            #15 0x00007f0ffc142dad _ZN2js9RunScriptEP9JSContextRNS_8RunStateE (libmozjs-52.so.0)
                                            #16 0x00007f0ffc14317a _ZN2js23InternalCallOrConstructEP9JSContextRKN2JS8CallArgsENS_14MaybeConstructE (libmozjs-52.so.0)

Comment 162 mobidyc 2018-04-30 11:32:33 UTC
*** Bug 1573159 has been marked as a duplicate of this bug. ***

Comment 163 dizzy 2018-05-03 06:23:48 UTC
switched gnome session to x.org - crashes happen too (as expected) but less frequent (most fs mounts happen without crash) and applications usually (but not always) survive gnome shell restarts

Comment 164 Test 2018-05-03 21:43:47 UTC
*** Bug 1574727 has been marked as a duplicate of this bug. ***

Comment 165 Evgeniy Kravchenko 2018-05-05 07:36:08 UTC
Similar problem has been detected:

I updated Evolution mails when it happened. There are Exchange, Google and IMAP accounts in it. Also the Firefox was opened with approx 5 tabs.

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=71228378ef33438aa17c0f26783821c8;i=28e1;b=38c02205136840c785f70e26180451fd;m=288fe3521;t=56b70239e8bf1;x=2c7a43524cd678c1
kernel:         4.15.17-300.fc27.x86_64
package:        gnome-shell-3.26.2-5.fc27
reason:         gnome-shell killed by SIGSEGV
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000

Comment 166 herve.gaucher 2018-05-05 15:06:10 UTC
*** Bug 1575273 has been marked as a duplicate of this bug. ***

Comment 167 Kevin R. Page 2018-05-08 07:35:16 UTC
I have been experiencing an unstable F27 installation for several months, with crashes of Xwayland and gnome-shell every day or two, particularly on resuming from suspend (on wayland and xorg). I've been tracking this bug as a possible cause.

I've been running for 10 days without the problem occurring with the workaround in bug #1553979 comment #37 (
https://bugzilla.redhat.com/show_bug.cgi?id=1553979#c37 ). I've not seen this level of stability for months.

This is anecdotal, and either my original problem or apparent solution may be a misdiagnosis of this bug, however I post here in case others are in the same situation. Apologies to those for who this isn't relevant.

Bug #1553979 is sensitive to memory pressure, which is consistent with my experience of the problem exhibiting more or less frequently as I've changed configuration or behaviour, and potentially as other bugs have been fixed.

Comment 168 Gerardo Muñoz 2018-06-04 22:57:28 UTC
Similar problem has been detected:

Just connect my smartphone to my PC, and then gnome shell crashed

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=63b693c64e574f36a39d920225893608;i=1285e2;b=cd6c80cd5606464f8d810d924429dac6;m=6d85098f0;t=56dd82a125f1b;x=f756d2048edfe261
kernel:         4.16.12-200.fc27.x86_64
package:        gnome-shell-3.26.2-5.fc27
reason:         gnome-shell killed by SIGSEGV
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000

Comment 169 netb2c 2018-06-20 01:27:34 UTC
*** Bug 1593061 has been marked as a duplicate of this bug. ***

Comment 170 mobidyc 2018-06-22 15:07:02 UTC
*** Bug 1594303 has been marked as a duplicate of this bug. ***

Comment 171 A. Lloyd Flanagan 2018-06-28 15:01:11 UTC
Similar problem has been detected:

Booted Linux, logged in as standard user, opened trash, clicked "Empty". That's it.

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=8ce7499ff9d84f9c940706a578f308cc;i=680e1;b=441d8e1423d34524ba45d127ac37443b;m=71222d5;t=56fb4e16021a3;x=743daf5b01c8ce1c
kernel:         4.16.16-200.fc27.x86_64
package:        gnome-shell-3.26.2-5.fc27
reason:         gnome-shell killed by SIGSEGV
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000

Comment 172 Robert Mader 2018-07-09 14:23:19 UTC
I'm also experiencing this bug on fedora 28, clipboard-indicator installed (which seems to trigger it at least some times).

I'd like to point out that it seems to have been fixed in ubuntu 18.04 for some time now: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1714989

I would be very greatful if the needed patch could get backported :)

Comment 173 Robert Mader 2018-07-09 15:39:53 UTC
Looks like it's this PR that fixes the issue: https://gitlab.gnome.org/GNOME/gnome-shell/merge_requests/115

It got merged after gnome-shell 3.29.2, so even on rawhide it's not fixed yet (can confirm the crash still happens on 3.29.2.1.fc29). Please backport this one as it makes life much harder and dangerous on the gnome-shell! :)

Comment 174 Robert Mader 2018-07-09 16:53:56 UTC
Well it seems this is also needed: https://gitlab.gnome.org/GNOME/gnome-shell/merge_requests/79

So we have the following commits, all of which got backported to ubuntu 18.04 and debian already:
https://gitlab.gnome.org/GNOME/gnome-shell/commit/44894262f49b9f8b2809321ebcf1cd9426303fd6
https://gitlab.gnome.org/GNOME/gnome-shell/commit/a24999b7a317483d20a4df0abdf04f40f9bf95ed
https://gitlab.gnome.org/GNOME/gnome-shell/commit/1f03599d1cf888f73a33363212b99905064e2c9e


For everyone suffering from this, here's a copr with the corresponding patches in the mean time: https://copr.fedorainfracloud.org/coprs/treba/gnome-shell-fixed/

Comment 175 jan p. springer 2018-07-09 17:10:12 UTC
(In reply to Robert Mader from comment #174)
thank you so much, that works fabulous.

Comment 176 Robert Mader 2018-07-13 12:58:16 UTC
Have to confirm that crashes still happen with clipboard-indicator installed. In the MR https://gitlab.gnome.org/GNOME/gnome-shell/merge_requests/115 the author also says:

> Crashes on st-label still continues to be around, while I've planned to do to some further changes to gjs to prevent this, also st-label should just warn when we use disposed elements, instead of causing crashes.

Comment 177 Arik Kfir 2018-07-24 07:39:59 UTC
*** Bug 1607746 has been marked as a duplicate of this bug. ***

Comment 180 Ben Cotton 2018-11-27 13:59:13 UTC
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.

Comment 181 Ben Cotton 2018-11-30 19:55:13 UTC
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.


Note You need to log in before you can comment on or make changes to this bug.