Re: Let's play "Where is X?" (was: logout kills X)

2019-02-04 Thread Greg Wooledge
On Sat, Feb 02, 2019 at 10:01:17PM +, Jonathan de Boyne Pollard wrote: > The problem with the Bourne Again shell package's |clear_console| /is/ KVT > switching, and /similarly eliminating KVT switching/ fixes it (as I > explained back in 2015, when I published a replacement |clear_console| >

[cause] Re: logout kills X

2019-02-04 Thread Holger Herrlich
The crash happens due to a race condition in switching forth and back using: ioctl(fd,VT_ACTIVATE, tmp_tty) ioctl(fd,VT_WAITACTIVE,tmp_tty) <- here ioctl(fd,VT_ACTIVATE, org_tty) ioctl(fd,VT_WAITACTIVE,org_tty) in clear_console.c's clear_console() function

Re: Let's play "Where is X?" (was: logout kills X)

2019-02-03 Thread Rusi Mody
https://www.facebook.com/381862631937250/posts/1867044320085733

Re: Let's play "Where is X?" (was: logout kills X)

2019-02-03 Thread Default User
On Sun, Feb 3, 2019, 04:04 On Sat, Feb 02, 2019 at 06:34:33PM -0500, Felix Miata wrote: > > Jonathan de Boyne Pollard composed on 2019-02-02 22:01 (UTC): > > > > > Felix Miata: > > > > >> Indeed. It's what I had in mind when I responded. I'll give one guess > > >> where it came from. Time's up

Re: Let's play "Where is X?" (was: logout kills X)

2019-02-03 Thread tomas
On Sat, Feb 02, 2019 at 06:34:33PM -0500, Felix Miata wrote: > Jonathan de Boyne Pollard composed on 2019-02-02 22:01 (UTC): > > > Felix Miata: > > >> Indeed. It's what I had in mind when I responded. I'll give one guess > >> where it came from. Time's up. Yes, systemd [...] > > This is qui

Re: Let's play "Where is X?" (was: logout kills X)

2019-02-02 Thread Felix Miata
Jonathan de Boyne Pollard composed on 2019-02-02 22:01 (UTC): > Felix Miata: >> Indeed. It's what I had in mind when I responded. I'll give one guess >> where it came from. Time's up. Yes, systemd. Who couldn't have >> guessed. It imposed a notion that I first noticed (wish to guess >>

Let's play "Where is X?" (was: logout kills X)

2019-02-02 Thread Jonathan de Boyne Pollard
Felix Miata: Indeed. It's what I had in mind when I responded. I'll give one guess where it came from. Time's up. Yes, systemd. Who couldn't have guessed. It imposed a notion that I first noticed (wish to guess where?) Yup, on Fedora, home of Leonard P, under the aegis of RedHat, and

Re: logout kills X

2019-02-02 Thread Jonathan de Boyne Pollard
Greg Wooledge: The man page for |clear_console|(1) is a little unclear to me, and a little bit disturbing. I cannot figure out what "changes the foreground virtual terminal to another terminal" is supposed to mean, but between that and the reference to |chvt|(1) under SEE ALSO, it seems like

Re: logout kills X

2019-02-02 Thread tomas
On Fri, Feb 01, 2019 at 10:33:14PM +, Brian wrote: > Bugs filed against X, bash and systemd. Only the much maligned systemd > [...] has had an analysis and discussion in -systemd. Silence from the X > and [...] the bash maintaners for 3+ years [...] I don't know if you are aware of it, but it

Re: logout kills X

2019-02-01 Thread Brian
On Fri 01 Feb 2019 at 10:54:32 -, Curt wrote: > On 2019-01-31, Brian wrote: > > > > Thank you for looking at this. I tried 'clear && reset' on unstable and > > have no complaints. Back to tty2 on after logging in and out and mouse > > and keyboard normal operation on X in tty1. > > > > So - i

[solved] Re: logout kills X

2019-02-01 Thread Holger Herrlich
On Thu, 31 Jan 2019 18:36:58 + Brian wrote: > On Thu 31 Jan 2019 at 12:56:59 -0500, Felix Miata wrote: > > > tty1 became special with the introduction of systemd. Do not use > > tty1 for X. Instead use tty2 and/or tty3 and/or tty4 and/or tty5 > > and/or tty6. Buster may have this fixed, as

Re: logout kills X

2019-02-01 Thread Curt
On 2019-01-31, Brian wrote: > > Thank you for looking at this. I tried 'clear && reset' on unstable and > have no complaints. Back to tty2 on after logging in and out and mouse > and keyboard normal operation on X in tty1. > > So - is bash the culprit, or are the interactions between it and other

Re: logout kills X

2019-01-31 Thread David Wright
On Thu 31 Jan 2019 at 15:01:49 (-0500), Greg Wooledge wrote: > > > mine runs clear && reset rather than clear_console. > > > Does that make any difference? > > > > Thank you for looking at this. I tried 'clear && reset' on unstable and > > have no complaints. Back to tty2 on after logging in

Re: logout kills X

2019-01-31 Thread Greg Wooledge
> > mine runs clear && reset rather than clear_console. > > Does that make any difference? > > Thank you for looking at this. I tried 'clear && reset' on unstable and > have no complaints. Back to tty2 on after logging in and out and mouse > and keyboard normal operation on X in tty1. > > S

Re: logout kills X

2019-01-31 Thread Brian
On Thu 31 Jan 2019 at 12:51:05 -0600, David Wright wrote: > On Thu 31 Jan 2019 at 18:36:58 (+), Brian wrote: > > On Thu 31 Jan 2019 at 12:56:59 -0500, Felix Miata wrote: > > > > > tty1 became special with the introduction of systemd. Do not use tty1 > > > for X. Instead use tty2 and/or tty3 a

Re: logout kills X

2019-01-31 Thread David Wright
On Thu 31 Jan 2019 at 18:36:58 (+), Brian wrote: > On Thu 31 Jan 2019 at 12:56:59 -0500, Felix Miata wrote: > > > tty1 became special with the introduction of systemd. Do not use tty1 > > for X. Instead use tty2 and/or tty3 and/or tty4 and/or tty5 and/or > > tty6. Buster may have this fixed, a

Re: logout kills X

2019-01-31 Thread Brian
On Thu 31 Jan 2019 at 12:56:59 -0500, Felix Miata wrote: > tty1 became special with the introduction of systemd. Do not use tty1 > for X. Instead use tty2 and/or tty3 and/or tty4 and/or tty5 and/or > tty6. Buster may have this fixed, as upstream has apparently fixed it > 3 months ago. The behavio

Re: logout kills X

2019-01-31 Thread Felix Miata
Holger Herrlich composed on 2019-01-31 15:22 (UTC+0100): > On Wed, 30 Jan 2019 14:57:59 -0500 Felix Miata wrote: >> or what gfx, > ?? Common shorthand for *graphics* hardware. AMD/ATI? Intel? NVidia? Matrox? Other? Model? e.g. # inxi -GxxSM System:Host: big31 Kernel: 4.9.0-8-amd64 x86_64 b

Re: logout kills X

2019-01-31 Thread Holger Herrlich
systemd is very aware the state: loginctl list-sessions SESSIONUID USER SEAT TTY 1 1000 addams seat0/dev/tty1 25 1000 addams seat0/dev/tty2 2 sessions listed.

Re: logout kills X

2019-01-31 Thread Holger Herrlich
On Wed, 30 Jan 2019 20:25:59 + Brian wrote: > On Wed 30 Jan 2019 at 14:57:59 -0500, Felix Miata wrote: > > > Brian composed on 2019-01-30 19:12 (UTC): > > > > > On Wed 30 Jan 2019 at 13:48:17 -0500, Felix Miata wrote: > > > > >> hoh...@arcor.de composed on 2019-01-30 18:38 (UTC+0

Re: logout kills X

2019-01-31 Thread Holger Herrlich
On Wed, 30 Jan 2019 14:57:59 -0500 Felix Miata wrote: > Brian composed on 2019-01-30 19:12 (UTC): > > > On Wed 30 Jan 2019 at 13:48:17 -0500, Felix Miata wrote: > > >> hoh...@arcor.de composed on 2019-01-30 18:38 (UTC+0100): > > >> > I logged in (to tty1) > >> > started X (startx) > >>

Re: logout kills X

2019-01-31 Thread Holger Herrlich
On Wed, 30 Jan 2019 20:33:44 + Brian wrote: > On Wed 30 Jan 2019 at 13:54:14 -0600, David Wright wrote: > > > On Wed 30 Jan 2019 at 19:12:42 (+), Brian wrote: > > > On Wed 30 Jan 2019 at 13:48:17 -0500, Felix Miata wrote: > > > > hoh...@arcor.de composed on 2019-01-30 18:38 (UTC+

Re: logout kills X

2019-01-31 Thread Holger Herrlich
On Wed, 30 Jan 2019 19:23:43 +0100 deloptes wrote: > hoh...@arcor.de wrote: > > > I finally want to know how to separate the sessions. > > why don't you use a window manager. Most of them offer the option to > log in as different user, which will open a new session on the next > console.

Re: logout kills X

2019-01-30 Thread Brian
On Wed 30 Jan 2019 at 20:33:44 +, Brian wrote: > On Wed 30 Jan 2019 at 13:54:14 -0600, David Wright wrote: > > > On Wed 30 Jan 2019 at 19:12:42 (+), Brian wrote: > > > On Wed 30 Jan 2019 at 13:48:17 -0500, Felix Miata wrote: > > > > hoh...@arcor.de composed on 2019-01-30 18:38 (UTC+0100):

Re: Let's play "Where is X?" (was: logout kills X)

2019-01-30 Thread Brian
On Wed 30 Jan 2019 at 17:06:31 -0500, Felix Miata wrote: > David Wright composed on 2019-01-30 13:54 (UTC-0600): > > > On Wed 30 Jan 2019 at 19:12:42 (+), Brian wrote: > > >> On Wed 30 Jan 2019 at 13:48:17 -0500, Felix Miata wrote: > > >>> Same problem if you don't use tty1, instead logging

Re: Let's play "Where is X?" (was: logout kills X)

2019-01-30 Thread Felix Miata
David Wright composed on 2019-01-30 13:54 (UTC-0600): > On Wed 30 Jan 2019 at 19:12:42 (+), Brian wrote: >> On Wed 30 Jan 2019 at 13:48:17 -0500, Felix Miata wrote: >>> Same problem if you don't use tty1, instead logging in first on tty2, and >>> after on tty3? >> Did *you* try this? In fa

Re: logout kills X

2019-01-30 Thread Brian
On Wed 30 Jan 2019 at 13:54:14 -0600, David Wright wrote: > On Wed 30 Jan 2019 at 19:12:42 (+), Brian wrote: > > On Wed 30 Jan 2019 at 13:48:17 -0500, Felix Miata wrote: > > > hoh...@arcor.de composed on 2019-01-30 18:38 (UTC+0100): > > > > > > > I logged in (to tty1) > > > > started X (start

Re: logout kills X

2019-01-30 Thread Brian
On Wed 30 Jan 2019 at 14:57:59 -0500, Felix Miata wrote: > Brian composed on 2019-01-30 19:12 (UTC): > > > On Wed 30 Jan 2019 at 13:48:17 -0500, Felix Miata wrote: > > >> hoh...@arcor.de composed on 2019-01-30 18:38 (UTC+0100): > > >> > I logged in (to tty1) > >> > started X (startx) > >> > swi

Re: logout kills X

2019-01-30 Thread Felix Miata
Brian composed on 2019-01-30 19:12 (UTC): > On Wed 30 Jan 2019 at 13:48:17 -0500, Felix Miata wrote: >> hoh...@arcor.de composed on 2019-01-30 18:38 (UTC+0100): >> > I logged in (to tty1) >> > started X (startx) >> > switched to tty2 >> > logged in (using the same name) >> > logged out >> > ->

Re: logout kills X

2019-01-30 Thread David Wright
On Wed 30 Jan 2019 at 19:12:42 (+), Brian wrote: > On Wed 30 Jan 2019 at 13:48:17 -0500, Felix Miata wrote: > > hoh...@arcor.de composed on 2019-01-30 18:38 (UTC+0100): > > > > > I logged in (to tty1) > > > started X (startx) > > > switched to tty2 > > > logged in (using the same name) > > > l

Re: logout kills X

2019-01-30 Thread Brian
On Wed 30 Jan 2019 at 13:48:17 -0500, Felix Miata wrote: > hoh...@arcor.de composed on 2019-01-30 18:38 (UTC+0100): > > > I logged in (to tty1) > > started X (startx) > > switched to tty2 > > logged in (using the same name) > > logged out > > > -> X on tty1 crashes > > Same problem if you don't

Re: logout kills X

2019-01-30 Thread Felix Miata
hoh...@arcor.de composed on 2019-01-30 18:38 (UTC+0100): > I logged in (to tty1) > started X (startx) > switched to tty2 > logged in (using the same name) > logged out > -> X on tty1 crashes Same problem if you don't use tty1, instead logging in first on tty2, and after on tty3? -- Evolution a

Re: logout kills X

2019-01-30 Thread Brian
On Wed 30 Jan 2019 at 19:23:43 +0100, deloptes wrote: > hoh...@arcor.de wrote: > > > I finally want to know how to separate the sessions. > > why don't you use a window manager. Most of them offer the option to log in > as different user, which will open a new session on the next console. > I ha

Re: logout kills X

2019-01-30 Thread deloptes
hoh...@arcor.de wrote: > I finally want to know how to separate the sessions. why don't you use a window manager. Most of them offer the option to log in as different user, which will open a new session on the next console. I have not heard of same user logged in in two different X sessions on sa

logout kills X

2019-01-30 Thread hohe72
I logged in (to tty1) started X (startx) switched to tty2 logged in (using the same name) logged out -> X on tty1 crashes some info: .local/share/xorg/Xorg.0.log: [ 41948.035] (EE) modeset(0): failed to set mode: Permission denied [ 41948.035] (EE) Fatal server error: [ 41948.035] (EE) Ent