i'm running feisty, and believe i have a simpler way of reproducing this
problem. i have never, to my knowledge, changed my local/language/etc.
(i'm in the US.)
boot the system. don't bother logging in to gdm.
switch directly to a console, with control-alt-F1.
log in, and run: "dialog --msgbo
i'm running feisty, and believe i have a simpler way of reproducing this
problem. i have never, to my knowledge, changed my local/language/etc.
(i'm in the US.)
boot the system. don't bother logging in to gdm.
switch directly to a console, with control-alt-F1.
log in, and run: "dialog --msgbo
i'm running feisty, and believe i have a simpler way of reproducing this
problem. i have never, to my knowledge, changed my local/language/etc.
(i'm in the US.)
boot the system. don't bother logging in to gdm.
switch directly to a console, with control-alt-F1.
log in, and run: "dialog --msgbo
i'm running feisty, and believe i have a simpler way of reproducing this
problem. i have never, to my knowledge, changed my local/language/etc.
(i'm in the US.)
boot the system. don't bother logging in to gdm.
switch directly to a console, with control-alt-F1.
log in, and run: "dialog --msgbo
i'm running feisty, and believe i have a simpler way of reproducing this
problem. i have never, to my knowledge, changed my local/language/etc.
(i'm in the US.)
boot the system. don't bother logging in to gdm.
switch directly to a console, with control-alt-F1.
log in, and run: "dialog --msgbo
i'm running feisty, and believe i have a simpler way of reproducing this
problem. i have never, to my knowledge, changed my local/language/etc.
(i'm in the US.)
boot the system. don't bother logging in to gdm.
switch directly to a console, with control-alt-F1.
log in, and run: "dialog --msgbo
