Urgh. I’ve got a bug report from a (Linux) user of my SDL/SDL_mixer-based
program complaining of
mcop warning: user defined signal handler found for SIG_PIPE, overriding
at startup and
icebreaker: relocation error: /usr/lib/libmcop.so.0: undefined symbol:
internalFreeAll__Q24Arts14StartupManager
at shutdown. (“icebreaker” being the executable).
I can recreate this if I try to start up the program when all audio devices
are busy, but the user reports that he sees this every time. Any clues? I’d
like to fix both cases. Problem occurs with SDL_Mixer 1.1 and 1.2.3 both…–
Matthew Miller @Matthew_Miller http://www.mattdm.org/
Boston University Linux ------> http://linux.bu.edu/
Urgh. I’ve got a bug report from a (Linux) user of my SDL/SDL_mixer-based
program complaining of
mcop warning: user defined signal handler found for SIG_PIPE, overriding
I’m not sure if anyone else will mention this but almost -all- the time I
run 'artsdsp -m ’ I see this. Suspect it’s probably part of
artsd not SDL…
at startup and
icebreaker: relocation error: /usr/lib/libmcop.so.0: undefined symbol:
internalFreeAll__Q24Arts14StartupManager
at shutdown. (“icebreaker” being the executable).
Oh fun. Sounds like not-quite-compatible C++ libs for artsd as well…
I tend to compile SDL with artsd disabled these days and use "artsdsp -m"
on the program when I need to hear it.
What systems are involved by the way? I myself am using debian-unstable,
have seen the first but not the second.
G’day, eh? 
- TeunisOn Tue, 21 May 2002, Matthew Miller wrote:
I’m not sure if anyone else will mention this but almost -all- the time I
run 'artsdsp -m ’ I see this. Suspect it’s probably part of
artsd not SDL…
Oh, yeah, I should have mentioned that. I totally blame artsd in some way.
However, I’m running under Window Maker, and the bug-reporting user is under
Gnome – artsd shouldn’t be sticking its nose in, should it?
What systems are involved by the way? I myself am using debian-unstable,
have seen the first but not the second.
Red Hat Linux 7.1 (user) and 7.2 (me).On Tue, May 21, 2002 at 12:06:44AM -0700, Teunis Peters wrote:
–
Matthew Miller @Matthew_Miller http://www.mattdm.org/
Boston University Linux ------> http://linux.bu.edu/
I used to get exactly the same problem. I’m running RH7.2 and KDE 2.2.1.
ARTS is run at start up and it would cause any SDL prog (maybe just those
that used the mixer) to give the mcop warning message.
I got around this by telling ARTS to suspend after 20 seconds of inactivity.
So… basically after I have used another prog like XMMS that uses ARTS I
just wait 20 seconds for the little pop of arts suspending before running
the prog.
Hope that’s of some help.> -----Original Message-----
From: Matthew Miller [SMTP:mattdm at mattdm.org]
Sent: Tuesday, May 21, 2002 2:43 PM
To: sdl at libsdl.org
Subject: Re: [SDL] sdl mixer and mcop errors?
On Tue, May 21, 2002 at 12:06:44AM -0700, Teunis Peters wrote:
I’m not sure if anyone else will mention this but almost -all- the time
I
run 'artsdsp -m ’ I see this. Suspect it’s probably part of
artsd not SDL…
Oh, yeah, I should have mentioned that. I totally blame artsd in some way.
However, I’m running under Window Maker, and the bug-reporting user is
under
Gnome – artsd shouldn’t be sticking its nose in, should it?
What systems are involved by the way? I myself am using
debian-unstable,
have seen the first but not the second.
Red Hat Linux 7.1 (user) and 7.2 (me).
–
Matthew Miller mattdm at mattdm.org http://www.mattdm.org/
Boston University Linux ------> http://linux.bu.edu/
SDL mailing list
SDL at libsdl.org
http://www.libsdl.org/mailman/listinfo/sdl
Hmmm. An okay workaround for an individual end-user, but for a developer who
just wants his program to not produce arcane error messages, that doesn’t
help much. Is statically linking to an SDL which isn’t compiled against arts
the only answer? Is that even an answer?On Tue, May 21, 2002 at 03:06:36PM +0100, Sweeney, Steven (FNB) wrote:
I used to get exactly the same problem. I’m running RH7.2 and KDE 2.2.1.
ARTS is run at start up and it would cause any SDL prog (maybe just those
that used the mixer) to give the mcop warning message.
I got around this by telling ARTS to suspend after 20 seconds of inactivity.
So… basically after I have used another prog like XMMS that uses ARTS I
just wait 20 seconds for the little pop of arts suspending before running
the prog.
–
Matthew Miller @Matthew_Miller http://www.mattdm.org/
Boston University Linux ------> http://linux.bu.edu/