https://bugzilla.novell.com/show_bug.cgi?id=656138 https://bugzilla.novell.com/show_bug.cgi?id=656138#c0 Summary: KDE4 hangs on startup Classification: openSUSE Product: openSUSE 11.3 Version: Final Platform: x86 OS/Version: openSUSE 11.3 Status: NEW Severity: Normal Priority: P5 - None Component: KDE4 Workspace AssignedTo: kde-maintainers@suse.de ReportedBy: jaanvajakas@hot.ee QAContact: qa@suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (compatible; Konqueror/4.4; Linux) KHTML/4.4.4 (like Gecko) SUSE After installing updates to openSUSE 11.3, KDE4 hangs on startup unless the nomodeset kernel parameter is used. (Before updating, out of the box this problem did not occur). Reproducible: Always Steps to Reproduce: 1. Install openSUSE 11.3 from KDE4 Live CD. 2. Log in to the installed system (works normally). 3. Install all available updates except the optional one (Microsoft TrueType Core fonts). 4. Reboot. 5. Log in to the installed system. The progress bar stops at the middle when loading KDE. 6. Press Ctrl-Alt-F1. The console shows up. 7. Press Ctrl-Alt-F7. The computer hangs completely: Ctrl-Alt-F1 does not work, Num Lock does not switch the keyboard light anymore, Alt-Ctrl-Del and power button seem to do nothing. Workarounds: * If instead of step 7 I log in as root and execute killall kdm kdm and log in again then KDE starts up normally. * If instead of steps 4-7 I log into IceWM then IceWM starts up normally. * If in step 4 I specify the kernel parameter nomodeset in GRUB then step 4 completes normally except that the display resolution is lower than the native resolution of my LCD display. Actual Results: See above. Expected Results: KDE login should not hang at step 5. The system should not hang at step 7. My motherboard is AOpen i945GMt-VFA with Intel i945GM chipset. The resolution of my LCD display is 1680x1050. The kernel version now (after updates at step 3) is 2.6.34.7-0.5-default. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.