Page 1 of 4 123 ... LastLast
Results 1 to 10 of 38

Thread: 90 Sekunden stop job beim Shutdown. Warum? Was?

  1. #1

    Default 90 Sekunden stop job beim Shutdown. Warum? Was?

    Dies ist eine junge Installation von openSUSE tumbleweed. Nach wenigen Tagen seit der Installation läuft der Shutdown auf einen Bremsklotz in Form einer 90-sekündigen Unterbrechung, bevor dann Schluss ist.

    Ich habe auf der selben Maschine eine gleichalte zweite Tumbleweed Installation, die das nicht macht. Ich habe den Bootvorgang auf verbose gestellt. Jetzt sehe ich beim Shutdown "A stop job is running for session of user {me}" mit einem Timer, der auf 90 Sekunden hoch läuft. Das passiert nicht, wenn ich vorm Login gleich wieder herunterfahre.

    Ich habe die logs in /var/log angesehen, aber die sind nur maschinenlesbar. Wie finde ich heraus, was da los ist?

  2. #2
    Join Date
    Mar 2011
    Location
    Sauerland
    Posts
    7,231

    Default AW: 90 Sekunden stop job beim Shutdown. Warum? Was?

    Das journal persistent machen und danach dort schauen.......

    https://doc.opensuse.org/documentati...ournalctl.html

    Da läuft ein systemd Service aus dem Ruder und es wird 90 Sekunden gewartet das der Dienst sich beendet, bevor dieser abgeschossen wird.
    Hab ich auch ab und an.......

  3. #3
    Join Date
    Jan 2014
    Location
    Erlangen
    Posts
    4,005

    Default Re: 90 Sekunden stop job beim Shutdown. Warum? Was?

    Quote Originally Posted by wodenhof View Post
    Ich habe die logs in /var/log angesehen, aber die sind nur maschinenlesbar. Wie finde ich heraus, was da los ist?
    Journal liefert Leserliches.
    Code:
    erlangen:~ # journalctl -b -1 -o short-monotonic -g Stopped --no-pager  
    -- Journal begins at Wed 2021-12-15 08:27:08 CET, ends at Sun 2022-01-16 20:11:01 CET. -- 
    [    2.786812] erlangen systemd[1]: Stopped target Initrd Default Target. 
    [    2.786839] erlangen systemd[1]: Stopped target Basic System. 
    [    2.786911] erlangen systemd[1]: Stopped target Initrd Root Device. 
    [    2.786938] erlangen systemd[1]: Stopped target Initrd /usr File System. 
    [    2.786999] erlangen systemd[1]: Stopped target Path Units. 
    [    2.801370] erlangen systemd[1]: Stopped Dispatch Password Requests to Console Directory Watch. 
    [    2.801439] erlangen systemd[1]: Stopped target Remote File Systems. 
    [    2.801464] erlangen systemd[1]: Stopped target Preparation for Remote File Systems. 
    [    2.801531] erlangen systemd[1]: Stopped target Slice Units. 
    [    2.801556] erlangen systemd[1]: Stopped target Socket Units. 
    [    2.801617] erlangen systemd[1]: Stopped target System Initialization. 
    [    2.801642] erlangen systemd[1]: Stopped target Swaps. 
    [    2.801705] erlangen systemd[1]: Stopped target Timer Units. 
    [    2.801803] erlangen systemd[1]: Stopped dracut initqueue hook. 
    [    2.803300] erlangen systemd[1]: Stopped Apply Kernel Variables. 
    [    2.803430] erlangen systemd[1]: Stopped Load Kernel Modules. 
    [    2.803553] erlangen systemd[1]: Stopped Create Volatile Files and Directories. 
    [    2.803634] erlangen systemd[1]: Stopped target Local File Systems. 
    [    2.803724] erlangen systemd[1]: Stopped Coldplug All udev Devices. 
    [    2.822277] erlangen systemd[1]: Stopped Rule-based Manager for Device Events and Files. 
    [    2.822752] erlangen systemd[1]: Stopped dracut pre-udev hook. 
    [    2.822806] erlangen systemd[1]: Stopped dracut cmdline hook. 
    [    2.822853] erlangen systemd[1]: Stopped dracut ask for additional cmdline parameters. 
    [    2.823427] erlangen systemd[1]: Stopped Create Static Device Nodes in /dev. 
    [    2.823456] erlangen systemd[1]: Stopped Create List of Static Device Nodes. 
    [    3.205450] erlangen systemd[1]: Stopped Switch Root. 
    [    3.206361] erlangen systemd[1]: Stopped target Switch Root. 
    [    3.206371] erlangen systemd[1]: Stopped target Initrd File Systems. 
    [    3.206376] erlangen systemd[1]: Stopped target Initrd Root File System. 
    [    3.212198] erlangen systemd[1]: Stopped Plymouth switch root service. 
    [    3.212622] erlangen systemd[1]: Stopped File System Check on Root Device. 
    [    3.212694] erlangen systemd[1]: Stopped Journal Service. 
    [    3.212739] erlangen systemd[1]: Stopped Entropy Daemon based on the HAVEGE algorithm. 
    [   22.718412] erlangen systemd[1091]: Stopped target Main User Target. 
    [   22.719995] erlangen systemd[1091]: Stopped D-Bus User Message Bus. 
    [   22.720127] erlangen systemd[1091]: Stopped target Basic System. 
    [   22.720291] erlangen systemd[1091]: Stopped target Paths. 
    [   22.720444] erlangen systemd[1091]: Stopped target Sockets. 
    [   22.720535] erlangen systemd[1091]: Stopped target Timers. 
    [   22.720628] erlangen systemd[1091]: Stopped Daily Cleanup of User's Temporary Directories. 
    [   22.720873] erlangen systemd[1091]: Stopped Create User's Volatile Files and Directories. 
    [   22.738849] erlangen systemd[1]: Stopped User Manager for UID 477. 
    [   22.747678] erlangen systemd[1]: Stopped User Runtime Directory /run/user/477. 
    [  390.634669] erlangen systemd[1]: Stopped target Graphical Interface. 
    [  390.634729] erlangen systemd[1]: Stopped target Multi-User System. 
    [  390.635410] erlangen systemd[1]: Stopped target Login Prompts. 
    [  390.635536] erlangen systemd[1]: Stopped target Sound Card. 
    [  390.635679] erlangen systemd[1]: Stopped target Timer Units. 
    [  390.635827] erlangen systemd[1]: Stopped Backup of /home. 
    [  390.635939] erlangen systemd[1]: Stopped Backup of RPM database. 
    [  390.636035] erlangen systemd[1]: Stopped Backup of /etc/sysconfig. 
    [  390.636124] erlangen systemd[1]: Stopped Balance block groups on a btrfs filesystem. 
    [  390.636207] erlangen systemd[1]: Stopped Scrub btrfs filesystem, verify block checksums. 
    [  390.636301] erlangen systemd[1]: Stopped Check if mainboard battery is Ok. 
    [  390.636384] erlangen systemd[1]: Stopped Discard unused blocks once a week. 
    [  390.636473] erlangen systemd[1]: Stopped Daily rotation of log files. 
    [  390.636557] erlangen systemd[1]: Stopped Daily man-db regeneration. 
    [  390.636642] erlangen systemd[1]: Stopped Daily locate database update. 
    [  390.636730] erlangen systemd[1]: Stopped Systemd timer to update the system daily with PackageKit. 
    [  390.636833] erlangen systemd[1]: Stopped Daily Cleanup of Snapper Snapshots. 
    [  390.637417] erlangen systemd[1]: Stopped Timeline of Snapper Snapshots. 
    [  390.637522] erlangen systemd[1]: Stopped Daily Cleanup of Temporary Directories. 
    [  390.639540] erlangen systemd[1]: Stopped auditd rules generation. 
    [  390.641302] erlangen systemd[1]: Stopped Apply settings from /etc/sysconfig/keyboard. 
    [  390.653693] erlangen systemd[1]: Stopped hd-idle disk spindown service. 
    [  390.654456] erlangen systemd[1]: Stopped irqbalance daemon. 
    [  390.654741] erlangen systemd[1]: Stopped Machine Check Exception Logging Daemon. 
    [  390.654821] erlangen systemd[1]: Stopped CUPS Scheduler. 
    [  390.655402] erlangen systemd[1]: Stopped Daemon for power management. 
    [  390.655540] erlangen systemd[1]: Stopped A remote-mail retrieval utility. 
    [  390.655880] erlangen systemd[1]: Stopped Save/Restore Sound Card State. 
    [  390.672876] erlangen systemd[1]: Stopped Restore /run/initramfs on shutdown. 
    [  390.676277] erlangen systemd[1]: Stopped Getty on tty1. 
    [  390.676453] erlangen systemd[1]: Stopped Command Scheduler. 
    [  390.676546] erlangen systemd[1]: Stopped Load/Save Random Seed. 
    [  390.691471] erlangen systemd[1]: Stopped Start fetchmail. 
    [  390.691574] erlangen systemd[1]: Stopped Hold until boot process finishes up. 
    [  390.700118] erlangen systemd[1]: Stopped Authorization Manager. 
    [  390.700503] erlangen systemd[1]: Stopped Disk Manager. 
    [  390.703198] erlangen systemd[1]: Stopped Session 2 of User karl. 
    [  390.705019] erlangen systemd[1175]: Stopped Konsole - Terminal. 
    [  390.708155] erlangen systemd[1175]: Stopped target Main User Target. 
    [  390.710529] erlangen systemd[1175]: Stopped Save jAlbum Project Files. 
    [  390.711086] erlangen systemd[1175]: Stopped Accessibility services bus. 
    [  390.711548] erlangen systemd[1175]: Stopped User preferences database. 
    [  390.711910] erlangen systemd[1175]: Stopped Firefox - Web Browser. 
    [  390.715562] erlangen systemd[1175]: Stopped Virtual filesystem service. 
    [  390.729783] erlangen systemd[1175]: Stopped D-Bus User Message Bus. 
    [  390.729896] erlangen systemd[1175]: Stopped target Basic System. 
    [  390.729954] erlangen systemd[1175]: Stopped target Paths. 
    [  390.729998] erlangen systemd[1175]: Stopped target Sockets. 
    [  390.730036] erlangen systemd[1175]: Stopped target Timers. 
    [  390.730064] erlangen systemd[1175]: Stopped Daily Cleanup of User's Temporary Directories. 
    [  390.730378] erlangen systemd[1175]: Stopped Create User's Volatile Files and Directories. 
    [  390.733588] erlangen systemd[1]: Stopped RealtimeKit Scheduling Policy Service. 
    [  390.737622] erlangen systemd[1]: Stopped Postfix Mail Transport Agent. 
    [  390.769894] erlangen systemd[1]: Stopped Initialize hardware monitoring sensors. 
    [  390.786270] erlangen systemd[1175]: Stopped KMail - E-Mail-Programm. 
    [  390.891015] erlangen systemd[1]: Stopped MiniDLNA is a DLNA/UPnP-AV server software. 
    [  390.891926] erlangen systemd[1]: Stopped target Network is Online. 
    [  391.046810] erlangen systemd[1175]: Stopped /usr/bin/korgac. 
    [  391.051552] erlangen systemd[1]: Stopped User Manager for UID 1000. 
    [  391.065022] erlangen systemd[1]: Stopped User Runtime Directory /run/user/1000. 
    [  391.102242] erlangen systemd[1]: Stopped D-Bus System Message Bus. 
    [  391.851967] erlangen systemd[1]: Stopped X Display Manager. 
    [  391.856729] erlangen systemd[1]: Stopped Permit User Sessions. 
    [  391.909065] erlangen systemd[1]: Stopped The Apache Webserver. 
    [  391.909228] erlangen systemd[1]: Stopped target Remote File Systems. 
    [  391.909314] erlangen systemd[1]: Stopped target System Time Synchronized. 
    [  391.909382] erlangen systemd[1]: Stopped target System Time Set. 
    [  391.910245] erlangen systemd[1]: Stopped NTP client/server. 
    [  391.910367] erlangen systemd[1]: Stopped target Network. 
    [  391.910424] erlangen systemd[1]: Stopped target Host and Network Name Lookups. 
    [  391.913916] erlangen systemd[1]: Stopped User Login Management. 
    [  391.914071] erlangen systemd[1]: Stopped target Basic System. 
    [  391.914139] erlangen systemd[1]: Stopped target Path Units. 
    [  391.925314] erlangen systemd[1]: Stopped Watch /etc/sysconfig/btrfsmaintenance. 
    [  391.977378] erlangen systemd[1]: Stopped Watch for changes in CA certificates. 
    [  391.977841] erlangen systemd[1]: Stopped CUPS Scheduler. 
    [  392.009346] erlangen systemd[1]: Stopped Watch for changes in issue snippets. 
    [  392.025356] erlangen systemd[1]: Stopped Watch for changes in smartmontools sysconfig file. 
    [  392.025628] erlangen systemd[1]: Stopped target Slice Units. 
    [  392.026374] erlangen systemd[1]: Stopped target Socket Units. 
    [  392.027434] erlangen systemd[1]: Stopped target System Initialization. 
    [  392.027871] erlangen systemd[1]: Stopped target Local Encrypted Volumes. 
    [  392.041333] erlangen systemd[1]: Stopped Dispatch Password Requests to Console Directory Watch. 
    [  392.041580] erlangen systemd[1]: Stopped target Local Verity Protected Volumes. 
    [  392.049871] erlangen systemd[1]: Stopped Network Name Resolution. 
    [  392.059479] erlangen systemd[1]: Stopped Record System Boot/Shutdown in UTMP. 
    [  392.082282] erlangen systemd[1]: Stopped Network Configuration. 
    [  392.082946] erlangen systemd[1]: Stopped Apply Kernel Variables. 
    [  392.083035] erlangen systemd[1]: Stopped Apply Kernel Variables for 5.16.0-1-default. 
    [  392.083131] erlangen systemd[1]: Stopped Load Kernel Modules. 
    [  392.133227] erlangen systemd[1]: Stopped Security Auditing Service. 
    [  392.133555] erlangen systemd[1]: Stopped Create Volatile Files and Directories. 
    [  392.133614] erlangen systemd[1]: Stopped target Local File Systems. 
    [  392.143389] erlangen systemd[1]: Stopped target Swaps. 
    erlangen:~ #
    i7-6700K (2016), i5-8250U (2018), AMD Ryzen 5 3400G (2020), 5600X (2022) openSUSE Tumbleweed, KDE Plasma

  4. #4
    Join Date
    Jan 2021
    Location
    Vachdorf
    Posts
    44

    Default AW: 90 Sekunden stop job beim Shutdown. Warum? Was?

    Bei mir "erscheint" "das" auch ab und zu bei Leap.
    Ich denke, da ist noch "wer" der denkt, er müsse noch etwas tun vor dem Runterfahren.
    Wenn alle Programme geschlossen sind, passiert das vermutlich nicht.
    Da ich "mehrerere" Mailadressen habe, kann es doch sein, das der "Wicht" in meinen System sagt:
    "Ich muß erst Deine gefühlten 17000 Mailverbindungen trennen und sei zufrieden, daß das nur 90 sec dauert."

  5. #5
    Join Date
    Jun 2008
    Location
    Netherlands
    Posts
    30,948

    Default Re: 90 Sekunden stop job beim Shutdown. Warum? Was?

    Ist tatsächlich interessant zu wissen ob das auch passiert wenn kein User mehr angemeldet ist.
    Henk van Velden

  6. #6

    Default Re: AW: 90 Sekunden stop job beim Shutdown. Warum? Was?

    Quote Originally Posted by Sauerland View Post
    Das journal persistent machen und danach dort schauen.......

    https://doc.opensuse.org/documentati...ournalctl.html

    Da läuft ein systemd Service aus dem Ruder und es wird 90 Sekunden gewartet das der Dienst sich beendet, bevor dieser abgeschossen wird.
    Hab ich auch ab und an.......
    Okay, hab's gemacht, hier ist der Ausschnitt aus journalctl -r:
    Code:
    Jan 17 21:52:51 ryzen systemd[1]: Stopping User Login Management... 
    Jan 17 21:52:51 ryzen systemd[1]: session-2.scope: Consumed 13.423s CPU time.
    Jan 17 21:52:51 ryzen systemd[1]: Stopped Session 2 of User matthias. 
    Jan 17 21:52:51 ryzen systemd[1]: session-2.scope: Failed with result 'timeout'.
    Jan 17 21:52:51 ryzen systemd[1]: session-2.scope: Killing process 2465 (n/a) with signal SIGKILL.
    Jan 17 21:52:51 ryzen systemd[1]: session-2.scope: Killing process 2461 (pipe-connection) with signal SIGKILL.
    Jan 17 21:52:51 ryzen systemd[1]: session-2.scope: Killing process 2460 (scdaemon) with signal SIGKILL.
    Jan 17 21:52:51 ryzen systemd[1]: session-2.scope: Stopping timed out. Killing.
    Jan 17 21:51:22 ryzen systemd[1808]: app-org.kde.dolphin-fd80401f3c77409ebb54cc484fa651da.scope: Consumed 4.613s CPU time.
    Jan 17 21:51:21 ryzen systemd[1]: Condition check resulted in Tell Plymouth To Jump To initramfs being skipped. 
    Jan 17 21:51:21 ryzen systemd[1]: Started Show Plymouth Reboot Screen. 
    Jan 17 21:51:21 ryzen systemd[1]: Received SIGRTMIN+20 from PID 5724 (plymouthd). 
    Jan 17 21:51:21 ryzen systemd[1]: Stopped target Host and Network Name Lookups. 
    Jan 17 21:51:21 ryzen systemd[1]: Stopped NTP client/server. 
    Jan 17 21:51:21 ryzen systemd[1]: chronyd.service: Deactivated successfully. 
    Jan 17 21:51:21 ryzen systemd[1]: Starting Show Plymouth Reboot Screen... 
    Jan 17 21:51:21 ryzen systemd[1]: Stopping NTP client/server... 
    Jan 17 21:51:21 ryzen chronyd[1172]: chronyd exiting 
    Jan 17 21:51:21 ryzen systemd[1]: Stopped target System Time Set. 
    Jan 17 21:51:21 ryzen systemd[1]: Stopped target System Time Synchronized. 
    Jan 17 21:51:21 ryzen systemd[1]: display-manager.service: Consumed 12.118s CPU time.
    Jan 17 21:51:21 ryzen systemd[1]: Stopped X Display Manager. 
    Jan 17 21:51:21 ryzen systemd[1]: display-manager.service: Deactivated successfully. 
    Jan 17 21:51:21 ryzen display-manager[1178]: Starting service sddm 
    Jan 17 21:51:21 ryzen sddm[1266]: QProcess: Destroyed while process ("/usr/libexec/sddm/sddm-helper") is still running.
    Jan 17 21:51:21 ryzen sddm[1266]: Running display stop script  "/usr/share/sddm/scripts/Xstop"
    Ich wüste nicht, dass Dolphin noch lief?!?

  7. #7

    Default Re: 90 Sekunden stop job beim Shutdown. Warum? Was?

    Ich habe nur 3 Mail-Accounts mit wenig Trafic.

    Und ja, das passiert auch, wenn ich mich erst abmelde und dann 'runterfahre.

    Danke an alle für die Unterstützung.

  8. #8
    Join Date
    Jan 2014
    Location
    Erlangen
    Posts
    4,005

    Default Re: AW: 90 Sekunden stop job beim Shutdown. Warum? Was?

    Quote Originally Posted by wodenhof View Post
    Okay, hab's gemacht, hier ist der Ausschnitt aus journalctl -r:
    Code:
    Jan 17 21:52:51 ryzen systemd[1]: Stopping User Login Management... 
    Jan 17 21:52:51 ryzen systemd[1]: session-2.scope: Consumed 13.423s CPU time.
    Jan 17 21:52:51 ryzen systemd[1]: Stopped Session 2 of User matthias. 
    Jan 17 21:52:51 ryzen systemd[1]: session-2.scope: Failed with result 'timeout'.
    Jan 17 21:52:51 ryzen systemd[1]: session-2.scope: Killing process 2465 (n/a) with signal SIGKILL.
    Jan 17 21:52:51 ryzen systemd[1]: session-2.scope: Killing process 2461 (pipe-connection) with signal SIGKILL.
    Jan 17 21:52:51 ryzen systemd[1]: session-2.scope: Killing process 2460 (scdaemon) with signal SIGKILL.
    Jan 17 21:52:51 ryzen systemd[1]: session-2.scope: Stopping timed out. Killing.
    Jan 17 21:51:22 ryzen systemd[1808]: app-org.kde.dolphin-fd80401f3c77409ebb54cc484fa651da.scope: Consumed 4.613s CPU time.
    Jan 17 21:51:21 ryzen systemd[1]: Condition check resulted in Tell Plymouth To Jump To initramfs being skipped. 
    Jan 17 21:51:21 ryzen systemd[1]: Started Show Plymouth Reboot Screen. 
    Jan 17 21:51:21 ryzen systemd[1]: Received SIGRTMIN+20 from PID 5724 (plymouthd). 
    Jan 17 21:51:21 ryzen systemd[1]: Stopped target Host and Network Name Lookups. 
    Jan 17 21:51:21 ryzen systemd[1]: Stopped NTP client/server. 
    Jan 17 21:51:21 ryzen systemd[1]: chronyd.service: Deactivated successfully. 
    Jan 17 21:51:21 ryzen systemd[1]: Starting Show Plymouth Reboot Screen... 
    Jan 17 21:51:21 ryzen systemd[1]: Stopping NTP client/server... 
    Jan 17 21:51:21 ryzen chronyd[1172]: chronyd exiting 
    Jan 17 21:51:21 ryzen systemd[1]: Stopped target System Time Set. 
    Jan 17 21:51:21 ryzen systemd[1]: Stopped target System Time Synchronized. 
    Jan 17 21:51:21 ryzen systemd[1]: display-manager.service: Consumed 12.118s CPU time.
    Jan 17 21:51:21 ryzen systemd[1]: Stopped X Display Manager. 
    Jan 17 21:51:21 ryzen systemd[1]: display-manager.service: Deactivated successfully. 
    Jan 17 21:51:21 ryzen display-manager[1178]: Starting service sddm 
    Jan 17 21:51:21 ryzen sddm[1266]: QProcess: Destroyed while process ("/usr/libexec/sddm/sddm-helper") is still running.
    Jan 17 21:51:21 ryzen sddm[1266]: Running display stop script  "/usr/share/sddm/scripts/Xstop"
    Ich wüste nicht, dass Dolphin noch lief?!?
    Dolphin stoppte doch ordnungsgemäß. Siehe z.B. dieses Beispiel:
    Code:
    karl@erlangen:~> journalctl --user -b -1 -u app-org.kde.kmail2-37fc91f2d98b4ce4b48c81a9bed05c71.scope 
    -- Journal begins at Wed 2021-12-15 08:27:13 CET, ends at Tue 2022-01-18 08:17:02 CET. -- 
    Jan 17 19:46:24 erlangen systemd[1186]: Started KMail - E-Mail-Programm. 
    Jan 17 19:46:26 erlangen kmail[1481]: Cannot initialize model with data QJsonObject(). missing: QJsonValue(string, "urls")
    Jan 17 19:48:55 erlangen kmail[1481]: kf.notifications: env says KDE is running but SNI unavailable -- check KDE_FULL_SESSION and XDG_CURRENT_DESKTOP
    Jan 17 19:48:55 erlangen kmail[1481]: "QLocalSocket: Die Verbindung wurde von der Gegenseite geschlossen" "/run/user/1000/akonadi/akonadiserver-cmd.socket"
    Jan 17 19:48:55 erlangen kmail[1481]: "QLocalSocket: Die Verbindung wurde von der Gegenseite geschlossen" "/run/user/1000/akonadi/akonadiserver-cmd.socket"
    Jan 17 19:48:55 erlangen kmail[1481]: "QLocalSocket: Die Verbindung wurde von der Gegenseite geschlossen" "/run/user/1000/akonadi/akonadiserver-cmd.socket"
    Jan 17 19:48:55 erlangen systemd[1186]: Stopping KMail - E-Mail-Programm... 
    Jan 17 19:48:55 erlangen systemd[1186]: Stopped KMail - E-Mail-Programm. 
    Jan 17 19:48:55 erlangen systemd[1186]: app-org.kde.kmail2-37fc91f2d98b4ce4b48c81a9bed05c71.scope: Consumed 1.515s CPU time.
    karl@erlangen:~> 
    Die Problembären sind die Prozesse 2460, 2461 und 2465. Wo gehören die hin?
    i7-6700K (2016), i5-8250U (2018), AMD Ryzen 5 3400G (2020), 5600X (2022) openSUSE Tumbleweed, KDE Plasma

  9. #9

    Default Re: AW: 90 Sekunden stop job beim Shutdown. Warum? Was?

    Quote Originally Posted by karlmistelberger View Post
    Die Problembären sind die Prozesse 2460, 2461 und 2465. Wo gehören die hin?
    Äh -- keine Ahnung. Wie kann man das herausbekommen? Die Nummern ändern sich doch nit jedem Booten...

    Ach ja, und danke für den Hinweis in Sachen Dolphin .

  10. #10

    Default Re: 90 Sekunden stop job beim Shutdown. Warum? Was?

    But (in case this helps):
    Code:
    me@ryzen:~> sudo systemctl status session-2.scope   
     session-2.scope - Session 2 of User me 
         Loaded: loaded (/run/systemd/transient/session-2.scope; transient) 
      Transient: yes 
         Active: active (running) since Tue 2022-01-18 17:37:33 CET; 4h 6min ago 
          Tasks: 128 
            CPU: 48.967s 
         CGroup: /user.slice/user-1000.slice/session-2.scope 
                 ├─5042 /usr/libexec/sddm/sddm-helper --socket /tmp/sddm-auth8d4488b6-4b19-4537-83c8-1f2541462c8a --id 1 --start /usr/bin/startplasma-x11 --user me 
                 ├─5053 /usr/bin/startplasma-x11 
                 ├─5132 /usr/bin/ssh-agent /usr/bin/gpg-agent --sh --daemon --keep-display /usr/libexec/xinit/xinitrc 
                 ├─5133 /usr/bin/gpg-agent --sh --daemon --keep-display /usr/libexec/xinit/xinitrc 
                 ├─5188 /usr/lib64/libexec/kf5/start_kdeinit 
                 ├─5189 "kdeinit5: Running..." "" "" "" "" "" "" "" "" "" "" 
                 ├─5190 /usr/lib64/libexec/kf5/klauncher --fd=9 
                 ├─5203 /usr/bin/kded5 
                 ├─5207 /usr/bin/kwin_x11 
                 ├─5218 /usr/bin/xsettingsd 
                 ├─5287 /usr/bin/ksmserver 
                 ├─5297 /usr/lib64/libexec/polkit-kde-authentication-agent-1 
                 ├─5299 /usr/lib64/libexec/org_kde_powerdevil 
                 ├─5301 /usr/bin/kaccess 
                 ├─5303 /usr/bin/plasmashell 
                 ├─5306 /usr/bin/xembedsniproxy 
                 ├─5308 /usr/lib64/libexec/baloo_file 
                 ├─5405 /usr/bin/gmenudbusmenuproxy 
                 ├─5451 /usr/libexec/geoclue-2.0/demos/agent 
                 ├─5580 scdaemon --multi-server 
                 ├─6234 /usr/lib64/libexec/kf5/kioslave5 /usr/lib64/qt5/plugins/kf5/kio/kio_file.so file "" local:/run/user/1000/kded5RVloyA.1.slave-socket 
                 └─6236 /usr/lib64/libexec/kf5/kioslave5 /usr/lib64/qt5/plugins/kf5/kio/kio_file.so file "" local:/run/user/1000/kded5LTsJGn.2.slave-socket 
    
    Jan 18 17:48:54 ryzen kscreenlocker_greet[7336]: qt.svg: <input>:303:1453: Could not add child element to parent element because the types are incorrect.
    Jan 18 17:48:54 ryzen kscreenlocker_greet[7336]: qt.svg: <input>:303:1631: Could not add child element to parent element because the types are incorrect.
    Jan 18 17:48:54 ryzen kscreenlocker_greet[7336]: qt.svg: <input>:303:1739: Could not add child element to parent element because the types are incorrect.
    Jan 18 17:48:54 ryzen kscreenlocker_greet[7336]: qt.svg: <input>:303:1980: Could not add child element to parent element because the types are incorrect.
    Jan 18 17:48:54 ryzen kscreenlocker_greet[7336]: qt.svg: <input>:303:2223: Could not add child element to parent element because the types are incorrect.
    Jan 18 17:48:54 ryzen kscreenlocker_greet[7336]: file:///usr/share/plasma/look-and-feel/org.kde.breeze.desktop/contents/components/UserList.qml:47:9: Unable to assign [undefined] to bool
    Jan 18 18:35:55 ryzen plasmashell[5303]: libkcups: Renew-Subscription last error: 0 successful-ok
    Jan 18 19:34:15 ryzen plasmashell[5303]: libkcups: Renew-Subscription last error: 0 successful-ok
    Jan 18 20:32:35 ryzen plasmashell[5303]: libkcups: Renew-Subscription last error: 0 successful-ok
    Jan 18 21:30:55 ryzen plasmashell[5303]: libkcups: Renew-Subscription last error: 0 successful-ok
    
    Since there was some complaint about "session-2.scope"...

Page 1 of 4 123 ... LastLast

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •