closing the bug as deprecated since gvfs is used now
** Changed in: gnome-vfs2 (Ubuntu)
Status: Confirmed = Invalid
--
Opening a file in gedit on a gnome-vfs share fails
https://bugs.launchpad.net/bugs/67385
You received this bug notification because you are a member of Ubuntu
Bugs,
I don't know... I have this error on gutsy
--
Opening a file in gedit on a gnome-vfs share fails
https://bugs.launchpad.net/bugs/67385
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
The problem occurs only if I browse the samba share looking for the text
file in Nautilus (Double click to Network Icon, Windows net, shared pc,
shared folder etc...) and I open the file double clicking on it.
If I open gedit first, I go to File, Open, and I browse Network, Windows
Net, etc...
Well, I have Gutsy Release Candidate, and I was just able to open a text
document on a gnome-vfs SAMBA share, so I guess it's been fixed in
Gutsy. The only issue is that gedit prompted me to allow it to access my
keyring in order to connect to the SAMBA share (my GNOME keyring
contains my
Sergio, what underlying protocol were you using? In other words, what
type of gnome-vfs share was it? FTP, WebDAV, SSH/SFTP, Samba?
--
Opening a file in gedit on a gnome-vfs share fails
https://bugs.launchpad.net/bugs/67385
You received this bug notification because you are a member of Ubuntu
It's a Windows share, so Samba.
--
Opening a file in gedit on a gnome-vfs share fails
https://bugs.launchpad.net/bugs/67385
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
Still here on Feisty up-to-date.
** Changed in: gnome-vfs2 (Ubuntu)
Status: New = Confirmed
--
Opening a file in gedit on a gnome-vfs share fails
https://bugs.launchpad.net/bugs/67385
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact
** Changed in: gnome-vfs2 (Ubuntu)
Importance: Undecided = Low
Status: Needs Info = Unconfirmed
--
Opening a file in gedit on a gnome-vfs share fails
https://bugs.launchpad.net/bugs/67385
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug
I still have this on an up to date system. Which package was patched?
--
Opening a file in gedit on a gnome-vfs share fails
https://launchpad.net/bugs/67385
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
There's been a patch out for gnome-vfs recently (if you keep your system
up to date, you should already have it by now). Can anyone who has
installed this patch reproduce this issue? I can't anymore...
** Changed in: gnome-vfs2 (Ubuntu)
Status: Unconfirmed = Needs Info
--
Opening a file
That's probably not a duplicate of the other bug which is fixed, no
--
Opening a file in gedit on a gnome-vfs share fails
https://launchpad.net/bugs/67385
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Could this be related to bug #60277? Given the symptoms (works the
second time), this may be a possibility...
--
Opening a file in gedit on a gnome-vfs share fails
https://launchpad.net/bugs/67385
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
@Rouben. Yes this happens with Totem as well, even with the same error
message. Originally I filed two separate bugs, one for Gedit and one for
Totem. Caroline Ford has merged the two into one as shown in an earlier
comment; the Totem-bug is apparantly completely wiped away, I cannot
find this one
do you open the gedit file from nautilus with a double click or from
gedit using the fileselector? The totem bug is described by bug #60326,
the gedit issue might be a different one
--
Opening a file in gedit on a gnome-vfs share fails
https://launchpad.net/bugs/67385
--
ubuntu-bugs mailing
@Sebastien Bacher. I open the file with a double-click in Nautilus.
Note: after failure, doing it exactly again, the file opens without a
problem.
--
Opening a file in gedit on a gnome-vfs share fails
https://launchpad.net/bugs/67385
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
@Sebastien Bacher.
You asked: does gnomevfs-ls smb://lin01/public/Setup/Linux works too? what
about gnomevfs-info smb://lin01/public/Setup/Linux/edgy-bugs.txt and
gnomevfs-cat smb://lin01/public/Setup/Linux/edgy-bugs.txt?
Yes, they all work. I also noticed that the error only occurs the first
Does this apply to Totem as well? I noticed that Totem has problems
opening files on SMB gnomevfs mounts. Perhaps this has something to do
with file locking (or something like that) which gnomevfs doesn't
implement properly?
--
Opening a file in gedit on a gnome-vfs share fails
does gnomevfs-ls smb://lin01/public/Setup/Linux works too? what about
gnomevfs-info smb://lin01/public/Setup/Linux/edgy-bugs.txt and
gnomevfs-cat smb://lin01/public/Setup/Linux/edgy-bugs.txt?
--
Opening a file in gedit on a gnome-vfs share fails
https://launchpad.net/bugs/67385
--
ubuntu-bugs
gedit and totem use gnome-vfs. Do you have the libgnomevfs2-extra
package installed? Does gnomevfs-ls smb://lin01/public work correctly?
** Changed in: Ubuntu
Sourcepackagename: None = gnome-vfs2
Assignee: (unassigned) = Ubuntu Desktop Bugs
--
Opening a file in gedit on a gnome-vfs share
Package libgnomevfs2-extra is installed:
[EMAIL PROTECTED]:~$ dpkg -l libgnomevfs2-extra
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Installed/Config-files/Unpacked/Failed-config/Half-installed
|/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err: uppercase=bad)
||/ Name
Could be, but I'm not certain about this, see this previously filed bug by me:
https://launchpad.net/distros/ubuntu/+source/file-roller/+bug/36498
In one of the comments, Nicolò Chieffo is saying: is it supposed that
file-roller can't handle gnome-vfs?? Well, it should This indicates
that
Detected on Edgy RC1, gedit 2.16.1. Write permissions are in place: possible to
create a text-file on the given share.
Added a screenshot.
** Attachment added: Error message
http://librarian.launchpad.net/4920986/open-textfile-with-gedit-on-samba.png
--
Opening a file in gedit on a
Detected on Edgy RC1, gedit 2.16.1. Write permissions are in place: possible to
create a text-file on the given share.
Added a screenshot.
** Attachment added: Error message
http://librarian.launchpad.net/4920987/open-textfile-with-gedit-on-samba.png
--
Opening a file in gedit on a
I've merged your two bugs as I think they are probably the same issue.
As you have the same problem with 2 packages I doubt that it is two
seperate bugs.
** Changed in: gedit (Ubuntu)
Sourcepackagename: gedit = None
--
Opening a file in gedit on a gnome-vfs share fails
24 matches
Mail list logo
