Muse not running after Ubuntu Studio 18.04.1 upgrade

MusE is a MIDI/Audio sequencer with recording and editing capabilities, aiming to be a complete multitrack virtual studio for Linux. http://muse-sequencer.org/

Moderators: khz, MattKingUSA, spamatica

Plug&Play
Established Member
Posts: 25
Joined: Sat Jan 14, 2017 2:09 am

Muse not running after Ubuntu Studio 18.04.1 upgrade

Postby Plug&Play » Tue Feb 05, 2019 8:09 pm

This may not be a muse problem, I have little experience with this sort of problem.

I recently installed MusE on Ubuntu Studio 16.04 . I downloaded it, installed qt5 and <something TBD>, ran 'compile_muse.sh' and did the build and install... all from the CLI. It was working, and I like it!

I upgraded my system to Ubuntu Studio 18.04.1 with no problems, but Muse did not work:
from my notes
reboot, retry running muse, same result: the splash image "MusE 3.02" (whatever) opens then closes, the end.
YES I opened & started qjackctl before I tried to open muse from the gui "Audio Production" menu.
After fail, when I close JACK, it complains that there is an application open. There are no zombies in the JACK connection diagram.


I tried to uninstall and re-compile, rebuild, install. Something changed: when I open from the command line I see a different MusE splash screen! There are errors and warnings, but the gui does open, but when I open a project file, I see 5 piano rolls, and nothing works - no play, can't close the piano rolls.

Back at the command line, there were a bunch of errors like

Code: Select all

(menulibre:4745): Gtk-WARNING **: 11:35:35.053: Theme parsing error:


I want a do-over! But I do not have permission to remove the menu entry using LibreMenu, and already tried rebuilding the code.
I think if I can undo the menu entry and uninstall muse that it will work if I start from scratch, except no need to download the installation files.

Any pointers on how to get unstuck are greatly appreciated.

Rob

Music Music Music !

spamatica
Established Member
Posts: 193
Joined: Mon Feb 08, 2010 10:38 am

Re: Muse not running after Ubuntu Studio 18.04.1 upgrade

Postby spamatica » Tue Feb 05, 2019 9:20 pm

Hi Rob,

that sounds wierd indeed.

The muse built from source will be called muse3, are you sure this is the one you are starting?
Possibly there is a 'muse' installed by Ubuntu Studio.

If we keep to the console, check:

Code: Select all

which muse3

to find out which actual binary you are trying to execute

If all that seems fine, run:

Code: Select all

muse3 -v

it will print the version and where the configuration file resides.

If the version is fine, try renaming the MusE.cfg file to make MusE do a fresh start.

If all that fails I need some more clues, a screenshot and a copy of the console log from a startup might make it clearer?

Plug&Play
Established Member
Posts: 25
Joined: Sat Jan 14, 2017 2:09 am

Re: Muse not running after Ubuntu Studio 18.04.1 upgrade

Postby Plug&Play » Wed Feb 06, 2019 12:54 am

thank you for the suggestions - I can't follow though this afternoon, but will in the next 24. I will try to find the manifest for Ubuntu 18.04.1. I know tried

Code: Select all

$ muse -v
in 16.04 before I downloaded it, but it never occurred to me try "muse3". When I installed "the latest" from the MusE website, to Ubuntu 16.04, I could invoke it with "muse".

Confirmed - muse is not in the manifest of Ubuntu Studio 18.04

more soon - & thanks again

Rob

Music Music Music !

Plug&Play
Established Member
Posts: 25
Joined: Sat Jan 14, 2017 2:09 am

Re: Muse not running after Ubuntu Studio 18.04.1 upgrade

Postby Plug&Play » Wed Feb 06, 2019 6:15 pm

I am having other problems, I am unable to remove MusE from my LibreMenu, and in LibreMenu there is a list of errors
Parsing-errors.png


I started MusE today, and noticed that the splash image does indicate version 2
however, when I looked in the extracted install folder, I only found this!
splash.png


I have a folder muse-3.0.2
I downloaded from
https://sourceforge.net/projects/lmuse/ ... z/download

Yet, when I look at the version ---

Code: Select all

Studio7010:...~$ muse -v
Config File </home/rob/.config/MusE/MusE.cfg>
muse: Linux Music Editor; Version 2.1.2, (svn revision 0)


After further investigation (looking in BASH history), I discovered that I had attempted to install from the repository

Code: Select all

sudo apt install muse

Am I completely screwed? If I have to reinstall Ubuntu, it will be a full install.


I don't know what to make of it - and I do not know how to get back to a sane starting place.
Spanatica: Is this the "console log from a startup" that you wanted?

Code: Select all

Studio7010:...Downloads$ muse %f
Config File </home/rob/.config/MusE/MusE.cfg>
LOCALE en_US
Denormal protection enabled.
Trying RTC timer...
RtcTimer::setTimerFreq(): cannot set freq 1024 on /dev/rtc: Permission denied
  precise timer not available, check file permissions and allowed RTC freq (/sys/class/rtc/rtc0/max_user_freq)
Trying ALSA timer...
AlsaTimer::initTimer(): best available ALSA timer: system timer
got timer = 79
Aquired timer frequency: 1000
dlopen(/usr/lib/dssi/whysynth.so) failed: /usr/lib/dssi/whysynth.so: undefined symbol: dssp_voicelist_mutex_unlock
no more csLADSPA plugins
scanDSSILib: dlopen(/usr/lib/dssi/whysynth.so) failed: /usr/lib/dssi/whysynth.so: undefined symbol: dssp_voicelist_mutex_unlock
JACK: buffersize changed 256
MusE: JackAudioDevice::realtimePriority: JACK is not running realtime
Audio::shutdown()
midi thread 2753 _NOT_ running SCHED_FIFO


~~~~ 10:59 AM Wednesday 06 Feb 2019 ~~~~
I was able to remove it, now there is no sign of it, not in the LibreMenu, not from the CLI

Code: Select all

sudo dpkg -r muse

I will report results of attempting to compile and install 3.02, again
You do not have the required permissions to view the files attached to this post.

Rob

Music Music Music !

Plug&Play
Established Member
Posts: 25
Joined: Sat Jan 14, 2017 2:09 am

Re: Muse not running after Ubuntu Studio 18.04.1 upgrade

Postby Plug&Play » Wed Feb 06, 2019 7:50 pm

Progress!

Code: Select all

Studio7010:...build$ which muse3
/usr/local/bin/muse3
Studio7010:...build$ muse3 -v
Config File </home/rob/.config/MusE/MusE.cfg>
configuration: unknown tag <dummyAudioBufSize> at line 17
configuration: unknown tag <dummyAudioSampleRate> at line 18

***WARNING***
Loaded config file version is 2.0
Current version is 3.1
Conversions may be applied!

(muse3:10169): Gtk-WARNING **: 11:32:13.577: Theme parsing error: gtk.css:597:14: not a number

Plus about 23 more similar errors.

Next, I hid the config file, and tried again.
All the GTK errors, but no " ***WARNING*** Loaded config file version is 2.0"

Code: Select all

Studio7010:...MusE$ muse3 -v
creating new config...
  success.
Config File </home/rob/.config/MusE/MusE.cfg>
configuration: unknown tag <dummyAudioBufSize> at line 21
configuration: unknown tag <dummyAudioSampleRate> at line 22

(muse3:10453): Gtk-WARNING **: 11:40:15.502: Theme parsing error: gtk.css:597:14: not a number


Finally, if I try to run it

Code: Select all

Studio7010:...MusE$ muse3 %f
Config File </home/rob/.config/MusE/MusE.cfg>
configuration: unknown tag <dummyAudioBufSize> at line 21
configuration: unknown tag <dummyAudioSampleRate> at line 22

(muse3:10520): Gtk-WARNING **: 11:53:40.199: Theme parsing error: gtk.css:597:14: not a number
# 23 more errors not shown
QApplication: invalid style override passed, ignoring it.
LOCALE en_US
Denormal protection enabled.
Select audio device from configuration : 0
User JackAudio backend - backend selected through configuration
MusE:initJackAudio: jack_get_version() returned zeros. Setting version major to 1.
Using Jack
free(): invalid pointer
Aborted (core dumped)

Rob

Music Music Music !

spamatica
Established Member
Posts: 193
Joined: Mon Feb 08, 2010 10:38 am

Re: Muse not running after Ubuntu Studio 18.04.1 upgrade

Postby spamatica » Wed Feb 06, 2019 8:01 pm

Looks like you got rid of the muse 2.x version, which is good.
It is very old. Sad that we haven't been able to get a more recent version into the repos...

Running muse3 in the end looks promising, not sure how far you got, is it working?
The GTK errors should be harmless anyway, they should not be directly related to muse.

Plug&Play
Established Member
Posts: 25
Joined: Sat Jan 14, 2017 2:09 am

Re: Muse not running after Ubuntu Studio 18.04.1 upgrade

Postby Plug&Play » Thu Feb 07, 2019 12:25 am

It is not working.
I displays a splash screen (3.2) and then crashes with a core dump.

Code: Select all

QApplication: invalid style override passed, ignoring it.
LOCALE en_US
Denormal protection enabled.
Select audio device from configuration : 0
User JackAudio backend - backend selected through configuration
MusE:initJackAudio: jack_get_version() returned zeros. Setting version major to 1.
Using Jack
free(): invalid pointer
Aborted (core dumped)


ouch.

Rob

Music Music Music !

Plug&Play
Established Member
Posts: 25
Joined: Sat Jan 14, 2017 2:09 am

Re: Muse not running after Ubuntu Studio 18.04.1 upgrade

Postby Plug&Play » Thu Feb 07, 2019 6:52 am

I just read through the thread
can't start muse3 - invalid pointer

https://linuxmusicians.com/viewtopic.php?f=61&t=18140&p=89952&hilit=free+%3A+invalid+pointer#p89952

It is interesting that the problems went away when sndrnrvk changed to Ubuntu Studio 16.04. My system was working until I upgraded from 16.04 to 18.04.1

I admit that my installation of MusE was clumsy - I had version 2 installed at the same time - neither worked.

Also, in that thread spamatica wrote
The gtk.css errors I've never seen before, we don't have any such file.
I wonder if that is diagnostic? I see those errors as well.

BTW - I had not actually used JACK since the upgrade: I confirmed that it is wokring by running Qtractor, Yoshimi and QJackCtl with no problems. Editing in MusE is a lot more fun!

Rob

Music Music Music !

spamatica
Established Member
Posts: 193
Joined: Mon Feb 08, 2010 10:38 am

Re: Muse not running after Ubuntu Studio 18.04.1 upgrade

Postby spamatica » Thu Feb 07, 2019 4:13 pm

Apart from the MusE.cfg file I think it should be quite safe having multiple MusE versions installed so I don't believe the problems originate from this.

The crash probably originates from one of two sources.
1. jack
2. a plugin that for some reason causes muse to crash

To check the first, try running MusE with another backend.
Running without audio (using MusE purely as a sequencer) always exist

Code: Select all

muse3 -a

If you check the help

Code: Select all

muse3 -h

You can check if the '-t Use RtAudio driver' option exists. In which case you can start

Code: Select all

muse3 -t

If you aren't using jack for anything but MusE this might be an option (responsiveness of the audio is worse though)

For the second point, plugins. You can start MusE without plugins using:

Code: Select all

muse3 -pNI2

If that works you can experiment with the options and maybe find out which type of plugin causes the crash.
Also running muse with more debug to the console will pinpoint what MusE was doing right before the crash.

Code: Select all

muse3 -D

Plug&Play
Established Member
Posts: 25
Joined: Sat Jan 14, 2017 2:09 am

Re: Muse not running after Ubuntu Studio 18.04.1 upgrade

Postby Plug&Play » Thu Feb 07, 2019 8:45 pm

Code: Select all

$ muse3 -t
is unavailable

Code: Select all

$ muse3 -D
showed very many ladspa drives loaded until

Code: Select all

loadPluginLib: adding ladspa plugin:/usr/lib/ladspa/cs_phaser.so name:Phaser1 with LFO label:Phaser1+LFO required features:0
free(): invalid pointer
Aborted (core dumped)
where it crashed.

I had modest success with

Code: Select all

$ muse3 -pN2D

The system crashed when I selected one internal synth, but seems to work with the generic Organ. By working, I mean that I could create a midi track, edit it with pianoroll, and play it back and save it - I didn't try to get audio out.

This is probably enough to allow me to continue with the project I am working on, but I am still interested in obtaining full functionality, and in contributing anything I can to the general knowledge if I am able.

Thanks for the help with this problem.

Rob

Music Music Music !

Tim E. Real
Established Member
Posts: 206
Joined: Sat Sep 15, 2012 12:36 am

Re: Muse not running after Ubuntu Studio 18.04.1 upgrade

Postby Tim E. Real » Thu Feb 07, 2019 10:07 pm

Hello. If I understand correctly you have the release 3.0.2.
What you are experiencing is bad plugins crashing MusE during plugin scanning.

Please try the git master version of MusE.
https://github.com/muse-sequencer/muse
As shown on that page, it is typically pulled from a command line while in some desired source folder with this command:
"git clone https://github.com/muse-sequencer/muse.git"

A safe plugin scanner was added in the last few months:
viewtopic.php?f=61&t=19166

Sorry for your pain, seems almost everyone who has certain other packages containing errant plugins, had this same problem.
But, at least you are already set up to build it once pulled :wink:

It's been a year since last release. The ChangeLog will show massive interesting changes :)

Plug&Play
Established Member
Posts: 25
Joined: Sat Jan 14, 2017 2:09 am

Re: Muse not running after Ubuntu Studio 18.04.1 upgrade

Postby Plug&Play » Fri Feb 08, 2019 4:16 am

Tim -

I will get on that in the AM. Just to clarify , I downloaded and installed Muse 3.02 from
https://sourceforge.net/projects/lmuse/%20...%20z/download

Also, after upgrading Ubuntu Studio to 18.04, I installed WaoN, which needed

Code: Select all

$ sudo apt-get install qt5-default qttools5-dev qttools5-dev-tools
$ sudo apt-get  install libqt5svg5  libqt5svg5-dev  libqt5svg5-private-dev

I am concerned that I may have changed a package that was provided by Ubuntu Studio

Otherwise, do you have any idea what this string of Gtk-WARNINGs are related to? Is this unusual?
[codeStudio7010:...~$ muse3 -D
Config File </home/rob/.config/MusE/MusE.cfg>

(muse3:5739): Gtk-WARNING **: 20:00:39.431: Theme parsing error: gtk.css:597:14: not a number

(muse3:5739): Gtk-WARNING **: 20:00:39.431: Theme parsing error: gtk.css:597:14: Expected a string.

(muse3:5739): Gtk-WARNING **: 20:00:39.431: Theme parsing error: gtk.css:600:17: Expected a string.

(muse3:5739): Gtk-WARNING **: 20:00:39.432: Theme parsing error: gtk.css:784:14: not a number

(muse3:5739): Gtk-WARNING **: 20:00:39.432: Theme parsing error: gtk.css:784:14: Expected a string.

(muse3:5739): Gtk-WARNING **: 20:00:39.432: Theme parsing error: gtk.css:787:17: Expected a string.

(muse3:5739): Gtk-WARNING **: 20:00:39.433: Theme parsing error: gtk.css:1096:14: not a number

(muse3:5739): Gtk-WARNING **: 20:00:39.433: Theme parsing error: gtk.css:1096:14: Expected a string.

(muse3:5739): Gtk-WARNING **: 20:00:39.433: Theme parsing error: gtk.css:1099:17: Expected a string.

(muse3:5739): Gtk-WARNING **: 20:00:39.437: Theme parsing error: gtk.css:2286:8: not a number

(muse3:5739): Gtk-WARNING **: 20:00:39.437: Theme parsing error: gtk.css:2286:18: Using Pango syntax for the font: style property is deprecated; please use CSS syntax

(muse3:5739): Gtk-WARNING **: 20:00:39.437: Theme parsing error: gtk.css:2291:8: not a number

(muse3:5739): Gtk-WARNING **: 20:00:39.437: Theme parsing error: gtk.css:2291:18: Using Pango syntax for the font: style property is deprecated; please use CSS syntax

(muse3:5739): Gtk-WARNING **: 20:00:39.441: Theme parsing error: gtk.css:4357:14: not a number

(muse3:5739): Gtk-WARNING **: 20:00:39.441: Theme parsing error: gtk.css:4357:14: Expected a string.

(muse3:5739): Gtk-WARNING **: 20:00:39.442: Theme parsing error: gtk.css:4419:12: not a number

(muse3:5739): Gtk-WARNING **: 20:00:39.442: Theme parsing error: gtk.css:4419:12: Expected a string.

(muse3:5739): Gtk-WARNING **: 20:00:39.442: Theme parsing error: gtk.css:4428:16: not a number

(muse3:5739): Gtk-WARNING **: 20:00:39.442: Theme parsing error: gtk.css:4428:16: Expected a string.

(muse3:5739): Gtk-WARNING **: 20:00:39.442: Theme parsing error: gtk.css:4443:22: not a number

(muse3:5739): Gtk-WARNING **: 20:00:39.442: Theme parsing error: gtk.css:4443:22: Expected a string.

(muse3:5739): Gtk-WARNING **: 20:00:39.442: Theme parsing error: gtk.css:4499:12: Expected a string.

(muse3:5739): Gtk-WARNING **: 20:00:39.442: Theme parsing error: gtk.css:4501:16: not a number

(muse3:5739): Gtk-WARNING **: 20:00:39.442: Theme parsing error: gtk.css:4501:16: Expected a string.

(muse3:5739): Gtk-WARNING **: 20:00:39.442: Theme parsing error: gtk.css:4549:12: not a number

(muse3:5739): Gtk-WARNING **: 20:00:39.442: Theme parsing error: gtk.css:4549:12: Expected a string.
QApplication: invalid style override passed, ignoring it.
LOCALE en_US
QtLibraryPath:
</usr/lib/x86_64-linux-gnu/qt5/plugins>
][/code]

I will get back to you after re-installing muse3 as you suggested.

Thank you for your help with this.

Rob

Music Music Music !

Tim E. Real
Established Member
Posts: 206
Joined: Sat Sep 15, 2012 12:36 am

Re: Muse not running after Ubuntu Studio 18.04.1 upgrade

Postby Tim E. Real » Fri Feb 08, 2019 5:00 am

Yup that's the official release version, a year old.
The git master version rocks much better. I hope you'll enjoy it.
Hopefully a new release will be out soon.

We don't use any Gtk code in MusE, except for some LV2 Plugin UI support.

What you are probably seeing is hopefully just a theme selection problem, as indicated at the bottom of the post.

After getting MusE to run (regardless of version) go to menu "Settings > Appearance Settings" and go to the "Style/Fonts" tab.
At the top of the tab there is a drop-down box from which a theme can be chosen.
My guess is that it's already on "Gtk2" or similar, or your system is actually running Gnome and the setting says
"Keep Qt system style" meaning Gtk.

So try picking a different theme like "Breeze" or "Oxygen" or "Fusion".
Please restart MusE for it to take effect.

Plug&Play
Established Member
Posts: 25
Joined: Sat Jan 14, 2017 2:09 am

Re: Muse not running after Ubuntu Studio 18.04.1 upgrade

Postby Plug&Play » Fri Feb 08, 2019 8:49 pm

Success! I seem to be back in business.

I followed the instructions in the README, except that I used wget to download the zip file.
I was not able to extract it with tar, but the file manager was able to do it.
I also had to manually remove the old icon in the gui launcher - actually removing the target from /usr/applications did it.

Thank you spamatica and Tim for your help with this, it is obvious that you are busy with other things in this project, and I know front line user help is a distraction.

Regards,

Rob

Music Music Music !


Return to “MusE Sequencer”

Who is online

Users browsing this forum: No registered users and 0 guests