Palemoon thinks it's already running when it isn't. Topic is solved

[xykreinov]

Whenever I try to start Pale Moon, I get this message:

Code: Select all

Pale Moon is already running, but is not responding. To open a new window, you must first close the existing Pale Moon process, or restart your system.

I check my system monitor and, every time, Pale Moon isn't already running prior to me trying to launch it. I've tried rebooting my system and reinstalling Pale Moon to no avail.
This behavior only started after migrating a system-user folder from an old Ubuntu install to my Artix install. So, I'm sure something about the Pale Moon folder from it is causing issues.
Any ideas for how I could go about fixing this besides just removing the old Pale Moon folder? I'd rather not have to reconfigure Pale Moon if I don't have to.

[Moonchild]

Check the directory's ownership and permissions. Pale Moon's process must have full write access.

[xykreinov]

Once I recursively gave user permissions to the Pale Moon folder (it and everything inside it) all works swimmingly.