Bug 77593 - Evolution not retaining settings
Summary: Evolution not retaining settings
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: evolution
Version: 8.0
Hardware: i386
OS: Linux
Target Milestone: ---
Assignee: Jeremy Katz
QA Contact:
Depends On:
TreeView+ depends on / blocked
Reported: 2002-11-09 23:08 UTC by Dee-Ann LeBlanc
Modified: 2008-05-01 15:38 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2003-01-03 07:37:48 UTC

Attachments (Terms of Use)

Description Dee-Ann LeBlanc 2002-11-09 23:08:43 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.1) Gecko/20021003

Description of problem:
If I close Evolution and then re-open it, it loses one specific setting, which
is my email address. I have this problem on one computer with RHL 8 and
evolution-1.0.8-10, but not another computer with RHL 8 and the exact same
package version. The problem computer was installed off the boxed set personal
edition but the computer without the problem was installed off the beta team's
8.0 download.

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

How reproducible:

Steps to Reproduce:
1. Enter GNOME.
2. Open Evolution.
3. Click Tools|Mail Settings
4. Select the account in question
5. Click Edit to open the Evolution Account Editor
6. Set email address under Required Information.
7. Click Apply, then OK
8. Exit Evolution
9. Restart Evolution
10. Repeat steps 3-5
11. The email address is set back to dee@localhost.localdomain

Actual Results:  I try to send mail and it bounces back because it's sent with
an invalid email address.

Expected Results:  Evolution should be retaining the settings.

Additional info:

I can't think of anything extra. See Description.

Comment 1 Jeremy Katz 2002-11-22 17:17:00 UTC
I haven't seen this on any of my machines or reported by anyone else.  Are you
maybe running out of disk space on the one machine or something?  Or not exiting

Comment 2 Jeremy Katz 2003-01-03 07:37:48 UTC
Closing due to inactivity.  If you have any further information to add to this
bug, please feel free to reopen it.

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