Help ! I did the online update and now I can't get to my desktop

English Install/Boot/Login
#1

Opensuse 13.2.

i get to the login prompt, fill in the info, and start to see the main screen.
the icons, disk drive etc.
then I get a white screen with a long message at the top that disappears before I can get all of it.
something like "dlcdenet.asus.com could not find. And something about protocol unsupported.

and there are 2 small boxes on the completely white screen with “this object could not be created for the following reason”
and no reason is given. Also in the 2 boxes are
“could not find requested components”

eventually it it gets to a message “no system tray”

whats odd is that I can hear music playing from an online source so some parts are up and running.

i can get out to a terminal window by pressing ctl alt f1.

i was looking around on this site to see if anyone else had this happen and I saw nothing other that to try this:
zypper patch.

i tried it and got a red error.
"download (curl) error for 'http://ftp.gwdg.de/pub/Linux/pack an/Susie/opensuse_13.2/repo data/respond.xml

everything has been ok until I tried the online update.

What do I do now ?

#2

Video card driver?

Did you try booting in rescue mode?? Advanced option on grub boot screen

#3

I tried the rescue mode with the same results, white screen.
let me try and reload the video drivers

#4

This won’t help then, if the same problem persists in recovery mode.

Try logging in to a different desktop session, you should be able to select one at the login screen (IceWM is installed by default).

Try with a fresh user account. (you can run YaST in text mode to create one)

But this would rather sound like something went wrong with installing the update. Did you get any error messages?
That “zypper patch” doesn’t work implies that you have no internet connection. How did you connect? NetworkManager and a wireless user connection?
Run “nmtui” in a xterm or text mode and switch it to a system connection (“Allow other users to connect”). Then you should have an internet connection even in text mode or IceWM. Or use “nm-applet”, but for this you’d have to have NetworkManager-gnome installed.

Then run “zypper up” and post error messages you might get.
And please your repo list as well:

zypper lr -d

Also check that your hard disk is not full.

#5

PS: As apparently vital parts of KDE fail to start, please run this in an xterm inside IceWM and post the output:

startkde

This should give a hint to what exactly the problem is.

#6

I tried the rescue mode with the same results, white screen.
let me try and reload the video drivers

i did my usual 2 step nvidia zypper ar and in, but it was no help.

when I did the debugging - advanced reboot, and it hung up with the white screen, I did a ctl alt f1 and I didn’t see any errors and the log got to:

OK reached target system initialization.

the last 2 lines said before the green OK we’re:
3.044804 Nvidia module license Nvidia taint kernel
3.044806 disabling lock debugging due to kernel taint.

When I got to the advanced selection, there were about 6 choices and I took the top one if that makes a difference.

#7

The top one is a normal boot.
Try the second one, that’s “recovery mode”.

#8

lots of disk space and I don’t know how to do a “inside IceWM” plain old IceWM gives a cnf

starkde gives a DISPLAY is not set or cannot connect to the X server.

#9

I did Yast from the command line, added a new user and he was able to get to the desktop. Though it looks kinda Spartan.

re the advanced choices, there are about 6 of them with I think each having a different kernel.

#10

You should not run “inside IceWM” in IceWM. You should “startkde” in an xterm window inside an IceWM session.

starkde gives a DISPLAY is not set or cannot connect to the X server.

In a graphical session?
I.e. you logged in to IceWM, opened an xterm window and typed it there?
I hope you didn’t run it as root, i.e. by using “su”. Run it as plain user.

If you still get that message, then try:

xhost +
startkde
#11

You get into a KDE desktop?
What do you exactly mean with “Spartan”?
You should get a desktop with the default settings. Is something missing?

re the advanced choices, there are about 6 of them with I think each having a different kernel.

No.
There are 3 different kernels, each one as normal boot and “recovery mode”.

But as you are using nvidia, you won’t see the full text as the resolution is too low.

#12

Looks Spartan because it is the default your setting are in your home the new guys is in his home. (even though they are both you)

So it looks like something in the KDE configs has gone south in your ~/.kde4 directory

As the new user open a super user file manager. navigate to you normal user home. rename .kde directory. Note the period and that it makes the file/directory hidden. But the root user should see it with out changing settings in the manager

Then log out and back in as your self this will start things up with the default settings so you will have to redo your desktop. It is good for the soul to do that from time to time rotfl!

If that does not fix things let us know

#13

wolfie, I have no idea what you mean by inside an IceWM session.
i am sitting at a command prompt and I type “startkde”
I don’t know what you mean by this “startkde” in an xterm window inside an IceWM session.
so I will try the host thing and I am not using sudo.

#14

Xhost + gives a " unable to open display "

i didnt try the startkde

#15

Log in to “IceWM” and run it there.

I am sitting at a command prompt and I type “startkde”

What “command prompt”? In text mode?
As I said, you should select IceWM on the login screen (the “wrench” icon in the bottom left corner) and login.
Then click on the “XTerm” button and you will get a command window.
In this window, type “startkde” and post the output.

I don’t know what you mean by this “startkde” in an xterm window inside an IceWM session.
so I will try the host thing and I am not using sudo.

Again, login to IceWM, run “xterm”, and type “startkde” into the appearing window.

I have the feeling you are running this in text mode.
Do it in a graphical session, IceWM e.g.

And you still didn’t tell about the “Spartan” desktop you got with a fresh user account.
Is it KDE? Is it working?
If yes, there’s something wrong with your user settings as gogalthorp wrote.
If not, it is an installation problem.

#16

Thank you for telling me how to start IceWM

I am running this now from within it.

When I did the startkde I saw a lot of error messages go flying by and then my browser started up and asked me if I wanted to restore it.
I was looking for a way to capture the IceWM log but dont see it.
So, that is where I am now.

In answer to your prior questions.
When I halted before at the white screen, I did a ctl-alt-del and I got to the term window, command prompt which asked me for a user id annd PW.

Re the new user, I think it is kde. THere were only 4 icons on the desktop. Firefox, and 3 others.

I am going to post thsi and stop Palemoon and see what the desktop looks like.

#17

The browser was probably started by KDE’s session management.
But did you get a functional KDE desktop?

I was looking for a way to capture the IceWM log but dont see it.

The “IceWM log” won’t help you much.

Please just copy/paste the last lines of output you get.
You could redirect the output to a file and provide that (via http://susepaste.org or similar):

startkde >startkde.log

In answer to your prior questions.
When I halted before at the white screen, I did a ctl-alt-del and I got to the term window, command prompt which asked me for a user id annd PW.

Hm? Ctrl+Alt+Del should show the logout dialog. Probably KDE crashed then…

Re the new user, I think it is kde. THere were only 4 icons on the desktop. Firefox, and 3 others.

Yes, that’s how it is after a fresh installation.

So renaming ~/.kde4/ for your standard user should help, but it will give you the same “spartan” default desktop, although the files in your Desktop folder should still be there…

#18

I found the log of IceWm and there was a lot of stuff in it talking about KSycoca.Private and darn it but I cant do copy and paste.

There were messages like this:
Warning your global KLocale is being recreated with a valid main component instead of a fake…tried to call i18…
and
KGet (1940) KGet::: create transfer : warning ! No plugin found to handle Kurl ("http://dlcdnet.asus.com/pub/ASUS/wireless/USB-N53/Dr_usb_N53_10140… and more.

Hundreds of lines of stuff like that.

#19

IceWM doesn’t use KSycoca. That’s probably not the “log of IceWm”…

Private and darn it but I cant do copy and paste.

Why?
Just select the text with the left mouse button, and paste it with the middle one.

There were messages like this:
Warning your global KLocale is being recreated with a valid main component instead of a fake…tried to call i18…
and
KGet (1940) KGet::: create transfer : warning ! No plugin found to handle Kurl ("http://dlcdnet.asus.com/pub/ASUS/wireless/USB-N53/Dr_usb_N53_10140… and more.

Hundreds of lines of stuff like that.

Well, it’s hard to tell what’s the problem without seeing the exact messages.
The KLocale message is only a “Warning” for developers and can be ignored.

The last one is “just” KGet, nothing critical, but if it cannot find a plugin for http connections, this might point to a bigger problem.
Try to run “kbuildsycoca4 --noincremental” (as user).
And again, do you get a working KDE desktop when you run “startkde”? Or do you see problems?

And what about the fresh user account? Any problems there?

Just to be sure, let’s also check that the nvidia driver is working. A non-working driver can cause big problems depending on your user settings (it might even cause KDE to crash), altough everything might still work fine on a fresh user account with the default settings.
So please install Mesa-demo-x if not installed, and post the output of:

glxinfo|grep render

Or provide the file /var/log/Xorg.0.log.

#20

No 3 button mouse here and the right button does not select. Ctl-v and ctl-c do not work.
no I did not get a working kde desktop.
I type “pale moon” into the xterm window.

so I will type the last few lines of what the window showed. Oh yeah, there was a lot of messages with this in them.
“found version 242, expecting version 243 or higher”

from the the xterm window.

kded(1814)/kdecore (trader ) KServiceTypeTrader::defaultOffers: KserviceTypeTrader: serviceType “KDEDModule” not found

[1435856022744] ABP timeline: Entered FilterStorage.saveToDisk() (First event)

and and about 6 more lines talking about ABP Timeline
the last one says
ABP timeline: Total time elapsed : 0