Bug 487708 - akregator 6.1.0 does not apply dark theme to the article content pane although the desktop uses a Dark Theme.
Summary: akregator 6.1.0 does not apply dark theme to the article content pane althoug...
Status: REPORTED
Alias: None
Product: akregator
Classification: Applications
Component: internal browser (show other bugs)
Version: 6.1.0
Platform: Manjaro Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords: qt6
: 489828 (view as bug list)
Depends on:
Blocks:
 
Reported: 2024-05-28 19:23 UTC by whatifgodwasoneofus
Modified: 2024-07-23 21:23 UTC (History)
4 users (show)

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


Attachments
Akregator 5.19.3 with dark color theme on Kubuntu 22.04.4 (139.76 KB, image/png)
2024-07-17 13:10 UTC, Ivan Petrunko
Details

Note You need to log in before you can comment on or make changes to this bug.
Description whatifgodwasoneofus 2024-05-28 19:23:25 UTC
STEPS TO REPRODUCE
1. Set the desktop's them to Breeze Dark
2. open Akregator, select a feed's article

OBSERVED RESULT
The article content is NOT rendered using the dark theme.

EXPECTED RESULT
The article content must be rendered using the dark theme.

SOFTWARE/OS VERSIONS

KDE Plasma Version: 6.0.5
KDE Frameworks Version:  6.2.0
Qt Version: 6.7.1

ADDITIONAL INFORMATION
If I launch akregator forcing the dark mode via QT Web Engine env var, it works as expected:
```
QTWEBENGINE_CHROMIUM_FLAGS="--blink-settings=darkModeEnabled=default" akregator
```
However, it should work without this hack. My desktop theme changes during the day (via koi), and I'd like to enjoy this feature "dynamically".

This is a long-awaited feature for akregator, which is available starting from v6.1.5 (24.05.0). Maybe it has not been thoroughly tested on all platforms?
Comment 1 whatifgodwasoneofus 2024-05-28 19:26:37 UTC
(In reply to whatifgodwasoneofus from comment #0)
> QTWEBENGINE_CHROMIUM_FLAGS="--blink-settings=darkModeEnabled=default"

Sorry, the correct cmdline for the workaround is:
QTWEBENGINE_CHROMIUM_FLAGS="--blink-settings=darkModeEnabled=true" akregator
Comment 2 victorhck 2024-06-05 14:05:50 UTC
same issue here:

Operating System: openSUSE Tumbleweed 20240531
KDE Plasma Version: 6.0.5
KDE Frameworks Version: 6.2.0
Qt Version: 6.7.1
Kernel Version: 6.9.3-1-default (64-bit)
Graphics Platform: X11

Even if I run the hack shared, it doesn't works. I get this message:

$ QTWEBENGINE_CHROMIUM_FLAGS="--blink-settings=darkModeEnabled=true" akregator  

Path override failed for key base::DIR_APP_DICTIONARIES and path '/usr/bin/qtwebengine_dictionaries'
Path override failed for key base::DIR_APP_DICTIONARIES and path '/usr/libexec/qt6/qtwebengine_dictionaries'
Path override failed for key base::DIR_APP_DICTIONARIES and path '/usr/libexec/qt6/qtwebengine_dictionaries'
failed to open /usr/lib64/dri/hybrid_drv_video.so
Not using hybrid_drv_video.so
Comment 3 Ivan Petrunko 2024-07-17 13:10:48 UTC
Created attachment 171740 [details]
Akregator 5.19.3 with dark color theme on Kubuntu 22.04.4

The problem is still present and relevant in Akregator 5.19.3 with dark color theme on Kubuntu 22.04.4 LTS.
Comment 4 Christophe Marin 2024-07-17 13:36:15 UTC
(In reply to Ivan Petrunko from comment #3)
> Created attachment 171740 [details]
> Akregator 5.19.3 with dark color theme on Kubuntu 22.04.4
> 

This is an old version that won't receive the fix.
Comment 5 Ivan Petrunko 2024-07-17 14:21:39 UTC
(In reply to Christophe Marin from comment #4)
> (In reply to Ivan Petrunko from comment #3)
> > Created attachment 171740 [details]
> > Akregator 5.19.3 with dark color theme on Kubuntu 22.04.4
> > 
> 
> This is an old version that won't receive the fix.

Hey Christophe. Got it. Which version doesn't have this bug?
Comment 6 Christophe Marin 2024-07-17 14:47:56 UTC
None yet, but articles use the system theme in what will become 6.2.0 (i.e. it will be part of the 24.08.0 release)
Comment 7 Ivan Petrunko 2024-07-17 14:55:37 UTC
(In reply to Christophe Marin from comment #6)
> None yet, but articles use the system theme in what will become 6.2.0 (i.e.
> it will be part of the 24.08.0 release)

Ok. Thanks for letting me know.
Comment 8 Christophe Marin 2024-07-23 21:23:51 UTC
*** Bug 489828 has been marked as a duplicate of this bug. ***