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 430113 - crash in Computer: I was using the terminal...
crash in Computer: I was using the terminal...
Status: RESOLVED DUPLICATE of bug 362346
Product: nautilus
Classification: Core
Component: general
unspecified
Other All
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-04-15 22:00 UTC by Sharmarke Aden
Modified: 2007-04-15 22:43 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16



Description Sharmarke Aden 2007-04-15 22:00:50 UTC
What were you doing when the application crashed?
I was using the terminal. I executed "mvn clean package" and a second after it started I killed the application with ctrl+c.


Distribution: Ubuntu 6.10 (edgy)
Gnome Release: 2.16.1 2006-10-02 (Ubuntu)
BugBuddy Version: 2.16.0

Memory status: size: 125509632 vsize: 0 resident: 125509632 share: 0 rss: 32362496 rss_rlim: 0
CPU usage: start_time: 1176655088 rtime: 0 utime: 1360 stime: 0 cutime:1248 cstime: 0 timeout: 112 it_real_value: 0 frequency: 60

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 -1227495760 (LWP 5553)]
0xffffe410 in __kernel_vsyscall ()

Thread 1 (Thread -1227495760 (LWP 5553))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/tls/i686/cmov/libpthread.so.0
  • #2 libgnomeui_segv_handle
    at gnome-ui-init.c line 874
  • #3 <signal handler called>
  • #4 __kernel_vsyscall
  • #5 raise
    from /lib/tls/i686/cmov/libc.so.6
  • #6 abort
    from /lib/tls/i686/cmov/libc.so.6
  • #7 g_logv
    from /usr/lib/libglib-2.0.so.0
  • #8 g_log
    from /usr/lib/libglib-2.0.so.0
  • #9 g_assert_warning
    from /usr/lib/libglib-2.0.so.0
  • #10 nautilus_directory_async_state_changed
  • #11 fm_directory_view_bump_zoom_level
  • #12 g_cclosure_marshal_VOID__VOID
    from /usr/lib/libgobject-2.0.so.0
  • #13 g_value_set_boxed
    from /usr/lib/libgobject-2.0.so.0
  • #14 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #15 g_signal_chain_from_overridden
    from /usr/lib/libgobject-2.0.so.0
  • #16 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #17 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #18 fm_directory_view_bump_zoom_level
  • #19 fm_directory_view_bump_zoom_level
  • #20 nautilus_clipboard_monitor_emit_changed
  • #21 nautilus_directory_async_state_changed
  • #22 nautilus_icon_container_request_update_all
  • #23 g_source_is_destroyed
    from /usr/lib/libglib-2.0.so.0
  • #24 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #25 g_main_context_check
    from /usr/lib/libglib-2.0.so.0
  • #26 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #27 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #28 POA_Nautilus_MetafileMonitor__init
  • #29 __libc_start_main
    from /lib/tls/i686/cmov/libc.so.6
  • #30 ??
  • #0 __kernel_vsyscall

Comment 1 Pedro Villavicencio 2007-04-15 22:43:30 UTC
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers?


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