Library and peripheral window behavior

[asw22]

I am presently expurging my Kobo SD from books present in the database, but not physically.
My Library and peripheral databases are quite large (ca 30,000 books). I need to check line after line books considered not present in the library against the library itself to be sure sometimes a book announced at not present is there on the SD...
The goal is to have a peripheral book list reflecting the peripheral written books.
My idea of fun, dont ask

My problem is when alternating between peripheral and library view, the view is not "stable": for instance, on the peripheral view, the list goes back after a while (ca 20 s) to zero. When you are at 15000, it's unpleasant.
On the library view, each time I open it the list has gone back by 500 books or so...
What happens, and what can be done?

It is as much fun as opening a book and systematically begins at first page, whatever the place where you closed your book last time...

Thanks!

[asw22]

Hello!

I have finally finished the cleanup of the database books not present physically. I have begun to fill it again and I am around 26000 without too much databse corruptions.

However, I have had to stop because of a bizarre event: the Libra 2 is not recognized by Calibre, and this happened overnight.
Here is the debug:

The bug is quite close to some reported here, but not exactly...

Spoiler:

Here is the DEBOG:
calibre 9.3.1 embedded-python: True
Windows-11-10.0.22631-SP0 Windows ('64bit', 'WindowsPE')
('Windows', '11', '10.0.22631')
Python 3.14.2
Windows: ('11', '10.0.22631', 'SP0', 'Multiprocessor Free')
Interface language: fr
EXE path: C:\Program Files\Calibre2\calibre.exe
Successfully initialized third party plugins: DeDRM (10, 0, 3) && Amazon.com Multiple Countries (1, 0, 0) && Author Book Count (2, 2, 3) && Babelio_db (1, 1, 0) && Barnes & Noble (1, 5, 8) && Check Books (0, 2, 0) && Clean Metadata (0, 0, 6) && EpubCheck (0, 2, 6) && EpubMerge (3, 2, 0) && EpubSplit (3, 12, 0) && Fantastic Fiction (1, 7, 2) && Find Duplicates (1, 10, 10) && Goodreads (1, 8, 4) && Goodreads More Tags (1, 2, 1, 2) && Kobo Utilities (2, 27, 1) && PocketBook Improved Device Interface (1, 0, 4) && Pocketbook Tools (0, 10, 0) && Quality Check (1, 14, 7) && SmartEject (2, 6, 0) && Wikidata (2, 0, 0) && ePub Extended Metadata {Reader} (0, 14, 5) && ePub Extended Metadata {Writer} (0, 14, 5) && ePub Extended Metadata (0, 14, 5)
USB devices on system:
(USBDevice(vendor_id=0x5e3 product_id=0x610 bcd=0x9226 devid=usb\vid_05e3&pid_0610&rev_9226 devinst=19),
USBDevice(vendor_id=0xdb0 product_id=0x76 bcd=0x1 devid=usb\vid_0db0&pid_0076&rev_0001 devinst=20),
USBDevice(vendor_id=0x46d product_id=0xc07d bcd=0x8802 devid=usb\vid_046d&pid_c07d&rev_8802&mi_01 devinst=21),
USBDevice(vendor_id=0x5e3 product_id=0x610 bcd=0x9226 devid=usb\vid_05e3&pid_0610&rev_9226 devinst=22),
USBDevice(vendor_id=0x3f0 product_id=0x6be bcd=0x4114 devid=usb\vid_03f0&pid_06be&rev_4114 devinst=23),
USBDevice(vendor_id=0x46d product_id=0xc52b bcd=0x1201 devid=usb\vid_046d&pid_c52b&rev_1201&mi_00 devinst=24),
USBDevice(vendor_id=0x480 product_id=0xa200 bcd=0x0 devid=usb\vid_0480&pid_a200&rev_0000 devinst=25),
USBDevice(vendor_id=0x46d product_id=0xc07d bcd=0x8802 devid=usb\vid_046d&pid_c07d&rev_8802 devinst=26),
USBDevice(vendor_id=0x46d product_id=0xc52b bcd=0x1201 devid=usb\vid_046d&pid_c52b&rev_1201 devinst=27),
USBDevice(vendor_id=0x3f0 product_id=0x6be bcd=0x4114 devid=usb\vid_03f0&pid_06be&rev_4114&mi_03 devinst=28),
USBDevice(vendor_id=None product_id=None bcd=None devid=usb\root_hub30&vid1022&pid15b8&rev0000 devinst=29),
USBDevice(vendor_id=0x46d product_id=0xc52b bcd=0x1201 devid=usb\vid_046d&pid_c52b&rev_1201&mi_01 devinst=30),
USBDevice(vendor_id=None product_id=None bcd=None devid=usb\root_hub30&vid1022&pid15b6&rev0000 devinst=31),
USBDevice(vendor_id=0x174c product_id=0x3074 bcd=0x1 devid=usb\vid_174c&pid_3074&rev_0001 devinst=32),
USBDevice(vendor_id=0x5e3 product_id=0x610 bcd=0x9226 devid=usb\vid_05e3&pid_0610&rev_9226 devinst=33),
USBDevice(vendor_id=0x174c product_id=0x55aa bcd=0x100 devid=usb\vid_174c&pid_55aa&rev_0100 devinst=34),
USBDevice(vendor_id=0x1058 product_id=0x25e2 bcd=0x4004 devid=usb\vid_1058&pid_25e2&rev_4004 devinst=35),
USBDevice(vendor_id=0x174c product_id=0x2074 bcd=0x1 devid=usb\vid_174c&pid_2074&rev_0001 devinst=36),
USBDevice(vendor_id=0x46d product_id=0xc52b bcd=0x1201 devid=usb\vid_046d&pid_c52b&rev_1201&mi_02 devinst=37),
USBDevice(vendor_id=0x525 product_id=0xa4a5 bcd=0x401 devid=usb\vid_0525&pid_a4a5&rev_0401 devinst=38),
USBDevice(vendor_id=0x3f0 product_id=0x6be bcd=0x4114 devid=usb\vid_03f0&pid_06be&rev_4114&mi_00 devinst=39),
USBDevice(vendor_id=None product_id=None bcd=None devid=usb\root_hub30&vid1022&pid15b7&rev0000 devinst=40),
USBDevice(vendor_id=None product_id=None bcd=None devid=usb\root_hub30&vid1022&pid43f7&rev0001 devinst=41),
USBDevice(vendor_id=0x46d product_id=0xc07d bcd=0x8802 devid=usb\vid_046d&pid_c07d&rev_8802&mi_00 devinst=42))

No disabled plugins
Looking for devices of type: MTP_DEVICE
List of WPD PNP ids:
['\\\\?\\swd#wpdbusenum#{b17f33ed-b0e4-11f0-904e-806e6f6e6963}#00000000007e1000#{6ac27878-a6fa-4155-ba85-f98f491d4f33}',
'\\\\?\\swd#wpdbusenum#{48eb3a98-2f21-11ef-8e0f-806e6f6e6963}#000002dc6c1fbc00#{6ac27878-a6fa-4155-ba85-f98f491d4f33}',
'\\\\?\\swd#wpdbusenum#{23edccf0-2f0f-11ef-8e0e-806e6f6e6963}#0000000000100000#{6ac27878-a6fa-4155-ba85-f98f491d4f33}',
'\\\\?\\swd#wpdbusenum#{798d01da-8b01-11ee-8df2-fe99fe4e0144}#0000000000100000#{6ac27878-a6fa-4155-ba85-f98f491d4f33}',
'\\\\?\\swd#wpdbusenum#{b17f33ed-b0e4-11f0-904e-806e6f6e6963}#000000e8e0b41000#{6ac27878-a6fa-4155-ba85-f98f491d4f33}',
'\\\\?\\swd#wpdbusenum#{48eb3a98-2f21-11ef-8e0f-806e6f6e6963}#000000f424200000#{6ac27878-a6fa-4155-ba85-f98f491d4f33}',
'\\\\?\\swd#wpdbusenum#{23edccf0-2f0f-11ef-8e0e-806e6f6e6963}#0000000ea609c400#{6ac27878-a6fa-4155-ba85-f98f491d4f33}',
'\\\\?\\swd#wpdbusenum#{b347ef45-837e-11f0-9001-d843ae17473e}#00000000007e0000#{6ac27878-a6fa-4155-ba85-f98f491d4f33}',
'\\\\?\\swd#wpdbusenum#{48eb3a98-2f21-11ef-8e0f-806e6f6e6963}#0000000000004400#{6ac27878-a6fa-4155-ba85-f98f491d4f33}',
'\\\\?\\swd#wpdbusenum#{b7fc8a7d-993e-11ef-8eaf-14ac60bed6d1}#0000000000100000#{6ac27878-a6fa-4155-ba85-f98f491d4f33}',
'\\\\?\\swd#wpdbusenum#_??_usbstor#disk&ven_linux& prod_file-stor_gadget&rev_0401#8&36424527&0#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}#{6ac27878-a6fa-4155-ba85-f98f491d4f33}',
'\\\\?\\swd#wpdbusenum#{48eb3a98-2f21-11ef-8e0f-806e6f6e6963}#000001e848200000#{6ac27878-a6fa-4155-ba85-f98f491d4f33}']
No suitable MTP devices found

Looking for devices of type: SMART_DEVICE_APP
All IP addresses {'{4F039A90-D331-4E38-99A9-4F18BCAEBD97}': [{'addr': '192.168.1.16', 'netmask': '255.255.255.0', 'broadcast': '192.168.1.255'}], '{9974615E-7897-11EE-8DCD-806E6F6E6963}': [{'addr': '127.0.0.1', 'netmask': '255.0.0.0', 'broadcast': '127.255.255.255'}]}
No device is connected

Looking for devices...

Devices possibly connected: None

Windows recognized the Libra (this is as "Linux_file-stor_gadget")

My understanding is that the Libra should be recognized as an USB device - it is not - it appears only in the list of WPD ND:
'\\\\?\\swd#wpdbusenum#_??_usbstor#disk&ven_linux& prod_file-stor_gadget&rev_0401#8&36424527&0#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}#{6ac27878-a6fa-4155-ba85-f98f491d4f33}'

I have connected/disconnected the device all day, and Calibre recognized the device. I eject properly (or maybe I let it connected for charge) close the device and the day after no recognition...
There was no update on Kobo or Calibre, and it happened on 9.2.1 and 9.3.1.

Please note I am still able to connect via Calibre using the connect/share procedure...Except the database is not saved anymore; apparently this is possible only if the Libra is normally recognized as a peripheral, not a File.

I have also tested with an Aura H2O: no problem for the peripheral and the associated SD card. The same for various Pocketbooks...

It is baffling!

[theducks]

W10 assigns my L2 as F: And W10 does detect as a Linux File-Stor Gadget

Are you running other software on your L2? Than might change things.

Have you updated your Kobo Utilities PI in Calibre <<<There was backup save issues

[asw22]

The only software present on my L2 are Nickel and KOReader. The reder is sproperly recogbized and accessible by W (O: in my case).
I have upgraded Kobo Utilities but when I am connected in the File mode, all the actions pertaining to database (including saving) are greyed...

[asw22]

The funny thing is that I defined "User defined USB" Calibre driver with the L2 hex addresses obtained via Calibre, and desactivated the Kobo Calibre driver and this works...but I still cannot save the database, this feature is obviously linked to the recognition of the peripheral as a Kobo.
I have the feeling the Kobo driver for some reason has stopped recognizing my L2, even if still it recognizes the H2O...

[theducks]

Originally Posted by asw22

The funny thing is that I defined "User defined USB" Calibre driver with the L2 hex addresses obtained via Calibre, and desactivated the Kobo Calibre driver and this works...but I still cannot save the database, this feature is obviously linked to the recognition of the peripheral as a Kobo.
I have the feeling the Kobo driver for some reason has stopped recognizing my L2, even if still it recognizes the H2O...

Look in Preferences: Sharing: Ignored devices (may not be present if none)

[asw22]

Nope. Not Ignored.

[PeterT]

Originally Posted by asw22

The funny thing is that I defined "User defined USB" Calibre driver with the L2 hex addresses obtained via Calibre, and desactivated the Kobo Calibre driver and this works...but I still cannot save the database, this feature is obviously linked to the recognition of the peripheral as a Kobo.
I have the feeling the Kobo driver for some reason has stopped recognizing my L2, even if still it recognizes the H2O...

So what are the values you've used? I'd like to check them against what calibre expects

Sent from my Pixel 9a using Tapatalk

[asw22]

ID USB vendor: 0x525
ID USB Product: 0xa4a5
ID USB Rev: 0x401

The values have been communicated by Calibre with the USB Device recognition procedure

[PeterT]

I believe that Kobo's vendor ID is 0x2237

From github

    VENDOR_ID           = [0x2237]

and the devices

AURA_PRODUCT_ID     = [0x4203]
    AURA_EDITION2_PRODUCT_ID    = [0x4226]
    AURA_HD_PRODUCT_ID  = [0x4193]
    AURA_H2O_PRODUCT_ID = [0x4213]
    AURA_H2O_EDITION2_PRODUCT_ID = [0x4227]
    AURA_ONE_PRODUCT_ID = [0x4225]
    CLARA_HD_PRODUCT_ID = [0x4228]
    CLARA_2E_PRODUCT_ID = [0x4235]
    ELIPSA_PRODUCT_ID   = [0x4233]
    ELIPSA_2E_PRODUCT_ID   = [0x4236]
    FORMA_PRODUCT_ID    = [0x4229]
    GLO_PRODUCT_ID      = [0x4173]
    GLO_HD_PRODUCT_ID   = [0x4223]
    LIBRA_H2O_PRODUCT_ID = [0x4232]
    LIBRA2_PRODUCT_ID   = [0x4234]
    MINI_PRODUCT_ID     = [0x4183]
    NIA_PRODUCT_ID      = [0x4230]
    SAGE_PRODUCT_ID     = [0x4231]
    TOUCH_PRODUCT_ID    = [0x4163]
    TOUCH2_PRODUCT_ID   = [0x4224]
    # This product id is shared by Kobo Libra Color, Clara Color and Clara BW
    # as well as tolino shine 5, shine color and vision color. Sigh.
    LIBRA_COLOR_PRODUCT_ID = [0x4237]
    # Kobo says the following will be used in future firmware (end 2024/2025)
    CLARA_COLOR_PRODUCT_ID = [0x4238]
    CLARA_BW_PRODUCT_ID    = [0x4239]
    TOLINO_VISION_COLOR_PRODUCT_ID = [0x5237]
    TOLINO_SHINE_COLOR_PRODUCT_ID = [0x5238]
    TOLINO_SHINE_5THGEN_PRODUCT_ID = [0x5239]

    PRODUCT_ID          = AURA_PRODUCT_ID + AURA_EDITION2_PRODUCT_ID + \
                          AURA_HD_PRODUCT_ID + AURA_H2O_PRODUCT_ID + AURA_H2O_EDITION2_PRODUCT_ID + \
                          GLO_PRODUCT_ID + GLO_HD_PRODUCT_ID + \
                          MINI_PRODUCT_ID + TOUCH_PRODUCT_ID + TOUCH2_PRODUCT_ID + \
                          AURA_ONE_PRODUCT_ID + CLARA_HD_PRODUCT_ID + FORMA_PRODUCT_ID + LIBRA_H2O_PRODUCT_ID + \
                          NIA_PRODUCT_ID + ELIPSA_PRODUCT_ID + \
                          SAGE_PRODUCT_ID + LIBRA2_PRODUCT_ID + CLARA_2E_PRODUCT_ID + ELIPSA_2E_PRODUCT_ID + \
                          LIBRA_COLOR_PRODUCT_ID + CLARA_COLOR_PRODUCT_ID + CLARA_BW_PRODUCT_ID + \
                          TOLINO_VISION_COLOR_PRODUCT_ID + TOLINO_SHINE_COLOR_PRODUCT_ID + TOLINO_SHINE_5THGEN_PRODUCT_ID

    BCD = [0x0110, 0x0326, 0x401, 0x409]

[PeterT]

What f/w version is on the Kobo?

[PeterT]

And when you connect to the PC, do you have KOReader shutdown on the Kobo (ie it's sitting at the STANDARD Nickel homepage and/or the STANDARD Kobo reading software)?

[asw22]

The version is the last one finishing by 552.
Koreader is accessible via Nickel Menu but not activated (up until Saturday it was working fine in this configuration).

I an not sure to understand the question?

What I do not understand is why Calibre has stopped recognizing the Libra as a USB device, and now recognizes it as WPD ND:

'\\\\?\\swd#wpdbusenum#_??_usbstor#disk&ven_linux& prod_file-stor_gadget&rev_0401#9&160776aa&0#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}#{6ac27878-a6fa-4155-ba85-f98f491d4f33}',

[DNSB]

For what it may be worth, under Windows, a Libra 2 shows a USB VID of 2237 and a PID of 4234.

I am wondering if you had a connection issue and the device is stuck. Have you tried it on a different computer or even a different USB port? Though I'm not sure why you would be seeing a PLX Technologies device unless you managed to place the Libra 2 in a fastboot mode.

Next question would be what version of Linux you are running?

[asw22]

I have tried many ports and a hub; I have never had connection issues; whether by connecting the cable or via Nickel, the reader is always properly recognized by Windows 11; I can access to it vi Connect/Share files, and this allows me normal operations with the Libra (except no saving database);
Why is Calibre not brutally recognizing anymore the reader as a Kobo?
I will try another computer; and I will also get a high quality cable, you never know...

What f...ng software this is! I have been an aeronautical engineer all my life and I find the lack of robustness of the Kobo firmware beyond appalling (like we say in France "écrit avec les pieds")...I understand that it is not a flight control computer...but there are other devices without issues (PocketBook for instance)!