Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #186053 > unrolled thread

XFCE wm deadlocks on (other) console logout

Back to article view | Back to linux.debian.user

Contents

  XFCE wm deadlocks on (other) console logout Zenaan Harkness <zenaan@freedbms.net> - 2017-08-28 06:20 +0200
    Re: XFCE wm deadlocks on (other) console logout Liam O'Toole <liam.p.otoole@gmail.com> - 2017-08-28 12:10 +0200
    Re: XFCE wm deadlocks on (other) console logout bw <bwtnguy@yahoo.com> - 2017-08-28 15:10 +0200
      Re: XFCE wm deadlocks on (other) console logout Zenaan Harkness <zenaan@freedbms.net> - 2017-08-29 04:40 +0200
    Re: XFCE wm deadlocks on (other) console logout Cindy-Sue Causey <butterflybytes@gmail.com> - 2017-08-28 15:30 +0200
      Re: XFCE wm deadlocks on (other) console logout Zenaan Harkness <zenaan@freedbms.net> - 2017-08-29 04:40 +0200

#186053 — XFCE wm deadlocks on (other) console logout

I consistently get a deadlock of the XFCE window manager, immediately
after I logout of say Linux console 2, when e.g. XFCE is running on
console 1.

Procedure to replicate:

1. login to console 1

2. start xfce

3. switch to console 2 (e.g. CTRL+ALT+F2)

4. loging to console 2

5. logout of console 2 (e.g. CTRL+D)


Notably, when I'm on console 2, either logged in or not, I can safely
use ALT+Left to go to console 1 and appears my XFCE desktop.

Similarly using Ctrl+Alt+F1

So I'm guessing some sort of unhandled race condition, but I'm at a
loss as to how to debug this.

[toc] | [next] | [standalone]

#186070

On 2017-08-28, Zenaan Harkness <zenaan@freedbms.net> wrote:
> I consistently get a deadlock of the XFCE window manager, immediately
> after I logout of say Linux console 2, when e.g. XFCE is running on
> console 1.
>
> Procedure to replicate:
>
> 1. login to console 1
>
> 2. start xfce
>
> 3. switch to console 2 (e.g. CTRL+ALT+F2)
>
> 4. loging to console 2
>
> 5. logout of console 2 (e.g. CTRL+D)
>
>
> Notably, when I'm on console 2, either logged in or not, I can safely
> use ALT+Left to go to console 1 and appears my XFCE desktop.
>
> Similarly using Ctrl+Alt+F1
>
> So I'm guessing some sort of unhandled race condition, but I'm at a
> loss as to how to debug this.

I suspect a deadlock of the graphics driver rather then the window
manager. Some drivers don't handle console switching very well. Can you
reproduce the problem with a different window manager?

-- 

Liam

[toc] | [prev] | [next] | [standalone]

#186077

On Mon, 28 Aug 2017, Zenaan Harkness wrote:

> I consistently get a deadlock of the XFCE window manager, immediately
> after I logout of say Linux console 2, when e.g. XFCE is running on
> console 1.
>
> Procedure to replicate:
>
> 1. login to console 1
>
> 2. start xfce
>
> 3. switch to console 2 (e.g. CTRL+ALT+F2)
>
> 4. loging to console 2
>
> 5. logout of console 2 (e.g. CTRL+D)
>


I have the same issue, using very minimal system with a wm.  Right now the 
workaround I'm using is comment out the clear_console call in 
~/.bash_logout

# ~/.bash_logout: executed by bash(1) when login shell exits.

# when leaving the console clear the screen to increase privacy

if [ "$SHLVL" = 1 ]; then
/bin/true
#    [ -x /usr/bin/clear_console ] && /usr/bin/clear_console -q
fi

I'm also looking at the TTYVTDisallocate=yes line in
/etc/systemd/system/getty.target.wants/getty@tty1.service -> 
/lib/systemd/system/getty@.service

I haven't tried changing this, but it looks interesting.  You might find 
more interesting things in these bug reports:

https://bugs.debian.org/805605
https://bugs.debian.org/810660
https://bugs.freedesktop.org/93164

Good Luck

[toc] | [prev] | [next] | [standalone]

#186105

On Mon, Aug 28, 2017 at 09:02:29AM -0400, bw wrote:
> 
> 
> On Mon, 28 Aug 2017, Zenaan Harkness wrote:
> 
> > I consistently get a deadlock of the XFCE window manager, immediately
> > after I logout of say Linux console 2, when e.g. XFCE is running on
> > console 1.
> > 
> > Procedure to replicate:
> > 
> > 1. login to console 1
> > 
> > 2. start xfce
> > 
> > 3. switch to console 2 (e.g. CTRL+ALT+F2)
> > 
> > 4. loging to console 2
> > 
> > 5. logout of console 2 (e.g. CTRL+D)
> > 
> 
> 
> I have the same issue, using very minimal system with a wm.  Right now the workaround I'm using is comment out the
> clear_console call in ~/.bash_logout
> 
> # ~/.bash_logout: executed by bash(1) when login shell exits.
> 
> # when leaving the console clear the screen to increase privacy
> 
> if [ "$SHLVL" = 1 ]; then
> /bin/true
> #    [ -x /usr/bin/clear_console ] && /usr/bin/clear_console -q
> fi

Fantastic!! Thank you so much!

Reading the man page for clear_console makes it perfectly clear -
after "clearing the screen" it jumps immediately to another console
(evidently in this case console 1) and then tries to jump straight
back, which of course is going to interact rather badly with X! :)


> I'm also looking at the TTYVTDisallocate=yes line in
> /etc/systemd/system/getty.target.wants/getty@tty1.service -> /lib/systemd/system/getty@.service
> 
> I haven't tried changing this, but it looks interesting.  You might find more interesting things in these bug reports:
> 
> https://bugs.debian.org/805605
> https://bugs.debian.org/810660
> https://bugs.freedesktop.org/93164

Thank you!

[toc] | [prev] | [next] | [standalone]

#186081

On 8/28/17, Zenaan Harkness <zenaan@freedbms.net> wrote:
> I consistently get a deadlock of the XFCE window manager, immediately
> after I logout of say Linux console 2, when e.g. XFCE is running on
> console 1.
>
> Procedure to replicate:
>
> 1. login to console 1
>
> 2. start xfce
>
> 3. switch to console 2 (e.g. CTRL+ALT+F2)
>
> 4. loging to console 2
>
> 5. logout of console 2 (e.g. CTRL+D)
>
>
> Notably, when I'm on console 2, either logged in or not, I can safely
> use ALT+Left to go to console 1 and appears my XFCE desktop.
>
> Similarly using Ctrl+Alt+F1
>
> So I'm guessing some sort of unhandled race condition, but I'm at a
> loss as to how to debug this.


I may not be quite understanding, but I just played along from behind
the lurk wall....

I had a BUNCH of shtuff open at that second. I didn't think things
through clearly, i.e. if mine locked up, I would have lost some
shtuff...

As it was...........

I got locked out... kinda sorta.

I CTRL+ALT+F2.... logged in to where I was still in console. Typed a
few "asdfasdfasdf" that obviously failed, and logged out.

I..... CTRL+ALT+F1.......

And there I sat at the login prompt.........

As soon that happened, I had a memory recall of having been there,
done there a couple months ago and never followed up on it. I didn't
try logging in because part of that memory recall is that I might have
lost some data on the last go-round with it.

I THOUGHT that F1 was the first console, is it not?

Out of pure *panic*, I went down the row..... F3, F4, F5......

Mystery solved: F7 is the new F1 in my case.

I started to ask if that helps in your case, but it sounds like you're
already able to use CTRL+ALT+F1 as expected so.... *?*

Just thinking out loud.. :)

Cindy :)
-- 
Cindy-Sue Causey
Talking Rock, Pickens County, Georgia, USA

* runs with duct tape *

[toc] | [prev] | [next] | [standalone]

#186104

On Mon, Aug 28, 2017 at 09:20:32AM -0400, Cindy-Sue Causey wrote:
> On 8/28/17, Zenaan Harkness <zenaan@freedbms.net> wrote:
> > I consistently get a deadlock of the XFCE window manager, immediately
> > after I logout of say Linux console 2, when e.g. XFCE is running on
> > console 1.
> >
> > Procedure to replicate:
> >
> > 1. login to console 1
> >
> > 2. start xfce
> >
> > 3. switch to console 2 (e.g. CTRL+ALT+F2)
> >
> > 4. loging to console 2
> >
> > 5. logout of console 2 (e.g. CTRL+D)
> >
> >
> > Notably, when I'm on console 2, either logged in or not, I can safely
> > use ALT+Left to go to console 1 and appears my XFCE desktop.
> >
> > Similarly using Ctrl+Alt+F1
> >
> > So I'm guessing some sort of unhandled race condition, but I'm at a
> > loss as to how to debug this.
> 
> 
> I may not be quite understanding, but I just played along from behind
> the lurk wall....
> 
> I had a BUNCH of shtuff open at that second. I didn't think things
> through clearly, i.e. if mine locked up, I would have lost some
> shtuff...
> 
> As it was...........
> 
> I got locked out... kinda sorta.
> 
> I CTRL+ALT+F2.... logged in to where I was still in console. Typed a
> few "asdfasdfasdf" that obviously failed, and logged out.
> 
> I..... CTRL+ALT+F1.......
> 
> And there I sat at the login prompt.........
> 
> As soon that happened, I had a memory recall of having been there,
> done there a couple months ago and never followed up on it. I didn't
> try logging in because part of that memory recall is that I might have
> lost some data on the last go-round with it.
> 
> I THOUGHT that F1 was the first console, is it not?

Indeed it is - by default, the first console is "1" (/dev/pts/1 ?)
and that's where I log in, then start xorg.


> Out of pure *panic*, I went down the row..... F3, F4, F5......

CTRL+RightArrow and CTRL+LeftArrow also work for me to cycle around
the consoles.


> Mystery solved: F7 is the new F1 in my case.

In some setups, this is the case - I don't run a graphical login
manager such as lightdm.


> I started to ask if that helps in your case, but it sounds like you're
> already able to use CTRL+ALT+F1 as expected so.... *?*

Exactly - the keyboard gets locked up.

Although I recall sometimes X completely dies - at least, I've
experienced something similar to your case.


> Just thinking out loud.. :)

Thanks for sharing - appreciated of course :)

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.user

csiph-web