Bug 47781 - Noatun Crashes on startup
Summary: Noatun Crashes on startup
Status: RESOLVED NOT A BUG
Alias: None
Product: noatun
Classification: Miscellaneous
Component: general (show other bugs)
Version: unspecified
Platform: Compiled Sources Linux
: NOR crash
Target Milestone: ---
Assignee: Multimedia Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2002-09-12 07:18 UTC by ted
Modified: 2003-01-28 13:15 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Bugzilla Maintainers 2002-09-12 07:15:46 UTC
(*** This bug was imported into bugs.kde.org ***)

Package:           noatun
Version:           2.1.3 (CVS from 9/11/2002) (using KDE 3.0.7 CVS/CVSup/Snapshot)
Severity:          crash
Installed from:    Compiled sources
Compiler:          gcc --version 2.95.3 
OS:                Linux
OS/Compiler notes: From scratch system. built kde (and arts) from cvs 

Ok. there are similar bugs to this here.

This is the message I get on startup (as it crashes):
mcop warning: user defined signal handler found for SIG_PIPE overriding
noatun: 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: KUniqueApplication: DCOP communication error!

Both arts and kdemultimedia packages were compiled from cvs. I've never installed any other versions of the apps (on this system). They both were compiled with only one configure option "--prefix=/usr/local/kde" 

I only have one copy of artsd installed on the system.

Have any Ideas? I'm getting sick of xmms.


(Submitted via bugs.kde.org)
Comment 1 Charles Samuels 2002-09-14 06:13:38 UTC
Make sure you're running the correct artsd. 
 
This is not a bug, this is a bad install. 
 
Comment 2 davidsmind 2003-01-28 13:15:12 UTC
Duplicate of bug numbers 
37721: http://bugs.kde.org/show_bug.cgi?id=37721 
and 
23867: http://bugs.kde.org/show_bug.cgi?id=23867 
 
Plus It doesn't even effect latest CVS