Each time I close the laptop lid, and then restore the PC power, I get a warning that KMix has crashed. When I attempt to recover or restart the application, it fails. I do not know what KMix is, but it is somehow linked to my touchpad as some of those functions stop working. Only way to resolve is system restart. Crash report below:

Application: kmix (4)
KDE Platform Version: 4.8.4 (4.8.4)
Qt Version: 4.8.1
Operating System: Linux 3.2.0-23-generic x86_64
Distribution: Ubuntu 12.04 LTS

-- Information about the crash:
<In detail, tell us what you were doing  when the application crashed.>

The crash can be reproduced every time.

-- Backtrace:
Application: KMix (kmix), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f15a941c780 (LWP 1739))]

Thread 3 (Thread 0x7f158a54c700 (LWP 1743)):
#0  0x00007f15a8cd40bd in read () at ../sysdeps/unix/syscall-template.S:82
#1  0x00007f159eb0e88f in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x00007f159ead3abd in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x00007f159ead3f96 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x00007f159ead4124 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x00007f15a5a50426 in QEventDispatcherGlib::processEvents (this=0x7f15840008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:426
#6  0x00007f15a5a1fc82 in QEventLoop::processEvents (this=<optimized out>, flags=...) at kernel/qeventloop.cpp:149
#7  0x00007f15a5a1fed7 in QEventLoop::exec (this=0x7f158a54bdd0, flags=...) at kernel/qeventloop.cpp:204
#8  0x00007f15a591efa7 in QThread::exec (this=<optimized out>) at thread/qthread.cpp:501
#9  0x00007f15a59ff9ff in QInotifyFileSystemWatcherEngine::run (this=0x2563e80) at io/qfilesystemwatcher_inotify.cpp:248
#10 0x00007f15a5921fcb in QThreadPrivate::start (arg=0x2563e80) at thread/qthread_unix.cpp:298
#11 0x00007f159f63ae9a in start_thread (arg=0x7f158a54c700) at pthread_create.c:308
#12 0x00007f15a8ce14bd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#13 0x0000000000000000 in ?? ()

Thread 2 (Thread 0x7f1589b3f700 (LWP 1744)):
#0  0x00007f15a8cd5b03 in __GI___poll (fds=<optimized out>, nfds=<optimized out>, timeout=<optimized out>) at ../sysdeps/unix/sysv/linux/poll.c:87
#1  0x00007f159ead3ff6 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x00007f159ead4124 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x00007f15a5a50426 in QEventDispatcherGlib::processEvents (this=0x7f15780008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:426
#4  0x00007f15a5a1fc82 in QEventLoop::processEvents (this=<optimized out>, flags=...) at kernel/qeventloop.cpp:149
#5  0x00007f15a5a1fed7 in QEventLoop::exec (this=0x7f1589b3edd0, flags=...) at kernel/qeventloop.cpp:204
#6  0x00007f15a591efa7 in QThread::exec (this=<optimized out>) at thread/qthread.cpp:501
#7  0x00007f15a59ff9ff in QInotifyFileSystemWatcherEngine::run (this=0x23ecad0) at io/qfilesystemwatcher_inotify.cpp:248
#8  0x00007f15a5921fcb in QThreadPrivate::start (arg=0x23ecad0) at thread/qthread_unix.cpp:298
#9  0x00007f159f63ae9a in start_thread (arg=0x7f1589b3f700) at pthread_create.c:308
#10 0x00007f15a8ce14bd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#11 0x0000000000000000 in ?? ()

Thread 1 (Thread 0x7f15a941c780 (LWP 1739)):
[KCrash Handler]
#6  0x00007f15a9001e23 in ?? () from /usr/lib/kde4/libkdeinit/libkdeinit4_kmix.so
#7  0x00007f15a8ffd64b in ?? () from /usr/lib/kde4/libkdeinit/libkdeinit4_kmix.so
#8  0x00007f15a5a35281 in QMetaObject::activate (sender=0x258a4c0, m=<optimized out>, local_signal_index=<optimized out>, argv=0x0) at kernel/qobject.cpp:3547
#9  0x00007f15a5a35281 in QMetaObject::activate (sender=0x25c12b0, m=<optimized out>, local_signal_index=<optimized out>, argv=0x0) at kernel/qobject.cpp:3547
#10 0x00007f15a8fd6b0c in ?? () from /usr/lib/kde4/libkdeinit/libkdeinit4_kmix.so
#11 0x00007f15a8fe6df5 in ?? () from /usr/lib/kde4/libkdeinit/libkdeinit4_kmix.so
#12 0x00007f15a73b8944 in ?? () from /usr/lib/x86_64-linux-gnu/libpulse.so.0
#13 0x00007f159eff2693 in ?? () from /usr/lib/x86_64-linux-gnu/libpulsecommon-1.1.so
#14 0x00007f159eff2a03 in pa_pdispatch_run () from /usr/lib/x86_64-linux-gnu/libpulsecommon-1.1.so
#15 0x00007f15a73aebdd in ?? () from /usr/lib/x86_64-linux-gnu/libpulse.so.0
#16 0x00007f159eff72a9 in ?? () from /usr/lib/x86_64-linux-gnu/libpulsecommon-1.1.so
#17 0x00007f15a719cab3 in ?? () from /usr/lib/x86_64-linux-gnu/libpulse-mainloop-glib.so.0
#18 0x00007f159ead3c9a in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#19 0x00007f159ead4060 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#20 0x00007f159ead4124 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#21 0x00007f15a5a503bf in QEventDispatcherGlib::processEvents (this=0x222fad0, flags=...) at kernel/qeventdispatcher_glib.cpp:424
#22 0x00007f15a6740d5e in QGuiEventDispatcherGlib::processEvents (this=<optimized out>, flags=...) at kernel/qguieventdispatcher_glib.cpp:204
#23 0x00007f15a5a1fc82 in QEventLoop::processEvents (this=<optimized out>, flags=...) at kernel/qeventloop.cpp:149
#24 0x00007f15a5a1fed7 in QEventLoop::exec (this=0x7fffe0c04860, flags=...) at kernel/qeventloop.cpp:204
#25 0x00007f15a5a24f67 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1148
#26 0x00007f15a8fee3e2 in kdemain () from /usr/lib/kde4/libkdeinit/libkdeinit4_kmix.so
#27 0x00007f15a8c1076d in __libc_start_main (main=0x400630, argc=3, ubp_av=0x7fffe0c04de8, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7fffe0c04dd8) at libc-start.c:226
#28 0x0000000000400661 in _start ()

Report to https://bugs.kde.org

Reproducible: Always

Steps to Reproduce:
1. Power on
2. Close laptop lid long enough for system to enter "Power saving mode"
3. Open laptop lid, press power button and login
Actual Results:  
Error log in details section is generated each time. 

Expected Results:  
Not crashed?

I am running Kubuntu 12.04 on an HP Probook 4520s. The touchpad uses synaptics drivers in Winblows and is somehow affected as certain functions do not start back up (typing detection, etc.)