Description of problem: After every boot on this computer, first session crashes as soon as I launch my first app. After that I can log back in and use the computer normally. Version-Release number of selected component: gnome-shell-3.28.3-1.fc28 Additional info: reporter: libreport-2.9.5 backtrace_rating: 4 cmdline: /usr/bin/gnome-shell crash_function: meta_window_place executable: /usr/bin/gnome-shell journald_cursor: s=c3f370e8d11643c9802c1728c173a7ea;i=1a7df;b=39a336f4036f4b26846697e8dfc6aae9;m=d2bc12f;t=5737c7d2f2a57;x=f24e5cf1ec703c56 kernel: 4.17.12-200.fc28.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 meta_window_place at core/place.c:894 #1 place_window_if_needed at core/constraints.c:488 #2 meta_window_constrain at core/constraints.c:299 #3 meta_window_move_resize_internal at core/window.c:3963 #4 meta_window_force_placement at core/window.c:2319 #5 meta_window_show at core/window.c:2401 #6 implement_showing at core/window.c:1721 #7 meta_window_calc_showing at core/window.c:1817 #8 idle_calc_showing at core/window.c:1817 #9 run_repaint_laters at core/util.c:809
Created attachment 1476226 [details] File: backtrace
Created attachment 1476227 [details] File: cgroup
Created attachment 1476228 [details] File: core_backtrace
Created attachment 1476229 [details] File: cpuinfo
Created attachment 1476230 [details] File: dso_list
Created attachment 1476231 [details] File: environ
Created attachment 1476232 [details] File: exploitable
Created attachment 1476233 [details] File: limits
Created attachment 1476234 [details] File: maps
Created attachment 1476235 [details] File: mountinfo
Created attachment 1476236 [details] File: open_fds
Created attachment 1476237 [details] File: proc_pid_status
Created attachment 1476238 [details] File: var_log_messages
Similar problem has been detected: I pulled the machine off its docking station reporter: libreport-2.9.5 backtrace_rating: 3 cmdline: /usr/bin/gnome-shell crash_function: meta_window_place executable: /usr/bin/gnome-shell journald_cursor: s=27faf2f7c1db40408ce71f28a71dd412;i=7367;b=d41b65a6f1e14166b37934ab50d194bf;m=e422be2b;t=579fd7bbaa94b;x=169b176d5e10851 kernel: 4.18.16-200.fc28.x86_64 package: gnome-shell-3.28.3-1.fc28 reason: gnome-shell killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
Still 100% reproducible to this day. A few more details: * the Microsoft Surface tablet this happens on has autologin enabled and it’s that first autologgedin session that crashes * I found out by accident that if I turn the tablet sideways for the accelerometer to trigger orientation change, then put it back to its landscape orientation, the crash doesn’t happen.
It’s probably also worth mentionning that this only happens on Wayland, not Xorg.
This message is a reminder that Fedora 29 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 29 on 2019-11-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 '29'. 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 29 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.
still valid on F31, according to reporter on irc
This message is a reminder that Fedora 31 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 31 on 2020-11-24. 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 '31'. 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 31 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 31 changed to end-of-life (EOL) status on 2020-11-24. Fedora 31 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.