Summary: | Crash while switching to debugger view | ||
---|---|---|---|
Product: | [Plasma] Oxygen | Reporter: | Gunther Piez <gpiez> |
Component: | general | Assignee: | Camilla Boemann <cbo> |
Status: | RESOLVED UPSTREAM | ||
Severity: | crash | CC: | hugo.pereira.da.costa |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Compiled Sources | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Gunther Piez
2010-04-30 19:17:22 UTC
*** This bug has been marked as a duplicate of bug 226364 *** Sorry, either this bug is different than 226364, or the patch mentioned there does not fix 226364 - because I when the crash happened, I was using kdebase-runtime-4.4.2, which already has the patch (I just double checked in the sources I was using to build it). I'm sorry, but its not a kdevelop bug either. I'll re-assign to oxygen for now, but you might have to open a report to Qt maybe. Looking at the stack trace you are right, this isn't kdevelop causing the crash. I simply took the crash wizard, which of course reported it with kdevelop as the culprit. I didn't want to disturb your release day ;-) Hi, Sorry for the stupid question, where does it appear in the crash report that it is an oxygen bug ? I only see lines about Qt. No mention about oxygen anywhere, unlike for bug 226364, which was fixed for kde4.4.2 (see e.g: Oxygen::TransitionWidget::grabWidget. That was the bad guy). I do not think it is an oxygen bug. Do I miss something ? one way to figure it out: - is the crash reproducible often ? - is it reproducible with any other style than oxygen ? Sorry, I did have this crash only once, AFAIK. There is some kdelibs stuff too, but of course I do not know what exactly caused this bug. Yeah, but the thread that crashes, (Thread1) really only mentions Qt. I would rather vote for a Qt bug. Will keep it open in the meanwhile, in case someone else (including you) can reproduce. Cheers marking as upstream, as there is nothing mentioning oxygen in the thread that crashed. |