[kontact] [Bug 449872] Kontact crashed while trying to reply to email
https://bugs.kde.org/show_bug.cgi?id=449872
--- Comment #4 from Sven Eden ---
I have resolved my issue:
Nothing I found on the internet worked. Then I stumbled about a several year
old post, where someone on a Kubuntu system suggested to purge sonnet.
So I unmerged (deinstalled) kde-frameworks/sonnet-5.90.0 from my system.
As several other packages where linked against
/usr/lib64/libKF5SonnetCore.so.5.90.0 and /usr/lib64/libKF5SonnetUi.so.5.90.0,
the Gentoo build manager Portage kept those libraries nevertheless.
There is a special install target to rebuild those packages ("emerge
@preserved-rebuild"), which I ran.
It did not only re-install sonnet, but also rebuilt
kde-frameworks/ktextwidgets-5.90.0
kde-apps/kpimtextedit-21.12.2
kde-apps/kanagram-21.12.2
kde-plasma/kdeplasma-addons-5.24.0
kde-plasma/kmenuedit-5.24.0
kde-plasma/plasma-desktop-5.24.0
kde-apps/libksieve-21.12.2
kde-apps/messagelib-21.12.2
kde-apps/ktp-text-ui-21.12.2
kde-apps/parley-21.12.2
kde-frameworks/khtml-5.90.0
kde-frameworks/ktexteditor-5.90.0
and finally:
kde-apps/kmail-21.12.2
The next time I tried to start Kontact, it showed up, and opened dozens of
windows with an empty e-mail to the person I originally tried to reply to.
After I had closed (and discarded) all these windows, everything seemed to be
fine.
I am still testing, but it seems Kontact is back to normal.
--
You are receiving this mail because:
You are the assignee for the bug.
[kontact] [Bug 449872] Kontact crashed while trying to reply to email
https://bugs.kde.org/show_bug.cgi?id=449872 --- Comment #3 from Sven Eden --- I ran "akonadictl fsck" and it found some items to clean up and scheduled some re-indexing. When the indexing agent finished, another run of "akonadictl fsck" did not find any issues. Kontact/Kmail are still crashing when starting. Once thing I forgot to mention: The crash happens even before a window shows up. -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 449872] Kontact crashed while trying to reply to email
https://bugs.kde.org/show_bug.cgi?id=449872 --- Comment #2 from Sven Eden --- Interesting... Adams and my crash happened about around the same time, yesterday... Both go through (Adam) KMComposerWin::slotRecipientAdded(MessageComposer::RecipientLineNG*) (this=0x562d31d2fe70, line=) at kmail-21.12.2/src/editor/kmcomposerwin.cpp:3776 ( me ) KMComposerWin::slotRecipientAdded(MessageComposer::RecipientLineNG*) (this=0x556321561410, line=) at kmail-21.12.2/src/editor/kmcomposerwin.cpp:3776 Then (Adam) QGpgME::QGpgMEAddUserIDJob::start(GpgME::Key const&, QString const&, QString const&, QString const&) (this=0x562d32e9f830, key=..., name=..., email=..., comment=) at qt/src/qgpgmeadduseridjob.cpp:82 ( me )QGpgME::QGpgMEAddUserIDJob::start(GpgME::Key const&, QString const&, QString const&, QString const&) (this=0x55632406a610, key=..., name=..., email=..., comment=...) at qgpgmeadduseridjob.cpp:82 Before that the stack consists of: (shortened) #33 src/widgets/widgets/qlineedit.cpp:318 #34 src/klineedit.cpp:371 #35 src/pimcommonakonadi/addressline/addresslineedit/addresseelineedit.cpp:249 #36 src/recipient/recipientline.cpp:169 #37 src/recipient/recipientline.cpp:135 #38 src/libkdepim/multiplyingline/multiplyinglineeditor.cpp:50 #39 src/recipient/recipientseditor.cpp:102 I think that this is an odd stack for an application startup. When I start KMail only, it also crashes and consists of this in the stack trace: (I have reformatted the lines to point at what DrKonqi presented me in red) #20 0x7f1649f142af in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) (sender=sender@entry=0x560d43431dd0, m=m@entry=0x7f1649067800 , local_signal_index=local_signal_index@entry=2, argv=argv@entry=0x0) <=== argv=0x0 ? marked red by DrKonqi at src/corelib/kernel/qobject.cpp:3946 #21 0x7f1648f5be03 in MessageComposer::RecipientLineNG::countChanged() (this=this@entry=0x560d43431dd0) at messagecomposer/src/KF5MessageComposer_autogen/LXYSN6NNNG/moc_recipientline.cpp:481 #22 0x7f1648fb4ffe in MessageComposer::RecipientLineNG::analyzeLine(QString const&) (this=0x560d43431dd0, text=) at messagecomposer/src/recipient/recipientline.cpp:120 Why does starting kmail call the message composer at all? -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 449872] Kontact crashed while trying to reply to email
https://bugs.kde.org/show_bug.cgi?id=449872 --- Comment #1 from Sven Eden --- Created attachment 146521 --> https://bugs.kde.org/attachment.cgi?id=146521=edit New crash information added by DrKonqi kontact (5.19.2 (21.12.2)) using Qt 5.15.2 - What I was doing when the application crashed: Pressed 'a' to reply to everybody on a selected E-Mail in kmail component. Since then I can no longer start kontact, it immediately crashes. However, when I restart akonadi, I get notifications about new E-Mails, and KOrganizer works. Starting kmail directly also crashes. - Custom settings of the application: Gentoo Linux with gcc-11.2.1 and Qt-5.15.2 I have rebuilt everything needed for kontact plus kontact itself and have restarted the computer several times. The odd thing is, that Kontact worked just fine like every day. However, I have removed ~/.local/share/akonadi/db_data a week ago and have had akonadi recreate it. Everything worked just fine, so I doubt this could be the issue. -- Backtrace (Reduced): #6 QString::QString(QString const&) (other=, this=) at /usr/lib/gcc/x86_64-pc-linux-gnu/11.2.1/include/g++-v11/bits/move.h:104 #7 std::_Head_base<4ul, QString, false>::_Head_base(QString const&) (__h=, this=) at /usr/lib/gcc/x86_64-pc-linux-gnu/11.2.1/include/g++-v11/tuple:193 #8 std::_Tuple_impl<4ul, QString>::_Tuple_impl(QString const&) (__head=, this=) at /usr/lib/gcc/x86_64-pc-linux-gnu/11.2.1/include/g++-v11/tuple:435 #9 std::_Tuple_impl<3ul, QString, QString>::_Tuple_impl(QString const&, QString const&) (__tail#0=, __head=, this=) at /usr/lib/gcc/x86_64-pc-linux-gnu/11.2.1/include/g++-v11/tuple:284 #10 std::_Tuple_impl<2ul, QString, QString, QString>::_Tuple_impl(QString const&, QString const&, QString const&) (__tail#1=, __tail#0=, __head=, this=) at /usr/lib/gcc/x86_64-pc-linux-gnu/11.2.1/include/g++-v11/tuple:284 -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 449872] Kontact crashed while trying to reply to email
https://bugs.kde.org/show_bug.cgi?id=449872 Sven Eden changed: What|Removed |Added CC||sven.e...@gmx.de -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 425872] Kontact crashes when accepting a delegated invitation
https://bugs.kde.org/show_bug.cgi?id=425872 --- Comment #1 from Sven Eden --- > Possible duplicates by query: bug 425720, bug 425651, bug 425629, bug > 425619, bug 425340. I have read all five and more, and none come close to this backtrace or near what is happening. So I hope I did the right thing reporting a new bug. -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 425872] New: Kontact crashes when accepting a delegated invitation
https://bugs.kde.org/show_bug.cgi?id=425872 Bug ID: 425872 Summary: Kontact crashes when accepting a delegated invitation Product: kontact Version: unspecified Platform: Compiled Sources OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: sven.e...@gmx.de Target Milestone: --- Application: kontact (5.15.0 (20.08.0)) (Compiled from sources) Qt Version: 5.15.0 Frameworks Version: 5.73.0 Operating System: Linux 5.7.18-gentoo x86_64 Windowing system: X11 Distribution: Gentoo/Linux -- Information about the crash: - What I was doing when the application crashed: A collegue delegated an invitation for a zoom meeting to me. When I press the "Accept" button, kontact crashes immediately. Important: Kontact works perfectly fine on any of the invitation response buttons in any invitation that got directly sent to me. This is the only case where it crashes. So I daresay the delegation has something to do with it. Some Background: The calendar used is an Exchange Calendar on an on-premise Exchange 2013 server, and is connected using CalDav over the latest version of davmail. I have searched for duplicates, but all DrKonqi showed me where about other areas than this. So hopefully I didn't miss _the_ relevant report I should have latched on. The crash can be reproduced every time. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault Content of s_kcrashErrorMessage: (null) [KCrash Handler] #6 0x7fb9a9cdedd4 in KMime::Content::parent() const (this=this@entry=0x5609fbd0cc80) at /data/portage/portage/kde-apps/kmime-20.08.0/work/kmime-20.08.0/src/kmime_content.cpp:828 #7 0x7fb9a9cdedea in KMime::Content::topLevel() const (this=this@entry=0x5609fbd0cc80) at /data/portage/portage/kde-apps/kmime-20.08.0/work/kmime-20.08.0/src/kmime_content.cpp:834 #8 0x7fb964eae11e in (anonymous namespace)::UrlHandler::findReceiver(KMime::Content*) (node=0x5609fbd0cc80) at /data/portage/portage/kde-apps/kdepim-addons-20.08.0/work/kdepim-addons-20.08.0/plugins/messageviewer/bodypartformatter/calendar/text_calendar.cpp:414 #9 0x7fb964eb3da0 in (anonymous namespace)::UrlHandler::handleInvitation(QString const&, KCalendarCore::Attendee::PartStat, MimeTreeParser::Interface::BodyPart*, MessageViewer::Viewer*) const (this=0x5609fb2cdce0, iCal=..., status=KCalendarCore::Attendee::Accepted, part=0x7ffe17263100, viewerInstance=0x5609f93da820) at /data/portage/portage/kde-apps/kdepim-addons-20.08.0/work/kdepim-addons-20.08.0/plugins/messageviewer/bodypartformatter/calendar/text_calendar.cpp:875 #10 0x7fb964eb615e in (anonymous namespace)::UrlHandler::handleClick(MessageViewer::Viewer*, MimeTreeParser::Interface::BodyPart*, QString const&) const (this=this@entry=0x5609fb2cdce0, viewerInstance=0x5609f93da820, part=part@entry=0x7ffe17263100, path=...) at /data/portage/portage/kde-apps/kdepim-addons-20.08.0/work/kdepim-addons-20.08.0/plugins/messageviewer/bodypartformatter/calendar/text_calendar.cpp:1217 #11 0x7fb9a87afab0 in MessageViewer::BodyPartURLHandlerManager::handleClick(QUrl const&, MessageViewer::ViewerPrivate*) const (this=, url=..., w=0x5609f95db0d0) at /data/portage/portage/kde-apps/messagelib-20.08.0-r1/work/messagelib-20.08.0/messageviewer/src/viewer/urlhandlermanager.cpp:168 #12 0x7fb9a87ad2c8 in MessageViewer::URLHandlerManager::handleClick(QUrl const&, MessageViewer::ViewerPrivate*) const (this=, url=..., w=w@entry=0x5609f95db0d0) at /data/portage/portage/kde-apps/messagelib-20.08.0-r1/work/messagelib-20.08.0/messageviewer/src/viewer/urlhandlermanager.cpp:288 #13 0x7fb9a8791661 in MessageViewer::ViewerPrivate::slotUrlOpen(QUrl const&) (this=0x5609f95db0d0, url=...) at /data/portage/portage/kde-apps/messagelib-20.08.0-r1/work/messagelib-20.08.0/messageviewer/src/viewer/viewer_p.cpp:2004 #14 0x7fb9ece100cd in QObject::event(QEvent*) (this=0x5609f95db0d0, e=0x7fb9b81091f0) at /data/portage/portage/dev-qt/qtcore-5.15.0/work/qtbase-everywhere-src-5.15.0/src/corelib/kernel/qobject.cpp:1314 #15 0x7fb9ed8567cf in QApplicationPrivate::notify_helper(QObject*, QEvent*) (this=this@entry=0x5609f89db9a0, receiver=receiver@entry=0x5609f95db0d0, e=e@entry=0x7fb9b81091f0) at /data/portage/portage/dev-qt/qtwidgets-5.15.0/work/qtbase-everywhere-src-5.15.0/src/widgets/kernel/qapplication.cpp:3671 #16 0x7fb9ed85f5f0 in QApplication::notify(QObject*, QEvent*) (this=0x7ffe17263840, receiver=0x5609f95db0d0, e=0x7fb9b81091f0) at /data/portage/portage/dev-qt/qtwidgets-5.15.0/work/qtbase-everywhere-src-5.15.0/src/widgets/kernel/qapplication.cpp:3417 #17 0x7fb9ecde4598 in QCoreApplication::notifyInternal2(QObject*, QEvent*) (receiver=0x5609f95db0d0, event=0x7fb9b81091f0) at
[Akonadi] [Bug 368161] Plasma (plasmashell), signal: Segmentation fault
https://bugs.kde.org/show_bug.cgi?id=368161 Sven Eden <sven.e...@gmx.de> changed: What|Removed |Added CC||sven.e...@gmx.de --- Comment #3 from Sven Eden <sven.e...@gmx.de> --- Unfortunately I have to add my backtrace by hand. DrKonqi lets me log in and find this report, but when I want to attach my report and click on "continue", nothing happens. :-( The crashing Thread 1 looks similar, but not exactly equal. However, Plasma crashed after I issued "akonadictl stop" in a console. I think that this is odd. I am using: System : Gentoo x86_64 Framework: 5.29.0 Plasma : 5.8.4 Apps : 16.12.0 QT : 5.7.1 GCC : 5.4.0 GLIBC: 2.23 Could this be some sort of race condition? -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f5e9c608780 (LWP 16603))] Thread 9 (Thread 0x7f5dcd141700 (LWP 22436)): #0 0x7f5e92f8e4a9 in g_source_iter_next (iter=iter@entry=0x7f5dcd140c80, source=source@entry=0x7f5dcd140c78) at /home/portage/dev-libs/glib-2.50.2/work/glib-2.50.2/glib/gmain.c:982 #1 0x7f5e92f90d9a in g_main_context_check (context=context@entry=0x7f5dc8003200, max_priority=2147483647, fds=fds@entry=0x7f5dc80033e0, n_fds=n_fds@entry=1) at /home/portage/dev-libs/glib-2.50.2/work/glib-2.50.2/glib/gmain.c:3742 #2 0x7f5e92f91400 in g_main_context_iterate (context=context@entry=0x7f5dc8003200, block=block@entry=1, dispatch=dispatch@entry=1, self=) at /home/portage/dev-libs/glib-2.50.2/work/glib-2.50.2/glib/gmain.c:3926 #3 0x7f5e92f9156c in g_main_context_iteration (context=0x7f5dc8003200, may_block=may_block@entry=1) at /home/portage/dev-libs/glib-2.50.2/work/glib-2.50.2/glib/gmain.c:3990 #4 0x7f5e97894ccb in QEventDispatcherGlib::processEvents (this=0x7f5dc8002700, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #5 0x7f5e9784654a in QEventLoop::exec (this=this@entry=0x7f5dcd140e40, flags=..., flags@entry=...) at kernel/qeventloop.cpp:212 #6 0x7f5e9769de24 in QThread::exec (this=) at thread/qthread.cpp:507 #7 0x7f5e976a206c in QThreadPrivate::start (arg=0x73ce6a0) at thread/qthread_unix.cpp:368 #8 0x7f5e967503a4 in start_thread (arg=0x7f5dcd141700) at pthread_create.c:333 #9 0x7f5e96f4c50d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 8 (Thread 0x7f5dd5da3700 (LWP 18808)): #0 0x7f5e96f3f45d in read () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f5e92fd6230 in read (__nbytes=16, __buf=0x7f5dd5da2c00, __fd=) at /usr/include/bits/unistd.h:44 #2 g_wakeup_acknowledge (wakeup=0x7f5dd01b0f90) at /home/portage/dev-libs/glib-2.50.2/work/glib-2.50.2/glib/gwakeup.c:210 #3 0x7f5e92f90f2e in g_main_context_check (context=context@entry=0x7f5dd000f030, max_priority=2147483647, fds=fds@entry=0x7f5dd0351c00, n_fds=n_fds@entry=1) at /home/portage/dev-libs/glib-2.50.2/work/glib-2.50.2/glib/gmain.c:3707 #4 0x7f5e92f91400 in g_main_context_iterate (context=context@entry=0x7f5dd000f030, block=block@entry=1, dispatch=dispatch@entry=1, self=) at /home/portage/dev-libs/glib-2.50.2/work/glib-2.50.2/glib/gmain.c:3926 #5 0x7f5e92f9156c in g_main_context_iteration (context=0x7f5dd000f030, may_block=may_block@entry=1) at /home/portage/dev-libs/glib-2.50.2/work/glib-2.50.2/glib/gmain.c:3990 #6 0x7f5e97894ccb in QEventDispatcherGlib::processEvents (this=0x7f5dd01ae230, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #7 0x7f5e9784654a in QEventLoop::exec (this=this@entry=0x7f5dd5da2e20, flags=..., flags@entry=...) at kernel/qeventloop.cpp:212 #8 0x7f5e9769de24 in QThread::exec (this=this@entry=0x1926330) at thread/qthread.cpp:507 #9 0x7f5e99e72895 in QQmlThreadPrivate::run (this=0x1926330) at qml/ftw/qqmlthread.cpp:147 #10 0x7f5e976a206c in QThreadPrivate::start (arg=0x1926330) at thread/qthread_unix.cpp:368 #11 0x7f5e967503a4 in start_thread (arg=0x7f5dd5da3700) at pthread_create.c:333 #12 0x7f5e96f4c50d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 7 (Thread 0x7f5dde3ac700 (LWP 16878)): #0 0x7f5e92f8e462 in g_source_iter_next (iter=iter@entry=0x7f5dde3abc40, source=source@entry=0x7f5dde3abc38) at /home/portage/dev-libs/glib-2.50.2/work/glib-2.50.2/glib/gmain.c:987 #1 0x7f5e92f90d9a in g_main_context_check (context=context@entry=0x7f5dd8000990, max_priority=2147483647, fds=fds@entry=0x7f5dd80048a0, n_fds=n_fds@entry=1) at /home/portage/dev-libs/glib-2.50.2/work/glib-2.50.2/glib/gmain.c:3742 #2 0x7f5e92f91400 in g_main_context_iterate (context=context@entry=0x7f5dd8000990, block=block@entry=1, dispatch=dispatch@entry=1, self=) at /home/portage/dev-libs/glib-2.50.2/work/glib-2.50.2/glib/gmain.c:3926 #3 0x7f5e92f9156c in g_main_context_it
[Akonadi] [Bug 363741] akonadi server 16.04.2: crashing every few seconds
https://bugs.kde.org/show_bug.cgi?id=363741 Sven Eden <sven.e...@gmx.de> changed: What|Removed |Added CC||sven.e...@gmx.de --- Comment #14 from Sven Eden <sven.e...@gmx.de> --- I tried this and removed the search folder. After a restart of both akonadi and kontact (I had gdb hooked to the akonadiserver process) and trying to do a search, gdb caught a SIGSEGV with the following trace: Thread 60 "QThread" received signal SIGSEGV, Segmentation fault. [Switching to Thread 0x7fd009ffb700 (LWP 17593)] 0x7fcfe854b9a8 in vtable for Xapian::Internal::QueryTerm () from /usr/lib64/libxapian-1.3.so.8 (gdb) bt #0 0x7fcfe854b9a8 in vtable for Xapian::Internal::QueryTerm () from /usr/lib64/libxapian-1.3.so.8 #1 0x7fcfe82a301b in ExternalPostList::ExternalPostList (this=0x7fcff009f1e0, db=..., source_=, factor_=, matcher=0x7fd009ff9d10) at matcher/externalpostlist.cc:40 #2 0x7fcfe81b5d4b in Xapian::Internal::QueryPostingSource::postlist (this=, qopt=0x7fd009ff9630, factor=1) at api/queryinternal.cc:739 #3 0x7fcfe81b40b1 in Xapian::Query::Internal::postlist_sub_xor (this=, ctx=..., qopt=, factor=) at api/queryinternal.cc:634 #4 0x7fcfe81b5533 in Xapian::Internal::QueryBranch::do_or_like (this=this@entry=0x7fcff001bd60, ctx=..., qopt=qopt@entry=0x7fd009ff9630, factor=factor@entry=1, elite_set_size=elite_set_size@entry=0, first=first@entry=1) at api/queryinternal.cc:1186 #5 0x7fcfe81b5afa in Xapian::Internal::QueryAndMaybe::postlist (this=0x7fcff001bd60, qopt=0x7fd009ff9630, factor=1) at api/queryinternal.cc:1550 #6 0x7fcfe82a32da in LocalSubMatch::get_postlist (this=0x7fcff009a6c0, matcher=0x7fd009ff9d10, total_subqs_ptr=0x7fd009ff979c) at matcher/localsubmatch.cc:204 #7 0x7fcfe82a9741 in MultiMatch::get_mset (this=this@entry=0x7fd009ff9d10, first=first@entry=0, maxitems=95894, check_at_least=check_at_least@entry=95894, mset=..., stats=..., mdecider=0x0, sorter=0x0) at matcher/multimatch.cc:419 #8 0x7fcfe81a4641 in Xapian::Enquire::Internal::get_mset (this=0x7fcff009a830, first=, maxitems=, check_at_least=, check_at_least@entry=0, rset=rset@entry=0x0, mdecider=0x0) at api/omenquire.cc:548 #9 0x7fcfe81a4984 in Xapian::Enquire::get_mset (this=this@entry=0x7fd009ffa030, first=, maxitems=, check_at_least=check_at_least@entry=0, rset=rset@entry=0x0, mdecider=0x0) at api/omenquire.cc:906 #10 0x7fcfe05e967d in Akonadi::Search::XapianSearchStore::exec (this=0x7fcff003fe70, query=...) at /home/portage/kde-apps/akonadi-search-16.04.2/work/akonadi-search-16.04.2/xapian/xapiansearchstore.cpp:177 #11 0x7fd00919e2e5 in Akonadi::Search::Query::exec (this=this@entry=0x7fd009ffa2a0) at /home/portage/kde-apps/akonadi-search-16.04.2/work/akonadi-search-16.04.2/core/query.cpp:252 #12 0x7fd0095f5f6d in SearchPlugin::search (this=, akonadiQuery=..., collections=..., mimeTypes=...) at /home/portage/kde-apps/akonadi-search-16.04.2/work/akonadi-search-16.04.2/akonadiplugin/searchplugin.cpp:348 #13 0x0053ed1d in Akonadi::Server::SearchRequest::searchPlugins (this=this@entry=0x7fd009ffa880) at /home/portage/kde-apps/akonadi-16.04.2/work/akonadi-16.04.2/src/server/search/searchrequest.cpp:112 #14 0x0053ef7f in Akonadi::Server::SearchRequest::exec (this=this@entry=0x7fd009ffa880) at /home/portage/kde-apps/akonadi-16.04.2/work/akonadi-16.04.2/src/server/search/searchrequest.cpp:123 #15 0x00443944 in Akonadi::Server::SearchManager::updateSearchImpl (this=, collection=..., cond=0x7fceeaffc4e0) at /home/portage/kde-apps/akonadi-16.04.2/work/akonadi-16.04.2/src/server/search/searchmanager.cpp:350 #16 0x004fbea5 in Akonadi::Server::SearchManager::qt_static_metacall (_o=, _c=, _id=, _a=) at /home/portage/kde-apps/akonadi-16.04.2/work/akonadi-16.04.2_build/src/server/moc_searchmanager.cpp:108 #17 0x7fd0165f8711 in QObject::event (this=0x27ac890, e=) at kernel/qobject.cpp:1256 #18 0x7fd0165cfaaa in doNotify (receiver=, event=) at kernel/qcoreapplication.cpp:1090 #19 0x7fd0165cfbda in QCoreApplication::notifyInternal2 (receiver=0x27ac890, event=event@entry=0x7fceec0deef0) at kernel/qcoreapplication.cpp:1015 #20 0x7fd0165d1c2a in QCoreApplication::sendEvent (event=0x7fceec0deef0, receiver=) at kernel/qcoreapplication.h:225 #21 QCoreApplicationPrivate::sendPostedEvents (receiver=receiver@entry=0x0, event_type=event_type@entry=0, data=0x27ab840) at kernel/qcoreapplication.cpp:1650 #22 0x7fd0165d20e8 in QCoreApplication::sendPostedEvents (receiver=receiver@entry=0x0, event_type=event_type@entry=0) at kernel/qcoreapplication.cpp:1508 #23 0x7fd01661ec13 in postEventSourceDispatch (s=0x7fcff00012d0) at kernel/qeventdispatcher_glib.cpp:270 #24 0x7fd013da0
[Akonadi] [Bug 255388] Kmail filters dont work in incoming mail
https://bugs.kde.org/show_bug.cgi?id=255388 --- Comment #114 from Sven Eden <sven.e...@gmx.de> --- Update on my previous report: After the mail filter finished, it got stuck at 100%. The akonadi_mailfilter_agent process used 100% CPU, and was neither interruptible nor stoppable using akonadiconsole. I quit kontact, shut down akonadi and even logged out and back into plasma, but the process remained until I killed it. After that it worked just fine yesterday. Today I wanted to filter some mails and it just started at 100% and was stuck again until the process got killed. I tried several times, with kontact and akonadi restarting in between, but always ended up killing the akonadi_mailfilter_agent. Then, all of a sudden, a myriad of status windows popped up, all with the filter being at 100%, but eventually it started its work regularly. If I had to guess, I'd think the filter has at least one race condition and a problematic endless loop somewhere. Didn't look up the sources, though... -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Akonadi] [Bug 255388] Kmail filters dont work in incoming mail
https://bugs.kde.org/show_bug.cgi?id=255388 Sven Eden <sven.e...@gmx.de> changed: What|Removed |Added CC||sven.e...@gmx.de --- Comment #113 from Sven Eden <sven.e...@gmx.de> --- I just came across this. Normally it was enough to fire up akonadiconsole, restart the mail filter agent, and then quickly start kontact. Not today. When, for the umpteenth time, the mail filter was stuck at 0%, I opened the akonadiconsole, and selected "Abort Activity" on the mail filter agent. And it immediately began to filter the 1,046 mails I had selected. So it seems, that the filter agent got ordered to do something else before answering my request and got stuck on that, and not the requested filtering itself. It is slow right now, because I had activated the filter log, but at least it works again. -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Akonadi] [Bug 354994] Crash of Akonadi CardCalDav
https://bugs.kde.org/show_bug.cgi?id=354994 --- Comment #13 from Sven Eden <sven.e...@gmx.de> --- Created attachment 97378 --> https://bugs.kde.org/attachment.cgi?id=97378=edit Check mEtagCaches[collection.remoteId()] result before using it The patch fixed the crash for me. However, I *do* think that it is a different issue, but at least you now know about it. ;-) -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Akonadi] [Bug 354994] Crash of Akonadi CardCalDav
https://bugs.kde.org/show_bug.cgi?id=354994 Sven Eden <sven.e...@gmx.de> changed: What|Removed |Added CC||sven.e...@gmx.de --- Comment #12 from Sven Eden <sven.e...@gmx.de> --- Hmm... I've updated to 15.12.2 but all mails regarding exchange calendar invitations still crash the resource. Maybe I hit a different bug? I got: "akonadi_davgroupware_resource" Signal: Segmentation fault (11) The most interesting lines from the backtrace are: #5 #6 QMap<QString, QString>::detach (this=0x10) at /usr/include/qt5/QtCore/qmap.h:364 #7 QMap<QString, QString>::operator[] (akey=..., this=0x10) at /usr/include/qt5/QtCore/qmap.h:629 #8 EtagCache::setEtag (this=0x0, remoteId=..., etag=...) at /home/portage/kde-apps/kdepim-runtime-15.12.2/work/kdepim-runtime-15.12.2/resources/dav/common/etagcache.cpp:38 #9 0x004719ed in DavGroupwareResource::onItemFetched (this=0x1239990, job=, updateType=DavGroupwareResource::ItemUpdateAdd) at /home/portage/kde-apps/kdepim-runtime-15.12.2/work/kdepim-runtime-15.12.2/resources/dav/resource/davgroupwareresource.cpp:958 See frame #8 where 'this' is 0x0? Frame #8 source is: (gdb) frame 8 #8 EtagCache::setEtag (this=0x0, remoteId=..., etag=...) at /home/portage/kde-apps/kdepim-runtime-15.12.2/work/kdepim-runtime-15.12.2/resources/dav/common/etagcache.cpp:38 38 mCache[ remoteId ] = etag; Frame #9 source is: (gdb) frame 9 #9 0x004719ed in DavGroupwareResource::onItemFetched (this=0x1239990, job=, updateType=DavGroupwareResource::ItemUpdateAdd) at /home/portage/kde-apps/kdepim-runtime-15.12.2/work/kdepim-runtime-15.12.2/resources/dav/resource/davgroupwareresource.cpp:958 958 mEtagCaches[collection.remoteId()]->setEtag(item.remoteId(), davItem.etag()); So I *guess* collection.remoteId() should be checked first... -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[kontact] [Bug 340680] another crash-on-exit due to nested event handling
https://bugs.kde.org/show_bug.cgi?id=340680 --- Comment #4 from Sven Eden <sven.e...@gmx.de> --- Created attachment 94848 --> https://bugs.kde.org/attachment.cgi?id=94848=edit New crash information added by DrKonqi kontact (4.14.10) on KDE Platform 4.14.12 using Qt 4.8.7 - What I was doing when the application crashed: KMail got stuck somewhere, wherever I clicked it said "Please wait while retrieving folder contents", so I quit kontact. About ~10 seconds later DrKonqi showed up, and the backtraces suggest this is the same or at least a similar crash. -- Backtrace (Reduced): #6 operator QItemSelectionModel* (this=) at ../../include/QtCore/../../../qt-everywhere-opensource-src-4.8.7/src/corelib/kernel/qpointer.h:78 #7 QAbstractItemView::selectionModel (this=0xe0108) at /home/portage/dev-qt/qtgui-4.8.7/work/qt-everywhere-opensource-src-4.8.7/src/gui/itemviews/qabstractitemview.cpp:766 #8 0x7fdf18bc657c in MailCommon::FolderTreeWidget::selectedCollections (this=) at /home/portage/kde-base/kdepim-common-libs-4.14.10/work/kdepim-common-libs-4.14.10/mailcommon/folder/foldertreewidget.cpp:243 #9 0x7fdf19289ea3 in KMMainWidget::updateFolderMenu (this=0x13fc3d0) at /home/portage/kde-base/kmail-4.14.10/work/kmail-4.14.10/kmail/kmmainwidget.cpp:3928 #10 0x7fdf1939aa8b in KMMainWidget::qt_static_metacall (_o=, _c=, _id=, _a=) at /home/portage/kde-base/kmail-4.14.10/work/kmail-4.14.10_build/kmail/moc_kmmainwidget.cpp:461 -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[kontact] [Bug 340680] another crash-on-exit due to nested event handling
https://bugs.kde.org/show_bug.cgi?id=340680 Sven Eden <sven.e...@gmx.de> changed: What|Removed |Added CC||sven.e...@gmx.de -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[kontact] [Bug 339739] kmail/kontact 4.14.1 crashes when compacting a folder with ghost items
https://bugs.kde.org/show_bug.cgi?id=339739 Sven Eden sven.e...@gmx.de changed: What|Removed |Added Summary|kmail/kontact 4.14.1|kmail/kontact 4.14.1 |crashes when xompacting a |crashes when compacting a |folder with ghost items |folder with ghost items -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[kontact] [Bug 339739] New: kmail/kontact 4.14.1 crashes when xompacting a folder with ghost items
https://bugs.kde.org/show_bug.cgi?id=339739 Bug ID: 339739 Summary: kmail/kontact 4.14.1 crashes when xompacting a folder with ghost items Product: kontact Version: unspecified Platform: Gentoo Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: mail Assignee: kdepim-bugs@kde.org Reporter: sven.e...@gmx.de Application: kontact (4.14.1) KDE Platform Version: 4.14.1 (Compiled from sources) Qt Version: 4.8.5 Operating System: Linux 3.15.10-geek x86_64 Distribution (Platform): Gentoo Packages -- Information about the crash: For a while now I keep getting error messages from our IMAP server: Save failed, server response: A08 BAD Command Argument Error. 12 I tracked it down to a ghost item in my outbox. The Folder is empty when opened and there is nothing in the folder on my hard disk either. - What I was doing when the application crashed: To get rid of this item I tried to archive (compact?) the folder. Kontact crashed at once. - Unusual behavior I noticed: Persistent ghost item in the outbox folder. -- Backtrace: Application: Kontact (kontact), signal: Aborted Using host libthread_db library /lib64/libthread_db.so.1. [Current thread is 1 (Thread 0x7f6be1f9e900 (LWP 30005))] Thread 4 (Thread 0x7f6bc7003700 (LWP 30006)): #0 pthread_cond_wait () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f6bdcda1622 in ?? () from /usr/lib64/qt4/libQtWebKit.so.4 #2 0x7f6bdcda1659 in ?? () from /usr/lib64/qt4/libQtWebKit.so.4 #3 0x7f6bd9d47083 in start_thread (arg=0x7f6bc7003700) at pthread_create.c:309 #4 0x7f6bdf4ee36d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111 Thread 3 (Thread 0x7f6bc6702700 (LWP 30007)): #0 0x7f6bdf4e4c8d in poll () at ../sysdeps/unix/syscall-template.S:81 #1 0x7f6bd8f08a7e in g_main_context_poll (priority=optimized out, n_fds=1, fds=0x7f6bc0003290, timeout=-1, context=0x7f6bc9a0) at /home/portage/dev-libs/glib-2.40.0-r1/work/glib-2.40.0/glib/gmain.c:4028 #2 g_main_context_iterate (context=context@entry=0x7f6bc9a0, block=block@entry=1, dispatch=dispatch@entry=1, self=optimized out) at /home/portage/dev-libs/glib-2.40.0-r1/work/glib-2.40.0/glib/gmain.c:3729 #3 0x7f6bd8f08b8c in g_main_context_iteration (context=0x7f6bc9a0, may_block=1) at /home/portage/dev-libs/glib-2.40.0-r1/work/glib-2.40.0/glib/gmain.c:3795 #4 0x7f6be0923ebe in QEventDispatcherGlib::processEvents (this=0x7f6bc8c0, flags=...) at kernel/qeventdispatcher_glib.cpp:452 #5 0x7f6be08f43c8 in QEventLoop::processEvents (this=this@entry=0x7f6bc6701c90, flags=...) at kernel/qeventloop.cpp:149 #6 0x7f6be08f46dd in QEventLoop::exec (this=this@entry=0x7f6bc6701c90, flags=...) at kernel/qeventloop.cpp:204 #7 0x7f6be07e7fb8 in QThread::exec (this=optimized out) at thread/qthread.cpp:536 #8 0x7f6be07ea73b in QThreadPrivate::start (arg=0x1306850) at thread/qthread_unix.cpp:338 #9 0x7f6bd9d47083 in start_thread (arg=0x7f6bc6702700) at pthread_create.c:309 #10 0x7f6bdf4ee36d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111 Thread 2 (Thread 0x7f6b70b10700 (LWP 30849)): #0 pthread_cond_wait () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f6b7daecedb in QTWTF::TCMalloc_PageHeap::scavengerThread (this=0x7f6b7dde8280 QTWTF::pageheap_memory) at ../3rdparty/javascriptcore/JavaScriptCore/wtf/FastMalloc.cpp:2359 #2 0x7f6b7daecf29 in QTWTF::TCMalloc_PageHeap::runScavengerThread (context=optimized out) at ../3rdparty/javascriptcore/JavaScriptCore/wtf/FastMalloc.cpp:1464 #3 0x7f6bd9d47083 in start_thread (arg=0x7f6b70b10700) at pthread_create.c:309 #4 0x7f6bdf4ee36d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111 Thread 1 (Thread 0x7f6be1f9e900 (LWP 30005)): [KCrash Handler] #6 0x7f6bdf43b2a9 in __GI_raise (sig=sig@entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:56 #7 0x7f6bdf43c5e8 in __GI_abort () at abort.c:89 #8 0x7f6bdf809745 in __gnu_cxx::__verbose_terminate_handler () at /home/portage/sys-devel/gcc-4.8.3/work/gcc-4.8.3/libstdc++-v3/libsupc++/vterminate.cc:95 #9 0x7f6bdf807876 in __cxxabiv1::__terminate (handler=optimized out) at /home/portage/sys-devel/gcc-4.8.3/work/gcc-4.8.3/libstdc++-v3/libsupc++/eh_terminate.cc:38 #10 0x7f6bdf8078a3 in std::terminate () at /home/portage/sys-devel/gcc-4.8.3/work/gcc-4.8.3/libstdc++-v3/libsupc++/eh_terminate.cc:48 #11 0x7f6bdf807b16 in __cxxabiv1::__cxa_rethrow () at /home/portage/sys-devel/gcc-4.8.3/work/gcc-4.8.3/libstdc++-v3/libsupc++/eh_throw.cc:125 #12 0x7f6be08f48d9 in QEventLoop::exec (this=this@entry=0x7fff4b4933e0, flags=...) at kernel/qeventloop.cpp:218 #13 0x7f6be08f9b99 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1221 #14 0x7f6bdfc7626c in QApplication::exec ()
[kmail2] [Bug 323168] GPG signature validation fails due to KMail modifying headers within received mails
https://bugs.kde.org/show_bug.cgi?id=323168 Sven Eden sven.e...@gmx.de changed: What|Removed |Added CC||sven.e...@gmx.de --- Comment #4 from Sven Eden sven.e...@gmx.de --- I just received a Mail where KMail changed Content-Type: multipart/signed; boundary=J/dobhs11T7y2rNN; micalg=pgp-sha1; protocol=application/pgp-signature to Content-Type: multipart/signed; boundary=J/dobhs11T7y2rNN; micalg=pgp-sha1; protocol=application/pgp-signature resulting in an invalid signature. -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[kmail2] [Bug 316107] big regression: kmail IMAP connection and message display problems
https://bugs.kde.org/show_bug.cgi?id=316107 --- Comment #13 from Sven Eden sven.e...@gmx.de --- (In reply to comment #12) The killed error probably means that the resource has crashed. After starting Akonadi. try attaching GDB to the akonadi_imap_resource process and see whether you can get any backtrace when it crashes (if it crashes) I am sorry, but after removing all filters and moving all e-mails to the inbox the resource no longer crashes. I suspect that the moving was too fast, or whatever, hence I've never seen anything suspicious in neither the filter log nor the akonadi console debugging output. I have tried to add another folder and set a filter to send messages from my private mail adress there, but single messages arriving don't seem top be a problem. The resource only crashed when multiple messages arrived. However, I want at least the e-mails from my coworkers to be sorted out of my inbox, so I'll re-create the corresponding folders and filter rules. I just do not know when I am done with it. -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[kmail2] [Bug 316107] big regression: kmail IMAP connection and message display problems
https://bugs.kde.org/show_bug.cgi?id=316107 --- Comment #11 from Sven Eden sven.e...@gmx.de --- Hello again, I have updated to KDE-4.11.0 and Akonadi-1.10.2 - the same issues but with some slight changes: - Although the IMAP account died (account killed notification received), the Mails that got sync'd last are correctly buffered and can be read. - Now when I click on Click _here_ to go online, it takes until the next auto-sync (5 minutes interval) before the next killed message comes. (Was immediatly before.) - formerly, when I started akonadi using akonadictl I had a couple of lines of not-fetched items and then no more output. Now this line comes only a few times but then is repeated over an over again once per second. The output is: sed@sed-notebook ~ $ akonadictl start Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString) search paths: (/home/sed/sys/bin, /usr/local/bin, /usr/bin, /bin, /opt/bin, /usr/x86_64-pc-linux-gnu/gcc-bin/4.7.3, /opt/nvidia-cg-toolkit/bin, /usr/lib64/subversion/bin, /usr/games/bin, /opt/vmware/bin, /var/qmail/bin, /usr/sbin, /usr/local/sbin, /usr/local/libexec, /usr/libexec, /opt/mysql/libexec, /opt/local/lib/mysql5/bin, /opt/mysql/sbin) QSqlDatabasePrivate::removeDatabase: connection 'initConnection' is still in use, all queries will cease to work. Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString) search paths: (/home/sed/sys/bin, /usr/local/bin, /usr/bin, /bin, /opt/bin, /usr/x86_64-pc-linux-gnu/gcc-bin/4.7.3, /opt/nvidia-cg-toolkit/bin, /usr/lib64/subversion/bin, /usr/games/bin, /opt/vmware/bin, /var/qmail/bin) search paths: (/usr/lib/kde4/plugins/, /usr/lib/qt4/plugins/, /usr/lib64/qt4/plugins, /usr/bin, /usr/lib64/kde4/plugins, /home/sed/.kde4/lib64/kde4/, /usr/lib64/kde4/) search paths: (/usr/lib/kde4/plugins/, /usr/lib/qt4/plugins/, /usr/lib64/qt4/plugins, /usr/bin, /usr/lib64/kde4/plugins, /home/sed/.kde4/lib64/kde4/, /usr/lib64/kde4/) search paths: (/usr/lib/kde4/plugins/, /usr/lib/qt4/plugins/, /usr/lib64/qt4/plugins, /usr/bin, /usr/lib64/kde4/plugins, /home/sed/.kde4/lib64/kde4/, /usr/lib64/kde4/) mMonitor true mMonitor true akonadi_nepomuk_feeder(26327) FeederPluginloader::feederPluginsForMimeType: No feeder for type text/calendar found akonadi_nepomuk_feeder(26327) ItemQueue::fetchJobResult: Not all items were fetched: 0 100 (...) akonadi_nepomuk_feeder(26327) ItemQueue::fetchJobResult: Not all items were fetched: 0 100 - akonadictl fsck and vacuum don't seem to do anything anymore. (Or maybe they just haven't got anything to do.) - akonadictl stop now gives a message (the first) I do not understand. The mentioned folder is there and valid: sed@sed-notebook ~ $ AkonadiAgentServer(26321)/kio (KDirWatch) KDirWatchPrivate::removeEntry: doesn't know /home/sed/Mail AkonadiAgentServer(26321)/kdecore (KConfigSkeleton) KCoreConfigSkeleton::writeConfig: akonadi_pop3_resource_0(26329)/akonadiresource (pop3) SettingsHelper::~SettingsHelper: Settings(0xd378f0) Application '/usr/bin/akonadi_kabc_resource' exited normally... Application '/usr/bin/akonadi_pop3_resource' exited normally... Application '/usr/bin/akonadi_sendlater_agent' exited normally... Application '/usr/bin/akonadi_agent_launcher' exited normally... Application '/usr/bin/akonadi_maildispatcher_agent' exited normally... Application '/usr/bin/akonadi_davgroupware_resource' exited normally... Application '/usr/bin/akonadi_agent_launcher' exited normally... Application '/usr/bin/akonadi_imap_resource' exited normally... Application '/usr/bin/akonadi_agent_launcher' exited normally... Application '/usr/bin/akonadi_mailfilter_agent' exited normally... Application '/usr/bin/akonadi_archivemail_agent' exited normally... Application '/usr/bin/akonadi_vcarddir_resource' exited normally... Application '/usr/bin/akonadi_newmailnotifier_agent' exited normally... Application '/usr/bin/akonadi_nepomuk_feeder' exited normally... Application 'akonadiserver' exited normally... However, after doing $ akonadictl start $ akonadictl fsck $ akonadictl vacuum $ akonadictl restart The IMAP account works again until, yes until, a message is received and moved into a different folder by the auto filter of kmail. *sigh* I will go and move _ALL_ my e-mails (luckily only ~3,000) into my inbox and delete the filters and the folders. Let's see whether the problem persists if only one inbox folder is left. -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Akonadi] [Bug 283334] After suspend to ram KMail does not work, akonadi says MySQL server has gone away.
https://bugs.kde.org/show_bug.cgi?id=283334 --- Comment #27 from Sven Eden sven.e...@gmx.de --- The live build of the akonadi server did improve the situation, my IMAP account didn't go offline, yet. However, every time I send an e-mail I get the following message: Account name: Save failed, server replied: A001889 BAD Error in IMAP command UID: Invalid arguments. However, the e-mails get sent and are stored in the sent folder like they should. -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Akonadi] [Bug 283334] After suspend to ram KMail does not work, akonadi says MySQL server has gone away.
https://bugs.kde.org/show_bug.cgi?id=283334 --- Comment #29 from Sven Eden sven.e...@gmx.de --- (In reply to comment #28) Ok, so marking this as fixed, feel free to reopen this bug if you run into the problem again. That was a bit fast. The Account died again. The main difference between the stable and the live build is, that the live build makes more noise. Instead of just one account name : Killed message I got several messages about items not being fetchable in offline mode surrounding this killed message. -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Akonadi] [Bug 283334] After suspend to ram KMail does not work, akonadi says MySQL server has gone away.
https://bugs.kde.org/show_bug.cgi?id=283334 --- Comment #30 from Sven Eden sven.e...@gmx.de --- Sorry for the double post, I was too fast when I realized what was going on. damn browser history, really. I had written that Bug 316107 is about exactly my issues, which are still present. and wanted to 'move' there as I never had any issue with mysql (which is what _this_ bug is about). So while answering I was completely on the wrong track thinking to be in the *other* bug report. Sorry about the noise. However, IMAP is still unusable, even with live built akonadi server. But it has nothing to do with mysql. -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[kmail2] [Bug 316107] big regression: kmail IMAP connection and message display problems
https://bugs.kde.org/show_bug.cgi?id=316107 --- Comment #9 from Sven Eden sven.e...@gmx.de --- I have tried with akonadi compiled from git://anongit.kde.org/akonadi , but IMAP stays switching to persistent offline mode after a while. -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Akonadi] [Bug 283334] After suspend to ram KMail does not work, akonadi says MySQL server has gone away.
https://bugs.kde.org/show_bug.cgi?id=283334 --- Comment #26 from Sven Eden sven.e...@gmx.de --- (In reply to comment #25) (In reply to comment #24) It's not in 1.10.2. Dan meant 'either master or 1.10 git branch' Sure? Akonadi worked flawlessly with my IMAP accounts since the upgrade yesterday... But let's see how it goes tomorrow. If it crashes again, I'll go for a live build, ok. Sure! So I am upgrading to a live build now. Did I check out from the correct repo? git://anongit.kde.org/akonadi -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[kmail2] [Bug 316107] big regression: kmail IMAP connection and message display problems
https://bugs.kde.org/show_bug.cgi?id=316107 Sven Eden sven.e...@gmx.de changed: What|Removed |Added CC||sven.e...@gmx.de --- Comment #8 from Sven Eden sven.e...@gmx.de --- *some* of the symptoms, although titled differently, are discussed/presented in Bug 283334 This issue make kmail almost unusable. Our Webinterface is an outdated horde mail installation. :( -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Akonadi] [Bug 283334] After suspend to ram KMail does not work, akonadi says MySQL server has gone away.
https://bugs.kde.org/show_bug.cgi?id=283334 --- Comment #23 from Sven Eden sven.e...@gmx.de --- (In reply to comment #22) Could someone test with Akonadi master (or 1.10 branch)? The issue should be fixed there. I've updated to akonadi server 1.10.2. I'll report back in a few days. -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Akonadi] [Bug 283334] After suspend to ram KMail does not work, akonadi says MySQL server has gone away.
https://bugs.kde.org/show_bug.cgi?id=283334 Sven Eden sven.e...@gmx.de changed: What|Removed |Added Status|UNCONFIRMED |CONFIRMED Ever confirmed|0 |1 --- Comment #19 from Sven Eden sven.e...@gmx.de --- *** This bug has been confirmed by popular vote. *** -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Akonadi] [Bug 283334] After suspend to ram KMail does not work, akonadi says MySQL server has gone away.
https://bugs.kde.org/show_bug.cgi?id=283334 --- Comment #20 from Sven Eden sven.e...@gmx.de --- This issue is getting more and more out of hand. I have tried with a fresh new user, the same happens, so it does not look like an old-configuration problem. The only thing that helps is to remove the imap resource (bye-bye mail filters!) and create a new one. The last time I wrote that re-booting my laptop helps. This is no longer the case. It helps the first 4 or 5 times the IMAP resource is going out for lunch, but then no longer. I just restarted my laptop, opened contact: No connection to IMAP server name killed Interesting, if I restart the IMAP resource in akonadi-console, I can go into its configuration and refetch the serverside subscription list. But once I exit the configuration I get the name killed message at once. The most evil thing is, that I have absolutely no idea how and where to get a backtrace or something like that. All of the debugging tabs in akonadi-console stay clear of any suspicious message. Only unrelated stuff telling me that everything is fine. (as if). -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Akonadi] [Bug 283334] After suspend to ram KMail does not work, akonadi says MySQL server has gone away.
https://bugs.kde.org/show_bug.cgi?id=283334 Sven Eden sven.e...@gmx.de changed: What|Removed |Added CC||sven.e...@gmx.de --- Comment #18 from Sven Eden sven.e...@gmx.de --- Not exactly the same problem, but probably related. Or maybe it is the same problem as the symptoms are the same. First, my System: Dell Latitude E6410 with 4GB RAM. Gentoo Linux with Kernel 3.9.5-geek QT 4.8.4 and KDE-4.10.4 all built from source with gcc-4.7.3 (safe CFLAGS/LDFLAGS settings) I tried with Mysql-5.1.67 and have now switched to MariaDB-5.5.31. (No, I am not using an embedded server, because I need a running mysql server anyway.) Now how it is breaking: IMAP Mail (neither over davmail to exchange nor to a linux IMAP server) does no longer work after a suspend-to-ram - resume cycle. This has been like that for quite a while, but there was always a workaround: restart agent in akonadi-console, set it online, go into the settings in kmail and reload the serverside subscriptions for that account. This is no longer working since KDE-4.10.3, and is not working with KDE-4.10.4. If I restart the agent(s), they stay offline. If I try to set them online, they stay offline. And the serverside subscription list stays empty and the button to fetch a new list is greyed out. The only solution is to reboot my laptop. .. Which makes Akopnadi/Kontact/KMail close to useless for anybody traveling with their machine or using suspension for any good reason. -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[kontact] [Bug 319254] New: kontact crashes when closing tray icon after suspend/resume
https://bugs.kde.org/show_bug.cgi?id=319254 Bug ID: 319254 Summary: kontact crashes when closing tray icon after suspend/resume Classification: Unclassified Product: kontact Version: 4.10.2 Platform: Compiled Sources OS: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: sven.e...@gmx.de Application: kontact (4.10.2) KDE Platform Version: 4.10.2 (Compiled from sources) Qt Version: 4.8.4 Operating System: Linux 3.8.10-geek x86_64 Distribution (Platform): Gentoo Packages -- Information about the crash: Note: Due to bug 310151 I had to search manually for possible duplicates but couldn't find any. I Apologize if I missed any duplicates. - What I was doing when the application crashed: Closed kontact and shut down akonadi (forgot that I had enabled that tray icon) and put my laptop to sleep. (suspend to ram) When I woke the laptop up, I saw that akonadi was restarted and shut it down again. After that I right-clicked the kmail icon and exited kontact. First Dr.Konqi showed up with this report telling me that kontact crashed, and after a few seconds plasma crashed. Unfortunately the second backtrace didn't yield any valuable data although my complete (!) system is compiled with debugging information. - Custom settings of the application: This is a complete new user account! -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault Using host libthread_db library /lib64/libthread_db.so.1. [Current thread is 1 (Thread 0x7f23f5d0e780 (LWP 12035))] Thread 4 (Thread 0x7f23dbdee700 (LWP 12036)): #0 pthread_cond_wait () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:162 #1 0x7f23f257d0cd in WTF::TCMalloc_PageHeap::scavengerThread (this=0x7f23f2f40200 WTF::pageheap_memory) at wtf/FastMalloc.cpp:2495 #2 0x7f23f257d1d9 in WTF::TCMalloc_PageHeap::runScavengerThread (context=optimized out) at wtf/FastMalloc.cpp:1618 #3 0x7f23edc18fea in start_thread (arg=0x7f23dbdee700) at pthread_create.c:305 #4 0x7f23f32a1fdd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:115 Thread 3 (Thread 0x7f23db4d5700 (LWP 12037)): #0 0x7f23f32990ef in __GI___poll (fds=optimized out, nfds=optimized out, timeout=optimized out) at ../sysdeps/unix/sysv/linux/poll.c:87 #1 0x7f23ecbe8af4 in g_main_context_poll (n_fds=1, fds=0x7f23d40029c0, timeout=-1, context=0x7f23d40009a0, priority=optimized out) at gmain.c:3584 #2 g_main_context_iterate (context=context@entry=0x7f23d40009a0, block=block@entry=1, dispatch=dispatch@entry=1, self=optimized out) at gmain.c:3285 #3 0x7f23ecbe8c14 in g_main_context_iteration (context=0x7f23d40009a0, may_block=1) at gmain.c:3351 #4 0x7f23f46993c6 in QEventDispatcherGlib::processEvents (this=0x7f23d40008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:426 #5 0x7f23f466a62f in QEventLoop::processEvents (this=this@entry=0x7f23db4d4e70, flags=...) at kernel/qeventloop.cpp:149 #6 0x7f23f466a8b8 in QEventLoop::exec (this=0x7f23db4d4e70, flags=...) at kernel/qeventloop.cpp:204 #7 0x7f23f456c2a0 in QThread::exec (this=optimized out) at thread/qthread.cpp:542 #8 0x7f23f456f26c in QThreadPrivate::start (arg=0xd8a890) at thread/qthread_unix.cpp:338 #9 0x7f23edc18fea in start_thread (arg=0x7f23db4d5700) at pthread_create.c:305 #10 0x7f23f32a1fdd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:115 Thread 2 (Thread 0x7f238e86e700 (LWP 12231)): #0 0x7f23f32990ef in __GI___poll (fds=optimized out, nfds=optimized out, timeout=optimized out) at ../sysdeps/unix/sysv/linux/poll.c:87 #1 0x7f23ecbe8af4 in g_main_context_poll (n_fds=1, fds=0x7f2388001300, timeout=-1, context=0x7f2388007fd0, priority=optimized out) at gmain.c:3584 #2 g_main_context_iterate (context=context@entry=0x7f2388007fd0, block=block@entry=1, dispatch=dispatch@entry=1, self=optimized out) at gmain.c:3285 #3 0x7f23ecbe8c14 in g_main_context_iteration (context=0x7f2388007fd0, may_block=1) at gmain.c:3351 #4 0x7f23f46993c6 in QEventDispatcherGlib::processEvents (this=0x7f2388008390, flags=...) at kernel/qeventdispatcher_glib.cpp:426 #5 0x7f23f466a62f in QEventLoop::processEvents (this=this@entry=0x7f238e86de40, flags=...) at kernel/qeventloop.cpp:149 #6 0x7f23f466a8b8 in QEventLoop::exec (this=0x7f238e86de40, flags=...) at kernel/qeventloop.cpp:204 #7 0x7f23f456c2a0 in QThread::exec (this=optimized out) at thread/qthread.cpp:542 #8 0x7f23f464b1ff in QInotifyFileSystemWatcherEngine::run (this=0x1956180) at io/qfilesystemwatcher_inotify.cpp:256 #9 0x7f23f456f26c in QThreadPrivate::start (arg=0x1956180) at thread/qthread_unix.cpp:338 #10 0x7f23edc18fea in start_thread (arg=0x7f238e86e700) at pthread_create.c:305 #11 0x7f23f32a1fdd in clone () at
[Akonadi] [Bug 318389] After performing search across several imap accounts, virtuoso has high cpu and won't stop
https://bugs.kde.org/show_bug.cgi?id=318389 Sven Eden sven.e...@gmx.de changed: What|Removed |Added CC||sven.e...@gmx.de --- Comment #4 from Sven Eden sven.e...@gmx.de --- (In reply to comment #3) Update: disabling email indexing in nepomuk and force-close virtuoso-t resolves the issue. But as soon as I re-enable email indexing in nepomuk, the problem starts again. Did you have a search folder in kmail with a very high e-mail count? I had this (over 10,000 hits) when I messed up an e-mail search. After removing the Last search folder, nepomuk went silent. (However, since then nepomuk starts several virtuoso-t instances which use ~50% of my 4GB RAM. No idea why.) -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Akonadi] [Bug 288268] imap agents crash when network connection gets closed
https://bugs.kde.org/show_bug.cgi?id=288268 Sven Eden sven.e...@gmx.de changed: What|Removed |Added CC||sven.e...@gmx.de --- Comment #45 from Sven Eden sven.e...@gmx.de --- Unfortunately this fix in 4.10.1 means, that whenever the slightest problem on the net occurs, my IMAP accounts produce four notifications: Name: Connection lost KMail: Connection lost Name: killed Name: killed Then I have to restart the whole of akonadi or I have to restart the agent in akonadi console multiple times until it gets back online. Happens whenever: Downloading one E-Mail. Before 4.10.1 this did not happen. -- You are receiving this mail because: You are on the CC list for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 294690] Kmail/akonadi creates duplicate messages with slow IMAP connections
https://bugs.kde.org/show_bug.cgi?id=294690 --- Comment #4 from Sven Eden sven.e...@gmx.de --- I just have the duplication issue again. The message reads. (translated from german): - The UID of the newly created message on the server can not be determined - The source of the mails are all equal except the following detail: Every duplicate has the following lines preceding the original header: - X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on sed-notebook.havi.de X-Spam-Status: No, score=0.0 required=5.0 tests=HTML_MESSAGE,T_DKIM_INVALID autolearn=ham version=3.3.2 X-Virus-Flag: no X-Virus-Flag: no - And every further copy has one additional line reading X-Virus-Flag: no Further the Header items have no line breaks any more. As an example the field Content-Type changes from - Content-Type: multipart/alternative; boundary0431793831243792098== - to - Content-Type: multipart/alternative; boundary0431793831243792098== - I have no idea whether this is important. But I shall add that I used both ClamAV and SpamAssassin with Thunderbird, too, and did not see that problem. (Thunderbird has other very serious problems, so it is no option any more.) -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 294690] Kmail/akonadi creates duplicate messages with slow IMAP connections
https://bugs.kde.org/show_bug.cgi?id=294690 --- Comment #5 from Sven Eden sven.e...@gmx.de --- Sorry for the double post, but I didn't see this before and want to give as much detail as possible. There is another change in the header of the duplicates. The first duplicate reads as above, but all that follow have a different second line: - X-Spam-Status: No, score=0.0 required=5.0 tests=HTML_MESSAGE,T_DKIM_INVALID autolearn=unavailable version=3.3.2 - The change is from autolearn=ham to autolearn=unavailable. -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 294690] Kmail/akonadi creates duplicate messages with slow IMAP connections
https://bugs.kde.org/show_bug.cgi?id=294690 Sven Eden sven.e...@gmx.de changed: What|Removed |Added CC||sven.e...@gmx.de --- Comment #3 from Sven Eden sven.e...@gmx.de --- I can confirm this when using an old IMAP server at work. POP3 works flawlessly. But When a new message arrives on the IMAP server, it is received once, and then again every few seconds. all accompanied by a system notification: save failed. server replied BAD Error AXXX in IMAP command UID: invalid arguments with XXX raised by one with each duplication. After some iterations the senders mail adress gets lost in the duplicates, then later the sending date. To stop this I have to switch kmail to offline, log in via web interface (Horde Mail) and manually delete all but the original mail from the server. Used here is KDE-4.9.3. Btw.: I am the only one around here using kmail, and I am the only one having this problem. When I use the very same account with Thunderbird, no duplication ever happens. -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 284274] kmail2 isn't able to send encrypted emails
https://bugs.kde.org/show_bug.cgi?id=284274 --- Comment #11 from Sven Eden sven.e...@gmx.de --- Just a little update: I have completely deleted everything from nepomuk and akonadi (after backing up my e-mails, calendars, filters and so on of course) and recreated everything from scratch. The problem remains. To send an e-mail I have to not only wait, but to restart different akonadi agents until it works. This is how I fixed it: I now have not only disabled automatic encryption, but automatic signing, too. Now all e-mails get sent without any problems. Unfortunately it is very important for some recipients that my e-mails are signed, so I do hope that this bug will be fixed somewhere in the not-so-far future. Further: I have tried to debug this using the akonadi-console with enabled debugger. Before the mentioned error window pops up, the log looks fine. There is nothing failing. So it seems to be a problem somewhere between the composer and the key management. But I do not really know, I am, to be honest, completely at sea here. -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 284274] kmail2 isn't able to send encrypted emails
https://bugs.kde.org/show_bug.cgi?id=284274 --- Comment #10 from Sven Eden sven.e...@gmx.de --- (In reply to comment #9) After disabling both and restarting kontact, I do not get this error again. Which was wrong. After another reboot the error is back although auto encryption is disabled. Automatic signing is enabled but was never an issue. -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 295795] Kontact (Kmail) crashes when typing in subject or body field of a new mail
https://bugs.kde.org/show_bug.cgi?id=295795 Sven Eden sven.e...@gmx.de changed: What|Removed |Added CC||sven.e...@gmx.de -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 295795] Kontact (Kmail) crashes when typing in subject or body field of a new mail
https://bugs.kde.org/show_bug.cgi?id=295795 --- Comment #4 from Sven Eden sven.e...@gmx.de --- Created attachment 69804 -- https://bugs.kde.org/attachment.cgi?id=69804action=edit New crash information added by DrKonqi kontact (4.8.0) on KDE Platform 4.8.1 (4.8.1) using Qt 4.8.0 - What I was doing when the application crashed: Opened kontact, started to write a new e-mail. The crash happens when I am either writing into the subject or the text field. - Custom settings: I just changed my language settings from German to American English in KDE Systemsettings to track down a different issue the german error text yields no hits in common web search engines. Therefore my country setting is Germany, Preferred Languages has American English first. Before I made this change kontact never crashed. - Test 1: I have pushed German back up to first place. Kontact now starts in german and I can finish my e-mail. Everything is fine again. - Test 2: I have pushed American English up to first place and this time changed the country settings to USA. Kontact now starts in english, I start a new mail, enter recipient and subject, hit tab (or click into the message box, it doesn't matter) and get the same crash again. - Test 3: This time I removed German from the preferred languages side and added British English as second. Kontact starts, I can write and send e-mail, everything is fine. - Test 4: After removing British English from the Preferred Languages, the crash is back. - Test 5: After swapping American and British English, the crash is still there. -- It seems there is a problem when eitehr British or American english is alone without the other chosen as the preferred language in Systemsettings-Country/RegionLanguage -- Backtrace (Reduced): #6 0x7f0bd45b64d3 in eventFilter (e=0x7fff87e3aa60, o=0x145f3b0, this=0x12d9820) at /home/portage/kde-base/kdelibs-4.8.1-r1/work/kdelibs-4.8.1/kdeui/sonnet/highlighter.cpp:355 #7 Sonnet::Highlighter::eventFilter (this=0x12d9820, o=0x145f3b0, e=0x7fff87e3aa60) at /home/portage/kde-base/kdelibs-4.8.1-r1/work/kdelibs-4.8.1/kdeui/sonnet/highlighter.cpp:337 #8 0x7f0bd3ab72b8 in QCoreApplicationPrivate::sendThroughObjectEventFilters (this=optimized out, receiver=0x145f3b0, event=0x7fff87e3aa60) at kernel/qcoreapplication.cpp:986 #9 0x7f0bd2e58e3f in notify_helper (e=0x7fff87e3aa60, receiver=0x145f3b0, this=0xb597a0) at kernel/qapplication.cpp:4546 #10 QApplicationPrivate::notify_helper (this=0xb597a0, receiver=0x145f3b0, e=0x7fff87e3aa60) at kernel/qapplication.cpp:4522 -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 284274] kmail2 isn't able to send encrypted emails
https://bugs.kde.org/show_bug.cgi?id=284274 Sven Eden sven.e...@gmx.de changed: What|Removed |Added CC||sven.e...@gmx.de --- Comment #9 from Sven Eden sven.e...@gmx.de --- I have this issue since I set kmail2 to automatically encrypt messages if possible and to encrypt messages stored in the sent folder. It never is, because there are only two recipients in my list with keys for encryption, but it seems to affect the whole thing. After disabling both and restarting kontact, I do not get this error again. -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 282076] akonadi imap resource crash (segfault) when trying to sync after DNS went away
https://bugs.kde.org/show_bug.cgi?id=282076 --- Comment #14 from Sven Eden sven eden gmx de 2012-02-20 08:09:41 --- I just tried to have kmail (4.8.0) to crash again, but couldn't reproduce. I changed the nameserver entry in /etc/resolv.conf to something non-existant and fetched mails. I get a message that the pop3 server is not available, but the imap account simply stays silent. No crash anymore! *yay* -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are on the CC list for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 280630] kmail crashes at startup every time [Akonadi::EntityTreeModelPrivate::removeItems, Akonadi::EntityTreeModelPrivate::purgeItems, Akonadi::EntityTreeModel::setData]
https://bugs.kde.org/show_bug.cgi?id=280630 Sven Eden sven.e...@gmx.de changed: What|Removed |Added CC||sven.e...@gmx.de -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 280630] kmail crashes at startup every time [Akonadi::EntityTreeModelPrivate::removeItems, Akonadi::EntityTreeModelPrivate::purgeItems, Akonadi::EntityTreeModel::setData]
https://bugs.kde.org/show_bug.cgi?id=280630 --- Comment #7 from Sven Eden sven eden gmx de 2012-02-17 07:56:24 --- Created an attachment (id=68866) -- (http://bugs.kde.org/attachment.cgi?id=68866) New crash information added by DrKonqi kontact (4.8.0) on KDE Platform 4.8.00 (4.8.0 using Qt 4.8.0 - What I was doing when the application crashed: Started kontact as usual. Akonadi Server was up and running. Note: All reports offered by DrKonqi which had titles looking related where marked as duplicates leading to this report. The Backtrace is different, I just followed the duplication leads. -- Backtrace (Reduced): #6 0x7f14f51a2955 in __GI_raise (sig=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64 #7 0x7f14f51a3dcb in __GI_abort () at abort.c:93 [...] #9 0x7f14f51e25e6 in malloc_printerr (action=3, str=0x7f14f52b9578 double free or corruption (fasttop), ptr=optimized out) at malloc.c:6283 #10 0x7f14f51e64dc in __GI___libc_free (mem=optimized out) at malloc.c:3738 #11 0x7f14f657efac in QString::free (d=0x1f33f60) at tools/qstring.cpp:1232 -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 286307] Kmail crash (QNetworkAccessHttpBackend::replyDownloadMetaData, QNetworkAccessHttpBackend::qt_static_metacall, QObject::event)
https://bugs.kde.org/show_bug.cgi?id=286307 --- Comment #80 from Sven Eden sven eden gmx de 2012-02-02 21:09:08 --- (In reply to comment #74) *** Bug 292990 has been marked as a duplicate of this bug. *** I have a feeling this is either not a duplicate, or I can provide something new. I did not add the latest crash report, because the relevant thread trace looks the same. But I did something I normally do not do, and remembered, that the same action lead to the reporting of Bug 292990. I opened kontact without starting akonadi server first. In earlier versions this was no problem, but here kontact started akonadi, I got some messages about failing agents (I am not at work, so they can't contact various office only sites) and kontact crashed. So, could kontact have a problem there? --- The trace of the relevant thread --- Thread 1 (Thread 0x7f2d34657780 (LWP 10309)): #0 0x7f2d31becd9d in read () at ../sysdeps/unix/syscall-template.S:82 #1 0x7f2d2b7e9600 in read (__nbytes=16, __buf=0x7fff6a2bdb60, __fd=optimized out) at /usr/include/bits/unistd.h:45 #2 g_wakeup_acknowledge (wakeup=0x1d74c10) at gwakeup.c:212 #3 0x7f2d2b7a5519 in g_main_context_check (context=0x1d75860, max_priority=2147483647, fds=0x26f4200, n_fds=14) at gmain.c:2912 #4 0x7f2d2b7a5e02 in g_main_context_iterate (context=0x1d75860, block=1, dispatch=1, self=optimized out) at gmain.c:3086 #5 0x7f2d2b7a62a1 in g_main_context_iteration (context=0x1d75860, may_block=1) at gmain.c:3152 #6 0x7f2d32fbb8ef in QEventDispatcherGlib::processEvents (this=0x1d7a830, flags=optimized out) at kernel/qeventdispatcher_glib.cpp:422 #7 0x7f2d3240b79e in QGuiEventDispatcherGlib::processEvents (this=optimized out, flags=optimized out) at kernel/qguieventdispatcher_glib.cpp:204 #8 0x7f2d32f8fce2 in QEventLoop::processEvents (this=optimized out, flags=...) at kernel/qeventloop.cpp:149 #9 0x7f2d32f8ff24 in QEventLoop::exec (this=0x7fff6a2bdd50, flags=...) at kernel/qeventloop.cpp:201 #10 0x7f2d32f943ab in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1064 #11 0x00403709 in main (argc=1, argv=0x7fff6a2be3f8) at /home/portage/kde-base/kontact-4.8.0/work/kontact-4.8.0/kontact/src/main.cpp:218 --- End of trace --- What is kontact/src/main.cpp doing in line 218 ? -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 292990] New: Kontact crashed right after opening
https://bugs.kde.org/show_bug.cgi?id=292990 Summary: Kontact crashed right after opening Product: kontact Version: unspecified Platform: Compiled Sources OS/Version: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: sven.e...@gmx.de Application: kontact (4.8.0) KDE Platform Version: 4.8.00 (4.8.0 (Compiled from sources) Qt Version: 4.7.4 Operating System: Linux 3.2.1-gentoo-r2 x86_64 Distribution (Platform): Gentoo Packages -- Information about the crash: - What I was doing when the application crashed: Resumed from hibernation, started Kontact, half a second after the window appeared, kontact went away and Dr.Konqi showed up. This is the first time I had such a crash since I started using KDE-4.1. - I just tried to start kontact again, and a window informed me, that it would be running on another display. So I try again after sending this report. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault [Current thread is 1 (Thread 0x7f2d34657780 (LWP 10309))] Thread 5 (Thread 0x7f2d1d1ee700 (LWP 10311)): #0 pthread_cond_wait () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:162 #1 0x7f2d31083b64 in scavengerThread (this=0x7f2d318a74e0) at wtf/FastMalloc.cpp:2378 #2 WTF::TCMalloc_PageHeap::runScavengerThread (context=0x7f2d318a74e0) at wtf/FastMalloc.cpp:1497 #3 0x7f2d2c968f2c in start_thread (arg=0x7f2d1d1ee700) at pthread_create.c:301 #4 0x7f2d31bfa50d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:115 Thread 4 (Thread 0x7f2d1c8ed700 (LWP 10312)): #0 0x7f2d31bf18d3 in __GI___poll (fds=optimized out, nfds=optimized out, timeout=optimized out) at ../sysdeps/unix/sysv/linux/poll.c:87 #1 0x7f2d2b7a5de4 in g_main_context_poll (n_fds=1, fds=0x1d85ed0, timeout=-1, context=0x1d86210, priority=optimized out) at gmain.c:3402 #2 g_main_context_iterate (context=0x1d86210, block=1, dispatch=1, self=optimized out) at gmain.c:3084 #3 0x7f2d2b7a62a1 in g_main_context_iteration (context=0x1d86210, may_block=1) at gmain.c:3152 #4 0x7f2d32fbb946 in QEventDispatcherGlib::processEvents (this=0x1d85ef0, flags=optimized out) at kernel/qeventdispatcher_glib.cpp:424 #5 0x7f2d32f8fce2 in QEventLoop::processEvents (this=optimized out, flags=...) at kernel/qeventloop.cpp:149 #6 0x7f2d32f8ff24 in QEventLoop::exec (this=0x7f2d1c8ece00, flags=...) at kernel/qeventloop.cpp:201 #7 0x7f2d32ea4644 in QThread::exec (this=optimized out) at thread/qthread.cpp:498 #8 0x7f2d32ea6e95 in QThreadPrivate::start (arg=0x1d85250) at thread/qthread_unix.cpp:331 #9 0x7f2d2c968f2c in start_thread (arg=0x7f2d1c8ed700) at pthread_create.c:301 #10 0x7f2d31bfa50d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:115 Thread 3 (Thread 0x7f2d0f8d3700 (LWP 10361)): [KCrash Handler] #6 _int_free (av=0x7f2d1820, p=0x7f2d1801c650) at malloc.c:4892 #7 0x7f2d31b99ff3 in _int_realloc (av=0x7f2d1820, oldp=0x7f2d1801c650, oldsize=80, nb=optimized out) at malloc.c:5341 #8 0x7f2d31b9b649 in __GI___libc_realloc (oldmem=0x7f2d1801c660, bytes=128) at malloc.c:3821 #9 0x7f2d32ea929a in QByteArray::realloc (this=0x7f2d0f8d2640, alloc=96) at tools/qbytearray.cpp:1440 #10 0x7f2d32ea9f01 in QByteArray::append (this=0x7f2d0f8d2640, ba=...) at tools/qbytearray.cpp:1584 #11 0x7f2d32f50af2 in operator+= (a=..., this=0x7f2d0f8d2640) at ../../include/QtCore/../../src/corelib/tools/qbytearray.h:492 #12 QUrlPrivate::toEncoded (this=0x7f2d0f8d26d0, options=...) at io/qurl.cpp:3962 #13 0x7f2d32f502be in QUrlPrivate::normalized (this=0x2438740) at io/qurl.cpp:4059 #14 0x7f2d32f51975 in QUrl::operator== (this=0x7f2d0f8d29d0, url=...) at io/qurl.cpp:5959 #15 0x7f2d2a5add6d in Nepomuk::ResourceData::updateKickOffLists (this=0x7f2d1801a710, prop=..., v=...) at /home/portage/kde-base/kdelibs-4.8.0-r1/work/kdelibs-4.8.0/nepomuk/core/resourcedata.cpp:675 #16 0x7f2d2a5ae632 in Nepomuk::ResourceData::load (this=0x7f2d1801a710) at /home/portage/kde-base/kdelibs-4.8.0-r1/work/kdelibs-4.8.0/nepomuk/core/resourcedata.cpp:392 #17 0x7f2d2a5aec2c in Nepomuk::ResourceData::property (this=0x7f2d1801a710, uri=...) at /home/portage/kde-base/kdelibs-4.8.0-r1/work/kdelibs-4.8.0/nepomuk/core/resourcedata.cpp:240 #18 0x7f2d2a5c25f3 in Nepomuk::Resource::property (this=0x7f2d0f8d2cf0, uri=...) at /home/portage/kde-base/kdelibs-4.8.0-r1/work/kdelibs-4.8.0/nepomuk/core/resource.cpp:301 #19 0x7f2d138e5f2a in MessageCore::NepomukResourceRetrieverRunnable::run (this=0x27e18e0) at /home/portage/kde-base/kdepim-common-libs-4.8.0-r1/work/kdepim-common-libs-4.8.0/messagecore/asyncnepomukresourceretriever.cpp:47 #20 0x7f2d32e9bf28 in QThreadPoolThread::run (this=0x24c88e0) at concurrent/qthreadpool.cpp:106 #21 0x7f2d32ea6e95 in QThreadPrivate::start
[Bug 279800] akonadi_nepomuk_email_feeder uses huge amounts of memory
https://bugs.kde.org/show_bug.cgi?id=279800 --- Comment #11 from Sven Eden sven eden gmx de 2011-11-12 12:20:49 --- (In reply to comment #8) What version of soprano are you using? (In reply to comment #10) soprano-daemon 2.7.0+dfsg.1-0ubuntu2 That may be the problem. The current version is 2.7.3, which is the version recommended for KDE 4.7.3. There have apparently been major improvements from 2.7.0 to 2.7.3, including performance and indexing improvements. You should probably see if you can get the kubuntu devs to upgrade to the current version. soprano-daemon 2.7.0+dfsg.1-0ubuntu2 I do not know whether this is the culprit. As I have stated, I have no longer any problem with the e-mail-feeder, and I have soprano-2.7.0 (compiled from source) installed. Further (might be) related packages: clucene-0.9.21b raptor-2.0.4 rasqal-0.9.27 redland-1.0.14 virtuoso-odbc-6.1.3 virtuoso-server-6.1.3 strigi-0.7.6 nepomuk-4.7.3 And strigi is the only package that got updated with the kde upgrade to 4.7.3 on my laptop. But I can't say from which version, sorry. -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are on the CC list for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 279800] akonadi_nepomuk_email_feeder uses huge amounts of memory
https://bugs.kde.org/show_bug.cgi?id=279800 --- Comment #5 from Sven Eden sven eden gmx de 2011-11-05 11:17:00 --- I must say, that upgrading to KDE-4.7.3 seems to have changed the reported behavior. The stats from my last post no read: PID USER PR NI VIRT RES SHR S %CPU %MEMTIME+ COMMAND 8517 sed 20 0 403m 36m 26m S0 1.0 0:00.98 akonadi_nepomuk The PID is the one from: sed@sed-notebook ~ $ ps -efa | grep email_feeder sed 8517 8486 0 10:44 ?00:00:01 /usr/bin/akonadi_nepomuk_email_feeder --identifier akonadi_nepomuk_email_feeder Therefore this bug/issue might be resolved now, but I'll keep an eye on my system. -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are on the CC list for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 279800] akonadi_nepomuk_email_feeder uses huge amounts of memory
https://bugs.kde.org/show_bug.cgi?id=279800 Sven Eden sven.e...@gmx.de changed: What|Removed |Added CC||sven.e...@gmx.de --- Comment #3 from Sven Eden sven eden gmx de 2011-09-27 13:14:49 --- I would be happy if the email_feeder *only* ate 1.5GB... Here is what top says (and htop confirms that): PID USER PR NI VIRT RES SHR S %CPU %MEMTIME+ COMMAND 4571 sed 20 0 4879m 1.9g 2836 S0 52.7 0:36.26 /usr/bin/akonadi_nepomuk_email_feeder --identifier akonadi_nepomuk_email_feeder Right now it does not use any CPU, but the memory isn't freed, and I have ~300MB RAM and ~1.7GB swap remaining (from 4GB + 6GB!). Why does the email_feeder need such a massive amount of ram? My specs: Gentoo Linux, everything built from source. QT-4.7.4 KDE-4.7.1 strigi-0.7.6 (if that matters.) -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are on the CC list for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 282076] akonadi imap resource crash (segfault) when trying to sync after DNS went away
https://bugs.kde.org/show_bug.cgi?id=282076 --- Comment #2 from Sven Eden sven eden gmx de 2011-09-18 11:41:54 --- It's the old companies mail server, using squirrel if I am not mistaken. I'll look into it on Monday. I _hope_ I can reproduce the error by simply altering /etc/resolv.conf to something unresponsive, but that's a shot in the dark. I have never - in over three years - seen the dns servers going down, but maybe it works out that way. -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are on the CC list for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 282076] New: akonadi imap resource crash (segfault) when trying to sync after DNS went away
https://bugs.kde.org/show_bug.cgi?id=282076 Summary: akonadi imap resource crash (segfault) when trying to sync after DNS went away Product: Akonadi Version: 4.7 Platform: Compiled Sources OS/Version: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: IMAP resource AssignedTo: er...@kde.org ReportedBy: sven.e...@gmx.de CC: vkra...@kde.org, kdepim-bugs@kde.org Application: akonadi_imap_resource (4.7) KDE Platform Version: 4.7.1 (4.7.1) (Compiled from sources) Qt Version: 4.7.3 Operating System: Linux 3.0.4-gentoo x86_64 Distribution (Platform): Gentoo Packages -- Information about the crash: - What I was doing when the application crashed: Working. Kmail2 runs on another screen. Suddenly the crash report tool popped up. But: While trying to log in to bugs.kde.org I noticed, that the DNS servers have gone out for lunch or something. My internet connection is working fine (I am currently logged into a remote server via SSH located about 600 miles from here) but bot DNS servers don't pong any more. I have searched for other reports, but they all have actions involved and their signal is Aborted while this is a Segmentation Fault. Thus I've chosen to open a new report, I guess they are not related. -- Backtrace: Application: Akonadi Resource (akonadi_imap_resource), signal: Segmentation fault [Current thread is 1 (Thread 0x7f04d1b8b780 (LWP 3377))] Thread 3 (Thread 0x7f04c71ce700 (LWP 6093)): #0 0x0035c2611d2b in dl_open_worker () from /lib64/ld-linux-x86-64.so.2 #1 0x0035c260da26 in _dl_catch_error () from /lib64/ld-linux-x86-64.so.2 #2 0x0035c261195a in _dl_open () from /lib64/ld-linux-x86-64.so.2 #3 0x0035c3f0d7b0 in do_dlopen () from /lib64/libc.so.6 #4 0x0035c260da26 in _dl_catch_error () from /lib64/ld-linux-x86-64.so.2 #5 0x0035c3f0d84f in dlerror_run () from /lib64/libc.so.6 #6 0x0035c3f0d8b7 in __libc_dlopen_mode () from /lib64/libc.so.6 #7 0x0035c3ee9105 in init () from /lib64/libc.so.6 #8 0x0035c4a0caf3 in pthread_once () from /lib64/libpthread.so.0 #9 0x0035c3ee91fc in backtrace () from /lib64/libc.so.6 #10 0x0035c3e6d7a6 in __libc_message () from /lib64/libc.so.6 #11 0x0035c3e72c15 in malloc_printerr () from /lib64/libc.so.6 #12 0x0035c3e77b4c in free () from /lib64/libc.so.6 #13 0x003c6aeb904c in QString::free(QString::Data*) () from /usr/lib64/qt4/libQtCore.so.4 #14 0x003c6aebd793 in QString::vsprintf(char const*, __va_list_tag*) () from /usr/lib64/qt4/libQtCore.so.4 #15 0x003c6ae6a8b9 in qt_message(QtMsgType, char const*, __va_list_tag*) () from /usr/lib64/qt4/libQtCore.so.4 #16 0x003c6ae6b115 in qWarning(char const*, ...) () from /usr/lib64/qt4/libQtCore.so.4 #17 0x003c6af8836c in socketNotifierSourceCheck(_GSource*) () from /usr/lib64/qt4/libQtCore.so.4 #18 0x0035c7e4249e in g_main_context_check () from /usr/lib64/libglib-2.0.so.0 #19 0x0035c7e42daa in g_main_context_iterate.clone.6 () from /usr/lib64/libglib-2.0.so.0 #20 0x0035c7e432bd in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #21 0x003c6af8890f in QEventDispatcherGlib::processEvents(QFlagsQEventLoop::ProcessEventsFlag) () from /usr/lib64/qt4/libQtCore.so.4 #22 0x003c6af5cd42 in QEventLoop::processEvents(QFlagsQEventLoop::ProcessEventsFlag) () from /usr/lib64/qt4/libQtCore.so.4 #23 0x003c6af5cf84 in QEventLoop::exec(QFlagsQEventLoop::ProcessEventsFlag) () from /usr/lib64/qt4/libQtCore.so.4 #24 0x003c6ae715b4 in QThread::exec() () from /usr/lib64/qt4/libQtCore.so.4 #25 0x0035f723c113 in KIMAP::SessionThread::run (this=0x28d7a00) at /var/tmp/portage/kde-base/kdepimlibs-4.7.1/work/kdepimlibs-4.7.1/kimap/sessionthread.cpp:169 #26 0x003c6ae73e05 in QThreadPrivate::start(void*) () from /usr/lib64/qt4/libQtCore.so.4 #27 0x0035c4a06d4c in start_thread () from /lib64/libpthread.so.0 #28 0x0035c3ed6ded in clone () from /lib64/libc.so.6 Thread 2 (Thread 0x7f04cd3de700 (LWP 9305)): #0 0x0035c3ece173 in poll () from /lib64/libc.so.6 #1 0x0035c7e42d8d in g_main_context_iterate.clone.6 () from /usr/lib64/libglib-2.0.so.0 #2 0x0035c7e432bd in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x003c6af88966 in QEventDispatcherGlib::processEvents(QFlagsQEventLoop::ProcessEventsFlag) () from /usr/lib64/qt4/libQtCore.so.4 #4 0x003c6af5cd42 in QEventLoop::processEvents(QFlagsQEventLoop::ProcessEventsFlag) () from /usr/lib64/qt4/libQtCore.so.4 #5 0x003c6af5cf84 in QEventLoop::exec(QFlagsQEventLoop::ProcessEventsFlag) () from /usr/lib64/qt4/libQtCore.so.4 #6 0x003c6ae715b4 in QThread::exec() () from /usr/lib64/qt4/libQtCore.so.4 #7 0x0035f723c113 in KIMAP::SessionThread::run (this=0x28c61d0) at /var/tmp/portage/kde-base/kdepimlibs-4.7.1/work/kdepimlibs-4.7.1/kimap/sessionthread.cpp:169 #8
[Bug 272525] Kontact crashed when resuming laptop from standby
https://bugs.kde.org/show_bug.cgi?id=272525 --- Comment #9 from Sven Eden sven eden gmx de 2011-08-19 14:51:04 --- (In reply to comment #2) I'll update to 4.7.0 tonight, let's see whether this happens ever again... Until now it never happened again after updating to 4.7.0. Note: I am putting this laptop into standby at least six times a day. -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 272525] Kontact crashed when resuming laptop from standby
https://bugs.kde.org/show_bug.cgi?id=272525 Sven Eden sven.e...@gmx.de changed: What|Removed |Added CC||sven.e...@gmx.de -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 272525] Kontact crashed when resuming laptop from standby
https://bugs.kde.org/show_bug.cgi?id=272525 --- Comment #2 from Sven Eden sven eden gmx de 2011-07-29 17:51:41 --- Created an attachment (id=62315) -- (http://bugs.kde.org/attachment.cgi?id=62315) New crash information added by DrKonqi kontact (4.6.1) on KDE Platform 4.6.5 (4.6.5) using Qt 4.7.3 - What I was doing when the application crashed: Resumed Laptop from Standby. Opened Kontact. The first (and last) action was to try to fold a subfolder I didn't want to see. Kontact immediately crashed. This was the first time this happened ever. kdepim is 4.6.1, KDE is 4.6.5 I'll update to 4.7.0 tonight, let's see whether this happens ever again... -- Backtrace (Reduced): #6 0x7fa51c37f432 in KSelectionProxyModelPrivate::mapTopLevelToSource(int, int) const () from /usr/lib64/libkdeui.so.5 #7 0x7fa51c37f6cf in KSelectionProxyModel::mapToSource(QModelIndex const) const () from /usr/lib64/libkdeui.so.5 #8 0x7fa51c37a843 in KSelectionProxyModel::data(QModelIndex const, int) const () from /usr/lib64/libkdeui.so.5 #9 0x7fa51777ec1c in Akonadi::EntityMimeTypeFilterModel::filterAcceptsRow(int, QModelIndex const) const () from /usr/lib64/libakonadi-kde.so.4 #10 0x7fa51bc18411 in QSortFilterProxyModelPrivate::source_items_inserted(QModelIndex const, int, int, Qt::Orientation) () from /usr/lib64/qt4/libQtGui.so.4 -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
