You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Not sure if that's the cause of the issue or not, though.
On a different note, it would be nice if Nyxt either provided the location of the socket, or prompted the user for permission to delete the socket and continue.
Describe the bug
Nyxt fails to open due to existing socket.
I use XMonad, and for virtually all of the times I close programs, I use a keybinding of
, ("S-C-M1-q", kill1)
(doc: https://hackage.haskell.org/package/xmonad-contrib-0.18.1/docs/XMonad-Actions-CopyWindow.html#v:kill1)Not sure if that's the cause of the issue or not, though.
On a different note, it would be nice if Nyxt either provided the location of the socket, or prompted the user for permission to delete the socket and continue.
Precise recipe to reproduce the issue
flatpak install Downloads/nyxt-electron-4.0.0-pre-release-1.flatpak
&c.flatpak run engineer.atlas.Nyxt-Electron
flatpak run engineer.atlas.Nyxt-Electron
Information
nyxt --system-information
:Output when started from a shell
The text was updated successfully, but these errors were encountered: