When clicking on the min icon, or running min in a terminal, it should open a min window
Actually, when I do so, it opens min, then an error message appears, saying "An error has occurred. Close all windows and restart Min" (sorry it's in french for me, may be it is not the real error message since I translated it), then I click "Ok", and min closes.
I tried to :
/var/crash/ files, didn't worksudo apt remove min then install (with gdebi and apt), didn't worksudo apt purge min then install (with gdebi and apt), didn't workThe only other possibility I see is to build from source...
This problem happened because I wanted to access about:config to disable dns prefetch, but it redirected me to about:blank#blocked (see #issue-727173407)
So I tried to run sudo min, an error message told me that min didn't support that without the --no-sandbox.
So I tried sudo min --no-sandbox, this launched min as expected, but about:config was still blocked.
I closed min and relauched it manually : here comes the bug.
Now, when I run min in a terminal, I get this error (in terminal):
Gtk-Message: 19:17:56.430: GtkDialog mapped without a transient parent. This is discouraged.
And Min launches, but with the error message translated above, and I can't do anything except closing it...
It still works like a charm with sudo min --no-sandbox, no warning or error...
Any idea ? :innocent:
Found a way :smile:
I removed ~/.config/Min, and now it starts again, as first time.
But, strange thing, ~/.config/Min/Crash Report was empty...
I don't close the issue (because the bug is probably still here) but for me it is solved, close it if you want
A config/cache file was probably corrupt, you didn't need to delete the whole folder.
I wanted to access about:config
about:config is a special page in Firefox, it isn't universal. There isn't even an equivalent in Chrome (Chromium ; informative post) and Min is based on Electron, which means we'll need to implement such a page ourselves.
So I tried to run sudo min, an error message told me that min didn't support that without the --no-sandbox.
This is a Chromium thing: https://bugs.chromium.org/p/chromium/issues/detail?id=638180.
I'm leaving the issue open, at least until testing (reproduction) is done.
I supposed also that it wasn't the hole folder to delete, but I had searched before in .local and .cache, didn't find anything, so I deleted everything, but I'll remember if it happens gain.
Thanks for your explanation anyway :)
Yeah, you'll get this error message if either you have multiple instances running at the same time, or if your history database gets corrupted (which I don't think I've seen happen before, so it's kind of strange you would run into that immediately). So I guess if it happens again, please open another issue.