[systemsettings] [Bug 472005] Touchpad disabled after booting, but can be re-enabled in settings
https://bugs.kde.org/show_bug.cgi?id=472005 --- Comment #15 from Rune --- I will be more precise: the laptop's screen broke and now the touchscreen does not work anymore. Ever since this happened, the issue has been gone. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 472005] Touchpad disabled after booting, but can be re-enabled in settings
https://bugs.kde.org/show_bug.cgi?id=472005 --- Comment #13 from Rune --- Unfortunately, I cannot. The laptop on which this problem occured broke. -- You are receiving this mail because: You are watching all bug changes.
[Plasma Vault] [Bug 487597] Error loading vaults
https://bugs.kde.org/show_bug.cgi?id=487597 --- Comment #1 from Rune --- Same problem with weather, except that the icon appears fine. -- You are receiving this mail because: You are watching all bug changes.
[Plasma Vault] [Bug 487597] New: Error loading vaults
https://bugs.kde.org/show_bug.cgi?id=487597 Bug ID: 487597 Summary: Error loading vaults Classification: Plasma Product: Plasma Vault Version: unspecified Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: ivan.cu...@kde.org Reporter: rune.fritzs...@web.de Target Milestone: --- SUMMARY When logging into plasma, a "placeholder" icon (the one that is e.g. used for a new file of unknown type) appears in the system tray. Clicking it informs the user of an error that occured when loading vaults. Note that I do not and have never actually used the vault functionality. STEPS TO REPRODUCE 1. Login to plasma 2. Observe placeholder icon in system tray 3. Click it OBSERVED RESULT The following error is shown: file:///usr/share/plasma/plasmoids/org.kde.plasma.vault/contents/ui/main.qml:102:36: Cannot assign object of type "QQC2.Action" to property of type "Action_QMLTYPE_88*" as the former is neither the same as the latter nor a sub-class of it. EXPECTED RESULT (Not sure, I never used vaults) SOFTWARE/OS VERSIONS Linux: 6.9.2-arch1-1 (64-bit) KDE Plasma Version: 6.0.5 KDE Frameworks Version: 6.2.0 Qt Version: 6.7.1 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 485685] Firefox starts a drag-and-drop operation when anything is in the clipboard and the application window is activated
https://bugs.kde.org/show_bug.cgi?id=485685 Rune P changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #1 from Rune P --- I haven't seen this issue since I upgraded to F40 (Plasma 6) a few days ago. Assuming fixed. -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 477348] Application Dashboard: Can't select items via keyboard after searching
https://bugs.kde.org/show_bug.cgi?id=477348 Rune changed: What|Removed |Added Resolution|FIXED |--- Status|RESOLVED|REOPENED --- Comment #9 from Rune --- This is sadly not fixed. The keyboard navigation does not work after searching, only after just opening the application dashboard. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 466650] Multimonitor-setup: after login on X11, primary DisplayPort monitor loses signal but still counts as enabled and a part of the desktop
https://bugs.kde.org/show_bug.cgi?id=466650 Rune changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #13 from Rune --- Fixed in Plasma 6.04 (or earlier) -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 485736] Dolphin crashes due to memory leak
https://bugs.kde.org/show_bug.cgi?id=485736 Rune changed: What|Removed |Added Summary|Dolphin crashes trying to |Dolphin crashes due to |load previews of large text |memory leak |files | -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 485736] Dolphin crashes trying to load previews of large text files
https://bugs.kde.org/show_bug.cgi?id=485736 --- Comment #1 from Rune --- I thought it was because of the .par files, but that seems to be wrong. In fact, I duplicated the directory, then deleted and restored some files and now everything went back to normal for a short while. I deleted the old directory and renamed the duplicated one to what the old one was, and after restarting dolphin, the problem was there again. Sadly, I have no information on what could be happening here. Additional info: - All directories mentioned here are synced to my Nextcloud - The memory is used by the process "kio-worker" -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 485736] New: Dolphin crashes trying to load previews of large text files
https://bugs.kde.org/show_bug.cgi?id=485736 Bug ID: 485736 Summary: Dolphin crashes trying to load previews of large text files Classification: Applications Product: dolphin Version: 24.02.2 Platform: Arch Linux OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: rune.fritzs...@web.de CC: kfm-de...@kde.org Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. Open a directory containing large text files or its parent directory in dolphin OBSERVED RESULT In the parent directory, the directory containing the text files does not show any preview icons. Memory usage skyrockets and when RAM+Swap is full, dolphin crashes after the system hangs for a few seconds. In my case, the text files (4) are around 600-700MB each and my 32GB of RAM (64 with ZRAM) are full within a few seconds. EXPECTED RESULT Icons indicating text files should be shown on the directory containing them. Memory usage should remain normal. SOFTWARE/OS VERSIONS Linux: 6.8.7 KDE Plasma Version: 6.0.4 KDE Frameworks Version: 6.1.0 Qt Version: 6.7.0 ADDITIONAL INFORMATION Tested with 4 >600mb .par files -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 485685] New: Firefox starts a drag-and-drop operation when anything is in the clipboard and the application window is activated
https://bugs.kde.org/show_bug.cgi?id=485685 Bug ID: 485685 Summary: Firefox starts a drag-and-drop operation when anything is in the clipboard and the application window is activated Classification: Plasma Product: plasmashell Version: 5.27.11 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Clipboard Assignee: plasma-b...@kde.org Reporter: r...@runesverden.dk Target Milestone: 1.0 Firefox (and likely other gtk apps) starts a drag-and-drop operation when anything is in the clipboard and the application window is activated. (I.e. STEPS TO REPRODUCE 1. Copy some text from a terminal window or any other app than Firefox. 2. Switch to the Firefox window while on a webpage that reacts to drag events, e.g. messenger.com. OBSERVED RESULT The webpage will now appear to have started a drag-and-drop operation and display "drop your files here" or similar. EXPECTED RESULT Activating a window should not cause a drag-and-drop operation. Does not happen when the clipboard is empty. SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Plasma Version: 5.27.11 KDE Frameworks Version: 5.115.0 Qt Version: 5.15.12 Fedora 39, Wayland ADDITIONAL INFORMATION According to https://gitlab.gnome.org/GNOME/gtk/-/issues/5519 the issue is caused by: The problem is that plasma(klipper(ksystemclipboard)) is sending "selection" and "primary selection" every time a window is activated, which gtk detects as drag move events. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 485270] Discover shows available updates that don't actually exist
https://bugs.kde.org/show_bug.cgi?id=485270 --- Comment #2 from Rune --- (In reply to Harald Sitter from comment #1) > What does `pkcon get-updates` say? It shows the same updates as discover. They can't be applied though (same error as in discover). -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 485270] New: Discover shows available updates that don't actually exist
https://bugs.kde.org/show_bug.cgi?id=485270 Bug ID: 485270 Summary: Discover shows available updates that don't actually exist Classification: Applications Product: Discover Version: 6.0.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: PackageKit Assignee: plasma-b...@kde.org Reporter: rune.fritzs...@web.de CC: aleix...@kde.org Target Milestone: --- Created attachment 168305 --> https://bugs.kde.org/attachment.cgi?id=168305&action=edit Screenshot of the "fake" updates SUMMARY Discover notifies that there are updates available. Checking manually (pacman), there are no updates. The list of available updates is always the same (see the attached screenshot). Trying to apply these updates results in an error message: "Unknown error ErrorUnknown.:cachyos-v3/graphene: unexpected error" STEPS TO REPRODUCE 1. Install discover and packagekit-qt6 2. Wait for the update notifier to show up OBSERVED RESULT Updates are shown that do not exist EXPECTED RESULT Updates shown in discover should reflect the actual available updates SOFTWARE/OS VERSIONS Linux: 6.8.4-arch1-1 (64-bit) KDE Plasma Version: 6.0.3 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.3 ADDITIONAL INFORMATION I will also file a bug report at archlinux since I am not sure this is the right place. -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 477348] Application Dashboard: Can't select items via keyboard after searching
https://bugs.kde.org/show_bug.cgi?id=477348 Rune changed: What|Removed |Added CC||rune.fritzs...@web.de -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 483142] [wayland] Pressing Enter on Application Dashboard does not open an Application in List
https://bugs.kde.org/show_bug.cgi?id=483142 Rune changed: What|Removed |Added CC||rune.fritzs...@web.de Status|REOPENED|CONFIRMED -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 483269] Cannot Reorder Favourites in Application Dashboard
https://bugs.kde.org/show_bug.cgi?id=483269 Rune changed: What|Removed |Added CC||rune.fritzs...@web.de -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 482928] Font rendering is weird on scaled displays
https://bugs.kde.org/show_bug.cgi?id=482928 --- Comment #3 from Rune --- This problem does not occur for all fonts. For the (default?) DejaVu Sans, font rendering is fine. Using Inter or IBM Plex Sans, the font rendering is weird as described. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 482928] Font rendering is weird on scaled displays
https://bugs.kde.org/show_bug.cgi?id=482928 --- Comment #2 from Rune --- I can reproduce this. It seems to be worse for higher font weights (see attachment). -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 482928] Font rendering is weird on scaled displays
https://bugs.kde.org/show_bug.cgi?id=482928 Rune changed: What|Removed |Added CC||rune.fritzs...@web.de --- Comment #1 from Rune --- Created attachment 166856 --> https://bugs.kde.org/attachment.cgi?id=166856&action=edit Bold and normal weight font comparison -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 481374] Graphics performance in QEMU/KVM guest with virGL is bad
https://bugs.kde.org/show_bug.cgi?id=481374 --- Comment #3 from Rune --- (In reply to Nate Graham from comment #2) > Does it happen on both X11 and Wayland, or only one? It happens in wayland only. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 481374] Graphics performance in QEMU/KVM guest with virGL is bad
https://bugs.kde.org/show_bug.cgi?id=481374 Rune changed: What|Removed |Added Summary|Graphics performance in |Graphics performance in |QEMU/KVM guest with virGL |QEMU/KVM guest with virGL |is bad (Qt 6.7) |is bad -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 481374] Graphics performance in QEMU/KVM guest with virGL is bad
https://bugs.kde.org/show_bug.cgi?id=481374 --- Comment #1 from Rune --- I tried fedora rawhide too - same problem, so this seems to be a problem of some Plasma component, not Qt 6.7 -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 481374] Graphics performance in QEMU/KVM guest with virGL is bad (Qt 6.7)
https://bugs.kde.org/show_bug.cgi?id=481374 Rune changed: What|Removed |Added Platform|Other |Arch Linux Keywords||qt6 -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 481374] New: Graphics performance in QEMU/KVM guest with virGL is bad (Qt 6.7)
https://bugs.kde.org/show_bug.cgi?id=481374 Bug ID: 481374 Summary: Graphics performance in QEMU/KVM guest with virGL is bad (Qt 6.7) Classification: I don't know Product: kde Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: rune.fritzs...@web.de Target Milestone: --- In a VM using QEMU/KVM, Spice and virGL, graphics performance is very bad with Plasma 6 RC 2 installed. This was tested using Arch Linux - without the KDE-unstable Repo enabled, performance is fine (around 120FPS in glxgears); with the repo enabled and thus Plasma 6 RC 2 installed, graphics performance is very bad (20FPS in glxgears). This is very evident in desktop use, not just with 3D-applications. STEPS TO REPRODUCE 1. Install an Arch Linux guest in a QEMU/KVM VM 2. Enable virGL for the guest OBSERVED RESULT Bad graphics performance EXPECTED RESULT Good graphics performance SOFTWARE/OS VERSIONS Linux: 6.7.4-arch1-1 KDE Plasma Version: 5.93.0 KDE Frameworks Version: 5.249.0 Qt Version: 6.7.0 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 472005] Touchpad disabled after booting, but can be re-enabled in settings
https://bugs.kde.org/show_bug.cgi?id=472005 Rune changed: What|Removed |Added Version|5.27.6 |5.27.10 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 472005] Touchpad disabled after booting, but can be re-enabled in settings
https://bugs.kde.org/show_bug.cgi?id=472005 Rune changed: What|Removed |Added Resolution|WORKSFORME |--- Status|RESOLVED|REOPENED --- Comment #11 from Rune --- The problem is back after some usage time. Please tell me which config files could be responsible for this so I can submit them here. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 478711] Changing display scaling for non-standard aspect ratios in a VM replaces the wallpaper and some icons in Plasma with black squares
https://bugs.kde.org/show_bug.cgi?id=478711 --- Comment #8 from Rune --- The wallpaper is only black if it is a .png file, if it is .jpg it works fine. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 478711] Changing display scaling for non-standard aspect ratios in a VM replaces the wallpaper and some icons in Plasma with black squares
https://bugs.kde.org/show_bug.cgi?id=478711 --- Comment #7 from Rune --- The wallpaper does not turn black anymore, however the icons in the logout manager are still replaced by black squares. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 478866] With Qt 6.7, every QDockWidget panel is enabled in every new window
https://bugs.kde.org/show_bug.cgi?id=478866 Rune changed: What|Removed |Added Resolution|UPSTREAM|FIXED --- Comment #18 from Rune --- Not sure which package update was responsible, but on arch (Qt 6.7.0, Linux 6.7.1, Plasma 5.92.0 and Frameworks 5.248.0), this seems to be fixed. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 478711] Changing display scaling for non-standard aspect ratios in a VM replaces the wallpaper and some icons in Plasma with black squares
https://bugs.kde.org/show_bug.cgi?id=478711 Rune changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 478711] Changing display scaling for non-standard aspect ratios in a VM replaces the wallpaper and some icons in Plasma with black squares
https://bugs.kde.org/show_bug.cgi?id=478711 Rune changed: What|Removed |Added Version|5.90.0 |5.91.0 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 478711] Changing display scaling for non-standard aspect ratios in a VM replaces the wallpaper and some icons in Plasma with black squares
https://bugs.kde.org/show_bug.cgi?id=478711 --- Comment #5 from Rune --- Created attachment 164661 --> https://bugs.kde.org/attachment.cgi?id=164661&action=edit Video showing the bug -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 478711] Changing display scaling for non-standard aspect ratios in a VM replaces the wallpaper and some icons in Plasma with black squares
https://bugs.kde.org/show_bug.cgi?id=478711 Rune changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 472005] Touchpad disabled after booting, but can be re-enabled in settings
https://bugs.kde.org/show_bug.cgi?id=472005 Rune changed: What|Removed |Added Ever confirmed|0 |1 Status|RESOLVED|REOPENED Resolution|WORKSFORME |--- --- Comment #9 from Rune --- Recently installed Plasma again on the laptop where the bug originally happened. Deleting all KDE related config files seems to have resolved the issue, maybe that can help identify what went wrong in the first place? -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 479072] Scrolling through app list in application dashboard does not work if it is opened by clicking the plasmoid
https://bugs.kde.org/show_bug.cgi?id=479072 Rune changed: What|Removed |Added Platform|Other |Arch Linux Keywords||qt6 -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 479072] New: Scrolling through app list in application dashboard does not work if it is opened by clicking the plasmoid
https://bugs.kde.org/show_bug.cgi?id=479072 Bug ID: 479072 Summary: Scrolling through app list in application dashboard does not work if it is opened by clicking the plasmoid Classification: Plasma Product: kdeplasma-addons Version: 5.91.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Application Dashboard Assignee: plasma-b...@kde.org Reporter: rune.fritzs...@web.de Target Milestone: --- When opening the application dashboard by clicking the plasmoid, scrolling through the application list does not work. When opening the dashboard using the super key, scrolling works fine. SOFTWARE/OS VERSIONS Linux: 6.6.8-arch1-1 KDE Plasma Version: 5.91.0 KDE Frameworks Version: 5.247.0 Qt Version: 6.7.0 -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 479047] SSH-Manager and Quick Commands are open when starting konsole
https://bugs.kde.org/show_bug.cgi?id=479047 Rune changed: What|Removed |Added Keywords||qt6 -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 479047] New: SSH-Manager and Quick Commands are open when starting konsole
https://bugs.kde.org/show_bug.cgi?id=479047 Bug ID: 479047 Summary: SSH-Manager and Quick Commands are open when starting konsole Classification: Applications Product: konsole Version: 24.01.85 Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: konsole-de...@kde.org Reporter: rune.fritzs...@web.de Target Milestone: --- When opening konsole, the SSH-Manager panel is open. Closing it reveals that the Quick Commands panel is open underneath. SOFTWARE/OS VERSIONS Linux: 6.6.8-arch1-1 KDE Plasma Version: 5.91.0 KDE Frameworks Version: 5.247.0 Qt Version: 6.7.0 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 478711] Changing display scaling for non-standard aspect ratios in a VM replaces the wallpaper and some icons in Plasma with black squares
https://bugs.kde.org/show_bug.cgi?id=478711 --- Comment #2 from Rune --- This only happens in Wayland. I cannot test it on real hardware as I don't have a monitor with such a strange aspect ratio. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 477238] Display resolution and scaling settings not persistent
https://bugs.kde.org/show_bug.cgi?id=477238 --- Comment #7 from Rune --- Just tested: setting an ICC color profile is not remembered either -- You are receiving this mail because: You are watching all bug changes.
[Plasma Workspace Wallpapers] [Bug 478711] New: Changing display scaling for non-standard aspect ratios makes the wallpaper go blank
https://bugs.kde.org/show_bug.cgi?id=478711 Bug ID: 478711 Summary: Changing display scaling for non-standard aspect ratios makes the wallpaper go blank Classification: Plasma Product: Plasma Workspace Wallpapers Version: 5.90.0 Platform: Other OS: Linux Status: REPORTED Keywords: qt6, wayland Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: rune.fritzs...@web.de Target Milestone: --- In the wayland session, for non-standard aspect ratios (e.g. maximized Virtualbox window with auto adjust, for me: 3.839:1.973), changing the display scaling factor results in the wallpaper going black. Some symbols like the ones in the logout/shutdown/reboot menu are replaced by a black rectangle. STEPS TO REPRODUCE 1. Set a non-standard aspect ratio (maybe non-integer?) 2. Change the display scaling OBSERVED RESULT Wallpaper and some icons go black EXPECTED RESULT Wallpaper and icons are unaffected by the changed scaling SOFTWARE/OS VERSIONS Linux: 6.2.0-39 generic KDE Plasma Version: 5.90.90 KDE Frameworks Version: 5.247.0 Qt Version: 6.6.1 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 478662] Login scripts do not work if they are in a hidden directory or are a hidden file themselves
https://bugs.kde.org/show_bug.cgi?id=478662 --- Comment #1 from Rune --- Edit: If the script is in a hidden directory, it is correctly shown in system settings, but does not work. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 478662] Login scripts do not work if they are in a hidden directory or are a hidden file themselves
https://bugs.kde.org/show_bug.cgi?id=478662 Rune changed: What|Removed |Added Platform|Other |Arch Linux -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 478662] New: Login scripts do not work if they are in a hidden directory or are a hidden file themselves
https://bugs.kde.org/show_bug.cgi?id=478662 Bug ID: 478662 Summary: Login scripts do not work if they are in a hidden directory or are a hidden file themselves Classification: I don't know Product: kde Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: rune.fritzs...@web.de Target Milestone: --- Login scripts do not work if they are in a hidden directory or are a hidden file themselves. If such a file is added as a login script in settings, it does not appear there the next time settings are opened and the script is not executed upon login. The corresponding .desktop file in .config/autostart/ exists. STEPS TO REPRODUCE 1. Set a hidden file or a file in a hidden directory as a login script 2. Log in OBSERVED RESULT The script is not executed and the settings do not show it in the autostart section. EXPECTED RESULT The script is executed and can be seen in the autostart section of the settings. SOFTWARE/OS VERSIONS Linux: 6.6.7-arch1-1 (64-bit) KDE Plasma Version: 5.27.10 KDE Frameworks Version: 5.113.0 Qt Version: 5.15.11 -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 477238] New: Display resolution and scaling settings not persistent
https://bugs.kde.org/show_bug.cgi?id=477238 Bug ID: 477238 Summary: Display resolution and scaling settings not persistent Classification: KDE Neon Product: neon Version: unspecified Platform: Other OS: Linux Status: REPORTED Keywords: qt6 Severity: normal Priority: NOR Component: Packages Unstable Edition Assignee: neon-b...@kde.org Reporter: rune.fritzs...@web.de CC: j...@jriddell.org, neon-b...@kde.org, sit...@kde.org Target Milestone: --- STEPS TO REPRODUCE 1. Boot Neon unstable in a VM 2. Set display resolution and scaling 3. Reboot OBSERVED RESULT The display resolution is reset to 800x600 after reboot. Scaling is reset to 100%. EXPECTED RESULT The settings should persist after a reboot. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Linux 6.2.0-36-generic (available in About System) KDE Plasma Version: 5.81.80 KDE Frameworks Version: 5.245.0 Qt Version: 6.6.0 -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 476933] New: Installer shortcut in welcome center not working and not showing the correct icon
https://bugs.kde.org/show_bug.cgi?id=476933 Bug ID: 476933 Summary: Installer shortcut in welcome center not working and not showing the correct icon Classification: KDE Neon Product: neon Version: unspecified Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Packages Unstable Edition Assignee: neon-b...@kde.org Reporter: rune.fritzs...@web.de CC: j...@jriddell.org, neon-b...@kde.org, sit...@kde.org Target Milestone: --- Created attachment 163116 --> https://bugs.kde.org/attachment.cgi?id=163116&action=edit Screenshot of the missing icon STEPS TO REPRODUCE 1. Boot into the KDE neon unstable live environment. 2. Click on the installer launcher in the welcome app. OBSERVED RESULT The icon of the installer launcher is the blank file icon instead of the correct one. Clicking on the icon throws this error: "Internal error: could not prompt the user for which application to start" EXPECTED RESULT The launcher has the correct icon and starts the installer. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Linux 6.2.0-36-generic KDE Plasma Version: 5.81.0 KDE Frameworks Version: 5.245.0 Qt Version: 6.6.0 -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 476791] Installation window is transparent
https://bugs.kde.org/show_bug.cgi?id=476791 --- Comment #2 from Rune --- I found a workaround: this issue does not occur in the X11 session. To get to the X11 session, you need to disable automatic login, log out, and then log in to Plasma (X11) using a blank password. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 476791] Installation window is transparent
https://bugs.kde.org/show_bug.cgi?id=476791 Rune changed: What|Removed |Added CC||rune.fritzs...@web.de --- Comment #1 from Rune --- I can reproduce this. The problem with the transparent windows occurs for any software that you try to start with superuser rights. Calamares can be started without issue if it is not started as a superuser, but then it obviously does not work to install the system. -- You are receiving this mail because: You are watching all bug changes.
[kolourpaint] [Bug 476134] New: Flatpak Kolourpaint does not show up in launcher
https://bugs.kde.org/show_bug.cgi?id=476134 Bug ID: 476134 Summary: Flatpak Kolourpaint does not show up in launcher Classification: Applications Product: kolourpaint Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kolourpaint-supp...@lists.sourceforge.net Reporter: soren.nissen+...@gmail.com Target Milestone: --- SUMMARY Flatpak Kolourpaint does not show up in launcher STEPS TO REPRODUCE 1. Install Kolourpaint 2. Open the launcher 3. Type "paint" OBSERVED RESULT Flatpak Kolourpaint does not show up in launcher EXPECTED RESULT Kolourpaint does not show up in launcher SOFTWARE/OS VERSIONS * Kolourpaint 23.08.2 * Pop!_OS 22.04 LTS * Gnome 42.9 ADDITIONAL INFORMATION Presumably due to missing keywords in .desktop, see: https://github.com/pop-os/launcher/issues/167#issuecomment-1780388408 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 472005] Touchpad disabled after booting, can be re-enabled in settings.
https://bugs.kde.org/show_bug.cgi?id=472005 --- Comment #4 from Rune --- (In reply to Nate Graham from comment #2) > After re-enabling the touchpad in System Settings, when you flip your laptop > into tablet mode, does the "enabled" checkbox get unchecked in System > Settings? or does it remain checked despite te touchpad being (correctly) > disabled while in tablet mode? Yes, the checkbox correctly gets unchecked. Only after I close the system settings and open them again though. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 472005] Touchpad disabled after booting, can be re-enabled in settings.
https://bugs.kde.org/show_bug.cgi?id=472005 --- Comment #1 from Rune --- I can now confirm that it happens on every boot. The settings show a connected mouse, which might disable the touchpad? There is no mouse connected. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 472005] Touchpad disabled after booting, can be re-enabled in settings.
https://bugs.kde.org/show_bug.cgi?id=472005 Rune changed: What|Removed |Added Summary|Touchpad sometimes disabled |Touchpad disabled after |after booting, can be |booting, can be re-enabled |re-enabled in settings. |in settings. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 472005] New: Touchpad sometimes disabled after booting, can be re-enabled in settings.
https://bugs.kde.org/show_bug.cgi?id=472005 Bug ID: 472005 Summary: Touchpad sometimes disabled after booting, can be re-enabled in settings. Classification: Applications Product: systemsettings Version: 5.27.6 Platform: Archlinux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_touchpad Assignee: plasma-b...@kde.org Reporter: rune.fritzs...@web.de CC: natalie_clar...@yahoo.de 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. Log into KDE plasma (I am using the wayland session, but I don't think it's different on X11) 2. Try using the touchpad OBSERVED RESULT Touchpad sometimes does not work. By navigating to the settings, it is apparent that the touchpad is diabled. It can be re-enabled. Trying to re-enable the touchpad using the keyboard macro button does not work. EXPECTED RESULT The toucpad should work normally and should never be disabled without the user requesting it. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: KDE Plasma 5.27.6 on Archlinux (available in About System) KDE Plasma Version: 5.27.6 KDE Frameworks Version: 5.107.0 Qt Version: 5.15.10 ADDITIONAL INFORMATION I am using a convertible laptop with a touchscreen. When converting it to tablet mode, the touchpad is automatically disabled (as it should be). This interaction might be causing the problem, I have no means of testing this as I only have this laptop. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 466238] Exiting full screen video playback with on a multi-monitor setup causes a freeze
https://bugs.kde.org/show_bug.cgi?id=466238 --- Comment #42 from Rune --- (In reply to Vlad Zahorodnii from comment #41) > Given comment 38, the original issue has been fixed so this bug report can > be closed. Please open a new bug report for the flickering issue. As stated in comment 39, this is not the case. The original issue still exists, it just takes a little bit of time in fullscreen before it happens. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 466238] Exiting full screen video playback with on a multi-monitor setup causes a freeze
https://bugs.kde.org/show_bug.cgi?id=466238 --- Comment #40 from Rune --- The flickering issue still randomly appears. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 466238] Exiting full screen video playback with on a multi-monitor setup causes a freeze
https://bugs.kde.org/show_bug.cgi?id=466238 --- Comment #39 from Rune --- (In reply to Rune from comment #38) > It seems like the issue with exiting fullscreen video playback has been > fixed in 5.27.5. I can't comment on the flickering issue yet. It is not fixed completely. It just does not happen every time anymore. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 466238] Exiting full screen video playback with on a multi-monitor setup causes a freeze
https://bugs.kde.org/show_bug.cgi?id=466238 --- Comment #38 from Rune --- It seems like the issue with exiting fullscreen video playback has been fixed in 5.27.5. I can't comment on the flickering issue yet. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 466238] Exiting full screen video playback with on a multi-monitor setup causes a freeze
https://bugs.kde.org/show_bug.cgi?id=466238 --- Comment #36 from Rune --- Created attachment 158785 --> https://bugs.kde.org/attachment.cgi?id=158785&action=edit Recording of the artifacts -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 466238] Exiting full screen video playback with on a multi-monitor setup causes a freeze
https://bugs.kde.org/show_bug.cgi?id=466238 --- Comment #35 from Rune --- (In reply to Rune from comment #34) > (In reply to Zamundaaa from comment #33) > > ok, that sounds like a driver bug then. Are you using adaptive sync? If so, > > does disabling that change anything? > > It was set to automatic, I now have it set to never. For video playback, > without the NP_DIRECT_SCANOUT line, exiting full screen still causes the > screen to become unresponsive. I will watch if the flickering issue happens > again, as it is kind of rare. Okay, the artifacting happened again today while playing back video even though adaptive sync is set to never. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 466238] Exiting full screen video playback with on a multi-monitor setup causes a freeze
https://bugs.kde.org/show_bug.cgi?id=466238 --- Comment #34 from Rune --- (In reply to Zamundaaa from comment #33) > ok, that sounds like a driver bug then. Are you using adaptive sync? If so, > does disabling that change anything? It was set to automatic, I now have it set to never. For video playback, without the NP_DIRECT_SCANOUT line, exiting full screen still causes the screen to become unresponsive. I will watch if the flickering issue happens again, as it is kind of rare. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 466238] Exiting full screen video playback with on a multi-monitor setup causes a freeze
https://bugs.kde.org/show_bug.cgi?id=466238 --- Comment #32 from Rune --- (In reply to Zamundaaa from comment #31) > Can you describe the flicker in more detail? With > KWIN_DRM_NO_DIRECT_SCANOUT=1 set, there should be no difference for native > Wayland apps vs windowed, at least on the KWin and driver side. The "flickering" starts at the upper edge of the screen, it is a multi-colored bar (whole width of the screen) that flickers and sometimes travels down the screen while flickering. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 466238] Exiting full screen video playback with on a multi-monitor setup causes a freeze
https://bugs.kde.org/show_bug.cgi?id=466238 --- Comment #30 from Rune --- (In reply to Zamundaaa from comment #29) > Do you know if this has happened with native Wayland apps, or only with > Xwayland? This has happened in both - Xwayland (wine game) and Firefox (wayland enabled) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 466238] Exiting full screen video playback with on a multi-monitor setup causes a freeze
https://bugs.kde.org/show_bug.cgi?id=466238 --- Comment #28 from Rune --- (In reply to Zamundaaa from comment #27) > Do you ever get artifacts with an app in windowed mode? No, never. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 466238] Exiting full screen video playback with on a multi-monitor setup causes a freeze
https://bugs.kde.org/show_bug.cgi?id=466238 --- Comment #26 from Rune --- I think this is the same problem, so I am adding to this thread. I have been using the wayland session with KWIN_DRM_NO_DIRECT_SCANOUT=1 since it provided a workaround. Lately (maybe since updating to 5.27.4?), I have been getting screen artifacts in full screen applications, including games, so this is not limited to video playback. Note that this happens pretty irregularily, mostly after a long time of using the fullscreen application, but sometimes directly after starting it. When the flickering artifacts appear, the framerate also becomes very very low. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 466238] Exiting full screen video playback with on a multi-monitor setup causes a freeze
https://bugs.kde.org/show_bug.cgi?id=466238 --- Comment #25 from Rune --- I think this is the same problem, so I am adding to this thread. I have been using the wayland session with KWIN_DRM_NO_DIRECT_SCANOUT=1 since it provided a workaround. Lately (maybe since updating to 5.27.4?), I have been getting screen artifacts in full screen applications, including games, so this is not limited to video playback. Note that this happens pretty irregularily, mostly after a long time of using the fullscreen application, but sometimes directly after starting it. When the flickering artifacts appear, the framerate also becomes very very low. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 466238] Exiting full screen video playback with on a multi-monitor setup causes a freeze
https://bugs.kde.org/show_bug.cgi?id=466238 --- Comment #24 from Rune --- Created attachment 157144 --> https://bugs.kde.org/attachment.cgi?id=157144&action=edit DRM log -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 466238] Exiting full screen video playback with on a multi-monitor setup causes a freeze
https://bugs.kde.org/show_bug.cgi?id=466238 --- Comment #22 from Rune --- (In reply to Zamundaaa from comment #21) > good, that narrows it down a lot. To narrow it down further, could you > remove that again and test with > > KWIN_DRM_PREFER_COLOR_DEPTH=24 > and > > KWIN_DRM_USE_MODIFIERS=0 > (one at a time only) instead? Neither one of those helped. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 466238] Exiting full screen video playback with on a multi-monitor setup causes a freeze
https://bugs.kde.org/show_bug.cgi?id=466238 --- Comment #20 from Rune --- (In reply to Zamundaaa from comment #19) > This seems to be caused by direct scanout, which you can disable by putting > > KWIN_DRM_NO_DIRECT_SCANOUT=1 > into /etc/environment and rebooting. If you do that, does the hang still > happen? Yes, that fixes the issue! -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 466650] Multimonitor-setup: after login on X11, primary DisplayPort monitor loses signal but still counts as enabled and a part of the desktop
https://bugs.kde.org/show_bug.cgi?id=466650 --- Comment #11 from Rune --- (In reply to Nate Graham from comment #10) > So if you log into the Wayland session, log out, and log back into the > Wayland session, it works? No, if I logged into the wayland session before logging into the X11 session, it works. The error never occurs in the wayland session. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 466650] Multimonitor-setup: after login on X11, primary DisplayPort monitor loses signal but still counts as enabled and a part of the desktop
https://bugs.kde.org/show_bug.cgi?id=466650 --- Comment #9 from Rune --- (In reply to Rune from comment #8) > Additional info: The problem only occurs on the first login after booting. > If I log out and in again, everything works as intended. That is, if I log into the wayland session (where the monitor is detected properly) and log back out and then into the X11 session. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 466650] Multimonitor-setup: after login on X11, primary DisplayPort monitor loses signal but still counts as enabled and a part of the desktop
https://bugs.kde.org/show_bug.cgi?id=466650 --- Comment #8 from Rune --- Additional info: The problem only occurs on the first login after booting. If I log out and in again, everything works as intended. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 466238] Exiting full screen video playback with on a multi-monitor setup causes a freeze
https://bugs.kde.org/show_bug.cgi?id=466238 --- Comment #18 from Rune --- (In reply to Zamundaaa from comment #11) > That's odd, there's not even a single relevant warning in that log. To > narrow down where to go from here, please attach the output of drm_info > (https://gitlab.freedesktop.org/emersion/drm_info) > - once before you play the video, just on the desktop > - once while you play the video in fullscreen > - twice after you try exiting fullscreen, with at least a few seconds in > between > > Also, if you drag another window on top of the fullscreen video instead of > exiting fullscreen, does that also cause the problem? I attached the requested logs. If I drag a window on top of the video, the behaviour is about the same as when trying to exit fullscreen: artifacts and the screen becomes unresponsive. The window never shows up, it is dragged "behind" the video. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 466238] Exiting full screen video playback with on a multi-monitor setup causes a freeze
https://bugs.kde.org/show_bug.cgi?id=466238 --- Comment #17 from Rune --- Created attachment 157059 --> https://bugs.kde.org/attachment.cgi?id=157059&action=edit Output of drm_info around 20 seconds later -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 466238] Exiting full screen video playback with on a multi-monitor setup causes a freeze
https://bugs.kde.org/show_bug.cgi?id=466238 --- Comment #16 from Rune --- Created attachment 157058 --> https://bugs.kde.org/attachment.cgi?id=157058&action=edit Output of drm_info after trying to exit fullscreen playback -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 466238] Exiting full screen video playback with on a multi-monitor setup causes a freeze
https://bugs.kde.org/show_bug.cgi?id=466238 --- Comment #15 from Rune --- Created attachment 157057 --> https://bugs.kde.org/attachment.cgi?id=157057&action=edit Output of drm_info during playback -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 466238] Exiting full screen video playback with on a multi-monitor setup causes a freeze
https://bugs.kde.org/show_bug.cgi?id=466238 --- Comment #14 from Rune --- Created attachment 157056 --> https://bugs.kde.org/attachment.cgi?id=157056&action=edit Output of drm_info on the desktop -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 466238] Exiting full screen video playback with on a multi-monitor setup causes a freeze
https://bugs.kde.org/show_bug.cgi?id=466238 --- Comment #13 from Rune --- (In reply to Nate Graham from comment #12) > (In reply to Rune from comment #7) > > I have to add: the HDMI monitor (secondary) has a different refresh rate > > (66Hz) than the primary one (60Hz). > Hmm, maybe it's Bug 465712? No, I only see these glitches when I exit fullscreen video playback. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 466238] Exiting full screen video playback with on a multi-monitor setup causes a freeze
https://bugs.kde.org/show_bug.cgi?id=466238 --- Comment #10 from Rune --- Created attachment 157039 --> https://bugs.kde.org/attachment.cgi?id=157039&action=edit Output of journalctl --user-unit plasma-kwin_wayland --boot 0 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 466238] Exiting full screen video playback with on a multi-monitor setup causes a freeze
https://bugs.kde.org/show_bug.cgi?id=466238 --- Comment #9 from Rune --- (In reply to Zamundaaa from comment #8) > Please attach the output of > > journalctl --user-unit plasma-kwin_wayland --boot 0 > after making the bug happen again Output attached. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 466650] Multimonitor-setup: after login on X11, primary DisplayPort monitor loses signal but still counts as enabled and a part of the desktop
https://bugs.kde.org/show_bug.cgi?id=466650 --- Comment #6 from Rune --- I have to add: the HDMI monitor (secondary) has a different refresh rate (66Hz) than the primary one (60Hz). -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 466238] Exiting full screen video playback with on a multi-monitor setup causes a freeze
https://bugs.kde.org/show_bug.cgi?id=466238 --- Comment #7 from Rune --- I have to add: the HDMI monitor (secondary) has a different refresh rate (66Hz) than the primary one (60Hz). -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 466650] Multimonitor-setup: after login on X11, primary DisplayPort monitor loses signal but still counts as enabled and a part of the desktop
https://bugs.kde.org/show_bug.cgi?id=466650 --- Comment #5 from Rune --- I now most of the time get a window saying that Plasma crashed and that I can report a bug. Sadly, this window closes before I can actually report it properly. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 466650] Multimonitor-setup: after login on X11, primary DisplayPort monitor loses signal but still counts as enabled and a part of the desktop
https://bugs.kde.org/show_bug.cgi?id=466650 --- Comment #4 from Rune --- Output: 68 DP-1 disabled disconnected priority 0 DisplayPort Modes: Geometry: 0,0 0x0 Scale: 1 Rotation: 1 Overscan: 0 Vrr: incapable RgbRange: unknown Output: 69 DP-2 enabled connected priority 1 DisplayPort Modes: 73:3840x2160@60*! 74:3840x2160@60 75:3840x2160@30 76:3200x1800@60 77:3200x1800@60 78:2880x1620@60 79:2880x1620@60 80:2560x1600@60 81:2560x1600@60 82:2560x1440@60 83:2560x1440@60 84:2560x1440@60 85:2048x1536@60 86:1920x1440@60 87:1856x1392@60 88:1792x1344@60 89:2048x1152@60 90:2048x1152@60 91:2048x1152@60 92:2048x1152@60 93:1920x1200@60 94:1920x1200@60 95:1920x1200@60 96:1920x1080@60 97:1920x1080@60 98:1920x1080@60 99:1920x1080@60 100:1920x1080@60 101:1920x1080@60 102:1600x1200@60 103:1600x1200@60 104:1680x1050@60 105:1680x1050@60 106:1680x1050@60 107:1400x1050@60 108:1600x900@60 109:1600x900@60 110:1600x900@60 111:1600x900@60 112:1600x900@60 113:1280x1024@60 114:1440x900@60 115:1400x900@60 116:1400x900@60 117:1280x960@60 118:1440x810@60 119:1440x810@60 120:1368x768@60 121:1368x768@60 122:1280x800@60 123:1280x800@60 124:1280x800@60 125:1280x800@60 126:1152x864@60 127:1280x720@60 128:1280x720@60 129:1280x720@60 130:1280x720@60 131:1280x720@60 132:1280x720@60 133:1024x768@60 134:1024x768@60 135:960x720@60 136:928x696@60 137:896x672@60 138:1024x576@60 139:1024x576@60 140:1024x576@60 141:1024x576@60 142:960x600@60 143:960x600@60 144:960x540@60 145:960x540@60 146:960x540@60 147:960x540@60 148:800x600@60 149:800x600@60 150:800x600@56 151:840x525@60 152:840x525@60 153:864x486@60 154:864x486@60 155:700x525@60 156:800x450@60 157:800x450@60 158:720x480@60 159:720x480@60 160:640x512@60 161:700x450@60 162:700x450@60 163:640x480@60 164:640x480@60 165:640x480@60 166:720x405@60 167:720x405@59 168:684x384@60 169:684x384@60 170:640x400@60 171:640x400@60 172:640x360@60 173:640x360@60 174:640x360@60 175:640x360@59 176:512x384@60 177:512x288@60 178:512x288@60 179:480x270@60 180:480x270@60 181:400x300@60 182:400x300@56 183:432x243@60 184:432x243@60 185:320x240@60 186:360x202@60 187:360x202@59 188:320x180@60 189:320x180@59 Geometry: 0,0 3840x2160 Scale: 1 Rotation: 1 Overscan: 0 Vrr: incapable RgbRange: unknown Output: 70 DP-3 disabled disconnected priority 0 DisplayPort Modes: Geometry: 0,0 0x0 Scale: 1 Rotation: 1 Overscan: 0 Vrr: incapable RgbRange: unknown Output: 71 HDMI-1 enabled connected priority 2 HDMI Modes: 156:800x450@60 157:800x450@60 161:700x450@60 162:700x450@60 163:640x480@60 165:640x480@60 166:720x405@60 167:720x405@59 168:684x384@60 169:684x384@60 170:640x400@60 171:640x400@60 172:640x360@60 173:640x360@60 174:640x360@60 175:640x360@59 176:512x384@60 177:512x288@60 178:512x288@60 179:480x270@60 180:480x270@60 181:400x300@60 182:400x300@56 183:432x243@60 184:432x243@60 185:320x240@60 186:360x202@60 187:360x202@59 188:320x180@60 189:320x180@59 190:800x480@66*! 191:640x480@66 Geometry: 3840,1680 800x480 Scale: 1 Rotation: 4 Overscan: 0 Vrr: incapable RgbRange: unknown -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 466650] Multimonitor-setup: Primary monitor disconnects after login
https://bugs.kde.org/show_bug.cgi?id=466650 --- Comment #2 from Rune --- (In reply to Nate Graham from comment #1) > When the DP screen goes black, can you move the cursor onto it or does it > stop at the shared screen edge? If you can, does the cursor remain visible > when moving onto the black screen? If it is, when you right-click on the > black background, what happens? I have not been clear here, the screen actually goes into power saving/no signal mode. I can move my cursor there (it is not visible of course) and even click things - I had a firefox window restored there from the previous session and was able to start a video there without seeing anything. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 466650] New: Multimonitor-setup: Primary monitor disconnects after login
https://bugs.kde.org/show_bug.cgi?id=466650 Bug ID: 466650 Summary: Multimonitor-setup: Primary monitor disconnects after login Classification: Plasma Product: kwin Version: 5.27.2 Platform: Archlinux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: multi-screen Assignee: kwin-bugs-n...@kde.org Reporter: rune.fritzs...@web.de Target Milestone: --- Flags: Wayland-, X11+ SUMMARY When I log into the X11-Session, my primary monitor (which is detected by sddm-git) goes black. It is connected via DisplayPort, the secondary monitor that is always detected is connect via HDMI. If I turn the monitor off and on again it is then detected properly and works fine. STEPS TO REPRODUCE 1. Log in to Plasma(X11) while using multiple monitors. One of them might have to be connected via DisplayPort. 2. Wait for the splash screen to disappear. 3. The secondary monitor shows the plasma desktop, while the primary monitor goes black. OBSERVED RESULT The secondary monitor shows the plasma desktop, while the primary monitor goes black. EXPECTED RESULT Both monitors show the plasma desktop. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Linux 6.2.1-arch1-1 (64-bit) (available in About System) KDE Plasma Version: 5.27.2 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 466238] Exiting full screen video playback with on a multi-monitor setup causes a freeze
https://bugs.kde.org/show_bug.cgi?id=466238 Rune changed: What|Removed |Added Version|5.27.0 |5.27.1 Summary|Exiting full screen video |Exiting full screen video |playback with on a |playback with on a |multi-monitor setup with|multi-monitor setup causes |different scaling factors |a freeze |causes a freeze | -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 466238] Exiting full screen video playback with on a multi-monitor setup with different scaling factors causes a freeze
https://bugs.kde.org/show_bug.cgi?id=466238 --- Comment #6 from Rune --- (In reply to Rune from comment #5) > (In reply to Rune from comment #0) > > SUMMARY > > > > Having multiple screens with different scaling factors in the plasma wayland > > session makes it impossible to exit fullscreen video playback. The screen > > that played back the video becomes unusable, the second screen works fine. > > Graphical glitches can be observed on the primary screen when trying to exit > > the full screen playback. > > > > > > STEPS TO REPRODUCE > > 1. Set different scaling factors on two monitors. > > 2. Start playing back video in full screen mode (tried firefox (Youtube, > > Netflix) as well as VLC (local file). > > 3. Try exiting the playback. > > > > OBSERVED RESULT > > > > The screen becomes unresponsive and shows graphical artifacts. > > > > EXPECTED RESULT > > > > The video playback can be exited normally. > > > > SOFTWARE/OS VERSIONS > > Linux/KDE Plasma: Arch Linux 6.1.12-arch > > (available in About System) > > KDE Plasma Version: 5.27.1 > > KDE Frameworks Version: 5.103.0 > > Qt Version: 5.15.8 > > > > ADDITIONAL INFORMATION > > > > AMD GPU with open source drivers, though proprietary OpenGL driver is > > installed. Hardware acceleration is enabled. > > More info: Even without mixed scaling factors, being unable to exit > fullscreen is a problem. Wether it occurs or not seems to be linked to the > time spent in fullscreen mode, > It also does only happen with video playback, not when playing e.g. video > games in full screen. Uninstalling the amdgpu-pro-oglp package (Proprietary AMD OpenGL driver) did not help. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 466238] Exiting full screen video playback with on a multi-monitor setup with different scaling factors causes a freeze
https://bugs.kde.org/show_bug.cgi?id=466238 --- Comment #5 from Rune --- (In reply to Rune from comment #0) > SUMMARY > > Having multiple screens with different scaling factors in the plasma wayland > session makes it impossible to exit fullscreen video playback. The screen > that played back the video becomes unusable, the second screen works fine. > Graphical glitches can be observed on the primary screen when trying to exit > the full screen playback. > > > STEPS TO REPRODUCE > 1. Set different scaling factors on two monitors. > 2. Start playing back video in full screen mode (tried firefox (Youtube, > Netflix) as well as VLC (local file). > 3. Try exiting the playback. > > OBSERVED RESULT > > The screen becomes unresponsive and shows graphical artifacts. > > EXPECTED RESULT > > The video playback can be exited normally. > > SOFTWARE/OS VERSIONS > Linux/KDE Plasma: Arch Linux 6.1.12-arch > (available in About System) > KDE Plasma Version: 5.27.1 > KDE Frameworks Version: 5.103.0 > Qt Version: 5.15.8 > > ADDITIONAL INFORMATION > > AMD GPU with open source drivers, though proprietary OpenGL driver is > installed. Hardware acceleration is enabled. More info: Even without mixed scaling factors, being unable to exit fullscreen is a problem. Wether it occurs or not seems to be linked to the time spent in fullscreen mode, It also does only happen with video playback, not when playing e.g. video games in full screen. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 466238] Exiting full screen video playback with on a multi-monitor setup with different scaling factors causes a freeze
https://bugs.kde.org/show_bug.cgi?id=466238 --- Comment #3 from Rune --- (In reply to Nate Graham from comment #2) > What scale factors are you using on each screen? 1.5 on my primary and 1 on my secondary. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 466238] Exiting full screen video playback with on a multi-monitor setup with different scaling factors causes a freeze
https://bugs.kde.org/show_bug.cgi?id=466238 --- Comment #1 from Rune --- (In reply to Rune from comment #0) > SUMMARY > > Having multiple screens with different scaling factors in the plasma wayland > session makes it impossible to exit fullscreen video playback. The screen > that played back the video becomes unusable, the second screen works fine. > Graphical glitches can be observed on the primary screen when trying to exit > the full screen playback. > > > STEPS TO REPRODUCE > 1. Set different scaling factors on two monitors. > 2. Start playing back video in full screen mode (tried firefox (Youtube, > Netflix) as well as VLC (local file). > 3. Try exiting the playback. > > OBSERVED RESULT > > The screen becomes unresponsive and shows graphical artifacts. > > EXPECTED RESULT > > The video playback can be exited normally. > > SOFTWARE/OS VERSIONS > Linux/KDE Plasma: Arch Linux 6.1.12-arch > (available in About System) > KDE Plasma Version: 5.27.1 > KDE Frameworks Version: 5.103.0 > Qt Version: 5.15.8 > > ADDITIONAL INFORMATION > > AMD GPU with open source drivers, though proprietary OpenGL driver is > installed. Hardware acceleration is enabled. The graphical glitches also occur with non-mixed scaling factors. It is possible to exit fullscreen though. Graphical artifafcts on newly drawn elements persist until reboot. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 466238] New: Exiting full screen video playback with on a multi-monitor setup with different scaling factors causes a freeze
https://bugs.kde.org/show_bug.cgi?id=466238 Bug ID: 466238 Summary: Exiting full screen video playback with on a multi-monitor setup with different scaling factors causes a freeze Classification: I don't know Product: kde Version: unspecified Platform: Archlinux OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: rune.fritzs...@web.de Target Milestone: --- SUMMARY Having multiple screens with different scaling factors in the plasma wayland session makes it impossible to exit fullscreen video playback. The screen that played back the video becomes unusable, the second screen works fine. Graphical glitches can be observed on the primary screen when trying to exit the full screen playback. STEPS TO REPRODUCE 1. Set different scaling factors on two monitors. 2. Start playing back video in full screen mode (tried firefox (Youtube, Netflix) as well as VLC (local file). 3. Try exiting the playback. OBSERVED RESULT The screen becomes unresponsive and shows graphical artifacts. EXPECTED RESULT The video playback can be exited normally. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux 6.1.12-arch (available in About System) KDE Plasma Version: 5.27.1 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 ADDITIONAL INFORMATION AMD GPU with open source drivers, though proprietary OpenGL driver is installed. Hardware acceleration is enabled. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 380201] Dolphin Crash when renaming and moving folders into folders.
https://bugs.kde.org/show_bug.cgi?id=380201 Rune Kock changed: What|Removed |Added CC||rune.k...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 380201] Dolphin Crash when renaming and moving folders into folders.
https://bugs.kde.org/show_bug.cgi?id=380201 --- Comment #1 from Rune Kock --- Created attachment 108085 --> https://bugs.kde.org/attachment.cgi?id=108085&action=edit New crash information added by DrKonqi dolphin (16.08.3) using Qt 5.9.1 - What I was doing when the application crashed: Creating new folder and moving files into it. Then folding open the new folder. - Unusual behavior I noticed: The new folder displayed at the wrong position in the tree. When I tried further folding in/out, the crash occurred. -- Backtrace (Reduced): #6 0x7f22944040ec in KFileItemModel::expandedParentsCount(KFileItemModel::ItemData const*) () from /usr/lib/x86_64-linux-gnu/libdolphinprivate.so.5 #7 0x7f229442a571 in KItemListView::hasSiblingSuccessor(int) const () from /usr/lib/x86_64-linux-gnu/libdolphinprivate.so.5 #8 0x7f229442c0f5 in KItemListView::updateSiblingsInformation(int, int) () from /usr/lib/x86_64-linux-gnu/libdolphinprivate.so.5 #9 0x7f22944330cc in KItemListView::slotItemsRemoved(KItemRangeList const&) () from /usr/lib/x86_64-linux-gnu/libdolphinprivate.so.5 [...] #11 0x7f229448b735 in KItemModelBase::itemsRemoved(KItemRangeList const&) () from /usr/lib/x86_64-linux-gnu/libdolphinprivate.so.5 -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 380275] New: Krunner crashed when trying to evaluate 129*0,19
https://bugs.kde.org/show_bug.cgi?id=380275 Bug ID: 380275 Summary: Krunner crashed when trying to evaluate 129*0,19 Product: krunner Version: 5.8.6 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@privat.broulik.de Reporter: jensr...@gmail.com Target Milestone: --- Application: krunner (5.8.6) Qt Version: 5.6.1 Frameworks Version: 5.26.0 Operating System: Linux 4.4.62-18.6-default x86_64 Distribution: "openSUSE Leap 42.2" -- Information about the crash: - What I was doing when the application crashed: Long time running (several days), so porbably swapped out krunner. Entered 129*0,19 into krunner to get it calculated, it failed because the decimal symbol is dot and not comma -- Backtrace: Application: krunner (krunner), signal: Aborted Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f6be2d358c0 (LWP 9390))] Thread 12 (Thread 0x7f6b95ffb700 (LWP 14707)): #0 0x7f6bdc17d0bf in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f6bdec3b65b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/libQt5Core.so.5 #2 0x7f6bc10ac42f in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #3 0x7f6bc10afdea in () at /usr/lib64/libKF5ThreadWeaver.so.5 #4 0x7f6bc10aa45b in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #5 0x7f6bc10ada46 in ThreadWeaver::Thread::run() () at /usr/lib64/libKF5ThreadWeaver.so.5 #6 0x7f6bdec3a9e9 in () at /usr/lib64/libQt5Core.so.5 #7 0x7f6bdc178744 in start_thread () at /lib64/libpthread.so.0 #8 0x7f6bde548d3d in clone () at /lib64/libc.so.6 Thread 11 (Thread 0x7f6b967fc700 (LWP 14706)): [KCrash Handler] #6 0x7f6bde4938d7 in raise () at /lib64/libc.so.6 #7 0x7f6bde494caa in abort () at /lib64/libc.so.6 #8 0x7f6bde4d11b4 in () at /lib64/libc.so.6 #9 0x7f6bde4d69d6 in malloc_printerr () at /lib64/libc.so.6 #10 0x7f6bde4d7723 in _int_free () at /lib64/libc.so.6 #11 0x7f6ba6255c6c in __gnu_cxx::hashtable, unsigned long, __gnu_cxx::hash, std::_Select1st >, std::equal_to, std::allocator >::erase(unsigned long const&) () at /usr/lib64/libqalculate.so.5 #12 0x7f6ba621430a in Calculator::getId(unsigned long) () at /usr/lib64/libqalculate.so.5 #13 0x7f6ba621481f in Calculator::parseNumber(MathStructure*, std::string, ParseOptions const&) () at /usr/lib64/libqalculate.so.5 #14 0x7f6ba6217fc2 in Calculator::parseOperators(MathStructure*, std::string, ParseOptions const&) () at /usr/lib64/libqalculate.so.5 #15 0x7f6ba62153d6 in Calculator::parseOperators(MathStructure*, std::string, ParseOptions const&) () at /usr/lib64/libqalculate.so.5 #16 0x7f6ba621a14f in Calculator::parse(MathStructure*, std::string, ParseOptions const&) () at /usr/lib64/libqalculate.so.5 #17 0x7f6ba6252f89 in Calculator::calculate(std::string, EvaluationOptions const&, MathStructure*, MathStructure*, bool) () at /usr/lib64/libqalculate.so.5 #18 0x7f6ba6593f76 in () at /usr/lib64/qt5/plugins/krunner_calculatorrunner.so #19 0x7f6ba6595536 in () at /usr/lib64/qt5/plugins/krunner_calculatorrunner.so #20 0x7f6ba6595b6d in () at /usr/lib64/qt5/plugins/krunner_calculatorrunner.so #21 0x7f6bc12ce1f6 in Plasma::AbstractRunner::performMatch(Plasma::RunnerContext&) () at /usr/lib64/libKF5Runner.so.5 #22 0x7f6bc10af587 in ThreadWeaver::Executor::run(QSharedPointer const&, ThreadWeaver::Thread*) () at /usr/lib64/libKF5ThreadWeaver.so.5 #23 0x7f6bc10ae3d0 in ThreadWeaver::Job::execute(QSharedPointer const&, ThreadWeaver::Thread*) () at /usr/lib64/libKF5ThreadWeaver.so.5 #24 0x7f6bc10adaf7 in ThreadWeaver::Thread::run() () at /usr/lib64/libKF5ThreadWeaver.so.5 #25 0x7f6bdec3a9e9 in () at /usr/lib64/libQt5Core.so.5 #26 0x7f6bdc178744 in start_thread () at /lib64/libpthread.so.0 #27 0x7f6bde548d3d in clone () at /lib64/libc.so.6 Thread 10 (Thread 0x7f6b96ffd700 (LWP 14705)): #0 0x7f6bdc17d0bf in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f6bdec3b65b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/libQt5Core.so.5 #2 0x7f6bc10ac42f in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #3 0x7f6bc10afdea in () at /usr/lib64/libKF5ThreadWeaver.so.5 #4 0x7f6bc10aa45b in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #5 0x7f6bc10afe32 in () at /usr/lib64/libKF5ThreadWeaver.so.5 #6 0x7f6bc10aa45b in ThreadWeaver::Weaver::applyForWork(ThreadWeaver
[kdenlive] [Bug 357991] Unable to rotate video negative amount when not using standard locale for numbers
https://bugs.kde.org/show_bug.cgi?id=357991 Rune changed: What|Removed |Added Status|RESOLVED|UNCONFIRMED Resolution|WAITINGFORINFO |--- --- Comment #3 from Rune --- I've now tested with version 16.08.00 and Kubuntu 16.04: Still doesn't work. I use "Rotate [Keyframeable]" and enter -900 for rotate X: It does not rotate. I enter 900 and it rotates as expected. My locale is set to nb_NO.UTF8 -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 362284] discover search doesn't work
https://bugs.kde.org/show_bug.cgi?id=362284 Rune changed: What|Removed |Added CC||p...@runechristensen.com --- Comment #2 from Rune --- I have the same problem, and can confirm that appstreamcli search chromium returns 2 entries: Chromium Browser and Chromium B.S.U. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 357991] New: Unable to rotate video negative amount when not using standard locale for numbers
https://bugs.kde.org/show_bug.cgi?id=357991 Bug ID: 357991 Summary: Unable to rotate video negative amount when not using standard locale for numbers Product: kdenlive Version: unspecified Platform: Kubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: User Interface Assignee: j...@kdenlive.org Reporter: p...@runechristensen.com I had the Norsk Bokmål, nb_no, locale for regional settings. When entering negative amount for rotation video did not rotate when I entered, e.g. -900. When changing regional settings for numbers to C, standard, the video rotated anti-clockwise 90 degrees when entering -900; as expected Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
