Description of problem: Open gnome shell type remina and click to remina Version-Release number of selected component: gnome-shell-3.26.2-4.fc27 Additional info: 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=a76959373d2d402d934465e93641861f;i=279c9;b=7e69ca1e986d43f4adc93fdd908df7e2;m=4b7db043;t=563ef5d1f647d;x=5d09b52a1760ea0b kernel: 4.14.14-300.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:4058 #1 st_label_get_text at ../src/st/st-label.c:310 #2 append_actor_text at ../src/st/st-widget.c:2178 #3 st_describe_actor at ../src/st/st-widget.c:2243 #4 ffi_call_unix64 at ../src/x86/unix64.S:76 #5 ffi_call at ../src/x86/ffi64.c:525 #6 gjs_invoke_c_function(JSContext*, Function*, JS::HandleObject, JS::HandleValueArray const&, mozilla::Maybe<JS::MutableHandle<JS::Value> >, GIArgument*) at gi/function.cpp:1033 #7 function_call(JSContext*, unsigned int, JS::Value*) at gi/function.cpp:1351 #8 js::CallJSNative(JSContext*, bool (*)(JSContext*, unsigned int, JS::Value*), JS::CallArgs const&) at /usr/src/debug/mozjs52-52.5.0-1.fc27.x86_64/jscntxtinlines.h:239 #9 js::InternalCallOrConstruct(JSContext*, JS::CallArgs const&, js::MaybeConstruct) at /usr/src/debug/mozjs52-52.5.0-1.fc27.x86_64/vm/Interpreter.cpp:447
Created attachment 1387992 [details] File: backtrace
Created attachment 1387993 [details] File: cgroup
Created attachment 1387994 [details] File: core_backtrace
Created attachment 1387995 [details] File: cpuinfo
Created attachment 1387996 [details] File: dso_list
Created attachment 1387997 [details] File: environ
Created attachment 1387998 [details] File: exploitable
Created attachment 1387999 [details] File: limits
Created attachment 1388000 [details] File: maps
Created attachment 1388001 [details] File: mountinfo
Created attachment 1388002 [details] File: open_fds
Created attachment 1388003 [details] File: proc_pid_status
Created attachment 1388004 [details] File: var_log_messages
*** Bug 1542872 has been marked as a duplicate of this bug. ***
*** Bug 1543507 has been marked as a duplicate of this bug. ***
Similar problem has been detected: Not completely sure - I pressed the Super key while an application was starting. The shell then displayed one of the miniatures like I have been dragging it (even though I have not) and froze for a brief period. Then it 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=990b211e52b54424a2cf9dc5352c7cc3;i=f9b77;b=edf1788647144855b7f42e5d66f1060f;m=3e1f59e89e;t=565413fb5baaf;x=b117eb87b250044a kernel: 4.14.18-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 1546846 has been marked as a duplicate of this bug. ***
Non developer here. I experienced the same random crash. If I understood the ABRT FAQ correctly, I'm not able to generate a usable backtrace myself. Replaced Simple Gnome extension by Dash to Dock. I haven't experienced a Gnome Shell crash so far... Pavel, any chance you're using that same extension as well?
Same problem here. I was using chromium and other applications when the crash occured. Log in abrt: [...] Preparing environment for backtrace generation ............ Generating backtrace .... Cleaning environment after backtrace generation Retrace job finished successfully --- Running analyze_BodhiUpdates --- Auf Bugzilla nach ähnlichen Fehlern suchen Duplicate bugzilla bug '#1539895' was found Searching for updates No updates for this package found But it seems no usable backtrace could be generated. Is https://retrace.fedoraproject.org/faf/reports/2019710/ and https://retrace.fedoraproject.org/faf/reports/2061203/ the same problem?
*** Bug 1560742 has been marked as a duplicate of this bug. ***
Sorry, I unintentionally removed the needinfo flag. Comment 16 described the same thing I was doing when it crashed. I pressed the Super key at the exact moment when an application window is started (I was starting Tor Browser). The overlay froze right there, and few moments later I was dropped to GDM. ABRT fails to produce a backtrace with the same error as others have reported. I haven't installed any extensions to GNOME.
*** Bug 1568465 has been marked as a duplicate of this bug. ***
1575951 might be related, at least Pavel's var_log_messages looks similar to what I described in my comment: https://bugzilla.redhat.com/show_bug.cgi?id=1575951#c14
This message is a reminder that Fedora 27 is nearing its end of life. On 2018-Nov-30 Fedora will stop maintaining and issuing updates for Fedora 27. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '27'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 27 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 27 changed to end-of-life (EOL) status on 2018-11-30. Fedora 27 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.