Bug 403434

Summary:	Incompatible version of Qt/qutebrowser packaged
Product:	[KDE Neon] neon	Reporter:	Florian Bruhin <kde.org>
Component:	general	Assignee:	Neon Bugs <neon-bugs-null>
Status:	RESOLVED FIXED
Severity:	normal	CC:	bryantdl7, jr, neon-bugs-null, sitter
Priority:	NOR
Version First Reported In:	unspecified
Target Milestone:	---
Platform:	Other
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description Florian Bruhin 2019-01-20 15:09:56 UTC

Hi! I'm the upstream of qutebrowser: https://www.qutebrowser.org/

KDE Neon has a qutebrowser package from Ubuntu 18.04 available, v1.1.1.

Unfortunately, due to changes in Qt 5.11, qutebrowser versions before v1.3.0 crash immediately when starting. So far, I've received about 80 crash reports from KDE Neon users about this (three today alone).

Dealing with those and explaining the problem to people takes time I'd rather spend on something else, and frankly, I'm a bit tired of it.

I've been asking in IRC about this before, and I've been told there's little that can be done unless qutebrowser becomes a KDE project so it lands in KDE Neon in an updated version (which I'd rather not do, at least at the moment).

I'm not sure how a workable solution would look, but the current situation is quite bad IMHO. I'd even be fine with something like blacklisting qutebrowser so it can't be installed via apt, if that's possible. I guess I could also try to backport patches to v1.1.1, but there are typically more issues with every Qt upgrade (QtWebEngine isn't exactly backwards-compatible if you use enough details of it).

Comment 1 Harald Sitter 2019-03-13 12:33:44 UTC

The situation is fairly terrible to be sure.

If/when https://phabricator.kde.org/T10282 gets implemented we can supposedly hide it from software stores, alas, that does nothing for CLIs which generally offer no 100% way to prevent installation of something.

Perhaps a larger design goal behind this should be to actively force application installation to not ever go to distribution packages but instead go for snaps or flatpaks.

Comment 2 BRYANTDL7 2025-09-09 16:05:48 UTC

This ticket has been archived due to the age of this request, in order to keep currently present issues at the forefront for proper resolution. If this issue is still present, please reopen this ticket and provide additional details related to the request.