On Sat, Aug 27, 2005 at 01:16:39PM +0200, Daniel Kobras wrote :
> severity 325064 important
> thanks
> 
> On Fri, Aug 26, 2005 at 09:53:37PM +0200, Brice Méalier wrote:
> > Starting program: /usr/bin/muse 
> > [Thread debugging using libthread_db enabled]
> > [New Thread -1222887744 (LWP 12558)]
> > /usr/bin/mozilla-firefox
> > no locale <muse_en_US>/</usr/share/muse/locale>
> > open projectfile: No such file or directory
> > starting with default template
> > [New Thread -1229898832 (LWP 12592)]
> > [New Thread -1238287440 (LWP 12593)]
> > [New Thread -1246676048 (LWP 12594)]
> > [New Thread -1255064656 (LWP 12595)]
> > cca_open_socket: could not connect to host 'localhost', service '14541'
> > cca_init: could not connect to server 'localhost' - disabling ladcca
> > midiSeqRunning = 1 watchMidi 0
> > midiSeqRunning = 1 watchMidi 0
> > midiSeqRunning = 1 watchMidi 0
> > WatchDog: fatal error, realtime task timeout
> >    (0,140-3) - stopping all services
> 
> Okay, thanks. So the random SIGSEGVs seem to be a symptom rather than
> the cause of this problem. Digging into the source code a bit, the final
> line I quoted above indicates there's something fishy about your Alsa
> setup, though. In particular, muse apparently does not receive timer
> tick events from Alsa. Alas, I'm not very familiar with Alsa these days
> and don't have a clue why those ticks might get lost. Is there anything
> special about your installation? Anyway, as this problem seems to be
> specific to certain setups, I'm lowering the severity of this bug report.
> 

Hummm no idea about what could be the cause!! I use alsa from unstable
because one bug has been solved only in unstable (the loading of the
sequencer module). Apart from that I use the realtime-lsm module for
jackd and that's all.


Best regards,

-- 
Brice Méalier
[EMAIL PROTECTED]
Linux user nb. 372699
Debian GNU/Linux testing
-----
"Unix IS user friendly, it is just selective about who his friends are"


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to