kdeinit5 crashed with SIGABRT in QMessageLogger::fatal()

[mrl586]

When I starting kdenlive, kdeinit5 crashed.

tux@Z50:~$ lsb_release -rd
Description: Ubuntu 15.04
Release: 15.04
tux@Z50:~$ apt-cache policy kinit
kinit:
  Asennettu: 5.9.0-0ubuntu1
  Ehdokas: 5.9.0-0ubuntu1
  Versiotaulukko:
 *** 5.9.0-0ubuntu1 0
        500 http://archive.ubuntu.com/ubuntu/ vivid/universe amd64 Packages
        100 /var/lib/dpkg/status

ProblemType: Crash
DistroRelease: Ubuntu 15.04
Package: kinit 5.9.0-0ubuntu1
ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3
Uname: Linux 3.19.0-16-generic x86_64
NonfreeKernelModules: fglrx
ApportVersion: 2.17.2-0ubuntu1
Architecture: amd64
CrashCounter: 1
Date: Wed May 6 05:52:37 2015
ExecutablePath: /usr/bin/kdeinit5
InstallationDate: Installed on 2015-05-05 (3 days ago)
InstallationMedia: Kubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
ProcCmdline: klauncher\ [kdeinit5]\ --fd=8
ProcEnviron:

Signal: 6
SourcePackage: kinit
StacktraceTop:
 QMessageLogger::fatal(char const*, ...) const () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
 ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/platforms/libqxcb.so
 ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/platforms/libqxcb.so
 ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/platforms/libqxcb.so
 QPlatformIntegrationFactory::create(QString const&, QStringList const&, int&, char**, QString const&) () from /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5
Title: kdeinit5 crashed with SIGABRT in QMessageLogger::fatal()
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 #1371864, 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.