Nickel indexing KOReader icons after FW 4.17 update #5430
Comments
|
for what it's worth, i just upgraded to the latest release, and nickel "lost" a bunch of those files, but still found files like: dang... there are actually ~120 of those files according to nickel. on the upside, this is making me use koreader much more because it obviously doesn't suffer from this problem. and i must say you folks rock: it's a great product and I thank you for your great work! :) |
|
Way ahead of you ;). (In case it wasn't clear, that was a hint that using the install scripts would have prevented the issue ;)). |
|
I updated the wiki to mention this, for the unwary who'd still want to do it manually. |
You're on a version that doesn't yet correctly detect point releases. That's usually fine but coincidentally not this month. |
|
Note that tweaking the setting after the fact (i.e., for someone who updated the FW on an existing KOReader installation, doing it at any later time than the first USBMS session) will cause Nickel to delete the files in question when it purges them from its database (as part of the sidecar cleanup). Which means you'll have to reinstall KOReader, because we kinda need those icons ;p. Which also means that if you have other, custom stuff in hidden folders, well, back them up somewhere first ;). TL;DR: Important to do it right the first time around ;). Also, fucking up the regex can and will blacklist onboard entirely, which leads to... fun results :D. I, err, may have "tried" this a couple times ;p. |
|
Btw, aren't there "only" ~60-70 icons and logos? |
Oops! Thanks for the heads up, I guess I need to reinstall all that stuff now. Ouch!
Yeah well, I guess I had more than just koreader in there... there's some vlavasoft things and so on... go figure. i hope KSM survived... |
|
FWIW, it seems like the
BTW, I think it's really awesome just stepped in with a solution with ten minutes of me opening this bug report. It's really great, thanks! |
|
Note that nickel only scans for content indexing after an USBMS session (and not at startup), which is both what gives us a window to set this after an update, and what makes this slightly more obscure if you miss that window. Plus, there's no easy way (short of tailing the syslog) to know when the process is entirely done (there's no "importing content" screen for the purge process). c.f, this post for more details with a similar issue ;). |
NiLuJe
changed the title
|
Keeping this open (at least for a while) for documentation purposes ;). |
folks might want to "pin" this issue here so people see it first as well. that way people will see if even if it's closed. it's kind of a FAQ of sort. :) |
|
@anarcat: Good idea, thanks! (I was thoroughly unaware of that feature ;p). Does it also still appear in the autocomplete, even if it's closed, that way? |
... in the autocomplete? not sure what you mean there. but yes, i think it shows up as pinned even if it's closed... |
|
The thing that auto-suggests already opened issues as you type the title of a new one (may have been/still be in beta ;p) ;). |
|
i think closed issues appear in autocomplete, yes. i don't think pinning has anything to do without it, however. |
|
What's the solution to this? I see whole bunch of appbar.*.png in book list. |
|
That would be actually reading the links in my original answer for context? Which ultimately leads you here. |
|
Closing this issue as it was fixed outside KO and its not something that KO needs to fix. I will leave the issue pinned! |
|
Do we need this issue pinned? The last entry is really over a year old. |
|
I'll unpin it, bit I'll blame you if a duplicate pops up next week. |
|
It did come up this week in a discussion ;). |
Issue
During the last Nickel upgrade, something changed and now all the little icons, files and logos shipped with koreader show up in the Nickel database. It's pretty nasty because there are a lot of those tiny things and they make Nickel almost unusable.
Steps to reproduce
Not exactly sure: I just did the latest official upgrades from Kobo and, during its next rescan, it found all that garbage.
Now, I guess I'm running a very old version of koreader and should upgrade, but for some reason, the OTA upgrades don't work, so I'm stuck with this. I also suspect this problem also happens in later version, unless the way to deploy koreader radically changed since I last checked.
Thanks for any advice!
The text was updated successfully, but these errors were encountered: