Hide Forgot
Description of problem: The gnome shell crashes. The issue occurs at random times (often when connected to a remote server via ssh -X) Version-Release number of selected component: gnome-shell-3.28.1-3.fc28 Additional info: reporter: libreport-2.9.5 backtrace_rating: 3 cmdline: /usr/bin/gnome-shell crash_function: g_type_check_instance_cast executable: /usr/bin/gnome-shell journald_cursor: s=4a242f2e16e0426c9acb5c7606117a4e;i=5275b;b=2da252a16d5c4bfda354693001a70fd5;m=76c8e4179a;t=56bafe20c807f;x=8cc18b056fdd3f68 kernel: 4.16.5-300.fc28.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_set_text #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:1088 #5 function_call(JSContext*, unsigned int, JS::Value*) at /usr/include/c++/8/new:169 #6 js::CallJSNative(JSContext*, bool (*)(JSContext*, unsigned int, JS::Value*), JS::CallArgs const&) at /usr/src/debug/mozjs52-52.7.3-1.fc28.x86_64/jscntxtinlines.h:239 #7 js::InternalCallOrConstruct(JSContext*, JS::CallArgs const&, js::MaybeConstruct) at /usr/src/debug/mozjs52-52.7.3-1.fc28.x86_64/vm/Interpreter.cpp:447 #8 InternalCall(JSContext*, js::AnyInvokeArgs const&) at /usr/src/debug/mozjs52-52.7.3-1.fc28.x86_64/vm/Interpreter.cpp:504 #9 js::Call(JSContext*, JS::Handle<JS::Value>, JS::Handle<JS::Value>, js::AnyInvokeArgs const&, JS::MutableHandle<JS::Value>) at /usr/src/debug/mozjs52-52.7.3-1.fc28.x86_64/vm/Interpreter.cpp:523 Potential duplicate: bug 1489554
Created attachment 1433159 [details] File: backtrace
Created attachment 1433160 [details] File: cgroup
Created attachment 1433161 [details] File: core_backtrace
Created attachment 1433162 [details] File: cpuinfo
Created attachment 1433163 [details] File: dso_list
Created attachment 1433164 [details] File: environ
Created attachment 1433165 [details] File: exploitable
Created attachment 1433166 [details] File: limits
Created attachment 1433167 [details] File: maps
Created attachment 1433168 [details] File: mountinfo
Created attachment 1433169 [details] File: open_fds
Created attachment 1433170 [details] File: proc_pid_status
Created attachment 1433171 [details] File: var_log_messages
Similar problem has been detected: I get regular GNOME Shell crashes to the login screen, mostly with unusable dumps. This is probably related to WiFi networks being switched, as the problems only occur when the WiFi connection is unstable and ethernet is not plugged in. Additionally, right after my GNOME session crashing and returning to the login screen, the "WiFi connection could not be activated" notification is shown. The behaviour seems similar to [1539895](https://bugzilla.redhat.com/show_bug.cgi?id=1539895) and [1575951](https://bugzilla.redhat.com/show_bug.cgi?id=1575951). When logging back in again after the crash, evolution is not able to fetch any e-mails and reports "source doesn't support prompt for credentials". This is probably interesting for [1340203](https://bugzilla.redhat.com/show_bug.cgi?id=1340203) and possibly also the cause for [1554936](https://bugzilla.redhat.com/show_bug.cgi?id=1554936) . reporter: libreport-2.9.5 backtrace_rating: 3 cmdline: /usr/bin/gnome-shell crash_function: g_type_check_instance_cast executable: /usr/bin/gnome-shell journald_cursor: s=4b1f7cbdccb64d17990dca3397f9396d;i=82eaa;b=eaaeefde6a3a41949b8194aafe39e15a;m=114f84462;t=56bd57418018c;x=f3b343b0f0271c88 kernel: 4.16.5-300.fc28.x86_64 package: gnome-shell-3.28.1-3.fc28 reason: gnome-shell killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
Created attachment 1434808 [details] var_log_messages - similar already deallocated errors, but for different objects My syslog looks similar to the one uploaded by dwskylander, but instead of Gio.Settings in my case Shell.GenericContainer, St.Widget and Meta.WindowActor are the problematic objects. Additionally, the stack trace only involves some "tweener.js" files and no GNOME shell plug-ins.
*** Bug 1578105 has been marked as a duplicate of this bug. ***
*** Bug 1578977 has been marked as a duplicate of this bug. ***
*** Bug 1579509 has been marked as a duplicate of this bug. ***
*** Bug 1579774 has been marked as a duplicate of this bug. ***
Similar problem has been detected: I opened Gnome Files and connected to an Other Location that was a windows SMB fileshare. I got the signin window and entered my credentials. On hitting OK, Gnome Shell crashed. I've had the same issue when connecting to Google Drive and other SMB file share so it feels like it's a Gnome Files issue. Most of the time when this happens, I sign in, try agan and it connects to Google Drive or the SMB file share without problem. I'm continually updating to the latest stable versions in Fedora 28 and I'm running Wayland Gnome Session. reporter: libreport-2.9.5 backtrace_rating: 3 cmdline: /usr/bin/gnome-shell crash_function: g_type_check_instance_cast executable: /usr/bin/gnome-shell journald_cursor: s=5ae27fd57da64c53a0317d8cf4bd79ca;i=7c458;b=aa2990ff6e8341c89ae70bb11933e654;m=74973280c;t=56cc6868e8c14;x=3462b2c182ee0c5a kernel: 4.16.8-300.fc28.x86_64 package: gnome-shell-3.28.2-1.fc28 reason: gnome-shell killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
Similar problem has been detected: Locked my desktop reporter: libreport-2.9.5 backtrace_rating: 4 cmdline: /usr/bin/gnome-shell crash_function: g_type_check_instance_cast executable: /usr/bin/gnome-shell journald_cursor: s=45fdc86cf9264375884f9bce8d5c3cec;i=42ff8;b=83eda5964c704a168d0a8414485f89b3;m=23e0cd18e;t=56f903052bc12;x=c0b384aa4b5819d2 kernel: 4.17.2-200.fc28.x86_64 package: gnome-shell-3.28.2-1.fc28 reason: gnome-shell killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 5040
Created attachment 1454788 [details] File: backtrace
*** Bug 1596932 has been marked as a duplicate of this bug. ***
*** Bug 1629597 has been marked as a duplicate of this bug. ***
This message is a reminder that Fedora 28 is nearing its end of life. On 2019-May-28 Fedora will stop maintaining and issuing updates for Fedora 28. 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 '28'. 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 28 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 28 changed to end-of-life (EOL) status on 2019-05-28. Fedora 28 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.