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 385092 - crash in CD/DVD Creator: I just create a symbolic...
crash in CD/DVD Creator: I just create a symbolic...
Status: RESOLVED DUPLICATE of bug 364674
Product: nautilus
Classification: Core
Component: general
unspecified
Other All
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2006-12-12 15:58 UTC by ph356
Modified: 2006-12-12 21:04 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description ph356 2006-12-12 15:58:23 UTC 
What were you doing when the application crashed?
I just create a symbolic link in a folder. Then I use the file browser to see whether the link is there. First I can't see it. Then I press the go to up directory then back again. The icon for the link just flashed, then disppear again. Then it crashed.


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: 527130624 vsize: 527130624 resident: 43712512 share: 24190976 rss: 43712512 rss_rlim: -1
CPU usage: start_time: 1165932373 rtime: 3842 utime: 3350 stime: 492 cutime:2 cstime: 10 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/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 46912496418256 (LWP 2775)]
(no debugging symbols found)
0x00000039a6e0d96f in waitpid () from /lib64/libpthread.so.0

+ Trace 93573

Thread 1 (Thread 46912496418256 (LWP 2775))

  • #0 waitpid
    from /lib64/libpthread.so.0
  • #1 gnome_gtk_module_info_get
    from /usr/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 /lib64/libglib-2.0.so.0
  • #6 g_log
    from /lib64/libglib-2.0.so.0
  • #7 g_assert_warning
    from /lib64/libglib-2.0.so.0
  • #8 nautilus_file_is_directory
  • #9 nautilus_file_is_directory
  • #10 nautilus_file_get_uri
  • #11 nautilus_file_ref
  • #12 nautilus_directory_async_state_changed
  • #13 nautilus_directory_async_state_changed
  • #14 gnome_vfs_async_get_job_limit
    from /usr/lib64/libgnomevfs-2.so.0
  • #15 gnome_vfs_async_get_job_limit
    from /usr/lib64/libgnomevfs-2.so.0
  • #16 g_main_context_dispatch
    from /lib64/libglib-2.0.so.0
  • #17 g_main_context_check
    from /lib64/libglib-2.0.so.0
  • #18 g_main_loop_run
    from /lib64/libglib-2.0.so.0
  • #19 gtk_main
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #20 POA_Nautilus_MetafileMonitor__init
  • #21 __libc_start_main
    from /lib64/libc.so.6
  • #22 g_cclosure_marshal_VOID__ENUM
  • #23 ??
  • #24 ??
  • #0 waitpid
    from /lib64/libpthread.so.0 






Comment 1


André Klapper





          2006-12-12 21:04:42 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 364674 ***