| Summary: | Kontact 4.6.41 crashes upon start | ||
|---|---|---|---|
| Product: | [Applications] kmail2 | Reporter: | Gerhard Riener <gerhard.riener> |
| Component: | sieve | Assignee: | kdepim bugs <kdepim-bugs> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | crash | CC: | andrew.n.rainey, aspotashev, chrigi_1, juergen, kde, leon.maurer, mchugh19, smartins, tokoe |
| Priority: | NOR | Keywords: | investigated, triaged |
| Version: | 2.0.89 | ||
| Target Milestone: | --- | ||
| Platform: | openSUSE | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
| Attachments: |
New crash information added by DrKonqi
valgrind output New crash information added by DrKonqi New crash information added by DrKonqi |
||
|
Description
Gerhard Riener
2011-02-11 19:32:19 UTC
*** Bug 269923 has been marked as a duplicate of this bug. *** *** Bug 270556 has been marked as a duplicate of this bug. *** I've seen this too. Created attachment 59061 [details]
New crash information added by DrKonqi
kmail (2.0.95) on KDE Platform 4.6.2 (4.6.2) using Qt 4.7.2
- What I was doing when the application crashed:
I made a fresh install of kdepim kdepim 4.5.95-1 from the kde-unstable repository.
I did not have a prior install of the old kdepim, so my home was completeley clean.
I first added an IMAP accound and enabled the ssl and disconnected flags on the account. Then I tried to sync the accound which resulted in kmail shutting down with a message like: "Failed to fetch the resource collection".
From then on kmail crashes on every start with the attached backtrace.
-- Backtrace (Reduced):
#6 0x00007f924490ec76 in QVariant::QVariant(QVariant const&) () from /usr/lib/libQtCore.so.4
#7 0x00007f92420ece87 in QDBusPendingReplyData::argumentAt(int) const () from /usr/lib/libQtDBus.so.4
#8 0x00007f923e5aafa8 in KSieveUi::Util::findSieveUrlForAccount(QString const&) () from /usr/lib/libksieveui.so.4
#9 0x00007f923e5afb6a in KSieveUi::Vacation::findURL() const () from /usr/lib/libksieveui.so.4
#10 0x00007f923e5afcab in KSieveUi::Vacation::Vacation(QObject*, bool, char const*) () from /usr/lib/libksieveui.so.4
Can you get a valgrind report ? Created attachment 59073 [details]
valgrind output
just ran "valgrind -v --log-file=kmail2.txt kmail".
The error message saying something like "Failed to fetch the resource collection", popped up quickly again before crashing.
output on the console:
[chrigi@myhost ~]$ valgrind -v --log-file=kmail2.txt kmail
kmail2(12694)/libakonadi Akonadi::SpecialCollectionsRequestJob::slotResult: Failed SpecialCollectionsRequestJob::slotResult "Unknown error. (Failed to fetch the resource collection.)"
kmail2(12694) MailCommon::Kernel::emergencyExit: "KMail encountered a fatal error and will terminate now.
The error was:
Failed to fetch the resource collection."
unnamed app(12693): Communication problem with "kmail2" , it probably crashed.
Error message was: "org.freedesktop.DBus.Error.NoReply" : " "Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken." "
==12694== Invalid read of size 8 ==12694== at 0x6DC2C76: QVariant::QVariant(QVariant const&) (in /usr/lib/libQtCore.so.4.7.2) ==12694== by 0x95BAE86: QDBusPendingReplyData::argumentAt(int) const (in /usr/lib/libQtDBus.so.4.7.2) ==12694== by 0xD0BCFA7: KSieveUi::Util::findSieveUrlForAccount(QString const&) (in /usr/lib/libksieveui.so.4.6.0) ==12694== by 0xD0C1B69: KSieveUi::Vacation::findURL() const (in /usr/lib/libksieveui.so.4.6.0) ==12694== by 0xD0C1CAA: KSieveUi::Vacation::Vacation(QObject*, bool, char const*) (in /usr/lib/libksieveui.so.4.6.0) ==12694== by 0x5C90EC6: KMMainWidget::slotCheckVacation() (in /usr/lib/libkmailprivate.so.4.6.0) ==12694== by 0x5CAA07C: KMMainWidget::qt_metacall(QMetaObject::Call, int, void**) (in /usr/lib/libkmailprivate.so.4.6.0) ==12694== by 0x6DB7C69: QObject::event(QEvent*) (in /usr/lib/libQtCore.so.4.7.2) ==12694== by 0x61B9A9C: QWidget::event(QEvent*) (in /usr/lib/libQtGui.so.4.7.2) ==12694== by 0x61686A3: QApplicationPrivate::notify_helper(QObject*, QEvent*) (in /usr/lib/libQtGui.so.4.7.2) ==12694== by 0x616D269: QApplication::notify(QObject*, QEvent*) (in /usr/lib/libQtGui.so.4.7.2) ==12694== by 0x5069D35: KApplication::notify(QObject*, QEvent*) (in /usr/lib/libkdeui.so.5.6.0) ==12694== Address 0x0 is not stack'd, malloc'd or (recently) free'd (In reply to comment #6) > The error message saying something like "Failed to fetch the resource > collection", popped up quickly again before crashing. Regarding this message, can you stop akonadi and then check if you have a stale mysql process ? (In reply to comment #8) > (In reply to comment #6) > > The error message saying something like "Failed to fetch the resource > > collection", popped up quickly again before crashing. > > Regarding this message, can you stop akonadi and then check if you have a stale > mysql process ? after stopping akonadi with "akonadictl stop" all akonadi and mysql processes are gone from the output of "ps aux". Created attachment 59207 [details]
New crash information added by DrKonqi
kmail (2.0.89) on KDE Platform 4.6.2 (4.6.2) using Qt 4.7.2
- What I was doing when the application crashed:
Same as the reporter, started kmail2 and experienced the crash.
-- Backtrace (Reduced):
#6 Private (this=0x7fffc6f59630, p=...) at ../../include/QtCore/../../src/corelib/kernel/qvariant.h:360
#7 QVariant::QVariant (this=0x7fffc6f59630, p=...) at kernel/qvariant.cpp:1419
#8 0x00007f3926047d18 in QDBusPendingReplyData::argumentAt (this=0x7fffc6f59c40, index=0) at qdbuspendingreply.cpp:270
#9 0x00007f39224faf86 in argumentAt<0> (identifier=<value optimized out>) at /usr/include/qt4/QtDBus/qdbuspendingreply.h:176
#10 operator QDBusPendingReplyTypes::Select<0, QString, void, void, void, void, void, void, void>::Type (identifier=<value optimized out>) at /usr/include/qt4/QtDBus/qdbuspendingreply.h:186
I just installed the master version of kdepim, and I ran into the same crash again, but this time the backtrace is a bit more useful. #6 0x00007f3b6238dc76 in QVariant::QVariant(QVariant const&) () from /usr/lib/libQtCore.so.4 #7 0x00007f3b626fde87 in QDBusPendingReplyData::argumentAt(int) const () from /usr/lib/libQtDBus.so.4 #8 0x00007f3b5c3b13b1 in QDBusPendingReply<QString, void, void, void, void, void, void, void>::argumentAt<0> (this=0x7fff0cfd2c80) at /usr/include/QtDBus/qdbuspendingreply.h:176 #9 0x00007f3b5c3b0ebc in QDBusPendingReply<QString, void, void, void, void, void, void, void>::operator QDBusPendingReplyTypes::Select<0, QString, void, void, void, void, void, void, void>::Type (this=0x7fff0cfd2c80) at /usr/include/QtDBus/qdbuspendingreply.h:186 #10 0x00007f3b5c3af644 in KSieveUi::Util::findSieveUrlForAccount (identifier=...) at /home/chrigi/devel/kde/kdepim/libksieve/ksieveui/util.cpp:108 #11 0x00007f3b5c3b46a0 in KSieveUi::Vacation::findURL (this=0x1539440) at /home/chrigi/devel/kde/kdepim/libksieve/ksieveui/vacation.cpp:493 #12 0x00007f3b5c3b3be3 in KSieveUi::Vacation::Vacation (this=0x1539440, parent=0x1247fc0, checkOnly=true, name=0x0) at /home/chrigi/devel/kde/kdepim/libksieve/ksieveui/vacation.cpp:426 #13 0x00007f3b66b139b5 in KMMainWidget::slotCheckVacation (this=0x1247fc0) at /home/chrigi/devel/kde/kdepim/kmail/kmmainwidget.cpp:2269 #14 0x00007f3b66b06847 in KMMainWidget::qt_metacall (this=0x1247fc0, _c=QMetaObject::InvokeMetaMethod, _id=67, _a=0x1420270) at /home/chrigi/devel/kde/build/kdepim/kmail/kmmainwidget.moc:409 #15 0x00007f3b62382c6a in QObject::event(QEvent*) () from /usr/lib/libQtCore.so.4 and on the console: [chrigi@myhost ~]$ kmail kmail2(2220)/libakonadi: Unable to obtain agent type for default resource agent configuration "/opt/devel/global/share/apps/akonadi/firstrun/defaultnotebook" kmail2(2220)/kdepimlibs (mailtransport) MailTransport::TransportManagerPrivate::fillTypes: Found Akonadi type "Dummy MailTransport Resource" kmail2(2220)/kdepimlibs (mailtransport) MailTransport::TransportManagerPrivate::fillTypes: Have SMTP, Sendmail, and 1 Akonadi types. kmail2(2220)/kdecore (KConfigSkeleton) KCoreConfigSkeleton::writeConfig: [chrigi@myhost ~]$ *** KMail got signal 11 (Exiting) *** Dead letters dumped. KCrash: Application 'kmail' crashing... KCrash: Attempting to start /usr/lib/kde4/libexec/drkonqi from kdeinit sock_file=/home/chrigi/.kde4/socket-myhost/kdeinit4__0 Btw. this should probably be added to the blocker list, no? It seems the reason for this crash was a broken "Local Folders" resource. The resource was configured to ".cur" instead of "~/.local/share/local-mail" by default (maybe from the previously installed betas). Reconfiguring it correctly didn't work immediately, but after a 'killall -u $USER', which kills everything of the user, I only had to toggle the resource online and now kmail2 works perfectly. Can the other reporters reproduce the fix mentioned in comment #12 ? I had the same issue. The local folders resource had an empty path. After setting it in the Akonadi manager, the crash is gone (Alas, I cannot say that "now kmail2 works perfectly". The overall performance impact of the new PIM is way too high for me to use this productively). *** Bug 279455 has been marked as a duplicate of this bug. *** My bug has been marked as a duplicate of this but, but it does not appear that my "Local Folders" resource has an empty path. It was set to "/home/leon/.local/share/local-mail"; the little window where you can set the path notes that "The selected path is a valid Maildir." Are there any other fixes I should try? It looks like my crash is gone after Kubuntu updated some packages. The current Archlinux package doesn't seem to have that bug anymore either. Created attachment 62877 [details]
New crash information added by DrKonqi
kmail (4.7.0 ) on KDE Platform 4.7.00 (4.7.0) using Qt 4.7.3
- What I was doing when the application crashed:
I have the same problem in kmail after upgrading kdepim to 4.7.0
-- Backtrace (Reduced):
#7 0x02a0c7bb in QVariant::QVariant(QVariant const&) () from /usr/lib/libQtCore.so.4
#8 0x07b6c8c5 in QDBusPendingReplyData::argumentAt(int) const () from /usr/lib/libQtDBus.so.4
#9 0x09c0c30c in KSieveUi::Util::findSieveUrlForAccount(QString const&) () from /usr/lib/libksieveui.so.4
#10 0x09c102d2 in KSieveUi::Vacation::findURL() const () from /usr/lib/libksieveui.so.4
#11 0x09c104b1 in KSieveUi::Vacation::Vacation(QObject*, bool, char const*) () from /usr/lib/libksieveui.so.4
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! |