Created attachment 143934 [details] today session errors SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** Often working with Kate, but not always, my PC with KDE Neon crashed today at least 6 times in 4 hours. Linux/KDE Plasma: Operating System: KDE neon 5.23 KDE Plasma Version: 5.23.3 KDE Frameworks Version: 5.88.0 Qt Version: 5.15.3 Kernel Version: 5.11.0-38-generic (64-bit) Graphics Platform: X11 Processors: 4 × AMD Ryzen 3 3200G with Radeon Vega Graphics Memory: 5,7 GiB of RAM Graphics Processor: AMD Radeon™ Vega 8 Graphics
Almost every day I have crashes in this machine (as already reported in my previous post), always when I click with mouse or press the keyboard: the system freezes, but .f.e. music player keep playing. After 15/30 sec. the system works, but only for a short while, and so on, with infinite loops. What should I do?
Created attachment 144994 [details] today (31/12/2021) session errors the last crash (looping freezing) at 16.39 of 31/12/2021
Hi, a quick scan of your logs shows that you have a LOT going on on this machine. Ultimately it's an X Server crash which I would guess is resource exhaustion. You have many thousand (234145!!) instances of this: 2021-12-30 13:31:15: Initialising aMule 2.3.2 compiled with wxGTK2 v3.0.4 and Boost 1.67 2021-12-30 13:31:15: Checking if there is an instance already running... !2021-12-30 13:31:15: There is an instance of aMule already running 2021-12-30 13:31:15: (lock file: /home/duns/.aMule/muleLock) 2021-12-30 13:31:15: Raising current running instance. eventually followed by a crash: klauncher: Exiting on signal 15 klauncher: Exiting on signal 1 XIO: fatal IO error 4 (Interrupted system call) on X server ":0" after 2072 requests (2072 known processed) with 0 events remaining. XIO: fatal IO error 0 (Success) on X server ":0" after 234145 requests (234122 known processed) with 0 events remaining. Exception in thread XInterface-thread: Traceback (most recent call last): File "/usr/lib/python3.8/threading.py", line 932, in _bootstrap_inner self.run() File "/usr/lib/python3/dist-packages/autokey/interface.py", line 1206, in run self.recordDisplay.record_enable_context(self.ctx, self.__processEvent) File "/usr/lib/python3/dist-packages/Xlib/ext/record.py", line 239, in enable_context EnableContext( File "/usr/lib/python3/dist-packages/Xlib/ext/record.py", line 220, in __init__ rq.ReplyRequest.__init__(self, *args, **keys) File "/usr/lib/python3/dist-packages/Xlib/protocol/rq.py", line 1369, in __init__ self.reply() File "/usr/lib/python3/dist-packages/Xlib/protocol/rq.py", line 1381, in reply self._display.send_and_recv(request = self._serial) File "/usr/lib/python3/dist-packages/Xlib/protocol/display.py", line 610, in send_and_recv raise self.socket_error Xlib.error.ConnectionClosedError: Display connection closed by server after that everything goes wrong, as you might expect. May I suggest stopping aMule and seeing if that helps?
ok, I will try as you suggest
Unfortunately, even without Amule, I got new crashes. This morning I was working with kate and the file I was working with, when the crash arrived, got empty (0bytes). I attach another log. The crash was at 11.45 or so. Thank you!
Created attachment 145153 [details] today crash log The crash was about at 11.45
Many freezings/crashes yesterday and today, even with few open applications. I have 8gb of RAM, and a PC quite new. I attach the log (the last crash is today at 18.39)
Created attachment 145236 [details] today crash log
None of these appear to be a backtrace
This still looks like something is killing your X Server: Gdk-Message: 22:10:55.022: xsnow: Fatal IO error 11 (Resource temporarily unavailable) on X server :0. Exception in thread XInterface-thread: Traceback (most recent call last): File "/usr/lib/python3.8/threading.py", line 932, in _bootstrap_inner self.run() File "/usr/lib/python3/dist-packages/autokey/interface.py", line 1206, in run self.recordDisplay.record_enable_context(self.ctx, self.__processEvent) File "/usr/lib/python3/dist-packages/Xlib/ext/record.py", line 239, in enable_context EnableContext( File "/usr/lib/python3/dist-packages/Xlib/ext/record.py", line 220, in __init__ rq.ReplyRequest.__init__(self, *args, **keys) File "/usr/lib/python3/dist-packages/Xlib/protocol/rq.py", line 1369, in __init__ self.reply() File "/usr/lib/python3/dist-packages/Xlib/protocol/rq.py", line 1381, in reply self._display.send_and_recv(request = self._serial) File "/usr/lib/python3/dist-packages/Xlib/protocol/display.py", line 610, in send_and_recv raise self.socket_error Xlib.error.ConnectionClosedError: Display connection closed by server XIO: fatal IO error 9 (Bad file descriptor) on X server ":0" after 8763 requests (8763 known processed) with 0 events remaining. There is too much going on on this machine for me to be much more helpful than this.
Thank you, David and John. In these days I am far from that PC. But when I go back there, what should I do tho get a backtrace?
Back to this PC I got other crashes. How could I get a backtrace, so that you may help me to fix this problem? I noticed that a backtrace via konsole requires that you know what app is the crash cause: I'm wrong?
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!
(In reply to Bug Janitor Service from comment #13) > 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! Thank you. The fact is that the PC which has this problem, is one I use only now and again. But in these days I am using it. I noticed the last time that if I detach the usb pen-drive, I can avoid the freezes/crashes. I will repeat this also this time. But after 2/3 days I will put the usb drive and follow the backtrace instructions you gave me.
As expected, in these last 4 days, using this PC (and today is the last I going to use it), no crashes and usb-drive unplugged. I will let plugged the usb-driv today, to see what happens. But in your above link I didn't find an easy way to track a possible crash....
Try using coredumpctl to list the coredumps and get a backtrack
(In reply to John Clark from comment #16) > Try using coredumpctl to list the coredumps and get a backtrack thank you. Today usb-drive pluggend AND a crash (before installing coredumpctl). It seems something related to usb.
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!