Control: reassign -1 src:linux
Control: severity -1 wishlist
Control: tag -1 upstream
On Tue, 2019-01-08 at 14:27 +0100, Michael Biebl wrote:
[...]
> I thus don't see a problem in udev's way of loading the modules.
>
> Ben, can you elaborate why you reassigned this to udev?
> Maybe I'm missing
Processing control commands:
> reassign -1 src:linux
Bug #918142 [udev] linux-image-4.19.0-1-amd64: Can no longer disable the
touchscreen module
Bug reassigned from package 'udev' to 'src:linux'.
Ignoring request to alter found versions of bug #918142 to the same values
previously set
Ignoring
Processing control commands:
> tag -1 pending
Bug #917633 [udev] udisk2 post-installation fails in chrooted environments
Added tag(s) pending.
--
917633: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917633
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processing commands for cont...@bugs.debian.org:
> reassign 917633 udev
Bug #917633 [udisks2] udisk2 post-installation fails in chrooted environments
Bug reassigned from package 'udisks2' to 'udev'.
No longer marked as found in versions udisks2/2.8.1-3.
Ignoring request to alter fixed versions of
Am 08.01.19 um 18:11 schrieb Isaac Gelado:
> As a side hint that might be helpful. I had two kernels 4.18 and 4.19
> in my system. This problem started when I first boot 4.19, while I was
> able to boot 4.18 without problems. At some point I decided to do an
> `update-initramfs -k all -u` and the
On Tue, Jan 8, 2019 at 8:38 AM Michael Biebl wrote:
>
> Am 08.01.19 um 16:43 schrieb Isaac Gelado:
> > Adding sleep 1 does not work. I also check that the -v flag is only
> > needed in one of the calls to udevadm.
>
> Urgh, this is getting really weird.
> -v should not affect the behaviour of
Am 08.01.19 um 17:38 schrieb Michael Biebl:
> Am 08.01.19 um 16:43 schrieb Isaac Gelado:
>> Adding sleep 1 does not work. I also check that the -v flag is only
>> needed in one of the calls to udevadm.
>
> Urgh, this is getting really weird.
> -v should not affect the behaviour of udevadm, but
Adding sleep 1 does not work. I also check that the -v flag is only needed
in one of the calls to udevadm.
On Tue, Jan 8, 2019 at 6:35 AM Michael Biebl wrote:
> On Mon, 7 Jan 2019 12:27:10 -0800 Isaac Gelado wrote:
> > I am having this very same issue. If I run
> >
> > udevadm trigger
On Mon, 7 Jan 2019 12:27:10 -0800 Isaac Gelado wrote:
> I am having this very same issue. If I run
>
> udevadm trigger --type=subsystems --action=add
> udevadm trigger --type=devices --action=add
>
> in the initramdfs shell, it does nothing at all. However, if I run
>
> udevadm trigger
Am 08.01.19 um 14:38 schrieb fakefur:
> hi again
>
> sorry i did not reassign it to udev - the kernel people did
My question was targeted at Ben Hutchings, our kernel maintainer.
--
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?
hi again
sorry i did not reassign it to udev - the kernel people did
i disable hid_multitouch but it is still enabled unless i disable
usbhid - this is the problem i'm having
"modprobe -r hid_multitouch" DOES NOT disable the touch screen
only "modprobe -r usbhid" disables it, but also disables
Am 08.01.19 um 13:37 schrieb Dmitry Bogatov:
>
> control: tags -1 +moreinfo
>
> Seems old discussion did not ended in solution. Let us try again.
>
> Dear udev maintainers, did anything changed? Are there still problems
> running /etc/init.d/udev from runlevel 1 (when udev daemon was killed)
>
Am 08.01.19 um 14:19 schrieb fakefur:
> as requested
> thanks
>
>
> lauren@THINKY:~$ lsmod | grep hid_multitouch
Ok, so the module is not loaded.
> lauren@THINKY:~$ grep hid_multitouch /etc/modprobe.d/*
> /etc/modprobe.d/blacklist.conf:blacklist hid_multitouch
>
> lauren@THINKY:~$ lsinitramfs
control: tags -1 +moreinfo
Seems old discussion did not ended in solution. Let us try again.
Dear udev maintainers, did anything changed? Are there still problems
running /etc/init.d/udev from runlevel 1 (when udev daemon was killed)
manually by sysadmin to restart it?
[2010-06-05 09:05]
Am 08.01.19 um 12:53 schrieb Vincent Lefevre:
> On 2019-01-06 12:30:04 +, Jakub Sokołowski wrote:
>> On Sun, 6 Jan 2019 08:33:09 +0100 ludszuweit1
>> wrote:
>>> Is it possible, that dev 240-2 have problems to boot with m2 connected
>>> SSDs?
>>
>> I don't use m2(though I do have it). I'm
On Fri, 04 Jan 2019 10:19:06 +0100 fakefur wrote:
> makes no difference
> i cannot disable the touchscreen
>
By "cannot disable the touchscreen", I assume you mean that the
hid_multitouch kernel module is loaded?
What's the output of
# lsmod | grep hid_multitouch
# grep hid_multitouch
On Tue, 18 Dec 2018 12:20:06 +0100 Michael Biebl wrote:
> Am 18.12.2018 um 12:09 schrieb Raphael Manfredi:
> > Quoting Michael Biebl:
> > : What happens if you boot into emergency mode (add emergency to the
> > : kernel command line)?
> > : This will start a very minimal system without any
Processing control commands:
> forwarded -1 https://github.com/systemd/systemd/issues/11272
Bug #918658 [systemd] [networkd] crash on resume in 240
Set Bug forwarded-to-address to
'https://github.com/systemd/systemd/issues/11272'.
> tags -1 + fixed-upstream patch
Bug #918658 [systemd] [networkd]
18 matches
Mail list logo
