brasero -g: segmentation fault

Bug #273183 reported by marco.pallotta
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
brasero (Ubuntu)
Fix Released
Medium
Ubuntu Desktop Bugs

Bug Description

Binary package hint: brasero

If I try to launch the command "brasero -g > brasero.out 2>&1" to debug a brasero issue I receive a "segmentation fault" after having pressed the button "burn". From this moment I cannot use my burner drive until next reboot as I always receive an error that says to me the the drive is locked because a burning process is currently running (but no related process is run).
My system is Hardy Heron x86-64 and brasero is version 0.7.1-3ubuntu1

Revision history for this message
marco.pallotta (marco-pallotta) wrote :
Revision history for this message
Pedro Villavicencio (pedro) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. However, your crash report is either missing or challenging to deal with as a ".crash" file. Please follow these instuctions to have apport report a new bug about your crash that can be dealt with by the automatic retracer.

If you are using Ubuntu with the Gnome desktop environment - launch nautilus and navigate to your /var/crash directory and double click on the crash report you wish to submit.

I'm closing this bug report since the process outlined above will automatically open a new bug report which can then dealt with more efficiently. Thanks in advance for your cooperation and understanding.

Changed in brasero:
status: New → Invalid
Revision history for this message
marco.pallotta (marco-pallotta) wrote :

@Pedro, excuse me having reopened the bug but I have no crash file inside /var/crash so I cannot proceed as you told me.

Changed in brasero:
status: Invalid → New
Revision history for this message
Pedro Villavicencio (pedro) wrote :

Try to get a backtrace then with the instructions located at http://wiki.ubuntu.com/DebuggingProgramCrash and attach that file to the report, thanks in advance.

Changed in brasero:
assignee: nobody → desktop-bugs
importance: Undecided → Medium
status: New → Incomplete
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:
status: Incomplete → Invalid
Revision history for this message
marco.pallotta (marco-pallotta) wrote :

I have attached two files:
- gdb-braser_-g.txt
- gdb-brasero.txt

The first is the backtrace of the command "brasero -g" that ends with segmentation fault (this is the issue I reported).
The second is the backtrace of the command "brasero" that ends with no errors.

Revision history for this message
marco.pallotta (marco-pallotta) wrote :
Revision history for this message
marco.pallotta (marco-pallotta) wrote :

Provided informations requested

Changed in brasero:
status: Invalid → New
Revision history for this message
marco.pallotta (marco-pallotta) wrote :

I forgot to say that the backtrace files were generated without debug symbols for the package yelp installed as posted in bug #255863 then converted by Sebastien Bacher to question 41547 (still not solved).

Revision history for this message
Pedro Villavicencio (pedro) wrote :

there's no backtrace on the files you attached, you don't need to install yelp that's only an example, what you need to install is brasero-dbgsym instead, are you still able to reproduce this? may you get another trace? thanks.

Changed in brasero:
status: New → Incomplete
Revision history for this message
marco.pallotta (marco-pallotta) wrote :

@Pedro, you are right! Evidently I didn't read what is written in https://wiki.ubuntu.com/DebuggingProgramCrash very well. Excuse me. I will do it again as soon as possible.

Revision history for this message
marco.pallotta (marco-pallotta) wrote :
Revision history for this message
marco.pallotta (marco-pallotta) wrote :
Revision history for this message
Pedro Villavicencio (pedro) wrote :

still no trace, you need to execute the commands at: https://wiki.ubuntu.com/Backtrace#Generation ; and if brasero -g is causing the crash you can run gdb as: gdb --args brasero -g ; thanks.

Revision history for this message
marco.pallotta (marco-pallotta) wrote :

I hope this is right, now.

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

the stacktrace has not debug symbol, did you install the brasero debug version?

Revision history for this message
marco.pallotta (marco-pallotta) wrote :

@Sebastien, I installed the brasero-dbgsym package.
If you want I try to reproduce the backtrace again to find if I was wrong in my previous attachment.

Revision history for this message
marco.pallotta (marco-pallotta) wrote :

I have attached brasero backtrace again. To avoid any misunderstanding I installed brasero-dbgsym before:

marco@dominus:~$ dpkg -l brasero-dbgsym
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Installed/Config-f/Unpacked/Failed-cfg/Half-inst/t-aWait/T-pend
|/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err: uppercase=bad)
||/ Nome Versione Descrizione
+++-==============-==============-============================================
ii brasero-dbgsym 0.7.1-3ubuntu1 debug symbols for package brasero

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
marco.pallotta (marco-pallotta) wrote :

Sebastien, in Jaunty the issue is fixed.

Revision history for this message
Pedro Villavicencio (pedro) wrote :

Thanks for the feedback, marking this as fixed then.

Changed in brasero (Ubuntu):
status: Incomplete → 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.