So in both cases it seems that something returns NULL, in the working one it says

QImage::convertDepth: Image is a null image
QImage::smoothScale: Image is a null image

and in the other dlsym complains about NULL input. These are probably related, and this Qt error makes sense since it's KDM that crashes. The driver itself or XDM work.

Walmartshopper, I disagree with your assessment about custom Kernels. I and a couple of other people who have already posted are using custom kernels. Be aware that when you build a custom kernel you have to point the NVIDIA driver to the sources:

I upgraded to 12.2 two days ago and built 2.6.28.1 and NVIDIA 180.22 last night with no issue.

works with me. im using 2.6.28 and it also works for my 2.6.27-5 or what ever is stock with slackware 12.1 =)

180.22 works on my laptop with slackware-current and the new KDE 4.2rc1 packages that just came out today. I'm waiting for 4.2 stable before upgrading my main box. I'll wait it out until the official slack packages for 4.2 are out and then try 180.22 again.

could you post you xorg.conf and also do
and post ~/stracestartx.txt
That might give some clue as to what's broken.
Don't worry - only read page 1

nvidia 7950 , 180.22 , stock generic-smp kernel, kde 4 from -current, no issues.

See my Xorg.0.log and .xsession-errors attached. I get the same EE error with 177.82 driver.

I have since reinstalled X and 180.22. Still a blank desktop. I added firefox to my session so it loads when I login. Now I got firefox and pidgin running. My shortcut keys do not work either.

What's really driving me up the wall is there are no errors (at least unusual ones) in Xorg or .xsession-errors.

Attached Files

	Xorg.0.log.180.22.txt (30.3 KB, 11 views)
	xsession-errors.txt (24.3 KB, 14 views)

I attached the strace output for kdm (with 180.22).

By the way, kdm doesn't crash. It continues to run in the background but I fall back to the console.

Attached Files

kdm.txt (7.6 KB, 18 views)

I just upgraded my desktop pc to slackware-current with kde 4.2rc1. Same exact packages as my laptop. Laptop works with 180.22, desktop doesn't. The only real difference is video card... 8400m vs. 8800gt.

With kde 4.2 and nvidia 180.22, I get the black desktop problem. Gkrellm loads, and I can move the mouse around, but nothing else starts up. The interesting thing is that I can start plasma from a command line, and it loads up fine. The desktop is mostly usable, except hotkeys and keyboard shortcuts like alt+f2 don't work, even after restarting the khotkeys service.

Also, if I rename /usr/bin/plasma to /usr/bin/plasma-real and create a shell script named /usr/bin/plasma that contains the following...

#!/bin/sh
/usr/bin/plasma-real

...plasma starts when I log in, and everything except keyboard shortcuts work. I couldn't live without alt+f2 and alt+tab though, so I switched back to 177.82. Plus, even though that works somewhat, it's not the correct way to start up kde, and I'm sure there are some other side effects involved.

Maybe it's a driver problem related to specific cards?

walmartshopper I have the same exact problem. I tried the plasma hack but that did not work for me. I have a T61 with quatro NV 140M.

Can you add strace -o ~/strace.txt /usr/bin/plasma-real to your script and post the file. I would like to compare it with mine.

I'm having the same basic problem that everyone else is describing with 180.22 driver and the previous 180.xx release as well. KDE 3.5.9, custom 2.6.25.17 PAE enabled kernel on Slackware 12.1, 6Gb RAM, Core 2 Duo on a Gigabyte GA-965P DS3 mobo. I'm also running an 8800GT card like walmartshopper mentioned. Getting the hdeinit error and dcopserver won't start.

No errors for me.
2.6.28 custom smp.
180.22 for a 7900GS
KDE 3.5.10

Hello,

I'm using nvidia packages from SlackBuilds.org with no problems:

/var/log/packages/nvidia-driver-180.22-i586-1_SBo
/var/log/packages/nvidia-kernel-180.22_2.6.27.7_smp-i486-1_SBo

Check they are the right drivers for your graphics card (mine is Nvidia GeForce 8400GS).

Greetings.

My card is a GeForce Go 6150. I've tested 180.xx with 12.1 and they worked (except for a fan noise issue which caused me to revert to 177.xx). This kdm crash started occurring after the upgrade to 12.2.

It still happens with 180.25.

180.27 was just released about 5 minutes ago... going to give it a shot.