Bug 108475 - X server freezes when switched to runlevel 5 from 3
Summary: X server freezes when switched to runlevel 5 from 3
Status: RESOLVED MOVED
Alias: None
Product: xorg
Classification: Unclassified
Component: Server/General (show other bugs)
Version: unspecified
Hardware: x86-64 (AMD64) Linux (All)
: medium major
Assignee: Xorg Project Team
QA Contact: Xorg Project Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-10-18 04:23 UTC by Hakan Duran
Modified: 2018-12-13 22:41 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:


Attachments
Screen image capture of the output of "journalctl -e --user" command at the time of X server freeze while logging in to KDE5 (1.10 MB, image/jpeg)
2018-10-18 04:23 UTC, Hakan Duran
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Hakan Duran 2018-10-18 04:23:30 UTC
Created attachment 142076 [details]
Screen image capture of the output of "journalctl -e --user" command at the time of X server freeze while logging in to KDE5

I use the following commands on Manjaro Linux to switch to runlevel 3, also known as multi-user.target in systemd language:
sudo systemctl set-default multi-user.target
sudo systemctl isolate multi-user.target
This causes no problem. To switch back to runlevel 5 (graphical.target) the following commands are used:
sudo systemctl set-default graphical.target
sudo systemctl isolate graphical.target
This effectively launces SDDM on tty1 as expected. However, loging in to KDE5 is not possible. Graphical display on tty1 freezes before KDE5 is launched. It is essentially a black screen with a responsive but useless mouse cursor. tty2-6 are still usable as CLI. From tty2 I can get the following error message (see attached screen image) by issuing the command "journalctl -e --user".
Suspecting nvidia module/driver to be the culprit, I switched to nouveau driver, but the problem persisted, although I was able to launch i3 with this change (KDE5 would still not launch and would produce similar errors as attached).
This is 100% reproducible so far.
Comment 1 GitLab Migration User 2018-12-13 22:41:00 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/xorg/xserver/issues/549.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.