[KScreen] [Bug 471195] [libkscreen] primary display is always on for all displays
https://bugs.kde.org/show_bug.cgi?id=471195 --- Comment #2 from Loader009 --- @ratijas - could you please have a look? thx -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 471195] [libkscreen] primary display is always on for all displays
https://bugs.kde.org/show_bug.cgi?id=471195 Loader009 changed: What|Removed |Added CC||m...@ratijas.tk -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 471195] [libkscreen] primary display is always on for all displays
https://bugs.kde.org/show_bug.cgi?id=471195 Loader009 changed: What|Removed |Added CC||wish42offcl98+bugs.kde.org@ ||posteo.org -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|crash |wishlist -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|wishlist|crash -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 449105] Dragging a window that was opened maximized moves the mouse cursor to the top left corner of the window
https://bugs.kde.org/show_bug.cgi?id=449105 koce...@tutanota.com changed: What|Removed |Added CC||koce...@tutanota.com -- You are receiving this mail because: You are watching all bug changes.
[kphotoalbum] [Bug 471814] New: 5.10.0 fails to build with exiv 0.28.0
https://bugs.kde.org/show_bug.cgi?id=471814 Bug ID: 471814 Summary: 5.10.0 fails to build with exiv 0.28.0 Classification: Applications Product: kphotoalbum Version: 5.10.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kpab...@willden.org Reporter: justin.zo...@gmail.com Target Milestone: --- SUMMARY Fails to build with exit 0.28.0 - see https://github.com/flathub/org.kde.kphotoalbum/pull/61 for automated test builds -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|crash |wishlist -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|wishlist|crash -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 471813] New: In brush mode, quickly pressing CTRL+Z after pressing V to draw a straight line crashes the program if the straight line is not done drawing.
https://bugs.kde.org/show_bug.cgi?id=471813 Bug ID: 471813 Summary: In brush mode, quickly pressing CTRL+Z after pressing V to draw a straight line crashes the program if the straight line is not done drawing. Classification: Applications Product: krita Version: 5.1.5 Platform: Archlinux OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: * Unknown Assignee: krita-bugs-n...@kde.org Reporter: tin1771718...@gmail.com Target Milestone: --- STEPS TO REPRODUCE 1. Open a blank canvas of any size and enter brush mode (any brush should do, I tried with Basic-5 Size) 2. Hold V and draw a straight line 3. After releasing the cursor and before the straight line is (fully) drawn, press CTRL+Z OBSERVED RESULT Crashed :) EXPECTED RESULT The drawn straight line is undone SOFTWARE/OS VERSIONS Linux Kernel Version: 6.3.9-arch1-1 (64-bit) KDE Plasma Version: 5.27.6 KDE Frameworks Version: 5.107.0 Qt Version: 5.15.10 ADDITIONAL INFORMATION Bug report: 01 Jul 2023 10:27:51 +0800. Executing krita Krita Version: 5.1.5, Qt version compiled: 5.15.7, loaded: 5.15.7. Process ID: 2 -- -- -- -- -- -- -- -- 01 Jul 2023 10:27:51 +0800: Style: fusion. Available styles: Windows, Fusion 01 Jul 2023 10:27:52 +0800: Database is up to date. Version: 0.0.17, created by Krita 5.1.5, at Fri June 16 12:47:19 2023 01 Jul 2023 10:27:58 +0800: Importing application/x-krita to application/x-krita. Location: /home/tin/Pictures/Art/clip files/Rain World.kra. Real location: /home/tin/Pictures/Art/clip files/Rain World.kra. Batchmode: 0 01 Jul 2023 10:27:58 +0800: Loaded image from application/x-krita. Size: 3840 * 2160 pixels, 8.3 dpi. Color model: 8-bit integer/channel RGB/Alpha (sRGB-elle-V2-srgbtrc.icc). Layers: 15 01 Jul 2023 10:28:27 +0800: ASSERT (krita): "!qimage.isNull()" in file /run/build/krita/libs/ui/kis_clipboard.cc, line 460 KRITA DID NOT CLOSE CORRECTLY coredumpctl info: PID: 5906 (krita) UID: 1000 (tin) GID: 1000 (tin) Signal: 6 (ABRT) Timestamp: Sat 2023-07-01 10:28:27 AWST (1h 20min ago) Command Line: krita Executable: /app/bin/krita Control Group: /user.slice/user-1000.slice/user@1000.service/app.slice/app-flatpak-org.kde.krita-5894.scope Unit: user@1000.service User Unit: app-flatpak-org.kde.krita-5894.scope Slice: user-1000.slice Owner UID: 1000 (tin) Boot ID: 9806a1fff4044f8684e988d484e69f24 Machine ID: 7394f17c4e62499a877399df094ea5c2 Hostname: Arch Storage: /var/lib/systemd/coredump/core.krita.1000.9806a1fff4044f8684e988d484e69f24.5906.168817850700.zst (present) Size on Disk: 130.3M Message: Process 5906 (krita) of user 1000 dumped core. Stack trace of thread 2: #0 0x7f5c03891184 n/a (/usr/lib/x86_64-linux-gnu/libc.so.6 + 0x91184) #1 0x7f5c0383f00e n/a (/usr/lib/x86_64-linux-gnu/libc.so.6 + 0x3f00e) #2 0x7f5c038287fc n/a (/usr/lib/x86_64-linux-gnu/libc.so.6 + 0x287fc) #3 0x7f5c0409dcaf n/a (/app/lib/libQt5Core.so.5.15.7 + 0x9dcaf) #4 0x7f5c06020158 n/a (/app/lib/libkritaui.so.18.0.0 + 0x420158) #5 0x7f5c06020681 n/a (/app/lib/libkritaui.so.18.0.0 + 0x420681) #6 0x7f5c06020c40 n/a (/app/lib/libkritaui.so.18.0.0 + 0x420c40) #7 0x7f5c062b4230 n/a (/app/lib/libkritaui.so.18.0.0 + 0x6b4230) #8 0x7f5c060cf1c2 n/a (/app/lib/libkritaui.so.18.0.0 + 0x4cf1c2) #9 0x7f5c0430568c n/a (/app/lib/libQt5Core.so.5.15.7 + 0x30568c) #10 0x7f5c04f75802 n/a (/app/lib/libQt5Widgets.so.5.15.7 + 0x175802) ELF object binary architecture: AMD x86-64 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 451702] Various KDE apps lock up with 100% CPU usage when monitor powers off
https://bugs.kde.org/show_bug.cgi?id=451702 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #4 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now 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 Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 467632] Window appears blank until resize or restart plasmashell
https://bugs.kde.org/show_bug.cgi?id=467632 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #7 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now 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 Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 466764] 16:10 resolution broken on Wayland with Nvidia
https://bugs.kde.org/show_bug.cgi?id=466764 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #6 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now 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 Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 448310] Cursor sometimes slow after shutting lid
https://bugs.kde.org/show_bug.cgi?id=448310 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #8 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now 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 Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 354741] Cancelling quick tile causes window to flicker
https://bugs.kde.org/show_bug.cgi?id=354741 --- Comment #15 from Bug Janitor Service --- 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 mark the bug 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! -- You are receiving this mail because: You are watching all bug changes.
[okteta] [Bug 471079] okteta show empty HEX-dump area
https://bugs.kde.org/show_bug.cgi?id=471079 --- Comment #6 from Bug Janitor Service --- 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 mark the bug 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! -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|crash |wishlist -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|wishlist|crash -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 471812] New: Orientation label moves after selecting a different monitor
https://bugs.kde.org/show_bug.cgi?id=471812 Bug ID: 471812 Summary: Orientation label moves after selecting a different monitor Classification: I don't know Product: kde Version: unspecified Platform: Other OS: Linux Status: REPORTED Keywords: qt6 Severity: minor Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: justin.zo...@gmail.com Target Milestone: --- Wasn't sure where to submit this so threw it under KDE. Need multiple monitors to test as it only appears to happen when you select a different monitor than the default one. STEPS TO REPRODUCE 1. Right-click on the desktop and select Configure Display Settings 2. Note the Orientation label's position 3. Select another display in the top section OBSERVED RESULT Orientation label moves EXPECTED RESULT The orientation label does not move Qt6 git master -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 469378] [Feature Request] Add option to temporarily pin selected region as a floating image
https://bugs.kde.org/show_bug.cgi?id=469378 Malachi Wu changed: What|Removed |Added CC||w5...@outlook.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 471811] New: Laptop screen auto-dimming
https://bugs.kde.org/show_bug.cgi?id=471811 Bug ID: 471811 Summary: Laptop screen auto-dimming Classification: Plasma Product: kwin Version: unspecified Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: milton...@gmail.com Target Milestone: --- Flags: Wayland- SUMMARY *** Screen is dimming itself without any user interactions, even when the laptop is plugged in to power. It acts as if power has been removed and it is running on the battery. The power removed notification sounds, though the power is still plugged in, and the screen dims by on its own. This has been observed when an external monitor is being used on the laptop's HDMI port. *** STEPS TO REPRODUCE 1. Plug in power the laptop from the power adapter 2. Attach an external monitor to the HDMI port 3. Wait for it to happen. OBSERVED RESULT Laptop screen auto-dims The screen brightness can be returned to its previous setting manually Occurs randomly, sometimes in 10 min intervals, other times at longer intervals EXPECTED RESULT The screen brightness not change and maintain its setting SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.27.5 KDE Frameworks Version: 5.106.0 Qt Version: 5.15.9 ADDITIONAL INFORMATION X11 Kernel: 6.1.31-2-MANJARO AMD Ryzen 7 4800H AMD Radeon Graphics -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 471810] New: Waydroid decorations don't paint background properly
https://bugs.kde.org/show_bug.cgi?id=471810 Bug ID: 471810 Summary: Waydroid decorations don't paint background properly Classification: Plasma Product: kwin Version: 5.27.6 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: decorations Assignee: kwin-bugs-n...@kde.org Reporter: vano...@gmail.com Target Milestone: --- Created attachment 160011 --> https://bugs.kde.org/attachment.cgi?id=160011=edit Image showing the issues described above SUMMARY When running waydroid in multi-window mode, the decorations don't paint properly under kwin. The action buttons (close, maximise, minimise) are drawn, but no background is drawn. Shadows suggest that the window is being drawn smaller than expected: the outer edge of the shadow around the titlebar matches the outer edge of the rest of the window's content. (See attached image!) STEPS TO REPRODUCE 1. Install waydroid, and enable multi-window mode ( waydroid prop set persist.waydroid.multi_windows true ) 2. Run an android app. If necessary, switch to multi-window mode by pressing the F11 key 3. Note the corruption in the header. OBSERVED RESULT Titlebar area has no background drawn. EXPECTED RESULT Background should be a solid colour, as it is under mutter. SOFTWARE/OS VERSIONS Operating System: Fedora Linux 38 KDE Plasma Version: 5.27.6 KDE Frameworks Version: 5.107.0 Qt Version: 5.15.10 Kernel Version: 6.3.8-200.fc38.x86_64 (64-bit) Graphics Platform: Wayland Processors: 4 × Intel® Core™ i5-7200U CPU @ 2.50GHz Memory: 11.5 GiB of RAM Graphics Processor: Mesa Intel® HD Graphics 620 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 471809] [Wayland] [NVIDIA] Compositing fails under vram exhaustion, nv_gbm_bo_create fails, Failed to allocate NVKMS memory for GEM object
https://bugs.kde.org/show_bug.cgi?id=471809 spr...@redhat.com changed: What|Removed |Added Summary|[Wayland] [NVIDIA] |[Wayland] [NVIDIA] |Compositing fails under |Compositing fails under |vram exhaustion |vram exhaustion, ||nv_gbm_bo_create fails, ||Failed to allocate NVKMS ||memory for GEM object -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 471809] New: [Wayland] [NVIDIA] Compositing fails under vram exhaustion
https://bugs.kde.org/show_bug.cgi?id=471809 Bug ID: 471809 Summary: [Wayland] [NVIDIA] Compositing fails under vram exhaustion Classification: Plasma Product: kwin Version: 5.27.6 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: spr...@redhat.com Target Milestone: --- SUMMARY Under vram exhaustion scenarios, windows, menus, etc, will all fail to render. Windows show only titlebar and become completely transparent. The following errors in the log: Jun 30 21:37:51 graviton.localdomain kwin_wayland_wrapper[50295]: src/nv_gbm.c:99: GBM-DRV error (nv_gbm_bo_create): DRM_IOCTL_NVIDIA_GEM_ALLOC_NVKMS_MEMORY failed (ret=-1) Jun 30 21:37:51 graviton.localdomain kernel: [drm:nv_drm_gem_alloc_nvkms_memory_ioctl [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x0100] Failed to allocate NVKMS memory for GEM object Jun 30 21:37:51 graviton.localdomain kwin_wayland_wrapper[50295]: Error getting buffer STEPS TO REPRODUCE 1. Run KDE Wayland with Nvidia driver 2. Open applications/games/etc to exhaust vram 3. Attempt to manipulate other windows, minimize/maximize, attempt to open the start menu, etc, they won't render on the screen OBSERVED RESULT Windows render only titlebar, no content. Start menu on the desktop gains the blue tick like it's opened, but not visible EXPECTED RESULT Windows/menus/etc work and are visible SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora 38 KDE Plasma Wayland KDE Plasma Version: plasma-workspace-wayland-5.27.6-1.fc38.x86_64 KDE Frameworks Version: kde-runtime-17.08.3-26.fc38.x86_64 Qt Version: qt5-qtwayland-5.15.10-1.fc38.x86_64 ADDITIONAL INFORMATION Even after vram is freed up, the windows need to be minimized/maximized again for them to be visible. Not sure if other stuff is broken elsewhere in the stack by this behavior. The windows still accept input, despite the broken compositing. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|crash |wishlist -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|wishlist|crash -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 471801] Upgrading 5.27.5 -> 5.27.6 broke dvorak layout and advanced keyboard behavior
https://bugs.kde.org/show_bug.cgi?id=471801 Fushan Wen changed: What|Removed |Added CC||qydwhotm...@gmail.com --- Comment #1 from Fushan Wen --- Have you tried downgrading Plasma to see if the problem is caused by 5.27.6? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 470540] Screen order is messed up after connecting an external display
https://bugs.kde.org/show_bug.cgi?id=470540 --- Comment #11 from leonardopsan...@gmail.com --- I tried to reproduce the error after the last reboot, but I couldn't. I tried: 1. Unplugging both cables: A. Unplugging the HDMI and and then the USC-C cable B. Plugging the HDMI cable back on and and then the USC-C cable All panels were correctly restored. 2. Unplugging both cables quick to maybe force a race condition: A. Unplugging the HDMI and and then the USC-C cable B. Plugging the HDMI cable back on and and then the USC-C cable I did both steps again, but tried to re-plug the cables as fast I could, so the USB cable was re-connected before KDE had a change to reconfigure itself after I re-plugged the HDMI cable (maybe it's a race condition), all panels were correctly restored. 3. Unplugging both cables (USB first): A. Unplugging the USC-C and then the HDMI cable B. Plugging the USC-C cable back on and and then the HDMI cable All panels were correctly restored. 4. With hibernate A. Unplugged both cables B. Closed the laptop lid (so it hibernates), C. Reconnected the cables D. Opened the lid and logged back in All panels were correctly restored. My feeling is that I can only reproduce this problem after the laptop has been on for a long time, like from Monday to Friday. I'll try again next Friday. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 470540] Screen order is messed up after connecting an external display
https://bugs.kde.org/show_bug.cgi?id=470540 --- Comment #10 from leonardopsan...@gmail.com --- Created attachment 160010 --> https://bugs.kde.org/attachment.cgi?id=160010=edit KDE config files diff -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 470540] Screen order is messed up after connecting an external display
https://bugs.kde.org/show_bug.cgi?id=470540 --- Comment #9 from leonardopsan...@gmail.com --- Rebooted the machine. Laptop screen still has the wrong panel. Restored backup files with systemctl --user stop plasma-plasmashell cp -avf $HOME/backup/org.kde.plasma.desktop-appletsrc $HOME/.config/ cp -avf $HOME/backup/plasmashellrc $HOME/.config/ sleep 5 systemctl --user start plasma-plasmashell Didn't make a difference, panels still on the wrong monitor. Moved panels using the "Panels and Desktop Management". The diff from my backup files is attached as 20230630-kde-diff.txt -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 459485] Recently used files cannot be chosen in file pickers
https://bugs.kde.org/show_bug.cgi?id=459485 Nate Graham changed: What|Removed |Added Version Fixed In||6.0 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 470540] Screen order is messed up after connecting an external display
https://bugs.kde.org/show_bug.cgi?id=470540 --- Comment #8 from leonardopsan...@gmail.com --- I had saved my monitor configuration with autorandr, so I used that to force-load the appropriate config, and then I restored plasma-org.kde.plasma.desktop-appletsrc and plasmashellrc: systemctl --user stop plasma-plasmashell cp -avf $HOME/backup/org.kde.plasma.desktop-appletsrc $HOME/.config/ cp -avf $HOME/backup/plasmashellrc $HOME/.config/ sleep 5 systemctl --user start plasma-plasmashell But now my panels are _on the wrong monitors_! When I saved org.kde.plasma.desktop-appletsrc and plasmashellrc, I had: 1. The laptop monitor with the original Kubuntu panel 2. The USB-C monitor with a new Kubuntu default panel (Application Launcher, Taskbar, System Tray), 3. The HDMI monitor with a panel containing just a Taskbar widget. After running the commands above, I got 1. The laptop monitor with panel containing just a Taskbar widget. 2. The USB-C monitor with a new Kubuntu default panel (Application Launcher, Taskbar, System Tray), 3. The HDMI monitor with a new Kubuntu default panel (Application Launcher, Taskbar, System Tray), Clearly unplugging and plugging the external monitors is a painful process, and even after "restoring" my configuration, the panels end up in the wrong screen. > 1. Can you describe how the output of `xrandr` changes, if at all, when you > reproduce the bug? xrand output attached as 20230630-xrandr.txt > 2. Can you describe how the output of `kscreen-doctor -o` changes, if at all, > when you reproduce the bug? > 3. Does the bug happen on Wayland too? Or is it 11-only? I'm not sure, can you please tell me how do I figure this out? I'm using Kubuntu 23.04's default server. > 4. Did you upgrade from an earlier Plasma version? If you did, can you move > aside (not delete) your ~/.local/share/kscreen folder, re-create the display arrangement in System Settings > Display and Monitor, reboot, and see if it's better now? It's a fresh Kubuntu 23.04 install. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|crash |wishlist -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|wishlist|crash -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 413709] krunner searches for the text suggested by auto-completion before actually accepting the suggestion
https://bugs.kde.org/show_bug.cgi?id=413709 Nate Graham changed: What|Removed |Added CC||n...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 471225] Open new tab to the right (or left) of currently active tab
https://bugs.kde.org/show_bug.cgi?id=471225 Nate Graham changed: What|Removed |Added Version Fixed In||23.08 CC||n...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 469625] Auto-hiding panels show a glitchy 1px gray line when sliding in/out
https://bugs.kde.org/show_bug.cgi?id=469625 Nate Graham changed: What|Removed |Added Version Fixed In||5.27.7 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 470540] Screen order is messed up after connecting an external display
https://bugs.kde.org/show_bug.cgi?id=470540 --- Comment #7 from leonardopsan...@gmail.com --- I finally had some time to try and reproduce this bug. I unplugged both external monitors, and plugged them back on. Plasmashell immediately crashed (_usr_bin_plasmashell.1000.crash.tar.bz2). Of the three available monitors, only the USC-C one is working, the laptop screen is completely black, as is the HDMI-connected monitor. After disconnecting the monitors but before reconnecting them, I ran sudo dmesg -c To clear the kernel event log. After plugging monitors the back on, I have [336221.542969] EDID block 0 (tag 0x00) checksum is invalid, remainder is 236 [336222.540425] i915 :00:02.0: [drm] *ERROR* Unexpected DP dual mode adaptor ID 41 [336222.950803] EDID block 0 (tag 0x00) checksum is invalid, remainder is 31 [336223.691976] i915 :00:02.0: [drm] *ERROR* Unexpected DP dual mode adaptor ID 50 [336233.788581] usb 1-5: USB disconnect, device number 23 [336233.788588] usb 1-5.1: USB disconnect, device number 24 [336236.522956] xhci_hcd :2d:00.0: xHC error in resume, USBSTS 0x401, Reinit [336236.522971] usb usb3: root hub lost power or was reset [336236.522977] usb usb4: root hub lost power or was reset [336247.237949] usb 1-5: new high-speed USB device number 25 using xhci_hcd [336247.388505] usb 1-5: New USB device found, idVendor=03f0, idProduct=0169, bcdDevice=55.60 [336247.388511] usb 1-5: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [336247.388512] usb 1-5: Product: USB2.1 Hub [336247.388513] usb 1-5: Manufacturer: GenesysLogic [336247.390784] hub 1-5:1.0: USB hub found [336247.391021] hub 1-5:1.0: 2 ports detected [336247.705940] usb 1-5.1: new high-speed USB device number 26 using xhci_hcd [336247.836320] usb 1-5.1: New USB device found, idVendor=03f0, idProduct=0169, bcdDevice=55.71 [336247.836326] usb 1-5.1: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [336247.836328] usb 1-5.1: Product: USB2.1 Hub [336247.836329] usb 1-5.1: Manufacturer: GenesysLogic [336247.837108] hub 1-5.1:1.0: USB hub found [336247.837380] hub 1-5.1:1.0: 4 ports detected The xrand output is Screen 0: minimum 320 x 200, current 3840 x 2160, maximum 16384 x 16384 eDP-1 connected (normal left inverted right x axis y axis) 2560x1440 60.01 + 60.01 1920x1440 60.01 1856x1392 60.01 1792x1344 60.01 2048x1152 60.01 1920x1200 60.01 1920x1080 60.01 1600x1200 60.01 1680x1050 60.01 1400x1050 60.01 1600x900 60.01 1280x1024 60.01 1400x900 60.01 1280x960 60.01 1440x810 60.01 1368x768 60.01 1280x800 60.01 1280x720 60.01 1024x768 60.01 960x720 60.01 928x696 60.01 896x672 60.01 1024x576 60.01 960x600 60.01 960x540 60.01 800x600 60.01 840x525 60.01 864x486 60.01 700x525 60.01 800x450 60.01 640x512 60.01 700x450 60.01 640x480 60.01 720x405 60.01 684x384 60.01 640x360 60.01 512x384 60.01 512x288 60.01 480x270 60.01 400x300 60.01 432x243 60.01 320x240 60.01 360x202 60.01 320x180 60.01 DP-1 disconnected (normal left inverted right x axis y axis) HDMI-1 connected (normal left inverted right x axis y axis) 3840x2160 30.0029.9729.98 1920x1200 59.95 1920x1080 60.0050.0059.94 1920x1080i60.0050.0059.94 1680x1050 59.88 1600x900 60.00 1280x1024 60.02 1440x900 59.90 1280x800 59.91 1280x720 60.0050.0059.94 1024x768 60.00 800x600 60.32 720x576 50.00 720x576i 50.00 720x480 60.0059.94 720x480i 60.0059.94 640x480 60.0059.94 720x400 70.08 DP-2 connected primary 3840x2160+0+0 (normal left inverted right x axis y axis) 597mm x 336mm 3840x2160 60.00*+ 29.98 1920x1200 59.88 1920x1080 60.0050.0059.94 1920x1080i60.0050.0059.94 1680x1050 59.95 1600x900 60.00 1280x1024 60.02 1440x900 59.89 1280x800 59.81 1280x720 60.0050.0059.94 1024x768 60.00 800x600 60.32 720x576 50.00 720x480 60.0059.94 640x480 60.0059.94 720x400 70.08 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 471808] New: Time Adjust based on filename sporadically incorrect
https://bugs.kde.org/show_bug.cgi?id=471808 Bug ID: 471808 Summary: Time Adjust based on filename sporadically incorrect Classification: Applications Product: digikam Version: 8.0.0 Platform: Appimage OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Plugin-Generic-TimeAdjust Assignee: digikam-bugs-n...@kde.org Reporter: adrian.br...@gmail.com Target Milestone: --- SUMMARY When modifying date/time metadata based on filename with the format described below, some of the files are correctly translated while other are incorrectly translated or deemed impossible to interpret. STEPS TO REPRODUCE 1. Run Digikam AppImage 2. Open Adjust Time & Date dialog 3. Select relevant files and tick File name timestamp OBSERVED RESULT Correctly adjusted: 2022-12-14_270__71a25cea-c940-4cba-ad7f-719a748d97e8.jpeg => 2022:12:14 00:00:00 2022-12-13_270__d8d2d326-0831-42c6-807a-f7ca326552fd.jpeg => 2022-12-13 00:00:00 Incorrectly adjusted: 2023-01-06_0__958ef4b3-d919-4a34-83dc-e8b4f5400053.jpeg => 2006:01:23 00:53:00 2022-11-02_270__3fcf88c8-a6d6-4e66-ae2f-0a0541a42226.jpeg => 2002:11:22 22:26:00 2022-11-10_270__71529f11-8064-43ec-b450-a0337a29a6c0.jpeg => 2010:11:22 03:37:00 2022-12-14_270__43e786ff-6d84-45b2-86a8-ccbf19041178.jpeg => 1178:04:19 00:00:00 Not able to be interpreted for adjustment: 2023-01-25_270__797e0df3-58d9-4382-9349-1ef1d3729c59.jpeg => nil 2023-01-24_0__791e8006-3631-42d5-9454-b7b069ebb78a.jpeg => nil EXPECTED RESULT 2023-01-06_0__958ef4b3-d919-4a34-83dc-e8b4f5400053.jpeg => 2023:01:06 00:00:00 2022-11-02_270__3fcf88c8-a6d6-4e66-ae2f-0a0541a42226.jpeg => 2022:11:02 00:00:00 2022-11-10_270__71529f11-8064-43ec-b450-a0337a29a6c0.jpeg => 2022:11:10 00:00:00 2022-12-14_270__43e786ff-6d84-45b2-86a8-ccbf19041178.jpeg => 2022:12:13 00:00:00 2023-01-25_270__797e0df3-58d9-4382-9349-1ef1d3729c59.jpeg => 2023-01-25 00:00:00 2023-01-24_0__791e8006-3631-42d5-9454-b7b069ebb78a.jpeg => 2023-01-24 00:00:00 SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora 37 using AppImage of digikam 8.0.0 KDE Plasma Version: KDE Frameworks Version: 5.104.0 Qt Version: 5.15.7 ADDITIONAL INFORMATION The format is most likely -MM-DD_ROTATION__UID.jpeg -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|crash |wishlist -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|wishlist|crash -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 471807] New: Add support for lazy reading and downloading of DWARF debuginfo
https://bugs.kde.org/show_bug.cgi?id=471807 Bug ID: 471807 Summary: Add support for lazy reading and downloading of DWARF debuginfo Classification: Developer tools Product: valgrind Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: jsew...@acm.org Reporter: ame...@redhat.com Target Milestone: --- Created attachment 160009 --> https://bugs.kde.org/attachment.cgi?id=160009=edit patch Currently valgrind attempts to read DWARF .debug_* sections as well as separate debuginfo files for ELF shared library binaries as soon as each shared library is loaded. This might also result in the downloading of separate debuginfo files via debuginfod. This is inefficient when some of this debuginfo never ends up being used by valgrind. I've attached a patch that adds support for lazy reading and downloading of DWARF debuginfo to help address this inefficiency. Currently only AMD64 Linux is supported. For the handful of client processes I've tested this with, I've seen ~25% reduction in the total amount of debuginfo data valgrind downloads. When all debuginfo for these processes is pre-downloaded, I've seen a ~10% average reduction in the time it takes for these processes to run and exit under valgrind. When valgrind must download all debuginfo, I've seen a ~20% average reduction in the time it takes for the processes to run and exit under valgrind. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 471183] Face recognition, see and edit references
https://bugs.kde.org/show_bug.cgi?id=471183 --- Comment #19 from Craig --- (In reply to Andy from comment #17) > Hi Mike! > I'll stop with face recognition for now. It frustrates me a little bit > because I keep having to reject the same images over and over again. And > because 90% of the images are assigned to the wrong people. Apparently, face > recognition doesn't learn from newly assigned faces. Even very clearly > recognizable faces remain in unknown or are not framed. > As a suggestion for the developers, it might help that only the last 50 > added faces per person are used for face recognition??? The recognition > grows with the years of life and the appearance of a person. It's just a > layman's idea :-) > > @Craig > The post in your link seems to be a different problem. > > > I'm really looking forward to the next program version. I think the better option would be to be able to select which faces are to be used as a reference for the learning. I am not sure how many pictures you have for each person, but I would imagine if you have 300 pictures that adding an additional 50 more isn't going to change the identification pattern. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|crash |wishlist -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|wishlist|crash -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 471806] New: Dolphin crash while using encrypted root partition
https://bugs.kde.org/show_bug.cgi?id=471806 Bug ID: 471806 Summary: Dolphin crash while using encrypted root partition Classification: Applications Product: dolphin Version: 23.04.2 Platform: Neon OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: dje...@gmail.com CC: kfm-de...@kde.org Target Milestone: --- Application: dolphin (23.04.2) Qt Version: 5.15.10 Frameworks Version: 5.107.0 Operating System: Linux 5.19.0-46-generic x86_64 Windowing System: X11 Distribution: KDE neon 5.27 DrKonqi: 5.27.6 [KCrashBackend] -- Information about the crash: Attempted to open Dolphin on an enrypted root partition immediately after a fresh installation. The crash can be reproduced every time. -- Backtrace: Application: Dolphin (dolphin), signal: Segmentation fault [KCrash Handler] #4 0x7f4761326e44 in Solid::StorageAccess::isEncrypted() const () from /lib/x86_64-linux-gnu/libKF5Solid.so.5 #5 0x7f476172f51b in ?? () from /lib/x86_64-linux-gnu/libKF5KIOWidgets.so.5 #6 0x7f476172f646 in ?? () from /lib/x86_64-linux-gnu/libKF5KIOWidgets.so.5 #7 0x7f47617344d5 in KIO::PreviewJob::slotResult(KJob*) () from /lib/x86_64-linux-gnu/libKF5KIOWidgets.so.5 #8 0x7f475f6f4854 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x7f4760c80130 in KJob::result(KJob*, KJob::QPrivateSignal) () from /lib/x86_64-linux-gnu/libKF5CoreAddons.so.5 #10 0x7f4760c85e3b in ?? () from /lib/x86_64-linux-gnu/libKF5CoreAddons.so.5 #11 0x7f475f6f4854 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #12 0x7f4761494e1a in KIO::SlaveInterface::error(int, QString const&) () from /lib/x86_64-linux-gnu/libKF5KIOCore.so.5 #13 0x7f4761497007 in KIO::SlaveInterface::dispatch(int, QByteArray const&) () from /lib/x86_64-linux-gnu/libKF5KIOCore.so.5 #14 0x7f476149557d in KIO::SlaveInterface::dispatch() () from /lib/x86_64-linux-gnu/libKF5KIOCore.so.5 #15 0x7f47614999b2 in KIO::Slave::gotInput() () from /lib/x86_64-linux-gnu/libKF5KIOCore.so.5 #16 0x7f475f6f4854 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #17 0x7f475f6ea2fe in QObject::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #18 0x7f476036c763 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #19 0x7f475f6bcdda in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #20 0x7f475f6bfec7 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #21 0x7f475f716c07 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #22 0x7f475d520d3b in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #23 0x7f475d576258 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #24 0x7f475d51e3e3 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #25 0x7f475f716258 in QEventDispatcherGlib::processEvents(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #26 0x7f475f6bb6fb in QEventLoop::exec(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #27 0x7f475f6c3c94 in QCoreApplication::exec() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #28 0x558601333b35 in ?? () #29 0x7f475ec29d90 in __libc_start_call_main (main=main@entry=0x55860132dc80, argc=argc@entry=1, argv=argv@entry=0x7ffded6de8d8) at ../sysdeps/nptl/libc_start_call_main.h:58 #30 0x7f475ec29e40 in __libc_start_main_impl (main=0x55860132dc80, argc=1, argv=0x7ffded6de8d8, init=, fini=, rtld_fini=, stack_end=0x7ffded6de8c8) at ../csu/libc-start.c:392 #31 0x5586013343e5 in ?? () [Inferior 1 (process 1391) detached] The reporter indicates this bug may be a duplicate of or related to bug 471182. Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|crash |wishlist -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|wishlist|crash -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 426644] Screens go black / unresponsive after sleep or lock
https://bugs.kde.org/show_bug.cgi?id=426644 kot...@hotmail.com changed: What|Removed |Added CC||kot...@hotmail.com -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|crash |wishlist -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|wishlist|crash -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 471797] DigiKam crashes on startup at 74% on Finding New Files
https://bugs.kde.org/show_bug.cgi?id=471797 --- Comment #6 from philip_ram...@hotmail.com --- Have added screenshots from Control Panel and from sysinfo32 which appear to show that QT_LOGGING_RULES is set to digikam*=true. Am I doing something wrong? I'm still getting the same output from DebugView when I start DigiKam. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 471797] DigiKam crashes on startup at 74% on Finding New Files
https://bugs.kde.org/show_bug.cgi?id=471797 --- Comment #5 from philip_ram...@hotmail.com --- Created attachment 160008 --> https://bugs.kde.org/attachment.cgi?id=160008=edit msinfo32 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 471797] DigiKam crashes on startup at 74% on Finding New Files
https://bugs.kde.org/show_bug.cgi?id=471797 --- Comment #4 from philip_ram...@hotmail.com --- Created attachment 160007 --> https://bugs.kde.org/attachment.cgi?id=160007=edit Control Panel > System > Advanced -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 471434] Colorscheme previews do not show the right colors
https://bugs.kde.org/show_bug.cgi?id=471434 David Redondo changed: What|Removed |Added Resolution|--- |FIXED Latest Commit||https://invent.kde.org/plas ||ma/plasma-workspace/-/commi ||t/14bb6df73f094b4f45ce3e5f1 ||a03738e81471c5d Status|ASSIGNED|RESOLVED --- Comment #3 from David Redondo --- Git commit 14bb6df73f094b4f45ce3e5f1a03738e81471c5d by David Redondo. Committed on 30/06/2023 at 13:42. Pushed by davidre into branch 'master'. kcms/colors: Provide QPalette colors via an extension type In Qt5 passing a QPalette to QML was working automagically but this is no longer the case. Provide properties for all the colors via an extension type. M +35 -0kcms/colors/colors.cpp https://invent.kde.org/plasma/plasma-workspace/-/commit/14bb6df73f094b4f45ce3e5f1a03738e81471c5d -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 471642] Severe memory leak in 5.27.5 with Wayland
https://bugs.kde.org/show_bug.cgi?id=471642 lacresha nelson changed: What|Removed |Added CC||lacreshanelson1...@gmail.co ||m Attachment #159983|image/png |text/plain mime type|| Attachment #159983|0 |1 is obsolete|| Attachment #159983|0 |1 is patch|| -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 471797] DigiKam crashes on startup at 74% on Finding New Files
https://bugs.kde.org/show_bug.cgi?id=471797 --- Comment #3 from Maik Qualmann --- The log shows no debug messages, only minor warnings. The Qt debug variable is not set correctly in the Windows environment variable editor: This entries must be entered as user environment variables, without the quotation marks. name: "QT_LOGGING_RULES" value: "digikam*=true" Maik -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 348104] Remove all tags from selected image(s)
https://bugs.kde.org/show_bug.cgi?id=348104 Maik Qualmann changed: What|Removed |Added Version Fixed In||8.1.0 Status|REPORTED|RESOLVED Resolution|--- |FIXED Latest Commit||https://invent.kde.org/grap ||hics/digikam/-/commit/21314 ||c7e642ace1bf885570a4cf98de4 ||4e050081 --- Comment #5 from Maik Qualmann --- Git commit 21314c7e642ace1bf885570a4cf98de44e050081 by Maik Qualmann. Committed on 30/06/2023 at 20:55. Pushed by mqualmann into branch 'master'. add function to remove all tags from images (except face tags) FIXED-IN: 8.1.0 M +2-1NEWS M +10 -0core/app/items/utils/contextmenuhelper.h M +1-0core/app/items/utils/contextmenuhelper_p.h M +25 -0core/app/items/utils/contextmenuhelper_tags.cpp M +1-0core/app/views/preview/itempreviewview.cpp M +1-0core/app/views/stack/itemiconview_views.cpp M +6-0core/utilities/maintenance/metadataremovetask.cpp https://invent.kde.org/graphics/digikam/-/commit/21314c7e642ace1bf885570a4cf98de44e050081 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 468908] Dolphin cannot open folders with special characters (e.g. Arabic, space, #) if konsole shell is set to Nushell
https://bugs.kde.org/show_bug.cgi?id=468908 Munzir Taha changed: What|Removed |Added Summary|With nushell as a default |Dolphin cannot open folders |shell, folders with Arabic |with special characters |file names cannot be opened |(e.g. Arabic, space, #) if ||konsole shell is set to ||Nushell -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 471805] New: Closing Firefox ESR window preview crashes taskbar
https://bugs.kde.org/show_bug.cgi?id=471805 Bug ID: 471805 Summary: Closing Firefox ESR window preview crashes taskbar Classification: Plasma Product: plasmashell Version: 5.27.5 Platform: Debian stable OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: miracledin...@gmail.com CC: k...@davidedmundson.co.uk Target Milestone: 1.0 Application: plasmashell (5.27.5) Qt Version: 5.15.8 Frameworks Version: 5.103.0 Operating System: Linux 6.1.0-9-amd64 x86_64 Windowing System: X11 Distribution: Debian GNU/Linux 12 (bookworm) DrKonqi: 5.27.5 [CoredumpBackend] -- Information about the crash: Steps to reproduce Set Icons-Only Task Manager to show Window Previews when clicking a grouped task. Click pinned Firefox ESR on panel Open a Private window in Firefox Click the Firefox group on the panel, then press the red X button to close the original (non-private) window. The KDE Plasma Panel then crashes and opens the crash handler. The crash can be reproduced every time. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault PID: 3142 (plasmashell) UID: 1000 (miracledinner) GID: 1000 (miracledinner) Signal: 11 (SEGV) Timestamp: Fri 2023-06-30 21:29:26 BST (27s ago) Command Line: /usr/bin/plasmashell --no-respawn Executable: /usr/bin/plasmashell Control Group: /user.slice/user-1000.slice/user@1000.service/session.slice/plasma-plasmashell.service Unit: user@1000.service User Unit: plasma-plasmashell.service Slice: user-1000.slice Owner UID: 1000 (miracledinner) Boot ID: 66ebc8751a8b46228556e6258997e58e Machine ID: aa59d6daa7bf435499c8eb8a556b2dc4 Hostname: elimina-debian Storage: /var/lib/systemd/coredump/core.plasmashell.1000.66ebc8751a8b46228556e6258997e58e.3142.168815696600.zst (present) Size on Disk: 19.3M Message: Process 3142 (plasmashell) of user 1000 dumped core. Module libsystemd.so.0 from deb systemd-252.6-1.amd64 Module libudev.so.1 from deb systemd-252.6-1.amd64 Stack trace of thread 3142: #0 0x7f8594ea9ccc n/a (libc.so.6 + 0x8accc) #1 0x7f8594e5aef2 raise (libc.so.6 + 0x3bef2) #2 0x7f859756ab46 _ZN6KCrash19defaultCrashHandlerEi (libKF5Crash.so.5 + 0x5b46) #3 0x7f8594e5af90 n/a (libc.so.6 + 0x3bf90) #4 0x7f8594ea9ccc n/a (libc.so.6 + 0x8accc) #5 0x7f8594e5aef2 raise (libc.so.6 + 0x3bef2) #6 0x7f8594e5af90 n/a (libc.so.6 + 0x3bf90) #7 0x7f8594ea4d34 n/a (libc.so.6 + 0x85d34) #8 0x7f8594ea73f8 pthread_cond_wait (libc.so.6 + 0x883f8) #9 0x7f85950d1a2b _ZN14QWaitCondition4waitEP6QMutex14QDeadlineTimer (libQt5Core.so.5 + 0xd1a2b) #10 0x7f859700bd58 n/a (libQt5Quick.so.5 + 0x20bd58) #11 0x7f859700d013 n/a (libQt5Quick.so.5 + 0x20d013) #12 0x7f85957493f5 _ZN7QWindow5eventEP6QEvent (libQt5Gui.so.5 + 0x1493f5) #13 0x7f85840dd055 n/a (libcorebindingsplugin.so + 0x3f055) #14 0x7f8596162fae _ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent (libQt5Widgets.so.5 + 0x162fae) #15 0x7f85952b16f8 _ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent (libQt5Core.so.5 + 0x2b16f8) #16 0x7f859573e5cd _ZN22QGuiApplicationPrivate18processExposeEventEPN29QWindowSystemInterfacePrivate11ExposeEventE (libQt5Gui.so.5 + 0x13e5cd) #17 0x7f8595711cac _ZN22QWindowSystemInterface22sendWindowSystemEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Gui.so.5 + 0x111cac) #18 0x7f85905c6eca n/a (libQt5XcbQpa.so.5 + 0x6deca) #19 0x7f8593d8b7a9 g_main_context_dispatch (libglib-2.0.so.0 + 0x547a9) #20 0x7f8593d8ba38 n/a (libglib-2.0.so.0 + 0x54a38) #21 0x7f8593d8bacc g_main_context_iteration (libglib-2.0.so.0 + 0x54acc) #22 0x7f8595309836 _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5 + 0x309836) #23 0x7f85952b017b _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5 + 0x2b017b) #24 0x7f85952b82d6 _ZN16QCoreApplication4execEv (libQt5Core.so.5 + 0x2b82d6) #25 0x55c329c87dc3 n/a (plasmashell + 0x26dc3) #26 0x7f8594e4618a n/a (libc.so.6 + 0x2718a) #27 0x7f8594e46245 __libc_start_main (libc.so.6 + 0x27245) #28 0x55c329c87ee1 n/a (plasmashell + 0x26ee1)
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|crash |wishlist -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|wishlist|crash -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 471797] DigiKam crashes on startup at 74% on Finding New Files
https://bugs.kde.org/show_bug.cgi?id=471797 --- Comment #2 from philip_ram...@hotmail.com --- Created attachment 160006 --> https://bugs.kde.org/attachment.cgi?id=160006=edit DebugView Log -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 471804] New: Color scheme "tint all colors colors with accent color" way too prominent on Okular background
https://bugs.kde.org/show_bug.cgi?id=471804 Bug ID: 471804 Summary: Color scheme "tint all colors colors with accent color" way too prominent on Okular background Classification: Applications Product: okular Version: 23.04.2 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: okular-de...@kde.org Reporter: quintenk...@gmail.com Target Milestone: --- Created attachment 160005 --> https://bugs.kde.org/attachment.cgi?id=160005=edit Screenshot of the described issue (Okular is in the background on the right) SUMMARY The Okular background, which is normally grey, gets an overly saturated version of my accent color, which looks rather ugly. STEPS TO REPRODUCE 1. Go to System Settings -> Colors, and enable "Tint all colors with accent colors" for the active theme. 2. Open a document in Okular 3. Zoom out so that the margins/background are clearly visible OBSERVED RESULT Background is colored very intensely EXPECTED RESULT Background is colored much more subtly, similar to how other windows are tinted. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.27.6 KDE Frameworks Version: 5.107.0 Qt Version: 5.15.10 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|crash |wishlist -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|wishlist|crash -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 471803] New: Kirigami makes colored icons black shadows
https://bugs.kde.org/show_bug.cgi?id=471803 Bug ID: 471803 Summary: Kirigami makes colored icons black shadows Classification: Frameworks and Libraries Product: frameworks-kirigami Version: 5.107.0 Platform: Archlinux OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: kdelibs-b...@kde.org Reporter: lionsshark...@gmail.com CC: notm...@gmail.com Target Milestone: Not decided Created attachment 160004 --> https://bugs.kde.org/attachment.cgi?id=160004=edit Shadowy icons from Oxygen in Kasts and KClock SUMMARY *** When using an icon theme that has colored action icons (I use Oxygen icons), Kirigami apps make them look like black shadows instead of their proper, colored icons. *** STEPS TO REPRODUCE 1. Use icon theme with colored "Actions" icons 2. Run app that uses Kirigami 3. Actions icons are black shadowy versions of what they should look like. OBSERVED RESULT Kirigami apps render colored action icons (such as the ones from Oxygen) as black filled versions of what they should look like, resembling a shadow. I think it has to do with the fact that Breeze (the default icon theme) has simple, outline icons for actions. EXPECTED RESULT All actions icons should appear as their default colored selves. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Kernel - 6.3.9-arch1-1 (64-bit) (available in About System) KDE Plasma Version: 5.27.6 KDE Frameworks Version: 5.107.0 Qt Version: 5.15.10 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 471797] DigiKam crashes on startup at 74% on Finding New Files
https://bugs.kde.org/show_bug.cgi?id=471797 Maik Qualmann changed: What|Removed |Added CC||metzping...@gmail.com --- Comment #1 from Maik Qualmann --- Please create a DebugView log so we can identify the last file scanned to reproduce the issue. The creation of the DebugView log is described here, don't forget to set the Qt debug environment variable: https://www.digikam.org/contribute/ Maik -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 471798] Manufacturer's Notes' metadata disappears
https://bugs.kde.org/show_bug.cgi?id=471798 Maik Qualmann changed: What|Removed |Added CC||metzping...@gmail.com --- Comment #1 from Maik Qualmann --- Please try the upcoming AppImage of digiKam-8.1.0 if the problem can be reproduced. digiKam-8.1.0 download: https://files.kde.org/digikam/ >From which camera and model does the problem occur? Can you provide a sample image? Maik -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 466320] kpipewire_logging: Window not available PipeWireSourceItem_QML_1025
https://bugs.kde.org/show_bug.cgi?id=466320 kdebugmalias...@outlook.com changed: What|Removed |Added CC||kdebugmalias...@outlook.com --- Comment #4 from kdebugmalias...@outlook.com --- In my case, i had many kpipewire_logging: Window not available PipeWireSourceItem together with tons of "kwin_screencast: Dropping a screencast frame because the compositor is slow" messages. After i disabled kwin screencast plugin in my ~/.config/kwinrc with the following: [Plugins] kwin5_plugin_screencastEnabled=false , plasma session works flawlessly and messages don't appear again, but windows previews are not shown. -- You are receiving this mail because: You are watching all bug changes.
[lokalize] [Bug 471802] New: Crash after editing a plural
https://bugs.kde.org/show_bug.cgi?id=471802 Bug ID: 471802 Summary: Crash after editing a plural Classification: Applications Product: lokalize Version: 23.04.2 Platform: openSUSE OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: sdepi...@gmail.com Reporter: freekdekru...@kde.nl CC: aa...@kde.org, sha...@ukr.net Target Milestone: --- Application: lokalize (23.04.2) Qt Version: 5.15.10 Frameworks Version: 5.107.0 Operating System: Linux 6.3.9-1-default x86_64 Windowing System: X11 Distribution: "openSUSE Tumbleweed" DrKonqi: 5.27.6 [KCrashBackend] -- Information about the crash: I tried to edit the file nl/messages/kdebugsettings/kdebugsettings.po in which one element needed editing. This element has a plural. Apparently the element with the plural (rules) needed to add an s to make the Dutch word (regel) a plural, which is regels. The first time I simply entered the s and lokalize crashed, leaving the .po file unchanged. The second time, of which this the bug report, it crashed again by entering the s. However now this file has nothing to edit anymore. The crash can be reproduced every time. -- Backtrace: Application: Lokalize (lokalize), signal: Segmentation fault [KCrash Handler] #4 QMapNodeBase::color (this=0x0) at tools/qmap.h:93 #5 QMapDataBase::freeNodeAndRebalance (this=0x55a116cdea40, z=0x55a1191196c0) at tools/qmap.cpp:234 #6 0x7fcbc4742b9e in QMapData >::deleteNode (z=, this=) at /usr/include/qt5/QtCore/qmap.h:281 #7 0x7fcbc46faf1a in Breeze::BaseDataMap::unregisterWidget (this=0x55a115b55228, key=0x55a119110c50) at /usr/src/debug/breeze-5.27.6/build/kstyle/breeze_autogen/4NBMFDNHZT/../../../../kstyle/animations/breezedatamap.h:95 #8 0x7fcbc4702e21 in Breeze::WidgetStateEngine::unregisterWidget (object=0x55a119110c50, this=0x55a115b551b0) at /usr/src/debug/breeze-5.27.6/build/kstyle/breeze_autogen/4NBMFDNHZT/../../../../kstyle/animations/breezewidgetstateengine.h:144 #9 Breeze::WidgetStateEngine::unregisterWidget (object=0x55a119110c50, this=0x55a115b551b0) at /usr/src/debug/breeze-5.27.6/build/kstyle/breeze_autogen/4NBMFDNHZT/../../../../kstyle/animations/breezewidgetstateengine.h:132 #10 Breeze::WidgetStateEngine::qt_static_metacall (_o=0x55a115b551b0, _a=0x7fff55cc9ce0, _id=, _c=) at /usr/src/debug/breeze-5.27.6/build/kstyle/breeze_autogen/4NBMFDNHZT/moc_breezewidgetstateengine.cpp:74 #11 0x7fcbd4525743 in doActivate (sender=0x55a119110c50, signal_index=0, argv=0x7fff55cc9ce0) at kernel/qobject.cpp:3937 #12 0x7fcbd451e40f in QMetaObject::activate (sender=sender@entry=0x55a119110c50, m=m@entry=0x7fcbd47be840 , local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7fff55cc9ce0) at kernel/qobject.cpp:3985 #13 0x7fcbd451e4bf in QObject::destroyed (this=this@entry=0x55a119110c50, _t1=, _t1@entry=0x55a119110c50) at .moc/moc_qobject.cpp:219 #14 0x7fcbd53e297b in QWidget::~QWidget (this=this@entry=0x55a119110c50, __in_chrg=) at kernel/qwidget.cpp:1499 #15 0x7fcbd549553d in QAbstractScrollAreaScrollBarContainer::~QAbstractScrollAreaScrollBarContainer (this=0x55a119110c50, __in_chrg=) at widgets/qabstractscrollarea_p.h:128 #16 QAbstractScrollAreaScrollBarContainer::~QAbstractScrollAreaScrollBarContainer (this=0x55a119110c50, __in_chrg=) at widgets/qabstractscrollarea_p.h:128 #17 0x7fcbd4516e4e in QObjectPrivate::deleteChildren (this=this@entry=0x7fcb8c0bf0a0) at kernel/qobject.cpp:2137 #18 0x7fcbd53e26a6 in QWidget::~QWidget (this=0x55a11910f670, __in_chrg=) at kernel/qwidget.cpp:1524 #19 0x7fcbd5542de9 in QScrollArea::~QScrollArea (this=0x55a11910f670, __in_chrg=) at widgets/qscrollarea.cpp:173 #20 0x7fcbd4516e4e in QObjectPrivate::deleteChildren (this=this@entry=0x55a11910d920) at kernel/qobject.cpp:2137 #21 0x7fcbd53e26a6 in QWidget::~QWidget (this=this@entry=0x55a119109c70, __in_chrg=) at kernel/qwidget.cpp:1524 #22 0x7fcbd54c44ed in QDockWidget::~QDockWidget (this=this@entry=0x55a119109c70, __in_chrg=) at widgets/qdockwidget.cpp:1314 #23 0x55a11536f41c in GlossaryNS::GlossaryView::~GlossaryView (this=, this=) at /usr/src/debug/lokalize-23.04.2/src/glossary/glossaryview.cpp:71 #24 GlossaryNS::GlossaryView::~GlossaryView (this=, this=) at /usr/src/debug/lokalize-23.04.2/src/glossary/glossaryview.cpp:71 #25 0x7fcbd4516e4e in QObjectPrivate::deleteChildren (this=this@entry=0x55a11861c6a0) at kernel/qobject.cpp:2137 #26 0x7fcbd53e26a6 in QWidget::~QWidget (this=0x55a118127bc0, __in_chrg=) at kernel/qwidget.cpp:1524 #27 0x55a115347ec9 in EditorTab::~EditorTab (this=, this=) at /usr/src/debug/lokalize-23.04.2/src/editortab.cpp:139 #28 0x7fcbd4519077 in QObject::event (this=0x55a118127bc0, e=0x55a117cc5ef0) at kernel/qobject.cpp:1334 #29 0x7fcbd53a519e in QApplicationPrivate::notify_helper
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|crash |wishlist -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|wishlist|crash -- You are receiving this mail because: You are watching all bug changes.
[bugs.kde.org] [Bug 37913] test test test test
https://bugs.kde.org/show_bug.cgi?id=37913 刘津 changed: What|Removed |Added CC||saukaguya0...@outlook.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 470882] Plasma Shell crashes just switching between desktops
https://bugs.kde.org/show_bug.cgi?id=470882 --- Comment #1 from cont...@robotoskunk.com --- Created attachment 160003 --> https://bugs.kde.org/attachment.cgi?id=160003=edit New crash information added by DrKonqi plasmashell (5.27.5) using Qt 5.15.8 Plasma randomly crashes switching between virtual desktops and it closes every Brave process after that PS: I'm not mad with the Plasma crash, but with closing every single Brave process when Plasma crashes. -- Backtrace (Reduced): #4 0x7fcb35673324 in QtQml::qmlAttachedPropertiesObject(QObject*, QObject* (*)(QObject*), bool) () at /lib/x86_64-linux-gnu/libQt5Qml.so.5 [...] #10 0x7fcb336a1fd4 in start_thread (arg=) at ./nptl/pthread_create.c:442 #11 0x7fcb337225bc in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:81 #5 __pthread_kill_implementation (threadid=, signo=signo@entry=11, no_tid=no_tid@entry=0) at ./nptl/pthread_kill.c:44 #6 0x7fcb336a3d2f in __pthread_kill_internal (signo=11, threadid=) at ./nptl/pthread_kill.c:78 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 470882] Plasma Shell crashes just switching between desktops
https://bugs.kde.org/show_bug.cgi?id=470882 cont...@robotoskunk.com changed: What|Removed |Added CC||cont...@robotoskunk.com -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 471801] New: Upgrading 5.27.5 -> 5.27.6 broke dvorak layout and advanced keyboard behavior
https://bugs.kde.org/show_bug.cgi?id=471801 Bug ID: 471801 Summary: Upgrading 5.27.5 -> 5.27.6 broke dvorak layout and advanced keyboard behavior Classification: I don't know Product: kde Version: unspecified Platform: Archlinux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: adam.m.fontenot+...@gmail.com Target Milestone: --- Created attachment 160002 --> https://bugs.kde.org/attachment.cgi?id=160002=edit upgrade log from pacman SUMMARY I ran a full upgrade on my Arch Linux system. This upgraded KDE components from 5.27.5 to 5.27.6 and Qt from 5.15.9 to 5.15.10. After this upgrade, my selected keyboard layout (dvorak) was broken in KDE. Oddly, possibly as a side effect of this, all "advanced" keyboard behavior (anything in the advanced tab of the keyboard KCM) was broken as well. For example, I have the Caps Lock key configured to be an additional Menu key, but pressing that key only activated caps lock after the upgrade. I've included the full Pacman log from the upgrade in case it's somehow relevant. NOTES * I normally have a layout switcher with two layouts visible on my taskbar, thanks to the keyboard layout widget. This widget was entirely hidden because only one layout was active (US Qwerty). * Going into the keyboard layout setting and removing all layouts except Dvorak from my configured layouts did not solve the problem. Even with US (Qwerty) removed, my keyboard behaved like US Qwerty and advanced configuration didn't work. RESOLUTION / WORKAROUND I was able to solve the problem by removing the dvorak layout and then re-adding it to my configuration. This also fixed the advanced behavior. I noted, when re-adding the keyboard, that there was no bare "dvorak" layout anymore. I had to select "English (Dvorak)", with the flag of the United States. I don't think this layout previously existed? Previously, the switcher widget did not show a flag for Dvorak, instead showing the letters "dvk" or "dvorak". I think what probably happened here is that this bare "dvorak" layout was removed in 5.27.6 in favor of localized Dvorak layouts with a flag, but this broke existing configurations because the layout name defined in the system configuration no longer exists. If this is the case, IMO this should be fixed with a point release so that users who have the existing configuration are seamlessly upgraded to the new configuration for Dvorak layouts. Basically, fixing this issue as early as possible would be ideal so that this bites as few users as possible. I haven't used Qwerty in over a decade (it's only there for other people borrowing this computer), so this bug effectively made my computer unusable for me until I found the workaround. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.27.6 KDE Frameworks Version: 5.107.0 Qt Version: 5.15.10 Kernel Version: 6.3.9-arch1-1 (64-bit) Graphics Platform: X11 ADDITIONAL INFORMATION Apologies for putting this in kde/general. I wasn't able to determine which system component is responsible for managing keyboard configurations. As far as I know, the systemsettings KCM is just an interface, and Kwin probably handles the keyboard mapping itself, but I wasn't able to guess further than that. Hopefully someone can help me by triaging. Thanks! -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 471183] Face recognition, see and edit references
https://bugs.kde.org/show_bug.cgi?id=471183 --- Comment #18 from Andy --- Mike = Maik! Sorry! -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 471183] Face recognition, see and edit references
https://bugs.kde.org/show_bug.cgi?id=471183 --- Comment #17 from Andy --- Hi Mike! I'll stop with face recognition for now. It frustrates me a little bit because I keep having to reject the same images over and over again. And because 90% of the images are assigned to the wrong people. Apparently, face recognition doesn't learn from newly assigned faces. Even very clearly recognizable faces remain in unknown or are not framed. As a suggestion for the developers, it might help that only the last 50 added faces per person are used for face recognition??? The recognition grows with the years of life and the appearance of a person. It's just a layman's idea :-) @Craig The post in your link seems to be a different problem. I'm really looking forward to the next program version. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 468908] With nushell as a default shell, folders with Arabic file names cannot be opened
https://bugs.kde.org/show_bug.cgi?id=468908 --- Comment #3 from Munzir Taha --- I just found the bug is related to me making nushell a default. It's actually not restricted to Arabic. If I create a folder with a name that ends in space, I get the same issue. Create a folder named 'F ' with a trailing space. Trying to open it dolphin shows The file or folder /tmp/F does not exist. The space is not passed as part of the name. There is no problem using nushell from the terminal to access the folder, so I guess, the bug lies in dolphin integration to shells -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 471800] New: some unicode characters make text line shift downwards at the default line height multiplier, cutting out underscores
https://bugs.kde.org/show_bug.cgi?id=471800 Bug ID: 471800 Summary: some unicode characters make text line shift downwards at the default line height multiplier, cutting out underscores Classification: Applications Product: kate Version: 23.04.0 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: kwrite-bugs-n...@kde.org Reporter: watisthis...@outlook.com Target Milestone: --- Created attachment 160001 --> https://bugs.kde.org/attachment.cgi?id=160001=edit twohearts added Adding certain unicode (UTF-8) characters (eg. the 'two hearts' character https://www.utf8icons.com/character/128149/two-hearts) shifts the whole text line downwards, making eg. underscore characters cut out at the default line height multiplier. >From Kate's settings the default font is Courier New 9 and line height multiplier is 1.0. Increasing line height multiplier helps to the cutting out characters. I'm using Kate 23.04.0 from Microsoft Store on Windows 10. Not sure if this is easily fixable or if the workaround is to just increase the line height.. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 468908] With nushell as a default shell, folders with Arabic file names cannot be opened
https://bugs.kde.org/show_bug.cgi?id=468908 Munzir Taha changed: What|Removed |Added Summary|[Regression]: Dolphin |With nushell as a default |cannot open folders with|shell, folders with Arabic |Arabic names|file names cannot be opened -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 471797] DigiKam crashes on startup at 74% on Finding New Files
https://bugs.kde.org/show_bug.cgi?id=471797 caulier.gil...@gmail.com changed: What|Removed |Added OS|Other |Microsoft Windows Component|general |Database-Scan CC||caulier.gil...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|crash |wishlist -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|wishlist|crash -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 471799] New: escape to turn off screen only works on wayland
https://bugs.kde.org/show_bug.cgi?id=471799 Bug ID: 471799 Summary: escape to turn off screen only works on wayland Classification: Plasma Product: kscreenlocker Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: tsengal...@gmail.com Target Milestone: --- SUMMARY Pressing escape should turn off the screen when on the lock screen. However, this behavior only happens when I am logged in to a wayland session. Pressing escape on the lock screen on a X11 session does nothing. STEPS TO REPRODUCE 1. Log in to a wayland 5.27 session 2. Lock the screen 3. Press escape. The screen should turn off 4. Do the same with a X11 session (log out of wayland session first). The screen does not turn off. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Debian 12.0, kernel 6.1.0-9-amd64 (available in About System) 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.
[kwin] [Bug 452119] With an Intel iGPU, animations aren't as smooth on Wayland versus Xorg
https://bugs.kde.org/show_bug.cgi?id=452119 Mads changed: What|Removed |Added CC||m...@ab3.no -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 471798] New: Manufacturer's Notes' metadata disappears
https://bugs.kde.org/show_bug.cgi?id=471798 Bug ID: 471798 Summary: Manufacturer's Notes' metadata disappears Classification: Applications Product: digikam Version: 8.0.0 Platform: Appimage OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Metadata-Exif Assignee: digikam-bugs-n...@kde.org Reporter: dan...@laposte.net 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 *** When import my photos, most of 'maker's notes' in metadata disappears. Only 'maker's notes', since version 7.9.0 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.
[valgrind] [Bug 471634] strtod() gives inaccurate values on Alpine Linux (musl-libc) under valgrind
https://bugs.kde.org/show_bug.cgi?id=471634 --- Comment #2 from Nick Little --- After looking through musl's strtod implementation, yes, long double is used. That is probably the issue. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|crash |wishlist -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|wishlist|crash -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 471797] DigiKam crashes on startup at 74% on Finding New Files
https://bugs.kde.org/show_bug.cgi?id=471797 Bug Janitor Service changed: What|Removed |Added Severity|critical|crash -- You are receiving this mail because: You are watching all bug changes.
[LabPlot2] [Bug 410175] [Feature Request] Reversed axis
https://bugs.kde.org/show_bug.cgi?id=410175 Stefan Gerlach changed: What|Removed |Added Summary|Reversed axis |[Feature Request] Reversed ||axis CC||stefan.gerlach@uni-konstanz ||.de -- You are receiving this mail because: You are watching all bug changes.
[LabPlot2] [Bug 405387] [Feature Request] Python scripting
https://bugs.kde.org/show_bug.cgi?id=405387 Stefan Gerlach changed: What|Removed |Added Summary|Feature request: python |[Feature Request] Python |scripting |scripting CC||stefan.gerlach@uni-konstanz ||.de -- You are receiving this mail because: You are watching all bug changes.
[LabPlot2] [Bug 469367] Segmentation fault when trying to open an Origin file.
https://bugs.kde.org/show_bug.cgi?id=469367 Stefan Gerlach changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|REPORTED|RESOLVED CC||stefan.gerlach@uni-konstanz ||.de Assignee|alexander.se...@web.de |stefan.gerlach@uni-konstanz ||.de -- You are receiving this mail because: You are watching all bug changes.
[LabPlot2] [Bug 457577] [Feature Request] Better support for time series diagram with trilean values
https://bugs.kde.org/show_bug.cgi?id=457577 Stefan Gerlach changed: What|Removed |Added CC||stefan.gerlach@uni-konstanz ||.de Summary|Better support for time |[Feature Request] Better |series diagram with trilean |support for time series |values |diagram with trilean values -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 471797] New: DigiKam crashes on startup at 74% on Finding New Files
https://bugs.kde.org/show_bug.cgi?id=471797 Bug ID: 471797 Summary: DigiKam crashes on startup at 74% on Finding New Files Classification: Applications Product: digikam Version: 8.1.0 Platform: Microsoft Windows OS: Other Status: REPORTED Severity: critical Priority: NOR Component: general Assignee: digikam-bugs-n...@kde.org Reporter: philip_ram...@hotmail.com Target Milestone: --- SUMMARY DigiKam crashes whenever I start it. "Finding New Items" gets to 74% and then the programme crashes. No logs are left (that I can find). exiftool.exe is left running as a background process. STEPS TO REPRODUCE 1. Start DigiKam 2. Wait until "Finding New Items" progress bar gets to 74% OBSERVED RESULT Programme crashes, with no error message or logs. EXPECTED RESULT Programme should continue running :-) SOFTWARE/OS VERSIONS Windows: 11 Pro 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.
[LabPlot2] [Bug 415375] [Feature Request] Automatically add fit curve equation to the plot and update them automatically.
https://bugs.kde.org/show_bug.cgi?id=415375 Stefan Gerlach changed: What|Removed |Added Assignee|alexander.se...@web.de |stefan.gerlach@uni-konstanz ||.de -- You are receiving this mail because: You are watching all bug changes.
[LabPlot2] [Bug 415375] [Feature Request] Automatically add fit curve equation to the plot and update them automatically.
https://bugs.kde.org/show_bug.cgi?id=415375 Stefan Gerlach changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |MOVED CC||stefan.gerlach@uni-konstanz ||.de --- Comment #2 from Stefan Gerlach --- This feature request is now tracked in #220 at https://invent.kde.org/education/labplot/-/issues/220. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 471796] New: pdf with forms does not handle special characters
https://bugs.kde.org/show_bug.cgi?id=471796 Bug ID: 471796 Summary: pdf with forms does not handle special characters Classification: Applications Product: okular Version: 23.04.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: PDF backend Assignee: okular-de...@kde.org Reporter: pub...@mellomrommet.no Target Milestone: --- SUMMARY When clicking "show forms" and filling in, everything looks fine. However, clicking "Show forms" again after filling in text, `æ` and `å` just disappears while `ø` is changed to `ł`. If filling in `ł` it disappears. Font sizes are also distorted, it seems Okular adjusts the size to fill each form entirely, rendering the document layout ugly. Printing uses the wrong display, even if forms are currently showing the correct characters. STEPS TO REPRODUCE 1. Download https://www.politiet.no/globalassets/02-tjenester-admin/politiattest/bekreftelse-pa-formal-med-soknad-om-politiattest.pdf 2. Open with Okular and click "Show forms". Fill in text containing special characters (the Norwegian æ, ø, å or others like ł or µ) 3. Click "Show forms" again. OBSERVED RESULT Text is incorrectly displayed and printed EXPECTED RESULT Text should be correctly displayed and printed SOFTWARE/OS VERSIONS Operating System: Manjaro Linux KDE Plasma Version: 5.27.5 KDE Frameworks Version: 5.106.0 Qt Version: 5.15.9 Kernel Version: 5.15.114-2-MANJARO (64-bit) Graphics Platform: X11 ADDITIONAL INFORMATION Filling in forms / saving / opening / displaying in Firefox works as expected. Printing to pdf from Firefox and opening in Okular, characters display correctly but font sizes are inconsistent. -- You are receiving this mail because: You are watching all bug changes.
