https://bugs.kde.org/show_bug.cgi?id=387454
--- Comment #11 from Nille <nille_kun...@hotmail.com> ---
I got this in Slackware64-current(15.0) KDE4.14.XX
I read this thread and saw gentoo and slackware and it made me think that it
might be eudev related.
Is it so that all of us that has this problem use eudev?
There was weltqgel that used systemd but since it was fixed later it might not
have been the same problem it could as well have been the gvfs udev problem
that appeared almost the same time.
The error message, first is original in my native tongue and the second is
translated by me.
Filen eller katalogen
udi=/org/kde/solid/udev/sys/devices/pci0000:00/0000:00:10.0/usb3/3-2/ finns
inte.
File or catalog
udi=/org/kde/solid/udev/sys/devices/pci0000:00/0000:00:10.0/usb3/3-2/ doesn't
exist.
It does work for me in xfce if i use pcmanfm or in KDE if i use thunar to open
the mtp device.
I did try and bisect the kernel and got this result.
git bisect bad 1455cf8dbfd06aa7651dcfccbadb7a093944ca65 is the
first bad commit
commit 1455cf8dbfd06aa7651dcfccbadb7a093944ca65
Author: Dmitry Torokhov <dmitry.torok...@gmail.com>
Date: Wed Jul 19 17:24:30 2017 -0700
driver core: emit uevents when device is bound to a driver
There are certain touch controllers that may come up in either normal
(application) or boot mode, depending on whether firmware/configuration is
corrupted when they are powered on. In boot mode the kernel does not create
input device instance (because it does not necessarily know the
characteristics of the input device in question).
Another number of controllers does not store firmware in a non-volatile
memory, and they similarly need to have firmware loaded before input device
instance is created. There are also other types of devices with similar
behavior.
There is a desire to be able to trigger firmware loading via udev, but it
has to happen only when driver is bound to a physical device (i2c or spi).
These udev actions can not use ADD events, as those happen too early, so we
are introducing BIND and UNBIND events that are emitted at the right
moment.
Also, many drivers create additional driver-specific device attributes
when binding to the device, to provide userspace with additional controls.
The new events allow userspace to adjust these driver-specific attributes
without worrying that they are not there yet.
Signed-off-by: Dmitry Torokhov <dmitry.torok...@gmail.com>
Signed-off-by: Greg Kroah-Hartman <gre...@linuxfoundation.org>
:040000 040000 fef96678b0a5ea8f89c41f006a3ccd013b4a36f4
34b72074bd6fab60bea1ec8066cf5ae9c600b37c M drivers
:040000 040000 5657f6e76558ed4e14f17edabc6c602b93011d6d
1dbac2e41568c1638ea059fc8bc1afe8878353b8 M include
:040000 040000 88854205d5255fbec438594cb3539e01c3610f82
54ad1fcb19ca64af9660e170ae0d7af186bd51ad M lib
--
You are receiving this mail because:
You are watching all bug changes.
