Bug 156010

Summary:	system freeze when using KDE4 - doesn't respond to any commands
Product:	[Unmaintained] plasma4	Reporter:	Jonathan Jesse <jjesse>
Component:	general	Assignee:	Plasma Bugs List <plasma-bugs-null>
Status:	RESOLVED WORKSFORME
Severity:	normal	CC:	finex
Priority:	NOR
Version First Reported In:	unspecified
Target Milestone:	---
Platform:	Ubuntu
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description Jonathan Jesse 2008-01-17 17:18:48 UTC

Version:            (using KDE 4.0.0)
Installed from:    Ubuntu Packages

Good morning,

I apoligize if I'm reporting this bug against the wrong package but when using a KDE4 session, packages installed from Kubuntu's KDE4 PPA (http://ppa.launchpad.net/kubuntu-members-kde4/ubuntu gutsy main), I switch between two windows, Firefox and Konverstation and the system freezes.  THere is no disk activity light indicating any activity.
When I ssh into the box through Top I don't see anything being hung or my processor using all of the resources.  If I try to kill anything I do not see any response on my system either.  Fresh install of Kubuntu 7.10, plus KDE4.  System is competly up to date.
Also when I am ssh'd into the system, I can' even do a sudo restart or a sudo shutdown -h now.  When I type those commands into the console session, I see "The System is going down for reboot" but nothing actually happens on my laptop.

I don't know what else I need to provide help out, but will try to do my best.

Thanks for all the great work on KDE,

Jonathan

Comment 1 FiNeX 2008-01-17 21:28:21 UTC

When you log in with ssh, can you see system logs?
can you check the active process (with top/ps )?

Comment 2 Jonathan Jesse 2008-01-17 21:31:41 UTC

thanks for the quick response, the next time it happens i will check for you

Comment 3 Jonathan Jesse 2008-01-24 01:05:36 UTC

Good evening,

After doing soem further digging and working I noticed I was having a crash as well in KDE 3 with the same symtpoms.  After digging and also posting on Kubuntu Users mailing list for further information it appears to be a problem with the NVidia driver.  Using an more updated closed source driver solves the problem.

CLosing this bug,

Thanks,

Jonathan