One-Click Install Packages for KOReader & Plato - Page 65

NiLuJe · 07-27-2023, 10:37 PM

First: You have a bad cable (or a bad port). Fix that first, as you're bound to have way more issues down the line if you keep hoping for the best with a flaky connection

.

Second: you're doing something wrong. Or macOS is doing something wrong for you; check the mac-specific mentions on those first two post

.

gtim108 · 07-31-2023, 06:48 PM

Quote:

Originally Posted by NiLuJe

c.f., https://github.com/koreader/koreader/issues/10408

I'm waiting on Kobo to actually release the kernel sources. As an actual owner of the device, feel free to poke Kobo CS about that.

JFYI, Kobo pushed the new commit into git -

Added Elipsa 2E
kernel tar split to fall under GH file size limit.

https://github.com/kobolabs/Kobo-Rea...ef712b27e2a49e

NiLuJe · 07-31-2023, 06:51 PM

Quote:

Originally Posted by gtim108

JFYI, Kobo pushed the new commit into git -

Added Elipsa 2E
kernel tar split to fall under GH file size limit.

https://github.com/kobolabs/Kobo-Rea...ef712b27e2a49e

Hadn't noticed.

gtim108 · 07-31-2023, 07:15 PM

Quote:

Originally Posted by NiLuJe

Hadn't noticed.

Stupid me :-)

Thanks!

lee.hauser · 08-09-2023, 11:13 PM

Just did the 1 click install on my new Libra 2. The install instructions resulted in a few minutes of uncertainly on my Mac, running Sonoma Public Beta 1. The right-click->Open resulted in a list of applications to open it with; I tried Terminal, and it just flashed by (there was no gatekeeper).

After trying this a couple of times, I decided to put my vast command line knowledge (ha ha) to use, opened Terminal, typed "./install.command" and everything went as expected.

JSWolf · 08-10-2023, 10:58 AM

Quote:

Originally Posted by lee.hauser

Just did the 1 click install on my new Libra 2. The install instructions resulted in a few minutes of uncertainly on my Mac, running Sonoma Public Beta 1. The right-click->Open resulted in a list of applications to open it with; I tried Terminal, and it just flashed by (there was no gatekeeper).

After trying this a couple of times, I decided to put my vast command line knowledge (ha ha) to use, opened Terminal, typed "./install.command" and everything went as expected.

I would not run a MacOS beta. The release versions are bad enough.

lee.hauser · 08-11-2023, 01:15 AM

Quote:

Originally Posted by JSWolf

I would not run a MacOS beta. The release versions are bad enough.

The only reason I mention my OS is for troubleshooting purposes. I’d be happy to hear relevant feedback if there is any.

JSWolf · 08-11-2023, 12:08 PM

Quote:

Originally Posted by lee.hauser

The only reason I mention my OS is for troubleshooting purposes. I’d be happy to hear relevant feedback if there is any.

The problem is that errors don't get fixed if your OS is not a release version qas the problem could be related to the OS. Try a release OS and if you have the same problem, then post about it.

NiLuJe · 08-11-2023, 03:01 PM

Apple may have finally won its crusade against letting people run "untrusted" code on their OS, even in its most benign fashion. Yay Apple. >_<".

Snark aside, I haven't followed the macOS changes on that front, but, yes, either it's a beta issue (god knows their betas are usually *very* beta), or it's indeed a result of their "security" crackdown efforts.

lee.hauser · 08-18-2023, 09:27 AM

Quote:

Originally Posted by JSWolf

The problem is that errors don't get fixed if your OS is not a release version qas the problem could be related to the OS. Try a release OS and if you have the same problem, then post about it.

Of course, Beta versions of OS software are often problematic. That's exactly why I mentioned I was running a beta, trying to signal to others running the beta and installing this software might run into this problem as well. What I was responding to was the wholly irrelevant comment on MacOS.

lee.hauser · 08-18-2023, 09:30 AM

Quote:

Originally Posted by NiLuJe

Apple may have finally won its crusade against letting people run "untrusted" code on their OS, even in its most benign fashion. Yay Apple. >_<".

Snark aside, I haven't followed the macOS changes on that front, but, yes, either it's a beta issue (god knows their betas are usually *very* beta), or it's indeed a result of their "security" crackdown efforts.

This time the installer worked just fine, just not quite as expected. I've encountered very, very few programs I haven't been able to run on any version of MacOS since BigSur.

JSWolf · 08-19-2023, 05:28 AM

Quote:

Originally Posted by lee.hauser

Of course, Beta versions of OS software are often problematic. That's exactly why I mentioned I was running a beta, trying to signal to others running the beta and installing this software might run into this problem as well. What I was responding to was the wholly irrelevant comment on MacOS.

What I'm meaning is don't report any bugs while running a beta OS unless it's easily reproducible on a non-beta OS.

DNSB · 09-12-2023, 08:58 PM

Quote:

Originally Posted by JSWolf

What I'm meaning is don't report any bugs while running a beta OS unless it's easily reproducible on a non-beta OS.

I tend to report them as a heads up that there may be issues when the beta goes RTM.

Dragen · 09-26-2023, 07:35 PM

One-click script (with KOReader) doesn't seem to be enabling the hidden sysfiles ignore.

NiLuJe · 09-27-2023, 12:54 PM

@Dragen:

Quote:

Originally Posted by NiLuJe

NOTE: Pertaining to that particular bit of trickery, I would *strongly* recommend that you do all this right after a clean, full reboot of your device!

And only trigger the USBMS session from within the Home screen, apparently there are still fd leaks lurking in Nickel otherwise...

08-09-2023, 11:13 PM	#965
lee.hauser Enthusiast Posts: 30 Karma: 10 Join Date: Sep 2010 Location: Seattle area Device: Kobo Libra 2	Just did the 1 click install on my new Libra 2. The install instructions resulted in a few minutes of uncertainly on my Mac, running Sonoma Public Beta 1. The right-click->Open resulted in a list of applications to open it with; I tried Terminal, and it just flashed by (there was no gatekeeper). After trying this a couple of times, I decided to put my vast command line knowledge (ha ha) to use, opened Terminal, typed "./install.command" and everything went as expected. Last edited by lee.hauser; 08-09-2023 at 11:16 PM.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Aura How to install ksm and koreader	mhss	Kobo Reader	0	01-17-2018 07:45 PM
Koreader could not be opened by click an epub file on the books list	johnleo	KOReader	4	12-11-2017 07:57 AM
Cannot install custom update packages via MRPI	anunay	Kindle Developer's Corner	9	02-09-2017 07:46 AM
Kobo-how to install koreader	sahbi	KOReader	22	01-02-2016 03:49 PM
Koreader install help	mrmojorizing	Kobo Developer's Corner	3	09-29-2014 01:24 PM

07-27-2023, 10:37 PM	#961
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	First: You have a bad cable (or a bad port). Fix that first, as you're bound to have way more issues down the line if you keep hoping for the best with a flaky connection . Second: you're doing something wrong. Or macOS is doing something wrong for you; check the mac-specific mentions on those first two post .

08-11-2023, 03:01 PM	#969
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	Apple may have finally won its crusade against letting people run "untrusted" code on their OS, even in its most benign fashion. Yay Apple. >_<". Snark aside, I haven't followed the macOS changes on that front, but, yes, either it's a beta issue (god knows their betas are usually very beta), or it's indeed a result of their "security" crackdown efforts.

09-26-2023, 07:35 PM	#974
Dragen Junior Member Posts: 9 Karma: 10 Join Date: Feb 2012 Device: Kindle	One-click script (with KOReader) doesn't seem to be enabling the hidden sysfiles ignore.