-
Notifications
You must be signed in to change notification settings - Fork 148
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Regarding polkit authorization prompts #1362
Comments
@tbzatek could you please check this, if it's acceptable, I can make a PR. |
Could you provide I believe this should be consistent with what This is the code in question in gvfs: https://gitlab.gnome.org/GNOME/gvfs/-/blob/master/monitor/udisks2/gvfsudisks2volume.c?ref_type=heads#L292-L327 So yes, I agree with your proposal, it should just distinguish different volume types. Btw. are you running a desktop session as root?! ( |
gio_mount_l.txt I understand what you say, and I'll modify the code and push later, and maybe I should remove all the *.po changes. I'm not running desktop session as root, but just mounted the partitions by root user so that the polkit dialog could be raised to show the changes when I unmount them by another user. |
Record_select-area_20250310111522.mp4
Regarding polkit authorization prompts, when udisks determines that an operation on a partition requires user authorization, the device name is displayed using the drive name + device descriptor format. However, this approach is somewhat counterintuitive. Users are interacting with a partition rather than the entire disk, and average users may not understand the origin of the displayed disk name.
To improve clarity, we propose the following adjustment:
• If a partition has an
idLabel
(e.g., a user-defined label), display the device name asidLabel (device descriptor)
.• If the
idLabel
is empty, retain the original display format (drive name + device descriptor).This change would align the prompt with user expectations and reduce confusion. For a practical demonstration, please refer to the example video.
Key Points:
idLabel
) when available, as they are more recognizable to users.The text was updated successfully, but these errors were encountered: