[kwin] [Bug 475077] Show non-linear virtual desktop arrangements again
https://bugs.kde.org/show_bug.cgi?id=475077 Kiril Vladimirov changed: What|Removed |Added CC||ki...@vladimiroff.org -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 486286] Excessive use of wl-clipboard crashes plasmashell in Klipper::checkClipData() while trying to create a QR code
https://bugs.kde.org/show_bug.cgi?id=486286
--- Comment #5 from Kiril Vladimirov ---
(In reply to Nate Graham from comment #3)
> Any chance you could mention what you're using this script for?
Honestly, no idea. Over time I got this habit to use wl-copy and wl-paste when
something needs to be done over the span of a few commands (i.e. when i/o
redirection is not feasible), instead of writing to throwaway files like
/tmp/{a,b,c,...} or piping tens of commands.
The issue was not that my script failed, as it makes sense to have an upper
limit of the clipboard size, but that any other copy-paste operation, even via
the UI in any application whatsoever, starting crashing my plasma shell. Could
try to dig up the script in question, but it was NOT 100% reproducible for
sure, because I remember that I've spent some fair amount of time, trying to
find the tipping point of buffer size.
--
You are receiving this mail because:
You are watching all bug changes.
[kwin] [Bug 484931] Waking the screen up right as it enters sleep breaks the session
https://bugs.kde.org/show_bug.cgi?id=484931 --- Comment #3 from Kiril Vladimirov --- > Jun 25 13:22:51 laptop kscreenlocker_greet[112584]: pam_unix(kde:auth): > authentication failure; logname=kiril uid=1000 euid=1000 tty= ruser= rhost= > user=kiril Just to clarify here. I have the option "Delay before password required" set to 5 seconds. If I set it to "Require password immediately" the issue is not reproducible for me. Always thought that it just turns the screen off earlier than actually locking the session. Looks like it just tries to authenticate with PAM which fails and the potential failure is not handled internally? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 484931] Waking the screen up right as it enters sleep breaks the session
https://bugs.kde.org/show_bug.cgi?id=484931 --- Comment #2 from Kiril Vladimirov --- Created attachment 170953 --> https://bugs.kde.org/attachment.cgi?id=170953=edit laptop__plasma-kwin_wayland.log Just happened on my machine. Moved the mouse at about 13:22 and the screen went black. Recovered about 30 seconds later this time, but often it never does. Attaching logs from `journalctl --user-unit plasma-kwin_wayland` -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 484931] Waking the screen up right as it enters sleep breaks the session
https://bugs.kde.org/show_bug.cgi?id=484931 Kiril Vladimirov changed: What|Removed |Added CC||ki...@vladimiroff.org -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 488225] After waking from a sleep of a few hours, the desktop session shows a black screen with a cursor
https://bugs.kde.org/show_bug.cgi?id=488225 Kiril Vladimirov changed: What|Removed |Added CC||ki...@vladimiroff.org -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 486286] Excessive use of wl-clipboard crashes plasmashell
https://bugs.kde.org/show_bug.cgi?id=486286 --- Comment #1 from Kiril Vladimirov --- Created attachment 168993 --> https://bugs.kde.org/attachment.cgi?id=168993=edit New crash information added by DrKonqi DrKonqi auto-attaching complete backtrace. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 486286] New: Excessive use of wl-clipboard crashes plasmashell
https://bugs.kde.org/show_bug.cgi?id=486286 Bug ID: 486286 Summary: Excessive use of wl-clipboard crashes plasmashell Classification: Plasma Product: plasmashell Version: 6.0.4 Platform: Fedora RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: generic-crash Assignee: plasma-b...@kde.org Reporter: ki...@vladimiroff.org Target Milestone: 1.0 Application: plasmashell (6.0.4) Qt Version: 6.7.0 Frameworks Version: 6.1.0 Operating System: Linux 6.8.7-300.fc40.x86_64 x86_64 Windowing System: Wayland Distribution: "Fedora release 40 (Forty)" DrKonqi: 6.0.4 [CoredumpBackend] -- Information about the crash: Created a script that uses wl-copy and wl-paste a lot (i.e. a tens of times per second) by sending and receiving a lot of data (about ~100K). That script was running fine for a few seconds and then plasmashell started crashing. Until the clipboard got cleared, the crash was reproducible on every single copy->paste operation. I'm still not able to create a 100% reproducible case, but posting this in order not to lose the traceback. The crash can be reproduced sometimes. -- Backtrace (Reduced): #5 0x7f5b095e3907 in QMimeData::hasText (this=this@entry=0x563cc0d96d20) at /usr/src/debug/qt6-qtbase-6.7.0-3.fc40.x86_64/src/corelib/kernel/qmimedata.cpp:408 #6 0x7f5aba1a98ac in Klipper::checkClipData (this=0x7f5a1401be80, selectionMode=) at /usr/src/debug/plasma-workspace-6.0.4-1.fc40.x86_64/klipper/klipper.cpp:785 #7 0x7f5b095fa3f4 in QtPrivate::QSlotObjectBase::call (this=0x563cc0d0e2f0, r=, a=0x7ffc279288e0) at /usr/src/debug/qt6-qtbase-6.7.0-3.fc40.x86_64/src/corelib/kernel/qobjectdefs_impl.h:469 #8 doActivate (sender=0x563cc0d0d390, signal_index=3, argv=0x7ffc279288e0) at /usr/src/debug/qt6-qtbase-6.7.0-3.fc40.x86_64/src/corelib/kernel/qobject.cpp:4078 [...] #10 0x7f5b08d8f0b0 in KSystemClipboard::changed (this=, _t1=) at /usr/src/debug/kf6-kguiaddons-6.1.0-2.fc40.x86_64/redhat-linux-build/src/KF6GuiAddons_autogen/include/moc_ksystemclipboard.cpp:142 Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[Marknote] [Bug 485882] [Feature Request] Towards replacing Obsidian Notes
https://bugs.kde.org/show_bug.cgi?id=485882 Kiril Vladimirov changed: What|Removed |Added CC||ki...@vladimiroff.org --- Comment #1 from Kiril Vladimirov --- (In reply to Kakadu.hafanana from comment #0) > 1) Git support: the notes should be easy accesable on disk, and it should be > a command 'commit all & push' This one is already done. Notes are stored as regular .md files on the disk, just like obsidian does. You don't have control over _where_, though. They're located in "/Notes/" (e.g. /home/username/Documents/Notes/Notebook1). -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 411579] GPU accelerated terminal
https://bugs.kde.org/show_bug.cgi?id=411579 Kiril Vladimirov changed: What|Removed |Added CC||ki...@vladimiroff.org -- You are receiving this mail because: You are watching all bug changes.
[Plasma Vault] [Bug 386200] Import Vault
https://bugs.kde.org/show_bug.cgi?id=386200 Kiril Vladimirov changed: What|Removed |Added CC||ki...@vladimiroff.org -- You are receiving this mail because: You are watching all bug changes.
[plasma-pk-updates] [Bug 473548] plasma-pk-updates applet doesn't load under Fedora 37 KDE desktop
https://bugs.kde.org/show_bug.cgi?id=473548 Kiril Vladimirov changed: What|Removed |Added CC|ki...@vladimiroff.org | -- You are receiving this mail because: You are watching all bug changes.
[frameworks-solid] [Bug 473642] Solid binary incompatibility breaks plasma-pk-updates, requiring a rebuild
https://bugs.kde.org/show_bug.cgi?id=473642 Kiril Vladimirov changed: What|Removed |Added CC||ki...@vladimiroff.org -- You are receiving this mail because: You are watching all bug changes.
[plasma-pk-updates] [Bug 473548] plasma-pk-updates applet doesn't load under Fedora 37 KDE desktop
https://bugs.kde.org/show_bug.cgi?id=473548 Kiril Vladimirov changed: What|Removed |Added CC||ki...@vladimiroff.org -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 438721] Crashes when the phone trys to connect
https://bugs.kde.org/show_bug.cgi?id=438721 --- Comment #14 from Kiril Vladimirov --- Created attachment 161094 --> https://bugs.kde.org/attachment.cgi?id=161094=edit New crash information added by DrKonqi kdeconnectd (23.04.3) using Qt 5.15.10 Happens to me on almost every single boot. Regardless of how many times I try to restart the kdeconnect deamon, the issue persists. Sometimes a reboot fixes it. -- Backtrace (Reduced): #4 0x7f328a180fa4 in Device::reloadPlugins() () at /usr/lib/libkdeconnectcore.so.23 #5 0x7f328a182040 in Device::addLink(NetworkPacket const&, DeviceLink*) () at /usr/lib/libkdeconnectcore.so.23 #6 0x7f328a17b333 in Daemon::onNewDeviceLink(NetworkPacket const&, DeviceLink*) () at /usr/lib/libkdeconnectcore.so.23 [...] #8 0x7f328a15b739 in LinkProvider::onConnectionReceived(NetworkPacket const&, DeviceLink*) () at /usr/lib/libkdeconnectcore.so.23 #9 0x7f328a16779f in LanLinkProvider::encrypted() () at /usr/lib/libkdeconnectcore.so.23 -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 438721] Crashes when the phone trys to connect
https://bugs.kde.org/show_bug.cgi?id=438721 Kiril Vladimirov changed: What|Removed |Added CC||ki...@vladimiroff.org -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 450471] Audio output not changed to HDMI automatically when plugin to TV
https://bugs.kde.org/show_bug.cgi?id=450471 Kiril Vladimirov changed: What|Removed |Added CC||ki...@vladimiroff.org --- Comment #3 from Kiril Vladimirov --- Does it make sense to re-open this or should I file a new one? I have the same problem with Plasma 5.27.3 (Wayland) and pipewire on a ThinkPad T490. What I would expect is for audio to automatically switch to "Digital Stereo (HDMI) Output + Analog Stereo Input" as soon as the laptop is connected to another device via HDMI (or usb-c dock in that matter) and switch back to "Analog Stereo Duplex", once disconnected. Right now it never changes automatically. It's especially annoying after disconnect, as the audio device completely disappears and any application that tries to play sound is stuck, until I manually go to "Configure Audio Devices" and change the empty profile to "Analog Stereo Duplex". -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 455317] Grid shows windows on wrong desktop on multi-screen setup
https://bugs.kde.org/show_bug.cgi?id=455317 --- Comment #2 from Kiril Vladimirov --- Yep, totally a config left-over from 5.24 as it turned out. Just recently noticed that there was no value chosen in the 'Desktop Grid' effect settings under 'Windows Layout'. As soon as I have chose anything, the effect now behaves properly with both a single and multiple monitors. Not sure if this should be closed as resolved, so I am leaving the bug "CONFIRMED" as it is. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 455317] Grid shows windows on wrong desktop on multi-screen setup
https://bugs.kde.org/show_bug.cgi?id=455317 Kiril Vladimirov changed: What|Removed |Added Version|5.25.1 |5.25.2 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 455317] Grid shows windows on wrong desktop on multi-screen setup
https://bugs.kde.org/show_bug.cgi?id=455317 Kiril Vladimirov changed: What|Removed |Added Version|5.25.0 |5.25.1 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 455317] Grid shows windows on wrong desktop on multi-screen setup
https://bugs.kde.org/show_bug.cgi?id=455317 --- Comment #1 from Kiril Vladimirov --- Just rebooted my machine, without having a second screen attached, and I can still reproduce it. Pretty sure this doesn't happen to everybody as it makes the grid effect pretty much useless. Could there be config left-overs from the previous effect implementation which cause this? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 455237] Windows from another desktop are being rendered on top of current one
https://bugs.kde.org/show_bug.cgi?id=455237 Kiril Vladimirov changed: What|Removed |Added Summary|Windows from another|Windows from another |desktop is being rendered |desktop are being rendered |on top of current one |on top of current one -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 455317] New: Grid shows windows on wrong desktop on multi-screen setup
https://bugs.kde.org/show_bug.cgi?id=455317 Bug ID: 455317 Summary: Grid shows windows on wrong desktop on multi-screen setup Product: kwin Version: 5.25.0 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: effects-desktop-grid Assignee: kwin-bugs-n...@kde.org Reporter: ki...@vladimiroff.org Target Milestone: --- SUMMARY The behavior is highly inconsistent and seems to depend on the active desktop while activating the grid effect. Windows always seem to appear on the correct screen but are often on the wrong desktop or completely missing (probably just drawn underneath another window). Here's a video recording that might make the issue easier to understand: https://i.imgur.com/ITw6TQi.mp4 STEPS TO REPRODUCE 1. Attach at least two screens and create a few desktops 2. Place windows on several (if not all) desktops and screens 3. Invoke the grid effect 4. Move to a different desktop and repeat step 3 OBSERVED RESULT Some windows are missing or shown on the wrong desktop, depending on where the effect has been activated from. EXPECTED RESULT Windows should appear consistently on their actual desktop. SOFTWARE/OS VERSIONS Linux: 5.17.13 KDE Plasma Version: 5.25.0 KDE Frameworks Version: 5.94.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION No kwin scripts or windows rules are enabled and this happens under Wayland. Haven't tested on X11 at all. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 455268] Can't drag only a single window from one virtual desktop to another
https://bugs.kde.org/show_bug.cgi?id=455268 Kiril Vladimirov changed: What|Removed |Added CC||ki...@vladimiroff.org -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 455280] While arranging a single window, all windows in the same workspace move along together.
https://bugs.kde.org/show_bug.cgi?id=455280 Kiril Vladimirov changed: What|Removed |Added CC||ki...@vladimiroff.org -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 455237] Windows from another desktop is being rendered on top of current one
https://bugs.kde.org/show_bug.cgi?id=455237 --- Comment #3 from Kiril Vladimirov --- > Do you have any rules set on this particular window? Totally forgot about it. I have a window rule to always open Firefox on desktop 1. Deleting it fixed the issue. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 455237] New: Windows from another desktop is being rendered on top of current one
https://bugs.kde.org/show_bug.cgi?id=455237 Bug ID: 455237 Summary: Windows from another desktop is being rendered on top of current one Product: kwin Version: 5.25.0 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: ki...@vladimiroff.org Target Milestone: --- SUMMARY After upgrading to 5.25.0 (Fedora Rawhide), upon changing a desktop _particular_ windows from the previous desktop are being rendered on top of current one. The window is not responding to any interactions whatsoever. Looks like it's just being rendered there. Re-focusing windows seems to work and the one actually on current desktop get precedence, but the desktop is never visible until the ghost one gets minimized or closed. Saying "particular" because it seems to be happening only with windows of some apps. Consistently happens with Firefox for instance. It doesn't seem to happen with Dolphin and Konsole, though. A recording might make the issue easier to grasp: https://drive.proton.me/urls/RTKT32T20C#0sfFTbgP5rKI STEPS TO REPRODUCE 1. Open some windows on one desktop. 2. Open Firefox on another. 3. Switch to the desktop from step 2 to step 1 OBSERVED RESULT Firefox is rendered on top of everything, even though once can not interact with. EXPECTED RESULT Firefox should not be visible given that it's not on the switched to desktop. SOFTWARE/OS VERSIONS Linux 5.17.13 KDE Plasma Version: 5.25.0 KDE Frameworks Version: 5.94.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION This is a regression after updating to 5.25 on my machine. I've never experienced an issue anywhere near that on 5.24 and below. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 107302] Per-screen virtual desktops
https://bugs.kde.org/show_bug.cgi?id=107302 Kiril Vladimirov changed: What|Removed |Added CC||ki...@vladimiroff.org -- You are receiving this mail because: You are watching all bug changes.
[xdg-desktop-portal-kde] [Bug 446341] Shared via pipewire screen is rotated in 180°
https://bugs.kde.org/show_bug.cgi?id=446341 Kiril Vladimirov changed: What|Removed |Added Version|5.23.4 |5.24.1 -- You are receiving this mail because: You are watching all bug changes.
[xdg-desktop-portal-kde] [Bug 446341] Shared via pipewire screen is rotated in 180°
https://bugs.kde.org/show_bug.cgi?id=446341 --- Comment #2 from Kiril Vladimirov --- I have it running on a Lenovo Thinkpad T490. It happens regardless of any external displays. Not sure what other information I should provide in order to dig into it. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 425648] KCM Font Management is missing in wayland
https://bugs.kde.org/show_bug.cgi?id=425648 Kiril Vladimirov changed: What|Removed |Added CC||ki...@vladimiroff.org -- You are receiving this mail because: You are watching all bug changes.
[xdg-desktop-portal-kde] [Bug 446341] New: Shared via pipewire screen is rotated in 180°
https://bugs.kde.org/show_bug.cgi?id=446341 Bug ID: 446341 Summary: Shared via pipewire screen is rotated in 180° Product: xdg-desktop-portal-kde Version: 5.23.4 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: jgrul...@redhat.com Reporter: ki...@vladimiroff.org Target Milestone: --- SUMMARY Even though no rotation (or scaling) options are applied in "Display configuration", when sharing a screen via pipewire it comes out rotated in 180°. STEPS TO REPRODUCE 1. Start a OBS Studio (for instance, running Google Meet or whatever app which allows sharing/recording a screen yields the same result) 2. Make sure you've selected a screen 3. Start recording/sharing OBSERVED RESULT Screen is rotated in 180°. EXPECTED RESULT Proper screen orientation. SOFTWARE/OS VERSIONS Operating System: Fedora Linux 35 KDE Plasma Version: 5.23.3 KDE Frameworks Version: 5.88.0 Qt Version: 5.15.2 Kernel Version: 5.15.5-200.fc35.x86_64 (64-bit) Graphics Platform: Wayland Graphics Processor: Mesa Intel® UHD Graphics 620 Pipewire: 0.3.40 -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 409392] NetworkManager widget freezes on VPN connection issues, freezing/blocking Plasma
https://bugs.kde.org/show_bug.cgi?id=409392 --- Comment #14 from Kiril Vladimirov --- > Cannot reproduce on git master. It could be also a bug in older versions of > NetworkManager. On my system the version is 1.32.12 Whether the particular bug in networkmanager-* (to me was in the openvpn plugin) gets fixed is irrelevant to this issue. IMHO it only uncovered a sub-optimal design decision in the widget. It all boils down to that plasma-nm blocks until a response from NetworkManager comes which in turn blocks the whole plasma. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kdelibs4support] [Bug 389935] Kcolorchooser doesn't work in wayland
https://bugs.kde.org/show_bug.cgi?id=389935 Kiril Vladimirov changed: What|Removed |Added CC||ki...@vladimiroff.org -- You are receiving this mail because: You are watching all bug changes.
[lokalize] [Bug 424024] Main window doesn't repaint correctly on Wayland
https://bugs.kde.org/show_bug.cgi?id=424024 Kiril Vladimirov changed: What|Removed |Added CC||ki...@vladimiroff.org -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 421664] Sending email does not work with XOAUTH2
https://bugs.kde.org/show_bug.cgi?id=421664 Kiril Vladimirov changed: What|Removed |Added CC||ki...@vladimiroff.org -- You are receiving this mail because: You are watching all bug changes.
[Plasma Vault] [Bug 442831] Add option to disable opening vault's mount point upon unlocking
https://bugs.kde.org/show_bug.cgi?id=442831 Kiril Vladimirov changed: What|Removed |Added Resolution|--- |NOT A BUG Status|REPORTED|RESOLVED --- Comment #2 from Kiril Vladimirov --- Huh, I've never noticed that. Thanks. -- You are receiving this mail because: You are watching all bug changes.
[Plasma Vault] [Bug 442831] New: Add option to disable opening vault's mount point upon unlocking
https://bugs.kde.org/show_bug.cgi?id=442831 Bug ID: 442831 Summary: Add option to disable opening vault's mount point upon unlocking Product: Plasma Vault Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: ivan.cu...@kde.org Reporter: ki...@vladimiroff.org Target Milestone: --- SUMMARY It doesn't always make sense to open the mount point location in dolphin (or any file manager, really) upon unlocking. For instance, when downloading 2fa backup passwords list, I want to unlock my credentials vault in order to be able to simply access it from the "Save As" dialog and then lock it immediately. STEPS TO REPRODUCE 1. Click "Unlock and Open" 2. Type your password OBSERVED RESULT The default file manager opens up the mount point folder. EXPECTED RESULT Be able to disable that behavior. The current is definitely a sensible default, though. -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 432947] Disconnecting from a wifi network while there's an active VPN connection hangs Plasma for a moment
https://bugs.kde.org/show_bug.cgi?id=432947 Kiril Vladimirov changed: What|Removed |Added CC||ki...@vladimiroff.org --- Comment #17 from Kiril Vladimirov --- This looks like a duplicate of bug 409392. While waiting for a response from NetworkManager, plasma-nm seems to be blocking the whole plasma. -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 409392] NetworkManager widget freezes on connection issues blocking all Plasma
https://bugs.kde.org/show_bug.cgi?id=409392 Kiril Vladimirov changed: What|Removed |Added CC||ki...@vladimiroff.org -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 439765] Clipboard is intermittently broken in the Wayland session
https://bugs.kde.org/show_bug.cgi?id=439765 Kiril Vladimirov changed: What|Removed |Added CC||ki...@vladimiroff.org -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 422426] Implement Wayland Primary Selection Protocol bridge with XWayland
https://bugs.kde.org/show_bug.cgi?id=422426 Kiril Vladimirov changed: What|Removed |Added CC||ki...@vladimiroff.org -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 424754] Plasma fails to paste text copied from apps running on Xwayland (tested Firefox and Chromium)
https://bugs.kde.org/show_bug.cgi?id=424754 Kiril Vladimirov changed: What|Removed |Added CC||ki...@vladimiroff.org -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 426429] Bad font rendering in sound settings comboboxs
https://bugs.kde.org/show_bug.cgi?id=426429 --- Comment #17 from Kiril Vladimirov --- (In reply to Nate Graham from comment #10) > Any chance you can check git master/Plasma 5.22 to see if it's fixed there? > I cannot reproduce the issue there. Still reproducible on Plasma 5.22.0. Operating System: Fedora 35 KDE Frameworks Version: 5.83.0 Qt Version: 5.15.2 Graphics Platform: Wayland Graphics Processor: Mesa Intel® UHD Graphics 620 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 437302] New: Plasma crashses after adding "Application Menu" as titlebar button to titlebar
https://bugs.kde.org/show_bug.cgi?id=437302 Bug ID: 437302 Summary: Plasma crashses after adding "Application Menu" as titlebar button to titlebar Product: systemsettings Version: 5.21.90 Platform: Fedora RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: ki...@vladimiroff.org Target Milestone: --- Application: systemsettings5 (5.21.90) Qt Version: 5.15.2 Frameworks Version: 5.82.0 Operating System: Linux 5.11.12-300.fc34.x86_64 x86_64 Windowing System: Wayland Drkonqi Version: 5.21.90 Distribution: "Fedora release 35 (Rawhide)" -- Information about the crash: - What I was doing when the application crashed: 1. Open System Settings -> Appearance -> Window decorations -> Titlebar Buttons 2. Drag "Application menu" to the titlebar 3. Click "Apply" Plasma crashes, even though the button is added and functional afterwards. The crash can be reproduced every time. -- Backtrace: Application: Системни настройки (systemsettings5), signal: Segmentation fault Content of s_kcrashErrorMessage: [Current thread is 1 (Thread 0x7f58f9939940 (LWP 12229))] [KCrash Handler] #6 0x7f58fc365ec4 in QWaylandClientExtensionPrivate::handleRegistryGlobal (data=0x5598ae860c70, registry=0x5598ac671430, id=47, interface=..., version=1) at global/qwaylandclientextension.cpp:67 #7 0x7f58fc3523d9 in QtWaylandClient::QWaylandDisplay::registry_global (this=, id=, interface=..., version=) at /usr/src/debug/qt5-qtwayland-5.15.2-6.fc35.x86_64/src/client/qwaylanddisplay.cpp:397 #8 0x7f58fc36e753 in QtWayland::wl_registry::handle_global (data=0x5598ac66d120, object=, name=47, interface=0x5598aed0b4d0 "org_kde_kwin_blur_manager", version=1) at /usr/src/debug/qt5-qtwayland-5.15.2-6.fc35.x86_64/src/client/qwayland-wayland.cpp:94 #9 0x7f58f9cffc04 in ffi_call_unix64 () at ../src/x86/unix64.S:76 #10 0x7f58f9cff107 in ffi_call (cif=cif@entry=0x7ffe26329790, fn=, rvalue=, rvalue@entry=0x0, avalue=avalue@entry=0x7ffe26329860) at ../src/x86/ffi64.c:525 #11 0x7f58fc2bfd10 in wl_closure_invoke (closure=closure@entry=0x5598aed0b3f0, target=, target@entry=0x5598ac671430, opcode=opcode@entry=0, data=, flags=) at ../src/connection.c:1018 #12 0x7f58fc2c042b in dispatch_event (display=display@entry=0x5598ac6712e0, queue=, queue=) at ../src/wayland-client.c:1452 #13 0x7f58fc2c061c in dispatch_queue (queue=0x5598ac6713b0, display=0x5598ac6712e0) at ../src/wayland-client.c:1598 #14 wl_display_dispatch_queue_pending (display=0x5598ac6712e0, queue=0x5598ac6713b0) at ../src/wayland-client.c:1840 #15 0x7f58fc34a7a3 in QtWaylandClient::QWaylandDisplay::flushRequests (this=0x5598ac66d110) at /usr/src/debug/qt5-qtwayland-5.15.2-6.fc35.x86_64/src/client/qwaylanddisplay.cpp:222 #16 0x7f58fe941ce0 in doActivate (sender=0x5598ac66fa50, signal_index=3, argv=0x7ffe26329b30) at kernel/qobject.cpp:3898 #17 0x7f58fe93cc27 in QMetaObject::activate (sender=sender@entry=0x5598ac66fa50, m=m@entry=0x7f58febe1440 , local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7ffe26329b30) at kernel/qobject.cpp:3946 #18 0x7f58fe94443a in QSocketNotifier::activated (this=this@entry=0x5598ac66fa50, _t1=..., _t2=, _t3=...) at .moc/moc_qsocketnotifier.cpp:178 #19 0x7f58fe944c53 in QSocketNotifier::event (this=0x5598ac66fa50, e=0x7ffe26329c30) at kernel/qsocketnotifier.cpp:302 #20 0x7f58ff4d9423 in QApplicationPrivate::notify_helper (this=, receiver=0x5598ac66fa50, e=0x7ffe26329c30) at kernel/qapplication.cpp:3632 #21 0x7f58fe90e098 in QCoreApplication::notifyInternal2 (receiver=0x5598ac66fa50, event=0x7ffe26329c30) at kernel/qcoreapplication.cpp:1063 #22 0x7f58fe96011f in socketNotifierSourceDispatch (source=0x5598ac6a11b0) at kernel/qeventdispatcher_glib.cpp:107 #23 0x7f58fc5f84cf in g_main_dispatch (context=0x5598ac6daf20) at ../glib/gmain.c:3337 #24 g_main_context_dispatch (context=0x5598ac6daf20) at ../glib/gmain.c:4055 #25 0x7f58fc64c4e8 in g_main_context_iterate.constprop.0 (context=context@entry=0x5598ac6daf20, block=block@entry=1, dispatch=dispatch@entry=1, self=) at ../glib/gmain.c:4131 #26 0x7f58fc5f5c03 in g_main_context_iteration (context=0x5598ac6daf20, may_block=1) at ../glib/gmain.c:4196 #27 0x7f58fe95f698 in QEventDispatcherGlib::processEvents (this=0x5598ac6f0810, flags=...) at kernel/qeventdispatcher_glib.cpp:423 #28 0x7f58fe90cab2 in QEventLoop::exec (this=this@entry=0x7ffe26329ea0, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:69 #29 0x7f58fe914fe4 in QCoreApplication::exec () at ../../include/QtCore/../../src/corelib/global/qflags.h:121 #30 0x5598ac60c58c in main (argc=, argv=0x7ffe26329fc0) at /usr/src/debug/plasma-systemsettings-5.21.90-1.fc35.x86_64/app/main.cpp:208 [Inferior
[systemsettings] [Bug 426429] Bad font rendering in sound settings comboboxs
https://bugs.kde.org/show_bug.cgi?id=426429 --- Comment #14 from Kiril Vladimirov --- > Any chance you can check git master/Plasma 5.22 to see if it's fixed there? I > cannot reproduce the issue there. It's still reproducible on current plasma 5.21.90 (Fedora Rawhide packages). Will try to run latest master in the following days. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 378711] [Wayland] Qt and Gtk applications have two different copy stacks
https://bugs.kde.org/show_bug.cgi?id=378711 Kiril Vladimirov changed: What|Removed |Added CC||ki...@vladimiroff.org -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 435220] Cannot paste text copied from firefox outside firefox in wayland session
https://bugs.kde.org/show_bug.cgi?id=435220 Kiril Vladimirov changed: What|Removed |Added Version|5.15.3 |5.21.5 -- You are receiving this mail because: You are watching all bug changes.
