udev update has broken ubuntu's ability to import photos in digikam, gphoto2 can no longer see usb camera, entangle can no longer see camera

Setting as "confirmed" as I have multiple anecdotal instances via #ubuntu IRC channel as well as twitter confirming this issue.

Set to "invalid" for Lunar and Mantic since they have different systemd versions.

I believe this is a regression of an SRU so I'm assigning this to "High" and assigning to the last uploader.

For understanding the nature of regression, it would be useful to see the output of

ls -l /dev/video*

Here is my output of ls -l /dev/video*

ls -l /dev/video*
crw-rw----+ 1 root video 81, 0 Sep 13 18:45 /dev/video0
crw-rw----+ 1 root video 81, 1 Sep 13 18:45 /dev/video1
crw-rw----+ 1 root video 81, 2 Sep 13 18:45 /dev/video2

Ok that shows ACLs are present. But I also just realized this was about still photography, not video, so those aren't the relevant devices. Less straightforward to find the right devices for a USB camera.

No I am using it for both still photography and for video streaming.

everything was working before the updating and then I updated " udev:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), systemd-timesyncd:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libpam-systemd:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libpam-systemd:i386 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libsystemd0:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libsystemd0:i386 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libnss-systemd:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libudev-dev:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), systemd:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libudev1:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libudev1:i386 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), systemd-sysv:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10) " and all of a sudden digikam could no longer talk to my camera, gphoto2 could no longer talk to my camera, entangle could no longer talk to my camera, again it all was working right before the update, I took a nap came back had an update, and did the update, went to live stream and gphoto2 could detect my camera, I took a picture with the camera manually, tried to import with digikam, digikam failed to connect, tried to use camera with entangle, which reported no camera attached, lsusb saw my camera clearly lsusb Bus 003 Device 006: ID 04b0:043f Nikon Corp. D5600 the only thing that changed was the above update/upgrade and now I am unable to do what I normally do, and well this bug stinks.

Okay, so looking again at the diff from 249.11-0ubuntu3.9 to 249.11-0ubuntu3.10[1], the only udev change is a new symlink for nvme devices. It seems very unlikely that this is related. The only other change that would be suspicious to me is the systemd.postinst change, i.e. requesting a reboot for this upgrade (because of bug 2013543), and not re-execing systemd.

Since no one has indicated otherwise, can you please tell us if this bug persists after (a) sudo systemctl daemon-reexec, and/or (b) reboot?

I have not yet looked into the details of the packages you are trying to use, so I am not sure if the above will help, but it will be very quick to test.

[1] http://launchpadlibrarian.net/683070059/systemd_249.11-0ubuntu3.9_249.11-0ubuntu3.10.diff.gz

Rebooting does nothing, same issue. systemctl daemon-reexec does nothing, same issue no one can talk to my camera, I tried a different camera same issue, lsusb cameras show up just fine so usb's are working, but something happens with that update that caused a roadblock between usb and other software packages.

YES this bug persists after (a) sudo systemctl daemon-reexec, and/or (b) reboot

Here is some backtrace of digikam crashing after trying to import photos from camera,
Application: digiKam (digikam), signal: Segmentation fault

[KCrash Handler]
#4 __strlen_avx2 () at ../sysdeps/x86_64/multiarch/strlen-avx2.S:74
#5 0x00007f50de2a8603 in __GI___strdup (s=0x0) at ./string/strdup.c:41
#6 0x00007f50e1c66820 in gp_port_set_info (port=0x7f4fc0001c00, info=info@entry=0x7f4fd37ec860) at gphoto2-port.c:146
#7 0x00007f50e0f8323d in gp_camera_set_port_info (camera=0x7f4fc0004760, info=0x7f4fd37ec860) at gphoto2-camera.c:421
#8 0x00007f50e196ae23 in () at /usr/lib/digikam/libdigikamgui.so.8.1.0
#9 0x00007f50e195f921 in Digikam::CameraController::executeCommand(Digikam::CameraCommand*) () at /usr/lib/digikam/libdigikamgui.so.8.1.0
#10 0x00007f50e1963164 in Digikam::CameraController::run() () at /usr/lib/digikam/libdigikamgui.so.8.1.0
#11 0x00007f50deaccca1 in () at /lib/x86_64-linux-gnu/libQt5Core.so.5
#12 0x00007f50de294b43 in start_thread (arg=<optimized out>) at ./nptl/pthread_create.c:442
#13 0x00007f50de326a00 in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:81

Thread 29 (Thread 0x7f4fd27fc640 (LWP 282576) "ThreadPoolSingl"):
#1 __futex_abstimed_wait_common (cancel=true, private=0, abstime=0x0, clockid=0, expected=0, futex_word=0x7f4fd27ea988) at ./nptl/futex-internal.c:87
#2 __GI___futex_abstimed_wait_cancelable64 (futex_word=futex_word@entry=0x7f4fd27ea988, expected=expected@entry=0, clockid=clockid@entry=0, abstime=abstime@entry=0x0, private=private@entry=0) at ./nptl/futex-internal.c:139
#3 0x00007f50de293ac1 in __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x7f4fd27ea938, cond=0x7f4fd27ea960) at ./nptl/pthread_cond_wait.c:503
#4 ___pthread_cond_wait (cond=0x7f4fd27ea960, mutex=0x7f4fd27ea938) at ./nptl/pthread_cond_wait.c:627
#5 0x00007f50d356a67b in () at /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#6 0x00007f4fd27ea860 in ()
#7 0x00007f4fd27ea8c0 in ()
#8 0x00007f50d7f17d70 in () at /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#9 0x000055b28184abe0 in ()
#10 0x0000000000000000 in ()

Thread 28 (Thread 0x7f4fd17fa640 (LWP 282575) "MemoryInfra"):
#1 __futex_abstimed_wait_common (cancel=true, private=0, abstime=0x0, clockid=0, expected=0, futex_word=0x7f4fd17e8878) at ./nptl/futex-internal.c:87
#2 __GI___futex_abstimed_wait_cancelable64 (futex_word=futex_word@entry=0x7f4fd17e8878, expected=expected@entry=0, clockid=clockid@entry=0, abstime=abstime@entry=0x0, private=private@entry=0) at ./nptl/futex-internal.c:139
#3 0x00007f50de293ac1 in __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x7f4fd17e8828, cond=0x7f4fd17e8850) at ./nptl/pthread_cond_wait.c:503
#4 ___pthread_cond_wait (cond=0x7f4fd17e8850, mutex=0x7f4fd17e8828) at ./nptl/pthread_cond_wait.c:627
#5 0x00007f50d356a67b in () at /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#6 0x0000000000000000 in ()

Thread 27 (Thread 0x7f4ff17fa640 (LWP 282551) "ThreadPoolSingl"):
#1 __futex_abstimed_wait_common (cancel=true, private=0, abstime=0x0, clockid=0, expected=0, futex_word=0x7f4ff17e8988) at ./nptl/futex-internal.c:87
#2 __GI___futex_abstimed_wait_cancelable64 (futex_word=futex_word@entry=0x7f4ff17e8988,...

The backtrace unfortunately doesn't provide any information that points to how this could be a systemd problem. The crashing thread appears to be:

Thread 12 (Thread 0x7f50a9f2e640 (LWP 282533) "ThreadPoolServi"):
#1 0x00007f50de277845 in buffered_vfprintf (s=0x7f50de41a6a0 <_IO_2_1_stderr_>, format=format@entry=0x7f50c74e8c85 "[%s] %s\n", args=args@entry=0x7f50a9f1c1e0, mode_flags=mode_flags@entry=2) at ./stdio-common/vfprintf-internal.c:2265
#2 0x00007f50de2766de in __vfprintf_internal (s=<optimized out>, format=0x7f50c74e8c85 "[%s] %s\n", ap=ap@entry=0x7f50a9f1c1e0, mode_flags=2) at ./stdio-common/vfprintf-internal.c:1236
#3 0x00007f50de334ec3 in ___fprintf_chk (fp=<optimized out>, flag=<optimized out>, format=<optimized out>) at ./debug/fprintf_chk.c:33
#4 0x00007f50c74cd37e in event_logv_ () at /lib/x86_64-linux-gnu/libevent-2.1.so.7
#5 0x00007f50c74cd549 in event_warn () at /lib/x86_64-linux-gnu/libevent-2.1.so.7
#6 0x00007f50c74d223c in () at /lib/x86_64-linux-gnu/libevent-2.1.so.7
#7 0x00007f50c74c95d1 in event_base_loop () at /lib/x86_64-linux-gnu/libevent-2.1.so.7
#8 0x00007f50d357c624 in () at /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5

since we don't see the format string arguments, this doesn't tell us what's being printed that's a problem or how it could be systemd-related.

I'm attaching the /lib/udev/rules.d/60-persistent-storage.rules from the previous version of systemd, 249.11-0ubuntu3.9. Since this is the only change in the new version affecting udev, even though we don't see how it would break your devices, we should test whether reverting this fixes your problem.

Please download the attached file and run the following commands:

sudo cp -a /lib/udev/rules.d/60-persistent-storage.rules{,.bak}
sudo mv 60-persistent-storage.rules /lib/udev/rules.d/60-persistent-storage.rules

Then reboot and report whether this has fixed your problem.

If it has not, we can walk you through a full manual rollback of the systemd package on your system.

I downloaded your rules and used you commands to move it, I rebooted and same issue, here is the result of gphoto2 --debug

gphoto2 --debug
0.000101 main (2): ALWAYS INCLUDE THE FOLLOWING LINES WHEN SENDING DEBUG MESSAGES TO THE MAILING LIST:
0.000114 main (2): gphoto2 2.5.27
0.000127 main (2): gphoto2 has been compiled with the following options:
0.000129 main (2): + gcc (C compiler used)
0.000131 main (2): + popt (mandatory, for handling command-line parameters)
0.000132 main (2): + exif (for displaying EXIF information)
0.000134 main (2): + cdk (for accessing configuration options)
0.000137 main (2): + aa (for displaying live previews)
0.000140 main (2): + jpeg (for displaying live previews in JPEG format)
0.000153 main (2): + readline (for easy navigation in the shell)
0.000157 main (2): libgphoto2 2.5.31
0.000160 main (2): libgphoto2 has been compiled with the following options:
0.000163 main (2): + standard camlib set SKIPPING SOME (ax203 canon digigr8 dimagev directory jl2005a jl2005c kodak_dc240 mars pentax ptp2 ricoh_g3 sierra sonix sq905 st2205 topfield tp6801 SKIPPING docupen lumix)
0.000166 main (2): + gcc (C compiler used)
0.000168 main (2): + no ltdl (for portable loading of camlibs)
0.000171 main (2): + EXIF (for special handling of EXIF files)
0.000175 main (2): libgphoto2_port 0.12.2
0.000177 main (2): libgphoto2_port has been compiled with the following options:
0.000179 main (2): + iolibs: disk ptpip serial
0.000181 main (2): + gcc (C compiler used)
0.000183 main (2): + no ltdl (for portable loading of iolibs)
0.000185 main (2): + EXIF (for vusb)
0.000187 main (2): + no USB (for USB cameras)
0.000188 main (2): + serial (for serial cameras)
0.000190 main (2): + no resmgr (serial port access and locking)
0.000192 main (2): + no ttylock (serial port locking)
0.000195 main (2): + no lockdev (serial port locking)
0.000197 main (2): CAMLIBS env var not set, using compile-time default instead
0.000199 main (2): IOLIBS env var not set, using compile-time default instead
0.000201 main (2): invoked with following arguments:
0.000203 main (2): --debug
0.000212 load_settings (2): Creating gphoto config directory ('/home/pasjrwoctx/.gphoto')
0.000248 load_settings (2): Loading settings from file '/home/pasjrwoctx/.gphoto/settings'.
0.000309 gp_camera_free (2): Freeing camera...
0.000312 gp_port_free (2): Freeing port...
0.000325 gp_filesystem_reset (2):...

In order to roll back udev in Synaptic, I get
To Be Removed
libgstreamer-plugins-base1.0-dev
libgudev-1.0-dev
libnm0:i386
libpipewire-0.3-0:i386
libpipewire-0.3-modules:i386
libspa-0.2-modules:i386
libudev-dev
libudev1:i386
pipewire:i386
steam:i386
To be downgraded
libudev1

I cant roll back or lose functionality and software. Im not sure how all this works together, but that update really messed things up, and I am no Programmer or Engineer, but normally I can with a little bit of digging, figure things out, but this has me very confused, as none of this should be tied together, and the bug has to do with how udev handles protocols for camera to software, because the computer can in fact see the camera when attached, the software is simply blocked from seeing the camera. USB harddrive not affected, I tried to reprogram my hand held Ham radio via usb, worked fine, it simply between what ever protocols ubuntu, udev and software packages use to see and communicate with cameras. And as a digital creator, this is a huge issue for me. If I do a fresh install I lose another 2 days getting everything back up running, not to mention I dont have extra drives right now for backing up, nor the funds to buy one, also the reason I have yet to, is if I do, and go to update, and this all happens again, then I am further behind. So I am trying to figure out how this update broke my system, and fix it so it is right.

Tried to stream with debug,
gphoto2 --stdout --capture-movie --debug | ffmpeg -i - -vcodec rawvideo -pix_fmt yuv420p -threads 0 -f v4l2 /dev/video0
0.000107 main (2): ALWAYS INCLUDE THE FOLLOWING LINES WHEN SENDING DEBUG MESSAGES TO THE MAILING LIST:
0.000131 main (2): gphoto2 2.5.27
0.000137 main (2): gphoto2 has been compiled with the following options:
0.000145 main (2): + gcc (C compiler used)
0.000148 main (2): + popt (mandatory, for handling command-line parameters)
0.000151 main (2): + exif (for displaying EXIF information)
0.000154 main (2): + cdk (for accessing configuration options)
0.000157 main (2): + aa (for displaying live previews)
0.000161 main (2): + jpeg (for displaying live previews in JPEG format)
0.000164 main (2): + readline (for easy navigation in the shell)
0.000172 main (2): libgphoto2 2.5.31
0.000175 main (2): libgphoto2 has been compiled with the following options:
0.000180 main (2): + standard camlib set SKIPPING SOME (ax203 canon digigr8 dimagev directory jl2005a jl2005c kodak_dc240 mars pentax ptp2 ricoh_g3 sierra sonix sq905 st2205 topfield tp6801 SKIPPING docupen lumix)
0.000184 main (2): + gcc (C compiler used)
0.000187 main (2): + no ltdl (for portable loading of camlibs)
0.000190 main (2): + EXIF (for special handling of EXIF files)
0.000196 main (2): libgphoto2_port 0.12.2
0.000200 main (2): libgphoto2_port has been compiled with the following options:
0.000203 main (2): + iolibs: disk ptpip serial
0.000206 main (2): + gcc (C compiler used)
0.000211 main (2): + no ltdl (for portable loading of iolibs)
0.000214 main (2): + EXIF (for vusb)
0.000217 main (2): + no USB (for USB cameras)
0.000221 main (2): + serial (for serial cameras)
0.000224 main (2): + no resmgr (serial port access and locking)
0.000227 main (2): + no ttylock (serial port locking)
0.000230 main (2): + no lockdev (serial port locking)
0.000235 main (2): CAMLIBS env var not set, using compile-time default instead
0.000238 main (2): IOLIBS env var not set, using compile-time default instead
0.000242 main (2): invoked with following arguments:
0.000245 main (2): --stdout
0.000248 main (2): --capture-movie
0.000252 main (2): --debug
0.000268 load_settings (2): Creating gphoto config directory ('/home/pasjrwoctx/.gphoto')
0.000306 load_settings (2): Loading settings from file '/home/pasjrwoctx/.gphoto/settings'.
0.000341 main ...

Dont know if this helps, but here is a complete list of installed

libnova-0.16-0 install
libgpg-error-l10n install
dpkg install
kerneloops install
libkf5quickaddons5 install
golang-golang-x-term-dev install
fontconfig:i386 install
r-cran-quantreg install
libkdecorations2-5v5 install
libvulkan1 install
libvulkan1:i386 install
telnet install
libgdal30 install
libkf5alarmcalendar5abi2 install
r-cran-evd install
signon-ui-service install
libdleyna-core-1.0-5 install
libnetfilter-conntrack3 install
php-composer-metadata-minifier install
python3-incremental install
libkf5wallet-data install
megapixels install
libqt5webengine-data install
php-symfony-config install
libkf5konq6 install
breeze install
libkf5mailtransportakonadi5 install
lsb-release install
libtext-unidecode-perl install
clamav-daemon install
libpulse-java install
puredata-import install
libpipewire-0.3-dev install
libevent-pthreads-2.1-7 install
plasma-runners-addons install
r-cran-fnn install
r-cran-mlmetrics install
clamav-milter install
gconf2-common install
fonts-cantarell install
r-cran-fts install
libgucharmap-2-90-7 install
python3-pyxattr install
libsphinxbase3 install
librust-syn+printing-dev install
libkf5identitymanagement5abi1 install
python3-parso install
libklu1 install
libkf5kdelibs4support5-bin install
cervisia install
libjs-prettify install
r-cran-jquerylib install
libssh2-1 install
libcuda1-340 install
libsub-exporter-perl install
fonts-sil-andika install
libsynctex2 install
tcpdump install
libperl5.34 install
node-highlight.js install
libokular5core10 install
fonts-tlwg-purisa-ttf install
fonts-tibetan-machine install
vlc-plugin-qt install
libsimage-dev install
tracker install
libopenblas0 install
openjdk-11-jre install
xserver-xorg-video-nouveau install
libblkid-dev install
dmidecode install
r-cran-gsl install
libspa-0.2-dev install
libel-api-java install
r-cran-spatstat.sparse install
libcups2 install
jalv install
libpoppler-qt5-1 install
libneon27-gnutls install
libkf5dav-data install
lintian install
gnustep-back0.29 install
qttranslations5-l10n install
pkg-kde-tools install
libxcb-present0 install
libxcb-present0:i386 install
libvlc5 install
libxapian30 install
libwrap0 install
python3-jedi install
r-cran-hms install
dvipng install
fonts-kacst-one install
python3-appdirs install
libcanberra-gtk3-0 install
reiserfsprogs install
libkf5kipi32.0.0 install
node-acorn install
libkeyutils1 install
libkeyutils1:i386 install
libmrpt-common-dev install
libkf5mailimporterakonadi5 install
python3-pycparser install
python3-blinker install
lsp-plugins-lv2 install
gstreamer1.0-qt5 install
qtchooser install
debhelper install
ruby-sdbm install
libkf5widgetsaddons5 install
kwave install
qtspeech5-flite-plugin install
libyajl2 install
libhtml-treebuilder-xpath-perl install
python3-pyclamd install
libhtml-treebuilder-libxml-perl install
libselinux1-dev install
r-cran-ini install
chafa install
libxtables12 install
libkpimimportwizard5 install
libcurl4 install
fonts-jura install
libpolkit-agent-1-0 install
dv4l install
libupower-glib3 install
libxml-namespac...

More interesting info, so I just tested digiKam-8.1.0-x86-64.appimage and it Can talk to my camera, but the Installed digikam package CAN NOT TALK, but I still can not use gphoto2 to stream my camera, nor can I use entangle to use my camera tethered. Because they can not talk to the camera, I understand the appimage has everything self contained, so it makes sense it works that way. But I wanted to let you know, as somehow it may be useful to figuring out this very odd bug.

Please install the attached apt preferences file to /etc/apt/preferences.d/ (as root) and then run 'sudo apt update && sudo apt upgrade'.

This should offer to downgrade all binary packages from the systemd source package to the current jammy-updates versions, without removing any other packages.

After doing so, you can run 'sudo rm /etc/apt/preferences.d/systemd-downgrade /lib/udev/rules.d/60-persistent-storage.rules.bak'.

Then reboot and let us know whether the problem with digikam, gphoto2, et al persists.

A shorter version that avoids the preferences file is:

sudo apt update && sudo apt install --no-remove '?installed?source-package(^systemd$)/jammy-updates'

Unless something else depends on a newer systemd in which case both don't work, but essentially this should.

PROBLEM STILL PERSISTS, and Now I HAVE NO AUDIO. No I have to do a fresh install. You guys really need to pay better attention to your updates, this is a system break not an upgrade. Im really not happy, and as I love ubuntu, and I really appreciate all the hard work you guys all put into making and keeping it great, sometimes I wish you took just a few extra minuets to verify nothing will break with your new updates. It sure would saved all of us a bunch of work. Now back to re-installing ubuntu and putting it all back together, hoping your update does not break it again.

On Thu, Sep 14, 2023 at 07:52:49PM -0000, Philip A Swiderski Jr wrote:
> PROBLEM STILL PERSISTS, and Now I HAVE NO AUDIO.

You didn't show the output of the apt command or otherwise confirm, but I
did stipulate that:

> This should offer to downgrade all binary packages from the systemd source
> package to the current jammy-updates versions, without removing any other
> packages.

If other packages were removed, but you proceeded with the downgrade, then
there could understandably be other regressions.

If no other packages were removed, but systemd was downgraded to the
249.11-0ubuntu3.9 version that you had installed before the most recent
stable release update, and you are having these problems, then there is no
evidence to indicate these problems are caused by either the downgrade, OR
the upgrade of systemd.

> Because they can not talk to the camera, I understand the appimage has
> everything self contained, so it makes sense it works that way.

No, that doesn't make sense, because the only point at which any of these
applications, either as appimage or deb, should be interacting with anything
handled by systemd, is when opening the device file and either succeeding
or getting permission denied. This is a question of udev acls, which should
apply equally to the appimage and the native .deb, unless the appimage runs
as a different user with different privileges. (And if it runs with
different privileges, whatever is setting up those "different privileges"
could be the actual source of your bug.)

My next step for debugging this problem would be to run 'strace -efile
digikam 2>&1 | grep /dev.*EPERM' to confirm whether there is a permissions
problem on your device files.

> Now back to re-installing
> ubuntu and putting it all back together, hoping your update does not
> break it again.

Yours is the only bug report of problems with this SRU and it so far has not
been reproducible. If we continue to be unable to reproduce it and you are
not able to assist with further debugging to isolate the problem on your
system, then this bug will eventually be closed and the update will be
re-published to jammy-updates.

> pipewire:i386

This explains the loss of audio after downgrade.

Unfortunately the semantics of package pins do not match on foreign-arch
packages without explicitly listing the arch name.

And for some reason, you had pipewire installed on your system for the wrong
architecture.

Julian's apt commandline approach appears to avoid this problem.

But you appear to have committed the results of either the pin-based
downgrade or a synaptic downgrade, without paying attention to the caveat
that it should not remove any packages.

So 'apt install pipewire' (NOT pipewire:i386) should have fixed the audio
regression.

It's still the case that, if the camera problem was still visible after
downgrading all of the binaries that were part of the systemd source
package, there is nothing that points to the camera behavior change being
the result of the systemd update.

Tried all your steps, they kept breaking my system more and more. Had to re-install ubutnu from liveusb, installed synaptic downgraded udev and locked verison, read markings, reboot, update, upgrade reboot, get my audio and bluetooth up and working again reboot, everything works, its your udev update, dont know how, dont know why, and not sure how my system is the only one effected, but its your udev update. Thanks for your help, hope you figure it out before it causes more issues wide spread. Im out for now on this bug. As fresh install and down grade udev and locking version has everything working again.

To reproduce your problem, can you specify steps to reproduce (with version numbers)? Which Ubuntu image did you use for installation? To which udev version did you downgrade? Which camera do you have and how did you connect it to your computer?

22.04.3LTS -Ubuntu
Downgrade: udev:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.7), libudev1:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.7)
 Camera any kind, I tried both my NikonD5600 and Olympus OM-D E-M5, which both work again as they should and did before this mess started.

Your original bug report was about an upgrade from 249.11-0ubuntu3.9 (the previous SRU version we've now rolled back to) to 249.11-0ubuntu3.10 (the withdrawn SRU which is currently in jammy-proposed).

> Downgrade: udev:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.7), libudev1:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.7)

This shows that after reinstall, you installed the -0ubuntu3.9 version that you reported you already had installed before encountering this bug; and then downgraded to -0ubuntu3.7, the version in jammy-security.

If you are saying that, after upgrading to -0ubuntu3.9, the problem with camera devices was still reproducible for you, then it is definitively not caused by any of the changes in -0ubuntu3.10.

I will therefore be re-releasing the -0ubuntu3.10 SRU.

We are still more than willing to assist you in determining the cause of the problems you're experiencing, but the evidence is not there that this is caused by the latest SRU.

I downgraded to 249.11-0ubuntu3.9, 249.11-0ubuntu3.7 Because I know for a Fact I had no issues with it, My last install was working with 249.11-0ubuntu3.9, you rolled out the update to 249.11-0ubuntu3.10 and that is when all this started. I simply went back to an older version after a fresh install to be safe, one computer and already lost 2 days on it, could not afford to try out 249.11-0ubuntu3.9 again and hope it all worked, I also know for a fact it Broke on 249.11-0ubuntu3.10. Again I am no programmer or software engineer, so you do what you feel is best for the code, I know what broke, when it broke, but I will never know why it broke. Close this bug out if your comfortable with rolling out 249.11-0ubuntu3.10.

I tried to reproduce the failure on a fresh Ubuntu 22.04 installation and was able to reproduce it (see bug #2036244 for it), but I saw this behavior regardless of the used systemd/udev version. I tried different kernel version, but I failed to pin down a set of packages where it worked reliable.

I changed my Sony Alpha 9 into PC control mode and successfully tested entangle (I could take photos there).