On 2020/03/09 20:16, Solene Rapenne wrote:
> On Tue, Feb 18, 2020 at 10:55:30AM +0100, Solene Rapenne wrote:
> > When I started calibre for the first time, I clicked on the button to choose
> > another location for the library files, then it hang.
> >
> > I started it again, choose default path, then when I click on "add a book",
> > file dialog appear totally grey with correct title, and it hangs, I get the
> > following output in the console.
> >
> > I'm running -current, I tried before and after updating packages today.
> >
> > Gimp also has an issue when using file dialog, I wonder if this is related.
> > There is no crash here, it just hang. I have no NFS mountpoints.
> >
> >
>
> It also happens on OpenBSD 6.6, I wonder when it started to not work.
>
> For what it's worth, wih calibre-2.85.1p12 the issue is still there.
>
A data point from me: it works here, both with my existing config, and
if I move away .config/calibre and start anew. FWIW I *do* have NFS
mountpoints and no problems from that. It is expected that there will be
some spew in the console (see below).
It's unlikely to be directly related to the gimp crash, it is a whole
different X11 stack (py-qt5 for calibre, Gtk+2 for gimp).
This is normal:
$ calibre
QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-sthen'
Failed to load libmtp, MTP device detection disabled
No module named libmtp
Exception in thread Thread-5:
Traceback (most recent call last):
File "/usr/local/lib/python2.7/threading.py", line 801, in __bootstrap_inner
self.run()
File "/usr/local/lib/calibre/calibre/gui2/device.py", line 409, in run
self.detect_device()
File "/usr/local/lib/calibre/calibre/gui2/device.py", line 267, in
detect_device
self.scanner.scan()
File "/usr/local/lib/calibre/calibre/devices/scanner.py", line 264, in scan
self.devices = self.scanner()
File "/usr/local/lib/calibre/calibre/devices/scanner.py", line 69, in __call__
self.libusb_err)
ValueError: DeviceScanner needs libusb to work. Error: No module named libusb
