Public bug reported:

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

** Affects: qutim (Ubuntu)
     Importance: Undecided
         Status: New


** Tags: apport-crash i386 lucid

-- 
qutim crashed with SIGSEGV in QString::operator=()
https://bugs.launchpad.net/bugs/548595
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to