On 06/09/2025 03:43, Jeffrey Walton wrote:
On Fri, Sep 5, 2025 at 3:30 PM Frank McCormick wrote:
Specifically rox-filer takes upwards of 30 seconds to display.
(ROX-Filer:8578): GVFS-WARNING **: 12:45:56.924: Error creating proxy:
Error calling StartServiceByName for org.gtk.vfs.Daemon: Timeout was
reached (g-io-error-quark, 24)
[...]
Is there anything interesting in `sudo journalctl -b | grep -i error`?
First of all, I am strongly against calling journalctl this way. Do not combine it with grep. A better way is e.g.
sudo journalctl -b --priority=warning
Not all messages having error priority contains string "error". (The
command has --grep option, but it is not for this use case.) Actually I
think, it is enough to run
sudo journalctl -b
and to press several times [PageDown] or just [Space] bar several times
paying attention to yellow and red lines. After all, the less(1) pager
has search (/, ?) and filter (&) commands.
I would check if necessary gvfs packages are installed. Next step is
busctl
to see if org.gtk.vfs.Daemon is there. (D-Bus services specific to user
session may be reviewed using "busctl --user").