Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 41144 - XFree-4.3.0-r4 won't start - server aborts with signal 4
Summary: XFree-4.3.0-r4 won't start - server aborts with signal 4
Status: RESOLVED INVALID
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: New packages (show other bugs)
Hardware: x86 Linux
: High major (vote)
Assignee: Gentoo X packagers
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-02-10 11:48 UTC by Daniel Rendall
Modified: 2004-02-12 00:09 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments
XFree86 log showing crash (XFree86.8.log,37.06 KB, text/plain)
2004-02-10 11:50 UTC, Daniel Rendall
Details
XF86config file (XF86Config,15.08 KB, text/plain)
2004-02-10 11:52 UTC, Daniel Rendall
Details
A different XF86config file (XF86Config.new,2.77 KB, text/plain)
2004-02-11 12:03 UTC, Daniel Rendall
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Daniel Rendall 2004-02-10 11:48:28 UTC
I upgraded XFree-4.3.0-r3 to XFree-4.3.0-r4 via an 'emerge -u world'. Emerge completed successfully, I ran etc-update and updated all the config files. Having done this, the server refused to start with 'startx', and the console messages end:
   *** If unresolved symbols were reported above, they might not
   *** be the reason for the server aborting.

Fatal server error:
Caught signal 4.  Server aborting

My XF86config hasn't changed. Rebooting the machine and retrying didn't make a difference.

I downgraded back to -r3 and everything worked fine.

Reproducible: Always
Steps to Reproduce:
1. emerge XFree86-4.3.0-r4 (upgrade from -r3)
2. startx

Actual Results:  
Server aborts with signal 4 (SIGILL) 

Expected Results:  
Started X 

Portage 2.0.50 (default-x86-1.4, gcc-3.3.2, glibc-2.3.2-r9, 2.6.1) 
================================================================= 
System uname: 2.6.1 i686 AMD Athlon(tm) processor 
Gentoo Base System version 1.4.3.13 
distcc 2.11.1 i686-pc-linux-gnu (protocols 1 and 2) (default port 3632) 
[disabled] 
ccache version 2.3 [enabled] 
Autoconf: sys-devel/autoconf-2.58 
Automake: sys-devel/automake-1.7.7 
ACCEPT_KEYWORDS="x86" 
AUTOCLEAN="yes" 
CFLAGS="-march=athlon -O3 -pipe" 
CHOST="i686-pc-linux-gnu" 
COMPILER="gcc3" 
CONFIG_PROTECT="/etc /usr/X11R6/lib/X11/xkb /usr/kde/2/share/config /usr/kde/3.1/share/config /usr/kde/3.2/share/config /usr/kde/3/share/config /usr/share/config /usr/share/texmf/tex/generic/config/ /usr/share/texmf/tex/platex/config/ /var/qmail/control" 
CONFIG_PROTECT_MASK="/etc/gconf /etc/env.d" 
CXXFLAGS="-march=athlon -O3 -pipe" 
DISTDIR="/usr/portage/distfiles" 
FEATURES="autoaddcvs ccache sandbox" 
GENTOO_MIRRORS="http://gentoo.oregonstate.edu 
http://distro.ibiblio.org/pub/Linux/distributions/gentoo" 
MAKEOPTS="-j6" 
PKGDIR="/usr/portage/packages" 
PORTAGE_TMPDIR="/data/portage" 
PORTDIR="/usr/portage" 
PORTDIR_OVERLAY="" 
SYNC="rsync://rsync.gentoo.org/gentoo-portage" 
USE="X alsa apm arts avi cdr crypt cups dga dvd encode esd foomaticdb gif 
gphoto2 gpm gtk2 guile java jpeg kde ladcca libg++ libwww mad motif mozilla 
mpeg ncurses oggvorbis opengl oss pam pdflib perl png python qt quicktime 
rage128 readline samba scanner spell ssl svga tcpd tetex tiff truetype x86 
xml2 xmms zlib"
Comment 1 Daniel Rendall 2004-02-10 11:50:41 UTC
Created attachment 25353 [details]
XFree86 log showing crash
Comment 2 Daniel Rendall 2004-02-10 11:52:14 UTC
Created attachment 25354 [details]
XF86config file

XF86config that I use. This works fine with xfree-4.3.0-r3, but -r4 crashes
with signal 4.
Comment 3 Donnie Berkholz (RETIRED) gentoo-dev 2004-02-11 10:55:47 UTC
Daniel, thanks for the excellent information. I'm going to hazard a guess it's a problem with the mouse in some way, since that's the last thing in the log, but I'll have to run a diff between -r3 and -r4 and take a look at it.

I do find it interesting that it's initializing Mouse0, but you only have Mouse1 set up in XF86Config's server layout. Do you have an /etc/X11/XF86Config-4 that could be taking precedence?
Comment 4 Daniel Rendall 2004-02-11 12:03:58 UTC
Created attachment 25427 [details]
A different XF86config file

Sorry, I think this might have been the actual XF86config it was using...
Comment 5 Daniel Rendall 2004-02-11 12:13:31 UTC
OK, my fault... I think that the log which I attached resulted from using the xf86cfg command which I tried after noticing that startx didn't work. I've attached the XF86config file which was automatically generated in ~root/.

Sorry about the confusion - I had the idea of filing the bug report once I'd got back to the working -r3 version by which time I'd forgotten some of the details. To reiterate (as far as I can remember):

After upgrading, startx bombed out with signal 4 using the XF86config file I originally attached. The relevant logfile appears to have been overwritten.

Moving the original XF86config file out of the way and running xf86cfg resulted in an automatically generated config file (just attached) and crashed in the same way (as far as I can tell) with the log file that's attached.

I'm happy to have a go at re-emerging -r4 and doing some tests, but you'd have to tell me what to try. Is there some cunning way I could build -r4 and -r3 as binary packages so that I can switch between them without having to recompile?
Comment 6 Donnie Berkholz (RETIRED) gentoo-dev 2004-02-11 13:46:57 UTC
I can't do anything further without a relevant log file and XF86Config. Make sure both are attached. Preferably logs for both the -r3 and -r4 cases, using the same (working) XF86Config.

And yes: when you have the correct package emerged, `quickpkg xfree` will build a binary in ${PORTDOR}/packages/All/. You then remerge using `emerge -k =xfree-4.3.0-r${REVISION}`.
Comment 7 Donnie Berkholz (RETIRED) gentoo-dev 2004-02-11 13:47:38 UTC
s/PORTDOR/PORTDIR, probably /usr/portage unless you changed it.
Comment 8 Daniel Rendall 2004-02-12 00:09:52 UTC
Recompiled -r4, rebooted and now it appears to work. It definitely didn't last time, but maybe there was some kind of compiler glitch (although the merge appeared to finish successfully).

Sorry about that. If I can reproduce the problem I'll reopen the bug but for now I'll assume that it's fine.