[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#374716: rosegarden4 crashes if snd-seq-midi is not loaded



Package: rosegarden
Version: 4-1.2.3

Hi,

If I run rosegardensequencer, it crashes immediately. If jackd is not
running, I get output like the following:

Rosegarden 4-1.2.3 - AlsaDriver - alsa-lib version 1.0.11

JackDriver::initialiseAudio - JACK server not running
ALSA lib seq_hw.c:457:(snd_seq_hw_open) open /dev/snd/seq failed: No
such file or directory
AlsaDriver::initialiseMidi - couldn't open sequencer - No such file or
directory
rosegardensequencer: seq.c:1055: snd_seq_poll_descriptors_count:
Assertion `seq' failed.
KCrash: Application 'rosegardensequencer' crashing...


If jackd is running, I get the following instead:

Rosegarden 4-1.2.3 - AlsaDriver - alsa-lib version 1.0.11

JackDriver::initialiseAudio - JACK sample rate = 44100Hz, buffer size
= 1024
JackDriver::initialiseAudio - creating disk thread
JackDriver::initialiseAudio - found 2 JACK physical outputs
JackDriver::initialiseAudio - connecting from "rosegarden:master out
L" to "alsa_pcm:playback_1"
JackDriver::initialiseAudio - connecting from "rosegarden:master out
R" to "alsa_pcm:playback_2"
JackDriver::initialiseAudio - found 2 JACK physical inputs
JackDriver::initialiseAudio - connecting from "alsa_pcm:capture_1" to
"rosegarden:record in 1 L"
JackDriver::initialiseAudio - connecting from "alsa_pcm:capture_2" to
"rosegarden:record in 1 R"
JackDriver::initialiseAudio - initialised JACK audio subsystem
ALSA lib seq_hw.c:457:(snd_seq_hw_open) open /dev/snd/seq failed: No
such file or directory
AlsaDriver::initialiseMidi - couldn't open sequencer - No such file or
directory
rosegardensequencer: seq.c:1055: snd_seq_poll_descriptors_count:
Assertion `seq' failed.
KCrash: Application 'rosegardensequencer' crashing...
zombified - calling shutdown handler


The crashes go away if I modprobe snd-seq-midi before running
rosegardensequencer.

Ethan

Attachment: signature.asc
Description: OpenPGP digital signature


Reply to: