Rosegarden 21.12 Crashes

[OmegAudio]

I hope that this helps someone.
I had recently re-installed my studio computer on Ubuntu 20.04, with the Low-Latency Kernel.
I have used Rosegarden for years, and tried to open an existing file.
And immediately Rosegarden would crash.
I could open Rosegarden and create a short four part MIDI project.
Save it and close it. Then try to open the same file and Crash.

I checked the Logs app and found messages where I could not find any reference.
After days of research I found nothing. No solution. Only reference to the same issue in 2010.
And that Rosegarden should be upgraded to a newer version that is way behind the current version.

Today I think I have found the solution through many trials and Crashes.
Open the Terminal: Ctrl+Alt+T
Then run Rosegarden using: sudo rosegarden

Rosegarden opens. Then allows me to open any existing file.
Edit a file and save. With no more crashes.
My assumption is that using the sudo command I am giving Rosegarden more privileges.
Which seems to over come the issue it has when running from the icon.
I have been able to repeat and reproduce this success over and over.
I hope this helps someone.

UPDATE
If I right click on each .rg file and check Permissions.
Owner is Me with Read and Write permissions.
And the Group is my user name.
All of the .rg files in my Home / Music show the same.
If I double click on a .rg file. The Rosegarden application opens, then crashes.

[bluebell]

I guess you started Rosegarden as root (with sudo) and after that it can't open some files for writing, e.g. .config/rosegardenmusic.conf or the directories and files of your song projects because they belong to root instead of your userid.

[folderol]

There is something extremely screwy there. You should definitely NOT run Rosegarden as root. I 've been running it for years with no such issues (currently under devuan). It sounds like something has the wrong user type.

[OmegAudio]

I guess you started Rosegarden as root (with sudo) and after that it can't open some files for writing, e.g. .config/rosegardenmusic.conf or the directories and files of your song projects because they belong to root instead of your userid.

I checked some of the .RG files from previous projects. When I right click and select Properties then select Permissions.
They show as Owner: Me with Read and Write access with the group being my user with Read and Write access..

This morning I uninstalled Rosegarden using the Ubuntu Software.
Then re-installed using Terminal command: sudo apt install rosegarden.
Rosegarden installed without issue.

I try to open Rosegarden then open one of the .rg files and again Rosegarden crashes.
If I open terminal and run: sudo rosegarden
I can then open a project file and edit and save without crashing.

Running Rosegarden with sudo seems to be a work around. I have used Rosegarden for years. And always was able to run the application from the Show Applications and the Rosegarden Icon. And open and edit existing files. Until recently when I reinstalled Ubuntu 22.04

[folderol]

Have you reported this to the Rosegarden devs? They are usually very supportive.

[Impostor]

Instead of running an application with sudo, which by consensus is a horrible idea, you could first find out if chowning everything in your home folder solves the problem.

Code: Select all

~$ sudo chown -R $USER:$USER ~

This assumes you're not logged in as root, which by consensus is also a horrible idea.

[bluebell]

I try to open Rosegarden then open one of the .rg files and again Rosegarden crashes.
If I open terminal and run: sudo rosegarden
I can then open a project file and edit and save without crashing.

Running Rosegarden with sudo seems to be a work around. I have used Rosegarden for years. And always was able to run the application from the Show Applications and the Rosegarden Icon. And open and edit existing files. Until recently when I reinstalled Ubuntu 22.04

Maybe starting Rosegarden with strace gives some hints:

Code: Select all

strace -eopen rosegarden

Then open a rg file.

[OmegAudio]

Instead of running an application with sudo, which by consensus is a horrible idea, you could first find out if chowning everything in your home folder solves the problem.

Code: Select all

~$ sudo chown -R $USER:$USER ~

This assumes you're not logged in as root, which by consensus is also a horrible idea.

Thank you for the help!
I checked all of the Rosegarden .rg files in my Home directory.
Which I created and copied to the Music Folder in Home.
When I right click and select Properties then select Permissions.
Owner is Me with Access being Read and Write.
Group is my user name with Read and Write access.
I do not see how making everything that is mine to be mine again, will make a difference.

I only use Rosegarden for MIDI, so no audio issues. When I run Rosegarden as sudo, everything works.
Just open from the Show Applications Icon and I cannot open files without it crashing.

[OmegAudio]

I try to open Rosegarden then open one of the .rg files and again Rosegarden crashes.
If I open terminal and run: sudo rosegarden
I can then open a project file and edit and save without crashing.

Running Rosegarden with sudo seems to be a work around. I have used Rosegarden for years. And always was able to run the application from the Show Applications and the Rosegarden Icon. And open and edit existing files. Until recently when I reinstalled Ubuntu 22.04

Maybe starting Rosegarden with strace gives some hints:

Code: Select all

strace -eopen rosegarden

Then open a rg file.

Thank you for this. I will have to go read about strace
I am by far not even close to being a novice with Ubuntu

[Impostor]

I do not see how making everything that is mine to be mine again, will make a difference.

Because if you ever used sudo to open an application, that application may write configuration files and whatnot to your home directory, and those files will then be owned by root, not you. So it may not be your old project files, but it could be certain configuration files. The easiest way to find out is to simply run the command I provided. Then ownership of everything in your home folder is correctly assigned to you again.

[bluebell]

I do not see how making everything that is mine to be mine again, will make a difference.

Because if you ever used sudo to open an application, that application may write configuration files and whatnot to your home directory, and those files will then be owned by root, not you. So it may not be your old project files, but it could be certain configuration files. The easiest way to find out is to simply run the command I provided. Then ownership of everything in your home folder is correctly assigned to you again.

Since Rosegarden crashes when loading one of his rg-files I suspect that there are files oder directories of rg-sessions that are owned by root and have to be chown'd as well.

[OmegAudio]

I do not see how making everything that is mine to be mine again, will make a difference.

Because if you ever used sudo to open an application, that application may write configuration files and whatnot to your home directory, and those files will then be owned by root, not you. So it may not be your old project files, but it could be certain configuration files. The easiest way to find out is to simply run the command I provided. Then ownership of everything in your home folder is correctly assigned to you again.

Thank you for this explanation.
I have been reading what and how to use chown and the command you provided.
I will provide the results once I have had opportunity to run this.

[OmegAudio]

Instead of running an application with sudo, which by consensus is a horrible idea, you could first find out if chowning everything in your home folder solves the problem.

Code: Select all

~$ sudo chown -R $USER:$USER ~

This assumes you're not logged in as root, which by consensus is also a horrible idea.

I have one user and group on the computer, Myself.

I ran the code: sudo chown -R $user:$user ~ (user is replacement for actual name)

I opened Rosegarden from the Show Applications > Rosegarden icon.
I tried to open a test file I had created that contains 4 midi tracks.
I received the error:
Rosegarden:
You do not have read permission for "/home/user/Music/Test Rosegarden/4Part_Test.rg

I tried to open another test file named RoseGardenTest.rg.

The file opened then Rosegarden Crashed.
Now the owner and group of that file, RoseGardenTest.rg, is root.

In terminal I tried changing the directory to _Music/Test_Rosegarden
Then run the ~/Music/Test_Rosegarden$ chown $user:$user 4Part_Test.rg And the owner and group did not change. They are still root.

I went back to the original script: ~$ sudo chown -R $USER:$USER ~ (I replaced user with my name)
The script takes only a second or two to run. And my RoseGarden test files do not change owner or group.

I had to do some research but was able to figure this out:
~/Music/Test_Rosegarden$ getfacl 4Part_Test.rg

file: 4Part_Test.rg

owner: root

group: root

user::rw-
group::---
other::---

This does not look like the chown made any changes to this file. Which tells me it did not make those changes any where else.

But opening Rosegarden through terminal using: sudo rosegarden , still does make everything work.

[bluebell]

Check your /home/$user directory. Maybe it belongs to root and has a setuid-bit in its permissions.

[Impostor]

I went back to the original script: ~$ sudo chown -R $USER:$USER ~ (I replaced user with my name)
The script takes only a second or two to run. And my RoseGarden test files do not change owner or group.

I ran the code: sudo chown -R $user:$user ~ (user is replacement for actual name)

If you mean you ran
sudo chown -R $jack:$jack ~
if your username is jack, that doesn't work. USER is a specific environment variable, $USER is its value. When you run the command with your username jack, you should replace $USER with jack.

sudo chown -R jack:jack ~

but you could just run it with $USER, provided you're not logged in as root, or use a root shell (in the latter case the terminal prompt has changed from ~$ to #, don't know about the former). You can check with
echo $USER
ran verbatim.