[Bug 135680] Re: evince chokes on absolute paths that include a #

2008-06-30 Thread Pedro Villavicencio
no response, closing the bug, thanks. ** Changed in: evince (Ubuntu) Status: Incomplete = Invalid -- evince chokes on absolute paths that include a # https://bugs.launchpad.net/bugs/135680 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug

[Bug 135680] Re: evince chokes on absolute paths that include a #

2008-06-06 Thread Pedro Villavicencio
May someone expriencing the behavior send this upstream? -- evince chokes on absolute paths that include a # https://bugs.launchpad.net/bugs/135680 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list

[Bug 135680] Re: evince chokes on absolute paths that include a #

2008-05-08 Thread Pedro Villavicencio
May someone able to reproduce this can send it to the upstream bug tracker? for forwarding instructions please have a look to https://wiki.ubuntu.com/Bugs/Upstream/GNOME ; leaving this as incomplete until that, thanks in advance. ** Changed in: evince (Ubuntu) Status: New = Incomplete --

[Bug 135680] Re: evince chokes on absolute paths that include a #

2008-02-28 Thread Aidan Furlan
I can confirm that this bug is NFS-related. I get the error The local file URI '%s' may not include a '#' -- whenever I try to open a pdf with a '#' in the filename on an NFS share, but if I copy the file to the desktop it opens. I can also open the same file from the share if I rename it to get

[Bug 135680] Re: evince chokes on absolute paths that include a #

2007-09-25 Thread Sebastien Bacher
unconfirming, I don't have a NFS configuration to try that, somebody getting the issue should probably send it upstream on bugzilla.gnome.org ** Changed in: evince (Ubuntu) Status: Incomplete = New -- evince chokes on absolute paths that include a # https://bugs.launchpad.net/bugs/135680

[Bug 135680] Re: evince chokes on absolute paths that include a #

2007-09-03 Thread Sebastien Bacher
is that specific to evince? or do you have similar issues with other GNOME softwares? -- evince chokes on absolute paths that include a # https://bugs.launchpad.net/bugs/135680 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. --

Re: [Bug 135680] Re: evince chokes on absolute paths that include a #

2007-09-03 Thread Peter Cordes
On Mon, Sep 03, 2007 at 03:09:41PM -, Sebastien Bacher wrote: is that specific to evince? or do you have similar issues with other GNOME softwares? AFAICT, only evince has this problem. bluefish, eog, file-roller, gedit and ghex2 are all fine on symlinks on /net/llama, and don't make

[Bug 135680] Re: evince chokes on absolute paths that include a #

2007-08-30 Thread Sebastien Bacher
Thank you for your bug. Opening a filename with a # from nautilus works fine on gutsy for me. What version of Ubuntu do you use? Did you try to double click on it with nautilus, does it work? ** Changed in: evince (Ubuntu) Importance: Undecided = Low Assignee: (unassigned) = Ubuntu

[Bug 135680] Re: evince chokes on absolute paths that include a #

2007-08-30 Thread Peter Cordes
Launching from Nautilus shows the same problem for me. You probably need an NFS mount, or maybe even an autofs-mounted NFS mount, to reproduce this. Like I said, it only happens in /net for me. I just tried copying my file to bar.pdf. Then evince /net/llama/home/peter/bar.pdf works. (It

[Bug 135680] Re: evince chokes on absolute paths that include a #

2007-08-29 Thread Peter Cordes
oh yeah, IIRC once evince is running, use open from the menu and browsing to the /net path works with no problem. And this is mis-titled, because the problem only happens on /net (or maybe any NFS mount). evince /home/peter/... is ok. -- evince chokes on absolute paths that include a #