Colin Guthrie wrote:
> Can't believe I didn't notice this before, but this only seems to affect
> x86_64 boxes Probably a key factor.
OK, we've gotten to the bottom of this now. Two of my fellow Mandriva
bods have worked out what's gone wrong:
J.A. Magallón wrote:
> Hi all...
>
> I have been
Can't believe I didn't notice this before, but this only seems to affect
x86_64 boxes Probably a key factor.
Do you think it's possible that this could be a bizarre compiler issue?
Or does this info turn on a lightbulb for anyone?
Col
mania103 is your
Colin Guthrie wrote:
> Colin Guthrie wr
Colin Guthrie wrote:
> Frederik Himpe wrote:
>> I am 100% sure it is caused by compiz update. I do a complete restart
>> of my computer every day. Let's take a look at the transactions done
>> around that time:
>
> OK I'm convinced ;) Now just to work out why.
Hi Compiz People :)
I've been t
Frederik Himpe wrote:
> I am 100% sure it is caused by compiz update. I do a complete restart
> of my computer every day. Let's take a look at the transactions done
> around that time:
OK I'm convinced ;) Now just to work out why.
Col
___
compiz ma
On Tue, 26 Feb 2008 01:35:13 +, Colin Guthrie wrote:
> Frederik Himpe wrote:
>> After these updates, I restarted X, and compiz was broken.
>
> Out of curiosity, could you have updated our X package before this
> update but not restarted X? I do this quite often as I tend to
> suspend... It ca
On Mon, 2008-02-25 at 09:55 +0100, Danny Baumann wrote:
>
> Option "AddARGBGLXVisuals"
>
> looks fishy to me. I'd recommend
>
> Option "AddARGBGLXVisuals" "True"
FYI, the "True" is redundant for boolean options.
--
Earthling Michel Dänzer | http://tungstengraphics.com
Li
Frederik Himpe wrote:
> After these updates, I restarted X, and compiz was broken.
Out of curiosity, could you have updated our X package before this
update but not restarted X? I do this quite often as I tend to
suspend... It can make it a pain for tracking down such errors
perhaps it is X it
On Mon, 25 Feb 2008 09:55:48 +0100, Danny Baumann wrote:
> Hi,
>
>> Since upgrading to compiz 0.7, it does not start anymore on my x86_64
>> system, with the error message
>> compiz (core) - Fatal: No GLXFBConfig for default depth, this isn't
>> going to work.
>> compiz (core) - Error: Failed to
Hi,
> Since upgrading to compiz 0.7, it does not start anymore on my x86_64
> system, with the error message
> compiz (core) - Fatal: No GLXFBConfig for default depth, this isn't going
> to work.
> compiz (core) - Error: Failed to manage screen: 0
> compiz (core) - Fatal: No manageable screens f
> A thing which is often cited, also in that bug report, is using
> --no-libgl-fallback, but compiz 0.7 does not seem to recognise
> that parameter.
It worked for me as it was described by "eagleMcMoe".
http://www.linuxquestions.org/questions/linux-desktop-74/compiz-no-glxfbconfig-for-default-dept
On Sat, 23 Feb 2008 18:44:28 +0100, Markus Elfring wrote:
>> http://qa.mandriva.com/show_bug.cgi?id=38064
>>
>> What could be wrong?
>
> Can the explanations from an other bug report help you? Example:
> http://bugs.opencompositing.org/show_bug.cgi?id=774
I already tried googling around, but it
> http://qa.mandriva.com/show_bug.cgi?id=38064
>
> What could be wrong?
Can the explanations from an other bug report help you?
Example:
http://bugs.opencompositing.org/show_bug.cgi?id=774
Regards,
Markus
___
compiz mailing list
compiz@lists.freedeskt
Since upgrading to compiz 0.7, it does not start anymore on my x86_64
system, with the error message
compiz (core) - Fatal: No GLXFBConfig for default depth, this isn't going
to work.
compiz (core) - Error: Failed to manage screen: 0
compiz (core) - Fatal: No manageable screens found on display :
13 matches
Mail list logo
