Bug 156620

Summary:	KDE4 won't start on Averatec Laptop
Product:	[I don't know] kde	Reporter:	Bill Egert <begert>
Component:	general	Assignee:	Unassigned bugs <unassigned-bugs-null>
Status:	RESOLVED NOT A BUG
Severity:	normal
Priority:	NOR
Version First Reported In:	unspecified
Target Milestone:	---
Platform:	Compiled Sources
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Bill Egert 2008-01-25 02:56:29 UTC

Version:            (using Devel)
Installed from:    Compiled sources
Compiler:          gcc 4.1.3 
OS:                Linux

After building KDE4 @rev 765018 on Kubuntu, I tried starting a new KDE4 session.  I know the method I am using works as this all works fine on my desktop.  The login graphic starts but gets stuck on the K at the end.  From here my system is completely locked up.

Here is a section I logged when trying to start KDE4 from a console:

kdeinit4: Got KWRAPPER 'ksmserver' from socket.
kdeinit4: preparing to launch /home/bill/KDE4/bin/ksmserver
<unknown program name>(5854)/ KStartupInfo::createNewStartupId: creating:  "laptop;1201224428;310208;5854_TIME0" : "unnamed app"
kdeinit4: PID 5854 terminated.
kdeinit4: Got SETENV 'SESSION_MANAGER=local/laptop:/tmp/.ICE-unix/5855,inet6/laptop:49573,inet/laptop:54458' from klauncher.
ksmserver(5855) KSMServer::restoreSession: KSMServer::restoreSession  "saved at previous logout"
klauncher(5846)/kdecore (KSycoca) KSycocaPrivate::openDatabase: Trying to open ksycoca from  "/home/bill/.kde4/cache-laptop/ksycoca4"
kdeinit4: Got EXEC_NEW 'kwin' from launcher.
kdeinit4: preparing to launch /home/bill/KDE4/bin/kwin
klauncher(5846)/kio (KLauncher) KLauncher::processRequestReturn: "kwin" (pid 5858) up and running.
kwin(5858) KWin::Extensions::init: Extensions: shape: 0x "11"  composite: 0x "4"  render: 0x "a"  fixes: 0x "40"
kwin(5858) KWin::CompositingPrefs::detect: glx version is  1 . 2
kwin(5858) KWin::CompositingPrefs::detectDriverAndVersion: GL vendor is "VIA Technology"
kwin(5858) KWin::CompositingPrefs::detectDriverAndVersion: GL renderer is "Mesa DRI UniChrome (KM400) 20060710 x86/MMX+/3DNow!+/SSE"
kwin(5858) KWin::CompositingPrefs::detectDriverAndVersion: GL version is "1.2 Mesa 7.0.1"
kwin(5858) KWin::CompositingPrefs::detectDriverAndVersion: XGL: no
kwin(5858) KWin::CompositingPrefs::detectDriverAndVersion: Detected driver "unknown" , version ""
kdeinit4: Got EXEC_NEW '/home/bill/KDE4/bin/krunner' from launcher.
kdeinit4: preparing to launch /home/bill/KDE4/bin/krunner
klauncher(5846)/kio (KLauncher) KLauncher::processRequestReturn: "/home/bill/KDE4/bin/krunner" (pid 5859) up and running.

Comment 1 Lubos Lunak 2008-01-25 16:03:09 UTC

- What does completely locked up mean exactly? Can you switch to text mode, does NumLock still change?
- Have you checked http://websvn.kde.org/*checkout*/trunk/KDE/kdebase/workspace/kwin/COMPOSITE_HOWTO ?
- What gfx card/driver is that?
- Is there really no debug output from kwin following this?

Comment 2 Bill Egert 2008-01-25 19:28:03 UTC

Lets see how I do answering these questions:

- What does completely locked up mean exactly? Can you switch to text mode, does NumLock still change?
  *- I mean that the screen is locked up, touchpad does not move mouse, and PC does not seem to respond to Keyboard commands.

- Have you checked http://websvn.kde.org/*checkout*/trunk/KDE/kdebase/workspace/kwin/COMPOSITE_HOWTO ?
   *- I have not checked this.

- What gfx card/driver is that?
  *-S3 Unichrome display controller /w shared video memory.  Is there some nice commands I can run that will give you the info you acyually want :P

- Is there really no debug output from kwin following this? 
   *- Yes, debug comes to a stop.

Comment 3 Lubos Lunak 2008-01-29 11:23:16 UTC

> I have not checked this.

Then that line indeed meant 'do so', but this doesn't look like KWin problem anyway. If it locks up completely, it's either X or kernel problem. Can you use Compiz on the same setup?

Comment 4 Bill Egert 2008-01-29 14:12:13 UTC

I have not tried to use Compiz on that laptop.  Would you suggest compiling KDE4 sources without composite to see if that helps?

Comment 5 Lubos Lunak 2008-01-29 14:41:52 UTC

You don't need to recompile to disable compositing : http://techbase.kde.org/index.php?title=Projects/KWin/4.0-release-notes#Troubleshooting
Or does this mean that you don't have effects enabled in KWin?

Comment 6 Bill Egert 2008-01-29 15:01:06 UTC

Unless effects are on by default, I don't see how I could have ever enabled composite to begin with.  I was just thinking that maybe to test if composite is a part of the problem, I could just recomplile without composite support and test.

Comment 7 Lubos Lunak 2008-01-29 15:27:25 UTC

This is not a KWin problem then (and IMHO not even a KDE problem in general).

Comment 8 Bill Egert 2008-01-29 16:03:41 UTC

I won't argue that it is a KWin issue, although I don't know how its not a KDE4 issue.  I log into Kubuntu just fine, its only when I try to start a KDE4 session does this happen.

Comment 9 Lubos Lunak 2008-01-29 19:45:25 UTC

KDE is only userspace applications and as such it should be not able to cause complete lockups, it can at most trigger such bugs in kernel/X/wherever. I suggest you report the problem to your distribution.

Comment 10 Lubos Lunak 2008-03-03 21:20:07 UTC

Closing as per comment #9.