Aura ONE Kobo Aura One reboots when deleting epubs

[AbominableDavid]

I've done some searching and haven't found anything - hopefully one of you can help me.

Sometime in the last few months my Kobo Aura One started rebooting when I tried to delete an epub. It happens every time I try to delete a file - the Kobo reboots and the file never gets deleted.

I can remove the files from the device when it's connected by USB, but they still show up under My Books.

I dealt with the problem for a while, figuring I just needed a factory reset, but I did the factory reset a few days ago, loaded up some books, tried to delete one, and it rebooted again.

I load books with Calibre and they're mostly non-DRM epub files.

[crane3]

I have the same problem with the KA1 LE. I have been told that it is because of a "scrambled" database; NOT TRUE.

I have factory reset the KA1 LE & the 'removed' books remain. However, after reloading the books from Calibre, I side-loaded some Light Novels from my computer. Interesting that a "removed" book from the side-loaded books shows up even tho the book does not show up in the author sort, only in the 'books' sorted list. Same problem with a book loaded from Calibre.

Looks to me the sqlite is not getting deleted when doing a factory reset. Can I delete the sqlite using my pc before doing a factory reset? Buggy book management and/or "factory reset".

On top of which, after I do a "factory reset" & KA1 LE is ready, I get a popup that say my Overdrive book has expired. The library book was returned many days past so where is the msg coming from??? Methinks the database still thinks that I have the library book even tho the books was checked out using my galaxy tab pro! Probably an Overdrive sync problem.

[DNSB]

Originally Posted by crane3

I have the same problem with the KA1 LE. I have been told that it is because of a "scrambled" database; NOT TRUE.

I have factory reset the KA1 LE & the 'removed' books remain. However, after reloading the books from Calibre, I side-loaded some Light Novels from my computer. Interesting that a "removed" book from the side-loaded books shows up even tho the book does not show up in the author sort, only in the 'books' sorted list. Same problem with a book loaded from Calibre.

Looks to me the sqlite is not getting deleted when doing a factory reset. Can I delete the sqlite using my pc before doing a factory reset? Buggy book management and/or "factory reset".

On top of which, after I do a "factory reset" & KA1 LE is ready, I get a popup that say my Overdrive book has expired. The library book was returned many days past so where is the msg coming from??? Methinks the database still thinks that I have the library book even tho the books was checked out using my galaxy tab pro! Probably an Overdrive sync problem.

How are you factory resetting your KA1 LE -- are you using factory reset from the GUI or are you using the manual factory reset procedure? Is your KA1 going through the initial setup procedure in the same way as you had to initially set up your KA1 when you unboxed it?

Whenever I've done a factory reset, any books on the internal storage, which is all the KA1 has, have been deleted and the database has no books imported.

[robko]

I agree with David. For some reason you're not accomplishing a true factory reset from what you're describing. A reboot reset maybe, but not a full reset.
And signing out of your Kobo account on your device and signing back in should also reset the database.

[crane3]

Originally Posted by DNSB

How are you factory resetting your KA1 LE -- are you using factory reset from the GUI or are you using the manual factory reset procedure? Is your KA1 going through the initial setup procedure in the same way as you had to initially set up your KA1 when you unboxed it?

Whenever I've done a factory reset, any books on the internal storage, which is all the KA1 has, have been deleted and the database has no books imported.

I am using the Gui reset in the settings for "factory reset". From your statement, it looks like the GUI "factory reset" is not a true reset. Will have to check out the manual factory reset after finishing reading my current book.

After the fake GUI factory reset, I still have to go thru the setup like after unboxing with selecting the language, getting wifi setup, logging to the account, waiting for firmware updating, seeing a dialog about searching wifi network to join(?) then some other stuff & a dialogue claiming my Overdrive book has expired. The part about Overdrive book expiring is different from after unboxing as I think that the msg was that the library will expire in 2 days.

So is it "safe" to delete the SQLite before doing the factory reset? Also saw 2 sqlites in .kobo, koreader & book; the book.sqlite is much smaller than the koreader.lite which I think is for all the books?

Don't remember if stated, but the "removed" book were removed prior to doing the factory reset. The side-load of books did not include the "removed book" which makes it curious where the ghost book came from and/or that the sqlite did not get reestablished with the re-loading of the books after the "factory reset".

[davidfor]

Originally Posted by crane3

I am using the Gui reset in the settings for "factory reset". From your statement, it looks like the GUI "factory reset" is not a true reset. Will have to check out the manual factory reset after finishing reading my current book.

The factory reset from the Settings is supposed to be a real factory reset. But, there have been some reports where it didn't work. From memory, when it didn't work, it restarted the device, but didn't show all the resetting screens.

Also, the question is asked because we have plenty of people report doing a factory reset and then when questioned, it turns out they just pressed the pinhole reset button. There is enough uncertainty, and your experience is unusual enough, to want to check exactly what you did.

After the fake GUI factory reset, I still have to go thru the setup like after unboxing with selecting the language, getting wifi setup, logging to the account, waiting for firmware updating, seeing a dialog about searching wifi network to join(?) then some other stuff & a dialogue claiming my Overdrive book has expired. The part about Overdrive book expiring is different from after unboxing as I think that the msg was that the library will expire in 2 days.

That sounds like a full factory reset, but it could be the same as logging out of the device. After this, did the device show the importing screen? The factory reset should format the book partition. If it didn't, any sideloaded books on the device will be imported after logging into the Kobo account. But, if the format happened, there won't be any sideloaded books and hence no import step.

So is it "safe" to delete the SQLite before doing the factory reset? Also saw 2 sqlites in .kobo, koreader & book; the book.sqlite is much smaller than the koreader.lite which I think is for all the books?

It is safe to delete the database files, but, when you do, you will automatically be taken through the setup. And this wouldn't have been way to try to fix the problem when it first occurred.

Don't remember if stated, but the "removed" book were removed prior to doing the factory reset. The side-load of books did not include the "removed book" which makes it curious where the ghost book came from and/or that the sqlite did not get reestablished with the re-loading of the books after the "factory reset".

If you connect the device to a PC after the factory reset, there should be three directories: .kobo, .kobo-images and .adobe-digital-editions. There might be a "Digital Editions" directory, but I'm pretty sure that isn't created until an epub is opened. The timestamp on the directories should be when the device finished the setup. I'm sure there shouldn't be anything else. If there is, it means the factory reset didn't happen. Or my memory is wrong.

When you have had this problem, have you connected to the PC and checked if the file was there or not? I'm also not sure whether you are saying the book never disappears from the library list, or that it disappears by comes back later. I also don't remember if you said before what happens if you delete the book using calibre, or simply delete the book from the device when it is connected to the PC. The behaviour when doing these things might give a clue as to what is going on.

[crane3]

When I do a "factory reset", the files are not there as KA1 LE says that there are not any books, which is true. I have not backed up anything to the cloud as I will not be using the cloud. The reset is supposed to give me a virgin reader.

I did a manual factory reset as per the user guide & the problem book still comes up; & this time one of the light novel books did not show up on the book list but is seen using the usb connection & file explorer!

Doing the KA1 remove just reboots; the book never disappear. Do not know how the book resurrects after a reset since it is not loaded. I never use Calibre to delete a book from the device nor do I delete a book from the device when connected to Calibre.

I found a problem in that it KA1 changes or truncates the title if it is considered "too long"; the database setup get confused or mangled.

e.g. "Risou no Himo Seikatsu Volume 05.epub" is listed on the KA1 as "Risou no Himo Seikatsu V05" in the book list. but "Risou no Himo Seikatsu Volume 06.epub" got listed as "Risou no Himo Seikatsu Volume 05.epub"

For "13 Mahouka Koukou no Rettousei #13 - Steeplechase Chapter (B-T)(Roah)-v2.epub", KA1 book list truncates to Mahouka Koukou no Rettousei #13.epub"

Looks to me like KA1 has a limitation on file name size. Will have to do another factory reset & not load my light novels as the KA1 is unable deal with long file names like an Android tablet. Or perhaps it is just the nickel app.

There is a bug with the forums as if one takes too long entering a reply, one is evidently logged out as the msg say I am not authorized to enter a reply or anything. I forgot to set the login to do the "remember me" thing.

[DNSB]

Originally Posted by crane3

I found a problem in that it KA1 changes or truncates the title if it is considered "too long"; the database setup get confused or mangled.

e.g. "Risou no Himo Seikatsu Volume 05.epub" is listed on the KA1 as "Risou no Himo Seikatsu V05" in the book list. but "Risou no Himo Seikatsu Volume 06.epub" got listed as "Risou no Himo Seikatsu Volume 05.epub"

For "13 Mahouka Koukou no Rettousei #13 - Steeplechase Chapter (B-T)(Roah)-v2.epub", KA1 book list truncates to Mahouka Koukou no Rettousei #13.epub"

Looks to me like KA1 has a limitation on file name size. Will have to do another factory reset & not load my light novels as the KA1 is unable deal with long file names like an Android tablet. Or perhaps it is just the nickel app.

Hmmm... the filename limit is 255 bytes on a FAT32 partition. Since you are copying the files over, I would suspect that the filename munging is from your computer. I just tested on my Clara HD since it was handy and copied a file with a 196 character filename (plus the . and extension) and it was not truncated.

However what your Kobo uses in the book list is not related to the filename. It is derived from the metadata embedded in the epub file you are transferring over to your device. The 240 character filename file that I transferred over was correctly named Out of the Vortex with the author name showing as Steve White and the series showing as Her Majesty’s American 1.5 (the series took a second connection to update the metadata after the book had been imported into the database) in My Books.

Check out calibre for correcting metadata along with either Sigil or calibre's editor using Flightcrew (Sigil, epub2) or epubcheck (Sigil, calibre editor, epub2 or epub3) to locate and correct errors in the structure and content of your ebooks before sending ebooks to your Kobo. Or even use the QualityCheck plugin for calibre to do some basic checks.

[davidfor]

Originally Posted by crane3

When I do a "factory reset", the files are not there as KA1 LE says that there are not any books, which is true. I have not backed up anything to the cloud as I will not be using the cloud. The reset is supposed to give me a virgin reader.

I did a manual factory reset as per the user guide & the problem book still comes up; & this time one of the light novel books did not show up on the book list but is seen using the usb connection & file explorer!

So, a factory reset and when you connected to the PC, the book was still there? In that case, the factory reset didn't happen properly. And that is wrong.

Doing the KA1 remove just reboots; the book never disappear. Do not know how the book resurrects after a reset since it is not loaded. I never use Calibre to delete a book from the device nor do I delete a book from the device when connected to Calibre.

I found a problem in that it KA1 changes or truncates the title if it is considered "too long"; the database setup get confused or mangled.

e.g. "Risou no Himo Seikatsu Volume 05.epub" is listed on the KA1 as "Risou no Himo Seikatsu V05" in the book list. but "Risou no Himo Seikatsu Volume 06.epub" got listed as "Risou no Himo Seikatsu Volume 05.epub"

For "13 Mahouka Koukou no Rettousei #13 - Steeplechase Chapter (B-T)(Roah)-v2.epub", KA1 book list truncates to Mahouka Koukou no Rettousei #13.epub"

For epubs, the device reads the metadata from inside the book. It will only use the file names if there is no metadata in the book. If you are getting those names in the books lists, then there is something wrong with the metadata in the books. Either it is missing, or it set incorrectly. When you send a book from calibre, the metadata should be updated to whatever is in the calibre library. This can be disabled,

Looks to me like KA1 has a limitation on file name size. Will have to do another factory reset & not load my light novels as the KA1 is unable deal with long file names like an Android tablet. Or perhaps it is just the nickel app.

The file name limitation is the same as the path limitation for the file system in use. In this case, the files system is FAT32 and the name length is 260 characters or something like that.

Calibre will massage the file names and paths to keep well within this limit. This is taking into account the directories in use, so it can give much shorter file names. But, that does not affect the metadata within the book.

The file name massaging that calibre does is to also remove characters that might be a problem. It will replace these with an underscore. The "#" in the above file name makes me uncomfortable, so I have just done a test on my Glo HD to check it is handled properly.

There is a bug with the forums as if one takes too long entering a reply, one is evidently logged out as the msg say I am not authorized to enter a reply or anything. I forgot to set the login to do the "remember me" thing.

If I'm taking along time to write a response, I hit the preview post occasionally to reset the timer.


The only thing I can think to suggest at this point is to format the book partition using Windows. This would normally be something I would never suggest, but it might work. Connect the device, and format the partition that is presented to the PC. The format needs to be FAT32 and use all the available space. Do a full format, not a quick format. When that is done, eject the device. It will then take you through the setup. After that, sideload a book and see what happens when you delete it.

If, after that, it still isn't working, then I think it is warranty replacement time. The last thought is that the storage is failing and needs to be fixed. And that can only be done by replacing the device. Hopefully it is still covered.

[davidfor]

Originally Posted by DNSB

Hmmm... the filename limit is 255 bytes on a FAT32 partition. Since you are copying the files over, I would suspect that the filename munging is from your computer. I just tested on my Clara HD since it was handy and copied a file with a 196 character filename (plus the . and extension) and it was not truncated.

And as soon as I read this I did remember a problem with long names. While the path name limit is 256 or 260 (can't remember where the extra 4 goes), the practical limit for a book is much shorter. This is because of the generated images. These are created with the full path of the book plus an identifier and an extension. And they go in a subdirectory. Because of this, the KoboTouch driver uses 185 characters as the maximum path length. There is also the files in "Digital Editions", but I thing this length covers them.

It's been ages since I tried this, but some strange things do happen when that books path length is to long. And it is because the path for the cover images is to long. I don't remember exactly what happened and would need to experiment.

[Uschiekid]

Originally Posted by crane3

I have the same problem with the KA1 LE. I have been told that it is because of a "scrambled" database; NOT TRUE.

I have factory reset the KA1 LE & the 'removed' books remain. However, after reloading the books from Calibre, I side-loaded some Light Novels from my computer. Interesting that a "removed" book from the side-loaded books shows up even tho the book does not show up in the author sort, only in the 'books' sorted list. Same problem with a book loaded from Calibre.

Looks to me the sqlite is not getting deleted when doing a factory reset. Can I delete the sqlite using my pc before doing a factory reset? Buggy book management and/or "factory reset".

On top of which, after I do a "factory reset" & KA1 LE is ready, I get a popup that say my Overdrive book has expired. The library book was returned many days past so where is the msg coming from??? Methinks the database still thinks that I have the library book even tho the books was checked out using my galaxy tab pro! Probably an Overdrive sync problem.

Was this returned overdrive book borrowed using the Aura One (ie using the integrated overdrive system) or was it sideloaded using ADE?

If it was borrowed on the Aura One, I wonder if it has to do with the fact that when a library book gets returned, a preview of the same book automatically replaces the returned book.

Maybe all this is irrelevant, but if the book you are trying to delete was a previously borrowed book, it could be why it's popping back on a "virgin" ereader (and why it's linked to your account in a way that isn't typical of your calibre based epub-library).

Just thought it might be worth asking, as none of the people working to solve this with you mentioned overdrive. Probably not important.

[crane3]

1. The Overdrive book was borrowed with another device, a tablet. I think that the library card id is synced with my devices that use the same library card.

2. The offending book is NOT in Calibre. The book was just copied to the KA1 using win10's file explorer. The real file names were not munged on the KA1, so the problem is the database extract of the metadata. I am not about to edit the metadata as they are light novels on the web; nor am I going to tell/post that the translators did a bad job as there are no problems with the books on my android tablets using moon+reader pro.

3. Just did a delete of the ".kobo" directory & went thru the mini(?) setup. The offending book remain in the book list!

4. Instead of immediately deleting the book, I just tried to read the book & the book came up; checked the number of pages & find that it is about right. Now, the embarrassing part is that it looks like the metadata did not get changed when the subsequent chapters were added using an online merge so that the title that included the word "incomplete" remained to muddle my mind! Calibre Companion on the tablets do not have any meta data problems nor any problem with my Boox C67ML e-ink reader.

5. Mystery partially solved! What remains now is the rebooting of the KA1 when deleting/removing a book which doesn't get removed but comes up with "not authorized to read DRM" on a book that does not have DRM.

[davidfor]

Originally Posted by crane3

2. The offending book is NOT in Calibre. The book was just copied to the KA1 using win10's file explorer. The real file names were not munged on the KA1, so the problem is the database extract of the metadata. I am not about to edit the metadata as they are light novels on the web; nor am I going to tell/post that the translators did a bad job as there are no problems with the books on my android tablets using moon+reader pro.

3. Just did a delete of the ".kobo" directory & went thru the mini(?) setup. The offending book remain in the book list!

When you did this, was the book file still on the device? Clearing the .kobo directory removes the database and books from Kobo. But, sideloaded books are still on the device. And when you finish the setup, they will be imported and hence in the book list. That is working as designed.

4. Instead of immediately deleting the book, I just tried to read the book & the book came up; checked the number of pages & find that it is about right. Now, the embarrassing part is that it looks like the metadata did not get changed when the subsequent chapters were added using an online merge so that the title that included the word "incomplete" remained to muddle my mind! Calibre Companion on the tablets do not have any meta data problems nor any problem with my Boox C67ML e-ink reader.

But, based on what you have said, there are different versions of the book involve, so it is hard to compare them. At the least, the version Calibre Companion is seeing is not the same as the version on your Aura ONE. The Calibre Companion only talks to calibre, and it uses whatever is in the calibre library for metadata. You said you manually put the book on the Aura ONE, so it hasn't been in calibre and hence hasn't had any metadata changes that might have taken place.

5. Mystery partially solved! What remains now is the rebooting of the KA1 when deleting/removing a book which doesn't get removed but comes up with "not authorized to read DRM" on a book that does not have DRM.

I don't remember you mentioning the DRM message. Is this happening when you try to read the book you tried to delete after the restart? If so, I have seen something like that. From memory, it means the book has been partly removed from the database. The main entry will still be there, but the rest are probably gone. But, it has been a long time since I've seen this and I think only in beta firmware. That doesn't help you much, but it gives me something to think about to look for.

And something that I've completely forgotten to ask about, is are there any stack logs in the .kobo directory? These have the name "stack_0n.log" (n is a number) and can be produced when there is an error like you describe. If there are any, it can give a clue as to exactly where the error is.

And an even dumber sounding question is, how big are these books? Most importantly, how many chapters do they have? I've just realised that the "light novels" you are talking about could be getting long. There is a chance that the delete is triggering a sickel reboot. If the behaviour when this happens is that you start the delete, it sits there for about 60 seconds, the light goes off and then the reboot happens, it might be sickel triggering a reboot because something seems to be hung. And if it is, then it explains the rest of the behaviour.

Which leads to another question: Is it all books? Is it just these light novels or everything? Maybe we should do a controlled test. Grab an epub from the MR library here, sideload that and then delete it. These books are generally in good condition and have no errors. If it happens, others can test with the same book. If it doesn't, then it suggests an issue with your books.

[crane3]

1. After deleting the .kobo directory, ALL the book files remain, both the sideloaded & from Calibre. Looks like the designed got changed; I did the delete of .kobo after seeing a msg in another thread that the books remained.

2. Your suggestion getting a book from the MR library is good. Did that & the book delete does the same thing, reboot & the get a DRM msg when trying to read it after the delete. The book is " he Book of Snobs - William Makepeace Thackery.epub". My placing the book in the same subdirectory as the light novels "should not matter"?

3. The stack_00.log:

Spoiler:

--------------------------------------------------------------------------
OH THE HUMANITY!
pid: 720, tid: 720 (nickel), rev: 112578920cc06e4fafa6cfc0c21a7fcdd976236a
>>> /usr/local/Kobo/nickel <<<
signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 00000004
r0 022a5e98 r1 022a5e98 r2 00000004 r3 80000000
r4 022a5e98 r5 7e80ba30 r6 00000025 r7 7e80b910
r8 efeaa64b r9 7e80b92c 10 2bd89f80 fp 00000004
ip 2e7ba020 sp 7e80b908 lr 022a5e98 pc 2b592d54 cpsr 800e0030
#00 sp: 0x7e80b908 ip: 0x2b592d54 /usr/local/Kobo/libnickel.so.1.0.0: _ZN12PluginLoader18supportedMimeTypesEv+0xc3
#01 sp: 0x7e80b958 ip: 0x2b541ac9 /usr/local/Kobo/libnickel.so.1.0.0: _ZN13VolumeManager20removeCommonBookDataERK6Device R6Volumeb+0x830
#02 sp: 0x7e80ba70 ip: 0x2b542271 /usr/local/Kobo/libnickel.so.1.0.0: _ZN13VolumeManager10removeBookERK6DeviceR6Volumeb+ 0x30
#03 sp: 0x7e80bab8 ip: 0x2b542515 /usr/local/Kobo/libnickel.so.1.0.0: _ZN13VolumeManager14removeBookDataERK6DeviceR6Volu me+0xcc
#04 sp: 0x7e80bae8 ip: 0x2b7abcd1 /usr/local/Kobo/libnickel.so.1.0.0: _ZN14DeletionHelper10deleteBookER6VolumeRK6Device+ 0xbc
#05 sp: 0x7e80bb28 ip: 0x2b7c8a3d /usr/local/Kobo/libnickel.so.1.0.0: _ZN16N3DeletionWizard18deleteBookAcceptedERK7QStri ng+0xc8
#06 sp: 0x7e80bbd0 ip: 0x2b7c9351 /usr/local/Kobo/libnickel.so.1.0.0: _ZN16N3DeletionWizard23deleteOrArchiveAcceptedEv+0 xdc
#07 sp: 0x7e80bc20 ip: 0x2e600f1d /usr/local/Trolltech/QtEmbedded-4.6.2-arm/lib/libQtCore.so.4.6.2: _ZN11QMetaObject8activateEP7QObjectiiPPv+0x1dc
#08 sp: 0x7e80bcd0 ip: 0x2e600f1d /usr/local/Trolltech/QtEmbedded-4.6.2-arm/lib/libQtCore.so.4.6.2: _ZN11QMetaObject8activateEP7QObjectiiPPv+0x1dc
#09 sp: 0x7e80bd80 ip: 0x2b645391 /usr/local/Kobo/libnickel.so.1.0.0: _ZN10TouchLabel13handleGestureEP8QGesture+0x70
#10 sp: 0x7e80be08 ip: 0x2b5bed5b /usr/local/Kobo/libnickel.so.1.0.0: _ZN15GestureReceiver21sendGestureToDelegateEP13QGe stureEventP15GestureDelegate+0xd6
#11 sp: 0x7e80be28 ip: 0x2d9d6ae3 /usr/local/Trolltech/QtEmbedded-4.6.2-arm/lib/libQtWidgets.so.4.6.2: _ZN19QApplicationPrivate13notify_helperEP7QObjectP 6QEvent+0x56
#12 sp: 0x7e80be40 ip: 0x2d9dc4e9 /usr/local/Trolltech/QtEmbedded-4.6.2-arm/lib/libQtWidgets.so.4.6.2: _ZN12QApplication6notifyEP7QObjectP6QEvent+0xff0
#13 sp: 0x7e80bfa0 ip: 0x2b7faf21 /usr/local/Kobo/libnickel.so.1.0.0: _ZN18Nickel3Application6notifyEP7QObjectP6QEvent+0 x34
#14 sp: 0x7e80bfd0 ip: 0x2e5e0111 /usr/local/Trolltech/QtEmbedded-4.6.2-arm/lib/libQtCore.so.4.6.2: _ZN16QCoreApplication14notifyInternalEP7QObjectP6Q Event+0x84
#15 sp: 0x7e80c000 ip: 0x2da12219 /usr/local/Trolltech/QtEmbedded-4.6.2-arm/lib/libQtWidgets.so.4.6.2: _ZN18QGestureRecognizer20unregisterRecognizerEN2Qt 11GestureTypeE+0x30d0
#16 sp: 0x7e80c0d0 ip: 0x2da13467 /usr/local/Trolltech/QtEmbedded-4.6.2-arm/lib/libQtWidgets.so.4.6.2: _ZN18QGestureRecognizer20unregisterRecognizerEN2Qt 11GestureTypeE+0x431e
#17 sp: 0x7e80c198 ip: 0x2da13ea5 /usr/local/Trolltech/QtEmbedded-4.6.2-arm/lib/libQtWidgets.so.4.6.2: _ZN18QGestureRecognizer20unregisterRecognizerEN2Qt 11GestureTypeE+0x4d5c
#18 sp: 0x7e80c1e0 ip: 0x2d9db599 /usr/local/Trolltech/QtEmbedded-4.6.2-arm/lib/libQtWidgets.so.4.6.2: _ZN12QApplication6notifyEP7QObjectP6QEvent+0xa0
#19 sp: 0x7e80c340 ip: 0x2b7faf21 /usr/local/Kobo/libnickel.so.1.0.0: _ZN18Nickel3Application6notifyEP7QObjectP6QEvent+0 x34
#20 sp: 0x7e80c370 ip: 0x2e5e0111 /usr/local/Trolltech/QtEmbedded-4.6.2-arm/lib/libQtCore.so.4.6.2: _ZN16QCoreApplication14notifyInternalEP7QObjectP6Q Event+0x84
#21 sp: 0x7e80c3a0 ip: 0x2d9dd987 /usr/local/Trolltech/QtEmbedded-4.6.2-arm/lib/libQtWidgets.so.4.6.2: _ZN19QApplicationPrivate22translateRawTouchEventEP 7QWidgetP12QTouchDeviceRK5QListIN11QTouchEvent10To uchPointEEm+0x9fe
#22 sp: 0x7e80c460 ip: 0x2da21ae1 /usr/local/Trolltech/QtEmbedded-4.6.2-arm/lib/libQtWidgets.so.4.6.2: _ZThn8_NK7QWidget6metricEN12QPaintDevice17PaintDev iceMetricE+0x2e38
#23 sp: 0x7e80c4e0 ip: 0x2d9d6ae3 /usr/local/Trolltech/QtEmbedded-4.6.2-arm/lib/libQtWidgets.so.4.6.2: _ZN19QApplicationPrivate13notify_helperEP7QObjectP 6QEvent+0x56
#24 sp: 0x7e80c4f8 ip: 0x2d9db91b /usr/local/Trolltech/QtEmbedded-4.6.2-arm/lib/libQtWidgets.so.4.6.2: _ZN12QApplication6notifyEP7QObjectP6QEvent+0x422
#25 sp: 0x7e80c658 ip: 0x2b7faf21 /usr/local/Kobo/libnickel.so.1.0.0: _ZN18Nickel3Application6notifyEP7QObjectP6QEvent+0 x34
#26 sp: 0x7e80c688 ip: 0x2e5e0111 /usr/local/Trolltech/QtEmbedded-4.6.2-arm/lib/libQtCore.so.4.6.2: _ZN16QCoreApplication14notifyInternalEP7QObjectP6Q Event+0x84
#27 sp: 0x7e80c6b8 ip: 0x2e16a581 /usr/local/Trolltech/QtEmbedded-4.6.2-arm/lib/libQtGui.so.4.6.2: _ZN22QGuiApplicationPrivate17processTouchEventEPN2 9QWindowSystemInterfacePrivate10TouchEventE+0xe24
#28 sp: 0x7e80c820 ip: 0x2e16c079 /usr/local/Trolltech/QtEmbedded-4.6.2-arm/lib/libQtGui.so.4.6.2: _ZN22QGuiApplicationPrivate24processWindowSystemEv entEPN29QWindowSystemInterfacePrivate17WindowSyste mEventE+0x18c
#29 sp: 0x7e80c858 ip: 0x2e15a877 /usr/local/Trolltech/QtEmbedded-4.6.2-arm/lib/libQtGui.so.4.6.2: _ZN22QWindowSystemInterface22sendWindowSystemEvent sE6QFlagsIN10QEventLoop17ProcessEventsFlagEE+0x1e
#30 sp: 0x7e80c868 ip: 0x2f79a6f3 /usr/local/Kobo/platforms/libkobo.so: _ZN13QFontEngineFT19alphaRGBMapForGlyphEj6QFixedRK 10QTransform+0xe1e
#31 sp: 0x7e80c878 ip: 0x2e5dea53 /usr/local/Trolltech/QtEmbedded-4.6.2-arm/lib/libQtCore.so.4.6.2: _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFla gEE+0xe6
#32 sp: 0x7e80c8b0 ip: 0x2e5e3931 /usr/local/Trolltech/QtEmbedded-4.6.2-arm/lib/libQtCore.so.4.6.2: _ZN16QCoreApplication4execEv+0x58
#33 sp: 0x7e80c8e0 ip: 0x0001c8f1 /usr/local/Kobo/nickel: main+0xb4c
#34 sp: 0x7e80caa0 ip: 0x2f5e3335 /lib/libc-2.11.1.so: __libc_start_main+0x9c
#35 sp: 0x7e80cbe8 ip: 0x0001cdfd /usr/local/Kobo/nickel: _start+0x20
--- --- --- --- --- --- --- --- --- --- --- --- --- --- --- ---
pid: 720, tid: 1080
r0 00000006 r1 301c6d80 r2 00000000 r3 00000000
r4 00000000 r5 00000020 r6 301c6d80 r7 0000008e
r8 2e7bb5c8 r9 00000000 10 004fcd20 fp 00000000
ip 00000000 sp 301c6d60 lr 00000000 pc 2f65c8d2 cpsr 800d0030
#00 sp: 0x301c6d60 ip: 0x2f65c8d2 /lib/libc-2.11.1.so: __select+0x31
#01 sp: 0x301c6d70 ip: 0x2e5985b5 /usr/local/Trolltech/QtEmbedded-4.6.2-arm/lib/libQtCore.so.4.6.2: _ZN9QLockFile6unlockEv+0x17e4
#02 sp: 0x301c6e28 ip: 0x2e46d651 /usr/local/Trolltech/QtEmbedded-4.6.2-arm/lib/libQtCore.so.4.6.2: _ZN7QThread21setTerminationEnabledEb+0x218
#03 sp: 0x301c6e50 ip: 0x2f45c473 /lib/libpthread-2.11.1.so: __pthread_get_minstack+0xec6
--- --- --- --- --- --- --- --- --- --- --- --- --- --- --- ---
pid: 720, tid: 1087
r0 0000000e r1 30c00560 r2 30c00770 r3 30c00980
r4 00000000 r5 00000000 r6 0000000e r7 0000008e
r8 30c00560 r9 30c00770 10 30c00980 fp 30c00468
ip 00000000 sp 30afec40 lr 00000000 pc 2f65c8d2 cpsr 80000030
#00 sp: 0x30afec40 ip: 0x2f65c8d2 /lib/libc-2.11.1.so: __select+0x31
#01 sp: 0x30afec50 ip: 0x2e61a023 /usr/local/Trolltech/QtEmbedded-4.6.2-arm/lib/libQtCore.so.4.6.2: _Z14qt_safe_selectiP6fd_setS0_S0_PK8timespec+0x172
#02 sp: 0x30afeca0 ip: 0x2e61b545 /usr/local/Trolltech/QtEmbedded-4.6.2-arm/lib/libQtCore.so.4.6.2: _ZN27QEventDispatcherUNIXPrivate8doSelectE6QFlagsI N10QEventLoop17ProcessEventsFlagEEP8timespec+0xdc
#03 sp: 0x30afeda0 ip: 0x2e61b9f1 /usr/local/Trolltech/QtEmbedded-4.6.2-arm/lib/libQtCore.so.4.6.2: _ZN20QEventDispatcherUNIX13processEventsE6QFlagsIN 10QEventLoop17ProcessEventsFlagEE+0xe8
#04 sp: 0x30afedc8 ip: 0x2e5dea53 /usr/local/Trolltech/QtEmbedded-4.6.2-arm/lib/libQtCore.so.4.6.2: _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFla gEE+0xe6
#05 sp: 0x30afee00 ip: 0x2e46a4cd /usr/local/Trolltech/QtEmbedded-4.6.2-arm/lib/libQtCore.so.4.6.2: _ZN7QThread4execEv+0x60
#06 sp: 0x30afee28 ip: 0x2e46d651 /usr/local/Trolltech/QtEmbedded-4.6.2-arm/lib/libQtCore.so.4.6.2: _ZN7QThread21setTerminationEnabledEb+0x218
#07 sp: 0x30afee50 ip: 0x2f45c473 /lib/libpthread-2.11.1.so: __pthread_get_minstack+0xec6
--- --- --- --- --- --- --- --- --- --- --- --- --- --- --- ---
pid: 720, tid: 1089
r0 0000000c r1 0053b850 r2 0053ba60 r3 0053bc70
r4 00000000 r5 00000000 r6 0000000c r7 0000008e
r8 0053b850 r9 0053ba60 10 0053bc70 fp 00539a90
ip 00000000 sp 314fec40 lr 00000000 pc 2f65c8d2 cpsr 80070030
#00 sp: 0x314fec40 ip: 0x2f65c8d2 /lib/libc-2.11.1.so: __select+0x31
#01 sp: 0x314fec50 ip: 0x2e61a023 /usr/local/Trolltech/QtEmbedded-4.6.2-arm/lib/libQtCore.so.4.6.2: _Z14qt_safe_selectiP6fd_setS0_S0_PK8timespec+0x172
#02 sp: 0x314feca0 ip: 0x2e61b545 /usr/local/Trolltech/QtEmbedded-4.6.2-arm/lib/libQtCore.so.4.6.2: _ZN27QEventDispatcherUNIXPrivate8doSelectE6QFlagsI N10QEventLoop17ProcessEventsFlagEEP8timespec+0xdc
#03 sp: 0x314feda0 ip: 0x2e61b9f1 /usr/local/Trolltech/QtEmbedded-4.6.2-arm/lib/libQtCore.so.4.6.2: _ZN20QEventDispatcherUNIX13processEventsE6QFlagsIN 10QEventLoop17ProcessEventsFlagEE+0xe8
#04 sp: 0x314fedc8 ip: 0x2e5dea53 /usr/local/Trolltech/QtEmbedded-4.6.2-arm/lib/libQtCore.so.4.6.2: _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFla gEE+0xe6
#05 sp: 0x314fee00 ip: 0x2e46a4cd /usr/local/Trolltech/QtEmbedded-4.6.2-arm/lib/libQtCore.so.4.6.2: _ZN7QThread4execEv+0x60
#06 sp: 0x314fee28 ip: 0x2e46d651 /usr/local/Trolltech/QtEmbedded-4.6.2-arm/lib/libQtCore.so.4.6.2: _ZN7QThread21setTerminationEnabledEb+0x218
#07 sp: 0x314fee50 ip: 0x2f45c473 /lib/libpthread-2.11.1.so: __pthread_get_minstack+0xec6
--- --- --- --- --- --- --- --- --- --- --- --- --- --- --- ---
pid: 720, tid: 1110
r0 00000025 r1 30200cc0 r2 30200ed0 r3 302010e0
r4 00000000 r5 00000000 r6 00000025 r7 0000008e
r8 30200cc0 r9 30200ed0 10 302010e0 fp 30200bc8
ip 00000000 sp 324fec40 lr 00000000 pc 2f65c8d2 cpsr 80030030
#00 sp: 0x324fec40 ip: 0x2f65c8d2 /lib/libc-2.11.1.so: __select+0x31
#01 sp: 0x324fec50 ip: 0x2e61a023 /usr/local/Trolltech/QtEmbedded-4.6.2-arm/lib/libQtCore.so.4.6.2: _Z14qt_safe_selectiP6fd_setS0_S0_PK8timespec+0x172
#02 sp: 0x324feca0 ip: 0x2e61b545 /usr/local/Trolltech/QtEmbedded-4.6.2-arm/lib/libQtCore.so.4.6.2: _ZN27QEventDispatcherUNIXPrivate8doSelectE6QFlagsI N10QEventLoop17ProcessEventsFlagEEP8timespec+0xdc
#03 sp: 0x324feda0 ip: 0x2e61b9f1 /usr/local/Trolltech/QtEmbedded-4.6.2-arm/lib/libQtCore.so.4.6.2: _ZN20QEventDispatcherUNIX13processEventsE6QFlagsIN 10QEventLoop17ProcessEventsFlagEE+0xe8
#04 sp: 0x324fedc8 ip: 0x2e5dea53 /usr/local/Trolltech/QtEmbedded-4.6.2-arm/lib/libQtCore.so.4.6.2: _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFla gEE+0xe6
#05 sp: 0x324fee00 ip: 0x2e46a4cd /usr/local/Trolltech/QtEmbedded-4.6.2-arm/lib/libQtCore.so.4.6.2: _ZN7QThread4execEv+0x60
#06 sp: 0x324fee28 ip: 0x2e46d651 /usr/local/Trolltech/QtEmbedded-4.6.2-arm/lib/libQtCore.so.4.6.2: _ZN7QThread21setTerminationEnabledEb+0x218
#07 sp: 0x324fee50 ip: 0x2f45c473 /lib/libpthread-2.11.1.so: __pthread_get_minstack+0xec6
--- --- --- --- --- --- --- --- --- --- --- --- --- --- --- ---
pid: 720, tid: 1116
r0 00000027 r1 346989a0 r2 00000000 r3 00000000
r4 00000000 r5 346989a0 r6 34698988 r7 0000008e
r8 30c01e68 r9 00000026 10 2e7bb768 fp 301f76d0
ip 00000000 sp 34698950 lr 00000000 pc 2f65c8d2 cpsr 800e0030
#00 sp: 0x34698950 ip: 0x2f65c8d2 /lib/libc-2.11.1.so: __select+0x31
#01 sp: 0x34698960 ip: 0x301e2b2d /usr/local/Kobo/generic/libkevdevtouch.so: _init+0x4095
#02 sp: 0x34698a48 ip: 0x2e60a11b /usr/local/Trolltech/QtEmbedded-4.6.2-arm/lib/libQtCore.so.4.6.2: _ZN15QSocketNotifier5eventEP6QEvent+0x1f2
#03 sp: 0x34698a68 ip: 0x2e601ce5 /usr/local/Trolltech/QtEmbedded-4.6.2-arm/lib/libQtCore.so.4.6.2: _ZN7QObject5eventEP6QEvent+0xd0
#04 sp: 0x34698b48 ip: 0x2d9d6ae3 /usr/local/Trolltech/QtEmbedded-4.6.2-arm/lib/libQtWidgets.so.4.6.2: _ZN19QApplicationPrivate13notify_helperEP7QObjectP 6QEvent+0x56
#05 sp: 0x34698b60 ip: 0x2d9db91b /usr/local/Trolltech/QtEmbedded-4.6.2-arm/lib/libQtWidgets.so.4.6.2: _ZN12QApplication6notifyEP7QObjectP6QEvent+0x422
#06 sp: 0x34698cc0 ip: 0x2b7faf21 /usr/local/Kobo/libnickel.so.1.0.0: _ZN18Nickel3Application6notifyEP7QObjectP6QEvent+0 x34
#07 sp: 0x34698cf0 ip: 0x2e5e0111 /usr/local/Trolltech/QtEmbedded-4.6.2-arm/lib/libQtCore.so.4.6.2: _ZN16QCoreApplication14notifyInternalEP7QObjectP6Q Event+0x84
#08 sp: 0x34698d20 ip: 0x2e61cc65 /usr/local/Trolltech/QtEmbedded-4.6.2-arm/lib/libQtCore.so.4.6.2: _ZN14QTimerInfoList14activateTimersEv+0x400
#09 sp: 0x34698d88 ip: 0x2e61b9df /usr/local/Trolltech/QtEmbedded-4.6.2-arm/lib/libQtCore.so.4.6.2: _ZN20QEventDispatcherUNIX13processEventsE6QFlagsIN 10QEventLoop17ProcessEventsFlagEE+0xd6
#10 sp: 0x34698db0 ip: 0x2e5dea53 /usr/local/Trolltech/QtEmbedded-4.6.2-arm/lib/libQtCore.so.4.6.2: _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFla gEE+0xe6
#11 sp: 0x34698de8 ip: 0x2e46a4cd /usr/local/Trolltech/QtEmbedded-4.6.2-arm/lib/libQtCore.so.4.6.2: _ZN7QThread4execEv+0x60
#12 sp: 0x34698e10 ip: 0x301e51f1 /usr/local/Kobo/generic/libkevdevtouch.so: _init+0x6759
#13 sp: 0x34698e28 ip: 0x2e46d651 /usr/local/Trolltech/QtEmbedded-4.6.2-arm/lib/libQtCore.so.4.6.2: _ZN7QThread21setTerminationEnabledEb+0x218
#14 sp: 0x34698e50 ip: 0x2f45c473 /lib/libpthread-2.11.1.so: __pthread_get_minstack+0xec6
--- --- --- --- --- --- --- --- --- --- --- --- --- --- --- ---
pid: 720, tid: 2475
r0 00000030 r1 30203a58 r2 30203c68 r3 30203e78
r4 36e98b90 r5 36e98b98 r6 36e98b90 r7 0000014f
r8 30203a58 r9 30203c68 10 30203e78 fp 00000000
ip 0000014f sp 36e98b80 lr 2f65c9cb pc 2f5e35f4 cpsr 80070030
#00 sp: 0x36e98b80 ip: 0x2f5e35f4 /lib/libc-2.11.1.so: gnu_get_libc_version+0x1a3
#01 sp: 0x36e98b88 ip: 0x2f65c9cb /lib/libc-2.11.1.so: pselect+0xca
#02 sp: 0x36e98c50 ip: 0x2e619ff7 /usr/local/Trolltech/QtEmbedded-4.6.2-arm/lib/libQtCore.so.4.6.2: _Z14qt_safe_selectiP6fd_setS0_S0_PK8timespec+0x146
#03 sp: 0x36e98ca0 ip: 0x2e61b545 /usr/local/Trolltech/QtEmbedded-4.6.2-arm/lib/libQtCore.so.4.6.2: _ZN27QEventDispatcherUNIXPrivate8doSelectE6QFlagsI N10QEventLoop17ProcessEventsFlagEEP8timespec+0xdc
#04 sp: 0x36e98da0 ip: 0x2e61b9ff /usr/local/Trolltech/QtEmbedded-4.6.2-arm/lib/libQtCore.so.4.6.2: _ZN20QEventDispatcherUNIX13processEventsE6QFlagsIN 10QEventLoop17ProcessEventsFlagEE+0xf6
#05 sp: 0x36e98dc8 ip: 0x2e5dea53 /usr/local/Trolltech/QtEmbedded-4.6.2-arm/lib/libQtCore.so.4.6.2: _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFla gEE+0xe6
#06 sp: 0x36e98e00 ip: 0x2e46a4cd /usr/local/Trolltech/QtEmbedded-4.6.2-arm/lib/libQtCore.so.4.6.2: _ZN7QThread4execEv+0x60
#07 sp: 0x36e98e28 ip: 0x2e46d651 /usr/local/Trolltech/QtEmbedded-4.6.2-arm/lib/libQtCore.so.4.6.2: _ZN7QThread21setTerminationEnabledEb+0x218
#08 sp: 0x36e98e50 ip: 0x2f45c473 /lib/libpthread-2.11.1.so: __pthread_get_minstack+0xec6
--- --- --- --- --- --- --- --- --- --- --- --- --- --- --- ---
pid: 720, tid: 3302
r0 2d8f8f94 r1 00000080 r2 00000003 r3 00000000
r4 00000000 r5 2d8f8f90 r6 2d8f8f78 r7 000000f0
r8 00000000 r9 00000001 10 2d8f8f77 fp 00000003
ip 000000f0 sp 35dc4d88 lr 2f45ff1f pc 2f4643c4 cpsr 400b0030
#00 sp: 0x35dc4d88 ip: 0x2f4643c4 /lib/libpthread-2.11.1.so: __res_state+0x2f
#01 sp: 0x35dc4d90 ip: 0x2f45ff1f /lib/libpthread-2.11.1.so: pthread_cond_wait+0xe6
#02 sp: 0x35dc4df8 ip: 0x2d4f2545 /usr/local/Trolltech/QtEmbedded-4.6.2-arm/lib/libQtWebKit.so.4.6.2: _ZN3WTF8Internal21fastMallocMatchFailedEPv+0xaf4
#03 sp: 0x35dc4e48 ip: 0x2d4f2581 /usr/local/Trolltech/QtEmbedded-4.6.2-arm/lib/libQtWebKit.so.4.6.2: _ZN3WTF8Internal21fastMallocMatchFailedEPv+0xb30
#04 sp: 0x35dc4e58 ip: 0x2d4f2581 /usr/local/Trolltech/QtEmbedded-4.6.2-arm/lib/libQtWebKit.so.4.6.2: _ZN3WTF8Internal21fastMallocMatchFailedEPv+0xb30
#05 sp: 0x35dc5460 ip: 0x2d4f2581 /usr/local/Trolltech/QtEmbedded-4.6.2-arm/lib/libQtWebKit.so.4.6.2: _ZN3WTF8Internal21fastMallocMatchFailedEPv+0xb30
#06 sp: 0x00000010 ip: 0x2d4f2581 /usr/local/Trolltech/QtEmbedded-4.6.2-arm/lib/libQtWebKit.so.4.6.2: _ZN3WTF8Internal21fastMallocMatchFailedEPv+0xb30
#07 sp: 0x0000000f ip: 0x2d4f2581 /usr/local/Trolltech/QtEmbedded-4.6.2-arm/lib/libQtWebKit.so.4.6.2: _ZN3WTF8Internal21fastMallocMatchFailedEPv+0xb30
--- --- --- --- --- --- --- --- --- --- --- --- --- --- --- ---
pid: 720, tid: 3303
r0 3536b144 r1 00000080 r2 00000025 r3 00000000
r4 00000000 r5 3536b140 r6 3536b124 r7 000000f0
r8 00000000 r9 00000001 10 3536b123 fp 00000025
ip 000000f0 sp 33e98da8 lr 2f45ff1f pc 2f4643c4 cpsr 400c0030
#00 sp: 0x33e98da8 ip: 0x2f4643c4 /lib/libpthread-2.11.1.so: __res_state+0x2f
#01 sp: 0x33e98db0 ip: 0x2f45ff1f /lib/libpthread-2.11.1.so: pthread_cond_wait+0xe6
#02 sp: 0x33e98e18 ip: 0x2d2e120d /usr/local/Trolltech/QtEmbedded-4.6.2-arm/lib/libQtWebKit.so.4.6.2: _ZN3JSC9HandleSet12writeBarrierEPNS_7JSValueERKS1_ +0x724
#03 sp: 0x33e98e40 ip: 0x2d517843 /usr/local/Trolltech/QtEmbedded-4.6.2-arm/lib/libQtWebKit.so.4.6.2: _ZN3WTF11OSAllocator18releaseDecommittedEPvj+0xe2
#04 sp: 0x33e98e50 ip: 0x2f45c473 /lib/libpthread-2.11.1.so: __pthread_get_minstack+0xec6
--- --- --- --- --- --- --- --- --- --- --- --- --- --- --- ---
pid: 720, tid: 5741
r0 0000002e r1 39dbc960 r2 39dbcb70 r3 39dbcd80
r4 00000000 r5 00000000 r6 0000002e r7 0000008e
r8 39dbc960 r9 39dbcb70 10 39dbcd80 fp 30203948
ip 00000000 sp 39c74c40 lr 00000000 pc 2f65c8d2 cpsr 80070030
#00 sp: 0x39c74c40 ip: 0x2f65c8d2 /lib/libc-2.11.1.so: __select+0x31
#01 sp: 0x39c74c50 ip: 0x2e61a023 /usr/local/Trolltech/QtEmbedded-4.6.2-arm/lib/libQtCore.so.4.6.2: _Z14qt_safe_selectiP6fd_setS0_S0_PK8timespec+0x172
#02 sp: 0x39c74ca0 ip: 0x2e61b545 /usr/local/Trolltech/QtEmbedded-4.6.2-arm/lib/libQtCore.so.4.6.2: _ZN27QEventDispatcherUNIXPrivate8doSelectE6QFlagsI N10QEventLoop17ProcessEventsFlagEEP8timespec+0xdc
#03 sp: 0x39c74da0 ip: 0x2e61b9f1 /usr/local/Trolltech/QtEmbedded-4.6.2-arm/lib/libQtCore.so.4.6.2: _ZN20QEventDispatcherUNIX13processEventsE6QFlagsIN 10QEventLoop17ProcessEventsFlagEE+0xe8
#04 sp: 0x39c74dc8 ip: 0x2e5dea53 /usr/local/Trolltech/QtEmbedded-4.6.2-arm/lib/libQtCore.so.4.6.2: _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFla gEE+0xe6
#05 sp: 0x39c74e00 ip: 0x2e46a4cd /usr/local/Trolltech/QtEmbedded-4.6.2-arm/lib/libQtCore.so.4.6.2: _ZN7QThread4execEv+0x60
#06 sp: 0x39c74e28 ip: 0x2e46d651 /usr/local/Trolltech/QtEmbedded-4.6.2-arm/lib/libQtCore.so.4.6.2: _ZN7QThread21setTerminationEnabledEb+0x218
#07 sp: 0x39c74e50 ip: 0x2f45c473 /lib/libpthread-2.11.1.so: __pthread_get_minstack+0xec6
--- --- --- --- --- --- --- --- --- --- --- --- --- --- --- ---
pid: 720, tid: 5742
r0 00000031 r1 30205d08 r2 30205f18 r3 30206128
r4 00000000 r5 00000000 r6 00000031 r7 0000008e
r8 30205d08 r9 30205f18 10 30206128 fp 30233a78
ip 00000000 sp 3b513c40 lr 00000000 pc 2f65c8d2 cpsr 80070030
#00 sp: 0x3b513c40 ip: 0x2f65c8d2 /lib/libc-2.11.1.so: __select+0x31
#01 sp: 0x3b513c50 ip: 0x2e61a023 /usr/local/Trolltech/QtEmbedded-4.6.2-arm/lib/libQtCore.so.4.6.2: _Z14qt_safe_selectiP6fd_setS0_S0_PK8timespec+0x172
#02 sp: 0x3b513ca0 ip: 0x2e61b545 /usr/local/Trolltech/QtEmbedded-4.6.2-arm/lib/libQtCore.so.4.6.2: _ZN27QEventDispatcherUNIXPrivate8doSelectE6QFlagsI N10QEventLoop17ProcessEventsFlagEEP8timespec+0xdc
#03 sp: 0x3b513da0 ip: 0x2e61b9f1 /usr/local/Trolltech/QtEmbedded-4.6.2-arm/lib/libQtCore.so.4.6.2: _ZN20QEventDispatcherUNIX13processEventsE6QFlagsIN 10QEventLoop17ProcessEventsFlagEE+0xe8
#04 sp: 0x3b513dc8 ip: 0x2e5dea53 /usr/local/Trolltech/QtEmbedded-4.6.2-arm/lib/libQtCore.so.4.6.2: _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFla gEE+0xe6
#05 sp: 0x3b513e00 ip: 0x2e46a4cd /usr/local/Trolltech/QtEmbedded-4.6.2-arm/lib/libQtCore.so.4.6.2: _ZN7QThread4execEv+0x60
#06 sp: 0x3b513e28 ip: 0x2e46d651 /usr/local/Trolltech/QtEmbedded-4.6.2-arm/lib/libQtCore.so.4.6.2: _ZN7QThread21setTerminationEnabledEb+0x218
#07 sp: 0x3b513e50 ip: 0x2f45c473 /lib/libpthread-2.11.1.so: __pthread_get_minstack+0xec6
--- --- --- --- --- --- --- --- --- --- --- --- --- --- --- ---
Recorded last user operations:
last user operation[34]: "upgradeTime"
last user operation[33]: "appStart"
last user operation[32]: "gotAchievement
last user operation[31]: "welcome"
last user operation[30]: "wirelessSetup"
last user operation[29]: "signedIn"
last user operation[28]: "keyboardCorrec
last user operation[27]: "batteryLevelAt
last user operation[26]: "fteComplete"
last user operation[25]: "mainNavOption"
last user operation[24]: "books"
last user operation[23]: "mainNavOption"
last user operation[22]: "search"
last user operation[21]: "statusBarOptio
last user operation[20]: "searchExecuted
last user operation[19]: "home"
last user operation[18]: "mainNavOption"
last user operation[17]: "pluggedIn"
last user operation[16]: "pluggedInBatte
last user operation[15]: "books"
last user operation[14]: "mainNavOption"
last user operation[13]: "longPress"
last user operation[12]: "startReadingBo
last user operation[11]: "gotAchievement
last user operation[10]: "openContent"
last user operation[9]: "readerShown"
last user operation[8]: "gotAchievement
last user operation[7]: "pageTurned"
last user operation[6]: "batteryLevelAt
last user operation[5]: "leaveContent"
last user operation[4]: "readerHidden"
last user operation[3]: "home"
last user operation[2]: "mainNavOption"
last user operation[1]: "books"
last user operation[0]: "mainNavOption"
--- --- --- --- --- --- --- --- --- --- --- --- --- --- --- --

-

[PeterT]

Please learn how to use to the [ spoiler ] .... [ /spoiler ] tags to hide logs like that from folks in