13.2 problems during boot and after

I hope this is the right forum . . .
I have various problems since a recent opensuse update and/or a VirtualBox update.

Setup
13.2 opensuse previously running well. Vbox 5.1.14 (updated directly from vbox.org as usual), running W10 guest (which is working perfectly).

Symptoms
Plasma links fail (no type) after normal operation, same for other launchers including konsole, shutdown options fail, mouse fails. Open apps freeze. Obliged to crash manually.

Error msg seen first day:
“Unable to save bookmarks in /home/c_______n/.local/share/user-places.xbel. Reported error was: 5… This error message will only be shown once. The cause of the error needs to be fixed as quickly as possible, which is most likely a full hard drive.” However the home partition is only 8% occupied. I also see various “Input-output error” signs.

Happens on first or second wake-up from Sleep. Has occurred before, after core KDE updates. Usually fixes itself after shutdown and boot once or twice. This time it persists.

Actions taken
[LIST=|INDENT=1]
[li]I booted the last “recovery” image and got two error msg:[/li]```

[li]“Failed to start LSB: VirtualBox Linux Additions kernel modules.” See “systemctl status vboxadd.service” for details.[/li]```


[li]“Failed to start X Display Manager” See “systemctl status display-manager.service” for details.[/li]```

[/LIST]


[ul]
[li]Ran [/li]```
# systemctl status vboxadd.service

vboxadd.service - LSB: VirtualBox Linux Additions kernel modules
   Loaded: loaded (/etc/init.d/vboxadd)
   Active: failed (Result: exit-code) since Sat 2017-02-11 21:23:48 CET; 21min ago
  Process: 1005 ExecStart=/etc/init.d/vboxadd start (code=exited, status=1/FAILURE)

Feb 11 21:23:48 linux systemd[1]: vboxadd.service: control process exited, code=exited status=1
Feb 11 21:23:48 linux systemd[1]: Failed to start LSB: VirtualBox Linux Additions kernel modules.
Feb 11 21:23:48 linux systemd[1]: Unit vboxadd.service entered failed state.
Feb 11 21:23:48 linux vboxadd[1005]: Starting the VirtualBox Guest Additions ..failed
Feb 11 21:23:48 linux vboxadd[1005]: (modprobe vboxguest failed)

[/ul]

[ul]
[li]I have reinstalled Virtual Box, the extension pac and the latest guest additions in w10.[/li][/ul]
No change so far.
zypper verify is good
zypper up says “nothing to do”

zypper se -si vbox virtualbox
# zypper se -si vbox virtualbox
Loading repository data...
Reading installed packages...


S | Name                         | Type    | Version                     | Arch   | Repository          
--+------------------------------+---------+-----------------------------+--------+---------------------
i | VirtualBox-5.1               | package | 5.1.14_112924_openSUSE132-1 | x86_64 | (System Packages)   
i | virtualbox-guest-kmp-default | package | 5.0.30_k3.16.7_53-62.1      | x86_64 | openSUSE-13.2-Update
i | virtualbox-guest-tools       | package | 5.0.30-62.3                 | x86_64 | openSUSE-13.2-Update
i | virtualbox-guest-x11         | package | 5.0.30-62.3                 | x86_64 | openSUSE-13.2-Update


Vbox Manager insists the guest additions are correct and they work perfectly in the guest. For good measure I reinstalled the correct guest additions to be sure.

12,3 is no longer supported there are no new updates for several weeks.

So let’s make sure you are not mixing versions show zypper lr -d

I am running 13.2 on Lenovo laptop. My old Dell is fine but time to delete it from the signature. Sorry about the mess on the first post. I ran out of edit time and then the machine crashed.

# zypper lr -d
# | Alias               | Name                                           | Enabled | GPG Check | Refresh | Priority | Type   | URI                                                               | Service
--+---------------------+------------------------------------------------+---------+-----------+---------+----------+--------+-------------------------------------------------------------------+--------
1 | 13.2                | vbox Oct 2016                                  | No      | ----      | No      |   99     | rpm-md | http://download.virtualbox.org/virtualbox/rpm/opensuse/13.2       |        
2 | KDE_Qt5             | The Qt5 development repository (openSUSE_13.2) | Yes     | (r ) Yes  | Yes     |   99     | rpm-md | http://download.opensuse.org/repositories/KDE:/Qt5/openSUSE_13.2/ |        
3 | Packman_13.2        | Packman 13.2                                   | Yes     | (r ) Yes  | Yes     |   99     | rpm-md | http://ftp.gwdg.de/pub/linux/misc/packman/suse/openSUSE_13.2/     |        
4 | google-chrome       | google-chrome                                  | Yes     | (r ) Yes  | Yes     |   99     | rpm-md | http://dl.google.com/linux/chrome/rpm/stable/x86_64               |        
5 | repo-non-oss        | openSUSE-13.2-Non-Oss                          | Yes     | ( p) Yes  | Yes     |   99     | yast2  | http://download.opensuse.org/distribution/13.2/repo/non-oss/      |        
6 | repo-oss            | openSUSE-13.2-Oss                              | Yes     | ( p) Yes  | Yes     |   99     | yast2  | http://download.opensuse.org/distribution/13.2/repo/oss/          |        
7 | repo-update         | openSUSE-13.2-Update                           | Yes     | (r ) Yes  | Yes     |   99     | rpm-md | http://download.opensuse.org/update/13.2/                         |        
8 | repo-update-non-oss | openSUSE-13.2-Update-Non-Oss                   | Yes     | (r ) Yes  | Yes     |   99     | rpm-md | http://download.opensuse.org/update/13.2-non-oss/  

The virtual W10 is still running perfectly. Now I’m trying to eliminate possible sources of the problem, eg, Chrome. Is there some way I can test it? KDE is not loading properly or some app has a memory leak?

Try a different user. you may have corruption in the KDE configs

I haven’t tried your suggestion yet. The symptoms changed slightly: the launchers and other things function normally for about an hour after boot. Then they stop functioning about the same time. It seems like a memory leak, no? I thought those were part of the past. I also found the Chrome browser was updated a few days ago (to 56.0) and on the internet I found a lot of comments about memory issues with Flash. I checked Yast and found I had indeed installed Flash (probably FireFox suggested it). I removed Flash and black-listed:

zypper addlock pullin-flash-player

Things now are almost normal. I still see complaints about the vbox LSB in the boot record but I think they are unrelated or vbox has a minor bug.

So this might be solved. Thanks.

Probably not a configuration problem then if it works for a time.

run top or ksysguard and see if you use up memory over time

I miss typed 13.2 is EOL no updates for several weeks now.

Odd problem. :\ Be sure all fans are working and clear air flow

Thanks. ksysguard is perfect for this. Memory usage is low (1.9 / 15.6) and steady. I have 8 tabs open on Chrome, konsole, etc. Thanks for the tip about EOL. Time to Leap. This laptop has an unusually big cooling capacity with a huge vent on the side. :slight_smile: