Thread: Libra 2 Very unstable Libra 2 with 4.33.19611
View Single Post
Old 06-26-2022, 10:23 PM   #58
davidfor
Grand Sorcerer
davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.
 
Posts: 24,905
Karma: 47303824
Join Date: Jul 2011
Location: Sydney, Australia
Device: Kobo:Touch,Glo, AuraH2O, GloHD,AuraONE, ClaraHD, Libra H2O; tolinoepos
Quote:
Originally Posted by Rkob View Post
I noticed that the device generated some stack traces (.kobo/stack_*.log), which indicate Segmentation Faults (SIGSEGV) in the nickel process.
For the record, if possible, the device will upload the stack trace logs to Kobo. They do look at them. This should happen if you have the option turned on to share data (last option on the "Energy saving and privacy" page of the settings), the device is signed into a Kobo account (ie. not in sideloaded mode or using DB hack to bypass registration) and WiFi is on.

And I did talk to someone at Kobo about this. He reminded me of the above. Their problem at the moment is that the information they have is basically, "it crashed". They have not seen any steps to reproduce it yet. At the moment, all they can see is, "it crashes".
davidfor is offline   Reply With Quote