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 363535 - crash in CD/DVD Creator: veiwing files on my seco...
crash in CD/DVD Creator: veiwing files on my seco...
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: 2006-10-19 23:04 UTC by acw.phillips
Modified: 2006-10-19 23:08 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description acw.phillips 2006-10-19 23:04:02 UTC 
What were you doing when the application crashed?
veiwing files on my second HD, this is the third time it has occured whilst doing this


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

Memory status: size: 202924032 vsize: 202924032 resident: 33619968 share: 20897792 rss: 33619968 rss_rlim: -1
CPU usage: start_time: 1161298295 rtime: 351 utime: 329 stime: 22 cutime:0 cstime: 1 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/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 47303973206560 (LWP 5737)]
(no debugging symbols found)
0x00002b05cc87aeef in waitpid () from /lib/libpthread.so.0

+ Trace 77237

Thread 1 (Thread 47303973206560 (LWP 5737))

  • #0 waitpid
    from /lib/libpthread.so.0
  • #1 gnome_gtk_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #2 <signal handler called>
  • #3 g_str_hash
    from /usr/lib/libglib-2.0.so.0
  • #4 g_hash_table_lookup
    from /usr/lib/libglib-2.0.so.0
  • #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 ??
  • #11 nautilus_marshal_BOOLEAN__POINTER
  • #12 nautilus_marshal_BOOLEAN__POINTER
  • #13 eel_read_file_cancel
    from /usr/lib/libeel-2.so.2
  • #14 gnome_vfs_job_get_count
    from /usr/lib/libgnomevfs-2.so.0
  • #15 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #16 g_main_context_check
    from /usr/lib/libglib-2.0.so.0
  • #17 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #18 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #19 POA_Nautilus_MetafileMonitor__init
  • #20 __libc_start_main
    from /lib/libc.so.6
  • #21 ??
  • #22 ??
  • #23 ??
  • #0 waitpid
    from /lib/libpthread.so.0 






Comment 1


André Klapper





          2006-10-19 23:08:25 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 issue has been already fixed, please install the latest Nautilus updates provided by Ubuntu.

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