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 146212 - nautilus crashed on selecting the "My Computer" menu item
nautilus crashed on selecting the "My Computer" menu item
Status: RESOLVED DUPLICATE of bug 137654
Product: nautilus
Classification: Core
Component: general
2.6.x
Other other
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2004-05-31 20:19 UTC by Ilguiz Latypov
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: 2.5/2.6



Description Ilguiz Latypov 2004-07-09 01:32:18 UTC
Distribution: Debian testing/unstable
Package: nautilus
Severity: normal
Version:  2.6.1
Synopsis: nautilus crashed on selecting the "My Computer" menu item
Bugzilla-Product: nautilus
Bugzilla-Component: general
Bugzilla-Version: 2.6.1
BugBuddy-GnomeVersion: 2.0 (2.6.1.1)
Description:
Description of the crash:

Pooh!

Steps to reproduce the crash:
1. Open the Network window.
2. Double-click the MS Windows Network line.
3. Choose the "My Computer" menu item.

Expected Results:

I would expect another window to open.

How often does this happen?

Once.  Haven't tried again.

Additional Information:

Debian unstable, updated May 31, 2004.
Includes Gnome 2.6.



Debugging Information:

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)...(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 1090331072 (LWP 7637)]
[New Thread 1104006064 (LWP 7662)]
[Thread debugging using libthread_db enabled]
[New Thread 1090331072 (LWP 7637)]
[New Thread 1104006064 (LWP 7662)]
[Thread debugging using libthread_db enabled]
[New Thread 1090331072 (LWP 7637)]
[New Thread 1104006064 (LWP 7662)]
(no debugging symbols found)...[New Thread 1103739824 (LWP 7661)]
(no debugging symbols found)...[New Thread 1103473584 (LWP 7660)]
(no debugging symbols found)...[New Thread 1103195056 (LWP 7638)]
(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)...0xffffe410 in __kernel_vsyscall
()
  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/tls/i686/cmov/libpthread.so.0
  • #2 libgnomeui_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 strcmp
    from /lib/tls/i686/cmov/libc.so.6
  • #5 ??
    from /usr/lib/gnome-vfs-2.0/modules/libcomputer.so
  • #6 ??
  • #7 ??
  • #8 pthread_mutex_unlock
    from /lib/tls/i686/cmov/libpthread.so.0
  • #9 ??
    from /usr/lib/gnome-vfs-2.0/modules/libcomputer.so
  • #10 ??
  • #11 ??
  • #12 ??
  • #13 ??
    from /usr/lib/gnome-vfs-2.0/modules/libcomputer.so
  • #14 ??
  • #15 ??
  • #16 ??
  • #17 g_free
    from /usr/lib/libglib-2.0.so.0




------- Bug moved to this database by unknown@bugzilla.gnome.org 2004-07-08 21:32 -------


Unknown version 2.6.1 in product nautilus. Setting version to "1.0.x".
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 Martin Wehner 2004-07-10 18:44:51 UTC
Thanks for the bug report. Unfortunately, that stack trace is not very useful in
determining the cause of the crash. Please make sure that the package was
compiled with debugging symbols and see
http://bugzilla.gnome.org/getting-traces.cgi for more information about useful
stack traces.
Comment 2 Olav Vitters 2004-07-30 18:50:53 UTC
Thanks for the bug report. This particular bug has already been reported into
our bug tracking system, but please feel free to report any further bugs you find.

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