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 445410 - crash in Computer: Listening to songs with ...
crash in Computer: Listening to songs with ...
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-06-08 08:09 UTC by DrTurkeytootz
Modified: 2007-06-22 21:39 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description DrTurkeytootz 2007-06-08 08:09:52 UTC 
What were you doing when the application crashed?
Listening to songs with Helio and copying files to a blank cdr using cd/dvd creator


Distribution: openSUSE 10.2 (X86-64)
Gnome Release: 2.16.1 2006-11-28 (SUSE)
BugBuddy Version: 2.16.0

Memory status: size: 507215872 vsize: 507215872 resident: 23986176 share: 16678912 rss: 40665088 rss_rlim: 416399360
CPU usage: start_time: 1181138522 rtime: 12797 utime: 8525 stime: 4272 cutime:1365 cstime: 310 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/opt/gnome/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 47146534756992 (LWP 3982)]
(no debugging symbols found)
0x00002ae125f2bc5f in waitpid () from /lib64/libpthread.so.0

+ Trace 139299

Thread 1 (Thread 47146534756992 (LWP 3982))

  • #0 waitpid
    from /lib64/libpthread.so.0
  • #1 gnome_gtk_module_info_get
    from /opt/gnome/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 /opt/gnome/lib64/libglib-2.0.so.0
  • #6 g_log
    from /opt/gnome/lib64/libglib-2.0.so.0
  • #7 g_assert_warning
    from /opt/gnome/lib64/libglib-2.0.so.0
  • #8 nautilus_directory_async_state_changed
  • #9 fm_directory_view_bump_zoom_level
  • #10 g_closure_invoke
    from /opt/gnome/lib64/libgobject-2.0.so.0
  • #11 g_signal_override_class_closure
    from /opt/gnome/lib64/libgobject-2.0.so.0
  • #12 g_signal_emit_valist
    from /opt/gnome/lib64/libgobject-2.0.so.0
  • #13 g_signal_emit
    from /opt/gnome/lib64/libgobject-2.0.so.0
  • #14 fm_directory_view_bump_zoom_level
  • #15 nautilus_directory_async_state_changed
  • #16 nautilus_directory_async_state_changed
  • #17 nautilus_undo_transaction_unregister_object
  • #18 POA_Nautilus_MetafileMonitor__init
  • #19 POA_Nautilus_MetafileMonitor__init
  • #20 POA_Nautilus_MetafileMonitor__init
  • #21 g_closure_invoke
    from /opt/gnome/lib64/libgobject-2.0.so.0
  • #22 g_signal_override_class_closure
    from /opt/gnome/lib64/libgobject-2.0.so.0
  • #23 g_signal_emit_valist
    from /opt/gnome/lib64/libgobject-2.0.so.0
  • #24 g_signal_emit
    from /opt/gnome/lib64/libgobject-2.0.so.0
  • #25 gnome_vfs_volume_monitor_emit_pre_unmount
    from /opt/gnome/lib64/libgnomevfs-2.so.0
  • #26 gnome_vfs_volume_monitor_client_get_type
    from /opt/gnome/lib64/libgnomevfs-2.so.0
  • #27 dbus_connection_dispatch
    from /usr/lib64/libdbus-1.so.3
  • #28 dbus_server_setup_with_g_main
    from /usr/lib64/libdbus-glib-1.so.2
  • #29 g_main_context_dispatch
    from /opt/gnome/lib64/libglib-2.0.so.0
  • #30 g_main_context_prepare
    from /opt/gnome/lib64/libglib-2.0.so.0
  • #31 g_main_loop_run
    from /opt/gnome/lib64/libglib-2.0.so.0
  • #32 gtk_main
    from /opt/gnome/lib64/libgtk-x11-2.0.so.0
  • #33 POA_Nautilus_MetafileMonitor__init
  • #34 __libc_start_main
    from /lib64/libc.so.6
  • #35 g_cclosure_marshal_VOID__ENUM
  • #36 ??
  • #37 ??
  • #0 waitpid
    from /lib64/libpthread.so.0 






Comment 1


André Klapper





          2007-06-22 21:39:03 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 ***