nautilus video preview engenders crashes

[Julien Thomas]

Binary package hint: nautilus

SInce a few days, nautilus repeatedly crash when videos are on the current folder processed by it.
I beliew that this as something to do with the video previewing, so the title.

I got also a strange bug in apport.log, see the information below. I do not assure that this has to do something with it, but
I think it is.

-- apport.log --
(pid 7382) Thu Nov 22 08:46:19 2007: called for pid 6513, signal 11
apport (pid 7382) Thu Nov 22 08:46:19 2007: executable: /usr/bin/trackerd (command line "trackerd")
apport (pid 7382) Thu Nov 22 08:46:19 2007: apport: report /var/crash/_usr_bin_trackerd.1000.crash already exists and unseen, doing nothing to avoid disk usage DoS

 ls /var/crash/_usr_bin_trackerd.1000.crash -l
6279033 2007-11-21 13:55 /var/crash/_usr_bin_trackerd.1000.crash

Step to reproduce
- update the system to its last version
- launch Nautilus
- use Nautilus to navigate a folder with a video inside

Actual results
Nautilus is freezing

Expected result
Video preview instead of a standard icon for the video file

Current solution
kill nautilus

[Pedro Villavicencio (pedro)]

Thanks for your bug report. Please try to obtain a backtrace http://wiki.ubuntu.com/DebuggingProgramCrash and attach the file to the bug report. This will greatly help us in tracking down your problem.

[Julien Thomas (julien-thomas-1)]

Unfortunately,

the bug report do not give any relevant informations.
As nautilus does not crash but freeze, I have to kill it with the "force to quit" and no real informations is obtained, see the example of the result file below.

(gdb) handle SIG33 pass nostop noprint
Signal Stop Print Pass to program Description
SIG33 No No Yes Real-time event 33
(gdb) set pagination 0
(gdb) run
Starting program: /usr/bin/nautilus
[Thread debugging using libthread_db enabled]
[New Thread -1227651408 (LWP 7579)]
[New Thread -1229689968 (LWP 7582)]
[New Thread -1238135920 (LWP 7585)]
[New Thread -1246528624 (LWP 7586)]
[New Thread -1254921328 (LWP 7587)]
[New Thread -1263314032 (LWP 7588)]

Program exited normally.
(gdb) backtrace full
No stack.
(gdb) info registers
The program has no registers now.
(gdb) thread apply all backtrace
(gdb) quit
(END)

[Julien Thomas (julien-thomas-1)]

For a quite uncomprehended reason, nautilus has generated logs last day (I discovered them today).
Maybe due to the dbgm package install (though it occurred a few weeks ago ?)

So, here are examples of the log (available as an attachment).

===== BEGIN MILESTONES =====
0x8177898 2007/12/04 16:58:47.6217 (GLog): invalid uninstantiatable type `(null)' in cast to `NautilusFile'
0x8177898 2007/12/04 16:58:47.6218 (GLog): nautilus_file_get_uri: assertion `NAUTILUS_IS_FILE (file)' failed
0x8177898 2007/12/04 16:58:47.6218 (GLog): nautilus_file_is_gone: assertion `NAUTILUS_IS_FILE (file)' failed
0x8177898 2007/12/04 16:58:47.6220 (GLog): nautilus_file_ref: assertion `NAUTILUS_IS_FILE (file)' failed
0x8177898 2007/12/04 16:58:47.7223 (USER): debug log dumped due to signal 11
0x8177898 2007/12/04 16:58:47.7239 (USER): debug log dumped due to signal 11

[Pedro Villavicencio (pedro)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please follow these instuctions to have apport report a new bug about your crash that can be dealt with by the automatic retracer.
If you are using Ubuntu with the Gnome desktop environment - launch nautilus and navigate to your /var/crash directory and double click on the crash report you wish to submit.
 I'm closing this bug report since the process outlined above will automatically open a new bug report which can then dealt with more efficiently. Thanks in advance for your cooperation and understanding.

[Julien Thomas (julien-thomas-1)]

Unfortunately, I find only one crash log on /var/crash (and it is the only one relevant crash file) _usr_bin_trackerd.1000.crash
As its name indicates, and as the "report program" indicates, it is about trackerd and not nautilus.

So, not a solution, and I did not open a new bug report.

-- Julien Thomas

[Julien Thomas (julien-thomas-1)]

I will add further information,in order to restart this thread which seems to have been forgotten ...

The first remark is that the bug still occured when I try to access a directory with media contents, though no relevant backtrack can be recovered ...

This bug may be related to another one: when I try to watch clips (not tested for videos) in totem, the X server sometimes crash and put my back to the loggin screen.
The following steps can though be produced :
- login
- view media content (video | audio)
- ...
- view media content (video | audio) ==> crash

I know that with no relevant backtrack, it won't be very easy to analyze this bug, so I will try to get some. Hope others may be able to get some too ...

[Adam Stovicek (arstovicek)]

I've been having the same kind of issues but with folders containing audio clips. I have seen no ill effects when browsing folders with video files. After some initial trial and error learning how to perform a backtrace, the one for Nautilus I have attached here. Hope it helps. I don't know enough to make heads or tails of it.

For anyone else that needs help in creating a backtrace, I installed nautilus-dbg from the repositories and followed the directions for backtracing at https://wiki.ubuntu.com/Backtrace for an already running process.

[Adam Stovicek (arstovicek)]

And here's a little additional backtrace for you. During this backtrace I can't even get nautilus to respond, not even to open a browser window, when initiating the backtrace. As soon as I attach the PID, I can't get nautilus to do anything. I initiate the final steps of the backtrace and quit gdb. As soon as I quit gdb and detach it from the PID, nautilus pops open a browser window much like it does after killing it. The issue with the audio files continues afterward.