brasero crashed with SIGSEGV in brasero_file_node_is_ancestor()

Bug #574771 reported by Matteo Settenvini on 2010-05-03
This bug affects 3 people
Affects Status Importance Assigned to Milestone
brasero (Ubuntu)

Bug Description

Binary package hint: brasero

Brasero often crashes when removing a folder from a project. For example:

1. add a complex structure to your project, with a couple of levels of folders + files. Take your home, for example.
2. order everything by name
3. try to delete some directories at different levels of the hierarchy. It will randomly crash.

Happens randomly, but really often.

ProblemType: Crash
DistroRelease: Ubuntu 10.04
Package: brasero 2.30.0-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.32-22.33-generic
Uname: Linux 2.6.32-22-generic x86_64
Architecture: amd64
Date: Mon May 3 22:44:47 2010
ExecutablePath: /usr/bin/brasero
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta amd64 (20100406.1)
ProcCmdline: brasero
 Segfault happened at: 0x7ff8fcd04e40 <brasero_file_node_is_ancestor+16>: mov (%rsi),%rsi
 PC (0x7ff8fcd04e40) ok
 source "(%rsi)" (0x00000001) not located in a known VMA region (needed readable region)!
 destination "%rsi" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: brasero
 brasero_file_node_is_ancestor ()
 ?? () from /usr/lib/
 g_hash_table_foreach () from /lib/
 brasero_file_monitor_foreach_cancel ()
 ?? () from /usr/lib/
Title: brasero crashed with SIGSEGV in brasero_file_node_is_ancestor()
UserGroups: adm admin audio cdrom dialout lpadmin plugdev sambashare

Matteo Settenvini (tchernobog) wrote :
visibility: private → public

 brasero_file_node_is_ancestor (parent=0x154e930, node=0x1)
 brasero_file_monitor_foreach_cancel_file_cb (
 IA__g_hash_table_foreach (hash_table=0xb28ca0,
 brasero_file_monitor_foreach_cancel (self=0xa07c60,
 brasero_data_project_node_removed (self=0xa07c60,

Changed in brasero (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Pedro Villavicencio (pedro) wrote :

Thank you for your bug report. This bug has been reported to the developers of the software. You can track it and make comments at:

Changed in brasero (Ubuntu):
status: New → Triaged
Changed in brasero:
status: Unknown → New
Changed in brasero:
importance: Unknown → Critical
Changed in brasero:
status: New → Expired
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.