[Bug 183485] New: knotify4 crashes and sends SIGSEGV

[Hugh Urwin]

http://bugs.kde.org/show_bug.cgi?id=183485

           Summary: knotify4 crashes and sends SIGSEGV
           Product: kde
           Version: unspecified
          Platform: Ubuntu Packages
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: NOR
         Component: general
        AssignedTo: unassigned-bugs at kde.org
        ReportedBy: h.e.urwin at gmail.com


Version:            (using KDE 4.2.0)
OS:                Linux
Installed from:    Ubuntu Packages

As reported by the OS:
This backtrace appears to be of no use.
This is probably because your packages are built in a way which prevents
creation of proper backtraces, or the stack frame was seriously corrupted in
the crash.
-----------------------------------------------------------
NOTE: A bug in backtracking system? every backtrace is reported as useless. The
system (kubuntu 8.10 - kde 4.2.00) is not broken
-----------------------------------------------------------

a bunch of 
(no debugging symbols found)
follows
[Thread debugging using libthread_db enabled]
[New Thread 0xb67056c0 (LWP 32559)]
more 
(no debugging symbols found)
....
(no debugging symbols found)
0xb80f7430 in __kernel_vsyscall ()
[Current thread is 0 (process 32559)]

Thread 1 (Thread 0xb67056c0 (LWP 32559)):
#0  0xb80f7430 in __kernel_vsyscall ()
#1  0xb6d1df10 in nanosleep () from /lib/tls/i686/cmov/libc.so.6
#2  0xb6d1dd4e in sleep () from /lib/tls/i686/cmov/libc.so.6
#3  0xb7f83d72 in ?? () from /usr/lib/libkdeui.so.5
#4  0xb7f84734 in KCrash::defaultCrashHandler () from /usr/lib/libkdeui.so.5
#5  <signal handler called>
#6  0xb79af7f7 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#7  0xb7d4cfc3 in ?? () from /usr/lib/libphonon.so.4
#8  0xb7d36216 in ?? () from /usr/lib/libphonon.so.4
#9  0xb7d374aa in ?? () from /usr/lib/libphonon.so.4
#10 0xb7d35b85 in ?? () from /usr/lib/libphonon.so.4
#11 0x08053244 in _start ()
#0  0xb80f7430 in __kernel_vsyscall ()

after hours knotify4 started crashing. It might have been concident with going
visible on kopete and started receiving messages. I see that even when the
backtracing was classed as useless by the OS, phonon seems to be involved in
the crash, which sounds reasonable since phonons not working on my system so
far and kopete seems to be relying on it. The problem with phonon is that I was
using oss on Hardy (and before.. for some years now actually) and phonon doesnt
seem to like it. When I changed the backend from xine to gstreamer as someone
suggested on some kde forum, the sound configuration applet crashed and those
applications relying on phonon (like dragon) will die silently (at least as
seen from kde). Right now i can confirm that the knotify is crashing
coincidently with some incoming messages from kopete and since the problem
appeared after changing the backend to gstreamer...an unproperly configured
phonon might be making knotify crash.


-- 
Configure bugmail: http://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.