Martin, for whatever it's worth, the following upower bug I filed might
also be related - since an idle nexus 7 has a longer battery life than
20 hours, one would hope.
https://bugs.freedesktop.org/show_bug.cgi?id=60110
Cheers,
Alex
** Bug watch added: freedesktop.org Bugzilla #60110
https://
(NOTE that I updated the patch for charge_full and charge_full_design -
yesterday I forgot to commit one last diff before generating the patch).
All of these patches have now been sent upstream as well. The android
one for energy_now has been updated with all the other extra
measurements.
https:/
The patch for charge_full and charge_full_design
** Patch removed:
"0001-power-bq27541_driver-Add-charge_full-charge_full_des.patch"
https://bugs.launchpad.net/ubuntu-nexus7/+bug/1093543/+attachment/3508110/+files/0001-power-bq27541_driver-Add-charge_full-charge_full_des.patch
** Patch added
Adds charge_full and charge_full_design nodes/measurements.
** Patch added:
"0001-power-bq27541_driver-Add-charge_full-charge_full_des.patch"
https://bugs.launchpad.net/ubuntu-nexus7/+bug/1093543/+attachment/3508110/+files/0001-power-bq27541_driver-Add-charge_full-charge_full_des.patch
--
Y
PS: note that the upower patch is against the upstream version, so it
may or may not apply cleanly to the version ubuntu has. Nonetheless, it
should be straight forward to apply the patch manually - it's just 1
line.
--
You received this bug notification because you are a member of Ubuntu
Bugs, w
Fixes units of energy_now (10mWh -> mWh)
** Patch added: "0001-power-bq27541_battery-fix-units-of-energy_now.patch"
https://bugs.launchpad.net/ubuntu-nexus7/+bug/1093543/+attachment/3508103/+files/0001-power-bq27541_battery-fix-units-of-energy_now.patch
--
You received this bug notification
Well, here go 3 more patches 1 for upower, 2 for the kernel.
The upower one just fixes a logic bug that will allow the design
capacity to be read via charge, even though the current energy is read
directly as energy.
The kernel patches are:
1) Fix a bug in a previous patch - even though the d
Attached is a kernel patch to provide current_now. It may help with the
upower issues, as it should result in upower using a different method to
calculate the remaining time, etc.
Cheers,
Alex
** Patch added: "0001-power-bq27541_battery-Provide-current_now.patch"
https://bugs.launchpad.net/ub
Actually I don't think the energy patch will change much. Fact is that,
since we don't provide current_now nor power_now, upower will do,
/* the hardware reporting failed -- try to calculate this */
if (energy_rate < 0.01)
energy_rate = up_device_supply_calculate_ra
While gema's issue (which was dealing with raw sysfs read data) is gone
with this patch, I suspect your issue might well be related to upower.
Did you try with the second patch as well? The "Provide energy
measurement" ? A quick skim through the relevant upower code would
indicate that it does try
The issue here is a bug in the bq27541 fuel gauge driver. The
get_property() function is not thread-safe, but reentry is possible in
several different scenarios.
The attached patch fixes this issue by protecting get_property() via a
mutex.
Below is the patch commit message, for clarity:
* Curre
Manually changing from grub-efi to grub-pc "solves" the issue - in that
at least grub works now.
While I do have an EFI "bios", it emulates the classic BIOS behaviour,
so I'm not sure why ubuntu outsmarted itself by picking the EFI grub.
--
You received this bug notification because you are a me
I've attached the lspci -vv output as well as a tarball of most of
/var/log/installer (except the partman log) if it helps.The motherboard
is an Asus M5A97.
Using ubuntu-bug or apport is a no-go because of the requirement of a
full-blown X and GTK environment - it'd be a pretty great idea if
ubun
** Attachment added: "lspci.txt"
https://bugs.launchpad.net/ubuntu/+source/grub/+bug/934614/+attachment/2887916/+files/lspci.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/934614
Title:
reins
Bug also affects me. I installed Ubuntu 12.04 amd64 (beta 1) using the
alternate installer. After rebooting, grub failed miserably with the
aforementioned error.
root@ubuntu:/# dpkg -l | grep -i grub
ii grub-common1.99-17ubuntu1
GRand Uni
is this huge gaping security hole going to be fixed anytime soon?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/876626
Title:
Unlocking the second crypto disk (/home) echos password on console
To m
FWIW, this issue seems to be with plymouth, as expected, not with
cryptsetup. It shouldn't be too hard to find the root cause with
plymouth tracing enabled.
Cheers,
Alex
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.lau
This also affects the first prompt, and there are further issues - the
"press s to skip mounting or m for manual recovery" message appears on
top of the password prompt. You can get around it with pressing esc
several times, but you end up with the same issue of it echoing the
passphrase.
See http
Turns out this last issue is because Ubuntu doesn't set the interface to auto
and dhcp in /etc/network/interfaces anymore. It must have been the case in the
past, because all of this originally worked without modifying the
aforementioned file. In any case, adding
auto eth0
iface eth0 inet dhcp
Actually, turns out that I still have the same problem using IPs instead of
hostnames. I'm using these entries now:
192.168.0.70:/secure/alex /home/alex/secure nfs
defaults,rw,exec,user,nobootwait0 0
192.168.0.70:/data /home/alex/data
Clint, thanks for showing interest in this, much appreciated. It is
really annoying when the system doesn't boot without user intervention
:)
It wasn't my intention to use the same title, actually; was more of a
coincidence/happy accident. New title sounds just fine.
Thanks,
Alex
--
You receive
Clint, thanks for the feedback. I've opened a new bug report at [1] and
subscribed you as you indicated.
Thanks,
Alex
[1]: https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/765545
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/765545
Title:
nfs mounts in fstab are mounted before network is up
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/ma
Public bug reported:
Binary package hint: mountall
I have the following two lines in fstab:
nasi.local:/secure/alex /home/alex/secure nfs
defaults,rw,exec,user,nobootwait0 0
nasi.local:/data/home/alex/data nfs
defaults,rw,exec,
Public bug reported:
Binary package hint: mountall
NFS fstab entries such as the following ones, even with the nobootwait
flag set, halt the boot and cause plymouth(?) to ask for user input.
This is completely unacceptable as it makes it impossible to have a
system boot up without intervention. E
So how is this bug "incomplete"? The issue is fairly obvious; dhclient
ISN'T being run before NFS mounts, as running it manually from the mount
recovery shell fixes the problem.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://b
** Changed in: mountall (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/688878
Title:
sshfs volume "is not ready yet or not present"
--
ubuntu-bugs mailing lis
t Byrum" wrote:
> bwalex: Are you saying that the boot is actually waiting for these
> mounts to timeout with nobootwait? That would be a pretty serious
> problem, and not related to this bug.
>
> The error message is a result of the fact that mountall just tries to
> mount *a
Sorry for the comment flood; but I forgot to mention that breaking to
manual mounting (by pressing M), starting dhclient manually and then
continuing the boot process is a workaround.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
htt
Also note that this happens reliably on every boot, so a race is
unlikely. I also don't have /var as a separate mountpoint.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/586022
Title:
nfs mounts hap
Well, I got the same issue since about January on Maverick, now also on
Natty. 'nobootwait' doesn't change a thing, it still waits on the nfs
mounts
Regards,
Alex
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launch
Well, that bug still happens, for example when pressing Alt+F2. It's
neither fixed nor invalid.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/741674
Title:
compiz crashed with SIGSEGV in g_closure_i
This bug also happened on Ubuntu Natty with today's packages. Just using
the default ubuntu desktop (compiz + unity)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/533670
Title:
wncksyncdaemon crashe
Public bug reported:
Binary package hint: mountall
The new behaviour in mountall to stop the boot process and ask for user
input when a completely non-critical volume is a really bad idea. Any
user with some experience will have fstab entries that might not be
there yet at boot and it's completel
For the volume you can change the line that reads volume<<3 to volume*7.
notify_notification_set_hint_int32(not, "value", volume<<3);
I normally use shifts wherever possible, but obviously LSL by 3 multiplies by
8, and given a maximum raw volume of 14, that goes a bit above the maximum.
Nonethel
Johannes,
yes, I'm a C programmer but the reason why I wrote the workaround was to avoid
having to spend a whole afternoon fixing GNU/Linux bugs. Plus, I'm a *BSD
developer and hence don't know my way round linux' weird ways of doing things
(e.g. hal).
I might take a look at it, but in my opi
Fabio,
the solution of adding the hotkey event has the exact problem Ubuntu was trying
to avoid: controlling the sound or brightness twice per click: one in hardware
and one in software. You'll notice that the sound control will jump twice as
much. At half the slider you'll have no sound whatso
I've updated the program to be able to deal with the new kind of
brightness /proc node in acpi/video/VID...
You can find it under http://bwalexh.wordpress.com/2009/05/03/new-
ubuntu-thinkpad-notification-program/
If for some reason you don't have /proc/acpi/video/VID but rather
/proc/acpi/video/
Hi,
Now I've changed the program to be able to use /proc/acpi/ibm/brightness. If it
doesn't exist, it just won't notify of brightness changes.
This will obviously not take take of brightness on the X301 or similar laptops
but I'll probably add the relevant code for the X301 and others that have i
well, /proc/acpi/ibm/brightness definitely does NOT exist on a T60, so
if someone please can show me a FULL cat /proc/acpi/ibm/brightness I can
change my program.
--
No notification when sliding audio volume, muting volume, sliding LCD
brightness on X31, X32, T60, R50e, T42, R52
https://bugs.lau
Zoltan;
if I get the information on the exact output of a cat on that /proc/ node I can
change my program to also take into account brightness changes (on a non T60
thinkpad).
But as I said, for me to do that, I need some real info on how that info looks,
or is it the same as on T60?
--
No no
I forgot to say that I've only tried this script on my own ThinkPad,
which is a T60. For some reason brightness control works fine for me, so
my C program will only take care of the sound notification.
--
No notification when sliding audio volume, muting volume, sliding LCD
brightness on X31, X3
Hi!
I've written a small C program which pops up notifications about changes in the
sound. It has two major advantages over the script here:
1) much less CPU intensive as it doesn't require executing external
applications and so on.
2) it detaches itself automatically from the controlling termin
43 matches
Mail list logo
