| Summary: | Creating ⪆ 111 tabs causes the shell to render error messages, rarely as text, more frequently as “□”. If interacted with, or if the user creates > 10 more tabs, Konsole forcefully closes, causing some shells to SEGV | ||
|---|---|---|---|
| Product: | [Applications] konsole | Reporter: | Roke Julian Lockhart Beedell <4wy78uwh> |
| Component: | single-process | Assignee: | Konsole Bugs <konsole-bugs-null> |
| Status: | REPORTED --- | ||
| Severity: | minor | CC: | christoph |
| Priority: | NOR | ||
| Version First Reported In: | 25.08.3 | ||
| Target Milestone: | --- | ||
| Platform: | Fedora RPMs | ||
| OS: | Linux | ||
| URL: | https://discussion.fedoraproject.org/t/why-does-debuginfod-lack-symbols-for-dotnet-packages/156270/15 | ||
| See Also: |
https://github.com/lxqt/qterminal/issues/1309#issuecomment-3633388780 https://bugzilla.redhat.com/show_bug.cgi?id=2420701 https://bugs.kde.org/show_bug.cgi?id=513666 |
||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | https://crash-reports.kde.org/organizations/kde/issues/332360/events/4ffa7f3eaa85413ca8df1140a290e1cd/ | ||
| Attachments: |
A Screenshot Of The “□”s
A Screenshot Of The Invisible Window A Screencast That Depicts How To Consistently Reproduce The Problem A Screenshot Of > 111 Tabs Existing |
||
|
Description
Roke Julian Lockhart Beedell
2025-12-10 22:36:21 UTC
Created attachment 187511 [details]
A Screenshot Of The Invisible Window
This required some serious wrangling to capture; it's solely possible with fast reflexes, and `sleep $number; spectacle --windowundercursor`. Otherwise, the window disappears.
Created attachment 187513 [details] A Screencast That Depicts How To Consistently Reproduce The Problem Originally created for https://bugzilla.redhat.com/show_bug.cgi?id=2420701#c16:~:text=attachment%202118325%20%5Bdetails%5D-,A%20Screencast%20That%20Depicts%20How%20To%20Consistently%20Reproduce%20The%20Problem,-Thanks!%20Regarding%20%E2%80%9CDo, but is of use here, too, for it demonstrates that this isn't pleasant for some shells. However, this problem is inherently subordinate to all shells being forcefully lost, which affects `bash`, too. This more looks like a resource exhaustion: QProcess: Cannot create pipe (Too many open files) QProcess: Cannot create pipe (Too many open files) Could you increase the allowed number of open files on your system? Created attachment 187852 [details] A Screenshot Of > 111 Tabs Existing (In reply to Christoph Cullmann from comment #3) Indeed, https://stackoverflow.com/revisions/34645/3#:~:text=ulimit%20%2Dn works: > ~~~ > The Wayland connection experienced a fatal error: Protocol error > RokeJulianLockhart@Beedell:~$ ulimit -n 10000 > RokeJulianLockhart@Beedell:~$ konsole > kf.windowsystem: static int KX11Extras::currentDesktop() may only be used on X11 > kf.windowsystem: static void KX11Extras::setOnDesktop(WId, int) may only be used on X11 > ~~~ Therefore, I suppose that Konsole should take into account the current limit. I am not sure if it is really feasible to properly check for that kind of resource limits with reasonable effort. No worries; Wayland's not going anywhere, nor is Konsole, so we're in no rush. If it's not too difficult to explain, however, might I know what's difficult? I presumed that it would be a matter of checking what the relevant `ulimit` is, and then ensure that the amount of tabs doesn't exceed it. Is it not 1:1? |