Re: Foliate does not work

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Sun, May 29, 2022 at 7:35 AM Samuel Sieb <samuel@xxxxxxxx> wrote:
>
> >>>>>>> I cannot be sure, but I suspect that after having upgraded to F36,
> >>>>>>> Foliate no longer works.
> >>>>>>>
> >>>>>>> Any ideas? Do others experience the same problem?
> >>>>>>
> >>>>>> You need to provide more details about what "not working" means.  I just
> >>>>>> installed it on F36 and opened an epub file with no problem.
> >>>>>
> >>>>> Thanks, Samuel. When I try to open whatever epub file, I get the
> >>>>> following error message:
> >>>>>
> >>>>> "Could not open file
> >>>>> Empty Response"
> >>>>
> >>>> "Empty Response" issues were discussed for multiple distros and install methods
> >>>> in foliate could not open file · Issue #401 · johnfactotum/foliate (github.com).
> >>>> It seems to stem from cross-origin protections:
> >>>>
> >>>> Quoting the wiki: By default, JavaScript and all external resources are blocked in Foliate.
> >>>> For additional safeguard against potential vulnerabilities it is recommended to run Foliate
> >>>> in a sandboxed environment, for example, by using the Flatpak package.
> >>>
> >>> Thanks, George. That is exactly the same problem I am having!
> >>
> >> That issue is all over the place.  It mostly seemed to be referring to
> >> the snap install, but then there were a couple of mentions of other
> >> types.  The rpm version works perfectly fine for me.  Is that what you
> >> are using?  Where is the file you're trying to open?
> >
> > Thanks, Samuel. The reported error corresponds to the rpm version of
> > foliate. The flatpak foliate package works perfectly.
>
> Did you see the comment about deleting the user local mime.cache file?
> That might explain the difference.  Mine is a new install and I've never
> associated epub files with anything.  If you don't want to delete it,
> then try temporarily moving it somewhere else and see if that solves
> your problem.

Thanks, Samuel and George. By removing the file

~/.local/share/mime/mime.cache

as suggested in the mentioned comment, the problem was fixed!

Paul
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure



[Index of Archives]     [Older Fedora Users]     [Fedora Announce]     [Fedora Package Announce]     [EPEL Announce]     [EPEL Devel]     [Fedora Magazine]     [Fedora Summer Coding]     [Fedora Laptop]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Desktop]     [Fedora Fonts]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Yosemite News]     [Gnome Users]     [KDE Users]     [Fedora Art]     [Fedora Docs]     [Fedora Sparc]     [Libvirt Users]     [Fedora ARM]

  Powered by Linux