Closed lrprawira closed 12 months ago
I have had encountered the same problem on Archlinux with DWM.
It was related to archlinux and the DBUS_SESSION_BUS_ADDRESS environment variable being setup incorrectly with something along the lines of unix:abstract=/tmp/dbus-randomchars,guid=aguidishere.
I also had no password keyring nor login password showing up in Seahorse, the GNOME application for managing encryption keys and passwords in the GNOME Keyring which is used by pgcli.
Following this post, I could solve my problem by exporting the following environnment variable in my .zshrc :
export DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/1000/bus
I have had encountered the same problem on Archlinux with DWM.
It was related to archlinux and the DBUS_SESSION_BUS_ADDRESS environment variable being setup incorrectly with something along the lines of unix:abstract=/tmp/dbus-randomchars,guid=aguidishere.
I also had no password keyring nor login password showing up in Seahorse, the GNOME application for managing encryption keys and passwords in the GNOME Keyring which is used by pgcli.
Following this post, I could solve my problem by exporting the following environnment variable in my .zshrc :
export DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/1000/bus
Thanks! Having the same problem with manjaro/bspwm. One day I hope to figure out how dbus works.
Thanks for the detailed answer, @evoludigit. :heart: No response from the original reporter for 18 months, I'll suppose that they have applied your fix. I'm thus closing this issue.
Description
pgcli
command just got stuck when executed but can still be aborted. Here is the traceback from when it timed out after 120 seconds:Your environment
pip freeze