Public bug reported:
16.04 gets a messed up fs, so that fsck has to be run every few hours. symptom
is other SW packages don't run properly. re-boot exit says clean. But upon
re-entry, fsck is needed.
Would like to see a warning, and choice, upon exit, that the fs is messed up
and would like to fix it now or when re-booting, or re-starting the system.
ps. fixing the origin of the messed up fs is preferred, but that seems to be
too far out...
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: ubuntu-release-upgrader-core 1:16.04.21
ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62
Uname: Linux 4.4.0-78-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
CrashDB: ubuntu
CurrentDesktop: Unity
Date: Wed May 31 22:40:33 2017
InstallationDate: Installed on 2017-05-13 (19 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
PackageArchitecture: all
ProcEnviron:
LANGUAGE=en_US
PATH=(custom, no user)
XDG_RUNTIME_DIR=<set>
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: ubuntu-release-upgrader
Symptom: release-upgrade
UpgradeStatus: No upgrade log present (probably fresh install)
** Affects: ubuntu-release-upgrader (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug dist-upgrade xenial
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1694879
Title:
Chrome would not start. reboot displayed line fsck clean. reboot
proceeded and came back with some prompt that indicates a fsck needs
to be done. Therefore it was not clean to begin with and thus no
warning, or indications that anything had gone wrong until after a
reboot had started. fsck is realativly fast, compared to a reboot or
startup, but does add time. I might rather clean uo the files when
shuting down or rebooting, or in the middle of doing something like
starting chrome when it does not start. ps. I have not figured out
what causes the file to get corrupted, but it happens every few hours
of human computer time. for example, a long day at the computer, and
there are a few times of fsck. a brief evening session and probably
not for a couple of days. My suspicion is that some routine/s is/are
not shutting down correctly.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1694879/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
