dx-packages team mailing list archive

["Christopher M. Penalver" <christopher.m.penalver@xxxxxxxxx>]

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 DX
Packages, which is subscribed to unity in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1353129

Title:
  [REGRESSION 2014-08] Volume up/down keys, and printScreen key, have
  stopped working

Status in unity package in Ubuntu:
  Confirmed

Bug description:
  All of a sudden, the volume keys from the keyboard have stopped
  working.

  The volume control on the top right corner of the screen does work if
  used with the mouse.

  I have both an external usb keyboard with dedicated volume + and -
  keys, and the builtin laptop keyboard where the volume +/-keys are the
  combination of the Fn key plus the up/down arrows.

  All these used to work up to a few minutes ago. Now none of them works.
  I think they stopped working with the last reboot.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-32-generic 3.13.0-32.57
  ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
  Uname: Linux 3.13.0-32-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  AudioDevicesInUse:
   USER        PID ACCESS COMMAND
   /dev/snd/controlC0:  teo        2303 F.... pulseaudio
   /dev/snd/pcmC0D0p:   teo        2303 F...m pulseaudio
  CurrentDesktop: Unity
  Date: Tue Aug  5 23:13:35 2014
  HibernationDevice: RESUME=UUID=ff7e702a-a05a-47fd-8c14-551e81f9e9e3
  InstallationDate: Installed on 2013-10-11 (298 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MachineType: Acer Aspire V3-571G
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-32-generic.efi.signed root=UUID=5830b30e-69e8-4bb4-8a2b-bc2b43c7414a ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-32-generic N/A
   linux-backports-modules-3.13.0-32-generic  N/A
   linux-firmware                             1.127.5
  SourcePackage: linux
  UpgradeStatus: Upgraded to trusty on 2014-05-24 (73 days ago)
  dmi.bios.date: 10/15/2012
  dmi.bios.vendor: Acer
  dmi.bios.version: V2.07
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: VA50_HC_CR
  dmi.board.vendor: Acer
  dmi.board.version: Type2 - Board Version
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V2.07
  dmi.modalias: dmi:bvnAcer:bvrV2.07:bd10/15/2012:svnAcer:pnAspireV3-571G:pvrV2.07:rvnAcer:rnVA50_HC_CR:rvrType2-BoardVersion:cvnAcer:ct10:cvrV2.07:
  dmi.product.name: Aspire V3-571G
  dmi.product.version: V2.07
  dmi.sys.vendor: Acer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1353129/+subscriptions