*** This bug is a duplicate of bug 36498 ***
https://bugs.launchpad.net/bugs/36498
After reading what I wrote I decided to leave it intact but to include
something much shorter for the faint of heart:
Exact steps leading to my problem - I used "connect to server" to get to
the file share becouse it was not on the network list. Since then the
share is accesible through bookmark. I set up the ip, username, path all
as a windows share. It asked the password, then I could see files in
nautilus "shared on ip" the window title. When I try to open any archive
(default program for that be file-roller) I get an open file-roller
window without anyting in it. Nothing opened. Just like pressing alt+f2
and running "file-roller". Archives are not damaged, there aint any
error messages, also archive cannot be oppened using the open dialog in
file roller and typing the full file path inside
(smb://[EMAIL PROTECTED]/folder/file.zip).
--- the long ramble following ---
Well I can perform most of the operations on the smb share. Can play
music using rythmbox, movies too using totem (all gstreamer stuff seems
to be working), can copy/delete/rename, whatever from file manager when
permissions are right (on target fs, all of this logged with username
and password). What won't work - opening any file using file-roller,
similar easy-tag is a no-go, the same with mplayer. Just won't work. I
dunno a lot about the inner workings of the samba support, but I
remember that mplayer had to be compiled with smb support built in (on
my previous linux distros) for this to work - to play files directly
from the share. Seems like some programs just don't have this option to
read files directly from smb share. And file-roller one of them, which
is kinda lacking since its the default program for archive. Had lots of
similar problems with lots of programs - programs willl either download
the file to temp file before opening em or just refuse to budge like
file roller.
I can provide more info, definetely and I would gladly cooperate more if
this can be resolved. It does seem quite critical to me though - home
networking is popular and failure to open files from network shares can
be daunting esp. if the archive is like 4 gig large and you don't have
local disk space for the operation.
I can try to enter the path in file-roller itself
smb://[EMAIL PROTECTED]/shared/file.name.zip and nothing happens, the input
box helped me to enter the path though, so the gnome itself is aware of
the share. It even asked me for permission to access password storage.
I seem so vague about this - I really have some terminology problems so
please be graphical in descriptions, more familiar with command line
than gui :D Command line is simple and this is compllicated...
----
Hope it is of any help, though it makes no sense to me. Just ask for any
further info I can provide coz I'd like to see this insect squashed.
Thanks for the interest
--
File-roller won't open files(archives) on remote samba shares
https://bugs.launchpad.net/bugs/107999
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
