Application: kwin (4.8.5 (4.8.5)) KDE Platform Version: 4.8.5 (4.8.5) Qt Version: 4.8.1 Operating System: Linux 3.2.0-33-generic x86_64 Distribution: Ubuntu 12.04.1 LTS -- Information about the crash: - What I was doing when the application crashed: I was surfing then decided to shut the computer down. What i noticed (not usual) is that my mouse cursor is doubled but the doubling is not so net precise. Is it relevant, i don't know? And that sometimes the computer seems stopping activity, the mouse can't be used, then i have to wait ( 5, 10, 20 seconds??) to be able to use my mouse! -- Backtrace: Application: KWin (kwin), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f73437c4780 (LWP 2334))] Thread 3 (Thread 0x7f7323da0700 (LWP 2340)): #0 0x00007f7342fcc023 in select () at ../sysdeps/unix/syscall-template.S:82 #1 0x00007f733e81b366 in qt_safe_select (nfds=18, fdread=0x7f731c000ac8, fdwrite=0x7f731c000d60, fdexcept=0x7f731c000ff8, orig_timeout=<optimized out>) at kernel/qcore_unix.cpp:83 #2 0x00007f733e8207b2 in QEventDispatcherUNIXPrivate::doSelect (this=0x7f731c000910, flags=..., timeout=0x0) at kernel/qeventdispatcher_unix.cpp:223 #3 0x00007f733e820ca3 in QEventDispatcherUNIX::processEvents (this=0x7f731c0008f0, flags=...) at kernel/qeventdispatcher_unix.cpp:926 #4 0x00007f733e7edc82 in QEventLoop::processEvents (this=<optimized out>, flags=...) at kernel/qeventloop.cpp:149 #5 0x00007f733e7eded7 in QEventLoop::exec (this=0x7f7323d9fdd0, flags=...) at kernel/qeventloop.cpp:204 #6 0x00007f733e6ecfa7 in QThread::exec (this=<optimized out>) at thread/qthread.cpp:501 #7 0x00007f733e7cd9ff in QInotifyFileSystemWatcherEngine::run (this=0xadb330) at io/qfilesystemwatcher_inotify.cpp:248 #8 0x00007f733e6effcb in QThreadPrivate::start (arg=0xadb330) at thread/qthread_unix.cpp:298 #9 0x00007f7337914e9a in start_thread (arg=0x7f7323da0700) at pthread_create.c:308 #10 0x00007f7342fd2cbd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 #11 0x0000000000000000 in ?? () Thread 2 (Thread 0x7f732359f700 (LWP 2341)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:162 #1 0x00007f733fa87222 in ?? () from /usr/lib/x86_64-linux-gnu/libQtScript.so.4 #2 0x00007f733fa87259 in ?? () from /usr/lib/x86_64-linux-gnu/libQtScript.so.4 #3 0x00007f7337914e9a in start_thread (arg=0x7f732359f700) at pthread_create.c:308 #4 0x00007f7342fd2cbd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 #5 0x0000000000000000 in ?? () Thread 1 (Thread 0x7f73437c4780 (LWP 2334)): [KCrash Handler] #6 0x0000000000000000 in ?? () #7 0x00007f734336a92a in KWin::Deleted::copyToDeleted (this=0xd45200, c=0xdb0220) at ../../kwin/deleted.cpp:78 #8 0x00007f734336abad in KWin::Deleted::create (c=0xdb0220) at ../../kwin/deleted.cpp:53 #9 0x00007f734334c570 in KWin::Unmanaged::release (this=0xdb0220) at ../../kwin/unmanaged.cpp:85 #10 0x00007f73432e4ced in KWin::Workspace::~Workspace (this=0xa52c50, __in_chrg=<optimized out>) at ../../kwin/workspace.cpp:533 #11 0x00007f73432e5559 in KWin::Workspace::~Workspace (this=0xa52c50, __in_chrg=<optimized out>) at ../../kwin/workspace.cpp:563 #12 0x00007f73432fc305 in KWin::Application::~Application (this=0x7fff00e261e0, __in_chrg=<optimized out>) at ../../kwin/main.cpp:340 #13 0x00007f73432fec94 in kdemain (argc=<optimized out>, argv=<optimized out>) at ../../kwin/main.cpp:541 #14 0x00007f7342f0076d in __libc_start_main (main=0x400630 <main(int, char**)>, argc=3, ubp_av=0x7fff00e26908, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7fff00e268f8) at libc-start.c:226 #15 0x0000000000400661 in _start () This bug may be a duplicate of or related to bug 308636. Possible duplicates by query: bug 308636, bug 308593, bug 307068, bug 302768, bug 301165. Reported using DrKonqi
*** This bug has been marked as a duplicate of bug 282933 ***
> What i noticed (not usual) is that my mouse cursor is doubled but the doubling is not so net precise. What do you mean by "doubled" - got two cursors? > Is it relevant probably, because ... > And that sometimes the computer seems stopping activity, the mouse can't be used, then i have to wait ( 5, 10, 20 seconds??) to be able to use my mouse! ... that's some I/O timeout and since the cursor is usually done in HW and the framebuffer (unless you run a virtual machine) that'd be an I/O timout in the kernel or in the X11 server. There's been random reports for the intel driver to cause that (that's the harmless case) but esp. if you don't have an intel chip: in most cases they're on HDD access. => check dmesg and if there's an I/O access error on sdx, check S.M.A.R.T. and in doubt run a test and check the Disk still intact and has no bad sectors. There may be an imminent disk failure in which case you _really_ should backup all relevant data.
Thanks for the precious informations! I have an i7 (motherboard GA-P55A-UD4)... I will do what you suggests avout the hard drive.... I think, first, that there is no bad sectors.. I will verify.. When i said "doubled", it is as when you squint and the both cursors contact... the doubled one is a bit inaccurate...