Bug 171101 - [kmail] error opening HTML attachment in konqueror
Summary: [kmail] error opening HTML attachment in konqueror
Alias: None
Product: Fedora
Classification: Fedora
Component: kdepim
Version: 3
Hardware: i386
OS: Linux
Target Milestone: ---
Assignee: Ngo Than
QA Contact: Ben Levenson
Depends On:
TreeView+ depends on / blocked
Reported: 2005-10-18 08:43 UTC by Radek Bíba
Modified: 2007-11-30 22:11 UTC (History)
0 users

Clone Of:
Last Closed: 2006-03-24 09:45:50 UTC

Attachments (Terms of Use)

Description Radek Bíba 2005-10-18 08:43:27 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.12) Gecko/20050922 Fedora/1.0.7-1.1.fc3 Firefox/1.0.7

Description of problem:
When I get an email with an HTML file attached and click on the created link kmail
offers me to save it, open it in konqueror or cancel it. If I select Open in
konqueror it launches konqueror with /tmp/kde-USERNAME in addressbar and an empty
content instead of the HTML file. Additionally, all CPU performance is cosumed by
konqueror, X, kwin and kicker - you may notice that konqueror toolbar and its icon
in kicker are flickering furiously.

What is strange is that a temporary file for the attachment in /tmp/kde-USERNAME
_is_ created.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. send yourself an e-mail with an HTML attachment
2 [details]. launch kmail, open your mailbox, open that e-mail
3. click on the generated link to the attachment, select Open in Konqueror
4. watch what's going on

Actual Results:  see Description

Expected Results:  the attachment is opened in konqueror

Additional info:

Perhaps other attachment types are affected, too. You may want to read
http://bugs.kde.org/show_bug.cgi?id=91410 - just two notes: 1) opening an archive
in Ark works 2) I see no error message 'File not found: ...'

Comment 1 Radek Bíba 2006-03-24 09:45:50 UTC
Not seeing this anymore in newer Fedora version and FC3 is actually deprecated so
closing this bug.

Note You need to log in before you can comment on or make changes to this bug.