I emerged kde-3.2.0_beta1 some time ago. There was clearly a problem (see below). I decided to wait for the final release.
Then beta2 came out. I decided to give it a try. Again the same problem:
* no programs can be started (dblclick on an icon, while bttn-down icon disappears, bttn-up: screen flashes, nothing else happens)
* start menu has black background: black letters on black background. (now that I think about it, probably start menu is just transparent, I have a black desktop background, couldn't change that because control center wouldn't start).
* start menu crashes when I browse through it ("kicker crashed, crashhandler started). start menu (and panel and taskbar and everything except desktop and icons) comes back after the first crash, but if you do the whole thing again, then the start menu doesn't restart anymore. left click on the desktop gives menu -> run command -> kicker gives you the start menu (etc...) back
* maybe related problem: k3b under kde3.1.4 gives also transparent menu's and crashes then. maybe the problem is in some library that both kicker and k3b use...
OK, crashhandler didn't give much info, so I decided to recompile with different CFLAGS and with USE="debug" (shouldn't make a difference for the kde ebuild, debug isn't used anywhere, but I didn't know that at that time, see bug 35628). Problem was gone!
Thought that the problem were the CFLAGS, so rebuilt kde without the USE="debug" and with the reduced CFLAGS. Problem was there again. Rebuilt kde with exactly the same command line, but now with USE="debug". Problem is gone!
Clearly USE="debug" does something that makes kde run on my machine. Question is what? And why doesn't it work without USE="debug"?
Steps to Reproduce:
1. emerge =kde-base/kdebase-3.2.0_beta2; emerge =kde-base/kdelibs-3.2.0_beta2
2. start kde, dblclick on some program icon on the desktop, nothing happens
3. USE="debug" emerge =kde-base/kdebase-3.2.0_beta2; USE="debug" emerge =kde-base/kdelibs-3.2.0_beta2
4. start kde, dblclick on some program icon on the desktop, program starts as expected
Icon disappears if you keep the mouse bttn down after the second click, screen
flashes when bttn released (screen is redrawn, I guess, maybe some program
Should have started the program without problems (duh)
Portage 2.0.49-r18 (default-x86-1.4, gcc-3.3.2, glibc-2.3.2-r9, 2.4.23)
System uname: 2.4.23 i686 Intel(R) Pentium(R) 4 CPU 2.60GHz
Gentoo Base System version 220.127.116.11
ccache version 2.3 [enabled]
CFLAGS="-march=pentium3 -mcpu=pentium3 -mmmx -msse -msse2 -O2
-fomit-frame-pointer -mfpmath=sse -pipe"
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/texmf/tex/platex/config/ /usr/share/texmf/xdvi/ /var/qmail/control"
CXXFLAGS="-march=pentium3 -mcpu=pentium3 -mmmx -msse -msse2 -O2
-fomit-frame-pointer -mfpmath=sse -pipe"
FEATURES="autoaddcvs ccache distcc sandbox userpriv"
USE="3dfx 3dnow X X509 Xaw3d aalib acl acpi alsa altivec apache2 apm arts
artswrappersuid avi berkdb cdr crypt cscope cups curl dga directfb dnd doc dv
dvb dvd emacs emacs-w3 encode esd evo faad fastcgi fbcon foomaticdb
foreign-package foreign-sysvinit gb gdbm ggi gif gnome gphoto2 gpm gtk gtk2 imap
libwww mad maildir mbox mcal md5sum memlimit mikmod mmx motif mozaccess
mozcalendar mozctl mozilla mozinterfaceinfo mozp3p mozsvg mozxmlterm mpeg mpi
mule mysql nas ncurses nls nocd objc oci8 odbc offensive oggvorbis opengl pam
parse-clocks pdflib perl pic plotutils png postgres ppds prelude python qt
quicktime readline samba sasl scanner sdl skey slang slp snmp socks5 spell sse
ssl stencil-buffer svga tcltk tcpd tetex threads tiff truetype usb vim-with-x
wmf wxwindows x86 xinerama xml2 xmms xosd xv zeo zlib"
It's probably still a result of your use flags, but the debug may trigger something internal to gcc that is reflecting differently. Unfortunately there's no way I can think of to diagnose your problem other than to say that if you keep rather clean use flags and reemerged without debug it should work fine.
sounds like something else is going on - nobody else seems to have these problems. i don't think it will be possible to really diagnose the problem.