mate-display-properties segfaults after changing resolution (with real xrandr)
Opened this issue · 2 comments
Steps to reproduce:
- LD_LIBRARY_PATH=/usr/lib/x86_64-linux-gnu/ mate-display-properties
- Change resolution of one of the monitors, click Apply.
- mate-display-properties is analagous to gnome-display-properties since Mate is based on Gnome2.
It would be nice if there could be a cleaner way to change resolutions etc, without the segfaults and X crashes. (X crashed the first time I tried to change res, then it went into the X segfault loop (other bug I reported) then I deleted fakexrandr.bin, then when I changed res the next time, mate-display-properties segfaulted, but X was still ok. Then I logged out, logged in and all was fine.
Can you provide any further debug information? Like e.g. a backtrace
$ LD_LIBRARY_PATH=/usr/lib/x86_64-linux-gnu/ gdb mate-display-properties
gdb> r
<wait for segfault>
gdb> bt
Hi,
I tried changing the resolutions down, but this time it didn't segfault, although mate-display-properties acted like it changed the resolution, but nothing changed at all. Perhaps it's not calling xrandr with the correct environment variable? Soon I'll reproduce the situation exactly and try again.
Reading symbols from mate-display-properties...(no debugging symbols found)...done.
(gdb) r
Starting program: /usr/bin/mate-display-properties
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x7fffef8e3700 (LWP 5211)]
[New Thread 0x7fffef0e2700 (LWP 5212)]
bt
[Thread 0x7fffef0e2700 (LWP 5212) exited]
[Thread 0x7fffef8e3700 (LWP 5211) exited]
[Inferior 1 (process 5207) exited normally]
(gdb) bt
No stack.
I tried running a backtrace after changing the resolution (which actually didn't change anything), but got nothing. Then tried again after closing the app. Also nothing?