Thunar delay on start

Gabriel-Costa · 2019-11-25 12:07:23

Hi there, I'm using arch & openbox with thunar as file manager, I'm using this for almost an year and I never had problems with thunar before, but now when I start thunar it takes around 30 to 50 seconds to start and when I want to close it, takes the same amount of time to close.

In Arch Wiki documentation for thunar it says that to solve the problem related with "slow cold start" it should be done:

Some people still have problems with Thunar taking a long time to start for the first time. This is due to gvfs checking the network, preventing Thunar from starting until gvfs finishes its operations. To change this behaviour, edit /usr/share/gvfs/mounts/network.mount and change AutoMount=true to AutoMount=false.

I have done it but is not working.

This is the configuration of my network.mount file

[Mount]
Type=network
Exec=/usr/lib/gvfsd-network
AutoMount=false

Any ideas!?

Thanks..

Last edited by Gabriel-Costa (2019-11-25 12:09:10)

fyulita · 2020-09-10 15:15:10

Hey I'm having the same issue and I can't find the solution anywhere. Did you manage to solve it?

fyulita · 2020-09-11 02:20:25

fyulita wrote:

Hey I'm having the same issue and I can't find the solution anywhere. Did you manage to solve it?

I managed to solve the problem I had so I'm going to answer myself in case it helps someone.

In my case the problem was that I was starting X with an incorrect .xinitrc file. Basically I was only launching my WM when I should also be launching other important programs. That's why Thunar and other programs like pavucontrol took forever to launch. My correct .xinitrc file looks like this:

#!/bin/sh

userresources=$HOME/.Xresources
usermodmap=$HOME/.Xmodmap
sysresources=/etc/X11/xinit/.Xresources
sysmodmap=/etc/X11/xinit/.Xmodmap

# merge in defaults and keymaps

if [ -f $sysresources ]; then
    xrdb -merge $sysresources
fi

if [ -f $sysmodmap ]; then
    xmodmap $sysmodmap
fi

if [ -f "$userresources" ]; then
    xrdb -merge "$userresources"
fi

if [ -f "$usermodmap" ]; then
    xmodmap "$usermodmap"
fi

# start some nice programs

if [ -d /etc/X11/xinit/xinitrc.d ]; then
    for f in /etc/X11/xinit/xinitrc.d/?*.sh ; do
	[ -x "$f" ] && . "$f"
    done
    unset f
fi

twm &
xclock -geometry 50x50-1+1 &
xterm -geometry 80x50+494+51 &
xterm -geometry 80x20+494-0 &
exec xterm -geometry 80x66+0+0 -name login &

exec /home/fyulita/.config/polybar/launch.sh &
exec xmonad

Only the last two lines are specific to me, the rest is what you should probably have.

2ManyDogs · 2020-09-11 12:35:49

fyulita wrote:

twm &
xclock -geometry 50x50-1+1 &
xterm -geometry 80x50+494+51 &
xterm -geometry 80x20+494-0 &
exec xterm -geometry 80x66+0+0 -name login &

exec /home/fyulita/.config/polybar/launch.sh &
exec xmonad

I think you should read this wiki section again: https://wiki.archlinux.org/index.php/Xinit#xinitrc

And then do a little research on "exec" and "&". I don't think that section is doing what you think it does, or what you want it to do.

Trilby · 2020-09-11 12:46:42

2ManyDogs wrote:

I don't think that section is doing what you think it does, or what you want it to do.

I almost commented on this too - but I didn't know where to start. I suspect they might be content with the end result of that hodge-podge of code that mostly by sheer coincidence ends up doing more-or-less what they want.

Pairing `exec` and a terminal `&` is nonsensical, but the end result is effectively the same as if the exec were not there at all. It will not end the xinitrc script as the `&` takes precedence and starts a new subshell in which `exec $WHATEVER` is executed. The xterm, xclock, and twm lines likely all just fail silently assuming they are not actually installed - if they were installed (or ever get installed) fyulita would likely be very unhappy with the results.

So it's a lot of gibberish indicating that fyulita didn't really read the wiki page they copy and pasted from, nor do they understand much about shell scripting. But again, the code as-is likely "works" in the sense of acheiving their intended goal (for now, in an extremely fragile, bloated, and silly way).

2ManyDogs · 2020-09-11 12:53:27

I also almost didn't comment -- but my issue is that fyulita is recommending that xinitrc as a "solution" for the OP's problem ("the rest is what you should probably have"), and while it may "work" it should not be recommended to others, and fyulita might want to take another look at it before it breaks.

seth · 2020-09-11 14:45:28

Leaving aside that it only works because twm isn't installed.
Also: necrobump, actually.

2ManyDogs · 2020-09-11 16:21:44

seth wrote:

Also: necrobump, actually.

True, and the OP has not been back to the forum since July.

Closing.

Arch Linux

#1 2019-11-25 12:07:23

Thunar delay on start

#2 2020-09-10 15:15:10

Re: Thunar delay on start

#3 2020-09-11 02:20:25

Re: Thunar delay on start

#4 2020-09-11 12:35:49

Re: Thunar delay on start

#5 2020-09-11 12:46:42

Re: Thunar delay on start

#6 2020-09-11 12:53:27

Re: Thunar delay on start

#7 2020-09-11 14:45:28

Re: Thunar delay on start

#8 2020-09-11 16:21:44

Re: Thunar delay on start

Board footer