When I'm using Icewm, and amsn, I go to the preferences menu of amsn, and then, the mouse and the keyboard keep freezed, and all apps too. Another way to reproduce is running Psi. When I try to acces to the options menu, and I navigate throughout the tabs, It freezes misteriously. I've experienced another way to reproduce the hang: When I'm using fontforge, and I try to select to 'Point' menu, an option called 'Tangent'. When I'm using Gnome, I go to the Key shortcuts preferences, and the X crashes, giving a signal 11 (from /var/log/X.log.0). I'm trying to investigate If I can access to the system through ssh, or If freezes in Gnome, reproducing the same with amsn, psi or fontforge. Reproducible: Always Steps to Reproduce: * All in Icewm 1. Execute amsn 2. Go to preferences menu 3. all it freezes. (the keyboard, the mouse, everything.) --- Another way --- 1. Execute Psi. 2. Go to Options dialog, and navigate through it. 3. It will freeze misteriously. Actual Results: The same as described before. Expected Results: Have an stable X. No hangs, no crashes.
Here some useful information: x11-xorg 6.7.99.90 Portage 2.0.50-r10 (gcc34-x86-2004.2, gcc-3.4.1, glibc-2.3.4.20040808-r0, 2.6.8.1) ================================================================= System uname: 2.6.8.1 i686 Intel(R) Pentium(R) 4 CPU 1400MHz Gentoo Base System version 1.5.3 Autoconf: sys-devel/autoconf-2.59-r4 Automake: sys-devel/automake-1.8.5-r1 ACCEPT_KEYWORDS="x86 ~x86" AUTOCLEAN="yes" CFLAGS="-O3 -march=pentium4 -fomit-frame-pointer -pipe -maccumulate-outgoing-args -fforce-addr -falign-f unctions=4 -ffast-math -msse" CHOST="i686-pc-linux-gnu" COMPILER="" CONFIG_PROTECT="/etc /usr/X11R6/lib/X11/xkb /usr/kde/2/share/config /usr/kde/3/share/config /usr/lib/moz illa/defaults/pref /usr/share/config /usr/share/texmf/dvipdfm/config/ /usr/share/texmf/dvips/config/ /us r/share/texmf/tex/generic/config/ /usr/share/texmf/tex/platex/config/ /usr/share/texmf/xdvi/ /var/qmail/ control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-O3 -march=pentium4 -fomit-frame-pointer -pipe -maccumulate-outgoing-args -fforce-addr -falign -functions=4 -ffast-math -msse" DISTDIR="/usr/portage/distfiles" FEATURES="autoaddcvs sandbox" GENTOO_MIRRORS="http://gentoo.osuosl.org http://distro.ibiblio.org/pub/Linux/distributions/gentoo" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/local/portage" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="X aalib acpi alsa apache2 avi berkdb bidi bitmap-fonts canna caps cdr cjk crypt cups dga directfb d ivx4linux dts dvd dvdread encode esd f77 fbcon fbdev foomaticdb gcj gdbm gif gimpprint gnome gpm gstream er gtk gtk2 gtkhtml imlib ipv6 jack java javascript jpeg libcaca libg++ libwww live lzo mad maildir mbox mikmod mng motif mozilla moznocompose moznoirc moznomail moznoxft mozsvg mozxmlterm mpeg nas ncurses ne t nethack network nls nptl objc oggvorbis opengl oss pam pdflib perl png python qt quicktime readline rt c sdl silverxp slang slp snmp socks5 spell sse sse2 ssl svg svga tcltk tcpd tetex tga theora tiff truety pe type1 unicode usb v4l v4l2 vanilla videos wmf x86 xml2 xmms xprint xv xvid xvmc zlib"
Here some useful information: x11-xorg 6.7.99.90 ^^^^ what version exactly?
Sorry, I've pasted too quickly :-P I'm using x11-xorg 6.7.99.904 But I've encountered the cause: the line "module glx" in xorg.conf This bug is already reported to bugs.freedesktop.org. Sorry :-) That's the bug #1281 in freedesktop bugzilla.
are you sure you mean bug 1281 on the fdo bugzilla?? can you give us a more accurate bug # please
When you compile X with the -O3 optimization you may experience mysterious errors in several applications. Re-emerge X using the -O2 optimization. To put it bluntly do not compile x11-xorg with -O3 optimization, it is unsafe.
http://freedesktop.org/bugzilla/show_bug.cgi?id=1281 cannot be the right bug. Cristian, could you provide us with the correct bug number so we can post it here? Marking this bug as resolved in anticipation of the correct link, since Cristian indicated his problem is fixed. Cristian, please re-open this bug if your issue is not in fact solved.
Resolving this as needinfo as only a workaround was found, and we don't know the upstream bug.
Anyone who has the correct bug # or any other relevent info can give this a better resolution.
actually what they should do is file a bug against Xorg in fd.o bugzilla with the backtrace from their log.
