On Sun, Mar 07, 2010 at 04:34:31PM -0500, MK wrote:
> On Sun, 07 Mar 2010 13:58:04 -0500
> des...@verizon.net wrote:
> > MK writes:
> > Try:
> >
> > sudo chvt 1
>
> I usually run as root -- and no, I don't need a lecture about it ;)
What exit code did chvt return?
Did it even try and switch to
On Sun, 07 Mar 2010 13:58:04 -0500
des...@verizon.net wrote:
> MK writes:
> Try:
>
> sudo chvt 1
I usually run as root -- and no, I don't need a lecture about it ;)
--
MK
MK writes:
> On Sun, 07 Mar 2010 12:39:46 -0500
> des...@verizon.net wrote:
>> Also check your xmodmap settings.
>>
>> Try:
>>
>> xmodmap -pke
>
> xmodmap is set okay. chvt doesn't work tho. Hmphh.
Try:
sudo chvt 1
On Sun, 07 Mar 2010 12:39:46 -0500
des...@verizon.net wrote:
> Also check your xmodmap settings.
>
> Try:
>
> xmodmap -pke
xmodmap is set okay. chvt doesn't work tho. Hmphh.
--
MK
Thomas Adam writes:
> On Sun, Mar 07, 2010 at 12:20:34PM -0500, MK wrote:
>> On Sun, 7 Mar 2010 16:04:19 +
>> Thomas Adam wrote:
>> > It's a setting for X11 -- nothing to do with FVWM. Read your
>> > xorg.conf manpage.
>>
>> Yeah, DontVTSwitch is not set anywhere, I am just trying to rule
On Sun, Mar 07, 2010 at 12:20:34PM -0500, MK wrote:
> On Sun, 7 Mar 2010 16:04:19 +
> Thomas Adam wrote:
> > It's a setting for X11 -- nothing to do with FVWM. Read your
> > xorg.conf manpage.
>
> Yeah, DontVTSwitch is not set anywhere, I am just trying to rule out
> possible causes.
Well,
On Sun, 7 Mar 2010 16:04:19 +
Thomas Adam wrote:
> It's a setting for X11 -- nothing to do with FVWM. Read your
> xorg.conf manpage.
Yeah, DontVTSwitch is not set anywhere, I am just trying to rule out
possible causes.
--
MK
On Sun, Mar 07, 2010 at 10:12:38AM -0500, MK wrote:
> Recently alt-ctrl F1-8 to drop into a VT stopped working; I don't use
> this everyday so I am not sure when, but I believe it was after
> installing 2.5.28 -- going back to 2.5.26 didn't help tho, so I am not
> sure.
>
> Have there been any rep
Recently alt-ctrl F1-8 to drop into a VT stopped working; I don't use
this everyday so I am not sure when, but I believe it was after
installing 2.5.28 -- going back to 2.5.26 didn't help tho, so I am not
sure.
Have there been any reports of this?
--
MK