[BUG] Firefox not showing up on Kasm Web UI about docker-firefox HOT 18 CLOSED

Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid.

from docker-firefox.

I've got exactly the same problem it seems.

from docker-firefox.

Probably same error here, Unraid on x86:

Logmessage:
Obt-Message: Xinerama extension is not present on the server
Crash Annotation GraphicsCriticalError: |[0][GFX1-]: Unrecognized feature ACCELERATED_CANVAS2D (t=1.20744) [GFX1-]: Unrecognized feature ACCELERATED_CANVAS2D

from docker-firefox.

I've got the same error I think
`[migrations] started
[migrations] no migrations found
usermod: no changes
───────────────────────────────────────

  ██╗     ███████╗██╗ ██████╗ 
  ██║     ██╔════╝██║██╔═══██╗
  ██║     ███████╗██║██║   ██║
  ██║     ╚════██║██║██║   ██║
  ███████╗███████║██║╚██████╔╝
  ╚══════╝╚══════╝╚═╝ ╚═════╝ 

Brought to you by linuxserver.io
───────────────────────────────────────

To support LSIO projects visit:
https://www.linuxserver.io/donate/

───────────────────────────────────────
GID/UID
───────────────────────────────────────

User UID: 99
User GID: 100
───────────────────────────────────────

[custom-init] No custom files found, skipping...
[ls.io-init] done.
Obt-Message: Xinerama extension is not present on the server
Crash Annotation GraphicsCriticalError: |[0][GFX1-]: Unrecognized feature ACCELERATED_CANVAS2D (t=0.619822) [GFX1-]: Unrecognized feature ACCELERATED_CANVAS2D`

from docker-firefox.

Interestingly enough the https://github.com/linuxserver/docker-baseimage-kasmvnc behaves the same way no matter what GUI application I try to run, not just firefox. Nothing shows up in the VNC viewer, no errors as far as I can see.

My understanding is also that there is supposed to be a way of launching the GUI application directly from the desktop as there should be some kind of menu present. Nothing resembling this shows up either.

from docker-firefox.

@lczerner host info please and docker setup.
uname -a
runc --version
docker --version

from docker-firefox.

I have the same issue.
Host: omv
uname -a:
Linux omv 6.0.0-0.deb11.6-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.0.12-1~bpo11+1 (2022-12-19) x86_64 GNU/Linux
runc --version:

runc version 1.1.5
commit: v1.1.5-0-gf19387a
spec: 1.0.2-dev
go: go1.19.7
libseccomp: 2.5.1

docker --version:
Docker version 23.0.3, build 3e7cbfd

Last working image: lscr.io/linuxserver/firefox:101.0.1
Not working image: lscr.io/linuxserver/firefox:109.0.1-r0-ls87

from docker-firefox.

I have the same issue. Host: omv uname -a: Linux omv 6.0.0-0.deb11.6-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.0.12-1~bpo11+1 (2022-12-19) x86_64 GNU/Linux runc --version:

runc version 1.1.5
commit: v1.1.5-0-gf19387a
spec: 1.0.2-dev
go: go1.19.7
libseccomp: 2.5.1

docker --version: Docker version 23.0.3, build 3e7cbfd

Last working image: lscr.io/linuxserver/firefox:101.0.1 Not working image: lscr.io/linuxserver/firefox:109.0.1-r0-ls87

Same issue as in Firefox tries to start up at 100% cpu for like 5-10 minutes then suddenly loads?
Where you can manually kill two pids for the stuck Firefox and it will then load?
If so it seems like this is a Firefox thing and Kernel 6 host level, all reports of this and my own testing were running kernel 6+.

There is not really anything I can do to fix that, my only recommendation would be to use the chromium image https://github.com/linuxserver/docker-chromium

from docker-firefox.

okay, I am confused. My docker-firefox latest is back again:

But I have no idea why. I did a lot of tests yesterday and today, the action was to run docker-chromium on another port and due to an problem when running docker-chromium and docker-firefox on the same time (both using internal as default port 3000 and 3001) I simply down the testing compose for the docker-chromium and restart my docker-firefox testing compose.

Perhaps some hints:
-increased the given ram to 4gb instead of 1gb for a short time
-force-recreate the testing-docker-compose once
-changed the autorun file within the contaoner (exec into it)once to "firefox --ProfileManager"

from docker-firefox.

okay, I am confused. My docker-firefox latest is back again: But I have no idea why. I did a lot of tests yesterday and today, the action was to run docker-chromium on another port and due to an problem when running docker-chromium and docker-firefox on the same time (both using internal as default port 3000 and 3001) I simply down the testing compose for the docker-chromium and restart my docker-firefox testing compose.

Perhaps some hints: -increased the given ram to 4gb instead of 1gb for a short time -force-recreate the testing-docker-compose once -changed the autorun file within the contaoner (exec into it)once to "firefox --ProfileManager"

That's good info, the profile generation might be to blame I'll look at that angle.

from docker-firefox.

changing shm_size: "1gb" to shm_size: "5gb" fixed it for me (on synology).

from docker-firefox.

I have fixed a bug in the base where there could be a potential race condition on load. Can any users please pull the latest image and let me know if this is fixed for them?

from docker-firefox.

For me it's working now on Unraid 6.11.5

from docker-firefox.

Working on synology DSM 7 Docker.

from docker-firefox.

Ok, thats good, I don't think the shm changes are needed the race condition was random and that was more likely it.

from docker-firefox.

I have the same issue. Host: omv uname -a: Linux omv 6.0.0-0.deb11.6-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.0.12-1~bpo11+1 (2022-12-19) x86_64 GNU/Linux runc --version:

runc version 1.1.5
commit: v1.1.5-0-gf19387a
spec: 1.0.2-dev
go: go1.19.7
libseccomp: 2.5.1

docker --version: Docker version 23.0.3, build 3e7cbfd

I can confirm that it is working again with my original 2gb shm size.

THX a lot @thelamer <3

from docker-firefox.

I can also confirm it's working.

from docker-firefox.

I have the same problem except it starts after "a while" (the better part of an hour). I see it using a full core during this warm up period.

❯ dc exec firefox ps aux --sort pcpu | tail -n1
abc          261 99.8  0.1 330748 16576 ?        R    17:19   5:44 /usr/lib/firefox/firefox

I haven't investigated the issue. I'll try increasing shm_size.

from docker-firefox.