Application: kded4 (4.10.5) KDE Platform Version: 4.10.5 Qt Version: 4.8.5 Operating System: Linux 3.4.0 armv7l Distribution: Debian GNU/Linux unstable (sid) -- Information about the crash: - What I was doing when the application crashed: Listening to a music with amarok ampache plugin. - Unusual behavior I noticed: Network connection suddenly shut, bluetooth headphones disonnected. Then i've seen crash report. Amarok is still working and didn't fail. Few seconds after network connection came back. -- Backtrace: Application: KDE Daemon (kdeinit4), signal: Segmentation fault Using host libthread_db library "/lib/arm-linux-gnueabihf/libthread_db.so.1". [Current thread is 1 (Thread 0x7582d000 (LWP 4033))] Thread 2 (Thread 0x7316e420 (LWP 4708)): #0 __GI___pthread_mutex_lock (mutex=0x72800560) at pthread_mutex_lock.c:116 #1 0x75f87d98 in pthread_mutex_lock (mutex=<optimized out>) at forward.c:192 #2 0x75ab8da2 in g_mutex_lock () from /lib/arm-linux-gnueabihf/libglib-2.0.so.0 #3 0x75a8c2fa in g_main_context_prepare () from /lib/arm-linux-gnueabihf/libglib-2.0.so.0 #4 0x75a8c8ec in ?? () from /lib/arm-linux-gnueabihf/libglib-2.0.so.0 #5 0x75a8c8ec in ?? () from /lib/arm-linux-gnueabihf/libglib-2.0.so.0 Backtrace stopped: previous frame identical to this frame (corrupt stack?) Thread 1 (Thread 0x7582d000 (LWP 4033)): [KCrash Handler] #6 __strcpy_chk (dest=dest@entry=0x1dc70d0 "pcm.(null)", src=src@entry=0x0, destlen=destlen@entry=128) at strcpy_chk.c:37 #7 0x731ab3e6 in strcpy (__src=0x0, __dest=0x1dc70d0 "pcm.(null)") at /usr/include/arm-linux-gnueabihf/bits/string3.h:104 #8 try_config (config=config@entry=0x1db1cc0, list=list@entry=0x7e9bbaf4, base=0x732cc7d4 "pcm", name=0x0) at namehint.c:243 #9 0x731abe8c in add_software_devices (list=0x7e9bbaf4, config=0x1db1cc0) at namehint.c:512 #10 snd_device_name_hint (card=-1, iface=<optimized out>, hints=0x7e9bbbd8) at namehint.c:591 #11 0x732c0252 in ?? () from /usr/lib/kde4/kded_phononserver.so #12 0x732c0252 in ?? () from /usr/lib/kde4/kded_phononserver.so Backtrace stopped: previous frame identical to this frame (corrupt stack?) Possible duplicates by query: bug 320854, bug 316471, bug 313232, bug 312565, bug 308766. Reported using DrKonqi
*** This bug has been marked as a duplicate of bug 268185 ***