emesene crashed with SIGSEGV in g_main_context_dispatch()

Bug #1117192 reported by Bullet
260
This bug affects 1 person
Affects Status Importance Assigned to Milestone
emesene (Ubuntu)
New
Undecided
Unassigned

Bug Description

emesene crashed with SIGSEGV in g_main_context_dispatch()

ProblemType: Crash
DistroRelease: Ubuntu 13.04
Package: emesene 2.12.5+dfsg-1ubuntu2
ProcVersionSignature: Ubuntu 3.8.0-4.8-generic 3.8.0-rc6
Uname: Linux 3.8.0-4-generic i686
ApportVersion: 2.8-0ubuntu4
Architecture: i386
Date: Wed Feb 6 05:32:21 2013
ExecutablePath: /usr/share/emesene/emesene/emesene
InstallationDate: Installed on 2013-01-09 (27 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha i386 (20130107)
InterpreterPath: /usr/bin/python2.7
MarkForUpload: True
PackageArchitecture: all
ProcCmdline: python /usr/bin/emesene -s
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x80c748c: mov 0x54(%ebp),%eax
 PC (0x080c748c) ok
 source "0x54(%ebp)" (0x00000054) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: emesene
StacktraceTop:
 ?? ()
 ?? ()
 ?? () from /usr/lib/python2.7/dist-packages/glib/_glib.so
 ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
 g_main_context_dispatch () from /lib/i386-linux-gnu/libglib-2.0.so.0
Title: emesene crashed with SIGSEGV in g_main_context_dispatch()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
Bullet (pcb972) 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 this software better. This particular crash has already been reported and is a duplicate of bug #1050358, 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.

information type: Private Security → Public Security
tags: removed: need-i386-retrace
To post a comment you must log in.
This report contains Public Security information  
Everyone can see this security related information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.