From: Efraim Flashner <efraim@flashner.co.il>
To: Rutger Helling <rhelling@mykolab.com>
Cc: 31711@debbugs.gnu.org
Subject: bug#31711: qutebrowser is broken
Date: Wed, 6 Jun 2018 12:48:41 +0300 [thread overview]
Message-ID: <20180606094841.GD5242@macbook41> (raw)
In-Reply-To: <20180604141427.527a21b6@mykolab.com>
[-- Attachment #1: Type: text/plain, Size: 1254 bytes --]
On Mon, Jun 04, 2018 at 02:14:27PM +0200, Rutger Helling wrote:
> Hi Guix,
>
> qutebrowser fails to start with the recent python-pyqt upgrade,
> possibly due to the removed qtwebkit input.
>
> The following error occurs:
> ---
>
> Fatal error: QtWebEngine is required to run qutebrowser but could not
> be imported! Maybe it's not installed?
>
> The error encountered was:
> No module named 'PyQt5.QtWebEngineWidgets'
>
> Please search for the python3 version of QtWebEngine in your
> distributions packages, or install it via pip.
>
> Please search for the python3 version of QtWebEngine in your
> distributions packages, or install it via pip.
As part of upgrading Qt to 5.11 the pyqt module for qtwebkit broke so
qtwebkit was removed from pyqt in an attempt to allow other packages
that didn't rely on it to continue working. Unfortunately qutebrowser
got caught up in the middle.
Realistically we'd need to either re-enable qtwebkit as an input for
pyqt or package qtwebengine and use that in pyqt.
--
Efraim Flashner <efraim@flashner.co.il> אפרים פלשנר
GPG key = A28B F40C 3E55 1372 662D 14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2018-06-06 9:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-04 12:14 bug#31711: qutebrowser is broken Rutger Helling
2018-06-06 9:48 ` Efraim Flashner [this message]
2018-06-06 12:31 ` Gábor Boskovits
2020-04-25 8:58 ` bug#31711: closing Tom Zander via Bug reports for GNU Guix
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180606094841.GD5242@macbook41 \
--to=efraim@flashner.co.il \
--cc=31711@debbugs.gnu.org \
--cc=rhelling@mykolab.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.