Muse does not start

Bug #677931 reported by igi on 2010-11-20
20
This bug affects 3 people
Affects Status Importance Assigned to Milestone
muse (Ubuntu)
Undecided
Unassigned

Bug Description

Binary package hint: muse

After launching muse from the Application menu, Muse splash screen appears, but then the program exits.

If I run it from the terminal, I get segmentation faults:
__
igor@igi-desktop:~$ muse
Denormal protection enabled.
Muse: __i386__ or __x86_64__ defined. Using optimized float buffer copying (asm movsl).
Muse: using unoptimized non-SSE dsp routines
no locale <muse_it_IT.utf8>/</usr/share/muse/locale>
Trying RTC timer...
fatal error: open /dev/rtc failed: Permesso negato
hint: check if 'rtc' kernel module is loaded, or used by something else
Trying ALSA timer...
AlsaTimer::initTimer(): best available ALSA timer: system timer
got timer = 49
open projectfile: Nessun file o directory
starting with default template
WARNING: Cannot lock memory:: Impossibile allocare memoria
JACK ERROR: Cannot use real-time scheduling (RR/5)(1: Funzione non permessa)
JACK ERROR: AcquireRealTime error
JACK ERROR: JackPosixSemaphore::TimedWait err = Chiamata di sistema interrotta
MusE: JackAudioDevice::realtimePriority: JACK is not running realtime
MusE: WARNING: Recommend setting audio realtime priority to at least 5!
Cannot set scheduling priority -5 for RT thread (Funzione non permessa)
creating thread <Prefetch> failed: Argomento non valido
JACK ERROR: JackPosixSemaphore::TimedWait err = Chiamata di sistema interrotta
JACK ERROR: JackPosixSemaphore::TimedWait err = Chiamata di sistema interrotta
JACK ERROR: JackPosixSemaphore::TimedWait err = Chiamata di sistema interrotta
AlsaTimer::setTimerTicks(): requested freq 1024 Hz too high for timer (max is 250)
  freq stays at 250 Hz
JACK ERROR: JackPosixSemaphore::TimedWait err = Chiamata di sistema interrotta
Cannot set scheduling priority -2 for RT thread (Funzione non permessa)
creating thread <Midi> failed: Argomento non valido
looping waiting for sequencer thread to start
looping waiting for sequencer thread to start
looping waiting for sequencer thread to start
looping waiting for sequencer thread to start
looping waiting for sequencer thread to start
looping waiting for sequencer thread to start
looping waiting for sequencer thread to start
looping waiting for sequencer thread to start
looping waiting for sequencer thread to start
looping waiting for sequencer thread to start
midi sequencer thread does not start!? Exiting...
Segmentation fault
---
Architecture: i386
DistroRelease: Ubuntu 11.04
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
Package: muse 1.1-0ubuntu3
PackageArchitecture: i386
ProcEnviron:
 LANGUAGE=it_IT:en
 PATH=(custom, no user)
 LANG=it_IT.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.38-8.42-generic-pae 2.6.38.2
Tags: natty running-unity
Uname: Linux 2.6.38-8-generic-pae i686
UpgradeStatus: Upgraded to natty on 2011-04-29 (2 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

igi (igor-cali) wrote :
description: updated
Fabrice Coutadeur (fabricesp) wrote :

Hi,

Could you try to run muse as root running the following command from a terminal window:
sudo muse
and paste the output in this bug report?

Thanks,
Fabrice

André Pirard (a.pirard) wrote :

Salut Fabrice, Hi igi,

In my case, Ubuntu 10.04 up to date and Muse 1.1
same problem: Muse won't start unless Jack is started.
Looks like Muse isn't getting enough precision from the rtc.
Running Muse as root allows it of course.
Otherwise, it wants Jack for its timer.

To allow enough rtc precision to underprivileged mode, type:
$ sudo sh -c "echo 1024 > /proc/sys/dev/hpet/max-user-freq"

To be able to run Muse, the system should allow users to set rtc frequencies up to 1024 Hz.

André Pirard (a.pirard) wrote :

Oops, sorry, I had left Jack running :-(
The command does not set the required permission.
But I think the reasoning is at least half correct.
When will we have comment update?

Here is my root Muse trace:

$ sudo muse
Denormal protection enabled.
no message buffer overruns
cannot connect to jack server
cannot create jack client
no locale <muse_en_US.utf8>/</usr/share/muse/locale>
Trying RTC timer...
got timer = 50
starting with default template
  name2route: <alsa_pcm:playback_1> not found
addRoute: invalid dst
  name2route: <alsa_pcm:playback_2> not found
addRoute: invalid dst
Get alsa timer for dummy driver:
AlsaTimer::initTimer(): best available ALSA timer: system timer
AlsaTimer::setTimerTicks(): warning: requested 86 Hz, actual freq is 125 Hz
audio dummy thread _NOT_ running SCHED_FIFO
lash_open_socket: could not connect to host 'localhost', service '14541'
lash_comm_connect_to_server: could not create server connection
lash_open_socket: could not connect to host 'localhost', service '14541'
lash_comm_connect_to_server: could not create server connection
lash_open_socket: could not connect to host 'localhost', service '14541'
lash_comm_connect_to_server: could not create server connection
lash_open_socket: could not connect to host 'localhost', service '14541'
lash_comm_connect_to_server: could not create server connection
lash_open_socket: could not connect to host 'localhost', service '14541'
lash_comm_connect_to_server: could not create server connection
lash_open_socket: could not connect to host 'localhost', service '14541'
lash_comm_connect_to_server: could not create server connection
lash_init: could not connect to server 'localhost' - disabling LASH
show did you know dialog!!!!
--- starts ---
Muse:checkAudioDevice: no audioDevice

André Pirard (a.pirard) wrote :

/proc/sys/dev/rtc/max-user-freq is the variable which should be set to 1024
According to http://manpages.ubuntu.com/manpages/lucid/en/man4/rtc.4.html
it should exist but it does not.
This seems to be the frequencies the kernel has been compiled for:
$ grep CONFIG_HZ /boot/config-`uname -r`
# CONFIG_HZ_100 is not set
CONFIG_HZ_250=y
# CONFIG_HZ_300 is not set
# CONFIG_HZ_1000 is not set
CONFIG_HZ=250

igi (igor-cali) wrote :

@André: I did not change the max-user-freq setting, since it was 64 per default, as specified.
Anyway I have rechecked my trace (in the description of this bug), and I have seen I had permission errors for rtc.
Trying to run both jack and muse as root, muse is properly starting. So I guess the solution is to properly set permissions for rtc folder when muse has to access it.

Changed in muse (Ubuntu):
status: New → Confirmed
cunnilinux (cunnilinux) wrote :

got the same situation on my system (11.04 development).

seems like the problem is:

jack_lsp
system:capture_1
system:capture_2
system:playback_1
system:playback_2

but

muse -Dd
(...snip...)
starting with default template
Song::clear
  name2route: <alsa_pcm:playback_1> not found
addRoute: invalid dst
  name2route: <alsa_pcm:playback_2> not found
addRoute: invalid dst

apport information

tags: added: apport-collected natty running-unity
description: updated
description: updated
André Pirard (a.pirard) wrote :

@igi & Canonical
Could you please explain (best in the bug description) which and how rtc permissions should be set?
Thanks.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers