I can confirm that the .desktop file as installed from the repos lacks the full path to bnf.

It is not lacking anything - icons placed in standard directories where hildon expect them, doesn't need to be provided with full path.

Thanks for confirming, though

/Estel

Hello, it is not about icons but about the path to the binary.

Yes, it was not about icons (where full path is not only not needed, but must not be set, to my experience).

But I have to apologize, Estel.
Of course a sudo in front of command does not require full path!

But I had similar once and thought it was that (not having root rights); and it was late...

As I just greyed out my nonsense in former post, it was not fully nonsense ;j My script is in totally different location!

karlitos
can you run
sudo bnf
from terminal as user (not as root)?
Please open a new x-term and directly type
sudo bnf

If that starts the window or black screen, then give us output of
lsmod | grep bq27

@Estel
Trying to calibrate my battery using your bqCapacity post.

Have you forgotten to mention ./i2cget needs chmod as well as bq27200.sh?

Good catch. I need to refine instructions anyway - i2cget is available from i2c-tool package for ages (in fact, was in time of writing initial tutorial...), so messing with placing i2cget manually isn't needed. bq27200.sh definitely needs chmod +x it.

Considering, that bq27200.sh is sitting in some random server for ages, I guess I will refine it a little, ask ShadowJK for permission and put it as part of bnf package - it will make things much easier.

/Estel

Hi Estel

Any idea why sudo bnf after reflashing my devica and clean install CSSU fthumb sudo bnf granted me with

Error: Could not set address to 0x55: Device or resource busy
/usr/sbin/bnf: line 44: arithmetic syntax error

tnx

Looks like something is occupying i2cbus - I bet, that bq27x00_battery module is loaded at startup. check your blacklist and enforced modules list (refer to kernel-power thread, it was discussed there, "somewhere" - I don't remember locations now, sadly ).

// edit

For quick confirm/deny, try (as root) modprobe -r bq27x00_battery - if it accepts command without errors, and then, bnf starts to work, you can be sure it is it.

Yep, exactly that is my assumption/explanation also

@Estel
Maybe you meant that from here on and ff?
Can not remember in kernel thread, but maybe also there...


--edit
and I remembered why bnf called from menu icon may sometimes not display any output, but shows black screen

Yea

BTW, don't get too 1337 with blacklisting bq27x00_battery - do it using a way, that you will be able to revert easily. Current progress on bme replacement (via re-written bq2415_battery and bq27x00_battery modules) mean, that after some time, you *will* want to use "reborn" bq27x00_battery, as module for exporting things for userland bme replacement bits.

After all, talking directly to i2c is always - more or less "dirty hack", and with dawn of proper BME replacement, it's going to get obsolete. While it will - for sure - mean availability of nicely integrated, GUI battery meters, it doesn't mean BNF will go away, though - for those hardy pack of people, that still like it, I will for sure release version that uses bq27x00_battery instead of i2cget, as soon as BME replacement using kernel module will be available.

/Estel