Bug 305454 - Crash on "Update address book folder" (kolabproxy/akonadi)
Summary: Crash on "Update address book folder" (kolabproxy/akonadi)
Status: RESOLVED FIXED
Alias: None
Product: Akonadi
Classification: Frameworks and Libraries
Component: Kolab Resource (show other bugs)
Version: 4.9
Platform: openSUSE Linux
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
: 306576 (view as bug list)
Depends on:
Blocks:
 
Reported: 2012-08-19 19:59 UTC by S. Bryant
Modified: 2012-12-19 15:00 UTC (History)
5 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description S. Bryant 2012-08-19 19:59:46 UTC
Application: akonadi_kolabproxy_resource (4.9)
KDE Platform Version: 4.9.00 "release 559"
Qt Version: 4.8.2
Operating System: Linux 3.1.10-1.16-desktop x86_64
Distribution: "openSUSE 12.1 (x86_64)"

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

Right clicked on 'Contacts' address book folder, and selected "Update address book folder" (F5).

- Other notes:

This bug did not occur in KDE 4.8.x.  It's new in 4.9.0.

As apparent from the stack trace, it's related to the contact's photograph.  One workaround is to remove the photos - I tried this and the refresh completed... but now my phone doesn't show me anybody's picture when a call is made. :-(

The crash can be reproduced every time.

-- Backtrace:
Application: Kolab of type Kolab Groupware Server (akonadi_kolabproxy_resource), signal: Segmentation fault
[KCrash Handler]
#6  header<KMime::Headers::ContentTransferEncoding> (create=<optimized out>, this=<optimized out>) at /usr/src/debug/kdepimlibs-4.9.0/kmime/kmime_content.h:833
#7  KMime::Content::contentTransferEncoding (this=0x0, create=true) at /usr/src/debug/kdepimlibs-4.9.0/kmime/kmime_content.cpp:999
#8  0x00007f4b4cbd988b in KMime::Content::decodedContent (this=0x0) at /usr/src/debug/kdepimlibs-4.9.0/kmime/kmime_content.cpp:374
#9  0x00007f4b4f65c03d in Kolab::getPicture (pictureAttachmentName=..., data=<optimized out>, type=...) at /usr/src/debug/libkolab-0.3.1/kolabformat/v2helpers.h:81
#10 0x00007f4b4f65c70b in Kolab::addresseeFromKolab (xmlData=..., data=...) at /usr/src/debug/libkolab-0.3.1/kolabformat/v2helpers.h:121
#11 0x00007f4b4f663fa8 in Kolab::KolabObjectReader::Private::readKolabV2 (this=0xbf9410, msg=..., objectType=Kolab::ContactObject) at /usr/src/debug/libkolab-0.3.1/kolabformat/kolabobject.cpp:246
#12 0x00007f4b4f664fde in Kolab::KolabObjectReader::parseMimeMessage (this=0x7fffc66e30c0, msg=...) at /usr/src/debug/libkolab-0.3.1/kolabformat/kolabobject.cpp:391
#13 0x00007f4b4f66540d in Kolab::KolabObjectReader::KolabObjectReader (this=0x7fffc66e30c0, msg=...) at /usr/src/debug/libkolab-0.3.1/kolabformat/kolabobject.cpp:104
#14 0x0000000000427217 in ?? ()
#15 0x0000000000417ff5 in _start ()

Possible duplicates by query: bug 300141.

Reported using DrKonqi
Comment 1 Laurent Montel 2012-08-20 06:44:18 UTC
I reported to libkolab developer.
Will fix in next release.
Comment 2 Laurent Montel 2012-08-21 06:13:28 UTC
Add patch here too

diff --git a/kolabformat/v2helpers.h b/kolabformat/v2helpers.h
index f93f9a1..dcc8563 100644
--- a/kolabformat/v2helpers.h
+++ b/kolabformat/v2helpers.h
@@ -77,6 +77,7 @@ QImage getPicture(const QString &pictureAttachmentName, 
const KMime::Message::Pt
     KMime::Content *imgContent = Mime::findContentByName(data, 
pictureAttachmentName/*"kolab-picture.png"*/, type);
     if (!imgContent) {
         Warning() << "could not find picture: " << pictureAttachmentName;
+        return QImage();
     }
     QByteArray imgData = imgContent->decodedContent();
     QBuffer buffer(&imgData);
@@ -268,4 +269,4 @@ QStringList readLegacyDictionaryConfiguration(const 
QByteArray &xmlData, QString
 
 }
 
-#endif
\ No newline at end of file
+#endif
Comment 3 Christian Mollekopf 2012-08-23 14:38:53 UTC
I applied the patch to libkolab master (thanks for the patch =), the question remains why you got to this point in the first place. (The picture is not being found in the mime message).

Any possibility that you could send one of the offending contacts to me as mime-message? You can of course anonymize it, I suspect it's an encoding issue with the pictures name.
Comment 4 Laurent Montel 2012-09-11 06:18:27 UTC
*** Bug 306576 has been marked as a duplicate of this bug. ***
Comment 5 Laurent Montel 2012-12-14 10:02:49 UTC
I close it as waitforinfo.
Patch was applyed.
Comment 6 S. Bryant 2012-12-16 21:18:00 UTC
Hi,

Now using KDE 4.9.4.  I'm not able to reproduce this bug - the picture handling seems to be working fine.  As far as I am concerned, this can be closed.

Many thanks,

Steve