User-Agent:       Mozilla/5.0 (X11; Linux x86_64; rv:36.0) Gecko/20100101
Firefox/36.0
Build Identifier: 

Recently, lots of KDE applications have started to crash randomly. (Most often
hadden with Plasma Workspace, and a few daemons like Bluetooth, etc.)

After reading the dumps in KDE's crash reporter, it seems to me that most of
the time, the crashed thread is either running in GLib, or some other function
in the call stack further down called from within GLib.

It seems to happens most often:
- after resume from "Suspend-to-RAM"
- after closing a KDE application (it crashes instead of closing)
- after logging out (nearly always a KDE application or a few will crash.
Workspace and daemon are the most popular, but other KDE apps might crash too).

I've already filled one crash report with KDE's reporter.
see KDE bug 344024 :
https://bugs.kde.org/show_bug.cgi?id=344024

I can keep filing such crash dumps if it helps.

Reproducible: Sometimes

Steps to Reproduce:
1. Just wait. (very rare)
Or: resume from "suspend-to-ram" (sometimes)
Or: close an application (rarer, that only crashes the application itself)
Or: log out (very oftern)

Actual Results:  
One or several applications will crash, KDE crash handler appears, showing a
dump, and offering to upload a crash report at bugs.kde.org

When looking at the dump, the offending thread is a few calls down from glib.

Expected Results:  
(system should be working crash free)

Running KDE & co from stock openSUSE repository. (The 3rd party repo I use is
Packman, but that's mostly used for media and should not crash basic KDE
application).

Everything started following latest glib update from "opensuse 13.2 updates"
repo.

Luckily I haven't lost any data to it.


As mentionned, I can keep filing the crash dumps at bugs.kde.org if it helps.