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 160430 - Opening a Directory Tree Node
Opening a Directory Tree Node
Status: RESOLVED DUPLICATE of bug 123051
Product: nautilus
Classification: Core
Component: Navigation
unspecified
Other other
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
: 166751 329150 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2004-12-04 14:47 UTC by Andrés Álvarez Iglesias
Modified: 2006-02-28 22:15 UTC
See Also:
GNOME target: ---
GNOME version: 2.7/2.8



Description Andrés Álvarez Iglesias 2004-12-04 14:47:40 UTC
Distribution: Fedora Core release 3 (Heidelberg)
Package: nautilus
Severity: normal
Version: GNOME2.8.0 unspecified
Gnome-Distributor: Red Hat, Inc
Synopsis: Opening a Directory Tree Node
Bugzilla-Product: nautilus
Bugzilla-Component: Navigation
Bugzilla-Version: unspecified
BugBuddy-GnomeVersion: 2.0 (2.8.0)
Description:
Description of the crash:


Steps to reproduce the crash:
1. 
2. 
3. 

Expected Results:


How often does this happen?


Additional Information:



Debugging Information:

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

(no debugging symbols found)...Using host libthread_db library
"/lib/tls/libthread_db.so.1".
(no debugging symbols found)...(no debugging symbols found)...(no
debugging symbols found)...(no debugging symbols found)...(no debugging
symbols found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...[Thread debugging using libthread_db enabled]
[New Thread -151198016 (LWP 4945)]
[New Thread -183657552 (LWP 5564)]
[Thread debugging using libthread_db enabled]
[New Thread -151198016 (LWP 4945)]
[New Thread -183657552 (LWP 5564)]
[Thread debugging using libthread_db enabled]
[New Thread -151198016 (LWP 4945)]
[New Thread -183657552 (LWP 5564)]
[New Thread -170751056 (LWP 4957)]
[New Thread -170484816 (LWP 4956)]
[New Thread -170218576 (LWP 4955)]
[New Thread -169952336 (LWP 4954)]
[New Thread -169686096 (LWP 4953)]
[New Thread -165586000 (LWP 4950)]
[New Thread -165319760 (LWP 4949)]
[New Thread -165053520 (LWP 4948)]
[New Thread -164787280 (LWP 4947)]
[New Thread -154285136 (LWP 4946)]
(no debugging symbols found)...(no debugging symbols found)...(no
debugging symbols found)...(no debugging symbols found)...(no debugging
symbols found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...0x0011b7a2 in _dl_sysinfo_int80
() from /lib/ld-linux.so.2

Thread 12 (Thread -154285136 (LWP 4946))

  • #0 _dl_sysinfo_int80
    from /lib/ld-linux.so.2
  • #1 poll
    from /lib/tls/libc.so.6
  • #2 g_main_context_acquire
    from /usr/lib/libglib-2.0.so.0
  • #3 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #4 link_thread_io_context
    from /usr/lib/libORBit-2.so.0
  • #5 ??
    from /usr/lib/libglib-2.0.so.0
  • #6 ??
  • #7 g_static_private_free
    from /usr/lib/libglib-2.0.so.0




------- Bug moved to this database by unknown@bugzilla.gnome.org 2004-12-04 09:47 -------


Unknown platform unknown. Setting to default platform "Other".
Unknown milestone "unknown" in product "nautilus".
   Setting to default milestone for this product, '---'
Setting to default status "UNCONFIRMED".
Setting qa contact to the default for this product.
   This bug either had no qa contact or an invalid one.

Comment 1 Elijah Newren 2004-12-04 16:22:57 UTC
Appears to be a unique stack trace, according to the simple-dup-finder.  Is
there any chance you could install the glib2, gtk2, and nautilus debuginfo rpms
from http://download.fedora.redhat.com/pub/fedora/linux/core/3/i386/debug/, get
the crash again, and then paste the new stack trace with debugging symbols here?
Comment 2 Martin Wehner 2005-04-03 18:47:54 UTC
*** Bug 166751 has been marked as a duplicate of this bug. ***
Comment 3 Martin Wehner 2005-04-03 18:49:55 UTC
I think this is basically a dup of bug 123051.

*** This bug has been marked as a duplicate of 123051 ***
Comment 4 Christian Kirbach 2006-02-01 22:33:03 UTC
Martin I believe it is not a dup. The trace is different.

reopening. dup it again if I am mistaken.
Comment 5 Christian Kirbach 2006-02-01 22:33:21 UTC
*** Bug 329150 has been marked as a duplicate of this bug. ***
Comment 6 Martin Wehner 2006-02-28 22:15:56 UTC
Yeah, I'm pretty sure.

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