Hi,
On Thu, Sep 25, 2014 at 10:18:24AM +0200, Andreas Florath wrote:
> Start-Date: 2014-09-23 07:07:59
> Commandline: apt-get upgrade
> Upgrade: libkrossui4:amd64 (4.14.0-1, 4.14.1-1), libmimic0:amd64
> (1.0.4-2.1+b1, 1.0.4-2.2), libkde3support4:amd64 (4.14.0-1, 4.14.1-1),
> telepathy-haze:amd6
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello!
Attached the list of packages which were updated two days ago.
Kind regards
Andre
=
Start-Date: 2014-09-23 07:07:59
Commandline: apt-get upgrade
Upgrade: libkrossui4:amd64 (4.14.0-1, 4.14.1-1), libmimic0:amd64 (1.0.4-2.1+b1,
1.0.4-2.
severity 762651 important
retitle 762651 libreoffice-core: SIGSEGV during start with (some9) recovery
items
thanks
> After some comparison and analyze, it looks that the cause is in the file
> 'registrymodifications.xcu'. When using the following content, soffice cores:
>
>
> http://openoffic
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello!
The problem exists also in versions 4.3.1-2 and 4.3.2~rc2.1.
Some more information:
when using a 'fresh' user configuration, soffice works.
After some comparison and analyze, it looks that the cause is in the file
'registrymodifications.xcu
-Ursprüngliche Nachricht-
Gesendet: Mittwoch, 24 September 2014 um 08:27:27 Uhr
Von: "Andreas Florath"
An: "Debian Bug Tracking System"
Betreff: Bug#762651: libreoffice-core: soffice cores during start with SIGSEGV
Package: libreoffice-core
Version: 1:4.3.1-1
Severity:
Package: libreoffice-core
Version: 1:4.3.1-1
Severity: grave
Justification: renders package unusable
Dear Maintainer,
soffice cores with SIGSEGV during start. (This happens since yesterday's
'apt-get upgrade'.)
$ rm core
$ soffice
$ file core
core: ELF 64-bit LSB core file x86-64, version 1 (SY
6 matches
Mail list logo
