Missing libudev-dev package for udev-249.11-0ubuntu3.1

Bug #1979802 reported by jiriprox
66
This bug affects 12 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

The latest Ubuntu 22.04 cloud image contains udev/now 249.11-0ubuntu3.1 amd64 Nevertheless there is no corresponding libudev-dev package available.

The same issue appears whenever new udev version is release :-(

apt install libudev-dev
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 libudev-dev : Depends: libudev1 (= 249.11-0ubuntu3) but 249.11-0ubuntu3.1 is to be installed
E: Unable to correct problems, you have held broken packages.

Here is list of available packages:
apt list |grep udev

WARNING: apt does not have a stable CLI interface. Use with caution in scripts.

bilibop-udev/jammy 0.6.3 amd64
brightness-udev/jammy 0.5.1-3 all
gir1.2-gudev-1.0/jammy 1:237-2build1 amd64
golang-gir-gudev-1.0-dev/jammy 2.0.4~git20211109.4b0a2df-1 all
golang-github-jochenvg-go-udev-dev/jammy 0.0~git20171110.d6b62d5-2 all
hdmi2usb-udev/jammy 0.0.1-2 all
ledger-wallets-udev/jammy 0.3 all
libgudev-1.0-0/jammy,now 1:237-2build1 amd64 [installed,automatic]
libgudev-1.0-dev/jammy 1:237-2build1 amd64
libgudev1.0-cil-dev/jammy 0.1-4.1ubuntu1 all
libgudev1.0-cil/jammy 0.1-4.1ubuntu1 all
libgudev3.0-cil-dev/jammy 3.0.0-1build1 all
libgudev3.0-cil/jammy 3.0.0-1build1 all
librte-gpudev22/jammy-updates,jammy-security 21.11.1-0ubuntu0.3 amd64
librust-libudev-dev/jammy 0.3.0-1 amd64
librust-libudev-sys-dev/jammy 0.1.4-1 amd64
libu2f-udev/jammy 1.1.10-3build2 all
libudev-dev/jammy 249.11-0ubuntu3 amd64
libudev0/jammy 200-1 amd64
libudev1/now 249.11-0ubuntu3.1 amd64 [installed,local]
libyubikey-udev/jammy 1.20.0-3 all
limesuite-udev/jammy 20.10.0+dfsg-5 all
ludevit/jammy 9.2-1 all
monodoc-gudev-manual/jammy 3.0.0-1build1 all
python3-pyudev/jammy 0.22.0-2 all
sg3-utils-udev/jammy,now 1.46-1build1 all [installed,automatic]
system-config-printer-udev/jammy 1.5.16-0ubuntu3 amd64
tpm-udev/jammy,now 0.6 all [installed,automatic]
udev/now 249.11-0ubuntu3.1 amd64 [installed,local]
udevil/jammy 0.4.4-3 amd64
uudeview/jammy 0.5.20-13 amd64
---
ProblemType: Bug
AlsaDevices:
 total 0
 crw-rw---- 1 root audio 116, 1 Jun 24 08:05 seq
 crw-rw---- 1 root audio 116, 33 Jun 24 08:05 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
CRDA: N/A
CasperMD5CheckResult: unknown
DistroRelease: Ubuntu 22.04
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Lsusb-t:
 /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/15p, 5000M
 /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/15p, 480M
     |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 480M
MachineType: QEMU Standard PC (Q35 + ICH9, 2009)
Package: linux (not installed)
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=C.UTF-8
 SHELL=/bin/bash
ProcFB:

ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-39-generic root=UUID=f44c6339-a6fd-4158-9e95-b421ec3173c9 ro default_hugepagesz=1G hugepagesz=1G hugepages=4 hugepagesz=2M hugepages=1024 vfio-pci.disable_denylist=1 rdt=cmt,mbmtotal,mbmlocal,l3cat,l3cdp,l2cat,l2cdp,mba console=tty1 console=ttyS0
ProcVersionSignature: Ubuntu 5.15.0-39.42-generic 5.15.35
RebootRequiredPkgs: Error: path contained symlinks.
RelatedPackageVersions:
 linux-restricted-modules-5.15.0-39-generic N/A
 linux-backports-modules-5.15.0-39-generic N/A
 linux-firmware N/A
RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
Tags: jammy uec-images
Uname: Linux 5.15.0-39-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: N/A
_MarkForUpload: True
dmi.bios.date: 04/01/2014
dmi.bios.release: 0.0
dmi.bios.vendor: SeaBIOS
dmi.bios.version: 1.15.0-1
dmi.chassis.type: 1
dmi.chassis.vendor: QEMU
dmi.chassis.version: pc-q35-6.2
dmi.modalias: dmi:bvnSeaBIOS:bvr1.15.0-1:bd04/01/2014:br0.0:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-6.2:cvnQEMU:ct1:cvrpc-q35-6.2:sku:
dmi.product.name: Standard PC (Q35 + ICH9, 2009)
dmi.product.version: pc-q35-6.2
dmi.sys.vendor: QEMU

Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote : Missing required logs.

This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:

apport-collect 1979802

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
jiriprox (jirix-x-prokes) wrote : CurrentDmesg.txt

apport information

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
tags: added: apport-collected jammy uec-images
description: updated
Revision history for this message
jiriprox (jirix-x-prokes) wrote : Lspci.txt

apport information

Revision history for this message
jiriprox (jirix-x-prokes) wrote : Lspci-vt.txt

apport information

Revision history for this message
jiriprox (jirix-x-prokes) wrote : Lsusb-v.txt

apport information

Revision history for this message
jiriprox (jirix-x-prokes) wrote : PciMultimedia.txt

apport information

Revision history for this message
jiriprox (jirix-x-prokes) wrote : ProcCpuinfo.txt

apport information

Revision history for this message
jiriprox (jirix-x-prokes) wrote : ProcCpuinfoMinimal.txt

apport information

Revision history for this message
jiriprox (jirix-x-prokes) wrote : ProcInterrupts.txt

apport information

Revision history for this message
jiriprox (jirix-x-prokes) wrote : ProcModules.txt

apport information

Revision history for this message
jiriprox (jirix-x-prokes) wrote : UdevDb.txt

apport information

Revision history for this message
jiriprox (jirix-x-prokes) wrote :
Revision history for this message
Michael Webster (miketwebster) wrote :

Can confirm.

The following packages have unmet dependencies:
 libudev-dev : Depends: libudev1 (= 249.11-0ubuntu3) but 249.11-0ubuntu3.1 is to be installed
E: Unable to correct problems, you have held broken packages.

Installing as build-deps inside docker (ubuntu:jammy-20220531).

Revision history for this message
Blaze (blaze) wrote :

As I see 249.11-0ubuntu3.1 is removed from repos completely and newer build is already in proposed

Revision history for this message
David Mc Carthy (davidmccar) wrote :

Still seeing this issue with libudev-dev (249.11-0ubuntu3) wanting libudev1 (= 249.11-0ubuntu3) but the repos offering libudev1 249.11-0ubuntu3.3.

Revision history for this message
Andrew Shultzabarger (ardnew) wrote :

Is there a way to locally change libudev-dev's required version of dependency libudev1 (249.11-0ubuntu3) to match the officially-installed libudev1 (249.11-0ubuntu3.1) as a _temporary_ workaround?

Revision history for this message
jiriprox (jirix-x-prokes) wrote :

Latest available Cloud image contains udev/libudev1 with version 249.11-0ubuntu3.1:
Corresponding libudev-dev package with version 249.11-0ubuntu3.1 does not exist.
If I install latest libudev-dev package (249.11-0ubuntu3.3) then it destroy the machine because it uninstall udev package and machine does not come up after reboot (That issue was already reported for Ubuntu 21.04, 21.10 and 22.04 pre-release https://bugs.launchpad.net/pkg-website/+bug/1967118)

It seams that issue appears whenever new udev package version is released !

Temporary workaround could be: update udev to latest version first and then install libudev-dev package.

Revision history for this message
jiriprox (jirix-x-prokes) wrote :

What is status of bugfix for this bug? In which version I can expect fix?

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.