nautilus crashed with SIGSEGV in start_thread()

Bug #344371 reported by Ian! D. Allen on 2009-03-17
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
brasero (Ubuntu)
Medium
Unassigned

Bug Description

Binary package hint: nautilus

Running fully upgraded (March 17) jaunty inside VMware Workstation.
When I use Workstation to attach any ISO image to the virtual IDE CD, nautilus starts crashing repeatedly,
filling up the task bar with failed instances.
Disconnecting the CDROM stops the crashing and the task bar eventually clears.
Attaching the *real* CDROM drive to the
virtual CD works fine - no crashing.

This does not happen under 8.10.

I've reported this before with earlier versions of nautilus but Apport didn't offer to merge this dump
with my previous submissions, so I'll leave it to you to figure out how to do that.

ProblemType: Crash
Architecture: i386
DistroRelease: Ubuntu 9.04
ExecutablePath: /usr/bin/nautilus
Package: nautilus 1:2.26.0-0ubuntu1
ProcCmdline: nautilus
ProcEnviron:
 PATH=(custom, user)
 LANG=en_CA.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: nautilus
StacktraceTop:
 ?? () from /usr/lib/libbrasero-media.so.0
 ?? () from /usr/lib/libbrasero-media.so.0
 ?? () from /usr/lib/libbrasero-media.so.0
 ?? () from /usr/lib/libglib-2.0.so.0
 start_thread () from /lib/tls/i686/cmov/libpthread.so.0
Title: nautilus crashed with SIGSEGV in start_thread()
Uname: Linux 2.6.28-10-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Ian! D. Allen (idallen) wrote :
Pedro Villavicencio (pedro) wrote :

this is more like a brasero one, reassigning.

Changed in brasero (Ubuntu):
importance: Undecided → Medium

StacktraceTop:brasero_medium_get_page_2A_write_speed_desc (self=<value optimized out>,
brasero_medium_init_real (object=0x8474158,
brasero_medium_probe_thread (self=0x8474158)
g_thread_create_proxy (data=0x84bb6e0)
start_thread () from /lib/tls/i686/cmov/libpthread.so.0

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers