[Bug 1721718] Re: Segmentation fault in meta_monitor_mode_get_resolution

2017-10-10 Thread Michael Thayer
Update: I see that there are files in /var/crash, but they are all from October 5. I will try deleting the GNOME Shell one and see if a new one is created if another crash happens. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https

[Bug 1721718] Re: Segmentation fault in meta_monitor_mode_get_resolution

2017-10-10 Thread Michael Thayer
I saw something similar again today. Hard to say how similar. For some reason Apport does not seem to be doing the automatic reporting, though it looked like it was set up at a quick glance. I will try catching it myself. -- You received this bug notification because you are a member of Ubuntu

[Bug 1721718] Re: Segmentation fault in meta_monitor_mode_get_resolution

2017-10-09 Thread Michael Thayer
I overcame my laziness and restarted everything. I was just able to reconfigure monitors without a crash, so assume this is fixed. I can always re-open if really necessary. Thanks. ** Changed in: mutter (Ubuntu) Status: Incomplete => Fix Released -- You received this bug notification b

[Bug 1721718] Re: Segmentation fault in meta_monitor_mode_get_resolution

2017-10-06 Thread LocutusOfBorg
there was a launchpad issue in posting this message, I now got it right -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1721718 Title: Segmentation fault in meta_monitor_mode_get_resolution To manage

[Bug 1721718] Re: Segmentation fault in meta_monitor_mode_get_resolution

2017-10-06 Thread LocutusOfBorg
oops, I din't notice the new mutter/vs the old one you tested. http://launchpadlibrarian.net/339870376/mutter_3.26.0+20170925~ea214fb-1ubuntu1_3.26.1-1.diff.gz + if (!monitor_mode) +{ + g_set_error (error, G_IO_ERROR, G_IO_ERROR_FAILED, + "Mode not avail

[Bug 1721718] Re: Segmentation fault in meta_monitor_mode_get_resolution

2017-10-06 Thread Michael Thayer
Gianfranco suggested off-Launchpad that I test the most recent version of libmutter (3.26.1), as it looks from the source as though this issue is fixed there. I will report back in a few days (I generally suspend and resume without restarting my session, so it will be a while until I start using t

[Bug 1721718] Re: Segmentation fault in meta_monitor_mode_get_resolution

2017-10-06 Thread LocutusOfBorg
thanks for the bug/patch, two things: 1) the patch seems to be reversed :p 2) what about putting the if statement inside calculate_scale call? static float calculate_scale (MetaMonitor *monitor, MetaMonitorMode *monitor_mode) { int resolution_width, resolution_height; int w

[Bug 1721718] Re: Segmentation fault in meta_monitor_mode_get_resolution

2017-10-06 Thread Ubuntu Foundations Team Bug Bot
The attachment "mutter.patch" seems to be a patch. If it isn't, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team. [This is an automated message performed by a Launchpad user owned by ~brian-murray, f

[Bug 1721718] Re: Segmentation fault in meta_monitor_mode_get_resolution

2017-10-06 Thread Michael Thayer
Quick fix below. For reasons of time I have done no testing beyond that GNOME Shell no longer crashes with the patch below. I have not tested the effect on scaling settings. ** Patch added: "mutter.patch" https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1721718/+attachment/4963800/+file

[Bug 1721718] Re: Segmentation fault in meta_monitor_mode_get_resolution

2017-10-06 Thread Michael Thayer
Second try with debug symbols for glib2.0 and libmutter. Thread 1 "gnome-shell" received signal SIGSEGV, Segmentation fault. meta_monitor_mode_get_resolution (monitor_mode=monitor_mode@entry=0x0, width=width@entry=0x7fff256d5ad8, height=height@entry=0x7fff256d5adc) at backends/meta-monito