Leap 16.0: Krusader im Systemverwaltungsmodus läuft nicht mehr

[Der Nippeser]

Nach der Umstellung auf Leap 16.0 (Neuinstallation nach fehlgeschlagener Migration) sammeln sich nun einige Ungereimtheiten im System.
Eine davon: Wenn ich den Krusader im Systemverwaltungsmodus starte, kommt zwar die Abfrage des Root-Passworts, dann aber nichts mehr.
Der betroffene User hat Sys-Admin-Rechte.
Im messages-File finde ich im fraglichen Zeitraum folgende Meldungen:

2026-04-19T14:24:50.783464+02:00 localhost systemd[1544]: Started Krusader – Systemverwaltungsmodus (root) - Dateimanager.
2026-04-19T14:24:50.957435+02:00 localhost su: pam_kwallet5(su:auth): pam_kwallet5: pam_sm_authenticate
2026-04-19T14:24:50.957647+02:00 localhost su: pam_kwallet5(su:auth): pam_kwallet5: we were already executed
2026-04-19T14:24:57.155117+02:00 localhost su: pam_kwallet5(su:auth): pam_kwallet5: pam_sm_authenticate
2026-04-19T14:24:57.155280+02:00 localhost su: pam_kwallet5(su:auth): pam_kwallet5: we were already executed
2026-04-19T14:24:57.265217+02:00 localhost su[3988]: (to root) harry on pts/5
2026-04-19T14:24:57.265516+02:00 localhost su[3988]: pam_kwallet5(su:setcred): pam_kwallet5: pam_sm_setcred
2026-04-19T14:24:57.268685+02:00 localhost su[3988]: pam_unix(su:session): session opened for user root(uid=0) by harry(uid=1001)
2026-04-19T14:24:57.268898+02:00 localhost su[3988]: pam_kwallet5(su:session): pam_kwallet5: pam_sm_open_session
2026-04-19T14:24:57.269002+02:00 localhost su[3988]: pam_kwallet5(su:session): pam_kwallet5: we were already executed
2026-04-19T14:24:57.282536+02:00 localhost su[3988]: pam_unix(su:session): session closed for user root
2026-04-19T14:24:57.282701+02:00 localhost su[3988]: pam_kwallet5(su:session): pam_kwallet5: pam_sm_close_session
2026-04-19T14:24:57.282815+02:00 localhost su[3988]: pam_kwallet5(su:setcred): pam_kwallet5: pam_sm_setcred
2026-04-19T14:24:57.302724+02:00 localhost su: pam_kwallet5(su:auth): pam_kwallet5: pam_sm_authenticate
2026-04-19T14:24:57.302900+02:00 localhost su: pam_kwallet5(su:auth): pam_kwallet5: we were already executed
2026-04-19T14:24:57.411629+02:00 localhost su[3995]: (to root) harry on pts/5
2026-04-19T14:24:57.411944+02:00 localhost su[3995]: pam_kwallet5(su:setcred): pam_kwallet5: pam_sm_setcred
2026-04-19T14:24:57.415131+02:00 localhost su[3995]: pam_unix(su:session): session opened for user root(uid=0) by harry(uid=1001)
2026-04-19T14:24:57.415250+02:00 localhost su[3995]: pam_kwallet5(su:session): pam_kwallet5: pam_sm_open_session
2026-04-19T14:24:57.415341+02:00 localhost su[3995]: pam_kwallet5(su:session): pam_kwallet5: we were already executed
2026-04-19T14:24:57.584378+02:00 localhost su[4023]: (to root) root on pts/6
2026-04-19T14:24:57.586405+02:00 localhost su[4023]: pam_unix(su:session): session opened for user root(uid=0) by harry(uid=0)
2026-04-19T14:24:57.586616+02:00 localhost su[4023]: pam_kwallet5(su:session): pam_kwallet5: pam_sm_open_session
2026-04-19T14:24:57.586789+02:00 localhost su[4023]: pam_kwallet5(su:session): pam_kwallet5: we were already executed
2026-04-19T14:24:57.598756+02:00 localhost su[4027]: (to root) root on pts/7
2026-04-19T14:24:57.601012+02:00 localhost su[4027]: pam_unix(su:session): session opened for user root(uid=0) by harry(uid=0)
2026-04-19T14:24:57.601149+02:00 localhost su[4027]: pam_kwallet5(su:session): pam_kwallet5: pam_sm_open_session
2026-04-19T14:24:57.601229+02:00 localhost su[4027]: pam_kwallet5(su:session): pam_kwallet5: we were already executed
2026-04-19T14:24:57.679065+02:00 localhost systemd-coredump[4033]: Process 4030 (krusader) of user 0 terminated abnormally with signal 6/ABRT, processing...
2026-04-19T14:24:57.688118+02:00 localhost systemd[1]: Started Process Core Dump (PID 4033/UID 0).
2026-04-19T14:24:57.690991+02:00 localhost systemd[1]: Started Pass systemd-coredump journal entries to relevant user for potential DrKonqi handling.
2026-04-19T14:24:57.753179+02:00 localhost systemd-coredump[4034]: Resource limits disable core dumping for process 4030 (krusader).
2026-04-19T14:24:57.753711+02:00 localhost systemd-coredump[4034]: Process 4030 (krusader) of user 0 terminated abnormally without generating a coredump.
2026-04-19T14:24:57.754462+02:00 localhost systemd[1]: systemd-coredump@1-4033-0.service: Deactivated successfully.
2026-04-19T14:24:57.757775+02:00 localhost su[4027]: pam_unix(su:session): session closed for user root
2026-04-19T14:24:57.757897+02:00 localhost su[4027]: pam_kwallet5(su:session): pam_kwallet5: pam_sm_close_session
2026-04-19T14:24:57.758936+02:00 localhost su[4023]: pam_unix(su:session): session closed for user root
2026-04-19T14:24:57.759078+02:00 localhost su[4023]: pam_kwallet5(su:session): pam_kwallet5: pam_sm_close_session
2026-04-19T14:24:57.761912+02:00 localhost drkonqi-coredump-processor[4035]: Entry doesn't look like a dump. This may have been a vaccum run. Nothing to process.
2026-04-19T14:24:57.762143+02:00 localhost drkonqi-coredump-processor[4035]: "/usr/bin/krusader" 4030 ""
2026-04-19T14:24:57.762223+02:00 localhost drkonqi-coredump-processor[4035]: The socket path doesn't exist @ "/run/user/0/drkonqi-coredump-launcher"
2026-04-19T14:24:57.768156+02:00 localhost systemd[1]: drkonqi-coredump-processor@1-4033-0.service: Deactivated successfully.
2026-04-19T14:24:57.777058+02:00 localhost su[3995]: pam_unix(su:session): session closed for user root
2026-04-19T14:24:57.778609+02:00 localhost su[3995]: pam_kwallet5(su:session): pam_kwallet5: pam_sm_close_session
2026-04-19T14:24:57.778706+02:00 localhost su[3995]: pam_kwallet5(su:setcred): pam_kwallet5: pam_sm_setcred
2026-04-19T14:24:57.795656+02:00 localhost systemd[1544]: app-org.kde.krusader.root\x2dmode@65c0b79986a54f1d8c8422ba8ab59551.service: Main process exited, code=exited, status=4/NOPERMISSION
2026-04-19T14:24:57.795904+02:00 localhost systemd[1544]: app-org.kde.krusader.root\x2dmode@65c0b79986a54f1d8c8422ba8ab59551.service: Failed with result 'exit-code'.

Die Meldungen zu DrKonqi gehören da wohl nicht zu, ich habe sie der Vollständigkeit wegen drin gelassen. Dazu werde ich in in Kürze einen weiteren Thread eröffnen.

Komischerweise hat das eine Weile funktioniert. Dabei fällt mir ein, das ich zuvor den KDE-Passwortspeicher gelöscht hatte. Aber hat der etwas damit zu tun? Müsste er sich dann nicht beim nächsten Booten neu erstellen?

Viele Grüße aus Köln

 

[Sauerland]

Hast du es mit dem Passwort für den User und auch mit dem Passwort für root versucht?

 

[Der Nippeser]

Wenn ich das vom Benutzer eingebe, sagt er mir dass das Passwort falsch ist und fragt noch einmal nach. Wenn ich (dann) das root-PW eingebe, verschwindet der Dialog - und nichts passiert mehr.

 

[Sauerland]

Funktioniert es, wenn du dich in einer Konsole als root anmeldest und dann:

krusader

 

[Der Nippeser]

Hätte ich auch selbst drauf kommen können...
Das Ding schmeißt allerdings dann ein paar Meldungen auf die Konsole:

kf.i18n: KLocalizedString: Domain is not set for this string, translation will not work. Please see https://api.kde.org/frameworks/ki18n/html/prg_guide.html msgid: "No jobs" msgid_plural: "" msgctxt: ""
14:55:51.392-debug default unknown@0 # System icon theme: "hicolor"
14:55:51.584-warning default unknown@0 # QWidget::insertAction: Attempt to insert null action
14:55:51.586-critical default unknown@0 # Couldn't start kglobalaccel from org.kde.kglobalaccel.service: QDBusError("org.freedesktop.DBus.Error.ServiceUnknown", "The name is not activatable")
14:55:51.592-warning kf.i18n unknown@0 # Trying to convert empty KLocalizedString to QString.
14:55:51.624-warning default unknown@0 # QObject::disconnect: wildcard call disconnects from destroyed signal of QAction::bookmarks
14:55:51.624-warning default unknown@0 # QObject::disconnect: wildcard call disconnects from destroyed signal of QAction::rightclick menu
14:55:51.624-warning default unknown@0 # QObject::disconnect: wildcard call disconnects from destroyed signal of QAction::compare dirs
14:55:51.624-warning default unknown@0 # QObject::disconnect: wildcard call disconnects from destroyed signal of QAction::media
14:55:51.624-warning default unknown@0 # QObject::disconnect: wildcard call disconnects from destroyed signal of QAction::search bar filter
14:55:51.624-warning default unknown@0 # QObject::disconnect: wildcard call disconnects from destroyed signal of QAction::set_jump_back
14:55:51.624-warning default unknown@0 # QObject::disconnect: wildcard call disconnects from destroyed signal of QAction::location_bar
14:55:51.624-warning default unknown@0 # QObject::disconnect: wildcard call disconnects from destroyed signal of QAction::cancel refresh
14:55:51.624-warning default unknown@0 # QObject::disconnect: wildcard call disconnects from destroyed signal of QAction::history
14:55:51.624-warning default unknown@0 # QObject::disconnect: wildcard call disconnects from destroyed signal of QAction::sync browse
14:55:51.624-warning default unknown@0 # QObject::disconnect: wildcard call disconnects from destroyed signal of KToggleAction::toggle sidebar
14:55:51.624-warning default unknown@0 # QObject::disconnect: wildcard call disconnects from destroyed signal of QAction::search bar selection
14:55:51.624-warning default unknown@0 # QObject::disconnect: wildcard call disconnects from destroyed signal of QAction::jump_back
14:55:51.624-warning default unknown@0 # QObject::disconnect: wildcard call disconnects from destroyed signal of QAction::search bar
14:55:51.624-warning default unknown@0 # QObject::disconnect: wildcard call disconnects from destroyed signal of QAction::sync panels
14:55:51.624-warning default unknown@0 # QObject::disconnect: wildcard call disconnects from destroyed signal of QAction::F9_Terminal
14:55:51.624-warning default unknown@0 # QObject::disconnect: wildcard call disconnects from destroyed signal of QAction::F3_View
14:55:51.624-warning default unknown@0 # QObject::disconnect: wildcard call disconnects from destroyed signal of QAction::F6_Move
14:55:51.624-warning default unknown@0 # QObject::disconnect: wildcard call disconnects from destroyed signal of QAction::unpack
14:55:51.624-warning default unknown@0 # QObject::disconnect: wildcard call disconnects from destroyed signal of QAction::calculate
14:55:51.624-warning default unknown@0 # QObject::disconnect: wildcard call disconnects from destroyed signal of QAction::F7_Mkdir
14:55:51.624-warning default unknown@0 # QObject::disconnect: wildcard call disconnects from destroyed signal of QAction::go_back
14:55:51.624-warning default unknown@0 # QObject::disconnect: wildcard call disconnects from destroyed signal of QAction::edit_paste
14:55:51.624-warning default unknown@0 # QObject::disconnect: wildcard call disconnects from destroyed signal of QAction::go_up
14:55:51.624-warning default unknown@0 # QObject::disconnect: wildcard call disconnects from destroyed signal of QAction::F2_Rename
14:55:51.624-warning default unknown@0 # QObject::disconnect: wildcard call disconnects from destroyed signal of QAction::edit_copy
14:55:51.624-warning default unknown@0 # QObject::disconnect: wildcard call disconnects from destroyed signal of QAction::new symlink
14:55:51.624-warning default unknown@0 # QObject::disconnect: wildcard call disconnects from destroyed signal of QAction::F5_Copy_Queue
14:55:51.624-warning default unknown@0 # QObject::disconnect: wildcard call disconnects from destroyed signal of QAction::test archives
14:55:51.624-warning default unknown@0 # QObject::disconnect: wildcard call disconnects from destroyed signal of QAction::match checksum
14:55:51.624-warning default unknown@0 # QObject::disconnect: wildcard call disconnects from destroyed signal of QAction::pack
14:55:51.624-warning default unknown@0 # QObject::disconnect: wildcard call disconnects from destroyed signal of QAction::std_redisplay
14:55:51.624-warning default unknown@0 # QObject::disconnect: wildcard call disconnects from destroyed signal of QAction::ftp disconnect
14:55:51.624-warning default unknown@0 # QObject::disconnect: wildcard call disconnects from destroyed signal of QAction::F3_ViewDlg
14:55:51.624-warning default unknown@0 # QObject::disconnect: wildcard call disconnects from destroyed signal of QAction::F8_Delete
14:55:51.624-warning default unknown@0 # QObject::disconnect: wildcard call disconnects from destroyed signal of QAction::cd to other panel
14:55:51.624-warning default unknown@0 # QObject::disconnect: wildcard call disconnects from destroyed signal of QAction::go_home
14:55:51.624-warning default unknown@0 # QObject::disconnect: wildcard call disconnects from destroyed signal of QAction::edit_cut
14:55:51.624-warning default unknown@0 # QObject::disconnect: wildcard call disconnects from destroyed signal of QAction::ftp new connection
14:55:51.624-warning default unknown@0 # QObject::disconnect: wildcard call disconnects from destroyed signal of QAction::edit_new_file
14:55:51.624-warning default unknown@0 # QObject::disconnect: wildcard call disconnects from destroyed signal of QAction::F6_Move_Queue
14:55:51.624-warning default unknown@0 # QObject::disconnect: wildcard call disconnects from destroyed signal of QAction::properties
14:55:51.624-warning default unknown@0 # QObject::disconnect: wildcard call disconnects from destroyed signal of QAction::create checksum
14:55:51.624-warning default unknown@0 # QObject::disconnect: wildcard call disconnects from destroyed signal of QAction::root
14:55:51.624-warning default unknown@0 # QObject::disconnect: wildcard call disconnects from destroyed signal of QAction::go_forward
14:55:51.624-warning default unknown@0 # QObject::disconnect: wildcard call disconnects from destroyed signal of QAction::F5_Copy
14:55:51.624-warning default unknown@0 # QObject::disconnect: wildcard call disconnects from destroyed signal of QAction::F4_Edit
14:55:51.624-warning default unknown@0 # QObject::disconnect: wildcard call disconnects from destroyed signal of QAction::alternative delete

Aber jetzt funktioniert es auch über die Oberfläche wieder!?!

Manchmal verstehe ich ihn nicht...

Viele Grüße aus Köln