Strangely the problem disappeared for me. The theme was correctly
applied after the last 4 boots. I can't tell you what changed though. I
didn't attempt any of the above suggestions and just did daily updates.
--
Meerkat (10.10) does not apply theme properly
I can confirm the same behavior on the W510 with 10.10.
--
Thinkpad T400s, T410s, T410, T510 microphone mute button does not work
https://bugs.launchpad.net/bugs/408903
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
I tested it with the alpha3 live CD and it seams to be fixed.
--
After wakeup from sleep, gnome-power-manager does not detect it is running on
battery
https://bugs.launchpad.net/bugs/472347
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Thanks Adam.
After patching the kernel and installing it I can confirm that this patch
works.
Now it only needs to make its way into the ubuntu kernel.
--
After wakeup from sleep, gnome-power-manager does not detect it is running on
battery
https://bugs.launchpad.net/bugs/472347
You received
** Attachment added: gconf-editor settings for g-p-m (thresholds)
http://launchpadlibrarian.net/35754201/Screenshot-Configuration%20Editor%20-%20thresholds.png
--
Action on critical battery is not triggered - gnome-power-manager
https://bugs.launchpad.net/bugs/481576
You received this bug
I can confirm Maciej's observation. After a short period of time on
critical power it drops to 0%.
I also wonder if it could be something about the missing time left which
g-p-m never shows on my laptop. Settings and thresholds for g-p-m in
gconf-editor indicate that g-p-m is working based on
Adam,
Can you please help me to apply this patch. I downloaded the kernel sources
and unpacked them. Now I'm stuck cause all the tutorials I found assume that I
have a archive as source for the patch. But I don't know how to get this.
Thanks, your help is appreciated.
--
After wakeup from
I did as you told me:
killall -9 gnome-power-manager
gnome-power-manager --no-daemon --verbose ~/gpm.log 21
This created an empty log file.
I let it run on battery until 2-3 minutes after the critical battery warning
was shown.
--
Action on critical battery is not triggered -
I had it running for over an hour before my battery was drained. The file was
still empty.
When I run
gnome-power-manager --verbose ~/gpm.log 21
it fills up pretty fast. I added that log yesterday already (see post
#2).
--
Action on critical battery is not triggered - gnome-power-manager
Public bug reported:
Binary package hint: gnome-power-manager
System Info:
Hardware: HP dv4-1120us
OS: Ubuntu 9.10
Kernel: 2.6.31-14-generic
gpm-version: 2.28.1-0ubuntu1
What I expected to happen:
When the battery reaches critical level the laptop should hibernate like set up
in the
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/35590170/Dependencies.txt
** Attachment added: DevkitPower.txt
http://launchpadlibrarian.net/35590171/DevkitPower.txt
** Attachment added: GConfNonDefault.txt
http://launchpadlibrarian.net/35590172/GConfNonDefault.txt
created a new bug report: 481576
https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/481576
--
Action on critical battery isn't triggered
https://bugs.launchpad.net/bugs/135548
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Attachment added: output of gnome-power-manager --verbose
http://launchpadlibrarian.net/35591704/gpm.log
--
Action on critical battery is not triggered - gnome-power-manager
https://bugs.launchpad.net/bugs/481576
You received this bug notification because you are a member of Ubuntu
Bugs,
I have the same bug in Karmic on HP dv4-1120us.
gpm.log is attached.
** Attachment added: gmp.log
http://launchpadlibrarian.net/35109884/gmp.log
--
Action on critical battery isn't triggered
https://bugs.launchpad.net/bugs/135548
You received this bug notification because you are a member
** Summary changed:
- After wakeup from sleep, gnome-power-manager does not detect it is running on
battery
+ After wakeup from sleep, gnome-power-manager does not detect battery
--
After wakeup from sleep, gnome-power-manager does not detect battery
https://bugs.launchpad.net/bugs/472347
You
*** This bug is a duplicate of bug 472347 ***
https://bugs.launchpad.net/bugs/472347
** This bug has been marked a duplicate of bug 472347
After wakeup from sleep, gnome-power-manager does not detect battery
--
Battery not recognized after suspend
https://bugs.launchpad.net/bugs/471888
** Summary changed:
- After wakeup from sleep, gnome-power-manager does not detect battery
+ After wakeup from sleep, gnome-power-manager does not detect it is running on
battery
--
After wakeup from sleep, gnome-power-manager does not detect it is running on
battery
Sorry for the name change, I was in the wrong report.
But I can confirm this behavior. I had filed a report on my own. See
here: https://bugs.launchpad.net/ubuntu/+source/gnome-power-
manager/+bug/471888
I marked it as duplicate.
--
After wakeup from sleep, gnome-power-manager does not detect
Architecture: amd64
DistroRelease: Ubuntu 9.10
NonfreeKernelModules: wl
Package: gnome-power-manager 2.28.1-0ubuntu1
PackageArchitecture: amd64
ProcEnviron:
SHELL=/bin/bash
LANG=en_US.UTF-8
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
Uname: Linux 2.6.31-14-generic x86_64
UserGroups: adm
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/35113538/Dependencies.txt
--
After wakeup from sleep, gnome-power-manager does not detect it is running on
battery
https://bugs.launchpad.net/bugs/472347
You received this bug notification because you are a member of Ubuntu
** Attachment added: DevkitPower.txt
http://launchpadlibrarian.net/35113541/DevkitPower.txt
--
After wakeup from sleep, gnome-power-manager does not detect it is running on
battery
https://bugs.launchpad.net/bugs/472347
You received this bug notification because you are a member of Ubuntu
** Attachment added: GConfNonDefault.txt
http://launchpadlibrarian.net/35113542/GConfNonDefault.txt
--
After wakeup from sleep, gnome-power-manager does not detect it is running on
battery
https://bugs.launchpad.net/bugs/472347
You received this bug notification because you are a member of
** Attachment added: gnome-power-bugreport.txt
http://launchpadlibrarian.net/35113543/gnome-power-bugreport.txt
** Tags added: apport-collected
--
After wakeup from sleep, gnome-power-manager does not detect it is running on
battery
https://bugs.launchpad.net/bugs/472347
You received this
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/35098178/Dependencies.txt
--
After opening laptop brightness stays in very low level
https://bugs.launchpad.net/bugs/460987
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Architecture: amd64
DistroRelease: Ubuntu 9.10
NonfreeKernelModules: wl
Package: gnome-power-manager 2.28.1-0ubuntu1
PackageArchitecture: amd64
ProcEnviron:
SHELL=/bin/bash
LANG=en_US.UTF-8
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
Uname: Linux 2.6.31-14-generic x86_64
UserGroups: adm
** Attachment added: DevkitPower.txt
http://launchpadlibrarian.net/35098180/DevkitPower.txt
--
After opening laptop brightness stays in very low level
https://bugs.launchpad.net/bugs/460987
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Attachment added: GConfNonDefault.txt
http://launchpadlibrarian.net/35098182/GConfNonDefault.txt
--
After opening laptop brightness stays in very low level
https://bugs.launchpad.net/bugs/460987
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Attachment added: XsessionErrors.txt
http://launchpadlibrarian.net/35098185/XsessionErrors.txt
--
After opening laptop brightness stays in very low level
https://bugs.launchpad.net/bugs/460987
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
** Attachment added: gnome-power-bugreport.txt
http://launchpadlibrarian.net/35098187/gnome-power-bugreport.txt
** Tags added: apport-collected
--
After opening laptop brightness stays in very low level
https://bugs.launchpad.net/bugs/460987
You received this bug notification because you
Brightness-Applet doesn't work for me. Screen stays on low brightness
until I reboot.
This is on a HP dv4-1120us laptop.
--
After opening laptop brightness stays in very low level
https://bugs.launchpad.net/bugs/460987
You received this bug notification because you are a member of Ubuntu
Bugs,
Public bug reported:
Binary package hint: gnome-power-manager
Package: gnome-power-manager
Ubuntu version: 9.10 (fully updated)
Package version: 2.28.1-0ubuntu1
Hardware: HP dv4-1120us laptop
Expected behavior:
(1) on AC-power, screen should be bright, charge the battery (if empty enough)
(2)
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/34991445/Dependencies.txt
** Attachment added: DevkitPower.txt
http://launchpadlibrarian.net/34991446/DevkitPower.txt
** Attachment added: GConfNonDefault.txt
http://launchpadlibrarian.net/34991447/GConfNonDefault.txt
I am not completely sure if this is the same bug but I have a similar
effect on my HP dv4-1120us laptop. After suspending and restarting the
laptop GPM thinks there is no battery in my system and always shows a
power plug even when the AC adapter is unplugged. This is persistent
until the system
Output of
ls -la /proc/acpi/*/*
cat /proc/acpi/*/*/*
hal-find-by-capability --capability battery | xargs -n 1 hal-device
hal-find-by-capability --capability ac_adapter | xargs -n 1 hal-device
after a clean boot once with the AC adapter plugged in and once
unplugged.
** Attachment added:
Output of
ls -la /proc/acpi/*/*
cat /proc/acpi/*/*/*
hal-find-by-capability --capability battery | xargs -n 1 hal-device
hal-find-by-capability --capability ac_adapter | xargs -n 1 hal-device
after resuming from suspend (error occurred) once with the AC adapter
plugged in and once unplugged.?
** Description changed:
After resuming from Suspend to Ram the Power Management Applet states
that the battery is not present.
Plugging out the power cord and plugging it back in doesn't change that.
This happens no matter what the power cord is plugged in or out when
suspending.
+
This also sometimes happens when resuming from Suspend to Disk.
--
Stuttering sound after resume from Suspend to Ram
https://bugs.launchpad.net/bugs/372362
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
(suspected)
** Package changed: ubuntu = pm-utils (Ubuntu)
--
Stuttering sound after resume from Suspend to Ram
https://bugs.launchpad.net/bugs/372362
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
** Attachment added: Xorg.0.log
http://launchpadlibrarian.net/26439364/Xorg.0.log
--
[Q45] Display corruption on Intel chipset
https://bugs.launchpad.net/bugs/362919
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
** Attachment added: snapshot of screen corruption
http://launchpadlibrarian.net/26439342/graphic_glitch1.png
--
[Q45] Display corruption on Intel chipset
https://bugs.launchpad.net/bugs/362919
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
I can confirm this bug.
I'm running a fresh install of Kubuntu 9.04 64bit on a HP dv4-1120us.
Output of lspci -vvnn is attached.
** Attachment added: lspci -vvnn output
http://launchpadlibrarian.net/26439323/lspci_output
--
[Q45] Display corruption on Intel chipset
** Attachment added: Xorg.0.log.old
http://launchpadlibrarian.net/26439377/Xorg.0.log.old
--
[Q45] Display corruption on Intel chipset
https://bugs.launchpad.net/bugs/362919
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
** Description changed:
- After resuming from Suspend to Ram when sound is played from an application
it stutters and never stops. Also the LED under the Mute-button is red instead
of white.
+ After resuming from Suspend to Ram when sound is played from notification or
application it stutters
I just upgraded my BIOS and the problem is gone. The system is
responding and I can login on a console. The HDD is obviously
detected/reconnected correctly. I can work with the applications that
were open and can open new applications as well.
--
HDD connection error after suspend to ram
I can't test if it also happens for Suspend to Disk, since my WIBU-
Installation only offers 256MB of swap which leads to a message stating
that there is not enough such swap space to suspend to disk.
** Description changed:
- After a Suspend to Disk the system wakes up but is unusable. It comes
I have the same problem as Alexander Saltykov has. Since low on Swap I
get back to the desktop and get the message. No problems like that when
resuming from Suspend to Ram though.
--
Kwin effects fail after resume from suspend to RAM
https://bugs.launchpad.net/bugs/328759
You received this bug
Public bug reported:
After resuming from Suspend to Ram the Power Management Applet states
that the battery is not present.
Plugging out the power cord and plugging it back in doesn't change that.
This happens no matter what the power cord is plugged in or out when suspending.
System Info:
HP
Public bug reported:
After resuming from Suspend to Ram the Power Management Applet states
that the battery is not present.
Plugging out the power cord and plugging it back in doesn't change that.
This happens no matter what the power cord is plugged in or out when suspending.
System Info:
HP
Public bug reported:
After resuming from Suspend to Ram the Power Management Applet states
that the battery is not present.
Plugging out the power cord and plugging it back in doesn't change that.
This happens no matter what the power cord is plugged in or out when suspending.
System Info:
HP
Public bug reported:
After resuming from Suspend to Ram when sound is played from an application it
stutters and never stops. Also the LED under the Mute-button is red instead of
white.
Only rebooting helps to get everything back to normal.
System Info:
HP dv4-1120us, 4GB Ram, 250GB SATA HDD
*** This bug is a duplicate of bug 372336 ***
https://bugs.launchpad.net/bugs/372336
** This bug has been marked a duplicate of bug 372336
Battery not present after resume from Suspend to Ram
--
Battery not present after resume from Suspend to Ram
https://bugs.launchpad.net/bugs/372338
*** This bug is a duplicate of bug 372336 ***
https://bugs.launchpad.net/bugs/372336
** This bug has been marked a duplicate of bug 372336
Battery not present after resume from Suspend to Ram
--
Battery not present after resume from Suspend to Ram
https://bugs.launchpad.net/bugs/372339
I have a Western Digital WDC WD2500BEVS-60UST0. That means it is not a HDD
model/manufacturer specific problem.
I attached my hdparm output.
** Attachment added: output of hdparm -i /dev/sda
http://launchpadlibrarian.net/26329086/hdparm_output
--
HDD connection error after suspend to ram
Public bug reported:
After a Suspend to Disk the system wakes up but is unusable. It comes up with
some error messages from the notification widget, but these are following
errors and not the cause of it.
This is a SATA system, I don't have that problem on my IDE system.
After switching to a
** Attachment added: lspci output of my system
http://launchpadlibrarian.net/26316861/lspci_output
--
HDD connection error after suspend to ram
https://bugs.launchpad.net/bugs/371732
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
55 matches
Mail list logo