Closed sgebauer closed 3 years ago
I am unable to reproduce this.
However, it could be related to me sidestepping the usual launch shell script in order to upgrade to upstream zypak
, if you're sure this isn't caused by something else I'll just revert it and try a cleaner workaround the next time.
I can reproduce this in a fresh Debian 10 VM, so it's not caused by any part of my specific setup.
The only additional condition seems to be that atom's restored state needs to have a project folder open. Starting from a fresh install, you need to do the following:
@sgebauer just to make sure before I merge, could you please test the build here to see whether it fixes your issue?
Yes, i can't reproduce it any more with the linked build.
Since the last update, atom always launches two instances.
To reproduce, simply run
flatpak run io.atom.Atom
. A few seconds after atom has started, a second atom window will open. This second window...$HOME/.var/app/io.atom.Atom/data/compile-cache
as the project folderThis does not happen if i revert to the last commit (
flatpak update --commit=7302bb14a117f156ef58ade8a7ac1cb51b6133cd8e9c672c223e24651c4de1ff io.atom.Atom
).(Flatpak version is 1.10.1 from Debian buster-backports)