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 349211 - Nautilus error
Nautilus error
Status: RESOLVED INCOMPLETE
Product: nautilus
Classification: Core
Component: general
2.12.x
Other other
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
: 352463 354084 386323 453819 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2006-07-29 19:52 UTC by razgoth
Modified: 2007-07-19 13:09 UTC
See Also:
GNOME target: ---
GNOME version: 2.11/2.12



Description razgoth 2006-07-29 19:51:53 UTC
Distribution: Unknown
Package: nautilus
Severity: Normal
Version: GNOME2.12.2 2.12.2
Gnome-Distributor: SUSE
Synopsis: Nautilus error
Bugzilla-Product: nautilus
Bugzilla-Component: general
Bugzilla-Version: 2.12.2
BugBuddy-GnomeVersion: 2.0 (2.12.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 '/opt/gnome/bin/nautilus'

(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1228519232 (LWP 3903)]
[New Thread -1391305824 (LWP 3981)]
[New Thread -1391039584 (LWP 3980)]
[New Thread -1390773344 (LWP 3979)]
[New Thread -1232610400 (LWP 3968)]
[New Thread -1232344160 (LWP 3967)]
[New Thread -1230595168 (LWP 3946)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

Thread 1 (Thread -1228519232 (LWP 3903))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/libpthread.so.0
  • #2 gnome_init_with_popt_table
    from /opt/gnome/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 g_str_hash
    from /opt/gnome/lib/libglib-2.0.so.0
  • #5 g_hash_table_lookup
    from /opt/gnome/lib/libglib-2.0.so.0
  • #6 nautilus_file_should_show
    from /opt/gnome/lib/libnautilus-private.so.2
  • #7 nautilus_file_emit_changed
    from /opt/gnome/lib/libnautilus-private.so.2
  • #8 nautilus_directory_emit_change_signals
    from /opt/gnome/lib/libnautilus-private.so.2
  • #9 emit_change_signals_for_all_files
    from /opt/gnome/lib/libnautilus-private.so.2
  • #10 nautilus_metafile_monitor_new
    from /opt/gnome/lib/libnautilus-private.so.2
  • #11 _ORBIT_skel_small_Nautilus_MetafileMonitor_metafile_ready
    from /opt/gnome/lib/libnautilus-private.so.2
  • #12 ORBit_c_stub_invoke
    from /opt/gnome/lib/libORBit-2.so.0
  • #13 Nautilus_MetafileMonitor_metafile_ready
    from /opt/gnome/lib/libnautilus-private.so.2
  • #14 nautilus_metafile_get
    from /opt/gnome/lib/libnautilus-private.so.2
  • #15 eel_read_entire_file_async
    from /opt/gnome/lib/libeel-2.so.2
  • #16 _gnome_vfs_job_new
    from /opt/gnome/lib/libgnomevfs-2.so.0
  • #17 g_list_copy
    from /opt/gnome/lib/libglib-2.0.so.0
  • #18 g_main_context_dispatch
    from /opt/gnome/lib/libglib-2.0.so.0
  • #19 g_main_context_check
    from /opt/gnome/lib/libglib-2.0.so.0
  • #20 g_main_loop_run
    from /opt/gnome/lib/libglib-2.0.so.0
  • #21 gtk_main
    from /opt/gnome/lib/libgtk-x11-2.0.so.0
  • #22 main
  • #0 __kernel_vsyscall




------- Bug created by bug-buddy at 2006-07-29 19:52 -------


Unknown version 2.12.2 in product nautilus.  Setting version to "2.12.x".

Comment 1 Damien Durand 2006-07-30 06:58:51 UTC
Thanks for taking the time to report this bug.
This bug report isn't very useful because it doesn't describe the bug well. If you have time and can still reproduce the bug, please read http://bugzilla.gnome.org/bug-HOWTO.html and add a more useful description to this bug.

Someone can add this report to needinfo.
Comment 2 Joachim Noreiko 2006-07-30 07:07:44 UTC
In particular, there is no description of what you actions were doing in Nautilus when the crash took place. Have you been able to reproduce the bug by performing those same actions?
Comment 3 Karsten Bräckelmann 2006-08-22 23:33:14 UTC
*** Bug 352463 has been marked as a duplicate of this bug. ***
Comment 4 Sergej Kotliar 2006-09-03 13:56:31 UTC
*** Bug 354084 has been marked as a duplicate of this bug. ***
Comment 5 André Klapper 2006-10-24 12:30:16 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 asked for (see comment #1 and comment #2).
Thanks!
Comment 6 Bruno Boaventura 2006-12-17 14:07:27 UTC
*** Bug 386323 has been marked as a duplicate of this bug. ***
Comment 7 André Klapper 2007-07-19 13:09:49 UTC
*** Bug 453819 has been marked as a duplicate of this bug. ***