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 344775 - nautilus crashes sometimes
nautilus crashes sometimes
Status: RESOLVED INCOMPLETE
Product: nautilus
Classification: Core
Component: general
2.14.x
Other other
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2006-06-13 16:15 UTC by SK8T
Modified: 2006-10-14 00:58 UTC
See Also:
GNOME target: ---
GNOME version: 2.13/2.14



Description SK8T 2006-06-13 16:15:42 UTC
X-Mailer: bug-buddy 2.14.0
Subject: nautilus crashes sometimes

Distribution: Ubuntu 6.06 (dapper)
Package: nautilus
Severity: Normal
Version: GNOME2.14.1 2.14.x
Gnome-Distributor: Ubuntu
Synopsis: nautilus crashes sometimes
Bugzilla-Product: nautilus
Bugzilla-Component: general
Bugzilla-Version: 2.14.x
BugBuddy-GnomeVersion: 2.0 (2.14.1)
Description:
Description of the crash:
It crashes sometimes -- i don't know it exactly, but may I've reportet
this bug two times ago

Steps to reproduce the crash:
1. click on a file
2. crash
3. -

Expected Results:
nautilus crashes, bug buddy opens

How often does this happen?
1 in 100 times approx

Additional Information:
Ubuntu 6.06 (may contact the ubuntu developer it starts to disturb me)


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)
[Thread debugging using libthread_db enabled]
[New Thread -1225156928 (LWP 9128)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

Thread 1 (Thread -1225156928 (LWP 9128))

  • #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 strrchr
    from /lib/tls/i686/cmov/libc.so.6
  • #5 fm_directory_view_pop_up_location_context_menu
  • #6 g_main_context_is_owner
    from /usr/lib/libglib-2.0.so.0
  • #7 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #8 g_main_context_check
    from /usr/lib/libglib-2.0.so.0
  • #9 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #10 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #11 POA_Nautilus_MetafileFactory__fini
  • #12 __libc_start_main
    from /lib/tls/i686/cmov/libc.so.6
  • #13 ??
  • #0 __kernel_vsyscall




------- Bug created by bug-buddy at 2006-06-13 16:15 -------

Comment 1 Elijah Newren 2006-06-13 16:36:52 UTC
Appears to be a unique stack trace.
Comment 2 Christian Kirbach 2006-06-14 10:10:31 UTC
Thanks for the bug report. Unfortunately, that stack trace is not very useful in determining the cause of the crash. Can you get us one with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so.
Comment 3 André Klapper 2006-09-27 14:24:27 UTC
Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information Christian asked for.
Thanks!
Comment 4 André Klapper 2006-10-14 00:58:37 UTC
*** Bug 362012 has been marked as a duplicate of this bug. ***