I've been using 10.2 since it came out, on both my laptop and desktop. All has been well, very well in fact, until today. There were 3 software updates that came up today. I didn't pay much attention to it, just clicked 'update' I faintly recall X or ORG something in the software updater. So I go boot into XP because I still use it for Frontpage and my web templates. Later today, I try to boot into 10.2, and it says:

Master Resource Control: runlevel 5 has been ......reached
Skipped services in runlevel5:.....................irq_balancer nfs microcode smbfs (in yellow)

(I'm pretty sure it always did that)

Then it says Welcome to openSUSE 10.2, and just a command line.

If I log in as root and type startx, the graphics come up, I can open up firefox and browse the web, BUT, when I try to open 'My Computer' Konqueror starts to open, then it throws up and goes back to the command line. There's a lot of text, and I can't type it all here, but here is some of what may be relevant:

Fatal server Error
Caught signal 11. server aborting

In file kernel/qpixmap_x11.cpp, line 748: Out of memory
Kcrash: Application Konqueror crashing...
kicker: fatal IO error: client killed
then there's a few more errors...............
xinit: connection to xserver lost
Hangup
GOT SIGHUP
*** kdesktop got signal 15 (Exiting)
*** kdesktop got signal 1 (Exiting)
kdesktop: Fatal IO error; Client killed
startkde:Shutting down...Warning: connect() failed: :No such file or directory
Error: Can't contact kdeinit!
kdeinit: Fatal IO error: client killed
kdeinit: sending SIGHUP to children
kdeinit: sending SIGTERM to children
kdeinit: exit
KWrited - listening on device /dev/pts/0
starting artsd!
kcminit: cannot connect to xserver :0
startkde: Running shutdown scripts...
xprop: unable to open display ':0'

Now, when I use my username, and type startx, I get my NVIDIA splash screen, then the kde splash screen, as though it is trying to load, then boom, back to the command line.
The error messages seem to be the same, but there is some text that scrolls by that I cannot see as well.

Someone, PLEASE help me out, I have a LOT of time into this install.

I am on my Dell laptop now and 10.2 is fine.

I am not a cli junkie, so if anyone can help, please give me step by step command line stuff, or I can boot in as root and use a terminal

Thanks in advance !!!

PS - I can use file manager OK and that's in Konqueror view, so I can view/edit files as root

Since you have nvidia graphics, I'm willing to make a small wager that the updates included a kernel update. That requires re-installing the nvidia driver so that it can incorporate the kernel update.

If "10.2" means SuSE 10.2, after re-installing the nvidia driver, run SaX2 to configure the graphics card.

As a temporary measure, "modprobe nv" to load the kernel nv (nvidia) driver to have 2d graphics until you get the nvidia driver re-installed (for 3d graphics).

You may be right. I'll report back in a few. I had not thought of that scenario, but why would it work as root and not user?

Whewwwwee!! Boy howdy. Thank God. That was it!!!

Thanks BigRig !!!

I remember too in the beginning when I first installed the drivers, that they would need to be recompiled after a kernel update and just forgot about it.

Do you know what patch it was? Or what Kernel update it was or what Repo it came from.

No, like I said I just kind of glanced at it and hit 'Update' I will definitely pay closer attention next time.

Is there a way for me to find out? Any Software Update log file or something hidden somewhere?

I should also say that the active repo's I have on and refreshing are:

suse.cs.utah.edu/suse/update/10.2

packman.iu-bremen.de/suse/10.2

download.opensuse.org/distribution/10.2/repo/oss/

Sure, run the following command:

sudo cat /var/log/YaST2/y2logRPM | tail -20

Post it here please.

Thank you.

OK, here is the output of that command. Sounds like you are hunting something down

root's password:
Additional rpm output:
warning: /var/adm/mount/AP_0x00000027/i586/libmac-3.99_u4_b5-0.pm.1.i586.rpm: Header V3 DSA signature: NOKEY, key ID 1dfa8f0c

2007-01-12 08:21:04 xmms-real-random-0.3-0.pm.1.i586.rpm installed ok
Additional rpm output:
warning: /var/adm/mount/AP_0x00000027/i586/xmms-real-random-0.3-0.pm.1.i586.rpm: Header V3 DSA signature: NOKEY, key ID 1dfa8f0c

2007-01-12 08:21:07 xmms-plugins-1.2.10-77.i586.rpm install failed
rpm output:
file /usr/lib/xmms/Input/libshn.so from install of xmms-plugins-1.2.10-77 conflicts with file from package xmms-shn-2.4.0-0.pm.1

2007-01-12 08:21:07 xmms-plugins-1.2.10-77.i586.rpm install failed
rpm output:
file /usr/lib/xmms/Input/libshn.so from install of xmms-plugins-1.2.10-77 conflicts with file from package xmms-shn-2.4.0-0.pm.1

2007-01-12 08:21:14 xmms-plugins-1.2.10-77.i586.rpm installed ok
2007-01-12 08:21:17 xmms-mac-0.3.1-0.pm.1.i586.rpm installed ok
Additional rpm output:
warning: /var/adm/mount/AP_0x00000027/i586/xmms-mac-0.3.1-0.pm.1.i586.rpm: Header V3 DSA signature: NOKEY, key ID 1dfa8f0c


I don't know how to put it in a grey text box like most do, so let me know that too if you will

Humm.. try running the above command again with tail -50 to give me more to work on.. Seems like the only things updated was xmms things.. once you provide the -50 i'll let you know what it may have been.. just wondering.. IMO it was something from the PackMan repo. If you wanted to be a tee bit safer you could remote it from your Zen updater.

I think the update that causes the problem (for systems with the nvidia driver) is the xorg-x11-server one.

OK, this is with tail -50

Some things I recently installed which I forgot about were some Window managers, like enlightenment and Windowmaker. Also installed fluxbox.

I know what you are saying about the Packman repo. I know it isn't there by default and I should probably turn it off

Same thing happened to me when I did this update. It was an update for X and the nvidia driver has to be reinstalled to get things back in working order.

It was an xorg update of some sort. It screwed me all up too.
I never did sort it out so I reinstalled. But I needed to do a reinstall anyway because the update before that one screwed up my yast print driver configuration down-loader on all 3 of my boxes..Now, I won't use any updates from suse till I learn how to install and use SMART.

Thanks for posting this. The same thing happened to me and I wound up reinstalling. Next time I'll try to be more patient as I too had a lot of work in my install.

Been there, done that.