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 352938 - crash on File Browser
crash on File Browser
Status: RESOLVED DUPLICATE of bug 349551
Product: nautilus
Classification: Core
Component: general
unspecified
Other All
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2006-08-26 06:00 UTC by acahalan
Modified: 2006-10-06 18:46 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description acahalan 2006-08-26 06:00:30 UTC 
What were you doing when the app crashed?:
I mounted a filesystem from an "su" shell in an xterm. Nautilus definitely should not bother me about this, crash or no crash. I get a zillion of these "quit unexpectedly" windows; they multiply when I move them out of my way. Of interest: I used the command-line gconf editor (gconfedit-2 maybe) to wipe the worthless ugly crud (home, trash, etc.) off my desktop background. Besides fixing the crash, please provide a very easy way to get rid of the stupid nonsense. I suggest right-click on the desktop offering a way to make the distracting icons go away, along with killing any associated processes.




Distribution: Fedora Core release 5.91 (FC6 Test2)
Gnome Release: 2.15.4 2006-07-12 (Red Hat, Inc)
BugBuddy Version: 2.15.0

Memmory status: size: 370188288 vsize: 370188288 resident: 14176256 share: 10010624 rss: 14176256 rss_rlim: -1
CPU usage: start_time: 1156571444 rtime: 17 utime: 9 stime: 8 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

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

(no debugging symbols found)
Using host libthread_db library "/lib64/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 46912496348496 (LWP 26074)]
(no debugging symbols found)
0x000000381f00dfbf in waitpid () from /lib64/libpthread.so.0

+ Trace 71017

Thread 1 (Thread 46912496348496 (LWP 26074))

  • #0 waitpid
    from /lib64/libpthread.so.0
  • #1 gnome_gtk_module_info_get
    from /usr/lib64/libgnomeui-2.so.0
  • #2 <signal handler called>
  • #3 raise
    from /lib64/libc.so.6
  • #4 abort
    from /lib64/libc.so.6
  • #5 g_logv
    from /lib64/libglib-2.0.so.0
  • #6 g_log
    from /lib64/libglib-2.0.so.0
  • #7 nautilus_directory_async_state_changed
  • #8 nautilus_directory_async_state_changed
  • #9 nautilus_directory_async_state_changed
  • #10 nautilus_directory_async_state_changed
  • #11 nautilus_undo_transaction_unregister_object
  • #12 egg_recent_item_unref
  • #13 g_hash_table_foreach
    from /lib64/libglib-2.0.so.0
  • #14 egg_recent_item_unref
  • #15 g_closure_invoke
    from /lib64/libgobject-2.0.so.0
  • #16 g_signal_override_class_closure
    from /lib64/libgobject-2.0.so.0
  • #17 g_signal_emit_valist
    from /lib64/libgobject-2.0.so.0
  • #18 g_signal_emit
    from /lib64/libgobject-2.0.so.0
  • #19 gnome_vfs_job_get_count
    from /usr/lib64/libgnomevfs-2.so.0
  • #20 g_main_context_dispatch
    from /lib64/libglib-2.0.so.0
  • #21 g_main_context_check
    from /lib64/libglib-2.0.so.0
  • #22 g_main_loop_run
    from /lib64/libglib-2.0.so.0
  • #23 gtk_main
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #24 POA_Nautilus_MetafileMonitor__init
  • #25 __libc_start_main
    from /lib64/libc.so.6
  • #26 ??
  • #27 ??
  • #28 ??
  • #0 waitpid
    from /lib64/libpthread.so.0 






Comment 1


André Klapper





          2006-10-06 18:46: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 349551 ***