brasero crashed with SIGSEGV in brasero_burn_record()

Bug #321220 reported by Paulo
32
This bug affects 6 people
Affects Status Importance Assigned to Milestone
brasero (Ubuntu)
Invalid
Medium
Ubuntu Desktop Bugs

Bug Description

Binary package hint: brasero

I cleanup a DVD-RW, started to record an ubuntu image and crashed.

DMESG:
[10299.926393] brasero[8908]: segfault at 0 ip 000000000045bc0b sp 00007fffd0876340 error 4 in brasero[400000+fe000]
[10321.826187] cdrom: This disc doesn't have any tracks I recognize!
[10321.913621] end_request: I/O error, dev sr0, sector 0
[10321.913635] Buffer I/O error on device sr0, logical block 0
[10321.979671] end_request: I/O error, dev sr0, sector 0
[10321.979684] Buffer I/O error on device sr0, logical block 0

ProblemType: Crash
Architecture: amd64
DistroRelease: Ubuntu 9.04
ExecutablePath: /usr/bin/brasero
Package: brasero 0.9.0-0ubuntu1
ProcCmdline: brasero
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: brasero
StacktraceTop:
 ?? ()
 brasero_burn_record ()
 brasero_burn_dialog_run ()
 brasero_app_burn ()
 brasero_app_burn_image ()
Title: brasero crashed with SIGSEGV in brasero_burn_record()
Uname: Linux 2.6.28-5-generic x86_64
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Tags: apport-crash
Revision history for this message
Paulo (pkhouri) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:brasero_burn_record (burn=0x22a10a0,
brasero_burn_dialog_run (dialog=0x1eae160,
brasero_app_burn (app=0x1c36060, session=0x2057c60)
brasero_app_burn_image (app=0x1c36060,
brasero_project_manager_switch (manager=0x1be1770,

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
Changed in brasero:
importance: Undecided → Medium
Revision history for this message
Pedro Villavicencio (pedro) wrote :

Thanks for the report, do you have the same issue with brasero 0.9.1 ?

Changed in brasero:
assignee: nobody → desktop-bugs
status: New → Incomplete
Revision history for this message
Paulo (pkhouri) wrote : Re: [Bug 321220] Re: brasero crashed with SIGSEGV in brasero_burn_record()

If I still have this problem, I can notify you, but now I not able to test
it.

Thanx!

On Mon, Jan 26, 2009 at 15:54, Pedro Villavicencio <email address hidden> wrote:

> Thanks for the report, do you have the same issue with brasero 0.9.1 ?
>
> ** Changed in: brasero (Ubuntu)
> Assignee: (unassigned) => Ubuntu Desktop Bugs (desktop-bugs)
> Status: New => Incomplete
>
> --
> brasero crashed with SIGSEGV in brasero_burn_record()
> https://bugs.launchpad.net/bugs/321220
> You received this bug notification because you are a direct subscriber
> of the bug.
>

Revision history for this message
Sebastien Bacher (seb128) wrote :

could you try if that's still an issue in jaunty?

Revision history for this message
Paulo (pkhouri) wrote :

For me it never happened again.

Revision history for this message
Sebastien Bacher (seb128) wrote :

We are closing this bug report as it lacks the information, described in the previous comments, we need to investigate the problem further. However, please reopen it if you can give us the missing information and don't hesitate to submit bug reports in the future.

Changed in brasero (Ubuntu):
status: Incomplete → Invalid
Revision history for this message
Paulo (pkhouri) wrote :

Ok, thanx!!

Good Job!!

On Tue, Sep 29, 2009 at 06:03, Sebastien Bacher <email address hidden> wrote:

> We are closing this bug report as it lacks the information, described in
> the previous comments, we need to investigate the problem further.
> However, please reopen it if you can give us the missing information and
> don't hesitate to submit bug reports in the future.
>
> ** Changed in: brasero (Ubuntu)
> Status: Incomplete => Invalid
>
> --
> brasero crashed with SIGSEGV in brasero_burn_record()
> https://bugs.launchpad.net/bugs/321220
> You received this bug notification because you are a direct subscriber
> of the bug.
>

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.