Crash in plasma shell due to bad connection manager

Alexandr Akulich akulichalexander at gmail.com
Mon Aug 3 12:52:32 UTC 2015


> Hey,
>
> On Sun, Aug 2, 2015 at 8:24 AM, Diane Trout <diane at ghic.org> wrote:
>
>> Hi,
>>
>> I was trying to develop a connection manager in python, and once had
>> enough interfaces implemented for TelepathyQt to try reading contacts I was
>> getting ktp-contactlist and plasmashell to crash.
>>
>>
>>
>> It looks like TelepathyQt was crashing at at TelepathyQt/contact.cpp:1048
>> when it was parsing the mess I was returning for
>> oft.Connection.Interface.ContactCapabilities/capabilities
>>
>> I suspect the plasma shell crash is because I had the ktp widget in the
>> system tray. This is with the Debian builds of 15.04.3 [1] and TelepathyQt
>> 0.9.6.1
>>
>> For reference this is the function that returns the garbage that triggers
>> the crash
>>
>> https://github.com/detrout/telepathy-gitter/blob/51cba4dacefb7fd10e4d107045f30a5679bd0912/glitter/contacts.py#L140
>>
>
> I'm not entirely sure about Python and/or the struct you need to return,
> however you can check the Telegram CM which is done in Qt,
> see https://github.com/Kaffeine/telegram-qt/ ...maybe it will help :)
>
The correct URL is https://github.com/TelepathyQt/telepathy-morse
>
>> Obviously I need to figure out how to properly construct the dbus
>> structure (any hints would be appreciated). I was also wondering if causing
>> plasmashell to crash because of my own bad code is something that should
>> file a plasmashell bugreport for?
>>
>
> Yeah, probably. Perhaps it should be fixed in tp-qt, even. Just
> file one and paste the backtrace there, we can follow it there.
>
I experienced a lot of crashes and craziness in KTp and Plasma during
Morse development.
It was too many different issues, so I didn't dive into that. After
all, there is no crashes, if connection manager behaves well. :-)


More information about the KDE-Telepathy mailing list