[Bug 779597] Re: VU meter doesn't work anymore
For me it kind of works, but the levels are insignificant, only a few pixels max (see attachment), so not useful at all. And I also suffer bug #830677, they seem to be related. ** Attachment added: pavucontrol vumeter 1.png https://bugs.launchpad.net/ubuntu/+source/pavucontrol/+bug/779597/+attachment/4231367/+files/pavucontrol%20vumeter%201.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/779597 Title: VU meter doesn't work anymore To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pavucontrol/+bug/779597/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 302570] Re: g-p-m doesn't save charge and discharge profiles
I haven't found an upstream bug about this, and I'm not sure if we should be the ones submitting it or the ubuntu package maintainer. I have been searching for a way to write a serial number to the battery so it will be reported by acpi, but so far I haven't found a way to do this nor I have found if it's even possible. After much thinking about the correct way to identify uniquely between various batteries I'm convinced that the correct way would be to be able to write a serial number if the battery hasn't one. Other correct way would be that the user manually identifies the battery each time the system has doubts, a major PITA. I'm still searching about the way to modify the serial number field in acpi. -- g-p-m doesn't save charge and discharge profiles https://bugs.launchpad.net/bugs/302570 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 302570] Re: g-p-m doesn't save charge and discharge profiles
After some more digging I have to agree 100% with Matti Laakso. If I
launch g-p-m --debug --no-daemon I see this:
TI:10:58:48 TH:0x9c30640FI:gpm-cell-unit.c
FN:gpm_cell_unit_print,78
- charge design 54521
[...]
TI:10:58:48 TH:0x9c30640FI:gpm-profile.c
FN:gpm_profile_set_config_id,783
- config_id = 901-54521
TI:10:58:48 TH:0x9c30640FI:gpm-profile.c
FN:gpm_profile_load_data,734
- loading battery data from
'/home/coma/.gnome2/gnome-power-manager/profile-901-54521-discharging.csv'
*** WARNING ***
TI:10:58:48 TH:0x9c30640FI:gpm-array.c FN:gpm_array_load_from_file,265
- cannot open file
/home/coma/.gnome2/gnome-power-manager/profile-901-54521-discharging.csv
TI:10:58:48 TH:0x9c30640FI:gpm-profile.c
FN:gpm_profile_load_data,745
- no data found, generating initial (poor) data
TI:10:58:48 TH:0x9c30640FI:gpm-profile.c
FN:gpm_profile_load_data,734
- loading battery data from
'/home/coma/.gnome2/gnome-power-manager/profile-901-54521-charging.csv'
*** WARNING ***
TI:10:58:48 TH:0x9c30640FI:gpm-array.c FN:gpm_array_load_from_file,265
- cannot open file
/home/coma/.gnome2/gnome-power-manager/profile-901-54521-charging.csv
TI:10:58:48 TH:0x9c30640FI:gpm-profile.c
FN:gpm_profile_load_data,745
- no data found, generating initial (poor) data
So the assumption of Matti Laakso is correct. And I think this model is not the
only one that reports a different battery.charge_level.design in each cycle, so
far battery.reporting.design (6580 now) seems to be more correct. I don't known
what should be the correct way to detect a different battery, but I think that
most users only have one battery, so perhaps the default should be to assume
that it is always the same battery and provide some way to disable the behavior
for people with multiple batteries.
$ lshal |grep battery
udi = '/org/freedesktop/Hal/devices/computer_power_supply_battery_BAT0'
battery.charge_level.current = 35000 (0x88b8) (int)
battery.charge_level.design = 50218 (0xc42a) (int)
battery.charge_level.last_full = 48791 (0xbe97) (int)
battery.charge_level.percentage = 71 (0x47) (int)
battery.charge_level.rate = 8005 (0x1f45) (int)
battery.is_rechargeable = true (bool)
battery.model = '901' (string)
battery.present = true (bool)
battery.rechargeable.is_charging = false (bool)
battery.rechargeable.is_discharging = true (bool)
battery.remaining_time = 15740 (0x3d7c) (int)
battery.reporting.current = 4586 (0x11ea) (int)
battery.reporting.design = 6580 (0x19b4) (int)
battery.reporting.last_full = 6393 (0x18f9) (int)
battery.reporting.rate = 1049 (0x419) (int)
battery.reporting.technology = 'Li-ion' (string)
battery.reporting.unit = 'mAh' (string)
battery.serial = '' (string)
battery.technology = 'lithium-ion' (string)
battery.type = 'primary' (string)
battery.vendor = 'ASUS' (string)
battery.voltage.current = 7632 (0x1dd0) (int)
battery.voltage.design = 8400 (0x20d0) (int)
battery.voltage.unit = 'mV' (string)
info.capabilities = {'battery'} (string list)
info.category = 'battery' (string)
info.udi = '/org/freedesktop/Hal/devices/computer_power_supply_battery_BAT0'
(string)
--
g-p-m doesn't save charge and discharge profiles
https://bugs.launchpad.net/bugs/302570
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 302570] Re: g-p-m doesn't save charge and discharge profiles
I'm not sure the name of the file is the culprint. I asked two friends winth different laptops to send me the contents of ~/.gnome2/gnome- power-manager, both of them are free of this bug, one has lots of files in this directory while the other one has four. There seems to be some problems in the naming of the files (some repated elements in some names): User A: profile-XM8001P02-XM8001P02-discharging.csv profile-XM8001P02-discharging.csv profile-XM8001P02-charging.csv profile-XM8001P02-XM8001P02-charging.csv User B: profile-47836-charging.csv profile-47836-discharging.csv profile-49483-charging.csv profile-49483-discharging.csv profile-49924-charging.csv profile-49924-discharging.csv profile-50097-charging.csv profile-50097-discharging.csv profile-50179-charging.csv profile-50179-discharging.csv profile-50284-charging.csv profile-50284-discharging.csv profile-50366-charging.csv profile-50366-discharging.csv profile-50654-charging.csv profile-50654-discharging.csv profile-51004-charging.csv profile-51004-discharging.csv profile-51148-charging.csv profile-51148-discharging.csv profile-51177-charging.csv profile-51177-discharging.csv profile-51264-charging.csv profile-51264-discharging.csv profile-51273-charging.csv profile-51273-discharging.csv profile-51340-charging.csv profile-51340-discharging.csv profile-51364-charging.csv profile-51364-discharging.csv profile-51465-charging.csv profile-51465-discharging.csv profile-51964-charging.csv profile-51964-discharging.csv profile-52123-charging.csv profile-52123-discharging.csv profile-52128-charging.csv profile-52128-discharging.csv profile-52204-charging.csv profile-52204-discharging.csv profile-52228-charging.csv profile-52228-discharging.csv profile-52238-charging.csv profile-52238-discharging.csv profile-52353-charging.csv profile-52353-discharging.csv profile-52492-charging.csv profile-52492-discharging.csv profile-52588-charging.csv profile-52588-discharging.csv profile-52636-charging.csv profile-52636-discharging.csv profile-52646-charging.csv profile-52646-discharging.csv profile-52723-charging.csv profile-52723-discharging.csv profile-52732-charging.csv profile-52732-discharging.csv profile-52776-charging.csv profile-52776-discharging.csv profile-52780-charging.csv profile-52780-discharging.csv profile-52939-charging.csv profile-52939-discharging.csv profile-53011-charging.csv profile-53011-discharging.csv profile-53097-charging.csv profile-53097-discharging.csv profile-53136-53280-charging.csv profile-53136-53280-discharging.csv profile-53145-charging.csv profile-53145-discharging.csv profile-53150-charging.csv profile-53150-discharging.csv profile-53179-charging.csv profile-53179-discharging.csv profile-53184-charging.csv profile-53184-discharging.csv profile-53198-charging.csv profile-53198-discharging.csv profile-53203-charging.csv profile-53203-discharging.csv profile-53208-charging.csv profile-53208-discharging.csv profile-53217-charging.csv profile-53217-discharging.csv profile-53222-charging.csv profile-53222-discharging.csv profile-53260-charging.csv profile-53260-discharging.csv profile-53280-53280-53280-charging.csv profile-53280-53280-53280-discharging.csv profile-53280-53280-charging.csv profile-53280-53280-discharging.csv profile-53280-charging.csv profile-53280-discharging.csv profile-generic_id-charging.csv profile-generic_id-discharging.csv Me (with the bug): profile-901-39677-charging.csv profile-901-39677-discharging.csv profile-901-45823-charging.csv profile-901-45823-discharging.csv profile-901-46244-charging.csv profile-901-46244-discharging.csv profile-901-46481-charging.csv profile-901-46481-discharging.csv profile-901-46586-charging.csv profile-901-46586-discharging.csv profile-901-46902-charging.csv profile-901-46902-discharging.csv profile-901-46941-charging.csv profile-901-46941-discharging.csv profile-901-47218-charging.csv profile-901-47218-discharging.csv profile-901-47389-charging.csv profile-901-47389-discharging.csv profile-901-47428-charging.csv profile-901-47428-discharging.csv profile-901-47494-charging.csv profile-901-47494-discharging.csv profile-901-47705-charging.csv profile-901-47705-discharging.csv profile-901-47744-charging.csv profile-901-47744-discharging.csv profile-901-47955-charging.csv profile-901-47955-discharging.csv profile-901-47994-charging.csv profile-901-47994-discharging.csv profile-901-48191-charging.csv profile-901-48191-discharging.csv profile-901-48231-charging.csv profile-901-48231-discharging.csv profile-901-48507-charging.csv profile-901-48507-discharging.csv profile-901-48652-charging.csv profile-901-48652-discharging.csv profile-901-48692-charging.csv profile-901-48692-discharging.csv profile-901-48718-charging.csv profile-901-48718-discharging.csv profile-901-48797-charging.csv profile-901-48797-discharging.csv profile-901-49731-charging.csv profile-901-49731-discharging.csv profile-901-49981-charging.csv profile-901-49981-discharging.csv profile-901-50152-charging.csv
[Bug 302570] [NEW] g-p-m doesn't save charge and discharge profiles
Public bug reported: Binary package hint: gnome-power-manager There is a question in https://answers.launchpad.net/ubuntu/+source /gnome-power-manager/+question/51483 about g-p-m losing all the info about charge/discharge profile after a restart or suspend. All that seems to be common is: Ubuntu 8.10 (8.04 worked OK) g-p-m 2.24.0 Laptop Asus Eee PC 901 ACPI and everything else seems to be OK, g-p-m works ok in a session, but the moment the system is restarted, suspended/resumed or AC is plugged/unplugged, g-p-m will forget all the collected data points. The files in ~/.gnome2/gnome-power-manager doesn't seem to be correct. I have taken a peek inside the profile-901-55048-charging.csv and profile-901-55048-discharging.csv that are the ones with the last modified time, the charging one seems ok but empty, now I'm running on battery so I have no history (flat line): profile-901-55048-charging.csv 0, 0, 0 1, 0, 0 2, 0, 0 3, 0, 0 4, 0, 0 5, 0, 0 6, 0, 0 7, 0, 0 [...] 96, 0, 0 97, 0, 0 98, 0, 0 99, 0, 0 The discharging one is a bit weird profile-901-55048-discharging.csv 0, 0, 0 0, 0, 0 0, 0, 0 0, 0, 0 0, 0, 0 0, 0, 0 0, 226, 0 0, 226, 0 0, 226, 0 0, 226, 0 0, 226, 0 0, 226, 0 [...] 0, 226, 0 0, 226, 0 0, 209, 17 0, 240, 17 0, 239, 17 0, 209, 17 0, 239, 17 0, 210, 16 0, 239, 17 0, 210, 17 0, 209, 16 0, 239, 17 0, 240, 18 0, 209, 16 [...] 0, 240, 14 0, 210, 11 0, 240, 15 0, 239, 16 0, 240, 18 0, 270, 18 0, 0, 0 both files have 100 lines, but something seems wrong, now I have switched to charging the files g-p-m is writing have changed : profile-901-48797-charging.csv 0, 0, 0 0, 0, 0 0, 0, 0 0, 0, 0 0, 0, 0 0, 0, 0 0, 106, 0 0, 106, 0 0, 106, 0 0, 106, 0 0, 106, 0 0, 106, 0 [...] 0, 120, 14 0, 89, 14 0, 89, 13 0, 90, 8 0, 119, 10 0, 89, 6 0, 90, 6 0, 120, 10 0, 89, 9 0, 119, 7 0, 120, 17 0, 150, 17 0, 149, 18 0, 149, 17 0, 210, 17 0, 210, 18 0, 0, 0 0, 0, 0 0, 0, 0 0, 0, 0 0, 0, 0 profile-901-48797-discharging.csv 0, 0, 0 1, 0, 0 2, 0, 0 3, 0, 0 4, 0, 0 5, 0, 0 6, 0, 0 7, 0, 0 8, 0, 0 9, 0, 0 10, 0, 0 11, 0, 0 [...] 94, 0, 0 95, 0, 0 96, 0, 0 97, 0, 0 98, 0, 0 99, 0, 0 So now they seem reversed. I think that the csv is wrong in profile-901-55048-discharging.csv and profile-901-48797-charging.csv and empty in the other ones. I expected g-p-m to save save/discharge profiles as it did in 8.04 and what happened is that whenever a change in the energy status of the laptop happens g-p-m loses the collected data points. The output of gnome-power-bugreport.sh: Distro version: DISTRIB_ID=Ubuntu DISTRIB_RELEASE=8.10 DISTRIB_CODENAME=intrepid DISTRIB_DESCRIPTION=Ubuntu 8.10 Kernel version: 2.6.27-8-eeepc g-p-m version:2.24.0 HAL version: 0.5.11 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 = 50635 (0xc5cb) (int) battery.charge_level.design = 54140 (0xd37c) (int) battery.charge_level.last_full = 52634 (0xcd9a) (int) battery.charge_level.percentage = 96 (0x60) (int) battery.charge_level.rate = 8302 (0x206e) (int) battery.is_rechargeable = true (bool) battery.model = '901' (string) battery.present = true (bool) battery.rechargeable.is_charging = false (bool) battery.rechargeable.is_discharging = true (bool) battery.remaining_time = 21956 (0x55c4) (int) battery.reporting.current = 6154 (0x180a) (int) battery.reporting.design = 6580 (0x19b4) (int) battery.reporting.last_full = 6397 (0x18fd) (int) battery.reporting.rate = 1009 (0x3f1) (int) battery.reporting.technology = 'Li-ion' (string) battery.reporting.unit = 'mAh' (string) battery.serial = '' (string) battery.technology = 'lithium-ion' (string) battery.type = 'primary' (string) battery.vendor = 'ASUS' (string) battery.voltage.current = 8228 (0x2024) (int) battery.voltage.design = 8400 (0x20d0) (int) battery.voltage.unit = 'mV' (string) GNOME Power Manager Process Information: coma 8793 0.0 1.5 35584 16296 ?Ss Nov21 0:41 gnome-power-manager coma 21116 0.3 1.3 3 13924 ?S18:11 0:34 gnome-power-statistics coma 28598 1.2 1.6 31512 17404 ?S20:16 0:16 file-roller file:///tmp/gnome-power-manager.tar.gz HAL Process Information: 111 5338 0.0 0.2 6320 2636 ?Ss Nov21 0:30 /usr/sbin/hald root 5342 0.0 0.1 3364 1112 ?SNov21 0:00 \_ hald-runner root 5424 0.0 0.1 3436 1028 ?SNov21 0:00 \_ hald-addon-input: Listening on /dev/input/event3 /dev/input/event8 /dev/input/event6 /dev/input/event4 /dev/input/event5 /dev/input/event1 /dev/input/event7 root 5431 0.0 0.0 3448 988 ?SNov21 0:00 \_ /usr/lib/hal/hald-addon-cpufreq 111 5432 0.0 0.0 2296 920 ?SNov21 0:00 \_
