Bug 512897

Summary: Dolphin fills up /tmp, and holds reference to deleted temp files with unlimited scrollback in terminal pane
Product: [Applications] dolphin Reporter: Troplo <troplo>
Component: panels: terminalAssignee: Dolphin Bug Assignee <dolphin-bugs-null>
Status: RESOLVED DUPLICATE    
Severity: normal CC: dolphin-bugs-null, ilikefoss, kdedev
Priority: NOR Keywords: regression
Version First Reported In: 25.11.90   
Target Milestone: ---   
Platform: Arch Linux   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description Troplo 2025-12-03 05:23:42 UTC
SUMMARY
A few weeks ago, I noticed that randomly, albeit quite regularly, programs will be unable to write to /tmp causing program instability, with a "Disk quota exceeded" error. I found out that the culprit appears to be Dolphin.

COMMAND      PID   USER  FD   TYPE DEVICE    SIZE/OFF NODE NAME
dolphin    20879 troplo  50u   REG   0,47   123506688 2430 /tmp/#2430 (deleted)
dolphin    20879 troplo  64u   REG   0,47 19574120448 2431 /tmp/#2431 (deleted)
dolphin    20879 troplo  67u   REG   0,47    92631040 2432 /tmp/#2432 (deleted)

tmpfs                                   24G   19G  4.7G  80% /tmp

Despite the partition only being 80% full, programs still can't write anything. Closing all Dolphin windows immediately releases the locked files and restores /tmp writing.

STEPS TO REPRODUCE
1. I'm not entirely sure specifically what causes this yet, if I do find the cause I'll let you know, I do use network shares and the embedded terminal extensively, however, it still occurs even when not moving/copying large files from/to the network share. Posting this to see if anyone has the same bug, or any insight.
2. 
3. 

OBSERVED RESULT
Dolphin fills up the /tmp folder with temporary files, and doesn't release the held lock after deleting them, causing them to not actually be deleted.

EXPECTED RESULT
Dolphin should release the lock.

SOFTWARE/OS VERSIONS
Operating System: Arch Linux 
KDE Plasma Version: 6.5.3
KDE Frameworks Version: 6.20.0
Qt Version: 6.10.1
Kernel Version: 6.18.0-zen1-1-zen (64-bit)
Graphics Platform: Wayland
Processors: 24 × 13th Gen Intel® Core™ i7-13700KF
Memory: 48 GiB of RAM (46.9 GiB usable)
Graphics Processor 1: AMD Radeon RX 7900 XTX
Graphics Processor 2: NVIDIA GeForce RTX 2070/PCIe/SSE2

Dolphin version: 25.11.90

ADDITIONAL INFORMATION
Comment 1 Troplo 2025-12-03 09:29:25 UTC
Alright I had unlimited scrollback enabled, and because I use the embedded terminal in Dolphin, that's why it appeared as a Dolphin issue.
I set a limit and it doesn't seem to be happening anymore, was the scrollback system changed? I've had it set to unlimited for years and haven't had this issue before, but I remember that it was never actually unlimited, so I'm not sure whether this would be considered a bug or not, as it probably is actually unlimited now.
Comment 2 TraceyC 2025-12-03 21:12:23 UTC
Thanks for the bug report. In order for this to be actionable, we need to be able to reproduce the bug. Can you provide more specific steps to trigger this?
Comment 3 John 2025-12-03 21:46:06 UTC
Hopefully it has the same cause as this one:
https://bugs.kde.org/show_bug.cgi?id=508402
So a fix can solve both.

I always use the unlimited scrollback, but to the normal terminal.
I pretty much never use the one embedded in Dolphin.
But to make a test for this bug report, I did it by going to the /tmp folder itself and then opening the embedded terminal and running a few ls and cd commands, but I could not reproduce it, like I could with the aforementioned bug report with just clicking on the modified column to sort it.
The unlimited scrollback seems to have been already set, maybe it followed my general Konsole preference (default profile).
So I don't know, maybe it needs more testing with more commands.
Comment 4 TraceyC 2025-12-04 00:31:50 UTC
This does look like the same problem as bug 508402. I'm going to merge this report in with that one. If the bug still happens on your system after that one is marked fixed, please reopen this report. Thanks!

*** This bug has been marked as a duplicate of bug 508402 ***