[frameworks-kwayland] [Bug 463065] paste issue to applications
https://bugs.kde.org/show_bug.cgi?id=463065 --- Comment #1 from Dennis --- Haven't seen this anymore in 22.10, 23.04, 24.04 and Neon unstable. Not sure it still happens on 22.04 but as there has been no other reports, we can close this as far as I'm concerned. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 460753] Feature request: network manager VPN connection parameter free field
https://bugs.kde.org/show_bug.cgi?id=460753 Dennis changed: What|Removed |Added Platform|Ubuntu |Neon CC||dennis@thegood.cloud Version|5.25.5 |master -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 458746] Apply button doesn't become active after editing wireguard connection
https://bugs.kde.org/show_bug.cgi?id=458746 Antti Savolainen changed: What|Removed |Added CC||antti.s...@gmail.com --- Comment #4 from Antti Savolainen --- I noticed that the apply button appears every second time the menu is viewed. Demonstrative video: https://youtu.be/McEqA54A35o -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 477486] On Neon unstable, dolphin does not have any compress/extract context menu's anymore
https://bugs.kde.org/show_bug.cgi?id=477486 --- Comment #6 from Dennis --- No, Ark is using: Qt Version 5.15.11 (built against 5.15.11) Dolphin is using: Qt Version 6.6.0 (built against 6.6.0) -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 477538] Reference Images Tool Leaves Black Area After Saving
https://bugs.kde.org/show_bug.cgi?id=477538 --- Comment #4 from Alvin Wong --- Can you at least confirm that it doesn't happen on 5.2.1, and that it does happen with the latest stable nightly build? [1] Please also attach the full output from "Help"->"Show system information for bug reports". [1]: https://binary-factory.kde.org/job/Krita_Stable_Windows_Build/ -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 477654] New: Plasma crash
https://bugs.kde.org/show_bug.cgi?id=477654 Bug ID: 477654 Summary: Plasma crash Classification: Plasma Product: plasmashell Version: 5.27.8 Platform: FreeBSD Ports OS: FreeBSD Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: poncife...@hotmail.com CC: k...@davidedmundson.co.uk Target Milestone: 1.0 Application: plasmashell (5.27.8) Qt Version: 5.15.10 Frameworks Version: 5.110.0 Operating System: FreeBSD 13.2-RELEASE-p4 amd64 Windowing System: X11 Distribution (Platform): FreeBSD Ports DrKonqi: 5.27.8 [KCrashBackend] -- Information about the crash: Plasma shell crashed after rearranging widgets in edit mode. I've tried reproducing the exact widgets I was using at the time but cannot seem to reproduce the crash. The reporter is unsure if this crash is reproducible. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault (lldb) process attach --pid 59678 Process 59678 stopped * thread #1, name = 'plasmashell', stop reason = signal SIGSTOP frame #0: 0x00083ef3b328 libc.so.7`__sys_wait4 + 8 libc.so.7`__sys_wait4: -> 0x83ef3b328 <+8>: syscall 0x83ef3b32a <+10>: jb 0x83ef37f28 0x83ef3b330 <+16>: retq 0x83ef3b331: int3 thread #2, name = 'plasmas:disk$0', stop reason = signal SIGSTOP frame #0: 0x000844d45d2c libthr.so.3`___lldb_unnamed_symbol546 + 12 libthr.so.3`___lldb_unnamed_symbol546: -> 0x844d45d2c <+12>: retq 0x844d45d2d <+13>: int3 0x844d45d2e <+14>: int3 0x844d45d2f <+15>: int3 thread #3, name = 'plasmash:gdrv0', stop reason = signal SIGSTOP frame #0: 0x000844d45d2c libthr.so.3`___lldb_unnamed_symbol546 + 12 libthr.so.3`___lldb_unnamed_symbol546: -> 0x844d45d2c <+12>: retq 0x844d45d2d <+13>: int3 0x844d45d2e <+14>: int3 0x844d45d2f <+15>: int3 thread #4, name = 'plasmashell', stop reason = signal SIGSTOP frame #0: 0x000844d52a2b libthr.so.3`_pthread_getspecific + 59 libthr.so.3`_pthread_getspecific: -> 0x844d52a2b <+59>: cmpl 0x4(%rdx,%rax), %esi 0x844d52a2f <+63>: jne0x844d52a37 ; <+71> 0x844d52a31 <+65>: movq (%rcx,%rax), %rax 0x844d52a35 <+69>: popq %rbp thread #5, name = 'plasmashell', stop reason = signal SIGSTOP frame #0: 0x00083ef3b00a libc.so.7`__sys_kevent + 10 libc.so.7`__sys_kevent: -> 0x83ef3b00a <+10>: jb 0x83ef37f28 0x83ef3b010 <+16>: retq 0x83ef3b011: int3 0x83ef3b012: int3 thread #6, name = 'plasmashell', stop reason = signal SIGSTOP frame #0: 0x00083ef3b0ca libc.so.7`__sys_poll + 10 libc.so.7`__sys_poll: -> 0x83ef3b0ca <+10>: jb 0x83ef37f28 0x83ef3b0d0 <+16>: retq 0x83ef3b0d1: int3 0x83ef3b0d2: int3 thread #7, name = 'plasmashell', stop reason = signal SIGSTOP frame #0: 0x00083ef366f9 libc.so.7`___lldb_unnamed_symbol4979 + 249 libc.so.7`___lldb_unnamed_symbol4979: -> 0x83ef366f9 <+249>: imulq $0x1dcd65, %rax, %rax ; imm = 0x1DCD65 0x83ef36700 <+256>: imulq $0x1dcd65, %rcx, %rcx ; imm = 0x1DCD65 0x83ef36707 <+263>: shrq $0x17, %rcx 0x83ef3670b <+267>: addq %rax, %rcx thread #8, name = 'plasmashell', stop reason = signal SIGSTOP frame #0: 0x000844d4dc18 libthr.so.3`___lldb_unnamed_symbol620 + 328 libthr.so.3`___lldb_unnamed_symbol620: -> 0x844d4dc18 <+328>: jne0x844d4dc00 ; <+304> 0x844d4dc1a <+330>: xorl %r14d, %r14d 0x844d4dc1d <+333>: testl %ecx, %ecx 0x844d4dc1f <+335>: jns0x844d4dc57 ; <+391> thread #9, name = 'plasmash:gdrv0', stop reason = signal SIGSTOP frame #0: 0x000844d45d2c libthr.so.3`___lldb_unnamed_symbol546 + 12 libthr.so.3`___lldb_unnamed_symbol546: -> 0x844d45d2c <+12>: retq 0x844d45d2d <+13>: int3 0x844d45d2e <+14>: int3 0x844d45d2f <+15>: int3 thread #10, name = 'plasmashell', stop reason = signal SIGSTOP frame #0: 0x000844d45d2c libthr.so.3`___lldb_unnamed_symbol546 + 12 libthr.so.3`___lldb_unnamed_symbol546: -> 0x844d45d2c <+12>: retq 0x844d45d2d <+13>: int3 0x844d45d2e <+14>: int3 0x844d45d2f <+15>: int3 thread #11, name = 'plasmashell', stop reason = signal SIGSTOP frame #0: 0x00083ef3b14a libc.so.7`__sys_read + 10 libc.so.7`__sys_read: -> 0x83ef3b14a <+10>: jb 0x83ef37f28 0x83ef3b150 <+16>: retq 0x83ef3b151: int3 0x83ef3b152: int3 thread #12, name = 'plasmash:gdrv0', stop reason = signal SIGSTOP frame #0: 0x000844d45d2c libthr.so.3`___lldb_unnamed_symbol546 + 12 libthr.so.3`___lldb_unnamed_symbol546: -> 0x844d45d2c <+12>: retq 0x844d45d2d <+13>: int3 0x844d45d2e <+14>: int3 0x844d45d2f <+15>: int3 thread
[kde] [Bug 477653] New: Add "Caps Lock (while pressed)" option to switch keyboard layouts
https://bugs.kde.org/show_bug.cgi?id=477653 Bug ID: 477653 Summary: Add "Caps Lock (while pressed)" option to switch keyboard layouts Classification: I don't know Product: kde Version: unspecified Platform: Arch Linux OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: alphabitser...@pm.me Target Milestone: --- Under System Settings → Keyboard → Advanced there's currently an option "Caps Lock (while pressed); Alt+Caps Lock for the original Caps Lock action." I would love if there were an option that functions just like this without the Alt+Caps Lock bind. Basically, just a "Caps Lock (while pressed)" option with no extra behavior from the Alt key. I use a non-Qwerty keyboard layout but a number of applications that support Vim motions. I've configured my system so that I'm always in my preferred layout, but while holding Caps Lock, it temporarily switches to Qwerty so I can easily use the home row for movement without rebinding my editor, terminal, etc. In some applications, for example, Zellij (a terminal multiplexer), includes default keybinds Alt+[hjkl] to navigate between panes. However, I can't make use of it because Alt+Caps Lock will toggle capitalization instead. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 477251] Unable to enter password in sddm wayland
https://bugs.kde.org/show_bug.cgi?id=477251 --- Comment #12 from fanzhuyi...@gmail.com --- (In reply to Vlad Zahorodnii from comment #11) > However, in meanwhile, I created a MR to revert a > layer-shell-qt change so layer shell windows get keyboard input by default. Can verify the MR fixes the issue for me. Thanks! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 477647] Fill Tool Doesn't Grow When on All Layers Mode
https://bugs.kde.org/show_bug.cgi?id=477647 Deif Lou changed: What|Removed |Added CC||gin...@gmail.com Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #2 from Deif Lou --- Please provide more information, a sample file with the drawing that you cannot fill correctly and a screenshot with all the tool settings you are using. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 443036] Metabug: let keyboard shortcuts live somewhere persistent, rather than in applets
https://bugs.kde.org/show_bug.cgi?id=443036 Dmitrii Chermnykh changed: What|Removed |Added CC||chermnykh2...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 477631] digiKam cannot decode Nikon Z8/Z9 NEF images in the HE/HE* formats
https://bugs.kde.org/show_bug.cgi?id=477631 Maik Qualmann changed: What|Removed |Added Summary|digiKam cannot decode Nikon |digiKam cannot decode Nikon |Z8/Z9 NEF images in the |Z8/Z9 NEF images in the |HE/HE* format |HE/HE* formats -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 477631] digiKam cannot decode Nikon Z8/Z9 NEF images in the HE/HE* format
https://bugs.kde.org/show_bug.cgi?id=477631 Maik Qualmann changed: What|Removed |Added Summary|Digikam Version 8.1 cannot |digiKam cannot decode Nikon |decode Nikon Z9 NEF files |Z8/Z9 NEF images in the |in both Ubuntu 22.04 LTS|HE/HE* format |using AppImage install and | |Windows 10 EXE install | -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 477631] Digikam Version 8.1 cannot decode Nikon Z9 NEF files in both Ubuntu 22.04 LTS using AppImage install and Windows 10 EXE install
https://bugs.kde.org/show_bug.cgi?id=477631 --- Comment #5 from Maik Qualmann --- See the status of current support for Z9 HE/HE* format here: https://www.libraw.org/node/2766 Maik -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 477652] New: Layout agnostic search
https://bugs.kde.org/show_bug.cgi?id=477652 Bug ID: 477652 Summary: Layout agnostic search Classification: Plasma Product: krunner Version: unspecified Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: geekx...@gmail.com CC: alexander.loh...@gmx.de, natalie_clar...@yahoo.de Target Milestone: --- SUMMARY When you type some English word with Russian keyboard layout, it would be great for Krunner to search elements with English symbols on the same keys. Google search works as expected, maybe it can be implemented in Krunner as it helps multilayout users a lot. STEPS TO REPRODUCE 1. Open Krunner 2. Type "Firefox" 3. Type "ашкуащч" OBSERVED RESULT When "ашкуащч" typed, nothing is shown EXPECTED RESULT When "ашкуащч" typed Firefox is shown SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora 38 / Wayland / Kernel 6.5.11 KDE Plasma Version: 5.27.9 KDE Frameworks Version: 5.111.0 Qt Version: 5.15.11 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 477251] Unable to enter password in sddm wayland
https://bugs.kde.org/show_bug.cgi?id=477251 Vlad Zahorodnii changed: What|Removed |Added Status|ASSIGNED|CONFIRMED --- Comment #11 from Vlad Zahorodnii --- (In reply to fanzhuyifan from comment #9) > (In reply to Vlad Zahorodnii from comment #6) > > Huh sddm-greeter crashes... > > So should I report this over at the sddm github? Not yet.. We would need to figure out why qtwayland fails to initialize when using xdg-shell. However, in meanwhile, I created a MR to revert a layer-shell-qt change so layer shell windows get keyboard input by default. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 477251] Unable to enter password in sddm wayland
https://bugs.kde.org/show_bug.cgi?id=477251 Bug Janitor Service changed: What|Removed |Added Status|CONFIRMED |ASSIGNED --- Comment #10 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/plasma/layer-shell-qt/-/merge_requests/48 -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 477630] Include ucontext.h rather than sys/ucontext.h in Solaris sources
https://bugs.kde.org/show_bug.cgi?id=477630 Paul Floyd changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #3 from Paul Floyd --- commit 03180d4403b2b6e849d0a311584ed8b1e6528158 Author: Paul Floyd Date: Tue Nov 28 08:00:19 2023 +0100 Bug 477630 - Include ucontext.h rather than sys/ucontext.h in Solaris sources Patch provided by Jakub Kulik kulik...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 477565] slow loading of the db database
https://bugs.kde.org/show_bug.cgi?id=477565 --- Comment #14 from caulier.gil...@gmail.com --- Jean, The 8.2.0 pre-release installer for Windows is online at usual place including commit #5336846cb9b723a09af27042f5a2b9bdb6909956 from Maik. Best Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 475805] Files with ending .bak are treated as if they were hidden.
https://bugs.kde.org/show_bug.cgi?id=475805 --- Comment #6 from Steve Vialle --- (In reply to Felix Ernst from comment #4) > This change was done to fix a long-standing and much reported bug. Please > look at https://bugs.kde.org/show_bug.cgi?id=3212 That's not a bug, it's a 20+ year long discussion on how best to implement a *feature request*, and whether or not it's even a good idea to begin with. What we have here isn't a fix for something that was broken, it's a departure from behaviour that has been standard since KDE 1.0, and followed the example set by such truly obscure file management utilities as 'ls' and the rest of coreutils. > It seems a bit like we are in a situation in which different people want > different and conflicting behaviour. It's a situation where this was requested 23 years ago, and never implemented because nobody could agree on what beyond dotfiles, if anything, should be hidden. Even after the revival this year, nobody at all suggested x-trash be lumped in under the existing "show hidden files" functionality, the request was for *user defined* hidden files. Even Méven's initial proposal to use x-trash mentioned it having it's own toggle... Which for reasons unexplained, it didn't get. What exactly is a hidden file now anyway? Traditional *nix dotfiles? Trash files according to MIME? Backup and temporary files? Anything that doesn't have a defined MIME type? Does what is visible in dolphin depend on the phase of the moon, or just what's considered an "uncluttered view" this week? If an option to hide backup files is really considered necessary, please either provide a visible and documented option to disable it (i.e. not notes on creating random extra mime types buried in an ancient feature request), or move it to it's own "show/hide x-trash mimetype" toggle. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 477470] File name timestamp formats
https://bugs.kde.org/show_bug.cgi?id=477470 --- Comment #4 from Maik Qualmann --- Git commit 0baec12ad941bccfaae4a8ba4bc30089cf90599a by Maik Qualmann. Committed on 28/11/2023 at 06:28. Pushed by mqualmann into branch 'master'. add “MMDD hhmmss” variant detection to the TimeAdjust tool M +2-1core/libs/timeadjust/timeadjustcontainer.cpp https://invent.kde.org/graphics/digikam/-/commit/0baec12ad941bccfaae4a8ba4bc30089cf90599a -- You are receiving this mail because: You are watching all bug changes.
[XWaylandVideoBridge] [Bug 477025] "Wayland to X recording bridge" is present in the task swicher apparently without any reason
https://bugs.kde.org/show_bug.cgi?id=477025 fanzhuyi...@gmail.com changed: What|Removed |Added CC||xalt7x.serv...@gmail.com --- Comment #4 from fanzhuyi...@gmail.com --- *** Bug 477595 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[XWaylandVideoBridge] [Bug 477595] Invisible window on KDE Plasma Task Switcher and Pager
https://bugs.kde.org/show_bug.cgi?id=477595 fanzhuyi...@gmail.com changed: What|Removed |Added CC||fanzhuyi...@gmail.com Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #2 from fanzhuyi...@gmail.com --- *** This bug has been marked as a duplicate of bug 477025 *** -- You are receiving this mail because: You are watching all bug changes.
[XWaylandVideoBridge] [Bug 477025] "Wayland to X recording bridge" is present in the task swicher apparently without any reason
https://bugs.kde.org/show_bug.cgi?id=477025 fanzhuyi...@gmail.com changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=477625 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 477625] Weird icon placement of apps that do not have window in Dekstop Overview
https://bugs.kde.org/show_bug.cgi?id=477625 fanzhuyi...@gmail.com changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=477025 CC||fanzhuyi...@gmail.com --- Comment #1 from fanzhuyi...@gmail.com --- Possible dupe of 477025 -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 477641] Displays wake up right after locking the screens and going to sleep
https://bugs.kde.org/show_bug.cgi?id=477641 Nate Graham changed: What|Removed |Added CC||n...@kde.org --- Comment #2 from Nate Graham --- > When locking the screen, I expect the display to go to sleep immediately and > stay asleep unless I press a key to wake them up Did it do this in the past? because that's not what it does by default, and you need to change some powerdevil settings to make this happen. Did you do so, and it worked in the past, but it stopped working recently? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 477598] Cannot delete panel
https://bugs.kde.org/show_bug.cgi?id=477598 fanzhuyi...@gmail.com changed: What|Removed |Added CC||fanzhuyi...@gmail.com --- Comment #2 from fanzhuyi...@gmail.com --- Can't reproduce on master. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 474918] Gamescope-git complains about missing wp_presentation/presentation-time support
https://bugs.kde.org/show_bug.cgi?id=474918 fanzhuyi...@gmail.com changed: What|Removed |Added CC||fanzhuyi...@gmail.com --- Comment #6 from fanzhuyi...@gmail.com --- (In reply to fanzhuyifan from comment #5) > *** Bug 477601 has been marked as a duplicate of this bug. *** 477601 requests to have this backported to plasma 5 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 474918] Gamescope-git complains about missing wp_presentation/presentation-time support
https://bugs.kde.org/show_bug.cgi?id=474918 --- Comment #5 from fanzhuyi...@gmail.com --- *** Bug 477601 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 477601] Request for wp_presentation/presentation-time to be Backported to Kwin 5.27.9 (at least)
https://bugs.kde.org/show_bug.cgi?id=477601 fanzhuyi...@gmail.com changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE CC||fanzhuyi...@gmail.com --- Comment #1 from fanzhuyi...@gmail.com --- *** This bug has been marked as a duplicate of bug 474918 *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 477635] Panel doesn't respect transparency setting, doesn't go transparent/translucent
https://bugs.kde.org/show_bug.cgi?id=477635 fanzhuyi...@gmail.com changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO CC||fanzhuyi...@gmail.com --- Comment #1 from fanzhuyi...@gmail.com --- Could you share a screenshot? I can't reproduce on my end. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 477641] Displays wake up right after locking the screens and going to sleep
https://bugs.kde.org/show_bug.cgi?id=477641 fanzhuyi...@gmail.com changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO CC||fanzhuyi...@gmail.com --- Comment #1 from fanzhuyi...@gmail.com --- Could you restart your machine, reproduce the issue, and provide the complete output of `journal -b`? Thanks! -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 477628] Add mremap support for Solaris
https://bugs.kde.org/show_bug.cgi?id=477628 Paul Floyd changed: What|Removed |Added Assignee|jsew...@acm.org |pjfl...@wanadoo.fr CC||pjfl...@wanadoo.fr -- You are receiving this mail because: You are watching all bug changes.
[kommit] [Bug 469468] Unable to open repo's
https://bugs.kde.org/show_bug.cgi?id=469468 --- Comment #2 from Jason Playne --- (In reply to Hamed Masafi from comment #1) > Could you please test with new version? > Now I don't think there is such a problem. > Please test with the latest version and let me know the result Hi Hamed, So sorry for not doing this sooner (I only just found it in my inbox) I found that the snap version was unable to open my existing repos the flatpak version was able to. So it's going to be a snap packaging issue. How I tested: * I still had Kommit installed via snap (v1.0.2) and opened it up and attempted to open my repo, nothing * I performed the following actions from the dialog ```ATTENTION sudo snap connect kommit:gpg-keys :gpg-keys sudo snap connect kommit:ssh-keys :ssh-keys if you wish to use your pre-existing keys``` * Opened a git repo - noithing Installed Kommit via Flatpak and it just worked. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 477650] Digikam crash when there is a avif file
https://bugs.kde.org/show_bug.cgi?id=477650 --- Comment #1 from caulier.gil...@gmail.com --- This problem must be fixed with current 8.2.0 pre-release installer available here : https://files.kde.org/digikam/ Please test and report. Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 477650] Digikam crash when there is a avif file
https://bugs.kde.org/show_bug.cgi?id=477650 caulier.gil...@gmail.com changed: What|Removed |Added CC||caulier.gil...@gmail.com Component|DImg-Core |Plugin-DImg-QImage -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 477592] Konsole crashes when mouse over of right side of the window.
https://bugs.kde.org/show_bug.cgi?id=477592 --- Comment #2 from d...@moxvallix.com --- (In reply to tcanabrava from comment #1) > Created attachment 163531 [details] > attachment-274781-0.html > > Please provide a backtrace > > On Mon, 27 Nov 2023 at 05:44 wrote: > > > https://bugs.kde.org/show_bug.cgi?id=477592 > > > > Bug ID: 477592 > >Summary: Konsole crashes when mouse over of right side of the > > window. > > Classification: Applications > >Product: konsole > >Version: 23.08.3 > > Platform: Other > > OS: Linux > > Status: REPORTED > > Severity: normal > > Priority: NOR > > Component: general > > Assignee: konsole-de...@kde.org > > Reporter: d...@moxvallix.com > > Target Milestone: --- > > > > SUMMARY > > Konsole crashes when the mouse hovers over the right side of the screen. > > Also, > > text doesn't render on the right side, and running programs, such as > > pacman, > > also cause a crash. > > > > STEPS TO REPRODUCE > > 1. Open Konsole > > 2. Mouse-over the right side of the window (specifically in the text > > area). > > > > OBSERVED RESULT > > Konsole crashes. > > > > EXPECTED RESULT > > I should be able to mouse over the right side of the window. > > > > SOFTWARE/OS VERSIONS > > Operating System: Arch Linux ARM > > KDE Plasma Version: 5.27.9 > > KDE Frameworks Version: 5.112.0 > > Qt Version: 5.15.11 > > Kernel Version: 6.1.62-3-rpi-ARCH (32-bit) > > Graphics Platform: X11 > > Processors: 4 x ARM Cortex-A72 > > Memory: 1.8 GiB of RAM > > Graphics Processor: V3D 4.2 > > Product Name: Raspberry Pi 4 Model B Rev 1.1 > > > > -- > > You are receiving this mail because: > > You are the assignee for the bug. I think this is what you need, hopefully: Starting program: /usr/bin/konsole [Thread debugging using libthread_db enabled] Using host libthread_db library "/usr/lib/libthread_db.so.1". [New Thread 0xaebcf220 (LWP 13787)] [New Thread 0xae1ff220 (LWP 13788)] [New Thread 0xa401e220 (LWP 13789)] [New Thread 0xa26ae220 (LWP 13790)] [New Thread 0xa1ead220 (LWP 13791)] [New Thread 0xa12ff220 (LWP 13792)] [New Thread 0xa0afe220 (LWP 13793)] [Detaching after fork from child process 13795] Thread 1 "konsole" received signal SIGSEGV, Segmentation fault. 0xb6e7b4ec in Konsole::TerminalDisplay::getCharacterPosition(QPoint const&, bool) const () from /usr/lib/libkonsoleprivate.so.1 Quit Thread 8 (Thread 0xa0afe220 (LWP 13793) "Thread (pooled)"): #0 0xb5617f78 in () at /usr/lib/libc.so.6 #1 0xb56180bc in () at /usr/lib/libc.so.6 #2 0xb561b934 in __pthread_cond_timedwait64 () at /usr/lib/libc.so.6 #3 0xb561bb70 in pthread_cond_timedwait () at /usr/lib/libc.so.6 #4 0xb59edb18 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib/libQt5Core.so.5 #5 0xb59ea874 in () at /usr/lib/libQt5Core.so.5 #6 0xb59e6498 in () at /usr/lib/libQt5Core.so.5 #7 0xb561c140 in () at /usr/lib/libc.so.6 #8 0xb569dd1c in () at /usr/lib/libc.so.6 Thread 7 (Thread 0xa12ff220 (LWP 13792) "Thread (pooled)"): #0 0xb5617f78 in () at /usr/lib/libc.so.6 #1 0xb56180bc in () at /usr/lib/libc.so.6 #2 0xb561b934 in __pthread_cond_timedwait64 () at /usr/lib/libc.so.6 #3 0xb561bb70 in pthread_cond_timedwait () at /usr/lib/libc.so.6 #4 0xb59edb18 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib/libQt5Core.so.5 #5 0xb59ea874 in () at /usr/lib/libQt5Core.so.5 #6 0xb59e6498 in () at /usr/lib/libQt5Core.so.5 #7 0xb561c140 in () at /usr/lib/libc.so.6 #8 0xb569dd1c in () at /usr/lib/libc.so.6 Thread 6 (Thread 0xa1ead220 (LWP 13791) "Thread (pooled)"): #0 0xb5617f78 in () at /usr/lib/libc.so.6 #1 0xb56180bc in () at /usr/lib/libc.so.6 #2 0xb561b934 in __pthread_cond_timedwait64 () at /usr/lib/libc.so.6 #3 0xb561bb70 in pthread_cond_timedwait () at /usr/lib/libc.so.6 #4 0xb59edb18 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib/libQt5Core.so.5 #5 0xb59ea874 in () at /usr/lib/libQt5Core.so.5 #6 0xb59e6498 in () at /usr/lib/libQt5Core.so.5 #7 0xb561c140 in () at /usr/lib/libc.so.6 #8 0xb569dd1c in () at /usr/lib/libc.so.6 Thread 5 (Thread 0xa26ae220 (LWP 13790) "Thread (pooled)"): #0 0xb5617f78 in () at /usr/lib/libc.so.6 #1 0xb56180bc in () at /usr/lib/libc.so.6 #2 0xb561b934 in __pthread_cond_timedwait64 () at /usr/lib/libc.so.6 #3 0xb561bb70 in pthread_cond_timedwait () at /usr/lib/libc.so.6 #4 0xb59edb18 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib/libQt5Core.so.5 #5 0xb59ea874 in () at /usr/lib/libQt5Core.so.5 #6 0xb59e6498 in () at /usr/lib/libQt5Core.so.5 #7 0xb561c140 in () at /usr/lib/libc.so.6 #8 0xb569dd1c in () at /usr/lib/libc.so.6 Thread 4 (Thread 0xa401e220 (LWP 13789) "konsole:disk$0"): #0 0xb5617f78 in () at /usr/lib/libc.so.6 #1 0xb56180bc in () at /usr/lib/libc.so.6 #2 0xb561b540 in pthread_cond_wait () at /usr/lib/libc.so.6 #3 0xabb0e74c in () at
[XWaylandVideoBridge] [Bug 476846] Crash on Loading Screenshare on Dicore
https://bugs.kde.org/show_bug.cgi?id=476846 Gaia Noseworthy changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 476891] The power manager does not work
https://bugs.kde.org/show_bug.cgi?id=476891 --- Comment #2 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.
[neon] [Bug 424763] The kdenlive snap version cannot read or access folder that have an Arabic name (RTL)
https://bugs.kde.org/show_bug.cgi?id=424763 --- Comment #3 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.
[XWaylandVideoBridge] [Bug 476846] Crash on Loading Screenshare on Dicore
https://bugs.kde.org/show_bug.cgi?id=476846 --- Comment #4 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.
[krita] [Bug 477651] New: The interface is flickering while working
https://bugs.kde.org/show_bug.cgi?id=477651 Bug ID: 477651 Summary: The interface is flickering while working Classification: Applications Product: krita Version: 5.2.1 Platform: Compiled Sources OS: All Status: REPORTED Severity: normal Priority: NOR Component: * Unknown Assignee: krita-bugs-n...@kde.org Reporter: jvineetmat...@gmail.com Target Milestone: --- SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. 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 The interface is flickering while working -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 477556] copy text on firefox leads to another tab or make a new tab sign on the right side of firefox
https://bugs.kde.org/show_bug.cgi?id=477556 drag...@qq.com changed: What|Removed |Added Platform|Other |Arch Linux -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 477650] New: Digikam crash when there is a avif file
https://bugs.kde.org/show_bug.cgi?id=477650 Bug ID: 477650 Summary: Digikam crash when there is a avif file Classification: Applications Product: digikam Version: 8.1.0 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: crash Priority: NOR Component: DImg-Core Assignee: digikam-bugs-n...@kde.org Reporter: tszw...@tszwing.net Target Milestone: --- Created attachment 163557 --> https://bugs.kde.org/attachment.cgi?id=163557=edit Digikam crash log, this log is the result of starting digikam for 2 times 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. I have a dropbox camera upload folder with around 80k images 2. I create a new library and try to import the dropbox camera upload folder 3. it load for hours, then it crash, when I re-open digikam, it will scan for new files, it stop at 99% for a few seconds then it crash. 4. when I remove the avif file from the folder, the digikam can start 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.
[krita] [Bug 477649] New: Python Paste as Paint Layer
https://bugs.kde.org/show_bug.cgi?id=477649 Bug ID: 477649 Summary: Python Paste as Paint Layer Classification: Applications Product: krita Version: 5.2.1 Platform: Other OS: Other Status: REPORTED Severity: wishlist Priority: NOR Component: Scripting Assignee: krita-bugs-n...@kde.org Reporter: keyth2363...@gmail.com Target Milestone: --- Ability to make a paste into new layer directly. Using a command like: Krita.instance().action( "paste_as_paint_layer" ).trigger() it would act like “edit_paste” action but would not be tool dependent on how paste would act. Currently “edit_paste” with every tool places a new layer but if the Reference tool is active it places references instead. In contrast “paste_into” does not create a new layer and gets stuck on a transform action and needs a input from the user to be finished. There is a “paste_as_reference” layer so it would be nice to -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 477648] New: Python API Active Tool request
https://bugs.kde.org/show_bug.cgi?id=477648 Bug ID: 477648 Summary: Python API Active Tool request Classification: Applications Product: krita Version: 5.2.0 Platform: Other OS: Other Status: REPORTED Severity: wishlist Priority: NOR Component: Scripting Assignee: krita-bugs-n...@kde.org Reporter: keyth2363...@gmail.com Target Milestone: --- A python API question to know which tool is active. could be something like : Krita.instance().activeTool() or in alternative to be able to do: - Krita.instance().tools() : giving the list of all tools available - boolean = Krita.instance().action( "InteractionTool" ).isChecked() : to know if a given tool is active -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 477526] NFS Mounts with all_squash,root_squash,anonuid=0,anongid=0 not able to modify files anymore
https://bugs.kde.org/show_bug.cgi?id=477526 --- Comment #1 from Jessica M --- I think this bug may be related to https://invent.kde.org/frameworks/kio/-/merge_requests/1221 -- You are receiving this mail because: You are watching all bug changes.
[Plasma SDK] [Bug 474302] 7436da18590999266e3aa887051aaa3104e7a9fc makes various icons not appear in Cuttlefish
https://bugs.kde.org/show_bug.cgi?id=474302 Justin Zobel changed: What|Removed |Added CC||jus...@kde.org --- Comment #1 from Justin Zobel --- For weather I see org.kde.kweather For preferences-desktop I see three like you do. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 477526] NFS Mounts with all_squash,root_squash,anonuid=0,anongid=0 not able to modify files anymore
https://bugs.kde.org/show_bug.cgi?id=477526 mira...@mirandastreeter.com changed: What|Removed |Added CC||mira...@mirandastreeter.com -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 477526] NFS Mounts with all_squash,root_squash,anonuid=0,anongid=0 not able to modify files anymore
https://bugs.kde.org/show_bug.cgi?id=477526 Jessica M changed: What|Removed |Added CC||jess...@jessicamaybe.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 450147] Visual glitch when the screen is locked while Kate is focused
https://bugs.kde.org/show_bug.cgi?id=450147 Patrick Silva changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #2 from Patrick Silva --- Tested on Arch Linux running Plasma 6 alpha and neon unstable; cannot reproduce. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 477647] Fill Tool Doesn't Grow When on All Layers Mode
https://bugs.kde.org/show_bug.cgi?id=477647 --- Comment #1 from Jeshuá --- It fills normally when the boundary is black, the color before was almost white. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 477355] display configuration applet: cannot leave presentation mode
https://bugs.kde.org/show_bug.cgi?id=477355 --- Comment #6 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/plasma/kscreen/-/merge_requests/262 -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 477355] display configuration applet: cannot leave presentation mode
https://bugs.kde.org/show_bug.cgi?id=477355 Bug Janitor Service changed: What|Removed |Added Status|CONFIRMED |ASSIGNED --- Comment #5 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/3611 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 477286] Alt tab switcher inaccessible with Orca on X and Wayland sessions
https://bugs.kde.org/show_bug.cgi?id=477286 --- Comment #1 from Fushan Wen --- A workaroud for now is to not use the default grid task switcher. The sidebar task switcher works as expected. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 414621] I cannot press play to play the animation in krita to look it over. It will not play no matter how much I try.
https://bugs.kde.org/show_bug.cgi?id=414621 Ivan Padilla changed: What|Removed |Added CC||shico.toz...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 477647] New: Fill Tool Doesn't Grow When on All Layers Mode
https://bugs.kde.org/show_bug.cgi?id=477647 Bug ID: 477647 Summary: Fill Tool Doesn't Grow When on All Layers Mode Classification: Applications Product: krita Version: nightly build (please specify the git hash!) Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: Tools/Colorize Assignee: krita-bugs-n...@kde.org Reporter: jeshuatu...@gmail.com Target Milestone: --- SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. I set my fill tool to grow 3 px to keep it clean, it's working on "current layer mode", but when on Fill the Merging of All Layers, it doesn't OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: 10 macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION Krita Version: 5.3.0-prealpha (git 042b578) Installation type: installer / portable package Hidpi: true Qt Version (compiled): 5.15.7 Version (loaded): 5.15.7 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 477475] Power profile is impossible to change
https://bugs.kde.org/show_bug.cgi?id=477475 Natalie Clarius changed: What|Removed |Added Resolution|--- |UPSTREAM Status|REPORTED|RESOLVED --- Comment #1 from Natalie Clarius --- Looks like a bug in the power profiles daemon itself, not in the Plasma applet: https://gitlab.freedesktop.org/hadess/power-profiles-daemon/-/issues/106 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 474016] Energy profile: Slider always immediately jumps back to "Save energy" mode
https://bugs.kde.org/show_bug.cgi?id=474016 Natalie Clarius changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=477475 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 477475] Power profile is impossible to change
https://bugs.kde.org/show_bug.cgi?id=477475 Natalie Clarius changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=474016 -- You are receiving this mail because: You are watching all bug changes.
[kooka] [Bug 47525] ocr doesn't work well while gocr works fine
https://bugs.kde.org/show_bug.cgi?id=47525 Natalie Clarius changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=477475 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 477475] Power profile is impossible to change
https://bugs.kde.org/show_bug.cgi?id=477475 Natalie Clarius changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=47525 -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 477638] Allow closing Krunner with another Meta press
https://bugs.kde.org/show_bug.cgi?id=477638 Natalie Clarius changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO --- Comment #1 from Natalie Clarius --- KRunner does have functionality to toggle. How do you have your shortcut set up? -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 477355] display configuration applet: cannot leave presentation mode
https://bugs.kde.org/show_bug.cgi?id=477355 Natalie Clarius changed: What|Removed |Added Assignee|kscreen-bugs-n...@kde.org |natalie_clar...@yahoo.de -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 477646] New: Text box flickers when typing in an electron/chromium application using an nvidia gpu
https://bugs.kde.org/show_bug.cgi?id=477646 Bug ID: 477646 Summary: Text box flickers when typing in an electron/chromium application using an nvidia gpu Classification: Plasma Product: kwin Version: 5.27.9 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: kde.propeller...@passinbox.com Target Milestone: --- When typing in any kind of text box in a chromium/electon based application, the last few typed characters typed in will sometimes dissapear and reappear inconsistently on an nvidia gpu. STEPS TO REPRODUCE 1. Open any kind of chromium based application (Ex. the thorium browser). 2. Type in a text box. OBSERVED RESULT The last few characters sometimes flicker when typing. EXPECTED RESULT The flickering shouldn't be happening. SOFTWARE/OS VERSIONS Linux: 6.6 KDE Plasma Version: 5.7.9 KDE Frameworks Version: 5.112 Qt Version: 5.15.11 This happens on a 30 series nvidia gpu using version 545.29 of the proprietary drivers. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 477645] New: KATE Document Preview Plugin only displaying plain text for HTML
https://bugs.kde.org/show_bug.cgi?id=477645 Bug ID: 477645 Summary: KATE Document Preview Plugin only displaying plain text for HTML Classification: Applications Product: kate Version: 21.12.3 Platform: Debian stable OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: plugin-preview Assignee: kwrite-bugs-n...@kde.org Reporter: pokingvic...@protonmail.com Target Milestone: --- Created attachment 163556 --> https://bugs.kde.org/attachment.cgi?id=163556=edit On the left is the Document rendering as expected in Konquerorr using WebEngine as expected. On the right is Kate with the file open, with the preview pane failing to behave as expected. Hopefully this is something easy to fix. Just would like to preface with my infinite gratitude for the fine people of the various KDE projects. SUMMARY When opening an HTML file with Kate, using the Document Preview Plugin, it does not work as expected. The Preview pane merely shows the file in its naked state, not rendering anything. Essentially just a copy of the code in the mane pane. I have tried manually setting it to HTML but with no such luck. I have also made sure I am on the right character set. I have opened the file in Konquerer and the file renders as expected, and since the preview pane uses the same engine to render this is puzzling. I notice that if you open the file directly from the preview pane, it sends you to a temporary file. In my instance this is "/tmp/kate.qLUkQt". You will notice the extension is not .html, I imagine this has a lot to do with the confusion of the preview pane. I have not found a way to redirect the preview pane to the actual file instead of this temporary file, nor should I really have to do that. Hopefully I am not just making a dumb mistake, but I feel like this should be pretty straightforward. Observe the included screenshot. On the left is the Document rendering as expected in Konquerorr using WebEngine as expected. On the right is Kate with the file open, with the preview pane failing to behave as expected. STEPS TO REPRODUCE 1. Activate Document Preview Plugin (which is included, at least in Debian) 2. Restart Kate for good measure 3. Open HTML or HTM File OBSERVED RESULT Plain black on white text in the preview pane, as if WebEngine loaded a text file. EXPECTED RESULT A rendered HTML Document being displayed in the Preview Pane Linux: Debian Stable 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.
[kphotoalbum] [Bug 477530] KPhotoAlbum crashes when new Category is added and immediately set as Category for Untagged Images in Settings
https://bugs.kde.org/show_bug.cgi?id=477530 Johannes Zarl-Zierl changed: What|Removed |Added Latest Commit||https://invent.kde.org/grap ||hics/kphotoalbum/-/commit/6 ||7a8cdf455673bbcd9d9e54a5499 ||8cbb3a53853b Resolution|--- |FIXED Status|CONFIRMED |RESOLVED --- Comment #2 from Johannes Zarl-Zierl --- Git commit 67a8cdf455673bbcd9d9e54a54998cbb3a53853b by Johannes Zarl-Zierl. Committed on 28/11/2023 at 00:45. Pushed by johanneszarl into branch 'master'. Fix crash when renaming or adding a category and using it as untagged category When trying to select an unsaved category (either newly created or renamed) as the untagged category in the category settings page, instead of populating the tag dropdown list, kphotoalbum would crash. The new behavior is to disable the tag dropdown instead. M +1-0CHANGELOG.md M +9-5Settings/UntaggedGroupBox.cpp https://invent.kde.org/graphics/kphotoalbum/-/commit/67a8cdf455673bbcd9d9e54a54998cbb3a53853b -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 474382] On Wayland, no titlebar buttons on CSD-using Firefox in Plasma 6
https://bugs.kde.org/show_bug.cgi?id=474382 --- Comment #21 from fanzhuyi...@gmail.com --- Should this be considered a duplicate of https://bugs.kde.org/show_bug.cgi?id=471853 ? -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 471853] Plasma 6 Wayland - Firefox (115.0) - Min, Max, Close icons are not displayed in header bar
https://bugs.kde.org/show_bug.cgi?id=471853 fanzhuyi...@gmail.com changed: What|Removed |Added CC||fanzhuyi...@gmail.com See Also||https://bugs.kde.org/show_b ||ug.cgi?id=474382 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 474382] On Wayland, no titlebar buttons on CSD-using Firefox in Plasma 6
https://bugs.kde.org/show_bug.cgi?id=474382 fanzhuyi...@gmail.com changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=471853 -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 477355] display configuration applet: cannot leave presentation mode
https://bugs.kde.org/show_bug.cgi?id=477355 --- Comment #4 from Natalie Clarius --- I can reproduce what I understand to be the same bug reported here and in the other thread. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 477355] display configuration applet: cannot leave presentation mode
https://bugs.kde.org/show_bug.cgi?id=477355 --- Comment #3 from Natalie Clarius --- Duplicate of https://bugs.kde.org/show_bug.cgi?id=474437? @Nate, you said you couldn't reproduce on the other bug report but you can here? Can you explain the difference? -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 477644] Implement tear-off windows so multiple documents can be visible simultaneously
https://bugs.kde.org/show_bug.cgi?id=477644 Christoph Cullmann changed: What|Removed |Added CC||cullm...@kde.org Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #1 from Christoph Cullmann --- You can split views and you can move stuff to new full screen windows. Either by 'File -> New Window' or right click a tab an use the 'detach' action. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 477117] Deleting panel sometimes crashes plasmashell in PanelConfigView::hideEvent()
https://bugs.kde.org/show_bug.cgi?id=477117 Nate Graham changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #1 from Nate Graham --- Have not been able to reproduce this recently, and I see lots of related-looking commits. Assuming one of them fixed it. -- You are receiving this mail because: You are watching all bug changes.
[kphotoalbum] [Bug 477530] KPhotoAlbum crashes when new Category is added and immediately set as Category for Untagged Images in Settings
https://bugs.kde.org/show_bug.cgi?id=477530 Johannes Zarl-Zierl changed: What|Removed |Added Ever confirmed|0 |1 CC||johan...@zarl-zierl.at Status|REPORTED|CONFIRMED --- Comment #1 from Johannes Zarl-Zierl --- I can reproduce the crash. It can also be reproduced by renaming a category and then picking it as Category for untagged images. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 477326] w\ fingerprint unlocking enabled: Black screen and cursor for 30 seconds after cancelling screen locking within the "unlock w/o password" grace period
https://bugs.kde.org/show_bug.cgi?id=477326 Bug Janitor Service changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|ASSIGNED --- Comment #4 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/3610 -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 465266] Cancelling the screen locker within the grace period causes authentication failures (which may cause account lockouts)
https://bugs.kde.org/show_bug.cgi?id=465266 Bug Janitor Service changed: What|Removed |Added Status|CONFIRMED |ASSIGNED --- Comment #4 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/3610 -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 477644] New: Implement tear-off windows so multiple documents can be visible simultaneously
https://bugs.kde.org/show_bug.cgi?id=477644 Bug ID: 477644 Summary: Implement tear-off windows so multiple documents can be visible simultaneously Classification: Applications Product: kate Version: unspecified Platform: Neon OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: kwrite-bugs-n...@kde.org Reporter: dave.lindbe...@gmail.com Target Milestone: --- Not much to say. This missing feature is what prevents me from using kate. (I'm using gedit instead, which is worse otherwise but has this critical feature.) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 477643] Plasma 5.27.80 got stuck on the splash screen in VMs with kwin_wayland errors
https://bugs.kde.org/show_bug.cgi?id=477643 Matt Fagnani changed: What|Removed |Added Keywords||qt6 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 477643] New: Plasma 5.27.80 got stuck on the splash screen in VMs with kwin_wayland errors
https://bugs.kde.org/show_bug.cgi?id=477643 Bug ID: 477643 Summary: Plasma 5.27.80 got stuck on the splash screen in VMs with kwin_wayland errors Classification: Plasma Product: kwin Version: 5.27.80 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: matt.fagn...@bell.net Target Milestone: --- Created attachment 163555 --> https://bugs.kde.org/attachment.cgi?id=163555=edit Journal for a boot when Plasma 5.27.80 got stuck on the splash screen in a VM using the llvmpipe driver SUMMARY I booted the Fedora Rawhide/40 KDE Plasma live image Fedora-KDE-Live-x86_64-Rawhide-20231127.n.0.iso in GNOME Boxes QEMU/KVM VMs in a Fedora 39 KDE Plasma host. Fedora-KDE-Live-x86_64-Rawhide-20231127.n.0.iso is the first Fedora Rawhide image using Plasma 5.27.80. Plasma 5.27.80 got stuck on the splash screen which was shown for at least 2 minutes. The cursor was still movable on the splash screen, and it changed to a hand shape when it was over the centre of the screen in some places where Plasma Welcome was later shown. When the VM had 3D acceleration disabled using the llvmpipe mesa 23.3.0-rc2 driver, the spinner on the splash screen spun for a few seconds then froze. When the VM had 3D acceleration enabled using the virgl mesa driver, the spinner on the splash screen spun for 2 seconds then disappeared. I changed to VT2 using the keyboard menu in the top bar of GNOME Boxes and selecting Ctrl+Alt+F2. When I changed back to VT1, Plasma was shown with the Plasma Welcome program open. There were some kwin_wayland errors in the journal when it was starting. Nov 27 16:54:38 kwin_wayland[1683]: kwin_wayland_drm: Atomic Mode Setting disabled on GPU /dev/dri/card1 because of cursor offset issues in virtual machines Nov 27 16:54:39 kwin_wayland[1683]: kwin_core: Parse error in tiles configuration for monitor "92e842d7-5928-5c43-884a-4912e7cc82ed" : "illegal value" Creating default setup Nov 27 16:54:41 kwin_wayland[1683]: OpenGL vendor string: Mesa Nov 27 16:54:41 kwin_wayland[1683]: OpenGL renderer string: llvmpipe (LLVM 17.0.4, 256 bits) Nov 27 16:54:41 kwin_wayland[1683]: OpenGL version string: 4.5 (Core Profile) Mesa 23.3.0-rc2 Nov 27 16:54:41 kwin_wayland[1683]: OpenGL shading language version string: 4.50 Nov 27 16:54:41 kwin_wayland[1683]: Driver: LLVMpipe Nov 27 16:54:41 kwin_wayland[1683]: GPU class: Unknown Nov 27 16:54:41 kwin_wayland[1683]: OpenGL version: 4.5 Nov 27 16:54:41 kwin_wayland[1683]: GLSL version: 4.50 Nov 27 16:54:41 kwin_wayland[1683]: Mesa version: 23.3 Nov 27 16:54:41 kwin_wayland[1683]: Requires strict binding:no Nov 27 16:54:41 kwin_wayland[1683]: Virtual Machine:no Nov 27 16:54:41 kwin_wayland[1683]: Timer query support:yes Nov 27 16:54:41 kwin_wayland[1683]: kwin_core: Parse error in tiles configuration for monitor "4d031bd2-ddeb-57b0-97bb-ac4d7cdf2819" : "illegal value" Creating default setup Nov 27 16:54:42 kwin_wayland[1683]: kwin_wayland_drm: Setting gamma failed! Function not implemented Nov 27 16:54:43 ksplashqml[1691]: libEGL warning: egl: failed to create dri2 screen Nov 27 16:54:43 kwin_wayland_wrapper[1775]: (WW) Option "-listen" for file descriptors is deprecated Nov 27 16:54:43 kwin_wayland_wrapper[1775]: Please use "-listenfd" instead. Nov 27 16:54:43 kwin_wayland_wrapper[1775]: (WW) Option "-listen" for file descriptors is deprecated Nov 27 16:54:43 kwin_wayland_wrapper[1775]: Please use "-listenfd" instead. Nov 27 16:54:43 kwin_wayland_wrapper[1775]: libEGL warning: egl: failed to create dri2 screen Nov 27 16:54:43 kwin_wayland_wrapper[1775]: libEGL warning: egl: failed to create dri2 screen Nov 27 16:54:43 kwin_wayland_wrapper[1775]: libEGL warning: NEEDS EXTENSION: falling back to kms_swrast Nov 27 16:54:43 kwin_wayland_wrapper[1775]: Refusing to try glamor on llvmpipe Nov 27 16:54:43 kwin_wayland_wrapper[1775]: EGL setup failed, disabling glamor Nov 27 16:54:43 kwin_wayland_wrapper[1775]: Failed to initialize glamor, falling back to sw Nov 27 16:54:43 kwin_wayland_wrapper[1785]: The XKEYBOARD keymap compiler (xkbcomp) reports: Nov 27 16:54:43 kwin_wayland_wrapper[1785]: > Warning: Could not resolve keysym XF86CameraAccessEnable Nov 27 16:54:43 kwin_wayland_wrapper[1785]: > Warning: Could not resolve keysym XF86CameraAccessDisable Nov 27 16:54:43 kwin_wayland_wrapper[1785]: > Warning: Could not resolve keysym XF86CameraAccessToggle Nov 27 16:54:43 kwin_wayland
[plasmashell] [Bug 477462] Only symbolic black and white emojis after a system update.
https://bugs.kde.org/show_bug.cgi?id=477462 David REVOY changed: What|Removed |Added Resolution|--- |WORKSFORME Status|REPORTED|RESOLVED --- Comment #1 from David REVOY --- Hi, I could workaround the situation with the actions here: https://invent.kde.org/-/snippets/2230#no-colored-emojis-on-konversation-or-kate In case the link breaks in the future, I copy here the info: This solved the issue: $ sudo dnf install google-noto-emoji-color-fonts Then edit the file /etc/fonts/conf.d/51-local.conf as sudo that setup the fonts and add this between the and tag: sans-serif Noto Sans Noto Color Emoji Noto Emoji DejaVu Sans serif Noto Serif Noto Color Emoji Noto Emoji DejaVu Serif monospace Noto Mono Noto Color Emoji Noto Emoji DejaVu Sans Mono Close, and launch this to refresh the font cache: $ fc-cache I'm closing the bug as resolved as it is probably a local install issue (if it was wide spread, probably other would have complained about it). -- You are receiving this mail because: You are watching all bug changes.
[krdc] [Bug 477642] New: Full-screen toolbar disappears when system in Screen Lock with Energy Saving
https://bugs.kde.org/show_bug.cgi?id=477642 Bug ID: 477642 Summary: Full-screen toolbar disappears when system in Screen Lock with Energy Saving Classification: Applications Product: krdc Version: 23.08.3 Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: uwol...@kde.org Reporter: dave.lindbe...@gmail.com CC: aa...@kde.org Target Milestone: --- Created attachment 163554 --> https://bugs.kde.org/attachment.cgi?id=163554=edit Screenshot illustrating the toolbar I'm referring to SUMMARY If krdc is accessing a remote RDP host (a Windows box) in full-screen mode when the local system (running krdc) goes into Screen Lock and Energy Saving simultaneously, when the user logs back into the local system later, krdc will still be accessing the host, but the toolbar at the top of the full-screen window is gone. There doesn't seem to be any way to get it back short of disconnecting the krdc session from the host side (there's no way to disconnect from the local side that I know of, since you can't access the toolbar). STEPS TO REPRODUCE (in KDE Neon) 1. systemsettings>Workspace Behavior>Screen Locking>Lock screen automatically after 1 minutes 2. systemsettings>Power Management>Energy Saving>Screen Enterg Saving Switch off after 1 minutes 3. Run krdc, connect to remote Windows host via RDP, go into full-screen mode. 4. Leave local system alone in full-screen mode (no keyboard/mouse action) for 2 minutes 5. Click a keyboard key, log back into system with password OBSERVED RESULT Toolbar is gone. EXPECTED RESULT Toolbar should still be visible and usable. SOFTWARE/OS VERSIONS Windows: 10 x64 (remote session) Linux/KDE Plasma: Linux MONOLITH 6.2.0-37-generic #38~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Thu Nov 2 18:01:13 UTC 2 x86_64 x86_64 x86_64 GNU/Linux Distributor ID: Neon Description:KDE neon 5.27 Release:22.04 Codename: jammy KDE Plasma Version: 5.27.9 KDE Frameworks Version: 5.111.0 Qt Version: 5.15.11 ADDITIONAL INFORMATION In attached screenshot, arrow points at the toolbar I'm talking about (I'm not 100% sure that's what it's called). Problem occurs only when local systems is BOTH in Screen Lock *and* Energy Saving mode simultaneously. Either one alone doesn't cause the problem. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 477641] New: Displays wake up right after locking the screens and going to sleep
https://bugs.kde.org/show_bug.cgi?id=477641 Bug ID: 477641 Summary: Displays wake up right after locking the screens and going to sleep Classification: Plasma Product: kscreenlocker Version: 5.27.9 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: ngomp...@gmail.com Target Milestone: --- SUMMARY When locking the screen, I expect the display to go to sleep immediately and stay asleep unless I press a key to wake them up. While it does go to sleep, the screens wake back up immediately with the login prompt. If I press the escape key, they go back to sleep again and stay asleep properly. STEPS TO REPRODUCE 1. Lock the screen via the application menu OBSERVED RESULT The screen locks, goes to sleep, then immediately wakes up with the lock screen. EXPECTED RESULT The screen locks and goes to sleep. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora Linux 39 (KDE Plasma) (available in About System) KDE Plasma Version: 5.27.9 KDE Frameworks Version: 5.111.0 Qt Version: 5.15.11 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[Bluedevil] [Bug 477633] Bluetooth tray applet sometimes doesn't show any devices even if KCM does
https://bugs.kde.org/show_bug.cgi?id=477633 --- Comment #2 from Bharadwaj Raju --- OK, I can reproduce it consistently by waking my laptop from suspend (close lid and reopen). -- You are receiving this mail because: You are watching all bug changes.
[Bluedevil] [Bug 477633] Bluetooth tray applet sometimes doesn't show any devices even if KCM does
https://bugs.kde.org/show_bug.cgi?id=477633 --- Comment #1 from Bharadwaj Raju --- Observation: when this happens and Bluetooth is off at that moment, I don't see the enable switch. I just see the enable button. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 477639] Ability to invert / reverse vertical but not horizontal scrolling, or vice versa
https://bugs.kde.org/show_bug.cgi?id=477639 David Edmundson changed: What|Removed |Added Resolution|--- |UPSTREAM CC||k...@davidedmundson.co.uk Status|REPORTED|RESOLVED --- Comment #2 from David Edmundson --- We're blocked on upstream. You can comment on that MR. If status there changes, feel free top reopen this. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 472503] Video slideshow tool does not produce playable video file - Port tool from QtAv to ffmpeg API.
https://bugs.kde.org/show_bug.cgi?id=472503 --- Comment #7 from Maik Qualmann --- add audio output to media player in the presentations tool: https://invent.kde.org/graphics/digikam/-/commit/49be815d5403ba84651b674004ffb09c142ee299 Maik -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 477640] New: File Selector (?) Rendering Wrong in a Few Apps
https://bugs.kde.org/show_bug.cgi?id=477640 Bug ID: 477640 Summary: File Selector (?) Rendering Wrong in a Few Apps Classification: I don't know Product: kde Version: unspecified Platform: openSUSE OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: dominicglus...@gmail.com Target Milestone: --- Created attachment 163553 --> https://bugs.kde.org/attachment.cgi?id=163553=edit Preview of the screen tearing 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 *** I've noticed this rendering error in some GTK apps but can't pin down the exact cause. I know its consistently an error in Firefox STEPS TO REPRODUCE 1. Start Plasma in Wayland 2. Open Firefox and go to any website that asks for a file upload, for example the kde bug report site 3. Tearing and broken file list making it unable to select something OBSERVED RESULT You can use arrow keys and the file preview to figure out what your selecting but that's the only workaround I've found EXPECTED RESULT Consistent file picker between all apps SOFTWARE/OS VERSIONS Linux/KDE Plasma: 6.6.2-1-default (available in About System) KDE Plasma Version: 5.27.9 KDE Frameworks Version: 5.112.0 Qt Version: 5.15.11 ADDITIONAL INFORMATION Hybrid Nvidia/Intel gpu laptop. I've tested on a amdgpu, and iris intel gpu with the same result -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 477639] Ability to invert / reverse vertical but not horizontal scrolling, or vice versa
https://bugs.kde.org/show_bug.cgi?id=477639 --- Comment #1 from forestbeasts --- ...Well that's not great. I poked at xinput to see whether there were separate scrolling direction properties to fiddle with there, found only one "natural scrolling" setting, and then found https://gitlab.freedesktop.org/libinput/libinput/-/issues/195. It looks like libinput got an upstream issue for allowing inverted scrolling on one axis but not the other, and closed it wontfix because effectively "who needs that". -- Topaz -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 477565] slow loading of the db database
https://bugs.kde.org/show_bug.cgi?id=477565 --- Comment #13 from Maik Qualmann --- I looked at the changes between 8.0.0 and 8.1.0, and I undid the only ones where I could imagine that it would have an influence on the loading time. With one of the next digiKam-8.2.0 pre-release versions we will see whether this was the cause. Maik -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 477565] slow loading of the db database
https://bugs.kde.org/show_bug.cgi?id=477565 --- Comment #12 from Maik Qualmann --- Git commit 5336846cb9b723a09af27042f5a2b9bdb6909956 by Maik Qualmann. Committed on 27/11/2023 at 22:22. Pushed by mqualmann into branch 'master'. revert to ItemAlbumModel from digiKam-8.0.0 M +43 -28 core/libs/models/itemalbummodel.cpp M +4-1core/libs/models/itemalbummodel.h https://invent.kde.org/graphics/digikam/-/commit/5336846cb9b723a09af27042f5a2b9bdb6909956 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 477631] Digikam Version 8.1 cannot decode Nikon Z9 NEF files in both Ubuntu 22.04 LTS using AppImage install and Windows 10 EXE install
https://bugs.kde.org/show_bug.cgi?id=477631 Maik Qualmann changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #4 from Maik Qualmann --- Thanks for the sample NEF images. Yes, these are NEF images compressed in HE/HE* format, so they only have around 30MB instead of 55 MB. With ExifTool you can see that these are compressed in HE format. We can't help here. The Libraw team first has to support this format and that may take some time. Switch back to lossless standard compression in the camera settings. Maik -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 477639] New: Ability to invert / reverse vertical but not horizontal scrolling, or vice versa
https://bugs.kde.org/show_bug.cgi?id=477639 Bug ID: 477639 Summary: Ability to invert / reverse vertical but not horizontal scrolling, or vice versa Classification: Applications Product: systemsettings Version: 5.27.5 Platform: Debian stable OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: kcm_mouse Assignee: plasma-b...@kde.org Reporter: forestbea...@brightfur.net CC: natalie_clar...@yahoo.de Target Milestone: --- SUMMARY Horizontal scrolling on a mouse, e.g. with tilt scroll wheels, can't be kept non-inverted while inverting vertical scroll. STEPS TO REPRODUCE 1. Invert scrolling. 2. Scroll horizontally. OBSERVED RESULT There's only one setting "Invert scroll direction" that covers both vertical and horizontal scrolling. EXPECTED RESULT There should be two separate settings, one for vertical and one for horizontal. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Debian 12 (available in About System) KDE Plasma Version: 5.27.5 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 ADDITIONAL INFORMATION The scroll tilt *can* be rebound using our mouse's software to have right be left and left be right, but it'd be nice to keep them the conceptual right way around. -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 477638] New: Allow closing Krunner with another Meta press
https://bugs.kde.org/show_bug.cgi?id=477638 Bug ID: 477638 Summary: Allow closing Krunner with another Meta press Classification: Plasma Product: krunner Version: unspecified Platform: unspecified OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: amanita+kdeb...@mailbox.org CC: alexander.loh...@gmx.de, natalie_clar...@yahoo.de Target Milestone: --- The standard appliacation menu can be opened and closed with meta. Krunner can only be opened, closing with Esc. It would be great to have it close with Meta too. Is this on purpose? -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 477630] Include ucontext.h rather than sys/ucontext.h in Solaris sources
https://bugs.kde.org/show_bug.cgi?id=477630 --- Comment #2 from Paul Floyd --- (In reply to Paul Floyd from comment #1) > Does this fix issues on more recent versions of Solaris? Or more precisely, which versions? -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 477470] File name timestamp formats
https://bugs.kde.org/show_bug.cgi?id=477470 --- Comment #3 from ratounade --- As there is a french IT in the loop : spéciale dédicace bravo Gilles c'est du super super boulot, merci -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 477470] File name timestamp formats
https://bugs.kde.org/show_bug.cgi?id=477470 ratounade changed: What|Removed |Added CC||rc...@free.fr --- Comment #2 from ratounade --- Hi, DigiKam is great but indeed, it is not clear how ."adjust time" with "File name timestamp" does work. All my +50K photos are under file name "MMDD hhmmss BLABLA!WHATEVER" DigiKam seems ok on 20190526 122104 IMG_1245 -> GOOD time stamp as it is 20190526 122104 but on does not work on 20190526 122104 P1160146 -> BAD time stamp as it is 20190526 160146 Quite surprising. And no way to find out your algorithm does work -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 468980] Digikam and Showfoto interface becomes buggy/broken after opening/closing settings page on Fedora (On Flatpack and AppImage, and only ShowFoto on RPM)
https://bugs.kde.org/show_bug.cgi?id=468980 --- Comment #16 from michael2macdon...@gmail.com --- (In reply to caulier.gilles from comment #15) > michael2macdonald, > > What's about this file using current 8.2.0 AppImage Linux bundle ? It's > reproducible ? > > https://files.kde.org/digikam/ > > Thanks in advance > > Gilles Caulier Sorry for the delayed response. I just tested it on Fedora 39 KDE and it is still reproducible. Michael MacDonald -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 477631] Digikam Version 8.1 cannot decode Nikon Z9 NEF files in both Ubuntu 22.04 LTS using AppImage install and Windows 10 EXE install
https://bugs.kde.org/show_bug.cgi?id=477631 --- Comment #3 from Maik Qualmann --- Note that libraw currently does not support high efficiency compression formats (HE) or HE*. If you have activated this in the camera, there is currently no chance of decoding this. There is currently no free program that can decode this. Maik -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 477379] digikam crashes on start with "failed to create drawable" / "glXCreatePbuffer failed."
https://bugs.kde.org/show_bug.cgi?id=477379 --- Comment #11 from Kristian --- ...and the same crash with a different user who newer used digikam. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 465815] KMail assumes KDEWallet as Secret Service provider, breaking other alternatives
https://bugs.kde.org/show_bug.cgi?id=465815 lod changed: What|Removed |Added Ever confirmed|0 |1 Version|5.22.2 |5.24.3 CC||k...@cyber-anlage.de Status|REPORTED|CONFIRMED Platform|Manjaro |Arch Linux --- Comment #3 from lod --- Same problem in the latest Version. -- You are receiving this mail because: You are watching all bug changes.
