LinuxServer.io
msedge isn't working after the Selkies update #157
Replies: 6 comments 4 replies
|
hi, thanks for reporting, at a minimum we will need your docker compose or run (we do not support deploying containers with any ui except unraid as they are known to introduce issues) We would also need your container logs, beginning with our ascii logo. thanks! |
|
Hi! Thanks for the quick response. Here are my Docker Compose configuration and container logs: Docker Compose Configservices:
msedge:
cpu_shares: 90
command: []
container_name: msedge
deploy:
resources:
limits:
memory: 15.37GB
cpus: "1.00"
reservations:
memory: 256MB
cpus: "0.00"
placement: {}
devices:
- /dev/dri:/dev/dri
entrypoint: null
environment:
CUSTOM_USER: afonsolfv
LC_ALL: pt_BR.UTF-8
LIBVA_DRIVER_NAME: iHD
PASSWORD: "***"
PGID: "1000"
PUID: "1000"
TZ: America/Sao_Paulo
image: linuxserver/msedge:latest
labels:
icon: https://upload.wikimedia.org/wikipedia/commons/thumb/7/7e/Microsoft_Edge_logo_%282019%29.png/250px-Microsoft_Edge_logo_%282019%29.png
network_mode: bridge
ports:
- target: 3000
published: "8000"
protocol: tcp
- target: 3001
published: "8001"
protocol: tcp
restart: unless-stopped
shm_size: "1073741824"
volumes:
- type: bind
source: /DATA/AppData/msedge/config
target: /config
- type: bind
source: /DATA/User/Downloads
target: /downloads
- type: bind
source: /media/sda1/Arquivos/Projetos Dev
target: /media/Projetos Dev
- type: bind
source: /DATA/AppData/msedge/fonts
target: /config/.local/share/fonts
x-casaos:
author: self
category: self
hostname: 192.168.31.52
icon: https://upload.wikimedia.org/wikipedia/commons/thumb/7/7e/Microsoft_Edge_logo_%282019%29.png/250px-Microsoft_Edge_logo_%282019%29.png
index: /
is_uncontrolled: false
main: msedge
port_map: "8001"
scheme: https
store_app_id: msedge
title:
custom: Edge
en_us: msedgeConsole LogPlease let me know if you need any additional information to troubleshoot this issue. Thank you! |
|
Please run linuxserver/webtop:dev and see if it works for you this is selkies head and will be the next release. For just the base which would translate more directly run lsiobase/selkies:dev and try typing in the terminal. |
|
Hi! Thanks for the reply! I tested linuxserver/webtop:dev, and it worked totally fine. I was able to type long texts without any issues, and the accentuation problem was gone—I could type anything using my keyboard layout. Going a bit further, I tested creating a fresh, clean container of msedge instead of upgrading my existing one. It ran smoothly without any tab freezing, except for the accented characters, which still don't work (for instance, I can't type "í" or "ú"). I'll roll back to the previous September build for now. If it were just a matter of starting fresh with a new container, I would happily do that and log into my profile to restore my history, but the main blocker is still the inability to type accents. That said, seeing that the accents worked fine on the webtop:dev build makes me hopeful that a future update will fix this! Thanks again for your help! |
|
Yeah we had a unicode coverage bug that did not pop up in testing because it starts having issues after an array of available characters is full. |
|
I just tested lsiobase/selkies:dev, and in the console, I was able to type everything smoothly, including all accented characters, which worked perfectly! There was no freezing at all. |
|
You are crashing because you only let it have 256mb of ram |
|
As I mentioned, I'm a beginner, so I might have made a mistake, but that doesn't seem to be the case here. I simply updated from the previous version, which was working fine with these exact same settings. I'm not sure if I was supposed to change anything in the YAML for the update. I tried change to 1GB, and still crashing. However, on a clean installation, this exact same YAML worked without crash, and the stats show SYSTEM MEMORY: 520MB / 15GB, so, seems like there's enough RAM available. Should I change something? |
|
Hi! I have an update that I think is worth sharing: I ran a bunch of tests with the latest available msedge image, but overall, none of them were working to get the special characters to show up. I tested on a few keyboard mapping websites, and whenever I press the keys for those characters, it is as if I didn't press anything at all. In some tests, there were even very unexpected results, like pressing However, I received one last tip that finally brought some results: using the environment variable As I mentioned before, inside the Selkies image (and even inside the msedge image when using the If there's anything else I can test or help investigate, please let me know! |
|
It just has not been updated yet selkies 2.1 is not out yet |
Uh oh!
There was an error while loading. Please reload this page.
Hi everyone!
I'm fairly new to the Docker world, still a beginner, but I've been using the linuxserver/msedge image for a few months now. I'm running it using ZimaOS 1.7.1. Usually, I update my Docker containers monthly. I was running a version from early September, and today (10/04/2026), I updated to the latest build, Index Digest sha256:74cbcae6d5fea76a2f3c4b105908b8b87cb1b6581fac1970306a5997f33b5120.
Right after updating, the first thing I noticed was that Selkies had been updated, and I was super impressed right off the bat! The new features look fantastic. However, I soon ran into a pretty frustrating issue. My main language is Brazilian Portuguese, which uses a lot of accented characters (like á, é, í, ó, ã, ê, etc.), and some of these accents stopped working reliably. It seems random — sometimes typing an "é" works, sometimes it doesn't; same for any other character.
On top of that, I hit a critical issue: on any webpage, whenever I started typing a longer piece of text, the browser tab would freeze completely. The only way to get it back was waiting for the "Tab Unresponsive: Wait or Exit?" prompt to pop up so I could force close it. Once I refreshed and tried typing again, it froze all over again. It got so bad that the container became unusable, so I had to roll back to the previous September version (before the new Selkies update), which didn't have any of these issues.
I'm running this on a pretty basic machine powered by an Intel Alder Lake N100 processor with integrated graphics (no dedicated GPU). Could this be related to my hardware setup, missing configuration, or is anyone else experiencing this bug?
Any help would be greatly appreciated!
Thanks so much in advance!
All reactions