Thanks - that seems to work nicely as a workaround on Oneiric for me
too. Very helpful.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/531190
Title:
upower (devkit-power) reporting bad data when AC
Furthermore, none of the workarounds work in Oneiric. The relevant keys
for gnome-power-manager no longer exist in gconf, and creating them has
no effect.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Also, with Oneiric on my Dell Mini 9 ...
Problem is *not* solved by removing gnome-power-manager altogether.
But ... problem does not occur at all if you use Xfce instead of Unity.
What's different about Xfce's power management versus Unity? Doesn't it
rely on upower too?
--
You received this
Affects me on 11.10 too, running on a Dell Mini 9.
It was fine in 11.04, incidentally.
I have the same result from upower --version as furyhunter.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
On my Dell Mini 9 too, also with the Broadcom STA driver and a 802.11n
router, at 2.4 GHz.
--
nm-applet displays the wrong connection status
https://bugs.launchpad.net/bugs/574270
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Changing the network mode to G-only made the correct icon to display.
--
nm-applet displays the wrong connection status
https://bugs.launchpad.net/bugs/574270
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Patch seems to solve the problem completely on my Dell Mini 9 too, both
a spontaneous and forced fsck having completed fine with the progress
bar also behaving just as expected, continuing up to 100% at a regular
pace and proper speed.
No surprising side-effects so far.
Many thanks to all
All seems well on my other affected machine now, too (a Dell M1330).
--
fsck progress stalls at boot, plymouthd/mountall eats CPU
https://bugs.launchpad.net/bugs/571707
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
Interesting thought that this could be related to upgrading from Karmic
rather than a fresh install. Both my machines suffer from the problem
and were upgraded, for what it's worth. How about everyone else?
--
fsck progress stalls at boot, plymouthd/mountall eats CPU
d...@dell:~$ sudo hwinfo --bios | grep Socket:
Socket: Microprocessor
d...@dell:~$ sudo hwinfo --gfxcard | grep Modules:
Driver Modules: drm
--
fsck progress stalls at boot, plymouthd/mountall eats CPU
https://bugs.launchpad.net/bugs/571707
You received this bug notification because you
d...@mini:~$ sudo hwinfo --bios | grep Socket:
Socket: U1
d...@mini:~$ sudo hwinfo --gfxcard | grep Modules:
Driver Modules: drm
--
fsck progress stalls at boot, plymouthd/mountall eats CPU
https://bugs.launchpad.net/bugs/571707
You received this bug notification because you are a member
Same problem here since the last Plymouth update; fsck gets to the
fateful 70% mark and then slows to a crawl (though not hanging).
The machine is a Dell Mini 9 with a tiny 32G drive so there is no
possibility that fsck is simply taking the right time to finish.
--
ply_boot_client_flush() does
Plymouth is *not* ready. My Dell Mini 9 is essentially unusable (takes over 40
mins to fsck) unless I disable the quiet option at boot.
This is a serious unfixed problem to leave in the final release and is likely
to stop unsophisticated new users dead.
--
ply_boot_client_flush() does not read
I get this on a Dell Mini 9; the slowdown starts at 70% and gets even
worse at 90%,to the point that I eventually just shut down the machine.
The odd behaviour from 70% on has been present ever since I installed
the beta. Initially there was a complete hang at 70%; this was fixed
(#554737)
Bootchart logs
** Attachment added: mini-lucid-20100429-1.tgz
http://launchpadlibrarian.net/46344607/mini-lucid-20100429-1.tgz
--
fsck at bootstrap is too slow
https://bugs.launchpad.net/bugs/571707
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Yes indeed; looks as if this might well be the same bug. Good news, if
so, as there seems to be some progress being made.
--
Lucid boot failed to complete after fsck
https://bugs.launchpad.net/bugs/554079
You received this bug notification because you are a member of Ubuntu
Bugs, which is
This is probably the same as bug #554079
--
ply_boot_client_flush() does not read replies (plymouth stuck during/after
filesystem check or error)
https://bugs.launchpad.net/bugs/554737
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Same thing on a Dell M1330, sticking at 90%.
This is a real showstopper bug.
--
Lucid boot failed to complete after fsck
https://bugs.launchpad.net/bugs/554079
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Same for me on a Dell MIni 9; whether forced or natural, fsck hangs at
70% for a short time, then advances to 71% and the system promptly
freezes altogether.
If I shut down with the off button and boot into the recovery mode of
the same (latest) kernel, fsck completes and is followed by a lot of
Could this be related?
https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/487744
I don't know when this mountall fix was released - might it have broken
something?
I'm pretty sure this behaviour is something that started within the last few
days.
--
Lucid boot failed to complete after
Sometime over the past few days a problem very like this has newly
arisen on my system
https://bugs.launchpad.net/ubuntu/+source/sysvinit/+bug/554079
Could this be a further problem with mountall?
--
Scheduled fsck during boot unresponsive and inactive for a very long time at
90%, making the
I was mistaken - bug *is* fixed by the latest update.
Many thanks to everybody
--
Application Indicator causes Gnome Power fallback icon to show/hide on each
refresh
https://bugs.launchpad.net/bugs/529052
You received this bug notification because you are a member of Ubuntu
Bugs, which is
This does not in fact solve the original bug report, which relates to
the battery icon appearing and disappearing in the notification area
(rather than anything to do with indicator-application.)
This is *not* fixed by the recent change to indicator-application.
--
Application Indicator causes
The lastest upgrade of mouseemu fixed this.
--
[i945gme] Keyboard not working after upgrade to Lucid
https://bugs.launchpad.net/bugs/513932
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
It was the same for me; however downgrading to 0.60-2 works.
Find shared-mime-info_0.60-2_i386.deb, if it's not still around eg
http://ftp.us.debian.org/debian/pool/main/s/shared-mime-info/shared-
mime-info_0.60-2_i386.deb
and do
sudo dpkg -i shared-mime-info_0.60-2_i386.deb
--
It's all fine now: just apply the latest upgrades, which include the
glib2.0 fix
--
shared-mime-info-0.7-ubuntu1 update is broken
https://bugs.launchpad.net/bugs/444962
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
Recent updates seem to have fixed this on my system.
--
Alias in ~/.fonts.conf ignored
https://bugs.launchpad.net/bugs/440903
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
27 matches
Mail list logo
