Re: Critical bug: pgAdmin v4.25 has started ignoring my "Browser Command" which completely cripples me and makes me unable to manage my PostgreSQL database.

Gosh, you're right, this does sound very rude.

I'm not sure where to start with this and I'm a user, not a developer of
the software, so shouldn't be taking this too personally.

You seem to have misread the licence of the software:
https://github.com/postgres/pgadmin4/blob/master/LICENSE.

As this is open source software, no one is guaranteeing you anything (why
should they, you didn't pay for it, right?). What they are guaranteeing you
is that the code is open for you to view and change if you so desire (given
certain conditions). There is a likelihood that other people will come and
fix and bugs, create new features, but that is not a given, nor should it
be.

If it is really "mission-critical software" then sitting around ranting in
a mailing list is not going to help you. If you are experiencing these
issues (personally I have had very few issues with the software, so can't
help you there). You need to do one of:

- Ask politely if anyone can help, file bugs properly on the bug tracker by
stating your system environment, steps to reproduce etc. Note, this email
does not meet the politeness criterion
- Obtain the skills yourself to fix your own issues, and ideally contribute
those back to the project
- Pay someone as a one off to fix the bugs you are experiencing or an
ongoing maintenance-type contract

I'm afraid your message just comes off as entitled, uninformed, and yes,
rude.

Stephen Knox

On Fri, Aug 21, 2020 at 11:23 AM <tutiluren(at)tutanota(dot)com> wrote:

> pgAdmin v4.25 has yet again broken something. After being harassed to
> upgrade to the latest version, pgAdmin has stopped opening itself properly.
>
> It no longer opens in the correct Pale Moon profile. It now opens in the
> *default* profile, which completely breaks everything. I've previously
> tried to explain how important it is for pgAdmin to have its own dedicated
> GUI/"webview", so I'm not going to go into details about why this is so
> important here. It seems to fall on deaf ears either way.
>
>
>