What is your daily dose of KDE crashes?

CPU is Intel i7-3***. There is no GPU on the dye. Has four cores. Hyperthreading is disabled. I have worked, though much less, in Windows in the same computer with Nvidia driver installed. Don’t remember crashes. I have no reasons to suspect a defect in RAM.

The graphics card is a low-powered Nvidia, not ancient. Installation of the latest driver from Nvidia’s web site went without problems.

RAM is 16 GB. Swap’s size is 22 GB.

I update both by running Apper and via Yast. Usually I run one of them once a day, manually. I will add ‘zypper update’ into the routine.

Crashes happened, for example, when I was:

  • Adjusting sound level.
  • Configuring Panel (crashed twice).
  • Started an application which tried to create its window. (This crash was not deadly.)

My frequency of kwin crashes these days (December 2016) is around 2 per day.

Most of the crashes occur when an application opens a window, or when several windows are going to be created by an application.

Luckily, most of the crashes are not deadly, meaning there is no need to reboot.

Interesting is to compare this with the crash rates of other applications:

  • Audacity, almost 2 per use (big, complex tasks).
  • Firefox, 0 or 1 per day.
  • Text editors (Kate, LibreOffice) - none.
  • Gimp - none.
  • Simple apps like calculator - none.
  • Photo viewers - 1 per day.
  • Media players: several per day, but may be because of media files.
  • Skype - 2 per hour of use.
  • Ksysguard - none per day.
  • Gparted - none.
  • Printer monitor from HP - 1 per day.
  • Command-line tools (fdisk, dd, mount, pico, gmake) - none per day.
  • Acroread - 1 at start, 1 per long use or 1 per hour.

Most of these rates are the same over years.

Perhaps I jump in here.
Thinkpad R61 7733 - Ten years old but works good.
I have a few crashes here and there every hour or so…


Storage:
    Disk Drive    INTEL SSDSC2BW120A4  (120 GB, SATA-III) (custom bios to enable full SATA-III speed)
    SMART Hard Disks Status    OK
 Processors / Intel(R) Core(TM)2 Duo CPU T8100 @ 2.10GHz ] (soon replaced with T9500)
    Chipset Properties:     Intel Crestline-GM GM965
    Memory Slots:            DRAM Slot #1  4 GB (DDR2 SDRAM) DRAM Slot #2  1 GB (DDR2 SDRAM)
    Memory Timings      5-5-5-15 (CL-RCD-RP-RAS)
    Graphics Processor Properties:
    Video Adapter      Intel GL960/GM965 Chipset - Graphics Controller 0
    GPU Code Name      Crestline-GM (Integrated 8086 / 2A02, Rev 0C)

Gpu drive.


user@linux-9egv:~>  /sbin/lspci -nnk | grep VGA -A2
00:02.0 VGA compatible controller [0300]: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (primary) [8086:2a02] (rev 0c)
        Subsystem: Lenovo ThinkPad T61/R61 [17aa:20b5]
        Kernel driver in use: i915
user@linux-9egv:~>

Partitions: (swap)


user@linux-9egv:~> lsblk
NAME                                        MAJ:MIN RM   SIZE RO TYPE  MOUNTPOINT
sda                                           8:0    0 111,8G  0 disk  
├─sda1                                        8:1    0   399M  0 part  /boot
└─sda2                                        8:2    0 111,4G  0 part  
  └─cr_ata-INTEL_SSDSC2BW120A4_CVDA344501PF1207GN-part2
                                            254:0    0 111,4G  0 crypt
    ├─system-swap                           254:1    0     2G  0 lvm   [SWAP]
    ├─system-root                           254:2    0    10G  0 lvm   /var/lib/machines
    └─system-home                           254:3    0    25G  0 lvm   /home
sr0                                          11:0    1  1024M  0 rom  
user@linux-9egv:~>

All is updated via zypper update.

I had a fair bit of lockups when writing in the thread “How do I set acceleration on “TPPS/2 IBM TrackPoint” ?” and when I started writing this. Atm Im in xfce instead. I don’t know what fails when the whole session locks. I had a total lockup a few minutes ago when starting a terminal.
I manually triggered a crash by starting firefox opening a terminal closing it open it. Opened dolphin and I got a crash.
Yet not a full lockup. It happens randomly so I cant trigger it with a specific task.

Dump:


kwin_x11 PID: 2097 Signal: Segmentation fault (11) Tid: 2016-12-20 15:02:35

Application: Kwin (kwin_x11), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fba24904940 (LWP 2097))]

Thread 6 (Thread 0x7fba035ef700 (LWP 2464)):
#0  0x00007ffe855a7b62 in clock_gettime ()
#1  0x00007fba24078806 in clock_gettime () from /lib64/libc.so.6
#2  0x00007fba215d3826 in ?? () from /usr/lib64/libQt5Core.so.5
#3  0x00007fba21739989 in QTimerInfoList::updateCurrentTime() () from /usr/lib64/libQt5Core.so.5
#4  0x00007fba21739f05 in QTimerInfoList::timerWait(timespec&) () from /usr/lib64/libQt5Core.so.5
#5  0x00007fba2173958a in QEventDispatcherUNIX::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQt5Core.so.5
#6  0x00007fba216e8fdb in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQt5Core.so.5
#7  0x00007fba21523f1a in QThread::exec() () from /usr/lib64/libQt5Core.so.5
#8  0x00007fba1c1159b8 in ?? () from /usr/lib64/libQt5Qml.so.5
#9  0x00007fba215289e9 in ?? () from /usr/lib64/libQt5Core.so.5
#10 0x00007fba2432d734 in start_thread () from /lib64/libpthread.so.0
#11 0x00007fba2406bd3d in clone () from /lib64/libc.so.6

Thread 5 (Thread 0x7fb9ee5c8700 (LWP 2302)):
#0  0x00007fba243320af in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0
#1  0x00007fba206be93b in ?? () from /usr/lib64/libQt5Script.so.5
#2  0x00007fba206be969 in ?? () from /usr/lib64/libQt5Script.so.5
#3  0x00007fba2432d734 in start_thread () from /lib64/libpthread.so.0
#4  0x00007fba2406bd3d in clone () from /lib64/libc.so.6

Thread 4 (Thread 0x7fba02bcf700 (LWP 2264)):
#0  0x00007ffe855a7b62 in clock_gettime ()
#1  0x00007fba24078806 in clock_gettime () from /lib64/libc.so.6
#2  0x00007fba215d3826 in ?? () from /usr/lib64/libQt5Core.so.5
#3  0x00007fba21739989 in QTimerInfoList::updateCurrentTime() () from /usr/lib64/libQt5Core.so.5
#4  0x00007fba21739f05 in QTimerInfoList::timerWait(timespec&) () from /usr/lib64/libQt5Core.so.5
#5  0x00007fba2173958a in QEventDispatcherUNIX::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQt5Core.so.5
#6  0x00007fba216e8fdb in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQt5Core.so.5
#7  0x00007fba21523f1a in QThread::exec() () from /usr/lib64/libQt5Core.so.5
#8  0x00007fba1c1159b8 in ?? () from /usr/lib64/libQt5Qml.so.5
#9  0x00007fba215289e9 in ?? () from /usr/lib64/libQt5Core.so.5
#10 0x00007fba2432d734 in start_thread () from /lib64/libpthread.so.0
#11 0x00007fba2406bd3d in clone () from /lib64/libc.so.6

Thread 3 (Thread 0x7fba09166700 (LWP 2178)):
#0  0x00007ffe855a7b62 in clock_gettime ()
#1  0x00007fba24078806 in clock_gettime () from /lib64/libc.so.6
#2  0x00007fba215d3826 in ?? () from /usr/lib64/libQt5Core.so.5
#3  0x00007fba21739989 in QTimerInfoList::updateCurrentTime() () from /usr/lib64/libQt5Core.so.5
#4  0x00007fba21738dd1 in QEventDispatcherUNIXPrivate::doSelect(QFlags<QEventLoop::ProcessEventsFlag>, timespec*) () from /usr/lib64/libQt5Core.so.5
#5  0x00007fba21739527 in QEventDispatcherUNIX::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQt5Core.so.5
#6  0x00007fba216e8fdb in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQt5Core.so.5
#7  0x00007fba21523f1a in QThread::exec() () from /usr/lib64/libQt5Core.so.5
#8  0x00007fba1b2f61d5 in ?? () from /usr/lib64/libQt5DBus.so.5
#9  0x00007fba215289e9 in ?? () from /usr/lib64/libQt5Core.so.5
#10 0x00007fba2432d734 in start_thread () from /lib64/libpthread.so.0
#11 0x00007fba2406bd3d in clone () from /lib64/libc.so.6

Thread 2 (Thread 0x7fba0b044700 (LWP 2131)):
#0  0x00007fba2406349d in poll () from /lib64/libc.so.6
#1  0x00007fba231ea3e2 in ?? () from /usr/lib64/libxcb.so.1
#2  0x00007fba231ebfcf in xcb_wait_for_event () from /usr/lib64/libxcb.so.1
#3  0x00007fba0bcf4839 in ?? () from /usr/lib64/libQt5XcbQpa.so.5
#4  0x00007fba215289e9 in ?? () from /usr/lib64/libQt5Core.so.5
#5  0x00007fba2432d734 in start_thread () from /lib64/libpthread.so.0
#6  0x00007fba2406bd3d in clone () from /lib64/libc.so.6

Thread 1 (Thread 0x7fba24904940 (LWP 2097)):
[KCrash Handler]
#6  0x00007fba1c101dd0 in QQmlBinding::write(QQmlPropertyData const&, QV4::Value const&, bool, QFlags<QQmlPropertyPrivate::WriteFlag>) () from /usr/lib64/libQt5Qml.so.5
#7  0x00007fba1c10324a in QQmlBinding::update(QFlags<QQmlPropertyPrivate::WriteFlag>) () from /usr/lib64/libQt5Qml.so.5
#8  0x00007fba1c10c2f6 in ?? () from /usr/lib64/libQt5Qml.so.5
#9  0x00007fba1c09a93b in QQmlComponentPrivate::complete(QQmlEnginePrivate*, QQmlComponentPrivate::ConstructionState*) () from /usr/lib64/libQt5Qml.so.5
#10 0x00007fba1c09a9f7 in QQmlComponentPrivate::completeCreate() () from /usr/lib64/libQt5Qml.so.5
#11 0x00007fba1c09a880 in QQmlComponent::create(QQmlContext*) () from /usr/lib64/libQt5Qml.so.5
#12 0x00007fba0805e7cf in ?? () from /usr/lib64/qt5/plugins/org.kde.kdecoration2/kwin5_aurorae.so
#13 0x00007fba23c8f047 in ?? () from /usr/lib64/libkwin.so.5
#14 0x00007fba23b73891 in KWin::Client::createDecoration(QRect const&) () from /usr/lib64/libkwin.so.5
#15 0x00007fba23b745ab in KWin::Client::updateDecoration(bool, bool) () from /usr/lib64/libkwin.so.5
#16 0x00007fba23bd5ed6 in KWin::Client::manage(unsigned int, bool) () from /usr/lib64/libkwin.so.5
#17 0x00007fba23b57994 in KWin::Workspace::createClient(unsigned int, bool) () from /usr/lib64/libkwin.so.5
#18 0x00007fba23bc40e0 in KWin::Workspace::workspaceEvent(xcb_generic_event_t*) () from /usr/lib64/libkwin.so.5
#19 0x00007fba216e8270 in QAbstractEventDispatcher::filterNativeEvent(QByteArray const&, void*, long*) () from /usr/lib64/libQt5Core.so.5
#20 0x00007fba0bcf2be4 in QXcbConnection::handleXcbEvent(xcb_generic_event_t*) () from /usr/lib64/libQt5XcbQpa.so.5
#21 0x00007fba0bcf4c3b in QXcbConnection::processXcbEvents() () from /usr/lib64/libQt5XcbQpa.so.5
#22 0x00007fba21716166 in QObject::event(QEvent*) () from /usr/lib64/libQt5Core.so.5
#23 0x00007fba223f1e3c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib64/libQt5Widgets.so.5
#24 0x00007fba223f649a in QApplication::notify(QObject*, QEvent*) () from /usr/lib64/libQt5Widgets.so.5
#25 0x00007fba216eafc5 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib64/libQt5Core.so.5
#26 0x00007fba216ecdaa in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /usr/lib64/libQt5Core.so.5
#27 0x00007fba217394b4 in QEventDispatcherUNIX::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQt5Core.so.5
#28 0x00007fba0bd5694d in ?? () from /usr/lib64/libQt5XcbQpa.so.5
#29 0x00007fba216e8fdb in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQt5Core.so.5
#30 0x00007fba216f0ec6 in QCoreApplication::exec() () from /usr/lib64/libQt5Core.so.5
#31 0x00007fba2454b9cc in kdemain () from /usr/lib64/libkdeinit5_kwin_x11.so (will be
#32 0x00007fba23fa26e5 in __libc_start_main () from /lib64/libc.so.6
#33 0x0000000000400809 in _start ()

I love kde but perhaps I have to abandon it for now. All other desktops works fine. XFCE Mate and Cinnamon.

I found this post fun.

I run TW with Plasma on an old laptop. The TW is always on the latest snapshot. But I only encountered a few of KDE crashes. It’s no more than 5 in a month, I guess. Maybe the reason is I do not use too many apps, or to say that I am not doing much with my laptop :slight_smile:

mm could be…or tumbleweed received/receives bugfixes related to these crashes and leap not? At least not yet? I’m writing this in a text document and saving to be sure that the session won’t lockup and I have to start all over again writing this post as it happened tens of times already.
I came back to this machine and kde keyring somehow decided to throw me out from my network sometime during the last hours…closed the root prompt and the network password prompt came up. Closed it. Clicked the wifi icon and it connected without the need for a password. Weird.
Now I can’t close the start menu…jesus…kde 5 is a mess…opensuse is rock solid if I run any of the other desktops other than kde.
I might try to get kde 4 on this. Its possible but takes some work. I’m just testing stability and configs how it works before I set this machine to its final state.

Yup, it’s weird because Leap should be more stable than TW. Anyway, it should not be so suck. BTW, have you tried to do a fresh install of your OS in some virtual machine to test whether the problems are caused by 3rd part apps or settings being messed up or not.

yes I did test leap in a in a virtual machine and kde was probably as unstable there as here. Even though I discovered more bugs on this machine due to longer testing. I noticed changing theme seemed to cause crashes so I reverted to stock opensuse branding theme.
I will do a fresh install later tonight after i’ve done some more testing. I first wanted to temporarily solve the trackpoint issue otherwise I feel stranded without an external mouse.

Like I said, I encountered less problem may be because I used most of the settings out of the box. I did not make too many customisations to the system, and used only a few 3rd party apps.

BTW, I replied to your other post on the TrackPoint. Hopefully it could be helpful.

I’ve done some further testing today. A fresh install and its rock stable on gnome and xfce. Will do another fresh install with kde this afternoon.
It could also been related to hardware because I changed the cooling paste and added some copper plates and the fan barely spins. And its acually blowing hot air when it revs up. It must been five years since I did that. Its one of those things I primarily don’t think of… because the inside is completely dust free.

Thank you I will read further into the trackpoint. I have no knowledge of xinput and all its related settings.

Yes you’re right cnzhx. Tumbleweed is way way way more stable. I can’t crash kde by in any way.

I am glad to hear that you found a suitable version but I am afraid that others may not agree with us. And I am not saying that Tumbleweed is more stable than Leap because Leap is based on a recent release of Tumbleweed. But I am not a deep user who can tell what’s happening with your circumstance.

After so many crashes in Plasma, libQtsomething, Kwin etc., I finally understood, after so many years, what the first letter in KDE stands for. Actually, two possibilities:

KDE = Krash Desktop Environment
KDE = Kids’ Desktop Environment

If your experience with it is so bad why not switch then ? :slight_smile: there are so many desktop environments to choose from nowadays and all of the ones I tried are quite decent. I’m currently running on XFCE (also was a fan of KDE in the past).

With Leap 42.3, I encounter about 1 crash per day when using the KDE intensely, and 0.2 crashes per day when using for a short time doing simple things.

Wow, that’s a lot! I haven’t seen KDE crash for more than a year or two, but then I’m still using oS 13.2 on my main desktop (others run oS 42.1 & 42.2, no issues there too). I do remember that there were many desktop restarts at the beginning, but soon (with incoming updates) it tapered out, so my experience is that KDE is rock-solid.

What was your experience with other DE’s? Also bad, I suppose, or you’d have changed it already - I know I would. In that case it might be something related to your hardware, like an unstable video driver or such, still not optimized to your hardware. What do you think?

Correction: Kwin does crash sometimes after heavy kpatience sessions (i.e., many consecutive games). But it is not often, recovery is automatic and it’s not disruptive enough for me to pursue a fix (it’s not a memory leak, nor related to compositing AFAICT).

42.1 was the first release to feature Plasma 5. It was also the first version of Leap, and a god awful start i might add for KDE users. Claiming to be a stable distro while shipping such a flaking piece of software was a pretty stupid thing to do if the devs were trying to get hype at the new structure OpenSUSE was adopting. I continued to pull Plasma 4 in from the 13.2 repo because i wasn’t happy. Eventually i shifted to Mate with Xmonad. Came back to KDE about six months back. OpenSUSE and Plasma5 have been running great for me ever since. A couple of graphical glitches with autohide panels but that’s very minor. I can’t remember the last time my system crashed. Was probably a month back. OpenSUSE 42.2 and 42.3 are good releases as far as Plasma goes. I’m a happy user.

Feel free to inspect the KDE Bugzilla for the segmentation fault Bug Reports DrKonqui posted for me there. :wink:

Link, please? But I’m still curious about ZStefan experience with other DEs in terms of stability, as I wrote above.

TBH, I think most issues happen the first few weeks after a new distro version is released; after a few updates (say, a month or two) things get (boringly) stable. :slight_smile: So are these reports from a still recent release or an old (3+ months) one?

What is your daily dose of KDE crashes?

Daily? Zero.

Weekly? Zero.

Random & very infrequent?
[ol]
[li]Yes, sometimes [interval maybe monthly+] a KWin crash that [with only a single exception since i began using oS TW in May this year] is benign (ie, nothing seems to be affected afterwards). The one big exception (some weeks ago) came out of the blue & mimicked the common KWin crash mode that plagued all other Plasma5 distros i’d used before coming to oS TW, viz: ALL my open windows in my main Activity were afterwards also present in my second Activity, & several windows from my multiple VDs per Activity concatenated onto a single VD. The other symptom of that failure mode is that it breaks my top RHS screen hot-corner “Desktop Grid” function (til the next logout/in). TW has never done that to me before or since, whereas all prior P5 distros did it to me probably daily or so, certainly not less often than weekly.[/li][li]Another once-off failure mode occurred 3 days ago, & this one did shock me. With no warning my desktop [& keyboard & mouse] froze. Ctrl-Alt-Backspace & even Magic Key with REISUB were unresponsive. Whilst i stared at my screen in confused disbelief, & desperately tried to recall what document edits had been active without me getting to Save, the screen suddenly blanked & then Tower rebooted itself. Once more, TW has never done this again before or since… & i hope it’ll be a looooooooooong time before the next instance.[/li][/ol]

Summary: Aside from those two notable exceptions, my oS TW KDE P5 experience wrt stability & reliability has been simply superb, vastly better than all other P5 distros i have used.