Bug 268642

Summary: kwin crash
Product: [Plasma] kwin Reporter: wilfredo garcia <sublimacion>
Component: generalAssignee: KWin default assignee <kwin-bugs-null>
Status: RESOLVED DUPLICATE    
Severity: crash    
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: Mandriva RPMs   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description wilfredo garcia 2011-03-16 12:24:45 UTC
Application: kwin (4.5.3 (KDE 4.5.3))
KDE Platform Version: 4.5.3 (KDE 4.5.3)
Qt Version: 4.7.0
Operating System: Linux 2.6.33.7-server-2mnb i686
Distribution: "Mandriva Linux 2010.2"

-- Information about the crash:
- What I was doing when the application crashed:Mandriva was begining and play starting sound then appear window bug

-- Backtrace:
Application: KWin (kwin), signal: Aborted
[KCrash Handler]
#7  0xffffe424 in __kernel_vsyscall ()
#8  0xb7677a81 in raise () from /lib/i686/libc.so.6
#9  0xb76793d2 in abort () from /lib/i686/libc.so.6
#10 0xb5aeaeaf in __gnu_cxx::__verbose_terminate_handler() () from /usr/lib/libstdc++.so.6
#11 0xb5ae87f5 in ?? () from /usr/lib/libstdc++.so.6
#12 0xb5ae8832 in std::terminate() () from /usr/lib/libstdc++.so.6
#13 0xb5ae88eb in __cxa_rethrow () from /usr/lib/libstdc++.so.6
#14 0xb6776670 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#15 0xb677bb50 in QCoreApplication::exec() () from /usr/lib/libQtCore.so.4
#16 0xb5c4b124 in QApplication::exec() () from /usr/lib/libQtGui.so.4
#17 0xb77e9bff in kdemain () from /usr/lib/libkdeinit4_kwin.so
#18 0x080485cb in _start ()

Possible duplicates by query: bug 268589, bug 268384, bug 268321, bug 268218, bug 268179.

Reported using DrKonqi
Comment 1 Thomas Lübking 2011-03-16 15:41:28 UTC
probably a dupe. from the providable backtrace (not your fault) we will never be able to say for sure, but there's a good chance that setting the scale method to "smooth" instead of "accurate" (KDE 4.6 only, "kcmshell4 kwincompositing" / "Advanced" tab) or blacklisting the lanczos filter (little harder process, preferably update to 4.6.x - if you can) will work around it.

*** This bug has been marked as a duplicate of bug 241163 ***