Date: prev next · Thread: first prev next last
2015 Archives by date, by thread · List index

Hi :)
If something is working well for you it is difficult NOT to recommend it to

However it is better to use more current versions and try to stick to
either the current "Fresh" or "Still" branches.  There seems to be about 1
genuine security issue per year (rather than the handful per month of the
main competition's suite).  Although these are usually dealt with before
becoming rampant out in the wild it is still probably better to avoid
potentially putting yourself at risk.  "Security through obscurity" is only
kinda good when it's one of many strands keeping you safe.

A quick google search for "microsoft visual c runtime library runtime
error. 6025 pure virtual function call." gave me a couple of links on the website and a few others.  Interesting to see at least a
couple refer to it potentially being due to missing libraries and a quick
glimpse suggested the processes for fixing the problem looked very
similar.  I'd take each suggestion "with a pinch of salt" but they seem to
build-up to, potentially, a better understanding.

Errr, apparently "6025" was a 'name' of a member of the band "The Dead
Kennedies" and the number appears to have been used as a reference number
for quite a lot of very dissimilar things too.
Regards from
Tom :)

On 4 August 2015 at 20:00, anne-ology <> wrote:

       you're right; I was wrong.

       These updates are quite necessary if one is on-line with the

From: V Stuart Foote <>
Date: Mon, Aug 3, 2015 at 7:18 PM
Subject: [libreoffice-users] Re: probllem about microsoft visual c


anne-ology wrote
If LO 3.4 is still available, then I would suggest you download that
one -
            it works error-free.

As do virtually all "releases" of LibreOffice.  And, if you must "revert"
the archival builds for the project releases are here:

Not trying to be harsh here, but, even the last release from that
series is rather outdated. Frankly even an OpenOffice 4.1 release would be
more appropriate than advising folks to use the LibreOffice 3.4  release
builds. Please stop continuing to suggest them as viable for users.

Regards OPs issue with Visual C runtimes, as long as the x86  MS Visual
Studio C++2010  versions (msvcr100.dll)
<>   are
installed for the 4.3 or 4.4 releases--the should provide good

But if moving to a 4.4 install (via upgrade, or clean install) it would be
wise to clear your user profile.  That has resolved similar C++ runtime
issues for folks.


View this message in context:
Sent from the Users mailing list archive at

To unsubscribe e-mail to:
Posting guidelines + more:
List archive:
All messages sent to this list will be publicly archived and cannot be

To unsubscribe e-mail to:
Posting guidelines + more:
List archive:
All messages sent to this list will be publicly archived and cannot be deleted


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.