Bug 30389

Summary:	X crash (Reached maximum concurrent process limit for user '1000', denying request.)
Product:	Mageia	Reporter:	Pierre Fortin <pfortin>
Component:	RPM Packages	Assignee:	Mageia Bug Squad <bugsquad>
Status:	RESOLVED WORKSFORME	QA Contact:
Severity:	normal
Priority:	Normal	CC:	lewyssmith, marja11
Version:	Cauldron
Target Milestone:	---
Hardware:	All
OS:	Linux
Whiteboard:
Source RPM:		CVE:
Status comment:
Attachments:	journalctl output around crash

Description Pierre Fortin 2022-05-06 19:27:35 CEST

Description of problem: Had just started watching
 https://www.youtube.com/watch?v=MyeCQS7ITnU  (Kodi setup on RasPi)
clicked fullscreen
something seemed off. All I recall is dragging a window and when it reached top of screen; instantly, switched to sddm login screen.

Version-Release number of selected component (if applicable):
Operating System: Mageia 9
KDE Plasma Version: 5.24.4
KDE Frameworks Version: 5.93.0
Qt Version: 5.15.2
Kernel Version: 5.17.5-server-2.mga9 (64-bit)
Graphics Platform: X11
Processors: 20 × 12th Gen Intel® Core™ i7-12700K
Memory: 62.5 GiB of RAM
Graphics Processor: AMD Radeon RX 6600 XT

How reproducible:  first time. 
Including part of journalctl output with some comments.

Crash may have been triggered when this happened:
May 06 12:44:34 pf.pfortin.com rtkit-daemon[1256]: Warning: Reached maximum concurrent process limit for user '1000', denying request.

I was not doing my usual heavy processing at the time; just idling and started to watch above video.

Steps to Reproduce:  unknown
1.
2.
3.

I update Cauldron every 24-48 hours.

Comment 1 Pierre Fortin 2022-05-06 19:28:31 CEST

Created attachment 13237 [details]
journalctl output around crash

Comment 2 Lewis Smith 2022-05-07 21:37:02 CEST

Thank you for the report and the journal. The complaint about "Reached maximum concurrent process limit" is curious: the value shown 256030 is enormous (and the nearest power of 2 is 262144). My system shows:
 $ ulimit -u
 4096
Yours is some 64 times bigger.

My guess is that the manipulations you described triggered a loop somewhere which caused the process overflow.

Can we leave this in obeyance until & if some reproduceability reveals itself? You mention both activating fullscreen and dragging a window - implicitly not possible at least on the same desktop.
My feeling is that this is one of those (hopefully one-off) glitches impossible to pin down.

CC: (none) => lewyssmith

Comment 3 Pierre Fortin 2022-05-07 22:29:15 CEST

Yup; no problem. Posted this in case someone else hits it.  As to fullscreen & dragging, the fullscreen had grown; but not to "full" screen. I don't recall if I grabbed that window or another above/below -- it happened so fast, and some of my reactions are sometimes too quick...
HTH

Comment 4 Marja Van Waes 2022-05-10 21:43:07 CEST

(In reply to Pierre Fortin from comment #3)
> Yup; no problem. Posted this in case someone else hits it.  As to fullscreen
> & dragging, the fullscreen had grown; but not to "full" screen. I don't
> recall if I grabbed that window or another above/below -- it happened so
> fast, and some of my reactions are sometimes too quick...
> HTH

I'll set it to unconfirmed for now.

Status: NEW => UNCONFIRMED
Summary: X crash => X crash (Reached maximum concurrent process limit for user '1000', denying request.)
CC: (none) => marja11
Ever confirmed: 1 => 0

Comment 5 Pierre Fortin 2022-10-27 16:35:38 CEST

No further occurences; closing.

Resolution: (none) => WORKSFORME
Status: UNCONFIRMED => RESOLVED