Summary: | Kwin crashed after changing qtcurve configuration | ||
---|---|---|---|
Product: | [Plasma] kwin | Reporter: | Mirza <mirza.dervisevic> |
Component: | general | Assignee: | KWin default assignee <kwin-bugs-null> |
Status: | RESOLVED FIXED | ||
Severity: | crash | CC: | cfeck, furykerry, hrvoje.senjan, null, wuseldusel |
Priority: | NOR | ||
Version: | 4.9.0 | ||
Target Milestone: | 4.9.2 | ||
Platform: | Ubuntu | ||
OS: | Linux | ||
Latest Commit: | http://commits.kde.org/kde-workspace/958eb66e979e002123d72339796d21df6e3d6160 | Version Fixed In: | 4.9.2 |
Sentry Crash Report: | |||
Attachments: | New crash information added by DrKonqi |
Description
Mirza
2012-08-17 23:05:29 UTC
*sigh" given KConfigGroup is invoked by KPluginInfo -> KSycoca there's just one thing left to do. :-( There's KSycoca::disableAutoRebuild() - but no apparent way to re-enable it or ensure it to be updated (in a sync way) And the most sad thing is that this is because: KConfigGroup config(KGlobal::config(), "KSycoca"); setStrategyFromString(config.readEntry("strategy")); Which will probably be configured on n < 2 systems ... :-\ queryScriptsToLoad() still runs in separate thread. Yes, sure. We just moved parts into the sync execution after their KConfigGroup invocation emerged - but since with KPluginInfo the core part of the script loader is affected, the only remaining option (unless we can prevent that sycoca behavior w/o preventing wanted updates) is to revert the async script loading - what i actually didn't want to say this directly ;-) yeah seems to be needed *sigh* *** Bug 306155 has been marked as a duplicate of this bug. *** *** Bug 306405 has been marked as a duplicate of this bug. *** *** Bug 306806 has been marked as a duplicate of this bug. *** Git commit 958eb66e979e002123d72339796d21df6e3d6160 by Thomas Lübking. Committed on 14/09/2012 at 16:08. Pushed by luebking into branch 'KDE/4.9'. Sync script loading, KConfGroup is not thread safe REVIEW: 106377 FIXED-IN: 4.9.2 M +21 -4 kwin/scripting/scripting.cpp M +1 -1 kwin/scripting/scripting.h http://commits.kde.org/kde-workspace/958eb66e979e002123d72339796d21df6e3d6160 Created attachment 80741 [details]
New crash information added by DrKonqi
kwin (4.10.80 "release 150") on KDE Platform 4.10.80 "release 150" using Qt 4.8.5
- What I was doing when the application crashed:
@Thomas, Martin, sorry if spamming here, drkonqi suggested also this one (as also the one i opened with "fast enough comp. changing", but backtrace i have now also references KWin scripting...)
Doubt this one is related though :-(
cd ~/.fonts/
git clone -b in-progress kde:oxygen-fonts
fc-cache -fv
App. appearance -> general font -> changed to oxy. sans -> apply -> crash
I cannot imagine this will be reproducible
-- Backtrace (Reduced):
#6 0x00007fb3b33886eb in qstrcmp (str1=..., str2=0xa1bbbf "") at tools/qbytearray.cpp:330
[...]
#10 0x00007fb3b3b08e23 in operator< (k2=..., k1=...) at /usr/src/debug/kdelibs-git/kdecore/config/kconfigdata.h:126
#11 qMapLessThanKey<KEntryKey> (key2=..., key1=...) at /usr/include/QtCore/qmap.h:107
#12 findNode (akey=..., this=0x90b070) at /usr/include/QtCore/qmap.h:487
#13 find (akey=..., this=0x90b070) at /usr/include/QtCore/qmap.h:608
(In reply to comment #9) > I cannot imagine this will be reproducible Apparently is - bug #321576 |