can not read /etc/udev/rules.d/z80_user.rules message
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Baltix |
Won't Fix
|
Undecided
|
Unassigned | ||
pysdm (Ubuntu) |
Won't Fix
|
High
|
Unassigned |
Bug Description
Binary package hint: udev
This message appeares in the log files at boot up of a Ubuntu 10.04 system.
The file in question is a link to the empty file /etc/udev/
The script testing/loading this file should test for an empty file and then ignore it, or whatever package creates this file should give it some content so this subsequent test does not fail.
Many people have posted about this message worried that there is a problem with their systems, even though this does not affect the operations of a system anything that causes erroneous warnings only helps to confuse and discredit any potential real messages.
ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: udev 151-12
ProcVersionSign
Uname: Linux 2.6.32-22-generic x86_64
NonfreeKernelMo
Architecture: amd64
CustomUdevRuleF
Date: Sat May 15 14:50:27 2010
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Alpha amd64 (20100308)
MachineType: Gigabyte Technology Co., Ltd. GA-MA78GM-S2HP
ProcCmdLine: BOOT_IMAGE=
ProcEnviron:
LANG=en_AU.utf8
SHELL=/bin/bash
SourcePackage: udev
dmi.bios.date: 06/23/2009
dmi.bios.vendor: Award Software International, Inc.
dmi.bios.version: F5
dmi.board.name: GA-MA78GM-S2HP
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.modalias: dmi:bvnAwardSof
dmi.product.name: GA-MA78GM-S2HP
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
Changed in pysdm (Ubuntu): | |
status: | Triaged → Won't Fix |
Changed in baltix: | |
status: | New → Invalid |
Changed in baltix: | |
status: | Invalid → Won't Fix |
Thank you. This workaround helps: /bugs.launchpad .net/ubuntu/ +source/ udev/+bug/ 580811"|sudo tee -a /etc/udev/ rules.d/ z80_user. rules
echo "#https:/
I guess it's a bug against update-manager-core in hardy or whatever else, because it's a left-over from an earlier installation that should be handled by the upgrade process...