Re: Xorg fails, no gui: systemd issue?

On Sun, Dec 10, 2023 at 12:57:59AM +0100, Anders Andersson wrote: > On Sat, Dec 9, 2023 at 3:01 AM Andrew M.A. Cater wrote: > > > > On Fri, Dec 08, 2023 at 06:13:59PM +, John - wrote: > > > Since I last (3 December) upgraded the software (sid) on my old > > > Thinkpad, my gui fails to come u

Re: Xorg fails, no gui: systemd issue?

Hello, On Sun, Dec 10, 2023 at 12:57:59AM +0100, Anders Andersson wrote: > On Sat, Dec 9, 2023 at 3:01 AM Andrew M.A. Cater wrote: > > Today is the 8th of December - strictly, that's barely a business week. > > > > Debian expressly comes with no guarantees. You are running sid a.k.a > > unstable

Re: Xorg fails, no gui: systemd issue?

On Sat, Dec 9, 2023 at 3:01 AM Andrew M.A. Cater wrote: > > On Fri, Dec 08, 2023 at 06:13:59PM +, John - wrote: > > Since I last (3 December) upgraded the software (sid) on my old Thinkpad, > > my gui fails to come up. The last line of /var/log/Xorg.0.log reads: > > (EE) systemd-login: faile

Re: Xorg fails, no gui: systemd issue?

Thanks for answering and thanks for the advice, most of which I agree with, since I've been running sd since 2006.Since I am now 84, I'm not as good at figuring things out as I used to be, so if anyone else can offer help, I'd be grateful. On Friday, December 8, 2023 at 03:36:19 PM EST, And

Re: Xorg fails, no gui: systemd issue?

On Fri, Dec 08, 2023 at 06:13:59PM +, John - wrote: > Since I last (3 December) upgraded the software (sid)  on my old Thinkpad, my > gui fails to come up. The last line of /var/log/Xorg.0.log reads: > (EE) systemd-login: failed to take device /dev/dri/card0: Message recipient > disconnected

Re: XOrg issues with Rage 128 Ultra graphics: No screens found.

On 10/18/2021 07:50 PM, Alex McKeever wrote: > Essentially, my screen can be found (I have an iMac G3 in which I’ve ran Sid > on)… however it can’t find any usable configurations, and manually generating > an XOrg configuration (editing it to give certain options) doesn’t help. Is > this an XOrg

Re: Xorg fatal server error segmentation fault i686

Richmond composed on 2021-05-05 12:49 (UTC+0100): > I installed debian on an old PC i686. I chose the mate desktop. When I > tried to log in throught display manager I could not, so: > I closed X down with telinit 3 > I logged in on the console as root > I ran xinit -- :0 > I switched to a non ro

Re: Xorg fatal server error segmentation fault i686

Dan Ritter writes: > Richmond wrote: >> I installed debian on an old PC i686. I chose the mate desktop. When I >> tried to log in throught display manager I could not, so: >> >> I closed X down with telinit 3 >> I logged in on the console as root >> I ran xinit -- :0 >> I switched to a non root

Re: Xorg fatal server error segmentation fault i686

On Wed, 05 May 2021 18:36:50 +0100 Richmond wrote: Hello Richmond, >package called nvidia-detect for this architecture. Oops, I'm sorry - you're right - I didn't check properly. Again, sorry about getting your hopes up. -- Regards _ / ) "The blindingly obvious is

Re: Xorg fatal server error segmentation fault i686

Brad Rogers writes: > On Wed, 05 May 2021 15:31:25 +0100 > Richmond wrote: > > Hello Richmond, > >>01:00.0 VGA compatible controller [0300]: NVIDIA Corporation NV11 >>[GeForce2 MX/MX 400] [10de:0110] (rev b2) > > As mentioned by Greg; > > On Wed, 5 May 2021 11:14:44 -0400 > Greg Wooledge wrote:

Re: Xorg fatal server error segmentation fault i686

Dan Ritter writes: > Richmond wrote: >> Dan Ritter writes: >> >> > Richmond wrote: >> >> I installed debian on an old PC i686. I chose the mate desktop. When I >> >> tried to log in throught display manager I could not, so: > ... >> >> What can I do? Perhaps use a different xserver. The displ

Re: Xorg fatal server error segmentation fault i686

On Wed, 05 May 2021 15:31:25 +0100 Richmond wrote: Hello Richmond, >01:00.0 VGA compatible controller [0300]: NVIDIA Corporation NV11 >[GeForce2 MX/MX 400] [10de:0110] (rev b2) As mentioned by Greg; On Wed, 5 May 2021 11:14:44 -0400 Greg Wooledge wrote: >Or else look for this nvidia detection

Re: Xorg fatal server error segmentation fault i686

On Wed, May 05, 2021 at 03:31:25PM +0100, Richmond wrote: > > 1) Identify your video hardware. Use "lspci -nn" for this. > > 01:00.0 VGA compatible controller [0300]: NVIDIA Corporation NV11 > [GeForce2 MX/MX 400] [10de:0110] (rev b2) OK. This is... a rather old device.

Re: Xorg fatal server error segmentation fault i686

Greg Wooledge writes: > On Wed, May 05, 2021 at 08:20:21AM -0400, Dan Ritter wrote: >> As your non-root user, write a .xinitrc: >> >> #!/bin/sh >> xterm & >> exec mate-session >> >> and then run >> >> startx >> >> Tell us what happens then. If it crashes, let us see your >> /etc/apt/sources.l

Re: Xorg fatal server error segmentation fault i686

Richmond wrote: > Dan Ritter writes: > > > Richmond wrote: > >> I installed debian on an old PC i686. I chose the mate desktop. When I > >> tried to log in throught display manager I could not, so: ... > >> What can I do? Perhaps use a different xserver. The display driver is > >> nouveau. > >

Re: Xorg fatal server error segmentation fault i686

Scrap the previous /etc/apt/sources I forgot I was using ssh into a different pc. cat /etc/apt/sources.list # # deb cdrom:[Debian GNU/Linux 10.9.0 _Buster_ - Official i386 DVD Binary-1 20210327-10:50]/ buster contrib main # deb cdrom:[Debian GNU/Linux 10.9.0 _Buster_ - Official i386 DVD Binary

Re: Xorg fatal server error segmentation fault i686

Richmond writes: > I installed debian on an old PC i686. I chose the mate desktop. When I > tried to log in throught display manager I could not, so: > > I closed X down with telinit 3 > I logged in on the console as root > I ran xinit -- :0 > I switched to a non root user in the xterm window on

Re: Xorg fatal server error segmentation fault i686

On Wed, May 05, 2021 at 08:20:21AM -0400, Dan Ritter wrote: > As your non-root user, write a .xinitrc: > > #!/bin/sh > xterm & > exec mate-session > > and then run > > startx > > Tell us what happens then. If it crashes, let us see your > /etc/apt/sources.list and anything in sources.list.d/ I

Re: Xorg fatal server error segmentation fault i686

Richmond wrote: > I installed debian on an old PC i686. I chose the mate desktop. When I > tried to log in throught display manager I could not, so: > > I closed X down with telinit 3 > I logged in on the console as root > I ran xinit -- :0 > I switched to a non root user in the xterm window on t

Re: Xorg: symbol lookup error: "/usr/lib/xorg/modules/drivers/radeon_drv.so": undefined symbol: "exaGetPixmapDriverPrivate"

On 2019-11-06, coolnodje wrote: > > The computer I run it on has a ATI Radeon FireGL V3100 graphic card. > > Launching an X environment invariably produce this error : > > Xorg: symbol lookup error: > "/usr/lib/xorg/modules/drivers/radeon_drv.so": undefined symbol: > "exaGetPixmapDriverPrivate" >

Re: xorg version in Buster

On Sat 27 Apr 2019 at 12:17:42 (-0400), Felix Miata wrote: > Paul Sutton composed on 2019-04-27 17:07 (UTC+0100): > > > According to https://packages.debian.org/source/buster/xorg-server the > > version of x-org supplied with Buster is 2:1.20.3.1  is this correct or > > is the actual version numbe

Re: xorg version in Buster

On 27/04/2019 17:07, Paul Sutton wrote: > Hi > > According to https://packages.debian.org/source/buster/xorg-server the > version of x-org supplied with Buster is 2:1.20.3.1  is this correct or > is the actual version number hidden in there somewhere.  I am not sure > how to interpret the number (

Re: xorg version in Buster

Paul Sutton composed on 2019-04-27 18:04 (UTC+0100): > Cool thanks so it look like 1.20.3-1  Depending on your audience, you might wish to use that which is likely to be experienced outside the package management system: > head -n2 /var/log/Xorg.0.log | grep Server X.Org X Server 1.20.3 > inxi -

Re: xorg version in Buster

On 27/04/2019 17:17, Felix Miata wrote: > Paul Sutton composed on 2019-04-27 17:07 (UTC+0100): > >> According to https://packages.debian.org/source/buster/xorg-server the >> version of x-org supplied with Buster is 2:1.20.3.1  is this correct or >> is the actual version number hidden in there som

Re: xorg version in Buster

Paul Sutton composed on 2019-04-27 17:07 (UTC+0100): > According to https://packages.debian.org/source/buster/xorg-server the > version of x-org supplied with Buster is 2:1.20.3.1  is this correct or > is the actual version number hidden in there somewhere.  I am not sure > how to interpret the nu

Re: xorg opengl / intel integrated graphics problem

So, apparently apt remove --purge nvidia* is not enough to clean the opengl mess nvidias drivers left. Manually removing the files nvidia replaced and reinstalling xorg and mesa as described in this answer did: https://unix.stackexchange.com/a/339652 Thanks for your help 24. März 2019 23:34, t...

Re: xorg opengl / intel integrated graphics problem

t...@t8w.de wrote: > due to a graphics card change in a few days, which will allow me to > properly use virtualization, I wanted to check a few things. First check, > starting the pc without the current dedicated graphics card, failed really > unexpectedly, because the integrated graphics card of

Re: Xorg log file filling up with error

On Tue, 18 Sep 2018, Frank McCormick wrote: > Date: Tue, 18 Sep 2018 14:06:17 > From: Frank McCormick > To: debian-user@lists.debian.org > Subject: Re: Xorg log file filling up with error > Resent-Date: Tue, 18 Sep 2018 18:06:49 + (UTC) > Resent-From: debian-user@lists.deb

Re: Xorg log file filling up with error

On 9/18/18 3:58 AM, Jude DaShiell wrote: On Mon, 17 Sep 2018, Frank McCormick wrote: Date: Mon, 17 Sep 2018 15:44:16 From: Frank McCormick To: debian-user@lists.debian.org Subject: Xorg log file filling up with error Resent-Date: Mon, 17 Sep 2018 19:59:39 + (UTC) Resent-From: debian-use

Re: Xorg log file filling up with error

On Mon, 17 Sep 2018, Frank McCormick wrote: > Date: Mon, 17 Sep 2018 15:44:16 > From: Frank McCormick > To: debian-user@lists.debian.org > Subject: Xorg log file filling up with error > Resent-Date: Mon, 17 Sep 2018 19:59:39 + (UTC) > Resent-From: debian-user@lists.debian.org > > Just noticed

Re: Xorg replaces TTY1

Felix Miata [2015-12-02 01:52:18-05] wrote: > /etc/X11/xorg.conf.d/00-keyboard.conf always works for me: > > Section "InputClass" > Identifier "system-keyboard" > Option "XkbOptions" "terminate:ctrl_alt_bksp" > EndSection I think /etc/default/keyboard is a

Re: Xorg replaces TTY1

Martin Str|mberg composed on 2015-12-02 07:39 (UTC+0100): > Chris Bannister wrote: >> On Thu, Nov 26, 2015 at 06:54:34PM +, Brian wrote: >> > There are still users (an example is in >> > this thread) who believe ctrl-alt-backspace no longer works in Debian. >> > It does. >> So it does! Wond

Re: Xorg replaces TTY1

In article Chris Bannister wrote: > On Thu, Nov 26, 2015 at 06:54:34PM +, Brian wrote: > > There are still users (an example is in > > this thread) who believe ctrl-alt-backspace no longer works in Debian. > > It does. > So it does! Wonder why it didn't work for me on another machine. :( I

Re: Xorg replaces TTY1

Lisi Reisz wrote: > That is a real question. $USER doesn't appear to need root rights to > access a different VT. I wrote: > Input to an un-logged-in active VT is collected by a copy of getty > running as root. Neal writes: > If there's a getty running on it. Thus "active" VT. > If you have re

Re: Xorg replaces TTY1

On Mon, 30 Nov 2015 11:01:07 -0600 John Hasler wrote: > Lisi Reisz wrote: > > That is a real question. $USER doesn't appear to need root rights to > > access a different VT. > > Input to an un-logged-in active VT is collected by a copy of getty > running as root. If there's a getty running on

Re: Xorg replaces TTY1

Lisi Reisz wrote: > That is a real question. $USER doesn't appear to need root rights to > access a different VT. Input to an un-logged-in active VT is collected by a copy of getty running as root. man getty -- John Hasler jhas...@newsguy.com Elmwood, WI USA

Re: Xorg replaces TTY1

On 2015-11-28, Lisi Reisz wrote: > On Saturday 28 November 2015 10:18:16 Vincent Lefevre wrote: >> X needs root rights to access a different VT > > Why? > > That is a real question. $USER doesn't appear to need root rights to > access a different VT. You, sitting at the keyboard, are not a pro

Re: Xorg replaces TTY1

On Sat 28 Nov 2015 at 17:07:13 +, Brian wrote: > On Sun 29 Nov 2015 at 04:27:59 +1300, Chris Bannister wrote: > > > On Sat, Nov 28, 2015 at 11:18:16AM +0100, Vincent Lefevre wrote: > > > On 2015-11-28 21:16:20 +1300, Chris Bannister wrote: > > > > On Fri, Nov 27, 2015 at 12:10:01PM +, Bri

Re: Xorg replaces TTY1

On Sun 29 Nov 2015 at 04:27:59 +1300, Chris Bannister wrote: > On Sat, Nov 28, 2015 at 11:18:16AM +0100, Vincent Lefevre wrote: > > On 2015-11-28 21:16:20 +1300, Chris Bannister wrote: > > > On Fri, Nov 27, 2015 at 12:10:01PM +, Brian wrote: > > > > On Fri 27 Nov 2015 at 18:29:20 +1300, Chris

Re: Xorg replaces TTY1

On Sat, Nov 28, 2015 at 11:18:16AM +0100, Vincent Lefevre wrote: > On 2015-11-28 21:16:20 +1300, Chris Bannister wrote: > > On Fri, Nov 27, 2015 at 12:10:01PM +, Brian wrote: > > > On Fri 27 Nov 2015 at 18:29:20 +1300, Chris Bannister wrote: > > > > > > > On Wed, Nov 25, 2015 at 06:40:00PM +00

Re: Xorg replaces TTY1

On Saturday 28 November 2015 13:06:09 Brian wrote: > As Vincent Lefevre said, root privileges are needed to access a vt other > than the one startx is used on. There's a hole in my bucket, dear Eliza... Lisi

Re: Xorg replaces TTY1

On Sat 28 Nov 2015 at 12:27:01 +, Lisi Reisz wrote: > On Saturday 28 November 2015 10:48:00 Nicolas George wrote: > > L'octidi 8 frimaire, an CCXXIV, Lisi Reisz a écrit : > > > I can access a plethora of VTs without changing to root. > > > > You, as far as I know, are a human being, not a Linu

Re: Xorg replaces TTY1

On Saturday 28 November 2015 10:48:00 Nicolas George wrote: > L'octidi 8 frimaire, an CCXXIV, Lisi Reisz a écrit : > > I can access a plethora of VTs without changing to root. > > You, as far as I know, are a human being, not a Linux process. You do not > access VTs, you access computer keyboards t

Re: Xorg replaces TTY1

L'octidi 8 frimaire, an CCXXIV, Lisi Reisz a écrit : > I can access a plethora of VTs without changing to root. You, as far as I know, are a human being, not a Linux process. You do not access VTs, you access computer keyboards that allow you to control VTs through the courtesy of the getty progr

Re: Xorg replaces TTY1

On Saturday 28 November 2015 10:41:39 Nicolas George wrote: > L'octidi 8 frimaire, an CCXXIV, Lisi Reisz a écrit : > > $USER doesn't appear to need root rights to access a different VT. > > Can you explain how you came to that conclusion? > > Regards, I can access a plethora of VTs without changin

Re: Xorg replaces TTY1

L'octidi 8 frimaire, an CCXXIV, Lisi Reisz a écrit : > $USER doesn't appear to need root rights to access a different VT. Can you explain how you came to that conclusion? Regards, -- Nicolas George signature.asc Description: Digital signature

Re: Xorg replaces TTY1

On Saturday 28 November 2015 10:18:16 Vincent Lefevre wrote: > X needs root rights to access a different VT Why? That is a real question. $USER doesn't appear to need root rights to access a different VT. Lisi

Re: Xorg replaces TTY1

On 2015-11-28 21:16:20 +1300, Chris Bannister wrote: > On Fri, Nov 27, 2015 at 12:10:01PM +, Brian wrote: > > On Fri 27 Nov 2015 at 18:29:20 +1300, Chris Bannister wrote: > > > > > On Wed, Nov 25, 2015 at 06:40:00PM +, Brian wrote: > > > > "startx -- vt7" won't work (tested). X only runs o

Re: Xorg replaces TTY1

The Wanderer composed on 2015-11-27 15:01 (UTC-0500): > Brian wrote: >> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=743015 >> where, with or without an alias, 'start -- vt7' would be the standard >> and traditional way, as it is on Jessie, to have X on vt7. On a freshly upgraded Stretch

Re: Xorg replaces TTY1

On Fri, Nov 27, 2015 at 12:10:01PM +, Brian wrote: > On Fri 27 Nov 2015 at 18:29:20 +1300, Chris Bannister wrote: > > > On Wed, Nov 25, 2015 at 06:40:00PM +, Brian wrote: > > > On Wed 25 Nov 2015 at 15:48:48 +0100, Vincent Lefevre wrote: > > > > > > > But then, if the user does "startx --

Re: Xorg replaces TTY1

On 2015-11-27 at 13:14, Brian wrote: > On Fri 27 Nov 2015 at 09:09:37 -0500, The Wanderer wrote: > >> On 2015-11-22 at 19:45, Brian wrote: >>> It's the first time I've heard using a bash alias described as a >>> "kludge". >> >> It's the difference between "configuring foo to do bar" and "tellin

Re: Xorg replaces TTY1

On Wed, 25 Nov 2015 08:22:20 +, Anthony Campbell wrote: > On 23 Nov 2015, John L. Ries wrote: > > Actually, if someone is starting X via startx instead of a display manager, > > it normally means either that the user is trying to test his X > > configuration, or that X is only intended to run

Re: Xorg replaces TTY1

On Fri 27 Nov 2015 at 09:09:37 -0500, The Wanderer wrote: > On 2015-11-22 at 19:45, Brian wrote: > > > On Sun 22 Nov 2015 at 19:00:36 -0500, The Wanderer wrote: > > > >> On 2015-11-22 at 18:52, Chris Bannister wrote: > > >>> In .bashrc (if using bash) > >>> > >>> alias startx="startx -- vt7" >

Re: Xorg replaces TTY1

On 2015-11-27 09:09:37 -0500, The Wanderer wrote: > On 2015-11-22 at 19:45, Brian wrote: > > Quoting: > > > > There are 2 reasons for this change: > > > > 1) It is needed to make Xorg run without root rights > > Which has never been necessary before... > > I can see why it would be desirabl

Re: Xorg replaces TTY1

(Phew. Sorry for the delay in replying.) On 2015-11-22 at 19:45, Brian wrote: > On Sun 22 Nov 2015 at 19:00:36 -0500, The Wanderer wrote: > >> On 2015-11-22 at 18:52, Chris Bannister wrote: >>> In .bashrc (if using bash) >>> >>> alias startx="startx -- vt7" >> >> While that would technically

Re: Xorg replaces TTY1

On Fri 27 Nov 2015 at 10:49:09 +0100, Vincent Lefevre wrote: > On 2015-11-27 18:36:39 +1300, Chris Bannister wrote: > > but by changing '/etc/systemd/logind.conf' to > > NAutoVTs=7 > > > > then on login 'alt-F7' will change to tty7 and issue startx from there. > > which doesn't solve the problem

Re: Xorg replaces TTY1

On Fri 27 Nov 2015 at 18:29:20 +1300, Chris Bannister wrote: > On Wed, Nov 25, 2015 at 06:40:00PM +, Brian wrote: > > On Wed 25 Nov 2015 at 15:48:48 +0100, Vincent Lefevre wrote: > > > > > But then, if the user does "startx -- vt7", he would still be affected > > > by the session manager issu

Re: Xorg replaces TTY1

On Thu, Nov 26, 2015 at 04:57:17PM -0500, Gene Heskett wrote: > There s/b a GOOD reason to change something so basic and well > established, and I have not seen that reason adequately explained yet. > Did I miss the memo? You either haven't read the whole thread or just don't agree with the rea

Re: Xorg replaces TTY1

On 2015-11-27 18:36:39 +1300, Chris Bannister wrote: > but by changing '/etc/systemd/logind.conf' to > NAutoVTs=7 > > then on login 'alt-F7' will change to tty7 and issue startx from there. which doesn't solve the problem at all since the goal is to type startx from some tty and have X run on *an

Re: Xorg replaces TTY1

People in this thread might find interesting: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=801487 Regards Mauro Il 27/11/2015 09:39, Petter Adsen ha scritto: On Fri, 27 Nov 2015 18:08:51 +1300 Chris Bannister wrote: On Thu, Nov 26, 2015 at 06:54:34PM +, Brian wrote: For many reade

Re: Xorg replaces TTY1

On Fri, 27 Nov 2015 18:08:51 +1300 Chris Bannister wrote: > On Thu, Nov 26, 2015 at 06:54:34PM +, Brian wrote: > > For many readers (diligent or otherwise), isn't this a matter of > > updated documentation and re-education. There are still users (an > > example is in this thread) who believe

Re: Xorg replaces TTY1

On Thu, Nov 26, 2015 at 03:05:26PM -0600, John Hasler wrote: > Renaud writes: > > One wonders why did they abandon the principle of backward compatibility ? > > Brian writes: > > How does that relate to the principle of constant inovation and > > improvement? > > By way of continuity. Sometimes

Re: Xorg replaces TTY1

On Wed, Nov 25, 2015 at 06:40:00PM +, Brian wrote: > On Wed 25 Nov 2015 at 15:48:48 +0100, Vincent Lefevre wrote: > > > On 2015-11-25 12:58:15 +, Brian wrote: > > > This is where I think the confusion lies. Quoting > > > > > > https://patchwork.freedesktop.org/patch/23004/ > > > > > >

Re: Xorg replaces TTY1

On Thu, Nov 26, 2015 at 08:21:55AM +1300, Chris Bannister wrote: > On Wed, Nov 25, 2015 at 08:22:20AM +, Anthony Campbell wrote: > > On 23 Nov 2015, John L. Ries wrote: > > > Actually, if someone is starting X via startx instead of a display > > > manager, > > > it normally means either that t

Re: Xorg replaces TTY1

On Thu, Nov 26, 2015 at 06:54:34PM +, Brian wrote: > On Thu 26 Nov 2015 at 11:04:23 -0600, John Hasler wrote: > > > Marc writes: > > > Not alone, at all. I run Mate, but I boot to a console, log in there, > > > and use startx to get my X session. > > > > So do I, and I have a decades-old mus

Re: Xorg replaces TTY1

On Thursday 26 November 2015 15:37:04 Brian wrote: > On Thu 26 Nov 2015 at 17:28:05 -0300, Renaud OLGIATI wrote: > > On Thu, 26 Nov 2015 13:46:54 -0600 > > > > John Hasler wrote: > > > > Only obsolete for those who have switched to systemd-Linux; the > > > > documentation remains still valid for

Re: Xorg replaces TTY1

Renaud writes: > One wonders why did they abandon the principle of backward compatibility ? Brian writes: > How does that relate to the principle of constant inovation and > improvement? By way of continuity. Sometimes it is necessary to break continuity, but it should not be done without carefu

Re: Xorg replaces TTY1

On Thu, 26 Nov 2015 20:37:04 + Brian wrote: > > One wonders why did they abandon the principle of backward compatibility ? > > How does that relate to the principle of constant inovation and > improvement? Is it that difficult to innovate and improve, without destroying what was before ?

Re: Xorg replaces TTY1

On Thu 26 Nov 2015 at 17:28:05 -0300, Renaud OLGIATI wrote: > On Thu, 26 Nov 2015 13:46:54 -0600 > John Hasler wrote: > > > > Only obsolete for those who have switched to systemd-Linux; the > > > documentation remains still valid for users of GNU-Linux. > > > True, and that only makes the pr

Re: Xorg replaces TTY1

On Thu, 26 Nov 2015 13:46:54 -0600 John Hasler wrote: > > Only obsolete for those who have switched to systemd-Linux; the > > documentation remains still valid for users of GNU-Linux. > True, and that only makes the problem worse. Now you have *two* sets of > confused new users. One wonders

Re: Xorg replaces TTY1

Renaud writes: > Only obsolete for those who have switched to systemd-Linux; the > documentation remains still valid for users of GNU-Linux. True, and that only makes the problem worse. Now you have *two* sets of confused new users. -- John Hasler jhas...@newsguy.com Elmwood, WI USA

Re: Xorg replaces TTY1

On Thu 26 Nov 2015 at 16:28:05 -0300, Renaud OLGIATI wrote: > On Thu, 26 Nov 2015 13:16:16 -0600 > John Hasler wrote: > > > > For many readers (diligent or otherwise), isn't this a matter of > > > updated documentation and re-education. > > > There is no getting rid of the old documentation

Re: Xorg replaces TTY1

On Thu, 26 Nov 2015 13:16:16 -0600 John Hasler wrote: > > For many readers (diligent or otherwise), isn't this a matter of > > updated documentation and re-education. > There is no getting rid of the old documentation and no way to mark it > obsolete. This is a significant cost of human inte

Re: Xorg replaces TTY1

I wrote: > So do I, and I have a decades-old muscle memory that tells me > CNTRL-ALT-F1 will get me a logged-in console. Having to reprogram that > is a (minor) nuisance. It will be a much larger nuisance for the new > users who will diligently read up on Linux before trying it (yes, there > are p

Re: Xorg replaces TTY1

On Thu 26 Nov 2015 at 11:04:23 -0600, John Hasler wrote: > Marc writes: > > Not alone, at all. I run Mate, but I boot to a console, log in there, > > and use startx to get my X session. > > So do I, and I have a decades-old muscle memory that tells me > CNTRL-ALT-F1 will get me a logged-in conso

Re: Xorg replaces TTY1

Marc writes: > Not alone, at all. I run Mate, but I boot to a console, log in there, > and use startx to get my X session. So do I, and I have a decades-old muscle memory that tells me CNTRL-ALT-F1 will get me a logged-in console. Having to reprogram that is a (minor) nuisance. It will be a much

Re: Xorg replaces TTY1

On 11/25/2015 12:22 AM, Anthony Campbell wrote: On 23 Nov 2015, John L. Ries wrote: Actually, if someone is starting X via startx instead of a display manager, it normally means either that the user is trying to test his X configuration, or that X is only intended to run intermittently, with TTY

Re: Xorg replaces TTY1

On Wed, Nov 25, 2015 at 08:22:20AM +, Anthony Campbell wrote: > On 23 Nov 2015, John L. Ries wrote: > > Actually, if someone is starting X via startx instead of a display manager, > > it normally means either that the user is trying to test his X > > configuration, or that X is only intended to

Re: Xorg replaces TTY1

On Wed 25 Nov 2015 at 15:48:48 +0100, Vincent Lefevre wrote: > On 2015-11-25 12:58:15 +, Brian wrote: > > This is where I think the confusion lies. Quoting > > > > https://patchwork.freedesktop.org/patch/23004/ > > > > again. > > > > There are 2 reasons for this change: > > > > 1) It

Re: Xorg replaces TTY1

On 2015-11-25 12:58:15 +, Brian wrote: > This is where I think the confusion lies. Quoting > > https://patchwork.freedesktop.org/patch/23004/ > > again. > > There are 2 reasons for this change: > > 1) It is needed to make Xorg run without root rights > 2) The old behavior creates a

Re: Xorg replaces TTY1

Would everyone tolerate some top posting so the stall can be set up? :) There are two issues here which I think are getting confused. The first concerns the issue raised by the OP: using startx on vt1 gets vt1 replaced by Xorg. Background to this change in historical behaviour is discussed in bug

Re: Xorg replaces TTY1

On Wednesday 25 November 2015 08:22:20 Anthony Campbell wrote: > I don't agree with this. I don't use a desktop manager but even if I > did, I'd prefer to start X via startx. This gives me more control. If > something goes wrong with X you are screwed if you don't have an easily > accessible TTY to

Re: Xorg replaces TTY1

On 23 Nov 2015, John L. Ries wrote: > Actually, if someone is starting X via startx instead of a display manager, > it normally means either that the user is trying to test his X > configuration, or that X is only intended to run intermittently, with TTY > mode being the norm. So having X replace

Re: Xorg replaces TTY1

On 2015-11-25 09:32:50 +0100, Vincent Lefevre wrote: > I agree, but there's still a contradiction with the above: what Chris > said (quote from developers) is that X no longer uses a different TTY I meant Brian, not Chris (quoting got wrong a few messages above). -- Vincent Lefèvre - Web:

Re: Xorg replaces TTY1

On 2015-11-24 22:15:25 +0100, Michael Biebl wrote: > Am 24.11.2015 um 21:47 schrieb Brian: > > On Tue 24 Nov 2015 at 21:13:29 +0100, Michael Biebl wrote: > > > >> Am 24.11.2015 um 19:01 schrieb Brian: > >>> On Tue 24 Nov 2015 at 17:36:49 +0100, Vincent Lefevre wrote: > >>> > On 2015-11-23 00:

Re: Xorg replaces TTY1

On Tue 24 Nov 2015 at 22:15:25 +0100, Michael Biebl wrote: > Am 24.11.2015 um 21:47 schrieb Brian: > > On Tue 24 Nov 2015 at 21:13:29 +0100, Michael Biebl wrote: > > > >> Am 24.11.2015 um 19:01 schrieb Brian: > >>> On Tue 24 Nov 2015 at 17:36:49 +0100, Vincent Lefevre wrote: > >>> > On 2015-

Re: Xorg replaces TTY1

Am 24.11.2015 um 21:47 schrieb Brian: > On Tue 24 Nov 2015 at 21:13:29 +0100, Michael Biebl wrote: > >> Am 24.11.2015 um 19:01 schrieb Brian: >>> On Tue 24 Nov 2015 at 17:36:49 +0100, Vincent Lefevre wrote: >>> On 2015-11-23 00:45:57 +, Brian wrote: > On Sun 22 Nov 2015 at 19:00:36 -0

Re: Xorg replaces TTY1

On Tue 24 Nov 2015 at 21:13:29 +0100, Michael Biebl wrote: > Am 24.11.2015 um 19:01 schrieb Brian: > > On Tue 24 Nov 2015 at 17:36:49 +0100, Vincent Lefevre wrote: > > > >> On 2015-11-23 00:45:57 +, Brian wrote: > >>> On Sun 22 Nov 2015 at 19:00:36 -0500, The Wanderer wrote: > >>> > On 2

Re: Xorg replaces TTY1

Am 24.11.2015 um 19:01 schrieb Brian: > On Tue 24 Nov 2015 at 17:36:49 +0100, Vincent Lefevre wrote: > >> On 2015-11-23 00:45:57 +, Brian wrote: >>> On Sun 22 Nov 2015 at 19:00:36 -0500, The Wanderer wrote: >>> On 2015-11-22 at 18:52, Chris Bannister wrote: >>> There are 2 reasons

Re: Xorg replaces TTY1

On Tue 24 Nov 2015 at 17:36:49 +0100, Vincent Lefevre wrote: > On 2015-11-23 00:45:57 +, Brian wrote: > > On Sun 22 Nov 2015 at 19:00:36 -0500, The Wanderer wrote: > > > > > On 2015-11-22 at 18:52, Chris Bannister wrote: > > > > > > > On Sun, Nov 22, 2015 at 05:56:04PM -0500, The Wanderer wr

Re: Xorg replaces TTY1

On 2015-11-23 00:45:57 +, Brian wrote: > On Sun 22 Nov 2015 at 19:00:36 -0500, The Wanderer wrote: > > > On 2015-11-22 at 18:52, Chris Bannister wrote: > > > > > On Sun, Nov 22, 2015 at 05:56:04PM -0500, The Wanderer wrote: > > > > > >>> startx -- vt7 > > >> > > >> That requires specifying

Re: Xorg replaces TTY1

On 11/24/2015 06:17 AM, Brian wrote: On Mon 23 Nov 2015 at 20:06:06 -0800, Marc Shapiro wrote: My box always has three X sessions going at the same time (still on Wheezy). I use an alias to set the vt. The value of the alias is determined by who is logged on and running startx: for me: al

Re: Xorg replaces TTY1

On Mon 23 Nov 2015 at 20:06:06 -0800, Marc Shapiro wrote: > On 11/22/2015 02:56 PM, The Wanderer wrote: > >On 2015-11-22 at 15:24, Brian wrote: > > > >>startx -- vt7 > > > >That requires specifying it by hand every time startx is run. As I > >indicated, that is unacceptable; I don't have to specif

Re: Xorg replaces TTY1

On 11/22/2015 02:56 PM, The Wanderer wrote: On 2015-11-22 at 15:24, Brian wrote: On Sun 22 Nov 2015 at 14:12:09 -0500, The Wanderer wrote: On 2015-11-22 at 13:26, Brian wrote: * 10-startx-Under-Linux-start-X-on-the-current-VT.patch, 11-startx-Pass-vtX-as-long-as-the-user-did-not-spec

Re: Xorg replaces TTY1

Then there all the new users out there who, having diligently read up on Linux, know exactly how to open a console... -- John Hasler jhas...@newsguy.com Elmwood, WI USA

Re: Xorg replaces TTY1

Actually, if someone is starting X via startx instead of a display manager, it normally means either that the user is trying to test his X configuration, or that X is only intended to run intermittently, with TTY mode being the norm. So having X replace the terminal in that circumstance does n

Re: Xorg replaces TTY1

On Sun 22 Nov 2015 at 19:00:36 -0500, The Wanderer wrote: > On 2015-11-22 at 18:52, Chris Bannister wrote: > > > On Sun, Nov 22, 2015 at 05:56:04PM -0500, The Wanderer wrote: > > > >>> startx -- vt7 > >> > >> That requires specifying it by hand every time startx is run. As I > >> indicated, th

Re: Xorg replaces TTY1

On 2015-11-22 at 18:52, Chris Bannister wrote: > On Sun, Nov 22, 2015 at 05:56:04PM -0500, The Wanderer wrote: > >>> startx -- vt7 >> >> That requires specifying it by hand every time startx is run. As I >> indicated, that is unacceptable; I don't have to specify the VT >> manually every time I

Re: Xorg replaces TTY1

On Sun, Nov 22, 2015 at 05:56:04PM -0500, The Wanderer wrote: > > startx -- vt7 > > That requires specifying it by hand every time startx is run. As I > indicated, that is unacceptable; I don't have to specify the VT manually > every time I lanch X now in order to get the current behavior, and I >

Re: Xorg replaces TTY1

On 2015-11-22 at 15:24, Brian wrote: > On Sun 22 Nov 2015 at 14:12:09 -0500, The Wanderer wrote: > >> On 2015-11-22 at 13:26, Brian wrote: >>> * 10-startx-Under-Linux-start-X-on-the-current-VT.patch, >>> 11-startx-Pass-vtX-as-long-as-the-user-did-not-specify-.patch: By >>> default >>>

  1   2   3   4   5   6   7   8   9   >