KDE Crash is not a specific problem so there is nothing to fix. I’m not trying to be a smart @#$ saying this, this is the feedback I get from OM developers. Your using KDE desktop so saying KDE Crash is no more than saying “It Crash”. Devs keep telling me that to fix “It” they need some idea of what “It” is.
To find out what is crashing you would look at journal logs (journalctl) and see what is posted right before the crash. There might also be something in /var/log/Xorg.0.log or /var/log/Xorg.0.log.old. And a third place to look /home/<user_name>/.local/share/sddm/xorg-session.log where <user_name> is replace with your user name. As with journalctl you are looking for the most recent entries right before a crash.
To access journal of your current boot:
$ journalctl -b 0
To access journal of your mosr recent previous boot:
$ journalctl -b -1
Pay attention to anything that say “error” or any red lines as red lines are supposed to indicate most serious issues. But in general you look at everything posted in the 1 or 2 minutes before crash or freeze.
Note: To post journalctl logs or other logs more than say 20 lines please put them in a pastebin.com or similar and post a link to that here. And it is best to include the command you used (for journal) and all of the output. Devs may see something earlier in logs that point to an issue with a computer.
OK thanks for logs. I haven’t had time to read them yet. Developers are all tied up with the conversion from urpmi to dnf for OM Lx 4 release. So users need to do everything possible to narrow down problems in order get things fixed.
An unfortunate consequence of an all volunteer community distro with a small community.
We do have more people developing than we did a year ago so there is progress on that front. But it is still to small of a group to do everything we wish we could. Same for QA-Team which has not grown and suffers even more from a lack of people involved.
I’m going to say again for about the 20th time that KDE/Plasma5 desktop crashing is very likely, almost certainly, an upstream issue. It would be faster to take questions about this to KDE.org and talk to KDE developers.
The fact that we are still seeing reports and bug reports about this at KDE.org and in other distros tells us that one heck of lot more developers than OpenMandriva has have looked at and not solved these issues.
Note: Lest anyone think I’m preaching or criticizing remember that I have these issues some times also.
I have asked will reply as soon as I get something.
Also it is possible you and I do have exactly the same issue as I don’t show any plasmashell coredumps. But I’ll keep plugging away at this form time to time as time allows. One difference may be that I have Intel graphics and yours I believe is nVidia.
Another question born of curiosity. If you run:
# urpme --auto-orphans
does that show and packages for removal? If so how many? I’m not asking you to actually run it just start it and see what it says and select ‘N’ for no if you do not want to run it.
From what I’m seeing the debug packages needed probably have to be built. Using my system as an example:
$ coredumpctl gdb 5950
#0 0x00007fe6e409de87 in raise () from /lib64/libc.so.6
#1 0x00007fe6e409f7f1 in abort () from /lib64/libc.so.6
#2 0x00007fe6e466f467 in QMessageLogger::fatal(char const*, ...) const () from /usr/lib64/libQt5Core.so.5
#3 0x00007fe6dc0d0758 in QXcbConnection::QXcbConnection(QXcbNativeInterface*, bool, unsigned int, char const*) () from /usr/lib64/libQt5XcbQpa.so.5
#4 0x00007fe6dc0d4d88 in QXcbIntegration::QXcbIntegration(QStringList const&, int&, char**) () from /usr/lib64/libQt5XcbQpa.so.5
#5 0x00007fe6e65363ca in ?? () from /usr/lib64/qt5/plugins/platforms/libqxcb.so
#6 0x00007fe6e4b641db in ?? () from /usr/lib64/libQt5Gui.so.5
#7 0x00007fe6e4b63d53 in QPlatformIntegrationFactory::create(QString const&, QStringList const&, int&, char**, QString const&) () from /usr/lib64/libQt5Gui.so.5
#8 0x00007fe6e4b6c8f4 in QGuiApplicationPrivate::createPlatformIntegration() () from /usr/lib64/libQt5Gui.so.5
#9 0x00007fe6e4b6d0e5 in QGuiApplicationPrivate::createEventDispatcher() () from /usr/lib64/libQt5Gui.so.5
#10 0x00007fe6e47c38a1 in QCoreApplicationPrivate::init() () from /usr/lib64/libQt5Core.so.5
#11 0x00007fe6e4b6a5ee in QGuiApplicationPrivate::init() () from /usr/lib64/libQt5Gui.so.5
#12 0x00007fe6e4fe92b9 in QApplicationPrivate::init() () from /usr/lib64/libQt5Widgets.so.5
#13 0x000000000041c4c8 in ?? ()
#14 0x00007fe6e4081a37 in __libc_start_main () from /lib64/libc.so.6
#15 0x000000000041b7ba in _start ()
So the to investigate we probably need these debug packages: