KNotify crashed signal 11

Bug #151970 reported by advanracing62
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
kdelibs (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1232533296 (LWP 7565)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[KCrash handler]
#6 0xb66a7a0b in KAudioManagerPlay::KAudioManagerPlay ()
   from /usr/lib/libartskde.so.1
#7 0xb6764893 in KNotify::restartedArtsd () from /usr/lib/kde3/knotify.so
#8 0xb676696d in KNotify::KNotify () from /usr/lib/kde3/knotify.so
#9 0xb67671aa in kdemain () from /usr/lib/kde3/knotify.so
#10 0x0804e6bf in ?? ()
#11 0x00000001 in ?? ()
#12 0x0806b298 in ?? ()
#13 0x00000001 in ?? ()
#14 0x00000000 in ?? ()

Revision history for this message
Ben (bensand) wrote :

Had a crash of KNotify today with the exact same dump. I had just booted up and opened Kmail when it hit me. This is a fresh upgrade to 7.10 ubuntu I did yesterday.

Revision history for this message
Alien.col (abelardo-duarte) wrote :

I can confirm this bug, it happens everytime i exit a kde4 session, there is no backtrace available. It also happens when initiating amarok.

Revision history for this message
Daniel T Chen (crimsun) wrote :

Is this symptom still reproducible in 8.10?

Changed in kdelibs:
status: New → Incomplete
Revision history for this message
Jonathan Thomas (echidnaman) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

Changed in kdelibs:
status: Incomplete → Invalid
Revision history for this message
notdefine (notdefine) wrote :

Same Problem here

Anwendung: KNotify (knotify4), Signal SIGSEGV
0x00007f83a1b4d621 in nanosleep () from /lib/libc.so.6
[Current thread is 0 (LWP 17020)]

Thread 2 (Thread 0x423ab950 (LWP 17199)):
#0 0x00007f839fed455d in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib/libpthread.so.0
#1 0x00007f8399a2bf31 in ?? () from /usr/lib/libxine.so.1
#2 0x00007f839fed03ea in start_thread () from /lib/libpthread.so.0
#3 0x00007f83a1b8bc6d in clone () from /lib/libc.so.6
#4 0x0000000000000000 in ?? ()

Thread 1 (Thread 0x7f83a48c46f0 (LWP 17020)):
[KCrash Handler]
#5 0x00007f83a1b27690 in strlen () from /lib/libc.so.6
#6 0x00007f83a1af044e in vfprintf () from /lib/libc.so.6
#7 0x00007f83a1ba1d18 in __vsnprintf_chk () from /lib/libc.so.6
#8 0x00007f8399a43fad in ?? () from /usr/lib/libxine.so.1
#9 0x00007f8399a269f4 in xine_log () from /usr/lib/libxine.so.1
#10 0x00007f8399a31ecc in ?? () from /usr/lib/libxine.so.1
#11 0x00007f8399c89aed in ?? () from /usr/lib/kde4/plugins/phonon_backend/phonon_xine.so
#12 0x00007f8399c89c65 in ?? () from /usr/lib/kde4/plugins/phonon_backend/phonon_xine.so
#13 0x00007f8399ca6c53 in ?? () from /usr/lib/kde4/plugins/phonon_backend/phonon_xine.so
#14 0x00007f8399ca733b in qt_plugin_instance () from /usr/lib/kde4/plugins/phonon_backend/phonon_xine.so
#15 0x00007f839b66a452 in ?? () from /usr/lib/kde4/plugins/phonon_platform/kde.so
#16 0x00007f839b66b68d in ?? () from /usr/lib/kde4/plugins/phonon_platform/kde.so
#17 0x00007f83a3eb9028 in ?? () from /usr/lib/libphonon.so.4
#18 0x00007f83a3eba067 in Phonon::Factory::backend () from /usr/lib/libphonon.so.4
#19 0x00007f83a3eb4dab in Phonon::GlobalConfig::audioOutputDeviceListFor () from /usr/lib/libphonon.so.4
#20 0x00007f83a3eb527d in Phonon::GlobalConfig::audioOutputDeviceFor () from /usr/lib/libphonon.so.4
#21 0x00007f83a3eaffde in ?? () from /usr/lib/libphonon.so.4
#22 0x000000000040c919 in _start ()

Changed in kdelibs:
status: Invalid → New
Revision history for this message
Jonathan Thomas (echidnaman) wrote :

Your crash is not the same. Your crash happens to be bug 290768.

Changed in kdelibs:
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.