After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 681144 - "Send To" function replaces spaces in file name with 0s and consequently cannot find the file when attempting to email it
"Send To" function replaces spaces in file name with 0s and consequently cann...
Status: RESOLVED FIXED
Product: evince
Classification: Core
Component: general
3.4.x
Other Linux
: Normal normal
: ---
Assigned To: Evince Maintainers
Evince Maintainers
Depends on:
Blocks:
 
 
Reported: 2012-08-03 15:06 UTC by Geoffrey van Wyk
Modified: 2012-08-08 02:17 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Geoffrey van Wyk 2012-08-03 15:06:07 UTC
When I try to email a PDF with spaces in the file name, Evince tells me that the file does not exist and so could not be attached.

Steps to reproduce:

1) Open the PDF file with spaces in the file name, e.g. "GNOME Rules.pdf", with Evince.

2) In Evince, click the File menu. On the file menu click Send To... item. The Send To dialog appears.

3) On the Send To dialog, in the Destination section, Email will be selected in the "Send as:" dropdown list. In the "Send to:" textbox, enter a valid email address.

4) On the Send To dialog, click the Send button.


Actual results:

The File Attach error message will appear, stating that the PDF file you were trying to send does not exist and so could not be attached.

In the File Attach dialog you will notice that spaces in the file name have been replaced by 0s. This is the reason why the program cannot find the file.

Expected results:
A new email message composing window from the default email client should appear, with the email address entered in to Send To dialog appearing in the To field, and with the PDF document attached.
Comment 1 Carlos Garcia Campos 2012-08-07 16:56:43 UTC
Fixed in git master, thanks for reporting.
Comment 2 Geoffrey van Wyk 2012-08-08 02:17:22 UTC
(In reply to comment #1)
> Fixed in git master, thanks for reporting.

Thanks.