Bug 151822 - SIGSEGV on starting Synth_FREEVERB controller
Summary: SIGSEGV on starting Synth_FREEVERB controller
Status: RESOLVED UNMAINTAINED
Alias: None
Product: noatun
Classification: Unmaintained
Component: general (other bugs)
Version First Reported In: unspecified
Platform: openSUSE Linux
: NOR crash
Target Milestone: ---
Assignee: Charles Samuels
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-11-03 20:18 UTC by Klaus Dorbath
Modified: 2018-09-04 15:26 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Klaus Dorbath 2007-11-03 20:18:04 UTC
Version:           2.10.0 (using KDE KDE 3.5.7)
Installed from:    SuSE RPMs
OS:                Linux

On starting the controller for Synth_FREEVERB noatun crashes reproducable.
OS: SuSE 10.3


SIGSEGV-Report:
Überprüfung der Systemkonfiguration beim Start deaktiviert.
(Translation: Check of systems configuration on start deactivated)

 [?1034h(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found)
.....
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0xb6107af0 (LWP 5809)]
(no debugging symbols found)
.....

(no debugging symbols found)
[KCrash handler]
#6  0xb6fa6426 in Arts::GuiFactory_base::_create ()
   from /opt/kde3/lib/libartsgui_idl.so.0
#7  0xb57f14ed in Arts::GenericGuiFactory_impl::createGui ()
   from /opt/kde3/lib/libartsgui.so
#8  0xb7e297de in Effect::configure () from /opt/kde3/lib/libnoatun.so.1
#9  0xb7e1d8da in EffectView::configureEffect ()
   from /opt/kde3/lib/libnoatun.so.1
#10 0xb7e1e4f4 in EffectView::qt_invoke () from /opt/kde3/lib/libnoatun.so.1
#11 0xb77158ad in QObject::activate_signal ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#12 0xb771644d in QObject::activate_signal ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#13 0xb7a50f7c in QButton::clicked () from /usr/lib/qt3/lib/libqt-mt.so.3
#14 0xb77a88ad in QButton::mouseReleaseEvent ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#15 0xb774e6e4 in QWidget::event () from /usr/lib/qt3/lib/libqt-mt.so.3
#16 0xb76b70ac in QApplication::internalNotify ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#17 0xb76b7fd3 in QApplication::notify () from /usr/lib/qt3/lib/libqt-mt.so.3
#18 0xb7d2cee2 in KApplication::notify () from /opt/kde3/lib/libkdecore.so.4
#19 0xb76564fa in QETWidget::translateMouseEvent ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#20 0xb76552c6 in QApplication::x11ProcessEvent ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#21 0xb7666070 in QEventLoop::processEvents ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#22 0xb76cdc30 in QEventLoop::enterLoop () from /usr/lib/qt3/lib/libqt-mt.so.3
#23 0xb76cdac6 in QEventLoop::exec () from /usr/lib/qt3/lib/libqt-mt.so.3
#24 0xb76b6c1f in QApplication::exec () from /usr/lib/qt3/lib/libqt-mt.so.3
#25 0xb7f79daf in kdemain () from /opt/kde3/lib/libkdeinit_noatun.so
#26 0x080484f2 in ?? ()
#27 0x00000001 in ?? ()
#28 0xbff7ba84 in ?? ()
#29 0xbff7b9f8 in ?? ()
#30 0x08048529 in ?? ()
#31 0xb7fa7f60 in ?? () from /lib/ld-linux.so.2
#32 0xbff7ba00 in ?? ()
#33 0xbff7ba58 in ?? ()
#34 0xb7e5bfe0 in __libc_start_main () from /lib/libc.so.6
Backtrace stopped: frame did not save the PC
Comment 1 Christoph Feck 2011-12-20 02:58:30 UTC
This crash report is at least 4 years old and there were no further comments or status updates since then.

Therefore we believe that this crash is already fixed in KDE 4 or the backtrace is no longer applicable to KDE 4.

If the crash still happens with a recent KDE version (4.7.4 or 4.8), please add an updated backtrace or provide steps to reproduce. For more information, see http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports

(To prevent automatic closing of this bug in the future, please set the bug status to ASSIGNED or NEW)
Comment 2 Andrew Crouthamel 2018-09-04 15:26:58 UTC
Hello! Sorry to be the bearer of bad news, but this project has been unmaintained for many years so I am closing this bug.