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

[VKSALIAN]

I recently upgraded my Ubuntu to 13.04 beta version. After that I can see the CCS v5.2 (Texas Instruments software) and pdfsam crashed / not opening. Please help me in fixing the problem.

ProblemType: Crash
DistroRelease: Ubuntu 13.04
Package: telepathy-mission-control-5 1:5.14.0-0ubuntu1
ProcVersionSignature: Ubuntu 3.8.0-16.26-generic 3.8.5
Uname: Linux 3.8.0-16-generic i686
ApportVersion: 2.9.2-0ubuntu5
Architecture: i386
CrashCounter: 1
Date: Tue Apr 9 12:08:05 2013
ExecutablePath: /usr/lib/telepathy/mission-control-5
InstallationDate: Installed on 2013-02-02 (66 days ago)
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 (20120423)
MarkForUpload: True
ProcCmdline: BOOT_IMAGE=/vmlinuz-3.8.0-16-generic root=UUID=e21cab08-67f8-4b88-b8c3-28e12ecea254 ro quiet splash vt.handoff=7
ProcEnviron:
 SHELL=/bin/false
 XDG_RUNTIME_DIR=<set>
 PATH=(custom, no user)
 LANGUAGE=en_IN:en
 LANG=en_IN
SegvAnalysis:
 Segfault happened at: 0xb71ce912 <g_slice_alloc+178>: mov (%edi),%edx
 PC (0xb71ce912) ok
 source "(%edi)" (0x00000001) 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_slice_alloc () from /lib/i386-linux-gnu/libglib-2.0.so.0
 g_string_sized_new () from /lib/i386-linux-gnu/libglib-2.0.so.0
 g_string_new () from /lib/i386-linux-gnu/libglib-2.0.so.0
 g_key_file_to_data () from /lib/i386-linux-gnu/libglib-2.0.so.0
 ?? ()
Title: mission-control-5 crashed with SIGSEGV in g_slice_alloc()
UpgradeStatus: Upgraded to raring on 2013-03-30 (10 days ago)
UserGroups:

[Apport retracing service (apport)]

Stacktrace:
 #0 0xb71ce912 in ?? ()
 No symbol table info available.
 #1 0xb726a5a0 in ?? ()
 No symbol table info available.
 Backtrace stopped: previous frame inner to this frame (corrupt stack?)
StacktraceTop:
 ?? ()
 ?? ()

[Marc Deslauriers (mdeslaur)]

Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find.

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Esteban Ulke (eulke)]

same here with saucy

[Damiano Dallatana (damidalla)]

Still here, from raring to saucy.

[Removed by request (removed1082169)]

In a fresh Saucy Alpha2.

[Fabio Duran Verdugo (fabioduran)]

Yes, I have the bug in Ubuntu-Gnome saucy Alpha2

[Fabio Duran Verdugo (fabioduran)]

attach the thread... ?field.comment=attach the thread...

[Julie Bermond (emmadoze)]

Same with saucy for me, using latest gnome environment. tend to happen a bit randomly but more often when using Deluge (Torrent) or Firefox... if that can help in any way...

[Linuxsusefan (linuxsusefan)]

Same with Saucy for me, using latest gnome envirenment (GNOME-Shell 3.10 from gnome3-team/staging ppa).

[Alberto Salvia Novella (es20490446e)]

Since this bug has a moderate impact on a large portion of Ubuntu users, it's high priority.

[Alberto Salvia Novella (es20490446e)]

Since this bug is:

- Valid.
- Well described.
- Reported in the upstream bug tracker (Launchpad).
- Ready to be worked on by a developer.

it's also triaged.