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 433656 - crash in CD/DVD Creator:
crash in CD/DVD Creator:
Status: RESOLVED DUPLICATE of bug 361582
Product: nautilus
Classification: Core
Component: general
unspecified
Other All
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-04-26 17:52 UTC by alwin_bakker
Modified: 2007-04-27 10:41 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description alwin_bakker 2007-04-26 17:52:45 UTC 
What were you doing when the application crashed?



Distribution: Fedora Core release 6 (Zod)
Gnome Release: 2.16.3 2007-01-31 (Red Hat, Inc)
BugBuddy Version: 2.16.0

System: Linux 2.6.20-1.2944.fc6 #1 SMP Tue Apr 10 17:46:00 EDT 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 70101000
Selinux: Enforcing
Accessibility: Disabled

Memory status: size: 490000384 vsize: 490000384 resident: 40382464 share: 20451328 rss: 40382464 rss_rlim: -1
CPU usage: start_time: 1177599577 rtime: 1458 utime: 1305 stime: 153 cutime:0 cstime: 2 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 46912496342992 (LWP 3626)]
(no debugging symbols found)
0x0000003dbbe0d96f in waitpid () from /lib64/libpthread.so.0

+ Trace 130735

Thread 1 (Thread 46912496342992 (LWP 3626))

  • #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 strchr
    from /lib64/libc.so.6
  • #4 strrchr
    from /lib64/libc.so.6
  • #5 eel_filename_get_rename_region
    from /usr/lib64/libeel-2.so.2
  • #6 fm_directory_view_bump_zoom_level
  • #7 fm_directory_view_pop_up_location_context_menu
  • #8 g_source_get_current_time
    from /lib64/libglib-2.0.so.0
  • #9 g_main_context_dispatch
    from /lib64/libglib-2.0.so.0
  • #10 g_main_context_check
    from /lib64/libglib-2.0.so.0
  • #11 g_main_loop_run
    from /lib64/libglib-2.0.so.0
  • #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
  • #16 ??
  • #17 ??
  • #0 waitpid
    from /lib64/libpthread.so.0 


----------- .xsession-errors (6 sec old) ---------------------
** (nautilus:3626): WARNING **: Got load_underway report from unknown view
** (nautilus:3626): WARNING **: Got load_underway report from unknown view
Message: fmt 5, channels: 2
Window manager warning: Invalid WM_TRANSIENT_FOR window 0x4e00001 specified for 0x4e00008 (Select ins).
Window manager warning: Invalid WM_TRANSIENT_FOR window 0x4e00001 specified for 0x4e0000c (New folder).
Window manager warning: last_focus_time (788702624) is greater than comparison timestamp (788702605).  This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET
Window manager warning: Received a _NET_WM_MOVERESIZE message for 0x3a00005 (eMule v0.4); these messages lack timestamps and therefore suck.
Window manager warning: Invalid WM_TRANSIENT_FOR window 0x5200001 specified for 0x520000a (Reading fi).
Window manager warning: Invalid WM_TRANSIENT_FOR window 0x5200001 specified for 0x520000a (Reading pd).
Window manager warning: Invalid WM_TRANSIENT_FOR window 0x5200001 specified for 0x5200008 (Select ins).
(nautilus:3626): Gtk-CRITICAL **: gtk_entry_get_text: assertion `GTK_IS_ENTRY (entry)' failed
** (bug-buddy:10658): WARNING **: Couldn't load icon for Open Folder
--------------------------------------------------
Comment 1 palfrey 2007-04-27 10:41:38 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 bug has been marked as a duplicate of 361582 ***