MobileRead Forums - View Single Post - Libra 2 Very unstable Libra 2 with 4.33.19611

Rkob · 06-15-2022, 04:35 AM

Hi,

I got a new Libra 2 last week. I really like the device, but it has been very unstable and crashes often, to the point of being barely usable.

When I intially started the device, it ran 4.30.18838.
I played a bit with the settings, logged in to Overdrive and Pocket, tried to read a few articles and a few pages from an Overdrive book. Everything seemed to work fine.
I got a pop-up asking me to update, I accepted, and the device restarted with 4.33.19611.
After this point, the device became very unstable:

Many freezes followed by restarts (even with very light use or when I did not touch anything at all)
A restart while sleeping

I tried a factory reset, but it didn't help.
I also did a manual reset yesterday, and observed the same as during the initial "out of the box" start :

Device came up with 4.30.18838 after the reset. Everything seemed stable
Got an upgrade pop-up which I cancelled ("Upgrade Later" or something)
Used the device a bit more without problem
Let the device alone for a couple of hours
When I took it again, it had upgraded to 4.33.19611 and now crashes constantly.

I noticed that the device generated some stack traces (.kobo/stack_*.log), which indicate Segmentation Faults (SIGSEGV) in the nickel process.

I would really appreciate some help/guidance from this forum! 😊

Can I safely assume that the HW is fine, since the device seems OK with 4.30.18838?
I was considering exchanging it, but it may not help if the crashes are due to a weird combination of firmware + specific settings / actions.
What could I do to investigate this further?
I could probably try a downgrade to 4.30.18838 again, to see if the device is stable there. But I guess I would need to patch the firmware ("Always show confirmation dialog before upgrading") to avoid an automatic upgrade as soon as I look the other way?
Other ideas of things I could try, to confirm that this is not a HW issue?
I cannot do much with the stack traces without the source code. What is the best way to send to the Kobo dev. team?
I saw a mention of the help@kobobooks.com address on an old thread. Is it still active and monitored by someone from Kobo? Would it help to send my traces there?

Regards,
--
Rkob

06-15-2022, 04:35 AM	#1
Rkob Reader Posts: 14 Karma: 10 Join Date: Jun 2022 Device: Kobo Libra 2	Very unstable Libra 2 with 4.33.19611 Hi, I got a new Libra 2 last week. I really like the device, but it has been very unstable and crashes often, to the point of being barely usable. When I intially started the device, it ran 4.30.18838. I played a bit with the settings, logged in to Overdrive and Pocket, tried to read a few articles and a few pages from an Overdrive book. Everything seemed to work fine. I got a pop-up asking me to update, I accepted, and the device restarted with 4.33.19611. After this point, the device became very unstable: Many freezes followed by restarts (even with very light use or when I did not touch anything at all) A restart while sleeping I tried a factory reset, but it didn't help. I also did a manual reset yesterday, and observed the same as during the initial "out of the box" start : Device came up with 4.30.18838 after the reset. Everything seemed stable Got an upgrade pop-up which I cancelled ("Upgrade Later" or something) Used the device a bit more without problem Let the device alone for a couple of hours When I took it again, it had upgraded to 4.33.19611 and now crashes constantly. I noticed that the device generated some stack traces (.kobo/stack_.log), which indicate Segmentation Faults (SIGSEGV) in the nickel* process. I would really appreciate some help/guidance from this forum! 😊 Can I safely assume that the HW is fine, since the device seems OK with 4.30.18838? I was considering exchanging it, but it may not help if the crashes are due to a weird combination of firmware + specific settings / actions. What could I do to investigate this further? I could probably try a downgrade to 4.30.18838 again, to see if the device is stable there. But I guess I would need to patch the firmware ("Always show confirmation dialog before upgrading") to avoid an automatic upgrade as soon as I look the other way? Other ideas of things I could try, to confirm that this is not a HW issue? I cannot do much with the stack traces without the source code. What is the best way to send to the Kobo dev. team? I saw a mention of the help@kobobooks.com address on an old thread. Is it still active and monitored by someone from Kobo? Would it help to send my traces there? Regards, -- Rkob