Starting my PC: When Plasma is up I am to enter root password for mounting a partition
Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Distribution: openSuSE Tumbleweed-KDE, Mint 21, MX-21, Manjaro
Posts: 4,629
Rep:
Starting my PC: When Plasma is up I am to enter root password for mounting a partition
This is on openSUSE tumbleweed but with about 6 other distros all over the machine. The actually runnung tumbleweed is on /dev/sdc2 and /home on /dev/sdc6. A popup pops up and says that the partition to be mounted is /dev/sdb8 which is a recently created logical partition for testing GhostBSD (which didn't work due to its installer). /dev/sdb8 has absolutely no relevance here. When I break off mounting /dev/sdb8 nothing happens or is broken.
How can I find out what is causing this? It says on the popup "polkit.subject-pid: 2366" and polkit.caller-pid: 1983". "px ax" yields
Distribution: openSuSE Tumbleweed-KDE, Mint 21, MX-21, Manjaro
Posts: 4,629
Original Poster
Rep:
Ah, you were right. I will post an excerpt below:
Code:
Mai 20 15:27:16 PC polkit-kde-authentication-agent-1[2325]: New PolkitAgentListener 0x557e61571200
Mai 20 15:27:16 PC polkit-kde-authentication-agent-1[2325]: Adding new listener PolkitQt1::Agent::Listener(0x557e61584bc0) for 0x557e61571200
Mai 20 15:27:16 PC polkit-kde-authentication-agent-1[2325]: Listener online
Mai 20 15:27:16 PC polkit-kde-authentication-agent-1[2325]: Authentication agent result: true
Mai 20 15:27:18 PC polkit-kde-authentication-agent-1[2325]: Listener adapter polkit_qt_listener_initiate_authentication
Mai 20 15:27:18 PC polkit-kde-authentication-agent-1[2325]: GSimpleAsyncResult: 0x557e6159c9e0
Mai 20 15:27:18 PC polkit-kde-authentication-agent-1[2325]: polkit_qt_listener_initiate_authentication callback for 0x557e61571200
Mai 20 15:27:18 PC polkit-kde-authentication-agent-1[2325]: Initiating authentication
Mai 20 15:27:18 PC polkit-kde-authentication-agent-1[2325]: Message of action: "Legitimierung ist zum Einhängen von SanDisk SDSSDH3500G (/dev/sdb8) notwendig"
Mai 20 15:27:18 PC polkit-kde-authentication-agent-1[2325]: Action description has been found
Mai 20 15:27:18 PC polkit-kde-authentication-agent-1[2325]: WinId of the dialog is 35651590 35651590
Mai 20 15:27:18 PC polkit-kde-authentication-agent-1[2325]: WinId of the shown dialog is 35651590 35651590
Mai 20 15:27:18 PC polkit-kde-authentication-agent-1[2325]: Trying again
Mai 20 15:27:18 PC polkit-kde-authentication-agent-1[2325]: Listener adapter polkit_qt_listener_initiate_authentication
Mai 20 15:27:18 PC polkit-kde-authentication-agent-1[2325]: GSimpleAsyncResult: 0x557e618e5650
Mai 20 15:27:18 PC polkit-kde-authentication-agent-1[2325]: polkit_qt_listener_initiate_authentication callback for 0x557e61571200
Mai 20 15:27:18 PC polkit-kde-authentication-agent-1[2325]: Initiating authentication
...
Mai 20 15:27:18 PC polkit-kde-authentication-agent-1[2325]: polkit_qt_listener_initiate_authentication_finish callback for 0x557e61571200
Mai 20 15:27:18 PC polkit-kde-authentication-agent-1[2325]: Another client is already authenticating, please try again later.
Mai 20 15:27:18 PC polkit-agent-helper-1[2658]: pam_kwallet5(polkit-1:auth): (null): pam_sm_authenticate
Mai 20 15:27:18 PC polkit-agent-helper-1[2658]: pam_kwallet5(polkit-1:auth): pam_kwallet5: Couldn't get password (it is empty)
Mai 20 15:27:18 PC polkit-kde-authentication-agent-1[2325]: REQUEST
Mai 20 15:27:18 PC polkit-kde-authentication-agent-1[2325]: Request: "Password: "
Mai 20 15:27:18 PC polkit-kde-authentication-agent-1[2325]: "Password: "
Mai 20 15:27:18 PC polkit-kde-authentication-agent-1[2325]: Listener adapter polkit_qt_listener_initiate_authentication
Mai 20 15:27:18 PC polkit-kde-authentication-agent-1[2325]: GSimpleAsyncResult: 0x7fc248009d60
Mai 20 15:27:18 PC polkit-kde-authentication-agent-1[2325]: polkit_qt_listener_initiate_authentication callback for 0x557e61571200
Mai 20 15:27:18 PC polkit-kde-authentication-agent-1[2325]: Initiating authentication
...
I don't understand what is happening. Can you make something of that? What should I do to stop that?
Distribution: openSuSE Tumbleweed-KDE, Mint 21, MX-21, Manjaro
Posts: 4,629
Original Poster
Rep:
I found a workaround but no solution. I right-clicked on removable media(?, that symbol with which on can eject and mount external devices / device monitoring, sorry I have to translate that from German). Got two lines:
First one like "attend to portable media" or so. In the popup I checked and /dev/sda8 was not activated. So I unchecked "Automatically mount all removable media at login". That leaves "Automatically mount all removable media when attached" active.
Second line like "manage device monitoring program" I activated "all devices"; "Show popup when new device is attache" stayed active.
Well, now the stupid popup doesn't show anymore. But it seems that the system rates /dev/sda8 as removable device: where the {censored} is the information stored that makes it think that? Any config - rc - whatever-file known which might be the culprit?
Well, at least, judging from the udisks(8) manpage, there's a way to override udisks' notion of automountable devices by setting the UDISKS_AUTO property in udev.
Distribution: openSuSE Tumbleweed-KDE, Mint 21, MX-21, Manjaro
Posts: 4,629
Original Poster
Rep:
Arrrgh, I hate that. From the man page you suggested:
Quote:
DRIVE CONFIGURATION
At start-up and when a drive is connected, udisksd(8) will apply configuration stored in the file /etc/udisks2/IDENTIFIER.conf ...
...only that there is no IDENTIFIER.conf in my system. SUSE seems to do it somehow differently. I really hate these things. But thanks anyhow for your help.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.