[kate] [Bug 483754] New: Breeze theme is not embedded in the nighly Kate for Windows
https://bugs.kde.org/show_bug.cgi?id=483754 Bug ID: 483754 Summary: Breeze theme is not embedded in the nighly Kate for Windows Classification: Applications Product: kate Version: 23.04.0 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: application Assignee: kwrite-bugs-n...@kde.org Reporter: m...@gikari.com Target Milestone: --- SUMMARY Kate downloaded from https://cdn.kde.org/ci-builds/utilities/kate/master/windows/ does not have a Breeze theme inside, contrary to Kate installed from Windows Store. STEPS TO REPRODUCE 1. Download and install Kate from https://cdn.kde.org/ci-builds/utilities/kate/master/windows/ (.exe) 2. Open Kate OBSERVED RESULT Kate is using Windows Native Qt theme. Breeze theme cannot be selected. EXPECTED RESULT Kate is using Breeze theme, or/and it could be selected in the settings. SOFTWARE/OS VERSIONS Windows 11 Version 23H2 -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 483752] New: Cannot download Windows Nightly 7z: Virus detected
https://bugs.kde.org/show_bug.cgi?id=483752 Bug ID: 483752 Summary: Cannot download Windows Nightly 7z: Virus detected Classification: Applications Product: kate Version: 23.04.0 Platform: Microsoft Windows OS: Other Status: REPORTED Severity: major Priority: NOR Component: application Assignee: kwrite-bugs-n...@kde.org Reporter: m...@gikari.com Target Milestone: --- SUMMARY 7z archive from https://cdn.kde.org/ci-builds/utilities/kate/master/windows cannot be downloaded, Windows Defender complains it is a virus: Trojan:Script/Wacatac.B!ml STEPS TO REPRODUCE 1. Open any browser on Windows 2. Try to download https://cdn.kde.org/ci-builds/utilities/kate/master/windows/kate-master-6736-windows-cl-msvc2022-x86_64.7z OBSERVED RESULT Windows Defender immidiately deletes the file complaining it is a Trojan:Script/Wacatac.B!ml EXPECTED RESULT Windows Defender does not delete the file. SOFTWARE/OS VERSIONS Windows 11 Home 23H2 ADDITIONAL INFORMATION The .exe installer is fine. Windows Defender compains only about "dbg" and not "non-dbg" 7z archives. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 385135] Monitor connection names differ across X11 and Wayland, causing multi-monitor containment mappings to break when switching session types
https://bugs.kde.org/show_bug.cgi?id=385135 Mikhail Zolotukhin changed: What|Removed |Added CC||m...@genda.life -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 448845] kded module crashes on startup in GtkConfig::setFont()
https://bugs.kde.org/show_bug.cgi?id=448845 --- Comment #16 from Mikhail Zolotukhin --- There is no info in the backtrace where exactly in `setFont` kded5 crashes, but here is my best guess: https://invent.kde.org/plasma/kde-gtk-config/-/blob/master/kded/configeditor.cpp#L46 No idea why, though. It's something on GTK side. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 316734] After waking the system, the desktop gets displayed for a moment before the lock screen appears
https://bugs.kde.org/show_bug.cgi?id=316734 Mikhail Zolotukhin changed: What|Removed |Added CC||m...@genda.life -- You are receiving this mail because: You are watching all bug changes.
[rust-qt-binding-generator] [Bug 445879] New: Support some of the built-in Qt types, when exposing them to Rust
https://bugs.kde.org/show_bug.cgi?id=445879 Bug ID: 445879 Summary: Support some of the built-in Qt types, when exposing them to Rust Product: rust-qt-binding-generator Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: j...@vandenoever.info Reporter: m...@genda.life Target Milestone: --- SUMMARY In particular, I wanted to use QJSValue type, so that I can call QML methods from the Rust side. -- You are receiving this mail because: You are watching all bug changes.
[rust-qt-binding-generator] [Bug 445878] New: Support generating and emitting custom signals
https://bugs.kde.org/show_bug.cgi?id=445878 Bug ID: 445878 Summary: Support generating and emitting custom signals Product: rust-qt-binding-generator Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: j...@vandenoever.info Reporter: m...@genda.life Target Milestone: --- SUMMARY Currently, you can only add Q_INVOKABLE functions and Q_PROPERTIES to your objects in the bindigs.json. It is not possible to create custom signals, so that you can emit them from Rust code, and attach to them in the QML. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 445839] New: Changes in contents of main script file are not seen by KWin until KWin reload
https://bugs.kde.org/show_bug.cgi?id=445839 Bug ID: 445839 Summary: Changes in contents of main script file are not seen by KWin until KWin reload Product: kwin Version: 5.23.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: scripting Assignee: kwin-bugs-n...@kde.org Reporter: m...@genda.life Target Milestone: --- SUMMARY I'm developing a script and when I change something in the code - I build and install it. When the installation is finished, the new version of the files becomes available in the installation location. However, when I turn the script off and on - KWin still uses the old version of the script. If I restart KWin the new version is used, but that's inconvenient and is not possible on Wayland session. STEPS TO REPRODUCE 1. Install some script and run it. 2. Change the script source, so that it outputs some new line to the console 3. Turn the script off and on. OBSERVED RESULT No new line is printed EXPECTED RESULT New line is printed in the console -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 445129] New: Provide an ability to emit dbus signals and react to the method calls, so that other programs could interact with a KWin Script
https://bugs.kde.org/show_bug.cgi?id=445129 Bug ID: 445129 Summary: Provide an ability to emit dbus signals and react to the method calls, so that other programs could interact with a KWin Script Product: kwin Version: 5.23.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: scripting Assignee: kwin-bugs-n...@kde.org Reporter: m...@genda.life Target Milestone: --- SUMMARY I would like to control my KWin script via Plasma Applet. To do this, I need an IPC between the Plasma Applet and the KWin Script. One of the ways I think this could be possible is via global functions in the scripting API: 1. Register and emit a dbus signal, so that external programs could react to it 2. Call a DBus method (already implemented) 3, Register a method, that could be called by an external program -- You are receiving this mail because: You are watching all bug changes.
[bugs.kde.org] [Bug 444700] New: Save changes button is displayed over the site header
https://bugs.kde.org/show_bug.cgi?id=444700 Bug ID: 444700 Summary: Save changes button is displayed over the site header Product: bugs.kde.org Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: sysad...@kde.org Reporter: m...@genda.life CC: she...@kde.org Target Milestone: --- Created attachment 143045 --> https://bugs.kde.org/attachment.cgi?id=143045=edit Save changes button SUMMARY Save changes button is displayed over the header, when you scroll the page a little. STEPS TO REPRODUCE 1. Open a bug report page (e.g. this bug reports) 2. Scroll the page down a bit OBSERVED RESULT The "Save Changes" button is displayed over the site header. EXPECTED RESULT The "Save Changes" button is displayed below the header. ADDITIONAL INFO I noticed, that the button for some reason has `z-index` property assigned to 10. When I remove this CSS property via dev tools, the button is displayed normally (e.g. under the header). -- You are receiving this mail because: You are watching all bug changes.
[bugs.kde.org] [Bug 444699] New: Menu in the header on mobile is cramped when using the new theme
https://bugs.kde.org/show_bug.cgi?id=444699 Bug ID: 444699 Summary: Menu in the header on mobile is cramped when using the new theme Product: bugs.kde.org Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: sysad...@kde.org Reporter: m...@genda.life CC: she...@kde.org Target Milestone: --- Created attachment 143044 --> https://bugs.kde.org/attachment.cgi?id=143044=edit Dev tools with mobile screen SUMMARY Items in menu bar are displayed incorrectly, when browsing from mobile device (See the screenshot). STEPS TO REPRODUCE 1. Open any page on mobile device or with mobile dev tools. OBSERVED RESULT The menu items are squished together. EXPECTED RESULT The menu items are displayed normally, just like on bugzilla.mozilla.org -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kconfig] [Bug 397602] Configuration files should contain only persistent configuration and not state
https://bugs.kde.org/show_bug.cgi?id=397602 Mikhail Zolotukhin changed: What|Removed |Added CC||m...@genda.life -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 443596] New: Ability to opt out of minimum window size rule, while the script is loaded
https://bugs.kde.org/show_bug.cgi?id=443596 Bug ID: 443596 Summary: Ability to opt out of minimum window size rule, while the script is loaded Product: kwin Version: 5.22.5 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: scripting Assignee: kwin-bugs-n...@kde.org Reporter: m...@genda.life Target Milestone: --- SUMMARY I am making the tiling window script. For its use case, sometimes it is desirable to opt out of the behavior, when the window do not resize below its minimum size. It would be nice if the KWin provided a function to toggle this rule. See also: https://github.com/gikari/bismuth/issues/102 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 443498] New: activitiesChanged signal is not emitted, when window is moved to another activity
https://bugs.kde.org/show_bug.cgi?id=443498
Bug ID: 443498
Summary: activitiesChanged signal is not emitted, when window
is moved to another activity
Product: kwin
Version: 5.22.5
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: scripting
Assignee: kwin-bugs-n...@kde.org
Reporter: m...@genda.life
Target Milestone: ---
SUMMARY
The activitiesChanged signal is not emitted, when the window is not present on
the current activity.
STEPS TO REPRODUCE
1. Use this code in kwin script:
client.activitiesChanged.connect(() => {
console.log("ActivitiesChanged is called")
})
2. Move window to another activity via Alt+F3 menu
OBSERVED RESULT
The window disappears from the screen (moved to another activity), the log is
empty
EXPECTED RESULT
The window disappears from the screen (moved to another activity), the
"ActivitiesChanged is called" is printed.
SOFTWARE/OS VERSIONS
Operating System: Arch Linux
KDE Plasma Version: 5.22.5
KDE Frameworks Version: 5.86.0
Qt Version: 5.15.2
Kernel Version: 5.10.69-1-lts (64-bit)
Graphics Platform: X11
Processors: 8 × Intel® Core™ i7-8550U CPU @ 1.80GHz
Memory: 15,5 GiB of RAM
Graphics Processor: Mesa Intel® UHD Graphics 620
ADDITIONAL INFORMATION
The log message is printed only if we change activities, while keeping the
window on the present screen.
--
You are receiving this mail because:
You are watching all bug changes.
[systemsettings] [Bug 442659] GTK3 Window decoration assets generated by kde-gtk-config are now all blank with Breeze window decoration
https://bugs.kde.org/show_bug.cgi?id=442659 --- Comment #3 from Mikhail Zolotukhin --- Since the drawing is performed using private KDecoration API (bad idea, yeah), the internal breakage is probably responsible. I have a hypothesis, that it is because of this commit: https://invent.kde.org/plasma/kwin/-/commit/08d3ceb024ff00d48ef8ffd5587c61ce1c5e06eb and -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 442393] New: Provide script config update signal
https://bugs.kde.org/show_bug.cgi?id=442393 Bug ID: 442393 Summary: Provide script config update signal Product: kwin Version: 5.22.5 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: scripting Assignee: kwin-bugs-n...@kde.org Reporter: m...@genda.life Target Milestone: --- SUMMARY Workspace configChanged signal (https://develop.kde.org/docs/plasma/kwin/api/#signals-1) does not work when script configuration is updated ([Script-] section in ~/.config/kwinrc). ADDITIONAL INFORMATION Without this signal, the user needs to disable the script and enable it again to apply changes to the configuration of KWin script. Providing this signal will improve the user experience, if the developer of the script correctly uses it. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 441037] Wrong characters' horizontal spacing results in overlapping
https://bugs.kde.org/show_bug.cgi?id=441037 --- Comment #2 from Mikhail Zolotukhin --- Created attachment 140767 --> https://bugs.kde.org/attachment.cgi?id=140767=edit Konsole text display -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 441037] Wrong characters' horizontal spacing results in overlapping
https://bugs.kde.org/show_bug.cgi?id=441037 --- Comment #1 from Mikhail Zolotukhin --- Created attachment 140766 --> https://bugs.kde.org/attachment.cgi?id=140766=edit Alacritty text display -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 441037] New: Wrong characters' horizontal spacing results in overlapping
https://bugs.kde.org/show_bug.cgi?id=441037 Bug ID: 441037 Summary: Wrong characters' horizontal spacing results in overlapping Product: konsole Version: 21.08.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: font Assignee: konsole-de...@kde.org Reporter: m...@genda.life Target Milestone: --- Created attachment 140765 --> https://bugs.kde.org/attachment.cgi?id=140765=edit Kitty text display SUMMARY Horizontal spacing between characters is uneven, and characters also overlap the following ones. STEPS TO REPRODUCE 1. Paste this text into some Konsole view (e.g. using Neovim or other console editor): "⠀⠀⠀⢀⣀⣀⣀⡀", "⠀⠀⠀⣠⣤⣶⣾⠿⠿⠟⠿⠿⣿⣷⣤⣄⡀⠀⠀⠀", " ⠀⢀⣠⣾⡿⠋⠉⠀⠈⠙⠿⣷⣤⡀", "⠀⠀⣤⡿⠛⠉⠀⠀⠀⠉⠛⢿⣦⡀⠀⠀", "⠀⡠⠒⠂⢩⣿⡿⠀⠹⣷⡄⠀", "⠸⡀⠀⢰⣿⠋⠀⠀⠀⠙⣿⣧", "⠀⠑⠠⡀⠀⠀⢀⣾⠋⠀⠘⣿⡆⠀⠀⠀", "⠀⠀⠀⠈⠢⢀⣸⡟⠀⠀⠀⢹⣇⠀⠀⠀", "⠀⠀⣿⡧⢄⡀⠀⢸⣿⠀⠀⠀", "⠀⠀⣿⡇⠀⠈⠁⠒⠤⣀⠀⢸⣿⣀⠀⠀", "⠀⠀⢸⣇⠀⠀⠉⠢⠤⠀⢀⣸⡟⠈⠑⠄", "⠀⠀⠀⢿⡄⠀⠀⠉⠑⠒⠤⣀⡀⠀⢠⣿⡇⠀⠀⢀⣣⡀⠀⠀", "⠀⣿⡟⠸⣷⡄⠀⠀⠀⠉⠀⠀⠒⠢⠤⠄⣀⣀⠀⠀⠀⢠⣿⡟⠀⠀⠀⣺⣿⡿⠀⠀", "⠀⣿⠇⠀⣤⡄⠀⠀⢠⣤⡄⠀⢨⣭⣠⣤⣤⣤⡀⠀⠀⢀⡄⠀⠀⠀⣤⣄⣤⣤⣤⠀⠀⣿⣯⠉⠉⣿⡟⠀⠈⢩⣭⣤⣤⣠⣤⣤⣤⣄⣤⣤", "⢠⣿⠀⠀⣿⠃⠀⠀⣸⣿⠁⠀⣿⣿⠉⠀⠈⣿⡇⠀⠀⠛⠋⠀⠀⢹⣿⠀⠀⠀⣿⠏⠀⠸⠿⠃⠀⣿⣿⠀⣰⡟⠀⢸⣿⣿⡟⢸⣿⡇⢀⣿", "⣸⡇⠀⢸⣿⠀⠀⠀⣿⡟⠀⢠⣿⡇⠀⠀⢰⣿⡇⠀⣰⣾⠟⠛⠛⣻⡇⠀⠀⢸⡿⠀⠀⢻⣿⢰⣿⠀⠀⣾⡇⠀⠀⠀⢸⣿⠇⢸⣿⠀⢸⡏", "⣿⣧⣤⣤⣤⡄⠀⠘⣿⣤⣤⡤⣿⠇⠀⢸⣿⠁⠀⠀⣼⣿⠀⠀⢿⣿⣤⣤⠔⣿⠃⠀⠀⣾⡇⠀⠀⢸⣿⣿⠋⠀⠀⠀⢠⣤⣤⣿⣥⣤⡄⠀⣼⣿⠀⣸⡏⠀⣿⠃", "⠉⠁⠀⠀⠈⠉⠉⠀⠉⠀⠀⠈⠉⠀⠀⠀⠉⠉⠀⠀⠀⠉⠉⠁⠈⠉⠀⠀⠀⠉⠀⠀⠀⠈⠉⠉⠈⠉⠁⠀⠉⠁⠀⠉⠁⠀⠉⠀", OBSERVED RESULT Horizontal spacing between characters is irregular and the "m" letter is truncated. (See screenshot) EXPECTED RESULT The "m" is not truncated and spacing between dots are even. (See Kitty terminal emulator screenshot) SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.22.4 KDE Frameworks Version: 5.85.0 Qt Version: 5.15.2 Kernel Version: 5.10.56-1-lts (64-bit) Graphics Platform: X11 Processors: 8 × Intel® Core™ i7-8550U CPU @ 1.80GHz Memory: 15,5 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics 620 ADDITIONAL INFORMATION I use fractional scaling (125%), which is respected by both Kitty and Konsole. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 431396] Window decoration buttons are mis-rendered
https://bugs.kde.org/show_bug.cgi?id=431396 Mikhail Zolotukhin changed: What|Removed |Added Version Fixed In||5.22.5 URL||https://invent.kde.org/plas ||ma/kde-gtk-config/-/merge_r ||equests/31 Status|CONFIRMED |RESOLVED Resolution|--- |FIXED Latest Commit||https://invent.kde.org/plas ||ma/kde-gtk-config/-/commit/ ||41b4edf6e0065adccf9ab1aa457 ||46d34e951a5d4 -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 431396] Window decoration buttons are mis-rendered
https://bugs.kde.org/show_bug.cgi?id=431396 Mikhail Zolotukhin changed: What|Removed |Added CC||m...@genda.life --- Comment #9 from Mikhail Zolotukhin --- This needs to be tested after [!31](https://invent.kde.org/plasma/kde-gtk-config/-/merge_requests/31) is merged. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 439224] New: Header area loses the underline and coloring when borders are specified for window decoration
https://bugs.kde.org/show_bug.cgi?id=439224 Bug ID: 439224 Summary: Header area loses the underline and coloring when borders are specified for window decoration Product: Breeze Version: 5.22.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: QStyle Assignee: plasma-b...@kde.org Reporter: m...@genda.life CC: noaha...@gmail.com Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. Set the window decoration to Breeze Dark 2. Set the window decorations border to normal 3. Open Dolphin OBSERVED RESULT The headerbar area is not separated with the line and blends with the rest of the app EXPECTED RESULT The headerbar area is separated and differs in color SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.22.2 KDE Frameworks Version: 5.83.0 Qt Version: 5.15.2 Kernel Version: 5.10.46-1-lts (64-bit) Graphics Platform: X11 Processors: 8 × Intel® Core™ i7-8550U CPU @ 1.80GHz Memory: 15,5 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics 620 ADDITIONAL INFORMATION It seems like this is intended behavior, because we assume that the underline, that stops at the border, that has the same color, as the upper and surroundings of the underline is odd. But this is not the case when we change the color border to something prominent (e.g. like in this screenshot: https://github.com/esjeon/krohnkite/blob/master/img/screenshot.png). Maybe the header area could be a configurable option in the Breeze style? -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 439222] New: Cannot set the window border color with kdeglobals config lines
https://bugs.kde.org/show_bug.cgi?id=439222 Bug ID: 439222 Summary: Cannot set the window border color with kdeglobals config lines Product: Breeze Version: 5.22.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: window decoration Assignee: plasma-b...@kde.org Reporter: m...@genda.life CC: kwin-bugs-n...@kde.org Target Milestone: --- SUMMARY Krohnkite tiling script recommends to set window borders color with the following config line in ~/.config/kdeglobals: ``` [WM] frame=61,174,233 inactiveFrame=239,240,241 ``` However, with the recent color schemes, this approach does not work. STEPS TO REPRODUCE 1. Set the color scheme to Breeze 2. Set the window borders to normal 3. Add frame color lines to kdeglobals: ``` kwriteconfig5 --file ~/.config/kdeglobals --group WM --key frame 61,174,233 kwriteconfig5 --file ~/.config/kdeglobals --group WM --key inactiveFrame 239,240,241 ``` 4. Restart KWin OBSERVED RESULT Window borders are grey. EXPECTED RESULT Window borders are blue. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.22.2 KDE Frameworks Version: 5.83.0 Qt Version: 5.15.2 Kernel Version: 5.10.46-1-lts (64-bit) Graphics Platform: X11 Processors: 8 × Intel® Core™ i7-8550U CPU @ 1.80GHz Memory: 15,5 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics 620 ADDITIONAL INFORMATION The diff between old (e.g. Nordic) and new (Breeze Dark) color scheme shows, that these lines belong only to the new color scheme: ``` [Colors:Complementary] BackgroundAlternate=30,87,116 BackgroundNormal=42,46,50 DecorationFocus=61,174,233 DecorationHover=61,174,233 ForegroundActive=61,174,233 ForegroundInactive=161,169,177 ForegroundLink=29,153,243 ForegroundNegative=218,68,83 ForegroundNeutral=246,116,0 ForegroundNormal=252,252,252 ForegroundPositive=39,174,96 ForegroundVisited=155,89,182 [Colors:Header] BackgroundAlternate=42,46,50 BackgroundNormal=49,54,59 DecorationFocus=61,174,233 DecorationHover=61,174,233 ForegroundActive=61,174,233 ForegroundInactive=161,169,177 ForegroundLink=29,153,243 ForegroundNegative=218,68,83 ForegroundNeutral=246,116,0 ForegroundNormal=252,252,252 ForegroundPositive=39,174,96 ForegroundVisited=155,89,182 [Colors:Header][Inactive] BackgroundAlternate=49,54,59 BackgroundNormal=42,46,50 DecorationFocus=61,174,233 DecorationHover=61,174,233 ForegroundActive=61,174,233 ForegroundInactive=161,169,177 ForegroundLink=29,153,243 ForegroundNegative=218,68,83 ForegroundNeutral=246,116,0 ForegroundNormal=252,252,252 ForegroundPositive=39,174,96 ForegroundVisited=155,89,182 ``` It seems like the these lines override the lines, specified in kdeglobals, but I'm not sure. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 437082] gtk3 csd apps do not respect third-party window decoration theme on Wayland
https://bugs.kde.org/show_bug.cgi?id=437082 --- Comment #2 from Mikhail Zolotukhin --- If GTK ignores modules string there is nothing we can do about it. GTK devs do not want us to modify the css theme on the go, so I am pessimistic about our support of theme consistency on wayland and flatpak. See also: https://gitlab.gnome.org/GNOME/gtk/-/issues/3409 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 436559] GTK3 CSD buttons are noticeably smaller than regular Breeze Qt style
https://bugs.kde.org/show_bug.cgi?id=436559 --- Comment #11 from Mikhail Zolotukhin --- Created attachment 138180 --> https://bugs.kde.org/attachment.cgi?id=138180=edit Generated SVGs visual diff If we compare the buttons' svg from Breeze GTK and the one GTK Daemon generates, we can notice the difference in margins from the edges. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 435558] Allow different gtk theme per application
https://bugs.kde.org/show_bug.cgi?id=435558 Mikhail Zolotukhin changed: What|Removed |Added Status|REPORTED|RESOLVED CC||m...@genda.life Resolution|--- |UPSTREAM --- Comment #1 from Mikhail Zolotukhin --- Sorry, this is impossible implement. Also, if I understand correctly, client uses GTK2 under the hood. If it is true, then I think the developers should port it to GTK4. GTK2 is ancient and unsupported. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 435164] Exporting gtk-error-bell=0 seems to have broken recently
https://bugs.kde.org/show_bug.cgi?id=435164 --- Comment #1 from Mikhail Zolotukhin --- "gtk-error-bell" was never exported in kde-gtk-config AFAIK. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 413111] Create a "Breeze Light" theme to mirror "Breeze Dark", allowing people to force all GTK apps to be light or dark rather than following the KDE color scheme
https://bugs.kde.org/show_bug.cgi?id=413111 Mikhail Zolotukhin changed: What|Removed |Added CC||m...@genda.life --- Comment #18 from Mikhail Zolotukhin --- Hm... Given the fact, that we cannot longer customize the Breeze GTK appearance in GTK4 with the current mechanism and the amount of confusion, that the single Breeze option in combobox gives to some users, I think what we can do is the following: 1. Create 3 Breeze GTK variants: Breeze Light, Breeze Dark and Breeze Native. 2. Breeze Native will be the default and will grab all its tweaks from some Plasma settings (color scheme, window decorations). Possibly Breeze Native will be auto-generated variant (Not yet sure how to do that exactly). 3. Breeze Light and Breeze Dark will use the standard Breeze Light and Breeze Dark color schemes. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 434014] Window decorations are not aplied for GTK apps with CSD
https://bugs.kde.org/show_bug.cgi?id=434014 --- Comment #4 from Mikhail Zolotukhin --- Plastic is indeed won't work, because it's too much effort to support (If someone want, they can create a MR). Oxygen on the other hand should be supported, AFAIK it's draws itself just like breeze. When I created this functionality I tested it, so I'm surprised. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 431374] Being able to disable the white circle around the "X" button at the top right corner of the Breeze-Dark-Gtk Window borders
https://bugs.kde.org/show_bug.cgi?id=431374 --- Comment #17 from Mikhail Zolotukhin --- Yes. If not, it is called "breeze-gtk" in pacman. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 431374] Being able to disable the white circle around the "X" button at the top right corner of the Breeze-Dark-Gtk Window borders
https://bugs.kde.org/show_bug.cgi?id=431374 Mikhail Zolotukhin changed: What|Removed |Added Resolution|WAITINGFORINFO |NOT A BUG Status|NEEDSINFO |RESOLVED --- Comment #15 from Mikhail Zolotukhin --- We don't touch 3rd party GTK themes. Because of that the circle change won't work. To properly disable the circle you need to set your GTK theme to "Breeze" (without any suffixes and prefixes), then select Breeze Dark color scheme in Appearance > Colors. That way you will be using the official Breeze GTK theme, that grabs its appearance from various Plasma settings, like colors and window decorations. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 432614] System font not apply for GTK applications
https://bugs.kde.org/show_bug.cgi?id=432614 Mikhail Zolotukhin changed: What|Removed |Added Resolution|--- |NOT A BUG Status|REPORTED|RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 432614] System font not apply for GTK applications
https://bugs.kde.org/show_bug.cgi?id=432614 --- Comment #3 from Mikhail Zolotukhin --- Created attachment 135492 --> https://bugs.kde.org/attachment.cgi?id=135492=edit Font Name in dialog It seems like Font name in the dialog is somewhat mangled. I think it's a problem with this particular font, so unfortunately I cannot help with that, sorry. What's interesting, is that if you delete the "[ ]" thing and save the config, it will use the correct font. Is Google Fonts the only source for Amaranth? If not, it is worth finding alternative .ttf font files somewhere else. If you could find them, please try to use them for configuration. If not, there is a hacky way I can fix that - remove the brackets from the font string, before writing the configuration, but I'm afraid that can broke some other fonts, that use "[]" in their name. Is that really common practice? -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 432614] System font not apply for GTK applications
https://bugs.kde.org/show_bug.cgi?id=432614 Mikhail Zolotukhin changed: What|Removed |Added CC||m...@genda.life --- Comment #1 from Mikhail Zolotukhin --- Could you please name the font you are trying to set? -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 431374] Being able to disable the white circle around the "X" button at the top right corner of the Breeze-Dark-Gtk Window borders
https://bugs.kde.org/show_bug.cgi?id=431374 --- Comment #10 from Mikhail Zolotukhin --- Hm, strange, it works for me. I've tested that on KDE Neon 5.20.5 (my local machine) and on master (KDE Neon Unstable in the VM). Maybe someone other can reproduce. What's interesting is that you cannot have Breeze-Dark theme, because its selection in GTK System Settings page cannot be performed (the theme is hidden). What is actually selected in the GTK page in your settings? -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 431374] Being able to disable the white circle around the "X" button at the top right corner of the Breeze-Dark-Gtk Window borders
https://bugs.kde.org/show_bug.cgi?id=431374 --- Comment #8 from Mikhail Zolotukhin --- There was a fix, that was merged in Plasma 5.20.5, that touches the GTK CSS updating mechanism. Please update to the latest Plasma version and check if the bug persists. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 431374] Being able to disable the white circle around the "X" button at the top right corner of the Breeze-Dark-Gtk Window borders
https://bugs.kde.org/show_bug.cgi?id=431374 --- Comment #6 from Mikhail Zolotukhin --- Also, please tell if the GTK app is installed via flatpak/snap or not. Because if the GTK app is installed via flatpak (or snap), it won't work. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 431365] "WINDOW DECORATIONS RELOADED" should be written to stdout
https://bugs.kde.org/show_bug.cgi?id=431365 Mikhail Zolotukhin changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 --- Comment #1 from Mikhail Zolotukhin --- https://invent.kde.org/plasma/kde-gtk-config/-/blob/master/window-decorations-reload-module/reloader.c#L58 This line can be deleted. It was just for debugging purposes and just passed through the review. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 430713] New: After clicking a link in app with a browser on another virtual desktop, the desktop is not switched
https://bugs.kde.org/show_bug.cgi?id=430713 Bug ID: 430713 Summary: After clicking a link in app with a browser on another virtual desktop, the desktop is not switched Product: kwin Version: 5.20.4 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: m...@genda.life Target Milestone: --- SUMMARY After clicking a link in app with a browser on another virtual desktop, the desktop is not switched STEPS TO REPRODUCE 1. Open browser (Firefox in my case) on one virtual desktop 2. Place an app with clickable links on another virtual desktop (i.e. Neochat, Telegram etc) 3. Click on any link OBSERVED RESULT Link is opened in a browser, but the virtual desktop is not switched to another. EXPECTED RESULT Desktop is switched to another desktop. SOFTWARE/OS VERSIONS Operating System: KDE neon 5.20 KDE Plasma Version: 5.20.4 KDE Frameworks Version: 5.77.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION I noticed, that changing the setting "Focus stealing prevention" to None helps, and therefore I have two questions: 1) Why isn't this setting a default? 2) It's unclear what exactly the settings "None, Low, Medium, High, Extreme" mean. May there can be a tooltip, like in Fonts KCM, that explains those options? -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 430580] New: Default color scheme is not correctly applied
https://bugs.kde.org/show_bug.cgi?id=430580 Bug ID: 430580 Summary: Default color scheme is not correctly applied Product: kdenlive Version: 20.12.0 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: User Interface Assignee: j...@kdenlive.org Reporter: m...@genda.life Target Milestone: --- SUMMARY When launching Kdenlive with the setting to follow system color scheme (i.e. called "default"), it used Breeze Dark instead of a system one. STEPS TO REPRODUCE 1. Set Plasma color scheme to something not default (I use Nordic) 2. Open Kdenlive, set default in Settings -> Color Theme -> Default. The scheme applies. 3. Reopen Kdenlive OBSERVED RESULT Breeze Dark color scheme is used. EXPECTED RESULT The scheme you've selected in Plasma settings is used. SOFTWARE/OS VERSIONS Operating System: KDE neon 5.20 KDE Plasma Version: 5.20.4 KDE Frameworks Version: 5.77.0 Qt Version: 5.15.2 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 417309] After I change shortcuts of task switcher, it's impossible to walk through all windows or all windows of the current app until Plasma session or kwin is restarted
https://bugs.kde.org/show_bug.cgi?id=417309 Mikhail Zolotukhin changed: What|Removed |Added CC||m...@genda.life Ever confirmed|0 |1 Status|REPORTED|CONFIRMED --- Comment #2 from Mikhail Zolotukhin --- I can confirm this bug. You cannot switch between windows executing the same shortcut: the switcher appears on the first press, but on the consequent ones there is no reaction. However, you can switch using the arrow keys. After KWin restart everything is fine. Operating System: KDE neon 5.20 KDE Plasma Version: 5.20.4 KDE Frameworks Version: 5.77.0 Qt Version: 5.15.2 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 430046] Cannot set dark theme for gtk2 apps
https://bugs.kde.org/show_bug.cgi?id=430046 Mikhail Zolotukhin changed: What|Removed |Added Status|REOPENED|RESOLVED Resolution|--- |INTENTIONAL --- Comment #9 from Mikhail Zolotukhin --- I tried to do what I was talking about and it seems like this workaround requires modification of the code in too many places with ambiguous unforeseen consequences. Doing so just to implement "Dark Mode" for GTK2 apps seems unreasonable to me. As I have discovered, this approach is VERY bug prone and, due to my limited time, I'm not sure I'm ready for potential bugs, that will be discovered in case of that change (I need to fix them you know, otherwise it's just irresponsible). I suggest learning the lesson Half-Life taught us and not touch what can cause the breakage in the working system. Sorry to inform about that. > Yeah this is what drives me crazy, I set Breeze-Dark in .gtkrc-2.0 but > Plasma settings resets it to Breeze after I change global theme to Breeze > Dark. You can completely disable GTK sync module in Background services KCM. Still, modifying .gtkrc won't help you, unless you manually stop the xsettigsd. (You can manually edit its config in ~/.config/xsettingsd/xsettingsd.conf). -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 430046] Cannot set dark theme for gtk2 apps
https://bugs.kde.org/show_bug.cgi?id=430046 --- Comment #7 from Mikhail Zolotukhin --- > So if GTK2 support is removed why it is still trying to interfere and reset > manual changes ? GTK2 support was not removed. We just removed the ghostly possibility to change the GTK2 theme to a different one from GTK3, because it is impossible to do so due to technical reasons anyway. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 430046] Cannot set dark theme for gtk2 apps
https://bugs.kde.org/show_bug.cgi?id=430046 --- Comment #6 from Mikhail Zolotukhin --- Probably going to make my life harder, but I think there is some truth in "This was working fine". The thing is now we set Breeze theme for all GTK3 and GTK2 apps. Previously there was an opportunity to set Breeze-Dark for GTK3 and GTK2. It didn't change a thing for GTK3 apps, since its colors was brought from system Color Scheme (and this was misleading, that's why I removed that ability), but GTK2 apps used a dark Breeze variant. After the removal it's no longer possible to set Dark Breeze theme for GTK2 and GTK3 apps and that's why while GTK3 apps are working fine, GTK2 ones are broken. I think there is a hacky way to make GTK2 apps at least respect "Dark Mode" - it is to use Breeze-Dark setting variant under the hood, while setting Breeze theme or setting color scheme. For example: if the user sets the GTK theme to Breeze - check if the current color scheme is dark (we already can do that) and if it is, set the theme to the "Breeze-Dark", if it is not, set to just "Breeze". The similar approach can be used with the color scheme change. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 429982] ~/.config/gtk-3.0/ files are not properly updated on Plasma 5.20
https://bugs.kde.org/show_bug.cgi?id=429982 Mikhail Zolotukhin changed: What|Removed |Added Resolution|--- |DUPLICATE CC||m...@genda.life Status|REPORTED|RESOLVED --- Comment #2 from Mikhail Zolotukhin --- This should be fixed in 5.20.5. Please rereport, if it won't be fixed in PLasma 5.20.5. *** This bug has been marked as a duplicate of bug 428842 *** -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 428842] Window decoration buttons change to look worse until re-selecting GTK theme
https://bugs.kde.org/show_bug.cgi?id=428842 Mikhail Zolotukhin changed: What|Removed |Added CC||michal.dybc...@gmail.com --- Comment #21 from Mikhail Zolotukhin --- *** Bug 429982 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 428842] Window decoration buttons change to look worse until re-selecting GTK theme
https://bugs.kde.org/show_bug.cgi?id=428842 Mikhail Zolotukhin changed: What|Removed |Added Status|ASSIGNED|RESOLVED Version Fixed In||5.20.5 Latest Commit||https://invent.kde.org/plas ||ma/kde-gtk-config/-/commit/ ||fb0bb26b2f879fc5e2bc6feafe0 ||fa4fe7b278bea Resolution|--- |FIXED -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 428120] Window decoration buttons in GTK CSD apps are sometimes mis-rendered
https://bugs.kde.org/show_bug.cgi?id=428120 Mikhail Zolotukhin changed: What|Removed |Added Version Fixed In||5.20.5 Status|ASSIGNED|RESOLVED Latest Commit||https://invent.kde.org/plas ||ma/kde-gtk-config/-/commit/ ||fb0bb26b2f879fc5e2bc6feafe0 ||fa4fe7b278bea Resolution|--- |FIXED -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 428322] When using a custom GTK theme, apps headers have a weird clash of icons caused by Breeze ones
https://bugs.kde.org/show_bug.cgi?id=428322 Mikhail Zolotukhin changed: What|Removed |Added Resolution|--- |FIXED Latest Commit||https://invent.kde.org/plas ||ma/kde-gtk-config/-/commit/ ||fb0bb26b2f879fc5e2bc6feafe0 ||fa4fe7b278bea Version Fixed In||5.20.5 Status|ASSIGNED|RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 428120] Window decoration buttons in GTK CSD apps are sometimes mis-rendered
https://bugs.kde.org/show_bug.cgi?id=428120 Mikhail Zolotukhin changed: What|Removed |Added Assignee|plasma-b...@kde.org |zom...@protonmail.com -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 429623] kde-gtk-config won't build on top of kdecoration dc874eeb6
https://bugs.kde.org/show_bug.cgi?id=429623 Mikhail Zolotukhin changed: What|Removed |Added Status|ASSIGNED|RESOLVED Latest Commit||6e81458e554ca433f0a40357522 ||1f353d9229382 Resolution|--- |FIXED -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 429623] kde-gtk-config won't build on top of kdecoration dc874eeb6
https://bugs.kde.org/show_bug.cgi?id=429623 Mikhail Zolotukhin changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|ASSIGNED --- Comment #1 from Mikhail Zolotukhin --- This is currently WIP: https://invent.kde.org/plasma/kde-gtk-config/-/merge_requests/16 -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 428322] When using a custom GTK theme, apps headers have a weird clash of icons caused by Breeze ones
https://bugs.kde.org/show_bug.cgi?id=428322 --- Comment #11 from Mikhail Zolotukhin --- I think I found the bug's source and the solution. The thing is that current Breeze GTK CSS customization is based on two sources: CSS provided by gtk.css file, that is in the `~/.config/gtk-3.0/` folder and the CSS file that can be loaded and unloaded dynamically via GTK module - window_decorations.css. This approach has some caveats. First, it will not fully work with GTK 4, because the latter dropped support for modules (i.e. extensions to GTK4). Because of that this bug will be reproducible in more conditions. Second, it basically has a conflicting way of loading CSS into GTK applications. GTK apps by default (i.e. without modules) has two sources of CSS: system theme, selected in GTK Settings Page (gtk.css is located in `/usr/share/themes`) and the user defined CSS (located in `~/.config/gtk-3.0/gtk.css`). With the module we can load CSS files literally from anywhere in our file system. What we are doing now is relaying on the built-in GTK functionality to load CSS from `.config` folder and also on the custom functionality of KDE written module to load and unload the CSS when the application is running. This bug happens because GTK initially loads the gtk.css from the `.config` with the decorations CSS and then, when the user is changing the theme, we ask our KDE module to unload the decorations CSS. But our module have nothing to unload, because it is not the one who loaded the CSS file and it does not know the pointer to the CSS provider from `.config`. (CSS provider is the GTK code structure to manipulate the CSS of applications). I haven't found the way to get the pointer to CSS provider for the `.config` CSS, so I have found another solution. What we should do is drop gtk.css in the ~/.config directory completely (or at least for window decorations, as we are using it for colors syncing, that does not break apps' appearance at least) and make the module responsibility loading window_decorations.css dynamically including loading it on the initialization step of the module. This should simplify the code base and fix the bugs. This would however mean, that decorations' appearance syncing will not work with gtk4 apps at all until we found a way to make it to so. Also, since the module must be written in C, we need to find some alternative way to watch GTK theme changing (perhaps monitoring the settings.ini file?). I think it's a reasonable trade off. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 428322] When using a custom GTK theme, apps headers have a weird clash of icons caused by Breeze ones
https://bugs.kde.org/show_bug.cgi?id=428322 --- Comment #8 from Mikhail Zolotukhin --- I find a more precise way to reproduce bug: 0. Do not open GTK app yet. 1. Open GTK page, set GTK theme to Breeze. 2. Open GTK app. 3. At this moment change the GTK theme in settings 4. Now the decorations are broken. However, the decoration changing behavior is ok if you do these actions: 5. Close the GTK app and open it again. 6. Decorations are normal now (the ones are from the GTK theme you've selected) 7. Change the GTK theme to Breeze and then again to another theme. TLDR: decorations are broken only if your initial (i.e. is selected in the settings, when you open a GTK app) theme is Breeze. Otherwise, (when the initial theme is another one), there should be no glitches, when changing the themes back and forth. Please confirm if the behavior is same for you as I described. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 428322] When using a custom GTK theme, apps headers have a weird clash of icons caused by Breeze ones
https://bugs.kde.org/show_bug.cgi?id=428322 --- Comment #7 from Mikhail Zolotukhin --- Some good meows: now I can reproduce this bug, so in the free time I will look into it more deeply and probably find a way to fix it. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 428120] Non-kwin window buttons are not switching correctly / are displayed weirdly in gtk apps
https://bugs.kde.org/show_bug.cgi?id=428120 --- Comment #8 from Mikhail Zolotukhin --- If this happens with only one they have, then may be it's somehow related to its internals? I recall Adwaita using Breeze decorations even before the patch with custom CSS landed in Plasma. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 428120] Non-kwin window buttons are not switching correctly / are displayed weirdly in gtk apps
https://bugs.kde.org/show_bug.cgi?id=428120 --- Comment #6 from Mikhail Zolotukhin --- Deleting the CSS files certainly won't help. They are used to update the appearance of GTK apps. The quote is from Manjaro Forum, where one switched to GNOME and faced the consequences. Again, I cannot reproduce this bug - for me decorations are updated with no issues. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 428617] GTK+ settings crashes when applying
https://bugs.kde.org/show_bug.cgi?id=428617 --- Comment #4 from Mikhail Zolotukhin --- There should be a program called Dr Konqui or something like that on Kubuntu. It should show the notification after the crash happened and suggest you to show the backtrace if you click on it. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 428617] GTK+ settings crashes when applying
https://bugs.kde.org/show_bug.cgi?id=428617 Mikhail Zolotukhin changed: What|Removed |Added Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #2 from Mikhail Zolotukhin --- And what GTK theme do you mean GTK2 or GTK3? -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 428617] GTK+ settings crashes when applying
https://bugs.kde.org/show_bug.cgi?id=428617 --- Comment #1 from Mikhail Zolotukhin --- I cannot reproduce. Could you please provide a crash backtrace? -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 428322] When using a custom GTK theme, apps headers have a weird clash of icons caused by Breeze ones
https://bugs.kde.org/show_bug.cgi?id=428322 --- Comment #4 from Mikhail Zolotukhin --- This is strange. You should only have "import colors" string. I cannot reproduce this bug, but I'll investigate. The thing is it's explicitly said in the code to remove the import statement when changing the theme to non-Breeze one. If nothing helps, I might want to tell the code to remove window decorations css file as well just to be sure. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 428322] GTK apps headers
https://bugs.kde.org/show_bug.cgi?id=428322 Mikhail Zolotukhin changed: What|Removed |Added CC||zom...@protonmail.com --- Comment #2 from Mikhail Zolotukhin --- What's the contents of your ~/.config/gtk-3.0/gtk.css? -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 428120] Non-kwin window buttons are not switching correctly / are displayed weirdly in gtk apps
https://bugs.kde.org/show_bug.cgi?id=428120 --- Comment #2 from Mikhail Zolotukhin --- I cannot reproduce this bug. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 426687] The hover effects for the titlebar buttons are missing in the Breeze GTK theme
https://bugs.kde.org/show_bug.cgi?id=426687 --- Comment #9 from Mikhail Zolotukhin --- (In reply to Nate Graham from comment #8) > Yep, I can confirm the whole hover effect is missing. However disabling > animations with the global speed slider in System Settings > Workspace > Behavior > General Behavior does not fix it for me. What if you disable animations globally and then change decoration theme back and forth? -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 426074] Buttons of gtk3 CSD do not respect size setting
https://bugs.kde.org/show_bug.cgi?id=426074 --- Comment #4 from Mikhail Zolotukhin --- Well, this is not regression. Before that GTK apps always had had breeze decoration with the same size despite the setting in the Breeze decoration settings. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 426074] Buttons of gtk3 CSD do not respect size setting
https://bugs.kde.org/show_bug.cgi?id=426074 Mikhail Zolotukhin changed: What|Removed |Added Resolution|FIXED |--- Status|RESOLVED|REOPENED --- Comment #3 from Mikhail Zolotukhin --- (In reply to Matej Mrenica from comment #2) > Latest version fixes this issue: > https://github.com/Zren/material-decoration/commit/ > 65fe6f577a978a9e601241d29bea35185eb7f69c This is workaround just for the one decoration theme. So this does not fix the issue for all decorations. The proper fix is to modify the CSS of Breeze GTK theme in the way it respects the geometry of a given decoration theme. Not sure if it is possible universally, but for popular decoration themes (such as Breeze) we can create some workarounds if needed. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 426687] The hover animation for the titlebar buttons is missing in the Breeze GTK theme on Plasma 5.19.90
https://bugs.kde.org/show_bug.cgi?id=426687 Mikhail Zolotukhin changed: What|Removed |Added Ever confirmed|0 |1 Status|NEEDSINFO |CONFIRMED Resolution|WAITINGFORINFO |--- --- Comment #7 from Mikhail Zolotukhin --- Huh? Indeed this setting is gone in the last dev iso. This explains why it is not working. The hack I used was the to temporary disable animations setting and then enable them for the moment the button is drawn. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 426074] Buttons of gtk3 CSD do not respect size setting
https://bugs.kde.org/show_bug.cgi?id=426074 Mikhail Zolotukhin changed: What|Removed |Added CC||matejm98m...@gmail.com --- Comment #1 from Mikhail Zolotukhin --- *** Bug 426670 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 426670] Buttons to close, maximize and minimize windows are very small in gtk apps with CSDs
https://bugs.kde.org/show_bug.cgi?id=426670 Mikhail Zolotukhin changed: What|Removed |Added CC||zom...@protonmail.com Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |DUPLICATE --- Comment #7 from Mikhail Zolotukhin --- I assume the decorations are tiny, because we do not sync the geometry of the buttons with GTK CSD. *** This bug has been marked as a duplicate of bug 426074 *** -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 421745] The color scheme of gtk3 apps is not immediately updated when I change the global theme. Plasma session needs to be restarted.
https://bugs.kde.org/show_bug.cgi?id=421745 Mikhail Zolotukhin changed: What|Removed |Added CC||med.medin.2...@gmail.com --- Comment #9 from Mikhail Zolotukhin --- *** Bug 426727 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 426727] Setting global theme doesn't affect color theme
https://bugs.kde.org/show_bug.cgi?id=426727 Mikhail Zolotukhin changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #2 from Mikhail Zolotukhin --- *** This bug has been marked as a duplicate of bug 421745 *** -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 426687] The hover animation for the titlebar buttons is missing in the Breeze GTK theme on Plasma 5.19.90
https://bugs.kde.org/show_bug.cgi?id=426687 --- Comment #5 from Mikhail Zolotukhin --- This is kinda strange. I did encountered this bug during development, but then specifically wrote a workaround to avoid it. Could you confirm, that if you disable animations in the Breeze decoration settings, the hover effects works? -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kded] [Bug 426669] Kded cannot start since update to Plasma 5.20 Beta
https://bugs.kde.org/show_bug.cgi?id=426669 Mikhail Zolotukhin changed: What|Removed |Added CC||zom...@protonmail.com --- Comment #3 from Mikhail Zolotukhin --- This stacktrace is not very useful. Since you are on Arch could you please compile kde-gtk-config from 5.20 branch and show the extended stacktrace? -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 426687] The hover animation for the titlebar buttons is missing in the Breeze GTK theme on Plasma 5.19.90
https://bugs.kde.org/show_bug.cgi?id=426687 Mikhail Zolotukhin changed: What|Removed |Added CC||zom...@protonmail.com --- Comment #1 from Mikhail Zolotukhin --- Were there animations in the previous Plasma versions? -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 426011] New: Do not stop audio stream on suspend from KDE Connect
https://bugs.kde.org/show_bug.cgi?id=426011 Bug ID: 426011 Summary: Do not stop audio stream on suspend from KDE Connect Product: Powerdevil Version: 5.19.4 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: zom...@protonmail.com Target Milestone: --- SUMMARY In advanced power settings we have an option called "Pause media players when suspending". It pauses all playback when I close laptop lid. However I also have a phone connected to Plasma desktop with KDE Connect. With it when I close the lid playback on the phone also stops, which is undesired, because I have a common scenario, when I work on my laptop and listen to the music from the phone and then go to bed with the phone and continue to listen music here without a pause. You can say "just disable this option", but I think, that this option was introduced because we can also listen to the music on the laptop, then close the lid and bring it to the public place and open it to continue our work, but without our sudden loud music playing out. So I want to keep this functionality, but in the same time have an option to ignore KDE Connect streams. STEPS TO REPRODUCE 1. Enable "Pause media players when suspending" in advanced power settings 2. Connect your phone with KDE Connect 3. Start music playback on the phone 4. Put the computer to suspend OBSERVED RESULT Music on a phone stops playing EXPECTED RESULT Music on the phone should continue playing SOFTWARE/OS VERSIONS Operating System: KDE neon 5.19 KDE Plasma Version: 5.19.4 KDE Frameworks Version: 5.73.0 Qt Version: 5.14.2 Kernel Version: 5.4.0-42-generic OS Type: 64-bit Processors: 8 × Intel® Core™ i7-8550U CPU @ 1.80GHz Memory: 15,5 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics 620 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-krunner] [Bug 423003] krunner crashes as soon as I start typing when PIM Contact Search plugin is enabled
https://bugs.kde.org/show_bug.cgi?id=423003 Mikhail Zolotukhin changed: What|Removed |Added CC||zom...@protonmail.com -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 425123] Middle mouse-click action not triggered on GTK-based applications
https://bugs.kde.org/show_bug.cgi?id=425123 Mikhail Zolotukhin changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED CC||zom...@protonmail.com --- Comment #1 from Mikhail Zolotukhin --- Seems like we possibly could sync KWin titlebar behavior with GNOME CSD one. There is a `org/gnome/desktop/wm/preferences/action-middle-click-titlebar` and other similar settings available. However, when I change those settings via dconf editor - nothing changes and GTK apps are still using default behavior. Could anyone confirm this and provide any alternative way to apply this settings to GTK applications under Plasma? On GNOME those settings are working fine. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 421745] The color scheme of gtk3 apps is not immediately updated when I change the global theme. Plasma session needs to be restarted.
https://bugs.kde.org/show_bug.cgi?id=421745 --- Comment #6 from Mikhail Zolotukhin --- For me colors are changing partially, when changing global theme. No idea why this happens, so I can't really fix it. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 423141] GTK2 theming broken after update to Plasma 5.19
https://bugs.kde.org/show_bug.cgi?id=423141 --- Comment #29 from Mikhail Zolotukhin --- Git commit d9d49d5c8f831a289401c50470a46a2cd5778faa by Mikhail Zolotukhin. Committed on 21/07/2020 at 15:19. Pushed by gikari into branch 'master'. [GTK Integration] Apply the same theme for GTK2 and GTK3 applications GTK configuration in Plasma depends on xsettings daemon, that has no separation between GTK2 and GTK3 theme, therefore separate themes for GTK2 and GTK3 are impossible, while this daemon is working. The daemon itself provides the functionality to apply settings to GTK applications without restarting them. The functionality to apply different themes to applications, depending on the framework version isn't necessary, when 99% of the themes are compatible with both versions and when most of the applications are using the last GTK version anyway. Given all that, I think, that a theme selection must be narrowed to one and only one theme for both versions of the GTK framework. M +1-1kcms/style/CMakeLists.txt D +0-34 kcms/style/gtk2_themes.knsrc R +1-1kcms/style/gtk_themes.knsrc [from: kcms/style/gtk3_themes.knsrc - 095% similarity] M +13 -39 kcms/style/gtkpage.cpp M +7-14 kcms/style/gtkpage.h M +1-17 kcms/style/gtkthemesmodel.cpp M +1-2kcms/style/gtkthemesmodel.h M +17 -95 kcms/style/package/contents/ui/GtkStylePage.qml https://invent.kde.org/plasma/plasma-desktop/commit/d9d49d5c8f831a289401c50470a46a2cd5778faa -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 423141] GTK2 theming broken after update to Plasma 5.19
https://bugs.kde.org/show_bug.cgi?id=423141 --- Comment #28 from Mikhail Zolotukhin --- Git commit 9323a96a9e7ec93f735e10ee671c3824b35429df by Mikhail Zolotukhin. Committed on 21/07/2020 at 15:18. Pushed by gikari into branch 'master'. Provide an unified interface for setting GTK theme GTK configuration in Plasma depends on xsettings daemon, that has no separation between GTK2 and GTK3 theme, therefore separate themes for GTK2 and GTK3 are impossible, while this daemon is working. The daemon itself provides the functionality to apply settings to GTK applications without restarting them. The functionality to apply different themes to applications, depending on the framework version isn't necessary, when 99% of the themes are compatible with both versions and when most of the applications are using the last GTK version anyway. Given all that, I think, that a theme selection must be narrowed to one and only one theme for both versions of the GTK framework. M +0-1CMakeLists.txt D +0-12 gtkproxies/CMakeLists.txt D +0-130 gtkproxies/preview.c D +0-576 gtkproxies/preview.ui D +0-71 gtkproxies/reload.c M +21 -1kconf_update/gtktheme.cpp M +3-28 kded/configeditor.cpp M +0-2kded/configeditor.h M +3-17 kded/gtkconfig.cpp M +3-8kded/gtkconfig.h M +0-60 kded/themepreviewer.cpp M +0-10 kded/themepreviewer.h https://invent.kde.org/plasma/kde-gtk-config/commit/9323a96a9e7ec93f735e10ee671c3824b35429df -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 424436] Dark Breeze theme not available for GTK3
https://bugs.kde.org/show_bug.cgi?id=424436 Mikhail Zolotukhin changed: What|Removed |Added Status|REOPENED|RESOLVED Resolution|--- |INTENTIONAL --- Comment #7 from Mikhail Zolotukhin --- > 1- Set global theme to non breeze theme for example Breath. Apply. > 2- Set GTK3 theme to Breath. Apply. > 3- Set global theme to Dark breeze. Normally from what I understand in this > stage GTK3 theme should be set to Dark breeze to follow Qt theming. > 4- Open a GTK3 app you will find it still uses Breath theme. > > So the problem is when you set your Global theme to Dark breeze then the > GTK3 theme should be set to breeze (this name really confuses because we > used to see it light but now it produces dark theme) You mean, that global themes do not have their preference for GTK themes? Indeed, that's the case. Please open a separate bug report for this :) -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 424436] Dark Breeze theme not available for GTK3
https://bugs.kde.org/show_bug.cgi?id=424436 Mikhail Zolotukhin changed: What|Removed |Added Status|REOPENED|RESOLVED Resolution|--- |INTENTIONAL --- Comment #5 from Mikhail Zolotukhin --- > So for now GTK3 theme setting (Settings>Application_Style) is not working at > all and is controlled by Qt theme settings ? No, it should work. > Who this genius that suggested to use one theme for Qt and GTK2/3, I always > use a downloaded themes for my GTK3 apps why would they follow Qt theme ? We do not touch non-Breeze themes. They should work. > And why when I set global theme to Breath-Dark theme, I still can find > Breath-Dark theme option in the list for GTK3 ? Breath and Breeze are different themes. Breath comes from Manajaro developers. We only hide Breeze-Dark and sync colors for Breeze. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 424436] Dark Breeze theme not available for GTK3
https://bugs.kde.org/show_bug.cgi?id=424436 Mikhail Zolotukhin changed: What|Removed |Added CC||zom...@protonmail.com Status|REOPENED|RESOLVED Resolution|--- |INTENTIONAL --- Comment #3 from Mikhail Zolotukhin --- > And if I wanted to use Oxygen theme for Plasma and dark breeze theme for > GTK3 ? Set color scheme to dark one and Breeze GTK will be dark. > And why GTK2 still has the possibility to select dark breeze theme > and not possible for GTK3 ? Because GTK2 does not have support for dynamic recoloring according to color scheme. Even more, we plan to remove GTK2 theme setting option and unite it with GTK3 one since GTK2 is old and deprecated. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 424427] Unify scrollbar behaviour and look
https://bugs.kde.org/show_bug.cgi?id=424427 Mikhail Zolotukhin changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED CC||zom...@protonmail.com --- Comment #1 from Mikhail Zolotukhin --- Thanks for reporting! *** This bug has been marked as a duplicate of bug 418516 *** -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 418516] Enable scrollbar arrows for Breeze GTK theme when they are enabled in Breeze widget theme
https://bugs.kde.org/show_bug.cgi?id=418516 Mikhail Zolotukhin changed: What|Removed |Added CC||med.medin.2...@gmail.com --- Comment #3 from Mikhail Zolotukhin --- *** Bug 424427 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 418936] On Wayland, cursor theme is not applied to GTK3 apps installed via flatpak
https://bugs.kde.org/show_bug.cgi?id=418936 Mikhail Zolotukhin changed: What|Removed |Added Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #3 from Mikhail Zolotukhin --- Cannot reproduce on latest KDE Neon Unstable. Could you reproduce? -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 418936] On Wayland, cursor theme is not applied to GTK3 apps installed via flatpak
https://bugs.kde.org/show_bug.cgi?id=418936 --- Comment #2 from Mikhail Zolotukhin --- (In reply to Nate Graham from comment #1) > Is this something we can set with xsettings maybe? Xsettings, as far as I know, is for X11 only. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 421133] Wayland: cursor is always the default size when hovering over GTK apps
https://bugs.kde.org/show_bug.cgi?id=421133 Mikhail Zolotukhin changed: What|Removed |Added Resolution|--- |FIXED Status|ASSIGNED|RESOLVED Latest Commit||https://invent.kde.org/plas ||ma/kde-gtk-config/commit/83 ||59e316e7b14e81f4cbdf4ceb147 ||83b7c90fc44 --- Comment #7 from Mikhail Zolotukhin --- Git commit 8359e316e7b14e81f4cbdf4ceb14783b7c90fc44 by Mikhail Zolotukhin. Committed on 17/07/2020 at 13:39. Pushed by gikari into branch 'master'. Synchronize the cursor size setting M +1-1README.md M +6-0kded/configvalueprovider.cpp M +1-0kded/configvalueprovider.h M +17 -3kded/gtkconfig.cpp M +1-0kded/gtkconfig.h https://invent.kde.org/plasma/kde-gtk-config/commit/8359e316e7b14e81f4cbdf4ceb14783b7c90fc44 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 423141] GTK2 theming broken after update to Plasma 5.19
https://bugs.kde.org/show_bug.cgi?id=423141 --- Comment #27 from Mikhail Zolotukhin --- (In reply to Nate Graham from comment #24) > Given the information you've provided here, I think we should do that. Maybe > you can re-open those or put them in GitLab? > > Inkscape just had its 1.0 release and now uses GTK3 so that pretty much just > leaves GIMP. Done. https://invent.kde.org/plasma/plasma-desktop/-/merge_requests/54 https://invent.kde.org/plasma/kde-gtk-config/-/merge_requests/7 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 423141] GTK2 theming broken after update to Plasma 5.19
https://bugs.kde.org/show_bug.cgi?id=423141 --- Comment #23 from Mikhail Zolotukhin --- It's impossible to fix keeping the existing functionality, i.e. changing the settings of the GTK apps without restarting them, using xsettingsd. More over GTK2 is deprecated, I do not want to sacrifice the UX and features to support the rare use case, where the themes for GTK applications depend on the framework version, and what's even more, where one version is too old and still used by 1-2 applications (Audacity (via wxWidgets) and GIMP), that still for some reason cannot port themselves to the newer version of the framework they are using during all these years (9 years since GTK3 release, I think). Regarding the previews: GTK2 one uses a hack: it stops xsettingsd before launching and starts it after closing the preview. This cannot be used for applications, that stay open during a long period of time, because this behavior breaks "on the fly settings changing" feature. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 423141] GTK2 theming broken after update to Plasma 5.19
https://bugs.kde.org/show_bug.cgi?id=423141 --- Comment #21 from Mikhail Zolotukhin --- The old diffs were here https://phabricator.kde.org/D29749 and there https://phabricator.kde.org/D29748 If I understood correctly, the main reasons the diff was abordoned were the UI and the fact, that there are still some major apps, that use GTK2 (GIMP and Audacity). I started a work on a list-based GTK theme selection some time ago, but it is unfinished and somewhat hacky on the Kirigami/QML side, since we do not have the exact needed component. Currently I don't have enough time to fully implement the idea, but I can create merge requests on Invent from the old diffs, -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 423141] GTK2 theming broken after update to Plasma 5.19
https://bugs.kde.org/show_bug.cgi?id=423141 Mikhail Zolotukhin changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |INTENTIONAL --- Comment #18 from Mikhail Zolotukhin --- This "bug" is happening, because GTK2 applications are using the theme provided by GTK3 setting, because the latter sets itself in xsettingsd.conf file. And xsettings does not have a separate settings for GTK2 and GTK3 applications (therefore it applies the theme from the config to both). Therefore, unfortunately, this is unfixable. It's also one of the reasons why I wanted to merge GTK2 and GTK3 theme setting into one in the UI. If the OP really want to use separate themes for GTK2 and GTK3 applications (which are rare these days if the themes are new), they can uninstall the xsettingsd daemon. But please note, that this action makes it impossible to change the theme and other settings (such as fonts, icons etc.) for GTK applications on the fly, i.e. without restarting them, Or the OP can just use one theme for GTK2 and GTK3 applications. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 422586] KDE resets GTK font setting to non-condensed font
https://bugs.kde.org/show_bug.cgi?id=422586 --- Comment #4 from Mikhail Zolotukhin --- What "hidden dconf method" are you talking about? -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 421393] Gtk configuration is broken on Fedora 32
https://bugs.kde.org/show_bug.cgi?id=421393 Mikhail Zolotukhin changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #12 from Mikhail Zolotukhin --- The problem is, that DPI scaling was incorrectly applied to GTK application. It is a fault of previous configuration. If you could, please check if you can reproduce this issue on a fresh Fedora KDE Spin install. Also, did you installed KDE on Fedora by yourself or used a Fedora KDE Spin? -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 421393] Gtk configuration is broken on Fedora 32
https://bugs.kde.org/show_bug.cgi?id=421393 --- Comment #10 from Mikhail Zolotukhin --- If you change the global scale in Display Configuration in System Settings to 100%, do the fonts become the equal size? If you change it to 125% or other scale? -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 421393] Gtk configuration is broken on Fedora 32
https://bugs.kde.org/show_bug.cgi?id=421393 Mikhail Zolotukhin changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO --- Comment #6 from Mikhail Zolotukhin --- What size are you using? What's inside ~/.config/gtk-3.0/settings.ini? -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 421393] Gtk configuration is broken on Fedora 32
https://bugs.kde.org/show_bug.cgi?id=421393 --- Comment #4 from Mikhail Zolotukhin --- Sorry, cannot reproduce. Could you please send the fonts you're using in Fonts System Settings page and the contents of the ~/.config/gtk-3.0/settings.ini? -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 421393] Gtk configuration is broken on Fedora 32
https://bugs.kde.org/show_bug.cgi?id=421393 --- Comment #2 from Mikhail Zolotukhin --- Sorry! I overlooked this bug report. Could you reproduce the issue on a fresh install or live USB? -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 422064] Flatpak apps do not follow the system color scheme
https://bugs.kde.org/show_bug.cgi?id=422064 Mikhail Zolotukhin changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 422010] regression: GTK theme doesn't apply to flatpak apps since Plasma 5.18.5
https://bugs.kde.org/show_bug.cgi?id=422010 --- Comment #9 from Mikhail Zolotukhin --- > Going to "Application Style > GNOME/GTK Application Style" and setting > Breeze-Dark explicitly there, was the only why I could get Flatpak apps to > apply the dark theme. Have you tested this? Flakpak apps indeed do not folow the system color scheme. Feel free to open a separate bug for that. -- You are receiving this mail because: You are watching all bug changes.
