| Summary: | KWin Crashes | ||
|---|---|---|---|
| Product: | [Plasma] kwin | Reporter: | Ryan McCann <ryan.mccann92> |
| Component: | tabbox | Assignee: | KWin default assignee <kwin-bugs-null> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | crash | CC: | cfeck, kotfantazer, ryan.mccann92 |
| Priority: | NOR | ||
| Version: | 4.10.0 | ||
| Target Milestone: | --- | ||
| Platform: | unspecified | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
| Attachments: | New crash information added by DrKonqi | ||
|
Description
Ryan McCann
2013-02-17 16:56:26 UTC
Is "kwinactive_gles" the official name of a KWin binary? If yes, could you add code to register itself as product "kwin" for DrKonqi bug reports? Since '"screenWidth"' is rather not 0x0, this is a stack corruption for sure. Also the backtrace ends in showig a tabbox (the tabstrip?) what seems rather unrelated to your described action. Do the other backtraces fit that pattern? (memory corruption and/or end in the tabbox?) How do I do that? I'm new to debugging and reporting bugs. everytime kwin crashes there should be a dialog (to eventually report the bug) click on details and post the contents here (also have a look at the "thread 1" section and whether the last few lines look similar) Alright I'll try that. Is there a log somewhere of all of this stuff in case I can't report the bug? Sometimes it becomes unresponsive before I can get through the bug reporter utility. Created attachment 77409 [details]
New crash information added by DrKonqi
kwinactive_gles (4.10.00) on KDE Platform 4.10.00 using Qt 4.8.4
- What I was doing when the application crashed:
I attempted to open Konsole from the applcation panel and it immediately crashed.
-- Backtrace (Reduced):
#6 QObject::setProperty (this=0x1899560, name=0x0, value=0x40236930 <KWin::TabBox::tabBox>) at kernel/qobject.cpp:3681
#7 0x4020f906 in KWin::TabBox::DeclarativeView::showEvent (this=0x1899560, event=0xbeba0c8c) at ../../../kwin/tabbox/declarative.cpp:179
#8 0x412d30e4 in QWidget::event (this=0x1899560, event=0xbeba0c8c) at kernel/qwidget.cpp:8593
#9 0x415296e4 in QFrame::event (this=0x1899560, e=0xbeba0c8c) at widgets/qframe.cpp:557
#10 0x4157a376 in QAbstractScrollArea::event (this=0x1899560, e=0xbeba0c8c) at widgets/qabstractscrollarea.cpp:996
I think I misspoke when I called it an "application menu" in my report. It was the tabbox that I was opening. Thanks, exact same backtrace - sounds suspicious for a memory corruption. Why '"screenWidth"' is resolved 0x0 if for the moment a mist. Compiler or architecture thing maybe. We'll probably not need further backtraces. That'S too deterministic. Kwin crashing when you select "disable visual effects for the full screen window" when starting stellarium. When unselected option "disable visual effects for full-screen windows" does not crash OS: Linux 3.6.11-4.fc16.i686 i686 System: Fedora release 16 (Verne) KDE: 4.8.5 (4.8.5) @Kot That is a driver bug and highly unrelated to this particular bug. I'm not sure what to do with this report. We cannot actually reproduce the issue due to lack of hardware and I'm kind of tempted to say it's a downstream issue. I rather doubt that Ubuntu is working properly on the Nexus 7. If you want to use Plasma Active on the Nexus 7 I'd suggest to try Mer (https://wiki.merproject.org/wiki/Community_Workspace/Tegra3/Nexus7 ). I think the best state for this bug is unmaintained as it's not a supported platform. The new dupe has some important findings, so please keep this the dupe of the other, thanks. *** This bug has been marked as a duplicate of bug 322830 *** |