[REVIEW 3-6][REVIEW 3-6-0] fdo#51252 LO cannot start (reports runtime error with Visual C++ Runtime Library)

Stephan Bergmann <sbergman -AT- redhat.com>
Thu, 26 Jul 2012 13:28:22 +0200

See <https://bugs.freedesktop.org/show_bug.cgi?id=51252#c35>, comment 35to "LO cannot start (reports runtime error with Visual C++ RuntimeLibrary)," on why I think it would be a good idea to backport<http://cgit.freedesktop.org/libreoffice/core/commit/?id=5c47e5f63a79a9e72ec4a100786b1bbf65137ed4>"fdo#51252 Disable copying share/prereg/bundled to avoid startupcrashes" to libreoffice-3-6 and libreoffice-3-6-0 and do a LO 3.6.0 rc4.


Sorry for the trouble,
Stephan

Context

[REVIEW 3-6][REVIEW 3-6-0] fdo#51252 LO cannot start (reports runtime error with Visual C++ Runtime Library) · Stephan Bergmann
- Re: [REVIEW 3-6][REVIEW 3-6-0 1/3] fdo#51252 LO cannot start (reports runtime error with Visual C++ Runtime Library) · Caolán McNamara
  - Re: [REVIEW 3-6][REVIEW 3-6-0 1/3] fdo#51252 LO cannot start (reports runtime error with Visual C++ Runtime Library) · Stephan Bergmann
  - Re: [PUSHED 3-6][REVIEW 3-6-0 2/3] fdo#51252 LO cannot start (reports runtime error with Visual C++ Runtime Library) · Eike Rathke
    - Re: [PUSHED 3-6-0] fdo#51252 LO cannot start (reports runtime error with Visual C++ Runtime Library) · Petr Mladek
- Re: [REVIEW 3-6][REVIEW 3-6-0] fdo#51252 LO cannot start (reports runtime error with Visual C++ Runtime Library) · Fridrich Strba

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.