Other i3 gnome keyring causing reliant programs to crash

stratacast1

stratacast1

I'm trying to solve an issue with Nextcloud core dumping when I sign into my user session. My suspicion is it has to do with my keyring. I switched from KDE to i3, which also meant I switched from kwallet to gnome-keyring. With my infinite knowledge (or 0) of debuggers, I did a backtrace and found that nextcloud is being sent a SIGABRT

Code: 
(lldb) bt all
* thread #1, name = 'nextcloud', stop reason = signal SIGABRT
  * frame #0: 0x000000080dc906ca
    frame #1: 0x000000080dc90680
  thread #2, name = 'nextcloud', stop reason = signal SIGABRT
    frame #0: 0x000000080dca312a
    frame #1: 0x000000080d593246
  thread #3, name = 'nextcloud', stop reason = signal SIGABRT
    frame #0: 0x000000080dca312a
    frame #1: 0x000000080d593246
  thread #4, name = 'nextcloud', stop reason = signal SIGABRT
    frame #0: 0x000000080dca312a
    frame #1: 0x000000080d593246
  thread #5, name = 'nextcloud', stop reason = signal SIGABRT
    frame #0: 0x000000080dce917a
    frame #1: 0x000000080d5937e3
  thread #6, name = 'nextcloud', stop reason = signal SIGABRT
    frame #0: 0x000000080d59eedc
    frame #1: 0x000000080d5926c0
  thread #7, name = 'nextcloud', stop reason = signal SIGABRT
    frame #0: 0x000000080d59eedc
    frame #1: 0x000000080d5926c0
  thread #8, name = 'nextcloud', stop reason = signal SIGABRT
    frame #0: 0x000000080dca312a
    frame #1: 0x000000080d593246

Even after my session has started, it will do this after trying to launch it about 2-5 times, and eventually it'll stick and I'll get a prompt for my keyring. This likely has something to do with my lack of knowledge with getting my keyring to work properly, which is hindering Nextcloud...at least that's what I'm seeing. This is what I have in my .xinitrc

Bash: 
eval $(/usr/local/bin/gnome-keyring-daemon --start --components=pkcs11,secrets)
export SSH_ASKPASS=/usr/local/bin/ssh-askpass; export SSH_ASKPASS
eval `ssh-agent -s`
ssh-add &

exec /usr/local/bin/i3

Any tips on getting around this issue?
 
I'm still stuck on this one, I know it has to do with how gnome-keyring starts. Nextcloud isn't the culprit here, but I can't figure out how to get gnome-keyring to consistently start
 
Greetings,

Just went through this some time ago, it has to do with some extra packages required.

This is part of a document I am writing, so I am just copy pasting here the relevant part of the chapter, adapt accordingly:

There is no need to install all of these packages, however if one wants to avoid issues with applications such as nextcloud client for instance (and probably with others), you need some extras such as dbus and dconf.

pkg install i3 i3blocks i3lock rofi seahorse libgnome-keyring dbus gsettings-desktop-schemas dconf gnome-keyring scrot arandr fish qt5-style-plugins rxvt-unicode adwaita-qt5 gnome-themes-extra git qt5ct

Add to /etc/rc.conf

Code: 
dbus_enable="YES"

and run service dbus start

Add to the file .xinitrc in your user home the following
Code: 
exec ssh-agent dbus-launch --csh-syntax --exit-with-session i3 -c ~/.config/i3
 
Last edited by a moderator:
x11-wm/i3 user here to. I'm not using gnome-keyring just a few commands in my .zshrc.
Code: 
# SSH & Keychain

 if [ -f ~/.ssh/agent.env ] ; then
    . ~/.ssh/agent.env > /dev/null
    if ! kill -0 $SSH_AGENT_PID > /dev/null 2>&1; then
        echo "Stale agent file found. Spawning a new agent. "
        eval `ssh-agent | tee ~/.ssh/agent.env`
        ssh-add
    fi
 else
     echo "Starting ssh-agent"
     eval `ssh-agent | tee ~/.ssh/agent.env`
     ssh-add
 fi

Works like a charm.
PS. Credits for those commands yash.
 
You must log in or register to reply here.
Back
Top