brasero crashed with SIGSEGV

Bug #131248 reported by tmakowka
12
This bug affects 1 person
Affects Status Importance Assigned to Milestone
brasero (Ubuntu)
Invalid
Medium
Unassigned
libisofs (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Binary package hint: brasero

I'm using Ubuntu Gutsy (all updates installed till today) with Brasero 0.6.0 from the repos. I created a data cd from an nfs share and started the brun process. Brasero was doing some "thinking" and then crashed. If i try to burn it again, brasero says "Error burning. drive cannot be locked (running burning process)" (freely translated from german by me ;) ). This was reproducible even after reboot.

ProblemType: Crash
Architecture: i386
CrashCounter: 1
Date: Thu Aug 9 09:53:32 2007
DistroRelease: Ubuntu 7.10
ExecutablePath: /usr/bin/brasero
NonfreeKernelModules: nvidia
Package: brasero 0.6.0-0ubuntu2
PackageArchitecture: i386
ProcCmdline: brasero
ProcCwd: /dump/sys/home/torben
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: brasero
StacktraceTop:
 ?? () from /usr/lib/libisofs.so.4
 ?? ()
 ?? () from /usr/lib/libisofs.so.4
 ?? ()
 ?? () from /usr/lib/libisofs.so.4
Title: brasero crashed with SIGSEGV
Uname: Linux c2d-gutsy 2.6.22-9-generic #1 SMP Fri Aug 3 00:50:37 GMT 2007 i686 GNU/Linux
UserGroups: adm admin audio cdrom dialout dip floppy lpadmin netdev plugdev powerdev scanner video

Tags: apport-crash
Revision history for this message
tmakowka (ubuntu-makowka) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:create_tree (t=0x86a1238, parent=0x86be800, iso=0x57e58955) at libisofs/ecma119_tree.c:76
create_tree (t=0x86a1238, parent=<value optimized out>, iso=0x86cb190) at libisofs/ecma119_tree.c:79
create_tree (t=0x86a1238, parent=<value optimized out>, iso=0x869c8a0) at libisofs/ecma119_tree.c:79
ecma119_tree_create (t=0x86a1238, iso_root=0x869c8a0) at libisofs/ecma119_tree.c:292
ecma119_target_new (volset=0x86d8ae8, volnum=0, level=2, flags=1) at libisofs/ecma119.c:265

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
Revision history for this message
Apport retracing service (apport) wrote : Stack trace with source code
Changed in brasero:
importance: Undecided → Medium
Changed in libisofs:
importance: Undecided → Medium
status: New → Triaged
Revision history for this message
Lionel Le Folgoc (mrpouit) wrote :

Hi,

Thanks for your bug report.
Could you try with the last gutsy revision (0.6.0-2ubuntu1)?

Changed in brasero:
status: New → Incomplete
Revision history for this message
tmakowka (ubuntu-makowka) wrote :

Hi,

sorry for the late reply. I tried a similar burn process with version 0.6.1-0ubuntu1 and this time it worked! Thanks!

Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for brasero (Ubuntu) because there has been no activity for 60 days.]

Revision history for this message
Hew (hew) wrote :

This bug report is being closed due to your last comment regarding this being fixed with an update. For future reference you can manage the status of your own bugs by clicking on the current status in the yellow line and then choosing a new status in the revealed drop down box. You can learn more about bug statuses at https://wiki.ubuntu.com/Bugs/Status . Thank you again for taking the time to report this bug and helping to make Ubuntu better. Please submit any future bugs you may find.

visibility: private → public
Changed in libisofs (Ubuntu):
status: Triaged → Invalid
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.