Ubuntu
nautilus package

Nautilus crashed. See info generated by bug buddy below:

Bug #14488 reported by Jery Wang
12
Affects Status Importance Assigned to Milestone
nautilus (Ubuntu)
Invalid
Medium
Sebastien Bacher

Bug Description

From: <>
To: <email address hidden>
X-Mailer: bug-buddy 2.10.0
Subject: Openning DVD+/-RW drive crash nautilus

Distribution: Debian 3.1
Package: nautilus
Severity: normal
Version: GNOME2.10.0 2.10.0
Gnome-Distributor: Ubuntu
Synopsis: Openning DVD+/-RW drive crash nautilus
Bugzilla-Product: nautilus
Bugzilla-Component: general
Bugzilla-Version: 2.10.0
BugBuddy-GnomeVersion: 2.0 (2.10.0)
Description:
Description of the crash:
I just installed LG DVD-R, DVD+R, DVD-RW, DVD+RW, DVD-ROM, CD-R, CD-RW,
CDR and I put DVD+RW inside.
The DVD is auto-detected and CD icon pops up on the desktop. But when I
double click window appears and dissappear so fast.
I tried to open nautilus and try to browse the DVD folder, nautilus
crashed immediately without being able to show the DVD content.

The DVD+RW already contains some file.

Steps to reproduce the crash:
1. Put DVD+RW inside the Drive
2. DVD is auto detected
3. Either double click the CD icon on the desktop or open nautilus and
browse, both crashed.

Expected Results:
Should be able to browse DVD+RW that already has some files inside.

How often does this happen?
always.

Additional Information:

 The DVD+RW was created by HP DVD writer previously on Windows
Platform.

Debugging Information:

Backtrace was generated from '/usr/bin/nautilus'

(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".

Revision history for this message
Jery Wang (jery-wang2002) wrote :

> The DVD is auto-detected and CD icon pops up on the desktop. But when I
> double click window appears and dissappear so fast.

A error dialog:
Error Displaying Folder

The folder contents could not be displayed.

You do not have the permissions necessary to view the contents of "cdrecorder"

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

> Backtrace was generated from '/usr/bin/nautilus'
>
> (no debugging symbols found)
> Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".

Can you copy the backtrace is the bug (with nautilus-dbg libgnomevfs2-0-dbg
installed) ? That's the useful part in a crash.

Revision history for this message
Jery Wang (jery-wang2002) wrote :

>
> Can you copy the backtrace is the bug (with nautilus-dbg libgnomevfs2-0-dbg
> installed) ? That's the useful part in a crash.

I have instaled both but I don't know how to capture the bug. The bug buddy is
not activated, unlike the first one.

However, I tried to su in terminal and run nautilus as root. I can see the
contents and nautilus does not crash.

This is my fstab content, in case needed:

# /etc/fstab: static file system information.
#
# <file system> <mount point> <type> <options> <dump> <pass>
proc /proc proc defaults 0 0
/dev/hda1 / ext3 defaults,errors=remount-ro 0 1
/dev/hda5 none swap sw 0 0
/dev/hdc /media/cdrom0 udf,iso9660 ro,user,noauto 0 0
/dev/fd0 /media/floppy0 auto rw,user,noauto 0 0

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

to get a backtrace:

- gnome-session-remove nautilus
- gdb nautilus
(gdb) r
.. crash ...
(gdb) thread apply all bt

Revision history for this message
Jery Wang (jery-wang2002) wrote :

(In reply to comment #4)
> to get a backtrace:
>
> - gnome-session-remove nautilus
> - gdb nautilus
> (gdb) r
> .. crash ...
> (gdb) thread apply all bt

The problem has disappeared.

I did change the fstab to become:

# /etc/fstab: static file system information.
#
# <file system> <mount point> <type> <options> <dump> <pass>
proc /proc proc defaults 0 0
/dev/hda1 / ext3 defaults,errors=remount-ro 0 1
/dev/hda5 none swap sw 0 0
/dev/hdc /media/cdrom0 udf,iso9660 ro,user,noauto 0 0
/dev/hdd /media/dvdrw auto defaults,user,noauto 0 0
/dev/fd0 /media/floppy0 auto rw,user,noauto 0 0

My DVD writer is hdd

Maybe because I put (I got it by googling around)
/dev/hdd /media/dvdrw auto defaults,user,noauto 0 0

then the problem disappear?

Or is it because I update very regularly every hour or so?

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

I don't know. The bug is fixed, I'm closing it. Feel free to reopen if you get
it again.

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

Other bug subscribers

Remote bug watches

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