This bug was fixed in the package systemd - 219-6ubuntu3
---
systemd (219-6ubuntu3) vivid; urgency=medium
* Merge fixes from Debian experimental branch:
- Fix display-managers autopkgtest race.
- Enable timesyncd in virtual machines.
- fsck, fsckd: Grab various fixes
Still not approved upstream ?
Today i got /home fsck'ed, and got that error logged ~100 times:
systemd[1]: Starting File System Check on /dev/disk/by-uuid/5d8d1ee...
systemd[1]: Started Copy rules generated while the root was ro.
systemd-fsck[499]: lhom has been mounted 35 times without being
** Changed in: systemd (Ubuntu)
Status: In Progress = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1429171
Title:
systemd-fsckd[232]: Couldn't connect to plymouth: Connection
Feedback
after having made a few upgrades on utopic/vivid64, when i came back
booting vivid32, i got this logged again into journalctl:
systemd-fsck[507]: lhom: Superblock last write time is in the future.
systemd-fsck[507]: (by less than a day, probably due to the hardware clock
being
Seems related to that issue:
ubuntu-gnome-default-settings (15.04.3) vivid; urgency=medium
* Add fsck report and cancel support with systemd to the logo theme
(LP: #1425434)
-- Didier Roche didro...@ubuntu.com Wed, 25 Feb 2015 10:14:50 +0100
--
You received this bug notification
dino99: I guess plymouth wasn't running for you when fsck started,
right?
I conditioned the fact that the messages are sent to plymouth if the pid
file is present (see http://lists.freedesktop.org/archives/systemd-
devel/2015-March/029174.html)
** Changed in: systemd (Ubuntu)
Status: New
@Didier
this is a vivid i386 with a gnome-shell session; so i suppose that
plymouth is always used while logging (as expected by default, but i
admit i rarely care about it as that process is quite hidden for user)
and i suppose it is deactivated when the login is done.
now when i got that
@dino99: As I said on the other bug: please stop running your machines
with debug and getting scared by debug messages :-) (that's another
one)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1429171
@Martin
as i remember, 'debug' was not used when that issue was seen
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1429171
Title:
systemd-fsckd[232]: Couldn't connect to plymouth: Connection
dino99, can you please do
journalctl -ab /tmp/journal.txt
and attach it here?
Didier, can you please have a look at this?
** Changed in: systemd (Ubuntu)
Assignee: (unassigned) = Didier Roche (didrocks)
--
You received this bug notification because you are a member of Ubuntu
Bugs,
that systemd-fsck have appeared after having upgraded an other vivid
installation (64 bits) on its own partition, sharing the swap partition but not
/home.
Booting back on that vivid 32 bits, systemd-fschk was ran and terminated as
expected, excepted for that plymouth error.
** Attachment
note2: as fschk has not been used since that error, this error has not
then been seen indeed. But i suppose there is an issue connecting to
plymouth in such a case.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
12 matches
Mail list logo
