To help us pinpoint your issue, please insert the output of the
following commands when ran on the system with the issue:
$ fwupdmgr --version client version: 1.3.3 compile-time dependency versions gusb: 0.3.0 efivar: 37 daemon version: 1.3.3
$ fwupdmgr get-devices
│
├─Samsung SSD 860 EVO 1TB:
│ Device ID: ff5bf9f6641211b248157b73007e1b638b3f0a05
│ Summary: ATA Drive
│ Current version: RVT03B6Q
│ Vendor: Advanced Micro Devices, Inc. [AMD]
│ GUIDs: 199fd920-dab0-5f9e-96fa-88130f6f4677
│ 8f72ef92-2740-56c2-8025-bac145539815
│ bcaa2f53-dc18-5430-afaa-561ca1cff361
│ Device Flags: • Internal device
│ • Updatable
│ • Requires AC power
│ • Needs a reboot after installation
│ • Device is usable for the duration of the update
│
└─System Firmware:
Device ID: a3d4c2fe79a3b6a95e12ce4585feef633eb5773e
Current version: 15.66.0
Minimum Version: 15.66.0
Vendor: HP
GUID: 785e408d-f2b9-469f-b7c1-519bdf9099b3
Device Flags: • Internal device
• Updatable
• Requires AC power
• Needs a reboot after installation
• Cryptograp
$ efibootmgr -v Timeout: 0 seconds BootOrder: 0004,0000,0001,0002,9999 Boot0000* Fedora HD(2,GPT,918e2fac-8a28-42d0-8a3b-3b41a8827bc5,0x40800,0x82000)/File(EFIfedorashimx64.efi) Boot0001* Windows Boot Manager HD(2,GPT,918e2fac-8a28-42d0-8a3b-3b41a8827bc5,0x40800,0x82000)/File(EFIMicrosoftBootbootmgfw.efi)WINDOWS.........x...B.C.D.O.B.J.E.C.T.=.{.9.d.e.a.8.6.2.c.-.5.c.d.d.-.4.e.7.0.-.a.c.c.1.-.f.3.2.b.3.4.4.d.4.7.9.5.}...s................ Boot0002* Internal Hard Disk PciRoot(0x0)/Pci(0x8,0x2)/Pci(0x0,0x0)/Sata(1,65535,0)/HD(2,GPT,918e2fac-8a28-42d0-8a3b-3b41a8827bc5,0x40800,0x82000)..BO Boot0004* Fedora HD(1,GPT,f0ec8669-c099-4184-8d9f-d48026e5d383,0x800,0x32000)/File(EFIfedorashimx64.efi) Boot9999* USB Drive (UEFI) PciRoot(0x0)/Pci(0x1d,0x0)/USB(16,0)..BO
$ efivar -l | grep fw
N/A
$ tree /boot │ ├── lua.c32 │ ├── mboot.c32 │ ├── memdisk │ ├── meminfo.c32 │ ├── menu.c32 │ ├── pci.c32 │ ├── pcitest.c32 │ ├── pmload.c32 │ ├── poweroff.c32 │ ├── prdhcp.c32 │ ├── pwd.c32 │ ├── pxechn.c32 │ ├── reboot.c32 │ ├── rosh.c32 │ ├── sanboot.c32 │ ├── sdi.c32 │ ├── sysdump.c32 │ ├── syslinux.c32 │ ├── vesa.c32 │ ├── vesainfo.c32 │ ├── vesamenu.c32 │ ├── vpdtep�``` Please answer the following questions: - Operating system and version: Fedora 31 - How did you install fwupd (ex: `from source`, `pacman`, `apt-get`, etc): bundled by the distribution - Have you tried rebooting? Yes - Are you using an NVMe disk? No, SATA SSD. - Is secure boot enabled (only for the UEFI plugin)? Yes
I have encountered this error while doing a simple sudo docker login. On checking the logs using journalctl -xe I found the following problem.
Jun 05 01:51:30 ubuntu sudo[24492]: pam_unix(sudo:session): session opened for user root by (uid=0)`
Jun 05 01:51:34 ubuntu dbus-daemon[7120]: [session uid=0 pid=7118] Activating service name='org.freedesktop.secrets' requested by ':1.41' (uid=0 pid=24502 comm="docker-credential-secretservice stostore " label="unconfined")`
Jun 05 01:51:34 ubuntu gnome-keyring-daemon[24511]: couldn't create socket directory: /home/aliicp/.cache/keyring-KUIFKZ: Permission denied`
Jun 05 01:51:34 ubuntu gnome-keyring-daemon[24511]: couldn't bind to control socket: /home/aliicp/.cache/keyring-KUIFKZ/control: Permission denied`
Jun 05 01:51:34 ubuntu gnome-keyring-d[24511]: couldn't create socket directory: /home/aliicp/.cache/keyring-KUIFKZ: Permission denied`
Jun 05 01:51:34 ubuntu gnome-keyring-d[24511]: couldn't bind to control socket: /home/aliicp/.cache/keyring-KUIFKZ/control: Permission denied
Jun 05 01:51:59 ubuntu sudo[24492]: pam_unix(sudo:session): session closed for user root`
Jun 05 01:53:34 ubuntu dbus-daemon[7120]: [session uid=0 pid=7118] Failed to activate service 'org.freedesktop.secrets': timed out (service_start_timeout=120000ms)
the keyring value set from command is ps aux | grep keyring:
aliicp 24044 0.0 0.3 288356 7944 pts/0 Sl+ 00:29 0:00 gnome-keyring-daemon --start --replace --foreground --components=secrets,ssh,pcks11
aliicp 24103 0.0 0.0 21536 1016 pts/2 S+ 00:33 0:00 grep --color=auto keyring
this problem doesn’t happen when I am using VirtualBox or Kitmatic instead of VMware. My base OS is Win7.
Thanks.
I ran a pacman -Syu a couple days ago and upgraded systemd. Here’s the pacman.log entry for it:
[2015-04-21 00:11] [ALPM] upgraded libsystemd (218-2 -> 219-5)
[2015-04-21 00:11] [ALPM] upgraded systemd (218-2 -> 219-5)
[2015-04-21 00:12] [ALPM-SCRIPTLET] Failed to execute operation: Connection timed outSince then, almost all systemd commands fail. For example:
$ sudo systemctl enable deluged
Error getting authority: Error initializing authority: Error calling StartServiceByName for org.freedesktop.PolicyKit1: GDBus.Error:org.freedesktop.DBus.Error.TimedOut: Activation of org.freedesktop.PolicyKit1 timed out (g-dbus-error-quark, 20)
Failed to execute operation: Connection timed outI get similar errors for things like trying to shutdown:
$ sudo poweroff
Error getting authority: Error initializing authority: Error calling StartServiceByName for org.freedesktop.PolicyKit1: Timeout was reached (g-io-error-quark, 24)
Failed to start poweroff.target: Connection timed out(The machine actually powers off something like 30 seconds later.)
There are a few other wonky things in my system, for example, some random subset of my torrents in deluge are in an error state (but I can’t get deluge to give me a meaningful error to investigate).
I downgraded systemd and libsystemd back to 218-2 and everything (even the torrents) work fine now. The effect was instantaneous, even before reboot. I tried reinstalling systemd before the downgrade but that didn’t fix anything. I don’t see any un-merged .pacnew files on my system. And I -Syu’d again a couple hours ago.
Any ideas on why systemd 219-5 is breaking on my system? Not seeing anything in my searches, unfortunately.
Last edited by B-Con (2015-04-23 06:56:12)
Upon starting the xfce4 on Ubuntu 13.10, I always get the following message in the log:
Error creating proxy: Error calling StartServiceByName for org.gtk.vfs.Daemon: Timeout was reached (g-io-error-quark, 24)
(xfsettingsd:10814): GVFS_CRITICAL **: fill_mountable_info: assertion 'proxy != NULL` failed
It appears about 20 seconds after the login and it also appeared on the previous version 13.04. It’s a minor issue, but it’s sometimes irritating because it sometimes hangs the logout, for example if I have logged in as the wrong user.
Here is the output of the ps -ef | grep gvfs command:
10821 1 0 08:37 ? 00:00:00 /usr/lib/gvfs/gvfsd
10826 1 0 08:37 ? 00:00:00 /usr/lib/gvfs//gvfsd-fuse -f /run/user/1000/gvfs
10890 1 0 08:37 ? 00:00:00 /usr/lib/gvfs/gvfs-udisks2-volume-monitor
10899 1 0 08:37 ? 00:00:00 /usr/lib/gvfs/gvfs-afc-volume-monitor
10906 1 0 08:37 ? 00:00:00 /usr/lib/gvfs/gvfs-gphoto2-volume-monitor
10914 1 0 08:37 ? 00:00:00 /usr/lib/gvfs/gvfs-mtp-volume-monitor
How can this be solved?
Asked
7 years, 1 month ago
Viewed
53k times
I’m running CentOS 7.2; see below:
# systemctl stop firewalld
Error getting authority: Error initializing authority: Error calling StartServiceByName for org.freedesktop.PolicyKit1: Timeout was reached (g-io-error-quark, 24)
Failed to stop firewalld.service: Connection timed out
Failed to get load state of firewalld.service: Connection timed out
journalctl just reports the following error: [system] Failed to activate service 'org.freedesktop.PolicyKit1': timed out
I found this bug for Ubuntu and a possible related one for a RHEL 7 bug.
asked Dec 15, 2015 at 21:40
1
This is an issue with polkit.service; it was not starting for me.
After further investigation I found that the polkitd user did not exist. Then yum reinstall polkit and systemctl start polkit fixed the issue.
I debugged this by running polkitd directly: /usr/lib/polkit-1/polkitd
answered Dec 15, 2015 at 22:18
3
it could be a dbus problem. consider to reinstall one.
apt install dbus
reboot after installing as dbus configs gets upgraded only after.
answered Jun 7, 2020 at 7:39
1
Issue
- The below is seen on attempting to set the hostname:
# hostnamectl set-hostname <hostname>
Error getting authority: Error initializing authority: Error calling StartServiceByName for org.freedesktop.PolicyKit1: Timeout was reached (g-io-error-quark, 24)
- Commands such as the below fail as well:
# systemctl restart sshd
Error getting authority: Error initializing authority: Error calling StartServiceByName for org.freedesktop.PolicyKit1: GDBus.Error:org.freedesktop.DBus.Error.TimedOut: Activation of org.freedesktop.PolicyKit1 timed out (g-dbus-error-quark, 20)
Environment
- Red Hat Enterprise Linux 7.x
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.
Current Customers and Partners
Log in for full access
Log In
Upon starting the xfce4 on Ubuntu 13.10, I always get the following message in the log:
Error creating proxy: Error calling StartServiceByName for org.gtk.vfs.Daemon: Timeout was reached (g-io-error-quark, 24)
(xfsettingsd:10814): GVFS_CRITICAL **: fill_mountable_info: assertion 'proxy != NULL` failedIt appears about 20 seconds after the login and it also appeared on the previous version 13.04. It’s a minor issue, but it’s sometimes irritating because it sometimes hangs the logout, for example if I have logged in as the wrong user.
Here is the output of the ps -ef | grep gvfs command:
10821 1 0 08:37 ? 00:00:00 /usr/lib/gvfs/gvfsd
10826 1 0 08:37 ? 00:00:00 /usr/lib/gvfs//gvfsd-fuse -f /run/user/1000/gvfs
10890 1 0 08:37 ? 00:00:00 /usr/lib/gvfs/gvfs-udisks2-volume-monitor
10899 1 0 08:37 ? 00:00:00 /usr/lib/gvfs/gvfs-afc-volume-monitor
10906 1 0 08:37 ? 00:00:00 /usr/lib/gvfs/gvfs-gphoto2-volume-monitor
10914 1 0 08:37 ? 00:00:00 /usr/lib/gvfs/gvfs-mtp-volume-monitorHow can this be solved?