Bug 108159 - "Save message" pops up wrong dialog box
Summary: "Save message" pops up wrong dialog box
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: evolution
Version: rawhide
Hardware: i386
OS: Linux
medium
low
Target Milestone: ---
Assignee: Dave Malcolm
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2003-10-28 05:53 UTC by Ben Hsu
Modified: 2007-11-30 22:10 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2006-05-05 12:18:20 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Ben Hsu 2003-10-28 05:53:51 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.5a) Gecko/20030728
Mozilla Firebird/0.6.1

Description of problem:
When I "save message" in evolution the file selector box has the heading "Attach
file(s)". It should be "Save message" or something like that

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

How reproducible:
Always

Steps to Reproduce:
1. compose new message
2. Hit Ctrl-S to save

    

Actual Results:  message box pops up with heading "Attach file(s)"

Expected Results:  message box should say something related to saving

Additional info:

Comment 1 Douglas Furlong 2003-10-28 09:10:24 UTC
I have just tried it again at work, and it no longer seems to be exhibiting the
behaviour.

I did test this on two seperate machines, and was getting the same results,
however, now I do not.

I have tried several times to re-create the bug, but nothing.

However, on a seperate machine, I have noticed that the error message for site
not contactable using Firebird .07 appears underneath the main browser window,
and the only way to get rid of it, is to tab to it, then hit return (hoewver
this does not bring the error mesasge to the front).

This suggests that it may be a problem else where, but I don't know where to
look : (

Doug

Comment 2 Jeremy Katz 2003-10-28 15:41:27 UTC
Fixed in -7.


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