Your message dated Thu, 11 Oct 2018 22:07:23 +0200
with message-id <2040658.f2F7QRe4l5@merkaba>
and subject line Re: Bug#910800: kontact: Kontact, Kmail, Knotes and Korganizer
crash
has caused the Debian Bug report #910800,
regarding kontact: Kontact, Kmail, Knotes and Korganizer crash
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
910800: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=910800
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: kontact
Version: 4:18.08.1-1
Severity: important
The programs Kontact, Kmail, Knotes and Korganizer crash due to a
segmentation
fault everytime I try to start them.
This crash happen since a couple of days ago, after an upgrade. I am
currently
running debian buster (testing), with kontact version 5.7.3.
I have tried to find relevant bug reports, finding the following:
KDE bug report on Korganizer crash on startup:
https://bugs.kde.org/show_bug.cgi?id=396694
Knotes bug report at KDE: https://bugs.kde.org/show_bug.cgi?id=399551
>From them I see that upgrading kontact to newer version may solve the
problem.
Thus, I have installed kontact from sid. This fixed the problem, although I
would like to come back to buster version once the bug is fixed.
Bellow, I paste the crash report with debug flags, in case it may be
helpful:
Application: kontact (5.7.3)
Qt Version: 5.11.1
Frameworks Version: 5.49.0
Operating System: Linux 4.18.0-1-amd64 x86_64
Distribution: Debian GNU/Linux testing (buster)
-- Information about the crash:
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 0x7ffbc67e7d80 (LWP 9666))]
Thread 4 (Thread 0x7ffbbca74700 (LWP 9669)):
#0 0x00007ffbdf777204 in __GI___libc_read (fd=8, buf=0x7ffbbca735d0,
nbytes=16) at ../sysdeps/unix/sysv/linux/read.c:27
#1 0x00007ffbdcf55180 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2 0x00007ffbdcf0f91f in g_main_context_check () at /usr/lib/x86_64-linux-
gnu/libglib-2.0.so.0
#3 0x00007ffbdcf0fdf0 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4 0x00007ffbdcf0ff6c in g_main_context_iteration () at
/usr/lib/x86_64-linux-
gnu/libglib-2.0.so.0
#5 0x00007ffbdfca724b in
QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>)
()
at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6 0x00007ffbdfc5425b in
QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7 0x00007ffbdfaa3176 in QThread::exec() () at /usr/lib/x86_64-linux-
gnu/libQt5Core.so.5
#8 0x00007ffbdefcf545 in () at /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5
#9 0x00007ffbdfaacd47 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#10 0x00007ffbde23cf2a in start_thread (arg=0x7ffbbca74700) at
pthread_create.c:463
#11 0x00007ffbdf785edf in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95
Thread 3 (Thread 0x7ffbbe74d700 (LWP 9668)):
#0 0x00007ffbde242e6c in futex_wait_cancelable (private=<optimized out>,
expected=0, futex_word=0x55c50414f2c0) at ../sysdeps/unix/sysv/linux/futex-
internal.h:88
#1 0x00007ffbde242e6c in __pthread_cond_wait_common (abstime=0x0,
mutex=0x55c50414f270, cond=0x55c50414f298) at pthread_cond_wait.c:502
#2 0x00007ffbde242e6c in __pthread_cond_wait (cond=0x55c50414f298,
mutex=0x55c50414f270) at pthread_cond_wait.c:655
#3 0x00007ffbbee21d8b in () at /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
#4 0x00007ffbbee21ab7 in () at /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
#5 0x00007ffbde23cf2a in start_thread (arg=0x7ffbbe74d700) at
pthread_create.c:463
#6 0x00007ffbdf785edf in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95
Thread 2 (Thread 0x7ffbc57e7700 (LWP 9667)):
#0 0x00007ffbdf77b739 in __GI___poll (fds=0x7ffbc57e6738, nfds=1,
timeout=-1)
at ../sysdeps/unix/sysv/linux/poll.c:29
#1 0x00007ffbde081cf7 in () at /usr/lib/x86_64-linux-gnu/libxcb.so.1
#2 0x00007ffbde08390a in xcb_wait_for_event () at /usr/lib/x86_64-linux-
gnu/libxcb.so.1
#3 0x00007ffbc64e26d9 in () at /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
#4 0x00007ffbdfaacd47 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5 0x00007ffbde23cf2a in start_thread (arg=0x7ffbc57e7700) at
pthread_create.c:463
#6 0x00007ffbdf785edf in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95
Thread 1 (Thread 0x7ffbc67e7d80 (LWP 9666)):
[KCrash Handler]
#6 0x00007ffbe0de1c20 in
KontactInterface::PimUniqueApplication::staticMetaObject () at
/usr/lib/x86_64-linux-gnu/libKF5KontactInterface.so.5
#7 0x00007ffbe0ddaf9d in
KontactInterface::PimUniqueApplication::start(QStringList const&, bool) ()
at
/usr/lib/x86_64-linux-gnu/libKF5KontactInterface.so.5
#8 0x000055c5038423e9 in main(int, char**) (argc=<optimized out>,
argv=<optimized out>) at ./src/main.cpp:212
-- System Information:
Debian Release: buster/sid
APT prefers testing-debug
APT policy: (500, 'testing-debug'), (500, 'unstable'), (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 4.18.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=es_ES.UTF-8, LC_CTYPE=es_ES.UTF-8 (charmap=UTF-8), LANGUAGE=
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages kontact depends on:
ii kdepim-runtime 4:17.12.3-2
ii kio 5.49.0-1
ii libc6 2.27-6
ii libgcc1 1:8.2.0-7
ii libkf5completion5 5.49.0-1
ii libkf5configcore5 5.49.0-1
ii libkf5configgui5 5.49.0-1
ii libkf5configwidgets5 5.49.0-1
ii libkf5coreaddons5 5.49.0-1
ii libkf5crash5 5.49.0-1
ii libkf5grantleetheme-plugins 18.08.1-1
ii libkf5grantleetheme5 18.08.1-1
ii libkf5i18n5 5.49.0-1
ii libkf5iconthemes5 5.49.0-1
ii libkf5kcmutils5 5.49.0-1
ii libkf5kdepimdbusinterfaces5 4:17.12.3-1
ii libkf5kiowidgets5 5.49.0-1
ii libkf5kontactinterface5 18.08.1-1
ii libkf5libkdepim-plugins 4:17.12.3-1
ii libkf5libkdepim5 4:17.12.3-1
ii libkf5parts5 5.49.0-1
ii libkf5service-bin 5.49.0-1
ii libkf5service5 5.49.0-1
ii libkf5widgetsaddons5 5.49.0-1
ii libkf5windowsystem5 5.49.0-1
ii libkf5xmlgui5 5.49.0-1
ii libqt5core5a 5.11.1+dfsg-9
ii libqt5dbus5 5.11.1+dfsg-9
ii libqt5gui5 5.11.1+dfsg-9
ii libqt5webengine5 5.11.1+dfsg-5
ii libqt5webenginewidgets5 5.11.1+dfsg-5
ii libqt5widgets5 5.11.1+dfsg-9
ii libstdc++6 8.2.0-7
Versions of packages kontact recommends:
ii accountwizard 4:17.12.3-1
ii akregator 4:17.12.3-1
ii kaddressbook 4:17.12.3-1
ii kmail 4:17.12.3-1
ii knotes 4:17.12.3-1
ii korganizer 4:17.12.3-2
Versions of packages kontact suggests:
pn gnokii <none>
-- no debconf information
--
Antonio Tenorio Fornés
atenor.io
--- End Message ---
--- Begin Message ---
Hello Antonio,
Antonio Tenorio Fornés - 11.10.18, 14:52:
> Package: kontact
> Version: 4:18.08.1-1
> Severity: important
>
> The programs Kontact, Kmail, Knotes and Korganizer crash due to a
> segmentation
> fault everytime I try to start them.
This is an temporary issue with an incomplete transition of KDEPIM from
Sid to Testing. You had a mixture of KDEPIM/Akonadi 17.12 and 18.08.
Thus closing.
[…]
> Thus, I have installed kontact from sid. This fixed the problem,
> although I would like to come back to buster version once the bug is
> fixed.
In case you use KDEPIM and Plasma software from testing, please
subscribe to debian-kde. It had a warning about this.
Also please carefully check whether an update contains all necessary
packages. Sandro, who packaged and uploaded KDEPIM 18.08, did what he
could to avoid an incomplete transition, yet it did not work out, the
automatic logic for the migration failed. See this comment from him:
Re: KDEPIM broken after upgrades in Buster [Was: Re: KDEPIM 18.08 broken
icons in Kontact
https://lists.debian.org/debian-kde/2018/10/msg00031.html
Please refrain from reporting transition related bugs. It creates
additional work for the already small Debian Qt/KDE team. Only report if
after a longer time the issue still remains, but preferably ask on
debian-kde mailing list first.
Thanks,
--
Martin
--- End Message ---
