On Mon, Aug 28, 2017 at 09:20:32AM -0400, Cindy-Sue Causey wrote: > On 8/28/17, Zenaan Harkness <zen...@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 :)
