Description of problem:
In some cases, the output of udevadm info --export-db has an unexpected format.
Version-Release number of selected component (if applicable):
[mulhern@dhcp-25-209 ~]$ udevadm --version
Always, on my machine.
Steps to Reproduce:
1. Update to f23 (this was not happening on f22).
2. Run udevadm info --export-db.
3. Expect that all entries will begin with an identifying letter followed by
a colon, e.g., "E: MODALIAS=usb:v0458p0137d0100dc00dsc00dp00ic03isc01ip02in00
4. Notice that some entries do not have this format, e.g., "MODALIAS=hid:b0003g0001v00000458p00000137".
5. Notice that there seems to be something wrong with the preceding entry in this case, e.g.,
Funky formatting for some entries in output of udevadm info --export-db.
No funky formatting.
Occurs with particular devices:
but not w/ any others that I have observed on my machine.
Looks like the problem originates in the database entry as libudev, via pyudev, think that the value of HID_UNIQ is
"u'\nMODALIAS=hid:b0003g0001v00000458p00000137'", which has to be wrong.
So, that's where to fix it.
[mulhern@dhcp-25-209 pyudev]$ udevadm info /sys/devices/pci0000:00/0000:00:14.0/usb3/3-4/3-4:1.0/0003:0458:0137.0001
E: HID_NAME=PixArt USB Optical Mouse
libudev (pyudev) doesn't seem to be able to obtain a value for MODALIAS (makes sense, pudev directly calls the udev get_property method) , but udevadm sort of can:
[mulhern@dhcp-25-209 udev]$ udevadm info --root --path /sys/devices/pci0000:00/0000:00:16.0/mei::12f80028-b4b7-4b2d-aca8-46e0ff65814c:01 --query property
Also, and I'm not sure if this is correct or not, sometimes MODALIAS looks surprising:
It's some sort of db corruption, I'm looking into it:
#0 device_add_property_aux (device=0x555555688be0, _key=0x55555568c123 "HID_UNIQ", _value=0x55555568c12c "\nMODALIAS=hid:b0003g0001v00000C76p00001607", db=false) at src/libsystemd/sd-device/sd-device.c:102
#1 0x00005555555e6ed9 in device_add_property_internal (device=0x555555688be0, key=0x55555568c123 "HID_UNIQ", value=0x55555568c12c "\nMODALIAS=hid:b0003g0001v00000C76p00001607") at src/libsystemd/sd-device/sd-device.c:149
Thanks for the report. This fixes it for me: https://github.com/systemd/systemd/pull/3330
systemd-229-8.fc24 has been submitted as an update to Fedora 24. https://bodhi.fedoraproject.org/updates/FEDORA-2016-5f8a34340d
systemd-229-8.fc24 has been pushed to the Fedora 24 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2016-5f8a34340d
systemd-229-8.fc24 has been pushed to the Fedora 24 stable repository. If problems still persist, please make note of it in this bug report.
Reopening for F23.
This message is a reminder that Fedora 23 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 23. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora 'version'
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.
Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 23 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
This seems to be fixed in F24.
Fedora 23 changed to end-of-life (EOL) status on 2016-12-20. Fedora 23 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
Thank you for reporting this bug and we are sorry it could not be fixed.