GNOME Bugzilla – Bug 539921
crash in CD/DVD Creator:
Last modified: 2008-06-24 11:11:48 UTC
What were you doing when the application crashed? Distribution: Debian lenny/sid Gnome Release: 2.22.2 2008-05-29 (Debian) BugBuddy Version: 2.22.0 System: Linux 2.6.25.6-2008.06.10 #5 PREEMPT Tue Jun 10 13:47:01 EEST 2008 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10400090 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: gnome Memory status: size: 402288640 vsize: 402288640 resident: 36757504 share: 18993152 rss: 36757504 rss_rlim: 18446744073709551615 CPU usage: start_time: 1214287071 rtime: 667 utime: 604 stime: 63 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/nautilus' (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 0x7fe5f723c7a0 (LWP 3046)] (no debugging symbols found) 0x00007fe5f23695ef in waitpid () from /lib/libpthread.so.0
+ Trace 201248
Thread 1 (Thread 0x7fe5f723c7a0 (LWP 3046))
----------- .xsession-errors --------------------- /bin/sh: paplay: command not found connection_message_func(): Callback CALLBACK: full-authentication!!! connection_message_func(): Callback CALLBACK: full-authentication!!! connection_message_func(): Callback CALLBACK: full-authentication!!! ** (nautilus:3046): WARNING **: Не знайдено опису для типу MIME "x-directory/smb-share" (файл "C%24"), повідомте про це на поштовий список gnome warning: .dynamic section for "/usr/lib/libkrb5.so.3" is not at the expected address (wrong library or version mismatch?) warning: .dynamic section for "/usr/lib/libk5crypto.so.3" is not at the expected address (wrong library or version mismatch?) warning: .dynamic section for "/usr/lib/libgssapi_krb5.so.2" is not at the expected address (wrong library or version mismatch?) --------------------------------------------------
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 522534 ***