Bug 20367

Summary: TpQt4 crash
Product: Telepathy Reporter: Dariusz Mikulski <dariusz.mikulski>
Component: tp-qtAssignee: Telepathy bugs list <telepathy-bugs>
Status: RESOLVED FIXED QA Contact: Telepathy bugs list <telepathy-bugs>
Severity: normal    
Priority: medium CC: dariusz.mikulski
Version: unspecified   
Hardware: Other   
OS: All   
Whiteboard:
i915 platform: i915 features:

Description Dariusz Mikulski 2009-02-27 13:38:06 UTC
details: https://paste.collabora.co.uk/226

Reproducing:
svn co --revision 933033 svn://anonsvn.kde.org/home/kde/branches/work/kopete/kopete-tpqt4/
compile kopete-tpqt4
run telepathy-accountmanager-kwallet
run kopete
add telepathy account from gabble, jabber protocol
change 2 or more times status
exit kopete


T-a-k output before segmentation fault:

telepathy-accountmanager-kwallet(7607) Account::propertiesUpdated: ++++++++++++++++++++++++++ Begin Updated Properties +++++++++++++++++++++++++++                                  
telepathy-accountmanager-kwallet(7607) Account::propertiesUpdated: Property:  "RequestedPresence" changed to: QVariant(Telepathy::SimplePresence, )                                 
telepathy-accountmanager-kwallet(7607) Account::propertiesUpdated: The property changed was of type Telepathy::SimplePresence. Dumping...                                           
telepathy-accountmanager-kwallet(7607) Account::propertiesUpdated:          2 : "" : ""                                                                                             
telepathy-accountmanager-kwallet(7607) Account::propertiesUpdated: +++++++++++++++++++++++++++ End Updated Properties ++++++++++++++++++++++++++++                                  
telepathy-accountmanager-kwallet(7607) Account::onRequestedPresenceChanged: Method called.                                                                                          
telepathy-accountmanager-kwallet(7607) Account::onRequestedPresenceChanged: Everything's OK. We can actually set the presence now!                                                  
telepathy-accountmanager-kwallet(7607) Account::onPresenceChangeComplete: slot called.                                                                                              
telepathy-accountmanager-kwallet(7607) Account::onPresenceChangeComplete: Setting self-presence failed: "org.freedesktop.Telepathy.Errors.InvalidArgument" "unknown status identifier: "
telepathy-accountmanager-kwallet(7607) Account::onConnectionStatusChanged: Called with status: 2 and reason: 1
telepathy-accountmanager-kwallet(7607) Account::propertiesUpdated: ++++++++++++++++++++++++++ Begin Updated Properties +++++++++++++++++++++++++++
telepathy-accountmanager-kwallet(7607) Account::propertiesUpdated: Property:  "ConnectionStatus" changed to: QVariant(uint, 2)
telepathy-accountmanager-kwallet(7607) Account::propertiesUpdated: Property:  "ConnectionStatusReason" changed to: QVariant(uint, 1)
telepathy-accountmanager-kwallet(7607) Account::propertiesUpdated: Property:  "CurrentPresence" changed to: QVariant(Telepathy::SimplePresence, )
telepathy-accountmanager-kwallet(7607) Account::propertiesUpdated: The property changed was of type Telepathy::SimplePresence. Dumping...
telepathy-accountmanager-kwallet(7607) Account::propertiesUpdated:          2 : "" : ""
telepathy-accountmanager-kwallet(7607) Account::propertiesUpdated: Property:  "Connection" changed to: QVariant(QDBusObjectPath, )
telepathy-accountmanager-kwallet(7607) Account::propertiesUpdated: +++++++++++++++++++++++++++ End Updated Properties ++++++++++++++++++++++++++++

Program received signal SIGSEGV, Segmentation fault
Comment 1 Dariusz Mikulski 2009-02-27 13:45:40 UTC
Backtrace:

[Switching to Thread 0xb60626c0 (LWP 7607)]
Telepathy::Client::DBusProxy::invalidate (this=0x9baa000, reason=@0xbfc03800, message=@0xbfc03804) at Client/dbus-proxy.cpp:230
230         if (!isValid()) {
(gdb) bt
#0  Telepathy::Client::DBusProxy::invalidate (this=0x9baa000, reason=@0xbfc03800, message=@0xbfc03804) at Client/dbus-proxy.cpp:230
#1  0x080aa49b in Telepathy::Client::Connection::onStatusChanged (this=0x9baa000, status=2, reason=1) at Client/connection.cpp:746
#2  0x080afd0d in Telepathy::Client::Connection::qt_metacall (this=0x9baa000, _c=QMetaObject::InvokeMetaMethod, _id=4, _a=0xbfc0391c)
    at ../TelepathyQt4/Client/_gen/connection.moc.hpp:106
#3  0xb7624098 in QMetaObject::activate (sender=0x9d9d7b8, from_signal_index=9, to_signal_index=9, argv=0xbfc0391c) at kernel/qobject.cpp:3053
#4  0xb7624d12 in QMetaObject::activate (sender=0x9d9d7b8, m=0x8169c00, local_signal_index=3, argv=0xbfc0391c) at kernel/qobject.cpp:3125
#5  0x0809ff4b in Telepathy::Client::ConnectionInterface::StatusChanged (this=0x9d9d7b8, _t1=2, _t2=1) at ../TelepathyQt4/_gen/cli-connection.moc.hpp:191
#6  0x080a4d15 in Telepathy::Client::ConnectionInterface::qt_metacall (this=0x9d9d7b8, _c=QMetaObject::InvokeMetaMethod, _id=3, _a=0xbfc03ae8)
    at ../TelepathyQt4/_gen/cli-connection.moc.hpp:111
#7  0xb772af8a in QDBusConnectionPrivate::deliverCall (this=0x9ce4fe8, object=0x9d9d7b8, msg=@0x9d92e0c, metaTypes=@0x9d92e10, slotIdx=9) at qdbusintegrator.cpp:886
warning: (Internal error: pc 0xb7733397 in read in psymtab, but not in symtab.)

warning: (Internal error: pc 0xb7733396 in read in psymtab, but not in symtab.)

warning: (Internal error: pc 0xb7733396 in read in psymtab, but not in symtab.)

#8  0xb7733397 in QDBusCallDeliveryEvent::placeMetaCall (this=warning: (Internal error: pc 0xb7733396 in read in psymtab, but not in symtab.)

warning: (Internal error: pc 0xb7733360 in read in psymtab, but not in symtab.)

warning: (Internal error: pc 0xb7733396 in read in psymtab, but not in symtab.)

0x9d92de0, object=warning: (Internal error: pc 0xb7733396 in read in psymtab, but not in symtab.)

0x9d9d7b8) at qdbusintegrator_p.h:96
#9  0xb761e790 in QObject::event (this=0x9d9d7b8, e=0x9d92de0) at kernel/qobject.cpp:1104
#10 0xb6a4600c in QApplicationPrivate::notify_helper (this=0x9b6e008, receiver=0x9d9d7b8, e=0x9d92de0) at kernel/qapplication.cpp:4079
#11 0xb6a4e30e in QApplication::notify (this=0xbfc04218, receiver=0x9d9d7b8, e=0x9d92de0) at kernel/qapplication.cpp:3626
#12 0xb7bb4871 in KApplication::notify (this=0xbfc04218, receiver=0x9d9d7b8, event=0x9d92de0) at /home/malcolm/kde/src/KDE/kdelibs/kdeui/kernel/kapplication.cpp:307
#13 0xb760de5b in QCoreApplication::notifyInternal (this=0xbfc04218, receiver=0x9d9d7b8, event=0x9d92de0) at kernel/qcoreapplication.cpp:597
#14 0xb760eab5 in QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x9b5c2c0) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:208
#15 0xb760ecad in QCoreApplication::sendPostedEvents (receiver=0x0, event_type=0) at kernel/qcoreapplication.cpp:1127
#16 0xb7639bcf in postEventSourceDispatch (s=0x9b70110) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:213
#17 0xb62726f8 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#18 0xb6275da3 in ?? () from /usr/lib/libglib-2.0.so.0
#19 0xb6275f61 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#20 0xb7639818 in QEventDispatcherGlib::processEvents (this=0x9b68d00, flags={i = -1077919496}) at kernel/qeventdispatcher_glib.cpp:318
#21 0xb6ae5ea5 in QGuiEventDispatcherGlib::processEvents (this=0x9b68d00, flags={i = -1077919448}) at kernel/qguieventdispatcher_glib.cpp:197
#22 0xb760c48a in QEventLoop::processEvents (this=0xbfc041a0, flags={i = -1077919384}) at kernel/qeventloop.cpp:144
#23 0xb760c8ca in QEventLoop::exec (this=0xbfc041a0, flags={i = -1077919320}) at kernel/qeventloop.cpp:195
#24 0xb760ed79 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:875
#25 0xb6a45e87 in QApplication::exec () at kernel/qapplication.cpp:3548
#26 0x0808bb35 in main (argc=1769304369, argv=0x292874) at /home/malcolm/kde/src/playground/network/telepathy-accountmanager-kwallet/src/main.cpp:95
Comment 2 Olli Salli 2010-09-16 16:50:49 UTC
This was fixed in 0.3.8 at the latest when we started creating the readiness helper earlier on, I think - so isReady() will just work, always.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.