Arch Linux

Pryka

Member

Registered: 2018-02-07

Posts: 85

[SOLVED]Apps can't connect to gnome-keyring and kde-wallet

I'm posting It here but I'm not really sure is a testing issue, but since I have no idea what is going on and I'm on testing... Here I am.

Since today all my apps using gnome-keyring or kdewallet can't connect to them. Chrome forgets all his sessions, Mainspring won't even start Skype ask for credentials on every restart.

This is how Google-Chrome logs look like when I try to force him to use kwallet or gnome-keyring:

kwallet

[813:813:1226/121840.961209:ERROR:bus.cc(396)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix")
[813:901:1226/121840.979689:ERROR:bus.cc(396)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix")
[813:813:1226/121840.961238:ERROR:kwallet_dbus.cc(100)] Error contacting kwalletd (isEnabled)
[813:813:1226/121841.005343:ERROR:bus.cc(396)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix")
[813:813:1226/121841.005373:ERROR:kwallet_dbus.cc(72)] Error contacting klauncher to start kwalletd
[813:813:1226/121841.005422:ERROR:bus.cc(396)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix")
[813:813:1226/121841.005452:ERROR:kwallet_dbus.cc(414)] Error contacting kwalletd (close)
[813:901:1226/121842.966833:ERROR:bus.cc(396)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix")
[813:901:1226/121842.966859:ERROR:kwallet_dbus.cc(100)] Error contacting kwalletd (isEnabled)
[813:901:1226/121842.966923:ERROR:bus.cc(396)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix")
[813:901:1226/121842.966935:ERROR:kwallet_dbus.cc(72)] Error contacting klauncher to start kwalletd
[813:813:1226/121846.249811:ERROR:x11_input_method_context_impl_gtk.cc(144)] Not implemented reached in virtual void libgtkui::X11InputMethodContextImplGtk::SetSurroundingText(const base::string16 &, const gfx::Range &)

(google-chrome:813): LIBDBUSMENU-GLIB-WARNING **: 12:18:46.576: Unable to get session bus: Nieznany lub nieobsługiwany transport „disabled” dla adresu „disabled:”
[813:830:1226/121846.823810:ERROR:connection_factory_impl.cc(408)] Failed to connect to MCS endpoint with error -137
[813:830:1226/121910.210193:ERROR:connection_factory_impl.cc(408)] Failed to connect to MCS endpoint with error -137
[813:813:1226/121922.091693:ERROR:account_tracker.cc(240)] AccessTokenFetched error: Connection failed (-137).
[813:813:1226/123939.208111:ERROR:http_bridge.cc(126)] Not implemented reached in virtual void syncer::HttpBridgeFactory::OnSignalReceived()

gnome-keyring

[2964:3041:1226/123945.959619:ERROR:bus.cc(396)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix")
Gkr-Message: 12:39:45.986: couldn't connect to dbus session bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix")
Gkr-Message: 12:39:46.104: couldn't connect to dbus session bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix")
[2964:2964:1226/123946.371854:ERROR:x11_input_method_context_impl_gtk.cc(144)] Not implemented reached in virtual void libgtkui::X11InputMethodContextImplGtk::SetSurroundingText(const base::string16 &, const gfx::Range &)

(google-chrome:2964): LIBDBUSMENU-GLIB-WARNING **: 12:39:46.388: Unable to get session bus: Nieznany lub nieobsługiwany transport „disabled” dla adresu „disabled:”

Mailspring just pops out this information and close

Mailspring could not store your password securely. Make sure you have libsecret installed and a keyring is present. For more information, visit http://support.getmailspring.com/hc/en-us/articles/115001875571

gnome-keyring and kwallet are up and runing.

Any idea what is going on?

EDIT:
Latest systemd from testing is the culprit - 240.0-1.

Downgraded systemd, systemd-sysvcompat, libsystemd and lib32-systemd to 239.370-1 and everyting is working again. Found multiple dbus issues with 240 all over the internet.

EDIT2:
If someone is affected by this it maybe related to this https://bugs.archlinux.org/task/61177

Last edited by Pryka (2019-01-08 09:09:31)

loqs

Member

Registered: 2014-03-06

Posts: 18,123

Re: [SOLVED]Apps can't connect to gnome-keyring and kde-wallet

https://bugs.chromium.org/p/chromium/is … ?id=918234

Pryka

Member

Registered: 2018-02-07

Posts: 85

Re: [SOLVED]Apps can't connect to gnome-keyring and kde-wallet

Fixed - https://bugs.archlinux.org/task/61177