Tumbleweed release:20170913
KDP Plasma version: 5.11.90
KDE Framwork: 5.39.0
Qt version: 5.9.1
OS: 64-bit
Kernel: Linux linux-5jug 4.13.1-1-default #1 SMP PREEMPT Sun Sep 10 12:02:44 UTC 2017 (0d725b5) x86_64 x86_64 x86_64 GNU/Linux
First of all it seems that Plasma is not stable. After boot it seems ok, but after some time is seems like Plasma is crashing. Desktop become black (background goes black), main taskbar disappeare, but system seems still running. I can ALT-F2 and start apps from there. To reboot i do CTRL-ALT-DEL and then i get the Logout, Shutdown and Reboot-screen.
After reboot everything seems ok again.
Then i can’t run Software Manager og Packet Repository Manager from Yast2. Don’t get any error-msg. It just won’t start.
So i tried to do “zypper dup --no-allow-vendor-change”
i get allot of error about problem upgrading some packages and is recommended to install another version. I choose recommended installation and then it do the upgrade. After reboot the system goes wild.
GUI don’t start and console is flashing. Harddrive is constantly working. I try to login to console, but it want registre all key-press so i can’t enter password correctly. After a long time trying entering password for Superuser, i manage to get in. I did so a Snapper rollback and now it is working again, but with all the same problem with Plasma.
I really don’t know how to fix this and need help.
Tumbleweed currently has Plasma 5.10.5 and KDE Frameworks 5.37.0.
And actually neither Plasma 5.11 nor KDE Frameworks 5.39.0 are released yet, KF 5.38 has just been released last weekend and Plasma 5.11.0 is in Beta currently.
You are obviously using the Unstable repos, which means you have to be prepared to experience problems.
Please post your repo list:
zypper lr -d
But basically you should probably remove/disable all additional repos (other than the two standard ones) and run “sudo zypper dup --allow-vendor-change” to get a stable system.
OTOH, at least some of your problems might be related to the kernel update I suppose, so try to boot the previous one and see whether it helps.
And then you are surprised that you have problems? :\
As I said, remove all these additional repos (especially the unstable ones including “Kernel:HEAD” which is the latest unstable kernel) and run “zypper dup --allow-vendor-change” to switch back to a standard Tumbleweed system. #14-20 are fine, the rest should be deleted (unless you know what you are doing)
KDE:Qt57 in particular is nonsense anyway and can only cause problems.
And having the installation medium as repo does not really make much sense with Tumbleweed either, unless you re-download it every time a new snapshot is published.
Yes.
Although I have no idea what is contained in those home:scalpel4k and [noparse]home:pontostroy:X11 repos.[/noparse]
If you have no good reason to use them, it’s probably better to remove them too, especially replacing X11 related stuff can induce instability…
Other remarks:
You don’t really need to add devel projects to Tumbleweed.
It’s Tumbleweed’s main point to always get the latest versions in the main repo, they will appear there just a few days later normally, after testing.
These include Printing (which is disabled anyway though) and devel:gcc, you might just remove them (though they shouldn’t cause problems for the rest of the system, although devel:gcc does contain the glibc runtime library that’s used by basically everything).
You don’t need repo #4, as it is exactly the same as #10.
home:namtrac:clang doesn’t seem to exist any more, so better remove it too.
In general, the less repos you use, the better, especially on Tumbleweed.
Only add repos if you need them (and know what they contain).
On Repository I would like to make a small note.
Using Click Install Sometimes there is some problem with the Repository and even if you choose not to keep it, sometimes it adds it too
Ok, here is my latest update!
After cleaning up repos og run zypper dup --no-allow-vendor-change, my system broke completly down. I only boot up in Rescue Console. Keyboard-setup was messed up.
I decide to reinstall the system from scratch.
Downloaded latest media (13.sep 2017) and format / (root) og kept /home
It boots up as normal, but KDE was very unstable. Unlock-screen crash and i couldnt unlock screen. I had to reboot to make it work again. Then KDE stop executing anything. I couldnt start any apps. CTRL-ALT-DEL didn’t work anymore. Nothing worked.
Now i reinstall everything. I format /home and now its a clean install.
It works better. No crash! No KDE-problems.
I don’t dare to execute Zypper Update. I’m afraid i will crash my system again :-o
At work i use LEAP (42.2) and i’m very satisfied with it. No problem at all. At home i try TW because i don’t have any important on the computer and only use it for web-browsing and daily use tasks. Now its working good. No problem since last installation. If i execute zypper update and brake it again, then i will change to LEAP.
Just in case it isn’t clear already though:
You should use “zypper dup” to update a Tumbleweed system, not “zypper up(date)”. The latter can actually break your system on certain occasions.
Btw, I told you to run “zypper dup --allow-vendor-change” after removing the repos, but you apparently ran “zypper dup --no-allow-vendor-change” (according to your previous post).
That might have contributed to your system breaking down.
The point was to make sure that all packages come from the repositories that are still configured, and not still from the ones you deleted. A vendor change is crucial here.
Thanks for the information! Sometimes i get confused because i read about different advices. I’ve read that you should NOT use --allow-vendor-change, and i just tought you misspelled
So the advice for TW is til NOT use zupper update, but insted use “zypper dup --allow-vendor-change”.
Can you confirm this?
