El 10/06/12 20:35, Don deJuan escribió:
On 06/10/2012 05:30 PM, Sébastien le Preste de Vauban wrote:
El 10/06/12 20:18, John Briggs escribió:
I also have the same problem. And remember that Ubuntu, Fedora work well, so I wonder whether it is a bug. On Jun 11, 2012 4:21 AM, "Mateusz Loskot" <mateusz@loskot.net> wrote:
On 10 June 2012 20:35, Sébastien le Preste de Vauban <ulpianosonsi@gmail.com> wrote:
El 10/06/12 14:11, Mateusz Loskot escribió: > On 10 June 2012 19:03, Javier Vasquez <j.e.vasquez.v@gmail.com> > wrote: >> On Sun, Jun 10, 2012 at 11:42 AM, Mateusz Loskot >> <mateusz@loskot.net> >> wrote: >>> I have been observing strange issues when I switch between X and >>> TTY. >>> [...] >> I started noticing this same thing since last year (though don't >> remember when exactly). Never asked cause the work around is >> simple, >> the TTY from which startx was run is considered "dead" to me, I >> just >> don't use it once in X. > Yes, you are right it's not a very disturbing issue. > I was just curious if it is known problem and perhaps there is a solution. I have a similar problem:
https://bugs.freedesktop.org/show_bug.cgi?id=47277 Nice one, I'm going to subscribe to this issue. Thanks!
Best regards, -- Mateusz Loskot, http://mateusz.loskot.net
What bug? The TTY running X is busy running the xinit/xsession process, until you kill that process you shouldn't be able to get the command line
On Mon, Jun 11, 2012 at 07:35:45AM +0800, 逸冰欧阳 wrote: prompt to run another program. The only way to overcome this shortcoming would be to run xinit in the background, which I wouldn't reccomend.
Regards
John
Well it happens to me with any TTY, not just the one running X.
Same here, I thought everyone had stated it is switching to any TTY from X or from some other TTY back to X and this will occur.
I suggest people being affected by this issue to reply to the bug report in https://bugs.freedesktop.org/show_bug.cgi?id=47277 so we get upstream attention.