After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 768908 - glib 2.49.3 breaks libsecret
glib 2.49.3 breaks libsecret
Status: RESOLVED DUPLICATE of bug 744456
Product: glib
Classification: Platform
Component: general
2.49.x
Other Linux
: Normal critical
: ---
Assigned To: gtkdev
gtkdev
Depends on:
Blocks:
 
 
Reported: 2016-07-17 22:54 UTC by Hussam Al-Tayeb
Modified: 2016-07-21 10:36 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Hussam Al-Tayeb 2016-07-17 22:54:38 UTC 
glib 2.49.3 breaks libsecret
journal says:
Jul 18 01:44:17 hades gnome-keyring-daemon[5282]: couldn't access control socket: /run/user/1000/keyring/control: No such file or directory
Jul 18 01:44:17 hades dbus-daemon[454]: Activated service 'org.freedesktop.secrets' failed: Process org.freedesktop.secrets received signal 11
Jul 18 01:44:17 hades goa-daemon[563]: secret_password_lookup_sync() failed: Error calling StartServiceByName for org.freedesktop.secrets: GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildSignaled: Process org.freedesktop.secrets receive
Jul 18 01:44:18 hades dbus-daemon[454]: Activating service name='org.freedesktop.secrets'
Jul 18 01:44:18 hades gnome-keyring-daemon[5590]: couldn't access control socket: /run/user/1000/keyring/control: No such file or directory
Jul 18 01:44:18 hades dbus-daemon[454]: Activated service 'org.freedesktop.secrets' failed: Process org.freedesktop.secrets received signal 11


reverting this commit fixes it https://git.gnome.org/browse/glib/patch/?id=fce7cfaf40b6e1e50c9140aa0397f5b8c8f821fb
Comment 1 Marinus Schraal 2016-07-19 07:02:59 UTC 
Looks like this is fallout of the problems reported at the end of bug #744456 really. Could you get a backtrace on the org.freedesktop.secrets process thats failing to be sure?
Comment 2 Hussam Al-Tayeb 2016-07-19 07:20:02 UTC 
(In reply to Marinus Schraal from comment #1)
> Looks like this is fallout of the problems reported at the end of bug
> #744456 really. Could you get a backtrace on the org.freedesktop.secrets
> process thats failing to be sure?

Hello. This means gnome-keyring, correct?
Comment 3 Marinus Schraal 2016-07-19 07:31:57 UTC 
Yes, but I guess it's easiest to get it to dump core and backtrace that. See https://wiki.gnome.org/Community/GettingInTouch/Bugzilla/GettingTraces/Details for more info.
Comment 4 Hussam Al-Tayeb 2016-07-19 11:45:20 UTC 
By the way, nautilus crashes as well:

                #1  0x00007f56a5ce1c03 g_log_writer_journald (libglib-2.0.so.0)
                #2  0x00007f56a5ce1e1e g_log_writer_default (libglib-2.0.so.0)
                #3  0x00007f56a5ce082c g_log_structured_array (libglib-2.0.so.0)
                #4  0x00007f56a5ce11cb g_log_structured (libglib-2.0.so.0)
                #5  0x00007f56a5ce130b g_log_default_handler (libglib-2.0.so.0)
                #6  0x00007f56a5ce1594 g_logv (libglib-2.0.so.0)
                #7  0x00007f56a5ce179f g_log (libglib-2.0.so.0)

Reverting back to before those changes fixes everything.
Comment 5 Marinus Schraal 2016-07-19 12:17:53 UTC 

*** This bug has been marked as a duplicate of bug 744456 ***
Comment 6 Hussam Al-Tayeb 2016-07-21 10:36:27 UTC 
Still an issue in 2.49.4