SUMMARY Version 20.11.90 - issue introduced in 20.08.03 Three named pipes are created in /tmp: stdInFIFOxxx, stdOutFIFOxxx, and stdErrFIFOxxx, where xxx are random letters. Upon exit, those named pipes remain in /tmp. Each time Kate is launched, three more named pipes are created, which are not deleted by the destructor of the class that created them. STEPS TO REPRODUCE 1. Launch Kate 2. Do stuff 3. Close Kate OBSERVED RESULT Three named pipes created at startup remain after exit. I noticed them after I found 24 such pipes in /tmp. EXPECTED RESULT All temporary named pipes are closed and deleted upon exit. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION
This happens on only one of my computers, not the other. Is there something in my .config that would cause these named pipes to appear in /tmp? I am not convinced the named pipes are from Kate code, as I cannot find any instance of QQueue. KDE Plasma Version: 5.20.4 KDE Frameworks Version: 5.76.0 Qt Version: 5.15.2 Kernel Version: 5.4.82 CPU: AMD Ryzen 7 1700 GPU: AMD/ATI Lexa Pro [Radeon RX550/550]
I isolated the issue to something in the user's ~/.local folder. A new user did not replicate the issue, a blank ~/.local resolved the vestigial named pipes. Although I'd like to know what in ~/.local could cause kate to create and leave behind named pipes in /tmp, consider this a personal mystery. Will follow up with an FYI should I discover a repeatable config setting.
The named pipes are from the GDB plugin. There is code to remove the named pipes, when the plugin is destroyed, but it seems that it either fails or the plugins are killed without proper unloading when kate is closed.