Created attachment 582576 [details] info file here: pgAdmin4 Python path: "/usr/lib64/python3.6/site-packages" Python Home: "" Webapp path: "/usr/share/pgadmin4/web/pgAdmin4.py" "Failed to launch the application server, server thread exiting.
libsodium minimal USE flag cancellation seems required. Sorry for the noise.
(In reply to CaptainBlood from comment #1) > libsodium minimal USE flag cancellation seems required. > Sorry for the noise. Well, now, that doesn't prevent it from happening to or fixing it for others. I need you to be clear on what you did to fix the issue. Is the only change you made to recompile dev-libs/libsodium with USE="-minimal"?
Prior to this libsodium issue, I activated ssl USE flag on dev-qt/qtnetwork package. I also flipped some qtwidgets USE flag back & forth, but finally cancelled such changes at the end of the day, IIRC. Unfortunately, although here is a per package file in /etc/portage/packages.use, I've mistakenly have reset all of these files timestamp (mis)using sed to create/update files to activate -python_targets_python2_7 constraint due to newly installed pgadmin4. So it has become quit difficult to retrieve the history leading to a working pgadmin4 here. Doubtedly, could't the problems you're facing being due to activated python2_7? Or dual python activated settings like I had in the beginning,e.g. python2_7/python3_6?
I've just tested pgadmin4 after flipping libsodium back to minimal. In the process, dev-python/pynacl has been rebuild, as the only libsodium dependent package. This raised the reported initial faulty behavior. While falling back to working pgadmin4, I first only rebuild libsodium: that led to a segfault at launch. Emerging pynacl a second time fixed that runtime segfault.
(In reply to CaptainBlood from comment #4) > I've just tested pgadmin4 after flipping libsodium back to minimal. > > In the process, dev-python/pynacl has been rebuild, as the only libsodium > dependent package. > > This raised the reported initial faulty behavior. > > While falling back to working pgadmin4, I first only rebuild libsodium: > that led to a segfault at launch. > > Emerging pynacl a second time fixed that runtime segfault. Thank you for taking the time to pinpoint the issue. We can add the requirement in dev-db/pgadmin4.
The bug has been referenced in the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=1218f5c7042155d1c4d5e062a8fd925a812d0e3e commit 1218f5c7042155d1c4d5e062a8fd925a812d0e3e Author: Aaron W. Swenson <titanofold@gentoo.org> AuthorDate: 2019-10-18 00:23:55 +0000 Commit: Aaron W. Swenson <titanofold@gentoo.org> CommitDate: 2019-10-18 00:24:14 +0000 dev-db/pgadmin4: Bump to 4.13 Now require ssl on dev-qt/qtnetwork, and minimal deactivated dev-libs/libsodium. Bug: https://bugs.gentoo.org/689708 Bug: https://bugs.gentoo.org/689678 Closes: https://bugs.gentoo.org/695970 Package-Manager: Portage-2.3.76, Repoman-2.3.16 Signed-off-by: Aaron W. Swenson <titanofold@gentoo.org> dev-db/pgadmin4/Manifest | 1 + dev-db/pgadmin4/pgadmin4-4.13.ebuild | 109 +++++++++++++++++++++++++++++++++++ 2 files changed, 110 insertions(+)
