isomaster crashed with SIGSEGV in g_cclosure_marshal_VOID__VOID() at chooseopen file from last file used

Bug #956982 reported by berg
18
This bug affects 3 people
Affects Status Importance Assigned to Milestone
isomaster (Ubuntu)
Fix Released
Medium
Unassigned

Bug Description

I started the Isomaster and I choose open a iso file.

the program show to me a list with lastest opened iso files ( from other programs because was first time that i installed and executed openmaster).

so I select one file and open it and the crash happened.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: isomaster 1.3.8-1
ProcVersionSignature: Ubuntu 3.2.0-18.29-generic-pae 3.2.9
Uname: Linux 3.2.0-18-generic-pae i686
NonfreeKernelModules: fglrx
ApportVersion: 1.94.1-0ubuntu2
Architecture: i386
Date: Fri Mar 16 10:48:17 2012
ExecutablePath: /usr/bin/isomaster
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha i386 (20120309)
ProcCmdline: isomaster
ProcEnviron:
 TERM=xterm
 SHELL=/bin/bash
 LANG=pt_BR.UTF-8
 LANGUAGE=pt_BR:pt:en
SegvAnalysis:
 Segfault happened at: 0xb6f422b6: movdqu (%edi),%xmm1
 PC (0xb6f422b6) ok
 source "(%edi)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%xmm1" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: isomaster
StacktraceTop:
 ?? () from /lib/i386-linux-gnu/libc.so.6
 ?? ()
 g_cclosure_marshal_VOID__VOID () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
 g_closure_invoke () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
 ?? () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
Title: isomaster crashed with SIGSEGV in g_cclosure_marshal_VOID__VOID()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers

Revision history for this message
berg (berg-foss) wrote :
visibility: private → public
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 ?? ()
 g_cclosure_marshal_VOID__VOID (closure=0x8c60318, return_value=0x0, n_param_values=1, param_values=0x8de0818, invocation_hint=0xbfb307d0, marshal_data=0x0) at /build/buildd/glib2.0-2.31.20/./gobject/gmarshal.c:85
 g_closure_invoke (closure=0x8c60318, return_value=0x0, n_param_values=1, param_values=0x8de0818, invocation_hint=0xbfb307d0) at /build/buildd/glib2.0-2.31.20/./gobject/gclosure.c:777
 signal_emit_unlocked_R (node=0x8c58f88, detail=0, instance=0x8c5fc78, emission_return=0x0, instance_and_params=0x8de0818) at /build/buildd/glib2.0-2.31.20/./gobject/gsignal.c:3547
 g_signal_emit_valist (instance=0x8c5fc78, signal_id=96, detail=0, var_args=0xbfb30a1c "\364/5\266x\374\305\b\364/5\266x\374\305\b\361\336\064\266x\374\305\b\210\027\306\bp\254\325\b\316\\\030\267\364\217\034\267\063\002\223\003x\374\305\b1\212\030\267\360\062\327\b3\002\223\003x\374\305\b\364\217\034\267h0\324\b") at /build/buildd/glib2.0-2.31.20/./gobject/gsignal.c:3295

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in isomaster (Ubuntu):
importance: Undecided → Medium
tags: removed: need-i386-retrace
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in isomaster (Ubuntu):
status: New → Confirmed
Revision history for this message
Unkraut (unkraut2) wrote :

This problem is gone with the version 1.3.9-1ubuntu1 present in Quantal Quetzal

Dear ubuntu gurus, please consider updating the version shipped with Precise Pangolin to 1.3.9-1ubuntu1. It works out of the box and the current version is unusable.
In the meantime if you run across this issue you can download and install the latest .deb from
https://launchpad.net/ubuntu/quantal/+package/isomaster

Cheers,
Simon

Revision history for this message
David Johnson (dj-david-web) wrote :

Closing this bug as it's old and fixed in the current isomaster release in Ubuntu.

Changed in isomaster (Ubuntu):
status: Confirmed → Fix Released
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.