Bugzilla – Bug 775489
Critical graphical artifacts/malfunction within Xorg after successful default installation with nouveau driver
Last modified: 2012-09-14 22:39:21 UTC
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:14.0) Gecko/20100101 Firefox/14.0.1 I just installed openSuSE12.2 RC2 and everything went smoothly. But after rebooting the system and autologin is precessed, the whole KDE Desktop is showing only graphics artifacts! Switching to Console 1, init 3 and init 5 again, i see the login screen and after KDE starts up, the Graphic artifacts and malfunction of X11/nouveau is gone. my system is: VAIO PCG-382N / (VGN FZ-50B) core2duo with Nvidia 8400gt. Samsung 830 (256GB) SSD drive. Reproducible: Always Steps to Reproduce: 1. install RC2 on a notebook with nvidia 8400gt. all settings on default. 2. reboot and autologin to KDE4 3. workaround: switch to console 1, login with root, execute init 3, and init 5. after that the graphics look normal and working pretty fine (effects, 3d, transparency..) Actual Results: After the first bootup and the system is configuring everything automatically, the autologin to KDE is ok and graphics looks fine. After rebooting the system and Xorg is loading, you can only see artifacts and cannot control anything by mouse. looks like graphics memory dump that is reacting little bit while moving the artifacted mouse coursor. did not deactivate KMS. just every setting is default.
Disabling Splash Screen (Plymouth) by pressing ESC during the very fast boot sequence, solves the issue. I guess, there is an issue with Plymouth instead of Xorg..
Hello, same bug here, the switch from plymouth (when bubbles join) to kdm fails with fancy display (mouse moves visible). Solution : remove 'splash=silent' from kernel command line so that the long "loading ..... [OK]" runs smoothly display driver : nouveau quadro nvs 140 M machine : lenevo T61 fresh install of 12.2 RC2 and after yast update august 12
So plymouth is still broken with RC2. Wonderful.
Duplicate of bug 771392. *** This bug has been marked as a duplicate of bug 771392 ***