What in the world is this? It has been several years since I have used KDE, but I don’t remember getting this kind of issue ever. Not that there were rolling release distros back then. I always had to install/upgrade by CD and compile-from-source for apps where I needed to use the latest.
** This is the full error:
Unable to create io-slave. klauncher said: Error loading '/usr/lib64/qt5/plugins/kf5/kio/destop.so
**
This message appeared after I updated earlier today. I rebooted my laptop after the update was done since I was also trying to fix the laptop screen brightness and had to change the kernel boot params. Then bam!
Ok a little background. New install. Just over the past weekend. I’m using Tumbleweed 20171007. Well, originally it was a Leap 42.3 install. By mistake. I intended to install TW and downloaded Leap instead. Silly me. And since it’s almost a 5GB download, I wanted to avoid another one. I learned that Leap can be easily switched to TW, and vice-versa. So that’s what I did. Previous update didn’t cause any issues.
UPDATE: After searching for answers last night I stumbled upon something where it mentioned that it was am incompatible libmodman package that was installed on the system that was causing havoc. So I gave it a shot with this package - http://download.opensuse.org/tumbleweed/repo/oss/suse/x86_64/libmodman1-2.0.1-17.9.x86_64.rpm. Note to others who encounter the same problem as I did and want to try this out: the link above can change all the time due to version changes. The one I had on my system, assuming it was from after that stupid update, was libmodman1-2.0.1-18.*
Thankfully it did fix my issue and my desktop is now back to normal. This might be a temporary fix. I don’t know what package dependencies were broken after I forced the libmodman package to another version. It’s a minor version change only so I hope this does not break a lot of things. Except that now I have noticed that I am getting a couple of errors when I open Yast Package Manager. These errors were not there before.
Hi tannington,
To answer your questions:
The update was performed from the Software Updates applet located @ the system tray. The update successfully finished and there were no error messages. On next reboot all hell broke loose.
With Tumbleweed the only recommended way to perform an update is to log out from any desktop environment, then from a virtual terminal use “zypper dup”, updates by any other method may fail. There are numerous threads on these forums explaining the reasons…
I have the following in my /etc/zypp/repos.d dir:
All just fine, I was unsure what you may have had enabled.
It would be a good idea to perform a “zypper dup” to ensure that you have all of the correct packages, (simply doing that may have solved your original problem).
With Tumbleweed the only recommended way to perform an update is to log out from any desktop environment, then from a virtual terminal use “zypper dup”, updates by any other method may fail. There are numerous threads on these forums explaining the reasons…
Seriously? I don’t get it. Lol! Is this common for rolling release distros? For Arch is it the same way?
All just fine, I was unsure what you may have had enabled.
I looked these up thoroughly before I made the repo switch. Almost a lot of people said the same thing that these 4 repos should be enough to switch from Leap to TW. I’ll probably give it another zypper dup today like you said. Or since it is still a fairly new install, I could just be patient and download the correct image for TW and reinstall from scratch.
“zypper dup”, or as you may see advised “zypper dup --no-allow-vendor-change” (the “–no-allow-vendor-change” has recently became a default so only “zypper dup” needed now), is the only way to go. Using YAST, the Update Applet, or a “zypper up” will, at some point result in a broken system.
(Whilst you can issue “zypper dup” from KDE’s konsole (or Gnomes equivalent) within a running x session it is safer to execute from a virtual terminal.)
Is this common for rolling release distros? For Arch is it the same way?
Sorry, don’t know, on both counts. TW is the only rolling release I’ve used, perhaps others will chime in.
Thanks guys! Appreciate the help. It’s okay now. Honestly, this is so inconvenient having to logout and update because updating by any other means is “broken”. Those nice GUIs are all for nothing I suppose.
What would be the LTS equivalent for opensuse? It would be Leap, yes? I think I don’t really need bleeding edge. I just want an updated browser (FF). And play video/audio files. Netflix of course. And so far FF fails to do so even if the version I have is 56. Could be I have to change some other settings even if DRM is already enabled. Just didn’t bother to tinker around and switched to Chrome. Would love to use less of Chrome.
It was more of a rhetorical question. I’m aware that distros have different update methods.
Well… if you want to use Tumbleweed that’s the way it is
Each new snapshot issued is regarded as a “Distribution Upgrade”. It’s not a case of the GUI method being “broken”, “zypper dup” from the command line is the (only correct) way to perform a distribution upgrade.
What would be the LTS equivalent for opensuse? It would be Leap, yes? I think I don’t really need bleeding edge.
Leap, the new name for “openSUSE”, has a lifetime of 36 months for each major release. Lifetimes are detailed here: Lifetime - openSUSE Wiki
I just want an updated browser (FF). And play video/audio files. Netflix of course. And so far FF fails to do so even if the version I have is 56. Could be I have to change some other settings even if DRM is already enabled. Just didn’t bother to tinker around and switched to Chrome. Would love to use less of Chrome.
If you have problems with Firefox then that would probably be better addressed in a new thread. I’m currently using V56 on Tumbleweed and don’t have any problems, but I don’t use it for audio/video. Incidentally, as you may well know, the version of FF on Leap 42.3 is 52.4.0 LTS.
I don’t get it. Lol! Is this common for rolling release distros? For Arch is it the same way?
…