Thanks for all your suggestions. I'm aware that I can run any browser (or aardict, or anything) outside of nickel, for instance in a Debian chroot. However, for convenience, I would like to be able to run my browser and access Wikipedia (which is an HTTP server running on localhost, this part of the setup works) from within nickel.
Thanks to BWinmill for pointing me to fickel. It's not hard to write a custom version of fickel which returns scan results and make the Kobo try to connect to a non-existant network. However, I'm still stuck. When the Kobo tries to connect to this fake network, it seems (from snooping on /tmp/nickel-hardware-status) that nickel expects the following messages:
Code:
network deconfig
network bound 192.168.100.48
However, writing those messages by hand if the network doesn't actually exist results in a "Something went wrong..." message from nickel. I tried setting the address of eth0 with ifconfig to match the fake value I write in /tmp/nickel-hardware-status, but the same error appears. However, writing the exact same messages by hand does not make nickel complain if the network actually exists. I tried stracing nickel to see what it does, but to no avail.
We're almost there; do you have any idea of what nickel may be checking when it is supposed to be connected? The error message is instant, so I very much doubt that it is anything really network-related (like pinging an address).
Thanks again for your answers!
Lucas Malor: Is there a way to call the Kobo web browser from the command line?
[Another idea: is it possible to run the Kobo web browser manually from Kobotweaks, bypassing nickel's check?]