Gentoo Forums :: View topic - Xorg fail with startx

Xorg fail with startx

View unanswered posts
View posts from last 24 hours
View posts from last 7 days

Goto page Previous 1, 2

Gentoo Forums Forum Index

Desktop Environments

View previous topic :: View next topic

Author

Message

pingtoo
l33t
l33t

Joined: 10 Sep 2021
Posts: 926
Location: Richmond Hill, Canada

Posted: Mon Apr 15, 2024 2:35 pm Post subject:

kgdrenefort,

I was at lost when I first saw your post said with default setting (xclock, xterm...) still not working. I was thinking I need to dig out the source code to see how to debug why the those program does not even produce some sort of error messages. Anyway I am glad I waited (pause to get breakfast) as it turn out just misunderstanding the situation.

So now we are left with only one issue "awesome" binary. As the state back from your last post that have execute "awesome", it is showing "Illegal instruction" which indicate the binary contain machine code (instruction) not suitable for your CPU. We have already establish that you build this binary on the "binhost" which have different CPU ARCH than your client CPU ARCH.

You tried build locally, however the build process failed due to error

kgdrenefort wrote:

And it failed: https://bpa.st/MU6A

It fails on this line into /var/tmp/portage/x11-wm/awesome-4.3-r103/work/awesome-4.3/tests/examples/runner.sh (line 22):

I checked the "runner.sh" script it try to launch test cases use lua program (I am not sure it is the "lua" binary or a different binary linked with liblua5.1) but the executable also produce

Code:

/var/tmp/portage/x11-wm/awesome-4.3-r103/work/awesome-4.3/tests/examples/runner.sh: line 22: 62 Illegal instruction (core dumped) "$@"

So the "awesome" issue is originated from the lua package on your client is not compatible with your client CPU ARCH.

I suggest you can try these steps

to rebuild lua package on your client
rebuild awesome package
launch awesome in X (startx)

I am not sure the depth of the lua system involve in the awesome system, so it is possible you need to rebuild something else in order to get the right configuration of lua package in order to build awesome.

As your question,

kgdrenefort wrote:

What do you mean by «Be sure that systemd or elogind is running (…)».

together with Neddy's suggestion "exec dbus-launch --sh-syntax --exit-with-session awesome"

It is about modern Desktop Environment (DE) that support "seat" and "session" concept, I think we can delay this part for now since awesomeWM in my opinion does not fit will for DE.

kgdrenefort
Apprentice

Joined: 19 Sep 2023
Posts: 186
Location: Somewhere in the 77

Posted: Mon Apr 15, 2024 3:12 pm Post subject:

NeddySeagoon wrote:

kgdrenefort,

Code:

2024-04-15 15:09:23 E: awesome: signal_fatal:457: signal 4, dumping backtrace
awesome(backtrace_get+0x5e) [0x55779a0b432e]
awesome(+0x12ec3) [0x55779a0a0ec3]
/usr/lib64/libc.so.6(+0x3a210) [0x7eff4c90c210]
/usr/lib64/liblua5.1.so.0(lua_newstate+0x1a3) [0x7eff4cb1b083]
/usr/lib64/liblua5.1.so.0(luaL_newstate+0x13) [0x7eff4cb08bd3]
awesome(luaA_init+0x17) [0x55779a0aa937]
awesome(main+0xe10) [0x55779a0a0650]
/usr/lib64/libc.so.6(+0x24090) [0x7eff4c8f6090]
/usr/lib64/libc.so.6(__libc_start_main+0x89) [0x7eff4c8f6149]
awesome(_start+0x25) [0x55779a0a0dc5]

is the interesting bit.

Code:

xinit: connection to X server lost

is expected as Xorg works.

Code:

2024-04-15 15:09:23 E: awesome: signal_fatal:457: signal 4, dumping backtrace

signal 4 is SIGILL.
That's an illegal instruction. That points to something that awesome needs is built for the wrong CPU.

After that error is generated, there may be a few lines at the end of dmesg that tell which file generated the illegal instruction.

Do startx again, when it fails, look at the end of dmesg. It should say something about an illegal instruction.
Post those few lines please.

Sadly, using dmesg command before and after trying to startx is identical, this is the output (before the startx command failed): https://bpa.st/PRWQ
(or the last 30 lines directly below, from the command dmesg after the failing startx attempt)

Code:

kgdrenefort@satan ~ $ dmesg | tail -n 30
[ 6.607692] nouveau 0000:01:00.0: DRM: DCB outp 03: 080153d6 0f220020
[ 6.607695] nouveau 0000:01:00.0: DRM: DCB outp 04: 08015392 00020020
[ 6.607697] nouveau 0000:01:00.0: DRM: DCB outp 05: 080143c6 0f220010
[ 6.607700] nouveau 0000:01:00.0: DRM: DCB outp 06: 08014382 00020010
[ 6.607702] nouveau 0000:01:00.0: DRM: DCB outp 08: 040383b6 0f220014
[ 6.607705] nouveau 0000:01:00.0: DRM: DCB outp 10: 020273a6 0f220010
[ 6.607707] nouveau 0000:01:00.0: DRM: DCB outp 11: 02027362 00020010
[ 6.607710] nouveau 0000:01:00.0: DRM: DCB outp 13: 02049300 00000000
[ 6.607713] nouveau 0000:01:00.0: DRM: DCB conn 00: 00000040
[ 6.607715] nouveau 0000:01:00.0: DRM: DCB conn 01: 00001161
[ 6.607717] nouveau 0000:01:00.0: DRM: DCB conn 02: 00001231
[ 6.607720] nouveau 0000:01:00.0: DRM: DCB conn 03: 01000331
[ 6.607722] nouveau 0000:01:00.0: DRM: DCB conn 04: 01000446
[ 6.607724] nouveau 0000:01:00.0: DRM: DCB conn 05: 02000546
[ 6.607726] nouveau 0000:01:00.0: DRM: DCB conn 06: 00010631
[ 6.607729] nouveau 0000:01:00.0: DRM: DCB conn 07: 00010746
[ 6.607731] nouveau 0000:01:00.0: DRM: DCB conn 08: 00020847
[ 6.607733] nouveau 0000:01:00.0: DRM: DCB conn 09: 00000900
[ 6.608694] nouveau 0000:01:00.0: DRM: MM: using COPY0 for buffer copies
[ 6.642044] nouveau 0000:01:00.0: DRM: Skipping nv_backlight registration
[ 6.642585] acpi device:01: registered as cooling_device9
[ 6.642999] [drm] Initialized nouveau 1.4.0 20120801 for 0000:01:00.0 on minor 0
[ 6.669966] 8021q: 802.1Q VLAN Support v1.8
[ 6.848840] fbcon: nouveaudrmfb (fb0) is primary device
[ 6.949202] iwlwifi 0000:25:00.0: Radio type=0x1-0x2-0x0
[ 7.238832] iwlwifi 0000:25:00.0: Radio type=0x1-0x2-0x0
[ 8.379014] Console: switching to colour frame buffer device 240x67
[ 8.380679] nouveau 0000:01:00.0: [drm] fb0: nouveaudrmfb frame buffer device
[ 9.874774] e1000e 0000:00:19.0 enp0s25: NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx
[ 36.373393] systemd-journald[373]: /var/log/journal/70965f52ac8d4b2b9994acbba20bc04e/user-1000.journal: Journal file uses a different sequence number ID, rotating.

pingtoo wrote:

To be honest, once you said you were reading code source I was thinking you were a bit of crazy, or very nice, or very curious :lol:

. I am sorry to have make you scratch your head for nothing.

pingtoo wrote:

So now we are left with only one issue "awesome" binary. As the state back from your last post that have execute "awesome", it is showing "Illegal instruction" which indicate the binary contain machine code (instruction) not suitable for your CPU. We have already establish that you build this binary on the "binhost" which have different CPU ARCH than your client CPU ARCH.

You tried build locally, however the build process failed due to error

kgdrenefort wrote:

And it failed: https://bpa.st/MU6A

It fails on this line into /var/tmp/portage/x11-wm/awesome-4.3-r103/work/awesome-4.3/tests/examples/runner.sh (line 22):

I checked the "runner.sh" script it try to launch test cases use lua program (I am not sure it is the "lua" binary or a different binary linked with liblua5.1) but the executable also produce

Code:

/var/tmp/portage/x11-wm/awesome-4.3-r103/work/awesome-4.3/tests/examples/runner.sh: line 22: 62 Illegal instruction (core dumped) "$@"

So the "awesome" issue is originated from the lua package on your client is not compatible with your client CPU ARCH.

I suggest you can try these steps

to rebuild lua package on your client
rebuild awesome package
launch awesome in X (startx)

Will do that tomorrow morning and get back to you.

pingtoo wrote:

As your question,

kgdrenefort wrote:

What do you mean by «Be sure that systemd or elogind is running (…)».

Ok, let's move this for later, then.

Regards,
GASPARD DE RENEFORT Kévin
_________________
«Gentoo does not have problems, only learning opportunities.» - NeddySeagoon
«If your Gentoo installation isn't valuable to you, feel free to continue to ignore the instructions.» - figueroa

NeddySeagoon
Administrator

Joined: 05 Jul 2003
Posts: 54272
Location: 56N 3W

Posted: Mon Apr 15, 2024 3:50 pm Post subject:

kgdrenefort,

That means something trapped the illegal instruction before it got to the kernel. It was worth looking.

There are three packages implicated so far. There may be more.

Code:

awesome(backtrace_get+0x5e) [0x55779a0b432e]
awesome(+0x12ec3) [0x55779a0a0ec3]
/usr/lib64/libc.so.6(+0x3a210) [0x7eff4c90c210]
/usr/lib64/liblua5.1.so.0(lua_newstate+0x1a3) [0x7eff4cb1b083]
/usr/lib64/liblua5.1.so.0(luaL_newstate+0x13) [0x7eff4cb08bd3]
awesome(luaA_init+0x17) [0x55779a0aa937]
awesome(main+0xe10) [0x55779a0a0650]
/usr/lib64/libc.so.6(+0x24090) [0x7eff4c8f6090]
/usr/lib64/libc.so.6(__libc_start_main+0x89) [0x7eff4c8f6149]
awesome(_start+0x25) [0x55779a0a0dc5]

That's awesome itself, /usr/lib64/libc.so.6, which is glibc and /usr/lib64/liblua5.1.so.0, which looks like lua5.1.

When glibc breaks, most things break too. Rebuild lua5.1 on the host that it will run on.
Do not use distcc nor ccache. We need a clean uncontaminated build.
It's possible that the problem is in a dependency of something too but this is a recursive process.
_________________
Regards,

NeddySeagoon

Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.

kgdrenefort
Apprentice

Joined: 19 Sep 2023
Posts: 186
Location: Somewhere in the 77

Posted: Tue Apr 16, 2024 8:21 am Post subject:

Hello,

If I understand, you wants me to rebuild lua packages and awesome as well.

These seems to have been rebuilt, from client, without any problem:

Code:

[IP-] [ ] app-eselect/eselect-lua-4-r1:0
[IP-] [ ] dev-lang/lua-5.1.5-r200:5.1
[IP-] [ ] dev-lang/luajit-2.1.0_beta3_p20220127-r2:2/2.1.0_beta3_p20220127
[IP-] [ ] dev-lua/luafilesystem-1.8.0-r101:0

But when it's about recompiling Awesome, saddly it's an error, complete buildlog here: https://bpa.st/QXPA

(The last lines where the first error is spotted below, from the paste above)

Code:

FAILED: CMakeFiles/lgi-check-run /var/tmp/portage/x11-wm/awesome-4.3-r103/work/awesome-4.3_build/CMakeFiles/lgi-check-run
cd /var/tmp/portage/x11-wm/awesome-4.3-r103/work/awesome-4.3_build && /var/tmp/portage/x11-wm/awesome-4.3-r103/work/awesome-4.3_build/lgi-check
[19/270] cd /var/tmp/portage/x11-wm/awesome-4.3-r103/work/awesome-4.3_build && /var/tmp/portage/x11-wm/awesome-4.3-r103/work/awesome-4.3/tests/examples/runner.sh /var/tmp/portage/x11-wm/awesome-4.3-r103/work/awesome-4.3/tests/examples/awful/mouse/coords.output.txt env -u LUA_PATH_5_1 -u LUA_PATH_5_2 -u LUA_PATH_5_3 "LUA_PATH=/var/tmp/portage/x11-wm/awesome-4.3-r103/work/awesome-4.3/tests/examples/shims/?.lua;/var/tmp/portage/x11-wm/awesome-4.3-r103/work/awesome-4.3/tests/examples/shims/?/init.lua;/var/tmp/portage/x11-wm/awesome-4.3-r103/work/awesome-4.3/tests/examples/shims/?;/var/tmp/portage/x11-wm/awesome-4.3-r103/work/awesome-4.3/lib/?.lua;/var/tmp/portage/x11-wm/awesome-4.3-r103/work/awesome-4.3/lib/?/init.lua;/var/tmp/portage/x11-wm/awesome-4.3-r103/work/awesome-4.3/lib/?;/var/tmp/portage/x11-wm/awesome-4.3-r103/work/awesome-4.3/themes/?.lua;/var/tmp/portage/x11-wm/awesome-4.3-r103/work/awesome-4.3/themes/?;" AWESOME_THEMES_PATH=/var/tmp/portage/x11-wm/awesome-4.3-r103/work/awesome-4.3/themes/ SOURCE_DIRECTORY=/var/tmp/portage/x11-wm/awesome-4.3-r103/work/awesome-4.3 lua /var/tmp/portage/x11-wm/awesome-4.3-r103/work/awesome-4.3/tests/examples/awful/template.lua /var/tmp/portage/x11-wm/awesome-4.3-r103/work/awesome-4.3/tests/examples/awful/mouse/coords.lua /var/tmp/portage/x11-wm/awesome-4.3-r103/work/awesome-4.3_build/doc/images/AUTOGEN_awful_mouse_coords || true
/var/tmp/portage/x11-wm/awesome-4.3-r103/work/awesome-4.3/tests/examples/runner.sh: line 22: 145 Illegal instruction (core dumped) "$@" > ${file_stdout} 2> ${file_stderr}
Result: 132
ninja: build stopped: subcommand failed.
* ERROR: x11-wm/awesome-4.3-r103::gentoo failed (compile phase):
* ninja -v -j2 -l2 failed
*
* Call stack:
* ebuild.sh, line 136: Called src_compile
* environment, line 3039: Called cmake_src_compile
* environment, line 1225: Called cmake_build
* environment, line 1192: Called eninja
* environment, line 1684: Called die
* The specific snippet of code:
* "$@" || die -n "${*} failed"
*
* If you need support, post the output of `emerge --info '=x11-wm/awesome-4.3-r103::gentoo'`,
* the complete build log and the output of `emerge -pqv '=x11-wm/awesome-4.3-r103::gentoo'`.
* The complete build log is located at '/var/tmp/portage/x11-wm/awesome-4.3-r103/temp/build.log'.
* The ebuild environment file is located at '/var/tmp/portage/x11-wm/awesome-4.3-r103/temp/environment'.
* Working directory: '/var/tmp/portage/x11-wm/awesome-4.3-r103/work/awesome-4.3_build'
* S: '/var/tmp/portage/x11-wm/awesome-4.3-r103/work/awesome-4.3'

>>> Failed to emerge x11-wm/awesome-4.3-r103, Log file:

>>> '/var/tmp/portage/x11-wm/awesome-4.3-r103/temp/build.log'

* Messages for package x11-wm/awesome-4.3-r103:

* ERROR: x11-wm/awesome-4.3-r103::gentoo failed (compile phase):
* ninja -v -j2 -l2 failed
*
* Call stack:
* ebuild.sh, line 136: Called src_compile
* environment, line 3039: Called cmake_src_compile
* environment, line 1225: Called cmake_build
* environment, line 1192: Called eninja
* environment, line 1684: Called die
* The specific snippet of code:
* "$@" || die -n "${*} failed"
*
* If you need support, post the output of `emerge --info '=x11-wm/awesome-4.3-r103::gentoo'`,
* the complete build log and the output of `emerge -pqv '=x11-wm/awesome-4.3-r103::gentoo'`.
* The complete build log is located at '/var/tmp/portage/x11-wm/awesome-4.3-r103/temp/build.log'.
* The ebuild environment file is located at '/var/tmp/portage/x11-wm/awesome-4.3-r103/temp/environment'.
* Working directory: '/var/tmp/portage/x11-wm/awesome-4.3-r103/work/awesome-4.3_build'
* S: '/var/tmp/portage/x11-wm/awesome-4.3-r103/work/awesome-4.3'

Where above there is an illegal instruction:

Code:

/var/tmp/portage/x11-wm/awesome-4.3-r103/work/awesome-4.3/tests/examples/runner.sh: line 22: 145 Illegal instruction (core dumped) "$@" > ${file_stdout} 2> ${file_stderr}

emerge --info:

Code:

satan ~ # emerge --info '=x11-wm/awesome-4.3-r103::gentoo'
Portage 3.0.61 (python 3.11.8-final-0, default/linux/amd64/23.0/desktop/systemd, gcc-13, glibc-2.38-r11, 6.6.21-gentoo-dist x86_64)
=================================================================
System Settings
=================================================================
System uname: Linux-6.6.21-gentoo-dist-x86_64-Intel-R-_Core-TM-_i7-2820QM_CPU_@_2.30GHz-with-glibc2.38
KiB Mem: 3958724 total, 3455708 free
KiB Swap: 4194300 total, 4194300 free
Timestamp of repository gentoo: Fri, 12 Apr 2024 10:30:00 +0000
Head commit of repository gentoo: 767b1858b6e42a550309b1daff116f1dda1ba4f4
sh bash 5.1_p16-r6
ld GNU ld (Gentoo 2.41 p5) 2.41.0
app-misc/pax-utils: 1.3.7::gentoo
app-shells/bash: 5.1_p16-r6::gentoo
dev-build/autoconf: 2.71-r6::gentoo
dev-build/automake: 1.16.5-r2::gentoo
dev-build/cmake: 3.28.3::gentoo
dev-build/libtool: 2.4.7-r4::gentoo
dev-build/make: 4.4.1-r1::gentoo
dev-build/meson: 1.3.2::gentoo
dev-lang/perl: 5.38.2-r2::gentoo
dev-lang/python: 3.10.14_p1::gentoo, 3.11.8_p1::gentoo, 3.12.2_p1::gentoo
dev-lang/rust-bin: 1.75.0::gentoo
sys-apps/baselayout: 2.14-r2::gentoo
sys-apps/sandbox: 2.38::gentoo
sys-apps/systemd: 255.3-r1::gentoo
sys-devel/binutils: 2.41-r5::gentoo
sys-devel/binutils-config: 5.5::gentoo
sys-devel/clang: 17.0.6::gentoo
sys-devel/gcc: 13.2.1_p20240210::gentoo
sys-devel/gcc-config: 2.11::gentoo
sys-devel/llvm: 17.0.6::gentoo
sys-kernel/linux-headers: 6.6-r1::gentoo (virtual/os-headers)
sys-libs/glibc: 2.38-r11::gentoo
Repositories:

gentoo
location: /var/db/repos/gentoo
sync-type: rsync
sync-uri: rsync://rsync.gentoo.org/gentoo-portage
priority: -1000
volatile: False
sync-rsync-verify-max-age: 3
sync-rsync-extra-opts:
sync-rsync-verify-jobs: 1
sync-rsync-verify-metamanifest: yes

Binary Repositories:

gentoobinhost
priority: 10
sync-uri: https://distfiles.gentoo.org/releases/amd64/binpackages/23.0/x86-64

binhost
priority: 1
sync-uri: http://192.168.1.103:81/packages

ACCEPT_KEYWORDS="amd64"
ACCEPT_LICENSE="@FREE @BINARY-REDISTRIBUTABLE"
CBUILD="x86_64-pc-linux-gnu"
CFLAGS="-march=native -O2 -pipe"
CHOST="x86_64-pc-linux-gnu"
CONFIG_PROTECT="/etc /usr/share/gnupg/qualified.txt"
CONFIG_PROTECT_MASK="/etc/ca-certificates.conf /etc/dconf /etc/env.d /etc/fonts/fonts.conf /etc/gconf /etc/gentoo-release /etc/revdep-rebuild /etc/sandbox.d"
CXXFLAGS="-march=native -O2 -pipe"
DISTDIR="/var/cache/distfiles"
ENV_UNSET="CARGO_HOME DBUS_SESSION_BUS_ADDRESS DISPLAY GDK_PIXBUF_MODULE_FILE GOBIN GOPATH PERL5LIB PERL5OPT PERLPREFIX PERL_CORE PERL_MB_OPT PERL_MM_OPT XAUTHORITY XDG_CACHE_HOME XDG_CONFIG_HOME XDG_DATA_HOME XDG_RUNTIME_DIR XDG_STATE_HOME"
FCFLAGS="-march=native -O2 -pipe"
FEATURES="assume-digests binpkg-docompress binpkg-dostrip binpkg-logs binpkg-multi-instance buildpkg-live config-protect-if-modified distlocks ebuild-locks fixlafiles ipc-sandbox merge-sync multilib-strict network-sandbox news parallel-fetch pid-sandbox pkgdir-index-trusted preserve-libs protect-owned qa-unresolved-soname-deps sandbox sfperms strict unknown-features-warn unmerge-logs unmerge-orphans userfetch userpriv usersandbox usersync xattr"
FFLAGS="-march=native -O2 -pipe"
GENTOO_MIRRORS="https://mirrors.ircam.fr/pub/gentoo-distfiles/ https://gentoo.mirrors.ovh.net/gentoo-distfiles/ https://mirrors.soeasyto.com/distfiles.gentoo.org/"
LANG="en_US.utf8"
LDFLAGS="-Wl,-O1 -Wl,--as-needed -Wl,-z,pack-relative-relocs"
LEX="flex"
MAKEOPTS="-j2 -l2"
PKGDIR="/var/cache/binpkgs"
PORTAGE_CONFIGROOT="/"
PORTAGE_RSYNC_OPTS="--recursive --links --safe-links --perms --times --omit-dir-times --compress --force --whole-file --delete --stats --human-readable --timeout=180 --exclude=/distfiles --exclude=/local --exclude=/packages --exclude=/.git"
PORTAGE_TMPDIR="/var/tmp"
SHELL="/bin/bash"
USE="X a52 aac acl acpi alsa amd64 bash-completion branding bzip2 cairo cdda cdr cet colord crypt cups curl dbus dri dts dvd dvdr encode exif flac gdbm gif git gpm grub gui hddtemp iconv icu ipv6 jpeg lcms libnotify libtirpc lm-sensors mad man mng mp3 mp4 mpeg multilib ncurses networkmanager nls ogg opengl openmp pam pango pcmcia pcre pdf png policykit posix ppds readline scanner sdl seccomp sound spell ssl startup-notification svg systemd test-rust tiff truetype udev udisks unicode upower usb vim-syntax vorbis vulkan wxwidgets x264 xattr xcb xft xml xv xvid zlib" ABI_X86="64" ADA_TARGET="gcc_12" APACHE2_MODULES="authn_core authz_core socache_shmcb unixd actions alias auth_basic authn_anon authn_dbm authn_file authz_dbm authz_groupfile authz_host authz_owner authz_user autoindex cache cgi cgid dav dav_fs dav_lock deflate dir env expires ext_filter file_cache filter headers include info log_config logio mime mime_magic negotiation rewrite setenvif speling status unique_id userdir usertrack vhost_alias" CALLIGRA_FEATURES="karbon sheets words" COLLECTD_PLUGINS="df interface irq load memory rrdtool swap syslog" CPU_FLAGS_X86="mmx mmxext sse sse2 aes avx pclmul popcnt sse3 sse4_1 sse4_2 ssse3" ELIBC="glibc" GPSD_PROTOCOLS="ashtech aivdm earthmate evermore fv18 garmin garmintxt gpsclock greis isync itrax mtk3301 ntrip navcom oceanserver oncore rtcm104v2 rtcm104v3 sirf skytraq superstar2 tsip tripmate tnt ublox" INPUT_DEVICES="libinput" KERNEL="linux" L10N="en fr" LCD_DEVICES="bayrad cfontz glk hd44780 lb216 lcdm001 mtxorb text" LUA_SINGLE_TARGET="lua5-1" LUA_TARGETS="lua5-1" OFFICE_IMPLEMENTATION="libreoffice" PHP_TARGETS="php8-1" POSTGRES_TARGETS="postgres15" PYTHON_SINGLE_TARGET="python3_11" PYTHON_TARGETS="python3_11" RUBY_TARGETS="ruby31" VIDEO_CARDS="nouveau" XTABLES_ADDONS="quota2 psd pknock lscan length2 ipv4options ipp2p iface geoip fuzzy condition tarpit sysrq proto logmark ipmark dhcpmac delude chaos account"
Unset: ADDR2LINE, AR, ARFLAGS, AS, ASFLAGS, CC, CCLD, CONFIG_SHELL, CPP, CPPFLAGS, CTARGET, CXX, CXXFILT, ELFEDIT, EMERGE_DEFAULT_OPTS, EXTRA_ECONF, F77FLAGS, FC, GCOV, GPROF, INSTALL_MASK, LC_ALL, LD, LFLAGS, LIBTOOL, LINGUAS, MAKE, MAKEFLAGS, NM, OBJCOPY, OBJDUMP, PORTAGE_BINHOST, PORTAGE_BUNZIP2_COMMAND, PORTAGE_COMPRESS, PORTAGE_COMPRESS_FLAGS, PORTAGE_RSYNC_EXTRA_OPTS, PYTHONPATH, RANLIB, READELF, RUSTFLAGS, SIZE, STRINGS, STRIP, YACC, YFLAGS

=================================================================
Package Settings
=================================================================

x11-wm/awesome-4.3-r103::gentoo was built with the following:
USE="dbus doc -gnome -test" ABI_X86="(64)" LUA_SINGLE_TARGET="lua5-1 -lua5-3 -luajit"
CFLAGS="-march=x86-64-v2 -O2 -pipe -mavx -mavx256-split-unaligned-store -mpclmul -mxsave -mxsaveopt"
CXXFLAGS="-march=x86-64-v2 -O2 -pipe -mavx -mavx256-split-unaligned-store -mpclmul -mxsave -mxsaveopt"
FEATURES="merge-sync xattr strict config-protect-if-modified parallel-fetch unknown-features-warn buildpkg distlocks fixlafiles assume-digests unmerge-logs usersync binpkg-dostrip preserve-libs usersandbox userpriv protect-owned network-sandbox ipc-sandbox unmerge-orphans binpkg-multi-instance binpkg-docompress pkgdir-index-trusted qa-unresolved-soname-deps pid-sandbox buildpkg-live multilib-strict userfetch binpkg-logs sandbox sfperms news ebuild-locks"

So far as I know, I do not do anything regarding options such as ccache or distcc, I guess it's safe to assume they are not implied.

Maybe I had to recompile glibc before anything else ? Will not run it without guidance, it'll first take heck of a time on this laptop so I would prefer to be asked to do so if possible, second I fear it'll break more stuff.

I'm wondering if, for this case, I could not ask Gentoo to recompile everything from client. Could take less that 10 hours I think, regarding the only big packages would be kernel and glibc I think. But that might be too much, I guess it's safer to assume there is a chunks to recompile, but not everything ?

Regards,
GASPARD DE RENEFORT Kévin
_________________
«Gentoo does not have problems, only learning opportunities.» - NeddySeagoon
«If your Gentoo installation isn't valuable to you, feel free to continue to ignore the instructions.» - figueroa

NeddySeagoon
Administrator

Joined: 05 Jul 2003
Posts: 54272
Location: 56N 3W

Posted: Tue Apr 16, 2024 10:25 am Post subject:

kgdrenefort,

Quote:

So far as I know, I do not do anything regarding options such as ccache or distcc, I guess it's safe to assume they are not implied.

They do not appear in FEATURES. So they are not in use.

It goes wrong here

Code:

[4/270] cd /var/tmp/portage/x11-wm/awesome-4.3-r103/work/awesome-4.3_build && /var/tmp/portage/x11-wm/awesome-4.3-r103/work/awesome-4.3/tests/examples/runner.sh /dev/null env -u LUA_PATH_5_1 -u LUA_PATH_5_2 -u LUA_PATH_5_3 "LUA_PATH=/var/tmp/portage/x11-wm/awesome-4.3-r103/work/awesome-4.3/tests/examples/shims/?.lua;/var/tmp/portage/x11-wm/awesome-4.3-r103/work/awesome-4.3/tests/examples/shims/?/init.lua;/var/tmp/portage/x11-wm/awesome-4.3-r103/work/awesome-4.3/tests/examples/shims/?;/var/tmp/portage/x11-wm/awesome-4.3-r103/work/awesome-4.3/lib/?.lua;/var/tmp/portage/x11-wm/awesome-4.3-r103/work/awesome-4.3/lib/?/init.lua;/var/tmp/portage/x11-wm/awesome-4.3-r103/work/awesome-4.3/lib/?;/var/tmp/portage/x11-wm/awesome-4.3-r103/work/awesome-4.3/themes/?.lua;/var/tmp/portage/x11-wm/awesome-4.3-r103/work/awesome-4.3/themes/?;" AWESOME_THEMES_PATH=/var/tmp/portage/x11-wm/awesome-4.3-r103/work/awesome-4.3/themes/ SOURCE_DIRECTORY=/var/tmp/portage/x11-wm/awesome-4.3-r103/work/awesome-4.3 lua /var/tmp/portage/x11-wm/awesome-4.3-r103/work/awesome-4.3/tests/examples/text/template.lua /var/tmp/portage/x11-wm/awesome-4.3-r103/work/awesome-4.3/tests/examples/text/awful/keygrabber/allowed_keys.lua /var/tmp/portage/x11-wm/awesome-4.3-r103/work/awesome-4.3_build/doc/images/AUTOGEN_text_awful_keygrabber_allowed_keys || true
/var/tmp/portage/x11-wm/awesome-4.3-r103/work/awesome-4.3/tests/examples/runner.sh: line 22: 62 Illegal instruction (core dumped) "$@" > ${file_stdout} 2> ${file_stderr}

Looking at the top of

/var/tmp/portage/x11-wm/awesome-4.3-r103/work/awesome-4.3/tests/examples/runner.sh:

#!/bin/sh
# Todo: Give this shell script a sane calling convention. Right now it has a
# file containing the expected output as first argument and just executes
# everything else.

set -ue

# Cleanup on errors / aborting
cleanup() {
rm -rf "$file_stderr" "$file_stdout" || true
}
trap "cleanup" 0 2 3 15

file_stdout=$(mktemp)
file_stderr=$(mktemp)

expected_output=$1
shift

# Run the command that we were given
exit_code=0
"$@" > ${file_stdout} 2> ${file_stderr} || exit_code=$? <--- Line 22

# If exit code is not zero or anything was produced on stderr...
if [ $exit_code -ne 0 -o -s "${file_stderr}" ]
then
echo "Result: ${exit_code}"
if [ -s "${file_stdout}" ]
then
echo "Output:"
cat "${file_stdout}"
fi
if [ -s "${file_stderr}" ]
then
echo "Error:"
cat "${file_stderr}"
fi
exit 1
fi

That's not useful to me as that's the run something and exit on error routine.
It's shell code too. You would notice if bash were broken, so the problem is with the something being run.

Post the content of /proc/cpuinfo and the output of resolve-march-native from the client.
You may need to install app-misc/resolve-march-native

Lets see how that stacks up with the clients

Code:

CPU_FLAGS_X86="mmx mmxext sse sse2 aes avx pclmul popcnt sse3 sse4_1 sse4_2 ssse3"

_________________
Regards,

NeddySeagoon

Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.

kgdrenefort
Apprentice

Joined: 19 Sep 2023
Posts: 186
Location: Somewhere in the 77

Posted: Tue Apr 16, 2024 11:18 am Post subject:

NeddySeagoon wrote:

kgdrenefort,

Quote:

So far as I know, I do not do anything regarding options such as ccache or distcc, I guess it's safe to assume they are not implied.

They do not appear in FEATURES. So they are not in use.

It goes wrong here

Code:

Looking at the top of

/var/tmp/portage/x11-wm/awesome-4.3-r103/work/awesome-4.3/tests/examples/runner.sh:

Code:

CPU_FLAGS_X86="mmx mmxext sse sse2 aes avx pclmul popcnt sse3 sse4_1 sse4_2 ssse3"

- /proc/cpuinfo (complete output, from client): https://bpa.st/6L2Q
- Flags for each CPU:

Code:

flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ht tm pbe syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc cpuid aperfmperf pni pclmulqdq dtes64 monitor ds_cpl smx est tm2 ssse3 cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic popcnt tsc_deadline_timer aes xsave avx lahf_lm epb pti xsaveopt dtherm ida arat pln pts

(I guess that was you were looking for)

From client:

Code:

satan ~ # resolve-march-native
-march=sandybridge -maes --param=l1-cache-line-size=64 --param=l1-cache-size=32 --param=l2-cache-size=8192

Regards,
GASPARD DE RENEFORT Kévin
_________________
«Gentoo does not have problems, only learning opportunities.» - NeddySeagoon
«If your Gentoo installation isn't valuable to you, feel free to continue to ignore the instructions.» - figueroa

Hu
Moderator

Joined: 06 Mar 2007
Posts: 21650

Posted: Tue Apr 16, 2024 3:02 pm Post subject:

kgdrenefort wrote:

Code:

[19/270] cd /var/tmp/portage/x11-wm/awesome-4.3-r103/work/awesome-4.3_build && /var/tmp/portage/x11-wm/awesome-4.3-r103/work/awesome-4.3/tests/examples/runner.sh /var/tmp/portage/x11-wm/awesome-4.3-r103/work/awesome-4.3/tests/examples/awful/mouse/coords.output.txt env -u LUA_PATH_5_1 -u LUA_PATH_5_2 -u LUA_PATH_5_3 "LUA_PATH=/var/tmp/portage/x11-wm/awesome-4.3-r103/work/awesome-4.3/tests/examples/shims/?.lua;/var/tmp/portage/x11-wm/awesome-4.3-r103/work/awesome-4.3/tests/examples/shims/?/init.lua;/var/tmp/portage/x11-wm/awesome-4.3-r103/work/awesome-4.3/tests/examples/shims/?;/var/tmp/portage/x11-wm/awesome-4.3-r103/work/awesome-4.3/lib/?.lua;/var/tmp/portage/x11-wm/awesome-4.3-r103/work/awesome-4.3/lib/?/init.lua;/var/tmp/portage/x11-wm/awesome-4.3-r103/work/awesome-4.3/lib/?;/var/tmp/portage/x11-wm/awesome-4.3-r103/work/awesome-4.3/themes/?.lua;/var/tmp/portage/x11-wm/awesome-4.3-r103/work/awesome-4.3/themes/?;" AWESOME_THEMES_PATH=/var/tmp/portage/x11-wm/awesome-4.3-r103/work/awesome-4.3/themes/ SOURCE_DIRECTORY=/var/tmp/portage/x11-wm/awesome-4.3-r103/work/awesome-4.3 lua /var/tmp/portage/x11-wm/awesome-4.3-r103/work/awesome-4.3/tests/examples/awful/template.lua /var/tmp/portage/x11-wm/awesome-4.3-r103/work/awesome-4.3/tests/examples/awful/mouse/coords.lua /var/tmp/portage/x11-wm/awesome-4.3-r103/work/awesome-4.3_build/doc/images/AUTOGEN_awful_mouse_coords || true
/var/tmp/portage/x11-wm/awesome-4.3-r103/work/awesome-4.3/tests/examples/runner.sh: line 22: 145 Illegal instruction (core dumped) "$@" > ${file_stdout} 2> ${file_stderr}

Where above there is an illegal instruction:

Code:

/var/tmp/portage/x11-wm/awesome-4.3-r103/work/awesome-4.3/tests/examples/runner.sh: line 22: 145 Illegal instruction (core dumped) "$@" > ${file_stdout} 2> ${file_stderr}

Building on the shell script that Neddy showed, we can say that "$@" caused the shell to run a program which crashed. We can tell from the shell script that this would start with running $2. We see from the build log that $2 would be env (presumably /usr/bin/env). However, we cannot say that env is broken, because it will execve the next stage, so env might be the guilty program or it might have run a guilty program. In the latter case, it looks like it would have run lua. Since that is an interpreter, we cannot say definitively that /usr/bin/lua is broken. It might have loaded an extension module (if Lua supports such things; many scripting languages do) that is broken. It might in turn have used execve to replace itself with yet another program, which is broken. Regardless, since a core dump is produced, inspecting the core dump in gdb will tell us which program crashed and which instruction the CPU rejected. This may help us understand both which program to rebuild and which compiler flags, if any, are allowing the build to use instructions you cannot use.

Earlier in the thread, there was a backtrace which plausibly blames lua5.1. You subsequently said you rebuilt it, but I wonder if your rebuild really did the right thing. What exactly did you run to rebuild lua? I see Lua as slotted, so you might have rebuilt the wrong slot. What is the output of lua -v ; emerge --verbose --info dev-lang/lua ; LC_ALL=C ls -ld /var/db/pkg/dev-lang/lua*?

pingtoo
l33t
l33t

Joined: 10 Sep 2021
Posts: 926
Location: Richmond Hill, Canada

Posted: Tue Apr 16, 2024 3:27 pm Post subject:

kgdrenefort wrote:

Hello,

If I understand, you wants me to rebuild lua packages and awesome as well.

These seems to have been rebuilt, from client, without any problem:

Code:

[IP-] [ ] app-eselect/eselect-lua-4-r1:0
[IP-] [ ] dev-lang/lua-5.1.5-r200:5.1
[IP-] [ ] dev-lang/luajit-2.1.0_beta3_p20220127-r2:2/2.1.0_beta3_p20220127
[IP-] [ ] dev-lua/luafilesystem-1.8.0-r101:0

I don't know how you concluded your lua binary is locally built, I can only take your word for it.
I checked on my machine that /usr/lib64/liblua5.1.so.0 came from dev-lang/lua

Code:

qfile /usr/lib64/liblua5.1.so.0
dev-lang/lua: /usr/lib64/liblua5.1.so.0

what we know so far,

X server is working
installed "awesome" binary not working, create error "illegal instruction"
try to rebuild x11-wm/awesome locally failed
rebuild x11-wm/awesome also failed with "illegal instruction"
in the process of rebuild, the build process call runner.sh which in turn call lua which give "illegal instruction"

So my conclusion is that "lua" binary on you client machine is for different CPU

I can only suggestion rebuild dev-lang/lua to test. I don't know anything else. So you may need someone else help.

NeddySeagoon
Administrator

Joined: 05 Jul 2003
Posts: 54272
Location: 56N 3W

Posted: Tue Apr 16, 2024 3:50 pm Post subject:

kgdrenefort

lua is slotted.

Code:

[U] dev-lang/lua
Available versions:
(5.1) 5.1.5-r200{tbz2}
(5.3) 5.3.6-r102
(5.4) 5.4.6
{+deprecated readline}
Installed versions: 5.1.5-r200(5.1){tbz2}(11:11:26 16/04/24)(deprecated readline)
Homepage: https://www.lua.org/
Description: A powerful light-weight programming language designed for extending applications

You need to rebuild slot 5.1, as that's the one in use.

Code:

emerge dev-lang/lua -1av

daes the wrong thing here.

Code:

$ emerge -1pv dev-lang/lua

These are the packages that would be merged, in order:
... done!
Dependency resolution took 3.33 s (backtrack: 0/20).

[ebuild NS ] dev-lang/lua-5.4.6:5.4::gentoo [5.1.5-r200:5.1::gentoo] USE="deprecated readline" 0 KiB

Total: 1 package (1 in new slot), Size of downloads: 0 KiB

That would build slot 5.4, which will install but not be used.

You must give the slot in the emerge command.

Code:

$ emerge -1av dev-lang/lua:5.1

_________________
Regards,

NeddySeagoon

Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.

kgdrenefort
Apprentice

Joined: 19 Sep 2023
Posts: 186
Location: Somewhere in the 77

Posted: Wed Apr 17, 2024 12:10 pm Post subject:

Hu wrote:

What is the output of lua -v ; emerge --verbose --info dev-lang/lua ; LC_ALL=C ls -ld /var/db/pkg/dev-lang/lua*?

https://bpa.st/3JYQ

Hu wrote:

Earlier in the thread, there was a backtrace which plausibly blames lua5.1. You subsequently said you rebuilt it, but I wonder if your rebuild really did the right thing. What exactly did you run to rebuild lua?

pingtoo wrote:

I don't know how you concluded your lua binary is locally built, I can only take your word for it.

To achieve what I think was a localy builded lua was these commands:

Code:

emerge --ask app-eselect/eselect-lua dev-lang/lua dev-lang/luajit dev-lua/luafilesystem

After removing parameters from make.conf to ask for the build of the binhost:

Code:

### Binary package settings (client) ###
#EMERGE_DEFAULT_OPTS="${EMERGE_DEFAULT_OPTS} --getbinpkg"
#FEATURES="getbinpkg"
#EMERGE_DEFAULT_OPTS="${EMERGE_DEFAULT_OPTS} --usepkg-exclude 'sys-kernel/gentoo-sources virtual/* www-servers/lighttpd'"
#PORTAGE_BINHOST="http://192.168.1.103:81/packages"

It has showed me it was build, not binary. I did not spotted any errors while doing this.

Hu wrote:

I see Lua as slotted, so you might have rebuilt the wrong slot.

Very possible, since I do not understand properly the slots in Gentoo.

NeddySeagoon wrote:

You must give the slot in the emerge command.

Code:

$ emerge -1av dev-lang/lua:5.1

To check that I used eix:

Code:

satan ~ # eix -e dev-lang/lua
[I] dev-lang/lua
Available versions:
(5.1) 5.1.5-r200{gpkg}
(5.3) 5.3.6-r102
(5.4) 5.4.6
{+deprecated readline}
Installed versions: 5.1.5-r200(5.1){gpkg}(06:36:44 PM 04/08/2024)(deprecated readline) 5.4.6(5.4)(10:06:48 AM 04/16/2024)(deprecated readline)
Homepage: https://www.lua.org/

After I ran your command:

Code:

emerge -1av dev-lang/lua:5.1

It compiled dev-lang/lua-5.1.5-r200, but the last output above seems to stay on the gpkg package, so the failed build of the binhost ? Just in case, because it cost nothing and I do not have time to check right now (merely to answer here) I rebooted, thinking maybe it will avoid me to manually change slot (pure guessing from me), but eix return the same.

Funny story: Just in case, I tried startx.

It works !

First of all, thank you. It was if I understand my Gentoo keeping the wrong lua in use, keeping the 5.1 slot which was a failure from me.

Now, because this is sadly not over, I have to find out why it failed, while all other packages seems to be working.

Does it needs another topic ?

Regards,
GASPARD DE RENEFORT Kévin
_________________
«Gentoo does not have problems, only learning opportunities.» - NeddySeagoon
«If your Gentoo installation isn't valuable to you, feel free to continue to ignore the instructions.» - figueroa

pingtoo
l33t
l33t

Joined: 10 Sep 2021
Posts: 926
Location: Richmond Hill, Canada

Posted: Wed Apr 17, 2024 1:56 pm Post subject:

kgdrenefort,

It is due to "awesome" binary were dynamically linked with liblua5.1.so.0. Since the new local build produced the correct instruction set for your client CPU.

I think if you try to rebuild x11-wm/awesome locally on your client, it should no longer run into the runner.sh error anymore.

Not sure if you notice, your output from Hu's suggestion at the top

Code:

kgdrenefort@satan ~ $ lua -v ; emerge --verbose --info dev-lang/lua ; LC_ALL=C ls -ld /var/db/pkg/dev-lang/lua*
Illegal instruction (core dumped)
Portage 3.0.61 (python 3.11.8-final-0, default/linux/amd64/23.0/desktop/systemd, gcc-13, glibc-2.38-r11, 6.6.21-gentoo-dist x86_64)
=================================================================
System Settings
=================================================================
System uname: Linux-6.6.21-gentoo-dist-x86_64-Intel-R-_Core-TM-_i7-2820QM_CPU_@_2.30GHz-with-glibc2.38
KiB Mem: 3958716 total, 3634488 free
KiB Swap: 4194300 total, 4194300 free
Timestamp of repository gentoo: Fri, 12 Apr 2024 10:30:00 +0000
Head commit of repository gentoo: 767b1858b6e42a550309b1daff116f1dda1ba4f4
sh bash 5.1_p16-r6
...

The "lua -v" did not produce output instead it also core dump with "Illegal instruction".
And at bottom

Code:

drwxr-xr-x 2 root root 4096 Apr 10 01:20 /var/db/pkg/dev-lang/lua-5.1.5-r200
drwxr-xr-x 2 root root 4096 Apr 16 10:06 /var/db/pkg/dev-lang/lua-5.4.6
drwxr-xr-x 2 root root 4096 Apr 16 10:06 /var/db/pkg/dev-lang/luajit-2.1.0_beta3_p20220127-r2

It show you have two version of dev-lang/lua and on Apr 16 you build lua-5.4.6

pingtoo
l33t
l33t

Joined: 10 Sep 2021
Posts: 926
Location: Richmond Hill, Canada

Posted: Wed Apr 17, 2024 2:11 pm Post subject:

kgdrenefort,

kgdrenefort, wrote:

Now, because this is sadly not over, I have to find out why it failed,

The reason is you client CPU is not exactly same as your build server CPU. I think you should open a new thread if you need further discussion on build server setup. However I suggest you search Gentoo's forums and Gentoo wiki, there are many discussion/topic about build server for multiple client machine.

As for

Quote:

To check that I used eix:

Code:

After I ran your command:

Code:

emerge -1av dev-lang/lua:5.1

Did you update eix database?

Code:

eix-update

prior to this check?

kgdrenefort
Apprentice

Joined: 19 Sep 2023
Posts: 186
Location: Somewhere in the 77

Posted: Wed Apr 17, 2024 2:18 pm Post subject:

pingtoo wrote:

kgdrenefort,

kgdrenefort, wrote:

Now, because this is sadly not over, I have to find out why it failed,

Quote:

To check that I used eix:

Code:

I did it after installing it, and I just did it after reading your comment.

Output is :

Code:

satan ~ # eix -e dev-lang/lua
[I] dev-lang/lua
Available versions:
(5.1) 5.1.5-r200{gpkg}
(5.3) 5.3.6-r102
(5.4) 5.4.6
{+deprecated readline}
Installed versions: 5.1.5-r200(5.1){gpkg}(01:57:39 PM 04/17/2024)(deprecated readline) 5.4.6(5.4)(10:06:48 AM 04/16/2024)(deprecated readline)
Homepage: https://www.lua.org/
Description: A powerful light-weight programming language designed for extending application

After I ran your command:

Code:

emerge -1av dev-lang/lua:5.1

Did you update eix database?

Code:

eix-update

prior to this check?

I think I'll open another topic for this matter.

Thanks for your time, almost a week to get awesome starting… Pheeew.

Regards,
GASPARD DE RENEFORT Kévin
_________________
«Gentoo does not have problems, only learning opportunities.» - NeddySeagoon
«If your Gentoo installation isn't valuable to you, feel free to continue to ignore the instructions.» - figueroa

NeddySeagoon
Administrator

Joined: 05 Jul 2003
Posts: 54272
Location: 56N 3W

Posted: Wed Apr 17, 2024 6:03 pm Post subject:

kgdrenefort,

Code:

emerge --ask app-eselect/eselect-lua dev-lang/lua dev-lang/luajit dev-lua/luafilesystem

builds the wrong version of lua

Code:

[ebuild R ] dev-lang/luajit-2.1.0_beta3_p20220613:2/2.1.0_beta3_p20220613::gentoo USE="-lua52compat -static-libs" 0 KiB
[ebuild R ] app-eselect/eselect-lua-4-r1::gentoo 0 KiB
[ebuild NS ] dev-lang/lua-5.4.6:5.4::gentoo [5.1.5-r200:5.1::gentoo] USE="deprecated readline" 0 KiB
[ebuild N ] dev-lua/luafilesystem-1.8.0-r101::gentoo USE="-test" LUA_TARGETS="lua5-1 -lua5-3 -lua5-4 -luajit" 0 KiB

That's slot 5.4 but awesome needs slot 5.1.

'Stotting' is Gentoos way of having several versions of a package installed at the same time. When you (re)build a slotted package, you need to take care that your build the slot you actually need.
The warning is

Code:

[ebuild NS ] dev-lang/lua-5.4.6:5.4::gentoo

N==New
S==Slot.
_________________
Regards,

NeddySeagoon

Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.

Display posts from previous:

	Gentoo Forums Forum Index Desktop Environments	All times are GMT Goto page Previous 1, 2
Page 2 of 2

Jump to:

You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum

Copyright 2001-2024 Gentoo Foundation, Inc. Designed by Kyle Manna © 2003; Style derived from original subSilver theme. | Hosting by Gossamer Threads Inc. © | Powered by phpBB 2.0.23-gentoo-p11 © 2001, 2002 phpBB Group
Privacy Policy