XGL (Part 4)

[unz]

in xorg.conf, device section

Code: Select all

   Option      "RenderAccel"                "true"

is set?

[djcronos]

I've been trying to get XGL to work, and am stuck on the part on installing Cairo. Whenever I do an emerge -v1a cairo, it's telling me I need to downgrade my Xorg 7.0 install to 6.8.2-r6. I checked the /etc/portage/package.keywords and xorg-x11 has ~x86 added to it.

I also added <=virtual/x11-6.8 to my /etc/portage/package.mask and still get this problem.

Why is cairo wanting to downgrade Xorg and how do I fix this?

Thanks in advance.

[CloudBolt]

I've been trying to get XGL to work, and am stuck on the part on installing Cairo. Whenever I do an emerge -v1a cairo, it's telling me I need to downgrade my Xorg 7.0 install to 6.8.2-r6. I checked the /etc/portage/package.keywords and xorg-x11 has ~x86 added to it.

I also added <=virtual/x11-6.8 to my /etc/portage/package.mask and still get this problem.

Why is cairo wanting to downgrade Xorg and how do I fix this?

Thanks in advance.

some package (be that cairo or one of cairo's dependencies) is trying to pull in xorg 6.8.2 because you didn't unmask that specific package. go over all packages, starting at the bottom of the list and unmask them until it doesn't pull in xorg 6.8.2 anymore.

edit: I hope you mean you added the virtual/x11-6.8 package to /etc/portage/package.UNmask, not mask. because then portage doesn't know it's unmasked.

[edward_og]

I'm having trouble building xgl with

Code: Select all

FEATURES="-strict" emerge xgl -v

and the xgl-coffee overlay (updated to most recent version).

Here's the last part of the call stack and emerge's error message:

Code: Select all

i686-pc-linux-gnu-gcc -DHAVE_CONFIG_H -I. -I. -I../include -I../include -I../include -I../include -I../include -I../include -I../include -I../include -I../hw/xfree86/os-support -I../hw/xfree86/os-support/bus -I../hw/xfree86/common -DHAVE_DIX_CONFIG_H -DUSE_MMX -mmmx -msse -Winline --param inline-unit-growth=10000 --param large-function-growth=10000 -D_BSD_SOURCE -DHAS_FCHOWN -DHAS_STICKY_DIR_BIT -I../include -I../include -I../Xext -I../composite -I../damageext -I../xfixes -I../Xi -I../mi -I../miext/shadow -I../miext/damage -I../render -I../randr -I../fb -Os -march=i686 -pipe -MT libfbmmx_la-fbmmx.lo -MD -MP -MF .deps/libfbmmx_la-fbmmx.Tpo -c fbmmx.c  -fPIC -DPIC -o .libs/libfbmmx_la-fbmmx.o
cc1: error: invalid parameter `inline-unit-growth'
cc1: error: invalid parameter `large-function-growth'
make[1]: *** [libfbmmx_la-fbmmx.lo] Error 1
make[1]: Leaving directory `/var/tmp/portage/xgl-0.0.1_p20060418/work/xgl-xorg/fb'
make: *** [all-recursive] Error 1

!!! ERROR: x11-base/xgl-0.0.1_p20060418 failed.
Call stack:
  ebuild.sh, line 1521:   Called dyn_compile
  ebuild.sh, line 924:   Called src_compile
  ebuild.sh, line 1233:   Called x-modular_src_compile
  x-modular.eclass, line 320:   Called x-modular_src_make
  x-modular.eclass, line 315:   Called die

!!! emake failed

Anyone have a suggestion to get xgl building?

[Henning Rogge]

I hit a roadblock, some of my java-programms (java 1.5) are not working with the XGL server... until the problem can be solved I have to switch back to the normal X Server.

I have another question, is it right that XGL doesn't support screen rotation (XRANDR) ?

[stask]

I hit a roadblock, some of my java-programms (java 1.5) are not working with the XGL server... until the problem can be solved I have to switch back to the normal X Server.

I have another question, is it right that XGL doesn't support screen rotation (XRANDR) ?

If by "not working" you mean that you have a blank window in java swing applications, you can try this solution http://compiz.net/viewtopic.php?id=282.
You'll need to wait while your java application is started before running compiz --replace gconf.

[Henning Rogge]

[If by "not working" you mean that you have a blank window in java swing applications, you can try this solution http://compiz.net/viewtopic.php?id=282.
You'll need to wait while your java application is started before running compiz --replace gconf.

can I do this after the XGL Server is running (both XGL and compiz are started during the boot process on my system).

Something like a batch

startJava.sh:

metacity --replace
java -jar Programm.jar &
sleep 10
compiz --replace gconf

[stask]

can I do this after the XGL Server is running (both XGL and compiz are started during the boot process on my system).

Yes you should do it while both XGL and compiz are running. You can do it with a script, but depending on your java applications you will need to adjust the "sleep" - 10 seconds might be not enough.

[arand]

I got xgl and compiz running finnally after a bit of work with configuring things. My problem now is that there is only one workspace in gnome. I tried adding more workspaces but there is only one workspace listed. Using the keyboard shortcuts I can't change workspaces.

How do I add more workspaces? Also can there be more than 4 workspaces, preferably 8 or 9 workspaces.

When I first got this working I did have multiple workspaces. I think I changed something in the gconf-editor but I can't find it now.

The system is running gnome 2.14, pentium M with ati moblity graphics card (so I am using the fglrx kernel module).

Thanks for your time,

EDIT::
It turns out that the order of the modules in gconf is very important. Once I got the order right that fixed the cube.

Sorry for taking up peoples time.

[Henning Rogge]

Yes you should do it while both XGL and compiz are running. You can do it with a script, but depending on your java applications you will need to adjust the "sleep" - 10 seconds might be not enough.

Hmm... that doesn't sound like a sollution for interactive java programms.

And developement of Swing applications will become a pain in the ass too.

[stask]

Hmm... that doesn't sound like a sollution for interactive java programms.

And developement of Swing applications will become a pain in the ass too.

Yes, you right, it's a workaround, not a solution. I'm using it to start my IDE for instance. Normally i'm not closing it at all, so i need to perform this "dance" only once a day. As soon as the java application is started it works properly (i.e. new windows are showed ok).
Anyway, i hope somebody will find what's the problem with compiz/java swing and create a patch soon.

[Biteableniles]

edward_og, I'm having the exact same problem with my xgl-coffee xgl build (at revision 182.) I'm trying everything short of unmerging XGL and reinstalling, since the older version is still working and I don't want to mess everything up.

Anyone have any suggestions?

[lacerto]

I've just spent the evening running through the howto. But after typing ./startxgl...wow..it's simply mind blowing! I was rather sceptical at first, having only seen the Novell video.

Once this stuff makes it into 'Production' releases, current & future versions of Gnome/KDE (3 & 4 respecively) will be truly astonishing.

Many thanks for everytone who has contributed to this post and the WIKI.

L

[Biteableniles]

Just an FYI,

Code: Select all

USE="-mmx" emerge -av xgl

fixed my xgl build error. I don't know why; somebody on the xgl-coffee forum posted that they were having the same build error on version xgl-0.0.1_p20060414; why I didn't have an error with MMX then when I do now, who knows.

[Henning Rogge]

I just found a "workaround" for developing java applications...

I emerged fluxbox and run eclipse (and all applications I start in the IDE on a second X-server

Code: Select all

eclipse-3.2 &
exec /usr/bin/fluxbox

Code: Select all

#!/bin/bash
xinit -- :1

Not nice, but the best thing I managed to do.

[Maximus2000]

Hi,
Has anyone seen this in the Ubuntu Forums?..... http://ubuntuforums.org/showthread.php?t=169179. I have I am using Coffees-testing overlay and XGL and Compizs fully upto date. How can I get this to work? Has anyone got this working?

[Jupiter1TX]

Hi,
Has anyone seen this in the Ubuntu Forums?..... http://ubuntuforums.org/showthread.php?t=169179. I have I am using Coffees-testing overlay and XGL and Compizs fully upto date. How can I get this to work? Has anyone got this working?

You can get the new plugins from quinns cvs here
http://www.beerorkid.com/compiz/
make sure to remove the "miniwin" plugin and add "dock, state, bs"
dock replaced miniwin and can be moved to top, bottom, left, right, on the screen
dock "miniwin" no longer uses 90% cpu---- RUNS GREAT NOW
bs plugin can change the brightness/saturation of the desktop
state plugin is still kinda buggy with making menu's transparent
wobbly effects on minimize/maximize is incredible "i believe it is called the moppsy effect"
wobbly effect on menus now also
switcher now has a zoom feature
decoration now has "shadow" effect, soon will have color shadows added
unfolded mode, just ctrl alt down and then when unfolded press shift and left or right
to move window to differant desktop
compiz forum has lots of info and tips
http://compiz.net/index.php

EDIT: If you maximize a window, then grab a corner like to resize, hold and move the corner
to look behind the window "warping the window", after releasing the warped window you will see
the new wobbly effect also

EDIT: Dock and miniwin create LOTS of problems when run together. One or the other must be
removed. David R. has said that miniwin is for developement of new features and dock should
be used instead for normal opperation.

[roderick]

Just an FYI,

Code: Select all

USE="-mmx" emerge -av xgl

fixed my xgl build error. I don't know why; somebody on the xgl-coffee forum posted that they were having the same build error on version xgl-0.0.1_p20060414; why I didn't have an error with MMX then when I do now, who knows.

That was me.

Something in the newer CVS version of Xgl is broken with MMX, so I had asked that a USE flag for disabling MMX be added. Fixed my Xgl issue. Hopefully as the CVS tree matures, this functionality will be able to be enabled again.

For now, setting USE="-mmx" for Xgl may be required on systems that have MMX explicitly enabled in their CFLAGS and USE. I'll post back if MMX begins to work again in a later release.

[mutlu_inek]

Regarding the Xgl HOWTO:

The part called "Setting up KDM" (http://gentoo-wiki.com/index.php?title= ... ing_up_KDM) gives advice to put the following line into /usr/kde/<your version>/share/config/kdm/kdmrc:

Code: Select all

ServerCmd=/usr/bin/Xgl -br -kb -ac -accel glx:pbuffer -accel xv

After following the HOWTO a couple of months ago I had encountered the problem that I was not able to load any keyboard setups by specifying them in xorg.conf. Forthermore, running setxkbmap returned "XKB extension not present on :0.0". After quite some time I was told that this was due to the -kb switch. Since, many others have had the same problems, some of whom I could help. Others had their num lock, caps lock or super keys not working.
At some point someone had put a small note into the HOWTO, mentioning the latter problem. Since this seemed not to be visible enough, I moved it within the wiki to make it more visible. Then, I added some information and today (after yet another user running into this problem) I finally changed it from "note" to "warning".

My question is whether the -kb switch should maybe be deleted from that command altogether? Is there any point in running Xgl without the XKB extension? Or are there cases in which this switch might actually be needed? If I had been sure that this switch is not necessary in any case, I would have deleted it long ago.


Funnily, later on in the GDM part, the HOWTO tells i810 users to run "name=Xgl server command=/usr/bin/Xgl -accel xv -accel glx:pbuffer -accel xv:pbuffer -ac -kb -audit 0 -br -dpms -dpi 72 flexible=true" instead of the usual command. Is there any link between i810 and XKB? Shouldn't this be deleted as well?

[Henning Rogge]

Don't add the "-kb" option to XGL... it would make your XKB-Extension disappear.

[mutlu_inek]

Well, that is what I wrote. I am aware of that. All I want to know is whether I can safly remove the switch (and the warning) from the HOWTO or not (because maybe some people need this switch for whatever).

[Henning Rogge]

Well, that is what I wrote. I am aware of that. All I want to know is whether I can safly remove the switch (and the warning) from the HOWTO or not (because maybe some people need this switch for whatever).

Sorry, I should have read your posting more carefully... I was a little bit tired when I wrote my last post.

I think we should remove the "-kb" from the wiki howto. Another post in this form said it's just the "remove the Keyboard extension" command.

[CloudBolt]

right, seems I have a strange problem, I've been trying to get XGL working with KDE, using the default startxgl script(the one in $OVERLAY/xgl-coffee/startxgl). I've symlinked it to /usr/bin, so I can run it by just typing startxgl [options]. when running

Code: Select all

startxgl 1 kde ati

though, the XGL server starts up cleanly, but compiz doesn't, and neither does GNOME-window-decorator. it just starts an XGL server with KDE using kwin. the strange thing is there are no errors to be found anywhere, and when running

Code: Select all

compiz --replace

and

Code: Select all

gnome-window-decorator

from a couple of shells everything works fine, including plugins. it just requires annoying manual labour.

[Joffer]

right, seems I have a strange problem, I've been trying to get XGL working with KDE, using the default startxgl script(the one in $OVERLAY/xgl-coffee/startxgl). I've symlinked it to /usr/bin, so I can run it by just typing startxgl [options]. when running

Code: Select all

startxgl 1 kde ati

though, the XGL server starts up cleanly, but compiz doesn't, and neither does GNOME-window-decorator. it just starts an XGL server with KDE using kwin. the strange thing is there are no errors to be found anywhere, and when running

Code: Select all

compiz --replace

and

Code: Select all

gnome-window-decorator

from a couple of shells everything works fine, including plugins. it just requires annoying manual labour.

I don't use the '1' option with my gnome XGL.. try:

Code: Select all

startxgl kde ati

[CloudBolt]

right, seems I have a strange problem, I've been trying to get XGL working with KDE, using the default startxgl script(the one in $OVERLAY/xgl-coffee/startxgl). I've symlinked it to /usr/bin, so I can run it by just typing startxgl [options]. when running

Code: Select all

startxgl 1 kde ati

though, the XGL server starts up cleanly, but compiz doesn't, and neither does GNOME-window-decorator. it just starts an XGL server with KDE using kwin. the strange thing is there are no errors to be found anywhere, and when running

Code: Select all

compiz --replace

and

Code: Select all

gnome-window-decorator

from a couple of shells everything works fine, including plugins. it just requires annoying manual labour.

I don't use the '1' option with my gnome XGL.. try:

Code: Select all

startxgl kde ati

that doesn't work, because then it tries to open display number: kde using window manager: ati and no video card selected. It does start XGL though, but still not starting compiz and gnome-window-decorator.