[bt-devel] [ bibletime-Bugs-1611953 ] SWORD BUG: Personal comments saved with invalid file names

Sat Nov 14 14:48:19 MST 2009

Bugs item #1611953, was opened at 2006-12-09 03:58
Message generated for change (Settings changed) made by mgruner
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100954&aid=1611953&group_id=954

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Backend / SWORD
Group: None
>Status: Closed
>Resolution: Fixed
Priority: 2
Private: No
Submitted By: John A. Sullivan III (jsulliva)
Assigned to: Martin Gruner (mgruner)
Summary: SWORD BUG: Personal comments saved with invalid file names

Initial Comment:
I am using bibletime 1.6.2 on ubuntu 6.0.6 filly patched for amd64.  Sword 1.5.9 and CLucene 0.9.16a all compiled from source.

I am not able to create new comments in the personal commentary (I do have sufficient permissions to do so).   More specifically, the comment is actually created but it cannot be retrieved.  It is created with an invalid file name (non-printable ascii character or ??).

BibleTime and Sword are both in /usr/local.  The /usr/local/share/sword/modules/comments/rawfiles/personal directory is owned by me and has a 755 rights mask.

----------------------------------------------------------------------

Comment By: Jonathan Marsden (jmarsden)
Date: 2009-11-14 21:26

Message:
> Jonathan, can you confirm this too?

Confirmed as fixed (problem no longer exists), using bibletime
2.3.3-1~jaunty2 and libsword8 1.6.0+dfsg-1~jaunty1 on Ubuntu 9.04 Jaunty
amd64.

----------------------------------------------------------------------

Comment By: Martin Gruner (mgruner)
Date: 2009-11-14 20:06

Message:
Jonathan, can you confirm this too?

----------------------------------------------------------------------

Comment By: John A. Sullivan III (jsulliva)
Date: 2009-11-14 19:54

Message:
I'm delighted to report that this is now working fine for me.   sword 1.6.0
bibletime 2.3.3 on 64 bit Ubuntu 8.0.4 fully patched.

----------------------------------------------------------------------

Comment By: Martin Gruner (mgruner)
Date: 2009-11-14 19:25

Message:
Can you please verify if this bug is still present in the latest Sword
(1.6.0)?

----------------------------------------------------------------------

Comment By: Nobody/Anonymous (nobody)
Date: 2009-04-02 00:46

Message:
I just re-recreated this one starting from scratch on my Ubuntu Intrepid
8.10 x64 machine.

That is, I:

 * Uninstalled bibletime and bibletime-data and libsword7
 * Made sure there was no /etc/sword.conf file, and no /usr/share/sword/
directory
 * rm -r ~/.sword # so that there are no existing modules or SWORD
configuration data
 * Followed the instructions at
http://devel.bibletime.info/wiki/Testing_BibleTime_on_Ubuntu
 * Installed KJV
 * Installed Personal
 * Opened KJV, and then right click on Personal and choose Edit -> Plain
text
 * Added a comment on Gen 1:1.  Clicked on the floppy disk icon to save
the comment.
 * Closed Personal
 * Opened it again (for editing, as above).
 * Added a couple of words to the comment.  Clicked on floppy disk icon.
 * Closed Personal, closed KJV, closed BibleTime
 * Look at files under ~/.sword/modules/comments/rawfiles/personal/
 * Note existence of a file whose name is \r\n  # Use ls -lb for seeing
this)

 * Start bibleetime
 * Open KJV and then Personal

Expected Behaviour: The edited comment should be displayed.

Actual Behaviour: The original unedited comment is displayed.

Note: There was no old data around, no 32 bit version of anything.
This is not a 32bit -> 64bit conversion bug, it is a file naming bug
in the 64bit version of the SOWRD 1.5.11 library.

----------------------------------------------------------------------

Comment By: Jonathan Marsden (jmarsden)
Date: 2009-03-24 06:47

Message:
Since it may be significant,
I am using sword 1.5.11, and
both BibleTime and sword were
installed from .deb packages.

----------------------------------------------------------------------

Comment By: Jonathan Marsden (jmarsden)
Date: 2009-03-24 06:46

Message:
This issue still exists for me
running BibleTime 2.0 alpha2
under Ubuntu 8.10 Intrepid x64.

The filename is displayed as ??
by an ls command but is actually 
the two characters CR and LF (ASCII
hex values 0x0D and 0x0A).  You can 
see this by doing

  tar cf - ~/.sword/modules/comments/rawfiles/personal/ | tar tf -

which on my test machine outputs:

tar: Removing leading `/' from member names
home/jonathan/.sword/modules/comments/rawfiles/personal/
home/jonathan/.sword/modules/comments/rawfiles/personal/incfile
home/jonathan/.sword/modules/comments/rawfiles/personal/\r\n
home/jonathan/.sword/modules/comments/rawfiles/personal/ot.vss
home/jonathan/.sword/modules/comments/rawfiles/personal/nt.vss
home/jonathan/.sword/modules/comments/rawfiles/personal/nt
home/jonathan/.sword/modules/comments/rawfiles/personal/0000000
home/jonathan/.sword/modules/comments/rawfiles/personal/ot

In this output from tar the characters concerned are displayed as \r\n

Furthermore, this file contains the edited version of the comment,
as the original reporter states.

Jonathan

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100954&aid=1611953&group_id=954