[DELAYED] Can't connect to wired: "Remote error from secret service"

Questions about cabled networking
Forum rules
Before you post please read how to get help
Post Reply
User avatar
Flemur
Level 16
Level 16
Posts: 6053
Joined: Mon Aug 20, 2012 9:41 pm
Location: Potemkin Village

[DELAYED] Can't connect to wired: "Remote error from secret service"

Post by Flemur » Mon Apr 30, 2018 10:56 am

Edit: I have a feeling I deleted/uninstalled something necessary for wired ethernet; so I'm putting this on hold until there's a better reason to reinstall an OS.

I'm trying to connect with ethernet rather than wifi, but when I start nm-applet and try to change settings (there doesn't seem to be a way to say "connect to ethernet" other than "connect automatically") I get these mysterious messages (and no connection):

Code: Select all

** Message: Cannot save connection due to error: Editor initializing...
** Message: Connection validates and can be saved
** Message: Remote error from secret service: org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.secrets was not provided by any .service files
1 - "Cannot save connection" is immediately followed by
2 - "Connection validates and can be saved" - is it saved or not?
3 - When I "Edit->Save", with or without changing anything, I get that mysterious message from my good friends (ha! ha!) at freedesktop.org .

I do not have "keyring" packages installed. Are they required for ethernet but NOT Wifi?

https://help.ubuntu.com/stable/ubuntu-h ... ct.html.en says:
"To set up most wired network connections, all you need to do is plug in a network cable. The wired network icon (settings) is displayed on the top bar with three dots while the connection is being established. The dots disappear when you are connected."

I don't see any dots and it doesn't connect....

Edit: After installing gnome-keyring and rebooting, it still can't connect but the freedesktop nonsense is gone:

Code: Select all

Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged.
** Message: Cannot save connection due to error: Editor initializing...
** Message: Connection validates and can be saved
Output of journalctl --follow when trying to add a new wired connections named "wired1":

Code: Select all

Apr 30 09:14:37 mycom dbus[659]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service'
Apr 30 09:14:37 mycom systemd[1]: Starting Hostname Service...
Apr 30 09:14:37 mycom dbus[659]: [system] Successfully activated service 'org.freedesktop.hostname1'
Apr 30 09:14:37 mycom systemd[1]: Started Hostname Service.
Apr 30 09:14:37 mycom org.gtk.vfs.Daemon[989]: ** (process:2109): WARNING **: send_done_cb: No such interface 'org.gtk.vfs.Enumerator' on object at path /org/gtk/vfs/client/enumerator/1 (g-dbus-error-quark, 19)
Apr 30 09:14:38 mycom org.gtk.vfs.Daemon[989]: ** (gvfsd:1045): WARNING **: dbus_mount_reply: Error from org.gtk.vfs.Mountable.mount(): Failed to retrieve share list from server: Connection refused
Apr 30 09:14:38 mycom org.gtk.vfs.Daemon[989]: ** (gvfsd:1045): WARNING **: dbus_mount_reply: Error from org.gtk.vfs.Mountable.mount(): Failed to retrieve share list from server: Connection refused
Apr 30 09:14:38 mycom org.gtk.vfs.Daemon[989]: ** (process:2139): WARNING **: Couldn't create directory monitor on smb://x-gnome-default-workgroup/. Error: The specified location is not mounted
Apr 30 09:14:38 mycom org.gtk.vfs.Daemon[989]: ** (gvfsd:1045): WARNING **: dbus_mount_reply: Error from org.gtk.vfs.Mountable.mount(): Failed to retrieve share list from server: Connection refused
Apr 30 09:14:38 mycom org.gtk.vfs.Daemon[989]: ** (gvfsd:1045): WARNING **: dbus_mount_reply: Error from org.gtk.vfs.Mountable.mount(): Failed to retrieve share list from server: Connection refused
Apr 30 09:14:38 mycom org.gtk.vfs.Daemon[989]: ** (process:2136): WARNING **: Couldn't create directory monitor on smb://x-gnome-default-workgroup/. Error: The specified location is not mounted
Apr 30 09:14:38 mycom org.gtk.vfs.Daemon[989]: ** (gvfsd:1045): WARNING **: dbus_mount_reply: Error from org.gtk.vfs.Mountable.mount(): Failed to retrieve share list from server: Connection refused
Apr 30 09:14:38 mycom org.gtk.vfs.Daemon[989]: ** (gvfsd:1045): WARNING **: dbus_mount_reply: Error from org.gtk.vfs.Mountable.mount(): Failed to retrieve share list from server: Connection refused
Apr 30 09:14:38 mycom org.gtk.vfs.Daemon[989]: ** (process:2129): WARNING **: Couldn't create directory monitor on smb://x-gnome-default-workgroup/. Error: The specified location is not mounted
Apr 30 09:14:38 mycom org.gtk.vfs.Daemon[989]: ** (process:2123): WARNING **: Couldn't create directory monitor on smb://x-gnome-default-workgroup/. Error: The specified location is not mounted
Apr 30 09:14:38 mycom org.gtk.vfs.Daemon[989]: ** (process:2125): WARNING **: Couldn't create directory monitor on smb://x-gnome-default-workgroup/. Error: The specified location is not mounted
Apr 30 09:14:38 mycom org.gtk.vfs.Daemon[989]: ** (process:2132): WARNING **: Couldn't create directory monitor on smb://x-gnome-default-workgroup/. Error: The specified location is not mounted
Apr 30 09:14:48 mycom NetworkManager[690]: <info>  [1525101288.5485] keyfile: add connection /etc/NetworkManager/system-connections/Wired1 (3bf6224f-5e68-485b-b143-f7d9dfd5d00a,"Wired1")
Apr 30 09:14:48 mycom NetworkManager[690]: <info>  [1525101288.5492] audit: op="connection-add" uuid="3bf6224f-5e68-485b-b143-f7d9dfd5d00a" name="Wired1" pid=2104 uid=1000 result="success"
Apr 30 09:14:48 mycom gnome-keyring-daemon[2235]: couldn't access control socket: /run/user/1000/keyring/control: No such file or directory
Apr 30 09:14:48 mycom org.freedesktop.secrets[989]: ** Message: couldn't access control socket: /run/user/1000/keyring/control: No such file or directory
Apr 30 09:15:08 mycom NetworkManager[690]: <info>  [1525101308.9162] keyfile: update /etc/NetworkManager/system-connections/Wired1 (3bf6224f-5e68-485b-b143-f7d9dfd5d00a,"Wired1")
Apr 30 09:15:08 mycom NetworkManager[690]: <info>  [1525101308.9177] audit: op="connection-update" uuid="3bf6224f-5e68-485b-b143-f7d9dfd5d00a" name="Wired1" pid=2104 uid=1000 result="success"
Apr 30 09:17:01 mycom CRON[2275]: pam_unix(cron:session): session opened for user root by (uid=0)
Apr 30 09:17:01 mycom CRON[2276]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
Apr 30 09:17:01 mycom CRON[2275]: pam_unix(cron:session): session closed for user root
Last edited by Flemur on Fri May 04, 2018 2:26 pm, edited 1 time in total.
Please edit your original post title to include [SOLVED] if/when it is solved!
Your data and OS are backed up....right?
Mint 18.3 Xfce/fluxbox/pulse-less
Xubuntu 17.10/fluxbox/pulse-less


User avatar
Flemur
Level 16
Level 16
Posts: 6053
Joined: Mon Aug 20, 2012 9:41 pm
Location: Potemkin Village

Re: Can't connect to wired: "Remote error from secret service"

Post by Flemur » Thu May 03, 2018 2:22 pm

Thanks I'll check those links in a bit...here's that output, it doesn't mean much to me:
$ nmcli general permissions

Code: Select all

PERMISSION                                                 VALUE   
org.freedesktop.NetworkManager.enable-disable-network      yes     
org.freedesktop.NetworkManager.enable-disable-wifi         yes     
org.freedesktop.NetworkManager.enable-disable-wwan         yes     
org.freedesktop.NetworkManager.enable-disable-wimax        yes     
org.freedesktop.NetworkManager.sleep-wake                  no      
org.freedesktop.NetworkManager.network-control             yes     
org.freedesktop.NetworkManager.wifi.share.protected        yes     
org.freedesktop.NetworkManager.wifi.share.open             yes     
org.freedesktop.NetworkManager.settings.modify.system      yes     
org.freedesktop.NetworkManager.settings.modify.own         yes     
org.freedesktop.NetworkManager.settings.modify.hostname    auth    
org.freedesktop.NetworkManager.settings.modify.global-dns  unknown 
org.freedesktop.NetworkManager.reload                      auth    
Would anything be easier if I were using "wicd" rather than NetworkManager? It seems "funny" that WiFi is easier than ethernet...
Please edit your original post title to include [SOLVED] if/when it is solved!
Your data and OS are backed up....right?
Mint 18.3 Xfce/fluxbox/pulse-less
Xubuntu 17.10/fluxbox/pulse-less

User avatar
administrollaattori
Level 14
Level 14
Posts: 5158
Joined: Tue Sep 03, 2013 4:51 am
Location: Finland
Contact:

Re: Can't connect to wired: "Remote error from secret service"

Post by administrollaattori » Fri May 04, 2018 4:10 am

Flemur wrote:
Thu May 03, 2018 2:22 pm
Thanks I'll check those links in a bit...here's that output, it doesn't mean much to me:
$ nmcli general permissions

Code: Select all

PERMISSION                                                 VALUE   
org.freedesktop.NetworkManager.enable-disable-network      yes     
org.freedesktop.NetworkManager.enable-disable-wifi         yes     
org.freedesktop.NetworkManager.enable-disable-wwan         yes     
org.freedesktop.NetworkManager.enable-disable-wimax        yes     
org.freedesktop.NetworkManager.sleep-wake                  no      
org.freedesktop.NetworkManager.network-control             yes     
org.freedesktop.NetworkManager.wifi.share.protected        yes     
org.freedesktop.NetworkManager.wifi.share.open             yes     
org.freedesktop.NetworkManager.settings.modify.system      yes     
org.freedesktop.NetworkManager.settings.modify.own         yes     
org.freedesktop.NetworkManager.settings.modify.hostname    auth    
org.freedesktop.NetworkManager.settings.modify.global-dns  unknown 
org.freedesktop.NetworkManager.reload                      auth    
Would anything be easier if I were using "wicd" rather than NetworkManager? It seems "funny" that WiFi is easier than ethernet...
I got the same results. How about if restarting network?

Code: Select all

sudo nmcli networking off
sudo nmcli networking on

User avatar
Flemur
Level 16
Level 16
Posts: 6053
Joined: Mon Aug 20, 2012 9:41 pm
Location: Potemkin Village

Re: Can't connect to wired: "Remote error from secret service"

Post by Flemur » Fri May 04, 2018 12:20 pm

administrollaattori wrote:
Fri May 04, 2018 4:10 am
I got the same results. How about if restarting network?

Code: Select all

sudo nmcli networking off
sudo nmcli networking on
No change. I was checking back here for the links you gave the other day. Some command from some website seemed to indicate that a kernel module needed for ethernet wasn't getting loaded.
Please edit your original post title to include [SOLVED] if/when it is solved!
Your data and OS are backed up....right?
Mint 18.3 Xfce/fluxbox/pulse-less
Xubuntu 17.10/fluxbox/pulse-less

Post Reply

Return to “Ethernet”