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 473889 - crash in Computer: Inserted Philips Audiogo...
crash in Computer: Inserted Philips Audiogo...
Status: RESOLVED DUPLICATE of bug 343488
Product: nautilus
Classification: Core
Component: general
unspecified
Other All
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-09-05 12:20 UTC by Hendrik Maryns
Modified: 2007-09-05 15:40 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description Hendrik Maryns 2007-09-05 12:20:51 UTC 
What were you doing when the application crashed?
Inserted Philips Audiogogear into USB bus.  Meanwhile, Kaffeine, Firefox, Thunderbird, Eclipse, Nautilus were running.


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

Memory status: size: 386064384 vsize: 386064384 resident: 12328960 share: 17911808 rss: 30240768 rss_rlim: 1792762880
CPU usage: start_time: 1188987874 rtime: 390 utime: 364 stime: 26 cutime:10 cstime: 6 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 47424521880160 (LWP 4031)]
0x00002b21df459c5f in waitpid () from /lib64/libpthread.so.0

+ Trace 160624

Thread 1 (Thread 47424521880160 (LWP 4031))

  • #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 g_str_hash
    at gstring.c line 95
  • #4 g_hash_table_lookup
    at ghash.c line 231
  • #5 nautilus_file_get_uri
  • #6 nautilus_file_get_uri
  • #7 nautilus_directory_async_state_changed
  • #8 nautilus_directory_async_state_changed
  • #9 nautilus_undo_transaction_unregister_object
  • #10 g_cclosure_marshal_VOID__ENUM
    at gmarshal.c line 334
  • #11 nautilus_marshal_BOOLEAN__POINTER
  • #12 nautilus_marshal_BOOLEAN__POINTER
  • #13 eel_read_entire_file_async
    from /opt/gnome/lib64/libeel-2.so.2
  • #14 dispatch_job_callback
    at gnome-vfs-job.c line 218
  • #15 g_main_context_dispatch
    at gmain.c line 2045
  • #16 g_main_context_iterate
    at gmain.c line 2677
  • #17 g_main_loop_run
    at gmain.c line 2881
  • #18 gtk_main
    from /opt/gnome/lib64/libgtk-x11-2.0.so.0
  • #19 POA_Nautilus_MetafileMonitor__init
  • #20 __libc_start_main
    from /lib64/libc.so.6
  • #21 g_cclosure_marshal_VOID__ENUM
    at gmarshal.c line 334
  • #22 ??
  • #23 ??
  • #0 waitpid
    from /lib64/libpthread.so.0 






Comment 1


palfrey





          2007-09-05 15:40:07 UTC
        



Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.


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