Hide Forgot
Description of problem: Doing Alt+tab between Phpstorm / Google Chrome / Firefox & terminal Happening a lot of time, restarting gnome-shell. On X, gnome just restart, but on Wayland my session is killed and and I go back to gdm Version-Release number of selected component: gnome-shell-3.22.2-2.fc25 Additional info: reporter: libreport-2.8.0 backtrace_rating: 4 cmdline: /usr/bin/gnome-shell crash_function: __memmove_sse2_unaligned_erms executable: /usr/bin/gnome-shell global_pid: 17995 kernel: 4.8.12-300.fc25.x86_64 pkg_fingerprint: 4089 D8F2 FDB1 9C98 pkg_vendor: Fedora Project runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 __memmove_sse2_unaligned_erms at ../sysdeps/x86_64/multiarch/memmove-vec-unaligned-erms.S:345 #1 memcpy at /usr/include/bits/string3.h:53 #2 nouveau_scratch_data at nouveau_buffer.c:1006 #3 nvc0_update_user_vbufs_shared at nvc0/nvc0_vbo.c:292 #4 nvc0_state_validate at nvc0/nvc0_state_validate.c:832 #5 nvc0_state_validate_3d at nvc0/nvc0_state_validate.c:850 #6 nvc0_draw_vbo at nvc0/nvc0_vbo.c:977 #7 cso_draw_arrays at cso_cache/cso_context.c:1687 #8 st_draw_quad at state_tracker/st_draw.c:487 #9 clear_with_quad at state_tracker/st_cb_clear.c:297
Created attachment 1230860 [details] File: backtrace
Created attachment 1230861 [details] File: cgroup
Created attachment 1230862 [details] File: core_backtrace
Created attachment 1230863 [details] File: dso_list
Created attachment 1230864 [details] File: environ
Created attachment 1230865 [details] File: exploitable
Created attachment 1230866 [details] File: limits
Created attachment 1230867 [details] File: maps
Created attachment 1230868 [details] File: mountinfo
Created attachment 1230869 [details] File: namespaces
Created attachment 1230870 [details] File: open_fds
Created attachment 1230871 [details] File: proc_pid_status
Created attachment 1230872 [details] File: var_log_messages
This it happened only when Phpstorm (using java) is launched
In fact, ALT+TAB crash on grouped window of the same app Example : I have two firefox windows, 1 for chrome and 1 for libreoffice. If I do a quick ALT+TAB between the three app, no problem. But if I stay a few moments on firefox, the group of windows is open and the next ALT+TAB will crash gnome shell.
I also seem to be experiencing this. I have not notices any specific applications that cause it but I have noticed it a number of times when task switching to firefox, the screen will freeze for a couple of seconds then I land at GDM with session lost.
I am also using the nouveau driver.
Upstream bug at Gnome here https://bugzilla.gnome.org/show_bug.cgi?id=773928 I think that this also could be caused by nouveau
I rolled the following packages back from 13.0.2-2 to 12.0.3-3 and my problem has gone away mesa-dri-drivers.i686 12.0.3-3.fc25 @@commandline mesa-dri-drivers.x86_64 12.0.3-3.fc25 @@commandline mesa-filesystem.i686 12.0.3-3.fc25 @@commandline mesa-filesystem.x86_64 12.0.3-3.fc25 @@commandline mesa-libEGL.i686 12.0.3-3.fc25 @@commandline mesa-libEGL.x86_64 12.0.3-3.fc25 @@commandline mesa-libGL.i686 12.0.3-3.fc25 @@commandline mesa-libGL.x86_64 12.0.3-3.fc25 @@commandline mesa-libGLES.x86_64 12.0.3-3.fc25 @@commandline mesa-libgbm.i686 12.0.3-3.fc25 @@commandline mesa-libgbm.x86_64 12.0.3-3.fc25 @@commandline mesa-libglapi.i686 12.0.3-3.fc25 @@commandline mesa-libglapi.x86_64 12.0.3-3.fc25 @@commandline mesa-libwayland-egl.x86_64 12.0.3-3.fc25 @@commandline
I confirm that the roll back of mesa drivers solved the problem
*** Bug 1413289 has been marked as a duplicate of this bug. ***
Hi, Bug corrected with last update Installation de: libglvnd i686 1:0.2.999-7.gitdc16f8c.fc25 updates-testing 82 k libglvnd x86_64 1:0.2.999-7.gitdc16f8c.fc25 updates-testing 88 k libglvnd-core-devel x86_64 1:0.2.999-7.gitdc16f8c.fc25 updates-testing 19 k libglvnd-devel x86_64 1:0.2.999-7.gitdc16f8c.fc25 updates-testing 11 k libglvnd-egl i686 1:0.2.999-7.gitdc16f8c.fc25 updates-testing 43 k libglvnd-egl x86_64 1:0.2.999-7.gitdc16f8c.fc25 updates-testing 42 k libglvnd-gles x86_64 1:0.2.999-7.gitdc16f8c.fc25 updates-testing 30 k libglvnd-glx i686 1:0.2.999-7.gitdc16f8c.fc25 updates-testing 118 k libglvnd-glx x86_64 1:0.2.999-7.gitdc16f8c.fc25 updates-testing 124 k libglvnd-opengl x86_64 1:0.2.999-7.gitdc16f8c.fc25 updates-testing 43 k Mise à jour: mesa-libEGL i686 13.0.3-4.fc25 updates 105 k mesa-libEGL x86_64 13.0.3-4.fc25 updates 103 k mesa-libEGL-devel x86_64 13.0.3-4.fc25 updates 38 k mesa-libGL i686 13.0.3-4.fc25 updates 181 k mesa-libGL x86_64 13.0.3-4.fc25 updates 164 k mesa-libGL-devel x86_64 13.0.3-4.fc25 updates 161 k mesa-libGLES x86_64 13.0.3-4.fc25 updates 21 k mesa-libOSMesa i686 13.0.3-4.fc25 updates 2.0 M mesa-libOSMesa x86_64 13.0.3-4.fc25 updates 1.9 M mesa-libglapi i686 13.0.3-4.fc25 updates 59 k mesa-libglapi x86_64 13.0.3-4.fc25 updates 49 k
Confirm, that the update works.
no, bug is back this morning...
Sadly, it's true, that the crash is back. See, https://retrace.fedoraproject.org/faf/reports/1509136/
*** Bug 1426213 has been marked as a duplicate of this bug. ***
*** Bug 1438530 has been marked as a duplicate of this bug. ***
This message is a reminder that Fedora 25 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 25. 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 '25'. 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 25 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 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 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.