Qutebrowser is outstanding on Linux.
It's totally unusable on FreeBSD - a real shame as it's by far the best browser for i3.
Hi,
i-bsd, Always acknowledge the possibility that what may at first glance appear as absolutely true for you, might not be likewise for others
In my case QuteBrowser runs so pretty and fast on FreeBSD that I was thinking of asking devs why would they have actually put heavy Chromium's QtWebEngine in its code (but yes, I know the other reasons why they chose WebEngine over WebKit for).
I run QuteBrowser on Linux as well, and If I were asked to tell whether of not I actually noticed a concrete difference in Linux with QtWebEngine, well the answer would be 'no'
A live screenshot of my desktop with Qutebrowser currently playing a Youtube video
:
Aside from chat,
a) In case it crashed on loading media content, are you sure you enabled plugins?
:set content.plugins true
Adobe Flash-Player closed-source plugin (for flashplayer)
or GStreamer-plugins (for HTML5) are required to be installed:
- for flashplayer, install
www/nspluginwrapper,
www/linux-flashplayer, and
www/flashplayer in that order
- for HTML5, install
multimedia/gstreamer-plugins, and
multimedia/gstreamer1-libav
I haven't tested HTML5 on Qutebrowser, as currently I have flashplayer installed, but I plan on migrating to HTML5, being flashplayer still only barely alive
b) In case it crashed on standard browsing, given Qutebrowser was only very recently added as binary package (but it's already been on ports' tree for a while):
- may it be that you build a binary-based system, but compiled qutebrowser from ports as it was unavailable as package? I believe
www/py-qt5-webkit*** and the other python dependencies are a version behind in packages
. Also, Is it possible you ran
pkg autoremove
in such a case, and deleted some of the dependencies, since, being qutebrowser not listed in
/var/db/pkg, those dependencies were instead perceived as orphans by pkgng?
- if you are instead on a source-based system, may it be you compiled some o the dependencies with incompatible options? This is another common mistake one can unwillingly commit when building the whole userland from source the first time (I confess having run in similar issues
)
**
Looking at your bug-report, I remember having seen Qt5-Webkit segmentation faults errors being reported elsewhere as due to mismatch between WebKit versions.
Finally, keep in mind that some Facebook and Reddit pages have been reported crashing QuteBrowser with QtWebKit
Off-Topic: I saw You wondered how to get a stack trace on FreeBSD for debugging purposes: like in Linux, you could use
gcore(1) to create a .core image of process
python3.6 /usr/local/bin/qutebrowser
like:
%
ps -axf | grep python3.6 | grep -
Code:
1483 - S 0:04.33 /usr/local/bin/python3.6 /usr/local/bin/qutebrowser
%
gcore -s -f python3.6 1483
, where '1483', is the $PID found above
And then use
gdb(1) over it:
%
gdb python3.6 core.1483
finally type
bt
to get a backtrace and navigate into it.
I suppose it should be even easier, and surely more polished, by simply using
DTrace, but I haven't found the time to dig into its man page yet, but if you feel keen to:
dtrace(1)...and here's the
Tutorial on FreeBSD wiki
PS: The only other Web Browser I use, aside QuteBrowser is
www/qupzilla-qt5. It's a feather, yet full of features...always been fond of Qupzilla