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 480094 - crash in CD/DVD Creator: this is our server, and ...
crash in CD/DVD Creator: this is our server, and ...
Status: RESOLVED DUPLICATE of bug 363289
Product: nautilus
Classification: Core
Component: general
unspecified
Other All
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
: 480095 480096 480097 480098 480099 480100 480101 480102 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2007-09-25 06:46 UTC by kumar.vikas
Modified: 2007-10-01 02:44 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16



Description kumar.vikas 2007-09-25 06:46:52 UTC
What were you doing when the application crashed?
this is our server, and hangs out itself.


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: 476356608 vsize: 476356608 resident: 14061568 share: 10174464 rss: 14061568 rss_rlim: -1
CPU usage: start_time: 1190702459 rtime: 23 utime: 15 stime: 8 cutime:0 cstime: 0 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 46912496393680 (LWP 4029)]
(no debugging symbols found)
0x000000373b20d96f in waitpid () from /lib64/libpthread.so.0

Thread 1 (Thread 46912496393680 (LWP 4029))

  • #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 strcmp
    from /lib64/libc.so.6
  • #4 gtk_hsv_new
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #5 gtk_hsv_new
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #6 gtk_icon_info_get_type
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #7 gtk_icon_theme_get_icon_sizes
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #8 gtk_window_get_default_icon_list
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #9 gtk_window_get_default_icon_list
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #10 gtk_window_set_icon_name
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #11 POA_Nautilus_MetafileMonitor__init
  • #12 POA_Nautilus_MetafileMonitor__init
  • #13 POA_Nautilus_MetafileMonitor__init
  • #14 fm_directory_view_bump_zoom_level
  • #15 nautilus_clipboard_monitor_emit_changed
  • #16 nautilus_clipboard_monitor_emit_changed
  • #17 nautilus_directory_async_state_changed
  • #18 nautilus_icon_container_request_update_all
  • #19 g_main_context_dispatch
    from /lib64/libglib-2.0.so.0
  • #20 g_main_context_check
    from /lib64/libglib-2.0.so.0
  • #21 g_main_loop_run
    from /lib64/libglib-2.0.so.0
  • #22 gtk_main
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #23 POA_Nautilus_MetafileMonitor__init
  • #24 __libc_start_main
    from /lib64/libc.so.6
  • #25 g_cclosure_marshal_VOID__ENUM
  • #26 ??
  • #27 ??
  • #0 waitpid
    from /lib64/libpthread.so.0

Comment 1 André Klapper 2007-10-01 02:43:09 UTC
*** Bug 480095 has been marked as a duplicate of this bug. ***
Comment 2 André Klapper 2007-10-01 02:43:11 UTC
*** Bug 480096 has been marked as a duplicate of this bug. ***
Comment 3 André Klapper 2007-10-01 02:43:13 UTC
*** Bug 480097 has been marked as a duplicate of this bug. ***
Comment 4 André Klapper 2007-10-01 02:43:16 UTC
*** Bug 480098 has been marked as a duplicate of this bug. ***
Comment 5 André Klapper 2007-10-01 02:43:17 UTC
*** Bug 480099 has been marked as a duplicate of this bug. ***
Comment 6 André Klapper 2007-10-01 02:43:19 UTC
*** Bug 480100 has been marked as a duplicate of this bug. ***
Comment 7 André Klapper 2007-10-01 02:43:23 UTC
*** Bug 480101 has been marked as a duplicate of this bug. ***
Comment 8 André Klapper 2007-10-01 02:43:25 UTC
*** Bug 480102 has been marked as a duplicate of this bug. ***
Comment 9 André Klapper 2007-10-01 02:44:12 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 363289 ***

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