Application: kaccess () KDE Platform Version: 4.5.5 (KDE 4.5.5) Qt Version: 4.6.3 Operating System: Linux 2.6.34.7-66.fc13.i686.PAE i686 Distribution: "Fedora release 13 (Goddard)" -- Information about the crash: - What I was doing when the application crashed: I'm trying to make "echo ^G" work in GnomeTerminal or Xterm inside KDE4 (Fedora 13) which itself is inside VirtualBox 4.0.2 on MacOSX SnowLeopard. I'd gotten as far as getting a sound sample to play, using the information from Bug 79108, but when I turned off the customized bell (leaving system bell on), I expected to hear the (simulated) buzzer on the motherboard beep. At this point, I'm ready to just use the customized bell, which is infinitely better than silence. -- Backtrace: Application: KDE Accessibility Tool (kaccess), signal: Segmentation fault [KCrash Handler] #7 0x053679d7 in Phonon::PulseSupport::PulseSupport (this=0x8982918) at /usr/src/debug/phonon-4.4.3/phonon/pulsesupport.cpp:718 #8 0x05367dd1 in Phonon::PulseSupport::getInstance () at /usr/src/debug/phonon-4.4.3/phonon/pulsesupport.cpp:670 #9 0x0534a60f in Phonon::AudioOutputPrivate::~AudioOutputPrivate (this=0x8973ca0, __in_chrg=<value optimized out>) at /usr/src/debug/phonon-4.4.3/phonon/audiooutput.cpp:539 #10 0x0534a713 in Phonon::AudioOutputPrivate::~AudioOutputPrivate (this=0x8973ca0, __in_chrg=<value optimized out>) at /usr/src/debug/phonon-4.4.3/phonon/audiooutput.cpp:545 #11 0x05343670 in Phonon::MediaNode::~MediaNode (this=0x8966ca8, __in_chrg=<value optimized out>) at /usr/src/debug/phonon-4.4.3/phonon/medianode.cpp:57 #12 0x05349377 in Phonon::AbstractAudioOutput::~AbstractAudioOutput (this=0x8966ca0, __in_chrg=<value optimized out>) at /usr/src/debug/phonon-4.4.3/phonon/abstractaudiooutput.cpp:40 #13 0x0534d644 in ~AudioOutput (this=0x8966ca0, __in_chrg=<value optimized out>) at /usr/src/debug/phonon-4.4.3/phonon/audiooutput.h:51 #14 Phonon::AudioOutput::~AudioOutput (this=0x8966ca0, __in_chrg=<value optimized out>) at /usr/src/debug/phonon-4.4.3/phonon/audiooutput.h:51 #15 0x0305afbf in QObjectPrivate::deleteChildren (this=0x88b9078) at kernel/qobject.cpp:1986 #16 0x03062236 in QObject::~QObject (this=0x88cb9d8, __in_chrg=<value optimized out>) at kernel/qobject.cpp:975 #17 0x05340869 in Phonon::MediaObject::~MediaObject (this=0x88cb9d8, __in_chrg=<value optimized out>) at /usr/src/debug/phonon-4.4.3/phonon/mediaobject.cpp:65 #18 0x053408d3 in Phonon::MediaObject::~MediaObject (this=0x88cb9d8, __in_chrg=<value optimized out>) at /usr/src/debug/phonon-4.4.3/phonon/mediaobject.cpp:65 #19 0x0305afbf in QObjectPrivate::deleteChildren (this=0x88c3278) at kernel/qobject.cpp:1986 #20 0x03062236 in QObject::~QObject (this=0xbfe4a328, __in_chrg=<value optimized out>) at kernel/qobject.cpp:975 #21 0x0304e0db in QCoreApplication::~QCoreApplication (this=0xbfe4a328, __in_chrg=<value optimized out>) at kernel/qcoreapplication.cpp:642 #22 0x0361237d in QApplication::~QApplication (this=0xbfe4a328, __in_chrg=<value optimized out>) at kernel/qapplication.cpp:1122 #23 0x0248847b in KApplication::~KApplication (this=0xbfe4a328, __in_chrg=<value optimized out>) at /usr/src/debug/kdelibs-4.5.5/kdeui/kernel/kapplication.cpp:908 #24 0x0248ea79 in KUniqueApplication::~KUniqueApplication (this=0xbfe4a328, __in_chrg=<value optimized out>) at /usr/src/debug/kdelibs-4.5.5/kdeui/kernel/kuniqueapplication.cpp:353 #25 0x00905769 in ~KAccessApp (argc=1, argv=0xbfe4a4f4) at /usr/src/debug/kdebase-workspace-4.5.5/kcontrol/access/kaccess.h:27 #26 kdemain (argc=1, argv=0xbfe4a4f4) at /usr/src/debug/kdebase-workspace-4.5.5/kcontrol/access/main.cpp:51 #27 0x080486cc in main (argc=1, argv=0xbfe4a4f4) at /usr/src/debug/kdebase-workspace-4.5.5/i686-redhat-linux-gnu/kcontrol/access/kaccess_dummy.cpp:3 Reported using DrKonqi
On the same screen, enabling 'use visible bell' and selecting 'flash screen' causes an interesting effect: I started an xterm, started an infinite echo ^G loop, and the xterm flashed. Then I selected the accessibility window and the xterm stopped flashing and kaccess started flashing! Switching back to the xterm took the flashing back to the xterm. Weird behaviour, indeed.
It would be very nice if we could get a backtrace of all threads (or at least one with all stack frames) :)
I'd love to give it to you, but you're getting what DrKonqi gives. I even took the time to download all of the debug rpms so that I'd get three stars (out of three) for bug report quality (according to DrKonqi). Perhaps we now need to open a enhancement request or bug report on DrKonqi?
Perhaps, if you could that would be very nice. I do believe that at some point drkonqi actually posted all threads, I wonder why that got changed. Moving the bug to pulsesupport though. Btw, pending a proper backtrace it would be cool if you could try with Phonon 4.4.4, loads of bug fixes are in there.
Closing for lack of feedback. Please feel free to reopen if you can reproduce this with Phonon 4.6.0 or later and provide the requested feedback.