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

The wheel is also a button on most modern mice. Press it it clicks. If have a really really old mouse maybe it does not have this function. but it would have to be ancient

I got an update today and it had a lot of KDE updates but I had no problems here.

Maybe you caught things being updated on the server/mirror and missed some things. Did you say you tried zypper up?

Do I do that from the xterm window ?
or somehow invoke Yast and do it there .
?

No, but the left button should select text.
And most mice today have at least 3 buttons. Normally the 3rd/middle button is part of the mouse wheel, so try to press that.
Or press left+right together, that should emulate the middle button if there is none.

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”

Ok, “kbuildsycoca4 --noincremental” should fix that.
And/or try to remove the content of /var/tmp/kdecase-$USER/.

from the the xterm window.

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

That sounds bad.
Again, kbuildsycoca4 should fix that. So run it and post the output.

If not, some system files are corrupted, but then a fresh user account shouldn’t work either.

[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

No idea what ABP timeline would mean, but I doubt it’s related to your problem…
Google seems to indicate this comes from Firefox’s AdBlock Plus plugin.

Yes.
But you need to do that as root, so run “sudo zypper up”.

or somehow invoke Yast and do it there .
?

You can install updates with YaST as well, yes. “Online Update” would install only official updates from the update repo, with “Softwaremanagement” you could install others as well.

You should find YaST in IceWM’s “start menu”.

did you mean to type kdecache ?

and I can select text ok but there is no way to copy it. Usually I use the right button but that now will position the cursor to the top of the xterm window.

Yes, sorry.

and I can select text ok but there is no way to copy it.

You don’t need to copy it.
Again, the previously selected text can be pasted with the middle mouse button, without having to “copy” it explicitly.

Ah, good to know.
ok, I did all that you asked.
cleaned out kdecache-me
ran the kbuildsycoca4 thing
did the zypper up and I did not see any red error messages like last time.

and I am still stuck.
what is weird is that when I am running xterm in IceWM and I wanted to try a normal boot,
i did a shutdown and it would not shut down. So I used the power off button.
then when I started it up again, it went back into IceWM automatically even though I made sure it was not checked in the wrench thingies.

and just for hecks , I rebooted with the new user that I just added and it worked fine.

If all is ok with the other user the problem lies in your KDE config files. Follow the procedure I outlined ie as root and without your user running remove/rename .kde4 this will put you back to default settings like your new user and you will have to set up the desktop again to your want/needs

You need to logout and then do a shutdown/reboot from the login screen (button in the bottom-right corner).
Or run “systemctl poweroff” or “systemctl reboot”.

then when I started it up again, it went back into IceWM automatically even though I made sure it was not checked in the wrench thingies.

KDM always uses the last selected session for each user.

and just for hecks , I rebooted with the new user that I just added and it worked fine.

So it is somehow related to the user settings.
Again, please post the output of “glxinfo|grep render” and/or /var/log/Xorg.0.log to verify that the nvidia driver is fully working.

Renaming ~/.kde4 should hopefully “fix” the problem in any case, but you’ll lose all your settings.
You could copy back the files in batches to see which one is causing the problem, most likely candidates are probably ~/.kde4/share/config/kwinrc and ~/.kde4/share/config/plasma-desktop-appletsrc, so you might also start with just renaming/deleting those two.

Still stuck.
i renamed .kde4 and did a shutdown from the power button(lower right corner) login screen and I still get the IceWM desktop.

So so how do I get back to a default desktop ?

Of course. As I wrote already, KDM will always use the last selected desktop for each user.

So so how do I get back to a default desktop ?

Select “KDE Plasma Workspace” or “Default” on the login screen, just as you did with IceWM before.

Oh yeah, when I take the start-with-advanced option from the main login screen, it leads me to another choice where there are about 14 choices.
beginning with
3.16.7-21-Desktop
.
.
.
and ending with
3.7.10-1.45-Desktop
3.7.10-1.45-Desktop (Recovery mode)
3.7.10-1.45-Default

So consider me confused as to which one to take.

Seems so.

You are talking about the boot menu now. Just do a normal boot.

You should choose “KDE Plasma Workspace” or “Default” at the Login Screen, i.e. the screen where you enter your username and password.
As you seem to have Auto-Login enabled, you have to logout first to get to the login screen.

But I thought that should all be clear by now…

Well, wolfie, still at the same place.
i tried both kde plasma and default and what I get is a completely white screen. After waiting a bit, about one minute, a message appears
HPLP status service
No system tray detected on this system
unable to start. Exiting.

and I don’t know what is going on when I say to power off, or shutdown and nothing happens. That is from both the IceWM desktop or the login screen power button.

i wind up by pressing the power button.

Hm. So then, can you please post the output of “glxinfo | grep render” and/or /var/log/Xorg.0.log?
And as I also asked before, please run “kbuildsycoca --noincremental” and post the output.

You can do that in IceWM, but you should run both as the affected user.

If that still happens with a fresh ~/.kde4, and it doesn’t happen on a fresh user account, something else must be the problem.

Btw, you should also be able to run “konsole” in IceWM (you should find it in the start menu), where you do have an option to copy text to the clipboard.

After waiting a bit, about one minute, a message appears
HPLP status service
No system tray detected on this system
unable to start. Exiting.

Yes, if Plasma fails to start, HPLIP won’t find a system tray to display its icon and tells you so.

and I don’t know what is going on when I say to power off, or shutdown and nothing happens. That is from both the IceWM desktop or the login screen power button.

I thought you were able to reboot/shutdown from the login screen before?

That it doesn’t work in IceWM is a bug there. Logout and you’ll get back to the login screen, where it should work.
If not, something else is broken too on your system.

The program 'kbuildsycoca' can be found in the following package:  * kdelibs3  path: /opt/kde3/bin/kbuildsycoca, repository: zypp (repo-oss) ]


Try installing with:
    sudo zypper install kdelibs3


hexdump@Corky-PC:~> glxinfo | grep render
direct rendering: Yes
OpenGL renderer string: GeForce 7050 / nForce 620i/integrated/SSE2
    GL_KTX_buffer_region, GL_NVX_conditional_render, 
    GL_OES_fbo_render_mipmap, GL_OES_get_program_binary, GL_OES_mapbuffer, 
    GL_OES_fbo_render_mipmap, GL_OES_get_program_binary, GL_OES_mapbuffer, 
hexdump@Corky-PC:~> 



and /var/log/xorg… Note that I removed some of the earlier entries cause it was too big to post.

     9.057] (WW) NVIDIA(0): Unable to support custom viewPortOut 1680 x 945 +0 +52
     9.058] (WW) NVIDIA(0): Unable to support custom viewPortOut 1680 x 945 +0 +52
     9.058] (--) NVIDIA(0): DPI set to (99, 98); computed from "UseEdidDpi" X config
     9.058] (--) NVIDIA(0):     option
     9.058] (II) UnloadModule: "nouveau"
     9.058] (II) Unloading nouveau
     9.058] (II) UnloadModule: "nv"
     9.058] (II) Unloading nv
     9.058] (II) UnloadModule: "modesetting"
     9.058] (II) Unloading modesetting
     9.058] (II) UnloadModule: "fbdev"
     9.058] (II) Unloading fbdev
     9.058] (II) UnloadSubModule: "fbdevhw"
     9.058] (II) Unloading fbdevhw
     9.058] (II) UnloadModule: "vesa"
     9.058] (II) Unloading vesa
     9.058] (--) Depth 24 pixmap format is 32 bpp
     9.063] (II) NVIDIA(0): ACPI: failed to connect to the ACPI event daemon; the daemon
     9.063] (II) NVIDIA(0):     may not be running or the "AcpidSocketPath" X
     9.063] (II) NVIDIA(0):     configuration option may not be set correctly.  When the
     9.063] (II) NVIDIA(0):     ACPI event daemon is available, the NVIDIA X driver will
     9.063] (II) NVIDIA(0):     try to use it to receive ACPI event notifications.  For
     9.063] (II) NVIDIA(0):     details, please see the "ConnectToAcpid" and
     9.063] (II) NVIDIA(0):     "AcpidSocketPath" X configuration options in Appendix B: X
     9.063] (II) NVIDIA(0):     Config Options in the README.
     9.063] (II) NVIDIA(0): Setting mode "CRT-0:nvidia-auto-select"
     9.169] (==) NVIDIA(0): Disabling shared memory pixmaps
     9.169] (==) NVIDIA(0): Backing store enabled
     9.169] (==) NVIDIA(0): Silken mouse enabled
     9.169] (==) NVIDIA(0): DPMS enabled
     9.169] (II) Loading sub module "dri2"
     9.169] (II) LoadModule: "dri2"
     9.169] (II) Module "dri2" already built-in
     9.169] (II) NVIDIA(0): [DRI2] Setup complete
     9.169] (II) NVIDIA(0): [DRI2]   VDPAU driver: nvidia
     9.169] (--) RandR disabled
     9.176] (II) Initializing extension GLX
     9.352] (II) config/udev: Adding input device Power Button (/dev/input/event3)
     9.352] (**) Power Button: Applying InputClass "evdev keyboard catchall"
     9.352] (**) Power Button: Applying InputClass "system-keyboard"
     9.352] (**) Power Button: Applying InputClass "evdev keyboard catchall"
     9.352] (II) LoadModule: "evdev"
     9.352] (II) Loading /usr/lib64/xorg/modules/input/evdev_drv.so
     9.352] (II) Module evdev: vendor="X.Org Foundation"
     9.352]    compiled for 1.16.1, module version = 2.9.0
     9.352]    Module class: X.Org XInput Driver
     9.352]    ABI class: X.Org XInput driver, version 21.0
     9.352] (II) Using input driver 'evdev' for 'Power Button'
     9.352] (**) Power Button: always reports core events
     9.352] (**) evdev: Power Button: Device: "/dev/input/event3"
     9.352] (--) evdev: Power Button: Vendor 0 Product 0x1
     9.352] (--) evdev: Power Button: Found keys
     9.352] (II) evdev: Power Button: Configuring as keyboard
     9.352] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXPWRBN:00/input/input4/event3"
     9.352] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 6)
     9.352] (**) Option "xkb_rules" "evdev"
     9.352] (**) Option "xkb_model" "pc104"
     9.352] (**) Option "xkb_layout" "us"
     9.375] (II) config/udev: Adding input device Power Button (/dev/input/event2)
     9.375] (**) Power Button: Applying InputClass "evdev keyboard catchall"
     9.375] (**) Power Button: Applying InputClass "system-keyboard"
     9.375] (**) Power Button: Applying InputClass "evdev keyboard catchall"
     9.375] (II) Using input driver 'evdev' for 'Power Button'
     9.375] (**) Power Button: always reports core events
     9.375] (**) evdev: Power Button: Device: "/dev/input/event2"
     9.375] (--) evdev: Power Button: Vendor 0 Product 0x1
     9.375] (--) evdev: Power Button: Found keys
     9.375] (II) evdev: Power Button: Configuring as keyboard
     9.375] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input3/event2"
     9.375] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 7)
     9.375] (**) Option "xkb_rules" "evdev"
     9.375] (**) Option "xkb_model" "pc104"
     9.375] (**) Option "xkb_layout" "us"
     9.375] (II) config/udev: Adding input device HDA NVidia Line Out Surround (/dev/input/event9)
     9.375] (II) No input driver specified, ignoring this device.
     9.375] (II) This device may have been added with another device file.
     9.375] (II) config/udev: Adding input device HDA NVidia Line Out CLFE (/dev/input/event10)
     9.375] (II) No input driver specified, ignoring this device.
     9.375] (II) This device may have been added with another device file.
     9.376] (II) config/udev: Adding input device HDA NVidia Line Out Side (/dev/input/event11)
     9.376] (II) No input driver specified, ignoring this device.
     9.376] (II) This device may have been added with another device file.
     9.376] (II) config/udev: Adding input device HDA NVidia Front Headphone (/dev/input/event12)
     9.376] (II) No input driver specified, ignoring this device.
     9.376] (II) This device may have been added with another device file.
     9.376] (II) config/udev: Adding input device HDA NVidia Front Mic (/dev/input/event5)
     9.376] (II) No input driver specified, ignoring this device.
     9.376] (II) This device may have been added with another device file.
     9.376] (II) config/udev: Adding input device HDA NVidia Rear Mic (/dev/input/event6)
     9.376] (II) No input driver specified, ignoring this device.
     9.376] (II) This device may have been added with another device file.
     9.376] (II) config/udev: Adding input device HDA NVidia Line (/dev/input/event7)
     9.376] (II) No input driver specified, ignoring this device.
     9.376] (II) This device may have been added with another device file.
     9.377] (II) config/udev: Adding input device HDA NVidia Line Out Front (/dev/input/event8)
     9.377] (II) No input driver specified, ignoring this device.
     9.377] (II) This device may have been added with another device file.
     9.377] (II) config/udev: Adding input device AT Translated Set 2 keyboard (/dev/input/event0)
     9.377] (**) AT Translated Set 2 keyboard: Applying InputClass "evdev keyboard catchall"
     9.377] (**) AT Translated Set 2 keyboard: Applying InputClass "system-keyboard"
     9.377] (**) AT Translated Set 2 keyboard: Applying InputClass "evdev keyboard catchall"
     9.377] (II) Using input driver 'evdev' for 'AT Translated Set 2 keyboard'
     9.377] (**) AT Translated Set 2 keyboard: always reports core events
     9.377] (**) evdev: AT Translated Set 2 keyboard: Device: "/dev/input/event0"
     9.377] (--) evdev: AT Translated Set 2 keyboard: Vendor 0x1 Product 0x1
     9.377] (--) evdev: AT Translated Set 2 keyboard: Found keys
     9.377] (II) evdev: AT Translated Set 2 keyboard: Configuring as keyboard
     9.377] (**) Option "config_info" "udev:/sys/devices/platform/i8042/serio0/input/input0/event0"
     9.377] (II) XINPUT: Adding extended input device "AT Translated Set 2 keyboard" (type: KEYBOARD, id 8)
     9.377] (**) Option "xkb_rules" "evdev"
     9.377] (**) Option "xkb_model" "pc104"
     9.377] (**) Option "xkb_layout" "us"
     9.377] (II) config/udev: Adding input device ImPS/2 Generic Wheel Mouse (/dev/input/event1)
     9.377] (**) ImPS/2 Generic Wheel Mouse: Applying InputClass "evdev pointer catchall"
     9.377] (**) ImPS/2 Generic Wheel Mouse: Applying InputClass "evdev pointer catchall"
     9.377] (II) Using input driver 'evdev' for 'ImPS/2 Generic Wheel Mouse'
     9.377] (**) ImPS/2 Generic Wheel Mouse: always reports core events
     9.377] (**) evdev: ImPS/2 Generic Wheel Mouse: Device: "/dev/input/event1"
     9.377] (--) evdev: ImPS/2 Generic Wheel Mouse: Vendor 0x2 Product 0x5
     9.378] (--) evdev: ImPS/2 Generic Wheel Mouse: Found 3 mouse buttons
     9.378] (--) evdev: ImPS/2 Generic Wheel Mouse: Found scroll wheel(s)
     9.378] (--) evdev: ImPS/2 Generic Wheel Mouse: Found relative axes
     9.378] (--) evdev: ImPS/2 Generic Wheel Mouse: Found x and y relative axes
     9.378] (II) evdev: ImPS/2 Generic Wheel Mouse: Configuring as mouse
     9.378] (II) evdev: ImPS/2 Generic Wheel Mouse: Adding scrollwheel support
     9.378] (**) evdev: ImPS/2 Generic Wheel Mouse: YAxisMapping: buttons 4 and 5
     9.378] (**) evdev: ImPS/2 Generic Wheel Mouse: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
     9.378] (**) Option "config_info" "udev:/sys/devices/platform/i8042/serio1/input/input2/event1"
     9.378] (II) XINPUT: Adding extended input device "ImPS/2 Generic Wheel Mouse" (type: MOUSE, id 9)
     9.378] (II) evdev: ImPS/2 Generic Wheel Mouse: initialized for relative axes.
     9.378] (**) ImPS/2 Generic Wheel Mouse: (accel) keeping acceleration scheme 1
     9.378] (**) ImPS/2 Generic Wheel Mouse: (accel) acceleration profile 0
     9.378] (**) ImPS/2 Generic Wheel Mouse: (accel) acceleration factor: 2.000
     9.378] (**) ImPS/2 Generic Wheel Mouse: (accel) acceleration threshold: 4
     9.378] (II) config/udev: Adding input device ImPS/2 Generic Wheel Mouse (/dev/input/mouse0)
     9.378] (II) No input driver specified, ignoring this device.
     9.378] (II) This device may have been added with another device file.
     9.378] (II) config/udev: Adding input device PC Speaker (/dev/input/event4)
     9.378] (II) No input driver specified, ignoring this device.
     9.378] (II) This device may have been added with another device file.
    32.730] (II) NVIDIA(GPU-0): Display (Acer AL2016W (CRT-0)) does not support NVIDIA 3D
    32.730] (II) NVIDIA(GPU-0):     Vision stereo.
    32.730] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
    32.730] (**) NVIDIA(0):     device Acer AL2016W (CRT-0) (Using EDID frequencies has
    32.730] (**) NVIDIA(0):     been enabled on all display devices.)
hexdump@Corky-PC:~> 



do you want me to install kbuildsycoca ?

Sigh, it’s “kbuildsycoca4 --noincremental”. I forgot the ‘4’ when writing it again this time…

As mentioned already, you could also redirect the output to a file and then provide that file via http://susepaste.org or similar.

kbuildsycoca4 --noincremental >kbuildsycoca4.log

hexdump@Corky-PC:~> glxinfo | grep render
direct rendering: Yes
OpenGL renderer string: GeForce 7050 / nForce 620i/integrated/SSE2
GL_KTX_buffer_region, GL_NVX_conditional_render,
GL_OES_fbo_render_mipmap, GL_OES_get_program_binary, GL_OES_mapbuffer,
GL_OES_fbo_render_mipmap, GL_OES_get_program_binary, GL_OES_mapbuffer,
hexdump@Corky-PC:~>

Looks ok.

and /var/log/xorg… Note that I removed some of the earlier entries cause it was too big to post.

Well, in such a case it’s best to upload it to http://susepaste.org or similar and post a link.

But shouldn’t be necessary any more, the driver seems to work from what I can tell.

do you want me to install kbuildsycoca ?

No, that’s the KDE3 version and won’t help at all.

What you could still try is to wipe out /tmp/ and /var/tmp/ completely. Those only contain temporary files, so you shouldn’t lose anything.
For this, log into IceWM and run:

sudo rm -r /tmp/* /var/tmp/*

Then logout and reboot and try KDE4 again.

Were closer. I got to the desktop and my icons are there though some things are missing. Understandably so.

I got an error message again about the taskbar and sure enough it is not there.

Can you quickly tell me how to get the taskbar back ?

and thanks again for all your help.

Good. So it apparently was something in /tmp or /var/tmp.
You got a default desktop now.

I got an error message again about the taskbar and sure enough it is not there.

Can you quickly tell me how to get the taskbar back ?

It’s about the system tray, not the task bar. But you should have one in the default settings.

Anyway, I would suggest to rename back your old .kde4 to also get back all settings. After all, that wasn’t was caused the problem anyway.
You should do this outside of KDE though, so log in to IceWM a last time, delete the current ~/.kde4 folder, and rename your old one back to ~/.kde4.

When you then log back in to KDE, all should be as before.

Re the taskbar, I found out how to get it.