Bug#483170: update on compiz+xscreensaver issues.
Alle sabato 7 giugno 2008, sean finney ha scritto:
> hi, as you can see from the BR this has been forwarded upstream. i have
> also found an ubuntu BR with very a very similar signature:
>
> https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/101943
>
> which unfortunately also did not have a solution. the compiz/compiz-fusion
> developers don't have much for ideas about what the problem could be
> either.
>
> also, i can reproduce this on my system in both kde and gnome environments.
> the system is not "locked up" when this happens, but the graphical
> interface is. that is, if you start ssh (beforehand, obviously) and log in
> remotely, you can still recover the system by killing the screensaver and
> compiz processes.
>
> therefore, i'm using the "nuclear option" to workaround this problem now,
> so that compiz can still be a viable candidate for lenny; i'm adding a
> conflicts from compiz-core -> xscreensaver-data-extra (non -extra
> screensavers shoudl still work).
>
>
>
> sean
Hi Sean,
from the same page in launchpad, it's unclear if the bug is related to nvidia
graphics card (indeed I've an nvidia 8600 gs), therefore to nvidia
proprietary drivers. Maybe it is safe to have a conflict not between compiz
and xscreensaver-data-extra, but between xscreensaver-data-extra and
nvidia-glx (just guessing) but you need to discuss it with their developers.
Another solution can be removing the troublesome screensavers from the
xscreensaver-data-extra package and create a different package with relative
warnings. IMHO, I'm just an user, it would be a pity to not have compiz in
the next stable release, because it's funny and everybody like it. On the
other hand, to forbid owners of ATI and other vendors graphics cards to
install both compiz and xscreensaver-data-extra, is too harsh. Until it's
clear who is "guilty" for this bug, I think there is no straight solution,
and you should provide different options to users.
Thank you, ciao
Valerio
Reply to: