Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#52958 - [uzbl-browser] Some commands fail without error in version 1:0.9.1+95+g3a4c70ad-1
Attached to Project:
Community Packages
Opened by Brandon Wilson (xelxebar) - Tuesday, 14 February 2017, 01:18 GMT
Last edited by Balló György (City-busz) - Tuesday, 14 February 2017, 23:48 GMT
Opened by Brandon Wilson (xelxebar) - Tuesday, 14 February 2017, 01:18 GMT
Last edited by Balló György (City-busz) - Tuesday, 14 February 2017, 23:48 GMT
|
Details## Summary
Commands like `scroll` and `event` seem to fall into a black hole in this version. It seems like uzbl-core is having problems communicating with uzbl-event-manager. Unfortunately, I haven't had a lot of time to do forensics, but the following error is sent to stdout repeatedly during use: ** (uzbl-core:99999): WARNING **: Error writing: Socket is already closed Which is coming from src/io.c:773 (commit g32347407) in upstream. I tried a manual compile of upstream at commit v0.9.1-22-g32347407 and this version runs without issue. Interestingly, running mixed versions---the package version of uzbl-core with upstream's uzbl-event-manager---also seems to run without issue. ## Version Info * package version(s) $ expac %v uzbl-core 1:0.9.1+95+g3a4c70ad-1 $ uzbl-core --version Commit: v0.9.1-95-g3a4c70ad ## Steps to Reproduce First, we get rid of custom config files and such: $ rm -r .config/uzbl/ Then we run uzbl-browser on a page large enough for scrolling: $ uzbl-browser 'https://kernel.org' Attempting to scroll with 'jkhl' or, in general, the `scroll` command acts as a no-op. Similarly for opening a new window. |
This task depends upon
Closed by Balló György (City-busz)
Tuesday, 14 February 2017, 23:48 GMT
Reason for closing: Upstream
Tuesday, 14 February 2017, 23:48 GMT
Reason for closing: Upstream
https://github.com/uzbl/uzbl/issues/323
We can't package the current stable version, because it depends on insecure webkitgtk.
Commit 32347407 on upstream master works just fine for me. Is the arch fork incompatible or just lagging a bit?
Also, did the move from webkitgtk happen in the last version bump? Was working for me up until I updated recently.
https://github.com/uzbl/uzbl/tree/next
The master branch still uses the insecure webkitgtk, so we can't use it.