Bug 352279 - Akonadi Kolab Resource crashes when cutting (and shortly thereafter pasting) an event
Summary: Akonadi Kolab Resource crashes when cutting (and shortly thereafter pasting) ...
Status: RESOLVED UNMAINTAINED
Alias: None
Product: Akonadi
Classification: Frameworks and Libraries
Component: Kolab Resource (show other bugs)
Version: 1.13.0
Platform: Mageia RPMs Linux
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-09-04 16:26 UTC by Matija Šuklje
Modified: 2018-02-01 09:51 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Matija Šuklje 2015-09-04 16:26:10 UTC
Application: akonadi_kolab_resource (4.14)
KDE Platform Version: 4.14.5
Qt Version: 4.8.6
Operating System: Linux 3.19.8-desktop-3.mga5 x86_64
Distribution: "Mageia 5"

-- Information about the crash:
- What I was doing when the application crashed:

1) created an event in a shared calendar on the Kolab server
2) figured out that it’s the wrong calendar
3) cut the event by means of keyboard shortcut Ctrl+X
4) pasted again by means of keyboard shortcut Ctrl+V

Results:
• crash of Kolab Resource

Expected results:
• no crash
• the event is pasted and asks in which calendar to be placed

The crash can be reproduced every time.

-- Backtrace:
Application: FSFE of type Kolab Groupware Server (akonadi_kolab_resource), signal: Aborted
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f57265437c0 (LWP 31848))]

Thread 3 (Thread 0x7f570efa9700 (LWP 31850)):
#0  0x00007f57213e3d1d in poll () at /lib64/libc.so.6
#1  0x00007f5720358eb4 in g_main_context_iterate.isra () at /lib64/libglib-2.0.so.0
#2  0x00007f5720358fbc in g_main_context_iteration () at /lib64/libglib-2.0.so.0
#3  0x00007f5725b7ce3e in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /lib64/libQtCore.so.4
#4  0x00007f5725b4e931 in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /lib64/libQtCore.so.4
#5  0x00007f5725b4ec45 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /lib64/libQtCore.so.4
#6  0x00007f5725a4c899 in QThread::exec() () at /lib64/libQtCore.so.4
#7  0x00007f5725a4efff in QThreadPrivate::start(void*) () at /lib64/libQtCore.so.4
#8  0x00007f5720a435bd in start_thread () at /lib64/libpthread.so.0
#9  0x00007f57213ef5cd in clone () at /lib64/libc.so.6

Thread 2 (Thread 0x7f570e7a8700 (LWP 31851)):
#0  0x00007f5720a48a28 in pthread_cond_timedwait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0
#1  0x00007f5725a4f4d2 in QWaitCondition::wait(QMutex*, unsigned long) () at /lib64/libQtCore.so.4
#2  0x00007f5725a42e65 in QThreadPoolThread::run() () at /lib64/libQtCore.so.4
#3  0x00007f5725a4efff in QThreadPrivate::start(void*) () at /lib64/libQtCore.so.4
#4  0x00007f5720a435bd in start_thread () at /lib64/libpthread.so.0
#5  0x00007f57213ef5cd in clone () at /lib64/libc.so.6

Thread 1 (Thread 0x7f57265437c0 (LWP 31848)):
[KCrash Handler]
#5  0x00007f572132b627 in raise () at /lib64/libc.so.6
#6  0x00007f572132cdba in abort () at /lib64/libc.so.6
#7  0x00007f5721922c0d in __gnu_cxx::__verbose_terminate_handler() () at /lib64/libstdc++.so.6
#8  0x00007f5721920c96 in __cxxabiv1::__terminate(void (*)()) () at /lib64/libstdc++.so.6
#9  0x00007f5721920ce1 in  () at /lib64/libstdc++.so.6
#10 0x00007f5721920f46 in __cxa_rethrow () at /lib64/libstdc++.so.6
#11 0x00007f5725b4ee5b in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /lib64/libQtCore.so.4
#12 0x00007f5725b53e59 in QCoreApplication::exec() () at /lib64/libQtCore.so.4
#13 0x00007f572604a45c in Akonadi::ResourceBase::init(Akonadi::ResourceBase*) () at /lib64/libakonadi-kde.so.4
#14 0x0000000000430fe8 in int Akonadi::ResourceBase::init<KolabResource>(int, char**) ()
#15 0x00007f5721317fd0 in __libc_start_main () at /lib64/libc.so.6
#16 0x000000000041b79e in _start ()

Pošlji na https://bugs.kde.org/

Reproducible: Always
Comment 1 Denis Kurz 2017-06-23 20:19:50 UTC
This bug has never been confirmed for a Kontact version that is based on KDE Frameworks, except possibly a Technology Preview version 5.0.x. Those versions differ significantly from the old 4.x series. Therefore, I plan to close it in around two or three months. In the meantime, it is set to WAITINGFORINFO to give reporters the opportunity to check if it is still valid. As soon as someone confirms it for a recent version (at least 5.1, ideally even more recent), I'll gladly reopen it.

Please understand that we lack the manpower to triage bugs reported for versions almost two years beyond their end of life.
Comment 2 Denis Kurz 2018-02-01 09:51:47 UTC
Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.1 aka 15.12; preferably much more recent), please open a new one unless it already exists. Thank you for all your input.