[Bug 71372] New: noatun crashes on startup
psychonaut at nothingisreal.com
psychonaut at nothingisreal.com
Sun Dec 28 16:28:44 GMT 2003
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
http://bugs.kde.org/show_bug.cgi?id=71372
Summary: noatun crashes on startup
Product: noatun
Version: unspecified
Platform: SuSE RPMs
OS/Version: Linux
Status: UNCONFIRMED
Severity: crash
Priority: NOR
Component: general
AssignedTo: kde-multimedia at kde.org
ReportedBy: psychonaut at nothingisreal.com
Version: (using KDE KDE 3.1.4)
Installed from: SuSE RPMs
Noatun crashes on startup:
[psy at port-3106 ~]$ noatun
mcop warning: user defined signal handler found for SIG_PIPE, overriding
WARNING: Couldn't instanciate artsobject Noatun::Session. (This is normally caused by a broken package or compiling kdemultimedia in a --prefix different from arts. It may also be from two conflicting packages, so uninstall every arts/artsd package you have installed and try againe.
ERROR: Communication problem with noatun, it probably crashed.
[psy at port-3106 ~]$
Here is the backtrace:
(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)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...[New Thread 16384 (LWP 16268)]
(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)...
0x41a2da86 in waitpid () from /lib/i686/libpthread.so.0
#0 0x41a2da86 in waitpid () from /lib/i686/libpthread.so.0
#1 0x40c2c010 in KCrash::defaultCrashHandler(int) ()
from /opt/kde3/lib/libkdecore.so.4
#2 0x41a2c96c in __pthread_sighandler () from /lib/i686/libpthread.so.0
#3 <signal handler called>
#4 0x40063aac in Engine::initArts() () from /opt/kde3/lib/libnoatun.so.0
#5 0x40061bb6 in Engine::Engine(QObject*) () from /opt/kde3/lib/libnoatun.so.0
#6 0x4006a08b in Player::Player(QObject*) () from /opt/kde3/lib/libnoatun.so.0
#7 0x4006f37e in NoatunApp::NoatunApp() () from /opt/kde3/lib/libnoatun.so.0
#8 0x4001cd58 in main () from /opt/kde3/lib/kde3/noatun.so
#9 0x41e8dd17 in __libc_start_main () from /lib/i686/libc.so.6
#10 0x080486f1 in _start ()
Package was just installed a few minutes ago via the SuSE 9.0 RPMs. I see from Bug #47781 that this may be due to a faulty installation. Is this a problem with SuSE's RPMs, then? There's nothing arts-related on my machine that hasn't been installed from the SuSE 9.0 RPMs; I haven't manually installed anything from source.
If this is due to a conflicting package, is there any way of finding out which one it is besides trial and error?
More information about the kde-multimedia
mailing list