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 388557 - crash in CD/DVD Creator: Running nautilus: 1. Sel...
crash in CD/DVD Creator: Running nautilus: 1. Sel...
Status: RESOLVED DUPLICATE of bug 374002
Product: nautilus
Classification: Core
Component: general
unspecified
Other All
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2006-12-22 09:40 UTC by fpm1703
Modified: 2006-12-25 23:33 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description fpm1703 2006-12-22 09:40:24 UTC 
What were you doing when the application crashed?
Running nautilus:
1. Selected View as List
2. Selected a file. Right clicked and `Rename' was grayed out.
3. Selected View as Icons; `Rename' still grayed out.
4. Terminated nautilus.
5. Invoked new nautilus session and selected directory I was in previously.
6. Bug Buddy window pops up!

System is an Intel E6300 (Core 2 Duo) w/ 2 GB ram (not overclocked).

Here's a copy of the stack trace dump:

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

System: Linux 2.6.18-1.2868.fc6 #1 SMP Fri Dec 15 17:29:48 EST 2006 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 70101000
Selinux: No
Accessibility: Disabled

Memory status: size: 494264320 vsize: 494264320 resident: 32976896 share: 20316160 rss: 32976896 rss_rlim: -1
CPU usage: start_time: 1166779443 rtime: 248 utime: 229 stime: 19 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 46912496428992 (LWP 13000)]
0x00000032b480d96f in waitpid () from /lib64/libpthread.so.0

+ Trace 96190

Thread 1 (Thread 46912496428992 (LWP 13000))

  • #0 waitpid
    from /lib64/libpthread.so.0
  • #1 libgnomeui_segv_handle
    at gnome-ui-init.c line 870
  • #2 <signal handler called>
  • #3 gtk_ui_manager_remove_ui
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #4 nautilus_marshal_BOOLEAN__POINTER
  • #5 fm_directory_view_bump_zoom_level
  • #6 fm_directory_view_update_menus
  • #7 fm_directory_view_bump_zoom_level
  • #8 g_timeout_dispatch
    at gmain.c line 3422
  • #9 IA__g_main_context_dispatch
    at gmain.c line 2045
  • #10 g_main_context_iterate
    at gmain.c line 2677
  • #11 IA__g_main_loop_run
    at gmain.c line 2881
  • #12 gtk_main
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #13 POA_Nautilus_MetafileMonitor__init
  • #14 __libc_start_main
    from /lib64/libc.so.6
  • #15 g_cclosure_marshal_VOID__ENUM
    at gmarshal.c line 334
  • #16 ??
  • #17 ??
  • #0 waitpid
    from /lib64/libpthread.so.0
  • #0 waitpid
    from /lib64/libpthread.so.0
  • #1 libgnomeui_segv_handle
    at gnome-ui-init.c line 870
  • #2 <signal handler called>
  • #3 gtk_ui_manager_remove_ui
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #4 nautilus_marshal_BOOLEAN__POINTER
  • #5 fm_directory_view_bump_zoom_level
  • #6 fm_directory_view_update_menus
  • #7 fm_directory_view_bump_zoom_level
  • #8 g_timeout_dispatch
    at gmain.c line 3422
  • #9 IA__g_main_context_dispatch
    at gmain.c line 2045
  • #10 g_main_context_iterate
    at gmain.c line 2677
  • #11 IA__g_main_loop_run
    at gmain.c line 2881
  • #12 gtk_main
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #13 POA_Nautilus_MetafileMonitor__init
  • #14 __libc_start_main
    from /lib64/libc.so.6
  • #15 g_cclosure_marshal_VOID__ENUM
    at gmarshal.c line 334
  • #16 ??
  • #17 ?? 






Comment 1


Christian Kirbach





          2006-12-25 23:33:46 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 374002 ***