Bug 2213658 - Logout should be clean - no service unit failures
Summary: Logout should be clean - no service unit failures
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: plasma-workspace
Version: 39
Hardware: Unspecified
OS: Linux
unspecified
low
Target Milestone: ---
Assignee: KDE SIG
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-06-08 22:11 UTC by Orion Poplawski
Modified: 2024-11-27 21:12 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2024-11-27 21:12:59 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Orion Poplawski 2023-06-08 22:11:51 UTC
When logging out of a plasma X11 or wayland session a number of systemd services end up in a failed state.  This clutters up logwatch and similar reports when trying to monitor system health.

Reproducible: Always

Steps to Reproduce:
1. Log out of session
2. sudo logwatch --service systemd --range Today

Actual Results:  
 ERROR: Failed state:
         dbus-:1.42-org.a11y.atspi.Registry: 1 Time(s)
         dbus-:1.49-org.a11y.atspi.Registry: 1 Time(s)
         plasma-kactivitymanagerd.service: 2 Time(s)
         plasma-kded.service: 3 Time(s)
         plasma-kglobalaccel.service: 1 Time(s)
         plasma-kscreen.service: 1 Time(s)
         plasma-kwin_x11.service: 2 Time(s)
         plasma-plasmashell.service: 1 Time(s)
         plasma-polkit-agent.service: 1 Time(s)
         plasma-powerdevil.service: 2 Time(s)
         plasma-xdg-desktop-portal-kde.service: 3 Time(s)
         xdg-desktop-portal-gnome.service: 5 Time(s)
         xdg-desktop-portal-gtk.service: 3 Time(s)

Expected Results:  
No service unit failures

Jun 08 15:48:56 kglobalaccel5[17033]: The X11 connection broke (error 1). Did the X11 server die?
Jun 08 15:48:56 kded5[17064]: X connection to :0 broken (explicit kill or server shutdown).
Jun 08 15:48:56 kglobalaccel5[17033]: The X11 connection broke: I/O error (code 1)
Jun 08 15:48:56 kglobalaccel5[17033]: XIO:  fatal IO error 25 (Inappropriate ioctl for device) on X server ":0"
Jun 08 15:48:56 kglobalaccel5[17033]:       after 8 requests (8 known processed) with 0 events remaining.
Jun 08 15:48:56 xdg-desktop-portal-kde[17449]: The X11 connection broke (error 1). Did the X11 server die?
Jun 08 15:48:56 kded5[16992]: X connection to :0 broken (explicit kill or server shutdown).
Jun 08 15:48:56 kded5[16992]: The X11 connection broke: I/O error (code 1)
Jun 08 15:48:56 at-spi2-registryd[17497]: X connection to :0 broken (explicit kill or server shutdown).
Jun 08 15:48:56 kaccess[17332]: The X11 connection broke (error 1). Did the X11 server die?
Jun 08 15:48:56 systemd[16706]: xdg-desktop-portal-gnome.service: Main process exited, code=exited, status=1/FAILURE
Jun 08 15:48:56 systemd[16706]: xdg-desktop-portal-gnome.service: Failed with result 'exit-code'.
Jun 08 15:48:56 systemd[16706]: plasma-kglobalaccel.service: Main process exited, code=exited, status=1/FAILURE
Jun 08 15:48:56 systemd[16706]: plasma-kglobalaccel.service: Failed with result 'exit-code'.
Jun 08 15:48:56 systemd[16706]: app-org.gnome.Evolution\x2dalarm\x2dnotify: Main process exited, code=exited, status=1/FAILURE
Jun 08 15:48:56 systemd[16706]: app-org.gnome.Evolution\x2dalarm\x2dnotify: Failed with result 'exit-code'.
Jun 08 15:48:56 systemd[16706]: plasma-xdg-desktop-portal-kde.service: Main process exited, code=exited, status=1/FAILURE
Jun 08 15:48:56 systemd[16706]: plasma-xdg-desktop-portal-kde.service: Failed with result 'exit-code'.
Jun 08 15:48:56 systemd[16706]: xdg-desktop-portal-gtk.service: Main process exited, code=exited, status=1/FAILURE
Jun 08 15:48:56 systemd[16706]: xdg-desktop-portal-gtk.service: Failed with result 'exit-code'.
Jun 08 15:48:56 systemd[16706]: dbus-:1.42-org.a11y.atspi.Registry: Main process exited, code=exited, status=1/FAILURE
Jun 08 15:48:56 systemd[16706]: dbus-:1.42-org.a11y.atspi.Registry: Failed with result 'exit-code'.
Jun 08 15:48:56 systemd[16706]: plasma-kded.service: Failed with result 'exit-code'.
Jun 08 15:48:56 kwin_x11[16993]: The X11 connection broke: I/O error (code 1)
Jun 08 15:48:56 kwin_x11[16993]: XIO:  fatal IO error 0 (Success) on X server ":0"
Jun 08 15:48:56 kwin_x11[16993]:       after 13263 requests (13241 known processed) with 0 events remaining.
Jun 08 15:48:56 systemd[16706]: plasma-kwin_x11.service: Main process exited, code=exited, status=1/FAILURE
Jun 08 15:48:56 systemd[16706]: plasma-kwin_x11.service: Failed with result 'exit-code'.

Comment 1 Fedora Release Engineering 2023-08-16 08:15:19 UTC
This bug appears to have been reported against 'rawhide' during the Fedora Linux 39 development cycle.
Changing version to 39.

Comment 2 Aoife Moloney 2024-11-08 10:53:24 UTC
This message is a reminder that Fedora Linux 39 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 39 on 2024-11-26.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
'version' of '39'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, change the 'version' 
to a later Fedora Linux version. Note that the version field may be hidden.
Click the "Show advanced fields" button if you do not see it.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora Linux 39 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora Linux, you are encouraged to change the 'version' to a later version
prior to this bug being closed.

Comment 3 Aoife Moloney 2024-11-27 21:12:59 UTC
Fedora Linux 39 entered end-of-life (EOL) status on 2024-11-26.

Fedora Linux 39 is no longer maintained, which means that it
will not receive any further security or bug fix updates. As a result we
are closing this bug.

If you can reproduce this bug against a currently maintained version of Fedora Linux
please feel free to reopen this bug against that version. Note that the version
field may be hidden. Click the "Show advanced fields" button if you do not see
the version field.

If you are unable to reopen this bug, please file a new report against an
active release.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.