Won't start in PCLOS

• Jul 7, 2010 - 22:02

I installed V 0.9.6-1 about 10 days ago (using Synaptic on PCLinux) and it worked great! But on Saturday I got the splash screen then nothing - not even an error message that would have helped. I've tried uninstalling & reinstalling, I've done the same with timidity and fluidsynth to see if it's those causing the problem. I've run mscore -F. I've tried amending the config file and deleting it altogether (after backing up of course). I can't find any .log files recording errors.

Any ideas anyone?


Comments

In reply to by David Bolton

I hope I've got this right - I used Ctrl Alt and F1 to get a terminal window. Then I logged in, and typed Mscore, getting that message and nothing else. I've not yet found out how to get back to the GUI without restarting with Ctrl alt del. Sorry, this may be my limited Linux skills.
Should I have been in a window within the GUI session?
Thanks for your help.

In reply to by PomPrint_

I thought that was it but Ctrl alt F7 got me to a screen that said something like "finding new hardware" and stuck. But as I've had help to get me to a terminal window in gui it doesn't matter. But thanks for your help.

Steve too!

In reply to by dewin_

Could you copy and paste the full contents of what is displayed on screen? Also you could try mscore -d to start MuseScore in debug mode and hopefully output a little more information before the crash.

In reply to by dewin_

Could you attach the file: ~/.config/MusE/MuseScore.ini

(You will probably need to change the file extension from ".ini" to ".txt" in order to attach it to a comment on this forum)

Do you have the 'Use internal synthesizer' box ticked on the I/O tab in the preferences and, if so, which of the three outputs have you selected? If Jack is ticked and is not running, this causes the problem that you have described. Try starting Jack, if you have it, and see if that helps.

Steve

In reply to by PomPrint_

Thanks to everyone for your help.

I've run xterm, entered mscore. I get "segmentation fault". I'll Google that later.

Steve: I can't see whether "use internal synthesizer" box is ticked, because it doesn't get that far. I think I was using Fluidsynth. I can't see fluidsynth or Jack in the process list, but I might not recognise them. Timidity is running.

I've typed jack and fluidsynth into the command line before running mscore - but no joy I'm afraid.

In reply to by dewin_

If all else fails, I suggest that you try using the 'Force Version' in the Synaptic Package Manager to downgrade to an earlier version. This has worked for me in the past. This can be found on the 'Package' menu.

Just type musescore in the quick search bar, highlight musescore, click on package and then select 'Force Version'

Hope this helps.

Steve

In reply to by dewin_

The only change I made to the 0.9.6.1 package is the fonts. This is the same change that I made to the 0.9.5 packages. The 0.9.6.1 version works on my machine without errors. Whatever the problem is on your machine, it is unlikely that an earlier version would fix it. It definitely would not work to use a package from a different distro. Building from source would likely work fine. It is not hard but it takes a while to build. The best solution, though, would be to find out what is wrong, so that if necessary I can rebuild the package.

The default settings are to use the built in synthesizer and alsa audio. I do not have pulse audio running, so I haven't tested if that interferes. I also don't have jack running. If you give more information, either here or at pclinuxos.com/forum, I'm sure we can get to the bottom of this.

Galen

I currently am running 0.9.6.1-1pclos, not 0.9.6-1pclos. The newer version is not in the repos yet, but it is on the way. This may provide the fix that you need. (If not, I will continue to look into it.)

Galen

In reply to by gseaman

Thanks everyone for your help and suggestions. I was going to have a go at compiling it as suggested, but today I ran an update everything on Synaptic and it's working! I noticed a few ALSA items in the update list, so maybe that was it. Anyway, I can get on with using it now. Fingers crossed!

Do you still have an unanswered question? Please log in first to post your question.