[plasmashell] [Bug 486222] New: Unable to have Unity style panel layout in Plasma 6 (can't have maximum width panel on the top with another panel on the left)
https://bugs.kde.org/show_bug.cgi?id=486222 Bug ID: 486222 Summary: Unable to have Unity style panel layout in Plasma 6 (can't have maximum width panel on the top with another panel on the left) Classification: Plasma Product: plasmashell Version: 6.0.4 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Panel Assignee: plasma-b...@kde.org Reporter: pizzad...@linuxmail.org CC: niccolo.venera...@gmail.com Target Milestone: 1.0 Created attachment 168959 --> https://bugs.kde.org/attachment.cgi?id=168959=edit description of bug *** If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** SUMMARY In KDE Plasma 6, I am unable to have a maximized panel on the top, alongside a panel on the left. I can only have a maximized panel on the left, alongside a panel on the top. Is there any reason for this, or is this a bug? STEPS TO REPRODUCE 1. Add a panel on the left side of the screen and on the top of the screen 2. Try to make the top panel full width, with the left panel underneath the top panel 3. Notice you can't do that. With a panel on the left, it won't let me resize the top panel to be full width. OBSERVED RESULT See image for details. https://i.postimg.cc/PJMDT4Gc/plasma-6-panel-bug.png EXPECTED RESULT For it to work like in Plasma 5. SOFTWARE/OS VERSIONS Operating System: Fedora Linux 40 KDE Plasma Version: 6.0.4 KDE Frameworks Version: 6.1.0 Qt Version: 6.7.0 Graphics Platform: Wayland ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kactivitymanagerd] [Bug 397487] Cannot disable activity tracking and history not deleted
https://bugs.kde.org/show_bug.cgi?id=397487 p d changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|FIXED |--- --- Comment #13 from p d --- It still doesn't work. Now, the settings "Do not remember" in "Recent files" doesn't save, and when I close that section of the KDE settings, it resets to "For all applications". -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 456057] Transparent windows stuck in desktop
https://bugs.kde.org/show_bug.cgi?id=456057 p d changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED |RESOLVED --- Comment #8 from p d --- this no longer happens for me -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 464629] Panel icon size isn't an option in Plasma 5.26.90, making it impossible to resize kickoff icon
https://bugs.kde.org/show_bug.cgi?id=464629 p d changed: What|Removed |Added Ever confirmed|0 |1 Status|NEEDSINFO |REOPENED Resolution|FIXED |--- --- Comment #3 from p d --- reopened -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 464629] Panel icon size isn't an option in Plasma 5.26.90, making it impossible to resize kickoff icon
https://bugs.kde.org/show_bug.cgi?id=464629 --- Comment #2 from p d --- Created attachment 155549 --> https://bugs.kde.org/attachment.cgi?id=155549=edit panel icon size option missing https://i.imgur.com/OcODDAF.png ^ this image explains what I mean -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 464629] New: Panel icon size isn't an option in Plasma 5.26.90, making it impossible to resize kickoff icon
https://bugs.kde.org/show_bug.cgi?id=464629 Bug ID: 464629 Summary: Panel icon size isn't an option in Plasma 5.26.90, making it impossible to resize kickoff icon Classification: Plasma Product: plasmashell Version: 5.26.90 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Panel Assignee: plasma-b...@kde.org Reporter: pizzad...@linuxmail.org CC: niccolo.venera...@gmail.com Target Milestone: 1.0 SUMMARY Panel icon size isn't an option in Plasma 5.26.90, making it impossible to resize kickoff icon. Icon sizes for non-task manager icons (kickoff, show desktop) aren't configurable in Plasma 5.27 beta (5.26.90). They should be configurable like they usually are. STEPS TO REPRODUCE 1. Try to configure panel icon sizes 2. Notice there is no option 3. Kickoff icon size can't be configured anymore OBSERVED RESULT Panel icon size isn't an option in Plasma 5.26.90, making it impossible to resize kickoff icon EXPECTED RESULT For there to be an option to resize panel icon size like in previous plasma versions SOFTWARE/OS VERSIONS Fedora KDE 37 with Plasma 5.27 beta (5.26.90) ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 464628] New: Panel size ( width / height ) keeps getting reset after plasmashell restart in Plasma 5.27 beta
https://bugs.kde.org/show_bug.cgi?id=464628 Bug ID: 464628 Summary: Panel size ( width / height ) keeps getting reset after plasmashell restart in Plasma 5.27 beta Classification: Plasma Product: plasmashell Version: 5.26.90 Platform: Other OS: Other Status: REPORTED Severity: normal Priority: NOR Component: Panel Assignee: plasma-b...@kde.org Reporter: pizzad...@linuxmail.org CC: niccolo.venera...@gmail.com Target Milestone: 1.0 SUMMARY Panel size ( width / height ) keeps getting reset after plasmashell restart in Plasma 5.27 beta. For example, after setting vertical panel width to 60, it is reset to 54 after restarting plasma. STEPS TO REPRODUCE 1. Set plasma panel size to some random width / height 2. Restart plasmashell 3. It goes back to some width / height you didn't set. OBSERVED RESULT Panel sizes aren't sticking across plasmashell restarts EXPECTED RESULT For panel sizes to be remembered SOFTWARE/OS VERSIONS Fedora KDE 37 with Plasma 5.27 beta (5.26.90) ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 463862] Kickoff resets to default size after typing into the search box after restarting plasmashell in Wayland
https://bugs.kde.org/show_bug.cgi?id=463862 --- Comment #7 from p d --- not fixed in latest kde nightly -- You are receiving this mail because: You are watching all bug changes.
[Haruna] [Bug 463737] Haruna 0.10.0 crash on launch
https://bugs.kde.org/show_bug.cgi?id=463737 p d changed: What|Removed |Added Ever confirmed|0 |1 Resolution|FIXED |--- CC||pizzad...@linuxmail.org Status|NEEDSINFO |REOPENED --- Comment #15 from p d --- This problem happens when opening a video with "Maximum recent files" in Haruna set to "0". When it's set to 0, and I try to play a video, Haruna crashes. When it's set to 1 or above, it works fine. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 463862] New: Kickoff resets to default size after typing into the search box after restarting plasmashell in Wayland
https://bugs.kde.org/show_bug.cgi?id=463862 Bug ID: 463862 Summary: Kickoff resets to default size after typing into the search box after restarting plasmashell in Wayland Classification: Plasma Product: plasmashell Version: 5.26.4 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Application Launcher (Kickoff) Assignee: plasma-b...@kde.org Reporter: pizzad...@linuxmail.org CC: mikel5...@gmail.com, noaha...@gmail.com Target Milestone: 1.0 SUMMARY After latest KDE updates in Fedora, Kickoff resets to default size after typing into the search box after restarting plasmashell in Wayland. STEPS TO REPRODUCE 1. In KDE wayland, Resize kickoff (make it bigger) 2. Restart plasmashell (or make it crash somehow so it will automatically restart) 3. Type into kickoff 4. Notice kickoff resets to default size OBSERVED RESULT Kickoff resets to default size after typing inside it after a plasmashell crash or restart EXPECTED RESULT For kickoff to keep the size like it did previously SOFTWARE/OS VERSIONS Operating System: Fedora Linux 37 KDE Plasma Version: 5.26.4 KDE Frameworks Version: 5.101.0 Qt Version: 5.15.7 Kernel Version: 6.0.15-300.fc37.x86_64 (64-bit) Graphics Platform: Wayland Processors: 4 × Intel® Core™ i5-7300U CPU @ 2.60GHz Memory: 7.6 GiB of RAM Graphics Processor: Mesa Intel® HD Graphics 620 ADDITIONAL INFORMATION It only started happening a few updates ago. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 460563] kwin_wayland crashes in Plasma 5.26 with error "No provider of eglQueryDmaBufModifiersEXT found." when attempting to screen share or use OBS (due to an aurorae theme)
https://bugs.kde.org/show_bug.cgi?id=460563 p d changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|WAITINGFORINFO |--- --- Comment #4 from p d --- (In reply to Nicolas Fella from comment #3) > For crashes we need a backtrace > > Please see > https://community.kde.org/Guidelines_and_HOWTOs/Debugging/ > How_to_create_useful_crash_reports#Retrieving_a_backtrace_using_coredumpctl > and try to obtain a backtrace for kwin_wayland (gdb) bt #0 0x7f29b06d3ccc in __pthread_kill_implementation () from /lib64/libc.so.6 #1 0x7f29b0683aa6 in raise () from /lib64/libc.so.6 #2 0x7f29b066d7fc in abort () from /lib64/libc.so.6 #3 0x7f29b0b084d5 in QMessageLogger::fatal(char const*, ...) const () from /lib64/libQt5Core.so.5 #4 0x7f29b19d141b in QGuiApplicationPrivate::createPlatformIntegration() () from /lib64/libQt5Gui.so.5 #5 0x7f29b19d18c8 in QGuiApplicationPrivate::createEventDispatcher() () from /lib64/libQt5Gui.so.5 #6 0x7f29b0d05ab1 in QCoreApplicationPrivate::init() () from /lib64/libQt5Core.so.5 #7 0x7f29b19d3c83 in QGuiApplicationPrivate::init() () from /lib64/libQt5Gui.so.5 #8 0x7f29b260b31d in QApplicationPrivate::init() () from /lib64/libQt5Widgets.so.5 #9 0x55e92c3efd23 in main (argc=, argv=) at /usr/src/debug/xdg-desktop-portal-kde-5.26.0-1.fc37.x86_64/src/xdg-desktop-portal-kde.cpp:25 Hope this helps. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 460563] kwin_wayland crashes in Plasma 5.26 with error "No provider of eglQueryDmaBufModifiersEXT found." when attempting to screen share or use OBS (due to an aurorae theme)
https://bugs.kde.org/show_bug.cgi?id=460563 p d changed: What|Removed |Added Summary|kwin_wayland crashes in |kwin_wayland crashes in |Plasma 5.26 with error "No |Plasma 5.26 with error "No |provider of |provider of |eglQueryDmaBufModifiersEXT |eglQueryDmaBufModifiersEXT |found." when attempting to |found." when attempting to |screen share or use OBS on |screen share or use OBS |Intel HD Graphics under |(due to an aurorae theme) |Wayland | -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 460563] kwin_wayland crashes in Plasma 5.26 with error "No provider of eglQueryDmaBufModifiersEXT found." when attempting to screen share or use OBS on Intel HD Graphics under Wayland
https://bugs.kde.org/show_bug.cgi?id=460563 p d changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|FIXED |--- Ever confirmed|0 |1 --- Comment #2 from p d --- I found the cause. It's caused by an aurorae theme ( https://store.kde.org/p/1887668 ) and I don't think it's specific to just that theme. If I set that aurorae theme, and reboot, I get crashing when I try to screen share, in Wayland. If I set it back to Breeze, and reboot, screen sharing works normally. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 460553] Kwin crashes in Plasma 5.26 if xdg-desktop-portal-gnome is installed and running and you attempt to screen share or use OBS
https://bugs.kde.org/show_bug.cgi?id=460553 p d changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #2 from p d --- due to corrupt kwinrc -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 460563] kwin_wayland crashes in Plasma 5.26 with error "No provider of eglQueryDmaBufModifiersEXT found." when attempting to screen share or use OBS on Intel HD Graphics under Wayland
https://bugs.kde.org/show_bug.cgi?id=460563 p d changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #1 from p d --- due to corrupt kwinrc -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 460563] New: kwin_wayland crashes in Plasma 5.26 with error "No provider of eglQueryDmaBufModifiersEXT found." when attempting to screen share or use OBS on Intel HD Graphics under Wayland
https://bugs.kde.org/show_bug.cgi?id=460563 Bug ID: 460563 Summary: kwin_wayland crashes in Plasma 5.26 with error "No provider of eglQueryDmaBufModifiersEXT found." when attempting to screen share or use OBS on Intel HD Graphics under Wayland Classification: Plasma Product: kwin Version: 5.26.0 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: pizzad...@linuxmail.org Target Milestone: --- SUMMARY On Fedora 37 KDE with KDE 5.26 packages from the @kdesig/kde COPR repo, Kwin (Wayland) crashes when attempting to screen share / use OBS. This is with Intel HD 620 graphics. The error message in the log shows: Oct 16 19:09:08 fedora-t580 kwin_wayland_wrapper[4491]: No provider of eglQueryDmaBufModifiersEXT found. Requires one of: Oct 16 19:09:08 fedora-t580 kwin_wayland_wrapper[4491]: EGL_EXT_image_dma_buf_import_modifiers STEPS TO REPRODUCE 1. Be on Fedora 37 KDE with Intel HD 620 graphics (or maybe similar) 2. Use KDE 5.26 on Fedora 37 3. Try to screen share / record screen in OBS 4. Notice Kwin Wayland instantly crashes OBSERVED RESULT kwin_wayland crashes EXPECTED RESULT For it to not crash. It works fine in KDE 5.25.5 SOFTWARE/OS VERSIONS Operating System: Fedora Linux 37 KDE Plasma Version: 5.26.0 KDE Frameworks Version: 5.98.0 Qt Version: 5.15.6 Kernel Version: 5.19.15-301.fc37.x86_64 (64-bit) Graphics Platform: Wayland Processors: 4 × Intel® Core™ i5-7300U CPU @ 2.60GHz Memory: 7.6 GiB of RAM Graphics Processor: Mesa Intel® HD Graphics 620 Manufacturer: LENOVO System Version: ThinkPad T580 ADDITIONAL INFORMATION This is different from https://bugs.kde.org/show_bug.cgi?id=460553 , the crash appears to be for a different reason. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 460553] Kwin crashes in Plasma 5.26 if xdg-desktop-portal-gnome is installed and running and you attempt to screen share or use OBS
https://bugs.kde.org/show_bug.cgi?id=460553 --- Comment #1 from p d --- I upgraded to Fedora 37 KDE with KDE 5.26 from the kdesig copr and now it seems to crash for a different reason (when attempting to record screen in OBS on Wayland): Oct 16 19:09:08 fedora-t580 kwin_wayland_wrapper[4491]: No provider of eglQueryDmaBufModifiersEXT found. Requires one of: Oct 16 19:09:08 fedora-t580 kwin_wayland_wrapper[4491]: EGL_EXT_image_dma_buf_import_modifiers -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 460553] New: Kwin crashes in Plasma 5.26 if xdg-desktop-portal-gnome is installed and running and you attempt to screen share or use OBS
https://bugs.kde.org/show_bug.cgi?id=460553 Bug ID: 460553 Summary: Kwin crashes in Plasma 5.26 if xdg-desktop-portal-gnome is installed and running and you attempt to screen share or use OBS Classification: Plasma Product: kwin Version: 5.26.0 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: pizzad...@linuxmail.org Target Milestone: --- SUMMARY If xdg-desktop-portal-gnome is installed and running (and it is by default on Fedora 36): Since KDE 5.26, using OBS or screen sharing causes the KDE session to crash and restart (tested in Wayland), and removing xdg-desktop-portal-gnome fixes this. STEPS TO REPRODUCE 1. Be on Fedora 36 KDE with wayland session 2. Have xdg-desktop-portal-gnome installed and running (it is by default) 3. Try to screen share in telegram or screen record in OBS 4. Instant crash OBSERVED RESULT Kwin crash when sharing / recording screen EXPECTED RESULT There to be no crash. SOFTWARE/OS VERSIONS Operating System: Fedora Linux 36 KDE Plasma Version: 5.26.0 KDE Frameworks Version: 5.98.0 Qt Version: 5.15.6 Kernel Version: 5.19.15-201.fc36.x86_64 (64-bit) Graphics Platform: Wayland Processors: 4 × Intel® Core™ i5-7300U CPU @ 2.60GHz Memory: 7.6 GiB of RAM Graphics Processor: Mesa Intel® HD Graphics 620 -- You are receiving this mail because: You are watching all bug changes.
[kactivitymanagerd] [Bug 397487] Cannot disable activity tracking and history not deleted
https://bugs.kde.org/show_bug.cgi?id=397487 p d changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED CC||pizzad...@linuxmail.org --- Comment #2 from p d --- Workaround: Create a script in cron that does this: #!/bin/bash sqlite3 ~/.local/share/kactivitymanagerd/resources/database 'delete from ResourceInfo; pragma wal_checkpoint(TRUNCATE); vacuum;' sqlite3 ~/.local/share/kactivitymanagerd/resources/test-backup/database 'delete from ResourceInfo; pragma wal_checkpoint(TRUNCATE); vacuum;' sqlite3 ~/.local/share/kactivitymanagerd/resources/working-backup/database 'delete from ResourceInfo; pragma wal_checkpoint(TRUNCATE); vacuum;' Create a script in ~/.config/plasma-workspace/shutdown/ that does this: #!/bin/bash rm ~/.local/share/kactivitymanagerd/resources*/database-wal -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 456057] Transparent windows stuck in desktop
https://bugs.kde.org/show_bug.cgi?id=456057 p d changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 456057] Transparent windows stuck in desktop
https://bugs.kde.org/show_bug.cgi?id=456057 p d changed: What|Removed |Added CC||pizzad...@linuxmail.org --- Comment #7 from p d --- I have this issue with Fedora KDE on Wayland, with Intel graphics. It usually happens when I'm moving a window and it disappears as I'm moving it, and a transparent version of it gets stuck on the desktop. Operating System: Fedora Linux 36 KDE Plasma Version: 5.25.3 KDE Frameworks Version: 5.96.0 Qt Version: 5.15.3 Kernel Version: 5.18.11-200.fc36.x86_64 (64-bit) Graphics Platform: Wayland Processors: 4 × Intel® Core™ i5-7300U CPU @ 2.60GHz Memory: 7.5 GiB of RAM Graphics Processor: Mesa Intel® HD Graphics 620 System Version: ThinkPad T580 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 454861] New: Icons Only Task Manager icons are spaced too far apart on vertical panels in KDE Plasma 5.24.90 beta
https://bugs.kde.org/show_bug.cgi?id=454861 Bug ID: 454861 Summary: Icons Only Task Manager icons are spaced too far apart on vertical panels in KDE Plasma 5.24.90 beta Product: plasmashell Version: 5.24.90 Platform: Other OS: Other Status: REPORTED Severity: normal Priority: NOR Component: Task Manager and Icons-Only Task Manager Assignee: plasma-b...@kde.org Reporter: pizzad...@linuxmail.org Target Milestone: 1.0 SUMMARY On vertical panels, even with the "Spacing between icons" setting set to "Small", icons have too much spacing in between them as of Plasma 5.24.90 beta Here's a comparision: Plasma 5.24.x : https://i.imgur.com/MooNeIF.jpeg Plasma 5.24.90 : https://i.imgur.com/Am9ooIT.jpeg STEPS TO REPRODUCE 1. Upgrade to Plasma 5.24.90 2. Use icons only task manager in a vertical panel 3. Notice the spacing is too much compared to Plasma 5.24.x , even with it set to "Small" OBSERVED RESULT Spacing is too much EXPECTED RESULT Spacing to be the same as previous plasma release, or at least give an option to achieve previous spacing. SOFTWARE/OS VERSIONS Operating System: Fedora Linux 36 KDE Plasma Version: 5.24.90 KDE Frameworks Version: 5.94.0 Qt Version: 5.15.3 Kernel Version: 5.17.11-300.fc36.x86_64 (64-bit) Graphics Platform: Wayland Processors: 4 × Intel® Core™ i5-7300U CPU @ 2.60GHz Memory: 7.6 GiB of RAM Graphics Processor: Mesa Intel® HD Graphics 620 Manufacturer: LENOVO Product Name: 20L9S28200 System Version: ThinkPad T580 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 450943] Screensharing of fullscreen programs doesn't work under Wayland
https://bugs.kde.org/show_bug.cgi?id=450943 p d changed: What|Removed |Added CC||lordofthemara...@gmail.com --- Comment #6 from p d --- *** Bug 450116 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 450116] Unable to record fullscreen applications with pipewire
https://bugs.kde.org/show_bug.cgi?id=450116 p d changed: What|Removed |Added Status|REOPENED|RESOLVED Resolution|--- |DUPLICATE --- Comment #10 from p d --- Nevermind, I just upgraded to KDE 5.24.3 and it works now. I'm not sure why it worked earlier, and then stopped working. This seems to be fixed with the commit "Backends/drm: fix recording with direct scanout. Commit. Fixes bug #450943". *** This bug has been marked as a duplicate of bug 450943 *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 450116] Unable to record fullscreen applications with pipewire
https://bugs.kde.org/show_bug.cgi?id=450116 p d changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|UPSTREAM|--- --- Comment #9 from p d --- It seems this problem has came back. :/ -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 450116] Unable to record fullscreen applications with pipewire
https://bugs.kde.org/show_bug.cgi?id=450116 --- Comment #7 from p d --- Seems fixed in latest OBS (flatpak) and latest Pipewire (0.3.47) so must have not been a KDE issue. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 450116] Unable to record fullscreen applications with pipewire
https://bugs.kde.org/show_bug.cgi?id=450116 --- Comment #5 from p d --- (In reply to Nate Graham from comment #4) > Can you check with Plasma 5.24? This is on Plasma 5.24.1 on Fedora, using Wayland. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 450116] Unable to record fullscreen applications with pipewire
https://bugs.kde.org/show_bug.cgi?id=450116 p d changed: What|Removed |Added Status|REPORTED|CONFIRMED CC||pizzad...@linuxmail.org Ever confirmed|0 |1 --- Comment #3 from p d --- I have this issue also. I can't record any fullscreen game (like Xonotic) with OBS and pipewire in wayland. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 448162] Every time I screencast the screen, Plasma crashes in GLVertexBufferPrivate::interleaveArrays()
https://bugs.kde.org/show_bug.cgi?id=448162 p d changed: What|Removed |Added CC||pizzad...@linuxmail.org Ever confirmed|0 |1 Status|REPORTED|CONFIRMED --- Comment #5 from p d --- I have the same issue. Firefox doesn't make it crash, only Chromium does. Operating System: Fedora Linux 35 KDE Plasma Version: 5.23.5 KDE Frameworks Version: 5.90.0 Qt Version: 5.15.2 Kernel Version: 5.15.18-200.fc35.x86_64 (64-bit) Graphics Platform: Wayland Processors: 4 × Intel® Core™ i5-7300U CPU @ 2.60GHz Memory: 7.6 GiB of RAM Graphics Processor: Mesa Intel® HD Graphics 620 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 444962] Some wayland native games in KDE 5.23 open in corner of screen unless I force them to run in xwayland (and in 5.23.3 they open as an invisible window)
https://bugs.kde.org/show_bug.cgi?id=444962 --- Comment #16 from p d --- https://bugs.kde.org/show_bug.cgi?id=447556 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 447556] New: Some wayland native games in KDE 5.23.4 crash instantly on startup
https://bugs.kde.org/show_bug.cgi?id=447556 Bug ID: 447556 Summary: Some wayland native games in KDE 5.23.4 crash instantly on startup Product: kwin Version: 5.23.4 Platform: Other OS: Other Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: pizzad...@linuxmail.org Target Milestone: --- SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** This is a continuation of https://bugs.kde.org/show_bug.cgi?id=444962 , in KDE 5.23.4 using Intel HD Graphics 620 on Wayland, some wayland native games like Xonotic flatpak crash instantly on startup. Disabling the wayland socket via flatseal solves the issue. I ran the flatpak with --socket=wayland to reproduce the issue, because I already disabled the wayland socket to workaround the issue. The xonotic flatpak ships with wayland enabled. STEPS TO REPRODUCE 1. Be on Intel HD Graphics and use KDE 5.23.4 wayland session 2. Install Xonotic from flathub and make sure wayland support is enabled in flatseal 3. The game will crash instantly upon launch This happens with other wayland native games such as SuperTuxKart on flathub. The behavior was different in previous KDE versions. In KDE 5.23.3, they launched, but the windows were invisible. In KDE 5.23.2, they launched in the corner of the screen. OBSERVED RESULT Wayland native games (not using xwayland) crash instantly on startup EXPECTED RESULT For them to work. SOFTWARE/OS VERSIONS Operating System: Fedora Linux 35 KDE Plasma Version: 5.23.4 KDE Frameworks Version: 5.89.0 Qt Version: 5.15.2 Kernel Version: 5.15.11-200.fc35.x86_64 (64-bit) Graphics Platform: Wayland Processors: 4 × Intel® Core™ i5-7300U CPU @ 2.60GHz Memory: 7.6 GiB of RAM Graphics Processor: Mesa Intel® HD Graphics 620 ADDITIONAL INFORMATION xonotic shows this in the logs Linked against SDL version 2.0.16 Using SDL library version 2.0.16 GL_VENDOR: Intel GL_RENDERER: Mesa Intel(R) HD Graphics 620 (KBL GT2) GL_VERSION: 4.6 (Compatibility Profile) Mesa 21.3.1 (git-9da08702b0) vid.support.arb_multisample 1 vid.support.gl20shaders 1 NOTE: requested 1x AA, got 0x AA Video Mode: fullscreen 1920x1080x32x0.00hz xdg_surface@30: error -1: invalid window geometry size (0x0) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 444962] Some wayland native games in KDE 5.23 open in corner of screen unless I force them to run in xwayland (and in 5.23.3 they open as an invisible window)
https://bugs.kde.org/show_bug.cgi?id=444962 p d changed: What|Removed |Added Resolution|FIXED |--- Status|RESOLVED|REOPENED --- Comment #14 from p d --- This is not fixed, however, there is different behavior now. In Plasma 5.23.4 instead of opening an invisible window, they just crash instantly. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 442846] Plasma Wayland Freezes upon unlocking screen after leaving laptop with intel graphics idle for long time
https://bugs.kde.org/show_bug.cgi?id=442846 --- Comment #10 from p d --- Maybe that is the case, because in past few months I also set Firefox to run in Wayland and haven't experienced the crash since. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 444962] Some wayland native games in KDE 5.23 open in corner of screen unless I force them to run in xwayland (and in 5.23.3 they open as an invisible window)
https://bugs.kde.org/show_bug.cgi?id=444962 p d changed: What|Removed |Added Summary|Some wayland native games |Some wayland native games |in KDE 5.23 open in corner |in KDE 5.23 open in corner |of screen unless I force|of screen unless I force |them to run in xwayland |them to run in xwayland ||(and in 5.23.3 they open as ||an invisible window) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 444962] Some wayland native games in KDE 5.23 open in corner of screen unless I force them to run in xwayland
https://bugs.kde.org/show_bug.cgi?id=444962 --- Comment #2 from p d --- Here is a recording of the problem with the yamagi quake 2 flatpak with wayland socket enabled: https://youtu.be/dwFMap8-r1E With Xonotic, it trashes my game config so I have to restore from a backup after disabling wayland socket. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 444962] Some wayland native games in KDE 5.23 open in corner of screen unless I force them to run in xwayland
https://bugs.kde.org/show_bug.cgi?id=444962 --- Comment #1 from p d --- With KDE 5.23.3 instead of opening up in the corner, wayland only games are completely invisible. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 444962] New: Some wayland native games in KDE 5.23 open in corner of screen unless I force them to run in xwayland
https://bugs.kde.org/show_bug.cgi?id=444962 Bug ID: 444962 Summary: Some wayland native games in KDE 5.23 open in corner of screen unless I force them to run in xwayland Product: kwin Version: 5.23.2 Platform: Other OS: Other Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: pizzad...@linuxmail.org Target Milestone: --- SUMMARY This didn't happen until KDE 5.23. On Intel HD Graphics 620, in Fedora 35 KDE wayland session, when running some games (like Xonotic flatpak from flathub), the games are stuck at the bottom right of the screen like in this pic: https://i.imgur.com/hauYCm8.jpg Disabling the wayland socket via flatseal solves the issue. Disabling vsync in-game also solves the issue, but that makes the game choppy for some weird reason. In the picture I linked above, I ran the flatpak with --socket=wayland to reproduce the issue, because I already disabled the wayland socket to workaround the issue. The xonotic flatpak ships with wayland enabled. STEPS TO REPRODUCE 1. Be on Intel HD Graphics and use KDE 5.23 wayland session 2. Install Xonotic from flathub and make sure vsync in xonotic is enabled 3. The game will launch in the corner of screen OBSERVED RESULT Wayland native games launch in the corner of the screen EXPECTED RESULT Games to launch properly. SOFTWARE/OS VERSIONS Operating System: Fedora Linux 35 KDE Plasma Version: 5.23.2 KDE Frameworks Version: 5.87.0 Qt Version: 5.15.2 Kernel Version: 5.14.15-300.fc35.x86_64 (64-bit) Graphics Platform: Wayland Processors: 4 × Intel® Core™ i5-7300U CPU @ 2.60GHz Memory: 7.6 GiB of RAM Graphics Processor: Mesa Intel® HD Graphics 620 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 444583] New: KDE connect remote input no longer works in plasma 5.23.2 on wayland
https://bugs.kde.org/show_bug.cgi?id=444583 Bug ID: 444583 Summary: KDE connect remote input no longer works in plasma 5.23.2 on wayland Product: kdeconnect Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: common Assignee: albertv...@gmail.com Reporter: pizzad...@linuxmail.org Target Milestone: --- SUMMARY In Plasma 5.22.x on wayland, I could use my android phone with kde connect to move my mouse via the "remote input" plugin. Since upgrading to 5.23 (on Fedora 35 via zawertun's kde copr repo) this no longer works. My mouse is not moved when swiping my fingers across the screen in the android app (tested f-droid and google play build). Other parts of KDE connect work fine. STEPS TO REPRODUCE 1. Be on plasma 5.23.2 2. try kde connect remote input plugin 3. notice your mouse doesn't move at all OBSERVED RESULT remote input plugin doesn't work EXPECTED RESULT remote input plugin to work SOFTWARE/OS VERSIONS Operating System: Fedora Linux 35 KDE Plasma Version: 5.23.2 KDE Frameworks Version: 5.87.0 Qt Version: 5.15.2 Kernel Version: 5.14.14-300.fc35.x86_64 (64-bit) Graphics Platform: Wayland Processors: 4 × Intel® Core™ i5-7300U CPU @ 2.60GHz Memory: 7.6 GiB of RAM Graphics Processor: Mesa Intel® HD Graphics 620 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 411884] In wayland BorderlessMaximizedWindows can cause window to not receive input
https://bugs.kde.org/show_bug.cgi?id=411884 --- Comment #28 from p d --- (In reply to Méven Car from comment #26) > (In reply to Méven Car from comment #25) > > (In reply to p d from comment #23) > > > With "Hide Titles" kwin script > > > > That's this one I guess: > > https://store.kde.org/p/1354715/ > > https://github.com/bahamondev/hide-titles/blob/master/contents/code/main.js > > > > > the issue still happens some of the time. > > > > Do you know if that is when you click the maximize button or drap up a > > window, or double click on a window title bar ? > > That's a different bug this one concerned specifically the > "BorderlessMaximizedWindows" case. Then why was my bug ( https://bugs.kde.org/show_bug.cgi?id=440380 ) marked duplicate of this bug, if it's a different bug? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 411884] In wayland BorderlessMaximizedWindows can cause window to not receive input
https://bugs.kde.org/show_bug.cgi?id=411884 --- Comment #27 from p d --- (In reply to Méven Car from comment #25) > (In reply to p d from comment #23) > > With "Hide Titles" kwin script > > That's this one I guess: > https://store.kde.org/p/1354715/ > https://github.com/bahamondev/hide-titles/blob/master/contents/code/main.js > > > the issue still happens some of the time. > > Do you know if that is when you click the maximize button or drap up a > window, or double click on a window title bar ? It happens sometimes with any of those actions. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 411884] In wayland BorderlessMaximizedWindows can cause window to not receive input
https://bugs.kde.org/show_bug.cgi?id=411884 --- Comment #23 from p d --- With "Hide Titles" kwin script, the issue still happens some of the time. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 411884] In wayland BorderlessMaximizedWindows can cause window to not receive input
https://bugs.kde.org/show_bug.cgi?id=411884 --- Comment #22 from p d --- I have KDE 5.23.2, that is supposed to include the patch, is it not? Operating System: Fedora Linux 35 KDE Plasma Version: 5.23.2 KDE Frameworks Version: 5.87.0 Qt Version: 5.15.2 Kernel Version: 5.14.14-300.fc35.x86_64 (64-bit) Graphics Platform: Wayland Processors: 4 × Intel® Core™ i5-7300U CPU @ 2.60GHz Memory: 7.6 GiB of RAM Graphics Processor: Mesa Intel® HD Graphics 620 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 411884] In wayland BorderlessMaximizedWindows can cause window to not receive input
https://bugs.kde.org/show_bug.cgi?id=411884 p d changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|FIXED |--- --- Comment #20 from p d --- The bug is not fixed fully. I still have the issue half the time, and when I maximize by double clicking the address bar, I have the issue all the time. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 442846] Plasma Wayland Freezes upon unlocking screen after leaving laptop with intel graphics idle for long time
https://bugs.kde.org/show_bug.cgi?id=442846 --- Comment #4 from p d --- I haven't had this issue in a while. Sometimes I launch a separate wayland session via (Ctrl + Alt + F and log in as different user, startplasma-wayland), then switch back. I wonder if that has something to do with the issue. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 443975] Dragging favorites icons in the application launcher causes overlapping
https://bugs.kde.org/show_bug.cgi?id=443975 p d changed: What|Removed |Added CC||pizzad...@linuxmail.org --- Comment #14 from p d --- I have this issue also. Fedora 35 KDE Beta with Zawertun KDE Copr repo. Operating System: Fedora Linux 35 KDE Plasma Version: 5.23.1 KDE Frameworks Version: 5.87.0 Qt Version: 5.15.2 Kernel Version: 5.14.12-300.fc35.x86_64 (64-bit) Graphics Platform: Wayland Processors: 4 × Intel® Core™ i5-7300U CPU @ 2.60GHz Memory: 7.6 GiB of RAM Graphics Processor: Mesa Intel® HD Graphics 620 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 442846] Plasma Wayland Freezes upon unlocking screen after leaving laptop with intel graphics idle for long time
https://bugs.kde.org/show_bug.cgi?id=442846 --- Comment #2 from p d --- I will let you know if I can login via ssh next time I encounter the issue. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 442847] New: plasmashell spams system log with "kf.config.core: "\"NaturalSize_1\" - conversion of \"-1,-1\" to QSizeF failed" multiple times a minute
https://bugs.kde.org/show_bug.cgi?id=442847 Bug ID: 442847 Summary: plasmashell spams system log with "kf.config.core: "\"NaturalSize_1\" - conversion of \"-1,-1\" to QSizeF failed" multiple times a minute Product: plasmashell Version: 5.22.5 Platform: Other OS: Other Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: pizzad...@linuxmail.org CC: plasma-b...@kde.org Target Milestone: 1.0 SUMMARY In Fedora 34 KDE wayland I have an issue where plasmashell spams systemd-journald and /var/log/messages several times a minute with this error message: Sep 22 23:28:11 fedora-t580 plasmashell[82570]: kf.config.core: "\"NaturalSize_1\" - conversion of \"-1,-1\" to QSizeF failed" Sep 22 23:28:11 fedora-t580 plasmashell[82570]: kf.config.core: "\"NaturalSize_1\" - conversion of \"-1,-1\" to QSizeF failed" Sep 22 23:28:11 fedora-t580 plasmashell[82570]: kf.config.core: "\"NaturalSize_1\" - conversion of \"-1,-1\" to QSizeF failed" Sep 22 23:28:26 fedora-t580 plasmashell[82570]: kf.config.core: "\"NaturalSize_1\" - conversion of \"-1,-1\" to QSizeF failed" Sep 22 23:28:26 fedora-t580 plasmashell[82570]: kf.config.core: "\"NaturalSize_1\" - conversion of \"-1,-1\" to QSizeF failed" The only workaround I found is to disable debug logging of Qt applications entirely via adding this to /etc/environment QT_LOGGING_RULES='*=false' STEPS TO REPRODUCE 1. Look in /var/log/messages 2. See log spam OBSERVED RESULT The message is displayed multiple times a minute and I have to disable Qt logging. EXPECTED RESULT There to be no log spam. SOFTWARE/OS VERSIONS Operating System: Fedora 34 KDE Plasma Version: 5.22.5 KDE Frameworks Version: 5.85.0 Qt Version: 5.15.2 Kernel Version: 5.13.19-200.fc34.x86_64 (64-bit) Graphics Platform: Wayland Processors: 4 × Intel® Core™ i5-7300U CPU @ 2.60GHz Memory: 7.6 GiB of RAM Graphics Processor: Mesa Intel® HD Graphics 620 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 442846] New: Plasma Wayland Freezes upon unlocking screen after leaving laptop with intel graphics idle for long time
https://bugs.kde.org/show_bug.cgi?id=442846 Bug ID: 442846 Summary: Plasma Wayland Freezes upon unlocking screen after leaving laptop with intel graphics idle for long time Product: kwin Version: 5.22.5 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: pizzad...@linuxmail.org Target Milestone: --- SUMMARY I use Fedora 34 KDE on a Thinkpad T580 with an i5-7300U CPU and Intel HD Graphics 620. When I lock the screen, and leave the laptop for a long period of time (a few hours), there is a 50% chance when I come back, and after unlocking the lock screen, my whole system will be in a frozen state. This only happens on wayland. When the system is in a frozen state, I can't ctrl+alt+f[number] either to access a tty. There is no response from any key I press. If I'm lucky, and I spam a bunch of keys, the system will unfreeze. Most of the time I have to force poweroff though. The problem doesn't happen if I don't keep the system on the lockscreen for a long period of the time. The problem doesn't happen if I close the laptop lid and let it sleep instead of keeping it open. STEPS TO REPRODUCE 1. On wayland, Leave intel hd graphics laptop on lock screen for long perioid of time 2. Come back to computer and unlock the screen 3. Full system freeze OBSERVED RESULT System freeze upon unlock after idle for a few hours EXPECTED RESULT System not to freeze SOFTWARE/OS VERSIONS Operating System: Fedora 34 KDE Plasma Version: 5.22.5 KDE Frameworks Version: 5.85.0 Qt Version: 5.15.2 Kernel Version: 5.13.19-200.fc34.x86_64 (64-bit) Graphics Platform: Wayland Processors: 4 × Intel® Core™ i5-7300U CPU @ 2.60GHz Memory: 7.6 GiB of RAM Graphics Processor: Mesa Intel® HD Graphics 620 ADDITIONAL INFORMATION I use BTRFS. -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 441933] New: Yakuake crashes most of the time when I close the tab
https://bugs.kde.org/show_bug.cgi?id=441933 Bug ID: 441933 Summary: Yakuake crashes most of the time when I close the tab Product: yakuake Version: 21.08.0 Platform: Fedora RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: h...@kde.org Reporter: pizzad...@linuxmail.org Target Milestone: --- Application: yakuake (21.08.0) Qt Version: 5.15.2 Frameworks Version: 5.85.0 Operating System: Linux 5.13.13-200.fc34.x86_64 x86_64 Windowing System: Wayland Drkonqi Version: 5.22.5 Distribution: "Fedora release 34 (Thirty Four)" -- Information about the crash: - What I was doing when the application crashed: Upon closing the yakuake tab, most of the time, yakuake crashes. This is on Fedora 34 KDE Wayland. The crash can be reproduced every time. -- Backtrace: Application: Yakuake (yakuake), signal: Segmentation fault [KCrash Handler] #4 0x7f75b62c2d2b in QStackedLayout::widget(int) const () from /lib64/libQt5Widgets.so.5 #5 0x7f758caf1a1d in Konsole::TabbedViewContainer::viewSplitterAt(int) () from /lib64/libkonsoleprivate.so.21 #6 0x7f758caf48a6 in Konsole::TabbedViewContainer::currentTabViewCount() () from /lib64/libkonsoleprivate.so.21 #7 0x7f758ca9c849 in Konsole::ViewManager::sessionFinished() () from /lib64/libkonsoleprivate.so.21 #8 0x7f75b57fc3a9 in void doActivate(QObject*, int, void**) () from /lib64/libQt5Core.so.5 #9 0x7f75b57fc3a9 in void doActivate(QObject*, int, void**) () from /lib64/libQt5Core.so.5 #10 0x7f75b574fe73 in QProcess::finished(int, QProcess::ExitStatus) () from /lib64/libQt5Core.so.5 #11 0x7f75b5754433 in QProcessPrivate::_q_processDied() () from /lib64/libQt5Core.so.5 #12 0x7f75b5758102 in QProcessPrivate::waitForFinished(int) () from /lib64/libQt5Core.so.5 #13 0x7f758cb06b3a in Konsole::Session::closeInNormalWay() () from /lib64/libkonsoleprivate.so.21 #14 0x7f758cafd13a in Konsole::Session::close() () from /lib64/libkonsoleprivate.so.21 #15 0x7f75b57fc3a9 in void doActivate(QObject*, int, void**) () from /lib64/libQt5Core.so.5 #16 0x7f75b57f73e3 in QObject::destroyed(QObject*) () from /lib64/libQt5Core.so.5 #17 0x7f75b62da813 in QWidget::~QWidget() () from /lib64/libQt5Widgets.so.5 #18 0x7f758cad71dd in Konsole::TerminalDisplay::~TerminalDisplay() () from /lib64/libkonsoleprivate.so.21 #19 0x7f75b57f178a in QObjectPrivate::deleteChildren() () from /lib64/libQt5Core.so.5 #20 0x7f75b62da556 in QWidget::~QWidget() () from /lib64/libQt5Widgets.so.5 #21 0x7f758ca7b6f5 in Konsole::ViewSplitter::~ViewSplitter() () from /lib64/libkonsoleprivate.so.21 #22 0x7f75b57f178a in QObjectPrivate::deleteChildren() () from /lib64/libQt5Core.so.5 #23 0x7f75b62da556 in QWidget::~QWidget() () from /lib64/libQt5Widgets.so.5 #24 0x7f75b645788d in QStackedWidget::~QStackedWidget() () from /lib64/libQt5Widgets.so.5 #25 0x7f75b57f178a in QObjectPrivate::deleteChildren() () from /lib64/libQt5Core.so.5 #26 0x7f75b62da556 in QWidget::~QWidget() () from /lib64/libQt5Widgets.so.5 #27 0x7f758caf19dd in Konsole::TabbedViewContainer::~TabbedViewContainer() () from /lib64/libkonsoleprivate.so.21 #28 0x7f75b57f178a in QObjectPrivate::deleteChildren() () from /lib64/libQt5Core.so.5 #29 0x7f75b62da556 in QWidget::~QWidget() () from /lib64/libQt5Widgets.so.5 #30 0x55f0693d86c5 in Session::~Session() () #31 0x55f0693d880d in Session::~Session() () #32 0x7f75b57f2d31 in QObject::event(QEvent*) () from /lib64/libQt5Core.so.5 #33 0x7f75b629c443 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib64/libQt5Widgets.so.5 #34 0x7f75b57c8798 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib64/libQt5Core.so.5 #35 0x7f75b57cbd06 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /lib64/libQt5Core.so.5 #36 0x7f75b581a0d7 in postEventSourceDispatch(_GSource*, int (*)(void*), void*) () from /lib64/libQt5Core.so.5 #37 0x7f75b35154cf in g_main_context_dispatch () from /lib64/libglib-2.0.so.0 #38 0x7f75b35694f8 in g_main_context_iterate.constprop () from /lib64/libglib-2.0.so.0 #39 0x7f75b3512c03 in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #40 0x7f75b5819b78 in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #41 0x7f75b57c71a2 in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #42 0x7f75b57cf6e4 in QCoreApplication::exec() () from /lib64/libQt5Core.so.5 #43 0x55f0693ba136 in main () [Inferior 1 (process 42464) detached] Possible duplicates by query: bug 441586. Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[kolourpaint] [Bug 440388] New: Kolourpaint on KDE wayland shows cursor above paintbrush unless launched with QT_QPA_PLATFORM=xcb
https://bugs.kde.org/show_bug.cgi?id=440388 Bug ID: 440388 Summary: Kolourpaint on KDE wayland shows cursor above paintbrush unless launched with QT_QPA_PLATFORM=xcb Product: kolourpaint Version: 21.04.1 Platform: Other OS: Other Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kolourpaint-supp...@lists.sourceforge.net Reporter: pizzad...@linuxmail.org Target Milestone: --- SUMMARY Kolourpaint, when launched with wayland regularly, shows the desktop cursor above the paintbrush cursor, making painting awkward. This is in Fedora 34 KDE, wayland session. STEPS TO REPRODUCE 1. Launch Kolourpaint in KDE Plasma Wayland session 2. Notice desktop cursor overlaps paintbrush cursor 3. Launch with env QT_QPA_PLATFORM=xcb kolourpaint and the issue is gone OBSERVED RESULT Cursor overlaps paintbrush cursor in wayland session. EXPECTED RESULT Cursor to be only the paintbrush icon. SOFTWARE/OS VERSIONS Operating System: Fedora 34 KDE Plasma Version: 5.22.4 KDE Frameworks Version: 5.83.0 Qt Version: 5.15.2 Kernel Version: 5.13.5-200.fc34.x86_64 (64-bit) Graphics Platform: Wayland Processors: 4 × Intel® Core™ i5-7300U CPU @ 2.60GHz Memory: 7.6 GiB of RAM Graphics Processor: Mesa Intel® HD Graphics 620 ADDITIONAL INFORMATION kolourpaint version: kolourpaint-21.04.1-1.fc34.x86_64 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 440380] New: Maximized windows are temporarily unresponsive when hiding titlebar for maximized windows in wayland
https://bugs.kde.org/show_bug.cgi?id=440380 Bug ID: 440380 Summary: Maximized windows are temporarily unresponsive when hiding titlebar for maximized windows in wayland Product: kwin Version: 5.22.4 Platform: Other OS: Other Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: pizzad...@linuxmail.org Target Milestone: --- SUMMARY I using Fedora KDE with Wayland, stock repos. If I enable a kwin script that hides the titlebar for maximized windows, or I use the "Window Buttons" 3rd party plasmoid, and enable that setting inside it's options, when I first maximize a window (using a window's own maximize buttons), I can't click on anything in the program window. The contents of the window is unresponsive. If I minimize and maximize the window again, I can suddenly interact with the program window. A workaround on the top panel is to activate the "Windows Go Below" panel setting, but it's not ideal. This problem does not happen on X11. STEPS TO REPRODUCE 1. Use KDE Wayland and enable a kwin script that hides maximized windows' titlebar 2. Maximize the window with the window's titlebar button's (not any other maximize panel button) 3. Notice you can't click on anything inside the window until you minimize, maximize again. OBSERVED RESULT See above. EXPECTED RESULT For program windows to be responsive when such kwin script is activated and maximizing the window for the first time. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Operating System: Fedora 34 KDE Plasma Version: 5.22.4 KDE Frameworks Version: 5.83.0 Qt Version: 5.15.2 Kernel Version: 5.13.5-200.fc34.x86_64 (64-bit) Graphics Platform: Wayland Processors: 4 × Intel® Core™ i5-7300U CPU @ 2.60GHz Memory: 7.6 GiB of RAM Graphics Processor: Mesa Intel® HD Graphics 620 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 438458] New: Yakuake flashes blue when closing it in Plasma 5.22 in X11
https://bugs.kde.org/show_bug.cgi?id=438458 Bug ID: 438458 Summary: Yakuake flashes blue when closing it in Plasma 5.22 in X11 Product: yakuake Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: h...@kde.org Reporter: pizzad...@linuxmail.org Target Milestone: --- SUMMARY Yakuake flashes blue when closing it in Plasma 5.22 in X11. This doesn't happen in Wayland. Unchecking "Ask the window manager to perform the animation" in "Configure Yakuake" works around the issue. I have recorded a short video of the issue so you know what I'm talking about: https://www.youtube.com/watch?v=D3ykqKQrY1o STEPS TO REPRODUCE 1. Be on Plasma 5.22 X11 session 2. Make sure "Ask the window manager to perform the animation" is checked in "Configure Yakuake" 3. Close Yakuake OBSERVED RESULT Blue flash / flicker EXPECTED RESULT No seizure inducing blue flash SOFTWARE/OS VERSIONS Linux/KDE Plasma: Operating System: Fedora 34 KDE Frameworks Version: 5.82.0 Qt Version: 5.15.2 Kernel Version: 5.12.9-300.fc34.x86_64 (64-bit) Graphics Platform: X11 Processors: 4 × Intel® Core™ i5-7300U CPU @ 2.60GHz Memory: 7.6 GiB of RAM Graphics Processor: Mesa Intel® HD Graphics 620 ADDITIONAL INFORMATION I use the "zawertun/kde" copr repo for latest plasma. -- You are receiving this mail because: You are watching all bug changes.
[Plasma Vault] [Bug 433459] Plasma Vault doesn't work with cryfs 0.11.0 (git version)
https://bugs.kde.org/show_bug.cgi?id=433459 --- Comment #3 from p d --- I compiled the latest cryfs commit and can confirm it's fixed now. Thanks very much! -- You are receiving this mail because: You are watching all bug changes.
[Plasma Vault] [Bug 433459] New: Plasma Vault doesn't work with cryfs 0.11.0 (git version)
https://bugs.kde.org/show_bug.cgi?id=433459 Bug ID: 433459 Summary: Plasma Vault doesn't work with cryfs 0.11.0 (git version) Product: Plasma Vault Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: ivan.cu...@kde.org Reporter: pizzad...@linuxmail.org Target Milestone: --- SUMMARY I use Fedora 33 KDE and have cryfs installed via this copr: https://copr.fedorainfracloud.org/coprs/fcsm/cryfs/ because it isn't available in the standard Fedora repos. This copr repo provides cryfs 0.11.0-dev which is from git. Plasma Vault doesn't work with this git version. When attempting to decrypt the vault, it doesn't invoke the cryfs command at all. Another frontend called SiriKali works, however. https://github.com/mhogomchungu/sirikali STEPS TO REPRODUCE 1. Install latest unstable cryfs from git 2. Try to decrypt cryfs vault 3. It does nothing OBSERVED RESULT Cryfs isn't launched EXPECTED RESULT For the cryfs command to start decrypting the vault upon entering the passphrase SOFTWARE/OS VERSIONS Linux/KDE Plasma: (available in About System) Operating System: Fedora 33 KDE Plasma Version: 5.21.0 KDE Frameworks Version: 5.79.0 Qt Version: 5.15.2 Kernel Version: 5.10.17-200.fc33.x86_64 OS Type: 64-bit Graphics Platform: X11 ADDITIONAL INFORMATION Latest KDE from this copr, but is a problem on stock Fedora kde also https://copr.fedorainfracloud.org/coprs/zawertun/kde/ -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 423141] GTK2 theming broken after update to Plasma 5.19
https://bugs.kde.org/show_bug.cgi?id=423141 --- Comment #3 from p d --- The problem now exists on both computers after trying to change the theme as a test, but good news! I found a workaround. Add this to ~/.profile, ~/.bashrc, and if you use fish shell, ~/.config/fish/config.fish export GTK2_RC_FILES=/usr/share/themes/Breeze-Dark/gtk-2.0/gtkrc export GTK_DATA_PREFIX="" You can change Breeze-Dark to the theme you like. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 423141] GTK2 theming broken after update to Plasma 5.19
https://bugs.kde.org/show_bug.cgi?id=423141 p d changed: What|Removed |Added CC||pizzad...@linuxmail.org --- Comment #1 from p d --- I have this issue on one of my machines, Fedora 32 KDE with zawertun's copr for latest KDE. On my other machine, I don't have this issue. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 423141] GTK2 theming broken after update to Plasma 5.19
https://bugs.kde.org/show_bug.cgi?id=423141 --- Comment #2 from p d --- It should be worth noting that both machines (affected and unaffected) are the same distro and copr repo. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 421498] Desktop settings get nuked on every startup
https://bugs.kde.org/show_bug.cgi?id=421498 --- Comment #8 from p d --- To workaround this issue put this in ~/.config/autostart-scripts, after backing up ~/.config/plasma-org.kde.plasma.desktop-appletsrc to "~/.config/plasma-org.kde.plasma.desktop-appletsrc.g00d" #!/bin/sh sleep 25s cp ~/.config/plasma-org.kde.plasma.desktop-appletsrc.g00d ~/.config/plasma-org.kde.plasma.desktop-appletsrc killall plasmashell sleep 1s kstart5 plasmashell -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 421498] Desktop settings get nuked on every startup
https://bugs.kde.org/show_bug.cgi?id=421498 --- Comment #7 from p d --- I can workaround this issue by creating a script that copies a backup of the plasma-org.kde.plasma.desktop-appletsrc file back to the original on startup. I had this issue since 5.18 came out. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 421498] Desktop settings get nuked on every startup
https://bugs.kde.org/show_bug.cgi?id=421498 p d changed: What|Removed |Added CC||pizzad...@linuxmail.org --- Comment #6 from p d --- I have the same issue on Fedora 32. Operating System: Fedora 32 KDE Plasma Version: 5.18.5 KDE Frameworks Version: 5.70.0 Qt Version: 5.13.2 Kernel Version: 5.6.14-300.fc32.x86_64 OS Type: 64-bit Processors: 4 × Intel® Core™ i5-4300M CPU @ 2.60GHz Memory: 7.5 GiB of RAM plasma from this copr https://copr.fedorainfracloud.org/coprs/zawertun/kde/ -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 415762] Exiting the session in a Yakuake tab sometimes crash Yakuake
https://bugs.kde.org/show_bug.cgi?id=415762 --- Comment #6 from p d --- Created attachment 127910 --> https://bugs.kde.org/attachment.cgi?id=127910=edit New crash information added by DrKonqi yakuake (3.0.5+) using Qt 5.13.2 New crash with latest version of yakuake ( yakuake-20.04.0-1.fc32.x86_64 ) on Fedora 32 with zawertun's kde copr repo. - What I was doing when the application crashed: Closing a tab with the "X" button on the right side of yakuake. -- Backtrace (Reduced): #6 0x7f1aaa327442 in QList::removeAll(QAction* const&) () from /lib64/libQt5Widgets.so.5 #7 0x7f1aaa36229b in QWidget::removeAction(QAction*) () from /lib64/libQt5Widgets.so.5 #8 0x7f1aaaf50f79 in KActionCollection::removeAssociatedWidget(QWidget*) () from /lib64/libKF5XmlGui.so.5 #9 0x7f1aaaf8a34f in KXMLGUIClient::prepareXMLUnplug(QWidget*) () from /lib64/libKF5XmlGui.so.5 #10 0x7f1aaaf8dd4f in KXMLGUIFactory::removeClient(KXMLGUIClient*) () from /lib64/libKF5XmlGui.so.5 -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 415762] Exiting the session in a Yakuake tab sometimes crash Yakuake
https://bugs.kde.org/show_bug.cgi?id=415762 p d changed: What|Removed |Added CC||pizzad...@linuxmail.org -- You are receiving this mail because: You are watching all bug changes.
[elisa] [Bug 409921] New: Elisa can't find or open music in folders with # (number sign) in them
https://bugs.kde.org/show_bug.cgi?id=409921 Bug ID: 409921 Summary: Elisa can't find or open music in folders with # (number sign) in them Product: elisa Version: 0.4.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: matthieu_gall...@yahoo.fr Reporter: pizzad...@linuxmail.org Target Milestone: --- SUMMARY Elisa can't find or open music in folders with # (number sign) in them. I have an album called "Mustard Plug - Yellow #5". I had to rename it to "Mustard Plug - Yellow Number 5" in order for Elisa to recognize it. If I tried to go to it manually in the files section, it said it could not find "Mustard Plug - Yellow" STEPS TO REPRODUCE 1. Create folder in music directory called "Blah Blah #1" 2. Notice that Elisa can't navigate to it in files section SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora 30 KDE with mkyral/plasma-unstable copr repo KDE Plasma Version: 5.16.3 KDE Frameworks Version: 5.59.0 Qt Version: 5.12.4 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kmenuedit] [Bug 400015] KDE menu editor
https://bugs.kde.org/show_bug.cgi?id=400015 p d changed: What|Removed |Added CC||pizzad...@linuxmail.org Ever confirmed|0 |1 Status|REPORTED|CONFIRMED --- Comment #1 from p d --- I ran into this bug also, when testing out the Papirus Dark icon theme from the Papirus PPA for *buntu. I'm using Kubuntu 18.10 with the Kubuntu backports PPA, so that would be KDE Plasma 5.14.1. Breeze Dark does not cause the crash. I tried downgrading kmenuedit to the non-backports ppa version and I still had the issue. System info: Kernel: Linux 4.18.0-10-generic x86_64 Distro: Ubuntu 18.10 CPU:Intel(R) Core(TM) i5 CPU M 520 @ 2.40GHz 4 cores/threads 2400.00 MHz RAM:3.65 GiB GPU:Mesa DRI Intel(R) Ironlake Mobile OpenGL 2.1 Mesa 18.2.2 GLSL 1.20 Backtrace: Application: KDE Menu Editor (kmenuedit), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f87bd866840 (LWP 16251))] Thread 4 (Thread 0x7f87abcb5700 (LWP 16254)): #0 0x7f87c29dd2eb in futex_wait_cancelable (private=, expected=0, futex_word=0x55f3979ad4f8) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7f87c29dd2eb in __pthread_cond_wait_common (abstime=0x0, mutex=0x55f3979ad4a8, cond=0x55f3979ad4d0) at pthread_cond_wait.c:502 #2 0x7f87c29dd2eb in __pthread_cond_wait (cond=0x55f3979ad4d0, mutex=0x55f3979ad4a8) at pthread_cond_wait.c:655 #3 0x7f87b04a246b in () at /usr/lib/x86_64-linux-gnu/dri/i965_dri.so #4 0x7f87b04a21d7 in () at /usr/lib/x86_64-linux-gnu/dri/i965_dri.so #5 0x7f87c29d7164 in start_thread (arg=) at pthread_create.c:486 #6 0x7f87c5a37def in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 3 (Thread 0x7f87b24e4700 (LWP 16253)): #0 0x7f87c1681d6f in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f87c16842b3 in g_main_context_prepare () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f87c1684d7b in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f87c1684f6c in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f87c406215b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f87c400f16b in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f87c3e5e0b6 in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f87c4f7a545 in () at /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #8 0x7f87c3e67c87 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x7f87c29d7164 in start_thread (arg=) at pthread_create.c:486 #10 0x7f87c5a37def in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 2 (Thread 0x7f87bc107700 (LWP 16252)): #0 0x7f87c5a2b6d9 in __GI___poll (fds=0x7f87bc106c78, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f87c1148917 in () at /usr/lib/x86_64-linux-gnu/libxcb.so.1 #2 0x7f87c114a53a in xcb_wait_for_event () at /usr/lib/x86_64-linux-gnu/libxcb.so.1 #3 0x7f87bd07d159 in () at /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #4 0x7f87c3e67c87 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f87c29d7164 in start_thread (arg=) at pthread_create.c:486 #6 0x7f87c5a37def in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 1 (Thread 0x7f87bd866840 (LWP 16251)): [KCrash Handler] #6 0x7f87c3ed83de in QString::mid(int, int) const () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f87c541fcf9 in () at /usr/lib/x86_64-linux-gnu/libKF5IconThemes.so.5 #8 0x7f87c54235e1 in () at /usr/lib/x86_64-linux-gnu/libKF5IconThemes.so.5 #9 0x7f87c5421e3c in () at /usr/lib/x86_64-linux-gnu/libKF5IconThemes.so.5 #10 0x7f87c5423f87 in () at /usr/lib/x86_64-linux-gnu/libKF5IconThemes.so.5 #11 0x7f87c40101ab in QCoreApplicationPrivate::sendThroughObjectEventFilters(QObject*, QEvent*) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #12 0x7f87c49cf491 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #13 0x7f87c49d6ae0 in QApplication::notify(QObject*, QEvent*) () at /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #14 0x7f87c4010499 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #15 0x7f87c4a0a1e8 in QWidgetPrivate::show_helper() () at /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #16 0x7f87c4a0d37b in QWidget::setVisible(bool) () at /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #17 0x7f87c4bbaa6a in QDialog::setVisible(bool) () at /usr/lib/x86_64
