> Is the problem reproducible after the reboot or only directly after the
> upgrade?
Actually, everything was working fine after upgrade until reboot (I did
reboot one day after upgrade). After reboot, the problem became visible
(and it was not solved by many other reboots).
--
Peter
Processing commands for cont...@bugs.debian.org:
> tags 944860 - moreinfo unreproducible
Bug #944860 [udev] udevadm trigger fails in containers with ro /sys
Removed tag(s) moreinfo and unreproducible.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
944860:
Processing control commands:
> retitle -1 udevadm trigger fails in containers with ro /sys
Bug #944860 [udev] udevadm trigger fails in chroot
Changed Bug title to 'udevadm trigger fails in containers with ro /sys' from
'udevadm trigger fails in chroot'.
--
944860:
Control: retitle -1 udevadm trigger fails in containers with ro /sys
Am 17.11.19 um 02:43 schrieb Michael Biebl:
> Am 17.11.19 um 01:57 schrieb Jonah Brüchert:
>> After slightly looking into the debos source code it seems also possible
>> that it uses a systemd-spawn container in some cases
>>
Am 17.11.19 um 01:57 schrieb Jonah Brüchert:
> After slightly looking into the debos source code it seems also possible
> that it uses a systemd-spawn container in some cases
> (https://github.com/go-debos/debos/blob/2764eed783b1b0ffb5d09f796338f09a4e2594b6/commands.go#L15)
Can you please verify,
Am 17.11.19 um 01:57 schrieb Jonah Brüchert:
> Thanks for looking into the issue.
>
>> Can you be more specific how you setup your chroot so we have a chance
>> to reproduce the problem?
[..]
I guess you'll need to break that down to a more minimal test case for
me being able to reproduce the
Thanks for looking into the issue.
Can you be more specific how you setup your chroot so we have a chance
to reproduce the problem?
The exact setup is a little more complicated.
The chroot is created using debos, which if I remember correctly uses a
chroot inside qemu if that's relevent.
For everyone affected by this issue, can you please answer this question:
Did you reboot after the upgrade?
Is the problem reproducible after the reboot or only directly after the
upgrade?
signature.asc
Description: OpenPGP digital signature
Control: tags -1 moreinfo unreproducible
Am 16.11.19 um 16:05 schrieb Jonah Brüchert:
> Package: udev
> Version: 243-5
> Severity: normal
>
> Dear Maintainer,
>
> When running udevadm trigger in a chroot, in this case using debos, it fails
> to write changes to /sys and exits with an error
Processing control commands:
> tags -1 moreinfo unreproducible
Bug #944860 [udev] udevadm trigger fails in chroot
Added tag(s) unreproducible and moreinfo.
--
944860: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=944860
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Out of curiosity, I tried to downgrade udev back to 243-5 and I am not
able to reproduce the issue anymore. It looks that the upgrade to 243-7
is not so important.
--
Peter
> On one machine (the AMDGPU one) `libinput debug-events --verbose`
would complain about certain devices not being initialised by udev,
including the keyboard device. Upgrading udev from version 243-5 to
243-7 and reloading udev by running `udevadm control --reload-rules &&
udevadm trigger`
Processing control commands:
> affects -1 xorg
Bug #944675 [udev] udev: Keyboard and mouse not working in X.org with udev 243-5
Bug #944813 [udev] xserver-xorg-input-evdev: Keyboard and mouse don't work
after X started
Bug #944838 [udev] xorg: after recent upgrade on two different machines, X no
Processing control commands:
> affects -1 xorg
Bug #944838 [udev] xorg: after recent upgrade on two different machines, X no
longer responds to kbd or mouse input
Bug #944675 [udev] udev: Keyboard and mouse not working in X.org with udev 243-5
Bug #944813 [udev] xserver-xorg-input-evdev:
Control: affects -1 xorg
Control: severity -1 grave
Severity: grave
Justification: renders package unusable
Thanks, I also figured this out myself separately by running `libinput
debug-events`, hopefully this helps someone else stumbling upon this strange
behaviour in the future.
However I am
Control: reassign -1 udev 243-5
Control: forcemerge 944675 -1
I think this is a problem with the new udev in testing, please follow up
on bug #944675 if you have new information.
Am 15.11.2019 um 19:35 schrieb mad:
> Package: xserver-xorg-input-evdev
> Version: 1:2.10.6-1
> Severity: important
Processing control commands:
> reassign -1 udev 243-5
Bug #944838 [xorg] xorg: after recent upgrade on two different machines, X no
longer responds to kbd or mouse input
Bug reassigned from package 'xorg' to 'udev'.
No longer marked as found in versions xorg/1:7.7+20.
Ignoring request to alter
Control: reassign -1 udev 243-5
Control: forcemerge 944675 -1
On 2019-11-16 03:45 +, Ximin Luo wrote:
> Package: xorg
> Version: 1:7.7+20
> Severity: important
>
> Dear Maintainer,
>
> After upgrading a bunch of packages on two very different machines, X no
> longer
> responds to keyboard
Processing control commands:
> reassign -1 udev 243-5
Bug #944813 [xserver-xorg-input-evdev] xserver-xorg-input-evdev: Keyboard and
mouse don't work after X started
Bug reassigned from package 'xserver-xorg-input-evdev' to 'udev'.
No longer marked as found in versions
For me it worked just fine.
I've done it in this order:
. upgraded udev
. run the commands sugested bellow
. reboot
. everything is fine (in heaven)
Cheers,
Mensagem encaminhada
Assunto: Re: [systemd/systemd] Keyboard and mouse not working in X.org
with udev 243-5 (#14027)
20 matches
Mail list logo
