PgAdmin4 STILL not usable when installed from RPMs on Fedora linux

Поиск
Список
Период
Сортировка
От Peter Juhasz
Тема PgAdmin4 STILL not usable when installed from RPMs on Fedora linux
Дата
Msg-id 1479906757.7320.23.camel@uhusystems.com
обсуждение исходный текст
Ответы Re: PgAdmin4 STILL not usable when installed from RPMs on Fedora linux
Re: PgAdmin4 STILL not usable when installed from RPMs on Fedora linux
Список pgadmin-support
Dear PgAdmin4 maintainers,

I've installed the latest pgadmin4-v1 package from the PGDG repository.
Unfortunately, it still does not work.

Now (as oppossed to the previous version of the package) there is a
pgadmin4 binary in the path, starting it results in the familiar "An
error occurred initialising the application server: Failed to locate
pgAdmin4.py, terminating server thread." message box and (usually) a
segmentation fault.

The reason for this is that the application does not know where to find
the python server backend. On my machine, it tries the following
locations:

stat("/home/pjuhasz/.config/pgAdmin Development Team/pgAdmin 4.conf", 0x7ffcb842f9b0) = -1 ENOENT (No such file or
directory)
stat("/home/pjuhasz/.config/pgAdmin Development Team/pgAdmin 4.conf", 0x7ffcb842f9b0) = -1 ENOENT (No such file or
directory)
stat("/home/pjuhasz/.config/pgAdmin Development Team/pgAdmin 4.conf", 0x7ffcb842f990) = -1 ENOENT (No such file or
directory)
stat("/home/pjuhasz/.config/pgAdmin Development Team.conf", 0x7ffcb842f9b0) = -1 ENOENT (No such file or directory)
stat("/home/pjuhasz/.config/pgAdmin Development Team.conf", 0x7ffcb842f9b0) = -1 ENOENT (No such file or directory)
stat("/home/pjuhasz/.config/pgAdmin Development Team.conf", 0x7ffcb842f990) = -1 ENOENT (No such file or directory)
stat("/etc/xdg/pgAdmin Development Team/pgAdmin 4.conf", 0x7ffcb842f9b0) = -1 ENOENT (No such file or directory)
stat("/etc/xdg/pgAdmin Development Team/pgAdmin 4.conf", 0x7ffcb842f9b0) = -1 ENOENT (No such file or directory)
stat("/etc/xdg/pgAdmin Development Team/pgAdmin 4.conf", 0x7ffcb842f990) = -1 ENOENT (No such file or directory)
stat("/etc/xdg/pgAdmin Development Team.conf", 0x7ffcb842f9b0) = -1 ENOENT (No such file or directory)
stat("/etc/xdg/pgAdmin Development Team.conf", 0x7ffcb842f9b0) = -1 ENOENT (No such file or directory)
stat("/etc/xdg/pgAdmin Development Team.conf", 0x7ffcb842f990) = -1 ENOENT (No such file or directory)

Not knowing the correct path it tries /usr/pgadmin4-
v1/runtime/pgAdmin4.py and even /pgAdmin4.py, then eventually gives up.

The package installs a pgadmin4.ini next to the pgAdmin4 binary,
containing the correct path, but this file is never accessed.

The reason for this is that QSettings is used in the pgadmin4 program
with default settings, which causes Qt to try the locations mentioned
above. This behavior is documented at e.g. http://doc.qt.io/archives/qt
-4.7/qsettings.html#platform-specific-notes .

Something is still wrong, though, because the application does not
start even after manually copying the provided pgadmin4.ini to one of
the previously mentioned locations.

I'd also like to mention that directory names with spaces and capital
letters are discouraged (to put it lightly) in Linux.


I can access the webapp from a browser after running "systemctl start
pgadmin4-v1.service", but
- this is not documented (AFAIK),
- this is not something I want to do,
- for users that don't have root permissions this might not be an
option.

Best regards,
Peter Juhasz




В списке pgadmin-support по дате отправления:

Предыдущее
От: Dave Page
Дата:
Сообщение: Re: pgScripts in pgAdmin4
Следующее
От: "Tomek"
Дата:
Сообщение: pgAdmin 4.x vs pgAdmin 3.x