Failed to SUID root

Bug #1182007 reported by TJ
318
This bug affects 72 people
Affects Status Importance Assigned to Milestone
signon (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

signond[7451]: ../../../../src/signond/signondaemon.cpp 360 init Failed to SUID root. Secure storage will not be available.

This report appears in syslog each time Empathy tries and fails to connect to Google Talk using the google-talkplugin interface.

It is not clear whether this SUID report is related to the Empathy failure.

See bug #1168582 "Google talk "Requires Authorization" after suspend/resume"

TJ (tj)
description: updated
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in signon (Ubuntu):
status: New → Confirmed
Revision history for this message
Steffen Krumbholz (skrumbholz) wrote :

My syslog is full of messages like these...

signond[3587]: ../../../../src/signond/signondaemon.cpp 360 init Failed to SUID root. Secure storage will not be available.
signond[3671]: ../../../../src/signond/signondaemon.cpp 360 init Failed to SUID root. Secure storage will not be available.

And now and then the online accounts (Facebook, Twitter, Google) are losing their authorisation with this message in /var/log/syslog...

May 25 19:46:41 eeepc signond[3671]: ../../../../src/signond/signonsessioncore.cpp 528 processStoreOperation Error occured while storing data.

Revision history for this message
sgttynis (sgttynis-deactivatedaccount) wrote :

Same here. After I upgrade my system from Ubuntu 12.10 to 13.04 (64bit) I get such a message every time I open the Online-Accounts and mark the Add Account (Konto hinzufügen... in german) entry. Maybe thats the reason why the ICQ accounts also do not work properly (you get an empty dialog).

Revision history for this message
Jakub Nietrzeba (gluth) wrote :

Same here, but unrelated to accounts. I'm unable to save password from evolution, online accounts and others. It keeps asking for password on every reboot.

Revision history for this message
Michael Sharman (msharman) wrote :

I'm having trouble trouble connecting to Google Talk get am getting the following in my syslog:
Mar 27 11:28:59 office-desktop signond[9112]: ../../../../src/signond/signondaemon.cpp 388 init Failed to SUID root. Secure storage will not be available.
Mar 27 11:28:59 office-desktop signond[9112]: ../../../../src/signond/credentialsaccessmanager.cpp 211 init Couldn't load AccessControlManager: "apparmor-ac"

Running 13.10 (64-bit)

description: updated
Revision history for this message
owise1 (o-wise-1) wrote :

Same problem here

david-desktop signond[2482]: ../../../../src/signond/signondaemon.cpp 388 init Failed to SUID root. Secure storage will not be available.
Apr 17 07:15:21 david-desktop signond[2482]: ../../../../src/signond/credentialsaccessmanager.cpp 211 init Couldn't load AccessControlManager: "apparmor-ac"

I am also having a system freeze with google talk after about ten minutes - not sure if related

running 13:10 (32bit) updated from fresh install of 13.04

Revision history for this message
Mark Rich (sir-marky) wrote :

Receiving these messages periodically in /var/log/syslog

Apr 23 18:54:26 markys-home-pc signond[12687]: ../../../../src/signond/signondaemon.cpp 388 init Failed to SUID root. Secure storage will not be available.

Revision history for this message
Amir (lalosher) wrote :

Same problem here

May 19 09:19:10 amir-laptop signond[2306]: ../../../../src/signond/signondaemon.cpp 388 init Failed to SUID root. Secure storage will not be available.

running 14.04 TLS (64-bit)

Revision history for this message
Anders Hall (a.hall) wrote :

Ubuntu 14.04

uname -a: 3.13.0-27-generic #50-Ubuntu SMP Thu May 15 18:06:16 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux

syslog: Jun 3 18:51:20 boll signond[5907]: ../../../../src/signond/signondaemon.cpp 388 init Failed to SUID root. Secure storage will not be available.

Perhaps something todo with removing Ubuntu One as i did? The "backup failed" message for Ubuntu One keeps coming back despite removing all libs.

Revision history for this message
mamunabms (mamunabms) wrote :

Getting same error.

uname -a
Linux moonstruck 3.13.0-35-generic #62-Ubuntu SMP Fri Aug 15 01:58:01 UTC 2014 i686 i686 i686 GNU/Linux

Aug 31 23:46:42 moonstruck signond[5364]: ../../../../src/signond/signondaemon.cpp 388 init Failed to SUID root. Secure storage will not be available.

Revision history for this message
Rob Harvey (jackcorbae-gmail) wrote :

In the past two weeks my PC has powered itself off several times - usually over night but twice while I was using it. I initially suspected VirtualBox as each time it happened to me I had a USB device attached to the guest system.

The overnight shutdowns didn't have VirtualBox open though - only Chrome and Pidgin.

Ubuntu 14.04 64bit

uname -a
Linux B045559 3.13.0-37-generic #64-Ubuntu SMP Mon Sep 22 21:28:38 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux

The last few entries in the syslog - they always ended with the signond error - but the log shows one occurred 2 hours earlier and the system stayed up ...

Oct 30 16:09:01 B045559 CRON[18897]: (root) CMD ( [ -x /usr/lib/php5/maxlifetime ] && [ -x /usr/lib/php5/sessionclean ] && [ -d /var/lib/php5 ] && /usr/lib/php5/sessionclean /var/lib/php5 $(/usr/lib/php5/maxlifetime))
Oct 30 16:17:01 B045559 CRON[18967]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
Oct 30 16:39:01 B045559 CRON[19107]: (root) CMD ( [ -x /usr/lib/php5/maxlifetime ] && [ -x /usr/lib/php5/sessionclean ] && [ -d /var/lib/php5 ] && /usr/lib/php5/sessionclean /var/lib/php5 $(/usr/lib/php5/maxlifetime))
Oct 30 16:44:23 B045559 signond[19144]: ../../../../src/signond/signondaemon.cpp 388 init Failed to SUID root. Secure storage will not be available.
Oct 30 17:17:01 B045559 CRON[19365]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
Oct 30 17:39:01 B045559 CRON[19489]: (root) CMD ( [ -x /usr/lib/php5/maxlifetime ] && [ -x /usr/lib/php5/sessionclean ] && [ -d /var/lib/php5 ] && /usr/lib/php5/sessionclean /var/lib/php5 $(/usr/lib/php5/maxlifetime))
Oct 30 18:09:01 B045559 CRON[19707]: (root) CMD ( [ -x /usr/lib/php5/maxlifetime ] && [ -x /usr/lib/php5/sessionclean ] && [ -d /var/lib/php5 ] && /usr/lib/php5/sessionclean /var/lib/php5 $(/usr/lib/php5/maxlifetime))
Oct 30 18:17:02 B045559 CRON[19789]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
Oct 30 18:39:01 B045559 CRON[19939]: (root) CMD ( [ -x /usr/lib/php5/maxlifetime ] && [ -x /usr/lib/php5/sessionclean ] && [ -d /var/lib/php5 ] && /usr/lib/php5/sessionclean /var/lib/php5 $(/usr/lib/php5/maxlifetime))
Oct 30 18:44:23 B045559 signond[19991]: ../../../../src/signond/signondaemon.cpp 388 init Failed to SUID root. Secure storage will not be available.

Revision history for this message
Electric Prism (electricprism-m-deactivatedaccount) wrote :

Linux 3.13.0-40-generic #69-Ubuntu SMP Thu Nov 13 17:53:56 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
Ubuntu 14.04 here with Gnome Staging Empathy 3.12, same problem.

Can't connect to Google Talk network
"Google Talk account requires authorisation"

Revision history for this message
Asher Diamond (asher-diamond) wrote :

I am still getting this error in 14.10. Is anyone going to fix this?
Looks like some kind of permission problem. Is 'Online Accounts' run as root?

    if (getuid() != 0) {
        BLAME() << "Failed to SUID root. Secure storage will not be available.";
    }

Revision history for this message
DigiAngel (jlay) wrote :

Count me in as well...I get this when facebook is enabled.

Revision history for this message
gna (nagy-gergely) wrote :

According to a gitlab Commit 18381573 authored 2 years ago by Alberto Mardegan:
https://gitlab.com/accounts-sso/signond/commit/18381573beaa4efe5b115ccdf3b3a689e98a72c6

signond: remove warning about not being root

Usually signond doesn't run as root; if necessary, this warning can be
moved to an extension.

This change made it into signon 8.57+15.10.20150616-0ubuntu1 so it should be fixed in wily

Revision history for this message
gna (nagy-gergely) wrote :
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.