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.
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
** Changed in: totem (Ubuntu)
Status: New => Invalid
--
nautilus video preview engenders crashes
https://bugs.launchpad.net/bugs/164452
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing list
desktop-bugs@l
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
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.
-- Julie
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
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:
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
SignalStop
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.
** Changed in: nautilus (Ubuntu)
Importance: Undecided => Medium
Assignee: (unassigned)
