I get the bug in 18.04 - what does this mean?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1436168
Title:
systemd-journald crashed with SIGABRT in
Another day, another couple systemd-journald crash just like this
invalid bug.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1436168
Title:
systemd-journald crashed with
This bug was marked as invalid, but I get the error about every other
day. Is there any info I can provide to help verify the bug?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
Keep getting this bug lately in 17.10. Seems to happen most often when
using Chrome/Chromium or Opera, and more often still if using one of
those browsers on a Google property (Google Search, Google Images,
Gmail, YouTube).
--
You received this bug notification because you are a member of Ubuntu
Okay, closing then.
** Changed in: systemd (Ubuntu)
Status: Incomplete = Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1436168
Title:
systemd-journald
In my opinion not... - i will report a new bug if somethings goes wrong
again.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1436168
Title:
systemd-journald crashed with
Is there anything left to do/analyze here?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1436168
Title:
systemd-journald crashed with SIGABRT in
Thanks for the hint, Martin.
Maybe there was also a hardware problem cause the PC froze and was dead...
Recovering on a new machine was without problems.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
How can i reproduce this if i dont want to erase the machine complete
and recover the backup again?
Do you have /var/log/journal/ , i. e. enabled persistant journal? If so,
you could try and move it away (or just delete it if you don't care).
If not, the journal is just kept in /run/log/journal
No, shure not!
I just recovered files and directories in and into /home/
Systemd-journald crashes twice a day with #1433320 and #1437915 and
#1444654 and #1437896 and #1439507 and ...
How can i reproduce this if i dont want to erase the machine complete
and recover the backup again?
--
You
Ah, were you perhaps overwriting files in /var/log/journal/, while
systemd/journal were actually running? Changing the files underneath it
certainly doesn't go well. Can you be more specific what happened here?
Can you reproduce this somehow?
** Changed in: systemd (Ubuntu)
Status: New =
11 matches
Mail list logo
