You are not logged in.

#1 2021-10-11 17:10:21

p-scvtvlatvs
Member
Registered: 2021-10-11
Posts: 27

dbus-daemon: Failed to activate service 'org.freedesktop.secrets'

Hi everyone,

I'm relatively new to Arch, and, I want to be able to use libsecret to manage my git credentials.  However, I'm not able to use gnome-keyring-daemon to save my github.com personal access token because of the following error displayed by journalctl -t dbus-daemon:
https://pastebin.com/93nVj5wP

My .xinitrc file can be seen at:
https://pastebin.com/ff8gD4f3

Any clues on this matter?

Offline

#2 2021-10-11 20:52:56

seth
Member
Registered: 2012-09-03
Posts: 24,049

Re: dbus-daemon: Failed to activate service 'org.freedesktop.secrets'

Is "localhostname" your actual hostname?

More important than *that* gnome-keyring-daemon could not be started or bound to the session bus is *why*.
Output of

loginctl session-status

Does

/usr/bin/gnome-keyring-daemon --start --foreground --components=secrets

print any errors?
Or does it start and can you then use gnome-keyring?

Online

#3 2021-10-11 22:04:47

p-scvtvlatvs
Member
Registered: 2021-10-11
Posts: 27

Re: dbus-daemon: Failed to activate service 'org.freedesktop.secrets'

Hi,

1. I change the hostname for this forum purposes.
2. The output of

 loginctl session-status 

starts with the following, among other things:

 37499 /usr/bin/gnome-keyring-daemon --start --components=pkcs11 

and then it continues at the end with the following:

Oct 11 17:55:58 localhostname gnome-keyring-daemon[37499]: The Secret Service was already initialized
Oct 11 17:55:58 localhostname org.freedesktop.secrets[39797]: SSH_AUTH_SOCK=/home/localusername/.xdg/runtime/keyring/ssh
Oct 11 17:55:58 localhostname gnome-keyring-d[37499]: The Secret Service was already initialized
Oct 11 17:56:23 localhostname evolution-sourc[37545]: secret_monitor_scan_secrets_thread: Error calling StartServiceByName for org.freedesktop.secrets: Timeout was reached
Oct 11 17:57:58 localhostname dbus-daemon[37457]: [session uid=1000 pid=37455] Failed to activate service 'org.freedesktop.secrets': timed out (service_start_timeout=120000ms)
Oct 11 17:58:02 localhostname gnome-session[37408]: gnome-session-binary[37408]: WARNING: Could not get session path for session. Check that logind is properly installed and pam_systemd is getting used at login.
Oct 11 17:58:02 localhostname gnome-session-binary[37408]: WARNING: Could not get session path for session. Check that logind is properly installed and pam_systemd is getting used at login.
Oct 11 18:09:07 localhostname gnome-session[37408]: gnome-session-binary[37408]: WARNING: Could not get session path for session. Check that logind is properly installed and pam_systemd is getting used at login.
Oct 11 18:09:07 localhostname gnome-session-binary[37408]: WARNING: Could not get session path for session. Check that logind is properly installed and pam_systemd is getting used at login.
Oct 11 18:09:07 localhostname org.gnome.Shell.desktop[37507]: Window manager warning: last_focus_time (29487303) is greater than comparison timestamp (29487278).  This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW.  Trying to work around...

3. The output of:

 /usr/bin/gnome-keyring-daemon --start --foreground --components=secrets 

is the following, but it looks like is waiting for something because the shell does not returns:

 SSH_AUTH_SOCK=/home/localusername/.xdg/runtime/keyring/ssh 

4. It looks like it starts but it appears not to work.


I remember that, the first time I started a git operation in a login session, a dialog would open asking me for a passphrase or password.  But now, nothing appears and it bails out with a timeout and it asks me for my personal access token (github password).

Thanks for the help!

Last edited by p-scvtvlatvs (2021-10-11 22:19:26)

Offline

#4 2021-10-11 23:30:18

loqs
Member
Registered: 2014-03-06
Posts: 13,968

Re: dbus-daemon: Failed to activate service 'org.freedesktop.secrets'

Please do not just post the parts of outputs you believe are relevant.  From the loginctl session-status you missed the entries that would have shown if the session was considered active and local.

Offline

#5 2021-10-12 00:14:02

p-scvtvlatvs
Member
Registered: 2021-10-11
Posts: 27

Re: dbus-daemon: Failed to activate service 'org.freedesktop.secrets'

Ok, here's the full output of

 loginctl session-status 
15 - procer (1000)
           Since: Mon 2021-10-11 16:55:56 UTC; 7h ago
          Leader: 37352 (login)
            Seat: seat0; vc1
             TTY: tty1
         Service: login; type tty; class user
           State: active
            Unit: session-15.scope
                  ├─37352 "login -- procer" "" "" "" "" "" "" "" ""
                  ├─37362 /bin/sh /usr/bin/startx /home/procer/.xdg/config/X11/xinit/xinitrc /home/procer/.xdg/config/X11/xinit/xserverrc -- vt1 -keeptty
                  ├─37397 xinit /home/procer/.xdg/config/X11/xinit/xinitrc /home/procer/.xdg/config/X11/xinit/xserverrc -- /usr/bin/X :1 vt1 -keeptty -auth /tmp/serverauth.8CbKotNFSs
                  ├─37398 /usr/lib/Xorg :1 vt1 -keeptty -auth /tmp/serverauth.8CbKotNFSs
                  ├─37408 /usr/lib/gnome-session-binary
                  ├─37420 /usr/bin/VBoxClient --clipboard
                  ├─37422 /usr/bin/VBoxClient --clipboard
                  ├─37432 /usr/bin/VBoxClient --seamless
                  ├─37433 /usr/bin/VBoxClient --seamless
                  ├─37439 /usr/bin/VBoxClient --draganddrop
                  ├─37440 /usr/bin/VBoxClient --draganddrop
                  ├─37447 /usr/bin/VBoxClient --vmsvga
                  ├─37448 /usr/bin/VBoxClient --vmsvga
                  ├─37456 dbus-launch --exit-with-session /usr/lib/gnome-session-binary
                  ├─37457 /usr/bin/dbus-daemon --syslog --fork --print-pid 4 --print-address 6 --session
                  ├─37464 /usr/lib/gvfsd
                  ├─37469 /usr/lib/gvfsd-fuse /home/procer/.xdg/runtime/gvfs -f
                  ├─37478 /usr/lib/at-spi-bus-launcher
                  ├─37483 /usr/bin/dbus-daemon --config-file=/usr/share/defaults/at-spi2/accessibility.conf --nofork --print-address 3
                 ├─37499 /usr/bin/gnome-keyring-daemon --start --components=pkcs11
                  ├─37507 /usr/bin/gnome-shell
                  ├─37538 /usr/lib/gnome-shell-calendar-server
                  ├─37545 /usr/lib/evolution-source-registry
                  ├─37552 /usr/lib/goa-daemon
                  ├─37556 /usr/lib/evolution-calendar-factory
                  ├─37570 /usr/lib/goa-identity-service
                  ├─37571 /usr/lib/gvfs-udisks2-volume-monitor
                  ├─37591 /usr/lib/gvfs-mtp-volume-monitor
                  ├─37600 /usr/lib/dconf-service
                  ├─37602 /usr/lib/evolution-addressbook-factory
                  ├─37605 /usr/lib/gvfs-gphoto2-volume-monitor
                  ├─37613 /usr/lib/gvfs-goa-volume-monitor
                  ├─37620 /usr/lib/gvfs-afc-volume-monitor
                  ├─37634 /usr/bin/gjs /usr/share/gnome-shell/org.gnome.Shell.Notifications
                  ├─37636 /usr/lib/at-spi2-registryd --use-gnome-session
                  ├─37648 /usr/lib/gsd-usb-protection
                  ├─37649 /usr/lib/gsd-media-keys
                  ├─37651 /usr/lib/gsd-wwan
                  ├─37654 /usr/lib/gsd-rfkill
                  ├─37656 /usr/lib/gsd-a11y-settings
                  ├─37660 /usr/lib/gsd-wacom
                  ├─37664 /usr/lib/gsd-power
                  ├─37665 /usr/lib/gsd-screensaver-proxy
                  ├─37666 /usr/lib/gsd-color
                  ├─37669 /usr/lib/gsd-xsettings
                  ├─37671 /usr/lib/gsd-print-notifications
                  ├─37672 /usr/lib/gsd-sharing
                  ├─37674 /usr/lib/gsd-datetime
                  ├─37678 /usr/lib/gsd-smartcard
                  ├─37679 /usr/lib/gsd-housekeeping
                  ├─37684 /usr/lib/gsd-sound
                  ├─37689 /usr/lib/gsd-keyboard
                  ├─37708 /usr/lib/gsd-printer
                  ├─37713 /usr/bin/gjs /usr/share/gnome-shell/org.gnome.ScreenSaver
                  ├─37785 /usr/lib/tracker-miner-fs-3
                  ├─37786 /usr/bin/gnome-software --gapplication-service
                  ├─37787 /usr/lib/evolution-data-server/evolution-alarm-notify
                  ├─37790 /usr/lib/gsd-disk-utility-notify
                  ├─37931 /usr/bin/gnome-calendar --gapplication-service
                  ├─37935 /usr/bin/seahorse --gapplication-service
                  ├─37952 /usr/lib/gvfsd-trash --spawner :1.3 /org/gtk/gvfs/exec_spaw/0
                  ├─38063 /usr/lib/firefox/firefox
                  ├─38164 /usr/lib/firefox/firefox -contentproc -childID 1 -isForBrowser -prefsLen 1 -prefMapSize 243773 -jsInit 286204 -parentBuildID 20211004184504 -appdir /usr/lib/firefox/browser 38063 true tab
                  ├─38204 /usr/lib/gvfsd-metadata
                  ├─38272 /usr/lib/firefox/firefox -contentproc -childID 2 -isForBrowser -prefsLen 4816 -prefMapSize 243773 -jsInit 286204 -parentBuildID 20211004184504 -appdir /usr/lib/firefox/browser 38063 true tab
                  ├─38321 /usr/lib/firefox/firefox -contentproc -childID 3 -isForBrowser -prefsLen 5515 -prefMapSize 243773 -jsInit 286204 -parentBuildID 20211004184504 -appdir /usr/lib/firefox/browser 38063 true tab
                  ├─38364 /usr/lib/firefox/firefox -contentproc -childID 4 -isForBrowser -prefsLen 7647 -prefMapSize 243773 -jsInit 286204 -parentBuildID 20211004184504 -appdir /usr/lib/firefox/browser 38063 true tab
                  ├─38472 /usr/lib/firefox/firefox -contentproc -parentBuildID 20211004184504 -prefsLen 8540 -prefMapSize 243773 -appdir /usr/lib/firefox/browser 38063 true rdd
                  ├─38526 /usr/lib/gnome-terminal-server
                  ├─38639 zsh
                  ├─38983 /usr/lib/firefox/firefox -contentproc -childID 5 -isForBrowser -prefsLen 8813 -prefMapSize 243773 -jsInit 286204 -parentBuildID 20211004184504 -appdir /usr/lib/firefox/browser 38063 true tab
                 ├─40576 /usr/lib/firefox/firefox -contentproc -childID 11 -isForBrowser -prefsLen 9915 -prefMapSize 243773 -jsInit 286204 -parentBuildID 20211004184504 -appdir /usr/lib/firefox/browser 38063 true tab
                  ├─40763 /usr/lib/firefox/firefox -contentproc -childID 13 -isForBrowser -prefsLen 9915 -prefMapSize 243773 -jsInit 286204 -parentBuildID 20211004184504 -appdir /usr/lib/firefox/browser 38063 true tab
                  └─40948 loginctl session-status

Oct 11 18:26:37 hydrivm dbus-daemon[37457]: [session uid=1000 pid=37455] Successfully activated service 'com.intel.dleyna-renderer'
Oct 11 18:26:37 hydrivm dleyna-renderer-service[40401]: Calling GetRenderers method
Oct 11 18:26:37 hydrivm dleyna-renderer-service[40401]: Client :1.92 lost
Oct 11 18:26:38 hydrivm dleyna-renderer-service[40401]: dLeyna: Exit
Oct 11 18:26:43 hydrivm gnome-keyring-daemon[37499]: The Secret Service was already initialized
Oct 11 18:26:43 hydrivm gnome-keyring-d[37499]: The Secret Service was already initialized
Oct 11 22:26:04 hydrivm gnome-session[37408]: gnome-session-binary[37408]: WARNING: Could not get session path for session. Check that logind is properly installed and pam_systemd is getting used at login.
Oct 11 22:26:04 hydrivm gnome-session-binary[37408]: WARNING: Could not get session path for session. Check that logind is properly installed and pam_systemd is getting used at login.
Oct 11 22:27:37 hydrivm gnome-session[37408]: gnome-session-binary[37408]: WARNING: Could not get session path for session. Check that logind is properly installed and pam_systemd is getting used at login.
Oct 11 22:27:37 hydrivm gnome-session-binary[37408]: WARNING: Could not get session path for session. Check that logind is properly installed and pam_systemd is getting used at login.

Last edited by p-scvtvlatvs (2021-10-12 13:50:04)

Offline

#6 2021-10-12 06:39:50

seth
Member
Registered: 2012-09-03
Posts: 24,049

Re: dbus-daemon: Failed to activate service 'org.freedesktop.secrets'

                  ├─37456 dbus-launch --exit-with-session /usr/lib/gnome-session-binary
                  ├─37457 /usr/bin/dbus-daemon --syslog --fork --print-pid 4 --print-address 6 --session

What is this? Why is a second gnome-session-binary dbus-launched?
It clearly seems to taint the session bus of the main instance.

echo $DBUS_SESSION_BUS_ADDRESS

Online

#7 2021-10-12 13:47:18

p-scvtvlatvs
Member
Registered: 2021-10-11
Posts: 27

Re: dbus-daemon: Failed to activate service 'org.freedesktop.secrets'

Here's the output:

echo $DBUS_SESSION_BUS_ADDRESS
unix:abstract=/tmp/dbus-iKDkaYNlAX,guid=4260fdd44b6e39cd93d6951e61646c9d

The only operation that I know of that deals with DBUS is in my .zshrc:

#!/usr/bin/env /usr/bin/zsh
# ------------------------------------------------------------------------------

if [[ -z ${DBUS_SESSION_BUS_ADDRESS} ]]; then
	if [[ -f ~/.dbus/session-bus/$(dbus-uuidgen --get)-0 ]]; then
		source ~/.dbus/session-bus/$(dbus--uuidgen --get)-0
		export DBUS_SESSION_BUS_ADDRESS
	fi
fi

I don't know where did I got that from.  Anyways, it's not being executed since I don't have a ~/.dbus directory.  Should I delete it from my .zshrc?

Offline

#8 2021-10-12 13:52:50

seth
Member
Registered: 2012-09-03
Posts: 24,049

Re: dbus-daemon: Failed to activate service 'org.freedesktop.secrets'

You'd want it to be sth. like "unix:path=/run/user/1000/bus"
So there's why stuff doesn't work - we just need to figure how you got there.

grep -r "dbus-launch" ~

Online

#9 2021-10-12 14:28:09

p-scvtvlatvs
Member
Registered: 2021-10-11
Posts: 27

Re: dbus-daemon: Failed to activate service 'org.freedesktop.secrets'

Here's the output:

grep -r "dbus-launch" ~       
grep: /home/procer/.xdg/runtime/systemd/inaccessible/reg: Permission denied
grep: /home/procer/.xdg/runtime/systemd/inaccessible/dir: Permission denied
/home/procer/.xdg/config/zsh/zhistory:: 1634048635:0;grep -r "dbus-launch" ~
grep: /home/procer/.xdg/config/antigen/.zcompdump.zwc: binary file matches
/home/procer/.xdg/config/antigen/.zcompdump:'dbus-launch' '_dbus'

Offline

#10 2021-10-12 14:34:02

seth
Member
Registered: 2012-09-03
Posts: 24,049

Re: dbus-daemon: Failed to activate service 'org.freedesktop.secrets'

Boring.

How do you login and startx?
If you only log into a console shell, do you get a proper $DBUS_SESSION_BUS_ADDRESS / loginctl session-status?

Online

#11 2021-10-12 14:52:56

p-scvtvlatvs
Member
Registered: 2021-10-11
Posts: 27

Re: dbus-daemon: Failed to activate service 'org.freedesktop.secrets'

Here's the contents of my .zprofile:

#!/usr/bin/env /usr/bin/zsh
# ------------------------------------------------------------------------------
systemctl --user import-environment PATH
systemctl --user set-environment XDG_VTNR=1
systemctl --user start xorg@0.socket
[[ -z ${DISPLAY} ]] && export DISPLAY=localhost:0.0
[[ -n ${XDG_VTNR} ]] && (( ${XDG_VTNR} == 1 )) \
	&& exec startx ${XDG_CONFIG_HOME}/X11/xinit/xinitrc \
		${XDG_CONFIG_HOME}/X11/xinit/xserverrc -- vt${XDG_VTNR} -keeptty \
		> ${XDG_DATA_HOME}/xorg/Xorg.log 2>&1
# ------------------------------------------------------------------------------

Last edited by p-scvtvlatvs (2021-10-12 15:02:07)

Offline

#12 2021-10-12 15:06:22

p-scvtvlatvs
Member
Registered: 2021-10-11
Posts: 27

Re: dbus-daemon: Failed to activate service 'org.freedesktop.secrets'

Here are the content(s) of my:

.xserverrc:
https://termbin.com/jpm7

.xinitrc:
https://termbin.com/8wzx

.zprofile:
https://termbin.com/yl2i

Last edited by p-scvtvlatvs (2021-10-12 15:13:28)

Offline

#13 2021-10-12 15:48:03

seth
Member
Registered: 2012-09-03
Posts: 24,049

Re: dbus-daemon: Failed to activate service 'org.freedesktop.secrets'

What is this, why is this and where did you get that from?
You're starting X11 via startx and also as a socket activated systemd user service and I'd not be surprised if this causes gnome-session-binary to trigger a second server start and itself via dbus-launch… or whatever.

# systemctl --user import-environment PATH
# systemctl --user set-environment XDG_VTNR=1
# systemctl --user start xorg@0.socket
# [[ -z ${DISPLAY} ]] && export DISPLAY=localhost:0.0
[[ -n ${XDG_VTNR} ]] && (( ${XDG_VTNR} == 1 )) \
	&& exec startx ${XDG_CONFIG_HOME}/X11/xinit/xinitrc \
		${XDG_CONFIG_HOME}/X11/xinit/xserverrc -- vt${XDG_VTNR} -keeptty \
		> ${XDG_DATA_HOME}/xorg/Xorg.log 2>&1

Online

#14 2021-10-12 16:26:11

p-scvtvlatvs
Member
Registered: 2021-10-11
Posts: 27

Re: dbus-daemon: Failed to activate service 'org.freedesktop.secrets'

I don't remember where did I got all that.  I think I saw it somewhere and joined all those commands together.

What could be the best approach to start X?

I commented all those lines and all I get now is the password prompt from the shell.  It looks like no keyring is being used.

Last edited by p-scvtvlatvs (2021-10-12 16:32:33)

Offline

#15 2021-10-12 16:33:49

seth
Member
Registered: 2012-09-03
Posts: 24,049

Re: dbus-daemon: Failed to activate service 'org.freedesktop.secrets'

Updated session-status?

Online

#16 2021-10-12 17:08:16

p-scvtvlatvs
Member
Registered: 2021-10-11
Posts: 27

Re: dbus-daemon: Failed to activate service 'org.freedesktop.secrets'

Here's the update:

 loginctl session-status 

https://termbin.com/0aoud

Offline

#17 2021-10-12 17:45:31

seth
Member
Registered: 2012-09-03
Posts: 24,049

Re: dbus-daemon: Failed to activate service 'org.freedesktop.secrets'

Nothing about the session and esp. the dbus-lauch call changed.
What starts the vboxclient processes (they come up twice as well)?

seth wrote:

If you only log into a console shell, do you get a proper $DBUS_SESSION_BUS_ADDRESS / loginctl session-status?

ie. don't startx from your zprofile and check the status there.

Online

#18 2021-10-12 18:04:09

p-scvtvlatvs
Member
Registered: 2021-10-11
Posts: 27

Re: dbus-daemon: Failed to activate service 'org.freedesktop.secrets'

seth wrote:

Nothing about the session and esp. the dbus-launch call changed.
What starts the vboxclient processes (they come up twice as well)?

I think it's the VirtualBox VM Guest Additions (it might be related to the VirtualBox kernel modules, I don't know)

seth wrote:

If you only log into a console shell, do you get a proper $DBUS_SESSION_BUS_ADDRESS / loginctl session-status?

I think I'm not getting a dbus session at all, I'm a bit lost here...  How should I proceed?

seth wrote:

ie. don't startx from your zprofile and check the status there.

Where should I startx from?  I might consider to use GDM instead of starting X after each login.

What do you mean with check the status there?


Sorry about all the questions, I feel very newbie on this, thanks for your time by the way!

Last edited by p-scvtvlatvs (2021-10-12 18:17:04)

Offline

#19 2021-10-12 19:56:34

seth
Member
Registered: 2012-09-03
Posts: 24,049

Re: dbus-daemon: Failed to activate service 'org.freedesktop.secrets'

I think it's the VirtualBox VM Guest Additions

It actually comes from /etc/xdg/autostart/vboxclient.desktop (checked virtualbox-guest-utils) and probably runs twice because gnome-session-binary does.

I might consider to use GDM instead of starting X after each login.

Your zprofile suggests that startx runs automatically?
Prevent that, so you'll only log into the console - there "echo $DBUS_SESSION_BUS_ADDRESS" and "loginctl session-status" so we can see those states before any efforts to start X11 or gnome.

Online

#20 2021-10-12 21:24:12

p-scvtvlatvs
Member
Registered: 2021-10-11
Posts: 27

Re: dbus-daemon: Failed to activate service 'org.freedesktop.secrets'

Ok, I commented everything in .zprofile, and did

echo $DBUS_SESSION_BUS_ADDRESS

which returned nothing.  Here's the loginctl session-status output:

https://termbin.com/5mp2

It looks like something is missing...

Last edited by p-scvtvlatvs (2021-10-12 21:24:46)

Offline

#21 2021-10-12 21:40:22

seth
Member
Registered: 2012-09-03
Posts: 24,049

Re: dbus-daemon: Failed to activate service 'org.freedesktop.secrets'

No, the session-status looks fine (but for the many empty login parameters), but the absent $DBUS_SESSION_BUS_ADDRESS isn't good.

Did you alter any PAM configs?

pacman -Qikk pambase systemd
stat /usr/lib/security/pam_systemd.so

Online

#22 2021-10-12 21:58:01

p-scvtvlatvs
Member
Registered: 2021-10-11
Posts: 27

Re: dbus-daemon: Failed to activate service 'org.freedesktop.secrets'

Here's the stdout of:

 pacman -Qikk pambase systemd 

    https://termbin.com/dt6ek


Here's the stderr:

    https://termbin.com/l8pt


Here's the output of:

 stat /usr/lib/security/pam_systemd.so 

    https://termbin.com/kx51


This is what I have in /etc/security/pam_env.conf:

    https://termbin.com/s5r4

Last edited by p-scvtvlatvs (2021-10-12 22:20:28)

Offline

#23 2021-10-12 22:02:36

seth
Member
Registered: 2012-09-03
Posts: 24,049

Re: dbus-daemon: Failed to activate service 'org.freedesktop.secrets'

Nope. Do you get a $DBUS_SESSION_BUS_ADDRESS if you change your default shell back to bash?

Online

#24 2021-10-12 22:09:03

p-scvtvlatvs
Member
Registered: 2021-10-11
Posts: 27

Re: dbus-daemon: Failed to activate service 'org.freedesktop.secrets'

seth wrote:

Nope. Do you get a $DBUS_SESSION_BUS_ADDRESS if you change your default shell back to bash?

I changed my shell to bash and echo $DBUS_SESSION_BUS_ADDRESS, but it still returns nothing.

Offline

#25 2021-10-12 22:18:10

seth
Member
Registered: 2012-09-03
Posts: 24,049

Re: dbus-daemon: Failed to activate service 'org.freedesktop.secrets'

You can probably plaster over the the original problem by "export DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/1000/bus" in your zprofile before the startx segment, but that will just hide the problem and I'm running out of ideas why it might not be set.

Online

Board footer

Powered by FluxBB