xorg-x11-7.0-r1 fails on libx11

[Albert_Alligator]

Just an observation from my own experience. Perhaps a clue for the right people.

On three of four x86 systems, I've migrated xorg from 6.8 to 7.0 with only minor stopping points.

The other system is one I'd tried migrating on months ago. I got stuck and reverted to 6.8

Is this a common scenario for other people having libX11 trouble perhaps.

It sounds like to me their trying to upgrade on another arch, but no one has mentioned which one

Sorry, here is my particular systems emerge --info

Code: Select all

Portage 2.1.1_pre2-r1 (default-linux/amd64/2005.0, gcc-3.4.6/amd64-vanilla, glibc-2.4-r3, 2.6.15-gentoo-r7 x86_64)
=================================================================
System uname: 2.6.15-gentoo-r7 x86_64 Mobile AMD Athlon 64 Processor 3000+
Gentoo Base System version 1.12.1
distcc 2.18.3 x86_64-pc-linux-gnu (protocols 1 and 2) (default port 3632) [disabled]
dev-lang/python:     2.3.5-r2, 2.4.3-r1
dev-python/pycrypto: 2.0.1-r5
dev-util/ccache:     [Not Present]
dev-util/confcache:  [Not Present]
sys-apps/sandbox:    1.2.18.1
sys-devel/autoconf:  2.13, 2.60
sys-devel/automake:  1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6-r2
sys-devel/binutils:  2.17
sys-devel/gcc-config: 2.0.0_rc1
sys-devel/libtool:   1.5.22
virtual/os-headers:  2.6.16
ACCEPT_KEYWORDS="amd64 ~amd64"
AUTOCLEAN="yes"
CBUILD="x86_64-pc-linux-gnu"
CFLAGS="-march=k8 -pipe -fomit-frame-pointer -O2"
CHOST="x86_64-pc-linux-gnu"
CONFIG_PROTECT="/etc /usr/kde/3.3/env /usr/kde/3.3/share/config /usr/kde/3.3/shutdown /usr/kde/3.5/env /usr/kde/3.5/share/config /usr/kde/3.5/shutdown /usr/lib64/mozilla/defaults/pref /usr/share/X11/xkb /usr/share/config /var/bind"
CONFIG_PROTECT_MASK="/etc/env.d /etc/eselect/compiler /etc/gconf /etc/revdep-rebuild /etc/terminfo /etc/texmf/web2c"
CXXFLAGS="-march=k8 -pipe -fomit-frame-pointer -O2"
DISTDIR="/usr/portage/distfiles"
FEATURES="autoconfig distlocks metadata-transfer sandbox sfperms strict"
GENTOO_MIRRORS="http://ftp.isu.edu.tw/pub/Linux/Gentoo http://mymirror.asiaosc.org/gentoo/ http://ftp.gentoo.or.kr ftp://gg3.net/pub/linux/gentoo/ http://gentoo.gg3.net/ http://mirror.gentoo.gr.jp"
MAKEOPTS="-j4"
PKGDIR="/usr/portage/packages"
PORTAGE_RSYNC_OPTS="--recursive --links --safe-links --perms --times --compress --force --whole-file --delete --delete-after --stats --timeout=180 --exclude='/distfiles' --exclude='/local' --exclude='/packages'"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR="/usr/portage"
PORTDIR_OVERLAY="/usr/local/portage/x11-themes/QtCurve"
SYNC="rsync://rsync.gentoo.org/gentoo-portage"
USE="amd64 X a52 aac aalib acpi alsa apache2 ati avi bash-completion berkdb bitmap-fonts browserplugin cdr cli crypt dba dlloader dri dts dvd dvdr dvdread dxr3 eds emboss encode flac foomatic foomaticdb fortran g77 gd gif gnome gpm gstreamer gtk gtk2 imlib innodb ipv6 isdnlog ithreads java java-external jpeg kde ldap libcaca lzw lzw-tiff mozilla mp3 mpeg mysql ncurses nls nptl nptlonly nsplugin ogg oggvorbis opengl oss pam pcre pdflib perl php png ppds pppd pthreads python qt qt3 qt4 quicktime readline reflection samba sdl session spell spl ssl tcpd threads tiff truetype truetype-fonts type1-fonts usb v4l vcd vorbis winbind xine xorg xpm xv xvmc zlib elibc_glibc input_devices_keyboard input_devices_mouse kernel_linux userland_GNU video_cards_radeon video_cards_vesa video_cards_fbdev"
Unset:  CTARGET, EMERGE_DEFAULT_OPTS, INSTALL_MASK, LANG, LC_ALL, LDFLAGS, LINGUAS, PORTAGE_RSYNC_EXTRA_OPTS

My system is a Mobile AMD64 Notebook (Ferrari 3400) and has been running fairly ok up until two weeks ago. The last six or so months has been riddled with problems with some packages now only being supported under modular X or xorg-x11-6.8 but not both. Other issues are more subtle, but most were fairly quickly resolved. This one is different, almost every package I'm trying to download or upgrade breaks on compile....and I haven't changed my make.conf file (other than some fairly basic changes, which I've already ruled out via testing.

[Philantrop]

/bin/sh: makedepend: command not found

Code: Select all

emerge x11-misc/makedepend

[Albert_Alligator]

Ok, now I'm missing so many libs it's becoming an overwhelming effort to trace them all back to the begining....how do I emerge them in order? There seem to be so many cross dependencies.

libXt depends on libSM which in turn depends on libICE


how many other will I find..... only the Gods of really weird package combinations know for sure.

AIEEEEEEEEEEEEEEEEEEEEEEEEEEE!!!!!

[ocin]

same shit for me: http://forums.gentoo.org/viewtopic-t-476716.html

[Albert_Alligator]

same shit for me: http://forums.gentoo.org/viewtopic-t-476716.html

One thing I'm sure of is that you'll need to use equery quite a bit.... so if you haven't already done this...do it

emerge gentoolkit

then do this

equery b glxproto.h

which should give you some output like this

Code: Select all

[ Searching for file(s) glxproto.h in *... ]
x11-proto/glproto-1.4.7 (/usr/lib64/opengl/xorg-x11/include/glxproto.h)

which shows you need to emerge glproto.

Now before you jump for joy thinking YAY.... I found my problem.... you might want to make sure all your prototypes are installed..... [see list on first page of this thread]

then try and emerge mesa again.... but you may just want to emerge the x11 library files I listed above to be safe.....

hope that helps

[Dralnu]

Start posting bugs at bugzilla. X isn't stable on anything but x86, which is why I was asking because mine went up fine (<--P4 i686)

[splun549]

I'd love to avoid upgrading right now, but portage seems to insist:


# emerge -puD world
These are the packages that would be merged, in order:

Calculating world dependencies ....... done!
[blocks B ] <=x11-base/xorg-x11-6.9 (is blocking x11-proto/kbproto-1.0.2)
[blocks B ] <=x11-base/xorg-x11-6.9 (is blocking x11-misc/util-macros-1.0.2)
[blocks B ] <=x11-base/xorg-x11-6.9 (is blocking x11-libs/libX11-1.0.1-r1)
[blocks B ] <=x11-base/xorg-x11-6.9 (is blocking x11-proto/xextproto-7.0.2)
[... Trimmed for brevity]
[ebuild U ] sys-devel/binutils-2.16.1-r3 [2.16.1-r2]
[ebuild N ] x11-misc/util-macros-1.0.2 USE="-debug"
[ebuild N ] x11-proto/kbproto-1.0.2 USE="-debug"
[ebuild N ] x11-proto/xextproto-7.0.2 USE="-debug"
[ebuild N ] x11-proto/xf86bigfontproto-1.1.2 USE="-debug"
[... Trimmed for brevity]
[ebuild N ] x11-drivers/xf86-video-nv-1.0.2.0 USE="-debug"
[ebuild U ] x11-base/xorg-x11-7.0-r1 [6.8.2-r8] INPUT_DEVICES="evdev% keyboard% mouse% -acecad% -aiptek% -calcomp%
-citron% -digitaledge% -dmc% -dynapro% -elo2300% -elographics% -fpit% -hyperpen% -jamstudio% -joystick% -magellan% -mag
ictouch% -microtouch% -mutouch% -palmax% -penmount% -spaceorb% -summa% -synaptics% -tek4957% -ur98% -vmmouse% -void% -w
acom%" VIDEO_CARDS="-apm% -ark% -chips% -cirrus% -cyrix% -dummy% -fbdev% -fglrx% -glint% -i128% -i740% -i810% -imstt% -
mach64% -mga% -neomagic% -nsc% -nv% -nvidia% -r128% -radeon% -rendition% -s3% -s3virge% -savage% -siliconmotion% -sis%
-sisusb% -tdfx% -tga% -trident% -tseng% -v4l% -vesa% -vga% -via% -vmware% -voodoo%"
[ebuild U ] media-libs/libpng-1.2.12 [1.2.8-r1]
[... Trimmed for brevity]

Since I'm running 6.8, I'm a bit confused as to why x11-base/xorg-x11-6.9 would be blocking these packages... it's not even on my machine.... this sort of thing shouldn't happen to one as dim as I.

[Albert_Alligator]

Start posting bugs at bugzilla. X isn't stable on anything but x86, which is why I was asking because mine went up fine (<--P4 i686)

I was certain I saw this:

The X team has marked modular X stable for most architectures. The x86 and AMD64 architectures will update to X.Org 7.0, and other architectures will move to 7.1. Those two architectures are on 7.0 because binary drivers were broken in the 7.1 update due to a number of planned changes to the ABI (Application Binary Interface). Some remaining architectures are expected to go stable soon. To learn how to upgrade properly, read the migration guide before starting the upgrade. It discusses how the USE flags changed, why X.Org went modular and why emerge xorg-x11 won't be quite enough. Please file bugs at https://bugs.gentoo.org/ for any problems you encounter during the upgrade. Modular X is composed of a vast amount of changes, so there will probably be a few remaining issues during the first couple of days it's in stable.

that indicated that it was.............. oh, I don't know..... stable?

Modular X has been out for quite sometime, and I know it wasn't stable, so I tried staying with 6.8 as long as possible..... then two weeks ago, something borked..... (probably user error) and I had to postpone fixing....then I saw the message above and thought I'd give it a try.

[Dralnu]

Start posting bugs at bugzilla. X isn't stable on anything but x86, which is why I was asking because mine went up fine (<--P4 i686)

I was certain I saw this:

The X team has marked modular X stable for most architectures. The x86 and AMD64 architectures will update to X.Org 7.0, and other architectures will move to 7.1. Those two architectures are on 7.0 because binary drivers were broken in the 7.1 update due to a number of planned changes to the ABI (Application Binary Interface). Some remaining architectures are expected to go stable soon. To learn how to upgrade properly, read the migration guide before starting the upgrade. It discusses how the USE flags changed, why X.Org went modular and why emerge xorg-x11 won't be quite enough. Please file bugs at https://bugs.gentoo.org/ for any problems you encounter during the upgrade. Modular X is composed of a vast amount of changes, so there will probably be a few remaining issues during the first couple of days it's in stable.

that indicated that it was.............. oh, I don't know..... stable?

Modular X has been out for quite sometime, and I know it wasn't stable, so I tried staying with 6.8 as long as possible..... then two weeks ago, something borked..... (probably user error) and I had to postpone fixing....then I saw the message above and thought I'd give it a try.

Read this post:

http://forums.gentoo.org/viewtopic-t-446184.html

That says that x86 is stable, the others are in the works

[Albert_Alligator]

Start posting bugs at bugzilla. X isn't stable on anything but x86, which is why I was asking because mine went up fine (<--P4 i686)

I was certain I saw this:

The X team has marked modular X stable for most architectures. The x86 and AMD64 architectures will update to X.Org 7.0, and other architectures will move to 7.1. Those two architectures are on 7.0 because binary drivers were broken in the 7.1 update due to a number of planned changes to the ABI (Application Binary Interface). Some remaining architectures are expected to go stable soon. To learn how to upgrade properly, read the migration guide before starting the upgrade. It discusses how the USE flags changed, why X.Org went modular and why emerge xorg-x11 won't be quite enough. Please file bugs at https://bugs.gentoo.org/ for any problems you encounter during the upgrade. Modular X is composed of a vast amount of changes, so there will probably be a few remaining issues during the first couple of days it's in stable.

that indicated that it was.............. oh, I don't know..... stable?

Modular X has been out for quite sometime, and I know it wasn't stable, so I tried staying with 6.8 as long as possible..... then two weeks ago, something borked..... (probably user error) and I had to postpone fixing....then I saw the message above and thought I'd give it a try.

Read this post:

http://forums.gentoo.org/viewtopic-t-446184.html

That says that x86 is stable, the others are in the works

Well I would say that the front page will be seen by many, while a post in the news and announcements forum may go unnoticed for a little while.

Anyway, I'm working through all of the issues, bit by bit, with every error and compile breakage, I use equery and find which library is missing and get it....and so on and so forth. I've pretty much finished except for one very annoying part where startx won't start because of this error;

Code: Select all

Fatal server error:
could not open default font 'fixed'
(**) RADEON(0): RADEONLeaveVT
(**) RADEON(0): EngineRestore (32/32)
(**) RADEON(0): RADEONRestore
(**) RADEON(0): RADEONRestoreMode()
(**) RADEON(0): RADEONRestoreMode(0x6ee968)
(**) RADEON(0): RADEONRestoreMemMapRegisters() :
(**) RADEON(0):   MC_FB_LOCATION   : 0x1fff0000
(**) RADEON(0):   MC_AGP_LOCATION  : 0x27ff2000
(**) RADEON(0):   Map Changed ! Applying ...
(**) RADEON(0):   Map applied, resetting engine ...
(**) RADEON(0): Updating display base addresses...
(**) RADEON(0): Memory map updated.
(**) RADEON(0): Programming CRTC1, offset: 0x00000000
(**) RADEON(0): Wrote: 0x00180006 0x00010030 0x00000000 (0x0000a700)
(**) RADEON(0): Wrote: rd=6, fd=48, pd=1
(**) RADEON(0): Ok, leaving now...

Found fixes on this page, but alas, they did not work for me.

Any hint or clue? Searching the forums turns up nothing as the only word not blocked in the search is 'fonts' which results in nothing of value.

[grofaz]

Well unfortunately for me, my system would not work with 6.8 either.... which was a little baffling.

Something happened with some package being updated (not sure which), and it completely buggered my system. I have not been able to recover yet.

If you want 6.8.2-r8 try this:

Code: Select all

emerge -ae =xorg-x11-6.8.2-r8
etc-update
revdep-rebuild

If you want 7.0 then try:

Code: Select all

emerge -aC xorg-x11
emerge -ae xorg-x11
etc-update
revdep-rebuild

It will take awhile but -e will recompile everything. Good luck!

[Dralnu]

Start posting bugs at bugzilla. X isn't stable on anything but x86, which is why I was asking because mine went up fine (<--P4 i686)

I was certain I saw this:

The X team has marked modular X stable for most architectures. The x86 and AMD64 architectures will update to X.Org 7.0, and other architectures will move to 7.1. Those two architectures are on 7.0 because binary drivers were broken in the 7.1 update due to a number of planned changes to the ABI (Application Binary Interface). Some remaining architectures are expected to go stable soon. To learn how to upgrade properly, read the migration guide before starting the upgrade. It discusses how the USE flags changed, why X.Org went modular and why emerge xorg-x11 won't be quite enough. Please file bugs at https://bugs.gentoo.org/ for any problems you encounter during the upgrade. Modular X is composed of a vast amount of changes, so there will probably be a few remaining issues during the first couple of days it's in stable.

that indicated that it was.............. oh, I don't know..... stable?

Modular X has been out for quite sometime, and I know it wasn't stable, so I tried staying with 6.8 as long as possible..... then two weeks ago, something borked..... (probably user error) and I had to postpone fixing....then I saw the message above and thought I'd give it a try.

Read this post:

http://forums.gentoo.org/viewtopic-t-446184.html

That says that x86 is stable, the others are in the works

Well I would say that the front page will be seen by many, while a post in the news and announcements forum may go unnoticed for a little while.

Anyway, I'm working through all of the issues, bit by bit, with every error and compile breakage, I use equery and find which library is missing and get it....and so on and so forth. I've pretty much finished except for one very annoying part where startx won't start because of this error;

Code: Select all

Fatal server error:
could not open default font 'fixed'
(**) RADEON(0): RADEONLeaveVT
(**) RADEON(0): EngineRestore (32/32)
(**) RADEON(0): RADEONRestore
(**) RADEON(0): RADEONRestoreMode()
(**) RADEON(0): RADEONRestoreMode(0x6ee968)
(**) RADEON(0): RADEONRestoreMemMapRegisters() :
(**) RADEON(0):   MC_FB_LOCATION   : 0x1fff0000
(**) RADEON(0):   MC_AGP_LOCATION  : 0x27ff2000
(**) RADEON(0):   Map Changed ! Applying ...
(**) RADEON(0):   Map applied, resetting engine ...
(**) RADEON(0): Updating display base addresses...
(**) RADEON(0): Memory map updated.
(**) RADEON(0): Programming CRTC1, offset: 0x00000000
(**) RADEON(0): Wrote: 0x00180006 0x00010030 0x00000000 (0x0000a700)
(**) RADEON(0): Wrote: rd=6, fd=48, pd=1
(**) RADEON(0): Ok, leaving now...

Found fixes on this page, but alas, they did not work for me.

Any hint or clue? Searching the forums turns up nothing as the only word not blocked in the search is 'fonts' which results in nothing of value.

I'd still suggest submiting bug reports. You might could almost get this whole thing working, lol

[Albert_Alligator]

yes, submitted a bug report yesterday, was told to do exactly what I had already done, that is emerge -C virtual/x11 and emerge -av xorg-x11.

Unfortunately, did not help as I was having to install each library one at a time, and each library would not pull in dependancies....so it would fail, then I'd have to do an equery on the point of failure, that is....if I was lucky and it was a header file or some other file that would lead me back to the package needed.

[Lucero del Alba]

Hi guys/gals:

I haven't read the entire discussion, I'll just tell you how I fixed it, just in case it's useful for anybody here.

Whenever I get this kind of problems, that is I got my compilation stopped by some weird error message when emerging multiple new packages at the same time (very few times I must confess), I just try to emerge those same packages in a different sort order and see what happens. And this got me things solved most of the times...

Okay, this is what I did for this case:

• I entered "emerge -pv xorg-x11" to have a look at all of the new packages.
• I picked a random new package to check whether or not it does not include our problematic package (libXt in this case) as a dependency. And then I found out libXv after my very first attempt, but many others might work.
• emerge -av libXv (it had 12 dependencies on my setup, not including libXt).
• emerge xorg-x11
• presto! (voilá!, if you prefer)

So, it seems that it was only just a matter of getting things sorted in the appropriated order.

As for this message (sorry I can't help it):

I don't want to offend anybody, but who is the genius who decided that modular X.org is stable? It's obvious that it isn't. Just search about this on forums or on bugzilla.

Modular X.org is stable for me, I got it working on my AMD64, and I just needed to be genius enough to prepend an additional command before emerging it. You should try to spend only 5 more minutes and try to use your brain just a little more before barking such a harmful critic. This people, Gentoo developers, been working so hard during the last weeks, probably months before releasing xorg-x11-7.0 stable, just because they really like it. I don't know them, I don't even know which their nicknames are, but I fully respect them - my two computers work because of them.

So, don't mind about this sort of destructive criticism you guys, and keep up the good job

[bunsen]

Since my post yesterday or so, I've had time to dig a bigger hole. Taking out lots of packages that looked as if they belong to modular X (plus or minus a few right ang wrong choices no doubt), I did get past the libX11 problem and even xorg-x11 built too.

Now, off topic I'm stuck on trying to builg Xaw3d somehow (xmkmf needed but it belongs to X)

[aguettinger]

Start posting bugs at bugzilla. X isn't stable on anything but x86, which is why I was asking because mine went up fine (<--P4 i686)

I don't know what you two are talking about, but modular xorg >=7.0 is marked stable for alpha, amd64, arm, mips, ppc, ppc64 and x86 since last friday:

http://packages.gentoo.org/search/?sstring=xorg-x11

No problem here on amd64 with nvidia-1.0.8762 and gcc-4.1.1. Went smooth without an error. I did:

1. quickpkg xorg-x11
2. emerge -Ca xorg-x11 virtual/x11
3. added:
media-video/nvidia-kernel ~amd64
media-video/nvidia-glx ~amd64
to /etc/portage/package.keywords
5. added INPUT_DEVICES="keyboard mouse" to /etc/make.conf
6. added VIDEO_CARDS="nvidia nv" to /etc/make.conf
7. emerge xorg-x11
8. etc-update
9. revdep-rebuild
10. emerge --update nvidia-kernel nvidia-glx
reboot and finished.

[juantxorena]

...

Modular X.org is stable for me, I got it working on my AMD64, and I just needed to be genius enough to prepend an additional command before emerging it. You should try to spend only 5 more minutes and try to use your brain just a little more before barking such a harmful critic. This people, Gentoo developers, been working so hard during the last weeks, probably months before releasing xorg-x11-7.0 stable, just because they really like it. I don't know them, I don't even know which their nicknames are, but I fully respect them - my two computers work because of them.

I spent more than 5 minutes. In fact, I spent from 30 th June afternoon to 3rd July morning trying to install it. After triyng emerge xorg-x11, emerge -DuNv xorg-x11, emerge -e xorg-x11, emerge -e world, uninstalling every single package that any of these had installed before trying it again (and packaging and uninstalling previous version of xorg before, of course), installing first the x11-proto packages then everything else, I finally had to write down all the dependency tree of xorg-x11 and installing packages one by one (or two by two, sometimes), after removing every single archive that xorg-x11 6.8 write over the modular xorg installation attemps (I had to search bugzilla and the forums). So please don't tell me I didn't spent time trying to install it.

The simple fact is that a lot of people have problems resolving dependecies with this package. Some people like you had few problems. Some others, like me, had a lot, with every package. Although it works perfect when installed, I think that a package must be installable by everyone to go stable. As I said before, I didn't intend to offen or to make destructive criticism, the "genius" word was a sarcastic adjetive, result of two days trying to upgrade to modular xorg. If it upset somebody, please sorry.

Back to the xorg problems, I already said how I managed to install it: after uninstalling previous versions of xorg, of course, resolve dependencies one by one using "equery b missing_file". If you can't see the missing file because of the scroll of the terminal, try "emerge foo > foo.archive". After you can see all the output of the emerge using "less foo.archive" or something. It worked for me.

And excuse me for my english and for the long post.

[grofaz]

Start posting bugs at bugzilla. X isn't stable on anything but x86, which is why I was asking because mine went up fine (<--P4 i686)

I don't know what you two are talking about, but modular xorg >=7.0 is marked stable for alpha, amd64, arm, mips, ppc, ppc64 and x86 since last friday:

http://packages.gentoo.org/search/?sstring=xorg-x11

No problem here on amd64 with nvidia-1.0.8762 and gcc-4.1.1. Went smooth without an error. I did:

1. quickpkg xorg-x11
2. emerge -Ca xorg-x11 virtual/x11
3. added:
media-video/nvidia-kernel ~amd64
media-video/nvidia-glx ~amd64
to /etc/portage/package.keywords
5. added INPUT_DEVICES="keyboard mouse" to /etc/make.conf
6. added VIDEO_CARDS="nvidia nv" to /etc/make.conf
7. emerge xorg-x11
8. etc-update
9. revdep-rebuild
10. emerge --update nvidia-kernel nvidia-glx
reboot and finished.

Yeah...I've done it both ways. Once when it actually worked as advertised and several aborted tries where after installing 150+- packages it died due to errors. Frankly I'm sick of xorg-x11-7.0!! I'm very happy with 6.8.2-r8, works fine and my fonts look good. 7.0 fonts look like S**t. So even if I got it bock online I'd have to spend more time fixing the fonts. Now I have to figure out how to make masking actually mask 7.0 so portage doesnt keep insisting I update to modular x. there must be an easier way than having to list each and every modular x x11 package? Putting >=x11-base/xorg-x11-7.0 doesn't work! And everytime I emerge --sync the package.mask file seems to get overwritten.

[wolfbite_aus]

Yer, i'm still going through libx11 HELL
back to 6.8 works

wait awhile try again
same HELL
back again

i'm posative that alot of peoples problems is not what their doing, as to what equipment is in there computers.

Some never have a problem, while other go through hell.
(admittally a fair few would be people that dont read faqs or forums and just want a fix for their stuff ups)

but with so many others having the SAME problem, then it cant be ALL idiots...

and for those people that says it just works, shutup
those that had hiccups and resolved and share are more informative than (haha it works for me)

I've learned lots (esp in diagnosing and tracking a fault)

So does anyone else have some supportive ideas to try??

[grofaz]

Yer, i'm still going through libx11 HELL
back to 6.8 works

wait awhile try again
same HELL
back again

i'm posative that alot of peoples problems is not what their doing, as to what equipment is in there computers.

Some never have a problem, while other go through hell.
(admittally a fair few would be people that dont read faqs or forums and just want a fix for their stuff ups)

but with so many others having the SAME problem, then it cant be ALL idiots...

and for those people that says it just works, shutup
those that had hiccups and resolved and share are more informative than (haha it works for me)

I've learned lots (esp in diagnosing and tracking a fault)

So does anyone else have some supportive ideas to try??

Well I fixed my setup by biting the bullet and reinstalling gentoo from scratch. Now fonts work well with mod x. But I don't recommend reinstalling unless you enjoy that sort of thing. There must be a good way to fix the system without resorting to reinstalling but for me trying to find it was taking longer than a fresh install!

Good luck.

[wolfbite_aus]

yer thats always the last resort (but thats also a window fix method

thought US linux guys can work out the problems (have had lots of help with gentoo forums)

Will hold off til next major update for clean install

will bash and try to fix first, else back to 6.8 (works every time)