Bug#790615: metacity crashes with SIGSEGV in meta_frame_get_frame_bounds

[Antonio Ospite]

On Tue, 30 Jun 2015 14:38:04 +0300
Alberts Muktupāvels <alberts.muktupavels at gmail.com> wrote:

> > Since I upgraded to metacity 3.17 I get these sporadic crashes.
> >
> > The first thing I looked at was in dmesg and this is what I got:
> >
> > traps: metacity[2515] general protection ip:7f1153f2dc00 sp:7fffac774eb8
> > error:0 in libmetacity-private.so.3.0.0[7f1153ef4000+a0000]
> >
> > I then investigated further with gdb and got a backtrace of the crash,
> > please see the attached file.
> >
> > If I had to guess I'd say that the crash may be related to some activity
> > with modal dialogs from Gtk, but I am not 100% sure about that.
> >
> 
> Can you give steps how to reproduce crash?
> 

It does not happen every time, but I'd say that when it does, it is
after a dialog has been shown.

For instance I use sylpheed, an email client based on Gtk2, and when
checking new emails a dialog with a progress meter is shown, sometimes
when metacity crashes it looks like it is when the dialogue is just
going to be destroyed.

I also managed to trigger the crash using zenity 3.16.3, with "zenity
--calendar" or "zenity --error" after clicking OK, but this is not
consistent either, it happens only sometimes.

Let me know if you have any more questions.

JFYI the video driver is "nouveau", I don't know if it can be related.

Thanks,
   Antonio

-- 
Antonio Ospite
http://ao2.it

A: Because it messes up the order in which people normally read text.
   See http://en.wikipedia.org/wiki/Posting_style
Q: Why is top-posting such a bad thing?