Modular X server bugs, annoyances and solutions (Part 1)

Message

fuoco · Post by **fuoco** » Wed Oct 19, 2005 5:48 pm

spyderous wrote:
fuoco wrote:I suppose the reason is that not all packages in portage are adapted to the new modular X dependencies ?
Exactly. You can help by filing bugs against those packages using http://dev.gentoo.org/~spyderous/xorg-x ... _howto.txt.

OK, I am soon approaching the end of the system install and then I will try to unmask the right stuff to get `emerge gnome-2.12` to pull modular X dependencies. I will report the ebuilds that don't work well with the modular X dependencies. Is that OK ? Is it even possible to do that before a modular X RC is out ?

wuno · Post by **wuno** » Wed Oct 19, 2005 6:47 pm

Ok, its going serious

7.0-RC1 is out

fuoco · Post by **fuoco** » Thu Oct 20, 2005 5:36 pm

ebuilds for modular X 7.0 RC1 are already in portage ?

StringCheesian · Post by **StringCheesian** » Thu Oct 20, 2005 5:39 pm

fuoco wrote:ebuilds for modular X 7.0 RC1 are already in portage ?

Yep, I'm halfway through them, and they're emerging fine so far.

Xake · Post by **Xake** » Thu Oct 20, 2005 8:12 pm

Ok. Now that I have emerge the new packages in portage it is time to say my first impressions.

My mousbuttons (number 2 and 3 with evdev) is still swapped.
My keyboard have stopped working as it should. Local keys work, however Alt and Alt Gr does not so I can't switch to framebuffer-console and I can't make (at)...

Xorg.0.log wrote:(**) Option "CoreKeyboard"
(**) Keyboard0: Core Keyboard
(**) Option "Protocol" "standard"
(**) Keyboard0: Protocol: standard
(**) Option "AutoRepeat" "500 30"
(**) Option "XkbRules" "xorg"
(**) Keyboard0: XkbRules: "xorg"
(**) Option "XkbModel" "pc105"
(**) Keyboard0: XkbModel: "pc105"
(**) Option "XkbLayout" "se"
(**) Keyboard0: XkbLayout: "se"
(**) Option "XkbOptions" "altwin:menu"
(**) Keyboard0: XkbOptions: "altwin:menu"
(**) Option "CustomKeycodes" "off"
(**) Keyboard0: CustomKeycodes disabled
(II) XINPUT: Adding extended input device "Keyboard0" (type: KEYBOARD)
(II) XINPUT: Adding extended input device "Mouse0" (type: KEYBOARD)
(II) XINPUT: Adding extended input device "NVIDIA Event Handler" (type: Other)
(EE) Couldn't load XKB keymap, falling back to pre-XKB keymap

What happened with that one in the transition from RC0 to RC1?

Other than that everything seems to work (nvidia binary drivers and opengl: no problem, GNOME 2.12: just as it did before).

For the rest of it: damn, this shit starts WAY faster now on my machine.

wuno · Post by **wuno** » Thu Oct 20, 2005 8:42 pm

Edit: Workaround isn't needed anymore, the -r1 ebuilds reflect the movement of the keyboard files

Xake wrote:Ok. Now that I have emerge the new packages in portage it is time to say my first impressions.

My mousbuttons (number 2 and 3 with evdev) is still swapped.
My keyboard have stopped working as it should. Local keys work, however Alt and Alt Gr does not so I can't switch to framebuffer-console and I can't make (at)...

What happened with that one in the transition from RC0 to RC1?
[/quote]
Somehow the xkeyboard extenions moved from /usr/lib/X11/xkb to /usr/share/X11/xkb. In the xorg CVS ChangeLog they said, this was due to match the monolith's paths.
And yes, no German Umlaute and no Alt Gr ... same symptoms as you said.
Otherwise, so far everything fine. Thanks to Spyderous making this ton of ebuilds so fast available

Voltago · Post by **Voltago** » Thu Oct 20, 2005 10:13 pm

wuno wrote:Workaround for the keyboard problems after upgrade to RC1:
Code: Select all
 # rm -rf /usr/lib/X11/xkb
 # ln -s /usr/share/X11/xkb /usr/lib/X11/
 # emerge xkbdata

Thanks for the tip, I'm sure you have spared me a headache or two...
Xorg-server now seems to have improved unicode support (I'm using UTF-8 ). Well, at least Qt doesn't bitch any more about unsupported locales, and the umlauts work all of a sudden in urxvt. AltGr seems to work fine too. All hail Spyderous!

fuoco · Post by **fuoco** » Fri Oct 21, 2005 12:36 am

Does cairo-1.0.2 have broken modular dependencies or am I wrong ? even though I have xorg-x11 masked it wants to pull it... there's both virtual/x11 and virtual/xft

wuno · Post by **wuno** » Fri Oct 21, 2005 5:58 am

fuoco wrote:Does cairo-1.0.2 have broken modular dependencies or am I wrong ? even though I have xorg-x11 masked it wants to pull it... there's both virtual/x11 and virtual/xft

I see no problem here, even w/o masking xorg-x11, after adding PROVIDES="virtual/x11" in xorg-server ebuild.

fuoco · Post by **fuoco** » Fri Oct 21, 2005 8:47 am

spyderous wrote:
fuoco wrote:I suppose the reason is that not all packages in portage are adapted to the new modular X dependencies ?
Exactly. You can help by filing bugs against those packages using http://dev.gentoo.org/~spyderous/xorg-x ... _howto.txt.

Seems like modular X bugs are not very welcome in bugzilla... I guess I will stop posting them.

fuoco · Post by **fuoco** » Fri Oct 21, 2005 8:50 am

wuno wrote:
fuoco wrote:Does cairo-1.0.2 have broken modular dependencies or am I wrong ? even though I have xorg-x11 masked it wants to pull it... there's both virtual/x11 and virtual/xft
I see no problem here, even w/o masking xorg-x11, after adding PROVIDES="virtual/x11" in xorg-server ebuild.

Bug asfar as I understand virtual/x11 is supposed to be drop, so instead of adding virutual/x11 provide in xorg-server, I add xorg-server to the ebuilds that miss them. They probably miss other deps as well - I don't yet know which ones and how to check, but I will try to work on it. I thought in that matter I could offer a bit of help to devs, but it doesn't seem welcome by them...

fuoco · Post by **fuoco** » Fri Oct 21, 2005 10:15 am

I'm trying to track down all the packages that pull xorg-x11 instead of having the correct modular X deps. So far I have quite a few just from 'emerge gnome' (2.12). Maybe I should post a list here?

I have now reached a dead end with mozilla-firefox and gecko-sdk. Both don't seem to depend on virtual/x11 or xorg-x11 directly, and still they want to pull it. I have also looked in the eclasses they inherit. Anyone knows what's going on there? and how to solve it?

wuno · Post by **wuno** » Fri Oct 21, 2005 11:06 am

fuoco wrote:I'm trying to track down all the packages that pull xorg-x11 instead of having the correct modular X deps. So far I have quite a few just from 'emerge gnome' (2.12). Maybe I should post a list here?

I have now reached a dead end with mozilla-firefox and gecko-sdk. Both don't seem to depend on virtual/x11 or xorg-x11 directly, and still they want to pull it. I have also looked in the eclasses they inherit. Anyone knows what's going on there? and how to solve it?

Do you USE mozsvg for building, this could be a point where it may depend on X

fuoco · Post by **fuoco** » Fri Oct 21, 2005 11:19 am

wuno wrote:
fuoco wrote:I'm trying to track down all the packages that pull xorg-x11 instead of having the correct modular X deps. So far I have quite a few just from 'emerge gnome' (2.12). Maybe I should post a list here?

I have now reached a dead end with mozilla-firefox and gecko-sdk. Both don't seem to depend on virtual/x11 or xorg-x11 directly, and still they want to pull it. I have also looked in the eclasses they inherit. Anyone knows what's going on there? and how to solve it?
Do you USE mozsvg for building, this could be a point where it may depend on X

I removed mozsvg and found out in mozconfig eclass moznoxft. fixed both and i now finally tracked ALL the problematic packages for gnome-2.12 in relation to modular X. I now have a full list of all those packages. I don't know if I should post it here...

wuno · Post by **wuno** » Fri Oct 21, 2005 11:26 am

Sorry, I just wanted to add to my last post that thing about the eclass, a little too late.

fuoco wrote: I removed mozsvg and found out in mozconfig eclass moznoxft. fixed both and i now finally tracked ALL the problematic packages for gnome-2.12 in relation to modular X. I now have a full list of all those packages. I don't know if I should post it here...

Why not? I am pretty sure that it will help!

Priyantha Bleeker · Post by **Priyantha Bleeker** » Fri Oct 21, 2005 2:10 pm

fuoco wrote:
wuno wrote:
fuoco wrote:I'm trying to track down all the packages that pull xorg-x11 instead of having the correct modular X deps. So far I have quite a few just from 'emerge gnome' (2.12). Maybe I should post a list here?

I have now reached a dead end with mozilla-firefox and gecko-sdk. Both don't seem to depend on virtual/x11 or xorg-x11 directly, and still they want to pull it. I have also looked in the eclasses they inherit. Anyone knows what's going on there? and how to solve it?
Do you USE mozsvg for building, this could be a point where it may depend on X
I removed mozsvg and found out in mozconfig eclass moznoxft. fixed both and i now finally tracked ALL the problematic packages for gnome-2.12 in relation to modular X. I now have a full list of all those packages. I don't know if I should post it here...

Can you post the list plz ?
I have the same problems I think.

balkira · Post by **balkira** » Fri Oct 21, 2005 6:28 pm

hi,

I've merged the 0.99.2-r1 version but it seems that ALT-GR doesn't work.
I have tried the previous workaround but it does not help.
Any suggestions?

wuno · Post by **wuno** » Fri Oct 21, 2005 7:33 pm

balkira wrote:hi,

I've merged the 0.99.2-r1 version but it seems that ALT-GR doesn't work.
I have tried the previous workaround but it does not help.
Any suggestions?

Did you emerge also xkbcomp and xkbdata both 0.99.1-r1?

balkira · Post by **balkira** » Fri Oct 21, 2005 7:55 pm

Yes I did but I should have read the xorg logs earlier.
My issue comes from this:

Code: Select all

X Protocol Version 11, Revision 0, 0.99.2
Build Operating System:Linux 2.6.13-gentoo-r4 i686
Current Operating System: Linux laptop 2.6.13-gentoo-r4 #2 SMP Sat Oct 15 16:44:19 GMT 2005 i686
Build Date: 21 October 2005
        Before reporting problems, check http://wiki.x.org
        to make sure that you have the latest version.
Module Loader present
Markers: (--) probed, (**) from config file, (==) default setting,
        (++) from command line, (!!) notice, (II) informational,
        (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Fri Oct 21 21:23:29 2005
(==) Using config file: "/etc/X11/xorg.conf"
The XKEYBOARD keymap compiler (xkbcomp) reports:
> Error:            Can't find file "pc/fr-latin9" for symbols include
>                   Exiting
>                   Abandoning symbols file "default"
Errors from xkbcomp are not fatal to the X server

and it is just a xorg.conf issue as the 'pc/fr-latin9' seems to have disappeared since the last update.
A quick locate tells me that there is only 'pc/latin' that is supported.
Thanks for the advice.
EDIT: changing to pc/fr solved the issue.

Archangel1 · Post by **Archangel1** » Sat Oct 22, 2005 6:26 am

Xake wrote:My mousbuttons (number 2 and 3 with evdev) is still swapped.

Mine too.... wish they'd fix this one!
There's a bug filed but no progress seems to have been made. I should think they'll have to fix it before making the final release (it's really a showstopper if you're using evdev) so hopefully there'll be something done soon.

Schmolch · Post by **Schmolch** » Sat Oct 22, 2005 6:51 am

With xorg modular i get the famous "cound not open default font:fixed"-error at startup.
i looked at the FAQ about that and i turns out that for some unknown reasons a few of my /usr/share/fonts dirs seem to have issues, including fonts/misc (i think thats were the default font fixed is).
Anyway, i rm'ed my whole ../fonts dir and remerged all the fonts and could not get it working.
I also used that "mkfontdir"-command on those dirs its complaining about.
In the end i just fetched Xorg Monolitic from cvs and thats working fine.

irondog · Post by **irondog** » Sat Oct 22, 2005 11:08 am

WTF. Those radeon drivers with EXA are so SWEEET! RC1 is such a nice one. For at least my ATI powered PC RC0 was completely broken (only fbdev drivers worked

).

I'm enjoying KDE 3.5-alpha1 with composite and opensource, EXA enabled Radeon drivers right now, Great!!

infirit · Post by **infirit** » Sat Oct 22, 2005 12:17 pm

irondog wrote:WTF. Those radeon drivers with EXA are so SWEEET! RC1 is such a nice one. For at least my ATI powered PC RC0 was completely broken (only fbdev drivers worked ).

I'm enjoying KDE 3.5-alpha1 with composite and opensource, EXA enabled Radeon drivers right now, Great!!

What type of card do you have? On my r350 composit is as slow as it was with XAA

EDIT: Never mind, all pre r300 cards have exa acceleration

irondog · Post by **irondog** » Sat Oct 22, 2005 1:24 pm

Ati Radeon 9200 (is a r200 I think).

Code: Select all

Section "Device"
    Identifier "ati0"
    Driver "radeon"
    Option "AccelMethod" "exa"
EndSection

Section "Extensions"
    Option "Composite" "Enable"
    Option "RENDER" "Enable"
EndSection

Tyrius · Post by **Tyrius** » Sat Oct 22, 2005 10:08 pm

Schmolch wrote:With xorg modular i get the famous "cound not open default font:fixed"-error at startup.
i looked at the FAQ about that and i turns out that for some unknown reasons a few of my /usr/share/fonts dirs seem to have issues, including fonts/misc (i think thats were the default font fixed is).
Anyway, i rm'ed my whole ../fonts dir and remerged all the fonts and could not get it working.
I also used that "mkfontdir"-command on those dirs its complaining about.
In the end i just fetched Xorg Monolitic from cvs and thats working fine.

I had the same problem. The issue for me was that the FONTPATH in the xorg.conf file had ":unscaled" at the end of some of the FONTPATH lines. When I removed this text xorg modular runs like a dream. I guess xorg modular doesn't like the ":unscaled" option.

Hope this helps. Good luck!