foliate icon indicating copy to clipboard operation
foliate copied to clipboard

Unable to open remote files with Nautilus

Open deschler opened this issue 4 years ago • 2 comments

Describe the bug Trying to open a remote file through GNOMEs file manager Nautilus fails and results in an error.

To Reproduce Steps to reproduce the behavior:

  1. Have Gnome configured to open epub files with Foliate
  2. Open a remote location in Nautilus (sftp or google-drive)
  3. Double-click an epub file to launch it with Foliate
  4. Foliate starts with error "Could not open file" "Empty response"

Expected behavior Foliate opens the epub, just like local ones.

Version:

  • Foliate version: 2.4.2
  • OS/Distribution and version: Ubuntu 20.04
  • Desktop environment: GNOME 3.36.3
  • Installation method: PPA (http://ppa.launchpad.net/apandada1/foliate/ubuntu focal/main amd64)

Additional context Opening remote files with other apps, like pdfs in the default viewer, works just fine.

deschler avatar Sep 20 '20 14:09 deschler

Any hope to fix this? This also affects samba shares. Here's what I see in the terminal while the UI shows "Could not open file, emtpy response":

`(WebKitWebProcess:2): dbind-WARNING **: 09:30:55.205: Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus-JCbfdHSIwv: No such file or directory

(com.github.johnfactotum.Foliate:97033): Gjs-WARNING **: 09:30:55.298: JS ERROR: Error: Empty Response _init/<@resource:///com/github/johnfactotum/Foliate/js/epubView.js:623:57 _handleAction@resource:///com/github/johnfactotum/Foliate/js/epubView.js:886:22 _init/<@resource:///com/github/johnfactotum/Foliate/js/epubView.js:617:18 main@resource:///com/github/johnfactotum/Foliate/js/main.js:476:24 run@resource:///org/gnome/gjs/modules/script/package.js:206:19 @/usr/bin/com.github.johnfactotum.Foliate:9:17`

esmorun avatar Oct 17 '21 07:10 esmorun

The same error (with the same stack trace) occurs on Fedora 35 with Foliate installed via DNF.

joreiff avatar Dec 12 '21 09:12 joreiff

This should be fixed with the new renderer (in the gtk4 branch). If not, it would be a WebKit bug. So I think it's safe to close this now. Feel free to comment if there are still issues.

johnfactotum avatar Mar 07 '23 15:03 johnfactotum