Bug 361281 - migrate away from qtwebkit (gui)
Summary: migrate away from qtwebkit (gui)
Status: RESOLVED FIXED
Alias: None
Product: ksysguard
Classification: Unmaintained
Component: libksysguard (show other bugs)
Version: 5.6.1
Platform: Other Linux
: NOR wishlist
Target Milestone: ---
Assignee: Plasma Development Mailing List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-04-01 14:34 UTC by Miklos Karacsony
Modified: 2020-07-05 22:23 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Miklos Karacsony 2016-04-01 14:34:13 UTC 
libksysguard still depends on qtwebkit, which was deprecated by the qt developers in the latest release. you can still build it from source, but it would be a good idea to migrate away from it. use something like webengine instead.

Reproducible: Always

Steps to Reproduce:
1. try to build libksysguard without qtwebkit installed
2. 
3.

Actual Results:  
it builds without gui

Expected Results:  
it builds the gui component as well
Comment 1 Fabian Vogt 2016-08-30 19:25:28 UTC 
With KDE Applications 16.08, ksysguard seems to be the only application depending on Qt WebKit.
It should be migrated to either use QML for the memory details view or WebEngine.
Comment 2 Martin Flöser 2016-08-31 06:09:08 UTC 
KSysguard is a workspace component. As long as https://bugreports.qt.io/browse/QTBUG-55384 is not fixed we should not port any workspace component to WebEngine.
Comment 3 groot 2020-07-05 22:23:38 UTC 
This has happened some time in the past nearly-four years. (The bug Martin refers to has been fixed since Qt 5.10, it seems)