Tuesday, October 11, 2016

wtf does this mean? org.freedesktop.DBus.Error.ServiceUnknown

 nm-applet-WARNING **: Failed to add/activate connection: (4) Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
** Message: Remote error from secret service: org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.secrets was not provided by any .service files
http://comphelp.org/guide/remote-error-from-secret-service-org-freedesktop-dbus-error-service/

For anyone still having the same problem: you might still have to enable the gnome-keyring to start.
The wiki has a good part about it.
https://bbs.archlinux.org/viewtopic.php?id=165293

Try going through these things: wiki.ubuntu.com/DebuggingNetworkManager


dmesg | tail
journalctl -xe | grep -i error
journalctl: command not found

dmesg | tail
[ 3453.232835] audit: type=1401 audit(1476198213.192:3709): op=security_compute_sid invalid_context=system_u:system_r:sysadm_dbusd_t:s0 scontext=system_u:system_r:sysadm_dbusd_t:s0 tcontext=system_u:system_r:sysadm_dbusd_t:s0 tclass=unix_stream_socket
[ 3453.232852] audit: type=1401 audit(1476198213.192:3710): op=security_compute_sid invalid_context=system_u:system_r:sysadm_dbusd_t:s0 scontext=system_u:system_r:sysadm_dbusd_t:s0 tcontext=system_u:system_r:sysadm_dbusd_t:s0 tclass=unix_stream_socket
[ 3453.232869] audit: type=1401 audit(1476198213.192:3711): op=security_compute_sid invalid_context=system_u:system_r:sysadm_dbusd_t:s0 scontext=system_u:system_r:sysadm_dbusd_t:s0 tcontext=system_u:system_r:sysadm_dbusd_t:s0 tclass=unix_stream_socket
[ 3453.359976] audit: type=1401 audit(1476198213.320:3712): op=security_compute_sid invalid_context=system_u:system_r:sysadm_dbusd_t:s0 scontext=system_u:system_r:sysadm_dbusd_t:s0 tcontext=system_u:object_r:lib_t:s0 tclass=process
[ 3454.371202] audit: type=1401 audit(1476198214.332:3713): op=security_compute_sid invalid_context=system_u:system_r:sysadm_dbusd_t:s0 scontext=system_u:system_r:sysadm_dbusd_t:s0 tcontext=system_u:system_r:sysadm_dbusd_t:s0 tclass=unix_stream_socket
[ 3454.371234] audit: type=1401 audit(1476198214.332:3714): op=security_compute_sid invalid_context=system_u:system_r:sysadm_dbusd_t:s0 scontext=system_u:system_r:sysadm_dbusd_t:s0 tcontext=system_u:system_r:sysadm_dbusd_t:s0 tclass=unix_stream_socket
[ 3454.371286] audit: type=1400 audit(1476198214.332:3715): avc:  denied  { connectto } for  pid=4605 comm="xfce4-notifyd" path=002F746D702F646275732D45614B79436F6C417639 scontext=system_u:system_r:sysadm_dbusd_t:s0 tcontext=system_u:system_r:sysadm_dbusd_t:s0 tclass=unix_stream_socket permissive=1
[ 3454.371291] SELinux:  Context system_u:system_r:sysadm_dbusd_t:s0 would be invalid if enforcing
[ 3454.372397] audit: type=1401 audit(1476198214.332:3716): op=security_compute_sid invalid_context=system_u:system_r:sysadm_dbusd_t:s0 scontext=system_u:system_r:sysadm_dbusd_t:s0 tcontext=system_u:system_r:sysadm_dbusd_t:s0 tclass=unix_dgram_socket
[ 3454.372428] audit: type=1401 audit(1476198214.332:3717): op=security_compute_sid invalid_context=system_u:system_r:sysadm_dbusd_t:s0 scontext=system_u:system_r:sysadm_dbusd_t:s0 tcontext=system_u:system_r:sysadm_dbusd_t:s0 tclass=unix_dgram_socket
https://wiki.gentoo.org/wiki/SELinux/Tutorials/Linux_services_and_the_system_u_SELinux_user
It is entirely possible, particularly with newer hardware, that there is no microcode update for the CPU. In that case, the output may look like this:
dmesg | grep microcode
[    0.981141] microcode: CPU0 sig=0x306a9, pf=0x10, revision=0x17
[    0.981151] microcode: CPU1 sig=0x306a9, pf=0x10, revision=0x17
[    0.981230] microcode: Microcode Update Driver: v2.00 , Peter Oruba