Bug 366589

Summary: plasma-desktop crashes when cups service is disabled, due to too many open files
Product: [Unmaintained] plasma4 Reporter: Xavier Raynaud <henri_38000>
Component: generalAssignee: Plasma Bugs List <plasma-bugs-null>
Status: RESOLVED UNMAINTAINED    
Severity: crash CC: ext.wu, rdieter
Priority: NOR    
Version First Reported In: 4.11.11   
Target Milestone: ---   
Platform: RedHat Enterprise Linux   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description Xavier Raynaud 2016-08-10 14:23:57 UTC
Plaftorm: centos7.2

$ plasma-desktop -v
Qt: 4.8.5
KDE Development Platform: 4.14.8
Plasma Desktop Shell: 4.11.19

On centos7.2, plasma-desktop crashes when cups service is disabled.
It seems that "/etc/cups/client.conf" is open in a loop (by plasma-desktop and/or KCupsConn), and never closed.
Once maximum opened file is reached, plasma-desktop crashes.

Reproducible: Always

Steps to Reproduce:
To reproduce the issue on centos7.2:
1/ disable cups service
2/ start KDE
3/ wait a bit
    type "lsof | grep cups | wc": you will see the number of entries growing up.
  

Actual Results:  
After ~10 minutes, a simple click on the KDE menu will crash plasma-desktop.
Comment 1 vvu 2016-11-27 14:57:05 UTC
cups-1.6.3-22.el7.x86_64
Comment 2 Nate Graham 2018-06-08 18:37:08 UTC
Hello!

This bug report was filed for KDE Plasma 4, which reached end-of-support status in August 2015. KDE Plasma 5's desktop shell has been almost completely rewritten for better performance and usability, so it is likely that this bug has already been resolved in Plasma 5.

Accordingly, we hope you understand why we must close this bug report. If the issue described  here is still present in KDE Plasma 5.12 or later, please feel free to open a new ticket in the "plasmashell" product after reading https://community.kde.org/Get_Involved/Bug_Reporting

If you would like to get involved in KDE's bug triaging effort so that future mass bug closes like this are less likely, please read https://community.kde.org/Get_Involved#Bug_Triaging

Thanks for your understanding!

Nate Graham