Oh, the script clearly shouldn't reference a non-existent path. The question is, what's the right way to fix it - by fixing the path, or by dropping the script?
We know that it's wrong - a kernel bug - if the script is needed at all. We also know that the last time the script was functional, it broke things for users on a number of models. What we don't know is how many users the LED is already working for, how many this change will fix it for, and how many it will break it for. Perhaps we should reassign this bug to the kernel, so the LED interaction can be fixed there? -- Asus Wireless button not updating WLED https://bugs.launchpad.net/bugs/451108 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
