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 559609 - crash in CD/DVD Creator:
crash in CD/DVD Creator:
Status: RESOLVED DUPLICATE of bug 480179
Product: nautilus
Classification: Core
Component: general
unspecified
Other All
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2008-11-06 15:20 UTC by pavel
Modified: 2008-11-06 15:23 UTC
See Also:
GNOME target: ---
GNOME version: 2.23/2.24



Description pavel 2008-11-06 15:20:09 UTC
What were you doing when the application crashed?



Distribution: Unknown
Gnome Release: 2.24.1 2008-10-25 (Archlinux)
BugBuddy Version: 2.24.1

System: Linux 2.6.27-ARCH #1 SMP PREEMPT Sun Oct 26 10:36:46 UTC 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10402000
Selinux: No
Accessibility: Disabled
GTK+ Theme: ClearlooksClassic
Icon Theme: Kamel

Memory status: size: 77574144 vsize: 77574144 resident: 27275264 share: 15265792 rss: 27275264 rss_rlim: 18446744073709551615
CPU usage: start_time: 1225985235 rtime: 230 utime: 203 stime: 27 cutime:1 cstime: 1 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/bin/nautilus'

[Thread debugging using libthread_db enabled]
[New Thread 0xb6a9f930 (LWP 28890)]
[New Thread 0xb480eb90 (LWP 28916)]
[New Thread 0xb560ab90 (LWP 28904)]
0xb7ff7424 in __kernel_vsyscall ()

Thread 1 (Thread 0xb6a9f930 (LWP 28890))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/libpthread.so.0
  • #2 g_spawn_sync
    from /usr/lib/libglib-2.0.so.0
  • #3 g_spawn_command_line_sync
    from /usr/lib/libglib-2.0.so.0
  • #4 run_bug_buddy
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #5 check_if_gdb
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #6 bugbuddy_segv_handle
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #7 <signal handler called>
  • #8 gconf_client_remove_dir
    from /usr/lib/libgconf-2.so.4
  • #9 nautilus_actions_config_gconf_reader_finalize
    from /usr/lib/nautilus/extensions-2.0/libnautilus-actions.so
  • #10 g_object_unref
    from /usr/lib/libgobject-2.0.so.0
  • #11 nautilus_actions_instance_dispose
    from /usr/lib/nautilus/extensions-2.0/libnautilus-actions.so
  • #12 g_object_unref
    from /usr/lib/libgobject-2.0.so.0
  • #13 free_module_objects
  • #14 eel_debug_shut_down
    from /usr/lib/libeel-2.so.2
  • #15 main
  • #0 __kernel_vsyscall


----------- .xsession-errors (31892 sec old) ---------------------
kded(8461)/kio (KDirWatch) KDirWatchPrivate::useINotify: inotify successfully used for monitoring
kded(8461)/kio (KDirWatch) KDirWatchPrivate::addEntry: Added File "/usr/share/mime/application/x-planperfect.xml" for "" ["KDirWatch-1"]
kded(8461)/kio (KDirWatch) KDirWatchPrivate::useINotify: trying to use inotify for monitoring
kded(8461)/kio (KDirWatch) KDirWatchPrivate::useINotify: inotify successfully used for monitoring
kded(8461)/kio (KDirWatch) KDirWatchPrivate::addEntry: Added File "/usr/share/mime/application/x-plasma.xml" for "" ["KDirWatch-1"]
kded(8461)/kio (KDirWatch) KDirWatchPrivate::useINotify: trying to use inotify for monitoring
kded(8461)/kio (KDirWatch) KDirWatchPrivate::useINotify: inotify successfully used for monitoring
kded(8461)/kio (KDirWatch) KDirWatchPrivate::addEntry: Added File "/usr/share/mime/application/x-profile.xml" for "" ["KDirWatch-1"]
kded(8461)/kio (KDirWatch) KDirWatchPrivate::useINotify: trying to use inotify for monitoring
kded(8461)/kio (KDirWatch) KDirWatchPrivate::useINotify: inotify successfully used for monitoring
kded(8461)/kio (KDirWatch) KDirWatchPrivate::addEntry: Added File "/usr/share/mime/application/x-pw.xml" for "" ["KDirWatch-1"]
kded(8461)/kio (KDirWatch) KDirWatchPrivate::useINotify: trying to use inotify for monitoring
kded(8461)/kio (KDirWatch) KDirWatchPrivate::useINotify: inotify successfully used for monitoring
...Too much output, ignoring rest...
--------------------------------------------------
Comment 1 A. Walton 2008-11-06 15:23:41 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 480179 ***