SEO

Please, help!
My X server crashes because of bitmap module.
There were never any problems before but
I have updated xorg-x11 but set off the "ipv6" USE flag:

x11-base/xorg-x11-6.8.2-r4 -3dfx +3dnow +bitmap-fonts -cjk -debug
-dlloader -dmx -doc -font-server -insecure-drivers -ipv6* -minimal
+mmx +nls -nocxx +opengl +pam -sdk +sse -static +truetype-fonts
+type1-fonts (-uclibc) -xprint +xv

and the problem is the X server doesn't want to run now on 'startx':

X Window System Version 6.8.2
Release Date: 9 February 2005
X Protocol Version 11, Revision 0, Release 6.8.2
Build Operating System: Linux 2.6.12-gentoo-r10 i686 [ELF]
Current Operating System: Linux 2.6.12-gentoo-r10 #1 Tue Sep 13 06:37:45
CEST 2005 i686
Build Date: 18 September 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: Sun Sep 18 04:45:28 2005
(==) Using config file: "/etc/X11/xorg.conf"
Duplicate symbol __i686.get_pc_thunk.bx
in /usr/lib/modules/fonts/libbitmap.a:bitmapmod.o
Also defined in /usr/lib/modules/fonts/libbitmap.a

Fatal server error:
Module load failure

Please consult the The X.Org Foundation support
at http://wiki.X.Org for help.
Please also check the log file at "/var/log/Xorg.0.log" for additional
information.

XIO: fatal IO error 104 (Connection reset by peer) on X server ":0.0"
after 0 requests (0 known processed) with 0 events remaining.

--
S

S <s7s@op.pl> wrote in news:Xns96D53A28EA369sss@195.34.135.84:

> My X server crashes because of bitmap module.

Should I recompile it but with USE="-bitmap-fonts"?
Will it help and what would it be the impact on functionality when this flag
was unset?

This is an excerpt from my "/var/log/Xorg.0.log"
from the place where '(WW)' starts to occur:

(**) Option "OffTime" "60"
(WW) Open APM failed (/dev/apm_bios) (No such file or directory)
(II) Module ABI versions:
X.Org ANSI C Emulation: 0.2
X.Org Video Driver: 0.7
X.Org XInput driver : 0.4
X.Org Server Extension : 0.2
X.Org Font Renderer : 0.4
(II) Loader running on linux
(II) LoadModule: "bitmap"
(II) Loading /usr/lib/modules/fonts/libbitmap.a
Duplicate symbol __i686.get_pc_thunk.bx in
/usr/lib/modules/fonts/libbitmap.a:bitmapmod.o
Also defined in /usr/lib/modules/fonts/libbitmap.a

Fatal server error:
Module load failure

--
S

S wrote:
> Should I recompile it but with USE="-bitmap-fonts"?

FWIW, I use xorg-x11-6.8.99.15-r1 without the "bitmap-fonts" USE flag.
All the fonts look great.

Paul Bredbury <i@hate-spam.com> wrote in news:20050918061806.746e06de.i@hate-
spam.com:

> FWIW, I use xorg-x11-6.8.99.15-r1 without the "bitmap-fonts" USE flag.
> All the fonts look great.

but I used it all the time so far and this is only now there are *any*
problems!

--
S

S wrote:

> (II) LoadModule: "bitmap"
> (II) Loading /usr/lib/modules/fonts/libbitmap.a
> Duplicate symbol __i686.get_pc_thunk.bx in
> /usr/lib/modules/fonts/libbitmap.a:bitmapmod.o
> Also defined in /usr/lib/modules/fonts/libbitmap.a
>
> Fatal server error:
> Module load failure

OK, I have "solved" the problem. There is an explanation here:

http://www.gentoo.org/proj/en/hardened/hardenedxorg.xml

USE="dlloader" must be together with USE="hardened" elsewhere, but
"dlloader" does not work with nVidia

so I recompiled xorg-x11 as USE="static" but it still has no chance to run
since it must not be "static" with nVidia which in turn is obliged to be
powered by binary *original* drivers (that are loaded as a modules, as I
understand - am I right?)

thus I had to recompile half of a system or so to eliminate all the code
relevant to USE="-hardened", including thus chunks as: gcc, glibc
and it works *now*

GOSH!!!

so the *conclusion* is:
the higly powerful safety option "hardened" is fully *incompatible* with the
nVidia graphics

--
S

S <s7s@imagine.op.pl> wrote:
>
> thus I had to recompile half of a system or so to eliminate all the code
> relevant to USE="-hardened", including thus chunks as: gcc, glibc
> and it works *now*

I guess it would have been sufficient to switch gcc temporarily
to a non-hardened profile (using gcc-config) before
(re)emerging xorg-x11.
At least, this had worked for me some months ago.
So for most things except xorg-x11 you can still have "hardened"
if you want.

Martin Vaeth wrote:

> I guess it would have been sufficient to switch gcc temporarily
> to a non-hardened profile (using gcc-config) before
> (re)emerging xorg-x11.

Thx,
it so so pity You had not said this before I revolutionized my system...

> So for most things except xorg-x11 you can still have "hardened"
> if you want.

that is... else?
these USE flags could be more documented, couldn't they?
sometimes it is so irritating user have to guess everything

"hardened" flag is to be compiled under in few but crucial items: gcc, glibc
pkgconfig - how does it work, especially how does these items influence
other packages when compiled or run - in the respect of the flag?

--
S

S <s7s@imagine.op.pl> wrote:
> Martin Vaeth wrote:
>
>> So for most things except xorg-x11 you can still have "hardened"
>> if you want.
>
> that is... else?

I had some other programs for which hardened caused trouble,
but I could never really find out (e.g. I got never rid of
some strange warnings when X started up). I could have tracked
down the "bad" libraries by trial-and-error (reemerging non-hardened
in a "binary search") but since I observed that "hardened" slowed
down my system anyway, I had decided one day that it is not worth
all the trouble and had recompiled most parts of my system
non-hardened.

> these USE flags could be more documented, couldn't they?
> sometimes it is so irritating user have to guess everything

Yes, indeed. Also e.g. the difference between PIE and PIC and
why some programs have trouble with these flags is rather
unclear unless you really study the source code. Also the
rough hint "PIC should be used only for libraries and not
for programs" is not really useful, since many projects
consist of programs *and* libraries.

> "hardened" flag is to be compiled under in few but crucial items:
> gcc, glibc pkgconfig - how does it work, especially how does
> these items influence other packages when compiled or run -
> in the respect of the flag?

I only know for gcc: With this flag you get the hardened
gcc-profiles, and if you use these profiles, PIC, PIE, and SSP
are automatically enabled (i.e. even if not explicitly set in
CFLAGS or CXXFLAGS). But maybe it has further effects...