** Changed in: file-roller
Importance: Unknown = Medium
--
Archive Manager cannot read archive from remote gnome-vfs shares (Samba, FTP,
etc.)
https://bugs.launchpad.net/bugs/36498
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a direct
** Changed in: file-roller
Status: Fix Released = Fix Committed
--
Archive Manager cannot read archive from remote gnome-vfs shares (Samba, FTP,
etc.)
https://bugs.launchpad.net/bugs/36498
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a
** Changed in: file-roller
Status: Fix Committed = Fix Released
--
Archive Manager cannot read archive from remote gnome-vfs shares (Samba, FTP,
etc.)
https://bugs.launchpad.net/bugs/36498
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a
** Changed in: fileroller (upstream)
Status: Confirmed = Fix Released
--
Archive Manager cannot read archive from remote gnome-vfs shares (Samba, FTP,
etc.)
https://bugs.launchpad.net/bugs/36498
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
This upload fixes the bug:
file-roller (2.19.1-0ubuntu1) gutsy; urgency=low
.
* New upstream version:
- Added ability to load and save remote archives, to add remote files
to an archive and to extract to remote locations. (Ubuntu: #36498)
- Make sure the extract_here
Rouben:
If you are seeing this behavior in totem (and I guess it depends on
whether you are using totem gstreamer or totem xine too) then your best
bet is to file a sepearte bug report as the problem may not be related
to what is seen in this bug.
--
Archive Manager cannot read archive from
Funny, I have the same problem with Totem. Basically it won't play
anything from gnome-vfs. Here's exactly how the error message appears:
=
Totem could not play 'smb://HOME_NET;[EMAIL PROTECTED]/private/engage.mpeg'.
Could not read from resource.
=
