nautilus crashed with SIGSEGV in brasero_scsi_command_issue_sync()

Bug #328344 reported by halovivek
8
Affects Status Importance Assigned to Milestone
brasero (Ubuntu)
Invalid
Medium
Ubuntu Desktop Bugs

Bug Description

Binary package hint: nautilus

installed the updates after restart got this error.

ProblemType: Crash
Architecture: amd64
CrashCounter: 1
DistroRelease: Ubuntu 9.04
ExecutablePath: /usr/bin/nautilus
Package: nautilus 1:2.25.4-0ubuntu1
ProcCmdline: nautilus
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: nautilus
StacktraceTop:
 brasero_scsi_command_issue_sync ()
 brasero_mmc2_get_configuration_feature ()
 ?? () from /usr/lib/libbrasero-media.so.0
 ?? () from /usr/lib/libbrasero-media.so.0
 g_thread_create_proxy (data=0x111b280)
Title: nautilus crashed with SIGSEGV in brasero_scsi_command_issue_sync()
Uname: Linux 2.6.28-7-generic x86_64
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

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

StacktraceTop:brasero_mmc2_get_configuration_feature (
brasero_medium_init_real (object=0x119ee50,
brasero_medium_probe_thread (self=0x119ee50)
g_thread_create_proxy (data=0x111b280)
start_thread () from /lib/libpthread.so.0

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
Changed in nautilus:
importance: Undecided → Medium
Revision history for this message
Sebastien Bacher (seb128) wrote :

the crash is a libbrasero one

Revision history for this message
Pedro Fragoso (ember) wrote :

Thanks for your bug report. Does this happens with brasero 2.25.90 ? If yes mind trying a better backtrace http://wiki.ubuntu.com/DebuggingProgramCrash some symbols are missing

Changed in brasero:
assignee: nobody → ubuntu-desktop
status: New → Incomplete
Pedro Fragoso (ember)
Changed in brasero:
assignee: ubuntu-desktop → desktop-bugs
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:
status: Incomplete → 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.