Plugging-in second monitor crashes the running mate-display-properties process #121
Comments
|
Are you able to get a backtrace with gdb? |
|
Yes, and it's best to do immediately after the desktop started after boot. Subsequent run will give little-to-none backtrace information; maybe stack were corrupted in those case. I can post the core file too (~15 MB bzip2'd), if anyone is interested. The second display is a Philips 107S66/05 CRT monitor, connected via VGA cable.
|
|
I've re-attempted to get a full backtrace, including local variables (using The second display is still the same Philips 107S66/05 CRT monitor, connected via VGA cable. |
|
I think this is not really specific to attaching second monitor, since other change in XRandR status seems to crash mate-display-properties in a similar manner. For example, if I ran So, I think this might share the same root cause as bug #106 (changing screen resolution crashes mate-display-properties). The only difference here is, in that bug report, Backtrace in second monitor case, command line
|
|
I can reproduce the issue. Also, extend mode (the default when monitor is plugged in) is broken. $ dpkg -l mate* | grep ^ii | awk '{print $2 $3}' $ inxi -Gx |
|
Program received signal SIGSEGV, Segmentation fault. (gdb) backtrace
#0 0x00007ffff70f0b31 in gdk_event_apply_filters (filters=<optimized out>, event=0x7fffe00031d0, xevent=0x7fffffffdc50)
at /build/buildd/gtk+2.0-2.24.23/gdk/x11/gdkevents-x11.c:356
#1 gdk_event_translate (display=display@entry=0x645020, event=event@entry=0x7fffe00031d0, xevent=xevent@entry=0x7fffffffdc50,
return_exposes=return_exposes@entry=0) at /build/buildd/gtk+2.0-2.24.23/gdk/x11/gdkevents-x11.c:1052
#2 0x00007ffff70f2116 in _gdk_events_queue (display=display@entry=0x645020) at /build/buildd/gtk+2.0-2.24.23/gdk/x11/gdkevents-x11.c:2336
#3 0x00007ffff70f21be in gdk_event_dispatch (source=<optimized out>, callback=<optimized out>, user_data=<optimized out>)
at /build/buildd/gtk+2.0-2.24.23/gdk/x11/gdkevents-x11.c:2397
#4 0x00007ffff60b0e04 in g_main_dispatch (context=0x650110) at /build/buildd/glib2.0-2.40.0/./glib/gmain.c:3064
#5 g_main_context_dispatch (context=context@entry=0x650110) at /build/buildd/glib2.0-2.40.0/./glib/gmain.c:3663
#6 0x00007ffff60b1048 in g_main_context_iterate (context=0x650110, block=block@entry=1, dispatch=dispatch@entry=1, self=<optimized out>)
at /build/buildd/glib2.0-2.40.0/./glib/gmain.c:3734
#7 0x00007ffff60b130a in g_main_loop_run (loop=0x904d30) at /build/buildd/glib2.0-2.40.0/./glib/gmain.c:3928
#8 0x00007ffff7402ea2 in IA__gtk_dialog_run (dialog=0x66a050) at /build/buildd/gtk+2.0-2.24.23/gtk/gtkdialog.c:1094
#9 0x0000000000406763 in run_application (app=0x61afa0) at xrandr-capplet.c:2526
#10 main (argc=1, argv=0x7fffffffe048) at xrandr-capplet.c:2573 |
|
Duplicate of |
I have some trouble with mate-display-properties regarding multi-monitor configuration.
When I plugged in the second display first, then run
mate-display-propertiesto configure it,it will work fine.
But if I run
mate-display-propertiesfirst, then plug in the second display,mate-display-properties will crash (Segmentation Fault).
To reproduce:
mate-display-propertiesfrom a terminalMATE: MATE 1.8.1 (from Debian backports repository)
System: Debian GNU/Linux 7.0 "Wheezy" i386
Display Adapter: Intel i915 (xorg-video-intel driver)
Machine: Samsung NP370R4V-S01TH Laptop
Note: In my case, the second monitor is a projector (connected via VGA cable).
But I think that normal monitor (VGA/DVI) or TV (HDMI) will do too.
The text was updated successfully, but these errors were encountered: