[telepathy] [Bug 322197] Text-UI crashed with uninitialised channel

[Lukáš Karas]

https://bugs.kde.org/show_bug.cgi?id=322197

Lukáš Karas <lukas.karas at centrum.cz> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |lukas.karas at centrum.cz

--- Comment #3 from Lukáš Karas <lukas.karas at centrum.cz> ---
This bug affect me relatively often (ones in week).

Ater IM startup (and login), I got some message. When I click to tray icon,
ktp-text-ui crashed. 

Interesting is that I was not able to find this message in telepathy logs
(~/.local/share/TpLogger/logs), so I know message text (from notification
popup) but I dont know who send me this message :-( It can be caused by the
same problem or something absolutely different.

Application: ktp-text-ui (0.8.1)
KDE Platform Version: 4.13.3
Qt Version: 4.8.6
Operating System: Linux 3.16.2 x86_64
Distribution: Ubuntu 14.04.1 LTS

-- Backtrace:
Application: Textové rozhraní  Telepathy (ktp-text-ui), signal: Segmentation
fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fc2b7b9a7c0 (LWP 7062))]

Thread 2 (Thread 0x7fc299ffd700 (LWP 7071)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x00007fc2aee8f81d in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4
#2  0x00007fc2aee8f859 in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4
#3  0x00007fc2b2d86182 in start_thread (arg=0x7fc299ffd700) at
pthread_create.c:312
#4  0x00007fc2b3a29fbd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 1 (Thread 0x7fc2b7b9a7c0 (LWP 7062)):
[KCrash Handler]
#6  Tp::Contact::alias (this=0x0) at
/build/buildd/telepathy-qt-0.9.3/TelepathyQt/contact.cpp:399
#7  0x00007fc2b542bdb4 in ChatWidget::ChatWidget (this=0x2b28fd0, channel=...,
account=..., parent=<optimized out>) at
/build/buildd/ktp-text-ui-0.8.1/lib/chat-widget.cpp:143
#8  0x00000000004186a1 in ChatTab::ChatTab (this=0x2b28fd0, channel=...,
account=..., parent=<optimized out>) at
/build/buildd/ktp-text-ui-0.8.1/app/chat-tab.cpp:38
#9  0x0000000000410682 in TelepathyChatUi::handleChannels (this=<optimized
out>, context=..., account=..., connection=..., channels=...,
channelRequests=..., userActionTime=..., handlerInfo=...) at
/build/buildd/ktp-text-ui-0.8.1/app/telepathy-chat-ui.cpp:167
#10 0x00007fc2b62f2280 in Tp::ClientHandlerAdaptor::onReadyOpFinished
(this=0x2ac1a10, op=<optimized out>) at
/build/buildd/telepathy-qt-0.9.3/TelepathyQt/client-registrar.cpp:509
#11 0x00007fc2b50b887a in QMetaObject::activate (sender=sender at entry=0xb40dd0,
m=m at entry=0x7fc2b6819480 <Tp::PendingOperation::staticMetaObject>,
local_signal_index=local_signal_index at entry=0, argv=argv at entry=0x7fffa10ee1c0)
at kernel/qobject.cpp:3539
#12 0x00007fc2b641e63f in Tp::PendingOperation::finished
(this=this at entry=0xb40dd0, _t1=_t1 at entry=0xb40dd0) at
/build/buildd/telepathy-qt-0.9.3/obj-x86_64-linux-gnu/TelepathyQt/_gen/pending-operation.moc.hpp:111
#13 0x00007fc2b641e731 in Tp::PendingOperation::emitFinished (this=0xb40dd0) at
/build/buildd/telepathy-qt-0.9.3/TelepathyQt/pending-operation.cpp:123
#14 0x00007fc2b50bcc1e in QObject::event (this=0xb40dd0, e=<optimized out>) at
kernel/qobject.cpp:1194
#15 0x00007fc2b41c2e2c in QApplicationPrivate::notify_helper
(this=this at entry=0xa902b0, receiver=receiver at entry=0xb40dd0,
e=e at entry=0xb56160) at kernel/qapplication.cpp:4567
#16 0x00007fc2b41c94a0 in QApplication::notify (this=this at entry=0xa7c180,
receiver=receiver at entry=0xb40dd0, e=e at entry=0xb56160) at
kernel/qapplication.cpp:4353
#17 0x00007fc2b70fad1a in KApplication::notify (this=0xa7c180,
receiver=0xb40dd0, event=0xb56160) at ../../kdeui/kernel/kapplication.cpp:311
#18 0x00007fc2b50a44dd in QCoreApplication::notifyInternal (this=0xa7c180,
receiver=receiver at entry=0xb40dd0, event=event at entry=0xb56160) at
kernel/qcoreapplication.cpp:953
#19 0x00007fc2b50a7b3d in sendEvent (event=0xb56160, receiver=0xb40dd0) at
../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:231
#20 QCoreApplicationPrivate::sendPostedEvents (receiver=receiver at entry=0x0,
event_type=event_type at entry=0, data=0xa311f0) at
kernel/qcoreapplication.cpp:1577
#21 0x00007fc2b50a7fe3 in QCoreApplication::sendPostedEvents
(receiver=receiver at entry=0x0, event_type=event_type at entry=0) at
kernel/qcoreapplication.cpp:1470
#22 0x00007fc2b50d1f83 in sendPostedEvents () at
../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:236
#23 postEventSourceDispatch (s=0xa8d950) at
kernel/qeventdispatcher_glib.cpp:287
#24 0x00007fc2ad12ae04 in g_main_dispatch (context=0xa90740) at
/build/buildd/glib2.0-2.40.0/./glib/gmain.c:3064
#25 g_main_context_dispatch (context=context at entry=0xa90740) at
/build/buildd/glib2.0-2.40.0/./glib/gmain.c:3663
#26 0x00007fc2ad12b048 in g_main_context_iterate
(context=context at entry=0xa90740, block=block at entry=1,
dispatch=dispatch at entry=1, self=<optimized out>) at
/build/buildd/glib2.0-2.40.0/./glib/gmain.c:3734
#27 0x00007fc2ad12b0ec in g_main_context_iteration (context=0xa90740,
may_block=1) at /build/buildd/glib2.0-2.40.0/./glib/gmain.c:3795
#28 0x00007fc2b50d17a1 in QEventDispatcherGlib::processEvents (this=0xa32af0,
flags=...) at kernel/qeventdispatcher_glib.cpp:434
#29 0x00007fc2b4264bb6 in QGuiEventDispatcherGlib::processEvents
(this=<optimized out>, flags=...) at kernel/qguieventdispatcher_glib.cpp:204
#30 0x00007fc2b50a30af in QEventLoop::processEvents
(this=this at entry=0x7fffa10ee7f0, flags=...) at kernel/qeventloop.cpp:149
#31 0x00007fc2b50a33a5 in QEventLoop::exec (this=this at entry=0x7fffa10ee7f0,
flags=...) at kernel/qeventloop.cpp:204
#32 0x00007fc2b50a8b79 in QCoreApplication::exec () at
kernel/qcoreapplication.cpp:1225
#33 0x00007fc2b41c137c in QApplication::exec () at kernel/qapplication.cpp:3828
#34 0x000000000040e995 in main (argc=1, argv=0x7fffa10eea18) at
/build/buildd/ktp-text-ui-0.8.1/app/main.cpp:72

-- 
You are receiving this mail because:
You are the assignee for the bug.