Bug 77484

Summary:	display prefs ignored after up2date
Product:	[Retired] Red Hat Linux	Reporter:	Need Real Name <ewalter>
Component:	squirrelmail	Assignee:	Warren Togami <wtogami>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	medium	Docs Contact:
Priority:	medium
Version:	8.0
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2004-10-20 04:26:20 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Need Real Name 2002-11-07 20:30:09 UTC

From Bugzilla Helper: 
User-Agent: Mozilla/5.0 (compatible; Konqueror/3; Linux) 
 
Description of problem: 
After running up2date, squirrel mail was upgraded from 1.2.7-4 to 1.2.8  My 
squirrelmail prefs were set to display 50 messages per page.  After the 
update, this setting was ignored.  Re-submitting my preferences here had no 
affect.  Deleting /var/lib/squirrelmail/prefs/myaccount.prefs and letting 
squirrelmail recreate it also failed to fix the problem.  Rolling back to 
version 1.2.7 resolved my problems.  Note: this problem manifested itself 
regardless of the user logging in to squirrelmail. 
 
Version-Release number of selected component (if applicable): 
1.2.8 
 
How reproducible: 
Always 
 
Steps to Reproduce: 
1.  Setup Squirrelmail 1.2.7 
2.  Set user prefs to display > 15 messages per page 
3.  Upgrade squirrelmail w/ up2date to 1.2.8 version 
4.  Login to inbox w/ over 15 messages in it. 
5.  See that prefs are ignored ;^) 
	 
 
Actual Results:  My display prefs were ignored.  On login, folders only 
display 15 messages per page, regardless of settings. 
 
Expected Results:  Number of messages displayed per folder should match 
settings in Options -> Display Preferences 
 
Additional info:

Comment 1 Warren Togami 2004-10-20 04:26:20 UTC

please open a new report if this is still an issue in FC3.