Brightness control key types "±" character

Bug #527102 reported by Matt Castelein on 2010-02-24
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
gnome-settings-daemon (Ubuntu)
Low
Unassigned

Bug Description

On my laptop, when I use the brightness up fn key, in addition to increasing the brightness, it also types the character "±" into whatever application has focus. This is happening on Karmic. I am not certain which packages are involved.
---
Architecture: amd64
DistroRelease: Ubuntu 10.04
GnomeSessionIdleInhibited: No
GnomeSessionInhibitors: None
GnomeSessionSuspendInhibited: No
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
Lsusb:
 Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 001 Device 002: ID 064e:a103 Suyin Corp.
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Package: gnome-power-manager 2.30.0-0ubuntu1
PackageArchitecture: amd64
ProcCmdLine: BOOT_IMAGE=/vmlinuz-2.6.32-24-generic root=UUID=703dd9bf-fa47-479e-bc43-937daca45927 ro quiet splash
ProcEnviron:
 LANG=en_US.utf8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-24.42-generic 2.6.32.15+drm33.5
Tags: lucid
Uname: Linux 2.6.32-24-generic x86_64
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
dmi.bios.date: 09/30/2008
dmi.bios.vendor: eMachines
dmi.bios.version: V1.03
dmi.board.name: Nile
dmi.board.vendor: eMachines
dmi.board.version: N/A
dmi.chassis.type: 10
dmi.chassis.vendor: eMachines
dmi.chassis.version: N/A
dmi.modalias: dmi:bvneMachines:bvrV1.03:bd09/30/2008:svn:pn:pvrV1.03:rvneMachines:rnNile:rvrN/A:cvneMachines:ct10:cvrN/A:
dmi.product.version: V1.03

affects: yelp (Ubuntu) → gnome-power-manager (Ubuntu)
Anzenketh (anzenketh) wrote :

Thanks for taking the time to report this bug and helping to make Ubuntu better. Could you please attach the resulting log file of: gnome-power-bugreport.sh & > gpm.log to the report? You might also want to take a look at the debugging instructions located at https://wiki.ubuntu.com/DebuggingGNOMEPowerManager and submit any other logs related to your problem. Thanks in advance.

Changed in gnome-power-manager (Ubuntu):
status: New → Incomplete
Changed in gnome-power-manager (Ubuntu):
status: Incomplete → New
Matt Castelein (matt-castelein) wrote :
Download full text (4.2 KiB)

root@balthasar:~# gnome-power-bugreport.sh: command not found

I guess you mean /usr/share/gnome-power-manager/gnome-power-bugreport...

Distro version: DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=10.04
DISTRIB_CODENAME=lucid
DISTRIB_DESCRIPTION="Ubuntu 10.04 LTS"
Kernel version: 2.6.32-22-generic
g-p-m version: 2.30.0
HAL version: 0.5.14
System manufacturer: missing
System version: missing
System product: missing
AC adapter present: yes
Battery present: yes
Laptop panel present: yes
CPU scaling present: yes
Battery Information:
  battery.charge_level.current = 41958 (0xa3e6) (int)
  battery.charge_level.design = 48840 (0xbec8) (int)
  battery.charge_level.last_full = 41958 (0xa3e6) (int)
  battery.charge_level.percentage = 100 (0x64) (int)
  battery.charge_level.rate = 0 (0x0) (int)
  battery.is_rechargeable = true (bool)
  battery.model = 'GRAPE71' (string)
  battery.present = true (bool)
  battery.rechargeable.is_charging = false (bool)
  battery.rechargeable.is_discharging = false (bool)
  battery.reporting.current = 3780 (0xec4) (int)
  battery.reporting.design = 4400 (0x1130) (int)
  battery.reporting.last_full = 3780 (0xec4) (int)
  battery.reporting.rate = 0 (0x0) (int)
  battery.reporting.technology = 'Li-ion' (string)
  battery.reporting.unit = 'mAh' (string)
  battery.serial = '0022' (string)
  battery.technology = 'lithium-ion' (string)
  battery.type = 'primary' (string)
  battery.vendor = 'Simplo' (string)
  battery.voltage.current = 12563 (0x3113) (int)
  battery.voltage.design = 11100 (0x2b5c) (int)
  battery.voltage.unit = 'mV' (string)
DeviceKit data:
Device: /org/freedesktop/UPower/devices/line_power_ACAD
  native-path: /sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:19/ACPI0003:00/power_supply/ACAD
  power supply: yes
  updated: Wed Jun 2 00:43:40 2010 (279 seconds ago)
  has history: no
  has statistics: no
  line-power
    online: yes

Device: /org/freedesktop/UPower/devices/battery_BAT1
  native-path: /sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:19/PNP0C0A:00/power_supply/BAT1
  vendor: Simplo
  model: GRAPE71
  serial: 0022
  power supply: yes
  updated: Wed Jun 2 00:43:46 2010 (273 seconds ago)
  has history: yes
  has statistics: yes
  battery
    present: yes
    rechargeable: yes
    state: fully-charged
    energy: 41.958 Wh
    energy-empty: 0 Wh
    energy-full: 41.958 Wh
    energy-full-design: 48.84 Wh
    energy-rate: 4.218 W
    voltage: 12.535 V
    percentage: 100%
    capacity: 85.9091%
    technology: lithium-ion

Daemon:
  daemon-version: 0.9.1
  can-suspend: yes
  can-hibernate yes
  on-battery: no
  on-low-battery: no
  lid-is-closed: no
  lid-is-present: yes
GNOME Power Manager Process Information:
blueh2o 3444 0.0 0.4 207288 11396 ? S 00:44 0:00 \_ gnome-power-manager
HAL Process Information:
107 1368 0.3...

Read more...

Pedro Villavicencio (pedro) wrote :

Thanks for taking the time to report this bug and helping to make Ubuntu better. Could you please open a terminal and execute: apport-collect 527102 ? It will attach the necessary information to this report. Thanks in advance.

Changed in gnome-power-manager (Ubuntu):
importance: Undecided → Low
status: New → Incomplete

apport information

tags: added: apport-collected
description: updated

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

Anzenketh (anzenketh) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to look at all reported bugs in a timely manner.
There have been many changes in Ubuntu since that time you reported the bug and your problem may have been fixed with some of the updates. It would help us a lot if you could test the current Ubuntu development version (10.10). If you can test it, and it is still an issue, we would appreciate if you could upload updated logs by running apport-collect <bug #>, and any other logs that are relevant for this particular issue.

Launchpad Janitor (janitor) wrote :

[Expired for gnome-power-manager (Ubuntu) because there has been no activity for 60 days.]

Changed in gnome-power-manager (Ubuntu):
status: Incomplete → Expired
Adolfo Jayme (fitojb) wrote :

The bug still happens.

Changed in gnome-power-manager (Ubuntu):
status: Expired → Confirmed
Matt Castelein (coldfusionpc) wrote :

This is still happening on 12.04 LTS. I just love how these things expire without getting looked into!

Adolfo Jayme (fitojb) wrote :

> I just love how these things expire without getting looked into!

No, you don't.

affects: gnome-power-manager (Ubuntu) → gnome-settings-daemon (Ubuntu)
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Related questions