kernel-packages team mailing list archive

[teo1978 <teo8976@xxxxxxxxx>]

> Why do you think asking to upgrade your BIOS is rigid criteria?

Asking to upgrade the BIOS is fine.
Refusing to look into the issue unless the BIOS is updated is ridiculous. 

Updating the BIOS is a tremendously cumbersome (and risky) process for a
user whose main working OS is Ubuntu. Hence most users just won't do
that (I won't), which means the bug will expire. And in the vast
majority of cases, there won't be a good reason for that because (1)
it's extremely unlikely that the issue is caused _solely_ by a bug in
the bios; (2) even if updating the bios makes the issue disappear, it
doesn't mean that the issue is a bug in the bios; actually it may mean
that it is an issue in the software triggered by some peculiarity in the
bios that is not even a bug, in which case the issue SHOULD be
investigated with the bios that triggers it, in order to fix a bug
rather than make it invisible (and perhaps resurface later); (3) even in
the event that the bug is triggered by a bug in the bios, chances are
that the OS is not responding correctly to the incorrect behavior of the
bios, i.e. there could be a bug in the bios _and_ the OS, and finally
(4) I remember Ubuntu being announced as "linux for human beings" or
something like that: if you really want it to be that, you must assume
that there are a lot of machines out there with outdated bioses, and
some of their "human being" owners just won't ever update a bios (or
have an idea of what it is) until the day when a friendly popup appears
allowing them to do it as easily as installing software updates (let's
forget for a moment that even upgrading Ubuntu can brick a computer).
So, given that the vast majority of bios bugs can almost certainly be
worked around by the OS (just think of other OSes that work on machines
with the same outdated bios and don't exhibit the issue), the OS should
either do that or provide a really stright-forward way to update the
bios. The latter may (to some extent) be not in the OS developers' hands
; the former definitely is.


> That's me!
Yes, I guess, but I was referring more specifically to another contributor who has been accused of being rude.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1353129

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

Status in linux package in Ubuntu:
  Incomplete

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/linux/+bug/1353129/+subscriptions