This made me went crasy upgraded Gnome 2.? to 2.4 (I never checked the version just before... 2.2?) everything was working fine I emerge unmerge asla-lib reboot can't enter in X (gnome) anymore! no error message on the screen or in the logs, just a "clean" shutdown Reproducible: Always Steps to Reproduce: 1- Install alsa 2- Install gnome 3- Remove alsa 4- Try to start gnome... Actual Results: X start, screen change of res, back to console, no error Expected Results: X would start and gnome should follow with no sound and possibly with an error message or an error message saying libalsa.so (or whatever) is missing I discovered the problem with: startx back to console X I went in X, killed it xinit same as startx gdm error: missing libalsa.so (or simmilar, didn't writted the error) CFLAGS="-O3 -march=athlon-xp -funroll-loops -fprefetch-loop-arrays -pipe" USE="3dnow acpi alsa apache2 avi cdr cups dga dvd encode foomaticdb gif gnome gphoto2 gtk gtk2 jack java maildir mbox mmx mozilla moeg mysql oggvorbis opengl perl png readline samba scanner sse ssl tcltk truetype usb video X xmms -kde"
I forgot to say: alsa = alsa-lib
Well it's just not wise to remove random libs from your system, they may be referenced here and there. Try revdep-rebuild to fix the apps/libs that reference alsa-lib. closing invalid, screw-up on the user side.
ok, I agree on the user error thing but gnome SHOULD complain and leaves an error somewhere! Right now it only quit cleanly, which is not a normal behavior. So I disagree with the "invalid" thing... This is a bug! Gnome fail to gives any error!
