GNOME Bugzilla – Bug 380830
crash in CD/DVD Creator: Opening the properties of any ODP file
Last modified: 2007-02-10 08:01:27 UTC
What were you doing when the application crashed? Opening the properties of a ODP (OpenOffice Presentation). Distribution: Ubuntu 6.10 (edgy) Gnome Release: 2.16.1 2006-10-02 (Ubuntu) BugBuddy Version: 2.16.0 Memory status: size: 119500800 vsize: 0 resident: 119500800 share: 0 rss: 33124352 rss_rlim: 0 CPU usage: start_time: 1164880542 rtime: 0 utime: 649 stime: 0 cutime:340 cstime: 0 timeout: 309 it_real_value: 0 frequency: 0 Backtrace was generated from '/usr/bin/nautilus' (no debugging symbols found) Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1226938704 (LWP 17762)] [New Thread -1311638624 (LWP 18611)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 90511
Thread 1 (Thread -1226938704 (LWP 17762))
*** Bug 380815 has been marked as a duplicate of this bug. ***
Properties of any ODP (Open Office Presentation) crashes Nautilus (I have to force close it) - No custom open with applications for this file type - nautilus always crash but always the CD/DVD Creator.
Thanks for taking the time to report this bug. Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so. Thanks in advance! Also, I cannot reproduce this problem (with nautilus 2.16.3).
This problem is under Nautilus 2.16.1 (Ubuntu Edgy) not 2.16.3. It seems that many Ubuntu users are having a similar crash while doing different tasks that are usually unrelated to the CD/DVD creator (a search in Gnome Bugzilla shows 300+ bug report from Ubuntu users. http://bugzilla.gnome.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=crash+Creator&long_desc_type=substring&long_desc=Distribution%3A+Ubuntu&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_status=NEEDINFO&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailqa_contact2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0=) I will try to install the debugging information packages to be able to get the debugging symbols.
I understand your problem is with 2.16.1. However, if the problem is fixed in 2.16.3 (I don't know; I just know it doesn't seem to happen for me), then you are not going to achieve anything here. From the GNOME perspective, the bug would be fixed, and you would need to talk to Ubuntu and make them ship a more recent release which includes the fix. What I'm trying to say is: If nobody can reproduce the problem with the current stable version (2.16.3) then we'll resolve it as OBSOLETE. If, on the other hand, you can e.g. provide a file which causes the same problem to appear with 2.16.3, then the additional debugging info would be helpful. (As an aside, I don't understand what relevance you are trying to attribute to the 300+ bugs reported by Ubuntu users)
As already written: Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Could you please install some debugging packages [1], start nautilus as normal, and reproduce the crash, if possible? Once bug-buddy pops up, you can find the stacktrace in the "details", now containing way more information. Please copy that stacktrace and paste it as a comment here. Thanks in advance! [1] debugging packages for nautilus, glib, gtk, pango, gnome-vfs and libgnome(ui). More details can be found here: http://live.gnome.org/GettingTraces/DistroSpecificInstructions
I have installed the debugging packages for nautilus and CD creator. Although nautilus always hangs forever until I have to force quit, the bug buddy does not always appear. I managed to get the bug-buddy details. There was another method using commands but the live.gnome.org server seems to be down now. Distribution: Ubuntu 6.10 (edgy) Gnome Release: 2.16.1 2006-10-02 (Ubuntu) BugBuddy Version: 2.16.0 Memory status: size: 122802176 vsize: 0 resident: 122802176 share: 0 rss: 33923072 rss_rlim: 0 CPU usage: start_time: 1166363395 rtime: 0 utime: 327 stime: 0 cutime:178 cstime: 0 timeout: 149 it_real_value: 0 frequency: 0 Backtrace was generated from '/usr/bin/nautilus' Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread -1227462992 (LWP 13856)] 0xffffe410 in __kernel_vsyscall ()
+ Trace 94856
Thread 1 (Thread -1227462992 (LWP 13856))
I installed few more debugging packages Another trace using gdb (since I could not get the bugbuddy to popup):
+ Trace 94861
Thread 1 (Thread -1227327824 (LWP 15541))
Problem in evince. Here's my trace, looks a bit different from yours; with evince 0.7.0:
+ Trace 95408
Reassigning and confirming.
*** Bug 384992 has been marked as a duplicate of this bug. ***
Hm, really looks so.
*** Bug 365947 has been marked as a duplicate of this bug. ***
Is this bug related to #370491? is it still reproducible?
*** Bug 401885 has been marked as a duplicate of this bug. ***
I can not reproduce #370491 on 2.17.90 but I still reproduce this bug (bug #380830) on 2.17.90 (using Ubuntu feisty)
More info: This bug is still reproducible using Nautilus 2.7.90 and evince 0.71
It was fixed in head I suppose, please reopen if you still can reproduce it *** This bug has been marked as a duplicate of 370491 ***