Qt applications on amd64 appear to hang for me. They start fine, draw their windows, but then I can't do anything with them. In particular, I tried designer (comes with qt) and psi. With psi, I can start an action, but the connection to the server is never established, the star is cycling and after that the window won't even close when I tell the window manager to close it. designer opens fine and then does not react when I click anywhere. I guess it might be that a qt-internal signalling issue with their signal-slot stuff? Reproducible: Always Steps to Reproduce: 1. start qt application 2. try to do anything with it Actual Results: hang Expected Results: work Portage 2.0.51-r15 (default-linux/amd64/2004.3, gcc-3.4.3, glibc-2.3.4.20041102-r0, 2.6.10-gentoo-r6 x86_64) ================================================================= System uname: 2.6.10-gentoo-r6 x86_64 unknown Gentoo Base System version 1.6.8 Python: dev-lang/python-2.3.4 [2.3.4 (#1, Jan 25 2005, 20:31:46)] dev-lang/python: 2.3.4 sys-devel/autoconf: 2.59-r6, 2.13 sys-devel/automake: 1.5, 1.8.5-r2, 1.6.3, 1.7.9, 1.4_p6, 1.9.4 sys-devel/binutils: 2.15.92.0.2-r2 sys-devel/libtool: 1.5.10-r3 virtual/os-headers: 2.6.8.1-r3 ACCEPT_KEYWORDS="amd64 ~amd64" AUTOCLEAN="yes" CFLAGS="-pipe -Os" CHOST="x86_64-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3/share/config /usr/lib/X11/xkb /usr/share/config /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-O2 -pipe" DISTDIR="/usr/portage/distfiles" FEATURES="autoaddcvs autoconfig ccache distlocks notitles sandbox userpriv usersandbox" GENTOO_MIRRORS="http://pandemonium.tiscali.de/pub/gentoo/ http://ftp.uni-erlangen.de/pub/mirrors/gentoo" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" SYNC="rsync://rsync.de.gentoo.org/gentoo-portage" USE="amd64 X aac acpi alsa berkdb bitmap-fonts bzlib cdb cdr crypt dvb dvd dvdr encode exif f77 flac font-server fortran ftp gif gmp gpm gtk gtk2 gtkhtml ipv6 jabber jp2 jpeg lzw lzw-tiff mad maildir mmap mozilla multilib ncurses netboot nptl nptlonly offensive ogg oggvorbis opengl oss pam png posix qt readline slang sockets speex spell ssl theora tiff truetype truetype-fonts type1-fonts usb userlocales xml2 xpm xrandr xv xvid zlib" Unset: ASFLAGS, CBUILD, CTARGET, LDFLAGS, PORTDIR_OVERLAY
I just tested running a qt application from my notebook via $DISPLAY set to my amd64 host, and it hangs the same way as when run locally. So it is apparently not a 64-bit issue in qt or a amd64 compiler bug.
I am unable to reproduce this error. Please upgrade to the latest stable versions and confirm whether you are still encountering these issues.
I am still encountering these issues. Running psi locally does not work. Running psi on my 32-bit notebook with $DISPLAY pointing to my local display causes psi to hang. Running psi locally with $DISPLAY pointing to my notebook works. So it's not Qt, it's X. * x11-base/xorg-x11 Latest version available: 6.8.2 Latest version installed: 6.8.2 * media-video/nvidia-glx Latest version available: 1.0.6629-r5 Latest version installed: 1.0.6629-r5 * media-video/nvidia-kernel Latest version available: 1.0.6629-r3 Latest version installed: 1.0.6629-r3
You have CFLAGS="-pipe -Os" in your emerge info. -Os has been known to cause issues on the amd64 architecture, and specifically with KDE/Qt. Is your whole system compiled with these FLAGS? I would recommend compiling at least xorg-x11 and qt/KDE stuff with -O1/-O2, or even no -Ox specified. I cannot reproduce this error, and would guess it is due to your use of -Os. GCC/glibc could or any other linked lib could possibly cause this issue too.
Please refer to the warning in the AMD64 technotes - -Os causes problems. emerge -e world with safer CFLAGS/CXXFLAGS. http://www.gentoo.org/proj/en/base/amd64/technotes/index.xml?part=1&chap=3
The technote warning is obsolete. The technote says -Os may prevent kde from compiling. This is no longer the case. I recompiled glibc and X with -O2 instead of -Os. It is now bigger and slower and has the exact same problem as before. Sir, if you don't know, then don't touch the bug. But marking it invalid on a whim is so childish, it makes my younger son look mature in comparison. Please note that Qt and KDE work when running on amd64 and $DISPLAY points to my i386 notebook. So I'm not recompiling Qt and KDE. Please don't suggest any more shots in the dark. I already tried all the wild guesses.
Please don't suggest a developer with lots of experience is being childish. He suggested you try the 'tried and tested' route to see if it is indeed your setup causing the problems - if you want support, which I should point out you don't pay said developer for, don't be so abrasive about the matter and either politely rebuke a suggested route or perhaps try it. Until you're willing to do that, this bug is closed.
Anyone who uses -O<larger than 2> or -Os better realize the consequences of those actions. Please work with the gcc developers upstream to resolve these compiler problems.
which part of "I tried it and it did not help" did you not understand?
Is there any point reopening the bug again? You've had several developers for AMD64 say its not a problem we're willing to look into diagnosing and fixing, as far as we're concerned you're not running a supported configuration and have explicitly setup your system contrary to the 'suggested' methods in our manual/technotes. The views taken by cryos and myself towards this matter are sanctioned by Gentoo/AMD64 project leads (Kugelfang, Kingtaco) and everyone else who works on this small part of Gentoo. If any fixing is to be done its upstream work by GCC, if you wish to take this matter up with them, please feel free.
Hi Felix, I tested the following cases: running designer on amd64, display on iBook: works (Qt) running designer on iBook, display on amd64: works (Qt) running kile on amd64, display on iBook: works (Qt, KDE) running kile on amd64, display on iBook: works (Qt, KDE) running anjuta on amd64, display on iBook: works (gtk) running anjuta on amd64, display on iBook: works (gtk) running xterm on amd64, display on iBook: works (good ol' X11) running xterm on amd64, display on iBook: works (good ol' X11) If you really want to get rid of your problem, _please_ remerge your complete system using sane CFLAGS. Again FYI: "-Os" is no sane CFLAG on amd64, neither for compiling xorg-x11 nor for any other package in Gentoo. WONTFIX is obviously the wrong resolution, but I won't touch this BUG anymore until you can show us, that your particular problem still arises with a recompiled system using sane CFLAGS. (emerge -e world) Also: Please don't refer to our developers as "childish" in future, especially not, when they don't behave childish. Marking this BUG as INVALID follows our policy on BUGs that show insane CFLAGS. (This policy also applies to packages that aren't in the portage tree or things like using unsupported kernels) Kind regards, Danny
you said you did re-emerge the affected packages. however, we were asking you to re-emerge all packages that were compiled with -Os with sane CFLAGS. btw, i think i don't have to tell you how to behave, but please always keep in mind that there is always a human on the other side. beeing rude will surely not help us.
It turns out that this only happens under fvwm. Using psi and qt/kde applications with kwm works fine. So apparently X is innocent and so is Qt. * x11-wm/fvwm Latest version available: 2.5.12 Latest version installed: 2.5.12
no activity for 1.5 months, closing. please reopen if this is still an issue.
I have same problem here (applications: skype and camstream) I guess this is the same bug as 84387 - qt with fvwm placing windows outside the desktop
Still a problem here... Running: x11-wm/fvwm-2.5.12 x11-libs/qt-3.3.4-r5 Emerge info: Portage 2.0.51.22-r1 (default-linux/amd64/2005.0, gcc-3.4.4, glibc-2.3.5-r0, 2.6.12-gentoo-r3 x86_64) ================================================================= System uname: 2.6.12-gentoo-r3 x86_64 AMD Athlon(tm) 64 Processor 3000+ Gentoo Base System version 1.6.12 dev-lang/python: 2.4.1-r1 sys-apps/sandbox: 1.2.9 sys-devel/autoconf: 2.13, 2.59-r7 sys-devel/automake: 1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.5 sys-devel/binutils: 2.16.1 sys-devel/libtool: 1.5.18-r1 virtual/os-headers: 2.6.11-r2 ACCEPT_KEYWORDS="amd64 ~amd64" AUTOCLEAN="yes" CBUILD="x86_64-pc-linux-gnu" CFLAGS="-march=k8 -O2 -pipe" CHOST="x86_64-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3.4/env /usr/kde/3.4/share/config /usr/kde/3.4/shutdown /usr/kde/3/share/config /usr/lib/X11/xkb /usr/share/config /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/texmf/web2c /etc/env.d" CXXFLAGS="-march=k8 -O2 -pipe" DISTDIR="/usr/portage/distfiles" FEATURES="autoconfig distlocks sandbox sfperms strict" GENTOO_MIRRORS="ftp://ftp.du.se/pub/os/gentoo http://ds.thn.htu.se/linux/gentoo ftp://mirror.pudas.net/gentoo" LANG="en_US.iso885915" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/local/portage" SYNC="rsync://rsync.europe.gentoo.org/gentoo-portage" USE="amd64 X acpi alsa apache2 avi berkdb bitmap-fonts bzip2 cdr crypt curl dbus dvd dvdr encode fam flac ftp gnome gpm gstreamer gtk gtk2 hal icq imagemagick imap imlib ipv6 jabber javascript jp2 jpeg kde kdeenablefinal libwww lm_sensors lzw lzw-tiff mad maildir mailwrapper matroska mime mp3 mpeg ncurses nls nptl nptlonly nvidia offensive ogg opengl oscar pam pdflib png postgres python qt readline samba sdl slang spell ssl tcpd tetex threads tiff truetype truetype-fonts type1-fonts usb userlocales vcd vhosts vorbis xine xinerama xml2 xrandr xv xvid zlib userland_GNU kernel_linux elibc_glibc" Unset: ASFLAGS, CTARGET, LC_ALL, LDFLAGS, LINGUAS
reopening per comment 16
This mail seems to describe the problem this bug brings up: http://article.gmane.org/gmane.compw.window-managers.windowmaker.devel/749 Even though it's to a windowmaker specific mailing list the mail still mensions fvwm.
Moving to bug 84387 *** This bug has been marked as a duplicate of 84387 ***
