glib2 2.72.0 causes "Empty response" #878

tummychow · 2022-03-23T06:41:40Z

Describe the bug
Opening any epub causes foliate to show "Could not open file" with this output:

(com.github.johnfactotum.Foliate:16547): Gjs-WARNING **: 23:22:45.931: 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:478:24
run@resource:///org/gnome/gjs/modules/script/package.js:206:19
@/usr/bin/foliate:9:17

To Reproduce
Open any epub with glib2 2.72.0

Version:
This is with Arch Linux's foliate 2.6.4-1 and glib2 2.72.0-1. Downgrading to Arch's glib2 2.70.4-2 fixes the issue. Honestly, I have no idea why. From past foliate issues, I assumed some other gtk package was involved (eg webkit2gtk 2.36.0-1 to 2.34.6-1, gjs 2:1.70.2-1 to 2:1.70.1-2, js78 78.15.0-4 to 78.15.0-3) but those downgrades don't fix it; only the glib2 downgrade has any effect.

The text was updated successfully, but these errors were encountered:

ksdrummer · 2022-03-23T21:33:29Z

I confirm that I have the exact same bug on arch : foliate 2.6.4-1 and glib2 2.72.0-1.

(com.github.johnfactotum.Foliate:362831): Gjs-WARNING **: 17:27:09.374: 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:478:24 run@resource:///org/gnome/gjs/modules/script/package.js:206:19 @/usr/bin/foliate:9:17

johnfactotum · 2022-03-24T07:11:02Z

For some reason I can't seem to reproduce this. Have glib2 2.72.0-1. Built both 2.6.4 and master and all seems fine.

tummychow · 2022-03-24T07:27:45Z

Interesting... I tried a few other downgrades thinking maybe glib2 was a red herring, but these also have no effect:

glib-networking 1:2.72.0-1 to 1:2.70.1-1
gobject-introspection-runtime 1.72.0-1 to 1.70.0-5
tracker3 3.3.0-1 to 3.2.1-2
gtk3 1:3.24.33-2 to 1:3.24.33-1

I'm not sure how something low in the stack (like glib2) could cause this error. Any additional debugging I can do to help?

johnfactotum · 2022-03-24T10:15:12Z

I don't really have any idea. But here's a somewhat minimal script for reproducing the problem:

#!/usr/bin/gjs
const fetchURI = 'file:///home/user/test'
const pageURI = 'file:///usr/share/com.github.johnfactotum.Foliate/assets/epub-viewer.html'

imports.gi.versions.Gtk = '3.0'
imports.gi.versions.WebKit2 = '4.0'
const { Gtk, WebKit2 } = imports.gi

const app = new Gtk.Application({ application_id: 'org.gtk.Example' })

const script = `fetch('${fetchURI}').then(res => res.text()).then(text => alert(text))`

app.connect('activate', () => {
    const win = new Gtk.ApplicationWindow({ application: app })
    const webView = new WebKit2.WebView({
        settings: new WebKit2.Settings({
            enable_write_console_messages_to_stdout: true,
            enable_developer_extras: true,
            allow_universal_access_from_file_urls: true,
        }),
    })
    webView.connect('load-changed', (_, event) =>
        event === WebKit2.LoadEvent.FINISHED
            ? webView.run_javascript(script, null, () => {}) : null)
    webView.load_uri(pageURI)
    win.add(webView)
    win.show_all()
})

app.run([])

To run this script you first need to make sure that /home/user/test exists by running, say, echo "Hello" > /home/user/test. The pageURI on the second line can be change to point to whatever local HTML page you have (in case Foliate isn't installed on the default location). If it alerts "Hello", then it works. Otherwise you would see the "Empty response" error either logged in the terminal or in WebKit's devtools console.

If one can reproduce with this GJS example, then it's probably a good idea to try to reproduce it in C as well and submit a bug to the WebKitGTK devs.

tummychow · 2022-03-24T20:36:26Z

Hmm, running through those steps (with echo "Hello" > /mnt/home/test) gives me this output:

CONSOLE SECURITY ERROR Cross origin requests are only supported for HTTP.
CONSOLE JS ERROR Fetch API cannot load file:///mnt/home/test due to access control checks.
CONSOLE JS ERROR Unhandled Promise Rejection: TypeError: Load failed

which seems... like an error, but not quite the same as the "Empty response" error. Downgrading glib2 does fix it; the window shows a "Hello" alert with this output instead:

CONSOLE SECURITY ERROR The Content Security Policy directive 'sandbox' is ignored when delivered via an HTML meta element.

I'll see about filing that upstream bug.

edit: https://bugs.webkit.org/show_bug.cgi?id=238347

johnfactotum · 2022-03-25T08:14:58Z

Perhaps it's related to how your filesystem is set up, as I still cannot reproduce it.

In any case, in the future we really want to stop making requests to files, which is not only unreliable, but also insecure, and bad for performance as the whole file is loaded in memory. Instead it should either set up a local server, or somehow get a File object.

ksdrummer · 2022-03-25T16:02:36Z

I don't know if it's really useful, but the script gave me the same output...

tummychow · 2022-03-25T19:58:44Z

Yeah I'm also going to investigate miscellaneous filesystem and DNS related things. glib2 2.72.0 has other peculiar behaviors on my system (eg the GTK file picker no longer shows mountpoints in the "other locations" list) which seem to be in the same ballpark as this. There must be something that makes the file:// request "look" cross-origin that's specific to my setup.

johackim · 2022-03-26T16:27:56Z

Temporary solution on Arch Linux with the downgrade command :

sudo downgrade glib2=2.70.4-1

kauesena · 2022-03-31T00:20:15Z

I'm on Arch and @johackim's suggestion solved it for me. It did not work simply by opening foliate as soon as I downgraded, I had to open a specific file. I do not have the downgrade package, but I used the native command:

pacman -U https://archive.archlinux.org/packages/g/glib2/glib2-2.70.4-1-x86_64.pkg.tar.zst

And then added

IgnorePkg=glib2

to /etc/pacman.conf.

truealex · 2022-04-05T09:39:20Z

I confirm there is a bug. if I roll back to the previous version of glibc, after rebooting, my desktop and taskbar do not appear. How to read books now?

Kandelai · 2022-04-07T20:07:19Z

I rolled back using @johackim solution and Foliate worked for me as well, using Garuda Linux/Arch.

lhirlimann · 2022-04-14T07:49:48Z

strace.log.gz

Strace log of the issue on fedora 36 if it can help.

Kandelai · 2022-04-17T14:54:46Z

Appears with the latest Arch updates, downgrading glib2 no longer works, thus no YacReader, also, still doesn't work with latest glib2 2.72.0-1. Running in terminal gets me;

'YACReader: error while loading shared libraries: libicuuc.so.70: cannot open shared object file: No such file or directory'

FedericoCeratto · 2022-04-18T10:55:18Z

FWIW the bug seems to appear on Debian as well but I cannot reproduce it on my hosts using glib 2.72.1

thebiblelover7 · 2022-04-21T10:29:43Z

I can reproduce this too

tummychow · 2022-04-22T01:10:58Z

Some more investigation updates:

2.72.1 does not fix the issue on Arch
I was able to bisect the issue to glib2 commit https://gitlab.gnome.org/GNOME/glib/-/commit/60173d0a387b45016684be8846c291dabd0aa5e8 which is rather horrifying because this is a merge of changes from an upstream library and I can't imagine how it's related. At least it gives me some hints on how some systems repro and others don't. (e: filed a bug for glib2 as well https://gitlab.gnome.org/GNOME/glib/-/issues/2639)

archisman-panigrahi · 2022-04-22T07:25:20Z

I cannot reproduce this issue with glib2 2.72.1-1 in Arch Linux MATE, and EndeavourOS KDE. Is this issue specific to GNOME?

moll · 2022-04-22T09:27:21Z

I can confirm @tummychow's comment that upgrading to glib2 v2.72.1-1 on Arch Linux does not seem to fix the issue.

bgvaughan · 2022-04-22T20:38:39Z

I filed a bug for Debian. I'm using Debian Sid with XFCE, not with Gnome, and foliate still doesn't work after updating to glib2 v2.72.1-1.

Kandelai · 2022-04-24T17:28:21Z

I am confused, why are users filing bug reports with their distro maintainers? Isn't this an issue for the Foliate maintainer to update Foliate to work with the latest Glib2?

tummychow · 2022-04-24T20:32:01Z

@Kandelai pretty sure foliate is already doing the right thing here - it's passing the option that disables cross origin restrictions for file urls. So the fact that it's failing a file url request, with a cross origin error message, certainly looks like an upstream bug. (As I've already said, I don't know how webkit2gtk and glib2 can interact in a way that causes this outcome. My guess is both are at fault in some way and glib2 happened to to be the one that revealed the issue.)

FedericoCeratto · 2022-04-24T20:34:09Z

@Kandelai because sometimes bugs are due to interactions between library versions or other OS components and so on and can be fixed by the package maintainer.
[I'm the maintainer of the Debian package]

eksperimental · 2022-04-24T22:29:43Z

If you are on Arch Linux and you use Cinnamon, DO NOT DOWNGRADE glib2 to 2.70.4-1
Your graphical interface will become unusable.

adamensler · 2022-04-27T05:19:24Z

Arch w/ Gnome shell 42 here. Encountered the same issue and found the downgrade trick above worked.

landfish2102 · 2022-05-05T19:43:20Z

I encountered this bug on Arch, but after deleting the file ~/.local/share/mime/mime.cache, I am now able to open ebooks with foliate 2.6.4 and glib 2.72.1 without problems. WARNING: removing this file may unset all your default applications and filetype associations!

This might provide a workaround for others that can't downgrade glib2.

Based on Michael Catanzaro's comment at https://gitlab.gnome.org/GNOME/glib/-/issues/2639, it appears that the upstream bug is triggered if an application has been set as default for the .html extension, which happens after Firefox is set as the default web browser. Deleting the mime database clears this default, at least temporarily. The following upstream issues are also relevant.

rokezu · 2022-05-11T21:34:09Z

Just to confirm the same bug on Arch Linux as fellow users of that distribution and same versions, hopefully a solution will be found. I'd rather not mess with mime.cache or downgrades of core packages.

eksperimental · 2022-05-11T21:40:14Z

Just to confirm the same bug on Arch Linux as fellow users of that distribution and same versions, hopefully a solution will be found. I'd rather not mess with mime.cache or downgrades of core packages.

Do not downgrade! I messed up my environment.

You can install it from Snap store, it works just fine.

Vednier · 2022-05-16T20:41:22Z

Oh well, having same problem on Ubuntu Mate 22.04 with same glib 2.72, so its global problem. Interestingly enough, Atril - Mate's standard viewer for PDF and epub have lost ability to show epub file at same time.

kauesena · 2022-05-18T22:06:48Z

Since my last comment, I have reinstalled ArchLinux and I can now use Foliate 2.6.4 (the most recent) with glib2 2.72.1-1 via the package foliate from the Community repository.

winteriscariot · 2022-05-19T01:42:51Z

Since my last comment, I have reinstalled ArchLinux and I can now use Foliate 2.6.4 (the most recent) with glib2 2.72.1-1 via the package foliate from the Community repository.

can you re-check this? I just did the same on my Arch install and i'm still getting the same error. Please verify your versions: i don't believe this issue is resolved. (there's been no update to Foliate that i can tell, nor to glib2, that would have fixed anything)

archisman-panigrahi · 2022-05-19T02:06:34Z

Reinstalling Arch created a new version of mime.cache which might have fixed the issue.

…

On Thu, 19 May, 2022, 7:13 am winteriscariot, ***@***.***> wrote: Since my last comment, I have reinstalled ArchLinux and I can now use Foliate 2.6.4 (the most recent) with glib2 2.72.1-1 via the package foliate from the Community repository. can you re-check this? I just did the same on my Arch install and i'm still getting the same error. Please verify your versions: i don't believe this issue is resolved. (there's been no update to Foliate that i can tell, nor to glib2, that would have fixed anything) — Reply to this email directly, view it on GitHub <#878 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAXL2XCGDW6AD23EXXJI643VKWMCTANCNFSM5RNA6IBA> . You are receiving this because you commented.Message ID: ***@***.***>

kauesena · 2022-05-19T02:23:53Z

@winteriscariot I have just rechecked the versions (using pacman -Qi) of glib2 and Foliate and they are respectively 2.72.1-1 and 2.6.4-1.

kauesena · 2022-05-19T02:34:06Z

If you (plural) need me to provide more information on my system or run any test, I'd be happy to oblige. I can think of no difference between the current installation from the previous one except that I've replaced the common kernel with the zen kernel and that I've started using LVM. However, I do not think such changes would interfere. The change must be of the sort @apandada1 mentioned.

rokezu · 2022-05-20T23:29:07Z

Well, I deleted mime.cache (mine was a file from 2011, not updated since then‽) and Foliate is working again, rebooted several times for a couple of days now, still working. File associations and such for other apps didn't change. I have no idea what is going on with these modern apps that resort to such convoluted ways to do an fopen() but well... So far this is working for me? In my case I just wanted to double check some ePubs from Humble Bundle that can't be opened correctly in my e-reader or with Calibre, and Foliate opened and formatted it successfully! I'm reading a comic at the moment. 😄📖

argosatcore · 2022-05-24T23:15:59Z

Well, I deleted mime.cache (mine was a file from 2011, not updated since then‽) and Foliate is working again, rebooted several times for a couple of days now, still working. File associations and such for other apps didn't change. I have no idea what is going on with these modern apps that resort to such convoluted ways to do an fopen() but well... So far this is working for me? In my case I just wanted to double check some ePubs from Humble Bundle that can't be opened correctly in my e-reader or with Calibre, and Foliate opened and formatted it successfully! I'm reading a comic at the moment. smilebook

This worked for me too on Debian Sid. After deleting ~/.local/share/mime/mime.cache, foliate started working again without any apparent issues. However, if I restore the deleted mime.cache file or recreate it via update-mime-database ~/.local/share/mime, the issue resurfaces.

chillycuz · 2022-05-31T05:44:28Z

I have the same exact experience as @argosatcore on fully updated Arch Linux 5.18, including failure after update-mime-database.

feute · 2022-06-22T04:32:19Z

I started having this issue on Fedora 36 with everything up to date. Deleting ~/.local/share/mime/mime.cache solved it.

Arkoprovo1996 · 2022-06-26T14:48:24Z

I started having this issue on Fedora 36 with everything up to date. Deleting ~/.local/share/mime/mime.cache solved it.

Wow, yes. I did too, on Manjaro and it fixed the issue. Thanks so much!! ♥

okias · 2022-06-28T09:45:17Z

on Debian removing ~/.local/share/mime/mime.cache also helped. It's nice we have workaround.

truealex · 2022-06-28T11:43:21Z

~~on latest Arch advice to delete mime.cache file does not work~~
sorry, it works

argosatcore · 2022-07-05T23:28:47Z

This issue has been fixed on Debian Sid. [1] It looks like the culprit was glib and is now fixed on version 2.72.3.

After running update-mime-database ~/.local/share/mime, I can now open EPUB files without a problem, and foliate works as expected.

[1] See: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009669

wenzezlaus · 2022-07-06T05:12:20Z

As well, on Arch the issue is fixed with glib2 updated to v. 2.72.3

kauesena · 2022-07-06T22:18:49Z

I second what @wenzezlaus reported. Somehow the issue reappeared to me some days ago but updating the system getting glib2.72.3 made foliate work again.

johnfactotum · 2022-09-23T19:05:21Z

Closing as it seems to have been fixed.

tummychow added the bug Something isn't working label Mar 23, 2022

jonathonf mentioned this issue Mar 27, 2022

Can't open any ebook #880

Closed

This was referenced Apr 12, 2022

Foliate doesn't open books on Fedora 36 #885

Closed

Foliate stopped working on Ubuntu 22.04 #879

Closed

johnfactotum mentioned this issue Apr 16, 2022

Could not open any file #886

Closed

rahulTPatil mentioned this issue May 8, 2022

mobi: Error ( The string did not match the expected pattern ) #893

Closed

khaled mentioned this issue May 16, 2022

foliate fails to open files NixOS/nixpkgs#173166

Closed

This comment was marked as outdated.

Sign in to view

mxschumacher mentioned this issue Jun 1, 2022

foliate could not open file #401

Open

iambumblehead mentioned this issue Jun 19, 2022

Endlessly loading #848

Closed

johnfactotum closed this as completed Sep 23, 2022

johnfactotum mentioned this issue Oct 21, 2022

New renderer #962

Closed

johnfactotum mentioned this issue Nov 13, 2022

Can't Import Books and Can't open books #934

Closed

johnfactotum mentioned this issue Dec 5, 2023

Catalogs broken due to Cross-Origin control error on Ubuntu 22.04 (PPA install) #918

Closed

glib2 2.72.0 causes "Empty response" #878

glib2 2.72.0 causes "Empty response" #878

Comments

tummychow commented Mar 23, 2022

ksdrummer commented Mar 23, 2022 • edited Loading

johnfactotum commented Mar 24, 2022

tummychow commented Mar 24, 2022 • edited Loading

johnfactotum commented Mar 24, 2022

tummychow commented Mar 24, 2022 • edited Loading

johnfactotum commented Mar 25, 2022

ksdrummer commented Mar 25, 2022

tummychow commented Mar 25, 2022

johackim commented Mar 26, 2022 • edited Loading

kauesena commented Mar 31, 2022 • edited Loading

truealex commented Apr 5, 2022

Kandelai commented Apr 7, 2022

lhirlimann commented Apr 14, 2022

Kandelai commented Apr 17, 2022

FedericoCeratto commented Apr 18, 2022

thebiblelover7 commented Apr 21, 2022

tummychow commented Apr 22, 2022 • edited Loading

archisman-panigrahi commented Apr 22, 2022

moll commented Apr 22, 2022

bgvaughan commented Apr 22, 2022

Kandelai commented Apr 24, 2022

tummychow commented Apr 24, 2022

FedericoCeratto commented Apr 24, 2022

eksperimental commented Apr 24, 2022 • edited Loading

adamensler commented Apr 27, 2022

landfish2102 commented May 5, 2022

rokezu commented May 11, 2022

eksperimental commented May 11, 2022

Vednier commented May 16, 2022

kauesena commented May 18, 2022 • edited Loading

winteriscariot commented May 19, 2022

archisman-panigrahi commented May 19, 2022 via email

kauesena commented May 19, 2022

kauesena commented May 19, 2022

This comment was marked as outdated.

rokezu commented May 20, 2022

argosatcore commented May 24, 2022 • edited Loading

chillycuz commented May 31, 2022

feute commented Jun 22, 2022

Arkoprovo1996 commented Jun 26, 2022

okias commented Jun 28, 2022

truealex commented Jun 28, 2022 • edited Loading

argosatcore commented Jul 5, 2022

wenzezlaus commented Jul 6, 2022

kauesena commented Jul 6, 2022

johnfactotum commented Sep 23, 2022

ksdrummer commented Mar 23, 2022 •

edited

Loading

tummychow commented Mar 24, 2022 •

edited

Loading

tummychow commented Mar 24, 2022 •

edited

Loading

johackim commented Mar 26, 2022 •

edited

Loading

kauesena commented Mar 31, 2022 •

edited

Loading

tummychow commented Apr 22, 2022 •

edited

Loading

eksperimental commented Apr 24, 2022 •

edited

Loading

kauesena commented May 18, 2022 •

edited

Loading

argosatcore commented May 24, 2022 •

edited

Loading

truealex commented Jun 28, 2022 •

edited

Loading