X broke --> after new intall KDE is slow

I have a Thinkpad X1 Carbon 20BS. I initially installed Tumbleweed into in using Tumbleweed with openSUSE-Tumbleweed-NET-x86_64-Snapshot20160916-Media.iso image. Everything worked smoothly until last week. After installing regular updates including new kernel, its X just crashed after typing in correct password. From text console I tried to run yast2 snapper, but it complained someting (unfortunately I don’t remember what), but result was I wasn’t able to restore to previous snapshot :(. / was btrfs, and /.snapshot contained stuff.

I tried reinstall. I first gave a shot for 42.2as fresh install, but it missed network after network install :O. This was strange, but I didn’t bother longer. I gave a shot for openSUSE-Tumbleweed-NET-x86_64-Snapshot20161202-Media.iso.

I did a fresh Tumbleweed KDE install. During boot it complains about Network Manager, Modem Manager and Bluetooth. They seem to start slowly. At least wired network works, though. It also complains may times about login service and nscd service failing. X session eventually starts and logging in is possible, but login screen (and lock screen) works only with US keyboard, even when console has Finnish keyboard defined and working. After logging in it takes ages and ages - at least 10 minutes for KDE session to start completely. From settings I must define to use Finnish keyboard despite I had selected Finnish keyboard during installation (this has never happened before). Keyboard behaviour is just an odd annoyance.

The worst thing is that all actions in KDE are slow. For example opening KDE menu from lower left corner Suse symbol takes 15 to 20 seconds. In KDE settings navigating between different settings is equally slow. Within individual settings changing settings might happen immediately, but usually it takes 10 to 15 seconds. Everything is very unresponsive. Still, I don’t see any high CPU activity, high memory usage nor high i/o activity.

What’s wrong? What can I test next? What has recently changed in Tumbleweed that may have caused this behaviour?

How do you update?

I don’t call fresh install using Tumbleweed network install USB stick an update, but a fresh install. I recreated and formatted all partitions, too.

Unfortunately I haven’t had time to try to fix that laptop until now.

KDE startup time is remarkably slow. Now laptop has been up 15 minutes, but KDE has not yet fully started :frowning:

I have now installed latest Tumbleweed updates (yast2 sw_singlePackagesAll packagesUpdate if newer version is available). Running kernel is now 4.8.14-1.

Some problems that still persist after reboot:
– KDE full startup takes 16 minutes from reboot (initial auto-login to X is enabled)
– KDE does offer neither shutdown nor reboot options
– Restoring from screen power saving (turned off screen) takes some 20–30 seconds
– Initially X uses US keyboard layout even when Linux console (vt) is using Finnish keyboad layout

  • After logging in at somepoint during KDE startup process keyboard layout changes to Finnish
    – As root from konsole reboot works but shutdown -r +0 gives an error
    Failed to connect to bus: No such file or directory
    Failed to connect to bus: No such file or directory
    Yes, error is repeated twice.
    – Bluetooth devices don’t work at all
    – Network Manager sees only wired connection
  • It does not see any Wi-Fi networks
  • Adding Mobile broadband connection failes with error about inablity to check authorization (message is shown too short time with too small font to read it all)
    – During bootup Bluetooth, Network Manager and Modem Manager delay boot 1 minute 30 seconds
    – Even before that boot proces shows several failures about login service.

I hope somebody could point me towards the root cause of all these issues. I do somehow believe, that all of these problems are somehow related to same root cause. I just don’t know where to look.

A comment to your problem listed first:
I initially also observed VERY slow start-up with recent Tumbleweed (but also Leap 42.2 on another machine). The reason was a process initializing the “file search” facility. This can be switched off in “Configure Desktop”, Search section. After that, everything was back to normal speed.

I finally managed to solve all problems – at once!

OpenSuse installation allows to create /tmp, /run, /var/lock and /var/run as tmpfs filesystems. However, systemd nowdays want that /var/run is a bind mount to /run.
⇒ Solution was to comment out /var/run tmpfs filesystem line from /etc/fstab and reboot.