Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 132215 - evolution won't re-save default signature as 'None' after a different has been selected and saved
Summary: evolution won't re-save default signature as 'None' after a different has bee...
Keywords:
Status: CLOSED DUPLICATE of bug 130110
Alias: None
Product: Fedora
Classification: Fedora
Component: evolution
Version: 3
Hardware: x86_64
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Dave Malcolm
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks: 131589
TreeView+ depends on / blocked
 
Reported: 2004-09-09 21:55 UTC by Zack Cerza
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-02-21 19:05:33 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)

Description Zack Cerza 2004-09-09 21:55:04 UTC 
Description of problem:
Evolution won't save an account's default signature as 'None' if it
has ever been changed from 'None' and saved. Confused yet? The steps
to reproduce should help explain... if not, come yell at me ;)

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

How reproducible:
Always

Steps to Reproduce:
1. On an account that has never had a default signature other than 'None':
2. Select a real signature, such as 'Autogenerated' or a custom sig
3. Press OK
4. Re-enter that account's Properties dialog
5. Select signature 'None'
6. Press OK
  
Actual results:
Default signature remains what was selected in step 2.

Expected results:
Default signature is 'None'.
Comment 1 Dave Malcolm 2004-09-15 23:15:53 UTC 
I've attempted to reproduce this in Evo 2.0.0 without success
Comment 2 Dave Malcolm 2004-09-28 19:00:47 UTC 

*** This bug has been marked as a duplicate of 130110 ***
Comment 3 Red Hat Bugzilla 2006-02-21 19:05:33 UTC 
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.
Note You need to log in before you can comment on or make changes to this bug.