View Single Post
Old 07-30-2022, 05:24 PM   #2
pazos
cosiņeiro
pazos ought to be getting tired of karma fortunes by now.pazos ought to be getting tired of karma fortunes by now.pazos ought to be getting tired of karma fortunes by now.pazos ought to be getting tired of karma fortunes by now.pazos ought to be getting tired of karma fortunes by now.pazos ought to be getting tired of karma fortunes by now.pazos ought to be getting tired of karma fortunes by now.pazos ought to be getting tired of karma fortunes by now.pazos ought to be getting tired of karma fortunes by now.pazos ought to be getting tired of karma fortunes by now.pazos ought to be getting tired of karma fortunes by now.
 
Posts: 1,406
Karma: 2451781
Join Date: Apr 2014
Device: BQ Cervantes 4
That's not an error.

The terminal plugin does a runtime check and fails on all pocketbooks. Then it disables itself and thus is not available for you to use.

You can disable that specific plugin if you want to get rid of those specific lines on your crash.log.

Which leads me to the next implicit Q/A:

"crash.log" is a file that's ALWAYS created by KO. It can contain crashes or not, but the name is what it is. I assume you enabled "all file associations" in KO. That includes log files and that's why you get a new document on your home after each KO run. That's not going to change unless you disable the association of log files. Please do that.

About wifi issues. Please try to reproduce on last nightly. Stable releases are just frozen nightlies at a point of time where no big code changes happened recently. You're safe installing a nightly on your device.

If you can reproduce on latest nightly please open a bug on github following the bug template. There's a contributor there doing an awesome job maintaining the PB platform. We can ping him there easily and keep track of the ticket, so other users can follow up and/or help resolving.

Last edited by pazos; 07-30-2022 at 05:27 PM.
pazos is offline   Reply With Quote