[kde] [Bug 496680] New: The virtual keyboard "maliit-keyboard" does not appear or function properly on the lock screen under Wayland.
https://bugs.kde.org/show_bug.cgi?id=496680 Bug ID: 496680 Summary: The virtual keyboard "maliit-keyboard" does not appear or function properly on the lock screen under Wayland. Classification: I don't know Product: kde Version: unspecified Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: m.benje...@gmail.com Target Milestone: --- When using the virtual keyboard "maliit-keyboard" on a system running KDE Plasma with Wayland, the keyboard fails to appear or respond when attempting to unlock the screen after sleep or lock. This behavior is inconsistent with how the keyboard operates on X11, where it functions correctly under similar conditions. The issue does not involve touch input, as the system is operated via a mouse. Attempts to manually launch "maliit-keyboard" produce the following terminal output: ```plaintext wordengine.cpp plugin "/usr/lib/x86_64-linux-gnu/maliit/keyboard2/languages/en/libenplugin.so" loaded inputmethod_p.h registerActiveLanguage(): activeLanguage is: "en" in inputMethod.cpp setActiveLanguage() activeLanguage is: "en" spellechecker.cpp in setLanguage() lang= "en" dictPath= "/usr/share/hunspell" inputMethod::reset() in clear preedit.. clearing word engine spellechecker.cpp in setLanguage() aff_file= "/usr/share/hunspell/en_US.aff" dic_file= "/usr/share/hunspell/en_US.dic" user dictionary= "/home/martin/.local/share/maliit-keyboard/en_userDictionary.dic" QSoundEffect(pulseaudio): Error decoding source file:///usr/share/maliit/keyboard2/sounds/key_tick2_quiet.wav ``` An attempt to resolve the `key_tick2_quiet.wav` error by creating an empty sound file did not resolve the issue. This behavior seems specific to Wayland, as switching to X11 resolves the problem. --- ### Steps to reproduce: 1. Set KDE Plasma to run on Wayland. 2. Lock the screen or let the system enter sleep mode, then wake it. 3. Attempt to use the virtual keyboard "maliit-keyboard" to enter the password via mouse interaction. --- **Observed result:** The virtual keyboard fails to appear or function. --- **Expected result:** The virtual keyboard should appear and allow input via mouse to unlock the screen, as it does on X11. --- ### Software/OS Versions: - **Operating System:** KDE Neon 6.2 - **KDE Plasma Version:** 6.2.3 - **KDE Frameworks Version:** 6.8.0 - **Qt Version:** 6.8.0 - **Kernel Version:** 6.8.0-49-generic --- **Additional information:** - This issue was discussed on the KDE forum under the following thread: " https://discuss.kde.org/t/i-have-some-problems-with-my-kde-neon-experience/25864/15?u=nitramo_off ". Forum participants suggested potential causes and troubleshooting steps, but the problem persists. - The keyboard works on the SDDM login screen, suggesting this is specific to the lock screen on Wayland. - No touch input is involved in this setup. - Switching to X11 resolves the issue, indicating the problem is specific to the Wayland session. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 497125] New: Dolphin: Erratic renaming behavior when quickly using F2 (rename) followed by Delete on a selected file.
https://bugs.kde.org/show_bug.cgi?id=497125 Bug ID: 497125 Summary: Dolphin: Erratic renaming behavior when quickly using F2 (rename) followed by Delete on a selected file. Classification: Applications Product: dolphin Version: 24.08.3 Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: m.benje...@gmail.com CC: kfm-de...@kde.org Target Milestone: --- Created attachment 176391 --> https://bugs.kde.org/attachment.cgi?id=176391&action=edit Visual demonstration of the issue. ### **Summary** Dolphin: Erratic renaming behavior when quickly using F2 (rename) followed by Delete on a selected file. --- ### **Description** Steps to Reproduce 1. Open Dolphin and navigate to a folder containing multiple files. 2. Select a file. 3. Quickly press **F2** (to rename the file), then immediately press **Delete** (to delete the file). Observed Result - The file is deleted as expected. - However, the rename text field appears on the next file in the list. - If the user clicks elsewhere (e.g., in empty space) to cancel the rename operation, the next file is renamed using the name of the deleted file. This issue can occasionally occur when using the mouse to rename and delete files in quick succession, but the behavior is consistently reproducible using the keyboard. Expected Result - Once a file is deleted, its name should not impact any other files. - The rename text field should not appear on any other files after the targeted file is deleted. Additional Information - This bug can lead to unintended renaming of files, causing confusion or data organization issues. - A video/gif demonstration of the issue is attached to this report for better understanding. --- ### **Software/OS Versions** - **Operating System:** KDE Neon 6.2 - **KDE Plasma Version:** 6.2.3 - **KDE Frameworks Version:** 6.8.0 - **Qt Version:** 6.8.0 - **Kernel Version:** 6.8.0-49-generic --- ### **Additional Information** - **Environment:** Wayland session (but may also occur under X11). - Attached gif shows the issue occurring with keyboard input. - The bug is harder to reproduce using the mouse, but similar behavior has been observed in specific scenarios. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 497119] New: Task Manager: Unexpected behavior when moving non-active icons in Wayland session with manual sorting.
https://bugs.kde.org/show_bug.cgi?id=497119 Bug ID: 497119 Summary: Task Manager: Unexpected behavior when moving non-active icons in Wayland session with manual sorting. Classification: I don't know Product: kde Version: unspecified Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: m.benje...@gmail.com Target Milestone: --- Created attachment 176384 --> https://bugs.kde.org/attachment.cgi?id=176384&action=edit Visual demonstration of the issue. ### **Summary** Task Manager: Unexpected behavior when moving non-active icons in Wayland session with manual sorting. --- ### **Description** Steps to Reproduce 1. Ensure you are using KDE Neon under a Wayland session. 2. Set the Task Manager to manual sorting mode. 3. Open multiple windows of various applications, ensuring they appear as separate icons (disable grouping). 4. Perform the following sequence: - Select an icon representing an inactive application. Drag it to a new position in the task manager and release the mouse button. - Immediately afterward, select a neighboring icon (without activating its associated application) and begin dragging it to a new position. Observed Result - While dragging the second icon, before releasing the mouse button: - The icon you are dragging suddenly resets to its original position. - The neighboring icon that your cursor first hovered over becomes "attached to your cursor" and starts moving instead. - This behavior consistently disrupts attempts to rearrange icons unless specific steps are taken to avoid it. For example: - If you have three distinct icons for the same app (not grouped) and drag the third (rightmost) icon to the left in the first position, this initial move succeeds. - However, if you then immediately try to drag the middle icon to a new position, let's say to the right: - The icon you try to move (middle one) resets to its original position. - The third (rightmost) icon unexpectedly becomes the one being moved, even though it wasn’t selected. Expected Result - The icon being dragged should remain selected and move to the intended position without interference. - Other icons should not reset or attach themselves to the cursor unexpectedly. Workaround - Click the icon first to activate its associated application, then drag it. This extra step prevents the erratic behavior and allows rearrangement. --- ### **Software/OS Versions** - **Operating System:** KDE Neon 6.2 - **KDE Plasma Version:** 6.2.3 - **KDE Frameworks Version:** 6.8.0 - **Qt Version:** 6.8.0 - **Kernel Version:** 6.8.0-49-generic --- ### **Additional Information** - **Environment:** Wayland session. - A detailed discussion and a visual demonstration of the issue (video/gif) are available in this forum thread: https://discuss.kde.org/t/problem-when-moving-not-active-icons-in-task-manager-kde-neon-wayland/26111 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 497119] Task Manager: Unexpected behavior when moving non-active icons in Wayland session with manual sorting.
https://bugs.kde.org/show_bug.cgi?id=497119 NitramO changed: What|Removed |Added Version|6.2.3 |6.2.4 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 497119] Task Manager: Unexpected behavior when moving non-active icons in Wayland session with manual sorting.
https://bugs.kde.org/show_bug.cgi?id=497119 --- Comment #2 from NitramO --- (In reply to Nate Graham from comment #1) > > *** This bug has been marked as a duplicate of bug 482770 *** I just updated to Qt 6.8.1, my KDE Plasma version is 6.2.4 and i still have the bug, btw the bug i reported is not exactly the same as this one so could it be another one? -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 497125] Dolphin: Erratic renaming behavior when quickly using F2 (rename) followed by Delete on a selected file.
https://bugs.kde.org/show_bug.cgi?id=497125 --- Comment #2 from NitramO --- (In reply to TraceyC from comment #1) > I'm not able to reproduce this on Dolphin 24.08.3 on Solus or built from > git-master, using keyboard only > I also tested on KDE Neon > When I press F2 and then Delete, the file name is erased, but the file is > not deleted. > > I clearly see the behavior you describe in the attachment, so this might be > a race condition I am not able to trigger. I'll leave this open in case > someone else is able to reproduce it. Yes maybe because i'm an idiot... I said it in the wrong order, you need to press Delete first and immediately F2 not in the other way... -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 482770] While dragging pinned app icons, the target icon changes if your drag moves over something that opens a window thumbnail popup
https://bugs.kde.org/show_bug.cgi?id=482770 --- Comment #29 from NitramO --- (In reply to Nate Graham from comment #28) > *** Bug 497119 has been marked as a duplicate of this bug. *** I just updated to Qt 6.8.1, my KDE Plasma version is 6.2.4 and i still have the bug, btw the bug i reported is not exactly the same as this one so could it be another one? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 497119] Task Manager: Unexpected behavior when moving non-active icons in Wayland session with manual sorting.
https://bugs.kde.org/show_bug.cgi?id=497119 NitramO changed: What|Removed |Added Status|RESOLVED|REOPENED Ever confirmed|0 |1 Resolution|DUPLICATE |--- -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 497119] Task Manager: Unexpected behavior when moving non-active icons in Wayland session with manual sorting.
https://bugs.kde.org/show_bug.cgi?id=497119 NitramO changed: What|Removed |Added Resolution|UPSTREAM|--- Status|RESOLVED|REOPENED -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 502375] [Regression] Activity switcher sidebar does not appear on principal screen but only on secondary
https://bugs.kde.org/show_bug.cgi?id=502375 NitramO changed: What|Removed |Added CC||m.benje...@gmail.com --- Comment #4 from NitramO --- (In reply to Nate Graham from comment #1) > Very likely caused by the fix for Bug 480890. > > It affects the Add Widgets sidebar too, right? Hi, could this issue be related to it? Do i need to do a new bug report or it's a duplicate in advance of this issue? https://discuss.kde.org/t/activity-selector-panel-misaligned-no-longer-left-anchored-after-update-kde-neon-wayland/32641 -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 496680] The virtual keyboard "maliit-keyboard" does not appear or function properly on the lock screen under Wayland when using a mouse
https://bugs.kde.org/show_bug.cgi?id=496680 --- Comment #3 from NitramO --- (In reply to Carlos De Maine from comment #1) > https://invent.kde.org/neon/neon/settings/-/merge_requests/13 Hi, do you have any news on this merge request? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 502656] New: [Regression] Activity Selector panel misaligned after update (Wayland, multi-monitor)
https://bugs.kde.org/show_bug.cgi?id=502656 Bug ID: 502656 Summary: [Regression] Activity Selector panel misaligned after update (Wayland, multi-monitor) Classification: Plasma Product: plasmashell Version: 6.3.4 Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Activity Switcher sidebar Assignee: plasma-b...@kde.org Reporter: m.benje...@gmail.com CC: ivan.cu...@kde.org Target Milestone: 1.0 Created attachment 180162 --> https://bugs.kde.org/attachment.cgi?id=180162&action=edit Image of the issue. SUMMARY After a recent update on KDE Neon (Wayland session), the Activity Selector panel is no longer anchored to the left side of the screen. Instead, it appears floating and misaligned, sometime stuck on the right edge of the screen. This behavior was not present before the update. I am using a multi-monitor setup (3 monitors). I initially asked about this on bug 502375 (https://bugs.kde.org/show_bug.cgi?id=502375), but was told the symptoms seem different, so this may be a separate issue. STEPS TO REPRODUCE 1. Use KDE Neon with Wayland session and 3 monitors 2. Press the Meta + A or Meta + Q keyboard shortcut to open the Activity Selector 3. Observe the position of the Activity Selector panel OBSERVED RESULT The panel appears floating on the right side of the screen, no longer docked or anchored to the left side as it used to be. EXPECTED RESULT The Activity Selector panel should be correctly anchored to the left side of the screen. SOFTWARE/OS VERSIONS Windows: N/A macOS: N/A Linux/KDE Plasma: KDE neon 6.3 KDE Plasma Version: 6.3.4 KDE Frameworks Version: 6.12.0 Qt Version: 6.8.2 Kernel Version: 6.11.0-21-generic (64-bit) Graphics Platform: Wayland ADDITIONAL INFORMATION - Forum thread with screenshot: https://discuss.kde.org/t/activity-selector-panel-misaligned-no-longer-left-anchored-after-update-kde-neon-wayland/32641 - I asked about this on bug 502375 (https://bugs.kde.org/show_bug.cgi?id=502375), and was told the symptoms are different, so it might be a different issue. - Screenshot attached (see image) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 500088] Virtual Desktop Manager: Window movement between desktops sometimes fails after the latest update
https://bugs.kde.org/show_bug.cgi?id=500088 --- Comment #6 from NitramO --- Since the last update, it seems fixed for me. My kinfo: Operating System: KDE neon 6.3 KDE Plasma Version: 6.3.4 KDE Frameworks Version: 6.13.0 Qt Version: 6.8.3 Kernel Version: 6.11.0-24-generic (64-bit) Graphics Platform: Wayland Processors: 20 × 13th Gen Intel® Core™ i7-13700H Memory: 31.0 Gio of RAM Graphics Processor 1: Intel® Graphics Graphics Processor 2: NVIDIA GeForce RTX 4060 Laptop GPU -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 459082] Wayland - Notification on primary monitor in wrong place
https://bugs.kde.org/show_bug.cgi?id=459082 NitramO changed: What|Removed |Added Status|NEEDSINFO |CONFIRMED Resolution|WAITINGFORINFO |--- CC||m.benje...@gmail.com --- Comment #8 from NitramO --- (In reply to Bug Janitor Service from comment #7) > 🐛🧹 ⚠️ This bug has been in NEEDSINFO status with no change for at least 15 > days. Please provide the requested information, then set the bug status to > REPORTED. If there is no change for at least 30 days, it will be > automatically closed as RESOLVED WORKSFORME. > > For more information about our bug triaging procedures, please read > https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging. > > Thank you for helping us make KDE software even better for everyone! I can confirm this bug. System configuration: OS: KDE neon 6.3 KDE Plasma: 6.3.4 KDE Frameworks: 6.13.0 Qt: 6.8.3 Kernel: 6.11.0-24-generic (64-bit) Graphics platform: Wayland CPU: Intel Core i7-13700H (20 threads) RAM: 31.0 Gio GPU 1: Intel Graphics GPU 2: NVIDIA GeForce RTX 4060 Laptop GPU Monitor setup: - Built-in laptop display (primary) - Two external monitors (always connected) - One 4K TV connected via HDMI switch (only detected when the switch is active) Bug behavior: When the 4K TV is detected (i.e. when the HDMI switch is sending signal), KDE uses only this display. Once the TV is disconnected, the previous 3-screen layout is restored. However, at that point, notifications are no longer displayed in the correct position. Observed issues: - Notifications appear in the top-left corner of the screen - Sometimes they are centered lower on the screen, but not in the expected bottom-right area - Occasionally they show up on the wrong screen entirely This happens quite randomly, but mostly when switching between the TV-only setup and the regular 3-monitor layout. Workaround: Killing and restarting plasmashell usually fixes the problem. However, the issue has reappeared on some occasions even without switching the display setup again. Additional related issues: - I have once observed the same misplacement behavior with the Application Launcher menu - Occasionally, the on-screen volume indicator (shown when using a media key) also appears in the wrong location — either on the wrong screen or in the top-left corner instead of its usual position near the bottom center -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 483645] Drag and drop files to web browser only work for the first file
https://bugs.kde.org/show_bug.cgi?id=483645 NitramO 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 483645] Drag and drop files to web browser only work for the first file
https://bugs.kde.org/show_bug.cgi?id=483645 --- Comment #33 from NitramO --- (In reply to NitramO from comment #32) > Same here! Please fix this issue, it's been here for whole year and it's > still not fixed... > > For me i can't drag and drop from Dolphin to any app at all... All i see in > the browser while dragging files is a "not-allowed" pointer. I can only drop > the file if i try to mess with the search bar or something while dragging > until the "not-allowed" pointer get replaced by "adding file" one, and then > when i drop the file it's corrupted, webistes/apps can get the name or info > about it but the file can't be used/decoded, so for example in Discord when > i try to send the message, i see the attached file and his name, but when i > try to send, it shows me an error telling me that the file is corrupt... > > - Operating System: KDE Neon 6.2 > - KDE Plasma Version: 6.3.0 > - KDE Frameworks Version: 6.10.0 > - Qt Version: 6.8.2 > - Kernel Version: 6.8.0-49-generic (64-bit) > - Graphics Platform: Wayland Ok, so here is a little update: Firstly, here is my "new" kinfo since the last updates: - Operating System: KDE neon 6.3 - KDE Plasma Version: 6.3.4 - KDE Frameworks Version: 6.13.0 - Qt Version: 6.8.3 - Kernel Version: 6.11.0-24-generic (64-bit) - Graphics Platform: Wayland - Processors: 20 × 13th Gen Intel® Core™ i7-13700H - Memory: 31.0 Gio of RAM - Graphics Processor 1: Intel® Graphics - Graphics Processor 2: NVIDIA GeForce RTX 4060 Laptop GPU So, I discovered something: I usually use two external monitors in addition to my laptop's internal display, but I also have an HDMI switch. When the switch is "activated," it sends the HDMI signal to a 4K TV, which temporarily changes the setup from 3 monitors to only the TV, until the switch is "disabled" and the HDMI signal is cut off. I noticed that when I only have one monitor connected/active, I don’t experience any issues with Dolphin drag-and-drop into web apps under Wayland — everything works as expected. So I'm not sure what's really causing the bug, but it seems to be related to the combination of Wayland and a multi-monitor setup. Can others who are experiencing this bug confirm whether you're also using multiple monitors? Or is it different for you? Also, is there anything I can test or try on my system to help you better understand and fix this bug? Just let me know which commands, tests, or diagnostics or anything else you'd like me to run and I'll do my best to help resolve this issue once and for all! -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 482262] Gwenview: Color Picker is missing: On Plasma 6, the "Select Color" menu won't show when you click on color palette => the three-dot button.
https://bugs.kde.org/show_bug.cgi?id=482262 NitramO changed: What|Removed |Added CC||m.benje...@gmail.com --- Comment #3 from NitramO --- Created attachment 180787 --> https://bugs.kde.org/attachment.cgi?id=180787&action=edit Visual demonstration of the issue. Same issue for me. (added an Attachement showing the issue) My kinfo: - Operating System: KDE neon 6.3 - KDE Plasma Version: 6.3.4 - KDE Frameworks Version: 6.13.0 - Qt Version: 6.8.3 - Kernel Version: 6.11.0-24-generic (64-bit) - Graphics Platform: Wayland - Processors: 20 × 13th Gen Intel® Core™ i7-13700H - Memory: 31.0 Gio of RAM - Graphics Processor 1: Intel® Graphics - Graphics Processor 2: NVIDIA GeForce RTX 4060 Laptop GPU -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 482262] Gwenview: Color Picker is missing: On Plasma 6, the "Select Color" menu won't show when you click on color palette => the three-dot button.
https://bugs.kde.org/show_bug.cgi?id=482262 --- Comment #4 from NitramO --- (In reply to NitramO from comment #3) > Created attachment 180787 [details] > Visual demonstration of the issue. > > Same issue for me. (added an Attachement showing the issue) > > My kinfo: > - Operating System: KDE neon 6.3 > - KDE Plasma Version: 6.3.4 > - KDE Frameworks Version: 6.13.0 > - Qt Version: 6.8.3 > - Kernel Version: 6.11.0-24-generic (64-bit) > - Graphics Platform: Wayland > - Processors: 20 × 13th Gen Intel® Core™ i7-13700H > - Memory: 31.0 Gio of RAM > - Graphics Processor 1: Intel® Graphics > - Graphics Processor 2: NVIDIA GeForce RTX 4060 Laptop GPU I'm using the flatpak version that comes by default with KDE Neon btw! -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 500088] Virtual Desktop Manager: Window movement between desktops sometimes fails after the latest update
https://bugs.kde.org/show_bug.cgi?id=500088 --- Comment #4 from NitramO --- (In reply to Nate Graham from comment #2) > Are you using fractional scaling? Yes, on one of my monitors that isn’t always connected, but in the example video, that wasn’t the case! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 497119] Task Manager: Unexpected behavior when moving non-active icons in Wayland session with manual sorting.
https://bugs.kde.org/show_bug.cgi?id=497119 --- Comment #12 from NitramO --- (In reply to Nate Graham from comment #9) > If you drag something and then immediately click, is everything fine? > > If yes, then it sounds exactly like Bug 491100. In that case, the options > are: > 1. The patch doesn't actually fix it > 2. You didn't apply the patch correctly "immediately click" where/how? On the icon itself that I'm moving? Could you be more precise please, so I try to reproduce? And regarding "2. You didn't apply the patch correctly"? What do you mean by that? I'm almost sure I applied it correctly, but the system told me I already had the patch, so I un-applied and re-applied it. Do you have any guide or advice to apply it properly or to check that it's fully applied? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 497119] Task Manager: Unexpected behavior when moving non-active icons in Wayland session with manual sorting.
https://bugs.kde.org/show_bug.cgi?id=497119 --- Comment #13 from NitramO --- (In reply to Roman from comment #10) > I am afraid I don't understand. What do you mean by "drag something and then > immediately click"? Order of tasks get incorrect while I am dragging (while > mouse button is still pressed), when I release the mouse button, the order > stays incorrect, why would clicking (on what? task that was dragged?) > changed anything at that point? > > Let me attach another demonstration - keep looking on firefox task YouTube, > how it "jumps" while I drag another task. > > Also, I have not patched anything myself, using unmodified plasma from arch > repository. And nothing becomes unresponsive (as bug 491100 suggests), > everything is responsive, tasks just "jump around" like shown, when manually > reordered. I have exactly the same issue, I can't be more precise than what you said and what i already said! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 491100] Reordering the icon in the Task Manager makes first click on other icons unresponsive
https://bugs.kde.org/show_bug.cgi?id=491100 --- Comment #38 from NitramO --- (In reply to Nate Graham from comment #37) > *** Bug 497119 has been marked as a duplicate of this bug. *** Hi, Could you describe me how to apply the patch exactly? Or else could you give me a link to a ressource or something that explain it in details? Because when I tried while awaiting for the Qt 6.8.3 update, it just told me I already had the patch and I tried to un-apply it like it suggested, and then re-applied it, but it still don't works sadly :/ Thanks in advance! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 497119] Task Manager: Unexpected behavior when moving non-active icons in Wayland session with manual sorting.
https://bugs.kde.org/show_bug.cgi?id=497119 --- Comment #17 from NitramO --- (In reply to Nate Graham from comment #14) > I'm preetty your your screen recording shows what I was expecting it > show. So let me be more precise with the instructions: > > 1. Click somewhere on the desktop > 2. Click on something in the Task Manager and drag it elsewhere by releasing > the mouse button. > 3. Before doing anything else, click again. Just click on the thing you just > dragged. One left click. > 4. Now, try to drag something else. > > At step 4, does the ordering get messed up, or does it work as expected? Thanks for the clarification. Yes it works "as expected" if I follow these steps, the additional click to "debug" after the dragging operation is what I described in the "Workaround" part of this request's description! But if I don't do it, it does not works, so I don't know if it's already fixed/patched in Upstream, but it don't works in Qt 6.8.2. Can you tell me if it's fixed in Qt 6.8.3? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 497119] Task Manager: Unexpected behavior when moving non-active icons in Wayland session with manual sorting.
https://bugs.kde.org/show_bug.cgi?id=497119 --- Comment #19 from NitramO --- (In reply to Nate Graham from comment #18) > Yes, it's supposed to be fixed in Qt 6.8.3. Thx! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 497119] Task Manager: Unexpected behavior when moving non-active icons in Wayland session with manual sorting.
https://bugs.kde.org/show_bug.cgi?id=497119 --- Comment #4 from NitramO --- (In reply to Nate Graham from comment #3) > There were unfortunately multiple issues, and the final one is fixed in Qt > 6.8.2. Hi, Since the last update of KDE Plasma 6.3 with Qt 6.8.2, the problem seems to be fixed a bit, but sometimes it works, sometimes not... - Operating System: KDE Neon 6.2 - KDE Plasma Version: 6.3.0 - KDE Frameworks Version: 6.10.0 - Qt Version: 6.8.2 - Kernel Version: 6.8.0-49-generic (64-bit) - Graphics Platform: Wayland I have multiple monitors! -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 496680] The virtual keyboard "maliit-keyboard" does not appear or function properly on the lock screen under Wayland when using a mouse
https://bugs.kde.org/show_bug.cgi?id=496680 --- Comment #2 from NitramO --- (In reply to Carlos De Maine from comment #1) > https://invent.kde.org/neon/neon/settings/-/merge_requests/13 Thanks! -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 500088] New: Virtual Desktop Manager: Window movement between desktops sometimes fails after the latest update
https://bugs.kde.org/show_bug.cgi?id=500088 Bug ID: 500088 Summary: Virtual Desktop Manager: Window movement between desktops sometimes fails after the latest update Classification: I don't know Product: kde Version: unspecified Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: m.benje...@gmail.com Target Milestone: --- Created attachment 178371 --> https://bugs.kde.org/attachment.cgi?id=178371&action=edit Visual demonstration of the issue. SUMMARY After the latest KDE Neon update, which was supposed to fix issues related to moving tabs/apps in the Task Manager with icons, a new issue appeared in the Virtual Desktop Manager. When trying to move an application window from one virtual desktop to another, the behavior is inconsistent. Sometimes, during the drag-and-drop action, the window gets stuck between two desktops and returns to its original position instead of moving to the intended virtual desktop. Other times, it works as expected. STEPS TO REPRODUCE 1. Open multiple virtual desktops. 2. Try to move an application window from one virtual desktop to another using drag and drop. 3. Observe the behavior when crossing between desktops. OBSERVED RESULT - The window sometimes gets stuck between two desktops and returns to its original position instead of moving to the intended virtual desktop. - In some cases, the movement works correctly, but the issue occurs randomly. EXPECTED RESULT The application window should move smoothly from one virtual desktop to another without getting stuck or returning to its original position. SOFTWARE/OS VERSIONS - Operating System: KDE Neon 6.2 - KDE Plasma Version: 6.3.0 - KDE Frameworks Version: 6.10.0 - Qt Version: 6.8.2 - Kernel Version: 6.8.0-49-generic (64-bit) - Graphics Platform: Wayland ADDITIONAL INFORMATION This issue appeared after the latest KDE Neon update, which was intended to fix the movement of tabs/apps in the Task Manager with icons. It is possible that both issues are related. A video demonstrating the problem is attached for better understanding. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 483645] Drag and drop files to web browser only work for the first file
https://bugs.kde.org/show_bug.cgi?id=483645 NitramO changed: What|Removed |Added CC||m.benje...@gmail.com --- Comment #32 from NitramO --- Same here! Please fix this issue, it's been here for whole year and it's still not fixed... For me i can't drag and drop from Dolphin to any app at all... All i see in the browser while dragging files is a "not-allowed" pointer. I can only drop the file if i try to mess with the search bar or something while dragging until the "not-allowed" pointer get replaced by "adding file" one, and then when i drop the file it's corrupted, webistes/apps can get the name or info about it but the file can't be used/decoded, so for example in Discord when i try to send the message, i see the attached file and his name, but when i try to send, it shows me an error telling me that the file is corrupt... - Operating System: KDE Neon 6.2 - KDE Plasma Version: 6.3.0 - KDE Frameworks Version: 6.10.0 - Qt Version: 6.8.2 - Kernel Version: 6.8.0-49-generic (64-bit) - Graphics Platform: Wayland -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 497119] Task Manager: Unexpected behavior when moving non-active icons in Wayland session with manual sorting.
https://bugs.kde.org/show_bug.cgi?id=497119 NitramO changed: What|Removed |Added Resolution|UPSTREAM|--- Status|RESOLVED|REOPENED --- Comment #6 from NitramO --- (In reply to Nate Graham from comment #5) > I suspect you're hitting Bug 491100, which was just fixed in Qt 6.8.3. I looked into it and tried installing the patch mentioned here: (In reply to pallaswept from comment #10) > (In reply to Nate Graham from comment #9) > > It's actually https://codereview.qt-project.org/c/qt/qtwayland/+/581714 > > Thanks Nate! > > Works great here, can confirm that patch resolves this issue at my machine. > > I'd normally like to help out my distro by packaging a cherry-picked patch > like this, but it seems like it might be too soon for me to go ahead yet(?). > I'll keep an eye on that link for when it is approved at that end, but if > you feel like it's safe to go ahead and patch distro packages, let me know. > > Thanks again and have a good weekend :) and (In reply to David Redondo from comment #30) > This commit fixes it fully for me > https://codereview.qt-project.org/c/qt/qtwayland/+/623667 Unfortunately, the patch didn't fix my issue. Also, my problem is a bit different from the one described in this bug report. It's more like this: When I sort the icons on one of the taskbars on any monitor (which now works since the last update), and then immediately try to sort icons on a taskbar on another monitor, if I didn’t click on an icon beforehand, it behaves similarly to what I originally described (and shown in the attached video). Additionally, the issue seems somewhat random, sometimes it works with no problems, and other times it doesn’t work at all. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 483645] Drag and drop files to web browser only work for the first file
https://bugs.kde.org/show_bug.cgi?id=483645 --- Comment #34 from NitramO --- (In reply to Nate Graham from comment #17) > You need to have a build from git master, not released packages. So Neon > Unstable, not Neon User. Hi, this bug is so annoying since I work every day with KDE Neon on my computer, so do you have any idea of when it's gonna be fixed or if it's even gonna be fixed one day? -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 482262] Gwenview: Color Picker is missing: On Plasma 6, the "Select Color" menu won't show when you click on color palette => the three-dot button.
https://bugs.kde.org/show_bug.cgi?id=482262 NitramO changed: What|Removed |Added CC||n...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 459082] Wayland - Notification on primary monitor in wrong place
https://bugs.kde.org/show_bug.cgi?id=459082
--- Comment #9 from NitramO ---
(In reply to Nate Graham from comment #6)
> (In reply to Andrej Halveland from comment #4)
> > I can reproduce this by simply plugging in my external monitor to my laptop
> > after Plasma is started.
> >
> > This can be fixed by simply opening "Display Configuration" from my system
> > tray and then switching to or between different modes ("Extend to left" or
> > "Extend to right"). Or it can also be fixed by re-arranging any screen in
> > System Settings.
> >
> > Here's a video of it:
> > https://youtu.be/YXzPtj2QO9E
>
> This issue is something else; in there your system tray popups are moving,
> not notifications.
>
> This is different from the original issue, which was about system
> notifications.
>
> Can anyone reproduce the original issue in Plasma 6.3 or newer? I'm unable
> to.
Yes me, i'm able to, as I explained it already in my other message!
--
You are receiving this mail because:
You are watching all bug changes.
[plasmashell] [Bug 506781] Spectacle not copying image to clipboard unless "Copy" is clicked
https://bugs.kde.org/show_bug.cgi?id=506781 NitramO changed: What|Removed |Added CC||m.benje...@gmail.com Ever confirmed|0 |1 Status|REPORTED|CONFIRMED --- Comment #1 from NitramO --- I have the same issue, but actually for me it's especially when I select an area and then press 'Enter' to crop my screenshot, it does not copy the image to the clipboard (while before it worked). But if I click on the 'Accept' button under the area I selected, it copies the image properly and I can paste it! Here is my kinfo: - Operating System: KDE neon User Edition - KDE Plasma Version: 6.4.1 - KDE Frameworks Version: 6.15.0 - Qt Version: 6.9.0 - Kernel Version: 6.11.0-29-generic (64-bit) - Graphics Platform: Wayland - Processors: 20 × 13th Gen Intel® Core™ i7-13700H - Memory: 32 Gio of RAM (31.0 Gio usable) - Graphics Processor 1: Intel® Graphics - Graphics Processor 2: NVIDIA GeForce RTX 4060 Laptop GPU -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 506979] New: Accent and dead key input broken in some apps on KDE Neon Wayland after recent update
https://bugs.kde.org/show_bug.cgi?id=506979 Bug ID: 506979 Summary: Accent and dead key input broken in some apps on KDE Neon Wayland after recent update Classification: KDE Neon Product: neon Version First unspecified Reported In: Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: neon-b...@kde.org Reporter: m.benje...@gmail.com CC: carlosd@gmail.com, j...@jriddell.org, neon-b...@kde.org Target Milestone: --- SUMMARY: Accent and dead key input (e.g. `^`, `¨`, `ê`, `ë`) is no longer working in certain applications since a recent update of KDE Neon under Wayland. The issue appears app-specific (e.g. affects Vesktop and LM Studio for me), and was not present before the update. STEPS TO REPRODUCE: 1. Use KDE Neon (Plasma 6.4.2) under a Wayland session. 2. Launch an application such as Vesktop (Flatpak) or LM Studio (AppImage). 3. Try typing characters using dead keys (e.g. `^` then `e` → `ê`, or `¨` then `e` → `ë`). OBSERVED RESULT: Dead keys like `^` or `¨` produce no character and do not combine with the following letter. The accent input is completely ignored in some apps. Other apps (like Discord Flatpak) behave correctly and allow proper input of accented characters. EXPECTED RESULT: Dead key input should function consistently across all applications in the Wayland session, as it did before the recent KDE Neon update. SOFTWARE/OS VERSIONS: - Operating System: KDE neon User Edition - KDE Plasma Version: 6.4.2 - KDE Frameworks Version: 6.15.0 - Qt Version: 6.9.0 - Kernel Version: 6.11.0-29-generic (64-bit) - Graphics Platform: Wayland - Processors: 20 × 13th Gen Intel® Core™ i7-13700H - Memory: 32 GiB - Graphics: Intel® Graphics + NVIDIA GeForce RTX 4060 Laptop GPU (hybrid) ADDITIONAL INFORMATION: This issue did not exist before (under Wayland). It appeared recently, presumably after the latest KDE Neon update I did. The problem can be worked around by manually setting environment variables before launching affected applications: GTK_IM_MODULE=ibus QT_IM_MODULE=ibus Creating a persistent fix (e.g. in `~/.config/environment.d/immodules.conf`) resolves the problem system-wide. This may suggests that the KDE Neon Wayland session does not export proper input method environment variables by default, which may break accent/dead key input in some apps that depend on them. It would be helpful if KDE Neon set these variables by default for Wayland sessions to ensure full compatibility. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 506608] Baloo file extractor keep crashing again and again at startup of KDE Neon...
https://bugs.kde.org/show_bug.cgi?id=506608 --- Comment #1 from NitramO --- Created attachment 182963 --> https://bugs.kde.org/attachment.cgi?id=182963&action=edit Taskbar filled with crash notifications -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 506608] New: Baloo file extractor keep crashing again and again at startup of KDE Neon...
https://bugs.kde.org/show_bug.cgi?id=506608
Bug ID: 506608
Summary: Baloo file extractor keep crashing again and again at
startup of KDE Neon...
Classification: Frameworks and Libraries
Product: frameworks-baloo
Version First 6.15.0
Reported In:
Platform: Neon
OS: Linux
Status: REPORTED
Keywords: drkonqi
Severity: crash
Priority: NOR
Component: Baloo File Daemon
Assignee: baloo-bugs-n...@kde.org
Reporter: m.benje...@gmail.com
Target Milestone: ---
Application: baloo_file_extractor (6.15.0)
ApplicationNotResponding [ANR]: false
Qt Version: 6.9.0
Frameworks Version: 6.15.0
Operating System: Linux 6.11.0-29-generic x86_64
Windowing System: Wayland
Distribution: KDE neon User Edition
DrKonqi: 6.4.1 [CoredumpBackend]
-- Information about the crash:
As the title says, when I log into my session on KDE Neon, the Baloo file
extractor keep crashing again and again completly filling the taskbar until I
kill every instances of it with the "System monitoring app" (or killall in the
terminal I presume...)
The crash can be reproduced every time.
-- Backtrace:
Application: Extracteur de fichiers Baloo (baloo_file_extractor), signal:
Aborted
Content of s_kcrashErrorMessage: std::unique_ptr = {get() = }
[New LWP 10715]
[New LWP 10717]
[New LWP 10719]
[New LWP 10718]
warning: could not find '.gnu_debugaltlink' file for
/lib/x86_64-linux-gnu/libglib-2.0.so.0
warning: could not find '.gnu_debugaltlink' file for
/lib/x86_64-linux-gnu/libcap.so.2
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
Core was generated by
`/usr/lib/x86_64-linux-gnu/libexec/kf6/baloo_file_extractor'.
Program terminated with signal SIGABRT, Aborted.
Download failed: Invalid argument. Continuing without source file
./nptl/./nptl/pthread_kill.c.
#0 __pthread_kill_implementation (no_tid=0, signo=6, threadid=)
at ./nptl/pthread_kill.c:44
warning: 44 ./nptl/pthread_kill.c: No such file or directory
[Current thread is 1 (Thread 0x7ae890b19a40 (LWP 10715))]
Cannot QML trace cores :(
Downloading source file
/usr/src/qt6-base-6.9.0-0zneon+24.04+noble+release+build112/src/corelib/kernel/qcoreapplication.cpp...
Downloading source file
/usr/src/qt6-base-6.9.0-0zneon+24.04+noble+release+build112/src/corelib/kernel/qobject.cpp...
Downloading source file
/usr/src/qt6-base-6.9.0-0zneon+24.04+noble+release+build112/src/corelib/kernel/qsingleshottimer.cpp...
Downloading source file
/usr/src/qt6-base-6.9.0-0zneon+24.04+noble+release+build112/obj-x86_64-linux-gnu/src/corelib/Core_autogen/include/moc_qsingleshottimer_p.cpp...
Downloading source file
/usr/src/qt6-base-6.9.0-0zneon+24.04+noble+release+build112/src/corelib/kernel/qobjectdefs_impl.h...
Downloading source file
/usr/src/kf6-baloo-6.15.0-0zneon+24.04+noble+release+build39/src/file/extractor/app.cpp...
Downloading source file
/usr/src/kf6-kfilemetadata-6.15.0-0zneon+24.04+noble+release+build23/src/extractors/plaintextextractor.cpp...
Downloading source file
/usr/src/kf6-baloo-6.15.0-0zneon+24.04+noble+release+build39/src/engine/termgenerator.cpp...
Downloading source file
/usr/src/kf6-baloo-6.15.0-0zneon+24.04+noble+release+build39/src/engine/document.cpp...
Downloading source file
/usr/src/qt6-base-6.9.0-0zneon+24.04+noble+release+build112/src/corelib/global/qassert.cpp...
Downloading source file
/usr/src/qt6-base-6.9.0-0zneon+24.04+noble+release+build112/src/corelib/global/qlogging.cpp...
Download failed: Invalid argument. Continuing without source file
./stdlib/./stdlib/abort.c.
Download failed: Invalid argument. Continuing without source file
./signal/../sysdeps/posix/raise.c.
Download failed: Invalid argument. Continuing without source file
./nptl/./nptl/pthread_kill.c.
Download failed: Invalid argument. Continuing without source file
./misc/../sysdeps/unix/sysv/linux/x86_64/clone3.S.
Download failed: Invalid argument. Continuing without source file
./nptl/./nptl/pthread_create.c.
Downloading source file
/usr/src/qt6-base-6.9.0-0zneon+24.04+noble+release+build112/src/corelib/thread/qthread_unix.cpp...
Downloading source file
/usr/src/qt6-wayland-6.9.0-0zneon+24.04+noble+release+build29/src/client/qwaylanddisplay.cpp...
Download failed: Invalid argument. Continuing without source file
./io/../sysdeps/unix/sysv/linux/poll.c.
Downloading source file
/usr/src/qt6-base-6.9.0-0zneon+24.04+noble+release+build112/src/dbus/qdbusconnectionmanager.cpp...
[Current thread is 1 (Thread 0x7ae890b19a40 (LWP 10715))]
Thread 4 (Thread 0x7ae88d5fe6c0 (LWP 10718)):
#0 0x7ae891b1b4cd in __GI___poll (fds=fds@entry=0x7ae88d5fdb00,
nfds=nfds@entry=2, timeout=timeout@entry=-1) at
../sysdeps/unix/sysv/linux/poll.c:29
#1 0x7ae88e43b2cf in poll (__timeout=-1, __nfds=2, __fds=0x7ae88d5fdb00)
at /usr/include/x86_64-linux-gnu/bits/poll2.h:39
#2 QtWaylandClient::EventTh
[gwenview] [Bug 507489] Gwenview Annotate: Clicking on color square does not open color picker (KDE Neon, Wayland, Flatpak version)
https://bugs.kde.org/show_bug.cgi?id=507489 --- Comment #4 from NitramO --- (In reply to Antonio Rojas from comment #3) > As explained in bug 482262, this is not a gwenview issue. Please read *all* > comments of that bug report. "It's not my fault, it's the fault of the 'program/API/third-party/lib/and so on...' that I use." Well, then it's your fault, if it's outdated/deprecated, it's your responsibility to fix it, to find a replacement, or even to file the bug report for the users using your OS/apps. I shouldn't have to do it, I did it because I know you won't do it, but it shouldn't be my role. I'm just using the report tool provided by KDE to report the bug on my system or system's apps. If there's a bug or an issue coming not directly from what I report, it's not my business... -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 507613] It crashed... Again... Like it does so many times a week...
https://bugs.kde.org/show_bug.cgi?id=507613 --- Comment #1 from NitramO --- Created attachment 183614 --> https://bugs.kde.org/attachment.cgi?id=183614&action=edit New crash information added by DrKonqi DrKonqi auto-attaching complete backtrace. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 507613] New: It crashed... Again... Like it does so many times a week...
https://bugs.kde.org/show_bug.cgi?id=507613 Bug ID: 507613 Summary: It crashed... Again... Like it does so many times a week... Classification: Plasma Product: kwin Version First 6.4.3 Reported In: Platform: Neon OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: m.benje...@gmail.com Target Milestone: --- Application: kwin_wayland (6.4.3) ApplicationNotResponding [ANR]: false Qt Version: 6.9.1 Frameworks Version: 6.16.0 Operating System: Linux 6.14.0-24-generic x86_64 Windowing System: Wayland Distribution: KDE neon User Edition DrKonqi: 6.4.3 [CoredumpBackend] -- Information about the crash: It crashed while I was just using my computer. (Like I opened or closed Brave Browser and Dolphin file explorer or something) It's been happening more and more since the last two updates... This is one of the reasons why I left Windows to switch to Linux, it's starting to bother me... The reporter is unsure if this crash is reproducible. -- Backtrace (Reduced): #6 std::__atomic_base::fetch_add (this=0x4d1, __i=1, __m=std::memory_order::acq_rel) at /usr/include/c++/14/bits/atomic_base.h:629 #7 QAtomicOps::ref (_q_value=) at /usr/include/x86_64-linux-gnu/qt6/QtCore/qatomic_cxx11.h:259 [...] #11 QArrayDataPointer::QArrayDataPointer (this=0x7ffc703e3590, other=...) at /usr/include/x86_64-linux-gnu/qt6/QtCore/qarraydatapointer.h:40 #12 QList::QList (this=0x7ffc703e3590, this=) at /usr/include/x86_64-linux-gnu/qt6/QtCore/qlist.h:76 #13 KWin::Window::desktops (this=this@entry=0x6288110fe090) at /usr/src/kwin-4:6.4.3-0zneon+24.04+noble+release+build48/src/window.cpp:806 #14 0x754b20a3ad30 in KWin::Window::isOnAllDesktops (this=0x6288110fe090) at /usr/src/kwin-4:6.4.3-0zneon+24.04+noble+release+build48/src/window.h:2090 #15 KWin::Window::isOnDesktop (this=0x6288110fe090, desktop=0x62880e889680) at /usr/src/kwin-4:6.4.3-0zneon+24.04+noble+release+build48/src/window.cpp:824 #16 0x754b20c0967d in KWin::TabBox::TabBoxHandlerImpl::checkDesktop (this=0x62880e79dc80, client=0x6288110fe090) at /usr/src/kwin-4:6.4.3-0zneon+24.04+noble+release+build48/src/tabbox/tabbox.cpp:94 #17 KWin::TabBox::TabBoxHandlerImpl::clientToAddToList (this=0x62880e79dc80, client=0x6288110fe090) at /usr/src/kwin-4:6.4.3-0zneon+24.04+noble+release+build48/src/tabbox/tabbox.cpp:163 #18 0x754b20c0f0df in KWin::TabBox::ClientModel::createFocusChainClientList (this=0x62880e7b90f0, start=) at /usr/src/kwin-4:6.4.3-0zneon+24.04+noble+release+build48/src/tabbox/clientmodel.cpp:158 #19 KWin::TabBox::ClientModel::createClientList (this=0x62880e7b90f0, partialReset=true) at /usr/src/kwin-4:6.4.3-0zneon+24.04+noble+release+build48/src/tabbox/clientmodel.cpp:213 #20 KWin::TabBox::TabBoxHandler::createModel (this=0x62880e79dc80, partialReset=true) at /usr/src/kwin-4:6.4.3-0zneon+24.04+noble+release+build48/src/tabbox/tabboxhandler.cpp:474 #21 KWin::TabBox::TabBox::reset (this=0x62880dc84eb0, partial_reset=true) at /usr/src/kwin-4:6.4.3-0zneon+24.04+noble+release+build48/src/tabbox/tabbox.cpp:400 #22 0x754b20a5150b in KWin::Workspace::addWaylandWindow (this=0x62880dc135c0, window=) at /usr/src/kwin-4:6.4.3-0zneon+24.04+noble+release+build48/src/workspace.cpp:786 #23 0x754b1e07cce9 in QtPrivate::QSlotObjectBase::call (a=0x7ffc703e3880, r=, this=0x62880eb1c450, this=, r=, a=) at /usr/src/qt6-base-6.9.1-0zneon+24.04+noble+release+build117/src/corelib/kernel/qobjectdefs_impl.h:461 #24 doActivate (sender=0x62880da09ff0, signal_index=3, argv=0x7ffc703e3880) at /usr/src/qt6-base-6.9.1-0zneon+24.04+noble+release+build117/src/corelib/kernel/qobject.cpp:4146 Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 507060] Unable to drag desktop files between monitors
https://bugs.kde.org/show_bug.cgi?id=507060 NitramO changed: What|Removed |Added CC||m.benje...@gmail.com --- Comment #10 from NitramO --- Same issue here! My kinfo: - Operating System: KDE neon User Edition - KDE Plasma Version: 6.4.3 - KDE Frameworks Version: 6.16.0 - Qt Version: 6.9.1 - Kernel Version: 6.14.0-24-generic (64-bit) - Graphics Platform: Wayland - Processors: 20 × 13th Gen Intel® Core™ i7-13700H - Memory: 32 Gio of RAM (31.0 Gio usable) - Graphics Processor 1: Intel® Graphics - Graphics Processor 2: NVIDIA GeForce RTX 4060 Laptop GPU -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 507489] New: Gwenview Annotate: Clicking on color square does not open color picker (KDE Neon, Wayland, Flatpak version)
https://bugs.kde.org/show_bug.cgi?id=507489 Bug ID: 507489 Summary: Gwenview Annotate: Clicking on color square does not open color picker (KDE Neon, Wayland, Flatpak version) Classification: Applications Product: gwenview Version First 25.04.3 Reported In: Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: gwenview-bugs-n...@kde.org Reporter: m.benje...@gmail.com Target Milestone: --- Created attachment 183514 --> https://bugs.kde.org/attachment.cgi?id=183514&action=edit Visual demonstration of the issue. SUMMARY: Cannot open color picker when annotating an image STEPS TO REPRODUCE: 1. Open Gwenview 2. Open any image 3. Click on "Show Editing Tools" → "Annotate" 4. Select any annotation tool (rectangle, text, pencil, etc.) from the left toolbar 5. Click on the color preview square in the top-left of the Annotate window OBSERVED RESULT: Clicking on the color square does nothing. No color picker opens, no menu or palette appears. It's not possible to change the color. There is no way to access the "three-dot" button because the initial color selection UI does not respond. EXPECTED RESULT: Clicking on the color square should open a color palette or color picker dialog, allowing the user to choose a color. SOFTWARE/OS VERSIONS: Windows: N/A macOS: N/A Linux/KDE Plasma: KDE neon User Edition KDE Plasma Version: 6.4.3 KDE Frameworks Version: 6.16.0 Qt Version: 6.9.1 Kernel Version: 6.14.0-24-generic (64-bit) Graphics Platform: Wayland ADDITIONAL INFORMATION: I am attaching a video that shows the issue. This bug makes annotation tools unusable if a color change is needed. I'm using the Flatpak version of Gwenview that comes by default with KDE Neon, by the way. My kinfo: - Operating System: KDE neon User Edition - KDE Plasma Version: 6.4.3 - KDE Frameworks Version: 6.16.0 - Qt Version: 6.9.1 - Kernel Version: 6.14.0-24-generic (64-bit) - Graphics Platform: Wayland - Processors: 20 × 13th Gen Intel® Core™ i7-13700H - Memory: 32 Gio of RAM (31.0 Gio usable) - Graphics Processor 1: Intel® Graphics - Graphics Processor 2: NVIDIA GeForce RTX 4060 Laptop GPU -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 482262] Gwenview: Color Picker is missing: On Plasma 6, the "Select Color" menu won't show when you click on color palette => the three-dot button.
https://bugs.kde.org/show_bug.cgi?id=482262 NitramO changed: What|Removed |Added Resolution|UPSTREAM|--- Status|RESOLVED|REOPENED --- Comment #11 from NitramO --- I still have this issue with latest update! My kinfo: - Operating System: KDE neon User Edition - KDE Plasma Version: 6.4.3 - KDE Frameworks Version: 6.16.0 - Qt Version: 6.9.1 - Kernel Version: 6.14.0-24-generic (64-bit) - Graphics Platform: Wayland - Processors: 20 × 13th Gen Intel® Core™ i7-13700H - Memory: 32 Gio of RAM (31.0 Gio usable) - Graphics Processor 1: Intel® Graphics - Graphics Processor 2: NVIDIA GeForce RTX 4060 Laptop GPU -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 507489] Gwenview Annotate: Clicking on color square does not open color picker (KDE Neon, Wayland, Flatpak version)
https://bugs.kde.org/show_bug.cgi?id=507489 --- Comment #2 from NitramO --- (In reply to Antonio Rojas from comment #1) > > *** This bug has been marked as a duplicate of bug 482262 *** Could you please explain me how this is resolved? I did the last update and it's not fixed for me! Also it's not the same bug as described in #bug 482262 read more carefully... I can't access to the color picker at all, in the bug 482262, the color picker is accessible but the "three dots" button in the color picker is not working. Please explain yourself or I'll just re-set it to "reported". -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 507673] New: It crashed while I was using my computer again...
https://bugs.kde.org/show_bug.cgi?id=507673 Bug ID: 507673 Summary: It crashed while I was using my computer again... Classification: Plasma Product: kwin Version First 6.4.3 Reported In: Platform: Neon OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: m.benje...@gmail.com Target Milestone: --- Application: kwin_wayland (6.4.3) ApplicationNotResponding [ANR]: false Qt Version: 6.9.1 Frameworks Version: 6.16.0 Operating System: Linux 6.14.0-24-generic x86_64 Windowing System: Wayland Distribution: KDE neon User Edition DrKonqi: 6.4.3 [CoredumpBackend] -- Information about the crash: It crashed while I was using my computer again... I just reopened the minimized Brave Browser window... The reporter is unsure if this crash is reproducible. -- Backtrace (Reduced): #6 0x55df3bfa2930 in ??? () #7 0x7a93e8045427 in KWin::Window::isOnActivity (this=0x55df380dfb40, activity=...) at /usr/src/kwin-4:6.4.3-0zneon+24.04+noble+release+build48/src/window.h:2100 #8 KWin::Window::isOnCurrentActivity (this=0x55df380dfb40) at /usr/src/kwin-4:6.4.3-0zneon+24.04+noble+release+build48/src/window.cpp:3250 #9 KWin::Window::isOnCurrentActivity (this=0x55df380dfb40) at /usr/src/kwin-4:6.4.3-0zneon+24.04+noble+release+build48/src/window.cpp:3244 #10 0x7a93e820968d in KWin::TabBox::TabBoxHandlerImpl::checkActivity (this=0x55df37622d00, client=0x55df380dfb40) at /usr/src/kwin-4:6.4.3-0zneon+24.04+noble+release+build48/src/tabbox/tabbox.cpp:106 #11 KWin::TabBox::TabBoxHandlerImpl::clientToAddToList (this=0x55df37622d00, client=0x55df380dfb40) at /usr/src/kwin-4:6.4.3-0zneon+24.04+noble+release+build48/src/tabbox/tabbox.cpp:164 #12 0x7a93e820f0df in KWin::TabBox::ClientModel::createFocusChainClientList (this=0x55df3763e110, start=) at /usr/src/kwin-4:6.4.3-0zneon+24.04+noble+release+build48/src/tabbox/clientmodel.cpp:158 #13 KWin::TabBox::ClientModel::createClientList (this=0x55df3763e110, partialReset=true) at /usr/src/kwin-4:6.4.3-0zneon+24.04+noble+release+build48/src/tabbox/clientmodel.cpp:213 #14 KWin::TabBox::TabBoxHandler::createModel (this=0x55df37622d00, partialReset=true) at /usr/src/kwin-4:6.4.3-0zneon+24.04+noble+release+build48/src/tabbox/tabboxhandler.cpp:474 #15 KWin::TabBox::TabBox::reset (this=0x55df36b1edf0, partial_reset=true) at /usr/src/kwin-4:6.4.3-0zneon+24.04+noble+release+build48/src/tabbox/tabbox.cpp:400 #16 0x7a93e805150b in KWin::Workspace::addWaylandWindow (this=0x55df36c13010, window=) at /usr/src/kwin-4:6.4.3-0zneon+24.04+noble+release+build48/src/workspace.cpp:786 #17 0x7a93e567cce9 in QtPrivate::QSlotObjectBase::call (a=0x7ffc7dda25e0, r=, this=0x55df379491b0, this=, r=, a=) at /usr/src/qt6-base-6.9.1-0zneon+24.04+noble+release+build117/src/corelib/kernel/qobjectdefs_impl.h:461 #18 doActivate (sender=0x55df368925a0, signal_index=3, argv=0x7ffc7dda25e0) at /usr/src/qt6-base-6.9.1-0zneon+24.04+noble+release+build117/src/corelib/kernel/qobject.cpp:4146 [...] #20 KWin::WaylandServer::windowAdded (this=, _t1=) at /usr/src/kwin-4:6.4.3-0zneon+24.04+noble+release+build48/obj-x86_64-linux-gnu/src/kwin_autogen/include/moc_wayland_server.cpp:149 #21 0x7a93e567cce9 in QtPrivate::QSlotObjectBase::call (a=0x7ffc7dda2688, r=, this=0x55df38e1bc10, this=, r=, a=) at /usr/src/qt6-base-6.9.1-0zneon+24.04+noble+release+build117/src/corelib/kernel/qobjectdefs_impl.h:461 #22 doActivate (sender=0x55df3c24a980, signal_index=61, argv=0x7ffc7dda2688) at /usr/src/qt6-base-6.9.1-0zneon+24.04+noble+release+build117/src/corelib/kernel/qobject.cpp:4146 Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 507613] kwin_wayland often crashes in std::__atomic_base::fetch_add
https://bugs.kde.org/show_bug.cgi?id=507613 --- Comment #4 from NitramO --- (In reply to Vlad Zahorodnii from comment #3) > If you find a reliable way to reproduce the crash, please let us know. You should look at bug 507673 https://bugs.kde.org/show_bug.cgi?id=507673 -- You are receiving this mail because: You are watching all bug changes.
