Comment 3 for bug 694528

Revision history for this message
Paul Gevers (paul-climbing) wrote : Re: [Bug 694528] Re: [gnome3]winff causes crash of gnome-shell

> Yes, I can reproduce it.

That is good. So now I guess I need to create GNOME3 environment to
test... Or can somebody else test this as well?

> I've found that ffmpeg is running at 100% of cpu, when shell crash, and winff don't crash, go on in his work.

Of course ffmpeg is running high. Converting videos is an intensive task.

> The messages in the shell terminal:
> Avviso del window manager: Log level 16: STACK_OP_ADD: window 0x1200012 already in stack
> Avviso del window manager: Log level 16: STACK_OP_ADD: window 0x1200012 already in stack
> Avviso del window manager: Specificato un WM_TRANSIENT_FOR finestra 0x1200008 non valido per 0x1200133 (Indice AVI).
> Avviso del window manager: Specificato un WM_TRANSIENT_FOR finestra 0x1200008 non valido per 0x1200544 (Correzione).
> Avviso del window manager: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x2400075 (WinFF)
> Avviso del window manager: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
> Avviso del window manager: Log level 16: invalid unclassed pointer in cast to `GObject'
> Avviso del window manager: Log level 8: g_object_get_data: assertion `G_IS_OBJECT (object)' failed
> Shell killed with signal 11

I am not exactly sure how, but could you try to make sure the messages
are in English next time? See also:
https://help.ubuntu.com/community/DebuggingNonEnglishErrors

I think Avviso means "warning"? Than that should NOT be the cause of the
crash.

> When possible i will try on another machine to see if reproducible there too.

Did this yield any information?

I still believe this bug should be reported to gnome3 instead of winff,
are you convinced it is winff's fault?