Rolf Leggewie, first, please again stop being rude by calling me a bot. As you have signed the Ubuntu Code of Conduct, and as a Ubuntu community member representing Ubuntu Bug Control, you have attested to be someone who is respectful, and considerate. However, calling me a bot, unreasonable, etc. does align with this at all. As well, incessantly claiming the kernel team doesn't deal with tickets is in direct contradiction to all the bugs fixed in linux (Ubuntu). At your convenience, please review the 7000+ bugs fixed there -> https://bugs.launchpad.net/ubuntu/+source/linux/+bugs?field.searchtext=&orderby=-importance&field.status%3Alist=FIXRELEASED&assignee_option=any&field.assignee=&field.bug_reporter=&field.bug_commenter=&field.subscriber=&field.tag=&field.tags_combinator=ANY&field .status_upstream-empty- marker=1&field.upstream_target=&field.has_cve.used=&field.omit_dupes.used=&field.omit_dupes=on&field.affects_me.used=&field.has_patch.used=&field.has_branches.used=&field.has_branches=on&field.has_no_branches.used=&field.has_no_branches=on&field.has_blueprints.used=&field.has_blueprints=on&field.has_no_blueprints.used=&field.has_no_blueprints=on&search=Search .
Despite this, regarding the article you quoted, I've followed it to get my bugs resolved, have steered others who have a non-buggy BIOS to it, and if you would care to check the changelog, contributed to it. These were the reasons I asked Teo for a BIOS update. As well, could you also please provide a technical detail on how you are confirming this bug when you don't have the same hardware, and you can't reproduce this issue in the same release as the original reporter? Also, how would mis-tasking this into Unity be helpful to getting a fix released in linux, or have linux developers look at it? Given how you said you aren't claiming this is a bug in Unity, but your actions are contradicting this by assigning this solely to the Unity package, unless you have a sound technical reason, or procedure advised to you as a member of Ubuntu Bug Control, could you please re-assign this back to linux (Ubuntu) given this would be the appropriate place for a fix to land as applicable? Thank you for your time and consideration in this matter, and I look forward to your response. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1353129 Title: [REGRESSION 2014-08] Volume up/down keys, and printScreen key, have stopped working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1353129/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
