mission-control-5 crashed with SIGSEGV in g_str_hash()

Bug #835497 reported by Ahmad Zain
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
telepathy-mission-control-5 (Ubuntu)
New
Undecided
Unassigned

Bug Description

this is with Gnome-shell

and the windows title bar is strange

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: telepathy-mission-control-5 1:5.9.1-0ubuntu1
ProcVersionSignature: Ubuntu 3.0.0-9.14-generic 3.0.3
Uname: Linux 3.0.0-9-generic i686
NonfreeKernelModules: wl
Architecture: i386
Date: Sat Aug 27 17:24:41 2011
ExecutablePath: /usr/lib/telepathy/mission-control-5
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-3.0.0-9-generic root=UUID=94741dcc-073b-4321-a16e-eec42763345c ro quiet splash vt.handoff=7
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, user)
 LANGUAGE=en_US:en
 LANG=en_US.UTF-8
SegvAnalysis:
 Segfault happened at: 0xe881da <g_str_hash+10>: movzbl (%ecx),%edx
 PC (0x00e881da) ok
 source "(%ecx)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%edx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: telepathy-mission-control-5
StacktraceTop:
 g_str_hash () from /lib/i386-linux-gnu/libglib-2.0.so.0
 g_hash_table_lookup () from /lib/i386-linux-gnu/libglib-2.0.so.0
 ?? ()
 ?? ()
 g_cclosure_marshal_VOID__VOID () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
Title: mission-control-5 crashed with SIGSEGV in g_str_hash()
UpgradeStatus: Upgraded to oneiric on 2011-08-25 (2 days ago)
UserGroups: adm admin cdrom dialout dip fax floppy fuse lpadmin plugdev root sambashare tape users video www-data

Revision history for this message
Ahmad Zain (am-zain) wrote :
Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #726301, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.

visibility: private → public
tags: removed: need-i386-retrace
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.