https://bugs.kde.org/show_bug.cgi?id=475506

            Bug ID: 475506
           Summary: Screen locking failed because of too many open files,
                    but rest of system works fine
    Classification: Plasma
           Product: kscreenlocker
           Version: 5.27.4
          Platform: openSUSE
                OS: Linux
            Status: REPORTED
          Severity: normal
          Priority: NOR
         Component: general
          Assignee: [email protected]
          Reporter: [email protected]
  Target Milestone: ---

SUMMARY
***
Due to a problem with an unrelated software component (KMozillaHelper, see
https://www.opensuse-forum.de/thread/66654-maximum-number-of-clients-reached-kmozillahelper/
(German, unfortunately)) I recently had many processes running and files open
even right after booting my system. This did not cause any noticeable problems.
I could start my IDE for software development, browse the web, etc. As far as I
can tell the only issue I had is that I could not lock my screen, either via
keyboard shortcut or by clicking the lock icon in the task bar. The error
message in the logs was this:
2023-10-09T13:14:55.692681+02:00 laptop ksmserver[4361]:
QProcessPrivate::createPipe: Cannot create pipe 0x7fbf90004b78 (Too many open
files)
2023-10-09T13:14:55.699846+02:00 laptop ksmserver[4361]: kscreenlocker: Greeter
Process not available

Obviously this issue can be fixed by killing spurious kmozillahelper processes,
but I do wonder why starting any other programm/process worked fine, and only
the screen locker (a vital component!) could not be started. So please give
this issue a thought before telling me to clean up my system ;-).

PS executing /usr/lib/kscreenlocker_greet manually did work as expected!
***


STEPS TO REPRODUCE
1. Open sufficiently many instances of KMozillaHelper
2. Try to lock the screen

OBSERVED RESULT
Screen did not lock

EXPECTED RESULT
Should have been locked

SOFTWARE/OS VERSIONS
KDE Plasma Version: 5.27.4
KDE Frameworks Version: 5.103.0
Qt Version: 5.15.8

ADDITIONAL INFORMATION
My "ulimit" settings:
$ ulimit -a
core file size               (blocks, -c) unlimited
data seg size              (kbytes, -d) unlimited
scheduling priority    (-e) 0
file size                        (blocks, -f) unlimited
pending signals          (-i) 127197
max locked memory (kbytes, -l) 64
max memory size      (kbytes, -m) unlimited
open files                    (-n) 1024
pipe size                      (512 bytes, -p) 8
POSIX message queues     (bytes, -q) 819200
real-time priority       (-r) 0
stack size                    (kbytes, -s) 8192
cpu time                      (seconds, -t) unlimited
max user processes   (-u) 127197
virtual memory          (kbytes, -v) unlimited
file locks                      (-x) unlimited

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to