Bug 77102 - users upgrading to 1.0.3 find the .Profile does not work
Summary: users upgrading to 1.0.3 find the .Profile does not work
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: abiword
Version: 8.0
Hardware: i386
OS: Linux
Target Milestone: ---
Assignee: Jeremy Katz
QA Contact: Mike McLean
URL: http://bugzilla.abisource.com/show_bu...
Depends On:
TreeView+ depends on / blocked
Reported: 2002-11-01 06:32 UTC by Need Real Name
Modified: 2007-04-18 16:48 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2002-11-01 06:32:46 UTC

Attachments (Terms of Use)

Description Need Real Name 2002-11-01 06:32:40 UTC
Description of Problem: 
users upgrading to 1.0.3 find the .Profile does not work

Version-Release number of selected component (if applicable):
RH ships pre-1.0.3, this occurs when users upgrade to 1.0.3

How Reproducible:
Had to guess

Steps to Reproduce:
1. do standard install 1.0.3
2. change your defaults
3. restart AbiWord
4. complain on userlist when defaults don't stick (note this won't be the only
5. I'll place comments in 4222
6. I might, someday, get feedback from Red Hat
7. actually give me feedback!
8. #'s 1-3 and #7 are all that are requested 

Actual Results:
Continues to act like nothing is changed (literally, nothing is changed)
the Profile has to be edited by hand.

Expected Results:
Normally, users anticipated their changes will stick.

Additional Information:
	There may be something similar on Windows, i.e. I may be hallucinating, but the
ones with the largest issues (major in traditional severity) occur on RH8
settings.  There's one in the list that has problems with the font warning and
splash screen on RH7.3, which I cannot confirm, that is to say, I possess the
same setup without the same problem.
	Do contact for more information or help with a work around.

/me decides not to go into the GPL speech.

Comment 1 Jeremy Katz 2002-11-01 15:59:57 UTC
We shipped abiword 1.0.2 in Red Hat Linux 8.0.  The configuration is
mind-numbingly boring, so the only way I can see this causing problems if if the
problem code is upstream.  Especially since you seem to imply that there are
reports of the same problem on Windows.  

I've confirmed that this works correctly with 1.0.2, so this is NOTABUG for me
until we ship something newer and see if the problem occurs.

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