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 477792 - crash in Open Folder:
crash in Open Folder:
Status: RESOLVED DUPLICATE of bug 454799
Product: nautilus
Classification: Core
Component: general
2.18.x
Other All
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
: 478382 479625 484689 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2007-09-17 14:52 UTC by avishay.aton
Modified: 2008-02-27 21:08 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description avishay.aton 2007-09-17 14:52:36 UTC
Version: 2.18.3

What were you doing when the application crashed?



Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.3 2007-07-02 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.20-2925.13.fc7xen #1 SMP Tue Jul 17 10:38:27 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 185491456 vsize: 185491456 resident: 69480448 share: 46354432 rss: 69480448 rss_rlim: 4294967295
CPU usage: start_time: 1188127179 rtime: 21512 utime: 14782 stime: 6730 cutime:437 cstime: 229 timeout: 0 it_real_value: 0 frequency: 100

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

(no debugging symbols found)
Using host libthread_db library "/lib/i686/nosegneg/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1208248608 (LWP 4380)]
[New Thread -1317364848 (LWP 7598)]
(no debugging symbols found)
0x00249402 in __kernel_vsyscall ()

Thread 2 (Thread -1317364848 (LWP 7598))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/i686/nosegneg/libpthread.so.0
  • #2 ??
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 strstr
    from /lib/i686/nosegneg/libc.so.6
  • #5 ??
  • #6 ??
    from /usr/lib/libgnomevfs-2.so.0
  • #7 ??
  • #8 ??
  • #9 ??


----------- .xsession-errors ---------------------
warning: .dynamic section for "/usr/lib/libgstvideo-0.10.so.0" is not at the expected address
warning: difference appears to be caused by prelink, adjusting expectations
warning: .dynamic section for "/usr/lib/libgstaudio-0.10.so.0" is not at the expected address
warning: difference appears to be caused by prelink, adjusting expectations
warning: .dynamic section for "/usr/lib/libXtst.so.6" is not at the expected address
warning: difference appears to be caused by prelink, adjusting expectations
warning: .dynamic section for "/usr/lib/libXxf86vm.so.1" is not at the expected address
warning: difference appears to be caused by prelink, adjusting expectations
--------------------------------------------------
Comment 1 Susana 2007-10-08 19:57:46 UTC
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.
Could you please install some debugging packages [1], start the application 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, pango, gtk, glib, gnome-vfs, libgnome and
libgnomeui. More details can be found here:
http://live.gnome.org/GettingTraces

Comment 2 Susana 2007-10-08 19:57:57 UTC
*** Bug 478382 has been marked as a duplicate of this bug. ***
Comment 3 Susana 2007-10-08 19:58:03 UTC
*** Bug 479625 has been marked as a duplicate of this bug. ***
Comment 4 Susana 2007-10-08 19:58:27 UTC
*** Bug 484689 has been marked as a duplicate of this bug. ***
Comment 5 palfrey 2007-11-09 15:31:15 UTC
Possible duplicate of Bug 454799
Comment 6 Susana 2008-02-27 21:08:08 UTC
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.


*** This bug has been marked as a duplicate of 454799 ***