Indexing for Search not working?

I've been using v3.4 of LibreOffice. I updated to v3.6.2.2 and now the
contents of documents are not indexed for search.

I'm using 64-bit Windows 7. The extension odt is checked for the indexing
option. I also checked the "Index Properties and File Contents" in the
Indexing Option in Windows.

When I search, doc files and ppt files appears in the result but not odt and
odp.

Is it just me or is this known bug? The same thing happened when I updated
to v3.5 so I went back to v3.4 for the searchability. Is there any
workaround?

Tea

Same here on Mac, OS 10.5.8, Libreoffice 3.6.2.2. Spotlight does not find
odt-documents. Looking into console, I find the message

"15.10.12 15:47:43 mdworker[116] Cannot find function pointer
MetadataImporterPluginFactory for factory
A3FCC88D-B9A6-4364-8B93-92123C8A2D18 in CFBundle/CFPlugIn 0x1664c0
</Applications/LibreOffice.app/Contents/Library/Spotlight/OOoSpotlightImporter.mdimporter>
(bundle, loaded)
15.10.12 15:47:43 mdworker[116] (Warning) ImportPluginLoading: Plugin at url
'Spotlight/OOoSpotlightImporter.mdimporter/ --
/Applications/LibreOffice.app/Contents/Library/' cannot be loaded. It will
not be used."

My fault or a bug in Libreoffice?

Thanks, gruesser

I'm going back to v3.4 for now. I hope this issue is going to be solved
quickly.

Tea

Hi :slight_smile:
Have you tried renaming your User Profile to see if that fixes it?
http://wiki.documentfoundation.org/Documentation/UserProfile

Which 3.4.x are you returning to?  Does the indexing work there?  Have you been able to post a bug-report about the issue?  I think they want to know roughly which version is the earliest one where the problem appeared. 
http://wiki.documentfoundation.org/Bug_Report
Regards from
Tom :slight_smile:

Hi Tom. Thank you for your suggestion. I went back to the v3.4.6 that I have
the installer. I am rebuilding the search index and try to see if v3.4.6
allows me to search indexed contents again. The indexing worked there, so
I'm hoping this will work.

If not, I will try changing the profile. I tried to find similar bug report
but couldn't find one. Is your indexing working?

Tea

It says ODF type 1.2 Extended in v3.4.6. Does it make sense?
If indexing is working in the LO v3.4.6 with ODF 1.2, should I try insalling
v3.6 then try to change the ODF to 1.1?

This is the reason I have no intention of updating from 3.4 until
ALL these bugs are worked out -
            then I'll update to 3.5; yes, I'll always be behind BUT I don't
have the hassles of these bugs :wink:

I've been using v3.4 of LibreOffice. I updated to v3.6.2.2 and now the

good thinking :slight_smile:

           actually who cares which version you're using as long as it
works well for you.

I'm going back to v3.4 for now. I hope this issue is going to be solved

Hi :slight_smile:
There are always bugs in any software.  Of course there are less new bugs in older versions but then you start running into theoretical security issues.  The 3.5.0 dealt with one of those so it might not be best to stay with 3.4.x forever.  On the other hand there are almost no reports of the theoretical risk actually getting targeted. 
Regards from
Tom :slight_smile:

I thought I reported the bug. It gave me "Bug 56035". when I filed report.
However, after I can't find my bug report any more. I don't know why... At
least I attempted to file.

Tea

Update: I think I found it.
https://bugs.freedesktop.org/show_bug.cgi?id=56035

Thank you very much and hope it will be fixed soon.

BRAVO Anne-Ology!!
Exactly that message - only in other words -- I have repeatedly tried to tell to the LibO-experts (devs) since January:
they must take a brake in developing and take a certain version (e.g. 3.4.xx) and make every module of the suite - Base included - absolutely free of bugs and inconsistencies both in programming and the instructions and especially the LibO-Help.
Every feature shall have a clear explanation and a detailed guiding how-to in the LibO-Help -- easily understood by any average non-expert user.

Obviously I've been crying in vain because I have not noticed any (re)actions -- the developing of new versions is continuing with the result of an increasing activity on this list.

I have LibO3.4.6 installed (Win7) but avoid using it (Calc, Base) because I have better to do than struggle with problems.
I would like to know which LibO version for the time being can be considered as the most reliable and productive -- especially regarding Base.
It would also be interesting to see an (valid) evaluation of that reliable usability on a scale 1-10 for each of the the different modules of versions 3.4.xx, 3.5.xx.x, 3.6.xx.x
Pertti Rönnberg

I cannot agree more.
I started with 3.5.4 a few month ago and saw some problems disappearing in 3.5.5 and 3.5.6. Currently I am hesitating to upgrade to 3.5.7.
I hope the dev-team listens to Pertti's words.

Hi :slight_smile:
Ok, so we should just get rid of or push away any devs that are interested in adding new functionality.  There are a lot of other projects they could go to for that sort of excitement.  We could build-up a strong core of devs that focus only on fixing things that already exist.  Get rid of any that have too much imagination.

We could watch and wait while other Office Suites develop new functionality and then try to catch up and try to write code to do the same thing but without the code looking too similar.  They would set the format and the way things should look and we just try to copy exactly without looking too similar.

Let our competitors do the driving and just gradually fall further and further back?!!??

Alternatively we could try to help all our devs by test driving the new branch asap.  Seek out 'bugs' or anything vaguely wonky.  Post bug reports.  Find work-arounds.  Fall back on the more stable release from the older branch (we can have 2 versions installed at once right?) for when we need to meet deadlines.

The question is do we want LO to fall behind and become increasingly irrelevant or are we ready to help push out into the world?  Do we want LO to keep going in the future or are we happy to be forced into switching back to MSO one day? 
Regards from
Tom :slight_smile:

It's not falling behind in development. It's about stability and
    this means productivity.It's like placing an always stronger engine in an F1 car without
    considering to get the power on the road. What means the best engine
    when the suspension is not strong enough. With other words I feel I
    spent a lot of time in this forum which are reducing my productivity
    time. I don't mind being in the forum because there are nice people
    here and I like to read the various opinions.)I don't know how many devs are working on new functions and how many
    on bug fixes. It would just be good to change for a certain time the
    ratio of devs working on bugs.Do we want it or not we are compared against MSO. But in MSO we
    don't know the bugs.... MS neglects them.On 17.10.2012 17:07, Tom Davies wrote:
Hi :)Ok, so we should just get rid of or push away any devs
              that are interested in adding new functionality.There
              are a lot of other projects they could go to for that sort
              of excitement.We could build-up a strong core of devs
              that focus only on fixing things that already exist.Get
              rid of any that have too much imagination.We could watch and wait while other Office Suites develop
              new functionality and then try to catch up and try to
              write code to do the same thing but without the code
              looking too similar.They would set the format and the
              way things should look and we just try to copy exactly
              without looking too similar.Let our competitors do the driving and just gradually fall
              further and further back?!!??Alternatively we could try to help all our devs by test
              driving the new branch asap.Seek out 'bugs' or anything
              vaguely wonky.Post bug reports.Find work-arounds.Fall back on the more stable release from the older branch
              (we can have 2 versions installed at once right?) for when
              we need to meet deadlines.The question is do we want LO to fall behind and become
              increasingly irrelevant or are we ready to help push out
              into the world?Do we want LO to keep going in the future
              or are we happy to be forced into switching back to MSO
              one day?Regards fromTom :)--- OnWed, 17/10/12, Dr. R. O Stapfreinhold@stapf-online.comwrote:From: Dr. R. O Stapfreinhold@stapf-online.comSubject: Re: [libreoffice-users] Indexing for Search not
                working?To:users@global.libreoffice.orgDate: Wednesday, 17 October, 2012, 8:44On 17.10.2012 16:07, Pertti Rnnberg wrote:BRAVO Anne-Ology!!Exactly that message - only in other words -- I
                  have repeatedly tried to tell to the LibO-experts
                  (devs) since January:they must take a brake in developing and take a
                  certain version (e.g. 3.4.xx) and make every module of
                  the suite - Base included - absolutely free of bugs
                  and inconsistencies both in programming and the
                  instructions and especially the LibO-Help.Every feature shall have a clear explanation and
                  a detailed guiding how-to in the LibO-Help -- easily
                  understood by any average non-expert user.I cannot agree more.I started with 3.5.4 a few month ago and saw some
                  problems disappearing in3.5.5 and 3.5.6. Currently I
                  am hesitating to upgrade to 3.5.7.I hope the dev-team listens to Pertti's words.-- For unsubscribe instructions e-mail to: users+help@global.libreoffice.orgProblems?http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/Posting guidelines + more:http://wiki.documentfoundation.org/NetiquetteList archive:http://listarchives.libreoffice.org/global/users/All messages sent to this list will be publicly
                  archived and cannot be deleted

Hi :slight_smile:
I think we both want the same thing.  The question is how to get it.

1.  How to encourage new devs to join?  At the moment we show LO as an exciting projects for devs to get involved with and quickly see the results of their work getting out there into the real world.  As a result they are likely to get into fixing any unexpected problems or side-issues that might have cropped up.

2.  We need a "stable branch" where new stuff never gets added, just fixes back-ported from the newer, more exciting branch.

That is pretty much what we have already.  By the time the newer branch reaches around .4 then it's usually stable enough for everyone = about as stable as the .6 or .7 of the older branch but with better compatibility with non-native formats and some interesting things.

If some of us helped the devs more by posting bug-reports earlier then we might be able to help them push that stability in earlier.  We might start finding the 3. or even the .2 starts to be the one stable enough to migrate our colleagues and co-workers to as well as ourselves instead of having to wait for the .4.

It's on us more than the devs.  They are working hard and need our support rather than our criticism.  Do we want to push devs away unless they only get involved with boring dry stuff and no reward, no chance of showing off prowess, no chance of getting recognition out there?

I like people in here too.  I also enjoy arguing with people i like and respect that have a good point of view and a good way of looking at the world.  I usually take good points from here and then argue in favour of them on the marketing list because you have very valid points here.

We do need an LTS because these frequent upgrades and uncertainty are just not possible when you have more than a handful of computers to maintain or have limited download, or ....  Well, tons of valid reasons 
Regards from
Tom :slight_smile:

As a user (and by no means a developer), I'm constantly doing battle with the features vs. stability issue. I agree that new features need to be pursued to keep LO competitive. I also agree, however, that LO is full-featured enough that users are justified in expecting a stable program. There's nothing more frustrating than finding that the program just won't complete a task because of some bug.

As writing is my thing, I currently have five word processors installed on my Windows computer. I use them all at various times due to inconsistencies in either features or stability. I would like to simply commit to one program, but no matter which direction I go, I run into either a lacking but necessary feature or an unstable feature that simply doesn't work. For example, I use the following:

Atlantis (shareware, $35.00 registration) -- Extremely stable, but lacking features I often need (PDF export, tables, etc.). However, it has a very clean interface and the best e-book exportation that I've seen anywhere. The Atlantis folks are slow to publish upgrades, but when they do, they are relatively bug-free and accompanied by very detailed instructions on how to use new features.

Microsoft Word Starter -- Came with my laptop OS. I only use it when I need 100% Word compatibility.

Lotus Symphony -- Lacking in many, many features, but one I really like is the tabbed interface, a feature I wish LO would adopt.

LibreOffice 3.5.6.2 -- Overall, it works well, but I discovered this morning that, if I try to open an RTF file, every line in the entire file is centered and I lose all paragraph breaks. I end up with one, centered paragraph. When I open the same file in Apache OpenOffice or Lotus Symphony, it loads perfectly. I have no idea if this is a bug in LO or a setting issue or a problem with my computer. But, until I figure it out, I need to use another option when loading RTF files. This type of continuously having to chase down solutions to weird problems is frustrating. Thus user list makes life a lot easier.

Apache OpenOffice 3.4.1 -- I've noticed that AOO seems to hyphenate my English(USA) words at the wrong locations. I haven't had that problem with LO, but I don't know why. So, if I want to open an RTF file, I need to use AOO, but if I want to edit that file and hyphenate it, I need to load it into LO, after first saving it in AOO to ODT format.

This is the type of juggling act we users end up doing as we bounce from one program to the next trying to find the features we need and avoid the bugs that bog us down.

I don't envy open source developers. They do a seemingly thankless job, and I often wonder what keeps them motivated, other than an apparent shared disdain for MS. However, I deeply appreciate all they do in their attempt to make LO the best program available, in terms of both features AND stability.

Virgil

Hi :) 
Board-discuss might be a better place to post this sort of thing.  Copy&paste is good.

Ubuntu are extending their LTS (Long Term Support) from 2 years to 4 or even 5.  Apparently it's impossible to set-up LO for even 1 years worth.

The Rtf issues sounds weird.  Have you tried renaming your User Profile?
http://wiki.documentfoundation.org/Documentation/UserProfile
Regards from
Tom :slight_smile:

Thanks for the "Board-discuss" tip. I'll check it out. Actually, I was just responding to your earlier post about features vs. stability. Didn't mean to abuse the user list.

I just tried renaming the user profile. It didn't fix the RTF issue. I checked Bugzilla and found a whole host of RTF import bugs reported, so my guess is that there is some issue there. It's not a huge issue for me, so I'm not going to worry too much about it.

Virgil

Hi :slight_smile:
You didn't abuse or misuse the Users List.  One of the functions of the list is to signpost people to where they might get better answers.  Plus, it does follow on nicely although i think we might have drifted off-topic over the past few posts as we do.

Sorry about the Rtf issue.  MS created it to ensure compatibility between all different programs on any platform.  The key words there are the 1st 3. 
Regards from
Tom :slight_smile:

Okay, the RTF issue just got weirder.

My original RTF file was created in Atlantis, which uses RTF as its default format. Again, the file loaded properly in AOO and Lotus Symphony, but not LO.

On a lark, I loaded the file into Word, made a change, and then resaved it. In that way, Word replaced all the Atlantis RTF code with its own. (Every word processor saves RTF files somewhat differently depending on its own unique sent of features.) I then loaded the file into LO and it looked perfect.

So, there is some communication gap between the way Atlantis saves RTF files and the way LO reads them.

Curiouser and curiouser.

Virgil