soffice.bin crashed with SIGSEGV in SfxBaseModel::Notify()

[cedric]

was working on creating a document with mail merge.
2 documents opened, when resizing windows, application crashed

Description: Ubuntu Utopic Unicorn (development branch)
Release: 14.10

libreoffice:
  Installed: (none)
  Candidate: 1:4.3.1~rc2-0ubuntu1
  Version table:
     1:4.3.1~rc2-0ubuntu1 0
        500 http://ch.archive.ubuntu.com/ubuntu/ utopic/universe amd64 Packages

ProblemType: Crash
DistroRelease: Ubuntu 14.10
Package: libreoffice-core 1:4.3.1~rc2-0ubuntu1
ProcVersionSignature: Ubuntu 3.16.0-14.20-generic 3.16.2
Uname: Linux 3.16.0-14-generic x86_64
ApportVersion: 2.14.7-0ubuntu2
Architecture: amd64
CurrentDesktop: KDE
Date: Wed Sep 17 12:48:41 2014
ExecutablePath: /usr/lib/libreoffice/program/soffice.bin
InstallationDate: Installed on 2014-09-16 (1 days ago)
InstallationMedia: Kubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140826.1)
ProcCmdline: /usr/lib/libreoffice/program/soffice.bin --writer file:///tmp/WG4211-UsingMailMerge.odt --splash-pipe=5
Signal: 11
SourcePackage: libreoffice
StacktraceTop:
 ?? () from /usr/lib/libreoffice/program/libsfxlo.so
 ?? () from /usr/lib/libreoffice/program/libsfxlo.so
 ?? () from /usr/lib/libreoffice/program/libsfxlo.so
 SfxBaseModel::Notify(SfxBroadcaster&, SfxHint const&) () from /usr/lib/libreoffice/program/libsfxlo.so
 SfxBroadcaster::Broadcast(SfxHint const&) () from /usr/lib/libreoffice/program/libsvllo.so
Title: soffice.bin crashed with SIGSEGV in SfxBaseModel::Notify()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

[Apport retracing service (apport)]

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1212033, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.