Thunar smb:// stops working

12oclocker · 2019-02-03 00:38:05

In bl-Helium-4-amd64.iso, I noticed when using Thunar 1.6.11, if I try to connect to a samba share using smb:// in the address field, and I accidentally mistype the share name making it invalid, sometimes that completely breaks all Thunar smb share access, not even valid shares can be accessed, and I must reboot for the problem to resolve. Anyone have any ideas how to fix, anyone seen this problem before? Did some typical googling but cannot find anything.

lowrider · 2019-02-03 00:45:01

get rid of M$ maybe? sorry :8

Bearded_Blunder · 2019-02-03 00:53:37

You could try restarting the Thunar daemon rather than a full reboot.
I guess I've been lucky, I've not seen the problem.
@lowrider, getting rid of M$ doesn't rid you of smb shares, many/most off the shelf NAS boxes expose smb shares.

12oclocker · 2019-02-03 16:04:44

actually lowrider, I got rid of MS years ago, but I still use samba shares across my network because it plays nicely with other embedded devices and NAS devices that use smb for their file sharing...
What is strange is that restarting the Thunar daemon seems to have no effect, only a reboot fixes the issue. I will see if I can track down exactly what daemon is failing when it pops up again, its very strange.

THX1138 · 2019-02-05 16:21:23

Couple of questions for 12oclocker
What effect on the does disabling the ethernet/wifi port, waiting 5 seconds, then re-enabling it, have when smb stops responding?
Have you disabled firewalls and other security on both machines?

If I were to take a wild guess my thoughts would be with something blocking a port
maybe some kind of security arrangement. I used to have a NAS drive that would block
connctions after a couple of unsuccessful attempts to log in, but the computer I was accessing from would keep hammering the door to get in.

You could try

netstat -tp

to see the state of smb before this happens
and again after it happens

Last edited by THX1138 (2019-02-05 16:33:43)

12oclocker · 2019-05-13 22:42:46

I found a fix, adding "sleep 1 &&" in autostart file before thunar dameon, fixes the issue on all 4 laptops I have.
It appears a race condition, that if thunar dameon starts too soon, before wifi or network connections maybe, then its network capabilities will be broken until rebooted. smbtree and smbclient always work, even when thunar does not.

ohnonot · 2019-05-14 04:42:39

12oclocker wrote:

It appears a race condition, that if thunar dameon starts too soon, before wifi or network connections maybe, then its network capabilities will be broken until rebooted.

are you sure a reboot is required?
shouldn't killing/restarting the thunar daemon be enough?

johnraff · 2019-05-14 07:02:46

Bearded_Blunder wrote:

You could try restarting the Thunar daemon rather than a full reboot.

12oclocker wrote:

What is strange is that restarting the Thunar daemon seems to have no effect, only a reboot fixes the issue.

ohnonot · 2019-05-17 03:51:10

^ fair enough.
i meant it more like "are you sure you actually really really killed all thunar processes" - but yes, i can see now that op mentioned "I will see if I can track down exactly what daemon is failing" - because i seem to remember that thunar is using some helper processes.

in any case, adding a 1s delay is a reasonable workaround i think, so no sleuthing required.

#1 2019-02-03 00:38:05

Thunar smb:// stops working

#2 2019-02-03 00:45:01

Re: Thunar smb:// stops working

#3 2019-02-03 00:53:37

Re: Thunar smb:// stops working

#4 2019-02-03 16:04:44

Re: Thunar smb:// stops working

#5 2019-02-05 16:21:23

Re: Thunar smb:// stops working

#6 2019-05-13 22:42:46

Re: Thunar smb:// stops working

#7 2019-05-14 04:42:39

Re: Thunar smb:// stops working

#8 2019-05-14 07:02:46

Re: Thunar smb:// stops working

#9 2019-05-17 03:51:10

Re: Thunar smb:// stops working

Board footer