[kde] [Bug 493425] New: Plasma hangs for +40s when copying items

bugzilla_noreply at kde.org bugzilla_noreply at kde.org
Sat Sep 21 11:30:33 BST 2024


https://bugs.kde.org/show_bug.cgi?id=493425

            Bug ID: 493425
           Summary: Plasma hangs for +40s when copying items
    Classification: I don't know
           Product: kde
           Version: unspecified
          Platform: Arch Linux
                OS: Linux
            Status: REPORTED
          Severity: normal
          Priority: NOR
         Component: general
          Assignee: unassigned-bugs at kde.org
          Reporter: jadenjorellyo+kde at gmail.com
  Target Milestone: ---

SUMMARY
Plasma KDE freezes when copying items to clipboard & opening clipboard manager
Win+V
(everything, such as: taskbar, startmenu, and brightness/volume screen overlay)

STEPS TO REPRODUCE
1. Configure klipper to have a History size of 2048 entries
2. Copy lots of items such as text and images (typical use) over time
....After lots of use....
3. Take a screenshot, then copy text, Open clipboard manager. (Win+V, or
taskbar)
One of these actions will trigger a freeze

OBSERVED RESULT
Over time when lots of entries have been accumulated,
plasma becomes unresponsive after copying text and especially images.
Opening clipboard manager can take over 40s. 

EXPECTED RESULT
Doesn't freeze on copy when there is a large clipboard history.
Searching through a unlimited or a very long history clipboard is very helpful
to my workflow.

SOFTWARE/OS VERSIONS (kinfo)
Operating System: Arch Linux 
KDE Plasma Version: 6.1.5
KDE Frameworks Version: 6.6.0
Qt Version: 6.7.2
Kernel Version: 6.10.10-arch1-1 (64-bit)
Graphics Platform: Wayland
Processors: 4 × Intel® Core™ i5-7200U CPU @ 2.50GHz
Memory: 7.6 GiB of RAM
Graphics Processor: Mesa Intel® HD Graphics 620

ADDITIONAL INFORMATION
The screen capture program used is Flameshot & Spectacle (Happens in both)
Bug posted on general product because "Sorry, entering a bug into the product
klipper has been disabled."

-- 
You are receiving this mail because:
You are the assignee for the bug.


More information about the Unassigned-bugs mailing list