Hide Forgot
Created attachment 1225220 [details] output of "journalctl -b -1 -n 300" Description of problem: Pretyy unpredictably, but quite often (twice a day), the X server crashes. I'm left with black monitors and I'm unable to switch to another virtual console (CTRL+ALT+F2), so I have to restart computer. There is nothing in abrt (/var/spool/abrt is empty). Only thing I noticed is, that I think everytime it crashes I'm currently moving with mouse cursor. Environment: Fedora 25. Thinkpad T440s with integrated Intel graphic, It only noticed this bug when the notebook was in docking station with two external monitors attached. My second workplace has this notebook only with one external monitor without docking station (and i DIDN'T experience that bug there, so there is very high probability it has to do something either with docking station OR two external monitors) Version-Release number of selected component (if applicable): I noticed this behavior somewhere during F25 beta phase. I thougth it would go away with fresh install of Fedora 25 final. Now I have F25 Final (KDE spin) installed to empty drive (clean system), but this bug is still there. Note, that I was using F24 with exactly same setup (monitors, docking station) and this bug did not happen there. How reproducible: Probably twice a day with described setup (docking station & two external monitors). Seems completely random. Only common thing I noticed is that the mouse was currently moving (but this could be a coincidence) Additional info: As I said ABRT is empty, but I'll put output of "journalctl -b -1 -n 300" as attachment che crash happens around "Nov 28 10:38:01" in this output. If there is some way I could provide you more info, please let me know. I'm very interested in helping to solve this bug, because crashing system 2-3 times a day is very annoying.
I can't find the relevant backtrace for Xorg in attachment 1225220 [details] Please also attach the Xorg logs ~/.local/share/xorg/Xorg.0.log and tell the exact version for the package you're using.
Created attachment 1225237 [details] xorg log from /var/log/Xorg.0.log.old This log should be from previous boot i guess? (The one where X crashed)
Created attachment 1225238 [details] xorg pacakges version
I don't have xorg folder in ~/.local/share/ so I attached the output from /var/log/xorg/
Created attachment 1225240 [details] output of `lspci -nn`
Unfortunately attachment 1225238 [details] doesn't contain a backtrace either so it doesn't help much.
Sorry, I meant attachment 1225237 [details]
Is there any way I can turn on debug logging or something like this? Something that will help me get a better stacktrace for you when this crash happens next time?
(In reply to Radim Hopp from comment #8) > Is there any way I can turn on debug logging or something like this? > Something that will help me get a better stacktrace for you when this crash > happens next time? It must be somewhere in the logs... Without any indication of what caused the crash, you may try with the "modesetting" driver instead of the "intel" driver, that would rule out a bug in the "intel" driver.
(In reply to Radim Hopp from comment #8) > Is there any way I can turn on debug logging or something like this? > Something that will help me get a better stacktrace for you when this crash > happens next time? Run the command gnome-abrt. This will open Problem Reporting, which will list past crashes, including those for xorg-x11-server. You'll also be able to report to Bugzilla, or get a link to the already-reported bug.
Once you're in Problem Reporting, right click the crash on the left, and click Open problem's data directory. In a terminal, cd to that directory, and run the command below. gdb $(cat executable) -c coredump It might ask you to run a dnf command. If it does, run it, and try again. Then, run these on the gdm prompt. (gdb) bt (gdb) bt full (gdb) info threads (gdb) thread apply all bt (gdb) thread apply all bt full
This message is a reminder that Fedora 25 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 25. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '25'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 25 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.