Ubuntu
xfburn package

xfburn crashed with SIGSEGV in g_closure_invoke()

Bug #410716 reported by Splinterpaw on 2009-08-08

This bug affects 10 people

	Status	Importance	Assigned to
Xfburn	Unknown	Unknown	xfce-bugs #5678
xfburn (Ubuntu)	Fix Released	Medium	Lionel Le Folgoc
Karmic	Fix Released	Medium	Lionel Le Folgoc

Bug Description

Binary package hint: xfburn

Program crashed when burning iso file.

Currently using release 9.10
Package version 0.4.2-0ubuntu1

Program crashed after it finished burning ISO file to disk.

ProblemType: Crash
Architecture: amd64
Date: Sat Aug 8 09:43:03 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/xfburn
NonfreeKernelModules: nvidia
Package: xfburn 0.4.2-0ubuntu1
ProcCmdline: xfburn
ProcEnviron:
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-5.24-generic
SegvAnalysis:
Segfault happened at: 0x41601b <iso_image_get_root@plt+27459>: mov 0x10(%rax),%rdi
PC (0x0041601b) ok
source "0x10(%rax)" (0x00000010) not located in a known VMA region (needed readable region)!
destination "%rdi" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: xfburn
StacktraceTop:
?? ()
g_closure_invoke ()
?? () from /usr/lib/libgobject-2.0.so.0
g_signal_emit_valist ()
g_signal_emit () from /usr/lib/libgobject-2.0.so.0
Title: xfburn crashed with SIGSEGV in g_closure_invoke()
Uname: Linux 2.6.31-5-generic x86_64
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Tags:

Related branches

lp:ubuntu/lucid/xfburn

lp:ubuntu/karmic-proposed/xfburn

Revision history for this message

Splinterpaw (wayaadisi) wrote on 2009-08-08:

Dependencies.txt Edit (3.1 KiB, text/plain; charset="utf-8")
Disassembly.txt Edit (1.1 KiB, text/plain; charset="utf-8")
ProcMaps.txt Edit (48.6 KiB, text/plain; charset="utf-8")
ProcStatus.txt Edit (770 bytes, text/plain; charset="utf-8")
Registers.txt Edit (956 bytes, text/plain; charset="utf-8")
Stacktrace.txt Edit (1.4 KiB, text/plain; charset="utf-8")
ThreadStacktrace.txt Edit (1.4 KiB, text/plain; charset="utf-8")

Revision history for this message

Apport retracing service (apport) wrote on 2009-08-08: Stacktrace.txt (retraced)

Stacktrace.txt (retraced) Edit (6.4 KiB, text/plain)

StacktraceTop:check_burn_button (dialog=0x12eab10) at xfburn-burn-image-dialog.c:436
IA__g_closure_invoke (closure=0x18782d0,
signal_emit_unlocked_R (node=0x149cb80,
IA__g_signal_emit_valist (instance=0x1499800,
IA__g_signal_emit (instance=0x8, signal_id=0,

Revision history for this message

Apport retracing service (apport) wrote on 2009-08-08: ThreadStacktrace.txt (retraced)

ThreadStacktrace.txt (retraced) Edit (6.4 KiB, text/plain)

Changed in xfburn (Ubuntu):
importance:	Undecided → Medium
tags:	removed: need-amd64-retrace

Revision history for this message

Lionel Le Folgoc (mrpouit) wrote on 2009-08-16:

Thanks for your bug report, forwarded upstream.

Changed in xfburn (Ubuntu):
status:	New → Triaged
visibility:	private → public

Revision history for this message

Lionel Le Folgoc (mrpouit) wrote on 2009-08-18:

Hi,

Upstream asked for more infos: did it crash after it finished burning successfully, or right after you clicked on the button?
If you can't remember, could you retry to reproduce the crash, and obtain a backtrace, as described in <https://wiki.ubuntu.com/Backtrace>? Thanks.

Changed in xfburn (Ubuntu):
status:	Triaged → Incomplete

Revision history for this message

Lionel Le Folgoc (mrpouit) wrote on 2009-09-13:

Ok, reproduced. It crashes right after it finishes burning.

Changed in xfburn (Ubuntu):
status:	Incomplete → Triaged

Lionel Le Folgoc (mrpouit) on 2009-11-22

Changed in xfburn (Ubuntu):
status:	Triaged → In Progress

Revision history for this message

Launchpad Janitor (janitor) wrote on 2009-11-22:

This bug was fixed in the package xfburn - 0.4.2-2ubuntu1

---------------
xfburn (0.4.2-2ubuntu1) lucid; urgency=low

  * Merge from Debian testing, remaining Ubuntu changes:
    - debian/patches/01_fix-infinite-dialog-spawn.patch: fix Xfburn asks an
    unlimited number of times to erase disk. LP: #434031

xfburn (0.4.2-2) unstable; urgency=low

  * debian/control:
    - switch section to xfce.
    - update standards version to 3.8.3.
    - promote hal to Depends: since xfburn will crash without.
  * debian/watch edited to track Xfce archive reorganisation.
-- Lionel Le Folgoc <email address hidden> Sun, 22 Nov 2009 18:20:56 +0100

Changed in xfburn (Ubuntu):
status:	In Progress → Fix Released

Lionel Le Folgoc (mrpouit) on 2009-12-01

Changed in xfburn (Ubuntu):
assignee:	nobody → Lionel Le Folgoc (mrpouit)
Changed in xfburn (Ubuntu Karmic):
importance:	Undecided → Medium
status:	New → In Progress
assignee:	nobody → Lionel Le Folgoc (mrpouit)

Revision history for this message

Cody A.W. Somerville (cody-somerville) wrote on 2009-12-01:

ACK

Revision history for this message

Martin Pitt (pitti) wrote on 2009-12-07: Please test proposed package

Accepted xfburn into karmic-proposed, the package will build now and be available in a few hours. Please test and give feedback here. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you in advance!

Changed in xfburn (Ubuntu Karmic):
status:	In Progress → Fix Committed
tags:	added: verification-needed

Revision history for this message

Launchpad Janitor (janitor) wrote on 2009-12-21:

#10

This bug was fixed in the package xfburn - 0.4.2-1ubuntu1.1

---------------
xfburn (0.4.2-1ubuntu1.1) karmic-proposed; urgency=low

  * debian/patches/02_keep-the-devlist-around.patch: do not crash when there is
    a property change in a drive. LP: #410716
  * debian/patches/03_uint-screwed-up-the-1-return.patch: do not crash if hald
    isn't running. LP: #480704
  * debian/control: promote hal to recommends, as xfburn tries to use it first
    (and falls back to libburn after).
-- Lionel Le Folgoc <email address hidden> Tue, 01 Dec 2009 15:06:51 +0100