16.04 is becoming more stable, kind of...

[TWPonKubuntu]

However:

PLasma still crashes, frequently (every 2 to 10 minutes) and eventually locks totally, forcing a hard shutdown and manual reboot. It has crashed three times while I composed this post.

The crash reporter will NOT accept my information and refuses to send a crash report... Which is frustrating...

I'm also getting this error message, frequently:

KDEInit could not launch '/usr/lib/i386-linux-gnu/libexec/kf5/kdesu'

and the file: 'kdesu' does not exist on the given path.

On the Plus side, the problems with a memory leak appear to have been solved, as physical memory (RAM) usage is now stable rather than slowly increasing.

Also the video driver no longer "tears" my screens. This is under a plain vanilla install from the latest download, so that problem appears to be solved.

[MoonRise]

Yeah, the crashes I was getting was with KWIN and I can't say quite regular but to the point that you do notice, especially when the crash report tells you that. At least 4 or 5 times a day. Does the same in NEON so I'm assuming Plasma5 to some extent is at the root of why. Maybe even them trying to get Wayland in?

[Snowhog]

I have no crashes in 16.04 or KDE neon; none.

[MoonRise]

Some of it I beleive is the graphics driver but never really dug in yet to see but same crash in 16.04 Kubuntu and Neon User on 16.04 Ubuntu. I haven't looked as it recovers (KWIN) by itself so not too annoying yet.

[TWPonKubuntu]

RE Plasma crashing, yes it does "recover" for about the first 10-15 crashes (I haven't counted) but then it freezes, forcing the hard reboot. This is the current major "show stopper" for my use (32bit system).

I'm not yet ready to move my code development to this system... Perhaps next year. Until then I'll use 14.04 LTS.

[GreyGeek]

My experience with Neon on top of Kubuntu 16.04 mirrors that of Snowhog's. No crashes of Plasma5 at all. The only unstable app I am using is FireFox, which is due entirely to the container plugin. When FF hangs I open Ksysmonitor and end the container plugin. FF responds immediately and the only two plugins (openH264 and pepperflash) reload when called. The latest Tor version of FF is very fast and very stable because it has no plugins yet still plays YouTube videos very well.

[MoonRise]

As I said I think mine is related to Nvidia driver. The below just occurred and is the same type error as past ones. As I said, no biggie right now. This is the 3 for the day. If I'm on it a little longer, maybe 2 more?

Application: KWin (kwin_x11), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7ff588527940 (LWP 3260))]


Thread 1 (Thread 0x7ff588527940 (LWP 3260)):
[KCrash Handler]
#6  0x00000000412c098f in ?? ()
#7  0x00007ff57821c2c0 in ?? () from /usr/lib/nvidia-340/libnvidia-glcore.so.340.96
#8  0x00007ff578223350 in ?? () from /usr/lib/nvidia-340/libnvidia-glcore.so.340.96
#9  0x00007ff577e90378 in ?? () from /usr/lib/nvidia-340/libnvidia-glcore.so.340.96
#10 0x00007ff586539c36 in QOpenGLTextureGlyphCache::resizeTextureData(int, int) () from /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5
#11 0x00007ff5864d7dfa in QTextureGlyphCache::fillInPendingGlyphs() () from /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5
#12 0x00007ff580c6c468 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#13 0x00007ff580c6a30c in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#14 0x00007ff580cf1ac7 in QQuickTextNode::addGlyphs(QPointF const&, QGlyphRun const&, QColor const&, QQuickText::TextStyle, QColor const&, QSGNode*) () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#15 0x00007ff580cf674c in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#16 0x00007ff580cf2a1f in QQuickTextNode::addTextLayout(QPointF const&, QTextLayout*, QColor const&, QQuickText::TextStyle, QColor const&, QColor const&, QColor const&, QColor const&, int, int, int, int) () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#17 0x00007ff580cf1479 in QQuickText::updatePaintNode(QSGNode*, QQuickItem::UpdatePaintNodeData*) () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#18 0x00007ff580caec80 in QQuickWindowPrivate::updateDirtyNode(QQuickItem*) () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#19 0x00007ff580caf4eb in QQuickWindowPrivate::updateDirtyNodes() () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#20 0x00007ff580cb0580 in QQuickWindowPrivate::syncSceneGraph() () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#21 0x00007ff580d9410a in QQuickRenderControl::sync() () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#22 0x00007ff565e9b170 in ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/org.kde.kdecoration2/kwin5_aurorae.so
#23 0x00007ff585ef9f36 in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#24 0x00007ff585f064e8 in QTimer::timerEvent(QTimerEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#25 0x00007ff585efaa93 in QObject::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#26 0x00007ff5867ba89c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#27 0x00007ff5867c2296 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#28 0x00007ff585eceda8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#29 0x00007ff585f2123e in QTimerInfoList::activateTimers() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#30 0x00007ff585f1f218 in QEventDispatcherUNIX::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#31 0x00007ff56ede287d in ?? () from /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
#32 0x00007ff585eccd9a in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#33 0x00007ff585ed53ac in QCoreApplication::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#34 0x00007ff5882f7206 in kdemain () from /usr/lib/x86_64-linux-gnu/libkdeinit5_kwin_x11.so
#35 0x00007ff587f45830 in __libc_start_main (main=0x400710, argc=1, argv=0x7ffc51655118, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7ffc51655108) at ../csu/libc-start.c:291
#36 0x0000000000400749 in _start ()

[TWPonKubuntu]

Hmmm, looks like your 64bit versions avoid the problem. Mine is 32bit.

Neon is limited to 64bit only, so I cannot test that.

Plasma crashed TWICE again during the writing of this post...

The error reported by the crash reporter:
Executable: plasmashell PID: 3604 Signal: Aborted (6) Time: 8/7/16 15:25:32
Not very helpful to me.

[MoonRise]

Much different from my issue. I actually just looked at Bug reports similar to mine but nothing there that was the same issue or solved for that mater.

[jglen490]

At first i had a lot of crashes - apparently. But more often than not the "crashed" application never really died. I haven't had a crash in almost a week. I'm declaring victory. Maybe the most recent dist-upgrade fixed some initial problems.

Now, I don't ever mess with a stock install - maybe (rarely) an outside program or two. I certainly don't see the point in topping 16.04.1 with something like Neon. I'm not sure that doesn't cause more problems than solutions - again, just based on some posts I'm seeing here.

Some people have no problems, and in fact have some sort of gain. Others have nothing but problems. Mixing up parts can't both be correct and incorrect at the same time. The only thing I want is a stable, reasonably featured computing platform that makes economic sense (no MS Windows!). I do not experiment

Right now I'm liking Xenial, a lot.

[TWPonKubuntu]

My "crashes" are strictly limited to the Plasma Desktop itself, with any other running apps generally not being effected (they continue to run in the background while Plasma restarts itself).

As I said in my prior comments to this thread, Plasma will crash regularly, and restart itself, for about 10-15 cycles and then it locks totally and I must do a hard reboot.

Whlle I find 16.04 to be better now than in the immediate past few weeks, it still has some problems which make it undesirable to use for code development. I don't want to risk losing my work to an untimely Plasma crash.

Plasma crashed and restarted twice while I wrote this post...

[GreyGeek]

Well, user experiences can very with the type of hardware Xenial is run on, as is the case with all distros, but the number of problems being reported are far less than what I would have suspected for a distro that changed both the major version level AND the Qt API at the same time. For me Xenial is running TWICE as fast as Trusty and is as stable as Trusty was for me. I dreaded this update for the reasons listed above and even switched to Mint's KDE, but returned because Kubuntu was better. I've been pleasantly surprised by Xenial.

[acheron]

In contrast while I was running Xenial, I had more rare crashes on a laptop with Intel HD graphics than on this Nvidia graphics machine.

Xenial was/is very stable overall for me.

[oshunluvr]

I'm still getting desktop lockups from nvidia drivers later than 340. But they've gotten farther apart - I can get 4-5 hours between lockups.

[jglen490]

I'm still getting desktop lockups from nvidia drivers later than 340. But they've gotten farther apart - I can get 4-5 hours between lockups.

Just curious, does ubuntu-drivers devices show an nvidia driver later than 340 as being recommended for your installation?