** Changed in: gnome-power-manager (Ubuntu)
Status: New = Fix Released
--
Battery indicator stuck on fully charged
https://bugs.launchpad.net/bugs/572970
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-power-manager in
Public bug reported:
Binary package hint: gnome-power-manager
When the laptop battery is fully charged and the power cable is removed
the battery monitor does not notice this change, and does not report the
battery as discharging until the battery is critically low alert is
hit.
This affects
** Attachment added: BootDmesg.txt
http://launchpadlibrarian.net/46934794/BootDmesg.txt
** Attachment added: CurrentDmesg.txt
http://launchpadlibrarian.net/46934795/CurrentDmesg.txt
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/46934796/Dependencies.txt
**
Bug reported at http://bugzilla.gnome.org/show_bug.cgi?id=582952
** Bug watch added: GNOME Bug Tracker #582952
http://bugzilla.gnome.org/show_bug.cgi?id=582952
--
Lock screen dialogue freezes on correct password
https://bugs.launchpad.net/bugs/363361
You received this bug notification
Hi, thanks for the response. Attached it the debug log you asked for.
It is also worth noting that, whilst creating this log, I noticed that the bug
only occurs once per boot:
The first time I kill gnome-screensaver, start it in debug mode and lock screen
the bug occurs.
Any further time I kill
As stated in my last comment this bug only occurs once per boot.
Attached is the debug log of the second attempt to lock/unlock which
works properly.
** Attachment added: debug log on unlocking success
http://launchpadlibrarian.net/26477048/gs_succeed.log
--
Lock screen dialogue freezes on
Public bug reported:
Binary package hint: gnome-screensaver
Running 9.04 release candidate (upgraded from 8.10)
gnome-screensaver version 2.24.0-0ubuntu6 (I think this is the package that
handles the lock screen dialogue?)
When confronted with the lock screen dialogue (whether produced from
Hi Basilio,
A subsequent upgrade of the Hardy alpha environment broke my
installation. I couldn't even log in: a failed malloc in the startup of
the session stopped me from even logging in in single-user mode.
I have since installed the server (64 bit) version of of Hardy beta but
have not
to the login screen.
On the other hand, I can login successfully if I choose a Gnome failsave
session.
Please could somone indicate what logs I should look at to find the
error?
Thanks for any help on this.
SteveH
The gdm logs of the succeeded startups and the failed ones seem to be
identical.
I'm
This is a squeaky wheel gets the grease posting, with a bit more info.
I also get the dropping to single dma msg, with an error number (I
assume) of 883.997589. Maybe that will tell you where it's being
issued. I tried Draconid's trick, killed gvm, and viola! played my
audio cd's. Just to see
10 matches
Mail list logo
