Version: 2.3.3 (using KDE 3.1.93 (CVS >= 20031111), yes) Compiler: gcc version 3.2.3 20030422 (Gentoo Linux 1.4 3.2.3-r2, propolice) OS: Linux (i686) release 2.6.0-test9-bk17 I disabled arts since it clashed with xmms. I then later tried to start noatun without having artsd running, and it crashed. I tried several times and it crashed every time. I then tried to enable artsd and noatun started up just fine. Strange thing is that I then tried to shut down artsd and start noatun again to see if it crashed again, and this time it didnt. Noatun enabled artsd by itself and started up just fine.
For a crash report a backtrace is needed as well. Also what do you expect from Noatun to do if artsd can't be started? It just won't work without artsd and so the only thing that would be appropriate is exiting with an error message like "You cannot run Noatun without arts".
Another one, I cannot reproduce this here. If I disable arts in kcontrol and then start noatun (I made sure that there's no artsd running anymore!) it still launches arts for me. If you try and rename the artsd binary to stop it from starting then I'd call this an user-bug and not an application-bug :) Simple rule: Don't try using Noatun if you don't want artsd.
Also note: OS: Linux (i686) release 2.6.0-test9-bk17 artsd and kernel 2.6.0 sometimes clash. It seems to be a kernel bug of some kind. A bug ticket is open here on bugs.kde.org waiting for resolution. Please make sure that you can play sounds through aRts after you've loaded artsd. I usually do that by hitting backspace on a konsole and waiting for an audible beep.
Well of course I didn't expect it to run without arts. The thing is I just forgot arts wasn't running when I started noatun. Still, that is no excuse for the program to crash. It should at least show me an errormessage saying it cannot be run without arts running. And as for the backtrace as I said after I got noatun running, I tried again to shutdown noatun and arts, and then starting noatun again. This time noatun started arts automatically as it should and it didn't crash.
And I said: I cannot reproduce this crash. If I start noatun with arts not running and sound being disabled in kcontrol it still autostarts artsd. If you cannot provide a scenario of how to reproduce this bug I'm going to close it. I NEED to reproduce this to find the cause for the crash.
Well this seems to be fixed. Noatun no longer crashes when the arts server is disabled, and maybe it was just a freak incident since it apparently didn't happen to other people.
KDE 3.3.1 & Fedora Core 2 Noatun crash. I think this maybe is same bug. Using host libthread_db library "/lib/tls/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread -151166848 (LWP 16583)] [KCrash handler] #4 0x0464fcc5 in Player::openFile (this=0x3ef0a5c, f=@0x1, autoplay=true) at player.cpp:285 #5 0x04659d2b in NoatunApp::newInstance (this=0xfeea60d0) at app.h:52 #6 0x002d7e42 in KUniqueApplication::processDelayed () from /usr/lib/libkdecore.so.4 #7 0x002d82ef in KUniqueApplication::qt_invoke () from /usr/lib/libkdecore.so.4 #8 0x0465a92b in NoatunApp::qt_invoke (this=0x12, _id=-18194224, _o=0x0) at app.moc:123 #9 0x03aaaa1c in QObject::activate_signal () from /usr/lib/qt-3.3/lib/libqt-mt.so.3 #10 0x03deb63a in QSignal::signal () from /usr/lib/qt-3.3/lib/libqt-mt.so.3 #11 0x03ac4bcd in QSignal::activate () from /usr/lib/qt-3.3/lib/libqt-mt.so.3 #12 0x03acc393 in QSingleShotTimer::event () from /usr/lib/qt-3.3/lib/libqt-mt.so.3 #13 0x03a4e49f in QApplication::internalNotify () from /usr/lib/qt-3.3/lib/libqt-mt.so.3 #14 0x03a4da9e in QApplication::notify () from /usr/lib/qt-3.3/lib/libqt-mt.so.3 #15 0x00231883 in KApplication::notify () from /usr/lib/libkdecore.so.4 #16 0x03a3dd85 in QEventLoop::activateTimers () from /usr/lib/qt-3.3/lib/libqt-mt.so.3 #17 0x039f6edb in QEventLoop::processEvents () from /usr/lib/qt-3.3/lib/libqt-mt.so.3 #18 0x03a60748 in QEventLoop::enterLoop () from /usr/lib/qt-3.3/lib/libqt-mt.so.3 #19 0x03a4e751 in QApplication::enter_loop () from /usr/lib/qt-3.3/lib/libqt-mt.so.3 #20 0x03c340a0 in QDialog::exec () from /usr/lib/qt-3.3/lib/libqt-mt.so.3 #21 0x005ef825 in KMessageBox::createKMessageBox () from /usr/lib/libkdeui.so.4 #22 0x005ef38c in KMessageBox::createKMessageBox () from /usr/lib/libkdeui.so.4 #23 0x005f1e21 in KMessageBox::errorWId () from /usr/lib/libkdeui.so.4 #24 0x005f1c1d in KMessageBox::error () from /usr/lib/libkdeui.so.4 #25 0x04648a9f in Engine::initArts (this=0x902e120) at engine.cpp:550 #26 0x04645116 in Engine (this=0x902e120, parent=0x0) at engine.cpp:252 #27 0x0464ec91 in Player (this=0x902e9d0, parent=0x0) at player.cpp:19 #28 0x04658168 in NoatunApp (this=0xfeea60d0) at app.cpp:95 #29 0x0084e1ee in kdemain (argc=0, argv=0x0) at main.cpp:44 #30 0x0804880b in main ()
I've had a similar crash with Noatun after recompiling KDE (3.5, Noatun 2.10.0) to use arts, before re-starting the aRts daemon, Noatun would show the error message about arts but crash immediately. Without opening a file, Noatun would display the error message without crashing.