X crashes sometimes at random, leaving the user in command mode, having lost any work in open applications. This happened twice. Both times while typing (but not clear if that is related to the crashes).
You'll need to provide a lot more information for this bug report to be useful. Things to look at: /var/log/Xorg.0.log /var/log/Xorg.0.log.old ~/.xsession-errors (for the user that was logged in) journalctl -b Try to find some information that can narrow down the cause of the crash. If you can find a stack trace, that'd be great.
Keywords: (none) => NEEDINFO
If you still remember at what time and date those X crashes happened: there might be something related in the journalctl logs from just before and around that time ("journalctl -b" only shows the logs since last time the system was booted). Try (with adjusted times + date) as root: journalctl -a --since="2016-07-21 10:15" --until="2016-07-21 10:30" > log.txt and attach log.txt to this report if there's anything in it that might be useful. That doesn't replace the information asked for in Comment #1, though! This can't be a release blocker, unless it happens a lot with Mga6 sta1 or RC Live isos in Live mode, because for all other cases it can be fixed with an update.
Priority: release_blocker => NormalCC: (none) => marja11
Created attachment 8227 [details] Full output of journalctl
Created attachment 8228 [details] targeted output of journalctl (about 10 minutes before till 2 minutes after the crash)
Created attachment 8229 [details] Xorg.0.log
Created attachment 8230 [details] Xorg.0.log.old
Created attachment 8231 [details] xsession-errors
All requested info in the files attached. If it is only me having this problem, then it might indeed not be a release blocker. Since I'm using Mga6 on a brand new laptop, that is certainly a possibility. But if others have the same experience, I think it should better be fixed: 6 crashes in 1 day is not going to give a good image of the distro.
Comment on attachment 8230 [details] Xorg.0.log.old (changing attachment type to text/plain, so it can be seen in a browser)
Attachment 8230 mime type: application/x-trash => text/plain
Thanks, Wim @ Nicolas Do you mind having a look, and reassigning if needed?
Keywords: NEEDINFO => (none)Assignee: bugsquad => mageia
Summary: Random X crashes => Random X crashes in Plasma5
seems more a kernel or driver issue to me.
(In reply to Nicolas Lécureuil from comment #11) > seems more a kernel or driver issue to me. Thx. Guessing it's kernel and reassigning to tmb, then. @ tmb Sorry for assigning yet another bug to you of which I don't know whether you're the maintainer of the package that's the real culprit. Please reassign if needed.
Assignee: mageia => tmb
Might be related to bug 18822. Do you input accented characters when it crashes?
Up till now it happened each time during typing. Not really when entering accented characters, but often when entering special characters. Also I"m typing on a physical Qwerty keyboard with Azerty layout settings (I'm used to blind typing on Azerty).
Just tried the ⬠and é characters. No problem when I type them according to the other bug, that would lead immediately to a crash. So I suppose it is not related after all. In my case I have not yet found out how to surely trigger a crash.
Could you try again with a fully updated Cauldron Wim? It seems that we had a major Xorg update on July 22nd, and all its reverse dependencies/drivers still needed to be rebuilt, what was done yesterday by tmb. On my end it fixed the crashes I was experiencing.
OK, I did a full update of my system. Will take a while to be sure if that solves the problem though, as I have no sure trigger to reproduce a crash. So confirming that the issue is definitely solved is a matter of waiting long enough going without crashes I guess.
Not yet fixed. Just had another crash. Again while typing, but this time in Thunderbird, not in Chrome.
CC: (none) => guichard.adrien
OK, found out what is the culprit and how to reproduce: I have a consistent crash when I use the key with the "0" on the row with the numbers, but not if I use it for typing a "0" but when typing the other character. As I have a Dutch qwerty keyboard, but I'm used to type on a Belgian azerty keyboard, I tested with both layouts, and it does it both with the "(" character in the Dutch qwerty layout and the "Ã " in the Belgian azerty layout. It also seems the be consistent over any X based situation: in the logon screen, in KDE, in Gnome, with the keyboard of the laptop but also with an external keyboard. Obviously nothing happens in tty, it is only X which crashes.
Further testing shows that this now happens also with the "â¬" and "é" characters, which did not give issues during my tests of 23/07. This is on a fully Cauldron updated system up to today. Also the "è" character seems to trigger the crash now. So now it looks like the same bug as bug 18822.
At this moment I can happiliy type à é ⬠ç and so on without X crashing on me, so I guess that the bug has been solved with one of the more recent updates. I've put the status on resolved.
Status: NEW => RESOLVEDResolution: (none) => FIXED