LightDM launching new Xorg process (in a new VT) after every resume from suspend

Bug #1608264 reported by Ryan
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Light Display Manager
New
Undecided
Unassigned

Bug Description

It appears that whenever a suspend/resume cycle occurs (close/open lid on laptop), LightDM launches a new Xorg process in a new VT before re-activating the original process on VT7. This causes a noticeable delay in being able to login with the greeter and causes the screen brightness to change before going back to what it should be set at.

LightDM version - 1.18.2-2

Attached is the lightdm log, and here is the output of ps showing the different processes.

[ryan@thinkpad : ~/Desktop] ps aux | grep Xorg
root 493 0.0 0.5 391852 68980 tty7 Ssl+ Jul30 0:44 /usr/lib/xorg-server/Xorg :0 -seat seat0 -auth /run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
root 1629 0.0 0.3 254272 41128 tty8 Ssl+ Jul30 0:00 /usr/lib/xorg-server/Xorg :1 -seat seat0 -auth /run/lightdm/root/:1 -nolisten tcp vt8 -novtswitch
root 2145 0.0 0.3 254288 41168 tty9 Ssl+ Jul30 0:00 /usr/lib/xorg-server/Xorg :2 -seat seat0 -auth /run/lightdm/root/:2 -nolisten tcp vt9 -novtswitch
root 2624 0.0 0.3 254272 41448 tty10 Ssl+ Jul30 0:00 /usr/lib/xorg-server/Xorg :3 -seat seat0 -auth /run/lightdm/root/:3 -nolisten tcp vt10 -novtswitch
root 3726 0.0 0.3 262372 41220 tty11 Ssl+ 00:45 0:00 /usr/lib/xorg-server/Xorg :4 -seat seat0 -auth /run/lightdm/root/:4 -nolisten tcp vt11 -novtswitch
root 4205 0.0 0.3 254272 41648 tty12 Ssl+ 00:52 0:00 /usr/lib/xorg-server/Xorg :5 -seat seat0 -auth /run/lightdm/root/:5 -nolisten tcp vt12 -novtswitch
root 4624 0.0 0.3 254288 41396 tty13 Ssl+ 00:58 0:06 /usr/lib/xorg-server/Xorg :6 -seat seat0 -auth /run/lightdm/root/:6 -nolisten tcp vt13 -novtswitch
root 11541 0.0 0.3 254704 41752 tty14 Ssl+ 14:41 0:00 /usr/lib/xorg-server/Xorg :7 -seat seat0 -auth /run/lightdm/root/:7 -nolisten tcp vt14 -novtswitch

Let me know if there is any info or logs that are required to investigate this issue.

Revision history for this message
Ryan (rylinaux) wrote :
Revision history for this message
Ryan (rylinaux) wrote :

Here is the output from ps, formatted a little nicer than in the original post.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.