qutim crashed with SIGSEGV in QString::operator=()

Bug #548595 reported by Dmitrij Gaysuk
20
This bug affects 4 people
Affects Status Importance Assigned to Milestone
qutim (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: qutim

crash on startup

ProblemType: Crash
Architecture: i386
Date: Fri Mar 26 08:42:42 2010
DistroRelease: Ubuntu 10.04
ExecutablePath: /usr/bin/qutim
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta i386 (20100318)
Package: qutim 0.2.0-0ubuntu2
ProcCmdline: qutim
ProcEnviron:
 LANG=ru_RU.utf8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-16.25-generic
SegvAnalysis:
 Segfault happened at: 0x7a416f0 <_ZN7QStringaSERKS_+32>: mov (%edi),%eax
 PC (0x07a416f0) ok
 source "(%edi)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: qutim
StacktraceTop:
 QString::operator=(QString const&) ()
 contactListTree::getOfflineMessage(unsigned short) ()
 contactListTree::qt_metacall(QMetaObject::Call, int, void**)
 QMetaObject::metacall(QObject*, QMetaObject::Call, int, void**) () from /usr/lib/libQtCore.so.4
 QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib/libQtCore.so.4
Title: qutim crashed with SIGSEGV in QString::operator=()
Uname: Linux 2.6.32-16-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
XsessionErrors:
 (polkit-gnome-authentication-agent-1:1325): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed
 (gnome-terminal:1680): Gtk-CRITICAL **: gtk_accel_map_unlock_path: assertion `entry != NULL && entry->lock_count > 0' failed
 (gnome-terminal:4691): Gtk-CRITICAL **: gtk_accel_map_unlock_path: assertion `entry != NULL && entry->lock_count > 0' failed

Revision history for this message
Dmitrij Gaysuk (dimaxwell-mail) wrote :
Revision history for this message
dino99 (9d9) wrote :

This version is outdated and no more supported

Changed in qutim (Ubuntu):
status: New → Invalid
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.