qutimdevelop team mailing list archive
-
qutimdevelop team
-
Mailing list archive
-
Message #01406
[Bug 1316458] [NEW] qutim crashed with SIGSEGV in qutim_sdk_0_3::Message::Message()/ when message to me sended/ vk
Private bug reported:
qutim crashed when message from vk to me sended
ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: qutim 0.3.2+201404261825-52~ubuntu13.10.1 [origin: LP-PPA-qutim-qutim]
ProcVersionSignature: Ubuntu 3.11.0-20.35-generic 3.11.10.6
Uname: Linux 3.11.0-20-generic i686
ApportVersion: 2.12.5-0ubuntu2.2
Architecture: i386
CrashCounter: 1
CrashDB: qutim
Date: Tue May 6 10:27:13 2014
ExecutablePath: /usr/bin/qutim
InstallationDate: Installed on 2013-05-17 (353 days ago)
InstallationMedia: Lubuntu 13.04 "Raring Ringtail" - Release i386 (20130423.1)
LocalModules:
MarkForUpload: True
ProcCmdline: qutim --single-instance
ProcEnviron:
LANGUAGE=ru_UA:ru
PATH=(custom, user)
XDG_RUNTIME_DIR=<set>
LANG=ru_UA.UTF-8
SHELL=/bin/bash
SegvAnalysis:
Segfault happened at: 0xb67c53e8 <_ZN13qutim_sdk_0_37MessageC2ERKS0_+40>: lock incl (%eax)
PC (0xb67c53e8) ok
source "(%eax)" (0x006f0068) not located in a known VMA region (needed readable region)!
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: qutim
StacktraceTop:
qutim_sdk_0_3::Message::Message(qutim_sdk_0_3::Message const&) () from /usr/lib/libqutim.so.0
?? () from /usr/lib/qutim/plugins/libvkontakte.so
?? () from /usr/lib/qutim/plugins/libvkontakte.so
QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib/i386-linux-gnu/libQtCore.so.4
qutim_sdk_0_3::ChatSession::unreadChanged(QList<qutim_sdk_0_3::Message> const&) () from /usr/lib/libqutim.so.0
ThirdParty: True
Title: qutim crashed with SIGSEGV in qutim_sdk_0_3::Message::Message()
UpgradeStatus: Upgraded to saucy on 2014-04-24 (11 days ago)
UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo video
** Affects: qutim
Importance: Undecided
Status: New
** Tags: apport-crash i386 need-i386-retrace saucy third-party-packages
--
You received this bug notification because you are a member of QutIM
Developers, which is subscribed to qutim.
https://bugs.launchpad.net/bugs/1316458
Title:
qutim crashed with SIGSEGV in qutim_sdk_0_3::Message::Message()/ when
message to me sended/ vk
Status in Multiplatform instant messenger:
New
Bug description:
qutim crashed when message from vk to me sended
ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: qutim 0.3.2+201404261825-52~ubuntu13.10.1 [origin: LP-PPA-qutim-qutim]
ProcVersionSignature: Ubuntu 3.11.0-20.35-generic 3.11.10.6
Uname: Linux 3.11.0-20-generic i686
ApportVersion: 2.12.5-0ubuntu2.2
Architecture: i386
CrashCounter: 1
CrashDB: qutim
Date: Tue May 6 10:27:13 2014
ExecutablePath: /usr/bin/qutim
InstallationDate: Installed on 2013-05-17 (353 days ago)
InstallationMedia: Lubuntu 13.04 "Raring Ringtail" - Release i386 (20130423.1)
LocalModules:
MarkForUpload: True
ProcCmdline: qutim --single-instance
ProcEnviron:
LANGUAGE=ru_UA:ru
PATH=(custom, user)
XDG_RUNTIME_DIR=<set>
LANG=ru_UA.UTF-8
SHELL=/bin/bash
SegvAnalysis:
Segfault happened at: 0xb67c53e8 <_ZN13qutim_sdk_0_37MessageC2ERKS0_+40>: lock incl (%eax)
PC (0xb67c53e8) ok
source "(%eax)" (0x006f0068) not located in a known VMA region (needed readable region)!
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: qutim
StacktraceTop:
qutim_sdk_0_3::Message::Message(qutim_sdk_0_3::Message const&) () from /usr/lib/libqutim.so.0
?? () from /usr/lib/qutim/plugins/libvkontakte.so
?? () from /usr/lib/qutim/plugins/libvkontakte.so
QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib/i386-linux-gnu/libQtCore.so.4
qutim_sdk_0_3::ChatSession::unreadChanged(QList<qutim_sdk_0_3::Message> const&) () from /usr/lib/libqutim.so.0
ThirdParty: True
Title: qutim crashed with SIGSEGV in qutim_sdk_0_3::Message::Message()
UpgradeStatus: Upgraded to saucy on 2014-04-24 (11 days ago)
UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo video
To manage notifications about this bug go to:
https://bugs.launchpad.net/qutim/+bug/1316458/+subscriptions
Follow ups
References