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



Thanks for the suggestions John.

I ran firefox from the console as you said, unfortunately the only error I got was it not being able to run the flash plugin that I had tried to install earlier.

I've downloaded the latest DSL 4.1 RC3 as well but it's the same, still no cursor in full screen FF. In fact it's even a little worse; I can't even select text with the mouse.

????

I was wondering, can you replicate the problem with DSL (not DSL-N which seems to work)?

I have to leave that to one of the other guys for now Kim... I've had to temporarily move onto another OS because my laptop isn't responding to ACPI yet and it keeps shutting down when I hit critical temperature.  I hope to fix that on Saturday and get back to DSL.

Do you have a Windows machine where you could run the LiveCD under virtualization?  Microsoft is giving Virtual PC 2007 away for free and DSL runs very nicely in it.  I'd recommend using the QEMU embedded version offered at ibiblio, but on my machine, Norton AV 2002 notices the disk activity and scans every byte that passes through the QEMU/DSL setup... you can imagine that my CPU gets killed when that happens.

As you guessed earlier it seems to be a window manager problem Changing the window manager to Fluxbox gives no problems (running DSL 4.1rc3 on VirtualBox).

Another quirk is that if you attempt to change to a different desktop using Alt+<num> when FF is in fullscreen mode under JWM & then click the FF window restore button with the mouse FF has moved to the desktop selected by Alt+<num> while FF was in full screen mode (i.e. on a standard installation of DSL 4.1rc3: open FF, press F11, Press Alt+2, click FF window restore button - FF is now on desktop 2, rather than desktop 1! - check the pager bottom left)

Quote (andrewb @ Nov. 28 2007,21:33)
As you guessed earlier it seems to be a window manager problem Changing the window manager to Fluxbox gives no problems (running DSL 4.1rc3 on VirtualBox).

My hunch is it's a ram problem. 64M is a bit light for FF.  Try running 'base norestore' (minimal apps, etc).

The virtual environment is providing 128Mb of RAM so I don't think that is the problem (I can try more!)
Next Page...
original here.