[Akonadi] [Bug 395131] Akonadi consumes all memory
https://bugs.kde.org/show_bug.cgi?id=395131 Ryan changed: What|Removed |Added CC||r...@interoctiv.com --- Comment #19 from Ryan --- (In reply to sombriks from comment #18) > Hi, i can confirm that bug still occurs ... > using openSUSE Tumbleweed kernel 6.5.6-1-default Also occurs with: openSUSE Tumbleweed 20240509 KDE Plasma Version: 6.0.4 KDE Frameworks Version: 6.1.0 Qt Version: 6.7.0 Kernel Version: 6.8.8-1-default (64-bit) Graphics Platform: Wayland -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 480925] Crash in KeyboardInterface::sendKey
https://bugs.kde.org/show_bug.cgi?id=480925 --- Comment #9 from Ryan Rix --- I'm sorry, I should have added that as an attachment or filtered the output. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 480925] Crash in KeyboardInterface::sendKey
https://bugs.kde.org/show_bug.cgi?id=480925 --- Comment #8 from Ryan Rix --- This crash has been happening to me multiple times a day some days for about three months now. does anyone have any advice to root-cause and debug this? I am prepared to patch and compile kwayland and kwin_wayland at least from source, and can decently printf debug, but don't really know much about how wayland works to really have a conceptual understanding of what is happening on this codepath. But it happens most regularly when i press ctrl-backspace, which i do in both of my primary applications emacs and firefox, as a muscle memory. It happened while I was drafting this comment. [rrix@virtuous-cassette:~]$ sudo coredumpctl list | grep kwin_wayland [sudo] password for rrix: Mon 2024-04-15 20:09:01 PDT5657 1000 1000 SIGSEGV missing /nix/store/8hwpp6dgndnihkg2gbwkvqllv3hjsg8y-kwin-5.27.10/bin/.kwin_wayland-wrapped - Mon 2024-04-15 22:31:34 PDT 393757 1000 1000 SIGSEGV missing /nix/store/8hwpp6dgndnihkg2gbwkvqllv3hjsg8y-kwin-5.27.10/bin/.kwin_wayland-wrapped - Tue 2024-04-16 09:42:25 PDT 410080 1000 1000 SIGSEGV missing /nix/store/8hwpp6dgndnihkg2gbwkvqllv3hjsg8y-kwin-5.27.10/bin/.kwin_wayland-wrapped - Fri 2024-04-19 17:57:46 PDT 461114 1000 1000 SIGSEGV missing /nix/store/8hwpp6dgndnihkg2gbwkvqllv3hjsg8y-kwin-5.27.10/bin/.kwin_wayland-wrapped - Mon 2024-04-22 17:06:28 PDT5764 1000 1000 SIGSEGV missing /nix/store/8hwpp6dgndnihkg2gbwkvqllv3hjsg8y-kwin-5.27.10/bin/.kwin_wayland-wrapped - Tue 2024-04-23 09:57:43 PDT 185495 1000 1000 SIGSEGV missing /nix/store/8hwpp6dgndnihkg2gbwkvqllv3hjsg8y-kwin-5.27.10/bin/.kwin_wayland-wrapped - Sat 2024-04-27 11:35:21 PDT 273848 1000 1000 SIGSEGV missing /nix/store/8hwpp6dgndnihkg2gbwkvqllv3hjsg8y-kwin-5.27.10/bin/.kwin_wayland-wrapped - Tue 2024-04-30 14:52:11 PDT5924 1000 1000 SIGSEGV missing /nix/store/8hwpp6dgndnihkg2gbwkvqllv3hjsg8y-kwin-5.27.10/bin/.kwin_wayland-wrapped - Mon 2024-05-06 13:22:22 PDT5623 1000 1000 SIGSEGV present /nix/store/8hwpp6dgndnihkg2gbwkvqllv3hjsg8y-kwin-5.27.10/bin/.kwin_wayland-wrapped 15.3M Mon 2024-05-06 20:06:06 PDT 211479 1000 1000 SIGSEGV present /nix/store/8hwpp6dgndnihkg2gbwkvqllv3hjsg8y-kwin-5.27.10/bin/.kwin_wayland-wrapped 16.5M Tue 2024-05-07 22:25:10 PDT 283556 1000 1000 SIGSEGV present /nix/store/8hwpp6dgndnihkg2gbwkvqllv3hjsg8y-kwin-5.27.10/bin/.kwin_wayland-wrapped 16.7M Tue 2024-05-07 22:26:29 PDT 631249 1000 1000 SIGSEGV present /nix/store/pphwrqfrkbngq394cpxv1pi98i1a54ys-kwin-5.27.11/bin/.kwin_wayland-wrapped 9.4M Tue 2024-05-07 22:32:00 PDT 634884 1000 1000 SIGSEGV present /nix/store/pphwrqfrkbngq394cpxv1pi98i1a54ys-kwin-5.27.11/bin/.kwin_wayland-wrapped 8.3M Tue 2024-05-14 19:31:29 PDT 639991 1000 1000 SIGSEGV present /nix/store/pphwrqfrkbngq394cpxv1pi98i1a54ys-kwin-5.27.11/bin/.kwin_wayland-wrapped 20.3M Tue 2024-05-14 19:32:23 PDT 1765630 1000 1000 SIGSEGV present /nix/store/pphwrqfrkbngq394cpxv1pi98i1a54ys-kwin-5.27.11/bin/.kwin_wayland-wrapped 7.8M Fri 2024-05-17 18:02:07 PDT5670 1000 1000 SIGSEGV present /nix/store/pphwrqfrkbngq394cpxv1pi98i1a54ys-kwin-5.27.11/bin/.kwin_wayland-wrapped 15.0M Sun 2024-05-19 21:32:47 PDT5714 1000 1000 SIGSEGV present /nix/store/pphwrqfrkbngq394cpxv1pi98i1a54ys-kwin-5.27.11/bin/.kwin_wayland-wrapped 13.8M Sun 2024-05-19 23:11:33 PDT 27291 1000 1000 SIGSEGV present /nix/store/pphwrqfrkbngq394cpxv1pi98i1a54ys-kwin-5.27.11/bin/.kwin_wayland-wrapped 14.1M Sun 2024-05-19 23:41:46 PDT 42049 1000 1000 SIGSEGV present /nix/store/pphwrqfrkbngq394cpxv1pi98i1a54ys-kwin-5.27.11/bin/.kwin_wayland-wrapped 12.5M Mon 2024-05-20 00:18:35 PDT 47675 1000 1000 SIGSEGV present /nix/store/pphwrqfrkbngq394cpxv1pi98i1a54ys-kwin-5.27.11/bin/.kwin_wayland-wrapped 9.4M Mon 2024-05-20 11:08:22 PDT 53705 1000 1000 SIGSEGV present /nix/store/pphwrqfrkbngq394cpxv1pi98i1a54ys-kwin-5.27.11/bin/.kwin_wayland-wrapped 11.9M Mon 2024-05-20 11:17:08 PDT 60377 1000 1000 SIGSEGV present /nix/store/pphwrqfrkbngq394cpxv1pi98i1a54ys-kwin-5.27.11/bin/.kwin_wayland-wrapped 13.5M Mon 2024-05-20 11:54:00 PDT 64847 1000 1000 SIGSEGV present /nix/store/pphwrqfrkbngq394cpxv1pi98i1a54ys-kwin-5.27.11/bin/.kwin_wayland-wrapped 16.0M Mon 2024-05-20 11:56:54 PDT 82622 1000 1000 SIGSEGV present /nix/store/pphwrqfrkbngq394cpxv1pi98i1a54ys-kwin-5.27.11/bin/.kwin_wayland-wrapped 9.9M Mon 2024-05-20 12:25:42 PDT 86677 1000 1000 SIGSEGV present /nix/store/pphwrqfrkbngq394cpxv1pi98i1a54ys-kwin-5.27.11/bin
[kwin] [Bug 480925] Crash in KeyboardInterface::sendKey
https://bugs.kde.org/show_bug.cgi?id=480925 Ryan Rix changed: What|Removed |Added CC||r...@n.rix.si --- Comment #7 from Ryan Rix --- I've been experiencing this crash for a while as well on an AMD running NixOS resulting in the same backtrace which BK lists in the journalctl output: Thread 1 (Thread 0x7fa17dac1380 (LWP 147914)): #0 0x7fa185601d60 in KWaylandServer::ClientConnection::client() const () from /nix/store/pphwrqfrkbngq394cpxv1pi98i1a54ys-kwin-5.27.11/lib/libkwin.so.5 #1 0x7fa185614b24 in KWaylandServer::KeyboardInterfacePrivate::keyboardsForClient(KWaylandServer::ClientConnection*) const () from /nix/store/pphwrqfrkbngq394cpxv1pi98i1a54ys-kwin-5.27.11/lib/libkwin.so.5 #2 0x7fa185614f79 in KWaylandServer::KeyboardInterface::sendKey(unsigned int, KWaylandServer::KeyboardKeyState, KWaylandServer::ClientConnection*) () from /nix/store/pphwrqfrkbngq394cpxv1pi98i1a54ys-kwin-5.27.11/lib/libkwin.so.5 #3 0x7fa185407401 in KWin::KeyboardInputRedirection::processKey(unsigned int, KWin::InputRedirection::KeyboardKeyState, std::chrono::duration >, KWin::InputDevice*) () from /nix/store/pphwrqfrkbngq394cpxv1pi98i1a54ys-kwin-5.27.11/lib/libkwin.so.5 #4 0x7fa183973c35 in void doActivate(QObject*, int, void**) () from /nix/store/h8jsqbn5bpci7v8gaxy7hrp2xc0s804v-qtbase-5.15.12/lib/libQt5Core.so.5 #5 0x7fa185322bfc in KWin::InputDevice::keyChanged(unsigned int, KWin::InputRedirection::KeyboardKeyState, std::chrono::duration >, KWin::InputDevice*) () from /nix/store/pphwrqfrkbngq394cpxv1pi98i1a54ys-kwin-5.27.11/lib/libkwin.so.5 #6 0x7fa1855c3405 in KWin::LibInput::Connection::processEvents() () from /nix/store/pphwrqfrkbngq394cpxv1pi98i1a54ys-kwin-5.27.11/lib/libkwin.so.5 #7 0x7fa1839684c0 in QObject::event(QEvent*) () from /nix/store/h8jsqbn5bpci7v8gaxy7hrp2xc0s804v-qtbase-5.15.12/lib/libQt5Core.so.5 #8 0x7fa18273e04e in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /nix/store/h8jsqbn5bpci7v8gaxy7hrp2xc0s804v-qtbase-5.15.12/lib/libQt5Widgets.so.5 #9 0x7fa18393c978 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /nix/store/h8jsqbn5bpci7v8gaxy7hrp2xc0s804v-qtbase-5.15.12/lib/libQt5Core.so.5 #10 0x7fa18393f9b1 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /nix/store/h8jsqbn5bpci7v8gaxy7hrp2xc0s804v-qtbase-5.15.12/lib/libQt5Core.so.5 #11 0x7fa183991ae0 in QEventDispatcherUNIX::processEvents(QFlags) () from /nix/store/h8jsqbn5bpci7v8gaxy7hrp2xc0s804v-qtbase-5.15.12/lib/libQt5Core.so.5 #12 0x0056a96d in QUnixEventDispatcherQPA::processEvents(QFlags) () #13 0x7fa18393b373 in QEventLoop::exec(QFlags) () from /nix/store/h8jsqbn5bpci7v8gaxy7hrp2xc0s804v-qtbase-5.15.12/lib/libQt5Core.so.5 #14 0x7fa183943876 in QCoreApplication::exec() () from /nix/store/h8jsqbn5bpci7v8gaxy7hrp2xc0s804v-qtbase-5.15.12/lib/libQt5Core.so.5 #15 0x0044e897 in main () I use the Bismuth tiling plugin but otherwise have a straightforward plasma configuration. it mostly happens when I am hitting an Emacs keybinding with a Ctrl modifier, but sometimes happens at random. Operating System: NixOS 23.11 KDE Plasma Version: 5.27.11 KDE Frameworks Version: 5.113.0 Qt Version: 5.15.12 Kernel Version: 6.1.90 (64-bit) Graphics Platform: Wayland Processors: 12 × AMD Ryzen 5 7640U w/ Radeon 760M Graphics Memory: 60.7 GiB of RAM Graphics Processor: AMD Radeon Graphics -- You are receiving this mail because: You are watching all bug changes.
[minuet] [Bug 487169] Available answer buttons do not register the answer.
https://bugs.kde.org/show_bug.cgi?id=487169 --- Comment #1 from Ryan --- Correction: The current video driver is nvidia. > prime-select get-current Driver configured: nvidia NVIDIA modules are loaded -- You are receiving this mail because: You are watching all bug changes.
[minuet] [Bug 487169] New: Available answer buttons do not register the answer.
https://bugs.kde.org/show_bug.cgi?id=487169 Bug ID: 487169 Summary: Available answer buttons do not register the answer. Classification: Applications Product: minuet Version: unspecified Platform: openSUSE OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: user-interface Assignee: sandroandr...@kde.org Reporter: r...@interoctiv.com Target Milestone: --- SUMMARY Clicking or tapping on any of the buttons under 'available answers' does not register the answer. STEPS TO REPRODUCE 1. Open Minuet and navigate to any of the exercises in the left navigation. 2. Click, tap, or press space to 'Play Question'. 3. Click or tap on any of the available answers. OBSERVED RESULT * Hovering over the answer button activates shading and the visualisations on the keyboard and musical staff below * Answers cannot be focused using the key (unlike the `Play Question` `Give Up`, and `Start Test` buttons) * Clicking or tapping any of the answer buttons fails to register the answer. * Ouput in the terminal shows this error when the answer button is clicked: `qrc:/ExerciseView.qml:317: TypeError: Property 'onExited' of object QQuickMouseArea(0x7fd104002830) is not a function` EXPECTED RESULT * should move focus to the answers, and to submit, just like the `Play Question`, `Give Up`, and `Start Test` buttons. * Clicking or tapping should register the answer and allow advancement to the next question. SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20240509 KDE Plasma Version: 6.0.4 KDE Frameworks Version: 6.1.0 Qt Version: 6.7.0 Kernel Version: 6.8.8-1-default (64-bit) Graphics Platform: Wayland Graphics Processor: Mesa Intel® UHD Graphics 620 ADDITIONAL INFORMATION * The answer buttons worked in the past few weeks before I last updated the operating system. Minuet may have been updated at that time. * I am also getting intermittent static noises briefly during some mouse interactions, such as moving the Minuet window and even when Minuet is not in focus. This stops when I exit Minuet. * Graphics could be an issue as I am using the proprietary Nvidia driver in a Plasma Wayland session. However, intel is currently active whereas Nvidia was in use the last time the buttons worked in Minuet. Device-1: Intel UHD Graphics 620 vendor: Hewlett-Packard driver: i915 v: kernel arch: Gen-9.5 process: Intel 14nm built: 2016-20 ports: active: DP-1,eDP-1 empty: DP-2,HDMI-A-1 bus-ID: 00:02.0 chip-ID: 8086:5917 class-ID: 0300 Device-2: NVIDIA GP108M [GeForce MX150] vendor: Hewlett-Packard driver: nvidia v: 550.78 alternate: nouveau,nvidia_drm non-free: 545.xx+ status: current (as of 2024-04; EOL~2026-12-xx) arch: Maxwell code: GMxxx process: TSMC 28nm built: 2014-2019 pcie: gen: 1 speed: 2.5 GT/s lanes: 4 link-max: gen: 3 speed: 8 GT/s bus-ID: 01:00.0 chip-ID: 10de:1d10 class-ID: 0302 Device-3: Suyin HP TrueVision FHD RGB-IR driver: uvcvideo type: USB rev: 2.0 speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 1-5:2 chip-ID: 064e:3401 class-ID: 0e02 serial: HF2066-P98B-OV07-REV0101 Display: wayland server: X.org v: 1.21.1.12 with: Xwayland v: 23.2.6 compositor: kwin_wayland driver: X: loaded: modesetting,nvidia alternate: intel dri: iris gpu: i915,nvidia d-rect: 4480x2520 display-ID: 0 Monitor-1: DP-1 pos: primary,top-left res: 2560x1440 size: N/A modes: N/A Monitor-2: eDP-1 pos: bottom-r res: 1920x1080 size: N/A modes: N/A -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 438970] All effects in timeline disabled and cannot be re-enabled after using Disable Timeline Effects and saving
https://bugs.kde.org/show_bug.cgi?id=438970 --- Comment #6 from Ryan K --- Yes, I was able to reproduce right now using 24.02.1. Disable timeline effects should either be a UI-only state that isn't saved to the file or a separate global property rather than and individual one. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 479760] Process becomes uninterruptable; requires forced reboot
https://bugs.kde.org/show_bug.cgi?id=479760 Ryan changed: What|Removed |Added Status|NEEDSINFO |RESOLVED --- Comment #4 from Ryan --- I completely forgot I filed the bug. It seems to have been an issue with my zpool set-up and my wavlink external drive. Drawing power from the wavlink hub resulted in the device transiently disconnecting. This caused zpool to stop responding and kate seemed to be worst affected by this but the problem is not a kate issue. -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 478358] Agenda items should display contents from General textbox, not just Title
https://bugs.kde.org/show_bug.cgi?id=478358 Ryan changed: What|Removed |Added CC||denu...@hotmail.com -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 484451] New: translation errors(zh_CN) in Kwin
https://bugs.kde.org/show_bug.cgi?id=484451 Bug ID: 484451 Summary: translation errors(zh_CN) in Kwin Classification: I don't know Product: kde Version: unspecified Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: spring...@outlook.com Target Milestone: --- SUMMARY In System Settings -> Keyboard -> Shortcuts -> Kwin, the Simplified Chinese translation of "Expand Window Vertically" and "Maximize Window Vertically" are both "垂直最大化窗口(Maximize Window Vertically)", and the Chinese translation of "Expand Window Horizontally" and " Maximize Window Horizontally" are both "水平最大化窗口(Maximize Window Vertically)". EXPECTED RESULT Expand Window Vertically -> 垂直扩展窗口 Maximize Window Vertically -> 垂直最大化窗口 Expand Window Horizontally -> 水平扩展窗口 Maximize Window Horizontally -> 水平最大化窗口 SOFTWARE/OS VERSIONS Linux: Arch Linux KDE Plasma Version: 6.0.2 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 483605] Pop-up Windows Resizing Themselves Automatically
https://bugs.kde.org/show_bug.cgi?id=483605 --- Comment #2 from Ryan Ronnander --- (In reply to David Edmundson from comment #1) > Can you share what scale factor you use? Sure thing, I am using 250% scale factor and "legacy applications apply scaling themselves". -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 483688] keyboard shortcuts don't work
https://bugs.kde.org/show_bug.cgi?id=483688 --- Comment #2 from Ryan --- (In reply to duha.bugs from comment #1) > What shortcut did you bind to meta+x ? Every widget in the system tray > seemed to work fine for me. System Settings -> Keyboard -> Shortcuts -> plasmashell -> Activate System Tray Widget I bind the shortcut to Meta+x, but it doesn't seem to work. This problem only appeared after I upgraded to plasma 6, before that everything was fine -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 483688] New: keyboard shortcuts don't work
https://bugs.kde.org/show_bug.cgi?id=483688 Bug ID: 483688 Summary: keyboard shortcuts don't work Classification: Plasma Product: plasmashell Version: master Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: System Tray Assignee: plasma-b...@kde.org Reporter: spring...@outlook.com CC: mate...@gmail.com Target Milestone: 1.0 SUMMARY: Keyborad shortcuts set to meta+x, but don't work when pressed SOFTWARE/OS VERSIONS: Linux/KDE Plasma: ArchLinux(kernel: 6.7.9-arch1-1) KDE Plasma Version: 6.0.2 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 483605] New: Pop-up Windows Resizing Themselves Automatically
https://bugs.kde.org/show_bug.cgi?id=483605 Bug ID: 483605 Summary: Pop-up Windows Resizing Themselves Automatically Classification: Plasma Product: kwin Version: 6.0.1 Platform: openSUSE OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: rronnan...@gmail.com Target Milestone: --- Created attachment 167205 --> https://bugs.kde.org/attachment.cgi?id=167205=edit Pop-up windows resizing themselves video SUMMARY After upgrading to 6.0.1 some application windows or pop-up windows will start dynamically resizing themselves. I've noticed this happening on 3rd party apps such as Zoom and Reaper (so far). STEPS TO REPRODUCE 1. Open application, trigger a dialog pop-up window. OBSERVED RESULT Window constantly resizes and expands. EXPECTED RESULT Window should stay statically sized. SOFTWARE/OS VERSIONS KDE Plasma Version: 6.0.1 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 410281] Falkon snap doesn't use ibus
https://bugs.kde.org/show_bug.cgi?id=410281 --- Comment #5 from Ryan Y --- I mentioned the Kate snap package because ibus *can* properly work in it, unlike in other KDE snaps I've tried. Sorry for the poorly written comments. -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 410281] Falkon snap doesn't use ibus
https://bugs.kde.org/show_bug.cgi?id=410281 --- Comment #3 from Ryan Y --- Sorry, I should've written the version number of the Kate Snap instead of the current date. It's stable 23.08.4. It's a "classic" snap package. -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 410281] Falkon snap doesn't use ibus
https://bugs.kde.org/show_bug.cgi?id=410281 Ryan Y changed: What|Removed |Added CC||ryuichi.ya...@gmail.com --- Comment #2 from Ryan Y --- Ibus does not work also on Kdenlive Snap (23.08.4) and some other KDE Snaps. I think the cause is the same. It works on Kate Snap as of now. (24-02-23) I'm using Wayland, if that helps. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 480120] New: Crash upon login
https://bugs.kde.org/show_bug.cgi?id=480120 Bug ID: 480120 Summary: Crash upon login Classification: Plasma Product: plasmashell Version: 5.27.10 Platform: FreeBSD Ports OS: FreeBSD Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: goestoli...@gmail.com CC: k...@davidedmundson.co.uk Target Milestone: 1.0 Application: plasmashell (5.27.10) Qt Version: 5.15.12 Frameworks Version: 5.113.0 Operating System: FreeBSD 13.2-STABLE arm64 Windowing System: X11 Distribution (Platform): FreeBSD Ports DrKonqi: 5.27.10 [KCrashBackend] -- Information about the crash: Curiously, I see a 'using software rendering' icon in the task bar. I have no idea if this is relevant, but I had just rebooted and logged in via lightdm (X11). The reporter is unsure if this crash is reproducible. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault (lldb) process attach --pid 58167 Process 58167 stopped * thread #1, name = 'plasmashell', stop reason = signal SIGSTOP frame #0: 0x9b13bce0 libc.so.7`__sys_wait4 + 4 libc.so.7`__sys_wait4: -> 0x9b13bce0 <+4>: svc#0 0x9b13bce4 <+8>: b.hs 0x9b13bcec; <+16> 0x9b13bce8 <+12>: ret 0x9b13bcec <+16>: b 0x9b139c40; ___lldb_unnamed_symbol4960 thread #2, name = 'plasmashell', stop reason = signal SIGSTOP frame #0: 0x9b13bbb8 libc.so.7`__sys_read + 8 libc.so.7`__sys_read: -> 0x9b13bbb8 <+8>: b.hs 0x9b13bbc0; <+16> 0x9b13bbbc <+12>: ret 0x9b13bbc0 <+16>: b 0x9b139c40; ___lldb_unnamed_symbol4960 libc.so.7`__sys_readv: 0x9b13bbc4 <+0>: movx8, #0x78 ; =120 thread #3, name = 'plasmashell', stop reason = signal SIGSTOP frame #0: 0x9b13baf0 libc.so.7`__sys_kevent + 8 libc.so.7`__sys_kevent: -> 0x9b13baf0 <+8>: b.hs 0x9b13baf8; <+16> 0x9b13baf4 <+12>: ret 0x9b13baf8 <+16>: b 0x9b139c40; ___lldb_unnamed_symbol4960 libc.so.7`__sys_msync: 0x9b13bafc <+0>: movx8, #0x41 ; =65 thread #4, name = 'plasmashell', stop reason = signal SIGSTOP frame #0: 0x9b13bb68 libc.so.7`__sys_poll + 8 libc.so.7`__sys_poll: -> 0x9b13bb68 <+8>: b.hs 0x9b13bb70; <+16> 0x9b13bb6c <+12>: ret 0x9b13bb70 <+16>: b 0x9b139c40; ___lldb_unnamed_symbol4960 libc.so.7`__sys_ppoll: 0x9b13bb74 <+0>: movx8, #0x221; =545 Executable module set to "/usr/local/bin/plasmashell". Architecture set to: aarch64-unknown-freebsd13.2. (lldb) settings set term-width 200 (lldb) thread info thread #1: tid = 100260, 0x9b13bce0 libc.so.7`__sys_wait4 + 4, name = 'plasmashell', stop reason = signal SIGSTOP (lldb) bt all * thread #1, name = 'plasmashell', stop reason = signal SIGSTOP * frame #0: 0x9b13bce0 libc.so.7`__sys_wait4 + 4 frame #1: 0xa39b4884 libthr.so.3`___lldb_unnamed_symbol721 + 72 frame #2: 0x880e0268 libKF5Crash.so.5`___lldb_unnamed_symbol226 + 304 frame #3: 0x880dfd38 libKF5Crash.so.5`KCrash::defaultCrashHandler(int) + 1124 frame #4: 0xa39b1f38 libthr.so.3`___lldb_unnamed_symbol678 + 240 frame #5: 0xa39b1678 libthr.so.3`___lldb_unnamed_symbol659 + 248 frame #6: 0xf000 frame #7: 0x8b35ebfc libQt5Quick.so.5`___lldb_unnamed_symbol14904 + 264 frame #8: 0x99cb2580 libQt5Gui.so.5`QWindow::event(QEvent*) + 576 frame #9: 0x8b3d84bc libQt5Quick.so.5`QQuickWindow::event(QEvent*) + 264 frame #10: 0x96c98544 libQt5Widgets.so.5`QApplicationPrivate::notify_helper(QObject*, QEvent*) + 300 frame #11: 0x96c9988c libQt5Widgets.so.5`QApplication::notify(QObject*, QEvent*) + 564 frame #12: 0x9d432fe0 libQt5Core.so.5`QCoreApplication::notifyInternal2(QObject*, QEvent*) + 220 frame #13: 0x99ca5168 libQt5Gui.so.5`QGuiApplicationPrivate::processExposeEvent(QWindowSystemInterfacePrivate::ExposeEvent*) + 268 frame #14: 0x99c83b74 libQt5Gui.so.5`QWindowSystemInterface::sendWindowSystemEvents(QFlags) + 264 frame #15: 0xd15b3bf4 libQt5XcbQpa.so.5`___lldb_unnamed_symbol3691 + 40 frame #16: 0xaeefa4bc libglib-2.0.so.0`___lldb_unnamed_symbol2507 + 332 frame #17: 0xaeefa890 libglib-2.0.so.0`___lldb_unnamed_symbol2508 + 560 frame #18: 0xaeefa96c libglib-2.0.so.0`g_main_context_iteration + 116 frame #19: 0x9d48cde4 libQt5Core.so.5`QEventDispatcherGlib::processEvents(QFlags) + 108 frame #20: 0x9d42f480 libQt5Core.so.5`QEventLoop::exec(QFlags) + 564 frame #21: 0x9d433780 libQt5Core.so.5`QCoreApplication::exec()
[kate] [Bug 479760] Process becomes uninterruptable; requires forced reboot
https://bugs.kde.org/show_bug.cgi?id=479760 --- Comment #1 from Ryan --- OS: Ubuntu 23.10 x86_64 Host: ASUS TUF Gaming A15 FA506IH_FA506IH 1.0 Kernel: 6.5.0-14-generic Uptime: 4 hours, 20 mins Packages: 2264 (dpkg), 70 (snap) Shell: bash 5.2.15 Resolution: 1920x1080 WM: sway Terminal: kitty CPU: AMD Ryzen 7 4800H with Radeon Graphics (16) @ 2.900GHz GPU: AMD ATI 05:00.0 Renoir GPU: NVIDIA 01:00.0 NVIDIA Corporation TU117M [NOT IN USE] Memory: 37176MiB / 39516MiB -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 479760] New: Process becomes uninterruptable; requires forced reboot
https://bugs.kde.org/show_bug.cgi?id=479760 Bug ID: 479760 Summary: Process becomes uninterruptable; requires forced reboot Classification: Applications Product: kate Version: unspecified Platform: Snap OS: Linux Status: REPORTED Severity: critical Priority: NOR Component: application Assignee: kwrite-bugs-n...@kde.org Reporter: jryan.dani...@gmail.com Target Milestone: --- SUMMARY While working with Kate, some open sessions may become frozen. Trying to kill the frozen sessions does not work. Looking at the 'properties' with system monitor shows that they are uninterruptable. Attempting to reboot/shutdown the computer does not complete. I need to hold the power button to get the computer to reboot/shutdown (I am assuming the uninterruptable kate session prevents the computer from shutting down). STEPS TO REPRODUCE 1. Open Kate, start a session from the session manager window. 2. Work. 3. Session (sometimes) freezes. OBSERVED RESULT Session becomes uninterruptable. EXPECTED RESULT No freeze or that the session can be killed if it does freeze. SOFTWARE/OS VERSIONS snap-id: AhMXNopXhzZ7XDMS9mZ2H2G40U3h3SkR tracking: latest/stable refresh-date: 18 days ago, at 22:30 CET channels: latest/stable:23.08.4 2023-12-10 (171) 276MB classic latest/candidate: 23.08.4 2023-12-09 (171) 276MB classic latest/beta: ↑ latest/edge: ↑ installed: 23.08.4(171) 276MB classic ADDITIONAL INFORMATION My home user directory is a zfs pool mounted inside the /home dir. I am accessing text files on an external drive (zpool) mounted inside my user home directory So it is a zfs pool mounted inside another zfs pool. I would guess that this may have something to do with the issue but it is a guess. I bring zfs up because in the past I have had problems shutting down when zfs would not unmount/export/whatever-it-does-at-shutdown and I could not power down. I don't know if zfs is stuck because of kate or if kate is stuck for some other reason. No other snaps /apps have produced similar issues to date. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 475864] Error on switch from yandex browser to desktop
https://bugs.kde.org/show_bug.cgi?id=475864 --- Comment #7 from Ryan --- Created attachment 164766 --> https://bugs.kde.org/attachment.cgi?id=164766=edit New crash information added by DrKonqi plasmashell (5.27.5) using Qt 5.15.8 This may not be useful System has 3 monitors (2560x1440, DVI, DP, HDMI) driven by a nvidia 1660Super. System was working as expected, then I put the system to sleep for a few hours. When I turned it back on and logged in, the plasma shell stopped responding. I cloud move the mouse, however I could not switch to any of the open applications ( Konsole, Google Chrome x3 and Visual Studio Code). sav sa After about 30 seconds the system recovered, however, my monitor setup had changed. My primary monitor is different, and all panel and widgets have moved between the 3 different monitors. The left, center and right monitor layout did not change ( I can move the mose correctly from the left to center to right montor), just the panels are now in a different montor than they were configured for. This occurs each time I resume from sleep. I've not yet tried to resume from hibernate. -- Backtrace (Reduced): #4 0x7fca4c9be3d0 in QSGAreaAllocator::deallocateInNode(QPoint const&, QSGAreaAllocatorNode*) () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #5 0x7fca4c9be446 in QSGAreaAllocator::deallocate(QRect const&) () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 [...] #10 0x7fca4ca67c09 in QQuickWindowPrivate::runAndClearJobs(QList*) () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 [...] #2 0x7fca4aad1a2b in QWaitCondition::wait(QMutex*, QDeadlineTimer) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 [...] #2 0x7fca4aad1a2b in QWaitCondition::wait(QMutex*, QDeadlineTimer) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 475864] Error on switch from yandex browser to desktop
https://bugs.kde.org/show_bug.cgi?id=475864 Ryan changed: What|Removed |Added CC||jenkinsr...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 477104] KDE Connect crashes after Bluetooth headphones power off
https://bugs.kde.org/show_bug.cgi?id=477104 --- Comment #15 from Ryan Olthof --- Kdeconnect settings, selecting my phone and disabling the system volume plugin resolved this for now. It appears that the plugin author Nicolas Fella has commented and merging a fix. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 477104] KDE Connect crashes after Bluetooth headphones power off
https://bugs.kde.org/show_bug.cgi?id=477104 Ryan Olthof changed: What|Removed |Added CC||e.oh...@burningpho3nix.xyz --- Comment #7 from Ryan Olthof --- *** Bug 475196 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 475196] KDE Connect crashes after phone disconnects
https://bugs.kde.org/show_bug.cgi?id=475196 Ryan Olthof changed: What|Removed |Added Status|REPORTED|RESOLVED CC||ryan.olt...@gmail.com Resolution|--- |DUPLICATE --- Comment #3 from Ryan Olthof --- *** This bug has been marked as a duplicate of bug 477104 *** -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 461862] KDE daemon crashes
https://bugs.kde.org/show_bug.cgi?id=461862 Ryan Olthof changed: What|Removed |Added CC||ryan.olt...@gmail.com Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE --- Comment #2 from Ryan Olthof --- *** This bug has been marked as a duplicate of bug 477104 *** -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 477104] KDE Connect crashes after Bluetooth headphones power off
https://bugs.kde.org/show_bug.cgi?id=477104 Ryan Olthof changed: What|Removed |Added CC||vanush.kamar...@gmail.com --- Comment #6 from Ryan Olthof --- *** Bug 461862 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 477104] KDE Connect crashes after Bluetooth headphones power off
https://bugs.kde.org/show_bug.cgi?id=477104 Ryan Olthof changed: What|Removed |Added CC||k...@trummer.xyz --- Comment #5 from Ryan Olthof --- *** Bug 476154 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 476154] KDE Connect crashed after disconnecting bluetooth device
https://bugs.kde.org/show_bug.cgi?id=476154 Ryan Olthof changed: What|Removed |Added Resolution|--- |DUPLICATE CC||ryan.olt...@gmail.com Status|REPORTED|RESOLVED --- Comment #4 from Ryan Olthof --- *** This bug has been marked as a duplicate of bug 477104 *** -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 477104] KDE Connect crashes after Bluetooth headphones power off
https://bugs.kde.org/show_bug.cgi?id=477104 Ryan Olthof changed: What|Removed |Added CC||bounteou...@protonmail.com --- Comment #4 from Ryan Olthof --- *** Bug 476500 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 476500] KDE connect crashes after powering off the headphones
https://bugs.kde.org/show_bug.cgi?id=476500 Ryan Olthof changed: What|Removed |Added Resolution|--- |DUPLICATE CC||ryan.olt...@gmail.com Status|REPORTED|RESOLVED --- Comment #1 from Ryan Olthof --- *** This bug has been marked as a duplicate of bug 477104 *** -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 477104] KDE Connect crashes after Bluetooth headphones power off
https://bugs.kde.org/show_bug.cgi?id=477104 Ryan Olthof changed: What|Removed |Added CC||ryan.olt...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 477104] KDE Connect crashes after Bluetooth headphones power off
https://bugs.kde.org/show_bug.cgi?id=477104 --- Comment #3 from Ryan Olthof --- Created attachment 163989 --> https://bugs.kde.org/attachment.cgi?id=163989=edit New crash information added by DrKonqi kdeconnectd (23.08.3) using Qt 5.15.11 Disconnecting bluetooth headphones results in this crash everytime. Not sure if it's related, but on Opensuse, I must run dracut -f --omit bluetooth --regenerate-all every kernel update as my laptop BT device is not recognized otherwise. -- Backtrace (Reduced): #4 0x7fd6600d1283 in PulseAudioQt::CardPrivate::update (this=, info=) at /usr/src/debug/pulseaudio-qt-1.3/src/card.cpp:72 #5 0x7fd660080e28 in context_get_card_info_callback (pd=pd@entry=0x563fc0d30ff0, command=command@entry=2, tag=tag@entry=1591, t=t@entry=0x563fc0d2d250, userdata=userdata@entry=0x563fc0d429a0) at ../src/pulse/introspect.c:990 #6 0x7fd64ffba6c1 in run_action (pd=0x563fc0d30ff0, r=0x563fc0c42e50, command=2, ts=0x563fc0d2d250) at ../src/pulsecore/pdispatch.c:291 #7 0x7fd64ffbe9ec in pa_pdispatch_run (pd=0x563fc0d30ff0, packet=packet@entry=0x563fc0d2f9d0, ancil_data=ancil_data@entry=0x563fc0d3fef8, userdata=userdata@entry=0x563fc0cca4c0) at ../src/pulsecore/pdispatch.c:344 #8 0x7fd66006f58e in pstream_packet_callback (p=, packet=0x563fc0d2f9d0, ancil_data=0x563fc0d3fef8, userdata=0x563fc0cca4c0) at ../src/pulse/context.c:364 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 469547] Weird typo in month name in tooltip
https://bugs.kde.org/show_bug.cgi?id=469547 Ryan Y changed: What|Removed |Added CC||ryuichi.ya...@gmail.com --- Comment #6 from Ryan Y --- Created attachment 163826 --> https://bugs.kde.org/attachment.cgi?id=163826=edit "Sun3ay" instead of "日曜日" I encountered a similar problem when using ja_JP locale in Plasma 6.0 Dev, but not in 5.27.29. In most of system locales I've tried, such as American English, German and French, the tooltip shows date and time in English without this glitch. As far as I know It can be observed only in ja_JP locale. Is this - https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/3606 - related? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 475421] New: Dynamic Wallpaper Plugin Broken
https://bugs.kde.org/show_bug.cgi?id=475421 Bug ID: 475421 Summary: Dynamic Wallpaper Plugin Broken Classification: Plasma Product: plasmashell Version: 5.27.8 Platform: Archlinux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Desktop Containment Assignee: plasma-b...@kde.org Reporter: rcavit...@gmail.com CC: notm...@gmail.com Target Milestone: 1.0 Created attachment 162184 --> https://bugs.kde.org/attachment.cgi?id=162184=edit Dynamic Wallpapers settings menu is blank SUMMARY *** Starting a few weeks ago, the Dynamic Wallpapers plugin seems to be totally broken. I noticed this initially when my wallpaper displayed as just a black screen, and upon attempting to reset my dynamic wallpaper to see if it'd reload I noticed that the plugin itself is broken. *** STEPS TO REPRODUCE 1. Attempt to set a dynamic wallpaper 2. Observe that the menu for it is broken. OBSERVED RESULT The settings menu for the Dynamic Wallpapers plugin is broken (blank, there's no option to select a dynamic wallpaper), and the plugin itself seems broken as the previously set wallpaper failed to display upon the breaking of the plugin. EXPECTED RESULT To be able to configure and select a dynamic wallpaper. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Archlinux KDE Plasma Version: 5.27.8 KDE Frameworks Version: 5.110.0 Qt Version: 5.15.11 ADDITIONAL INFORMATION I am running the open source version of the Nvidia kernel module, though I imagine even if that broke displaying the actual wallpapers the settings menu for it would still function? This is on X11, I have not tested on Wayland given the state of affairs that still exists between Wayland and Nvidia's drivers. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 385020] KMail2 does not wait for unlocking of KWallet
https://bugs.kde.org/show_bug.cgi?id=385020 Ryan McCoskrie changed: What|Removed |Added CC||w...@ryanmccoskrie.me Status|RESOLVED|REOPENED Resolution|WORKSFORME |--- Ever confirmed|0 |1 --- Comment #5 from Ryan McCoskrie --- This bug is happening on my laptop in 2023, desktop is fine. Both are using Fedora. Any hints on how I can collect relevant information? -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 425562] Edit Identity > Help Button = Wrong URL
https://bugs.kde.org/show_bug.cgi?id=425562 Ryan Y changed: What|Removed |Added CC||ryuichi.ya...@gmail.com Alias|Button, Help, Identity | -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kcoreaddons] [Bug 387663] Dolphin doesn't update view (doesn't show new files)
https://bugs.kde.org/show_bug.cgi?id=387663 Ryan E changed: What|Removed |Added CC||eskridger...@gmail.com --- Comment #86 from Ryan E --- I am getting this bug while using Dolphin to access a networked and password-protected SMB drive. The following steps recreate the bug for me 100% of the time: 1. Auto-mount SMB drive to /media/ by adding the following string to /etc/fstab : /// /media/ cifs credentials=path/to/.smbcredentials, uid=1000, gid=1000, iocharset=uft8 0 0 2. Reboot. 3. Right click pinned Dolphin icon on the KDE Task Manager. Click "Open New Window". 4. Navigate to /media/ 5. Open a second instance of Dolphin using the pinned icon on the KDE Task Manager. 6. Navigate to smb:/// 7. Enter credentials. 8. Right-click in the instance pointing to the SMB file path and create hello.txt 9. See that the Dolphin instance pointing to /media/ does not reflect changes. 10. Press F5 to refresh and can now see hello.txt The reverse is not true. If I create a file in the instance pointing to /media/, that file is immediately shown in the file pointing to the SMB address. Everything stated above also applies to directories. It also occurs when using tabs and split views. System information: Operating System: Kubuntu 22.04 KDE Plasma Version: 5.24.7 KDE Frameworks Version: 5.92.0 Qt Version: 5.15.3 Kernel Version: 6.2.0-26-generic (64-bit) Graphics Platform: X11 Processors: 4 × Intel® Core™ i7-5600U CPU @ 2.60GHz Memory: 15.5 GiB of RAM Graphics Processor: Mesa Intel® HD Graphics 5500 Manufacturer: Dell Product Name: Latitude E7450 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 471294] Pan tool shortcuts not working
https://bugs.kde.org/show_bug.cgi?id=471294 --- Comment #12 from Ryan --- (In reply to Dmitry Kazakov from comment #9) > Hi, Ryan! > > By "recording" I meant not "recording of your fingers", but recording of > your screen (via, e.g., OBS Studio) :) You can actually also summon the > on-screen-keyboard so we could see what keys are pressed at the moment. That > is needed so we could see how Krita reacts to your shortcuts and what > actually happens. > > It might also be a good idea to reset your Krita configurations. Try to move > these files/folders into some safe space: > > %LOCALAPPDATA%\kritarc > %APPDATA%\krita\input > > There used to be some bugs that could cause clashes with shortcuts during > some of updates of Krita It was a fresh install of Krita from Microsoft App Store. Yeah, I paid for the store version bc I like the software. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 471294] Pan tool shortcuts not working
https://bugs.kde.org/show_bug.cgi?id=471294 --- Comment #11 from Ryan --- (In reply to Dmitry Kazakov from comment #9) > Hi, Ryan! > > By "recording" I meant not "recording of your fingers", but recording of > your screen (via, e.g., OBS Studio) :) You can actually also summon the > on-screen-keyboard so we could see what keys are pressed at the moment. That > is needed so we could see how Krita reacts to your shortcuts and what > actually happens. > > It might also be a good idea to reset your Krita configurations. Try to move > these files/folders into some safe space: > > %LOCALAPPDATA%\kritarc > %APPDATA%\krita\input > > There used to be some bugs that could cause clashes with shortcuts during > some of updates of Krita No offense, but how is a screen recording supposed to show anything when the keyboard shortcuts do not work and are not visible? You're just going to be staring at a fixed frame the entire video and/or listening to me gripe. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 472576] Wily Beast and Weakest Creature's (Touhou 17's) icon being assigned to random windows.
https://bugs.kde.org/show_bug.cgi?id=472576 --- Comment #5 from Ryan --- (In reply to Fushan Wen from comment #4) > Can you post the content of 'Touhou Kikeijuu ~ Wily Beast and Weakest > Creature..desktop' in that folder? [Desktop Entry] Name=Touhou Kikeijuu ~ Wily Beast and Weakest Creature. Comment=Play this game on Steam Exec=steam steam://rungameid/1079160 Icon=steam_icon_1079160 Terminal=false Type=Application Categories=Game; -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 472576] Wily Beast and Weakest Creature's (Touhou 17's) icon being assigned to random windows.
https://bugs.kde.org/show_bug.cgi?id=472576 --- Comment #3 from Ryan --- (In reply to Fushan Wen from comment #1) > Can you run `ls -al ~/.local/share/applications` and post the output here ``` total 62 drwxr-xr-x 3 ryan ryan 8192 Jul 11 13:25 . drwxr-xr-x 70 ryan ryan 3452 Jul 24 09:47 .. -rwxr-xr-x 1 ryan ryan 175 May 26 20:01 'Borderlands 3.desktop' -rwxr-xr-x 1 ryan ryan 580 Mar 15 19:28 'cxmenu-cxoffice-f49ef4ef-9b84-4e2f-8ee8-841053c8ed14-0nlqhb8-Database Compare.desktop' -rwxr-xr-x 1 ryan ryan 616 Mar 15 19:28 'cxmenu-cxoffice-f49ef4ef-9b84-4e2f-8ee8-841053c8ed14-0nlqhb8-Office Language Preferences.desktop' -rwxr-xr-x 1 ryan ryan 622 Mar 15 19:28 'cxmenu-cxoffice-f49ef4ef-9b84-4e2f-8ee8-841053c8ed14-0nlqhb8-Office Upload Center.desktop' -rwxr-xr-x 1 ryan ryan 642 Mar 15 19:28 'cxmenu-cxoffice-f49ef4ef-9b84-4e2f-8ee8-841053c8ed14-0nlqhb8-Skype for Business Recording Manager.desktop' -rwxr-xr-x 1 ryan ryan 585 Mar 15 19:28 'cxmenu-cxoffice-f49ef4ef-9b84-4e2f-8ee8-841053c8ed14-0nlqhb8-Spreadsheet Compare.desktop' -rwxr-xr-x 1 ryan ryan 666 Mar 15 19:28 'cxmenu-cxoffice-f49ef4ef-9b84-4e2f-8ee8-841053c8ed14-0nlqhb8-Telemetry Dashboard for Office.desktop' -rwxr-xr-x 1 ryan ryan 687 Mar 15 19:28 'cxmenu-cxoffice-f49ef4ef-9b84-4e2f-8ee8-841053c8ed14-0nlqhb8-Telemetry Log for Office.desktop' -rwxr-xr-x 1 ryan ryan 548 Mar 15 19:28 cxmenu-cxoffice-f49ef4ef-9b84-4e2f-8ee8-841053c8ed14-3ii0rqp-Access.desktop -rwxr-xr-x 1 ryan ryan 556 Mar 15 19:28 cxmenu-cxoffice-f49ef4ef-9b84-4e2f-8ee8-841053c8ed14-3ii0rqp-Excel.desktop -rwxr-xr-x 1 ryan ryan 615 Mar 15 19:28 'cxmenu-cxoffice-f49ef4ef-9b84-4e2f-8ee8-841053c8ed14-3ii0rqp-Microsoft OneDrive.desktop' -rwxr-xr-x 1 ryan ryan 554 Mar 15 19:28 'cxmenu-cxoffice-f49ef4ef-9b84-4e2f-8ee8-841053c8ed14-3ii0rqp-OneNote 2016.desktop' -rwxr-xr-x 1 ryan ryan 551 Mar 15 19:28 cxmenu-cxoffice-f49ef4ef-9b84-4e2f-8ee8-841053c8ed14-3ii0rqp-Outlook.desktop -rwxr-xr-x 1 ryan ryan 574 Mar 15 19:28 cxmenu-cxoffice-f49ef4ef-9b84-4e2f-8ee8-841053c8ed14-3ii0rqp-PowerPoint.desktop -rwxr-xr-x 1 ryan ryan 558 Mar 15 19:28 cxmenu-cxoffice-f49ef4ef-9b84-4e2f-8ee8-841053c8ed14-3ii0rqp-Publisher.desktop -rwxr-xr-x 1 ryan ryan 605 Mar 15 19:28 'cxmenu-cxoffice-f49ef4ef-9b84-4e2f-8ee8-841053c8ed14-3ii0rqp-Skype for Business.desktop' -rwxr-xr-x 1 ryan ryan 567 Mar 15 19:28 cxmenu-cxoffice-f49ef4ef-9b84-4e2f-8ee8-841053c8ed14-3ii0rqp-Word.desktop -rwxr-xr-x 1 ryan ryan 174 May 20 08:22 'Dead Space.desktop' -rwxr-xr-x 1 ryan ryan 175 Apr 15 20:26 'Evolution RTS.desktop' -rwxr-xr-x 1 ryan ryan 175 May 1 16:55 'Factorio Demo.desktop' -rwxr-xr-x 1 ryan ryan 171 Feb 17 20:47 Frostpunk.desktop -rw-r--r-- 1 ryan ryan 340 Apr 5 21:22 iDrive-Test.desktop -rwxr-xr-x 1 ryan ryan 170 Apr 5 17:41 'Just Cause 2.desktop' -rwxr-xr-x 1 ryan ryan 174 Mar 24 15:53 'Just Cause 3.desktop' -rwxr-xr-x 1 ryan ryan 182 Mar 30 17:08 'Kerbal Space Program.desktop' -rw-r--r-- 1 ryan ryan 1040 Apr 23 07:22 mimeinfo.cache -rw-r--r-- 1 ryan ryan 479 Jul 3 18:33 ModOrganizer-steamtinkerlaunch-dl.desktop-off -rw-r--r-- 1 ryan ryan 486 Jul 3 18:27 ModOrganizer-steamtinkerlaunch-dl.desktop-old -rwxr-xr-x 1 ryan ryan 174 Apr 5 18:10 'Pathologic 2.desktop' -rwxr-xr-x 1 ryan ryan 163 Apr 15 20:07 'Quake II RTX.desktop' -rwxr-xr-x 1 ryan ryan 168 Jun 9 20:33 'RAGE 2.desktop' -rwxr-xr-x 1 ryan ryan 162 Jun 9 20:33 RAGE.desktop -rwxr-xr-x 1 ryan ryan 174 Apr 5 18:10 'Rebel Galaxy.desktop' -rwxr-xr-x 1 ryan ryan 173 May 1 20:39 Retrowave.desktop -rwxr-xr-x 1 ryan ryan 178 Jul 1 20:23 'SONG OF HORROR.desktop' -rwxr-xr-x 1 ryan ryan 174 Apr 5 18:43 'Space Colony.desktop' -rwxr-xr-x 1 ryan ryan 191 Apr 29 15:36 'S.T.A.L.K.E.R. Call of Pripyat.desktop' -rwxr-xr-x 1 ryan ryan 185 Apr 29 15:36 'S.T.A.L.K.E.R. Clear Sky.desktop' -rwxr-xr-x 1 ryan ryan 193 Apr 29 15:37 'S.T.A.L.K.E.R. Shadow of Chernobyl.desktop' -rwxr-xr-x 1 ryan ryan 180 May 29 11:32 'Starpoint Gemini 2.desktop' -rwxr-xr-x 1 ryan ryan 214 Jul 11 13:25 'Touhou Kikeijuu ~ Wily Beast and Weakest Creature..desktop' -rw--- 1 ryan ryan 8168 Apr 24 20:35 vivaldi-stable.desktop -rw-r--r-- 1 ryan ryan 517 Jul 3 18:36 vortex-steamtinkerlaunch-dl.desktop drwxr-xr-x 3 ryan ryan 3452 Jul 3 17:29 wine -rw-r--r-- 1 ryan ryan 202 Apr 23 07:22 wine-extension-chm.desktop -rw-r--r-- 1 ryan ryan 209 Apr 23 07:22 wine-extension-gif.desktop -rw-r--r-- 1 ryan ryan 204 Apr 23 07:22 wine-extension-hlp.desktop -rw-r--r-- 1 ryan ryan 202 Apr 23 07:22 wine-extension-htm.desktop -rw-r--r-- 1 ryan ryan 216 Apr 23 07:22 wine-extension-ini.desktop -rw-r--r-- 1 ryan ryan 212 Apr 23 07:22 wine-extension-jfif.desktop -rw-r--r-- 1 ryan ryan 211 Apr 23 07:22 wine-extension-jpe.desktop -rw-r--r-- 1 ryan ryan 225 Apr 23 07:22 wine-extension-msp.desktop -rw-r--r-- 1 ryan ryan 207 Apr 23 07:22 wine-extension-pdf.desktop -rw-r--r-- 1 ryan ryan 209 Apr 23 07:22 w
[plasmashell] [Bug 472576] Wily Beast and Weakest Creature's (Touhou 17's) icon being assigned to random windows.
https://bugs.kde.org/show_bug.cgi?id=472576 --- Comment #2 from Ryan --- Nvidia and Wayland are not on speaking terms right now, so I can't confirm this on Wayland currently. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 472576] New: Wily Beast and Weakest Creature's (Touhou 17's) icon being assigned to random windows.
https://bugs.kde.org/show_bug.cgi?id=472576 Bug ID: 472576 Summary: Wily Beast and Weakest Creature's (Touhou 17's) icon being assigned to random windows. Classification: I don't know Product: kde Version: unspecified Platform: Archlinux OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: rcavit...@gmail.com Target Milestone: --- Created attachment 160501 --> https://bugs.kde.org/attachment.cgi?id=160501=edit That isn't Touhou! SUMMARY *** So I've noticed this on both my main PC and my Steam Deck, but when Touhou 17 is installed and an application does not have its own icon, it will be assigned Touhou 17's icon instead rather than a generic X.org icon. *** STEPS TO REPRODUCE 1. Own Touhou 17 via Steam and have it installed. 2. Open a window which does not have its own icon? I can reproduce this reliably by using a Chromium-based web browser to pop out a video in a floating window (see attachment). OBSERVED RESULT It's all Touhou EXPECTED RESULT Generic X.org icon assigned to windows. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Archlinux KDE Plasma Version: 5.27.6 KDE Frameworks Version: 5.108.0 Qt Version: 5.15.10 ADDITIONAL INFORMATION As given away above, this does happen on X11, I will test on Wayland too and see if the behavior is the same. I will edit this bug report (if possible) or add a comment with the results of that. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 472120] Move tool reverts previous transform operation
https://bugs.kde.org/show_bug.cgi?id=472120 Ryan changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 472120] Move tool reverts previous transform operation
https://bugs.kde.org/show_bug.cgi?id=472120 --- Comment #11 from Ryan --- Created attachment 160442 --> https://bugs.kde.org/attachment.cgi?id=160442=edit performance settings All my settings are standard except for key bindings set to photoshop. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 472120] Move tool reverts previous transform operation
https://bugs.kde.org/show_bug.cgi?id=472120 --- Comment #8 from Ryan --- Created attachment 160327 --> https://bugs.kde.org/attachment.cgi?id=160327=edit full screen reproduction all transform tool modes -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 472120] Move tool reverts previous transform operation
https://bugs.kde.org/show_bug.cgi?id=472120 --- Comment #7 from Ryan --- Sure. I didn't think to try those options. It seems to happen consistently if I have it set to Accurate with Instant Preview. If I set it to the other 2 options then it doesn't happen. I have recorded all options and used undo between each one. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 472120] Move tool reverts previous transform operation
https://bugs.kde.org/show_bug.cgi?id=472120 --- Comment #3 from Ryan --- I reproduced it on latest master (splash screen says 5.2.0 prealpha). Once I did this enough times on enough layers it just started happening almost every time. (around 30 times on 40+ layers) -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 472120] Move tool reverts previous transform operation
https://bugs.kde.org/show_bug.cgi?id=472120 --- Comment #2 from Ryan --- Note: I have built krita from the latest master branch locally and I have sofar been unable to reproduce this problem. does anyone know if it was addressed intentionally as a fix recently? I will keep this posted, if I don't then I haven't been able to reproduce it as I use the latest version daily. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 472120] Move tool reverts previous transform operation
https://bugs.kde.org/show_bug.cgi?id=472120 --- Comment #1 from Ryan --- Created attachment 160219 --> https://bugs.kde.org/attachment.cgi?id=160219=edit reproduction steps instead of reduction by 50% this video increases the size of the truck layer. on the instant the canvas is clicked with the move tool, it reverts its size to before it was transformed. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 472120] Move tool reverts previous transform operation
https://bugs.kde.org/show_bug.cgi?id=472120 Ryan changed: What|Removed |Added CC||rocif...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 472120] New: Move tool reverts previous transform operation
https://bugs.kde.org/show_bug.cgi?id=472120 Bug ID: 472120 Summary: Move tool reverts previous transform operation Classification: Applications Product: krita Version: 5.1.4 Platform: Other OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: Tools/Move Assignee: krita-bugs-n...@kde.org Reporter: rocif...@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. Paste an image as a new layer into a blank document 2. Ctrl+T free transform the layer, drag the corner to resize it to roughly 50% smaller in width and height. Press enter to commit the transform. Optional: wait for the progress bar in the layers window to finish (this does not significantly affect the reproduction steps). 3. Press keyboard shortcut for move tool (V in photoshop hotkeys) and drag the layer to move it OBSERVED RESULT At least 50% of the time the pixels in the layer revert to before step 2 was committed, the layer is the original size. It can be observed in many ways that this is real pixel data and not a rendering artifact. I cannot find any surefire way to reproduce this every time, but if the keyboard shortcuts are used quickly then it (frustratingly) happens almost every time. EXPECTED RESULT The layer should move with the mouse and the previous transform should have been permanent, ie. the layer should remain around 50% of the original size and not resize at all when moved. SOFTWARE/OS VERSIONS Windows: 10 Mac OSX ADDITIONAL INFORMATION The behaviour is consistent between windows and mac (multiple os versions) -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 471294] Pan tool shortcuts not working
https://bugs.kde.org/show_bug.cgi?id=471294 --- Comment #6 from Ryan --- A video recording of a keyboard shortcut not working? I can give you logs if you tell me what to give you. You can't just trust that I know when my finger is typing? I have a WPM of over 100, and a computer science degree, and have been using programs since 1997. I think I know when a keyboard shortcut isn't working. Especially when other keyboard shortcuts are working in the same program. I had a problem with another software like this, due to AMD Software Adrenalin Edition capturing the key combinations, however those shortcuts have been disabled in AMD Software, and the other application now responds appropriately. I don't have any other applications that capture keyboard input running in the background. <https://www.avast.com/sig-email?utm_medium=email_source=link_campaign=sig-email_content=webmail> Virus-free.www.avast.com <https://www.avast.com/sig-email?utm_medium=email_source=link_campaign=sig-email_content=webmail> <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2> On Thu, Jun 22, 2023 at 9:47 AM Dmitry Kazakov wrote: > https://bugs.kde.org/show_bug.cgi?id=471294 > > Dmitry Kazakov changed: > >What|Removed |Added > > > Resolution|--- |WAITINGFORINFO > CC||dimul...@gmail.com > Status|REPORTED|NEEDSINFO > > --- Comment #5 from Dmitry Kazakov --- > Hi, Ryan! > > Could you please make a video recording of the problem? I cannot reproduce > it > here. > > It would also be helpful if you could try the nightly build of Krita from > here: > > https://binary-factory.kde.org/job/Krita_Nightly_Windows_Build/lastSuccessfulBuild/artifact/krita-nightly-x64-5.2.0-prealpha-6d578e3bbb.zip > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 471294] Pan tool shortcuts not working
https://bugs.kde.org/show_bug.cgi?id=471294 --- Comment #2 from Ryan --- 1. I didn't change anything. 2. It is in fact set to those things. 3. There are more bugs than just this with the shortcuts. Zoom doesn't work either. Using the Zoom tool itself is also bugged: it only zooms in, never out. I have to set the Zoom factor in the bottom right control in the window. Ryan Johnson | My Profile<https://linkr.bio/AMDphreak> | GSO<https://www.germantownsymphony.org> member, FSF, EFF supporter From: sh_zam Sent: Wednesday, June 21, 2023 8:45 AM To: rj.amdphr...@gmail.com Subject: [krita] [Bug 471294] Pan tool shortcuts not working https://bugs.kde.org/show_bug.cgi?id=471294 sh_zam changed: What|Removed |Added Keywords||triaged CC||sh...@sdf.org Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO --- Comment #1 from sh_zam --- Hi! Can you check if the Canvas Input Profile (Settings -> Configure Krita) has these shortcut assigned to Pan Canvas action (check if you are using Krita Default profile/or something else that you made yourself). If it is assigned, and it still doesn't work, can you please share the file in C:\Users\\AppData\Roaming\krita\input corresponding to the profile name that is active. -- You are receiving this mail because: You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 471295] Zoom tool zooms in while zoom out is selected
https://bugs.kde.org/show_bug.cgi?id=471295 --- Comment #1 from Ryan --- Windows 11 stable -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 471295] New: Zoom tool zooms in while zoom out is selected
https://bugs.kde.org/show_bug.cgi?id=471295 Bug ID: 471295 Summary: Zoom tool zooms in while zoom out is selected Classification: Applications Product: krita Version: 5.1.5 Platform: Compiled Sources OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: Tools Assignee: krita-bugs-n...@kde.org Reporter: rj.amdphr...@gmail.com Target Milestone: --- SUMMARY Zoom tool always zooms in, even when Ctrl is held. The mouse cursor changes to a minus sign, but the tool still zooms in, instead of zooming out. STEPS TO REPRODUCE 1. Open Krita 2. 3. OBSERVED RESULT Zoom in EXPECTED RESULT Zoom out. 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 471294] New: Pan tool shortcuts not working
https://bugs.kde.org/show_bug.cgi?id=471294 Bug ID: 471294 Summary: Pan tool shortcuts not working Classification: Applications Product: krita Version: 5.1.5 Platform: Compiled Sources OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: Tools Assignee: krita-bugs-n...@kde.org Reporter: rj.amdphr...@gmail.com Target Milestone: --- SUMMARY Pan tool does not work via its default shortcuts (Space + leftclick, and middleclick). STEPS TO REPRODUCE 1. Open Krita 2. Open big document 3. Try to navigate. OBSERVED RESULT The mouse cursor does not change from the currently-selected tool EXPECTED RESULT Mouse cursor changes, and can pan. SOFTWARE/OS VERSIONS Windows: 11 Stable ADDITIONAL INFORMATION Installed via Microsoft Windows Store -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 469160] kscreen-doctor segmentation faults in KIconLoader::~KIconLoader() when exiting
https://bugs.kde.org/show_bug.cgi?id=469160 --- Comment #4 from Ryan Rix --- ``` ~ $ KSCREEN_BACKEND=QScreen kscreen-doctor --json | jq .outputs[0].name kscreen.qscreen: Screen added QScreen(0x12e4010, name="DSI-1") "DSI-1" warning: queue 0x12f48e0 destroyed while proxies still attached: wl_display@1 still attached "DSI-1" ~ $ KSCREEN_BACKEND=KWayland kscreen-doctor --json | jq .outputs[0].name warning: queue 0x1bc6880 destroyed while proxies still attached: wl_display@1 still attached corrupted double-linked list parse error: Invalid numeric literal at line 1, column 8 ``` seems like the issue is specific to the KWayland backend, i feel like our backtraces are maybe a red herring? -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 469160] kscreen-doctor segmentation faults in KIconLoader::~KIconLoader() when exiting
https://bugs.kde.org/show_bug.cgi?id=469160 Ryan Rix changed: What|Removed |Added CC||r...@n.rix.si --- Comment #3 from Ryan Rix --- This only happens when I am running kwin_wayland -- kwin_x11 does not exhibit this issue. in my case it's slightly different behavior but only occurs on kwin_wayland: ``` ~ $ kscreen-doctor --json warning: queue 0x1aec2f0 destroyed while proxies still attached: wl_display@1 still attached corrupted size vs. prev_size in fastbins aborted (core dumped) ``` Thread 1 (Thread 0x73cff880 (LWP 3617698) ".kscreen-doctor"): #0 0x76e21adc in __pthread_kill_implementation () from /nix/store/yaz7pyf0ah88g2v505l38n0f3wg2vzdj-glibc-2.37-8/lib/libc.so.6 #1 0x76dd2cb6 in raise () from /nix/store/yaz7pyf0ah88g2v505l38n0f3wg2vzdj-glibc-2.37-8/lib/libc.so.6 #2 0x76dbc8ba in abort () from /nix/store/yaz7pyf0ah88g2v505l38n0f3wg2vzdj-glibc-2.37-8/lib/libc.so.6 #3 0x76dbd5f5 in __libc_message.cold () from /nix/store/yaz7pyf0ah88g2v505l38n0f3wg2vzdj-glibc-2.37-8/lib/libc.so.6 #4 0x76e2b785 in malloc_printerr () from /nix/store/yaz7pyf0ah88g2v505l38n0f3wg2vzdj-glibc-2.37-8/lib/libc.so.6 #5 0x76e2c04e in unlink_chunk.constprop () from /nix/store/yaz7pyf0ah88g2v505l38n0f3wg2vzdj-glibc-2.37-8/lib/libc.so.6 #6 0x76e2d6cb in _int_free () from /nix/store/yaz7pyf0ah88g2v505l38n0f3wg2vzdj-glibc-2.37-8/lib/libc.so.6 #7 0x76e2fe83 in free () from /nix/store/yaz7pyf0ah88g2v505l38n0f3wg2vzdj-glibc-2.37-8/lib/libc.so.6 #8 0x7fffe4a2a3c3 in KIconTheme::~KIconTheme() () from /nix/store/d57as4xqqimmrisfn48nwx81hh7851ck-kiconthemes-5.106.0/lib/libKF5IconThemes.so.5 #9 0x7fffe4a22e7a in KIconLoaderPrivate::clear() () from /nix/store/d57as4xqqimmrisfn48nwx81hh7851ck-kiconthemes-5.106.0/lib/libKF5IconThemes.so.5 #10 0x7fffe4a2312e in KIconLoaderPrivate::~KIconLoaderPrivate() () from /nix/store/d57as4xqqimmrisfn48nwx81hh7851ck-kiconthemes-5.106.0/lib/libKF5IconThemes.so.5 #11 0x7fffe4a23398 in KIconLoader::~KIconLoader() () from /nix/store/d57as4xqqimmrisfn48nwx81hh7851ck-kiconthemes-5.106.0/lib/libKF5IconThemes.so.5 #12 0x7fffe4a233e9 in (anonymous namespace)::Q_QGS_globalIconLoader::innerFunction()::Holder::~Holder() () from /nix/store/d57as4xqqimmrisfn48nwx81hh7851ck-kiconthemes-5.106.0/lib/libKF5IconThemes.so.5 #13 0x76dd5285 in __run_exit_handlers () from /nix/store/yaz7pyf0ah88g2v505l38n0f3wg2vzdj-glibc-2.37-8/lib/libc.so.6 #14 0x76dd53be in exit () from /nix/store/yaz7pyf0ah88g2v505l38n0f3wg2vzdj-glibc-2.37-8/lib/libc.so.6 #15 0x76dbdad5 in __libc_start_call_main () from /nix/store/yaz7pyf0ah88g2v505l38n0f3wg2vzdj-glibc-2.37-8/lib/libc.so.6 #16 0x76dbdb89 in __libc_start_main_impl () from /nix/store/yaz7pyf0ah88g2v505l38n0f3wg2vzdj-glibc-2.37-8/lib/libc.so.6 #17 0x00406165 in _start () Operating System: NixOS 23.11 KDE Plasma Version: 5.27.5 KDE Frameworks Version: 5.106.0 Qt Version: 5.15.9 Kernel Version: 6.1.30 (64-bit) Graphics Platform: Wayland Processors: 8 × Intel® Core™ i7-7700K CPU @ 4.20GHz Memory: 62.7 GiB of RAM Graphics Processor: Mesa Intel® HD Graphics 630 -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 469462] No drag and drop to the timeline on Fedora 38 with Appimage
https://bugs.kde.org/show_bug.cgi?id=469462 --- Comment #4 from Ryan Hadley --- (In reply to emohr from comment #3) > Can you test the following. Select a clip in the project bin. Hit “v”. This > should insert the clip into the timeline. Yes, Pressing V does insert clips onto the timeline. I've also noticed I cannot drag an effect onto a video clip in the timeline either -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 466054] Integrate input method panel into system tray
https://bugs.kde.org/show_bug.cgi?id=466054 --- Comment #7 from Ryan Y --- OK, thank you two for looking into this bug report. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 469462] No drag and drop to the timeline on Fedora 38 with Appimage
https://bugs.kde.org/show_bug.cgi?id=469462 Ryan Hadley changed: What|Removed |Added CC||hadley8...@gmail.com --- Comment #2 from Ryan Hadley --- Im having the same issue Using Ubuntu 23.04 on X11 The latest version from the package manager in ubuntu (Installed via snap) Happy to provide more info if needed, Just thought Id put some more activity on this bug -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 469884] snap fails to start
https://bugs.kde.org/show_bug.cgi?id=469884 --- Comment #1 from Ryan --- When I run '''snap revert kate''', kate works again. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 469884] New: snap fails to start
https://bugs.kde.org/show_bug.cgi?id=469884 Bug ID: 469884 Summary: snap fails to start Classification: Applications Product: kate Version: 23.04.1 Platform: Snap OS: Linux Status: REPORTED Severity: critical Priority: NOR Component: application Assignee: kwrite-bugs-n...@kde.org Reporter: jryan.dani...@gmail.com Target Milestone: --- SUMMARY *** Start kate via terminal, nothing happens. Yesterday before the snap was automatically refreshed, kate worked. Today, it doesn't. *** STEPS TO REPRODUCE 1. Start kate via terminal OBSERVED RESULT Nothing happens. There is nothing printed to the terminal either. EXPECTED RESULT Kate starts. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Ubuntu Sway 22.10 x86_64 , 5.19.0-42-generic kernel (available in About System) ADDITIONAL INFORMATION I was on 23.04.0 yesterday and it worked. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 469858] New: Classic and confined snap don't use the same 'hidden' files
https://bugs.kde.org/show_bug.cgi?id=469858 Bug ID: 469858 Summary: Classic and confined snap don't use the same 'hidden' files Classification: Applications Product: kate Version: 23.04.0 Platform: Snap OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: sessions Assignee: kwrite-bugs-n...@kde.org Reporter: jryan.dani...@gmail.com Target Milestone: --- SUMMARY *** I have moved from the confined snap to the classic snap. The keyboard shortcuts, external tools and sessions have reverted to a set-up from several months ago. I guess because the classic snap is not reading the information from the same place the confined snap was saving info to. *** STEPS TO REPRODUCE 1. ''' sudo snap refresh kate --classic''' 2. open kate via the terminal. OBSERVED RESULT The presented session information is from several months ago (when I refreshed to the confined snap). The external tools listed and the keyboard shortcuts appear to have reverted to that of several months ago as well. EXPECTED RESULT Kate initiates with the settings I was using most recently (i.e. before I refreshed to the classic snap). SOFTWARE/OS VERSIONS Linux/KDE Plasma: Ubuntu Sway 22.10 x86_64, 5.19.0-42-generic kernel (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.
[neon] [Bug 467993] konsole cannot run other apps
https://bugs.kde.org/show_bug.cgi?id=467993 --- Comment #4 from Ryan --- (In reply to Scarlett Moore from comment #3) > Can you please update to the recent release 23.04.0 and see if the issue > still exists. It will need the --classic flag to install. > Thanks > Scarlett Hello I apologise for replying so late. Yes, with the --classic flag kate can run external programs. My external tools and the spelling checker are working again. Thank you for the help! -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kxmlgui] [Bug 468576] Middle-clicking various things (certain Panel widgets, KWin-drawn titlebars) crashes the app being middle-clicked in KCheckAccelerators::eventFilter()
https://bugs.kde.org/show_bug.cgi?id=468576 --- Comment #8 from Ryan Y --- Does this mean the fix has already been merged? That's awesome. Thank you, Nate and David! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 468576] Middle-clicking certain widgets in a panel crashes plasmashell
https://bugs.kde.org/show_bug.cgi?id=468576 --- Comment #4 from Ryan Y --- I'm not a professional but it looks like the same issue. #0 QRect::width (this=) at kernel/qwidget.h:860 #1 QWidget::rect (this=0x5616e95b60d0) at kernel/qwidget.h:860 #2 QWidgetPrivate::pointInsideRectAndMask (p=..., this=0x5616e95b1f80) at ../../include/QtWidgets/5.15.8/QtWidgets/private/../../../../../src/widgets/kernel/qwidget_p.h:840 #3 QWidgetPrivate::childAt_helper (this=0x5616e95b1f80, p=..., ignoreChildrenInDestructor=ignoreChildrenInDestructor@entry=false) at kernel/qwidget.cpp:10176 #4 0x7fd1a09dc97f in QWidget::childAt (this=this@entry=0x5616e95b60d0, p=...) at kernel/qwidget.cpp:10168 #5 0x7fd1a01a99a9 in KCheckAccelerators::eventFilter (this=0x5616e84030b0, obj=0x5616e95b60d0, e=0x7ffec66dd250) at /usr/src/debug/kf5-kxmlgui-5.104.0-1.fc37.x86_64/src/kcheckaccelerators.cpp:174 #6 0x7fd1a129d1d1 in QCoreApplicationPrivate::sendThroughApplicationEventFilters (this=this@entry=0x5616e81f4cb0, receiver=receiver@entry=0x5616e95b60d0, event=event@entry=0x7ffec66dd250) at kernel/qcoreapplication.cpp:1172 #7 0x7fd1a09aeda0 in QApplicationPrivate::notify_helper (this=0x5616e81f4cb0, receiver=0x5616e95b60d0, e=0x7ffec66dd250) at kernel/qapplication.cpp:3611 #8 0x7fd1a129d4e8 in QCoreApplication::notifyInternal2 (receiver=0x5616e95b60d0, event=0x7ffec66dd250) at kernel/qcoreapplication.cpp:1064 #9 0x7fd1a129d6d2 in QCoreApplication::sendEvent (receiver=, event=) at kernel/qcoreapplication.cpp:1462 #10 0x7fd1a29f42ff in KDecoration2::Decoration::mousePressEvent (this=, event=0x7ffec66dd250) at /usr/src/debug/kdecoration-5.27.4-1.fc37.x86_64/src/decoration.cpp:365 #11 0x7fd1a29f1b07 in KDecoration2::Decoration::event (this=, event=) at /usr/src/debug/kdecoration-5.27.4-1.fc37.x86_64/src/decoration.cpp:294 #12 0x7fd1a09aed62 in QApplicationPrivate::notify_helper (this=, receiver=0x5616e9587240, e=0x7ffec66dd250) at kernel/qapplication.cpp:3640 #13 0x7fd1a129d4e8 in QCoreApplication::notifyInternal2 (receiver=0x5616e9587240, event=0x7ffec66dd250) at kernel/qcoreapplication.cpp:1064 #14 0x7fd1a129d6d2 in QCoreApplication::sendEvent (receiver=, event=) at kernel/qcoreapplication.cpp:1462 #15 0x7fd1a2c4e60d in KWin::DecorationEventFilter::pointerEvent (this=, event=0x7ffec66dd380, nativeButton=) at /usr/src/debug/kwin-5.27.4.1-1.fc37.x86_64/src/input.cpp:1396 #16 0x7fd1a2c8e5d5 in std::__invoke_impl (__f=, __t=@0x5616e85cb280: 0x5616e85cbb10) at /usr/include/c++/12/bits/invoke.h:71 #17 std::__invoke (__fn=) at /usr/include/c++/12/bits/invoke.h:96 #18 std::_Bind, KWin::MouseEvent*, unsigned int))(KWin::MouseEvent*, unsigned int)>::__call(std::tuple&&, std::_Index_tuple<0ul, 1ul, 2ul>) (__args=..., this=) at /usr/include/c++/12/functional:495 #19 std::_Bind, KWin::MouseEvent*, unsigned int))(KWin::MouseEvent*, unsigned int)>::operator()(KWin::InputEventFilter* const&) ( this=) at /usr/include/c++/12/functional:580 #20 __gnu_cxx::__ops::_Iter_pred, KWin::MouseEvent*, unsigned int))(KWin::MouseEvent*, unsigned int)> >::operator()(KWin::InputEventFilter* const*) (__it=0x5616e85cb280, this=) at /usr/include/c++/12/bits/predefined_ops.h:318 #21 std::__find_if, KWin::MouseEvent*, unsigned int))(KWin::MouseEvent*, unsigned int)> > >(KWin::InputEventFilter* const*, KWin::InputEventFilter* const*, __gnu_cxx::__ops::_Iter_pred, KWin::MouseEvent*, unsigned int))(KWin::MouseEvent*, unsigned int)> >, std::random_access_iterator_tag) (__pred=..., __last=0x5616e85cb2b0, __first=0x5616e85cb280) at /usr/include/c++/12/bits/stl_algobase.h:2079 #22 std::__find_if, KWin::MouseEvent*, unsigned int))(KWin::MouseEvent*, unsigned int)> > >(KWin::InputEventFilter* const*, KWin::InputEventFilter* const*, __gnu_cxx::__ops::_Iter_pred, KWin::MouseEvent*, unsigned int))(KWin::MouseEvent*, unsigned int)> >) (__pred=..., __last=0x5616e85cb2b0, __first=0x5616e85cb228) at /usr/include/c++/12/bits/stl_algobase.h:2112 #23 std::find_if, KWin::MouseEvent*, unsigned int))(KWin::MouseEvent*, unsigned int)> >(KWin::InputEventFilter* const*, KWin::InputEventFilter* const*, std::_Bind, KWin::MouseEvent*, unsigned int))(KWin::MouseEvent*, unsigned int)>) (__pred=..., __last=0x5616e85cb2b0, __first=0x5616e85cb228) at /usr/include/c++/12/bits/stl_algo.h:3877 #24 std::none_of, KWin::MouseEvent*, unsigned int))(KWin::MouseEvent*, unsigned int)> >(KWin::InputEventFilter* const*, KWin::InputEventFilter* const*, std::_Bind, KWin::MouseEvent*, unsigned int))(KWin::MouseEvent*, unsigned int)>) (__pred=..., __last=0x5616e85cb2b0, __first=0x5616e85cb228) at /usr/include/c++/12/bits/stl_algo.h:474 #25 std::any_of, KWin::MouseEvent*, unsigned int))(KWin::MouseEvent*, unsigned int)> >(KWin::InputEventFilter* const*, KWin::InputEventFilter* const*, std::_Bind, KWin::MouseEvent*, unsigned int))(KWin::MouseEvent*, unsigned int)
[plasmashell] [Bug 468576] Middle-clicking certain widgets in a panel crashes plasmashell
https://bugs.kde.org/show_bug.cgi?id=468576 --- Comment #2 from Ryan Y --- I'm using Breeze Dark. Yes, it happens in the Wayland session too. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 468576] New: Middle-clicking certain widgets in a panel crashes plasmashell
https://bugs.kde.org/show_bug.cgi?id=468576 Bug ID: 468576 Summary: Middle-clicking certain widgets in a panel crashes plasmashell Classification: Plasma Product: plasmashell Version: 5.27.4 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Panel Assignee: plasma-b...@kde.org Reporter: ryuichi.ya...@gmail.com CC: niccolo.venera...@gmail.com Target Milestone: 1.0 SUMMARY Middle-clicking on some panel widgets (e.g. to mute all speakers) crashes plasmashell. STEPS TO REPRODUCE 1. Middle-click the volume panel icon OBSERVED RESULT Crashes plasmashell EXPECTED RESULT Does not crash plasmashell SOFTWARE/OS VERSIONS Operating System: Fedora Linux 37 KDE Plasma Version: 5.27.4 KDE Frameworks Version: 5.104.0 Qt Version: 5.15.8 Kernel Version: 6.2.10-200.fc37.x86_64 (64-bit) Graphics Platform: X11 ADDITIONAL INFORMATION I'm using Breeze as my application style theme. It also happens on a Wayland session. On my system, middle-clicking the titlebar buttons crashes KWin as well. So it might not be an issue in plasmashell but in Qt or something. A backtrace generated by gdb: Thread 1 "plasmashell" received signal SIGSEGV, Segmentation fault. 0x7fb191bdc8ef in QWidgetPrivate::pointInsideRectAndMask (p=..., this=0x5637162b5800) at ../../include/QtWidgets/5.15.8/QtWidgets/private/../../../../../src/widgets/kernel/qwidget_p.h:840 840 return q->rect().contains(p) && (!extra || !extra->hasMask || q->testAttribute(Qt::WA_MouseNoMask) Thread 1 (Thread 0x7fb18c91a980 (LWP 13671) "plasmashell"): #0 0x7fb191bdc8ef in QWidgetPrivate::pointInsideRectAndMask (p=..., this=0x5637162b5800) at ../../include/QtWidgets/5.15.8/QtWidgets/private/../../../../../src/widgets/kernel/qwidget_p.h:840 #1 QWidgetPrivate::childAt_helper (this=0x5637162b5800, p=..., ignoreChildrenInDestructor=ignoreChildrenInDestructor@entry=false) at kernel/qwidget.cpp:10176 #2 0x7fb191bdc97f in QWidget::childAt (this=this@entry=0x563718302d30, p=...) at kernel/qwidget.cpp:10168 #3 0x7fb1931f19a9 in KCheckAccelerators::eventFilter (this=0x563715ba84c0, obj=0x563718302d30, e=0x7ffc580c8f00) at /usr/src/debug/kf5-kxmlgui-5.104.0-1.fc37.x86_64/src/kcheckaccelerators.cpp:174 #4 0x7fb190e9d1d1 in QCoreApplicationPrivate::sendThroughApplicationEventFilters (this=this@entry=0x563715698e30, receiver=receiver@entry=0x563718302d30, event=event@entry=0x7ffc580c8f00) at kernel/qcoreapplication.cpp:1172 #5 0x7fb191baeda0 in QApplicationPrivate::notify_helper (this=0x563715698e30, receiver=0x563718302d30, e=0x7ffc580c8f00) at kernel/qapplication.cpp:3611 #6 0x7fb190e9d4e8 in QCoreApplication::notifyInternal2 (receiver=0x563718302d30, event=0x7ffc580c8f00) at kernel/qcoreapplication.cpp:1064 #7 0x7fb190e9d6f2 in QCoreApplication::sendSpontaneousEvent (receiver=, event=) at kernel/qcoreapplication.cpp:1474 #8 0x7fb19136ad6d in QGuiApplicationPrivate::processMouseEvent (e=0x56371ac07b20) at kernel/qguiapplication.cpp:2278 #9 0x7fb191349f1c in QWindowSystemInterface::sendWindowSystemEvents (flags=flags@entry=...) at kernel/qwindowsysteminterface.cpp:1169 #10 0x7fb17f116a7e in xcbSourceDispatch (source=) at qxcbeventdispatcher.cpp:105 #11 0x7fb18fc65c7f in g_main_dispatch (context=0x7fb178005010) at ../glib/gmain.c:3454 #12 g_main_context_dispatch (context=0x7fb178005010) at ../glib/gmain.c:4172 #13 0x7fb18fcbc118 in g_main_context_iterate.constprop.0 (context=0x7fb178005010, block=1, dispatch=1, self=) at ../glib/gmain.c:4248 #14 0x7fb18fc62f00 in g_main_context_iteration (context=0x7fb178005010, may_block=1) at ../glib/gmain.c:4313 #15 0x7fb190eee5fa in QEventDispatcherGlib::processEvents (this=0x563715773d80, flags=...) at kernel/qeventdispatcher_glib.cpp:423 #16 0x7fb190e9bf3a in QEventLoop::exec (this=this@entry=0x7ffc580c9290, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:69 #17 0x7fb190ea4002 in QCoreApplication::exec () at ../../include/QtCore/../../src/corelib/global/qflags.h:121 #18 0x7fb19135fad0 in QGuiApplication::exec () at kernel/qguiapplication.cpp:1863 #19 0x7fb191baecd9 in QApplication::exec () at kernel/qapplication.cpp:2832 #20 0x563713e266ac in main (argc=, argv=) at /usr/src/debug/plasma-workspace-5.27.4.1-1.fc37.x86_64/shell/main.cpp:235 Detaching from program: /usr/bin/plasmashell, process 13671 [Inferior 1 (process 13671) detached] -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 467775] Okular crashes when clicking in PDF form editable multi-line text field
https://bugs.kde.org/show_bug.cgi?id=467775 --- Comment #4 from Ryan Thompson --- Oddly, I can no longer reproduce the issue on the file in question. In the intervening days, my system has been upgraded and I now have Okular version 22.12.3 (whereas at the time of reporting I had 22.12.2. I suppose it's possible that some change in this new version fixed the bug, or possibly the bug was in some other library that got updated as well. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kded] [Bug 452691] [Bluetooth - Bluedevil] PS4 / Dual Shock 4 Controller Crashed kded5
https://bugs.kde.org/show_bug.cgi?id=452691 Ryan Y changed: What|Removed |Added CC||ryuichi.ya...@gmail.com Alias|bluedevil, bluetooth, | |crash, segfault,| |segmentation-fault | --- Comment #8 from Ryan Y --- Isn't it because you've set multiple aliases like "crash" and "segfault"? Searching those words with the search bar directs you to this bug report. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 467993] konsole cannot run other apps
https://bugs.kde.org/show_bug.cgi?id=467993 --- Comment #2 from Ryan --- (In reply to Waqar Ahmed from comment #1) > There was a change related to the snap store release recently, perhaps this > is due that? Yes, that is what has happened. I think the updates have been fantastic so far. It looks and works amazing. The only problem I have been having thus far is the problem with running almost anything in Konsole. I guess in creating the snap some plug needs to be specified to allow it to run things listed in the PATH. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 466536] Blur effect sometimes does not blur the background of "Add Panel" menu until turning menu blur in Breeze widget theme off and on again
https://bugs.kde.org/show_bug.cgi?id=466536 Ryan Y changed: What|Removed |Added Version|5.27.1 |5.27.3 --- Comment #4 from Ryan Y --- It happened again. I can now confirm that touching the "Transparency" setting in the application style temporarily fixes the issue; turning the blur desktop effect on and off doesn't. Operating System: Fedora Linux 37 KDE Plasma Version: 5.27.3 KDE Frameworks Version: 5.104.0 Qt Version: 5.15.8 Graphics Platform: X11 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 468032] Make the floating panel de-float when a popup is open
https://bugs.kde.org/show_bug.cgi?id=468032 --- Comment #1 from Ryan Y --- Created attachment 157765 --> https://bugs.kde.org/attachment.cgi?id=157765=edit The panel de-floats when it's in "Always Visible" mode and a window is touching it -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 468032] New: Make the floating panel de-float when a popup is open
https://bugs.kde.org/show_bug.cgi?id=468032 Bug ID: 468032 Summary: Make the floating panel de-float when a popup is open Classification: Plasma Product: plasmashell Version: 5.27.3 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: Panel Assignee: plasma-b...@kde.org Reporter: ryuichi.ya...@gmail.com CC: niccolo.venera...@gmail.com Target Milestone: 1.0 Created attachment 157764 --> https://bugs.kde.org/attachment.cgi?id=157764=edit The popup does not know the panel is floating SUMMARY Currently, the floating panel stays afloat even when a popup is open. As the result, they do not align with each other as shown in the attachment. I think it would be great if the panel de-floats when a popup is open, just like it does when a window is touching it. STEPS TO REPRODUCE 1. Place a menu widget on the edge of a panel 2. Open the menu OBSERVED RESULT The panel stays afloat, and the popup does not align with it EXPECTED RESULT The panel de-floats so that it aligns with the popup SOFTWARE/OS VERSIONS Operating System: Fedora Linux 37 KDE Plasma Version: 5.27.3 KDE Frameworks Version: 5.104.0 Qt Version: 5.15.8 Graphics Platform: X11 -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 467993] konsole cannot run other apps
https://bugs.kde.org/show_bug.cgi?id=467993 Ryan changed: What|Removed |Added Product|neon|kate Component|Snaps |general Assignee|sgmo...@kde.org |kwrite-bugs-n...@kde.org Version|unspecified |22.12.3 -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 467993] New: konsole cannot run other apps
https://bugs.kde.org/show_bug.cgi?id=467993 Bug ID: 467993 Summary: konsole cannot run other apps Classification: KDE Neon Product: neon Version: unspecified Platform: Ubuntu OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Snaps Assignee: sgmo...@kde.org Reporter: jryan.dani...@gmail.com CC: neon-b...@kde.org Target Milestone: --- SUMMARY *** I have upgraded the Kate snap to the latest. Since then I cannot run custom scripts on the built in konsole. *** STEPS TO REPRODUCE Try to start any of a number of apps from within Konsole (in kate). e.g. type in the Konsole inkscape gimp latex htop OBSERVED RESULT Nothing happens. EXPECTED RESULT Something happens. In the previous version of the snap I could run custom scripts and start other apps from kate. SOFTWARE/OS VERSIONS snap-id: AhMXNopXhzZ7XDMS9mZ2H2G40U3h3SkR tracking: latest/stable refresh-date: today at 10:18 SAST channels: latest/stable:22.12.3 2023-03-27 (135) 212MB - latest/candidate: 22.12.3 2023-03-27 (135) 212MB - latest/beta: ↑ latest/edge: ↑ installed: 22.12.3(135) 212MB - ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 467775] Okular crashes when clicking in PDF form editable multi-line text field
https://bugs.kde.org/show_bug.cgi?id=467775 --- Comment #2 from Ryan Thompson --- (In reply to Albert Astals Cid from comment #1) > We're going to need the file Unfortunately the specific file is confidential. However, I suspect that there is a specific character in that fillable field causing the crash, so I will see if I can reduce it to just that character and delete the rest of the filled contents, which would result in a file I can share. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 467775] New: Okular crashes when clicking in PDF form editable multi-line text field
https://bugs.kde.org/show_bug.cgi?id=467775 Bug ID: 467775 Summary: Okular crashes when clicking in PDF form editable multi-line text field Classification: Applications Product: okular Version: 22.12.2 Platform: Archlinux OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: okular-de...@kde.org Reporter: rct+b...@thompsonclan.org Target Milestone: --- Application: okular (22.12.2) Qt Version: 5.15.8 Frameworks Version: 5.103.0 Operating System: Linux 6.1.19-1-MANJARO x86_64 Windowing System: X11 Distribution: Manjaro Linux DrKonqi: 5.26.5 [KCrashBackend] -- Information about the crash: When opening a some PDFs with fillable fields. Clicking in a multi-line text box immediately crashes Okular, before I can even start typing in the field. Worth noting, the PDF in question already has text in those fields, and the backtrace seems font-related, so my expectation is that one of the characters already present in the filled form is causing issues with the font Okular is using to render the form text. The crash can be reproduced every time. -- Backtrace: Application: Okular (okular), signal: Segmentation fault [KCrash Handler] #4 0x7ff36995a750 in GfxResources::doLookupFont(char const*) const () at /usr/lib/libpoppler.so.126 #5 0x7ff36995a822 in GfxResources::lookupFont(char const*) () at /usr/lib/libpoppler.so.126 #6 0x7ff369955b8e in Form::ensureFontsForAllCharacters(GooString const*, std::__cxx11::basic_string, std::allocator > const&, GfxResources*) () at /usr/lib/libpoppler.so.126 #7 0x7ff36994a82b in () at /usr/lib/libpoppler.so.126 #8 0x7ff37042457d in Poppler::FormFieldText::setText(QString const&) () at /usr/lib/libpoppler-qt5.so.1 #9 0x7ff3953c4b3d in () at /usr/lib/libOkular5Core.so.10 #10 0x7ff3a2f0357a in QUndoStack::push(QUndoCommand*) () at /usr/lib/libQt5Widgets.so.5 #11 0x7ff3955816ba in () at /usr/lib/qt/plugins/okularpart.so #12 0x7ff3a1ebea71 in () at /usr/lib/libQt5Core.so.5 #13 0x7ff3955869aa in () at /usr/lib/qt/plugins/okularpart.so #14 0x7ff3a1ebea71 in () at /usr/lib/libQt5Core.so.5 #15 0x7ff3a1ebec20 in () at /usr/lib/libQt5Core.so.5 #16 0x7ff3a2d57d0d in () at /usr/lib/libQt5Widgets.so.5 #17 0x7ff3a2d38956 in QTextEdit::setPlainText(QString const&) () at /usr/lib/libQt5Widgets.so.5 #18 0x7ff395588718 in () at /usr/lib/qt/plugins/okularpart.so #19 0x7ff3a2b78b5c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5 #20 0x7ff3a1e8df48 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib/libQt5Core.so.5 #21 0x7ff3a2b74bec in QApplicationPrivate::setFocusWidget(QWidget*, Qt::FocusReason) () at /usr/lib/libQt5Widgets.so.5 #22 0x7ff3a2ba97f7 in QWidget::setFocus(Qt::FocusReason) () at /usr/lib/libQt5Widgets.so.5 #23 0x7ff3a2b78efb in QApplicationPrivate::giveFocusAccordingToFocusPolicy(QWidget*, QEvent*, QPoint) () at /usr/lib/libQt5Widgets.so.5 #24 0x7ff3a2b7f016 in QApplication::notify(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5 #25 0x7ff3a1e8df48 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib/libQt5Core.so.5 #26 0x7ff3a2b7c377 in QApplicationPrivate::sendMouseEvent(QWidget*, QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer&, bool, bool) () at /usr/lib/libQt5Widgets.so.5 #27 0x7ff3a2bcd505 in () at /usr/lib/libQt5Widgets.so.5 #28 0x7ff3a2bcf2ae in () at /usr/lib/libQt5Widgets.so.5 #29 0x7ff3a2b78b5c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5 #30 0x7ff3a1e8df48 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib/libQt5Core.so.5 #31 0x7ff3a233efbc in QGuiApplicationPrivate::processMouseEvent(QWindowSystemInterfacePrivate::MouseEvent*) () at /usr/lib/libQt5Gui.so.5 #32 0x7ff3a2328885 in QWindowSystemInterface::sendWindowSystemEvents(QFlags) () at /usr/lib/libQt5Gui.so.5 #33 0x7ff39cf2e8d0 in () at /usr/lib/libQt5XcbQpa.so.5 #34 0x7ff3a091682b in g_main_context_dispatch () at /usr/lib/libglib-2.0.so.0 #35 0x7ff3a096dcc9 in () at /usr/lib/libglib-2.0.so.0 #36 0x7ff3a09150e2 in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #37 0x7ff3a1ed8c6c in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #38 0x7ff3a1e866ec in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #39 0x7ff3a1e91219 in QCoreApplication::exec() () at /usr/lib/libQt5Core.so.5 #40 0x55637e34a882 in () #41 0x7ff3a163c790 in __libc_start_call_main (main=main@entry=0x55637e349080, argc=argc@entry=2, argv=argv@entry=0x7ffcdc576ae8) at ../sysdeps/nptl/libc_start_call_main.h:58 #42 0x7ff3a163c84a in __libc_start_main_impl (main=0x55637e349080,
[kdeconnect] [Bug 461046] Totally can't use in iOS 16.0.3
https://bugs.kde.org/show_bug.cgi?id=461046 --- Comment #22 from Ryan Qian --- (In reply to Apollo Zhu from comment #20) > 1. In terms of receiving files, > https://www.reddit.com/r/kde/comments/x0wipc/on_kde_connect_ios_where_do_files_go_when/imb4y4q/ > suggest that you might need to unhide the “on my phone” option to see the KDE > Connect folder. > I tested with the Qt client and couldn’t find any problem, so I guess the > above might be why. FYI, I tried it, but I didn't find the KDE Connect folder or other related buttons under `Files --> On My iPhone`. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 466536] Blur effect does not blur the background of "Add Panel" menu
https://bugs.kde.org/show_bug.cgi?id=466536 --- Comment #2 from Ryan Y --- Yes, I'm using the setting in Breeze application style, and I'm on X11. For some reason, whether toggling the blur effect or setting the menu to be opaque and then to be transparent seem to have fixed the issue... now it's blurred just fine. All the other menus were properly blurred, just this particular menu was not blurred. I don't think this is just a temporally glitch, as the menu had been like that for at least several weeks, even after having gone through some reboots. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 466536] New: Blur effect does not blur the background of "Add Panel" menu
https://bugs.kde.org/show_bug.cgi?id=466536 Bug ID: 466536 Summary: Blur effect does not blur the background of "Add Panel" menu Classification: Plasma Product: kwin Version: 5.27.1 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: effects-various Assignee: kwin-bugs-n...@kde.org Reporter: ryuichi.ya...@gmail.com Target Milestone: --- Created attachment 156791 --> https://bugs.kde.org/attachment.cgi?id=156791=edit The wallpaper can be seen through the menu SUMMARY The blur effect does not blur the background of "Add Panel" menu STEPS TO REPRODUCE 1. Open the standard menu on desktop 2. Hover the cursor over "Add Panel" OBSERVED RESULT The background of the menu is not blurred EXPECTED RESULT The background of the menu is blurred SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora Linux (available in About System) KDE Plasma Version: 5.27.1 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 -- You are receiving this mail because: You are watching all bug changes.
[NeoChat] [Bug 466328] New: crashes upon changing the view
https://bugs.kde.org/show_bug.cgi?id=466328 Bug ID: 466328 Summary: crashes upon changing the view Classification: Applications Product: NeoChat Version: unspecified Platform: Neon OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: General Assignee: fe...@posteo.de Reporter: ryan...@gmail.com CC: c...@carlschwan.eu Target Milestone: --- Application: neochat (23.01) Qt Version: 5.15.8 Frameworks Version: 5.103.0 Operating System: Linux 5.15.0-60-generic x86_64 Windowing System: X11 Distribution: KDE neon 5.27 DrKonqi: 5.27.1 [KCrashBackend] -- Information about the crash: When changing to see a message, and sometimes when a message comes in, neochat will crash. Not sure if this is related to #456903 (closed) Additionally, the icons for each chat are excessively large on a desktop view, something like 512x512 pixels and I don't think they look like expected. The crash can be reproduced every time. -- Backtrace: Application: NeoChat (neochat), signal: Segmentation fault [KCrash Handler] #4 0x7f1995bb29b4 in QString::operator=(QString const&) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x5592272f0efe in ?? () #6 0x559227296928 in ?? () #7 0x7f1995ce6e79 in QSortFilterProxyModel::data(QModelIndex const&, int) const () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x5592272d4248 in ?? () #9 0x7f199533f4f7 in ?? () from /lib/x86_64-linux-gnu/libQt5QmlModels.so.5 #10 0x7f1997b979f6 in ?? () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #11 0x7f1997b98975 in QV4::QObjectWrapper::virtualResolveLookupGetter(QV4::Object const*, QV4::ExecutionEngine*, QV4::Lookup*) () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #12 0x7f1997bb8125 in ?? () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #13 0x7f1997bbcb9f in ?? () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #14 0x7f1997b4eaee in QV4::Function::call(QV4::Value const*, QV4::Value const*, int, QV4::ExecutionContext const*) () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #15 0x7f1997cdb3a5 in QQmlJavaScriptExpression::evaluate(QV4::CallData*, bool*) () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #16 0x7f1997ce16a8 in QQmlBinding::evaluate(bool*) () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #17 0x7f1997ce59db in ?? () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #18 0x7f1997ce3664 in QQmlBinding::update(QFlags) () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #19 0x7f1997cf0fca in QQmlObjectCreator::finalize(QQmlInstantiationInterrupt&) () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #20 0x7f1997c86235 in QQmlIncubatorPrivate::incubate(QQmlInstantiationInterrupt&) () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #21 0x7f1997c8684d in QQmlEnginePrivate::incubate(QQmlIncubator&, QQmlContextData*) () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #22 0x7f1995353363 in ?? () from /lib/x86_64-linux-gnu/libQt5QmlModels.so.5 #23 0x7f19981ac375 in ?? () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #24 0x7f19981bb6ee in ?? () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #25 0x7f19981aab38 in ?? () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #26 0x7f19981af13e in ?? () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #27 0x7f19981af49a in QQuickItemView::modelUpdated(QQmlChangeSet const&, bool) () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #28 0x7f1995d55108 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #29 0x7f199532603a in QQmlInstanceModel::modelUpdated(QQmlChangeSet const&, bool) () from /lib/x86_64-linux-gnu/libQt5QmlModels.so.5 #30 0x7f1995346e7c in ?? () from /lib/x86_64-linux-gnu/libQt5QmlModels.so.5 #31 0x7f199534d4c2 in ?? () from /lib/x86_64-linux-gnu/libQt5QmlModels.so.5 #32 0x7f199534d8c8 in ?? () from /lib/x86_64-linux-gnu/libQt5QmlModels.so.5 #33 0x7f199535905d in QQmlDelegateModel::_q_modelReset() () from /lib/x86_64-linux-gnu/libQt5QmlModels.so.5 #34 0x7f1995359ca3 in QQmlDelegateModel::qt_metacall(QMetaObject::Call, int, void**) () from /lib/x86_64-linux-gnu/libQt5QmlModels.so.5 #35 0x7f1995d54e46 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #36 0x7f1995cb6191 in QAbstractItemModel::modelReset(QAbstractItemModel::QPrivateSignal) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #37 0x7f1995cee30a in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #38 0x7f1995d55108 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #39 0x7f1995cb6191 in QAbstractItemModel::modelReset(QAbstractItemModel::QPrivateSignal) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #40 0x7f1995cee30a in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #41 0x7f1995d55108 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #42 0x7f1995cb6191 in QAbstractItemModel::modelReset(QAbstractItemModel::QPrivateSignal) () from /lib/x86_64-l
[krita] [Bug 463135] Keyboard keys lose focus/stop working.
https://bugs.kde.org/show_bug.cgi?id=463135 --- Comment #8 from ryan --- (In reply to Halcyoen from comment #7) > i have what i think is the same issue on kde neon. the issue appears > whenever i press ctrl+alt or ctrl+shift. after this my canvas input command > for the color sampler (alt+left click) or resizing the brush (alt+right > click) stops working. the quickest way to "unblock" my canvas inputs is by > pressing ctrl again. > > this only seems to happen in the version downloaded from the official repos > though. i do not experience this issue on windows, not with the appimage > version and not with the flatpak version. is it tied to plasma somehow? > > as for the bug where you lose input after holding alt and selecting a new > brush preset, it seems to go back quite some time. at least krita 4.2. the > OS wouldnt let me open krita 4.0 for some reason. The problem happens to me with a fresh Ubuntu install on a virtual machine. I have used Kde for roughly 3 years now, and the problem has been consistent with every version past krita 5.0.2. In 5.0.2, there appears to be some version of this bug, but like you described, the key locking disappears after a short period of time. It's annoying, but still usable. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 465998] Long date from the tooltip is incorrect
https://bugs.kde.org/show_bug.cgi?id=465998 Ryan Y changed: What|Removed |Added CC||ryuichi.ya...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 466054] New: Integrate input method panel into system tray
https://bugs.kde.org/show_bug.cgi?id=466054 Bug ID: 466054 Summary: Integrate input method panel into system tray Classification: Plasma Product: plasmashell Version: 5.27.0 Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: Kimpanel Assignee: plasma-b...@kde.org Reporter: ryuichi.ya...@gmail.com CC: wen...@gmail.com Target Milestone: 1.0 Created attachment 156477 --> https://bugs.kde.org/attachment.cgi?id=156477=edit fcitx5-unikey is in use Currently the input method panel applet is separated from the system tray applet, and they use different spacing lengths between their icons. As the result, the margin between icons in a panel is inconsistent as shown in the attachment. I'm not sure if it's possible, but I would love to see them integrated in one applet and the icons aligned in a consistent manner. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 428066] Panel show/hide animation does not work in "Windows Can Cover" mode
https://bugs.kde.org/show_bug.cgi?id=428066 Ryan Y changed: What|Removed |Added Version|5.20.0 |5.26.5 CC||ryuichi.ya...@gmail.com --- Comment #1 from Ryan Y --- I assume the panel is supposed to behave like that, but I would also love to see the animation working in "Windows Can Cover" mode. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 433059] "Active/Inactive Titlebar" colors are visible and editable but confusingly unused when Header colors are present
https://bugs.kde.org/show_bug.cgi?id=433059 Ryan Y changed: What|Removed |Added CC||ryuichi.ya...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 446874] Crash in QSGOpaqueTextureMaterialShader::updateState()
https://bugs.kde.org/show_bug.cgi?id=446874 Ryan changed: What|Removed |Added Flags||X11+ CC||mercy.sp...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 465499] Docs need screenshots
https://bugs.kde.org/show_bug.cgi?id=465499 --- Comment #1 from Ryan --- The "Size" properties shown in this video on Youtube do not show up for me with rectangles. https://www.bing.com/videos/search?q=krita+rounded+rectangle&=detail=4FD5DEFE3796CDDC26EF4FD5DEFE3796CDDC26EF&=VRDGAR=%2Fvideos%2Fsearch%3Fq%3Dkrita%2Brounded%2Brectangle%26FORM%3DHDRSC3 @ 4:35 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 465499] New: Docs need screenshots
https://bugs.kde.org/show_bug.cgi?id=465499 Bug ID: 465499 Summary: Docs need screenshots Classification: Applications Product: krita Version: unspecified Platform: unspecified OS: Unspecified Status: REPORTED Severity: normal Priority: NOR Component: * Unknown Assignee: krita-bugs-n...@kde.org Reporter: rj.amdphr...@gmail.com Target Milestone: --- ### SUMMARY The docs are not very useful and need screenshots. I'm trying to figure out where in the heck the rectangle corner rounding setting is, but I can't find it in the app, and the docs are next to useless for showing me where to look for it. https://docs.krita.org/en/reference_manual/tools/rectangle.html -- You are receiving this mail because: You are watching all bug changes.
[lokalize] [Bug 424024] Main window doesn't repaint correctly on Wayland
https://bugs.kde.org/show_bug.cgi?id=424024 Ryan Y changed: What|Removed |Added CC||ryuichi.ya...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 463135] Keyboard keys lose focus/stop working.
https://bugs.kde.org/show_bug.cgi?id=463135 --- Comment #6 from ryan --- In addition, there is a small window of time where if one presses the alt key after selecting a brush and then left clicks the canvas, that the same bug will appear. In my instance, since I often select color right after selecting a brush, I see this bug a lot. I actually think this is how I am triggering the bug rather than when pressing the alt key during brush selection. There is one little bit information that may help, if you press the alt key after selecting a brush, and then wait for the color picker icon to appear, then it becomes safe to left click to sample a color. If done before the transition, the keyboard keys will become stuck. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 463135] Keyboard keys lose focus/stop working.
https://bugs.kde.org/show_bug.cgi?id=463135 --- Comment #5 from ryan --- After further testing, I believe the subject of my last reply is the issue. I tested version 5.1.5 and I can see that I lose function of the keyboard until I select another brush. I'm unsure why I was still able to before. It seems that the alt key is the only modifier that will cause the keyboard to lock-up. There is also no need to change any settings as I discovered that the alt key is what triggers the issue, regardless of what is bound to it. Again, the steps to reproduce the bug is: while holding the alt key, select a different brush and then click the canvas window. Let go of the alt key and try to use the keyboard (also affects mouse). You can resolve the bug by selecting a new brush or by clicking on a different window (layers, toolbox, etc). While I have discovered the problem, this bug is probably not something a lot of people experience because it takes human error to even bring it out (selecting a brush while holding a modifier key), and then it also takes someone who doesn't use the default bindings. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 463135] Keyboard keys lose focus/stop working.
https://bugs.kde.org/show_bug.cgi?id=463135 --- Comment #4 from ryan --- I may have isolated a part of the issue. While using the changes to the Canvas Input Settings that I've discussed already, press and hold the key to sample the canvas color (alt) and then select a brush from the brush preset window. While still holding the alt-key, left click on the canvas. You can now let go of alt. The effect will be that you can no longer use the alt-key. The default settings seem to not be affected by this bug. While this is similar to the issue I am experiencing, this particular method still allows one to use other keys like the spacebar for panning the canvas. The problem I originally described doesn't even allow one to use the spacebar, so I'm still unsure of how that bug comes about, but the cause might be related. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 464261] New: CIFS shares mounts should be allowed to set a nickname like a KIO SMB share
https://bugs.kde.org/show_bug.cgi?id=464261 Bug ID: 464261 Summary: CIFS shares mounts should be allowed to set a nickname like a KIO SMB share Classification: Applications Product: dolphin Version: 22.12.1 Platform: Archlinux OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: k...@kishi.dev CC: kfm-de...@kde.org Target Milestone: --- SUMMARY When mounting a CIFS share in the user home directory makes it appear under the "Remote" section of Dolphin. This new link is the full directory path of the mount "/home/username/NAS". When opening a share via the "Network" menu and bookmarking it, you are given the option to set a nickname for the share. STEPS TO REPRODUCE 1. Mount a CIFS share in the user directory. ex) `sudo mount -t cifs //192.168.1.XXX/share /home/username/NAS -o username=foo,password=bar,vers=3,uid=1000` 2. Open Dolphin and look in the "Remote" section of the "Places" panel. OBSERVED RESULT A new share is present, but you are unable to rename it to a shortened name in the preferences. EXPECTED RESULT Ability to change the label in the preferences. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux KDE Plasma Version: 5.26.5 KDE Frameworks Version: 5.101.0 Qt Version: 5.15.8 ADDITIONAL INFORMATION cifs-utils: 7.0 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 463135] Keyboard keys lose focus/stop working.
https://bugs.kde.org/show_bug.cgi?id=463135 --- Comment #2 from ryan --- (In reply to Halla Rempt from comment #1) > Can you check whether this is also the case with the appimage, or only with > your distribution packages? I've tested and found this issue with all versions, as I have been wanting to move beyond 5.0.2 for awhile now. I believe I have found what triggers the issue. If I test the program with the default Canvas Input Settings, everything seems to work well. However, if I change the alternate invocation to 'alt+left button' (sample foreground color from merged image) and change primary setting to 'ctrl+alt+left button' (brush size), the issue starts. I also remove all other actions in alternate invocation that would conflict with this setup. Basically I change the keys for resize brush and color picker away from defaults which trigger the issue. All I did was change these settings and start painting. Within minutes of panning, selecting brushes, using the above hotkeys, and doing it in a random order, the problem manifests. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 464126] Cannot share files stored on samba share to other device
https://bugs.kde.org/show_bug.cgi?id=464126 Ryan H. changed: What|Removed |Added CC||k...@kishi.dev -- You are receiving this mail because: You are watching all bug changes.
