[Kernel-packages] [Bug 1665530] Re: Brightness control keys not working on Gigabyte P57 laptop
** Attachment added: "acpi dump" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1665530/+attachment/4931898/+files/acpi_dump -- 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/1665530 Title: Brightness control keys not working on Gigabyte P57 laptop Status in linux package in Ubuntu: Confirmed Bug description: I have a gigabyte P57 laptop running Ubuntu 16.04 kernel 4.8.x. My brightness control keys (fn+F3, fn+F4) are not getting detected. After reading about how keypresses are handled by the Linux kernel, I used showkey to check the scancodes of these keys. I did not get any output. Similarly no output from xev, evtest and acpi_listen. Just for your reference, other keys like volume up (fn+F9) are working alright. --- ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 InstallationDate: Installed on 2016-12-14 (65 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia Package: linux (not installed) Tags: xenial Uname: Linux 4.8.0-040800-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1665530/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1665530] Re: Brightness control keys not working on Gigabyte P57 laptop
There is nothing logged in dmesg log. So I have attached kern log ** Attachment added: "kern.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1665530/+attachment/4931899/+files/kern.log -- 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/1665530 Title: Brightness control keys not working on Gigabyte P57 laptop Status in linux package in Ubuntu: Confirmed Bug description: I have a gigabyte P57 laptop running Ubuntu 16.04 kernel 4.8.x. My brightness control keys (fn+F3, fn+F4) are not getting detected. After reading about how keypresses are handled by the Linux kernel, I used showkey to check the scancodes of these keys. I did not get any output. Similarly no output from xev, evtest and acpi_listen. Just for your reference, other keys like volume up (fn+F9) are working alright. --- ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 InstallationDate: Installed on 2016-12-14 (65 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia Package: linux (not installed) Tags: xenial Uname: Linux 4.8.0-040800-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1665530/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1665530] [NEW] Brightness control keys not working on Gigabyte P57 laptop
Public bug reported: I have a gigabyte P57 laptop running Ubuntu 16.04 kernel 4.8.x. My brightness control keys (fn+F3, fn+F4) are not getting detected. After reading about how keypresses are handled by the Linux kernel, I used showkey to check the scancodes of these keys. I did not get any output. Similarly no output from xev, evtest and acpi_listen. Just for your reference, other keys like volume up (fn+F9) are working alright. ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- 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/1665530 Title: Brightness control keys not working on Gigabyte P57 laptop Status in linux package in Ubuntu: New Bug description: I have a gigabyte P57 laptop running Ubuntu 16.04 kernel 4.8.x. My brightness control keys (fn+F3, fn+F4) are not getting detected. After reading about how keypresses are handled by the Linux kernel, I used showkey to check the scancodes of these keys. I did not get any output. Similarly no output from xev, evtest and acpi_listen. Just for your reference, other keys like volume up (fn+F9) are working alright. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1665530/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1665530] Re: Brightness control keys not working on Gigabyte P57 laptop
apport information ** Tags added: apport-collected xenial ** Description changed: I have a gigabyte P57 laptop running Ubuntu 16.04 kernel 4.8.x. My brightness control keys (fn+F3, fn+F4) are not getting detected. After reading about how keypresses are handled by the Linux kernel, I used showkey to check the scancodes of these keys. I did not get any output. Similarly no output from xev, evtest and acpi_listen. - Just for your reference, other keys like volume up (fn+F9) are working - alright. + Just for your reference, other keys like volume up (fn+F9) are working alright. + --- + ApportVersion: 2.20.1-0ubuntu2.5 + Architecture: amd64 + CurrentDesktop: Unity + DistroRelease: Ubuntu 16.04 + InstallationDate: Installed on 2016-12-14 (65 days ago) + InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) + NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia + Package: linux (not installed) + Tags: xenial + Uname: Linux 4.8.0-040800-generic x86_64 + UnreportableReason: The running kernel is not an Ubuntu kernel + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo + _MarkForUpload: True ** Attachment added: "JournalErrors.txt" https://bugs.launchpad.net/bugs/1665530/+attachment/4820565/+files/JournalErrors.txt -- 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/1665530 Title: Brightness control keys not working on Gigabyte P57 laptop Status in linux package in Ubuntu: Confirmed Bug description: I have a gigabyte P57 laptop running Ubuntu 16.04 kernel 4.8.x. My brightness control keys (fn+F3, fn+F4) are not getting detected. After reading about how keypresses are handled by the Linux kernel, I used showkey to check the scancodes of these keys. I did not get any output. Similarly no output from xev, evtest and acpi_listen. Just for your reference, other keys like volume up (fn+F9) are working alright. --- ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 InstallationDate: Installed on 2016-12-14 (65 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia Package: linux (not installed) Tags: xenial Uname: Linux 4.8.0-040800-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1665530/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1665530] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1665530/+attachment/4820566/+files/ProcEnviron.txt ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- 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/1665530 Title: Brightness control keys not working on Gigabyte P57 laptop Status in linux package in Ubuntu: Confirmed Bug description: I have a gigabyte P57 laptop running Ubuntu 16.04 kernel 4.8.x. My brightness control keys (fn+F3, fn+F4) are not getting detected. After reading about how keypresses are handled by the Linux kernel, I used showkey to check the scancodes of these keys. I did not get any output. Similarly no output from xev, evtest and acpi_listen. Just for your reference, other keys like volume up (fn+F9) are working alright. --- ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 InstallationDate: Installed on 2016-12-14 (65 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia Package: linux (not installed) Tags: xenial Uname: Linux 4.8.0-040800-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1665530/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1264344] [NEW] Filename conflict when copying files - unexpected behaviour when trying to rename the target file
Public bug reported:
I use nautilus filemanger in my ubuntu box. When I copy and paste files
between folders, sometimes a dialog box pops up saying that the target
folder already contains a file with the same name asking me to choose
among a set of options on how to proceed. One of the options available
is to rename the target filename so that the file can be pasted to the
target folder. When I rename the file through this dialog, it does not
paste the file with the new name as expected. Instead it shows the name
conflict dialog again for the same file with the old name. When I try to
rename the file again with a different name, it accepts the command and
pastes the file.
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: linux-image-3.2.0-57-generic 3.2.0-57.87
ProcVersionSignature: Ubuntu 3.2.0-57.87-generic 3.2.52
Uname: Linux 3.2.0-57-generic x86_64
NonfreeKernelModules: fglrx
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
ApportVersion: 2.0.1-0ubuntu17.6
Architecture: amd64
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: PCH [HDA Intel PCH], device 0: STAC92xx Analog [STAC92xx Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: prasanna 2424 F pulseaudio
/dev/snd/pcmC0D0p: prasanna 2424 F...m pulseaudio
Card0.Amixer.info:
Card hw:0 'PCH'/'HDA Intel PCH at 0xc750 irq 56'
Mixer name : 'Intel CougarPoint HDMI'
Components : 'HDA:111d7605,103c1656,00100105
HDA:80862805,80860101,0010'
Controls : 26
Simple ctrls : 12
Date: Thu Dec 26 12:09:03 2013
HibernationDevice: RESUME=UUID=af25c2c3-daeb-4c20-ab5a-cd9142a49d7e
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64
(20120425)
MachineType: Hewlett-Packard HP Pavilion dv6 Notebook PC
MarkForUpload: True
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-57-generic
root=UUID=684493b8-0e0c-48e9-9c16-48bad55116c6 ro quiet splash
acpi_backlight=vendor vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-3.2.0-57-generic N/A
linux-backports-modules-3.2.0-57-generic N/A
linux-firmware1.79.9
SourcePackage: linux
StagingDrivers: rts_pstor mei
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/05/2011
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: F.1B
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: 1656
dmi.board.vendor: Hewlett-Packard
dmi.board.version: 10.31
dmi.chassis.asset.tag: Chassis Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.version: Chassis Version
dmi.modalias:
dmi:bvnHewlett-Packard:bvrF.1B:bd10/05/2011:svnHewlett-Packard:pnHPPaviliondv6NotebookPC:pvr058C11244720001620100:rvnHewlett-Packard:rn1656:rvr10.31:cvnHewlett-Packard:ct10:cvrChassisVersion:
dmi.product.name: HP Pavilion dv6 Notebook PC
dmi.product.version: 058C11244720001620100
dmi.sys.vendor: Hewlett-Packard
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug precise running-unity staging
--
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/1264344
Title:
Filename conflict when copying files - unexpected behaviour when
trying to rename the target file
Status in “linux” package in Ubuntu:
New
Bug description:
I use nautilus filemanger in my ubuntu box. When I copy and paste
files between folders, sometimes a dialog box pops up saying that the
target folder already contains a file with the same name asking me to
choose among a set of options on how to proceed. One of the options
available is to rename the target filename so that the file can be
pasted to the target folder. When I rename the file through this
dialog, it does not paste the file with the new name as expected.
Instead it shows the name conflict dialog again for the same file with
the old name. When I try to rename the file again with a different
name, it accepts the command and pastes the file.
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: linux-image-3.2.0-57-generic 3.2.0-57.87
ProcVersionSignature: Ubuntu 3.2.0-57.87-generic 3.2.52
Uname: Linux 3.2.0-57-generic x86_64
NonfreeKernelModules: fglrx
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
ApportVersion: 2.0.1-0ubuntu17.6
Architecture: amd64
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: PCH [HDA Intel PCH], device 0: STAC92xx Analog [STAC92xx Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: prasanna 2424 F pulseaudio
/dev/snd/pcmC0D0p: prasanna 2424 F...m pulseaudio
Card0.Amixer.info:
Card hw:0 'PC
