Path: csiph.com!v102.xanadu-bbs.net!xanadu-bbs.net!feeder.erje.net!eu.feeder.erje.net!weretis.net!feeder4.news.weretis.net!eternal-september.org!feeder.eternal-september.org!mx02.eternal-september.org!.POSTED!not-for-mail From: Unknown Newsgroups: comp.os.linux.misc,alt.os.linux.slackware,alt.os.linux.debian Subject: Re: Can different-users have different-X? Date: Sun, 28 Dec 2014 06:04:27 +0000 (UTC) Organization: A noiseless patient Spider Lines: 83 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Injection-Date: Sun, 28 Dec 2014 06:04:27 +0000 (UTC) Injection-Info: mx02.eternal-september.org; posting-host="09420d015ba3eb679bc9e581e3e10353"; logging-data="15568"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1/n01P3xdS2IVyRrGgnqQw0jnu72MYdaFs=" User-Agent: Pan/0.133 (House of Butterflies) Cancel-Lock: sha1:kDZmRrHHlpTBcdcSbwLtPfrlXbo= Xref: csiph.com comp.os.linux.misc:13116 On Wed, 08 Oct 2014 14:34:28 +0200, Øyvind Røtvold wrote: > not.socialnetwork@gmail.com writes: > > [ snip ] >> >> The error is >> >> What am I doing wrong? > > You're trying to start a server at display 0, the default, and there's > already one running there. > > This should work: > > xinit -- :1 & > DISPLAY=:1 xterm My log syntax: -> what I input; == the resulting output; => observation => This log now in VT3 => in VT4 -> xinit -- :1 & == drip under pressure. ~:xinit -- :1 & [1] 5802 ~: entering d=X ? why did blok of: `cat << ` cause HANGING ? ready to continue after intro-trace of d [now copied to X] ? = /usr/local/sbin/X: line 5: read: read error: 0: Input/output error numbered lines of Partns:- waiting for X server to begin accepting connections . .. .. .. ..... Needs Ctrl/D to: ..logout => in VT5 -> 1 xterm == Warning: This program is an suid-root program or is being run by the root user. The full text of the error or warning message cannot be safely formatted in this environment. You may get a more descriptive message by running the program as a non-root user or by removing the suid bit on the executable. xterm Xt error: Can't open display: %s -> pstree | grep x == |-bash---startx---xinit-+-X | `-blackbox-+-bbkeys .... => So the original X seems to have survived. Yes, I'm now in X. ------------------------------------------------- > >> Can I change the font-server settings, and still recover my work? Is it >> possible that after the system boots, it's OK; but exercising various >> programs, changes some font-setting, which then makes xpdf ...etc. >> fuzzy? > > You can do a 'xrdb -query' after startup, save the result and try to > reset to that result later with eg. 'xrdb -remove', 'xrdb -merge'. ==> Save result NOW [in bad state] -> xrdb -query ==xrdb: Can't open display <- OK ? try in X => Now in X -> xrdb -query == no output -> xrdb -h == -> xrdb -query == no output -> xrdb -screens == no *RETURN* => 10 minutes later need ^C to ------------------- end of log of failed-tests ----------- Thanks. PS. An excelent article by David Davidovic @ http://tutplus.com points to problems. But how it could start OK, and later change to BAD is a mystery for me. BTW there's 2 problems here: 1. xpdf ..etc BECOMES badly displayed after OK when initially run-X. 2. It would be interesting to keep the initial X, and experiment with others, at the same time.