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 369156 - crash in CD/DVD Creator: I clicked on then home s...
crash in CD/DVD Creator: I clicked on then home s...
Status: RESOLVED DUPLICATE of bug 350975
Product: nautilus
Classification: Core
Component: general
unspecified
Other All
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2006-11-02 00:18 UTC by bodman.delphi
Modified: 2006-11-02 00:56 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description bodman.delphi 2006-11-02 00:18:16 UTC 
What were you doing when the application crashed?
I clicked on then home shortcut in my desktop ...


Distribution: Fedora Core release 6 (Zod)
Gnome Release: 2.16.0 2006-09-04 (Red Hat, Inc)
BugBuddy Version: 2.16.0

Memory status: size: 78995456 vsize: 0 resident: 78995456 share: 0 rss: 21381120 rss_rlim: 0
CPU usage: start_time: 1162418713 rtime: 0 utime: 446 stime: 0 cutime:418 cstime: 0 timeout: 28 it_real_value: 0 frequency: 0

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 -1208550656 (LWP 2799)]
(no debugging symbols found)
0x00d98402 in __kernel_vsyscall ()

+ Trace 81680

Thread 1 (Thread -1208550656 (LWP 2799))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/libpthread.so.0
  • #2 gnome_gtk_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 g_str_hash
    from /lib/libglib-2.0.so.0
  • #5 g_hash_table_lookup
    from /lib/libglib-2.0.so.0
  • #6 nautilus_file_get_uri
  • #7 nautilus_file_get_uri
  • #8 nautilus_directory_async_state_changed
  • #9 nautilus_directory_async_state_changed
  • #10 nautilus_undo_transaction_unregister_object
  • #11 ORBit_c_stub_invoke
    from /usr/lib/libORBit-2.so.0
  • #12 g_cclosure_marshal_VOID__ENUM
  • #13 nautilus_marshal_BOOLEAN__POINTER
  • #14 nautilus_marshal_BOOLEAN__POINTER
  • #15 eel_read_entire_file_async
    from /usr/lib/libeel-2.so.2
  • #16 gnome_vfs_async_get_job_limit
    from /usr/lib/libgnomevfs-2.so.0
  • #17 gnome_vfs_async_get_job_limit
    from /usr/lib/libgnomevfs-2.so.0
  • #18 g_source_is_destroyed
    from /lib/libglib-2.0.so.0
  • #19 g_main_context_dispatch
    from /lib/libglib-2.0.so.0
  • #20 g_main_context_check
    from /lib/libglib-2.0.so.0
  • #21 g_main_loop_run
    from /lib/libglib-2.0.so.0
  • #22 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #23 POA_Nautilus_MetafileMonitor__init
  • #24 __libc_start_main
    from /lib/libc.so.6
  • #25 g_cclosure_marshal_VOID__ENUM
  • #0 __kernel_vsyscall 






Comment 1


Behdad Esfahbod





          2006-11-02 00:56:50 UTC
        



Thanks for taking the time to report this bug.
Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so. Thanks in advance!
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 350975 ***