Comment 3 for bug 670592

Revision history for this message
u-foka (ufooka) wrote : Re: [Bug 670592] Re: compiz crashes when screensaver activates

Hy!

It happens usually after at least 4-5 hours of running, and it seems that it
comes up more likely if I run my catalyst development server that generates
a bit more load...

I use the blank screensaver, so it's can't be the problem.

I tryed to enable crash dumping in compiz crash handler plugin, but it only
tells me that there is no debug headers installed, and I can't find a dbg
package for compiz :( No any additional info if I run compiz in a terminal
and the crash happens... Any way to obtain crash info?

If it happened once, I restart compiz, then screensaver activates again, it
crashes again at unlock nearly all the time.

I'l make a video next time it crashes... but I can describe what happens at
unlock:
Normally: I enter my passwrd , the password dialog and the black background
disappears and my backgound image shows, then in a blink, my windows, panel
and docky appears...
Abnormally: naturally the same until the blink, then all window form all
desktops are visible with metacity running, panel is ok, and docky has a
black background as there isn't compositing...

Additionally I'l try to monitor when compiz disappears from the process list
from another computer trough ssh. Because I don't know if it only crashes
after unlock, or while the screensaver active...

On Thu, Nov 4, 2010 at 2:25 PM, flipefr <email address hidden> wrote:

> Maybe the bug is fixed for maverick. Anyway i can not reproduce it in
> maverick, it would be helpful if you could record a video of the process or
> at least try to determinate the conditions that made it crash, without more
> information we can not do much more. I mark it as incomplete.
> Anyway thank you for taking the time to request this package and helping to
> make Ubuntu better
>
> ** Changed in: compiz (Ubuntu)
> Status: New => Incomplete
>
> --
> compiz crashes when screensaver activates
> https://bugs.launchpad.net/bugs/670592
> You received this bug notification because you are a direct subscriber
> of the bug.
>