Summary: | Crash when switching GUI mode | ||
---|---|---|---|
Product: | [Applications] kdevelop | Reporter: | Amilcar do Carmo Lucas <a.lucas> |
Component: | general | Assignee: | KDevelop Developers <kdevelop-devel> |
Status: | RESOLVED FIXED | ||
Severity: | crash | CC: | hattons, kaplun, nospam |
Priority: | NOR | ||
Version: | git master | ||
Target Milestone: | --- | ||
Platform: | openSUSE | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Amilcar do Carmo Lucas
2003-12-01 15:58:26 UTC
Yeah, this is an all time classic. It still happens. Sometimes. With some of the "KDE-Styles" such as dotNET and Plastik. So it isn't really ours.. Maybe we're misbehaving, but I don't think KStyle should kill us.. Where is this? kdelibs? To make it more explicit: This bug can on occasion be triggered by switching gui mode in KDevelop3. It used to be a frequent crash with the old IDEAl implementation and some of the kstyles, but seems more or less fixed now. It appears there is still a problem around somewhere though. If that is in qt, kmdi or kstyles I have no idea, but I doubt its specific to KDevelop. *** Bug 75852 has been marked as a duplicate of this bug. *** *** Bug 76558 has been marked as a duplicate of this bug. *** *** Bug 77438 has been marked as a duplicate of this bug. *** Note the fix suggested in http://bugs.kde.org/show_bug.cgi?id=76558#c6 Yeah, which suggests KDevelop buginess. Most likely the same as #76558. The -1 is pretty much the only reason other than corrupted data that that code can crash, and it comes from QWindowsStyle (was donated by TT), so putting in workarounds KDE-side only is not gonna help much *** This bug has been marked as a duplicate of 76558 *** Hmm, wrong. Need to learn to read better Still, IMHO, this is up to kdevelop and/or KMDI to get right, unless you can convince TT to put in the guards for -1 into all Qt styles, in which case i'll change KStyle. The crashing documentation plugin is gone and we no longer change UI mode runtime, so for KDevelop this problem should be gone. Closing for now, maybe we'll have to revisit this, but this particular report is solved. |