Compiz Fusion 0.7.7 (git 28 Jul 2008)
Hey, when I try to run COmpiz fusion on my HDD install I got this:
HELP!!!!![/code]
Code: Select all
# Xlib: extension "GLX" missing on display ":0.0".
compiz (core) - Fatal: Root visual is not a GL visual
compiz (core) - Error: Failed to manage screen: 0
compiz (core) - Fatal: No manageable screens found on display :0.0
[1]+ Exit 1 LIBGL_ALWAYS_INDIRECT=1 INTEL_BATCH=1 compiz --replace --indirect-rendering --sm-disable ccp
@panzerpuppy: This package is not compatible with Puppy 4. Sorry, I don't have the time for upload/download anything or even reply messages at this moment.
@olovram: Make sure that you are using Xorg (not Xvesa), to install the GLX extension launch petget and install xorg_OPENGL(Puppy3 with opensource drivers) or install the proprietary nVidia driver to use nvidia's GLX. (Puppy3 with nVidia's gpu)
@tombh: I've compiled Compiz Fusion in Puppy 4 and I get the same error message. Puppy 4 don't have the full Xorg server, seems that we need to recompile Xorg with the GLX extension and make a rematered ISO with it.
@olovram: Make sure that you are using Xorg (not Xvesa), to install the GLX extension launch petget and install xorg_OPENGL(Puppy3 with opensource drivers) or install the proprietary nVidia driver to use nvidia's GLX. (Puppy3 with nVidia's gpu)
@tombh: I've compiled Compiz Fusion in Puppy 4 and I get the same error message. Puppy 4 don't have the full Xorg server, seems that we need to recompile Xorg with the GLX extension and make a rematered ISO with it.
[url=http://www.puppylinux.com][img]http://i.imgur.com/M4OyHe1.gif[/img][/url]
I got a backtrace on the seg fault
But perhaps your seg fault is for a different reason, besides I tried to run the compiz package from Puppy 3, so it's hardly surprising that I get a seg fault. I'm starting to collect the dependencies myself, I'm doing alright so far but not sure where to get a certain GL/gl.h, I see that GL/glx.h and GL/glu.h are a part of the glu1-mesa-devs but GL/gl.h doesn't seem to come with them.
Reading on the compiz forums there are a number of problems reported with compiling because most distros don't have xcb support as default. But seeing as you must have had the xcb headers to even compile in the first place then I guess this isn't the same problem.0xb7f2a3e1 in XGetXCBConnection () from /usr/X11R7/lib/libX11-xcb.so.1
But perhaps your seg fault is for a different reason, besides I tried to run the compiz package from Puppy 3, so it's hardly surprising that I get a seg fault. I'm starting to collect the dependencies myself, I'm doing alright so far but not sure where to get a certain GL/gl.h, I see that GL/glx.h and GL/glu.h are a part of the glu1-mesa-devs but GL/gl.h doesn't seem to come with them.
[url=http://www.tombh.co.uk/colour_memories/contribute.php]Colour-Memories Database[/url]
Well I've finally got compiz running in Puppy 4. All that was required was to recompile libX11 with the configure flag "--with-xcb", I've supplied a pet of the updated library.
libX11-1.1.4-i486.pet
Unfortunately Emerald is now seg faulting, the backtrace there is,
But the main thing is that compiz is alive and kicking
So you can follow all wow's instructions and use all wow's packages in Puppy 4 just as you would in Puppy 3 except you'll need to install this updated library afterwards.
Let me know how it goes.
libX11-1.1.4-i486.pet
Unfortunately Emerald is now seg faulting, the backtrace there is,
Emerald just provides the window decoration, so you can't click to drag, minimize or close.Program received signal SIGSEGV, Segmentation fault.
0xb785c451 in g_atomic_int_exchange_and_add () from /usr/lib/libglib-2.0.so.0
But the main thing is that compiz is alive and kicking
So you can follow all wow's instructions and use all wow's packages in Puppy 4 just as you would in Puppy 3 except you'll need to install this updated library afterwards.
Let me know how it goes.
Last edited by tombh on Tue 22 Jul 2008, 22:33, edited 3 times in total.
[url=http://www.tombh.co.uk/colour_memories/contribute.php]Colour-Memories Database[/url]
Edited my last post to say that the library should be installed after wow's packages because they will overwrite the changes otherwise.
PS I recompiled Emerald and stopped receiving the seg fault, except now it complains about
PS I recompiled Emerald and stopped receiving the seg fault, except now it complains about
I'm not entirely convinced that it's enopught to stop Emerald and that maybe there's maybe another problem -- more likely that I'm using emerald compiled in Puppy 4 with wow's packages from Puppy 3. I'll push on and try get all of compiz compiled in Puppy 4 then see what happens.GLib-GObject-CRITICAL **: g_object_ref: assertion `G_IS_OBJECT (object)' failed
[url=http://www.tombh.co.uk/colour_memories/contribute.php]Colour-Memories Database[/url]
I've managed to compile all of compiz-fusion and emerald for Puppy 4 and it's all working fine on my computer.
I'm providing a pet for testing, I'm afraid I haven't been able to test it out on another install to make sure everything's in it.
fusion-0.7.6_400-tbhtest1.pet
This was compiled *with* xcb support so you must update your libX11 with the pet posted above.
It does not contain the compiz-manager script, so to run compiz you must use the following;
I'm providing a pet for testing, I'm afraid I haven't been able to test it out on another install to make sure everything's in it.
fusion-0.7.6_400-tbhtest1.pet
This was compiled *with* xcb support so you must update your libX11 with the pet posted above.
It does not contain the compiz-manager script, so to run compiz you must use the following;
If emerald doesn't start with it, type;LIBGL_ALWAYS_INDIRECT=1 compiz --replace --indirect-rendering --sm-disable ccp &
One thing I've noticed opn my machine is that there is a serious bug with the freewins plugin and when it is enabled it causes a lot of crashes, even when using other plugins.emerald --replace
Last edited by tombh on Mon 21 Jul 2008, 22:27, edited 1 time in total.
[url=http://www.tombh.co.uk/colour_memories/contribute.php]Colour-Memories Database[/url]
I've tested your .pets 3 times and my keyboard becames useless after install libX11-1.1.4-i486.pet and restart X.
This is what I did (on a fresh install):
1. xorg_xorg_full_dri-7.3.pet [OK]
2. libX11-1.1.4-i486.pet [Error]
3. fusion-0.7.6_400-tbhtest1.pet [OK]
Only happens when X is running.
This is what I did (on a fresh install):
1. xorg_xorg_full_dri-7.3.pet [OK]
2. libX11-1.1.4-i486.pet [Error]
3. fusion-0.7.6_400-tbhtest1.pet [OK]
Only happens when X is running.
[url=http://www.puppylinux.com][img]http://i.imgur.com/M4OyHe1.gif[/img][/url]
This rings a bell, though I can't remember how I fixed it, maybe it was just doing a full reboot. Okay so I'll go and test these pets in a fresh install. It'd be good to know we've got CF sorted in Dingo, so I'll try and do it later today.
What was the error from the libX11 pet?
What was the error from the libX11 pet?
[url=http://www.tombh.co.uk/colour_memories/contribute.php]Colour-Memories Database[/url]
Right, figured out the libX11 problem. It turns out that libX11 has some locale and keysym text files that it depends on and due to the fact that the version I compiled was prefixed to look for these files somewhere else it didn't find the ones already in Puppy.
So I've recompiled and repackaged libX11 with its own locale and keysym files. The extra text files install to /usr/share/X11, whereas the ones already in Puppy are at /usr/X11R7/lib/X11, so I guess that's some duplication going on. I'm not sure how you would specify the compile prefix to get libX11 to look for its files there. These extra files are only about 2MB and there's quite a lot of them, perhaps only a couple are needed, I've no idea though. Nevermind they only add up to ~200k in the pet.
Though it would be nice to slimline this a bit as that 2MB will otherwise need to be included in the next version of wNOP and it all adds up. I actually used a configure option called "--enable-xlocaledir" with this version now, which enables support for an environment variable called XLOCALEDIR, which I guess might be just the ticket to get libX11 to use Puppy's existing files. I haven't had a chance to test it out yet though.
Anyway here it is libX11-1.1.4-i486.pet
Now for the bad news, libX11 works, it fired up compiz-fusion perfectly only to discover I compiled Emerald against a newer version of glib! So Emerald is segfaults with the older glib of a fresh install. I must have automatically just went for the newest version of glib when I needed its DEV files. So how do I find out which version of glib to compile? I guess it will be in the devx_400.sfs in the relevant glib-2.0.pc file, but I've overwritten it with newer one so I can't tell. My one is version 2.16.4.
So I've recompiled and repackaged libX11 with its own locale and keysym files. The extra text files install to /usr/share/X11, whereas the ones already in Puppy are at /usr/X11R7/lib/X11, so I guess that's some duplication going on. I'm not sure how you would specify the compile prefix to get libX11 to look for its files there. These extra files are only about 2MB and there's quite a lot of them, perhaps only a couple are needed, I've no idea though. Nevermind they only add up to ~200k in the pet.
Though it would be nice to slimline this a bit as that 2MB will otherwise need to be included in the next version of wNOP and it all adds up. I actually used a configure option called "--enable-xlocaledir" with this version now, which enables support for an environment variable called XLOCALEDIR, which I guess might be just the ticket to get libX11 to use Puppy's existing files. I haven't had a chance to test it out yet though.
Anyway here it is libX11-1.1.4-i486.pet
Now for the bad news, libX11 works, it fired up compiz-fusion perfectly only to discover I compiled Emerald against a newer version of glib! So Emerald is segfaults with the older glib of a fresh install. I must have automatically just went for the newest version of glib when I needed its DEV files. So how do I find out which version of glib to compile? I guess it will be in the devx_400.sfs in the relevant glib-2.0.pc file, but I've overwritten it with newer one so I can't tell. My one is version 2.16.4.
[url=http://www.tombh.co.uk/colour_memories/contribute.php]Colour-Memories Database[/url]
@el ginko: Xorg also does some Dual monitor stuff, though no experience myself. http://gentoo-wiki.com/HOWTO_Dual_Monitors
[url=http://www.tombh.co.uk/colour_memories/contribute.php]Colour-Memories Database[/url]