Description of problem: abrt-xorg.service fails to start. Systemctl status reports that abrt-dum-journal-xorg cannot read journal data. After running journalctl --verify I found several corrupted journal entires. $ systemctl status abrt-xorg --no-pager -l ● abrt-xorg.service - ABRT Xorg log watcher Loaded: loaded (/usr/lib/systemd/system/abrt-xorg.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Wed 2017-08-16 17:44:08 CEST; 4h 4min ago Process: 1113 ExecStart=/usr/bin/abrt-dump-journal-xorg -fxtD (code=exited, status=1/FAILURE) Main PID: 1113 (code=exited, status=1/FAILURE) Aug 16 17:44:07 overlord systemd[1]: Started ABRT Xorg log watcher. Aug 16 17:44:08 overlord abrt-dump-journal-xorg[1113]: abrt-dump-journal-xorg: Cannot read journal data. Aug 16 17:44:08 overlord systemd[1]: abrt-xorg.service: Main process exited, code=exited, status=1/FAILURE Aug 16 17:44:08 overlord systemd[1]: abrt-xorg.service: Unit entered failed state. Aug 16 17:44:08 overlord systemd[1]: abrt-xorg.service: Failed with result 'exit-code'. $ abrt-dump-journal-xorg -vvv abrt-dump-journal-xorg: Loading settings from 'xorg.conf' abrt-dump-journal-xorg: Loaded option 'BlacklistedXorgModules' = 'nvidia, fglrx, vboxvideo' abrt-dump-journal-xorg: Loaded option 'JournalFilters' = '_COMM=gdm-x-session, _COMM=gnome-shell' abrt-dump-journal-xorg: Loaded option 'BlacklistedXorgModules' = 'nvidia, fglrx, vboxvideo' abrt-dump-journal-xorg: Loaded option 'JournalFilters' = '_COMM=gdm-x-session, _COMM=gnome-shell' abrt-dump-journal-xorg: Loaded 'xorg.conf' abrt-dump-journal-xorg: Using journal filter from conf file xorg.conf abrt-dump-journal-xorg: Using journal match: '_COMM=gdm-x-session' abrt-dump-journal-xorg: Using journal match: '_COMM=gnome-shell' abrt-dump-journal-xorg: Failed to read 'MESSAGE' field: Bad message abrt-dump-journal-xorg: Cannot read journal data. Version-Release number of selected component (if applicable): abrt-addon-xorg-2.10.3-1.fc26.x86_64 How reproducible: Corrupt journal somehow.
I seem to have same/similar issue as Dawid. Journal corruption should not avoid abrt-xorg starting up. Moreover, there must be a way to repair corrupted journal.
This message is a reminder that Fedora 26 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 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 Fedora 'version' of '26'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 26 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, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 26 changed to end-of-life (EOL) status on 2018-05-29. Fedora 26 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 please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.
I am seeing exactly this issue on Fedora 28 x86_64. The output of abrt-dump-journal-xorg -vvv is identical to that shown in the original report.
I am experiencing the same as Jerry James
This message is a reminder that Fedora 28 is nearing its end of life. On 2019-May-28 Fedora will stop maintaining and issuing updates for Fedora 28. 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 Fedora 'version' of '28'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 28 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, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 28 changed to end-of-life (EOL) status on 2019-05-28. Fedora 28 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 please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.