Do

Do doesn't load (no process) if started together with compiz

Bug #416149 reported by Hinrich
14
This bug affects 3 people
Affects Status Importance Assigned to Milestone
Do
New
Medium
Unassigned

Bug Description

I checked all other (similar) bugs, but I believe this is no duplicate.

If Do is started at the same time as compiz, it crashes in almost all cases.
This has been reported on various boards and as workaround it has been proposed to launch Do after calling "sleep x" (usually 10 to 30 seconds) in a script. This works, but is in my opinion no adequate solution.

The last message on stdout is:
---
Marshaling composited_changed signal
---
... then it goes on at stderr (see attachment).

This happens with 0.8.2 and also with the current bazaar trunk.

System:
Intel Graphics GM965 with xf86-video-intel 2.8.0 (latest release)
Arch Linux, Gnome, Compiz 0.8.2, Startup with fusion-icon

Revision history for this message
Hinrich (bugs-hinrich) wrote :
Revision history for this message
Alex Launi (alexlauni) wrote : Re: [Bug 416149] Re: Do doesn't load (no process) if started together with compiz

what distro?

--
--Alex Launi

Revision history for this message
Hinrich (bugs-hinrich) wrote :
Revision history for this message
Robert Dyer (psybers) wrote :

The actual exception you posted shouldnt occur... at least not with the latest bzr trunk. We have an explicit null check in place on the only thing that can be null. I wonder if perhaps at some point after we check it (where we remove like 5 event listeners) the object becomes null... I'm not even sure that can happen.

Really the only problem you should have at startup is the standard 'docky wont show' or 'Do uses 100% cpu' bugs everyone else seems to have. :-)

If I make a test branch would you be willing to pull/compile/test that to see if it fixed (as I cant reproduce this bug)?

Revision history for this message
Hinrich (bugs-hinrich) wrote :

Thanks for the response. I'd be glad to help and test it with another branch.

Robert Dyer (psybers)
Changed in do:
importance: Undecided → Medium
Revision history for this message
Chris (narbsy) wrote :

I have this same bug, same log messages and everything while running xmonad & xcompmgr, though it only occurs when I start gnome-do before xcompmgr, and not after. Having a sleep (even sleep 30) does not affect it.

Revision history for this message
Chris (narbsy) wrote :

Err, running latest of bazaar trunk.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.