Changing default mounting options causes root owner

[bhikkhu subhuti]

Ubuntu 22.04
If I change the default mounting options in Gnome Disk Utility the owner is root. This threw me for a loop when all of my git repos were not working. I thought it was an ubuntu 22.04 problem or a ppa.

It is directly from Gnome Disk Utility by changing the auto mount options. I don't remember this happening before.

Reproduce

**Control:**
Under default mount options.
Go to your data partition, right click and look at properties/permissions.
You will be the owner.

**Cause the bug.**
Select a data partition you might have (ntfs) for dual boot machines to share data.
Change the switch from default mounting options (top switch) to manual settings. Change label to human readable. ("Data"). Reboot.

Go to your data partition, right click and look at properties/permissions.

It will say the owner is root and you are not the owner.

**Fix For The Problem:**
It took a long time, but I had to add uid=1000,gid=1000 to the settings. This hard to research "mystery setting" is not acceptable for a GUI mounting tool.

Reboot.
Go to your data partition, right click and look at properties/permissions
You will be the owner.

[bhikkhu subhuti (bksubhuti)]

I think that there should also be checkboxes and options to help one fill in the options line. Gui to select icon too. There is a reason for GUI.. and it is not really being used.

[Sebastien Bacher (seb128)]

Thank you for your bug report. That's probably worth reporting upstream on https://gitlab.gnome.org/GNOME/gnome-disk-utility/-/issues

Unsure it is changing the mount option, when selecting as an user it can map to the user who did the action but for a system mount that's not possible. The UI could provide easier way to set those options though

[bhikkhu subhuti (bksubhuti)]

The problem is, if you want a partition to be auto-mounted, you either must edit the fstab or THE INSTRUCTIONS are to turn off the "default" mounting in gnome disk utility and it will auto-mount. However, the auto-mounting is done as system root and I don't have access to it. So I must google and google and more google until I find that I put some settings like uuid=1000.

This is a big problem.
Why?
Well I setup my 22.04 with a full wipe, but kept my data partition.
My git was totally broken on my data partition and I thought it was ubuntu 22.04
But then with just git and ubuntu and vscode it worked.. so I installed the rest of the apps and it broke (I also setup my data partition to auto-mount)
then I thought it was my proton vpn which was the only ppa
It took a long time to realize it was the auto-mount .. merely changing defaults switch.

I had wiped my system 3 times before I figured this out.
Then I had to do a lot of googling to auto-mount for myself. It seems very logical that I would want to use a drive that I setup as automount.

If the user is selecting auto-mount, why not automatically allow that user to read access?
Instead it defaults to system.

[Sebastien Bacher (seb128)]

Right, the behaviour is confusing and it would be better if the UI guided the user into not hitting that issue, still it is an upstream problem and needs to be discussed on their gitlab

[bhikkhu subhuti (bksubhuti)]

I am beyond my troubles with this issue and only compassionately posting this issue to help others. With some careful thought, I will share this issue with gnome nautilus team. It seems logical that one should be able to right click on a drive located on the sidebar thinggy. or a drive located in "Other locations" Right click, automount (obviously it would be for the current user).

Perhaps a server would not like this mounted for everyone with sensitive drives.. but then again.. you would not automount such sensitive drives.

However, you might point to them and they might point to you.
I hope it gets resolved. Auto-mount is essential for recent-file-lists to work properly.

Ubuntu is quite stable and needs to focus on more usabliltiy issues.

[bhikkhu subhuti (bksubhuti)]

However, you might point to them and they might point to you.
I hope it gets resolved.

I'm referring to two teams pointing at each other for the other to fix it.