GNOME Bugzilla – Bug 789735
Web problem with Squirrelmail
Last modified: 2018-05-11 13:22:05 UTC
Login to SquirrelMail okay, but clicking menu items fails with a request for login. Works correctly with uzbl web browser. Using Xubuntu 17.10 with latest version of Web (epiphany-browser) in Ubuntu repository. SquirrelMail version 1.4.22
Do you see any errors in the web inspector?
No errors in web inspector.
OK... with nothing more to go on, I can redirect you to WebKit Bugzilla, but unfortunately it's quite unlikely this issue receive much attention unless the SquirrelMail developers can find something specific wrong in WebKit. Thanks for taking the time to report this. This issue is most likely a bug in WebKit. Please report the bug to https://bugs.webkit.org/ including a link to this bug report and noting the version of WebKitGTK+ that you have installed. When reporting the WebKit bug, be sure to include the prefix '[GTK]' in the bug summary and select the 'WebKit Gtk' component.
It doesn't appear to be a problem with WebKit. As I said, it works correctly with uzbl which is a minimal WebKit browser. What else do you need to know to replicate the problem?
uzbl is using an ancient version of WebKitGTK+, so that comparison is not interesting. I would recommend uninstalling that, since it's vulnerable to hundreds of security bugs from 2014 on. Please check in MiniBrowser. If you use Fedora, you'll find it at /usr/libexec/webkit2gtk-4.0/MiniBrowser and in the webkitgtk4-devel package. On other distros it's going to be under /usr/lib somewhere and the package will be named differently. You'll almost certainly be able to reproduce the problem in MiniBrowser, but if not, then that would indicate it likely is indeed an Epiphany problem.
I think you are correct. I don't see MiniBrowser, so I tried Qupzilla. Same problem. Thanks :-)
QupZilla doesn't even use WebKit, it uses Chromium. Please, don't report website bugs here; Epiphany just controls the user interface around the web view. Bugs with websites need to be reported on WebKit Bugzilla almost always. Pretty much the only Epiphany component that can break websites is the adblocker (which is worth turning off as a test).
Arora works. Arora uses WebKit and only WebKit2 is installed in system. Are you able to use Squirrelmail with Epiphany?
(In reply to Technical Support from comment #8) > Arora works. Arora uses WebKit and only WebKit2 is installed in system. It uses QtWebKit... you really need to check WebKitGTK+ MiniBrowser, it's the only way we can figure out if something is wrong in Epiphany or in WebKit. > Are you able to use Squirrelmail with Epiphany? I don't intend to create an account to check.
Also failing is netsurf and dillo. I wonder if Web, Netsurf, and Dillo share a package that has the problem? I don't suppose you have a .deb of MiniBrowser or know where I could get one. Either that, or is there another WebKit2 browser you would like me to try. Small packages preferred, but I can try something bigger if it will help. Do you want me to set up a squirrelmail account for you to see the problem for yourself?
Sorry, I missed in the first post that you were using Ubuntu. Looks like MiniBrowser is installed in the main WebKitGTK+ package, so you should already have it. Look for /usr/lib/<multiarch triplet>/webkit2gtk-4.0/MiniBrowser. (In reply to Technical Support from comment #10) > Also failing is netsurf and dillo. I wonder if Web, Netsurf, and Dillo share > a package that has the problem? That's not very likely. (In reply to Technical Support from comment #10) > Do you want me to set up a squirrelmail account for you to see the problem > for yourself? I guess you could, but first let's figure out if it's an Epiphany problem or a WebKit problem.
Surf-2 uses WebKit2 and works. Minibrowser has the same problem as the others. The problem *appears* to be with Epiphany, but it is a very common problem.
(In reply to Technical Support from comment #12) > Surf-2 uses WebKit2 and works. Finally, you found an appropriate comparison. I had forgotten about this one! > Minibrowser has the same problem as the others. Huh. Try changing the cookies policy in the preferences dialog to Always Accept. Does that help?
Yeah, thanks for the information on MiniBrowser. It's strange that Surf-2 works and MiniBrowser doesn't. Changing cookies policy doesn't help. Though it does make sense that the problem has something to do with cookie management.
The problem now appears to be fixed in MiniBrowser. Still broken in Epiphany. WebKitGTK+ 2.20.2 SquirrelMail version 1.4.22 Most recent updates from Ubuntu 18.4 repository (main, universe, restricted, multiverse, partner; security, updates, backports) Epiphany 3.28.1 Clicking on any email message returns "You must be logged in to access this page." error. Surf-2.0 and MiniBrowser (supplied with WebKit) Clicking on any email message returns the content of the message as expected. Firefox Clicking on any email message returns the content of the message as expected.
Try changing cookies to always accept. And disable the adblocker for good measure (though that's probably not it this time).
Neither option makes a difference.
One final test: find the Epiphany web extension (usually /usr/lib64/epiphany/web-extensions/libephywebextension.so) and, as root, move it away to someplace safe. Then try again. This will completely disable all Epiphany code running in the web process. That will tell us which bug report we need to keep open. :)
Removed libephywebextension.so from /usr/lib/x86_64-linux-gnu/epiphany-browser/web-extensions The web-extensions folder is confirmed empty. Tried squirrelmail. No change. Continue using Epiphany browser as before. No change. I'm not clear. What does libephywebextension.so do? Are there any other experiments that might help?
(In reply to Technical Support from comment #19) > I'm not clear. What does libephywebextension.so do? It gets dlopened by WebKit, and is what Epiphany uses to run code in the web process. Removing it was a big hammer to test whether Epiphany is doing something to break the page. Since it's still broken after removing the web extension, we can conclude that this is a WebKit problem, even if we don't know how to reproduce it in MiniBrowser yet. So let's track this in https://bugs.webkit.org/show_bug.cgi?id=179101 rather than on GNOME Bugzilla. P.S. In the future, please don't open bugs on both Bugzillas unless we ask you to!