| Summary: | Certain parts of KDE Plasma stop working after long-term use | ||
|---|---|---|---|
| Product: | [Plasma] plasmashell | Reporter: | alerikaisattera |
| Component: | general | Assignee: | David Edmundson <kde> |
| Status: | RESOLVED FIXED | ||
| Severity: | major | CC: | nate, plasma-bugs-null, tcberner, valdikss |
| Priority: | NOR | ||
| Version First Reported In: | 5.22.4 | ||
| Target Milestone: | 1.0 | ||
| Platform: | Manjaro | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
| Attachments: |
fdlog
fdlog |
||
How did you install your system? This seems like a configuration/packaging bug. However this is interesting: > QProcessPrivate::createPipe: Cannot create pipe 0x55848c032c68 (Too many open files) Do things start working if you increase the open file limit? See https://www.tecmint.com/increase-set-open-file-limits-in-linux/ > How did you install your system? This seems like a configuration/packaging
> bug.
>
Manjaro installed from official Manjaro KDE edition
> Do things start working if you increase the open file limit? See
> https://www.tecmint.com/increase-set-open-file-limits-in-linux/
This is already unreasonably large (9223372036854775807), so probably not
(In reply to alerikaisattera from comment #3) > > Do things start working if you increase the open file limit? See > > https://www.tecmint.com/increase-set-open-file-limits-in-linux/ > > This is already unreasonably large (9223372036854775807), so probably not I saw there are some other limits, which are smaller Increasing limits had no apparent effect. The bug occured in 10 days, which seems to be typical for it This time the error messages are
This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.
Available platform plugins are: eglfs, linuxfb, minimal, minimalegl, offscreen, vnc, wayland-egl, wayland, wayland-xcomposite-egl, wayland-xcomposite-glx, xcb.
Next time when you spot this bug, execute Konsole (you say it works) and run:
ps aux > fdlog.txt
ls -la /proc/*/fd >> fdlog.txt
gzip fdlog.txt
and upload fdlog.txt.gz here.
Do you have any additional plasmoids, maybe third-party ones? (In reply to valdikss from comment #8) > Do you have any additional plasmoids, maybe third-party ones? No Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! Created attachment 141607 [details]
fdlog
This time I tried closing Dolphin and restarting it. Restarting via shortcut failed, but was successful via Krunner. This fixed opening files in some applications (Kate) but not in others (VLC). Didn't fix rest of the problem
Something is indeed wrong with Dolphin, it has a lot of sockets.
It's not clear whether this is a network sockets or unix sockets. Run
ps aux > fdlog.txt
ls -la /proc/*/fd >> fdlog.txt
ss -np >> fdlog.txt
gzip fdlog.txt
please.
(In reply to valdikss from comment #13) > Something is indeed wrong with Dolphin, it has a lot of sockets. > It's not clear whether this is a network sockets or unix sockets. Run > > ps aux > fdlog.txt > ls -la /proc/*/fd >> fdlog.txt > ss -np >> fdlog.txt > gzip fdlog.txt > > please. Will do it next time I have this bug. This should take about 10 days, unless I have to do reboot/shutdown in this time (In reply to alerikaisattera from comment #14) > Will do it next time I have this bug. This should take about 10 days, unless > I have to do reboot/shutdown in this time If `ls -la /proc/*/fd` shows many fds for dolphin, you can do that right now, without waiting for the bug. Marking as needsinfo. Please reopen after attaching the file Created attachment 141947 [details]
fdlog
Added info with socket information included
reopened with new info (In reply to alerikaisattera from comment #17) > Created attachment 141947 [details] > fdlog > > Added info with socket information included Unfortunately I don't know what's the cause of these sockets and how to fix that. I would guess that is file descriptor leak. Maybe KDE developers can help. Plasmashell had a sensible amount of fd's open. (In reply to David Edmundson from comment #20) > Plasmashell had a sensible amount of fd's open. Take a look at dolphin with 303 fds in the latest file. Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! Due to lack of updates, I recenlty had a Plasma session running for almost a month. During that time, only Dolphin-related bugs were detected, with error message "QProcessPrivate::createPipe: Cannot create pipe 0x5607b2303378 (Too many open files)" in logs. Restarting Dolphin fixes this. No bugs in other components have been detected OK, if Plasma is now working find and only Dolphin-related bugs were found, please report them separately to Dolphin. :) Thanks! |
This is a highly enigmatic bug. After long-term use of KDE Plasma (for a few days without restart) one or more of the following stop working: * Thumbnails for new images/videos in Dolphin * Starting software via keyboard shortcuts. This may affect Dolphin, Spectacle, Krunner, but never Konsole * Opening any files via Dolphin * Certain actions in Dolphin (for instance, change ownership) Prior to Plasma 5.22, every failed action was accompanied by log message This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem. Available platform plugins are: eglfs, linuxfb, minimal, minimalegl, offscreen, vnc, wayland-egl, wayland, wayland-xcomposite-egl, wayland-xcomposite-glx, xcb. from either kdeinit5, kglobalaccel or, in case of opening a file in a program, that program. This message was followed by a crash message. In Plasma 5.22, however, the message is QProcessPrivate::createPipe: Cannot create pipe 0x55848c032c68 (Too many open files) with the number different every time. No crash messages STEPS TO REPRODUCE This bug is quite hard to reproduce, exact trigger is not known 1. Use Plasma for multiple days with no restart 2. After some time, some parts of Plasma (described above) stop working OBSERVED RESULT Using Plasma for multiple days causes some functions to stop working EXPECTED RESULT Using Plasma for multiple days must not cause any problems SOFTWARE/OS VERSIONS KDE Plasma Version: Present at least since 5.19 to 5.22. Possibly was present before 5.19 as well