[kde] [Bug 470195] New: Cannot open any apps, getting "Resource error (fork failure): Cannot allocate memory" on everything

William Coolman bugzilla_noreply at kde.org
Wed May 24 08:29:52 BST 2023


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

            Bug ID: 470195
           Summary: Cannot open any apps, getting "Resource error (fork
                    failure): Cannot allocate memory" on everything
    Classification: I don't know
           Product: kde
           Version: unspecified
          Platform: Other
                OS: Linux
            Status: REPORTED
          Severity: normal
          Priority: NOR
         Component: general
          Assignee: unassigned-bugs at kde.org
          Reporter: wcoolfox at gmail.com
  Target Milestone: ---

Created attachment 159219
  --> https://bugs.kde.org/attachment.cgi?id=159219&action=edit
Can't open anything through main K menu, Task Manager, or Desktop

Operating System: Kubuntu 23.04
KDE Plasma Version: 5.27.4
KDE Frameworks Version: 5.104.0
Qt Version: 5.15.8
Kernel Version: 6.2.0-20-generic (64-bit)
Graphics Platform: Wayland
Processors: 12 × AMD Ryzen 5 PRO 5650U with Radeon Graphics
Memory: 14.4 GiB of RAM
Graphics Processor: AMD Radeon Graphics
Manufacturer: LENOVO
Product Name: 20XF004SUS
System Version: ThinkPad T14s Gen 2
ADDITIONAL INFORMATION

I can't open *anything* in the K menu or from the task manager. I'm getting a
"Resource error (fork failure): Cannot allocate memory" error for everything,
see attachment. Also, none of my desktop icons are viewable.

I have 16 gigs of memory total, and have been running Kubuntu for a year
without any real problems. I don't know what update brought on this behavior?
Running free -h shows I have 9.1Gi left, so I don't know what is going on.

The only way I was able to even open Firefox to file this bug report was
krunner. So far, I've been able to open most things through it, or typing into
konsole once I opened that through krunner, but this is a huge inconvenience.

-- 
You are receiving this mail because:
You are the assignee for the bug.


More information about the Unassigned-bugs mailing list