Archives/cdm
2
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Updates cdm's call to startx to be compatible with Xorg 1.16.

Browse Source 
In the Xorg 1.16 notes at:

  https://www.archlinux.org/news/xorg-server-116-is-now-available/

it mentions that X "must be launched from the same virtual terminal as was used
to log in"; therefore, cdm now launches, by default, on the same VT.

"...redirecting stderr also breaks rootless login"; therefore, cdm no longer
saves stderr. All the Xorg output should be available in is already available in
logs:

  ~/.local/share/xorg/
This commit is contained in:
Ben Pence 2014-08-02 10:45:16 -04:00
parent c2255fd12a
commit 87e3ce54e4
2 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
src/cdm-xlaunch
View File

@ -87,9 +87,9 @@ fi
if $altstartx; then if $altstartx; then
# Alternative method of calling setsid(/startx) for systems that are unresponsive to the 'normal' call. # Alternative method of calling setsid(/startx) for systems that are unresponsive to the 'normal' call.
(setsid startx "$@" > "$startxlog" 2>&1) (startx "$@" > "$startxlog"
else else
setsid startx "$@" > "$startxlog" 2>&1 startx "$@" > "$startxlog"
fi fi
# If wait(1) returns with a value >128, it was interrupted by kill(1), # If wait(1) returns with a value >128, it was interrupted by kill(1),

2
src/cdmrc
View File

@ -41,7 +41,7 @@ display=0
# Where should the first X tty be spawned? # Where should the first X tty be spawned?
# special value `keep' causes to run X in current tty. # special value `keep' causes to run X in current tty.
xtty=7 xtty=keep
# Should cdm(1) stick to the specified display? # Should cdm(1) stick to the specified display?
locktty=no locktty=no