Public bug reported:
I have an Acer Aspire One (model zg5). When I pull the power cable, the
acpi command updates output within a few seconds to
Battery 0: Discharging, 91%, 06:14:30 remaining
However, even half an hour later, the GPM icon still says I'm on power.
Also, the battery graphing
** Attachment added: screenshot showing acpi output, GPM applet state and
Graphs
https://bugs.launchpad.net/bugs/849772/+attachment/2401408/+files/Screenshot.png
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-power-manager
It's a while since I've actually looked at this. There was a bug day
coming up among edubuntu developers and I mentioned this bug as one
which was causing problems for some people. Jordan said he had a fix,
though I'm not sure what version that was against.
On an LTSP system, it's not uncommon
Hi,
laserjock says he has a fix for this.
https://lists.ubuntu.com/archives/edubuntu-
devel/2010-January/003224.html
Hopefully he'll pass it on soon :-)
Gavin
--
User administration, groups are not sortable; users-admin
https://bugs.launchpad.net/bugs/379944
You received this bug
Oops, sorry, that's for bug 259163
--
User administration, groups are not sortable; users-admin
https://bugs.launchpad.net/bugs/379944
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-system-tools in ubuntu.
--
desktop-bugs
Many thanks for everyone's the work on this, particularly Milan.
Gavin
--
Adding a new user with Real Name containing an apostrophe fails
https://bugs.launchpad.net/bugs/180261
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
While perhaps not an exact duplicate, it seems this bug relates to bug
259163
--
User administration, groups are not sortable; users-admin
https://bugs.launchpad.net/bugs/379944
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
I've been looking through the code for this and am adding some notes
here in case they help anyone else (or me to recall later).
As Jordan observes, these errors are telling us about the problem:
(users-admin:724): Gtk-CRITICAL **: gtk_tree_sortable_get_sort_column_id:
assertion
I've reported this bug upstream to the gnome developers and linked that
bug to this launchpad bug.
** Bug watch added: GNOME Bug Tracker #593107
http://bugzilla.gnome.org/show_bug.cgi?id=593107
** Also affects: gst via
http://bugzilla.gnome.org/show_bug.cgi?id=593107
Importance: Unknown
I've submitted a patch upstream to system-tools-backends which hopefully
should resolve this bug.
http://bugzilla.gnome.org/show_bug.cgi?id=519273
This should hopefully be committed upstream soon and filter down in the
next update.
--
Adding a new user with Real Name containing an apostrophe
Public bug reported:
Binary package hint: gnome-power-manager
On an acer aspire one, the battery light started flashing. I looked at
the gnome applet and it said the battery was 99.3% full. The /proc/acpi
info had the correct data however.
I haven't managed to repeat this as yet. As soon as
this screenshot shows the mouseover on the applet showing 99.8% while
the /proc/acpi/ data is totally contradictory, saying 3%.
** Attachment added: screenshot showing contradicition between applet and
/proc/acpi
http://launchpadlibrarian.net/30387712/Screenshot-1.png
--
[karmic] applet not
On reflection, my interpretation of the sums is a little wrong. It's 3%
of an hour left. Either way, 99.2% battery charge seems way off.
--
[karmic] applet not updating battery charge (still says 92% when down to 1%)
https://bugs.launchpad.net/bugs/414392
You received this bug notification
This bug may be fixed but it's not working for me.
The reason in my case though is that the weather applet (and gnome proxy
in general) doesn't seem able to deal with proxy authentication which is
required on my site.
1250239082.625136 172.16.1.3 TCP_DENIED/407 1906 GET
Public bug reported:
Binary package hint: gnome-applets
Hi,
I have a proxy server configured in GNOME with a wpad.dat script for my
network. I have the gnome application on my desktop. I don't get any
data.
When I tell the applet to reload, i see this in our Squid logs.
1250239255.714
Currently Jaunty Jackalope. I can upgrade a spare laptop to Karmic and
test if that's likely to have a fix?
--
weather applet won't do proxy authentication
https://bugs.launchpad.net/bugs/413469
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug
I don't think it is fixed to be honest. The problem is a bit
intermittent, but I'm pretty certain I still see it.
--
[jaunty] screen brightness dims on AC power despite config to leave at 100%
https://bugs.launchpad.net/bugs/355180
You received this bug notification because you are a member of
Public bug reported:
Binary package hint: gnome-power-manager
I have a Dell Latitude D410 laptop running the latest testing version of
Jaunty.
While I'm typing here, I have the laptop on AC power. I find the screen
keeps dimming down to about 60%. I then use the hotkey to brighten the
screen
Oops. I may have jumped the gun on this. I was running an upgrade as I
typed and the above versions are post-upgrade. Since the reboot, I'm
not seeing the issue.
This may be fixed already.
Gavin
--
[jaunty] screen brightness dims on AC power despite config to leave at 100%
Hi,
It seems a reliable way for me to prompt the flickering to start is to
unplug or replug the power cable. Whatever process goes on, at the
point the flickering happens, there's no output coming from the gsd
instance with debug:
gnome-settings-daemon --no-daemon --debug
Attached is the full
Having realised that I should pass the --no-daemon --debug when using
gdb, here's another backtrace using those options.
I've run 'killall -3 gnome-settings-daemon' during the flickering (which
comes and goes) and taken a backtrace.
** Attachment added: gdb-gnome-settings-daemon3.txt
I managed to get a backtrace on the second attempt. If you look at the
file attached, it has a failed attempt first, then a second attach, then
a backtrace.
When the screen started flickering, I killed GSD with signal 3, then
took the backtrace as suggested in the wiki.
Let me know if this is
** Attachment added: gnome session errors file from the session
http://launchpadlibrarian.net/23602397/.xsession-errors
--
[jaunty] strange desktop flickering makes desktop unusable, killing GSD is
workaround
https://bugs.launchpad.net/bugs/339491
You received this bug notification because
23 matches
Mail list logo
