Bug 403641

Summary:	jpilot cannot view private records on x86_64 platform
Product:	[Fedora] Fedora	Reporter:	George Avrunin <avrunin>
Component:	pilot-link	Assignee:	Ivana Varekova <varekova>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	low	Docs Contact:
Priority:	low
Version:	8
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:	0.12.2-17.fc8	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2008-02-02 09:00:21 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 George Avrunin 2007-11-28 23:42:42 UTC

Description of problem: jpilot cannot show private records


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


How reproducible: every time


Steps to Reproduce:
1. Start jpilot with a database containing private records
2. Click on the "lock" button to view private records
3. jpilot asks for password, but never accepts the password
  
Actual results: jpilot never accepts the PalmOS password and so doesn't allow
the user to view private records.


Expected results: Should accept password and unlock private records


Additional info: The problem seems to be due to a 64-bit bug in pilot-link.  I
asked about this problem on the jpilot list and received a response from Ludovic
Rousseau, who pointed me to the following bug he had recently
filed at pilot-link.org: http://bugs.pilot-link.org/1858

He says that the problem is due to a 64-bit bug in pilot-link, where
pi-md5.h has 
  #define UINT32 unsigned long
which is incorrect on 64-bit systems, and that this prevents jpilot from
computing the right hash to view private records.  He recommends
changing this to 
  #define UINT32 unsigned int
though he notes that this will work on 32- and 64-bit systems but fail
on 16-bit ones. 

I rebuilt the pilot-link and jpilot srpms with this change in the pilot-link
source and jpilot can now view private records on my laptop.  So the fix seems
to work, but I have not tested it extensively.

(This is probably really a bug in pilot-link, but as far as I know it only
manifests itself in jpilot.  Rahul Sundaram on the Fedora list recommended
filing it against jpilot.)

Comment 1 Ivana Varekova 2007-12-10 14:49:17 UTC

This is pilot-link problem - there have to be change pilot-link source code - so
reassignning to pilot-link.

Comment 2 Ivana Varekova 2007-12-11 08:46:04 UTC

Thanks for the bug report and really detailed description/investigation - the
bug is fixed in pilot-link-0.12.2-11.fc8.

Comment 3 Fedora Update System 2007-12-12 19:59:38 UTC

pilot-link-0.12.2-11.fc8 has been pushed to the Fedora 8 testing repository.  If problems still persist, please make note of it in this bug report.
 If you want to test the update, you can install it with 
 su -c 'yum --enablerepo=updates-testing update pilot-link'

Comment 4 Fedora Update System 2008-01-11 22:11:10 UTC

pilot-link-0.12.2-17.fc8 has been pushed to the Fedora 8 testing repository.  If problems still persist, please make note of it in this bug report.
 If you want to test the update, you can install it with 
 su -c 'yum --enablerepo=updates-testing update pilot-link'

Comment 5 Fedora Update System 2008-02-02 09:00:12 UTC

pilot-link-0.12.2-17.fc8 has been pushed to the Fedora 8 stable repository.  If problems still persist, please make note of it in this bug report.