[kwin] [Bug 474839] Kwin crashes in KWin::BlurEffect::blurRegion() when moving tabs out of Firefox window and back
https://bugs.kde.org/show_bug.cgi?id=474839 Guilherme Silva changed: What|Removed |Added CC||oguilhe...@protonmail.com --- Comment #3 from Guilherme Silva --- Created attachment 169588 --> https://bugs.kde.org/attachment.cgi?id=169588=edit KWin 6.0.4 crash on X11 I think I just experienced this same crash, on Plasma 6.0.4 + X11 + NVIDIA. Full system info: Operating System: Arch Linux KDE Plasma Version: 6.0.4 KDE Frameworks Version: 6.2.0 Qt Version: 6.7.0 Kernel Version: 6.9.1-arch1-1 (64-bit) Graphics Platform: X11 Processors: 4 × Intel® Core™ i5-3570K CPU @ 3.40GHz Memory: 7,7 GiB of RAM Graphics Processor: NVIDIA GeForce GTX 660/PCIe/SSE2 I can't reproduce the crash anymore, however. I remember I just had Firefox opened, and then after I began dragging a random image from Nate's latest blog post, KWin restarted. I'm attaching the gdb backtrace of the crash, according to this guide: https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports#Generate_backtrace_from_core -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kidletime] [Bug 328987] Power saving should not trigger if joystick/controller/gamepad is in use
https://bugs.kde.org/show_bug.cgi?id=328987 Guilherme Silva changed: What|Removed |Added CC||oguilhe...@protonmail.com -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 471279] Dolphin crash when dragging files or folders across or to the path navigation bar
https://bugs.kde.org/show_bug.cgi?id=471279 Guilherme Silva changed: What|Removed |Added CC||oguilhe...@protonmail.com -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 482154] uninstalling plasma-discover results in MANY warnings: "kf.service.services: KApplicationTrader: mimeType "x-scheme-handler/appstream" not found"
https://bugs.kde.org/show_bug.cgi?id=482154 --- Comment #9 from Guilherme Silva --- As a workaround, I've manually disabled all warnings from kf.service.services by creating this file: ~/.config/QtProject/qtlogging.ini With this content: [rules] kf.service.services.warning=false -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 484223] New: "TypeError" warning whenever I launch System Setting's sound configuration
https://bugs.kde.org/show_bug.cgi?id=484223 Bug ID: 484223 Summary: "TypeError" warning whenever I launch System Setting's sound configuration Classification: Applications Product: systemsettings Version: 6.0.2 Platform: Arch Linux OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: kcm_pulseaudio Assignee: plasma-b...@kde.org Reporter: oguilhe...@protonmail.com CC: m...@ratijas.tk, now...@gmail.com Target Milestone: --- SUMMARY Whenever I open System Setting's sound configuration, the following warning message pops up in the system journal three times: qrc:/kcm/kcm_pulseaudio/DeviceListItem.qml:66: TypeError: Cannot read property 'description' of undefined STEPS TO REPRODUCE 1. Right-click on the "volume" icon in the system tray 2. Click on "Configure Audio Devices..." 3. Open journalctl -b OBSERVED RESULT On my machine, this warning pops up three times: qrc:/kcm/kcm_pulseaudio/DeviceListItem.qml:66: TypeError: Cannot read property 'description' of undefined EXPECTED RESULT No warnings. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 6.0.2 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 Kernel Version: 6.8.1-arch1-1 (64-bit) Graphics Platform: X11 Processors: 4 × Intel® Core™ i5-3570K CPU @ 3.40GHz Memory: 7,7 GiB of RAM Graphics Processor: NVIDIA GeForce GTX 660/PCIe/SSE2 ADDITIONAL INFORMATION These warning do not seem to affect the main functionality of the applet in any way. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 478549] Nerd fonts are not rendered on plasma 6 when using detached font
https://bugs.kde.org/show_bug.cgi?id=478549 --- Comment #7 from Guilherme Silva --- The change introduced to fix QTBUG-110502 has been reverted: https://codereview.qt-project.org/c/qt/qtbase/+/548651 If that change is actually responsible for this bug, then this should be fixed in the next minor Qt release (I think). -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 475468] Window and panel resizing is very laggy
https://bugs.kde.org/show_bug.cgi?id=475468 Guilherme Silva changed: What|Removed |Added CC||oguilhe...@protonmail.com -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 482154] uninstalling plasma-discover results in MANY warnings: "kf.service.services: KApplicationTrader: mimeType "x-scheme-handler/appstream" not found"
https://bugs.kde.org/show_bug.cgi?id=482154 --- Comment #7 from Guilherme Silva --- It'd be great to have those removed. I don't know exactly where they're coming from (I don't have Discover installed at all), but my system journal is getting constantly spammed with those: > $ journalctl -b -o cat --no-pager | grep 'mimeType > "x-scheme-handler/appstream" not found' | wc -l > 1246 > $ uptime > 15:00:34 up 10:41, 1 user, load average: 0,90, 0,91, 0,82 That's 1246 messages in only 10 hours of uptime. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 482154] uninstalling plasma-discover results in MANY warnings: "kf.service.services: KApplicationTrader: mimeType "x-scheme-handler/appstream" not found"
https://bugs.kde.org/show_bug.cgi?id=482154 Guilherme Silva changed: What|Removed |Added CC||oguilhe...@protonmail.com -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 478549] Nerd fonts are not rendered on plasma 6 when using detached font
https://bugs.kde.org/show_bug.cgi?id=478549 Guilherme Silva changed: What|Removed |Added CC||oguilhe...@protonmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 482908] Missing fallback icon for desktop-less MPRIS2 clients
https://bugs.kde.org/show_bug.cgi?id=482908
Guilherme Silva changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Latest Commit||https://invent.kde.org/plas
||ma/plasma-workspace/-/commi
||t/9d92011d6022b57058ef8b02b
||5384f42e3e3f687
Resolution|--- |FIXED
--- Comment #2 from Guilherme Silva ---
Git commit 9d92011d6022b57058ef8b02b5384f42e3e3f687 by Guilherme Silva.
Committed on 09/03/2024 at 05:30.
Pushed by fusionfuture into branch 'master'.
libkmpris: prevent an empty icon from being used
The previous logic would only use the fallback icon
("emblem-music-symbolic"), if the client had the "DesktopEntry"
property[1] set.
But since clients are allowed to omit that property completely
(mpd-mpris[2] does that), m_iconName would stay an empty string, and
clients would be left icon-less.
This change ensures that m_iconName is never an empty string.
[1]
https://specifications.freedesktop.org/mpris-spec/latest/Media_Player.html#Property:DesktopEntry
[2] https://github.com/natsukagami/mpd-mpris/
M +3-3libkmpris/playercontainer.cpp
M +1-1libkmpris/playercontainer.h
https://invent.kde.org/plasma/plasma-workspace/-/commit/9d92011d6022b57058ef8b02b5384f42e3e3f687
--
You are receiving this mail because:
You are watching all bug changes.
[plasmashell] [Bug 482908] New: Missing fallback icon for desktop-less MPRIS2 clients
https://bugs.kde.org/show_bug.cgi?id=482908 Bug ID: 482908 Summary: Missing fallback icon for desktop-less MPRIS2 clients Classification: Plasma Product: plasmashell Version: 6.0.1 Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Media Player Assignee: plasma-b...@kde.org Reporter: oguilhe...@protonmail.com CC: k...@privat.broulik.de Target Milestone: 1.0 Created attachment 166727 --> https://bugs.kde.org/attachment.cgi?id=166727=edit Missing icon in Music applet SUMMARY I use a daemon called mpd-mpris [1] to implement the MPRIS2 interface for Music Player Daemon (MPD). This daemon does not set the "DesktopEntry" option[2], because it doesn't really have one. This was fine back in Plasma 5, because a fallback icon would be used instead. However, since Plasma 6, I get no icon at all (see the attachment for a screenshot). My suspicion is that the issue lies in this block of code from libkmpris: https://invent.kde.org/plasma/plasma-workspace/-/blob/6e0343c873df504d20926a6e2afc146ea0e14938/libkmpris/playercontainer.cpp#L570-575 mpd-mpris does not seem to set the "DesktopEntry" option at all[3], and so that branch in libkmpris that handles the fallback icon case, is never reached. STEPS TO REPRODUCE 1. Have a working MPD server 2. Install mpd-mpris 3. Invoke mpd-mpris from the command line 4. Open the Music applet on Plasma 6 OBSERVED RESULT Notice the missing icon for the MPD client. EXPECTED RESULT A fallback icon should be be used. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 6.0.1 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 Kernel Version: 6.7.8-arch1-1 (64-bit) Graphics Platform: X11 Processors: 4 × Intel® Core™ i5-3570K CPU @ 3.40GHz Memory: 7,7 GiB of RAM Graphics Processor: NVIDIA GeForce GTX 660/PCIe/SSE2 ADDITIONAL INFORMATION N/A Refs: [1] https://github.com/natsukagami/mpd-mpris/ [2] https://specifications.freedesktop.org/mpris-spec/latest/Media_Player.html#Property:DesktopEntry [3] https://github.com/natsukagami/mpd-mpris/blob/4a10c25567adab6a67edf6ee43f3ff0128068dd9/root.go#L18-L26 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 482107] Open Terminal here fails to open Konsole
https://bugs.kde.org/show_bug.cgi?id=482107 Guilherme Silva changed: What|Removed |Added CC||oguilhe...@protonmail.com -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 482215] Konsole crash when trying to open terminal from Dolphin
https://bugs.kde.org/show_bug.cgi?id=482215 Guilherme Silva changed: What|Removed |Added CC||oguilhe...@protonmail.com -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 481952] On X11, panels are hidden after minimizing Dolphin window
https://bugs.kde.org/show_bug.cgi?id=481952 Guilherme Silva changed: What|Removed |Added CC||oguilhe...@protonmail.com -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 482579] On X11, if dolphin is minimized with panels on, after restore the panels are lost
https://bugs.kde.org/show_bug.cgi?id=482579 Guilherme Silva changed: What|Removed |Added CC||oguilhe...@protonmail.com -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 481354] Dolphin crashed after I deleted a file
https://bugs.kde.org/show_bug.cgi?id=481354 --- Comment #1 from Guilherme Silva --- Created attachment 165829 --> https://bugs.kde.org/attachment.cgi?id=165829=edit gdb backtrace -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 481354] New: Dolphin crashed after I deleted a file
https://bugs.kde.org/show_bug.cgi?id=481354 Bug ID: 481354 Summary: Dolphin crashed after I deleted a file Classification: Applications Product: dolphin Version: 23.08.4 Platform: Arch Linux OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: oguilhe...@protonmail.com CC: kfm-de...@kde.org Target Milestone: --- SUMMARY I'm not sure what caused the crash, and I can't consistently reproduce it. Here are some details right before the crash occurred: - I had 5 tabs opened in Dolphin - Some of these opened tabs, had folders that were deleted externally (i.e. I ran "rm -r" from a terminal window) - The file I deleted was considerably large (2.6 GB) STEPS TO REPRODUCE Unclear. OBSERVED RESULT Dolphin crashes. EXPECTED RESULT No crash. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.27.10 KDE Frameworks Version: 5.115.0 Qt Version: 5.15.12 Kernel Version: 6.7.4-arch1-1 (64-bit) Graphics Platform: X11 Processors: 4 × Intel® Core™ i5-3570K CPU @ 3.40GHz Memory: 7,7 GiB of RAM Graphics Processor: NVIDIA GeForce GTX 660/PCIe/SSE2 -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 391083] Allow user to 'press' keys that aren't on Android keyboard
https://bugs.kde.org/show_bug.cgi?id=391083 Guilherme Silva changed: What|Removed |Added CC||oguilhe...@protonmail.com -- You are receiving this mail because: You are watching all bug changes.
[kde-cli-tools] [Bug 477878] New: ktraderclient5 gets stuck and memory usage rapidly increases
https://bugs.kde.org/show_bug.cgi?id=477878 Bug ID: 477878 Summary: ktraderclient5 gets stuck and memory usage rapidly increases Classification: Plasma Product: kde-cli-tools Version: 5.27.9 Platform: Other OS: Other Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: aleix...@kde.org Reporter: oguilhe...@protonmail.com Target Milestone: --- Created attachment 163731 --> https://bugs.kde.org/attachment.cgi?id=163731=edit This is a gdb backtrace of the process while its memory was steadily increasing. I'm not sure if that's useful, but I hope it is! SUMMARY This is unfortunately not easily reproducible, but the times I was able to trigger this was upon a clean boot. The bug happens upon clicking on this clickable URL being displayed inside of a program called TwitchDropsMiner. STEPS TO REPRODUCE 1. Download this portable program that displays the clickable link: https://github.com/DevilXD/TwitchDropsMiner/releases/download/dev-build/Twitch.Drops.Miner.Linux.PyInstaller.zip 2. Extract the zip file and run the "TwitchDropsMiner" executable 3. Go to the "Help" tab 4. Under the "Useful links" section, click on the "See Twitch inventory" link OBSERVED RESULT Sometimes, after you click on that link a process named ktraderclient5 spawns and gets stuck using a lot of CPU and memory, indefinitely. EXPECTED RESULT Upon clicking the link I expect it to open on Firefox (my default web browser) SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.27.9 KDE Frameworks Version: 5.112.0 Qt Version: 5.15.11 Kernel Version: 6.6.3-arch1-1 (64-bit) Graphics Platform: X11 Processors: 4 × Intel® Core™ i5-3570K CPU @ 3.40GHz Memory: 7,7 GiB of RAM Graphics Processor: NVIDIA GeForce GTX 660/PCIe/SSE2 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 416048] Morphing Popups effect: glitch when the size of a tooltip is reduced
https://bugs.kde.org/show_bug.cgi?id=416048 Guilherme Silva changed: What|Removed |Added CC||oguilhe...@protonmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasma-browser-integration] [Bug 414928] Spotify Web media controls misbehaving
https://bugs.kde.org/show_bug.cgi?id=414928 --- Comment #3 from Guilherme Silva --- I know I'm a bit late (just a little over 3 years ), but I can still reproduce the problem on version 1.8.1 of the extension (currently running on Firefox). Here's the video (!!!LOUD VOLUME WARNING!!!): https://www.youtube.com/watch?v=tX8zOQxeTjQ In the video, I initially show how Spotify controls are supposed to behave (while Plasma Integration for Spotify Web is disabled): - I'm able to pause songs - The duration of the song in the seek bar is displayed accurately And after that, I enable Plasma Integration and reloaded the page. Upon playing the first song on the playlist, you can notice that the pause button is immediately replaced by a play button, so you can't actually pause songs because of this bug. Additionally, the duration of the song displayed in Spotify's seek bar is not updated properly. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 416671] When using two screens, any window in full screen mode on your secondary screen can go out of bonds
https://bugs.kde.org/show_bug.cgi?id=416671 Guilherme Silva changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #2 from Guilherme Silva --- I've used GNOME for the past 2 years and I just got back to KDE. I'm happy to report that I can't reproduce the problem anymore! I'm on Plasma 5.27.5 (X11 session) Thanks! -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 462615] Use KActionCollection::setDefaultShortcut(s) instead
https://bugs.kde.org/show_bug.cgi?id=462615 Guilherme Silva changed: What|Removed |Added CC||oguilhe...@protonmail.com -- You are receiving this mail because: You are watching all bug changes.
[ksplash] [Bug 422904] [NVIDIA][Wayland] ksplashqml crashes with SIGSEGV
https://bugs.kde.org/show_bug.cgi?id=422904 --- Comment #8 from Guilherme Silva --- This one is quite old, but I'm fairly certain that this crash was only happening on Wayland with the old (and now removed) EGLStreams backend, so feel free to close this one. :) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 391322] Meta key randomly stops opening Plasma launcher menu
https://bugs.kde.org/show_bug.cgi?id=391322 Guilherme Silva changed: What|Removed |Added CC|oguilhe...@protonmail.com | -- You are receiving this mail because: You are watching all bug changes.
[frameworks-solid] [Bug 423810] Device Notifier tries to auto-mount a NTFS partition from Hard Disk at login
https://bugs.kde.org/show_bug.cgi?id=423810 --- Comment #10 from Guilherme Silva --- I know this has been marked as duplicate, but I'm not sure about it. Pardon my ignorance, but why does the Device Notifier is trying to mount a hard disk in the first place? Because I've configured it to only mount removable devices. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 426952] [NVIDIA][Wayland] kwin_wayland uses 100% of the CPU all the time
https://bugs.kde.org/show_bug.cgi?id=426952 Guilherme Silva changed: What|Removed |Added Resolution|WAITINGFORINFO |NOT A BUG Status|NEEDSINFO |RESOLVED --- Comment #4 from Guilherme Silva --- Actually, never mind. I found out what the problem was. I had `KWIN_DRM_USE_EGL_STREAMS=1` set in my ~/.pam_environment, but after a systemd update, a PAM config file (more specifically, /etc/pam.d/common-session) got overwritten and removed the `user_readenv=1` option I had added there, which functionality is to set environment variables globally. Long story short: The software rasterizer was being used instead of EGLStreams! I'm so sorry for wasting your guys' time. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 426952] [NVIDIA][Wayland] kwin_wayland uses 100% of the CPU all the time
https://bugs.kde.org/show_bug.cgi?id=426952 --- Comment #3 from Guilherme Silva --- Created attachment 131928 --> https://bugs.kde.org/attachment.cgi?id=131928=edit perf.data.tar.xz Thanks for the instructions! I recorded for about 3 seconds, so I hope it helps. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 426952] [NVIDIA][Wayland] kwin_wayland uses 100% of the CPU all the time
https://bugs.kde.org/show_bug.cgi?id=426952 --- Comment #1 from Guilherme Silva --- Created attachment 131926 --> https://bugs.kde.org/attachment.cgi?id=131926=edit kwin_wayland CPU usage It took me ages to take this screenshot. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 426952] New: [NVIDIA][Wayland] kwin_wayland uses 100% of the CPU all the time
https://bugs.kde.org/show_bug.cgi?id=426952 Bug ID: 426952 Summary: [NVIDIA][Wayland] kwin_wayland uses 100% of the CPU all the time Product: kwin Version: 5.19.5 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: platform-wayland Assignee: kwin-bugs-n...@kde.org Reporter: oguilhe...@protonmail.com Target Milestone: --- Created attachment 131925 --> https://bugs.kde.org/attachment.cgi?id=131925=edit wayland-session.log SUMMARY I'm trying to run Plasma on a Wayland session using a NVIDIA GPU, but after I log in, I can barely move the mouse cursor around, due to the kwin_wayland process hogging the CPU. I have no idea how to debug this myself, but point me to the right direction and I'll gladly help! SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20200923 KDE Plasma Version: 5.19.5 KDE Frameworks Version: 5.74.0 Qt Version: 5.15.1 Kernel Version: 5.8.10-1-default OS Type: 64-bit Processors: 4 × Intel® Core™ i5-3570K CPU @ 3.40GHz Memory: 7,7 GiB of RAM Graphics Processor: GeForce GTX 660/PCIe/SSE2 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 423810] Device Notifier tries to auto-mount a NTFS partition from Hard Disk at login
https://bugs.kde.org/show_bug.cgi?id=423810 --- Comment #2 from Guilherme Silva --- Created attachment 129851 --> https://bugs.kde.org/attachment.cgi?id=129851=edit Device Notifier trying to mount NTFS partition from hard drive at login -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 423810] Device Notifier tries to auto-mount a NTFS partition from Hard Disk at login
https://bugs.kde.org/show_bug.cgi?id=423810 --- Comment #1 from Guilherme Silva --- Created attachment 129850 --> https://bugs.kde.org/attachment.cgi?id=129850=edit My settings for Device Notifier -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 423810] New: Device Notifier tries to auto-mount a NTFS partition from Hard Disk at login
https://bugs.kde.org/show_bug.cgi?id=423810 Bug ID: 423810 Summary: Device Notifier tries to auto-mount a NTFS partition from Hard Disk at login Product: plasmashell Version: 5.19.2 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Device Notifier Assignee: plasma-b...@kde.org Reporter: oguilhe...@protonmail.com Target Milestone: 1.0 SUMMARY I have configured Device Notifier to "automatically mount all removable media at login", but for some reason, it is still asking me to mount a NTFS partition from my hard disk, every time I login. The offending partition resides on /dev/sdb, which is a 1 TB hard disk: # fdisk -l /dev/sdb Disk /dev/sdb: 931,53 GiB, 1000204886016 bytes, 1953525168 sectors Disk model: ST1000DM003-1CH1 Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disklabel type: gpt Device StartEnd Sectors Size Type /dev/sdb1 208904 976976909 976768006 465,8G Microsoft basic data /dev/sdb2 976977920 1953523711 976545792 465,7G Linux LVM As you can see, there is actually two partitions in that disk, but Device Notifier only tries to mount the first one - I know because it prompts me for my root password every time I log in. SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20200630 KDE Plasma Version: 5.19.2 KDE Frameworks Version: 5.71.0 Qt Version: 5.15.0 Kernel Version: 5.7.5-1-default OS Type: 64-bit ADDITIONAL INFORMATION The time I was using Arch Linux I was also experiencing this, but I didn't actually report to you guys because I thought I was messing something up. But this openSUSE installation is fresh, so it wasn't actually me. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 414834] Plasma crashes on Wayland when I change global theme
https://bugs.kde.org/show_bug.cgi?id=414834 Guilherme Silva changed: What|Removed |Added CC||oguilhe...@protonmail.com --- Comment #7 from Guilherme Silva --- Created attachment 129325 --> https://bugs.kde.org/attachment.cgi?id=129325=edit full gdb backtrace of the crash Getting the same crash on Plasma 5.19 when I change the global theme on Wayland + NVIDIA. Operating System: openSUSE Tumbleweed 20200611 KDE Plasma Version: 5.19.0 KDE Frameworks Version: 5.70.0 Qt Version: 5.15.0 Kernel Version: 5.6.14-1-default OS Type: 64-bit Processors: 4 × Intel® Core™ i5-3570K CPU @ 3.40GHz Memory: 7,7 GiB of RAM Graphics Processor: GeForce GTX 660/PCIe/SSE2 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 422424] kwin_wayland crashes when I change global theme
https://bugs.kde.org/show_bug.cgi?id=422424 --- Comment #4 from Guilherme Silva --- Thanks, I'll post it there. -- You are receiving this mail because: You are watching all bug changes.
[ksplash] [Bug 422904] [NVIDIA][Wayland] ksplashqml crashes with SIGSEGV
https://bugs.kde.org/show_bug.cgi?id=422904 --- Comment #6 from Guilherme Silva --- Created attachment 129298 --> https://bugs.kde.org/attachment.cgi?id=129298=edit [17447] kactivitymanagerd - full gdb backtrace -- You are receiving this mail because: You are watching all bug changes.
[ksplash] [Bug 422904] [NVIDIA][Wayland] ksplashqml crashes with SIGSEGV
https://bugs.kde.org/show_bug.cgi?id=422904 --- Comment #5 from Guilherme Silva --- Created attachment 129297 --> https://bugs.kde.org/attachment.cgi?id=129297=edit [17339] ksplashqml - full gdb backtrace -- You are receiving this mail because: You are watching all bug changes.
[ksplash] [Bug 422904] [NVIDIA][Wayland] ksplashqml crashes with SIGSEGV
https://bugs.kde.org/show_bug.cgi?id=422904 --- Comment #4 from Guilherme Silva --- Created attachment 129296 --> https://bugs.kde.org/attachment.cgi?id=129296=edit [17326] Xwayland - full gdb backtrace -- You are receiving this mail because: You are watching all bug changes.
[ksplash] [Bug 422904] [NVIDIA][Wayland] ksplashqml crashes with SIGSEGV
https://bugs.kde.org/show_bug.cgi?id=422904 Guilherme Silva changed: What|Removed |Added Attachment #129294|0 |1 is obsolete|| --- Comment #3 from Guilherme Silva --- Created attachment 129295 --> https://bugs.kde.org/attachment.cgi?id=129295=edit [17209] kglobalaccel5 - full gdb backtrace -- You are receiving this mail because: You are watching all bug changes.
[ksplash] [Bug 422904] [NVIDIA][Wayland] ksplashqml crashes with SIGSEGV
https://bugs.kde.org/show_bug.cgi?id=422904 Guilherme Silva changed: What|Removed |Added Attachment #129293|0 |1 is obsolete|| --- Comment #2 from Guilherme Silva --- Created attachment 129294 --> https://bugs.kde.org/attachment.cgi?id=129294=edit [17326] kglobalaccel5 - full gdb backtrace -- You are receiving this mail because: You are watching all bug changes.
[ksplash] [Bug 422904] [NVIDIA][Wayland] ksplashqml crashes with SIGSEGV
https://bugs.kde.org/show_bug.cgi?id=422904 --- Comment #1 from Guilherme Silva --- Created attachment 129293 --> https://bugs.kde.org/attachment.cgi?id=129293=edit kglobalaccel5 - full gdb backtrace -- You are receiving this mail because: You are watching all bug changes.
[ksplash] [Bug 422904] New: [NVIDIA][Wayland] ksplashqml crashes with SIGSEGV
https://bugs.kde.org/show_bug.cgi?id=422904 Bug ID: 422904 Summary: [NVIDIA][Wayland] ksplashqml crashes with SIGSEGV Product: ksplash Version: 5.19.0 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: oguilhe...@protonmail.com Target Milestone: --- SUMMARY After I log in to a Plasma Wayland session on NVIDIA, _sometimes_ I'd get a dark screen, with only the mouse cursor being displayed. However, trying to double or right click does nothing, so I essentially end up with a broken Plasma session, with the only option being rebooting my computer. Unfortunately, though, I haven't found a consistent way to reproduce this yet. Additionally, a bunch of KDE components seem to fail after ksplashqml crashes (though I'm not experienced enough on debugging to precisely confirm the crash order of these compoenents). coredumpctl shows me this: $ coredumpctl list --since=today Sat 2020-06-13 03:49:31 -03 17209 1000 100 6 present /usr/bin/kglobalaccel5 Sat 2020-06-13 03:49:45 -03 17339 1000 100 11 present /usr/bin/ksplashqml Sat 2020-06-13 03:49:46 -03 17447 1000 100 6 present /usr/lib64/libexec/kactivitymanagerd Sat 2020-06-13 03:49:47 -03 17326 1000 100 6 present /usr/bin/Xwayland In my next e-mails, I'll be attaching full gdb backtraces (with symbols) for all these processes, starting from the lowest pid. SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20200611 KDE Plasma Version: 5.19.0 KDE Frameworks Version: 5.70.0 Qt Version: 5.15.0 Kernel Version: 5.6.14-1-default OS Type: 64-bit Processors: 4 × Intel® Core™ i5-3570K CPU @ 3.40GHz Memory: 7,7 GiB of RAM Graphics Processor: GeForce GTX 660/PCIe/SSE2 ADDITIONAL INFORMATION NVIDIA proprietary driver version 440.82 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 422022] Black Screen with moveable mouse in Plasma Wayland on any nVidia GPU
https://bugs.kde.org/show_bug.cgi?id=422022 Guilherme Silva changed: What|Removed |Added CC||oguilhe...@protonmail.com --- Comment #1 from Guilherme Silva --- Are you able to test again on Plasma 5.19.0 + Qt 5.15.0? I was having the same issue as you're having some time ago, but after the latest updates from Plasma and Qt, at least I got a somewhat "ok-ish" Wayland experience on NVIDIA. Well, let's put it this way: Now I get more than a mouse cursor on a black screen... :) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 422903] New: [NVIDIA][Wayland] The Task Manager widget has a much darker contrast when compared to a X11 session
https://bugs.kde.org/show_bug.cgi?id=422903 Bug ID: 422903 Summary: [NVIDIA][Wayland] The Task Manager widget has a much darker contrast when compared to a X11 session Product: plasmashell Version: 5.19.0 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Task Manager Assignee: h...@kde.org Reporter: oguilhe...@protonmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Created attachment 129290 --> https://bugs.kde.org/attachment.cgi?id=129290=edit Wayland session SUMMARY I'm not certain if there is an specific effect that is not being applied, but basically the Task Manager applet has a darker color (or contrast, translucency, I'm not sure) when I'm on a Wayland session. Also, to be honest, I'm not sure if that's the expected behavior, but I decided to report anyway. STEPS TO REPRODUCE 1. Have a NVIDIA GPU 2. Log in to a "Full Wayland" Plasma session 3. Notice the dark color contrast of Task Manager widget 4. Logout 5. Switch to a X11 Plasma session 6. Notice the much lighter color contrast on the Task Manager applet OBSERVED RESULT Darker color contrast on the Task Manager applet EXPECTED RESULT Color contrast to match in both Wayland and X11 SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20200611 KDE Plasma Version: 5.19.0 KDE Frameworks Version: 5.70.0 Qt Version: 5.15.0 Kernel Version: 5.6.14-1-default OS Type: 64-bit Processors: 4 × Intel® Core™ i5-3570K CPU @ 3.40GHz Memory: 7,7 GiB of RAM Graphics Processor: GeForce GTX 660/PCIe/SSE2 ADDITIONAL INFORMATION NVIDIA proprietary driver version 440.82 As far as I could tell, the colors are off only on Plasmoids, i.e. on Dolphin they match in both Wayland and X11 sessions. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 422903] [NVIDIA][Wayland] The Task Manager widget has a much darker contrast when compared to a X11 session
https://bugs.kde.org/show_bug.cgi?id=422903 --- Comment #1 from Guilherme Silva --- Created attachment 129291 --> https://bugs.kde.org/attachment.cgi?id=129291=edit X11 session -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 422424] kwin_wayland crashes when I change global theme
https://bugs.kde.org/show_bug.cgi?id=422424 --- Comment #2 from Guilherme Silva --- Hmm, now that I think about it, I think my issue might not exactly be related to yours... Once I select the theme and hit "Apply", my screen goes completely dark. Though I'm able to switch to a VT, I don't know how to end that Plasma session that is broken, so I just restart my computer instead. Also, according to coredumpctl, is plasmashell that crashes for me, not kwin_wayland: $ coredumpctl list --since=today Sat 2020-06-13 02:28:10 -036711 1000 100 6 present /usr/bin/plasmashell -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 422424] kwin_wayland crashes when I change global theme
https://bugs.kde.org/show_bug.cgi?id=422424 Guilherme Silva changed: What|Removed |Added CC||oguilhe...@protonmail.com --- Comment #1 from Guilherme Silva --- Created attachment 129289 --> https://bugs.kde.org/attachment.cgi?id=129289=edit gdb full backtrace I'm having the same issue and I can reproduce it consistently. Keep in mind that I'm running Plasma on Wayland using NVIDIA's proprietary graphics driver, version 440.82. Operating System: openSUSE Tumbleweed 20200611 KDE Plasma Version: 5.19.0 KDE Frameworks Version: 5.70.0 Qt Version: 5.15.0 Kernel Version: 5.6.14-1-default OS Type: 64-bit Processors: 4 × Intel® Core™ i5-3570K CPU @ 3.40GHz Memory: 7,7 GiB of RAM Graphics Processor: GeForce GTX 660/PCIe/SSE2 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 422901] New: There is a plasmashell crash message every time I log in
https://bugs.kde.org/show_bug.cgi?id=422901 Bug ID: 422901 Summary: There is a plasmashell crash message every time I log in Product: plasmashell Version: 5.19.0 Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: oguilhe...@protonmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.19.0) Qt Version: 5.15.0 Frameworks Version: 5.70.0 Operating System: Linux 5.6.14-1-default x86_64 Windowing system: Wayland Distribution: openSUSE Tumbleweed -- Information about the crash: - What I was doing when the application crashed: Whenever I log in to Plasma, there's an icon in the system tray saying plasmashell crashed, but I'm not sure if the crash happens during login or logout. Important: This crash message only happens when I choose the Wayland session. I'm using a NVIDIA GPU with the latest proprietary graphics driver installed, so I understand the Wayland support right now might not the best, but I'm hoping it can be improved. Thank you! The crash can be reproduced every time. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault [KCrash Handler] #4 QExplicitlySharedDataPointer::operator bool (this=0x18) at /usr/include/qt5/QtCore/qshareddata.h:176 #5 KConfigGroup::parent (this=this@entry=0x7ffd3f1eb240) at /usr/src/debug/kconfig-5.70.0-1.2.x86_64/src/core/kconfiggroup.cpp:545 #6 0x55663c0ae84d in PanelView::restore (this=0x55663cc02cb0) at /usr/src/debug/plasma5-workspace-5.19.0-1.1.x86_64/shell/panelview.cpp:576 #7 0x55663c0af1b5 in PanelView::containmentChanged (this=0x55663cc02cb0) at /usr/src/debug/plasma5-workspace-5.19.0-1.1.x86_64/shell/panelview.cpp:1179 #8 PanelView::qt_static_metacall (_o=0x55663cc02cb0, _c=, _id=, _a=0x7ffd3f1eb3b0) at /usr/src/debug/plasma5-workspace-5.19.0-1.1.x86_64/build/shell/plasmashell_autogen/include/moc_panelview.cpp:261 #9 0x7fb52a44f020 in doActivate (sender=0x55663cc02cb0, signal_index=43, argv=0x7ffd3f1eb3b0, argv@entry=0x0) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:395 #10 0x7fb52a448340 in QMetaObject::activate (sender=, m=m@entry=0x7fb52c61afc0 , local_signal_index=local_signal_index@entry=2, argv=argv@entry=0x0) at kernel/qobject.cpp:3946 #11 0x7fb52c5f4f23 in PlasmaQuick::ContainmentView::containmentChanged (this=) at /usr/src/debug/plasma-framework-5.70.0-2.2.x86_64/build/src/plasmaquick/KF5PlasmaQuick_autogen/include/moc_containmentview.cpp:267 #12 0x7fb52c5f61d1 in PlasmaQuick::ContainmentViewPrivate::setContainment (this=0x55663d381d70, cont=0x55663cb05da0) at /usr/src/debug/plasma-framework-5.70.0-2.2.x86_64/src/plasmaquick/containmentview.cpp:93 #13 0x7fb52c5f7849 in PlasmaQuick::ContainmentView::setContainment (this=this@entry=0x55663cc02cb0, cont=) at /usr/src/debug/plasma-framework-5.70.0-2.2.x86_64/src/plasmaquick/containmentview.cpp:256 #14 0x55663c0b3d50 in ShellCorona::createWaitingPanels (this=) at /usr/src/debug/plasma5-workspace-5.19.0-1.1.x86_64/shell/shellcorona.cpp:1406 #15 0x7fb52a44efe6 in QtPrivate::QSlotObjectBase::call (a=0x7ffd3f1eb760, r=0x55663c7b6530, this=0x55663c855900) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #16 doActivate (sender=0x55663c7b65e8, signal_index=3, argv=argv@entry=0x7ffd3f1eb760) at kernel/qobject.cpp:3886 #17 0x7fb52a448340 in QMetaObject::activate (sender=, m=m@entry=0x7fb52a6fac40 , local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7ffd3f1eb760) at kernel/qobject.cpp:3946 #18 0x7fb52a452efa in QTimer::timeout (this=, _t1=...) at .moc/moc_qtimer.cpp:205 #19 0x7fb52a44496f in QObject::event (this=0x55663c7b65e8, e=0x7ffd3f1eb8d0) at kernel/qobject.cpp:1291 #20 0x7fb52afc50cf in QApplicationPrivate::notify_helper (this=, receiver=0x55663c7b65e8, e=0x7ffd3f1eb8d0) at kernel/qapplication.cpp:3671 #21 0x7fb52a418b0a in QCoreApplication::notifyInternal2 (receiver=0x55663c7b65e8, event=0x7ffd3f1eb8d0) at ../../include/QtCore/5.15.0/QtCore/private/../../../../../src/corelib/thread/qthread_p.h:325 #22 0x7fb52a46f313 in QTimerInfoList::activateTimers (this=0x55663c78e960) at kernel/qtimerinfo_unix.cpp:643 #23 0x7fb52a46fbcc in timerSourceDispatch (source=) at kernel/qeventdispatcher_glib.cpp:183 #24 idleTimerSourceDispatch (source=) at kernel/qeventdispatcher_glib.cpp:230 #25 0x7fb5288a72c7 in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0 #26 0x7fb5288a7648 in ?? () from /usr/lib64/libglib-2.0.so.0 #27 0x7fb5288a76ff in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #28 0x7fb52a46ff4f in QEventDispatcherGlib::processEvents (this=0x55663c7df690, flags=...) at kernel/qeventdispatcher_glib.cpp:423
[plasmashell] [Bug 417534] Empty ~/.gtkrc-2.0 file is created every time I login
https://bugs.kde.org/show_bug.cgi?id=417534 --- Comment #7 from Guilherme Silva --- Created attachment 129154 --> https://bugs.kde.org/attachment.cgi?id=129154=edit Patch for kde-gtk-config 5.19.80 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 417534] Empty ~/.gtkrc-2.0 file is created every time I login
https://bugs.kde.org/show_bug.cgi?id=417534
--- Comment #6 from Guilherme Silva ---
Created attachment 129153
--> https://bugs.kde.org/attachment.cgi?id=129153=edit
Patch for kde-gtk-config 5.18.5
Actually, never mind my last e-mail. The real culprit is the kde-gtk-config
daemon.
Once I:
- Disable its service ("Plasma GTKd") in Plasma's Background Services manager
- Remove the empty ~/.gtkrc-2.0 file
- And, finally, re-login, the file isn't created anymore.
So, brand new steps to reproduce:
1. Open the Background Services manager:
$ kcmshell5 kcmkded
2. Search and disable "Plasma GTKd", hit OK.
3. Make sure there's no .gtkrc-2.0 file in your home folder.
4. Open the Background Services again, but now with GTK2_RC_FILES set:
$ env GTK2_RC_FILES=/tmp/gtkrc kcmshell5 kcmkded
5. Re-enable the "Plasma GTKd" service, hit Apply.
6. There should be an empty .gtkrc-2.0 in your home now:
$ file ~/.gtkrc-2.0
/home/gui/.gtkrc-2.0: empty
I've fixed it locally (without any heavy testing, however) by removing some
duplicated code and creating a method that will either respect GTK2_RC_FILES or
fallback to ~/.gtkrc-2.0, if GTK2_RC_FILES isn't set or if it's empty.
I'm attaching two patches (they accomplish the same): The first one I made for
kde-gtk-config v5.18.5 (the latest version on Arch), and the other one which I
just rebased against commit 380bff1f (v5.19.80).
KDE Devs: Feel free to use it (or not), modify it, whatever. I'm reluctant to
submit it for review, because I _really_ don't program in C++. So if did that
and you guys' asked for modifications, I'd be wasting your time.
If the patch is ready to merge, awesome! If it's not, then I'm sorry.
And thank you for making Plasma so awesome. :)
--
You are receiving this mail because:
You are watching all bug changes.
[plasmashell] [Bug 417534] Empty ~/.gtkrc-2.0 file is created every time I login
https://bugs.kde.org/show_bug.cgi?id=417534 --- Comment #5 from Guilherme Silva --- Sorry I took this long to respond. Yes, I can still reproduce this on Plasma 5.18.5. A quick search for ".gtkrc-2.0" on KDE's org on Github showed me this file (specifically, the writeGtk2Settings() method): https://github.com/KDE/plasma-workspace/blob/7f2ae10539f2167663aab713986e3f5e0528289f/gmenu-dbusmenu-proxy/menuproxy.cpp#L169 That method doesn't address the GTK2_RC_FILES variable, instead it hardcodes it to ~/.gtkrc-2.0. A bit down in the code, that method is called by writeGtk2Settings(), which I guess ends up creating a new (but empty) .gtkrc-2.0 in my home directory. Just a wild guess, though. I'm not a C++ programmer but I'll try fixing it locally, and I'll let you guys know if that's what's causing the problem. Thanks. -- You are receiving this mail because: You are watching all bug changes.
[flatpak-platform-plugin] [Bug 417441] GTK apps running with GTK_USE_PORTAL=1 ignore GTK theme settings
https://bugs.kde.org/show_bug.cgi?id=417441 Guilherme Silva changed: What|Removed |Added CC||oguilhe...@protonmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 417534] Empty ~/.gtkrc-2.0 file is created every time I login
https://bugs.kde.org/show_bug.cgi?id=417534 --- Comment #1 from Guilherme Silva --- Probably related to this? https://phabricator.kde.org/D26261 I skimmed through the code a bit and noticed the GTK2 config path is hardcoded to ~/.gtkrc-2.0, plus there's no mention of GTK2_RC_FILES. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 417534] New: Empty ~/.gtkrc-2.0 file is created every time I login
https://bugs.kde.org/show_bug.cgi?id=417534 Bug ID: 417534 Summary: Empty ~/.gtkrc-2.0 file is created every time I login Product: plasmashell Version: 5.18.0 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: oguilhe...@protonmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 SUMMARY I'm not sure if it's Plasma itself who's creating the file, but I'm pretty sure it started happening after I upgraded to 5.18. This could be related to the fact that I have my gtkrc config file pointing elsewhere, using the GTK2_RC_FILES environment variable. So perhaps that is confusing Plasma... Not sure why ~/.gtkrc-2.0 is created as an empty file, though. STEPS TO REPRODUCE 1. (Maybe) have GTK2_RC_FILES set to ~/.config/gtk-2.0/gtkrc 2. Delete the ~/.gtkrc-2.0 (if any) 3. Logout Plasma 4. Login OBSERVED RESULT An empty file named .gtkrc-2.0 will be created in your home directory EXPECTED RESULT No .gtkrc-2.0 in my home directory SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux KDE Plasma Version: 5.18.0 KDE Frameworks Version: 5.67.0 Qt Version: 5.14.1 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 416671] New: When using two screens, any window in full screen mode on your secondary screen can go out of bonds
https://bugs.kde.org/show_bug.cgi?id=416671 Bug ID: 416671 Summary: When using two screens, any window in full screen mode on your secondary screen can go out of bonds Product: kwin Version: 5.17.5 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: core Assignee: kwin-bugs-n...@kde.org Reporter: oguilhe...@protonmail.com Target Milestone: --- SUMMARY Sorry I couldn't word the title better, but basically here's the display setup I currently have: 1x Monitor @ 1920x1080 (left side) 1x TV @ 1360x768 (right side) So to reproduce this, I'm afraid having a secondary monitor is necessary. STEPS TO REPRODUCE 1. Open Plasma's Display Configuration tool: kcmshell5 kcm_kscreen 2. Enable your secondary screen, side-by-side in my case. Leave the tool open for now 3. Open a new Konsole window (Ctrl+Alt+T), drag it onto your secondary screen 4. Hit F11 to enter full screen mode in Konsole 5. Go back to the Display Configuration tool, disable your secondary screen now 6. The Konsole window, which was in full screen mode on your secondary screen, is now moved to your primary (and only) screen, so far so good 7. Now, hit F11 to leave full screen mode on Konsole OBSERVED RESULT Once you do that last step, the Konsole window will actually disappear and move back to your secondary screen. And even though this Konsole window still shows up in the Task Manager widget, once you try to activate the window, KWin will raise it on your disabled secondary screen again. So, since the window is now out of bonds, you can't use your mouse to drag it back onto your primary screen. EXPECTED RESULT Once you leave full screen mode, the window should stay in the first screen, instead of moving back to the disabled secondary screen. SOFTWARE/OS VERSIONS Linux: Arch Linux, kernel 5.4.13 KDE Plasma Version: 5.17.5 KDE Frameworks Version: 5.66.0 Qt Version: 5.14.0 ADDITIONAL INFORMATION I was also able to reproduce this with a Chromium tab in full screen mode. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 415770] Environment variable 'GTK2_RC_FILES' is ignored
https://bugs.kde.org/show_bug.cgi?id=415770 --- Comment #2 from Guilherme Silva --- That was fast! Thanks a bunch, guys! -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 415770] New: Environment variable 'GTK2_RC_FILES' is ignored
https://bugs.kde.org/show_bug.cgi?id=415770 Bug ID: 415770 Summary: Environment variable 'GTK2_RC_FILES' is ignored Product: systemsettings Version: 5.17.4 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_gtk Assignee: aleix...@gmail.com Reporter: oguilhe...@protonmail.com Target Milestone: --- SUMMARY The kcm_gtk system component currently ignores the GTK2_RC_FILES environment variable and hardcodes reading/writing to ~/.gtkrc-2.0. I personally have the GTK2_RC_FILES variable set to $XDG_CONFIG_HOME/gtk-2.0/gtkrc in order to avoid cluttering my home directory. STEPS TO REPRODUCE 1. Open the terminal. 2. Backup your current ~/.gtkrc-2.0: (Don't forget to restore it afterwards! :) > mv ~/.gtkrc-2.0 ~/.gtkrc-2.0.bak 3. Point GTK2_RC_FILES to your backup file: > export GTK2_RC_FILES=~/.gtkrc-2.0.bak 4. Launch Plasma's GTK config.: > kcmshell5 kde-gtk-config OBSERVED RESULT kde-gtk-config still tries to read from ~/.gtkrc-2.0 instead of ~/.gtkrc-2.0.bak. EXPECTED RESULT kde-gtk-config should respect the GTK2_RC_FILES variable when reading/writing to the GTK2 config file. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux KDE Plasma Version: 5.17.4 KDE Frameworks Version: 5.65.0 Qt Version: 5.14.0 -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 414034] Extra .desktop file present in okular snap
https://bugs.kde.org/show_bug.cgi?id=414034 Guilherme Silva changed: What|Removed |Added CC||oguilhe...@protonmail.com --- Comment #2 from Guilherme Silva --- FYI, this secondary desktop file appears in the official okular package on Arch Linux as well. The "main" desktop file of Okular is located here: /usr/share/applications/org.kde.okular.desktop And the one you mentioned, which is meant for the "/usr/bin/okularkirigami" binary, sits here: /usr/share/applications/org.kde.okular.kirigami.desktop Also worth mentioning that desktop file for Okular Kirigami _does not_ have a "Categories" section in it, so when you open the Application Launcher in Plasma, the Okular Kirigami program shows under the "Lost & Found" section instead of "Graphics". -- You are receiving this mail because: You are watching all bug changes.
[plasma-browser-integration] [Bug 414928] Spotify Web media controls misbehaving
https://bugs.kde.org/show_bug.cgi?id=414928 --- Comment #1 from Guilherme Silva --- I'm so sorry, I forgot to add the summary! I'm not sure if my explanation was clear enough too, ugh... Anyway, I'll try again: The Spotify media controls (located at the bottom of the page) misbehave when I play any song. Most specifically, the pause button is replaced by a play button, indicating that there's no song currently playing, plus sometimes interrupting playback after aforementioned song finishes playing. -- You are receiving this mail because: You are watching all bug changes.
[plasma-browser-integration] [Bug 414928] New: Spotify Web media controls misbehaving
https://bugs.kde.org/show_bug.cgi?id=414928 Bug ID: 414928 Summary: Spotify Web media controls misbehaving Product: plasma-browser-integration Version: unspecified Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Chrome Assignee: k...@privat.broulik.de Reporter: oguilhe...@protonmail.com Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. Install Plasma Integration on Chromium 2. Go to open.spotify.com and login 3. Choose any playlist 4. Click the on the play button (located on the left side of any song) OBSERVED RESULT Even though the song plays normally, notice that the pause button in Spotify media controls is immediately replaced by the play button. And that issue sometimes causes another one: Spotify won't play the next song in the playlist because it thinks the playback was actually paused. EXPECTED RESULT The pause button shouldn't be replaced by a play button, therefore playback shouldn't be interrupted after the song ends. Disabling media controls on open.spotify.com makes playback function correctly. SOFTWARE/OS VERSIONS Linux: 5.4.2 (kernel) KDE Plasma Version: 5.17.4 KDE Frameworks Version: 5.64.0 Qt Version: 5.13.2 ADDITIONAL INFORMATION I was able to reproduce this on a clean Chromium profile, with no extensions except Plasma Integration. I could not reproduce this on Firefox. Plus, on Firefox I couldn't find the option to disable media controls. The extension popup menu seems to load a blank page... If necessary, I can record a video of it. Just let me know. Thank you! -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 391322] Super (Meta) Key stops working
https://bugs.kde.org/show_bug.cgi?id=391322 Guilherme Silva changed: What|Removed |Added CC||oguilhe...@protonmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 353983] Turning off compositing breaks Plasma panel rendering
https://bugs.kde.org/show_bug.cgi?id=353983 Guilherme Silva changed: What|Removed |Added CC||guih@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 399234] New: Compositing breaks system tray functionality in programs running under Wine Staging
https://bugs.kde.org/show_bug.cgi?id=399234 Bug ID: 399234 Summary: Compositing breaks system tray functionality in programs running under Wine Staging Product: kwin Version: 5.13.5 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: compositing Assignee: kwin-bugs-n...@kde.org Reporter: guih@gmail.com Target Milestone: --- SUMMARY Any program running under Wine Staging that uses the system tray will not work properly when you right/left mouse click that program's icon. STEPS TO REPRODUCE 1. Enable KWin compositing; 2. Download this test program (SHA-1: 63ae606aee64259091e7f82436d4ecdf3a6e9047): https://www.nirsoft.net/utils/tflash210.zip 3. Run the .exe with Wine Staging; (vanilla Wine will _not_ work!) OBSERVED RESULT Interacting with the blue round icon that was added to the system tray does absolutely nothing, i.e. the context menu won't show up after you right click it. Left clicking is supposed to change the icon to a different one, but it doesn't. EXPECTED RESULT The context menu window should pop-up after you right click the program's icon in system tray and left clicking it should change the icon. SOFTWARE VERSIONS KDE Plasma Version: 5.13.5 KDE Frameworks Version: 5.50.0 Qt Version: 5.11.2 ADDITIONAL INFORMATION There's a silly workaround to this: 1. Disable compositing (Alt+Shift+F12); 2. Run the desired program with Wine Staging; 3. Enable compositing again (Alt+Shift+F12); 4. Right/left clicking the tray icon works as expected now. I've reported this to the Wine Staging team as well (relevant details here: https://bugs.winehq.org/show_bug.cgi?id=45899). In my tests on virtual machines using different desktop environments (MATE, Cinnamon, XFCE), KDE was the only one in which I was able to reproduce this bug. A Wine Staging developer then suggested me to report it to you guys. Thank you! -- You are receiving this mail because: You are watching all bug changes.
