Bug 499460 - Holding backspace while using ManageEngine SNMP MIB Browser causes Plasma to completely freeze
Summary: Holding backspace while using ManageEngine SNMP MIB Browser causes Plasma to ...
Status: RESOLVED UPSTREAM
Alias: None
Product: plasmashell
Classification: Plasma
Component: general (show other bugs)
Version: 6.2.91
Platform: Arch Linux Linux
: NOR normal
Target Milestone: 1.0
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2025-02-03 13:34 UTC by Antti Savolainen
Modified: 2025-04-26 15:35 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
htop ssh screenshot (257.58 KB, image/png)
2025-02-03 16:29 UTC, Antti Savolainen 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Antti Savolainen 2025-02-03 13:34:32 UTC 
SUMMARY
Download link: https://www.manageengine.com/products/mibbrowser-free-tool/download.html
If select a text box in this program and then hold backspace, I can cause Plasma to completely freeze. If I escape to TTY with Ctrl+Alt+F3, the system is fully responsive and htop doesn't report any abnormal CPU and RAM usage.

STEPS TO REPRODUCE
1. Open ManageEngine SNMP MIB Browser
2. Select a text box.
3. Hold backspace for a few seconds

OBSERVED RESULT
Plasma freezes completely

EXPECTED RESULT
An application should not be able to freeze Plasma

SOFTWARE/OS VERSIONS
Linux: Arch Linux
KDE Plasma Version: 6.2.91
KDE Frameworks Version: 6.10.0
Qt Version: 6.9.0
Comment 1 fanzhuyifan 2025-02-03 16:20:49 UTC 
Is this on x11 or wayland? When you observe the system freeze, do you see anything in the logs? Is any process using 100% CPU?
Comment 2 Antti Savolainen 2025-02-03 16:29:55 UTC 
Created attachment 177931 [details]
htop ssh screenshot

I'm using wayland. Here's a htop screenshot on my phone with an ssh when the freeze happens
Comment 3 Antti Savolainen 2025-03-23 23:07:25 UTC 
This might be a pipewire/wireplumber bug. See wireplumber at the top of htop

I'll report this to them tomorrow.
Comment 4 Antti Savolainen 2025-04-26 15:35:03 UTC 
This was probably fixed in Pipewire upstream