https://bugs.kde.org/show_bug.cgi?id=387454
--- Comment #29 from Stefan Brüns <stefan.bru...@rwth-aachen.de> --- (In reply to Nate Graham from comment #28) > So whose responsibility is it for fixing this? Is this the kernel's problem > or ours? The kernel has a "never break userspace, even if userspace is broken" policy, so if brought to the attention of the kernel developers, there will likely be changes in the kernel. On the other hand, I don't think it is the best approach here - it may take weeks until a solution is found, if at all possible (improving handling of some devices *AND* not breaking userspace), and more weeks until it reaches distributions and users. The culprit is likely the missing handling of the "bind" action in solid/backends/shared/udev*.cpp (UdevQt) (which can likely be done by just emitting deviceChanged), *and* the missing handling of deviceChanged in solid/backends/devices/udev/udevmanager.cpp. The changes in UdevQt are trivial, but the changes in udevmanager are likely more evolved. -- You are receiving this mail because: You are watching all bug changes.
