External Monitor Crash

asked 2017-05-03 14:01:19 -0600

talz gravatar image

I'm running F25 on my Dell XPS 15 latpop. Lately, when closing the lid on the laptop while an external monitor is connected, gnome shell crashes.

I have a feeling that it's due to bad repositioning of windows. My laptop runs a 4k motnior, and my external display has 1440p resolution - so they run with a different scaling factor.

Apr 18 23:02:59 talz-laptop systemd-logind[889]: Lid closed.
Apr 18 23:03:00 talz-laptop org.gnome.Shell.desktop[1247]: Window manager warning: No rect to clip to found!
Apr 18 23:03:00 talz-laptop org.gnome.Shell.desktop[1247]: Window manager warning: struts occupy an unusually large percentage of the screen; available remaining height = 0 < 100Window manager warning: No rect to clip to found!
Apr 18 23:03:00 talz-laptop gnome-shell[1247]: value "-1911" of type 'gint' is invalid or out of range for property 'y1' of type 'gint'
Apr 18 23:03:00 talz-laptop gnome-shell[1247]: value "-1884" of type 'gint' is invalid or out of range for property 'y2' of type 'gint'
Apr 18 23:03:00 talz-laptop gnome-shell[1247]: value "-1911" of type 'gint' is invalid or out of range for property 'y1' of type 'gint'
Apr 18 23:03:00 talz-laptop gnome-shell[1247]: value "-1911" of type 'gint' is invalid or out of range for property 'y2' of type 'gint'
Apr 18 23:03:00 talz-laptop gnome-shell[1247]: The program 'gnome-shell' received an X Window System error.
                                               This probably reflects a bug in the program.
                                               The error was 'BadValue (integer parameter out of range for operation)'.
                                                 (Details: serial 15392 error_code 2 request_code 12 (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.)
Apr 18 23:03:00 talz-laptop kernel: do_trap: 66 callbacks suppressed
Apr 18 23:03:00 talz-laptop kernel: traps: gnome-shell[1247] trap int3 ip:7f60258b3a31 sp:7ffc03919cb0 error:0
Apr 18 23:03:00 talz-laptop kernel:  in libglib-2.0.so.0.5000.3[7f6025864000+110000]
edit retag flag offensive close merge delete

Comments

Same issue here, with Fedora 26 on a Dell XPS-13 9350.

dliappis gravatar imagedliappis ( 2017-11-09 02:30:19 -0600 )edit