brasero crashed with SIGSEGV in g_file_get_path()

Bug #479433 reported by Josip Bakić
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
brasero (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Binary package hint: brasero

Hi!

After successfully burning 3 DVDs, I closed the Brasero window. It froze for a couple of seconds, and I got this bug report that I'm submitting here.

ProblemType: Crash
Architecture: i386
Date: Mon Nov 9 20:22:50 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/brasero
NonfreeKernelModules: fglrx
Package: brasero 2.28.2-0ubuntu1
ProcCmdline: brasero
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
SegvAnalysis:
 Segfault happened at: 0x332df8 <g_file_get_path+40>: mov (%esi),%edi
 PC (0x00332df8) ok
 source "(%esi)" (0x0000007b) not located in a known VMA region (needed readable region)!
 destination "%edi" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: brasero
StacktraceTop:
 g_file_get_path () from /usr/lib/libgio-2.0.so.0
 ?? ()
 ?? ()
 ?? () from /usr/lib/libgio-2.0.so.0
 ?? () from /usr/lib/libgio-2.0.so.0
Title: brasero crashed with SIGSEGV in g_file_get_path()
Uname: Linux 2.6.31-14-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
Josip Bakić (josip-bakic) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt (retraced)

StacktraceTop:g_file_get_path () from /usr/lib/libgio-2.0.so.0
g_proxy_mount_has_mount_path (mount=0x90ebd50,
get_mount_for_mount_path (mount_path=0x90d2718 "/",
?? () from /usr/lib/libgio-2.0.so.0
?? () from /usr/lib/libgio-2.0.so.0

Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt (retraced)
Changed in brasero (Ubuntu):
importance: Undecided → Medium
tags: removed: need-i386-retrace
visibility: private → public
Revision history for this message
Pedro Villavicencio (pedro) wrote :

is this reproducible everytime?

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

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to New. Thanks again!.

Changed in brasero (Ubuntu):
status: Incomplete → Invalid
Revision history for this message
Josip Bakić (josip-bakic) wrote :

I apologize for not responding, I was busy at the time you asked, and later I completely forgot.

Anyways, I've burned some DVDs in the meantime and this did not happen again. It hasn't crashed again. Though, brasero often acts strange after burning, and I'm developing a habit of restarting it after each burn. Can't remember the exact details of the odd behaviour. Not sure if this bug holds any relevance here after this, I'll reopen it just to be sure this reaches you.

Thank you!

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

no, let's close it for now, thanks for the feedback though.

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