Bug 180722 - KDE4's kmail cannot save any attachment to network paths
Summary: KDE4's kmail cannot save any attachment to network paths
Status: RESOLVED DUPLICATE of bug 165418
Alias: None
Product: kmail
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-01-14 20:09 UTC by Tamás Németh
Modified: 2009-03-19 00:38 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Tamás Németh 2009-01-14 20:09:56 UTC
Version:           4.1.3-3.11 (using KDE 4.1.3)
Compiler:          gcc-4.3 compiled for openSUSE 11.1 by the opensuse team
OS:                Linux
Installed from:    SuSE RPMs

It cannot save to network directories, like smb://, ftp://, sftp:// and the
like, only to local directories, while - for example - KDE4's kwrite can save
to network places, and it seems to use the same KDE4 dialog.

Reproducible: Always

Steps to Reproduce:
1.Send yourself a mail with an attachment
2 [details].Read it in kmail (KDE4 version)
3.Try to save the attachment, giving a remote URL (e.g.
sftp://LOGIN@HOST/DIRECTORY) as the path to save the file to.
Actual Results:  
It will report something like writing to the file was unsuccesful.

Expected Results:  
It should be able to save to remote directories, like kwrite, for example.

There are other strange symptoms, relating to saving to network places in
kmail. For example I instructed it to save the path, the loginname and the
password to kwallet, but it asked for the password again, despite showing the
contents of the target directory before asking for the password!?!?!?


I've also reported it here:
https://bugzilla.novell.com/show_bug.cgi?id=466105
Comment 1 Jaime Torres 2009-01-18 13:26:03 UTC
It works for me in kde 4.1.96, using fish://user@host/path ,pressing intro, entering the password, and then the filename.
Comment 2 Jonathan Marten 2009-02-24 15:40:24 UTC

*** This bug has been marked as a duplicate of bug 165418 ***