Description of problem: Running PyCharm Professional, quit the application, screen froze for about 10 seconds and crashed out to GDM login screen. Version-Release number of selected component: gnome-shell-3.28.2-1.fc28 Additional info: reporter: libreport-2.9.5 backtrace_rating: 4 cmdline: /usr/bin/gnome-shell executable: /usr/bin/gnome-shell journald_cursor: s=69f329df491d4a87bbcff7ae75eeabcc;i=44db;b=0929a31146e140e1b2eb6d716cc58779;m=4e3029327;t=56ce21fe48bed;x=dcafbaac94fd9481 kernel: 4.16.9-300.fc28.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 1000
Created attachment 1440683 [details] File: backtrace
Created attachment 1440684 [details] File: cgroup
Created attachment 1440685 [details] File: core_backtrace
Created attachment 1440686 [details] File: cpuinfo
Created attachment 1440687 [details] File: dso_list
Created attachment 1440688 [details] File: environ
Created attachment 1440689 [details] File: limits
Created attachment 1440690 [details] File: maps
Created attachment 1440691 [details] File: mountinfo
Created attachment 1440692 [details] File: open_fds
Created attachment 1440693 [details] File: proc_pid_status
Created attachment 1440694 [details] File: var_log_messages
*** Bug 1582364 has been marked as a duplicate of this bug. ***
Similar problem has been detected: GNOME Shell crashes when I close Evolution. It seems to be easily reproducible as it has happened many times. reporter: libreport-2.9.5 backtrace_rating: 4 cmdline: /usr/bin/gnome-shell executable: /usr/bin/gnome-shell journald_cursor: s=06397ce6af3f4e198c9728974dd1eaf1;i=e2149;b=4d4c28c19d784f7fa303ac0be5e1ccee;m=6e404186;t=56cfe637c30cb;x=5d023a6714368470 kernel: 4.16.10-300.fc28.x86_64 package: gnome-shell-3.28.2-1.fc28 reason: gnome-shell killed by SIGTRAP rootdir: / runlevel: N 5 type: CCpp uid: 1001
*** Bug 1583397 has been marked as a duplicate of this bug. ***
Similar problem has been detected: Finished reading email with evolution. Nothing unexpected occurring. Gnome crashed, back to login. reporter: libreport-2.9.5 backtrace_rating: 4 cmdline: /usr/bin/gnome-shell executable: /usr/bin/gnome-shell journald_cursor: s=5f05a03c80ee413cb13eb630d83e2410;i=31123;b=b4a91f35fd724a919d7465a0074cc4fa;m=59863e16;t=56d7462d6400b;x=dd43dbc3687672b2 kernel: 4.15.14-300.fc27.x86_64 package: gnome-shell-3.28.2-1.fc28 reason: gnome-shell killed by SIGTRAP rootdir: / runlevel: N 5 type: CCpp uid: 1000
*** Bug 1585423 has been marked as a duplicate of this bug. ***
*** Bug 1588129 has been marked as a duplicate of this bug. ***
Similar problem has been detected: I clicked on evince to close... reporter: libreport-2.9.5 backtrace_rating: 3 cmdline: /usr/bin/gnome-shell executable: /usr/bin/gnome-shell journald_cursor: s=1e61e4e254d347538730f13e84667e60;i=10e6e;b=ddb8613ec5fb484a912c3ef99c2c1689;m=14d3778b5;t=56e3571d45184;x=63e4269ae1b8f189 kernel: 4.16.13-300.fc28.x86_64 package: gnome-shell-3.28.2-1.fc28 reason: gnome-shell killed by SIGTRAP rootdir: / runlevel: N 5 type: CCpp uid: 1000
*** Bug 1590276 has been marked as a duplicate of this bug. ***
*** Bug 1590540 has been marked as a duplicate of this bug. ***
Similar problem has been detected: Right out of the blue, after about 1/2 hour in evolution and a bit of Firefox, the entire Gnome crashed upon exit from evolution. This is a repeat of about 4 other crashes, over 2 months now. Where is the fix for this highest-priority issue??? reporter: libreport-2.9.5 backtrace_rating: 3 cmdline: /usr/bin/gnome-shell executable: /usr/bin/gnome-shell journald_cursor: s=5f05a03c80ee413cb13eb630d83e2410;i=3d72c;b=e2f74348c5164b5daa62079cd2c5adaa;m=6b4566f1;t=56e79aeffce5b;x=ca0dce966c365b2e kernel: 4.15.14-300.fc27.x86_64 package: gnome-shell-3.28.2-1.fc28 reason: gnome-shell killed by SIGTRAP rootdir: / runlevel: N 5 type: CCpp uid: 1000
*** Bug 1592589 has been marked as a duplicate of this bug. ***
*** Bug 1592829 has been marked as a duplicate of this bug. ***
*** Bug 1600136 has been marked as a duplicate of this bug. ***
*** Bug 1609481 has been marked as a duplicate of this bug. ***
Problem still present 2018/07/27, with all Fedora updates applied and machine operating normally. Same trigger - evolution termination causing the crash.
Please attach the highest possible priority to this, as this bug destroys your gnome session and kills all running apps in gnome, is fairly repeatable, and has a large number of Customers affected. It is hard to imaging a higher priority bug.
*** Bug 1610402 has been marked as a duplicate of this bug. ***
*** Bug 1613220 has been marked as a duplicate of this bug. ***
Similar problem has been detected: I was shutting Evolution down and removed the Ethernet cable from laptop while it was trying to save updates to the IMAP folders in my email accounts. It hung for a minute, and then a dialog opened asking if I wanted to wait or close the program right away. I chose to close it right away, and Gnome seemed to crash, leaving me back at the login page. I could log in again, and everything seemed fine. I am using Feodra 28. reporter: libreport-2.9.5 backtrace_rating: 3 cmdline: /usr/bin/gnome-shell crash_function: dump_gjs_stack_on_signal_handler executable: /usr/bin/gnome-shell journald_cursor: s=94475619ad6c4342b1a2cc34b977617b;i=18d9d2;b=f3e4c3e3a57349e592881c8669eb109a;m=1f80ef769;t=573419f8ec85e;x=773b8085f3b16c0e kernel: 4.17.9-200.fc28.x86_64 package: gnome-shell-3.28.3-1.fc28 reason: gnome-shell killed by SIGTRAP rootdir: / runlevel: N 5 type: CCpp uid: 10000
*** Bug 1615918 has been marked as a duplicate of this bug. ***
*** Bug 1619237 has been marked as a duplicate of this bug. ***
*** Bug 1620992 has been marked as a duplicate of this bug. ***
*** Bug 1621065 has been marked as a duplicate of this bug. ***
Similar problem has been detected: - Log in new Wayland session. - Start firefox-wayland - Open a couple of tabs in the main window and a private browsing window, also with one or two tabs - Close main window - Close private window - Gnome shell crashed. reporter: libreport-2.9.5 backtrace_rating: 4 cmdline: /usr/bin/gnome-shell crash_function: raise executable: /usr/bin/gnome-shell journald_cursor: s=40034e1a68b443a4b382fdd5fc390aa7;i=1ec82;b=80b753c2426348da9400ec977b11a332;m=28affcb7;t=57540225bf39f;x=96ee6a41b210d41b kernel: 4.18.5-200.fc28.x86_64 package: gnome-shell-3.28.3-1.fc28 reason: gnome-shell killed by SIGTRAP rootdir: / runlevel: N 5 type: CCpp uid: 1000
*** Bug 1619026 has been marked as a duplicate of this bug. ***
*** Bug 1626758 has been marked as a duplicate of this bug. ***
*** Bug 1629365 has been marked as a duplicate of this bug. ***
Similar problem has been detected: Normal evolution exit and the whole desktop crashed. This has been happening for the entire life of Fedora-28, with no signs of a fix. Can we please move back to a stable version of Gnome from Fedora-27 or previous? reporter: libreport-2.9.5 backtrace_rating: 3 cmdline: /usr/bin/gnome-shell crash_function: dump_gjs_stack_on_signal_handler executable: /usr/bin/gnome-shell journald_cursor: s=5f05a03c80ee413cb13eb630d83e2410;i=bdfe4;b=dffaacb7066843caab753461632fb9a3;m=316b7483;t=57669b67c807b;x=360e0c441b0ae651 kernel: 4.15.14-300.fc27.x86_64 package: gnome-shell-3.28.3-1.fc28 reason: gnome-shell killed by SIGTRAP rootdir: / runlevel: N 5 type: CCpp uid: 1000
*** Bug 1632888 has been marked as a duplicate of this bug. ***
*** Bug 1633261 has been marked as a duplicate of this bug. ***
Similar problem has been detected: Evolution normal exit still causing a fatal Gnome crash. Fedora 28 is fully up-to-date. reporter: libreport-2.9.5 backtrace_rating: 3 cmdline: /usr/bin/gnome-shell crash_function: dump_gjs_stack_on_signal_handler executable: /usr/bin/gnome-shell journald_cursor: s=5f05a03c80ee413cb13eb630d83e2410;i=c3204;b=c4a8f1a403f24d548980a821d362f4c8;m=468abf87;t=576d079497b5c;x=e9810420903dac8 kernel: 4.15.14-300.fc27.x86_64 package: gnome-shell-3.28.3-1.fc28 reason: gnome-shell killed by SIGTRAP rootdir: / runlevel: N 5 type: CCpp uid: 1000
*** Bug 1635209 has been marked as a duplicate of this bug. ***
*** Bug 1635596 has been marked as a duplicate of this bug. ***
*** Bug 1635661 has been marked as a duplicate of this bug. ***
Similar problem has been detected: Trying to copy text with CTRL+C in an etherpad tab in Firefox-wayland. reporter: libreport-2.9.5 backtrace_rating: 3 cmdline: /usr/bin/gnome-shell crash_function: dump_gjs_stack_on_signal_handler executable: /usr/bin/gnome-shell journald_cursor: s=c915b4b30af843fa81060d930eb509d9;i=1fe3b1;b=0c394e2bfad14a26be1cb618ebae7034;m=b0b16805;t=5776388a37691;x=52a9a23590d420d2 kernel: 4.18.9-200.fc28.x86_64 package: gnome-shell-3.28.3-1.fc28 reason: gnome-shell killed by SIGTRAP rootdir: / runlevel: N 5 type: CCpp uid: 501
In my case the gnome-shell crash was preceded in the journal by a couple of possibly related messages about timestamps: Oct 04 11:10:55 hp org.gnome.Shell.desktop[1066]: Window manager warning: last_user_time (2958273) is greater than comparison timestamp (2958239). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around... Oct 04 11:10:55 hp org.gnome.Shell.desktop[1066]: Window manager warning: W18 (Red Hat Et) appears to be one of the offending windows with a timestamp of 2958273. Working around... Oct 04 11:10:59 hp gnome-shell[1066]: The program 'gnome-shell' received an X Window System error. This probably reflects a bug in the program. The error was 'BadWindow (invalid Window parameter)'. (Details: serial 5952 error_code 3 request_code 18 (core protocol) minor_code 0) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the GDK_SYNCHRONIZE environment variable to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.)
Similar problem has been detected: normal evolution exit. Nothing noticed, then BLAM!!! Gnome shell crash kills entire desktop session. reporter: libreport-2.9.5 backtrace_rating: 3 cmdline: /usr/bin/gnome-shell crash_function: dump_gjs_stack_on_signal_handler executable: /usr/bin/gnome-shell journald_cursor: s=5f05a03c80ee413cb13eb630d83e2410;i=ca3bf;b=b8f052d36814436d83c4482dac473cdb;m=5316630b;t=5776e908264e8;x=654ad3af76d81a59 kernel: 4.15.14-300.fc27.x86_64 package: gnome-shell-3.28.3-1.fc28 reason: gnome-shell killed by SIGTRAP rootdir: / runlevel: N 5 type: CCpp uid: 1000
Similar problem has been detected: gnome-shell crash, maybe just after resume from suspend? gnome-shell seems to be spamming stack traces every minute or so anyway, so I don't know if any of them are relevant to the crash. Oct 08 13:05:12 alan-laptop gnome-shell[2074]: The program 'gnome-shell' received an X Window System error. This probably reflects a bug in the program. The error was 'BadWindow (invalid Window parameter)'. (Details: serial 655043 error_code 3 request_code 18 (core protocol) minor_code 0) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the GDK_SYNCHRONIZE environment variable to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.) reporter: libreport-2.9.5 backtrace_rating: 3 cmdline: /usr/bin/gnome-shell crash_function: dump_gjs_stack_on_signal_handler executable: /usr/bin/gnome-shell journald_cursor: s=2dfd4bfd0b9c49e7bf8baeec3ec3ffc7;i=7f76fa;b=20ee7f8eb413415cb1c92e59d58849e4;m=287d7623fc;t=577b6718d8fc4;x=51fdd985c4bd0f1 kernel: 4.18.10-200.fc28.x86_64 package: gnome-shell-3.28.3-1.fc28 reason: gnome-shell killed by SIGTRAP rootdir: / runlevel: N 5 type: CCpp uid: 1001
*** Bug 1637975 has been marked as a duplicate of this bug. ***
Similar problem has been detected: Firefox and evolution both running. Exit from evolution and instant Gnome shell crash, Previously reported many times before, by many people. reporter: libreport-2.9.5 backtrace_rating: 3 cmdline: /usr/bin/gnome-shell crash_function: dump_gjs_stack_on_signal_handler executable: /usr/bin/gnome-shell journald_cursor: s=5f05a03c80ee413cb13eb630d83e2410;i=d1e78;b=139d84e6e1434921bdc821437d8a3989;m=488eb974;t=577e7fb8292aa;x=ec144365d727b6d5 kernel: 4.15.14-300.fc27.x86_64 package: gnome-shell-3.28.3-1.fc28 reason: gnome-shell killed by SIGTRAP rootdir: / runlevel: N 5 type: CCpp uid: 1000
*** Bug 1638157 has been marked as a duplicate of this bug. ***
Similar problem has been detected: exit evolution causes an immediate gnome shell crash. The only other app open on the desktop was firefox. I run evolution on Ubuntu 16 and 18 as well, and it only crashes on Fedora 28 for me. It was also stable in Fedora 26. Evolution exit causes a complete desktop failure about 10% of the time, implying some really serious design errors in desktop separation from the application.. reporter: libreport-2.9.5 backtrace_rating: 3 cmdline: /usr/bin/gnome-shell crash_function: dump_gjs_stack_on_signal_handler executable: /usr/bin/gnome-shell journald_cursor: s=5f05a03c80ee413cb13eb630d83e2410;i=d360e;b=a944f804ccd949e0a5fe725926d6cef0;m=5caff089;t=578128972de5a;x=3236ff89f5af3485 kernel: 4.15.14-300.fc27.x86_64 package: gnome-shell-3.28.3-1.fc28 reason: gnome-shell killed by SIGTRAP rootdir: / runlevel: N 5 type: CCpp uid: 1000
*** Bug 1639011 has been marked as a duplicate of this bug. ***
*** Bug 1641375 has been marked as a duplicate of this bug. ***
*** Bug 1642505 has been marked as a duplicate of this bug. ***
*** Bug 1642537 has been marked as a duplicate of this bug. ***
Similar problem has been detected: Evolution and Firefox open. Finished reading email, closed evolution and gnome shell crashed. This problem has occurred throughout the entire life of Fedora 28, and no fixes done. Please mark Evolution as unstable software and replace it in F29. reporter: libreport-2.9.5 backtrace_rating: 3 cmdline: /usr/bin/gnome-shell crash_function: dump_gjs_stack_on_signal_handler executable: /usr/bin/gnome-shell journald_cursor: s=5f05a03c80ee413cb13eb630d83e2410;i=e1804;b=040e13f5788c4d6fba733811253806ab;m=2550faba;t=5794904feecd7;x=84dc998a877ffb40 kernel: 4.15.14-300.fc27.x86_64 package: gnome-shell-3.28.3-1.fc28 reason: gnome-shell killed by SIGTRAP rootdir: / runlevel: N 5 type: CCpp uid: 1000
Similar problem has been detected: Exit Evolution from a Wayland session. Does not happen consistently. reporter: libreport-2.9.5 backtrace_rating: 3 cmdline: /usr/bin/gnome-shell crash_function: dump_gjs_stack_on_signal_handler executable: /usr/bin/gnome-shell journald_cursor: s=b4cfc7621e9d4ba3b66d5723ae42d461;i=33743;b=add93124e3d84ff7857f733cfd93a55d;m=a610626b;t=57aa12e52a4c1;x=cec71864eadec61b kernel: 4.18.17-200.fc28.x86_64 package: gnome-shell-3.28.3-1.fc28 reason: gnome-shell killed by SIGTRAP rootdir: / runlevel: N 5 type: CCpp uid: 1000
*** Bug 1650052 has been marked as a duplicate of this bug. ***
*** Bug 1654859 has been marked as a duplicate of this bug. ***
I think I have a highly repeatable scenario for this problem: Open Evolution, with 2 accounts - one imap from upstream provider and one gmail managed via Gnome. Read some email. Open Firefox, any realease in the last 2 years. Read some web sites. Read the rest of your unopened email. Exit Evolution. Note total Gnome Shell crash upon exit.
Can we please mark this as a blocker bug for Fedora 30? This is a fatal UI bug that has been in Fedora-only for multiple releases now, and is overdue for a fix.
*** Bug 1677983 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.