telephony-service-handler crashed with SIGSEGV in QString()

Bug #1336726 reported by Michał Sawicz
16
This bug affects 2 people
Affects Status Importance Assigned to Milestone
telephony-service (Ubuntu)
Triaged
Medium
Unassigned

Bug Description

I got a jabber message on my desktop, telepathy went into a frenzy, pinging me about two sms messages and pinging about a new jabber message every second until I removed telephony-service...

ProblemType: Crash
DistroRelease: Ubuntu 14.10
Package: telephony-service 0.1+14.10.20140618-0ubuntu1
ProcVersionSignature: Ubuntu 3.15.0-6.11-generic 3.15.0
Uname: Linux 3.15.0-6-generic x86_64
NonfreeKernelModules: wl nvidia
ApportVersion: 2.14.3-0ubuntu2
Architecture: amd64
CurrentDesktop: Unity
Date: Wed Jul 2 12:30:35 2014
ExecutablePath: /usr/bin/telephony-service-handler
ProcCmdline: /usr/bin/telephony-service-handler
SegvAnalysis:
 Segfault happened at: 0x7fe8b8cdff70 <_ZNK2Tp9DBusProxy10objectPathEv>: mov 0x38(%rsi),%rdx
 PC (0x7fe8b8cdff70) ok
 source "0x38(%rsi)" (0x00000038) not located in a known VMA region (needed readable region)!
 destination "%rdx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: telephony-service
StacktraceTop:
 Tp::DBusProxy::objectPath() const () from /usr/lib/x86_64-linux-gnu/libtelepathy-qt5.so.0
 Tp::Account::uniqueIdentifier() const () from /usr/lib/x86_64-linux-gnu/libtelepathy-qt5.so.0
 TextHandler::onTextChannelAvailable(Tp::SharedPtr<Tp::TextChannel>) ()
 ?? ()
 QMetaObject::activate (sender=0x23922b0, signalOffset=<optimized out>, local_signal_index=<optimized out>, argv=0x7ffff1ec5d40) at kernel/qobject.cpp:3680
Title: telephony-service-handler crashed with SIGSEGV in Tp::DBusProxy::objectPath()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm autopilot cdrom dip lpadmin plugdev sambashare sbuild sudo vboxusers

Revision history for this message
Michał Sawicz (saviq) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 QString (other=<error reading variable: Cannot access memory at address 0x38>, this=this@entry=0x7ffff1ec5ac0) at /usr/include/qt5/QtCore/qstring.h:765
 Tp::DBusProxy::objectPath (this=0x0) at /build/buildd/telepathy-qt5-0.9.3/TelepathyQt/dbus-proxy.cpp:131
 Tp::Account::uniqueIdentifier (this=<optimized out>) at /build/buildd/telepathy-qt5-0.9.3/TelepathyQt/account.cpp:2096
 TextHandler::onTextChannelAvailable (this=0x239c600, channel=...) at /build/buildd/telephony-service-0.1+14.10.20140618/handler/texthandler.cpp:140
 TextHandler::qt_static_metacall (_o=<optimized out>, _c=<optimized out>, _id=<optimized out>, _a=<optimized out>) at /build/buildd/telephony-service-0.1+14.10.20140618/obj-x86_64-linux-gnu/handler/moc_texthandler.cpp:97

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : StacktraceSource.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in telephony-service (Ubuntu):
importance: Undecided → Medium
summary: - telephony-service-handler crashed with SIGSEGV in
- Tp::DBusProxy::objectPath()
+ telephony-service-handler crashed with SIGSEGV in QString()
tags: removed: need-amd64-retrace
Michał Sawicz (saviq)
information type: Private → Private Security
information type: Private Security → Public
Bill Filler (bfiller)
Changed in telephony-service (Ubuntu):
status: New → Triaged
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.