Since I'm honestly not sure how to get a debug log, and it isn't really a problem (nothing bad happens, Calibre just freezes for around a minute while - I'm assuming - something happens in the background), and because I'm not sure what you mean by database size (number of books? file size of the backup? used space on the Kobo?), and since it doesn't seem to be affecting other people, I'm just going to ignore it for now. If it becomes a problem I'll figure out what I need to send to you! Oh, but I'm on Windows 11.
Thanks!
Right click on the Preferences icon and select Restart in debug mode. Then run calibre doing what you do that causes Kobo Utilities to take extra time to run. When you exit calibre, you'll have a debug log that you can post.
Right click on the Preferences icon and select Restart in debug mode. Then run calibre doing what you do that causes Kobo Utilities to take extra time to run. When you exit calibre, you'll have a debug log that you can post.
Well, I got the log, but I'm not sure it's necessary and I really don't think I should post the whole thing on here given how long it is. How would I post it if I was going to?
That said, I don't know if it was something to do with debug mode, or with me having just updated to Calibre 9.4, but the freeze this time was only about 15 seconds, not around a full minute like it has been. That doesn't bother me much at all, especially since I am honestly unsure if things are still running in the background and it's just a stupid Windows freezing things issue. Even with the full minute or so of freezing, I'm not all that bothered, I just mentioned it in case it was an issue with the update of Kobo Utilities, but it doesn't seem to be happening to anyone else, so *shrugs*
If someone REALLY wants to look into it, let me know how/where to send the log. That aside, I'm not going to worry about it and I'm not going to ask anyone else to worry about it.
Device: Kobo Libra2,Kobo Aura2v1, K4NT(Fixed: New Bat.), Galaxy Tab A
Quote:
Originally Posted by JDesat
Well, I got the log, but I'm not sure it's necessary and I really don't think I should post the whole thing on here given how long it is. How would I post it if I was going to?
That said, I don't know if it was something to do with debug mode, or with me having just updated to Calibre 9.4, but the freeze this time was only about 15 seconds, not around a full minute like it has been. That doesn't bother me much at all, especially since I am honestly unsure if things are still running in the background and it's just a stupid Windows freezing things issue. Even with the full minute or so of freezing, I'm not all that bothered, I just mentioned it in case it was an issue with the update of Kobo Utilities, but it doesn't seem to be happening to anyone else, so *shrugs*
If someone REALLY wants to look into it, let me know how/where to send the log. That aside, I'm not going to worry about it and I'm not going to ask anyone else to worry about it.
Thanks, though!
Wrap log files in spoiler tags
eg
[spoiler]Logs here[/spoller]
Wrap log files in spoiler tags
eg
[spoiler]Logs here[/spoller]
Should I remove the portion of the log that shows the fics I sent to the Kobo? (I ask because some of them are fanfics from QQ and I know we aren't supposed to post NSFW links.)
Also, if the problem is only affecting me (and not overly annoying even to me) do you actually want me to post them for you to look into? I'm willing to do it if you are, I'm just not overly worried either way if I'm the only one affected.
Should I remove the portion of the log that shows the fics I sent to the Kobo? (I ask because some of them are fanfics from QQ and I know we aren't supposed to post NSFW links.)
Also, if the problem is only affecting me (and not overly annoying even to me) do you actually want me to post them for you to look into? I'm willing to do it if you are, I'm just not overly worried either way if I'm the only one affected.
You could just edit the names and change them to something else.
Device: Kobo Libra2,Kobo Aura2v1, K4NT(Fixed: New Bat.), Galaxy Tab A
Quote:
Originally Posted by JSWolf
IMHO, I think it's better to put the log in code block. Then we can see it without having to see the entire thing at once.
Nope! If you DO NOT want to see it, it stays as an icon. If you do, you click and it expands a bit. The whole code block does NOT fill the screen on monitors/laptops.
Nope! If you DO NOT want to see it, it stays as an icon. If you do, you click and it expands a bit. The whole code block does NOT fill the screen on monitors/laptops.
It can expand a lot depending on how long the log file it. The code block is a fixed size. So that's why a code block is better if the log is long enough.
I have to agree with @theducks. Spoilers work best for hiding long log files and anything that most people will not bother to read. Code blocks are best when you want people to see chunks of text with the original formatting. The first spoiler is a spoiler, the second is a spoiler wrapped around code. I did not do a plain code block since that is what you will see when you click on the second spoiler. Code does not hide the text nor is it a fixed length.
Driver: KoboTouch'
[3.65] main UI initialized...
[3.65] Hiding splash screen
[3.65] splash screen hidden
[3.65] Started up in 3.65 seconds with 56 books
[8.79] [DEBUG] [koboutilities.action:KoboUtilitiesAction.set_toolb ar_button_tooltip:180] setting to text='Utilities to use with Kobo ereaders
Driver: KoboTouch'
[14.68] Shutdown starting...
[14.71] Shutdown message shown...
[14.74] Grid view shutdown
[14.74] Bookshelf view shutdown
[14.75] Actions shutdown
[14.95] Various services shutdown
[14.95] Metadata backup shutdown
[14.95] [Backup Configuration Folder]: starting backup process
[16.91] [Backup Configuration Folder]: wrote config backup to C:\Users\<user>\Desktop\Calibre Config Backups\backup-calibre\2026-02-27 at 12-28-22.zip. Size: 89,913,112 bytes.
[16.91] [Backup Configuration Folder]: finished
[16.92] Current database closed
[16.93] Windows hidden
[16.94] Waiting for overseers, mdns, and live to shutdown
[16.94] Waiting for device manager to shutdown
[16.94] Shutdown complete in 2.26, quitting...
This is what I think is the relevant section of the log file going by what it says is going on at that point. Also, it's the only point where there is any gaps at all in what I'm guessing is a time code of some kind (the [114.07] or whatever at the start of some lines). After the end point of this there was no freeze, and the freeze happens after it gets the list of books on the device.