Description of problem: I was developing a Python application using PyQt5 in PyCharm (riddled with bugs :D) When launching the app, the Gnome shell crashed. This crash happened only once. First occurrence. Version-Release number of selected component: gnome-shell-3.24.2-1.fc26 Additional info: reporter: libreport-2.9.1 backtrace_rating: 4 cmdline: /usr/bin/gnome-shell crash_function: meta_window_unmanage executable: /usr/bin/gnome-shell journald_cursor: s=ebf182228bb846c9aa3139d112408896;i=15a55;b=5b280c2cdaf341e189935b627a1ab316;m=d23c1d88b;t=5548985ebff82;x=656c5facfff14e81 kernel: 4.11.9-300.fc26.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 1000 Potential duplicate: bug 1312751
Created attachment 1300100 [details] File: backtrace
Created attachment 1300101 [details] File: cgroup
Created attachment 1300102 [details] File: core_backtrace
Created attachment 1300103 [details] File: cpuinfo
Created attachment 1300104 [details] File: dso_list
Created attachment 1300105 [details] File: environ
Created attachment 1300106 [details] File: limits
Created attachment 1300107 [details] File: maps
Created attachment 1300108 [details] File: open_fds
Created attachment 1300109 [details] File: proc_pid_status
Created attachment 1300110 [details] File: var_log_messages
Similar problem has been detected: Opened WebStorm and was thrown to the GNOME login screen. WebStorm had been opened successfully immediately prior to the crash. Among the other open programs were Files, Chrome, and JetBrains ToolBox. reporter: libreport-2.9.1 backtrace_rating: 4 cmdline: /usr/bin/gnome-shell crash_function: meta_window_unmanage executable: /usr/bin/gnome-shell journald_cursor: s=fe286b0a0cf84c2c91b081348ef8724a;i=6389d;b=b8f960e0be4740a9aae457c674b273ef;m=cb58f1c8;t=554eefd10ae02;x=a79a42f274414d2e kernel: 4.11.10-300.fc26.x86_64 package: gnome-shell-3.24.2-1.fc26 reason: gnome-shell killed by signal 6 rootdir: / runlevel: N 5 type: CCpp uid: 1000
Similar problem has been detected: I was developing a pyqt5 application in PyCharm. I just clicked on the run button and immediately resized the main window to the left half of my monitor. This was not the first run of my application and cannot be reproduced. reporter: libreport-2.9.1 backtrace_rating: 4 cmdline: /usr/bin/gnome-shell crash_function: meta_window_unmanage executable: /usr/bin/gnome-shell journald_cursor: s=ebf182228bb846c9aa3139d112408896;i=a26b0;b=f3e3d26f8f4d45b291c591a4af5953a1;m=147c04fd4d;t=55569d99fcc99;x=f71df82095bd43b9 kernel: 4.11.11-300.fc26.x86_64 package: gnome-shell-3.24.3-1.fc26 reason: gnome-shell killed by signal 6 rootdir: / runlevel: N 5 type: CCpp uid: 1000
Similar problem has been detected: Still developing my pyqt5 application. I can reproduce this crash by launching my app and immediately resize the window to the left half of the window by moving it to the left border of the screen. On startup, my app accesses the web and blocks the gui loop. It's a work in progress. reporter: libreport-2.9.1 backtrace_rating: 4 cmdline: /usr/bin/gnome-shell crash_function: meta_window_unmanage executable: /usr/bin/gnome-shell journald_cursor: s=ebf182228bb846c9aa3139d112408896;i=a3bc3;b=f3e3d26f8f4d45b291c591a4af5953a1;m=14ed8c506d;t=5556a4b271fb9;x=f90c09cdac82dd70 kernel: 4.11.11-300.fc26.x86_64 package: gnome-shell-3.24.3-1.fc26 reason: gnome-shell killed by signal 6 rootdir: / runlevel: N 5 type: CCpp uid: 1000
*** Bug 1480603 has been marked as a duplicate of this bug. ***
*** Bug 1480641 has been marked as a duplicate of this bug. ***
Similar problem has been detected: I was resuming a WinXP VM in VirtualBox. As soon as it was done - presumably, about to show a new window - Gnome shell crashed. I've done this several times before, but this is the first time I got a crash. reporter: libreport-2.9.1 backtrace_rating: 4 cmdline: /usr/bin/gnome-shell crash_function: meta_window_unmanage executable: /usr/bin/gnome-shell journald_cursor: s=9b397d177151466ab5c377b0289c5bad;i=149cf;b=f442f00dfdcb4030af1425842db87eae;m=3285ec1dc;t=5573536b0a35e;x=c465258b107dab21 kernel: 4.12.5-300.fc26.x86_64 package: gnome-shell-3.24.3-1.fc26 reason: gnome-shell killed by signal 6 rootdir: / runlevel: N 5 type: CCpp uid: 1000
Similar problem has been detected: Maximizing window of InteliJ IDEA 2017.2.2 on secondary screen. reporter: libreport-2.9.1 backtrace_rating: 4 cmdline: /usr/bin/gnome-shell crash_function: meta_window_unmanage executable: /usr/bin/gnome-shell journald_cursor: s=2a73e490eeae4fba9f96671e2eed2a9d;i=12bee;b=75b8d638a0964f6694d5c059b83b07c0;m=67a1bc3e5;t=557484a61ea59;x=66dd240492955677 kernel: 4.12.5-300.fc26.x86_64 package: gnome-shell-3.24.3-1.fc26 reason: gnome-shell killed by signal 6 rootdir: / runlevel: N 5 type: CCpp uid: 1000
*** Bug 1484013 has been marked as a duplicate of this bug. ***
*** Bug 1486932 has been marked as a duplicate of this bug. ***
*** Bug 1487824 has been marked as a duplicate of this bug. ***
*** Bug 1491719 has been marked as a duplicate of this bug. ***
*** Bug 1495319 has been marked as a duplicate of this bug. ***
Similar problem has been detected: I just closed Planner (https://wiki.gnome.org/action/show/Apps/Planner?action=show&redirect=Planner). It happened several times. reporter: libreport-2.9.1 backtrace_rating: 4 cmdline: /usr/bin/gnome-shell crash_function: meta_window_unmanage executable: /usr/bin/gnome-shell journald_cursor: s=6944ecdb56ea497892b11e3f0e6d055b;i=5f80;b=07b578dfe77c4ab2a01cadd033bcb48b;m=55985471;t=55b2b8459c8db;x=2f52f364b5215665 kernel: 4.13.4-200.fc26.x86_64 package: gnome-shell-3.24.3-2.fc26 reason: gnome-shell killed by SIGABRT rootdir: / runlevel: N 5 type: CCpp uid: 1000
Similar problem has been detected: I was moving progress dialog reporter: libreport-2.9.1 backtrace_rating: 4 cmdline: /usr/bin/gnome-shell crash_function: meta_window_unmanage executable: /usr/bin/gnome-shell journald_cursor: s=1b74d235af3f49f5a79e3ac4f1eb07bd;i=412d;b=352bb6796c5a4afdb0d1964dc5d4d855;m=fc8cfe303;t=55b2d28dd029f;x=65e5d87912fb1734 kernel: 4.13.4-200.fc26.x86_64 package: gnome-shell-3.24.3-2.fc26 reason: gnome-shell killed by SIGABRT rootdir: / runlevel: N 5 type: CCpp uid: 1000
*** Bug 1513921 has been marked as a duplicate of this bug. ***
Similar problem has been detected: Moved an Intellij IDEA window to a different screen. reporter: libreport-2.9.1 backtrace_rating: 4 cmdline: /usr/bin/gnome-shell crash_function: meta_window_unmanage executable: /usr/bin/gnome-shell journald_cursor: s=6e4cf1d5a88e44178bd21189c3bfb06d;i=1ec574;b=c3f275c10e3042119b288b7c1be8a8ed;m=8f0f362683;t=55fd15996915c;x=7c52a6516417bcb6 kernel: 4.13.15-200.fc26.x86_64 package: gnome-shell-3.24.3-2.fc26 reason: gnome-shell killed by SIGABRT rootdir: / runlevel: N 5 type: CCpp uid: 1000
*** Bug 1542403 has been marked as a duplicate of this bug. ***
This message is a reminder that Fedora 26 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 26. 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 '26'. 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 26 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 26 changed to end-of-life (EOL) status on 2018-05-29. Fedora 26 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.