Other Help Topics :: Cannot type in Firefox fullscreen - DSL 4.0

Hi Robert,

Please don't let my comments about virtualization let us get off track here. I'm happy to know how you feel about virtualization. I was just bringing observations to the table.

Kimangroo reported the Firefox-F11-JWM issue based on an installation to hard-drive on a 500MHz laptop with 64MB of RAM.

My apologies for getting off track,
John

Looking through the DSL relatives i see KioskCD

There has been several DSL+kiosk combinations, but I don't recall keyboard issues off the top of my head.
Do you actually have an "UK" keyboard?
iirc there were kiosk extensions for firefox as well.

OT:

Quote

Sorry, I've never ever had success switching WMs while in virtualization so I cannot offer opposite effects. I end up with a black screen when I try this. Also, I've never ever had success exiting to console by using Ctrl+Alt+Backspace combo... this seems to be common combo on most Linux OS, am I just getting confused and it's different on DSL?

I've also seen this under vmware+DSL 4.0. You have to chvt back to the x server (ctrl+alt+f1 or f2) - hence the ctrl+alt+backspace will not work. You might need to press different codes to get the vm to capture the key presses.

Thanks for bearing with me on this one!

I did try KioskCD but thought it would be easier to configure my wireless card using DSL. As it happens KioskCD doesn't seem to boot fullscreen, and even when F11 is pressed a windows bar is still present. I tried BoothCD as well but haven't be able to get that to boot yet.

If I really can't work out what is going wrong, I can just use fluxbox and have firefox start after the desktop is loaded in xinitrc. That seems to be working. It's just that that seems to cut the whole "make an internet kiosk" project short and the fact that it should work but doesn't will just bug me endlessly!

As far as keyboards are concerned the original laptop I'm working on with the hard drive install is an Advent 7250 with a uk keyboard, the Toshiba has a Japanese keyboard, and the Acer desktop another UK keyboard. AFAICR they all show the same error when booting:

Cloop initializing cloop v2.1
Entering runlevel 5
Loading usr/share/keymaps/i386/qwerty/uk.kmap.gz
Operation failed

Is that not relevant at all? (no matter what keyboard lang I chose it fails to load) I hate to see any kind of "operation failed" message on boot!

Quote (kimangroo @ Nov. 30 2007,06:29)

AFAICR they all show the same error when booting:

Loading usr/share/keymaps/i386/qwerty/uk.kmap.gz
Operation failed

(no matter what keyboard lang I chose it fails to load)

Is this true if you accept the default english + US options that show up at the very beginning of a first run?

Maybe the support for all of the languages except the default has suffered a hit somehow?

Next Page...
original here.