Bug#908796: udev 240-2: failed to connect to udev daemon (on boot)

[js jb]

I've just tested udev_240-4 in my system and it seems to work fine: both mouse and sound devices are working properly on my systemthat tracks the testing distribution. This compares to udev_240-2 on the same system, which did not find the mouse nor the sound devices.

I'm surprised at the change between udev_240-2  and udev_240-4, since I thought the -4 refers only to the debian revision but it resultedin a significant change in the package's usability.
Note: it seems that now upgrading udev from within X windows brings down the X window session; I don't recall this happening before 240.
thanks,--jack


      From: Martin Pitt <mpitt at debian.org>
 To: js jb <em2jacks at yahoo.com>; 908796 at bugs.debian.org 
 Sent: Wednesday, January 16, 2019 2:11 AM
 Subject: Re: Bug#908796: udev 240-2: failed to connect to udev daemon (on boot)
   
Hello js jb,

js jb [2019-01-16  0:27 +0000]:
> Is 240-4 slated to get to the testing distribution soon?

If nothing unforeseen comes in between (like finding another RC bug that got
introduced into -3 or -4), it should enter testing in two days:

  https://tracker.debian.org/pkg/systemd → look at "excuses".

Martin


   
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20190121/06623ec1/attachment.html>