#Can't run KF after closing [Fixed]

1 messages · Page 1 of 1 (latest)

lyric hare
#

Hey. I tried to run KF after closing it and with many times it's impossible to open it.

But after adding killall mesquite to the top of the scriptlet file (before wait 2), KF can always be launched 🤔

5.18.2 FW

spice pumice
#

hmm

#

seems to be an error with caching

#

if it is just you, leave the killall mesquite beforehand

#

also, please try replacing mesquite with "KindleForge"

#

see if that fixes

timber belfry
#

hmmmm

#

caching issue yeah

#

does a reboot fix it?

#

i could add it for everyone but i feel like it would slow it down

#

(that's why the process stays open by default)

#

kinda strange

#

added bugs & kindleforge tags

lyric hare
#

I tried to fix it myself.

I deleted:
/mnt/us/documents/KindleForge* /mnt/us/.active_content_sandbox/KindleForge /var/local/mesquite/xyz.penguins184.kindleforge /var/local/mesquite/KindleForge

After restarting, I reinstalled version 4.0.7 and now it works fine.

Installation also works, because killall mesquite wasn't a good idea after all, it blocked the installation completely 😄

#

Can't run KF after closing [Fixed]

timber belfry
#

peak!!

lyric hare
#

Okay, I know why this happened. I was playing around with this:

# Last opened: 0
# Modify the “Last opened” comment to set the current time.
# This is to put the script at the top of the list of recently read books.
timestamp=$(date +%s)
sed -i “s/^# Recently opened:.*/# Recently opened: $timestamp/” “$0”

I forgot to revert to original file (I tought I did it lol haha)

But thanks to this, I managed to make the kindlefetch position change after use.
Try it if you want @timber belfry 🙂

timber belfry
#

and above

#

(sh_integration has been rewritten in C)

lyric hare
timber belfry
#

weird

#

2.2.5 came out

timber belfry
#

2.2.2a had the change

#

2.2.3 is chattr changes

#

2.2.4 fixes 2.2.2a which is broken

#

2.2.5 fixes PATH stuff

lyric hare
timber belfry
#

o

#

ig they didn't build clint's changes then

#

the next one should fix PATH stuff ig?

#

2.2.4 does fix a sh_it memleak tho

#

2.2.2a didn't work for me either, nor did 2.2.3, 2.2.4 fixed it

lyric hare
#

Edit: 2.2.4 sucks, going back to 2.2.1 😄

spice pumice
#

fair

#

i’m on winterbreak

timber belfry
timber belfry
#

idk why

lyric hare
timber belfry
#

leet reference or something

#

i think it looks kinda ugly

#

weird last use updates for me

#

the editing thing was an issue for below 2.2.4 in my case, do you use the run hotfix booklet? is there another memleak or something

#

like deletion creation and modification was severely delayed

lyric hare