[BUG] Restarting docker container leads to a blank screen and Edge no longer launching/available,

[nicgord]

Is there an existing issue for this?

• I have searched the existing issues

Current Behavior

On first launch of docker container works great. If you have the browser open with tabs showing and restart the docker container edge no longer works at all. You are presented with a black screen and no way to launch Edge. (see attached image)

Expected Behavior

After restaring Docker Edge should work. (Doesnt matter if it remembers tabs or not)

Steps To Reproduce

Create docker container with config mounted to a local folder
Browse the web, open a few tabs
Do a docker stop and docker start
Try and access Edge.... it will be a black screen as attached.

Environment

- OS:
- How docker service was installed:

CPU architecture

x86-64

Docker creation

.

Container logs

.

[github-actions]

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

[nicgord]

Others having this problem are noted in this unrelated issue - #3

[ShonkaiDJ]

Others having this problem are noted in this unrelated issue - #3

That is not an unrelated issue. It is actually the same issue. The difference is they took it one step further to inspect what is going on and added a log line that might explain what happens.

As it goes on in the tread there, the mentioned problem in the log may not be the problem. (Could still be part of the solution, for obvious reasons)

What IS the work-around is to remove all the files in the config folder (see your compose file) and open it like new
AFTER which you do seem to have to close at least the tab in the browser where you run Edge in. When you close that tab, if you close that tab, edge will still be working even if you visit it after a restart of the container.

I think we would all agree that it should open even if you forgot to neatly close everything. But I still do not see how hat would make it an unrelated issue.

[thelamer]

Can anyone in this thread implement a similar concept as the chromium image and remove singletons on init if it is not running?
https://github.com/linuxserver/docker-chromium/blob/master/root/usr/bin/wrapped-chromium#L7

You would modify the microsoft-edge wrapper.
Or just in general does removing the singletons work to let it launch ?

[nicgord]

@ShonkaiDJ - The other issue is "ERROR: openbox-xdg-autostart requires PyXDG to be installed" was raised because of the error in the log with multiple people saying is not a concern.... are you say that installing PyXDG in the container fixes this issue?

If it is the same issue I am happy to close, but I think the description of the other issue may be ambiguous if it is not PyXDG that causes this.

[nicgord]

@thelamer I think you are onto something Did some testing and it seems deleting those files solves the issue.

For now I grabbed a copy of microsoft-edge from https://github.com/linuxserver/docker-msedge/blob/master/root/usr/bin/microsoft-edge

edited to include the following as the second line
rm /config/.config/microsoft-edge/Singleton*

Mounted the edited file via my docker compose.file
volumes:
- ./microsoft-edge:/usr/bin/microsoft-edge

I think it is working, will report back if I see error again before proposing a proper fix as a pull request.

[thelamer]

Resolved in the latest image

[ShonkaiDJ]

@ShonkaiDJ - The other issue is "ERROR: openbox-xdg-autostart requires PyXDG to be installed" was raised because of the error in the log with multiple people saying is not a concern.... are you say that installing PyXDG in the container fixes this issue?

If it is the same issue I am happy to close, but I think the description of the other issue may be ambiguous if it is not PyXDG that causes this.

No, that is not what I was trying to say. But I do confirm that the log error is not causing the black screen. I have the same error in my log but simply closing the browser-tab makes my screen come back every time, reboot after reboot. So my guess is these people are right the error is of no concern. The black screen is the human main issue. ;-)

[LinuxServer-CI]

This issue has been automatically marked as stale because it has not had recent activity. This might be due to missing feedback from OP. It will be closed if no further activity occurs. Thank you for your contributions.