Koreader running on Kobos (all of them, hopefully!) - Page 158

Frenzie · 08-26-2015, 02:58 AM

Quote:

Originally Posted by WolfBack

Franzie, the code above do the trick as I wanted!
I apply that code in all of my books with calibre and the Koreader sees the non-breaking space (nbsp) as scene break!
Thank you again!

You're welcome.

barobach_so · 09-03-2015, 05:33 PM

hi

my koreader crashes when going to SD card. it exits and come back to Nickel when I tap sd on screen
but it can read files onmain memory

Anyone can help me to solve this ?

its last version (released 20150808)

tshering · 09-03-2015, 07:33 PM

I wonder whether this is intended behaviour. When turning on Wifi connection, I see

Spoiler:

And after exiting koreader, I still see:

Spoiler:

This makes it impossible to umount properly the user partition.

Ken Maltby · 09-03-2015, 09:04 PM

Quote:

Originally Posted by tshering

I wonder whether this is intended behaviour. When turning on Wifi connection, I see

Spoiler:

And after exiting koreader, I still see:

Spoiler:

This makes it impossible to umount properly the user partition.

If you are looking at this issue, I can understand using lsof (to see a list of open files and the process ids using them) but why grep fonts? Wouldn't grep fonts get that list anyway?

Luck;
Ken

Perhaps we could add:

exec 3<&-

after the call to reader.lua ? It should change your 2nd lsof results, wouldn't it?

NiLuJe · 09-03-2015, 10:52 PM

@tshering: A copy of the corresponding full process tree might be helpful here, none of those things should have a hold on fonts (besides luajit with koreader running, of course ;p).

tshering · 09-04-2015, 06:30 AM

Quote:

Originally Posted by Ken Maltby

If you are looking at this issue, I can understand using lsof (to see a list of open files and the process ids using them) but why grep fonts?

I did it only to shorten the list.

Quote:

Originally Posted by Ken Maltby

Wouldn't grep fonts get that list anyway?

Against which list would I have to run grep?

Quote:

Originally Posted by Ken Maltby

Perhaps we could add:

exec 3<&-

after the call to reader.lua ? It should change your 2nd lsof results, wouldn't it?

I am not sure about that.
Maybe it would be possible to prevent this to start with. I have no idea how the opening of font files is related to wifi.
As for now, I thought of killing the process(es) that keep the files opened.

tshering · 09-04-2015, 06:47 AM

Quote:

Originally Posted by NiLuJe

@tshering: A copy of the corresponding full process tree might be helpful here, none of those things should have a hold on fonts (besides luajit with koreader running, of course ;p).

If by "full process tree" you mean something different than lsof without grep, please tell me the exact command.

I add some listings.

turning wifi on in KSM, then lsof
launching Koreader, then lsof
exiting from Koreader, then lsof (no open font files)

Spoiler:

turning wifi off in KSM, then lsof
launching Koreader, turning wifi on in Koreader, then lsof
exiting from Koreader, then lsof (several open font files)

Spoiler:

PeterT · 09-04-2015, 08:47 AM

Maybe a

Code:

ps

or

Code:

ps -t

Ken Maltby · 09-04-2015, 09:48 AM

Quote:

Originally Posted by tshering

I am not sure about that.
Maybe it would be possible to prevent this to start with. I have no idea how the opening of font files is related to wifi.
As for now, I thought of killing the process(es) that keep the files opened.

I wonder how the processes impacted would react to having their open files closed? If there would be a log entry made? Would something show on errout? Would the process terminate? Just a thought, you guys are the ones that really understand this stuff, I haven't messed with Unix/Linux in over twenty years. I like the way this modern use of scripting, allows for trying out dumb ideas, right inside working code.

Luck;
Ken

NiLuJe · 09-04-2015, 11:15 AM

@tshering: yep, what @PeterT said

. I'm partial to ps faux, but I don't remember if the Kobo has a fully-fledged psutils with all the right flags, so just something basic with the full commandlines in tree form should help pinpointing where those processes come from

.

tshering · 09-04-2015, 11:17 AM

Quote:

Originally Posted by PeterT

Maybe a

Code:

ps

or

Code:

ps -t

Right, ps was the first thing I was thinking about. But then I thought what will NiLuJe learn by it, that he does not already know. Reading his post again, I try to understand that he wants to have both ps, and lsof of the same situation.

Spoiler:

Edit: -T is the only available option to ps.

NiLuJe · 09-04-2015, 01:29 PM

@tshering: Huh, no idea why the hell would wpa-supplicant and its children would inherit/have a hold on these fonts... Does this happen with KOReader's builtin network-manager? If not, it might be a quirk of how this is done in KSM? But if it's done before KOReader is even started, why the hell is it even looking at KOReader stuff?

Although, given the PIDs in your last post, wpa-supplicant appears to have been started *after* KOReader, so I'm confused. [EDIT: Because that's what you did, I got confused with the spoiler blocks ;p]

EDIT: Okay, yeah, the Kobo only has busybox ps*. pstree might be more readable, although I personally kind of hate how it presents stuff, but, still, better than nothing ;p.

PeterT · 09-04-2015, 01:38 PM

I wonder if the wpa-supplicant might be related to the active telnet session and possibly the spawning of child processes for commands entered at the command prompt?

NiLuJe · 09-04-2015, 01:42 PM

@PeterT: Nah, wpa-supplicant is started from ~nickel/KOReader/KSM when enabling WiFi

.

On a sidenote, nickel seems to be using dhcpcd instead of udhcpc nowadays, but that's another thing entierely ^^.

But it definitely shouldn't have a hold on fonts, FWIW, this is with nickel's/the system's wpa-supplicant call:

Code:

/mnt/onboard/.niluje/usbnet/bin/lsof +c0 | ag wpa                                                                                                                     
dhcpcd-dbus           2153            root    9u     unix 0x9eda6d00      0t0 13428 /tmp/dhcpcd-dbus-wpa-2153.0 type=DGRAM
dhcpcd-dbus           2153            root   10u     unix 0x9eda6680      0t0 13430 /tmp/dhcpcd-dbus-wpa-2153.1 type=DGRAM
wpa_supplicant        2160            root  cwd       DIR      179,1     1024     2 /
wpa_supplicant        2160            root  rtd       DIR      179,1     1024     2 /
wpa_supplicant        2160            root  txt       REG      179,1   385184 32819 /bin/wpa_supplicant
wpa_supplicant        2160            root  mem       REG      179,1    97580   934 /lib/ld-2.11.1.so
wpa_supplicant        2160            root  mem       REG      179,1   266828   672 /usr/lib/libssl.so.0.9.8
wpa_supplicant        2160            root  mem       REG      179,1  1138080   666 /usr/lib/libcrypto.so.0.9.8
wpa_supplicant        2160            root  mem       REG      179,1     9816   788 /lib/libdl-2.11.1.so
wpa_supplicant        2160            root  mem       REG      179,1   881932   752 /lib/libc-2.11.1.so
wpa_supplicant        2160            root    0u      CHR        1,3      0t0   145 /dev/null
wpa_supplicant        2160            root    1u      CHR        1,3      0t0   145 /dev/null
wpa_supplicant        2160            root    2u      CHR        1,3      0t0   145 /dev/null
wpa_supplicant        2160            root    3u     unix 0x9eda6b60      0t0 13392 type=DGRAM
wpa_supplicant        2160            root    4u     sock        0,5      0t0 13393 can't identify protocol
wpa_supplicant        2160            root    5u  netlink                 0t0 13394 ROUTE
wpa_supplicant        2160            root    6u     pack      13398      0t0 34958 type=SOCK_DGRAM
wpa_supplicant        2160            root    7u     unix 0x9eda7520      0t0 13400 /var/run/wpa_supplicant/eth0 type=DGRAM

NiLuJe · 09-04-2015, 01:59 PM

Meh, it's probably system() and no CLOEXEC biting us in the ass, we're inheriting open fds.

The simplest workaround I can think of is killing WiFi when quitting KOReader, which seems a bit harsh, but would solve this.

(In fact, the startup script does just that when started manually w/ nickel running).

Doing it the right way would mean using CLOEXEC everywhere, which might be easier said than done, and would break compatibility with Linux < 2.6.23 (which, granted, only applies to legacy (non-touch) Kindles and possibly the first gen Kobos).

EDIT²: FreeType should default to using CLOEXEC... If it doesn't, that's probably a ToolChain issue. I don't remember which TC the buildbot is using for the Kobos, I'll launch a build with my own just for shit 'n giggles...

09-03-2015, 07:33 PM	#2358
tshering Wizard Posts: 3,489 Karma: 2914715 Join Date: Jun 2012 Device: kobo touch	I wonder whether this is intended behaviour. When turning on Wifi connection, I see Spoiler: (none) login: root [root@(none) ~]# lsof \| grep font 9509 /mnt/onboard/.adds/koreader/luajit /mnt/onboard/.adds/koreader/font s/noto/NotoSans-Regular.ttf 9509 /mnt/onboard/.adds/koreader/luajit /mnt/onboard/.adds/koreader/font s/noto/NotoSans-Regular.ttf 9509 /mnt/onboard/.adds/koreader/luajit /mnt/onboard/.adds/koreader/font s/droid/DroidSansMono.ttf 9509 /mnt/onboard/.adds/koreader/luajit /mnt/onboard/.adds/koreader/font s/noto/NotoSans-Regular.ttf 9509 /mnt/onboard/.adds/koreader/luajit /mnt/onboard/.adds/koreader/font s/noto/NotoSans-Bold.ttf 9509 /mnt/onboard/.adds/koreader/luajit /mnt/onboard/.adds/koreader/font s/noto/NotoSans-Regular.ttf 9509 /mnt/onboard/.adds/koreader/luajit /mnt/onboard/.adds/koreader/font s/droid/DroidSansMono.ttf 9509 /mnt/onboard/.adds/koreader/luajit /mnt/onboard/.adds/koreader/font s/droid/DroidSansMono.ttf 9509 /mnt/onboard/.adds/koreader/luajit /mnt/onboard/.adds/koreader/font s/noto/NotoSans-Regular.ttf 9509 /mnt/onboard/.adds/koreader/luajit /mnt/onboard/.adds/koreader/font s/noto/NotoSans-Bold.ttf 9509 /mnt/onboard/.adds/koreader/luajit /mnt/onboard/.adds/koreader/font s/noto/NotoSans-Regular.ttf 9509 /mnt/onboard/.adds/koreader/luajit /mnt/onboard/.adds/koreader/font s/noto/NotoSans-Bold.ttf 9509 /mnt/onboard/.adds/koreader/luajit /mnt/onboard/.adds/koreader/font s/noto/NotoSans-Regular.ttf 9544 /bin/wpa_supplicant /mnt/onboard/.adds/koreader/fonts/noto/NotoSans- Regular.ttf 9544 /bin/wpa_supplicant /mnt/onboard/.adds/koreader/fonts/noto/NotoSans- Regular.ttf 9544 /bin/wpa_supplicant /mnt/onboard/.adds/koreader/fonts/droid/DroidSan sMono.ttf 9544 /bin/wpa_supplicant /mnt/onboard/.adds/koreader/fonts/noto/NotoSans- Regular.ttf 9544 /bin/wpa_supplicant /mnt/onboard/.adds/koreader/fonts/noto/NotoSans- Bold.ttf 9544 /bin/wpa_supplicant /mnt/onboard/.adds/koreader/fonts/noto/NotoSans- Regular.ttf 9544 /bin/wpa_supplicant /mnt/onboard/.adds/koreader/fonts/droid/DroidSan sMono.ttf 9544 /bin/wpa_supplicant /mnt/onboard/.adds/koreader/fonts/droid/DroidSan sMono.ttf 9544 /bin/wpa_supplicant /mnt/onboard/.adds/koreader/fonts/noto/NotoSans- Regular.ttf 9544 /bin/wpa_supplicant /mnt/onboard/.adds/koreader/fonts/noto/NotoSans- Bold.ttf 9544 /bin/wpa_supplicant /mnt/onboard/.adds/koreader/fonts/noto/NotoSans- Regular.ttf 9544 /bin/wpa_supplicant /mnt/onboard/.adds/koreader/fonts/noto/NotoSans- Bold.ttf 9544 /bin/wpa_supplicant /mnt/onboard/.adds/koreader/fonts/noto/NotoSans- Regular.ttf 9551 /bin/busybox /mnt/onboard/.adds/koreader/fonts/noto/NotoSans-Regular. ttf 9551 /bin/busybox /mnt/onboard/.adds/koreader/fonts/noto/NotoSans-Regular. ttf 9551 /bin/busybox /mnt/onboard/.adds/koreader/fonts/droid/DroidSansMono.tt f 9551 /bin/busybox /mnt/onboard/.adds/koreader/fonts/noto/NotoSans-Regular. ttf 9551 /bin/busybox /mnt/onboard/.adds/koreader/fonts/noto/NotoSans-Bold.ttf 9551 /bin/busybox /mnt/onboard/.adds/koreader/fonts/noto/NotoSans-Regular. ttf 9551 /bin/busybox /mnt/onboard/.adds/koreader/fonts/droid/DroidSansMono.tt f 9551 /bin/busybox /mnt/onboard/.adds/koreader/fonts/droid/DroidSansMono.tt f 9551 /bin/busybox /mnt/onboard/.adds/koreader/fonts/noto/NotoSans-Regular. ttf 9551 /bin/busybox /mnt/onboard/.adds/koreader/fonts/noto/NotoSans-Bold.ttf 9551 /bin/busybox /mnt/onboard/.adds/koreader/fonts/noto/NotoSans-Regular. ttf 9551 /bin/busybox /mnt/onboard/.adds/koreader/fonts/noto/NotoSans-Bold.ttf 9551 /bin/busybox /mnt/onboard/.adds/koreader/fonts/noto/NotoSans-Regular. ttf 9560 /bin/busybox /mnt/onboard/.adds/koreader/fonts/noto/NotoSans-Regular. ttf 9560 /bin/busybox /mnt/onboard/.adds/koreader/fonts/noto/NotoSans-Regular. ttf 9560 /bin/busybox /mnt/onboard/.adds/koreader/fonts/droid/DroidSansMono.tt f 9560 /bin/busybox /mnt/onboard/.adds/koreader/fonts/noto/NotoSans-Regular. ttf 9560 /bin/busybox /mnt/onboard/.adds/koreader/fonts/noto/NotoSans-Bold.ttf 9560 /bin/busybox /mnt/onboard/.adds/koreader/fonts/noto/NotoSans-Regular. ttf 9560 /bin/busybox /mnt/onboard/.adds/koreader/fonts/droid/DroidSansMono.tt f 9560 /bin/busybox /mnt/onboard/.adds/koreader/fonts/droid/DroidSansMono.tt f 9560 /bin/busybox /mnt/onboard/.adds/koreader/fonts/noto/NotoSans-Regular. ttf 9560 /bin/busybox /mnt/onboard/.adds/koreader/fonts/noto/NotoSans-Bold.ttf 9560 /bin/busybox /mnt/onboard/.adds/koreader/fonts/noto/NotoSans-Regular. ttf 9560 /bin/busybox /mnt/onboard/.adds/koreader/fonts/noto/NotoSans-Bold.ttf 9560 /bin/busybox /mnt/onboard/.adds/koreader/fonts/noto/NotoSans-Regular. ttf [root@(none) ~]# And after exiting koreader, I still see: Spoiler: (none) login: root [root@(none) ~]# lsof \| grep fonts 9551 /bin/busybox /mnt/onboard/.adds/koreader/fonts/noto/NotoSans-Regular. ttf 9551 /bin/busybox /mnt/onboard/.adds/koreader/fonts/noto/NotoSans-Regular. ttf 9551 /bin/busybox /mnt/onboard/.adds/koreader/fonts/droid/DroidSansMono.tt f 9551 /bin/busybox /mnt/onboard/.adds/koreader/fonts/noto/NotoSans-Regular. ttf 9551 /bin/busybox /mnt/onboard/.adds/koreader/fonts/noto/NotoSans-Bold.ttf 9551 /bin/busybox /mnt/onboard/.adds/koreader/fonts/noto/NotoSans-Regular. ttf 9551 /bin/busybox /mnt/onboard/.adds/koreader/fonts/droid/DroidSansMono.tt f 9551 /bin/busybox /mnt/onboard/.adds/koreader/fonts/droid/DroidSansMono.tt f 9551 /bin/busybox /mnt/onboard/.adds/koreader/fonts/noto/NotoSans-Regular. ttf 9551 /bin/busybox /mnt/onboard/.adds/koreader/fonts/noto/NotoSans-Bold.ttf 9551 /bin/busybox /mnt/onboard/.adds/koreader/fonts/noto/NotoSans-Regular. ttf 9551 /bin/busybox /mnt/onboard/.adds/koreader/fonts/noto/NotoSans-Bold.ttf 9551 /bin/busybox /mnt/onboard/.adds/koreader/fonts/noto/NotoSans-Regular. ttf 9560 /bin/busybox /mnt/onboard/.adds/koreader/fonts/noto/NotoSans-Regular. ttf 9560 /bin/busybox /mnt/onboard/.adds/koreader/fonts/noto/NotoSans-Regular. ttf 9560 /bin/busybox /mnt/onboard/.adds/koreader/fonts/droid/DroidSansMono.tt f 9560 /bin/busybox /mnt/onboard/.adds/koreader/fonts/noto/NotoSans-Regular. ttf 9560 /bin/busybox /mnt/onboard/.adds/koreader/fonts/noto/NotoSans-Bold.ttf 9560 /bin/busybox /mnt/onboard/.adds/koreader/fonts/noto/NotoSans-Regular. ttf 9560 /bin/busybox /mnt/onboard/.adds/koreader/fonts/droid/DroidSansMono.tt f 9560 /bin/busybox /mnt/onboard/.adds/koreader/fonts/droid/DroidSansMono.tt f 9560 /bin/busybox /mnt/onboard/.adds/koreader/fonts/noto/NotoSans-Regular. ttf 9560 /bin/busybox /mnt/onboard/.adds/koreader/fonts/noto/NotoSans-Bold.ttf 9560 /bin/busybox /mnt/onboard/.adds/koreader/fonts/noto/NotoSans-Regular. ttf 9560 /bin/busybox /mnt/onboard/.adds/koreader/fonts/noto/NotoSans-Bold.ttf 9560 /bin/busybox /mnt/onboard/.adds/koreader/fonts/noto/NotoSans-Regular. ttf [root@(none) ~]# This makes it impossible to umount properly the user partition.

09-04-2015, 08:47 AM	#2363
PeterT Grand Sorcerer Posts: 13,534 Karma: 78910202 Join Date: Nov 2007 Location: Toronto Device: Libra H2O, Libra Colour	Maybe a Code: ps or Code: ps -t

09-04-2015, 01:29 PM	#2367
NiLuJe BLAM! Posts: 13,506 Karma: 26047202 Join Date: Jun 2010 Location: Paris, France Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E	@tshering: Huh, no idea why the hell would wpa-supplicant and its children would inherit/have a hold on these fonts... Does this happen with KOReader's builtin network-manager? If not, it might be a quirk of how this is done in KSM? But if it's done before KOReader is even started, why the hell is it even looking at KOReader stuff? Although, given the PIDs in your last post, wpa-supplicant appears to have been started after KOReader, so I'm confused. [EDIT: Because that's what you did, I got confused with the spoiler blocks ;p] EDIT: Okay, yeah, the Kobo only has busybox ps. pstree* might be more readable, although I personally kind of hate how it presents stuff, but, still, better than nothing ;p. Last edited by NiLuJe; 09-04-2015 at 02:03 PM.

09-04-2015, 01:59 PM	#2370
NiLuJe BLAM! Posts: 13,506 Karma: 26047202 Join Date: Jun 2010 Location: Paris, France Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E	Meh, it's probably system() and no CLOEXEC biting us in the ass, we're inheriting open fds. The simplest workaround I can think of is killing WiFi when quitting KOReader, which seems a bit harsh, but would solve this. (In fact, the startup script does just that when started manually w/ nickel running). Doing it the right way would mean using CLOEXEC everywhere, which might be easier said than done, and would break compatibility with Linux < 2.6.23 (which, granted, only applies to legacy (non-touch) Kindles and possibly the first gen Kobos). EDIT²: FreeType should default to using CLOEXEC... If it doesn't, that's probably a ToolChain issue. I don't remember which TC the buildbot is using for the Kobos, I'll launch a build with my own just for shit 'n giggles... Last edited by NiLuJe; 09-04-2015 at 02:10 PM.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
KOReader: a document reader for PDF, DJVU, EPUB, FB2, HTML, ... (GPLv3)	hawhill	Kindle Developer's Corner	1289	04-07-2025 10:18 AM
Touch Using two Kobos	tkavan	Kobo Reader	4	06-23-2017 02:47 AM
2 kobos at once	tsarinaerika	Kobo Reader	14	06-03-2013 04:13 AM
Syncing between two Kobos	fx3000se	Kobo Reader	4	01-24-2013 02:10 PM
2 kobos 1 account	retired05	Kobo Reader	9	05-05-2012 08:25 AM

09-03-2015, 05:33 PM	#2357
barobach_so Connoisseur Posts: 76 Karma: 25460 Join Date: Feb 2015 Device: kobo h2o	hi my koreader crashes when going to SD card. it exits and come back to Nickel when I tap sd on screen but it can read files onmain memory Anyone can help me to solve this ? its last version (released 20150808)

09-03-2015, 10:52 PM	#2360
NiLuJe BLAM! Posts: 13,506 Karma: 26047202 Join Date: Jun 2010 Location: Paris, France Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E	@tshering: A copy of the corresponding full process tree might be helpful here, none of those things should have a hold on fonts (besides luajit with koreader running, of course ;p).

09-04-2015, 11:15 AM	#2365
NiLuJe BLAM! Posts: 13,506 Karma: 26047202 Join Date: Jun 2010 Location: Paris, France Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E	@tshering: yep, what @PeterT said . I'm partial to ps faux, but I don't remember if the Kobo has a fully-fledged psutils with all the right flags, so just something basic with the full commandlines in tree form should help pinpointing where those processes come from .

09-04-2015, 01:38 PM	#2368
PeterT Grand Sorcerer Posts: 13,534 Karma: 78910202 Join Date: Nov 2007 Location: Toronto Device: Libra H2O, Libra Colour	I wonder if the wpa-supplicant might be related to the active telnet session and possibly the spawning of child processes for commands entered at the command prompt?

Advert

Advert