Application: kontact (5.8.2) Qt Version: 5.11.1 Frameworks Version: 5.48.0 Operating System: Linux 4.15.0-24-generic x86_64 Distribution: KDE neon User Edition 5.13 -- Information about the crash: - What I was doing when the application crashed: On KDE Neon, Plasma desktop was upgraded from 5.12 to 5.13 and I restarted the system. Simple tried to start Kontact application and it's every time crashes. The crash can be reproduced every time. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f310b224940 (LWP 6854))] Thread 2 (Thread 0x7f30dcc4b700 (LWP 6857)): #0 0x00007f3107c0474d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x00007f310196738c in g_main_context_poll (priority=2147483647, n_fds=1, fds=0x7f30d8003020, timeout=<optimized out>, context=0x7f30d8000990) at /build/glib2.0-prJhLS/glib2.0-2.48.2/./glib/gmain.c:4135 #2 g_main_context_iterate (context=context@entry=0x7f30d8000990, block=block@entry=1, dispatch=dispatch@entry=1, self=<optimized out>) at /build/glib2.0-prJhLS/glib2.0-2.48.2/./glib/gmain.c:3835 #3 0x00007f310196749c in g_main_context_iteration (context=0x7f30d8000990, may_block=may_block@entry=1) at /build/glib2.0-prJhLS/glib2.0-2.48.2/./glib/gmain.c:3901 #4 0x00007f31087320bb in QEventDispatcherGlib::processEvents (this=0x7f30d80008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #5 0x00007f31086d95ba in QEventLoop::exec (this=this@entry=0x7f30dcc4ac40, flags=..., flags@entry=...) at kernel/qeventloop.cpp:214 #6 0x00007f310850e5e4 in QThread::exec (this=<optimized out>) at thread/qthread.cpp:525 #7 0x00007f3106e77f35 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #8 0x00007f3108519727 in QThreadPrivate::start (arg=0x7f31070f0d60) at thread/qthread_unix.cpp:367 #9 0x00007f310395e6ba in start_thread (arg=0x7f30dcc4b700) at pthread_create.c:333 #10 0x00007f3107c1041d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 1 (Thread 0x7f310b224940 (LWP 6854)): [KCrash Handler] #6 0x00007f310acb2c20 in KontactInterface::PimUniqueApplication::staticMetaObject () from /usr/lib/x86_64-linux-gnu/libKF5KontactInterface.so.5 #7 0x00007f310aaadd3d in KontactInterface::PimUniqueApplication::start (arguments=..., unique=unique@entry=true) at /workspace/build/src/pimuniqueapplication.cpp:135 #8 0x000000000040437b in main (argc=1, argv=0x7ffe00e3f848) at /workspace/build/src/main.cpp:216 Reported using DrKonqi
Created attachment 114030 [details] New crash information added by DrKonqi kontact (5.8.2) using Qt 5.11.1 - What I was doing when the application crashed: When I try to start Kontact it crashes immediatly. No startscreen or something else is seen. - Custom settings of the application: the application starts automatically when I boot KDE Neon -- Backtrace (Reduced): #6 0x00007f71acb5ec20 in KontactInterface::PimUniqueApplication::staticMetaObject () from /usr/lib/x86_64-linux-gnu/libKF5KontactInterface.so.5 #7 0x00007f71ac959d3d in KontactInterface::PimUniqueApplication::start (arguments=..., unique=unique@entry=true) at /workspace/build/src/pimuniqueapplication.cpp:135 #8 0x000000000040437b in main (argc=1, argv=0x7ffc6dd0dbf8) at /workspace/build/src/main.cpp:216
Confirmed this bug on a fresh install of KDE Neon. The bug appears after upgrade through apt-get alone, could not locate the precise package that provokes the problem.
*** Bug 396698 has been marked as a duplicate of this bug. ***
*** Bug 396686 has been marked as a duplicate of this bug. ***
Probably caused by the 18.08 branching, needing a recompile of all KDEPIM packages.
(In reply to Christoph Feck from comment #5) > Probably caused by the 18.08 branching, needing a recompile of all KDEPIM > packages. pulling in todays updates fixed it for me, thanks
Created attachment 114043 [details] New crash information added by DrKonqi kmail (5.8.2) using Qt 5.11.1 I have the same propblem since upgrading KDE Neon an hour ago. No further updates are offered – so if “todays updates” mentioned by tomas nackaerts in https://bugs.kde.org/show_bug.cgi?id=396694#c6 are already generally available, then they do NOT solve the problem for everyone. -- Backtrace (Reduced): #7 0x00007f15de4fad3d in KontactInterface::PimUniqueApplication::start (arguments=..., unique=unique@entry=true) at /workspace/build/src/pimuniqueapplication.cpp:135 #8 0x00000000004035fc in main (argc=1, argv=0x7ffd70150678) at /workspace/build/src/main.cpp:128
Still not fixed.
Created attachment 114044 [details] New crash information added by DrKonqi kmail (5.8.2) using Qt 5.11.1 - What I was doing when the application crashed: Launching KMail after KDE Neon upgrade from 5.13.2 to 5.13.3 -- Backtrace (Reduced): #7 0x00007f19e30dfd3d in KontactInterface::PimUniqueApplication::start (arguments=..., unique=unique@entry=true) at /workspace/build/src/pimuniqueapplication.cpp:135 #8 0x00000000004035fc in main (argc=1, argv=0x7fff60769b68) at /workspace/build/src/main.cpp:128
*** Bug 396720 has been marked as a duplicate of this bug. ***
*** Bug 396722 has been marked as a duplicate of this bug. ***
*** Bug 396700 has been marked as a duplicate of this bug. ***
*** Bug 396724 has been marked as a duplicate of this bug. ***
I have the same problem, but i not upgrade to plasma 5.13.3 yet. I'm just install kmail from apt and then crashes when it's start. here is backtrace from gdb. KDE Plasma Version: 5.13.2 KDE Frameworks Version: 5.47.0 Qt Version: 5.11.1 OS: KDE Neon #0 0x0000000000000001 in ?? () #1 0x00007ffff7bd0d3d in KontactInterface::PimUniqueApplication::start(QStringList const&, bool) () from /usr/lib/x86_64-linux-gnu/libKF5KontactInterface.so.5 #2 0x00000000004035fc in ?? () #3 0x00007ffff4efc830 in __libc_start_main (main=0x402720, argc=0x1, argv=0x7fffffffdb38, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7fffffffdb28) at ../csu/libc-start.c:291 #4 0x0000000000403829 in _start ()
*** Bug 396728 has been marked as a duplicate of this bug. ***
Todays update solved this bug for me. Thank you for the fast response! Well done ;)
Hi yc-153434@hs-weingarten.de ! Which update you mind?
I did an update at 4pm. There was an update of the PIM suite
I have nothing to update for now but I can not run the korganizer from this same reason as here. Maybe I haven't lasted package in repo yet...
Try in terminal: sudo pkcon refresh sudo pkcon update
Sadly pkcon return nothing to do, I will be waiting. Some workaround for people which using the korganizer in this case: install the kontact application. When you will run kontact you have your organizer. In case run korganizer independently you will crash error as before.
I now saw another update. This fixed the problem for me.
Which distro you are using?
KDE Neon User Edition
After the recent updates the problem is partially fixed for me. KOrganizer won't start directly (see duplicate #396700). But the workaround via Kontact, proposed by Paweł Krzak, works. Distro: KDE Neon User Edition
sorry looks like the friday snapshot got a half-done KDE PIM. Saturday's got it complete apart from korganizer. Today's snapshot should be fixed. apologies for the hassle.
Now it's fixed! Thanks!