Red Hat Bugzilla – Bug 1275462
Long delay in starting GTK applications
Last modified: 2017-08-08 08:19:51 EDT
Starting up any GTK-using application takes an inordinate amount of time with this output:
GVFS-WARNING **: Error creating proxy: Error calling StartServiceByName for org.gtk.vfs.Daemon: Timeout was reached (g-io-error-quark, 24)
I see this in the journal:
Oct 26 20:57:58 bronto-burt dbus-daemon: Activating systemd to hand-off: service name='org.gtk.vfs.Daemon' unit='gvfs-daemon.service'
Oct 26 20:59:58 bronto-burt dbus-daemon: Failed to activate service 'org.gtk.vfs.Daemon': timed out
Oct 26 20:59:58 bronto-burt dbus-daemon: Failed to activate service 'org.freedesktop.systemd1': timed out
Uninstalling gvfs doesn't help anything either.
Removing gvfs makes things happy again. Reassigning.
Thanks for your bug report.
Could you test also latest gvfs-188.8.131.52-3 package (I can't reproduce with)? This package contains one dbus related patch, which might potentially also fix this issue...
This bug appears to have been reported against 'rawhide' during the Fedora 24 development cycle.
Changing version to '24'.
More information and reason for this action is here:
Still able to reproduce the problem with gvfs-1.29.4-1.fc25. Not sure what's up with it; I do have a pretty stripped down system (from a DE point-of-view), so does gvfs not do well if none of its backends are installed?
(In reply to Ben Boeckel from comment #4)
> Still able to reproduce the problem with gvfs-1.29.4-1.fc25. Not sure what's
> up with it; I do have a pretty stripped down system (from a DE
> point-of-view), so does gvfs not do well if none of its backends are
Do you see same problems if you boot from live disk? Is it possible to reproduce this uninstalling some packages? What do you mean with stripped down system and that none of its backends are installed? If you manually removed some important parts, it doesn't have to work correctly...
Do you see some failures if you start the main daemon manually:
This message is a reminder that Fedora 24 is nearing its end of life.
Approximately 2 (two) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 24. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora 'version'
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.
Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 24 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
Fedora 24 changed to end-of-life (EOL) status on 2017-08-08. Fedora 24 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
Thank you for reporting this bug and we are sorry it could not be fixed.