Just to note from the Rosegarden development team... We do not consider "JACK isn't running" issues to be bugs with Rosegarden, and neither should Ubuntu. JACK must be running in order for certain optional features to work, and anyone consulting Rosegarden's documentation should be aware of this fact, and should have generic, distro-independent resources explaining what to do about it if they want the features turned on.
The missing "snd-seq-midi" from most distributions in the last year or so has been a real problem, but about all we can do about this is what we now do in 1.4.0 (not yet in Ubuntu, but packaged for Debian Sid) which is say what amounts to "Your MIDI is busted. Try running "modprobe snd-seq-midi" and run this application again." I don't see how it's an application's fault that a distro's auto detection routines have suddenly decided nobody wants to use MIDI for some reason. This never used to be a problem, but now it's broken on many different distros. I don't think this is our problem upstream, and it isn't the "rosegarden" package maintainer's problem. This should be directed toward whoever maintains the hardware autodetection routines. This missing module affects the entire spectrum of users who want to do MIDI on Linux. (So does the new default 250 Hz kernel timer. Bleck.) -- Rosegarden does not start successfully by default in Dapper. https://launchpad.net/bugs/36801 -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
