Library and peripheral window behavior - Page 2

theducks · 02-25-2026, 07:12 PM

There are a LOT of Libra2 being used on Calibre Windows. It ain't Calibre.

Something has mucked with either the Libra2 or Windows USB.

Keep a Linux (mint) Live CD (on flash). It is great for checking Is it my HW or Windows.

DNSB · 02-25-2026, 07:46 PM

I assume you have done all the usual steps such as restarting your Kobo, re-installing the firmware, etc.

You may also want to try Nirsoft's USBDeview to see if you have any odd USB devices such as ones with device name of unknown. Alternatively, you can open Device Manager and check for devices that are in an error state (yellow !) or are in the Unknown folder.

I did find that when I connect my Kobo Libra Colour to my Windows 11 computer and I get the first connection bing, a device with the VID 0525 and PID of A4A5 shows up but it never goes into connected mode. When I tap on Connect in the popup on the Libra Colour, a new device with VID 2237 and PID 4237 shows up and goes into a connected state. My Sage does much the same except the unconnected VID is 1D6B and the PID is 0106.

So at a wild-eyed guess, your Libra 2 is not registering the tap on Connect in the Computer Detected popup. If you are not seeing the Computer Detected popup, do you have AutoUsbGadget=True under [DeveloperSettings] in the Kobo eReader.conf file?

PeterT · 02-25-2026, 09:13 PM

I'm of the school of thought that the f/w on the device is corrupted; the udev rules and scripts they invoke when a USB connection is established are not working correctly.

Just download the correct f/w, and expand the zip file to the .kobo directory.

Sent from my TB350FU using Tapatalk

02-25-2026, 07:46 PM	#17
DNSB Bibliophagist Posts: 50,615 Karma: 178402706 Join Date: Jul 2010 Location: Vancouver Device: Kobo Sage, Libra Colour, Lenovo M8 FHD, Paperwhite 4, Tolino epos	I assume you have done all the usual steps such as restarting your Kobo, re-installing the firmware, etc. You may also want to try Nirsoft's USBDeview to see if you have any odd USB devices such as ones with device name of unknown. Alternatively, you can open Device Manager and check for devices that are in an error state (yellow !) or are in the Unknown folder. I did find that when I connect my Kobo Libra Colour to my Windows 11 computer and I get the first connection bing, a device with the VID 0525 and PID of A4A5 shows up but it never goes into connected mode. When I tap on Connect in the popup on the Libra Colour, a new device with VID 2237 and PID 4237 shows up and goes into a connected state. My Sage does much the same except the unconnected VID is 1D6B and the PID is 0106. So at a wild-eyed guess, your Libra 2 is not registering the tap on Connect in the Computer Detected popup. If you are not seeing the Computer Detected popup, do you have AutoUsbGadget=True under [DeveloperSettings] in the Kobo eReader.conf file? Attached Thumbnails Last edited by DNSB; 02-25-2026 at 08:03 PM.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Calibre on OSX - Bizarre window behavior - bug?	stisev	Calibre	6	09-02-2020 01:40 AM
Strange library behavior	jlmwrite	Nook Developer's Corner	9	01-23-2011 02:46 PM
A few questions about library behavior	HardBall	enTourage Archive	18	12-14-2010 07:22 AM
Request Allow choice for browser behavior when a window closes. . .	kenjennings	enTourage Archive	0	06-12-2010 07:57 PM
possible augmentation in main library window	polarbearmike	Calibre	4	01-23-2010 07:28 PM

02-25-2026, 07:12 PM	#16
theducks Well trained by Cats Posts: 31,554 Karma: 62543878 Join Date: Aug 2009 Location: The Central Coast of California Device: Kobo Libra2,Kobo Aura2v1, K4NT(Fixed: New Bat.), Galaxy Tab A	There are a LOT of Libra2 being used on Calibre Windows. It ain't Calibre. Something has mucked with either the Libra2 or Windows USB. Keep a Linux (mint) Live CD (on flash). It is great for checking Is it my HW or Windows.

02-25-2026, 09:13 PM	#18
PeterT Grand Sorcerer Posts: 13,835 Karma: 80512154 Join Date: Nov 2007 Location: Toronto Device: Libra H2O, Libra Colour	I'm of the school of thought that the f/w on the device is corrupted; the udev rules and scripts they invoke when a USB connection is established are not working correctly. Just download the correct f/w, and expand the zip file to the .kobo directory. Sent from my TB350FU using Tapatalk