After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 482487 - crash in Home Folder: right click on file obje...
crash in Home Folder: right click on file obje...
Status: RESOLVED INCOMPLETE
Product: nautilus
Classification: Core
Component: general
unspecified
Other All
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
: 550133 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2007-10-02 07:51 UTC by jerry
Modified: 2008-09-03 16:47 UTC
See Also:
GNOME target: ---
GNOME version: 2.19/2.20



Description jerry 2007-10-02 07:51:33 UTC
What were you doing when the application crashed?
right click on file object


Distribution: Ubuntu 5.10 (breezy)
Gnome Release: 2.20.0 2007-09-21 (Debian)
BugBuddy Version: 2.20.0

System: Linux 2.6.22-2-k7 #1 SMP Fri Aug 31 01:02:37 UTC 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10400000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome

Memory status: size: 96849920 vsize: 96849920 resident: 19193856 share: 9453568 rss: 19193856 rss_rlim: 4294967295
CPU usage: start_time: 1191088713 rtime: 1301 utime: 1202 stime: 99 cutime:1754 cstime: 259 timeout: 0 it_real_value: 0 frequency: 100

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

Using host libthread_db library "/lib/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread 0xb6b0fb80 (LWP 18589)]
0xb75a1bf1 in waitpid () from /lib/libpthread.so.0

Thread 1 (Thread 0xb6b0fb80 (LWP 18589))

  • #0 waitpid
    from /lib/libpthread.so.0
  • #1 g_spawn_sync
    from /usr/lib/libglib-2.0.so.0
  • #2 g_spawn_command_line_sync
    from /usr/lib/libglib-2.0.so.0
  • #3 ??
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #4 <signal handler called>
  • #5 ??
    from /usr/lib/nautilus/extensions-1.0/libdiff-ext.so
  • #6 ??
  • #7 ??
  • #8 ??
  • #0 waitpid
    from /lib/libpthread.so.0


----------- .xsession-errors (221227 sec old) ---------------------
WARNING: Assertion failure in downloads.c:4702: "NULL == sha1 || NULL == file_info || file_info->sha1 == sha1"
WARNING: Assertion failure in downloads.c:4702: "NULL == sha1 || NULL == file_info || file_info->sha1 == sha1"
WARNING: Assertion failure in downloads.c:4702: "NULL == sha1 || NULL == file_info || file_info->sha1 == sha1"
WARNING: Assertion failure in downloads.c:4702: "NULL == sha1 || NULL == file_info || file_info->sha1 == sha1"
WARNING: Assertion failure in downloads.c:4702: "NULL == sha1 || NULL == file_info || file_info->sha1 == sha1"
WARNING: Assertion failure in downloads.c:4702: "NULL == sha1 || NULL == file_info || file_info->sha1 == sha1"
WARNING: Assertion failure in downloads.c:4702: "NULL == sha1 || NULL == file_info || file_info->sha1 == sha1"
WARNING: Assertion failure in downloads.c:4702: "NULL == sha1 || NULL == file_info || file_info->sha1 == sha1"
WARNING: Assertion failure in downloads.c:4702: "NULL == sha1 || NULL == file_info || file_info->sha1 == sha1"
WARNING: Assertion failure in downloads.c:4702: "NULL == sha1 || NULL == file_info || file_info->sha1 == sha1"
WARNING: Assertion failure in downloads.c:4702: "NULL == sha1 || NULL == file_info || file_info->sha1 == sha1"
WARNING: Assertion failure in downloads.c:4702: "NULL == sha1 || NULL == file_info || file_info->sha1 == sha1"
WARNING: Assertion failure in downloads.c:4702: "NULL == sha1 || NULL == file_info || file_info->sha1 == sha1"
WARNING: Assertion failure in downloads.c:4702: "NULL == sha1 || NULL == file_info || file_info->sha1 
...Too much output, ignoring rest...
--------------------------------------------------
Comment 1 Susana 2007-10-07 18:44:27 UTC
Thanks for taking the time to report this bug.
Unfortunately, the 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 help fixing this by installing some debugging packages [1],
start the application as normal, and try to 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] Please install debug packages for nautilus, glib2, gtk2, pango, gnome-vfs2,
libgnome, and libgnomeui.

More details can be found here: http://live.gnome.org/GettingTraces

Comment 2 Sergio Infante Montero 2008-09-01 06:47:49 UTC
*** Bug 550133 has been marked as a duplicate of this bug. ***
Comment 3 Sergio Infante Montero 2008-09-03 16:47:00 UTC
*** Bug 550655 has been marked as a duplicate of this bug. ***