[neon] [Bug 488853] Neon 6.1 - kwin on X11 fails to shutdown/logout/restart
https://bugs.kde.org/show_bug.cgi?id=488853 pablo changed: What|Removed |Added CC||pa...@netcomputacion.com -- You are receiving this mail because: You are watching all bug changes.
[angelfish] [Bug 469381] [Feature Request - Desktop] When opening a new tab, focus the address bar
https://bugs.kde.org/show_bug.cgi?id=469381 Pablo Alonso changed: What|Removed |Added Assignee|t...@tutanota.com |j...@kaidan.im -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 488018] New: Clicking on a shortcut to a system settings module from the panel does not hide the middle list if it doesn't have one
https://bugs.kde.org/show_bug.cgi?id=488018 Bug ID: 488018 Summary: Clicking on a shortcut to a system settings module from the panel does not hide the middle list if it doesn't have one Classification: Applications Product: systemsettings Version: 6.0.5 Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: t...@tutanota.com Target Milestone: --- Created attachment 170131 --> https://bugs.kde.org/attachment.cgi?id=170131=edit Screnshot of the observed result *** 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 When you click a shortcut to a system settings module (For example, clicking on "Configure energy saving" on the battery applet) and you already have system settings open on another page, the middle list of buttons (The one that changes when you switch from a page from the left-most list) won't update STEPS TO REPRODUCE 1. Open system settings 2. Click on a page on the left-most list that has an arrow (For example "Monitor and displays") 3. Click on a panel applet that opens a module that has no sub-pages (For example, the "Energy and battery" applet) 4. Click the shortcut to the system settings module for the applet OBSERVED RESULT The module opens, but the middle list of buttons does not update (In the example, it still shows the list for "Monitor and displays") EXPECTED RESULT The middle list should be hidden as the "Energy and savings" page does not have subpages SOFTWARE/OS VERSIONS Operating System: CachyOS Linux (Based on Arch Linux) KDE Plasma Version: 6.0.5 KDE Frameworks Version: 6.2.0 Qt Version: 6.7.1 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 469022] Selected area bleaches text
https://bugs.kde.org/show_bug.cgi?id=469022 --- Comment #59 from pablo --- Just FYI .. my issue is no longer a problem with: o KDE Plasma 6.0.3 o Frameworks: 6.0.0 o Qt Version: 6.7.0 o Graphics Platform: X11 My iGPU is Intel. I'm not sure whether to close this bug based on the comments of others. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 485056] New: Cannot switch desktops while moving windows and Maximize/Tile enabled
https://bugs.kde.org/show_bug.cgi?id=485056 Bug ID: 485056 Summary: Cannot switch desktops while moving windows and Maximize/Tile enabled Classification: Plasma Product: kwin Version: 6.0.3 Platform: openSUSE OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: effects-window-management Assignee: kwin-bugs-n...@kde.org Reporter: pa...@blueoakdb.com Target Milestone: --- SUMMARY Under "Mouse & Touchpad" is the "Screen Edges" setting which one can configure switching desktop on edge when moving windows: Switch desktop on edge: Only When Moving Windows. Under 5.x, this worked while the following two settings were also set: * Maximize: __ Windows dragged to top edge * Tile: __ Windows dragged to left or right edge Under 6.x, switching desktop only works consistently if Maximize/Tile are disabled. STEPS TO REPRODUCE 0. Have at least two Virtual Desktops (I have eight) 1. Enable Maximize/Tile and "Switch desktop on edge: Only When Moving Windows" 2. Log out, log in 3. Open a Konsole window on Desktop 1 4. Drag right. Do it again. Eventually desktop switching will stop working. For me, sometimes it works for one switch or none at all. OBSERVED RESULT Eventually, instead of the desktop being switched, the window is resized to 1/2 the screen. I also have an upper left corner trigger that stops working. EXPECTED RESULT The desktop should continue to switch and screen triggers should continue to work. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: 6.8.2/6.0.3 (available in About System) KDE Plasma Version: 6.0.3 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.3 ADDITIONAL INFORMATION The current work-around is to disable the Maximize and Tile options. -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 485006] New: I can't create a new profile
https://bugs.kde.org/show_bug.cgi?id=485006 Bug ID: 485006 Summary: I can't create a new profile Classification: Applications Product: yakuake Version: 24.02.1 Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: h...@kde.org Reporter: pablo.diaz.aco...@gmail.com Target Milestone: --- Created attachment 168119 --> https://bugs.kde.org/attachment.cgi?id=168119=edit Screenshot showing the validation error SUMMARY When I try to create a profile in the Create New Profile form, a validation error appears regardless of the profile name I put. STEPS TO REPRODUCE 1. Open Manage Profiles window. 2. Click New... button. 3. Set a valid Profile name. 4. Click OK button. OBSERVED RESULT The validation error "Profile name exceeded maximum allowed length (-9)." appears and prevents profile creation. EXPECTED RESULT The profile is created properly SOFTWARE/OS VERSIONS Linux/KDE Plasma: ArchLinux 6.8.2-arch2-1 (64-bit) KDE Plasma Version: 6.0.3 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.3 ADDITIONAL INFORMATION Konsole is not installed -- You are receiving this mail because: You are watching all bug changes.
[krdc] [Bug 482950] KRDC RDP Blue screen shows nothing
https://bugs.kde.org/show_bug.cgi?id=482950 --- Comment #5 from pablo --- (In reply to Tony Murray from comment #2) > Duplicate of 481968 and 482836, I'm going to leave this open until 24.02.1 > is released next week which contains the fix. Using 24.02.1, I still have the issue. Please let me know if there are additional details that I can provide. Thank you -- You are receiving this mail because: You are watching all bug changes.
[krdc] [Bug 482950] KRDC RDP Blue screen shows nothing
https://bugs.kde.org/show_bug.cgi?id=482950 pablo changed: What|Removed |Added CC||pa...@blueoakdb.com -- You are receiving this mail because: You are watching all bug changes.
[krdc] [Bug 484608] KRDC 24.02 doesn't connect to MacOS via VNC anymore
https://bugs.kde.org/show_bug.cgi?id=484608 pablo changed: What|Removed |Added CC||pa...@blueoakdb.com --- Comment #1 from pablo --- Have you tried any other VNC viewer? My current work-around is to use TigerVNC to reach a Linux remote. I'm curious if it's the same for you. I'm also on Tumbleweed. For reference, here's the Tumbleweed bug reference - https://bugzilla.opensuse.org/show_bug.cgi?id=1222019 -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 481774] New: "Download New Kdenlive Title Template" window in the background and not clickable
https://bugs.kde.org/show_bug.cgi?id=481774 Bug ID: 481774 Summary: "Download New Kdenlive Title Template" window in the background and not clickable Classification: Applications Product: kdenlive Version: 23.08.4 Platform: macOS (DMG) OS: macOS Status: REPORTED Severity: normal Priority: NOR Component: User Interface Assignee: j...@kdenlive.org Reporter: pgilfernan...@gmail.com Target Milestone: --- Created attachment 166065 --> https://bugs.kde.org/attachment.cgi?id=166065=edit screenshot SUMMARY When creating a new Title clip and pressing in the "Download new title clip" button, the popup window opens behind the actual Title clip one and is not active, even if you move to the side the "Title clip" one you can't make the Download popup to active *** 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 *** STEPS TO REPRODUCE 1. open Kdenlive 2. create a new Title clip 3. press "download new title clip" button 4. move the "Title clip" window to the side and try to access the Download one... OBSERVED RESULT That window is not accessible EXPECTED RESULT The "Download New Kdenlive Title Template" popup should be in the front and active SOFTWARE/OS VERSIONS macOS: 12.6.7 Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 469022] Selected area bleaches text
https://bugs.kde.org/show_bug.cgi?id=469022 --- Comment #56 from pablo --- (In reply to A. R. Kristiansen from comment #55) > Just tried in the X11 session, and I can't reproduce there. Hi, Thanks for your experiments. I'd suggest opening a separate bug under Wayland as what you're experiencing is different than this defect. Which, for me, I haven't experienced in a long time. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 474832] SDDM greeter does not launch when logging out.
https://bugs.kde.org/show_bug.cgi?id=474832 --- Comment #7 from Pablo --- (In reply to Nate Graham from comment #5) > Aha, that makes this Bug 467547. Can you confirm that the version of SDDM > you have on your system is NOT 0.20 or newer? Actually, I remember that recently there was an update in Debian for KDE packages and I remember the SDDM update was included. And the error was still persistent after that update. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 474832] SDDM greeter does not launch when logging out.
https://bugs.kde.org/show_bug.cgi?id=474832 --- Comment #6 from Pablo --- (In reply to Nate Graham from comment #5) > Aha, that makes this Bug 467547. Can you confirm that the version of SDDM > you have on your system is NOT 0.20 or newer? > > *** This bug has been marked as a duplicate of bug 467547 *** Thanks for reply. I switched to gnome greeter and I did uninstall SDDM so there is probably now way of telling the SDDM version now (?) It was SDDM that came with Debian 12 + KDE Plasma only netinstaller. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 474832] SDDM greeter does not launch when logging out.
https://bugs.kde.org/show_bug.cgi?id=474832 --- Comment #4 from Pablo --- (In reply to Nate Graham from comment #3) > So to be clear, nothing is actually crashing? Alright, sorry. So it seems that SDDM greeter is not starting. What I should do now? I have changed summary. I would edit importance too, but I am not able to do so now. Should I change "product" or "component" fields? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 474832] SDDM greeter does not launch when logging out.
https://bugs.kde.org/show_bug.cgi?id=474832 Pablo changed: What|Removed |Added Summary|Plasma Crash when logging |SDDM greeter does not |out.|launch when logging out. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 474832] Plasma Crash when logging out.
https://bugs.kde.org/show_bug.cgi?id=474832 --- Comment #2 from Pablo --- (In reply to Nate Graham from comment #1) > Is there actually a crash, whose backtrace you didn't attach? Sorry, I am still new into Linux. I used Ubuntu for about a year and recently switched to Debian 12. I did log in and out few times today to force some lines to appear in shell after logging out (things that I saw earlier, but did not attach backtrace to them - hope that it will shed some more light on the matter). P.S. Please let me know if there is any sensitive info that I should edit out. P.S.2: In addition to of what is visible below, there was a lot of repeating info about hardware random number generator failing (AMD CPU's related well known bug). I did cut it out again to let you read more easily (sorry it still a lot of lines, I was even thinking about editing out lines that appear multiple times, but probably it will be better to leave them as they are). user@computer:~$ dbus-run-session startplasma-wayland dbus-daemon[8263]: [session uid=1000 pid=8263] Activating service name='org.freedesktop.systemd1' requested by ':1.0' (uid=1000 pid=8264 comm="startplasma-wayland") dbus-daemon[8263]: [session uid=1000 pid=8263] Activated service 'org.freedesktop.systemd1' failed: Process org.freedesktop.systemd1 exited with status 1 dbus-daemon[8263]: [session uid=1000 pid=8263] Activating service name='org.freedesktop.systemd1' requested by ':1.0' (uid=1000 pid=8264 comm="startplasma-wayland") dbus-daemon[8263]: [session uid=1000 pid=8263] Activated service 'org.freedesktop.systemd1' failed: Process org.freedesktop.systemd1 exited with status 1 dbus-daemon[8263]: [session uid=1000 pid=8263] Activating service name='org.freedesktop.systemd1' requested by ':1.0' (uid=1000 pid=8264 comm="startplasma-wayland") dbus-daemon[8263]: [session uid=1000 pid=8263] Activated service 'org.freedesktop.systemd1' failed: Process org.freedesktop.systemd1 exited with status 1 dbus-daemon[8263]: [session uid=1000 pid=8263] Activating service name='org.freedesktop.systemd1' requested by ':1.0' (uid=1000 pid=8264 comm="startplasma-wayland") dbus-daemon[8263]: [session uid=1000 pid=8263] Activated service 'org.freedesktop.systemd1' failed: Process org.freedesktop.systemd1 exited with status 1 dbus-daemon[8263]: [session uid=1000 pid=8263] Activating service name='org.freedesktop.systemd1' requested by ':1.0' (uid=1000 pid=8264 comm="startplasma-wayland") dbus-daemon[8263]: [session uid=1000 pid=8263] Activated service 'org.freedesktop.systemd1' failed: Process org.freedesktop.systemd1 exited with status 1 dbus-daemon[8263]: [session uid=1000 pid=8263] Activating service name='org.freedesktop.systemd1' requested by ':1.0' (uid=1000 pid=8264 comm="startplasma-wayland") dbus-daemon[8263]: [session uid=1000 pid=8263] Activated service 'org.freedesktop.systemd1' failed: Process org.freedesktop.systemd1 exited with status 1 dbus-daemon[8263]: [session uid=1000 pid=8263] Activating service name='org.freedesktop.systemd1' requested by ':1.0' (uid=1000 pid=8264 comm="startplasma-wayland") dbus-daemon[8263]: [session uid=1000 pid=8263] Activated service 'org.freedesktop.systemd1' failed: Process org.freedesktop.systemd1 exited with status 1 dbus-daemon[8263]: [session uid=1000 pid=8263] Activating service name='org.kde.KSplash' requested by ':1.0' (uid=1000 pid=8264 comm="startplasma-wayland") dbus-daemon[8263]: [session uid=1000 pid=8263] Activating service name='org.freedesktop.systemd1' requested by ':1.0' (uid=1000 pid=8264 comm="startplasma-wayland") dbus-daemon[8263]: [session uid=1000 pid=8263] Activated service 'org.freedesktop.systemd1' failed: Process org.freedesktop.systemd1 exited with status 1 dbus-daemon[8263]: [session uid=1000 pid=8263] Activating service name='org.freedesktop.systemd1' requested by ':1.3' (uid=1000 pid=8291 comm="/usr/bin/kwin_wayland_wrapper --xwayland") dbus-daemon[8263]: [session uid=1000 pid=8263] Activated service 'org.freedesktop.systemd1' failed: Process org.freedesktop.systemd1 exited with status 1 kdeinit5: preparing to launch '/usr/lib/x86_64-linux-gnu/libexec/kf5/klauncher' kdeinit5: Launched KLauncher, pid = 8302, result = 0 No backend specified, automatically choosing drm OpenGL vendor string: AMD OpenGL renderer string: AMD Radeon RX 6600 (navi23, LLVM 15.0.6, DRM 3.49, 6.1.0-12-amd64) OpenGL version string: 4.6 (Core Profile) Mesa 22.3.6 OpenGL shading language version string: 4.60 Driver: Unknown GPU class: Unknown OpenGL version: 4.6 GLSL version: 4.60 Mesa version: 22.3.6 Linux kernel version: 6.1 Requires strict binding:no GLSL shaders: yes Texture NPOT sup
[plasmashell] [Bug 474832] New: Plasma Crash when logging out.
https://bugs.kde.org/show_bug.cgi?id=474832 Bug ID: 474832 Summary: Plasma Crash when logging out. Classification: Plasma Product: plasmashell Version: 5.27.5 Platform: Debian stable OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: Session Management Assignee: plasma-b...@kde.org Reporter: z273a...@duck.com Target Milestone: 1.0 SUMMARY Plasma crashes when trying to log out from user session. Any GUI not visible (SDDM), only black screen and cursor. I have to press Ctrl+Alt+F3 to login in through terminal and then manually start GUI by running command "dbus-run-session startplasma-wayland". When trying to repeat this process (logging out) again I see terminal only (not any GUI again) and I am not logged out (can run dbus-run-session startplasma-wayland again without need to type in user name and password). The same behavior overall can be observed even when logging in (after OS start/restart) into X11 session instead of Wayland session and then repeating whole process. It does not happen when logging in for the first time after start of OS. STEPS TO REPRODUCE 1. Choose "Log Out" from user session through Application Launcher. 2. Confirm "OK". OBSERVED RESULT Only Black Screen with cursor visible. EXPECTED RESULT SDDM visible with option to choose user and log in again. SOFTWARE/OS VERSIONS Linux: Debian 12 (Stable) KDE Plasma Version: 5.27.5 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 ADDITIONAL INFORMATION Text from Shell: user@computer:~$ dbus-run-session startplasma-wayland dbus-daemon[6277]: [session uid=1000 pid=6277] Activating service name='org.freedesktop.systemd1' requested by ':1.0' (uid=1000 pid=6278 comm="startplasma-wayland") dbus-daemon[6277]: [session uid=1000 pid=6277] Activated service 'org.freedesktop.systemd1' failed: Process org.freedesktop.systemd1 exited with status 1 dbus-daemon[6277]: [session uid=1000 pid=6277] Activating service name='org.freedesktop.systemd1' requested by ':1.0' (uid=1000 pid=6278 comm="startplasma-wayland") dbus-daemon[6277]: [session uid=1000 pid=6277] Activated service 'org.freedesktop.systemd1' failed: Process org.freedesktop.systemd1 exited with status 1 dbus-daemon[6277]: [session uid=1000 pid=6277] Activating service name='org.freedesktop.systemd1' requested by ':1.0' (uid=1000 pid=6278 comm="startplasma-wayland") dbus-daemon[6277]: [session uid=1000 pid=6277] Activated service 'org.freedesktop.systemd1' failed: Process org.freedesktop.systemd1 exited with status 1 dbus-daemon[6277]: [session uid=1000 pid=6277] Activating service name='org.freedesktop.systemd1' requested by ':1.0' (uid=1000 pid=6278 comm="startplasma-wayland") dbus-daemon[6277]: [session uid=1000 pid=6277] Activated service 'org.freedesktop.systemd1' failed: Process org.freedesktop.systemd1 exited with status 1 dbus-daemon[6277]: [session uid=1000 pid=6277] Activating service name='org.freedesktop.systemd1' requested by ':1.0' (uid=1000 pid=6278 comm="startplasma-wayland") dbus-daemon[6277]: [session uid=1000 pid=6277] Activated service 'org.freedesktop.systemd1' failed: Process org.freedesktop.systemd1 exited with status 1 dbus-daemon[6277]: [session uid=1000 pid=6277] Activating service name='org.freedesktop.systemd1' requested by ':1.0' (uid=1000 pid=6278 comm="startplasma-wayland") dbus-daemon[6277]: [session uid=1000 pid=6277] Activated service 'org.freedesktop.systemd1' failed: Process org.freedesktop.systemd1 exited with status 1 dbus-daemon[6277]: [session uid=1000 pid=6277] Activating service name='org.freedesktop.systemd1' requested by ':1.0' (uid=1000 pid=6278 comm="startplasma-wayland") dbus-daemon[6277]: [session uid=1000 pid=6277] Activated service 'org.freedesktop.systemd1' failed: Process org.freedesktop.systemd1 exited with status 1 dbus-daemon[6277]: [session uid=1000 pid=6277] Activating service name='org.kde.KSplash' requested by ':1.0' (uid=1000 pid=6278 comm="startplasma-wayland") dbus-daemon[6277]: [session uid=1000 pid=6277] Activating service name='org.freedesktop.systemd1' requested by ':1.0' (uid=1000 pid=6278 comm="startplasma-wayland") dbus-daemon[6277]: [session uid=1000 pid=6277] Activated service 'org.freedesktop.systemd1' failed: Process org.freedesktop.systemd1 exited with status 1 dbus-daemon[6277]: [session uid=1000 pid=6277] Activating service name='org.freedesktop.systemd1' requested by ':1.3' (uid=1000 pid=6304 comm="/usr/bin/kwin_wayland_wrapper --xwayland") dbus-daemon[6277]: [session uid=1000 pid=6277] Activated service 'org.freedesktop.systemd1' failed: Process org.freedesktop.systemd1 exited with status 1 kdeinit5: preparing to launch '/usr/lib/x86_64-linux-gnu/libexec/kf5/klauncher' kdeinit5: Launched KLauncher, pid = 6317, result = 0 No backend specified, automatically choosing drm OpenGL vendor string: AMD OpenGL renderer string: AMD Radeon
[systemsettings] [Bug 474022] Double "Input Method" (fcitx configuration tool) menu entry under "Regional Settings" when using Sidebar View.
https://bugs.kde.org/show_bug.cgi?id=474022 Pablo changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #2 from Pablo --- FIXED I did uninstall package "kde-config-fcitx" and the second menu entry did disappear. I already have other package used for fcitx5 configuration: "fcitx5-config-qt". Both packages are invoked by use of "fcitx5-configtool" command which then "will automatically detect your desktop environment and launch the corresponding implementation within fcitx5-configtool package. " as described here: https://fcitx-im.org/wiki/Special:MyLanguage/Configtool_(Fcitx_5). But still I cannot configure Fcitx5 through "System Settings" Menu. "Input Method" menu looks like the old one provided with Fcitx4 (though I did uninstall old Fcitx and I did purge it), and fields in window are empty, buttons do not react on mouse-clicking. I have to launch "fcitx5-configtool" through Terminal to configure Fcitx5 successfully. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 474022] Double "Input Method" (fcitx configuration tool) menu entry under "Regional Settings" when using Sidebar View.
https://bugs.kde.org/show_bug.cgi?id=474022 --- Comment #1 from Pablo --- Created attachment 161326 --> https://bugs.kde.org/attachment.cgi?id=161326=edit Screenshot 2 Screenshots -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 474022] New: Double "Input Method" (fcitx configuration tool) menu entry under "Regional Settings" when using Sidebar View.
https://bugs.kde.org/show_bug.cgi?id=474022 Bug ID: 474022 Summary: Double "Input Method" (fcitx configuration tool) menu entry under "Regional Settings" when using Sidebar View. Classification: Applications Product: systemsettings Version: 5.27.5 Platform: Debian stable OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_regionandlang Assignee: plasma-b...@kde.org Reporter: z273a...@duck.com CC: hanyo...@protonmail.com Target Milestone: --- Double "Input Method" (fcitx configuration tool) menu entry under "Regional Settings" when using Sidebar View. STEPS TO REPRODUCE 1. Go to "System Settings" and use "Sidebar View". 2. Then go to "Regional Settings". OBSERVED RESULT Doubled "Input Method" menu entry visible on the Sidebar (Only when using sidebar view, when using "Icon View" only one "Input Method" entry visible). When still in "System Settings" and move cursor on "Regional Settings" entry, there is an information "Contain 5 Items". EXPECTED RESULT Single "Input Method" menu entry visible on the Sidebar. When still in "System Settings" and move cursor on "Regional Settings" entry, there should be an information "Contain 4 Items". SOFTWARE/OS VERSIONS Linux: Debian 12 with Wayland KDE Plasma Version: 5.27.5 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 473246] New: Noise filter layer area issues and not working properly after flattened
https://bugs.kde.org/show_bug.cgi?id=473246 Bug ID: 473246 Summary: Noise filter layer area issues and not working properly after flattened Classification: Applications Product: krita Version: 5.1.5 Platform: Ubuntu OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Filter Layers Assignee: krita-bugs-n...@kde.org Reporter: pablojmurat...@gmail.com Target Milestone: --- SUMMARY *** The "Random Noise" filter layer is not working properly. The are the noise is applied is not defined properly and changes when hiding and showing the filter layer. The inherit alpha option of the filter layer doesn´t affect the area. Flattening the noise filter transforms the layer into a paint layer, but it's transparency still hides the layers below in the same group. After many tests, it seems when flattening the noise filter layer, it doesn´t show updates to layers below when inside a group, all becomes normal after the layer is moved again. *** STEPS TO REPRODUCE 1. Create a new document 2. Fill the document with a clear color and random lines of a different color (this will help verify noise and transparency later) 3. Create a new paint layer. 4. Select a square area and fill with another clear color, unselect the area. 5. Select the layer containing the painted square and create a group. 6. Add a "Random Noise filter" layer with Level 50 over the layer with the square inside the group. 7. VERIFY: the are of the filter layer is incorrect and changes when hiding or showing the filter layer. 8. Hide the painted layer with the lines and the painted layer with the square. 9. Flatten the noise filter layer. 10. Show both painted layers 11. VERIFY: The painted layer outside the group is visible, but the painted layer inside the group and below the filter layer isn´t 12. VERIFY: Move the flattened filter layer (now a paint layer) to verify it has transparency 13. Hide the flattened filter layer 14. VERIFY: the layer containing the square and inside the group becomes visible (this happens even with more than one paint layer inside the group). 15. Show the flattened filter layer and turn on it's inherit alpha option. 16. Paint something on the layer with the square. 17. VERIFY: the layer with the square is still hidden and changes aren't visble. 17. Move the flattened filter layer. 18. VERIFY: now the layer with the square becomes visible and works as expected. 19. VERIFY: further changes in the square layer become visible. OBSERVED RESULT The filter layer doesn´t affect only the area of the painted layers below ( as is the case of the "Halftone" layer for example, which works ok). EXPECTED RESULT The Noise filter layer should affect only the areas of painted layers below (or the alpha lock should do) After flattening the Noise filter layer, transparency of the flattened layer shouldn´t hide the layers below in the same group. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Ubuntu 22.04.3 LTS ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 472062] New: Unable to select layer by pressing R and clicking on part of an image if the layer is locked
https://bugs.kde.org/show_bug.cgi?id=472062 Bug ID: 472062 Summary: Unable to select layer by pressing R and clicking on part of an image if the layer is locked Classification: Applications Product: krita Version: 5.1.5 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Layer Stack Assignee: krita-bugs-n...@kde.org Reporter: pablojmurat...@gmail.com 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 *** STEPS TO REPRODUCE 1. Create two layers 2. Draw something on each layer 3. Verify that holding down R and clicking the drawing on an unlocked and unselected layer, that layer is selected 3. Block both layers 4. Hold down R and click on the drawing of the unselected and locked layer OBSERVED RESULT The layer that contains the clicked image while pressing R is not selected. EXPECTED RESULT The layer that contains the clicked image while pressing R should be selected SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Ubuntu 22.04.2 (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 470486] New: Can't update system
https://bugs.kde.org/show_bug.cgi?id=470486 Bug ID: 470486 Summary: Can't update system Classification: Applications Product: Discover Version: 5.27.4 Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Updates (interactive) Assignee: plasma-b...@kde.org Reporter: pbuy...@gmail.com CC: aleix...@kde.org Target Milestone: --- Dependency resolution failed:The following packages have unmet dependencies: kdesdk-devenv-dependencies: Depends: libkf5wallet-dev but it is not going to be installed libkf5kdelibs4support-dev: Depends: libkf5wallet-dev (= 5.51) but it is not going to be installed libkf5khtml-dev: Depends: libkf5wallet-dev (= 5.51.0~) but it is not going to be installed libkf5mailtransport-dev: Depends: libkf5wallet-dev (= 5.19.0~) but it is not going to be installed -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 469022] Selected area bleaches text
https://bugs.kde.org/show_bug.cgi?id=469022 --- Comment #45 from pablo --- (In reply to jonzn4SUSE from comment #43) > Created attachment 159258 [details] > nvidia drivers installed > > Just installed updated version Spectacle version 23.04.1 and still have the > issue with or without nvidia drivers installed. My initial thinking was not that there was an issue with the Nvidia driver but in my case, my Intel driver. I thought this because my work-around is to force spectacle to use my Nvidia card, not my (current) default Intel. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 469022] Selected area bleaches text
https://bugs.kde.org/show_bug.cgi?id=469022 --- Comment #42 from pablo --- (In reply to jonzn4SUSE from comment #41) > Here is my other laptop with the issue. > > [ snipped ] > > I have also tried a 2nd user and still have the issue on this machine, but > it works for all users in Wayland. The above is a very interesting (at least to me) data point. It would not suggest a graphics driver issue. However, this technology stack is not my area of expertise. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 469022] Selected area bleaches text
https://bugs.kde.org/show_bug.cgi?id=469022 --- Comment #40 from pablo --- (In reply to jonzn4SUSE from comment #39) > (In reply to pablo from comment #33) > > (In reply to jonzn4SUSE from comment #31) > > > Graphics: > > > Device-1: Intel HD Graphics P630 driver: i915 v: kernel > > > Device-2: NVIDIA GP104GLM [Quadro P4000 Mobile] driver: N/A > > > > Have you tried forcing spectacle to run on the Nvidia card? Please see > > comment #16 > > Still have the issue. Did I need to log out or reboot after running? Hi, With my dual GPU laptop using openSUSE Tumbleweed, I use /prime-select/ to offload the graphics to my Nvidia card - see https://en.opensuse.org/SDB:NVIDIA_SUSE_Prime -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 469022] Selected area bleaches text
https://bugs.kde.org/show_bug.cgi?id=469022 --- Comment #33 from pablo --- (In reply to jonzn4SUSE from comment #31) > Graphics: > Device-1: Intel HD Graphics P630 driver: i915 v: kernel > Device-2: NVIDIA GP104GLM [Quadro P4000 Mobile] driver: N/A Have you tried forcing spectacle to run on the Nvidia card? Please see comment #16 -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 469022] Selected area bleaches text
https://bugs.kde.org/show_bug.cgi?id=469022 --- Comment #29 from pablo --- (In reply to pier andre from comment #28) > I don't know if it is useful to say that it is not related to a driver > issue, in the same laptop I tried with another user and the problem did not > happen. Hi Pier, To confirm, you are saying that you created a new vanilla, Linux User spectacle works but it does not work with your existing user? Both using say X11 or Wayland? What graphic card(s) do you have? Below is my set up: $ inxi -G Graphics: Device-1: Intel CometLake-H GT2 [UHD Graphics] driver: i915 v: kernel Device-2: NVIDIA TU106M [GeForce RTX 2060 Max-Q] driver: nvidia v: 525.116.04 Device-3: Realtek Integrated_Webcam_HD driver: uvcvideo type: USB Display: x11 server: X.Org v: 21.1.8 with: Xwayland v: 23.1.1 driver: X: loaded: modesetting,nvidia dri: iris gpu: i915 resolution: 1: 2560x1440~60Hz 2: N/A API: OpenGL v: 4.6 Mesa 23.0.3 renderer: Mesa Intel UHD Graphics (CML GT2) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 467574] kwin_screencast: Dropping a screencast frame because the compositor is slow
https://bugs.kde.org/show_bug.cgi?id=467574 Pablo Wagner changed: What|Removed |Added CC||pablowag...@tutanota.com -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 469022] Selected area bleaches text
https://bugs.kde.org/show_bug.cgi?id=469022 --- Comment #27 from pablo --- Hi Noah, It looks like my test yesterday was wrong. The problem still exists unless I use my Nvidia card. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 469022] Selected area bleaches text
https://bugs.kde.org/show_bug.cgi?id=469022 --- Comment #26 from pablo --- While I see in Bug 470052 the problem is reported against version 24.04.1 of spectacle, I no longer have the issue. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 469629] New: Spectacle don't start
https://bugs.kde.org/show_bug.cgi?id=469629 Bug ID: 469629 Summary: Spectacle don't start Classification: Applications Product: Spectacle Version: unspecified Platform: unspecified OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: General Assignee: noaha...@gmail.com Reporter: pablosanchezl...@gmail.com CC: k...@david-redondo.de Target Milestone: --- Application: spectacle (23.07.70) Qt Version: 5.15.9 Frameworks Version: 5.106.0 Operating System: Linux 6.3.1-1-default x86_64 Windowing System: Wayland Distribution: "openSUSE Tumbleweed" DrKonqi: 5.27.5 [KCrashBackend] -- Information about the crash: Spectacle crash on start, using the unstable repositories The crash can be reproduced every time. -- Backtrace: Application: Spectacle (spectacle), signal: Segmentation fault [KCrash Handler] #4 0x7f2f1eabeb00 in QQmlType::QQmlType(QQmlType const&) () from /lib64/libQt5Qml.so.5 #5 0x7f2f1eb25525 in ?? () from /lib64/libQt5Qml.so.5 #6 0x7f2f1eb283c0 in ?? () from /lib64/libQt5Qml.so.5 #7 0x7f2f1eb285d9 in ?? () from /lib64/libQt5Qml.so.5 #8 0x7f2f1eb285d9 in ?? () from /lib64/libQt5Qml.so.5 #9 0x7f2f1eb2904d in ?? () from /lib64/libQt5Qml.so.5 #10 0x7f2f1eb23cc7 in ?? () from /lib64/libQt5Qml.so.5 #11 0x7f2f1ea73ae5 in ?? () from /lib64/libQt5Qml.so.5 #12 0x7f2f1ea79c98 in ?? () from /lib64/libQt5Qml.so.5 #13 0x7f2f1ea67e35 in QQmlDataBlob::tryDone() () from /lib64/libQt5Qml.so.5 #14 0x7f2f1eac7c3c in QQmlTypeLoader::setData(QQmlDataBlob*, QQmlDataBlob::SourceCodeData const&) () from /lib64/libQt5Qml.so.5 #15 0x7f2f1eac8352 in QQmlTypeLoader::setData(QQmlDataBlob*, QString const&) () from /lib64/libQt5Qml.so.5 #16 0x7f2f1eac91cf in QQmlTypeLoader::loadThread(QQmlDataBlob*) () from /lib64/libQt5Qml.so.5 #17 0x7f2f1eac963c in QQmlTypeLoader::load(QQmlDataBlob*, QQmlTypeLoader::Mode) () from /lib64/libQt5Qml.so.5 #18 0x7f2f1eac9f10 in QQmlTypeLoader::getType(QUrl const&, QQmlTypeLoader::Mode) () from /lib64/libQt5Qml.so.5 #19 0x7f2f1ea78ed4 in ?? () from /lib64/libQt5Qml.so.5 #20 0x7f2f1ea7b3a0 in ?? () from /lib64/libQt5Qml.so.5 #21 0x7f2f1eac7ed9 in QQmlTypeLoader::setData(QQmlDataBlob*, QQmlDataBlob::SourceCodeData const&) () from /lib64/libQt5Qml.so.5 #22 0x7f2f1eac8352 in QQmlTypeLoader::setData(QQmlDataBlob*, QString const&) () from /lib64/libQt5Qml.so.5 #23 0x7f2f1eac91cf in QQmlTypeLoader::loadThread(QQmlDataBlob*) () from /lib64/libQt5Qml.so.5 #24 0x7f2f1ea8359d in ?? () from /lib64/libQt5Qml.so.5 #25 0x7f2f1eb4223c in ?? () from /lib64/libQt5Qml.so.5 #26 0x7f2f1eb42982 in ?? () from /lib64/libQt5Qml.so.5 #27 0x7f2f1f5a51ae in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib64/libQt5Widgets.so.5 #28 0x7f2f1dcec978 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib64/libQt5Core.so.5 #29 0x7f2f1dceff71 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /lib64/libQt5Core.so.5 #30 0x7f2f1dd46713 in ?? () from /lib64/libQt5Core.so.5 #31 0x7f2f1c2488d8 in g_main_context_dispatch () from /lib64/libglib-2.0.so.0 #32 0x7f2f1c248ce8 in ?? () from /lib64/libglib-2.0.so.0 #33 0x7f2f1c248d7c in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #34 0x7f2f1dd45f26 in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #35 0x7f2f1dceb40b in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #36 0x7f2f1db0294e in QThread::exec() () from /lib64/libQt5Core.so.5 #37 0x7f2f1eb41ef5 in ?? () from /lib64/libQt5Qml.so.5 #38 0x7f2f1db03b7d in ?? () from /lib64/libQt5Core.so.5 #39 0x7f2f1d492ab4 in start_thread () from /lib64/libc.so.6 #40 0x7f2f1d519b60 in clone3 () from /lib64/libc.so.6 Thread 11 (Thread 0x7f2ef77fe6c0 (LWP 21154) "spectacle:sh5"): #1 0x7f2f1d491da0 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libc.so.6 #2 0x7f2f060c7bfb in ?? () from /usr/lib64/dri/iris_dri.so #3 0x7f2f0610eb37 in ?? () from /usr/lib64/dri/iris_dri.so #4 0x7f2f1d492ab4 in start_thread () from /lib64/libc.so.6 #5 0x7f2f1d519b60 in clone3 () from /lib64/libc.so.6 Thread 10 (Thread 0x7f2ef7fff6c0 (LWP 21153) "spectacle:sh4"): #1 0x7f2f1d491da0 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libc.so.6 #2 0x7f2f060c7bfb in ?? () from /usr/lib64/dri/iris_dri.so #3 0x7f2f0610eb37 in ?? () from /usr/lib64/dri/iris_dri.so #4 0x7f2f1d492ab4 in start_thread () from /lib64/libc.so.6 #5 0x7f2f1d519b60 in clone3 () from /lib64/libc.so.6 Thread 9 (Thread 0x7f2efc9ba6c0 (LWP 21152) "spectacle:sh3"): #1 0x7f2f1d491da0 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libc.so.6 #2 0x7f2f060c7bfb in ?? () from /usr/lib64/dri/iris_dri.so #3
[plasmashell] [Bug 469016] Plasma panel visually (but not functionally) freezing with Wayland+Nvidia
https://bugs.kde.org/show_bug.cgi?id=469016 Pablo Wagner changed: What|Removed |Added CC||pablowag...@tutanota.com --- Comment #7 from Pablo Wagner --- I don't think it's limited to nvidia GPUs (assuming it's the same bug), since I'm also seeing this in a Intel laptop. Replying this comment from #469175: SOFTWARE/OS VERSIONS Operating System: openSUSE tumbleweed KDE Plasma Version: 5.27.4 KDE Frameworks Version: 5.105.0 Qt Version: 5.15.9 Kernel Version: 6.2.12-1-default (64 bits) Graphics Platform: Wayland Processors: 8 × 11th Gen Intel® Core™ i5-1135G7 @ 2.40GHz Memory: 15,4 GiB of RAM Graphics Processor: Mesa Intel® Xe Graphics -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 469175] Panel with taskbar freezes visually but remains operational
https://bugs.kde.org/show_bug.cgi?id=469175 Pablo Wagner changed: What|Removed |Added CC||pablowag...@tutanota.com --- Comment #1 from Pablo Wagner --- Another me-too: SOFTWARE/OS VERSIONS Operating System: openSUSE tumbleweed KDE Plasma Version: 5.27.4 KDE Frameworks Version: 5.105.0 Qt Version: 5.15.9 Kernel Version: 6.2.12-1-default (64 bits) Graphics Platform: Wayland Processors: 8 × 11th Gen Intel® Core™ i5-1135G7 @ 2.40GHz Memory: 15,4 GiB of RAM Graphics Processor: Mesa Intel® Xe Graphics -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 469022] Selected area bleaches text
https://bugs.kde.org/show_bug.cgi?id=469022 --- Comment #22 from pablo --- (In reply to Noah Davis from comment #21) > I used to use an Nvidia optimus laptop and trying to do things with the > Nvidia card, especially after kernel updates, was always such a pain. FWIW, which isn't much as in it's only one data point, this is the first time I've had an issue. It took a bit of research to get the right environment variables to offload. Once sorted though, it's been steady. Except for this bugger of an issue. :) Again, thank you so much for helping me out. I truly appreciate it! -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 469022] Selected area bleaches text
https://bugs.kde.org/show_bug.cgi?id=469022 --- Comment #20 from pablo --- (In reply to Noah Davis from comment #18) > > It's my Nvidia Optimus setting. When I force `spectacle` to run on my > > Nvidia card, it's all good - see the attached blurry picture. > > So you have to use Nvidia for Spectacle to work right? That's right. For unknown reasons, the Intel iGPU is unhappy. Which is very funky. I too am on openSUSE TW. I may dig into this issue as time permits. > Ouch. Not sure why there's an ouch. It's Linux. There are always edge cases that we work-around.:) -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 469022] Selected area bleaches text
https://bugs.kde.org/show_bug.cgi?id=469022 --- Comment #17 from pablo --- If you're okay with it, I'd like to close this defect as RESOLVED. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 469022] Selected area bleaches text
https://bugs.kde.org/show_bug.cgi?id=469022 --- Comment #16 from pablo --- Created attachment 158472 --> https://bugs.kde.org/attachment.cgi?id=158472=edit Mucho better! Hi Noah, Thank you so much for your help! I've figured it out. It's my Nvidia Optimus setting. When I force `spectacle` to run on my Nvidia card, it's all good - see the attached blurry picture. Here's a shell script that I cobbled together to run applications on my dGPU: ::: run_on_nvidia ::: #!/bin/bash # # Run GPU intensive applications via our Nvidia card # export __NV_PRIME_RENDER_OFFLOAD=1 export __VK_LAYER_NV_optimus="NVIDIA_only" export __NV_PRIME_RENDER_OFFLOAD_PROVIDER="NVIDIA-G0" export __GLX_VENDOR_LIBRARY_NAME="nvidia" exec "$@" # Never reached exit 0 -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 469022] Selected area bleaches text
https://bugs.kde.org/show_bug.cgi?id=469022 --- Comment #13 from pablo --- Would you mind running a test that includes the /KDE System Settings/ in /Icon View/? Specifically, do the icons blanch after selecting the /Capture Mode/ > /Rectangular Region/? Thx a bundle! -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 469022] Selected area bleaches text
https://bugs.kde.org/show_bug.cgi?id=469022 --- Comment #12 from pablo --- Thank you for your test results. The biggest difference I see is that in your example, I can see the spectacle controls. In my case, they're white-ish which makes them extremely difficult to discern. Is it possibly a GPU issue? This rig is an Optimus Nvidia laptop. I have it set in /Offset/ mode. The primary GPU is the iGPU, Intel. What OS are you using? Perhaps I can stand up a VM to run a quick test. I'm open to any ideas to test things out. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 469022] Selected area bleaches text
https://bugs.kde.org/show_bug.cgi?id=469022 --- Comment #9 from pablo --- Created attachment 158465 --> https://bugs.kde.org/attachment.cgi?id=158465=edit Vanilla Linux user test Hi, Attached are the results of using a new, vanilla Linux user. The /with-effects/ sub-directory is the true, vanilla Linux user. The /with-no-effects/ sub-directory contains the test results with all the effects disabled. I am having to use my phone's camera to take the pictures. I try to keep it the same distance. ::: Contents ::: $ tar -vcf vanilla_Linux_user.tar vanilla_Linux_user vanilla_Linux_user/ vanilla_Linux_user/with-effects/ vanilla_Linux_user/with-effects/01_b4.png vanilla_Linux_user/with-effects/02_b4_selection.png vanilla_Linux_user/with-effects/03_selection.png vanilla_Linux_user/with-no-effects/ vanilla_Linux_user/with-no-effects/03_selection.png vanilla_Linux_user/with-no-effects/02_b4_selection.png vanilla_Linux_user/with-no-effects/01_b4.png -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 469022] Selected area bleaches text
https://bugs.kde.org/show_bug.cgi?id=469022 --- Comment #8 from pablo --- I'm going to try to rule out my own environment by creating a vanilla Linux user. I'll incrementally add to it: 1) Vanilla 2) Disable all effects 3) Switch to dark theme I should have thought of that before submitting the bug. Sorry about that ... be right back. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 469022] Selected area bleaches text
https://bugs.kde.org/show_bug.cgi?id=469022 --- Comment #7 from pablo --- Created attachment 158464 --> https://bugs.kde.org/attachment.cgi?id=158464=edit Region is visible with all desktop effects disabled -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 469022] Selected area bleaches text
https://bugs.kde.org/show_bug.cgi?id=469022 --- Comment #6 from pablo --- Created attachment 158463 --> https://bugs.kde.org/attachment.cgi?id=158463=edit After selecting /Rectangular Region/ option Hi Noah, Good call. I hadn't thought of that being an issue. I disabled all effects and for good measure, re-logged in. The bleaching is still there but now it's .. different. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 469022] Selected area bleaches text
https://bugs.kde.org/show_bug.cgi?id=469022 --- Comment #3 from pablo --- Created attachment 158458 --> https://bugs.kde.org/attachment.cgi?id=158458=edit Region is further washed out When selecting the region, the text is no longer visible. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 469022] Selected area bleaches text
https://bugs.kde.org/show_bug.cgi?id=469022 --- Comment #2 from pablo --- Created attachment 158457 --> https://bugs.kde.org/attachment.cgi?id=158457=edit After selecting /Rectangular Region/ Compared to the '01_original.png', the text is washed out. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 469022] Selected area bleaches text
https://bugs.kde.org/show_bug.cgi?id=469022 --- Comment #1 from pablo --- Created attachment 158456 --> https://bugs.kde.org/attachment.cgi?id=158456=edit Before running spectacle -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 469022] New: Selected area bleaches text
https://bugs.kde.org/show_bug.cgi?id=469022 Bug ID: 469022 Summary: Selected area bleaches text Classification: Applications Product: Spectacle Version: 23.04.0 Platform: openSUSE OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: noaha...@gmail.com Reporter: pa...@blueoakdb.com CC: k...@david-redondo.de Target Milestone: --- SUMMARY Hi, After selecting /Rectangular Region/, Spectacle overlays a light background over the entire screen. With a web page with a white background and black(ish) text, the text is washed out. Any text within the rectangular region is washed out further. I'm attaching a tar-ball with annotated images: $ tar -cvf example.1.tar example.1 example.1/ example.1/01_original.jpg example.1/02_spectacle_running_b4_capture.jpg example.1/03_specactle_running_defining_area.jpg Changing /Use light background/ makes the problem worst. :( STEPS TO REPRODUCE 1. Select /Breeze Dark/ theme - just in case this is the problem. 2. Go to the test website that has a white background with dark text - https://www.npr.org 3. Start `spectacle` and select `Rectangular Region` - notice the dark text is bleached. 4. Select part of the text, notice the text in the region is washed out. OBSERVED RESULT ** This is somewhat redundant as I mentioned above what's happening. But here it is ... :) ** After selecting `Rectangular Region`, spectacle creates an overlay which bleaches the test website's dark text when the background is white. When continuing to select the region, the text in the region is washed out. EXPECTED RESULT The text should be visible when the background is white and the text is black. SOFTWARE/OS VERSIONS Linux: 6.2.12-1-default KDE Plasma Version: 5.27.4 KDE Frameworks Version: 5.105.0 Qt Version: 5.15.9 ADDITIONAL INFORMATION Thank you! :) -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 468659] Breeze Light and Dark "Inactive Titlebar Text" color does not work
https://bugs.kde.org/show_bug.cgi?id=468659 --- Comment #2 from Pablo --- (In reply to Pablo from comment #1) > Worth noting: I've been pointed to this similar bug report: > > But I'm not sure that's the entire story. Breeze Light does define an > inactive text color for headers (see this screenshot: > https://i.imgur.com/iG3jE9z.png), and it isn't applied either. Sorry the link to the other bug is missing and I cannot edit my previous message: https://bugs.kde.org/show_bug.cgi?id=433059 -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 468659] Breeze Light and Dark "Inactive Titlebar Text" color does not work
https://bugs.kde.org/show_bug.cgi?id=468659 --- Comment #1 from Pablo --- Worth noting: I've been pointed to this similar bug report: But I'm not sure that's the entire story. Breeze Light does define an inactive text color for headers (see this screenshot: https://i.imgur.com/iG3jE9z.png), and it isn't applied either. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 468659] New: Breeze Light and Dark "Inactive Titlebar Text" color does not work
https://bugs.kde.org/show_bug.cgi?id=468659 Bug ID: 468659 Summary: Breeze Light and Dark "Inactive Titlebar Text" color does not work Classification: Plasma Product: Breeze Version: 5.27.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Color scheme Assignee: plasma-b...@kde.org Reporter: r...@uzy.me Target Milestone: --- SUMMARY In the Breeze Light and Breeze Dark theme, the "Inactive Titlebar Text" color is not respected. The title text of inactive windows stays the same color as the title text of active window while it's not how it is defined in the theme. This does not affect Breeze Classic. See https://imgur.com/a/rj9AvBS for screenshots. STEPS TO REPRODUCE 1. Use either Breeze Light or Breeze Dark color scheme for Plasma. 2. Have a first window opened. 3. Focus a second window. OBSERVED RESULT The titlebar text of the first window stayed the same color as in active window. EXPECTED RESULT The titlebar text of the first window changes of color for the "Inactive Titlebar Text" color defined by the selected theme. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Debian 12 (Linux 6.1.0-7-amd64) (available in About System) KDE Plasma Version: 5.27.3 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 ADDITIONAL INFORMATION I'm using X11. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 461269] konsole mostly slow to display window on start
https://bugs.kde.org/show_bug.cgi?id=461269 --- Comment #2 from pablo --- Comment on attachment 153366 --> https://bugs.kde.org/attachment.cgi?id=153366 WAYLAND_DEBUG with 2s start delay - search for /[ 532235.427] wl_callb...@24.done(1214)/ I tail'd the file during the test. The tail paused and no window was displayed at this point in the output: [ 532235.409] wl_drm@25.format(842094158) [ 532235.414] wl_drm@25.format(909203022) [ 532235.418] wl_drm@25.format(1448695129) [ 532235.423] wl_drm@25.capabilities(1) [ 532235.427] wl_callb...@24.done(1214) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 461269] konsole mostly slow to display window on start
https://bugs.kde.org/show_bug.cgi?id=461269 --- Comment #1 from pablo --- Created attachment 153367 --> https://bugs.kde.org/attachment.cgi?id=153367=edit WAYLAND_DEBUG with no observable delay -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 461269] New: konsole mostly slow to display window on start
https://bugs.kde.org/show_bug.cgi?id=461269 Bug ID: 461269 Summary: konsole mostly slow to display window on start Classification: Plasma Product: kwin Version: 5.26.2 Platform: OpenSUSE OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: pa...@blueoakdb.com Target Milestone: --- Created attachment 153366 --> https://bugs.kde.org/attachment.cgi?id=153366=edit WAYLAND_DEBUG with 2s start delay - search for /[ 532235.427] wl_callb...@24.done(1214)/ SUMMARY Hi, Using konsole as a test case, there is a noticeable lag to display the window: o At first start up o After some period of time (e.g. a minute) between new window starts I have captured some WAYLAND_DEBUG=1 output showing lag vs no lag. This is an excerpt of the debug when I observed the a two second lag: [ 532235.418] wl_drm@25.format(1448695129) [ 532235.423] wl_drm@25.capabilities(1) [ 532235.427] wl_callb...@24.done(1214) # # After running konsole in another window, the /tail -f/ paused above. # No window was displayed for about two seconds. # [ 534388.338] -> wl_display@1.get_registry(new id wl_registry@24) [ 534388.428] -> wl_disp...@1.sync(new id wl_callback@26) [ 534391.580] wl_display@1.delete_id(26) [ 534391.586] wl_registry@24.global(1, "wl_compositor", 5) SET UP 1. Create a new Linux user whose shell is /bin/bash 2. Log in to the new user using Wayland STEPS TO REPRODUCE Repeated make the following call, ctrl-D the new window to exit. To observe the start delay, wait about 30 seconds between the calls: WAYLAND_DEBUG=1 konsole >> konsole.wayland_debug 2>&1 OBSERVED RESULT When a new konsole window is started /shortly/ after a previously started konsole window, there is no observable delay. However, if there's a 30 second delay between calls, a start delay is observed. EXPECTED RESULT The windows should start immediately. As observed on X11. SOFTWARE/OS VERSIONS Linux/KDE Plasma: 6.0.5-1-default (available in About System) KDE Plasma Version: 5.26.2 KDE Frameworks Version: 5.99.0 Qt Version: 5.15.6 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 461218] New: /skip pager/ property ignored on wayland
https://bugs.kde.org/show_bug.cgi?id=461218 Bug ID: 461218 Summary: /skip pager/ property ignored on wayland Classification: Plasma Product: kwin Version: 5.26.2 Platform: OpenSUSE OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: rules Assignee: kwin-bugs-n...@kde.org Reporter: pa...@blueoakdb.com CC: isma...@gmail.com Target Milestone: --- SUMMARY Under wayland, the /Skip pager/ kwin rule property is ignored. STEPS TO REPRODUCE 0. Check Pager's /Show application icons on window outlines/ 1. Create a new rule for konsole 2. Add the property /Virtual Desktops/ set to /All Desktops/ 3. Add the property /Skip pager/ set to /Force/ and /Yes/ 4. Click OK OBSERVED RESULT The konsole icon appears in all of the pager widget panes. EXPECTED RESULT The konsole icon should not appear in pager. It should be ... skipped. :) SOFTWARE/OS VERSIONS Linux/KDE Plasma: 6.0.5-1 (available in About System) KDE Plasma Version: 5.26.2 KDE Frameworks Version: 5.99.0 Qt Version: 5.15.6 -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 460184] New: bug in open app version 20,12.0 kde 5.78.0 qt 5.15.2 sistem windows xcb
https://bugs.kde.org/show_bug.cgi?id=460184 Bug ID: 460184 Summary: bug in open app version 20,12.0 kde 5.78.0 qt 5.15.2 sistem windows xcb Classification: Applications Product: konqueror Version: 5.0.97 Platform: Debian stable OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: konq-b...@kde.org Reporter: pec...@hotmail.com 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 *** STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: 5,20.5 (available in About System) KDE Plasma Version: 2.20.5 KDE Frameworks Version: 5.78.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION kernel 5.10.0/18/amd64 os 64 bits Operating System: Debian GNU/Linux 11 KDE Plasma Version: 5.20.5 KDE Frameworks Version: 5.78.0 Qt Version: 5.15.2 Kernel Version: 5.10.0-18-amd64 OS Type: 64-bit Processors: 4 × AMD Ryzen 3 3200G with Radeon Vega Graphics Memory: 15.6 GiB of RAM Graphics Processor: llvmpipe -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 458941] New: Copy merged crashes the application
https://bugs.kde.org/show_bug.cgi?id=458941 Bug ID: 458941 Summary: Copy merged crashes the application Product: krita Version: 5.1.0 Platform: Appimage OS: Linux Status: REPORTED Severity: major Priority: NOR Component: Usability Assignee: krita-bugs-n...@kde.org Reporter: netinf...@gmail.com Target Milestone: --- Selecting all the image that is being edited (ctrl+A) and doing "copy merged" crashes the application. STEPS TO REPRODUCE 1. Create a new document 2. Select all with ctrl+A 3. Select Copy merged from the Edit menu OBSERVED RESULT The following messages is repeated indefinitely in the console (since I start the app from the command line) until application crashes. SAFE ASSERT (krita): "qAbs(row) < 0x7FFF && qAbs(col) < 0x7FFF" in file /home/appimage/workspace/Krita_Release_Appimage_Build/krita/libs/image/tiles3/kis_tile_hash_table2.h, line 151 The crash doesn't occur if part of the image is selected, like using any of the selection tools. EXPECTED RESULT The application should be copied with all the layers merged. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 458875] Krita get stuck at rendering after opening a new window and new view
https://bugs.kde.org/show_bug.cgi?id=458875 --- Comment #1 from Pablo --- Since I start Krita from the command line, this is are the messages I saw Replacing libstdc++.so.6 with the fallback version: libstdc++.so.6.0.28 → libstdc++.so.6.0.29 Bundle “/home/pablo/.local/share/krita/SK_V1.bundle” is broken. File “brushes/bristles_circle_variable.svg” is missing Bundle “/home/pablo/.local/share/krita/SK_V1.bundle” is broken. File “brushes/circle_hard_eroded.gih” is missing Bundle “/home/pablo/.local/share/krita/SK_V1.bundle” is broken. File “brushes/oil_bristle.png” is missing Could not load the resource from the bundle “paintoppresets” “paintoppresets/Special_dyna_dots.kpp” “/home/pablo/.local/share/krita/Krita_3_Default_Resources.bundle” QObject::startTimer: Timers cannot have negative intervals /tmp/.mount_krita_VheoUu/usr/lib/krita-python-libs/krita added to PYTHONPATH WARNING: KisResourceLocator::loadRequiredResources failed to sanity check the embedded resource: parent resource: KoResourceSignature(“paintoppresets”, “”, “k)_Blender_Basic.kpp”, “k) Blender Basic”) embedded resource: KoResourceSignature(“patterns”, “fdc6eb8cb5e67e92f77e61e822db3e4a”, “4-flathack-black55.png”, “4-flathack-black55.png”) qt.qpa.xkeyboard: QXcbKeyboard::handleKeyEvent: key released, but it has no record in the registry code 37 qtcode 16777249 QFSFileEngine::open: No file name specified SAFE ASSERT (krita): “!m_d->isActive” in file /home/appimage/workspace/Krita_Release_Appimage_Build/krita/libs/ui/tool/KisAsyncColorSamplerHelper.cpp, line 112 QFSFileEngine::open: No file name specified qt.qpa.xkeyboard: QXcbKeyboard::handleKeyEvent: key pressed, but it is already present in the registry code 64 qtcode 16777251 registered qtcode 16777251 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 458875] New: Krita get stuck at rendering after opening a new window and new view
https://bugs.kde.org/show_bug.cgi?id=458875 Bug ID: 458875 Summary: Krita get stuck at rendering after opening a new window and new view Product: krita Version: 5.1.0 Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Usability Assignee: krita-bugs-n...@kde.org Reporter: netinf...@gmail.com Target Milestone: --- SUMMARY Krita gets stuck at rendering if another view of the file is open, this behaviour also happens with a new image. STEPS TO REPRODUCE 1. Create a new document or open an existing .kra 2. Create a new window (Window -> New Window) 3. In the second window make a new view of the same file (Window -> New view) 4. Start editing the file on the first window OBSERVED RESULT After a few edits (been clicking repeatedly for around 5 seconds) Krita gets stuck at rendering, the interface can still be usable (like changing colos, selecting tools or brushes, menu options) but no more drawing is possible. The file cannot be saved, saving shows the "waiting for image operation to complete" dialog and clicking on the "save without waiting" button and entering a new file name shows the same "waiting for image operation to complete" dialog without buttons this time. I tried different brushes and the get the same issue, so it doesn't seem brush dependent. This is reproduced 100% of the time. EXPECTED RESULT Rendering should finish independently of using another view or not. SOFTWARE/OS VERSIONS Qt 5.12.8 (x86_64-little_endian-lp64 shared (dynamic) release build; by GCC 9.3.0) on "xcb" OS: Ubuntu 20.04.4 LTS [linux version 5.4.0-73-generic] ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[frameworks-ktexteditor] [Bug 457392] Kate crashes when calling wordLeft on column 1 of a line of length 1
https://bugs.kde.org/show_bug.cgi?id=457392 --- Comment #1 from Pablo --- It was actually a lot more easy than I thought it would be. Proposed fix: https://invent.kde.org/frameworks/ktexteditor/-/merge_requests/395 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-ktexteditor] [Bug 457392] New: Kate crashes when calling wordLeft on column 1 of a line of length 1
https://bugs.kde.org/show_bug.cgi?id=457392 Bug ID: 457392 Summary: Kate crashes when calling wordLeft on column 1 of a line of length 1 Product: frameworks-ktexteditor Version: unspecified Platform: Compiled Sources OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: general Assignee: kwrite-bugs-n...@kde.org Reporter: r...@uzy.me 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 *** STEPS TO REPRODUCE 1. Open a new file in Kate 2. press any letter 3. press Ctrl+Left OBSERVED RESULT Kate crashes. Thread 1 "kate" received signal SIGABRT, Aborted. 0x763b8ce1 in raise () from /lib/x86_64-linux-gnu/libc.so.6 (gdb) bt #0 0x763b8ce1 in raise () from /lib/x86_64-linux-gnu/libc.so.6 #1 0x763a2537 in abort () from /lib/x86_64-linux-gnu/libc.so.6 #2 0x767a0bf1 in QMessageLogger::fatal(char const*, ...) const () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #3 0x767a0040 in qt_assert(char const*, char const*, int) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x75eafb98 in QString::at (this=0x5a10d230, i=-1) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qstring.h:1072 #5 0x76065446 in CamelCursor::operator+= (this=0x7fffbf70, n=-1) at /home/p4bl0/projects/kde/src/frameworks/ktexteditor/src/view/kateviewinternal.cpp:1369 #6 0x76065816 in CamelCursor::operator-= (this=0x7fffbf70, n=1) at /home/p4bl0/projects/kde/src/frameworks/ktexteditor/src/view/kateviewinternal.cpp:1423 #7 0x76063d3c in CalculatingCursor::operator-- (this=0x7fffbf70) at /home/p4bl0/projects/kde/src/frameworks/ktexteditor/src/view/kateviewinternal.cpp:961 #8 0x76050bd8 in operator() (__closure=0x7fffc1d8, cursor=...) at /home/p4bl0/projects/kde/src/frameworks/ktexteditor/src/view/kateviewinternal.cpp:1500 #9 0x76050ff5 in KateViewInternal::wordPrev (this=0x5a41eca0, sel=false) at /home/p4bl0/projects/kde/src/frameworks/ktexteditor/src/view/kateviewinternal.cpp:1530 #10 0x76035a76 in KTextEditor::ViewPrivate::wordLeft (this=0x5aa62bb0) at /home/p4bl0/projects/kde/src/frameworks/ktexteditor/src/view/kateview.cpp:3860 #11 0x760486ed in QtPrivate::FunctorCall, QtPrivate::List<>, void, void (KTextEditor::ViewPrivate::*)()>::call(void (KTextEditor::ViewPrivate::*)(), KTextEditor::ViewPrivate*, void**) ( f=(void (KTextEditor::ViewPrivate::*)(KTextEditor::ViewPrivate * const)) 0x76035a08 , o=0x5aa62bb0, arg=0x7fffc400) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qobjectdefs_impl.h:152 #12 0x76046f1b in QtPrivate::FunctionPointer::call for more, q to quit, c to continue without paging-- rivate::List<>, void>(void (KTextEditor::ViewPrivate::*)(), KTextEditor::ViewPrivate*, void**) ( f=(void (KTextEditor::ViewPrivate::*)(KTextEditor::ViewPrivate * const)) 0x76035a08 , o=0x5aa62bb0, arg=0x7fffc400) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qobjectdefs_impl.h:185 #13 0x760442ab in QtPrivate::QSlotObject, void>::impl(int, QtPrivate::QSlotObjectBase*, QObject*, void**, bool*) (which=1, this_=0x5ab51510, r=0x5aa62bb0, a=0x7fffc400, ret=0x0) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qobjectdefs_impl.h:418 #14 0x769f35a6 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #15 0x7760fb62 in QAction::triggered(bool) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #16 0x776123a1 in QAction::activate(QAction::ActionEvent) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #17 0x77612f67 in QAction::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #18 0x7761615f in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #19 0x769bcfca in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #20 0x76f5bcab in QShortcutMap::dispatchEvent(QKeyEvent*) () from /lib/x86_64-linux-gnu/libQt5Gui.so.5 #21 0x76f5c66b in QShortcutMap::tryShortcut(QKeyEvent*) () from /lib/x86_64-linux-gnu/libQt5Gui.so.5 #22 0x76f05cae in QWindowSystemInterface::handleShortcutEvent(QWindow*, unsigned long, int, QFlags, unsigned int, unsigned int, unsigned int, QString const&, bool, unsigned short) () from /lib/x86_64-linux-gnu/libQt5Gui.so.5 #23 0x76f284cb in
[kwin] [Bug 454974] DBus method ColorPicker.pick fails to retrieve color (returns black)
https://bugs.kde.org/show_bug.cgi?id=454974 pablo changed: What|Removed |Added CC||pa...@blueoakdb.com -- You are receiving this mail because: You are watching all bug changes.
[kinfocenter] [Bug 454301] New: Start problem virtualbox
https://bugs.kde.org/show_bug.cgi?id=454301 Bug ID: 454301 Summary: Start problem virtualbox Product: kinfocenter Version: 5.24.4 Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: critical Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: pprov...@gmail.com CC: hubn...@gmail.com Target Milestone: --- Created attachment 149149 --> https://bugs.kde.org/attachment.cgi?id=149149=edit Error Printscreen SUMMARY *** Do not Start my VirtualBoxwindows.vdi after migrate of kubuntu 20.04.04 LTS to kubuntu 22.04 LTS The VM windows.vdi work very good on Kubuntu 20.04.04 *** STEPS TO REPRODUCE 1. Install kubuntu 22.04 LTS 2. Install VirtualBox : # atp install virtualbox + virtualbox-ext-pack + virtualbox-guest-additions-iso and others defaults 3. Restored a copy of the windows.vdi VM backup 4. Create and Configure new restored VM in virtualbox manager dashboard 5. Start. and crash with reported error msj. 6. In kubuntu 20.04.04 LTS work very good. OBSERVED RESULT The VirtualBox Linux kernel driver is either not loaded or not set up correctly. Please reinstall virtualbox-dkms package and load the kernel module by executing 'modprobe vboxdrv' as root. If your system has EFI Secure Boot enabled you may also need to sign the kernel modules (vboxdrv, vboxnetflt, vboxnetadp, vboxpci) before you can load them. Please see your Linux system's documentation for more information. where: suplibOsInit what: 3 VERR_VM_DRIVER_NOT_INSTALLED (-1908) - The support driver is not installed. On linux, open returned ENOENT. EXPECTED RESULT Start VM SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Kununtu 22.04 LTS (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 452546] New: Plasma Settings Crash
https://bugs.kde.org/show_bug.cgi?id=452546 Bug ID: 452546 Summary: Plasma Settings Crash Product: kde Version: unspecified Platform: unspecified OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: jpley...@gmail.com Target Milestone: --- Application: plasma-settings (22.02) Qt Version: 5.15.3 Frameworks Version: 5.92.0 Operating System: Linux 5.17.1-arch1-1 x86_64 Windowing System: X11 Distribution: Linux DrKonqi: 5.24.4 [KCrashBackend] -- Information about the crash: - What I was doing when the application crashed: I just oppened de plasma settings app after a fresh install of all Plasma environment. OS: Arcolinix WM: qtile The crash can be reproduced every time. -- Backtrace: Application: Settings (plasma-settings), signal: Segmentation fault [KCrash Handler] #4 0x7fa61ea6c520 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib/libQt5Core.so.5 #5 0x7fa6040de579 in Kvantum::Animation::updateTarget() () from /usr/lib/qt/plugins/styles/libkvantum.so #6 0x7fa61e8b0923 in QAbstractAnimation::setCurrentTime(int) () from /usr/lib/libQt5Core.so.5 #7 0x7fa61e8b0a6e in ?? () from /usr/lib/libQt5Core.so.5 #8 0x7fa61e8abd83 in QUnifiedTimer::updateAnimationTimers(long long) () from /usr/lib/libQt5Core.so.5 #9 0x7fa61e8af263 in QAnimationDriver::advanceAnimation(long long) () from /usr/lib/libQt5Core.so.5 #10 0x7fa61e068c6a in ?? () from /usr/lib/libQt5Quick.so.5 #11 0x7fa61e06d840 in ?? () from /usr/lib/libQt5Quick.so.5 #12 0x7fa61e8c48cc in ?? () from /usr/lib/libQt5Core.so.5 #13 0x7fa61e43d5c2 in start_thread () from /usr/lib/libc.so.6 #14 0x7fa61e4c2584 in clone () from /usr/lib/libc.so.6 Thread 4 (Thread 0x7fa613fff640 (LWP 28541) "QQmlThread"): #1 0x7fa61cf186c5 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #2 0x7fa61eab85f7 in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/libQt5Core.so.5 #3 0x7fa61ea6488b in QEventLoop::exec(QFlags) () from /usr/lib/libQt5Core.so.5 #4 0x7fa61e8c7a56 in QThread::exec() () from /usr/lib/libQt5Core.so.5 #5 0x7fa61fdfed00 in ?? () from /usr/lib/libQt5Qml.so.5 #6 0x7fa61e8c48cc in ?? () from /usr/lib/libQt5Core.so.5 #7 0x7fa61e43d5c2 in start_thread () from /usr/lib/libc.so.6 #8 0x7fa61e4c2584 in clone () from /usr/lib/libc.so.6 Thread 3 (Thread 0x7fa618923640 (LWP 28540) "QDBusConnection"): #1 0x7ffeb7de49aa in clock_gettime () #2 0x7fa61e48892d in clock_gettime@GLIBC_2.2.5 () from /usr/lib/libc.so.6 #3 0x7fa61cf1ad15 in g_main_context_prepare () from /usr/lib/libglib-2.0.so.0 #4 0x7fa61cf717e6 in ?? () from /usr/lib/libglib-2.0.so.0 #5 0x7fa61cf186c5 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #6 0x7fa61eab85f7 in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/libQt5Core.so.5 #7 0x7fa61ea6488b in QEventLoop::exec(QFlags) () from /usr/lib/libQt5Core.so.5 #8 0x7fa61e8c7a56 in QThread::exec() () from /usr/lib/libQt5Core.so.5 #9 0x7fa61dc123a9 in ?? () from /usr/lib/libQt5DBus.so.5 #10 0x7fa61e8c48cc in ?? () from /usr/lib/libQt5Core.so.5 #11 0x7fa61e43d5c2 in start_thread () from /usr/lib/libc.so.6 #12 0x7fa61e4c2584 in clone () from /usr/lib/libc.so.6 Thread 2 (Thread 0x7fa619146640 (LWP 28539) "QXcbEventQueue"): #1 0x7fa61a15263b in ?? () from /usr/lib/libxcb.so.1 #2 0x7fa61a15437b in xcb_wait_for_event () from /usr/lib/libxcb.so.1 #3 0x7fa619251b12 in ?? () from /usr/lib/libQt5XcbQpa.so.5 #4 0x7fa61e8c48cc in ?? () from /usr/lib/libQt5Core.so.5 #5 0x7fa61e43d5c2 in start_thread () from /usr/lib/libc.so.6 #6 0x7fa61e4c2584 in clone () from /usr/lib/libc.so.6 Thread 1 (Thread 0x7fa61964fa80 (LWP 28537) "plasma-settings"): #1 0x7fa61e43c960 in pthread_cond_wait@@GLIBC_2.3.2 () from /usr/lib/libc.so.6 #2 0x7fa61e8cbcfc in QWaitCondition::wait(QMutex*, QDeadlineTimer) () from /usr/lib/libQt5Core.so.5 #3 0x7fa61e072607 in ?? () from /usr/lib/libQt5Quick.so.5 #4 0x7fa61e0c4784 in QQuickWindow::event(QEvent*) () from /usr/lib/libQt5Quick.so.5 #5 0x7fa61f5881c6 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/libQt5Widgets.so.5 #6 0x7fa61ea6c5aa in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib/libQt5Core.so.5 #7 0x7fa61ee34609 in QPlatformWindow::windowEvent(QEvent*) () from /usr/lib/libQt5Gui.so.5 #8 0x7fa61f58c4fc in QApplication::notify(QObject*, QEvent*) () from /usr/lib/libQt5Widgets.so.5 #9 0x7fa61ea6c5aa in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib/libQt5Core.so.5 #10 0x7fa61eab7dd5 in QTimerInfoList::activateTimers() () from /usr/lib/libQt5Core.so.5 #11
[plasmashell] [Bug 449900] Mouse-click Mouse Action always runs Kate (with app's .desktop) instead of application
https://bugs.kde.org/show_bug.cgi?id=449900 --- Comment #5 from pablo --- (In reply to Nicolas Fella from comment #4) > > [ trimmed ] > > This fixes launching apps since OpenUrlJob, by default, doesn't launch > executables Thank you so much for the extremely quick turn-around! <3 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 449900] New: Mouse-click Mouse Action always runs Kate (with app's .desktop) instead of application
https://bugs.kde.org/show_bug.cgi?id=449900 Bug ID: 449900 Summary: Mouse-click Mouse Action always runs Kate (with app's .desktop) instead of application Product: plasmashell Version: 5.24.0 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Desktop Containment Assignee: notm...@gmail.com Reporter: pa...@blueoakdb.com CC: plasma-b...@kde.org Target Milestone: 1.0 Created attachment 146509 --> https://bugs.kde.org/attachment.cgi?id=146509=edit emacs example SUMMARY Before the upgrade to 5.24, I was able to rt-click on my desktop background for the /Application Launcher/ and launch an application. After the upgrade, for any application I try to launch, /Kate/ is run with that application's /.desktop/ file - see the attached /emacs/ example. The work-around is to use the /Application Launcher/ from the systray. STEPS TO REPRODUCE 1. Set up the environment as follows: - /Wallpaper/ settings are: o Layout > Desktop o Wallpaper type > Plain Color - /Mouse Actions/ > /Right-Button/ > /Application Launcher/ 2. Mouse to the desktop background and rt-click. Pick any application to launch. OBSERVED RESULT Kate is launched with the application's .desktop file. EXPECTED RESULT Launch the application. SOFTWARE/OS VERSIONS Linux/KDE Plasma: openSUSE Tumbleweed KDE Plasma Version: 5.24.0 KDE Frameworks Version: 5.90.0 Qt Version: 5.15.2 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 444877] New: System Preferences
https://bugs.kde.org/show_bug.cgi?id=444877 Bug ID: 444877 Summary: System Preferences Product: systemsettings Version: 5.22.5 Platform: Fedora RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: pablo.emanuel.ambro...@gmail.com Target Milestone: --- Application: systemsettings5 (5.22.5) Qt Version: 5.15.2 Frameworks Version: 5.85.0 Operating System: Linux 5.11.12-300.fc34.x86_64 x86_64 Windowing System: X11 Drkonqi Version: 5.22.5 Distribution: Fedora 34 (Workstation Edition) -- Information about the crash: System preferences is not opening and I can't adjust the controls The crash can be reproduced every time. -- Backtrace: Application: Preferencias del sistema (systemsettings5), signal: Segmentation fault [KCrash Handler] #4 0x7faa3e39c339 in QPixmapStyle::drawControl(QStyle::ControlElement, QStyleOption const*, QPainter*, QWidget const*) const () from /lib64/libQt5Widgets.so.5 #5 0x7faa0c945d28 in KQuickStyleItem::updatePolish() () from /usr/lib64/qt5/qml/org/kde/qqc2desktopstyle/private/libqqc2desktopstyleplugin.so #6 0x7faa3ca4d75c in QQuickWindowPrivate::polishItems() () from /lib64/libQt5Quick.so.5 #7 0x7faa3cadb7f2 in QQuickRenderControl::polishItems() () from /lib64/libQt5Quick.so.5 #8 0x7faa3cd81c15 in QQuickWidgetPrivate::render(bool) () from /lib64/libQt5QuickWidgets.so.5 #9 0x7faa3e3162bc in QWidget::event(QEvent*) () from /lib64/libQt5Widgets.so.5 #10 0x7faa3e2d4e73 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib64/libQt5Widgets.so.5 #11 0x7faa3d745f48 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib64/libQt5Core.so.5 #12 0x7faa3e30d866 in QWidgetPrivate::sendPendingMoveAndResizeEvents(bool, bool) () from /lib64/libQt5Widgets.so.5 #13 0x7faa3e3121a7 in QWidgetPrivate::show_helper() () from /lib64/libQt5Widgets.so.5 #14 0x7faa3e315353 in QWidgetPrivate::setVisible(bool) () from /lib64/libQt5Widgets.so.5 #15 0x7faa3e312129 in QWidgetPrivate::showChildren(bool) () from /lib64/libQt5Widgets.so.5 #16 0x7faa3e3121c3 in QWidgetPrivate::show_helper() () from /lib64/libQt5Widgets.so.5 #17 0x7faa3e315353 in QWidgetPrivate::setVisible(bool) () from /lib64/libQt5Widgets.so.5 #18 0x7faa3e312129 in QWidgetPrivate::showChildren(bool) () from /lib64/libQt5Widgets.so.5 #19 0x7faa3e3121c3 in QWidgetPrivate::show_helper() () from /lib64/libQt5Widgets.so.5 #20 0x7faa3e312149 in QWidgetPrivate::showChildren(bool) () from /lib64/libQt5Widgets.so.5 #21 0x7faa3e3121c3 in QWidgetPrivate::show_helper() () from /lib64/libQt5Widgets.so.5 #22 0x7faa3e315353 in QWidgetPrivate::setVisible(bool) () from /lib64/libQt5Widgets.so.5 #23 0x7faa3e312129 in QWidgetPrivate::showChildren(bool) () from /lib64/libQt5Widgets.so.5 #24 0x7faa3e3121c3 in QWidgetPrivate::show_helper() () from /lib64/libQt5Widgets.so.5 #25 0x7faa3e315353 in QWidgetPrivate::setVisible(bool) () from /lib64/libQt5Widgets.so.5 #26 0x7faa3e2fa6c7 in QStackedLayout::setCurrentIndex(int) () from /lib64/libQt5Widgets.so.5 #27 0x7faa3ea42c59 in QtPrivate::QFunctorSlotObject, void>::impl(int, QtPrivate::QSlotObjectBase*, QObject*, void**, bool*) () from /lib64/libKF5WidgetsAddons.so.5 #28 0x7faa3d7764b0 in void doActivate(QObject*, int, void**) () from /lib64/libQt5Core.so.5 #29 0x7faa3d70a87b in QItemSelectionModel::selectionChanged(QItemSelection const&, QItemSelection const&) () from /lib64/libQt5Core.so.5 #30 0x7faa3d712a06 in QItemSelectionModel::select(QItemSelection const&, QFlags) () from /lib64/libQt5Core.so.5 #31 0x7faa3d70e1e1 in QItemSelectionModel::select(QModelIndex const&, QFlags) () from /lib64/libQt5Core.so.5 #32 0x7faa3d70bfa4 in QItemSelectionModel::setCurrentIndex(QModelIndex const&, QFlags) () from /lib64/libQt5Core.so.5 #33 0x7faa3ea3f5f8 in QtPrivate::QFunctorSlotObject, void>::impl(int, QtPrivate::QSlotObjectBase*, QObject*, void**, bool*) () from /lib64/libKF5WidgetsAddons.so.5 #34 0x7faa3d7764b0 in void doActivate(QObject*, int, void**) () from /lib64/libQt5Core.so.5 #35 0x7faa3d6fcbda in QAbstractItemModel::layoutChanged(QList const&, QAbstractItemModel::LayoutChangeHint) () from /lib64/libQt5Core.so.5 #36 0x7faa3ea499b0 in KPageWidgetModel::addPage(KPageWidgetItem*) () from /lib64/libKF5WidgetsAddons.so.5 #37 0x7faa3ed461fa in ModuleView::loadModule(QModelIndex const&, QStringList const&) () from /lib64/libsystemsettingsview.so.3 #38 0x7faa2002cb61 in SidebarMode::loadModule(QModelIndex const&, QStringList const&) [clone .part.0] () from /usr/lib64/qt5/plugins/systemsettingsview/systemsettings_sidebar_mode.so #39 0x7faa200309e4 in SidebarMode::qt_static_metacall(QObject*, QMetaObject::Call, int, void**) () from
[plasmashell] [Bug 359783] Right-aligned desktop icons move all the way to the left when icons are added or moved
https://bugs.kde.org/show_bug.cgi?id=359783 --- Comment #43 from Juan Pablo Firrincieli --- I've created an account in Qt but being of no company it seems that I can only search for opened bugs instead of open a new one, I couldn't find this issue in the open bugs, but maybe there is one with technical info on it. El mié, 16 de jun. de 2021 a la(s) 11:55, Nate Graham ( bugzilla_nore...@kde.org) escribió: > https://bugs.kde.org/show_bug.cgi?id=359783 > > --- Comment #42 from Nate Graham --- > That commit was in 2019 though, and the bug report was originally opened in > 2016. > > Either way, I guess we need a Qt bug report. If you don't know of one, > would > you be able to flie one? > > -- > You are receiving this mail because: > You are on the CC list for the bug. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 435406] New: The system crash when i was use plasma wayland session
https://bugs.kde.org/show_bug.cgi?id=435406 Bug ID: 435406 Summary: The system crash when i was use plasma wayland session Product: kdeconnect Version: unspecified Platform: Neon Packages OS: Linux Status: REPORTED Severity: critical Priority: NOR Component: plasmoid Assignee: albertv...@gmail.com Reporter: pablosaavedraso...@protonmail.com Target Milestone: --- Created attachment 137368 --> https://bugs.kde.org/attachment.cgi?id=137368=edit The system crash when i was use plasma wayland session SUMMARY The system crash when i was use plasma wayland session STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 435405] New: The system crash when i was use plasma wayland session
https://bugs.kde.org/show_bug.cgi?id=435405 Bug ID: 435405 Summary: The system crash when i was use plasma wayland session Product: dolphin Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: critical Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: pablosaavedraso...@protonmail.com CC: kfm-de...@kde.org Target Milestone: --- Created attachment 137367 --> https://bugs.kde.org/attachment.cgi?id=137367=edit The system crash when i was use plasma wayland session The system crash when i was use plasma wayland session EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[choqok] [Bug 230331] choqok navigation keyboard shortcuts
https://bugs.kde.org/show_bug.cgi?id=230331 Pablo Michael Silva changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 431365] "WINDOW DECORATIONS RELOADED" shouldn't be written to stdout
https://bugs.kde.org/show_bug.cgi?id=431365 pablo changed: What|Removed |Added CC||pa...@blueoakdb.com -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 430932] New: Improve behavior of selection tool
https://bugs.kde.org/show_bug.cgi?id=430932 Bug ID: 430932 Summary: Improve behavior of selection tool Product: kdenlive Version: 20.04.1 Platform: Mint (Ubuntu based) OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: User Interface Assignee: j...@kdenlive.org Reporter: pablo.pa...@cabolabs.com Target Milestone: --- SUMMARY There is an inconsistent behavior in the timeline using the selection tool. Sometimes clicking on a track selects the track portion (yellow highlight), sometimes moves the Project Monitor time pointer (the vertical line with the triangle on the top), and sometimes does nothing. This behavior is inconsistent, happens sometimes. For instance, sometimes after cutting a clip in a timeline to remove that portion, I cut start, cut end, then try to select (selection tool) that segment, and the segment doesn't highlight, and I need to click outside the track then inside the segment so it gets selected. As said, other times when I click, instead of selecting a segment, it moves the playback pointer (vertical line with the triangle on top). STEPS TO REPRODUCE It happens sometimes, always with the selection tool, or after changing cut tool to selection tool. OBSERVED RESULT Described above. EXPECTED RESULT All this makes losing time while editing. It would be nice to have a more consistent behavior for the action of selecting a segment and for moving the playback cursor/marker, and that the selection tool always select, without the need of clicking on different places of the clip in the track. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION I'll try to make a video to catch the behavior described. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 398497] Clicking tabs opens new window
https://bugs.kde.org/show_bug.cgi?id=398497 --- Comment #4 from Pablo --- Yes -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 428954] New: Kwin crashes when open any decorated window
https://bugs.kde.org/show_bug.cgi?id=428954 Bug ID: 428954 Summary: Kwin crashes when open any decorated window Product: kwin Version: 5.17.5 Platform: Debian stable OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: pabloypu...@gmail.com Target Milestone: --- Application: kwin_x11 (5.17.5) Qt Version: 5.15.1 Frameworks Version: 5.74.0 Operating System: Linux 5.9.0-2-amd64 x86_64 Distribution: Debian GNU/Linux bullseye/sid -- Information about the crash: After login, Kwin crashes every time a decorated window is opened. The crash can be reproduced every time. -- Backtrace: Application: KWin (kwin_x11), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7fa810a468c0 (LWP 6643))] Thread 3 (Thread 0x7fa80f417700 (LWP 6648)): #0 0x7fa81864f456 in __ppoll (fds=0x7fa8dc78, nfds=1, timeout=, sigmask=0x0) at ../sysdeps/unix/sysv/linux/ppoll.c:44 #1 0x7fa8170ee779 in qt_safe_poll(pollfd*, unsigned long, timespec const*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x7fa8170efe13 in QEventDispatcherUNIX::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #3 0x7fa817099b7b in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7fa816eba9be in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7fa8153faa27 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #6 0x7fa816ebbb01 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7fa8162d9ea7 in start_thread (arg=) at pthread_create.c:477 #8 0x7fa818659d4f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 2 (Thread 0x7fa81034f700 (LWP 6646)): #0 0x7fa81864f35f in __GI___poll (fds=0x7fa81034ebe8, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7fa816dd1d02 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #2 0x7fa816dd398a in xcb_wait_for_event () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #3 0x7fa81064f260 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #4 0x7fa816ebbb01 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7fa8162d9ea7 in start_thread (arg=) at pthread_create.c:477 #6 0x7fa818659d4f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 1 (Thread 0x7fa810a468c0 (LWP 6643)): [KCrash Handler] #4 0x7fa816f3cef0 in QString::operator=(QString const&) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7fa81836c10c in KWin::Decoration::DecoratedClientImpl::requestShowToolTip (text=..., this=0x55bf028b77e0) at ./decorations/decoratedclient.cpp:227 #6 KWin::Decoration::DecoratedClientImpl::requestShowToolTip (this=0x55bf028b77e0, text=...) at ./decorations/decoratedclient.cpp:221 #7 0x7fa80d0f8910 in Breeze::Decoration::isLeftEdge (this=0x55bf026eda20) at /usr/include/c++/9/bits/atomic_base.h:413 #8 Breeze::Decoration::recalculateBorders (this=this@entry=0x55bf026eda20) at ./kdecoration/breezedecoration.cpp:397 #9 0x7fa80d0fc7f9 in Breeze::Decoration::reconfigure (this=this@entry=0x55bf026eda20) at ./kdecoration/breezedecoration.cpp:379 #10 0x7fa80d0fca28 in Breeze::Decoration::init (this=0x55bf026eda20) at ./kdecoration/breezedecoration.cpp:248 #11 0x7fa81836dd52 in KWin::Decoration::DecorationBridge::createDecoration (this=0x55bf02471980, client=client@entry=0x55bf028b8e40) at ./decorations/decorationbridge.cpp:288 #12 0x7fa8183424cc in KWin::Client::createDecoration (this=this@entry=0x55bf028b8e40, oldgeom=...) at ./decorations/decorationbridge.h:99 #13 0x7fa818346758 in KWin::Client::updateDecoration (this=0x55bf028b8e40, check_workspace_pos=, force=) at ./client.cpp:387 #14 0x7fa8183da246 in KWin::Client::manage (this=this@entry=0x55bf028b8e40, w=w@entry=14680070, isMapped=isMapped@entry=true) at ./manage.cpp:348 #15 0x7fa8184769a5 in KWin::Workspace::createClient (this=this@entry=0x55bf0244eff0, w=14680070, is_mapped=is_mapped@entry=true) at ./workspace.cpp:616 #16 0x7fa81847aa1f in KWin::Workspace::initWithX11 (this=0x55bf0244eff0) at ./workspace.cpp:488 #17 0x7fa81847bd51 in KWin::Workspace::init (this=this@entry=0x55bf0244eff0) at ./workspace.cpp:286 #18 0x7fa81847c56d in KWin::Workspace::Workspace (this=0x55bf0244eff0, sessionKey=...) at ./workspace.cpp:195 #19 0x7fa8183d7054 in KWin::Application::createWorkspace (this=0x7ffc61df8410) at ./main.cpp:281 #20 0x7fa818728e6c in operator() (__closure=0x55bf024f5a90) at ./main_x11.cpp:251 #21 QtPrivate::FunctorCall, QtPrivate::List<>, void, KWin::ApplicationX11::performStartup() >::call (arg=, f=...) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qobjectdefs_impl.h:146 #22
[korganizer] [Bug 428693] New: google Calendar no sync
https://bugs.kde.org/show_bug.cgi?id=428693 Bug ID: 428693 Summary: google Calendar no sync Product: korganizer Version: 5.13.80 Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: critical Priority: NOR Component: agendaview (weekview) Assignee: kdepim-b...@kde.org Reporter: jple...@gmail.com Target Milestone: --- Created attachment 133026 --> https://bugs.kde.org/attachment.cgi?id=133026=edit no deja seleccionar calendario SUMMARY STEPS TO REPRODUCE 1. al crear un nuevo evento no dejar selecionar calendario 2. no funciona 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Kubuntu 20.04 (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 212017] Blackberry needs to sync with Korganizer and korganizer with google calendar - pls - - or google calendar will make korganizer obsolete
https://bugs.kde.org/show_bug.cgi?id=212017 Juan Pablo changed: What|Removed |Added CC||jple...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kamoso] [Bug 421618] Cannot unset filter
https://bugs.kde.org/show_bug.cgi?id=421618 Pablo Cholaky changed: What|Removed |Added CC||walterc...@slash.cl -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 422230] Plasma crashed when I opened settings of "System Monitor Sensor" widget immediately after add it to desktop
https://bugs.kde.org/show_bug.cgi?id=422230 --- Comment #1 from Pablo Cholaky --- Created attachment 128944 --> https://bugs.kde.org/attachment.cgi?id=128944=edit New crash information added by DrKonqi plasmashell (5.18.5) using Qt 5.15.0 - What I was doing when the application crashed: Open Sensors plugin. Observe the crash - Unusual behavior I noticed: Plasmashell crashes every time -- Backtrace (Reduced): #4 0x7fd7f1d4decf in QMapNodeBase::nextNode() const () at /usr/lib64/libQt5Core.so.5 #5 0x7fd7f3c890b1 in Plasma::DataContainer::checkForUpdate() () at /usr/lib64/libKF5Plasma.so.5 #6 0x7fd7f1ec83fc in void doActivate(QObject*, int, void**) () at /usr/lib64/libQt5Core.so.5 #7 0x7fd7f1e2d7af in QProcess::finished(int, QProcess::ExitStatus) () at /usr/lib64/libQt5Core.so.5 #8 0x7fd7f1e311c2 in QProcessPrivate::_q_processDied() () at /usr/lib64/libQt5Core.so.5 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 422230] Plasma crashed when I opened settings of "System Monitor Sensor" widget immediately after add it to desktop
https://bugs.kde.org/show_bug.cgi?id=422230 Pablo Cholaky changed: What|Removed |Added CC||walterc...@slash.cl -- You are receiving this mail because: You are watching all bug changes.
[ksudoku] [Bug 421753] New: This has a situation where there is ambiguity to continue
https://bugs.kde.org/show_bug.cgi?id=421753 Bug ID: 421753 Summary: This has a situation where there is ambiguity to continue Product: ksudoku Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: iandw...@gmail.com Reporter: delam...@unam.mx CC: kde-games-b...@kde.org Target Milestone: --- Created attachment 128592 --> https://bugs.kde.org/attachment.cgi?id=128592=edit Here I send a situation in ksudoku tiny killer where in line 2 and 4 one should put the numbers 2 and 4 and there is no information to choose correctly SUMMARY I found that in ksudoku tiny killer sometimes a situation happens that there is no information to chose the right solution. Here I send a situation where in line two one has to chose where to put 2 and 4 the same happens in line four and there is no way to chose where these "2 and 4" should be placed STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[ksudoku] [Bug 421713] I played the tiny killer and I found that the game has ambiguities
https://bugs.kde.org/show_bug.cgi?id=421713 --- Comment #2 from Pablo de la Mora --- In the figure that I sent there is an extra "2" in the second line, but when I was playing the second line was 1xx3 and the fourth line was 3yy1 so a possible solution was; xx => 42 yy => 24 but also; xx => 24 yy => 42 This ambiguity is not the first time that happened to me -- You are receiving this mail because: You are watching all bug changes.
[ksudoku] [Bug 421713] New: I played the tiny killer and I found that the game has ambiguities
https://bugs.kde.org/show_bug.cgi?id=421713 Bug ID: 421713 Summary: I played the tiny killer and I found that the game has ambiguities Product: ksudoku Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: iandw...@gmail.com Reporter: delam...@unam.mx CC: kde-games-b...@kde.org Target Milestone: --- Created attachment 128562 --> https://bugs.kde.org/attachment.cgi?id=128562=edit I played the tiny killer and I found that the game has ambiguities SUMMARY I opened a Tiny Killer and I found that it has a situation where there are ambiguities Below I send the saved game where you can see the problem STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[muon] [Bug 421278] New: Muon - Search not showing results
https://bugs.kde.org/show_bug.cgi?id=421278 Bug ID: 421278 Summary: Muon - Search not showing results Product: muon Version: 5.8.0 Platform: Kubuntu Packages OS: Linux Status: REPORTED Severity: major Priority: NOR Component: muon Assignee: echidna...@kubuntu.org Reporter: jpmore...@gmail.com CC: silh...@gmail.com Target Milestone: --- Created attachment 128333 --> https://bugs.kde.org/attachment.cgi?id=128333=edit Search not showing results SUMMARY Search for packages does not show any results, even the package exist if you search manually. STEPS TO REPRODUCE 1. Open Muon Package Manager 2. Search for latte-dock ( empty result list ) 3. OBSERVED RESULT Empty results when query for package. EXPECTED RESULT Search manually and confirm the package exist. Also you can confirm with first package in the list 0ad. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Kubuntu 20.04 focal fossa (available in About System) KDE Plasma Version: 5.18.4 KDE Frameworks Version: 5.68.0 Qt Version: 5.12.8 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 419088] "Error: cannot open the file" when I try to add a title clip.
https://bugs.kde.org/show_bug.cgi?id=419088 --- Comment #2 from Pablo --- And how can I fix it? It worked and I don't know why, but stopped working. I tried to uninstall and install again, but the error continues to appear. El dom., 22 mar. 2020 18:44, emohr escribió: > https://bugs.kde.org/show_bug.cgi?id=419088 > > emohr changed: > >What|Removed |Added > > > Resolution|--- |WAITINGFORINFO > Flags||timeline_corruption+ > Status|REPORTED|NEEDSINFO > CC||fritzib...@gmx.net > > --- Comment #1 from emohr --- > This is a typical packaging issue. Please try with the current Kdenlive > AppImage version 19.12.3 to see if there are any packaging issues > https://files.kde.org/kdenlive/release/ > > If the problem/issue doesn't occur when using the AppImage, then it's your > configuration or packaging. > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 419088] New: "Error: cannot open the file" when I try to add a title clip.
https://bugs.kde.org/show_bug.cgi?id=419088 Bug ID: 419088 Summary: "Error: cannot open the file" when I try to add a title clip. Product: kdenlive Version: 19.12.3 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Effects & Transitions Assignee: vpi...@kde.org Reporter: pdelarosa2...@gmail.com Target Milestone: --- SUMMARY "Error: cannot open the file" when I try to add a title clip. STEPS TO REPRODUCE 1. Add clip 2. Add title clip 3. "Cannot open the file" OBSERVED RESULT "Error: cannot open the file" EXPECTED RESULT I wanted to add a title clip, I can't SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Arch Linux, Plasma 5.18.3 (available in About System) KDE Plasma Version: 5.18.3 KDE Frameworks Version: 5.68.0 Qt Version: 5.14.1 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 404990] Sign in with Google temporarily disabled for this app
https://bugs.kde.org/show_bug.cgi?id=404990 Pablo Reyes changed: What|Removed |Added CC||reye...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 359783] Folder view icons aligned left, but configured to be on the right
https://bugs.kde.org/show_bug.cgi?id=359783 Juan Pablo Firrincieli changed: What|Removed |Added CC||jpf...@gmail.com Resolution|UPSTREAM|--- Status|RESOLVED|REOPENED Ever confirmed|0 |1 --- Comment #2 from Juan Pablo Firrincieli --- I can confirm that this bug it's still present on KDE Plasma 5.17.3 using KDE Neon. I configured them right aligned and they start at left and then some times they move at start to the right (with animation) and other they align as right aligned but keep on the left side of the screen. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 412451] New: Export > Share > Twitter does not work
https://bugs.kde.org/show_bug.cgi?id=412451 Bug ID: 412451 Summary: Export > Share > Twitter does not work Product: Spectacle Version: unspecified Platform: Debian stable OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: General Assignee: m...@baloneygeek.com Reporter: r...@uzy.me CC: k...@david-redondo.de Target Milestone: --- SUMMARY In the "Export" drop-down menu of Spectacle there is a "Share" submenu in which there is a "Twitter" option, but all it does is open a new empty window in which you can only click the "cancel" button. STEPS TO REPRODUCE 1. invoke Spectacle 2. click the "Export" menu, select "Share", and then "Twitter" 3. That's it. OBSERVED RESULT Empty window. EXPECTED RESULT Twitter form to post a new tweet already populated with the screenshot as image attachment. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Debian 10 (Linux 4.19.0-6-amd64) (available in About System) KDE Plasma Version: 5.14.5 KDE Frameworks Version: 5.54.0 Qt Version: 5.11.3 ADDITIONAL INFORMATION Someone on the #kde IRC channel was able to reproduce the bug. -- You are receiving this mail because: You are watching all bug changes.
[elisa] [Bug 407918] Does not find music on other ext4 partition even when added to search paths
https://bugs.kde.org/show_bug.cgi?id=407918 Pablo B changed: What|Removed |Added CC||trippyturtletag...@gmail.co ||m --- Comment #11 from Pablo B --- I'm also having this same issue on Manjaro, although it didn't use to happen a few months ago. My partition is ext4 and it's mounted on /media and doesn't seem to find any files inside it for some reason. I've tried uninstalling, deleting the elisarc file inside .config and reconfiguring but it won't find any files unless I move them to /home/name/Music. I've also tried to create a symlink inside Music folder and still nothings happens. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 400790] kwin crash after suspension
https://bugs.kde.org/show_bug.cgi?id=400790 Pablo Niklas changed: What|Removed |Added Platform|unspecified |Neon Packages -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 400790] New: kwin crash after suspension
https://bugs.kde.org/show_bug.cgi?id=400790 Bug ID: 400790 Summary: kwin crash after suspension Product: kwin Version: 5.14.2 Platform: unspecified OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: pablo.nik...@gmail.com Target Milestone: --- Application: kwin_x11 (5.14.2) Qt Version: 5.11.2 Frameworks Version: 5.51.0 Operating System: Linux 4.15.0-38-generic x86_64 Distribution: KDE neon User Edition 5.14 -- Information about the crash: - kwin crashed every time my laptop wake up from suspension. - Strange behaviour: Label from icons doesn't appear properly on desktop. - I have installed the nvidia drivers from the distro repo. - The linux distribution is: neon Linux. -- Backtrace: Application: KWin (kwin_x11), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7fca1f487840 (LWP 3614))] Thread 7 (Thread 0x7fc9fd948700 (LWP 9385)): #0 0x7fca1edd9cf6 in __GI_ppoll (fds=0x7fc9f0012f98, nfds=1, timeout=, sigmask=0x0) at ../sysdeps/unix/sysv/linux/ppoll.c:39 #1 0x7fca1c3e2d51 in qt_safe_poll(pollfd*, unsigned long, timespec const*) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x7fca1c3e445e in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #3 0x7fca1c38b30a in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7fca1c1b6bba in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7fca1c1c1adb in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7fca17e206db in start_thread (arg=0x7fc9fd948700) at pthread_create.c:463 #7 0x7fca1ede688f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 6 (Thread 0x7fc9e7fff700 (LWP 3912)): #0 0x7fca1c3bb8e2 in QMetaObject::activate(QObject*, int, int, void**) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #1 0x7fca1c3e4620 in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x7fca1c38b30a in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #3 0x7fca1c1b6bba in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7fca168ac4f5 in () at /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #5 0x7fca1c1c1adb in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7fca17e206db in start_thread (arg=0x7fc9e7fff700) at pthread_create.c:463 #7 0x7fca1ede688f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 5 (Thread 0x7fc9e7014700 (LWP 3625)): #0 0x7fca17e269f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x7fca1b3c6fb8) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7fca17e269f3 in __pthread_cond_wait_common (abstime=0x0, mutex=0x7fca1b3c6f68, cond=0x7fca1b3c6f90) at pthread_cond_wait.c:502 #2 0x7fca17e269f3 in __pthread_cond_wait (cond=0x7fca1b3c6f90, mutex=0x7fca1b3c6f68) at pthread_cond_wait.c:655 #3 0x7fca1b0d1954 in () at /usr/lib/x86_64-linux-gnu/libQt5Script.so.5 #4 0x7fca1b0d1999 in () at /usr/lib/x86_64-linux-gnu/libQt5Script.so.5 #5 0x7fca17e206db in start_thread (arg=0x7fc9e7014700) at pthread_create.c:463 #6 0x7fca1ede688f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 4 (Thread 0x7fc9fca25700 (LWP 3622)): #0 0x7fca1edd9cf6 in __GI_ppoll (fds=0x7fc9f4000d28, nfds=1, timeout=, sigmask=0x0) at ../sysdeps/unix/sysv/linux/ppoll.c:39 #1 0x7fca1c3e2d51 in qt_safe_poll(pollfd*, unsigned long, timespec const*) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x7fca1c3e445e in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #3 0x7fca1c38b30a in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7fca1c1b6bba in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7fca168ac4f5 in () at /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #6 0x7fca1c1c1adb in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7fca17e206db in start_thread (arg=0x7fc9fca25700) at pthread_create.c:463 #8 0x7fca1ede688f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 3 (Thread 0x7fc9ff7ef700 (LWP 3619)): #0 0x7fca1edd9cf6 in __GI_ppoll (fds=0x7fc9f800eb98, nfds=1, timeout=, sigmask=0x0) at ../sysdeps/unix/sysv/linux/ppoll.c:39 #1 0x7fca1c3e2d51 in qt_safe_poll(pollfd*, unsigned long, timespec const*) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x7fca1c3e445e in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #3 0x7fca1c38b30a in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4
[krita] [Bug 384081] Vector markers start-end line styles not loaded on Windows and macOS
https://bugs.kde.org/show_bug.cgi?id=384081 --- Comment #11 from Pablo --- (In reply to Boudewijn Rempt from comment #10) > The problem is actually that the markers don't get loaded on macOS, not that > the combobox is broken. That may be the reason but, remember, I have also tested it under Windows 10 and it happens the same... -- You are receiving this mail because: You are watching all bug changes.
[kio] [Bug 308542] I am not work the Dolphin file manager when connecting with USB my cellular phone Samsung Galaxy SII I9100 with Android 4.0.X
https://bugs.kde.org/show_bug.cgi?id=308542 Pablo Provasi changed: What|Removed |Added Status|NEEDSINFO |RESOLVED --- Comment #5 from Pablo Provasi --- (In reply to Andrew Crouthamel from comment #4) > Dear Bug Submitter, > > This bug has been in NEEDSINFO status with no change for at least 15 days. > Please provide the requested information as soon as possible and set the bug > status as REPORTED. Due to regular bug tracker maintenance, if the bug is > still in NEEDSINFO status with no change in 30 days, the bug will be closed > as RESOLVED > WORKSFORME due to lack of needed information. > > For more information about our bug triaging procedures please read the wiki > located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging > > If you have already provided the requested information, please set the bug > status as REPORTED so that the KDE team knows that the bug is ready to be > confirmed. > > Thank you for helping us make KDE software even better for everyone! Dear friend. Yo reporté el error hace 3 teléfonos y 6 años atrás. I reported that bug 3 phones algo and 6 yers ago. Now I do not have that problema. Thank you -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 384081] Vector markers dropdown not working (start-end line styles)
https://bugs.kde.org/show_bug.cgi?id=384081 --- Comment #9 from Pablo --- Hi Dimitry, I can confirm you the bug still persists in Krita 4.1.3, even reseting all configuratons files as you have suggested. I have tried it on Windows 10 and I also get the error... -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 398512] New: Pointer threshold has wrong default?
https://bugs.kde.org/show_bug.cgi?id=398512 Bug ID: 398512 Summary: Pointer threshold has wrong default? Product: systemsettings Version: 5.12.6 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: kcm_mouse Assignee: unassigned-b...@kde.org Reporter: kais...@gmail.com CC: unassigned-b...@kde.org Target Milestone: --- It seems that the "Pointer threshold" value is set to 4 (when doing a clean install with Ubuntu 18.04.1 as base) but its default is 2 (when clicking the default button). So is it correct to be 4 or not? I did a clean install of Ubuntu 18.04.1, installed updates, restarted Then installed kubunto-desktop, restarted, logged in Opened system settings->input devices->mouse->advanced Had some problems with tabs in konsole as seen in: https://bugs.kde.org/show_bug.cgi?id=398497 and noticed that 2 is the default but it is installed with 4 -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 398497] Clicking tabs opens new window
https://bugs.kde.org/show_bug.cgi?id=398497 --- Comment #2 from Pablo --- In dolphin I have no problem. After tesing in dolphin I did as you said and increased the "drag start time" to 1000 from default 500, much better. I noticed something strange in that menu(I use two computers, one where I dont use more than one tab in konsole) that the: Pointer threshold is 4, but pressing the "Defaults"-button sets it to 2. So I did use default on the computer I had problems with multiple tabs in konsole I pressed default so I got: "Pointer threshold" = 2 and "Drag start time" = 500 and I get no problem with the dragging off tabs of Konsole, strange that it has a value of 4 from installation but gets a value of 2 when pressing default. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 398497] New: Clicking tabs opens new window
https://bugs.kde.org/show_bug.cgi?id=398497 Bug ID: 398497 Summary: Clicking tabs opens new window Product: konsole Version: 17.12.3 Platform: Kubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: tabbar Assignee: konsole-de...@kde.org Reporter: kais...@gmail.com Target Milestone: --- Created attachment 114900 --> https://bugs.kde.org/attachment.cgi?id=114900=edit konsole with tabs Seems that with Ubuntu 18.04.1 LTS and kubuntu-desktop (Installed: 1.370) clicking on tabs in konsole is to sensitive, have alot of tabs in open and half the time switching tabs (selecting the tab with the mouse) draws the tabs out to its own window -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 300532] Custom keyboard shortcuts are reset on reboot or logout – KDE 4, KDE 5
https://bugs.kde.org/show_bug.cgi?id=300532 --- Comment #41 from Pablo --- Still same thing, did a fresh install of ubuntu 18 then installed kubuntu-desktop and this bug still is present, here I am trying to set "Activate Application Launcher Widget" under menu-item "Plasma" to "None" as phpstorm uses the shortcut but after each reboot the key is reset. My assignment of "Meta+D" for "Show Desktop" under the "KWin" meny persists -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 374240] Krita crashes when creating a filter layer
https://bugs.kde.org/show_bug.cgi?id=374240 --- Comment #9 from Pablo --- Hi Raghavendra, I have just checked with version 4.1.0 and it works correctly, I have tried adding 2 new filter layers and they worked as expected. =) Do you want me to try anything else? And, of course, thanks a lot for the bug fixing ;) -- You are receiving this mail because: You are watching all bug changes.
