gistfile1.txt

03:35:07 <kent\n> I have a bug that I've been seeing since at least 1.8 that I can't seem to track down, and I can't work it out. Its possible its something gentoo are doing, but I can't see where if it is ( bibletime is built raw from upstream sources, no patches, same for sword ) 
03:35:16 <kent\n> many dictionaries fail to be usable 
03:35:29 <kent\n> as in, they only show their first entry in the dictionary browser 
03:35:39 <kent\n> KJVD exhibits this problem 
03:35:46 <kent\n> WebstersDict does not 
03:36:28 <kent\n> BibleTime 2.3.3, SWORD library version 1.6.0, This program uses Qt Open Source Edition version 4.5.3. 
03:37:06 <jotik> Hi kent\n!
03:37:09 <kent\n> my initial thought was it was a zLD vs RawLD problem, but upon manually converting the RawLD to zLD , the problem still persists
03:37:21 <kent\n> hi jotik :)
03:38:22 <jotik> I'm on a similar Gentoo system.
03:39:29 <kent\n> I also eliminated it being an app-dict/sword-* problem by eliminating everything in there and installing stuff raw 
03:39:31 <jotik> What do you mean by first entry only?
03:39:55 <kent\n> Open KJVD, drop down menu has only one item in it , "ABASE" 
03:40:10 <kent\n> up and down arrows do not do anything 
03:40:39 <kent\n> oddly, once indexed, it can be searched inside, but only the search tool can see inside it
03:41:36 <jotik> I can't reproduce it.
03:41:49 <kent\n> its very odd. 
03:42:05 <kent\n> i've purged my sword conf many times now. 
03:42:25 <tabthorpe> longtom: here
03:43:03 <jotik> kent\n: is KJVD the only lexicon open?
03:43:21 <kent\n> yes. 
03:44:06 <longtom> tabthorpe: Finished that pdf if you want it...
03:44:21 <tabthorpe> longtom: let us pm
03:44:40 <kent\n> 1.6.0(11:39:24 14/10/09)(curl -debug -doc -icu -lucene) 
03:44:44 <jotik> kent\n: Most likely this isn't the case, but could you tell us your CXXFLAGS and ARCH
03:44:45 <kent\n> ( app-text/sword  
03:44:58 <kent\n> amd64
03:45:52 <kent\n> and CXXFlags, -march=native -mtune=native -O2 -pipe 
03:49:08 <jotik> truly odd.
03:49:25 <kent\n> its been happening to me since ~Janurary :/
03:49:33 <jotik> whats your GCC version?
03:49:50 <kent\n> 4.4.2, but it wasn't 4.4 back in janurary :)
03:51:17 <-- longtom (n=cango@dsl-242-183-190.telkomadsl.co.za) has quit (Read error: 60 (Operation timed out))
03:52:39 --> longtom (n=cango@dsl-242-183-190.telkomadsl.co.za) has joined #bibletime
03:53:46 <kent\n> ok, not january, june. 
03:54:15 <kent\n> http://bugs.gentoo.org/show_bug.cgi?id=271965 # I thought it was 1.6.0 of sword comming out, but its not 
03:54:48 <kent\n> but 1.6.0 just solved the "hey, they don't index at all" issue 
03:58:23 <jotik> Personally I'm not familiar with that code so I can't help you right away.
03:58:48 <kent\n> it appears to be a bug in my bibletime conf
03:58:57 <jotik> If it happens only with KJVD then I think its rather a sword issue.
03:58:59 <kent\n> i just trashed it and started again and the problem is gone 
03:59:15 <kent\n> ( well, mv ;) ) 
04:00:44 <kent\n> appears to be a problem in indices/ or cache/ 
04:00:55 <jotik> Hmm... I think there might have been some changes regarding configuration, but I'm not aware of any that might be related to your issue.
04:02:08 <jotik> I'm a relatively new BibleTime developer, so...
04:02:34 <kent\n> it would appear that ~/.bibletime/cache/KJVD was generated at a past time, and generated badly ( back when my indexer was broken  ) 
04:02:43 <kent\n> and nothing has invalidated that cache 
04:03:14 <kent\n> and even though I've deleted the dictionaries/lexicons/everything on the sword side, its still there.
04:03:32 <jotik> the BibleTime cache?
04:03:36 <kent\n> yeah.
04:04:09 <kent\n> rm ~/.bibletime/cache/KJVD  # pain goes away 
04:04:46 <jotik> _mg_: Are you familiar with how BibleTime handles caches for modules?
04:04:49 <kent\n> this behaviour also indicates to me if a cached entity is updated to contain more keys, that the cache wont be updated 
04:05:19 <jotik> kent\n: it appears so.
04:06:01 <kent\n> ( this explains no matter how much I changed/replaced the underlying data by regenerating it, nothing happened ) 
04:06:30 <jotik> So hopefully you could work around this for the time being?
04:07:17 <kent\n> yep :) 
04:07:36 <kent\n> but I'd imagine, there are others like myself who've needlessly suffered :)
04:08:04 <jotik> I know the feeling.
04:08:25 <jotik> Perhaps its because we both use Gentoo. :D
04:09:08 <kent\n> yeah, "oh, its a bug, thats ok, I'm on testing anyway, I expect things to be broken" 
04:09:20 <kent\n> only 3 releases later do you go "ok, something is wrong" 
04:10:40 <jotik> iTwinkle: tell _mg_ Perhaps we should have some kind of feature for regenerating some caches or something in case they are faulty as described by kent\n (read log).
04:10:40 <iTwinkle> jotik: yessir
04:13:10 <jotik> kent\n: thanks for reporting this.
04:13:48 <kent\n> strangely, I could have worked it out on my own, but somehow it didn't work till I had somebody to bounce ideas off.
04:14:33 <jotik> If you have the time could you please file a bug report at http://bit.ly/BT-Bugs about this. We would really appreciate it.
04:15:08 <jotik> I really have to get back to doing my job right now.
04:16:45 <jotik> http://sourceforge.net/tracker/?func=add&group_id=954&atid=100954 would be a more correct link to filing a bug.