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
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
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
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
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
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
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
> > 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
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
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
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
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
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.
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
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)
> >>
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+
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.
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):
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
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
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
>> > ->
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
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
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
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
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
26 matches
Mail list logo
