udev rules wrongly match on monitor hub, wrong invocation of systemd unit, changes config files in udev rules
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
HPLIP |
Fix Released
|
Undecided
|
Unassigned | ||
hplip (Ubuntu) |
Fix Released
|
High
|
Unassigned |
Bug Description
During boot, systemd-
Journal report this:
> root@alice:~# journalctl -u systemd-udev-settle
> -- Logs begin at Wed 2015-03-18 12:38:16 CET, end at Wed 2015-03-18 12:47:32 CET. --
> Mar 18 12:38:16 alice systemd[1]: Starting udev Wait for Complete Device Initialization...
> Mar 18 12:41:16 alice systemd[1]: systemd-
> Mar 18 12:41:16 alice systemd[1]: Failed to start udev Wait for Complete Device Initialization.
> Mar 18 12:41:16 alice systemd[1]: Unit systemd-
> Mar 18 12:41:16 alice systemd[1]: systemd-
> Mar 18 12:41:17 alice systemd[1]: Starting udev Wait for Complete Device Initialization...
> Mar 18 12:41:18 alice systemd[1]: Started udev Wait for Complete Device Initialization.
The dmesg output arround that time is:
> [ 8.537560] Adding 16723964k swap on /dev/sda4. Priority:-1 extents:1 across:16723964k FS
> [ 9.559871] input: ST LIS3LV02DL Accelerometer as /devices/
> [ 189.205551] Bluetooth: Core ver 2.20
> [ 189.205565] NET: Registered protocol family 31
ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: dbus 1.8.12-1ubuntu3
ProcVersionSign
Uname: Linux 3.19.0-9-generic x86_64
NonfreeKernelMo
ApportVersion: 2.16.2-0ubuntu3
Architecture: amd64
CurrentDesktop: XFCE
Date: Wed Mar 18 12:51:08 2015
SourcePackage: dbus
UpgradeStatus: Upgraded to vivid on 2015-03-02 (15 days ago)
Related branches
tags: | added: systemd-boot |
Changed in linux (Ubuntu): | |
importance: | Undecided → Medium |
Changed in hplip (Ubuntu): | |
status: | Confirmed → In Progress |
It seems then that the accelerometer is taking a long time to initialize, right?
Mind starting a debug boot (systemd. log_level= debug in grub init line) and pasting the journactl -b output so that we get all related logs? Thanks!