ureadahead reports relative path errors in journalctl output
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
ureadahead (Ubuntu) |
Won't Fix
|
High
|
Unassigned | ||
Xenial |
Fix Released
|
Low
|
Dan Streetman | ||
Bionic |
Fix Released
|
Low
|
Dan Streetman |
Bug Description
[impact]
ureadahead logs thousands of lines of useless noise on each boot.
[test case]
install bionic on physical hardware (ureadhead doesn't run under virt) and check the boot logs:
#journalctl -b | grep ureadahead | wc -l
30244
ureadahead stores its data in /var/lib/
to reproduce this test case without waiting a month, just remove the pack file and reboot.
[regression potential]
very little, adding the -q param only causes libnih to switch to quiet mode. any regression would likely be around ureadahead not starting at all, which really wouldn't be that bad anyway, as ureadahead has been removed entirely from Ubuntu starting in cosmic.
[other info]
original description:
--
ureadahead reports relative path errors in my journalctl output.
This is currently 4368 lines of useless annoyances in my logs.
To see if you have this problem, run: journalctl -b | grep ureadahead | grep relative | wc -l
Thanks
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: ureadahead 0.100.0-19
ProcVersionSign
Uname: Linux 4.4.0-22-generic x86_64
NonfreeKernelMo
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
Date: Sun May 8 15:55:18 2016
InstallationDate: Installed on 2016-04-04 (34 days ago)
InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Beta amd64 (20160325)
ProcEnviron:
TERM=linux
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: ureadahead
UpgradeStatus: No upgrade log present (probably fresh install)
Changed in ureadahead (Ubuntu): | |
importance: | Undecided → High |
tags: | added: bionic |
description: | updated |
Changed in ureadahead (Ubuntu Xenial): | |
status: | New → In Progress |
importance: | Undecided → Low |
assignee: | nobody → Dan Streetman (ddstreet) |
description: | updated |
Status changed to 'Confirmed' because the bug affects multiple users.