Bug 274748 - kwin crashed during draging of window
Summary: kwin crashed during draging of window
Status: RESOLVED DUPLICATE of bug 258925
Alias: None
Product: kwin
Classification: Plasma
Component: general (show other bugs)
Version: unspecified
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-06-02 13:53 UTC by Sal Colon
Modified: 2011-06-02 13:58 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Sal Colon 2011-06-02 13:53:25 UTC
Application: kwin (4.6.2 (4.6.2))
KDE Platform Version: 4.6.2 (4.6.2)
Qt Version: 4.7.2
Operating System: Linux 2.6.38-8-generic x86_64
Distribution: Ubuntu 11.04

-- Information about the crash:
- What I was doing when the application crashed:I was installing Starcraft 2 using PlayOnLinux. I drug the second POL window and kwin crashed. Starcraft had just finished updating. Running FF 4.0 in background w/ 4 open tabs. Also have system settings open. I have 4 gb ram. Hope all this info helps.

-- Backtrace:
Application: KWin (kwin), signal: Segmentation fault
[Current thread is 1 (Thread 0x7f20705f07c0 (LWP 1605))]

Thread 3 (Thread 0x7f2053b50700 (LWP 1616)):
#0  0x00007f206fe39143 in select () at ../sysdeps/unix/syscall-template.S:82
#1  0x00007f206c18832c in qt_safe_select (nfds=21, fdread=0x20291a0, fdwrite=0x2029438, fdexcept=0x20296d0, orig_timeout=<value optimized out>) at kernel/qcore_unix.cpp:82
#2  0x00007f206c18d3d0 in QEventDispatcherUNIXPrivate::doSelect (this=0x2028fe0, flags=..., timeout=0x0) at kernel/qeventdispatcher_unix.cpp:219
#3  0x00007f206c18e04a in QEventDispatcherUNIX::processEvents (this=0x2028860, flags=...) at kernel/qeventdispatcher_unix.cpp:919
#4  0x00007f206c15f882 in QEventLoop::processEvents (this=<value optimized out>, flags=...) at kernel/qeventloop.cpp:149
#5  0x00007f206c15fabc in QEventLoop::exec (this=0x7f2053b4fcd0, flags=...) at kernel/qeventloop.cpp:201
#6  0x00007f206c076924 in QThread::exec (this=<value optimized out>) at thread/qthread.cpp:492
#7  0x00007f206c141c2f in QInotifyFileSystemWatcherEngine::run (this=0x1ffb110) at io/qfilesystemwatcher_inotify.cpp:248
#8  0x00007f206c079175 in QThreadPrivate::start (arg=0x1ffb110) at thread/qthread_unix.cpp:320
#9  0x00007f206d69b853 in ?? () from /usr/lib/nvidia-current/libGL.so.1
#10 0x00007f206676cd8c in start_thread (arg=0x7f2053b50700) at pthread_create.c:304
#11 0x00007f206fe4104d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#12 0x0000000000000000 in ?? ()

Thread 2 (Thread 0x7f205333f700 (LWP 1617)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:162
#1  0x00007f206eca02a2 in QTWTF::TCMalloc_PageHeap::scavengerThread (this=0x7f206efb9180) at ../3rdparty/javascriptcore/JavaScriptCore/wtf/FastMalloc.cpp:2359
#2  0x00007f206eca02d9 in QTWTF::TCMalloc_PageHeap::runScavengerThread (context=0x7f206efc7254) at ../3rdparty/javascriptcore/JavaScriptCore/wtf/FastMalloc.cpp:1464
#3  0x00007f206d69b853 in ?? () from /usr/lib/nvidia-current/libGL.so.1
#4  0x00007f206676cd8c in start_thread (arg=0x7f205333f700) at pthread_create.c:304
#5  0x00007f206fe4104d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#6  0x0000000000000000 in ?? ()

Thread 1 (Thread 0x7f20705f07c0 (LWP 1605)):
[KCrash Handler]
#6  0x00007f206f318522 in Plasma::Corona::popupPosition (this=0x1bd61c0, item=0x285fc10, s=..., alignment=<value optimized out>) at ../../plasma/corona.cpp:578
#7  0x00007f206f3b5884 in Plasma::ToolTipManagerPrivate::showToolTip (this=0x1d48890) at ../../plasma/tooltipmanager.cpp:399
#8  0x00007f206f3b5c25 in Plasma::ToolTipManager::qt_metacall (this=0x1bb81a0, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x7fff68642cc0) at ./tooltipmanager.moc:88
#9  0x00007f206c1755f8 in QMetaObject::activate (sender=0x1d33450, m=<value optimized out>, local_signal_index=<value optimized out>, argv=0x0) at kernel/qobject.cpp:3287
#10 0x00007f206c1741c9 in QObject::event (this=0x1d33450, e=<value optimized out>) at kernel/qobject.cpp:1190
#11 0x00007f206b5219e4 in QApplicationPrivate::notify_helper (this=0x18b8600, receiver=0x1d33450, e=0x7fff686433c0) at kernel/qapplication.cpp:4462
#12 0x00007f206b5263aa in QApplication::notify (this=<value optimized out>, receiver=0x1d33450, e=0x7fff686433c0) at kernel/qapplication.cpp:4341
#13 0x00007f206f93c866 in KApplication::notify (this=0x7fff686437c0, receiver=0x1d33450, event=0x7fff686433c0) at ../../kdeui/kernel/kapplication.cpp:311
#14 0x00007f206c16049c in QCoreApplication::notifyInternal (this=0x7fff686437c0, receiver=0x1d33450, event=0x7fff686433c0) at kernel/qcoreapplication.cpp:731
#15 0x00007f206c18df12 in sendEvent (this=0x18b91c0) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:215
#16 QTimerInfoList::activateTimers (this=0x18b91c0) at kernel/qeventdispatcher_unix.cpp:604
#17 0x00007f206c18e05b in QEventDispatcherUNIX::processEvents (this=0x181d340, flags=...) at kernel/qeventdispatcher_unix.cpp:923
#18 0x00007f206b5c9c0c in QEventDispatcherX11::processEvents (this=0x181d340, flags=...) at kernel/qeventdispatcher_x11.cpp:152
#19 0x00007f206c15f882 in QEventLoop::processEvents (this=<value optimized out>, flags=...) at kernel/qeventloop.cpp:149
#20 0x00007f206c15fabc in QEventLoop::exec (this=0x7fff68643700, flags=...) at kernel/qeventloop.cpp:201
#21 0x00007f206c163ecb in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1008
#22 0x00007f20701481ec in kdemain (argc=<value optimized out>, argv=0x7fff68643e58) at ../../kwin/main.cpp:542
#23 0x00007f206fd79eff in __libc_start_main (main=0x400740 <main(int, char**)>, argc=3, ubp_av=0x7fff68643e58, init=<value optimized out>, fini=<value optimized out>, rtld_fini=<value optimized out>, stack_end=0x7fff68643e48) at libc-start.c:226
#24 0x0000000000400669 in _start ()

Possible duplicates by query: bug 274581, bug 273579, bug 271482, bug 270051, bug 267726.

Reported using DrKonqi
Comment 1 Martin Flöser 2011-06-02 13:58:55 UTC

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