You are not logged in.
Ever since using systemd (although I cannot say that I can confirm that systemd is directly causing it), launching remote video files with various players (f.e. totem, vlc) result in a freeze of the players. Sometimes it does run. It seems random.
However I have found out that having smbd.service running completely solves any application freeze.
I am not under the assumption that a samba client requires a server on the same system all of a sudden? Maybe I'm missing something...
EDIT: just to be clear: when I open a remote video file on a samba share with a player the player often freezes. When I start smbd.service on the client no more freezes...
Last edited by whoop (2013-01-22 16:40:49)
Offline
I think samba is a dependency of vlc.
I'm not sure why this is.
I never have samba running when using vlc and it works just fine.
It might be a problem with your X server.
I may have to CONSOLE you about your usage of ridiculously easy graphical interfaces...
Look ma, no mouse.
Offline
I think samba is a dependency of vlc.
I'm not sure why this is.
I never have samba running when using vlc and it works just fine.
It might be a problem with your X server.
Ahh, I see I have not been clear. I meant I have no problem running video files perse. I do have problems opening remote files from a samba share. I often get an application freeze when running a (video) file from a remote samba share. The problem goes away when I start smbd.service on the client side (which seems illogical). This seems have started when I made the switch to systemd.
I don't get why it should have anything to do with X.
Offline
Um...you don't need smbd.service running necessarily for the client, you need nmbd.service, which is probably called as a dependency with smbd.service. If you can, and don't need the extensive security that samba provides, I would suggest using NFS exports.
I may have to CONSOLE you about your usage of ridiculously easy graphical interfaces...
Look ma, no mouse.
Offline