[kdevelop] [Bug 368458] Can't change highlight color used when hovering identifier

https://bugs.kde.org/show_bug.cgi?id=368458 --- Comment #1 from Elvis Stansvik --- Created attachment 100986 --> https://bugs.kde.org/attachment.cgi?id=100986=edit Hovering an identifier in the editor -- You are receiving this mail because: You are watching all bug

[kdevelop] [Bug 368458] New: Can't change highlight color used when hovering identifier

https://bugs.kde.org/show_bug.cgi?id=368458 Bug ID: 368458 Summary: Can't change highlight color used when hovering identifier Product: kdevelop Version: 5.0.0 Platform: Other OS: Linux Status:

[Breeze] [Bug 368337] Consider disabling Qt::WA_OpaquePaintEvent for QSplitterHandle

https://bugs.kde.org/show_bug.cgi?id=368337 --- Comment #10 from Elvis Stansvik --- Sorry, I was wrong in the above. Breeze does respect handleWidth, but the default is for it to have no width, and unlike Fusion there are no "dots" or marks on the handle to indicate it is a

[Breeze] [Bug 368337] Consider disabling Qt::WA_OpaquePaintEvent for QSplitterHandle

https://bugs.kde.org/show_bug.cgi?id=368337 --- Comment #9 from Elvis Stansvik --- Ah, that could perhaps work. Though my test case just used QGLWidget because that was an easy way to make a minimal test case. In our real application it's a QVTKWidget [1], and I'm not sure

[Breeze] [Bug 368337] Consider disabling Qt::WA_OpaquePaintEvent for QSplitterHandle

https://bugs.kde.org/show_bug.cgi?id=368337 --- Comment #7 from Elvis Stansvik --- Sorry, posted the above comment before I read your reply. Thanks for the fast reply, I think I understand what is going on, and I understand the rationale for the proxy (since the default

[Breeze] [Bug 368337] Consider disabling Qt::WA_OpaquePaintEvent for QSplitterHandle

https://bugs.kde.org/show_bug.cgi?id=368337 --- Comment #6 from Elvis Stansvik --- Okay, I've now confirmed that disabling use of the SplitterProxy, by setting SplitterProxyEnabled to false in the Breeze style config, fixes the issue. So perhaps the problem is that the

[Breeze] [Bug 368337] Consider disabling Qt::WA_OpaquePaintEvent for QSplitterHandle

https://bugs.kde.org/show_bug.cgi?id=368337 --- Comment #4 from Elvis Stansvik --- My analysis might not be correct, as I just tried adding splitter->handle(1)->setAttribute(Qt::WA_OpaquePaintEvent, false); to the test case, and the problem remains. I see there's

[Breeze] [Bug 368337] Consider disabling Qt::WA_OpaquePaintEvent for QSplitterHandle

https://bugs.kde.org/show_bug.cgi?id=368337 --- Comment #3 from Elvis Stansvik --- Created attachment 100954 --> https://bugs.kde.org/attachment.cgi?id=100954=edit Screenshot showing the artifact issue -- You are receiving this mail because: You are watching all bug

[Breeze] [Bug 368337] Consider disabling Qt::WA_OpaquePaintEvent for QSplitterHandle

https://bugs.kde.org/show_bug.cgi?id=368337 --- Comment #1 from Elvis Stansvik --- Created attachment 100952 --> https://bugs.kde.org/attachment.cgi?id=100952=edit Test case source code -- You are receiving this mail because: You are watching all bug changes.

[Breeze] [Bug 368337] Consider disabling Qt::WA_OpaquePaintEvent for QSplitterHandle

https://bugs.kde.org/show_bug.cgi?id=368337 --- Comment #2 from Elvis Stansvik --- Created attachment 100953 --> https://bugs.kde.org/attachment.cgi?id=100953=edit .pro file to build test case -- You are receiving this mail because: You are watching all bug changes.

[Breeze] [Bug 368337] New: Consider disabling Qt::WA_OpaquePaintEvent for QSplitterHandle

https://bugs.kde.org/show_bug.cgi?id=368337 Bug ID: 368337 Summary: Consider disabling Qt::WA_OpaquePaintEvent for QSplitterHandle Product: Breeze Version: 5.5.5 Platform: Ubuntu Packages OS: Linux

[kdelibs] [Bug 279592] Allow per-application color scheme

https://bugs.kde.org/show_bug.cgi?id=279592 Elvis Stansvik changed: What|Removed |Added CC||elvst...@gmail.com ---

[plasma4] [Bug 323230] windows (maximized) are going under the vertical panel on dual screen setup

https://bugs.kde.org/show_bug.cgi?id=323230 --- Comment #38 from Elvis Stansvik --- Btw, the monitor/screen layout I'm using is: xrandr --output DP2-2 --mode 2560x1440 --primary --output eDP1 --mode 1920x1080 --left-of DP2-2 That is, the laptop panel (eDP1) to the left of

[plasma4] [Bug 323230] windows (maximized) are going under the vertical panel on dual screen setup

https://bugs.kde.org/show_bug.cgi?id=323230 Elvis Stansvik changed: What|Removed |Added CC||elvst...@gmail.com ---

[kdenlive] [Bug 351730] Getting numerous errors from Konsole: "QXcbConnection: XCB error: 8 (BadMatch), sequence: 50336, resource id: 115343659, major code: 130 (Unknown), minor code: 3"

https://bugs.kde.org/show_bug.cgi?id=351730 Elvis Stansvik changed: What|Removed |Added CC||elvst...@gmail.com ---

[plasmashell] [Bug 356874] Warn user about locked widgets in wallpaper settings

https://bugs.kde.org/show_bug.cgi?id=356874 --- Comment #4 from Elvis Stansvik --- Yea, that'll work. I would have found that when I was first searching around. -- You are receiving this mail because: You are watching all bug changes.

[kate] [Bug 356974] Support for syntax highlighted fenced code blocks in Markdown

https://bugs.kde.org/show_bug.cgi?id=356974 --- Comment #1 from Elvis Stansvik --- I should add that, should Kate gain a live Markdown preview, which I've heard people ask for, then this wish could almost be thrown in the garbage, since I think it would then be easy to let

[kate] [Bug 356974] New: Support for syntax highlighted fenced code blocks in Markdown

https://bugs.kde.org/show_bug.cgi?id=356974 Bug ID: 356974 Summary: Support for syntax highlighted fenced code blocks in Markdown Product: kate Version: unspecified Platform: Other OS: Linux

[plasmashell] [Bug 356899] Desktop Settings are not saved and loads default settings on reboot/startup.

https://bugs.kde.org/show_bug.cgi?id=356899 Elvis Stansvik changed: What|Removed |Added CC||elvst...@gmail.com

[plasmashell] [Bug 356899] Desktop Settings are not saved and loads default settings on reboot/startup.

https://bugs.kde.org/show_bug.cgi?id=356899 --- Comment #2 from Elvis Stansvik --- Created attachment 96212 --> https://bugs.kde.org/attachment.cgi?id=96212=edit ~/.config/plasma-org.kde.plasma.desktop-appletsrc before applying settings -- You are receiving this mail

[plasmashell] [Bug 356899] Desktop Settings are not saved and loads default settings on reboot/startup.

https://bugs.kde.org/show_bug.cgi?id=356899 --- Comment #4 from Elvis Stansvik --- Created attachment 96214 --> https://bugs.kde.org/attachment.cgi?id=96214=edit ~/.config/plasma-org.kde.plasma.desktop-appletsrc after logging out and in again -- You are receiving this

[plasmashell] [Bug 356899] Desktop Settings are not saved and loads default settings on reboot/startup.

https://bugs.kde.org/show_bug.cgi?id=356899 --- Comment #3 from Elvis Stansvik --- Created attachment 96213 --> https://bugs.kde.org/attachment.cgi?id=96213=edit ~/.config/plasma-org.kde.plasma.desktop-appletsrc after unchecking "Show desktop toolbox" and setting Layout to

[plasmashell] [Bug 356899] Desktop Settings are not saved and loads default settings on reboot/startup.

https://bugs.kde.org/show_bug.cgi?id=356899 --- Comment #6 from Elvis Stansvik --- My ~/.xsession-errors after relogin, shows no indication of a plasmashell crash during the relogin (searched for "crash" and "plasmashell" in it). Is it possible that plasmashell somehow

[plasmashell] [Bug 356899] Desktop Settings are not saved and loads default settings on reboot/startup.

https://bugs.kde.org/show_bug.cgi?id=356899 --- Comment #7 from Elvis Stansvik --- Or is the lastScreen setting the culprit here? After applying the settings changes, I have lastScreen=-1 in the [Containments][42]. Before the change, I had lastScreen=0 in [Containments][28],

[plasmashell] [Bug 351079] Spontaneously adding desktop containments at startup

https://bugs.kde.org/show_bug.cgi?id=351079 --- Comment #10 from Elvis Stansvik --- (In my comment above I said ~/.config/plasma-org.kde.plasma.desktop-appletsrc_after, this was a paste-o and I of course meant ~/.config/plasma-org.kde.plasma.desktop-appletsrc. The former was

[plasmashell] [Bug 356899] Desktop Settings are not saved and loads default settings on reboot/startup.

https://bugs.kde.org/show_bug.cgi?id=356899 --- Comment #8 from Elvis Stansvik --- Another piece of info: In my .xsession-errors, I get several: kscreen: Primary output changed from KScreen::Output(Id: 73 , Name: "VGA1" ) ( "VGA1" ) to KScreen::Output(Id: 73 , Name: "VGA1" )

[plasmashell] [Bug 356899] Desktop Settings are not saved and loads default settings on reboot/startup.

https://bugs.kde.org/show_bug.cgi?id=356899 --- Comment #10 from Elvis Stansvik --- See also https://bugs.kde.org/show_bug.cgi?id=351079 which I believe is the issue with containments I'm seeing, and which may be related (causing?) this bug. -- You are receiving this mail

[plasmashell] [Bug 351079] Spontaneously adding desktop containments at startup

https://bugs.kde.org/show_bug.cgi?id=351079 Elvis Stansvik changed: What|Removed |Added CC||elvst...@gmail.com ---

[plasmashell] [Bug 343216] Plasmashell crased after exiting full screen

https://bugs.kde.org/show_bug.cgi?id=343216 --- Comment #14 from Elvis Stansvik --- Created attachment 96205 --> https://bugs.kde.org/attachment.cgi?id=96205=edit The effect on fonts after the crash As a side effect of the crash, something happened to the fonts in certain

[plasmashell] [Bug 356874] New: Warn user about locked widgets in wallpaper settings

https://bugs.kde.org/show_bug.cgi?id=356874 Bug ID: 356874 Summary: Warn user about locked widgets in wallpaper settings Product: plasmashell Version: 5.5.1 Platform: Archlinux Packages OS: Linux Status: