English
Ask Your Question
3

Fedora 27 freezes after login

asked 2017-12-07 05:00:04 +0000

mlaz7 gravatar image

updated 2017-12-09 03:05:01 +0000

Occasionally, after selecting my username, entering password and clicking login, i get stuck at a frozen gray screen which doesn't respond to any input. I'm running fedora 27 on gnome with wayland disabled and using the nvidia drivers for a gtx1060. On the occasions that this doesn't happen, everything seems to be working great. When it does, I have to power off computer with the power button and power back on. Any ideas what could cause this behavior??

OK, probably should have done this from the start, but below are my /var/log/Xorg.1.log and /var/log/Xorg.1.log.old. I noticed some weird got pause messages from systemd-logind in the .old file, but I'm not really sure what to make of these. Hopefully someone can use this info to help me narrow down a cause. (Sorry, I can't attach files, so these are just incredibly long blocks of code......)

Xorg.1.log:


[    13.844] _XSERVTransSocketUNIXCreateListener: ...SocketCreateListener() failed
[    13.844] _XSERVTransMakeAllCOTSServerListeners: server already running
[    13.844] (--) Log file renamed from "/var/log/Xorg.pid-1437.log" to "/var/log/Xorg.1.log"
[    13.844] 
X.Org X Server 1.19.5
Release Date: 2017-10-12
[    13.844] X Protocol Version 11, Revision 0
[    13.844] Build Operating System:  4.12.9-300.fc26.x86_64 
[    13.845] Current Operating System: Linux Mike-Laptop 4.13.16-302.fc27.x86_64 #1 SMP Thu Nov 30 15:33:36 UTC 2017 x86_64
[    13.845] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.13.16-302.fc27.x86_64 root=UUID=c71e3b1d-4bb4-483b-8c33-616a59502613 ro rd.driver.blacklist=nouveau modprobe.blacklist=nouveau nvidia-drm.modeset=1 rhgb quiet LANG=en_US.UTF-8 elevator=deadline
[    13.845] Build Date: 12 October 2017  07:35:27PM
[    13.845] Build ID: xorg-x11-server 1.19.5-1.fc27 
[    13.845] Current version of pixman: 0.34.0
[    13.845]    Before reporting problems, check http://wiki.x.org
    to make sure that you have the latest version.
[    13.845] Markers: (--) probed, (**) from config file, (==) default setting,
    (++) from command line, (!!) notice, (II) informational,
    (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[    13.845] (==) Log file: "/var/log/Xorg.1.log", Time: Fri Dec  8 18:48:50 2017
[    13.845] (==) Using config directory: "/etc/X11/xorg.conf.d"
[    13.845] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[    13.845] (==) No Layout section.  Using the first Screen section.
[    13.845] (==) No screen section available. Using defaults.
[    13.845] (**) |-->Screen "Default Screen Section" (0)
[    13.845] (**) |   |-->Monitor "<default monitor="">"
[    13.845] (==) No monitor specified for screen "Default Screen Section".
    Using a default monitor configuration.
[    13.845] (==) Automatically adding devices
[    13.845] (==) Automatically enabling devices
[    13.845] (==) Automatically adding GPU devices
[    13.845] (==) Automatically binding GPU devices
[    13.845] (==) Max clients allowed: 256, resource mask: 0x1fffff
[    13.845] (==) FontPath set to:
    catalogue:/etc/X11/fontpath.d,
    built-ins
[    13.845] (==) ModulePath set to "/usr/lib64/xorg/modules"
[    13.845] (II) The server relies on udev to provide the list of input devices.
    If no devices become available ...
(more)
edit retag flag offensive close merge delete

Comments

1

Use a terminal via ctl-F2, look in the /var/log/messages log and /var/log/X.org.log. Try another desktop manager, e.g., LightDM, KDM.

robbiethek ( 2017-12-07 20:42:46 +0000 )edit

On one of the times that it does work, have you examined previous logs, to see what might be causing the strange behaviour?

steveebey73742 ( 2017-12-07 23:16:33 +0000 )edit

I have the exact same problem with a very similar scenario. I bought a new motherboard and CPU so decided to reinstall F27 from scratch after doing a back up of home and other important files. The also am using the nvidia drivers from rpmfusion. I have found that if I remove 'rhbg' by editing the grub boot string that I do get get the freezes. If the freeze happens, both the keyboard and mouse become inoperative with the OS so opening a terminal is not possible.

brad ( 2017-12-17 20:09:47 +0000 )edit

1 answer

Sort by ยป oldest newest most voted
2

answered 2017-12-11 20:37:37 +0000

mlaz7 gravatar image

So, I switched to LightDM, and after a few days of use, still no freezing. The issue seems to be with GDM, however I actually really like LightDM. I have always used GDM and never knew what I was missing. The ease with which you can customize LightDM is Awesome!!! So, for me, switching the DM is an acceptable solution. Still unsure what caused the issue in GDM in the first place, but I'm happy just not using GDM. Thanks for the suggestions guys!!

edit flag offensive delete link more

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

[hide preview]

Use your votes!

  • Use the 30 daily voting points that you get!
  • Up-vote well framed questions that provide enough information to enable people provide answers.
  • Thank your helpers by up-voting their comments and answers. If a question you asked has been answered, accept the best answer by clicking on the checkbox on the left side of the answer.
  • Down-voting might cost you karma, but you should consider doing so for incorrect or clearly detrimental questions and answers.

Question Tools

Follow
2 followers

Stats

Asked: 2017-12-07 05:00:04 +0000

Seen: 80 times

Last updated: Dec 11