[systemsettings] [Bug 421745] On Wayland, the color scheme of gtk3 apps is not immediately updated when I change the global theme; the apps need to be restarted
https://bugs.kde.org/show_bug.cgi?id=421745 --- Comment #45 from SoilpH96 --- For me, the GTK color settings aren't applied the first time after I open a application if I use the plasma-apply-colorscheme command line tool (both when using it directly or invoking it from scripts). They will be applied at all subsequent times, and will be applied if the color scheme is changed from System Settings. Firefox also does not apply the color scheme correctly the first time even if using System Settings, appearing to use the Adwaita theme, but will apply it correctly at subsequent times. Chromium appears to require restarting to apply any color scheme correctly. The end result is that currently theme switching automated via scripting remains mostly broken in GTK applications on Wayland. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 462249] Krita should have a option to respect system color scheme
https://bugs.kde.org/show_bug.cgi?id=462249 --- Comment #3 from SoilpH96 --- Respectfully I think it should be provided as a option, since it is not mandatory in the other applications I mentioned to use the system color scheme, but it is possible to use a custom one. Other graphics applications like GIMP also let you use the system provided theme. I attached a comparison of Kate and Krita's current UI to select the in-app theme to better explain what I'm talking about, you can also see in this screenshot the visual bug where Krita applies two accent colors (one from the KDE system theme which is Breeze Light in this example and one from its own theme), whereas Kate applies the whole theme consistently in all its interface with only one accent color. This should be fixed regardless because it's a inconsistency that bothers specifically who is going to use their own color scheme. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 462249] Krita should have a option to respect system color scheme
https://bugs.kde.org/show_bug.cgi?id=462249 --- Comment #2 from SoilpH96 --- Created attachment 154041 --> https://bugs.kde.org/attachment.cgi?id=154041=edit comparison of kate and krita -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 462249] New: Krita should have a option to respect system color scheme
https://bugs.kde.org/show_bug.cgi?id=462249 Bug ID: 462249 Summary: Krita should have a option to respect system color scheme Classification: Applications Product: krita Version: 5.1.3 Platform: Archlinux OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: General Assignee: krita-bugs-n...@kde.org Reporter: filippo27...@gmail.com Target Milestone: --- Currently, Krita has no option to respect the KDE system color schemes but only provides its own. It should have a option to use the system default color scheme similar to other KDE apps like Kate, Konsole, Okular among others. As it is currently implemented, there is also a mismatch of the Krita accent color and the KDE accent color in the UI, with the latter appearing in some places like hovering over menus. This inconsistency doesn't exist in the other apps I mentioned when changing color scheme. Reporting as a minor bug because of this visual inconsistency. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 445196] Open/Save File Dialog suffers from horrible tearing in Wayland under certain circumstances.
https://bugs.kde.org/show_bug.cgi?id=445196 --- Comment #18 from SoilpH96 --- Hello, this bug has been marked as fixed for a good while, but there hasn't been a Phonon release since then to distribute the fix. Could it be possible to do a new minor release of Phonon, or at least recommend distros to include this patch, since this has long persisted as a serious usability problem on Wayland? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 460643] lookandfeeltool crashes/doesn't work when invoked by other tools such as cron, darkman...
https://bugs.kde.org/show_bug.cgi?id=460643 --- Comment #3 from SoilpH96 --- (In reply to Nicolas Fella from comment #2) > Using "lookandfeeltool -platform offscreen" should avoid the crash, but it > could break some parts of the functionality Yes it works and doesn't seem to break any functionality. Hooray. The darkman author should probably be notified so that he can update the example scripts. So should this bug be marked as resolved or is the crash without this flag unintended behavior? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 460643] New: lookandfeeltool crashes/doesn't work when invoked by other tools such as cron, darkman...
https://bugs.kde.org/show_bug.cgi?id=460643 Bug ID: 460643 Summary: lookandfeeltool crashes/doesn't work when invoked by other tools such as cron, darkman... Classification: Plasma Product: plasmashell Version: 5.26.0 Platform: Archlinux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Global Theme packages Assignee: plasma-b...@kde.org Reporter: filippo27...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 SUMMARY I used the tool darkman (https://darkman.whynothugo.nl/) to automate dark theme switching at night. This has stopped working since updating to Plasma 5.26. I've found that lookandfeeltool, which was invoked by darkman via scripts, crashed every time darkman activates, but invoking it manually via command-line works. Using cron to invoke lookandfeeltool also appears to not work, but I have not found coredumps caused by that. Operating System: Arch Linux KDE Plasma Version: 5.26.0 KDE Frameworks Version: 5.99.0 Qt Version: 5.15.6 Kernel Version: 6.0.2-arch1-1 (64-bit) Graphics Platform: Wayland BACKTRACE #0 0x7faa7ae81b1b in __GI_mincore () at ../sysdeps/unix/syscall-template.S:117 #1 0x7faa740bfe68 in _eglPointerIsDereferencable () at ../mesa-22.2.1/src/egl/main/eglglobals.c:159 #2 0x7faa740cf21b in get_wl_surface_proxy () at ../mesa-22.2.1/src/egl/drivers/dri2/platform_wayland.c:422 #3 dri2_wl_create_window_surface () at ../mesa-22.2.1/src/egl/drivers/dri2/platform_wayland.c:701 #4 0x7faa740b6680 in _eglCreateWindowSurfaceCommon () at ../mesa-22.2.1/src/egl/main/eglapi.c:994 #5 0x7faa740b7b19 in eglCreatePlatformWindowSurface () at ../mesa-22.2.1/src/egl/main/eglapi.c:1071 #6 0x7faa75567ad4 in QtWaylandClient::QWaylandGLContext::updateGLFormat (this=0x555a86357980) at /usr/src/debug/qtwayland/src/hardwareintegration/client/wayland-egl/qwaylandglcontext.cpp:357 #7 QtWaylandClient::QWaylandGLContext::QWaylandGLContext (share=0x555a863579c0, format=..., display=, eglDisplay=, this=0x555a86357980) at /usr/src/debug/qtwayland/src/hardwareintegration/client/wayland-egl/qwaylandglcontext.cpp:340 #8 QtWaylandClient::QWaylandEglClientBufferIntegration::createPlatformOpenGLContext (this=this@entry=0x555a86275030, glFormat=..., share=share@entry=0x0) at /usr/src/debug/qtwayland/src/hardwareintegration/client/wayland-egl/qwaylandeglclientbufferintegration.cpp:155 #9 0x7faa79f0b6e3 in QtWaylandClient::QWaylandIntegration::createPlatformOpenGLContext (this=, context=0x7ffc64a42e40) at /usr/src/debug/qtwayland/src/client/qwaylandintegration.cpp:178 #10 0x7faa7ba710e3 in QOpenGLContext::create (this=this@entry=0x7ffc64a42e40) at kernel/qopenglcontext.cpp:612 #11 0x7faa755a8191 in checkBackend (checkContext=...) at /usr/src/debug/plasma-integration-5.26.0/src/platformtheme/qtquickrenderersettings.cpp:43 #12 initializeRendererSessions () at /usr/src/debug/plasma-integration-5.26.0/src/platformtheme/qtquickrenderersettings.cpp:79 #13 initializeRendererSessions () at /usr/src/debug/plasma-integration-5.26.0/src/platformtheme/qtquickrenderersettings.cpp:52 #14 0x7faa7b51902f in qt_call_pre_routines () at kernel/qcoreapplication.cpp:317 #15 QCoreApplicationPrivate::init (this=this@entry=0x555a86271b70) at kernel/qcoreapplication.cpp:849 #16 0x7faa7ba2a1b9 in QGuiApplicationPrivate::init (this=this@entry=0x555a86271b70) at kernel/qguiapplication.cpp:1530 #17 0x7faa7c0d0e0e in QApplicationPrivate::init (this=0x555a86271b70) at kernel/qapplication.cpp:513 #18 0x7faa7c0d0f34 in QApplication::QApplication (this=, argc=, argv=, _internal=, this=, argc=, argv=, _internal=) at kernel/qapplication.cpp:501 #19 0x555a8536a09d in main (argc=, argv=) at /usr/src/debug/plasma-workspace-5.26.0/kcms/lookandfeel/lnftool.cpp:27 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 421745] The color scheme of gtk3 apps is not immediately updated when I change the global theme; the apps need to be restarted
https://bugs.kde.org/show_bug.cgi?id=421745 SoilpH96 changed: What|Removed |Added CC||filippo27...@gmail.com --- Comment #37 from SoilpH96 --- Can still reproduce on Plasma 5.25.5. Tested on Firefox and Virt-Manager. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 448044] GTK apps do not change colors when switching Global Themes that specify color schemes
https://bugs.kde.org/show_bug.cgi?id=448044 SoilpH96 changed: What|Removed |Added CC||filippo27...@gmail.com --- Comment #8 from SoilpH96 --- I suffer from this bug as well, but it's worth mentioning that Firefox specifically appears to change its theme to Adwaita, even though the specified GTK theme is still Breeze according to gsettings. I can confirm that the workaround is to set the color scheme manually. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 451407] New: [Visual consistency] System tray should follow icon theme rather than plasma style
https://bugs.kde.org/show_bug.cgi?id=451407 Bug ID: 451407 Summary: [Visual consistency] System tray should follow icon theme rather than plasma style Product: plasmashell Version: 5.24.3 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: System Tray Assignee: plasma-b...@kde.org Reporter: filippo27...@gmail.com CC: mate...@gmail.com Target Milestone: 1.0 When using an icon theme different from the one in the plasma style, most icons in the system tray don't change, but every other icon in Plasma, including in the taskbar, launcher and on Plasmoids, does. The workaround would be to manually change icons in the Plasma theme but it is pretty cumbersome. I'm requesting in this report to make it so that the system tray can follow the icon theme specified by the user, even if it is changed. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 432123] Libreoffice opens with generic LO icon on panel in wayland, not on X11
https://bugs.kde.org/show_bug.cgi?id=432123 SoilpH96 changed: What|Removed |Added CC||filippo27...@gmail.com --- Comment #5 from SoilpH96 --- LibreOffice can correctly set its icon if loaded with the gtk3 backend (run SAL_USE_VCLPLUGIN=gtk3 libreoffice --writer to test). Different LibreOffice applications also will show in separate icons on the taskbar. So, it is not a bug affecting LibreOffice as a whole but only its KF5 backend. According to what I found on the LO bugzilla (https://bugs.documentfoundation.org/show_bug.cgi?id=125934) this is due to a missing implementation in Qt5 (https://bugreports.qt.io/browse/QTBUG-77182) of the Wayland specification, that has since been properly implemented in GTK. So this seems to be neither a Plasma nor a LibreOffice bug, rather a Qt bug. It *might* be possible to work around it with some hacks in Plasma, but it's probably better to try getting it fixed upstream. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 448078] Global Menu does not work in Qt6 on Wayland
https://bugs.kde.org/show_bug.cgi?id=448078 SoilpH96 changed: What|Removed |Added Summary|Global Menu does not work |Global Menu does not work |in Qt6 |in Qt6 on Wayland -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 448078] New: Global Menu does not work in Qt6
https://bugs.kde.org/show_bug.cgi?id=448078 Bug ID: 448078 Summary: Global Menu does not work in Qt6 Product: plasmashell Version: 5.23.5 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Global Menu Assignee: k...@privat.broulik.de Reporter: filippo27...@gmail.com CC: mvourla...@gmail.com, plasma-b...@kde.org Target Milestone: 1.0 SUMMARY Global menu does not appear when using a Qt6 application in a Wayland session STEPS TO REPRODUCE 1. Start Plasma Wayland. 2. Open any Qt6 application (tested on Qbittorrent 4.4) OBSERVED RESULT The global menu is not rendered. The menu in application windows is also not rendered, unlike a similar bug (Bug 424485) affecting GTK applications on Wayland. The global menu is correctly rendered for applications running on XWayland. EXPECTED RESULT The menu should be rendered properly, as with Qt5 apps. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.23.5 KDE Frameworks Version: 5.89.0 Qt5 Version: 5.15.2 Qt6 Version: 6.2.2 Kernel Version: 5.15.13-arch1-1 (64-bit) Graphics Platform: Wayland -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 445196] Open/Save File Dialog suffers from horrible tearing in Wayland under certain circumstances.
https://bugs.kde.org/show_bug.cgi?id=445196 --- Comment #2 from SoilpH96 --- Created attachment 143406 --> https://bugs.kde.org/attachment.cgi?id=143406=edit Tearing in file dialog. Here is a screenshot of the bug occurring. The application used to trigger this is Firefox with "widget.use-xdg-desktop-portal" enabled in about:config. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 445196] New: Open/Save File Dialog suffers from horrible tearing in Wayland under certain circumstances.
https://bugs.kde.org/show_bug.cgi?id=445196 Bug ID: 445196 Summary: Open/Save File Dialog suffers from horrible tearing in Wayland under certain circumstances. Product: frameworks-kio Version: 5.87.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Open/save dialogs Assignee: kio-bugs-n...@kde.org Reporter: filippo27...@gmail.com CC: kdelibs-b...@kde.org Target Milestone: --- SUMMARY When browsing folders within the file dialog in Wayland, bad tearing can happen, making the dialog unusable. This can always be reproduced with Firefox (version 94.0.1), but only occasionally with other applications (I also got it reliably when trying to choose a new notification sound in System Settings). STEPS TO REPRODUCE 1. Open the file dialog from Firefox 2. Try to browse OBSERVED RESULT The folder view tears badly, making the dialog unusable. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.23.2 KDE Frameworks Version: 5.87.0 Qt Version: 5.15.2 Kernel Version: 5.14.16-arch1-1 (64-bit) Graphics Platform: Wayland Processors: 4 × Intel® Core™ i5-7200U CPU @ 2.50GHz Memory: 7.7 GiB of RAM Graphics Processor: Mesa Intel® HD Graphics 620 -- You are receiving this mail because: You are watching all bug changes.
[flatpak-platform-plugin] [Bug 417768] GTK apps from FlatPak or run with GTK_USE_PORTAL=1 set do not respect GTK theme set in System Settings
https://bugs.kde.org/show_bug.cgi?id=417768 SoilpH96 changed: What|Removed |Added CC|filippo27...@gmail.com | -- You are receiving this mail because: You are watching all bug changes.
[flatpak-platform-plugin] [Bug 417768] GTK apps from FlatPak or run with GTK_USE_PORTAL=1 set do not respect GTK theme set in System Settings
https://bugs.kde.org/show_bug.cgi?id=417768 SoilpH96 changed: What|Removed |Added CC||filippo27...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 435807] [Feature request] Add a setting to prevent discover from checking for updates automatically.
https://bugs.kde.org/show_bug.cgi?id=435807 --- Comment #2 from SoilpH96 --- (In reply to Aleix Pol from comment #1) > I'm not really familiar with the problem in ArchLinux. Is it documented > anywhere? https://wiki.archlinux.org/index.php/System_maintenance#Partial_upgrades_are_unsupported https://wiki.archlinux.org/index.php/GNOME/Tips_and_tricks#Prevent_GNOME_Software_from_downloading_updates > I'm not sure it makes sense to stop all cache refreshes. For example we > probably need one when starting Discover or the package states are > potentially all out of sync. I don't think this is necessarily a problem, the cache would still be refreshed when the user decides to initiate the update, obviously. > Furthermore, I'm not sure the option should be in the GUI either. How would > a user know they need to disable updates download? As long as the option exists I am fine, really. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 435807] New: [Feature request] Add a setting to prevent discover from checking for updates automatically.
https://bugs.kde.org/show_bug.cgi?id=435807 Bug ID: 435807 Summary: [Feature request] Add a setting to prevent discover from checking for updates automatically. Product: Discover Version: 5.21.4 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: PackageKit Assignee: lei...@leinir.dk Reporter: filippo27...@gmail.com CC: aleix...@kde.org Target Milestone: --- Currently, there is no option (that I know of) to prevent Discover from checking for updates in the background. While this behavior might be the most convenient default for most users, one might want to stop automatic updates for any reason. In particular, on Arch Linux this behavior using the PackageKit backend leads to a "partial update" which is unsupported by pacman and can potentially cause breakage if the user is not careful, which makes it really hard for Arch users to recommend using Discover. According to the Arch Wiki, GNOME Software has a similar setting through dconf, "gsettings set org.gnome.software download-updates false", but I have not tested this as I don't use GNOME. My request is to add this feature to Discover and expose it through GUI. Thank you for your attention. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 431178] Quick tiled windows can't be maximized
https://bugs.kde.org/show_bug.cgi?id=431178 SoilpH96 changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #1 from SoilpH96 --- The bug appears to have been resolved after updating to Plasma 5.21. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 431275] matlab
https://bugs.kde.org/show_bug.cgi?id=431275 --- Comment #1 from SoilpH96 --- Sorry accidentally submitted, please delete this. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 431275] New: matlab
https://bugs.kde.org/show_bug.cgi?id=431275 Bug ID: 431275 Summary: matlab Product: okular Version: 20.12.1 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: okular-de...@kde.org Reporter: filippo27...@gmail.com Target Milestone: --- SUMMARY Okular d STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 430538] Markdown files opened as plain text
https://bugs.kde.org/show_bug.cgi?id=430538 SoilpH96 changed: What|Removed |Added CC||filippo27...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 431178] New: Quick tiled windows can't be maximized
https://bugs.kde.org/show_bug.cgi?id=431178 Bug ID: 431178 Summary: Quick tiled windows can't be maximized Product: kwin Version: 5.20.4 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: filippo27...@gmail.com Target Milestone: --- SUMMARY Quick tiled Wayland windows can't be maximized, either by the window decoration button or by a keyboard shortcut. However, XWayland windows work as expected. STEPS TO REPRODUCE 1. Quick tile a Wayland native window. 2. Attempt to maximize it OBSERVED RESULT The window cannot be maximized. Attempting to do so appears to remove the window border, although it will be restored by retrying a second time. Detatching the window from the screen edge however will allow it to be maximized as normal. EXPECTED RESULT The window should be maximized normally, as observed when trying to reproduce the issue on an XWayland window. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.20.4 KDE Frameworks Version: 5.77.0 Qt Version: 5.15.2 Kernel Version: 5.10.4-arch2-1 OS Type: 64-bit -- You are receiving this mail because: You are watching all bug changes.
