GNOME Bugzilla – Bug 436631
crash in Home Folder: Nenhuma a??o
Last modified: 2007-05-11 15:22:48 UTC
What were you doing when the application crashed? Nenhuma ação Distribution: Unknown Gnome Release: 2.18.1 2007-04-14 (KateOS) BugBuddy Version: 2.18.1 System: Linux 2.6.19.3-kateos #5 PREEMPT Sun Apr 15 21:21:55 CEST 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 70100000 Selinux: No Accessibility: Disabled GTK+ Theme: OSX-theme Icon Theme: Gion Memory status: size: 85090304 vsize: 85090304 resident: 30425088 share: 14585856 rss: 30425088 rss_rlim: 4294967295 CPU usage: start_time: 1178474490 rtime: 12959 utime: 12283 stime: 676 cutime:362 cstime: 23 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/nautilus' (no debugging symbols found) Using host libthread_db library "/lib/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1227487552 (LWP 10533)] 0xb7107dc1 in __waitpid_nocancel () from /lib/libpthread.so.0
+ Trace 132915
Thread 1 (Thread -1227487552 (LWP 10533))
----------- .xsession-errors (39387 sec old) --------------------- ** (gnome-desktop-item-edit:5173): WARNING **: invalid source position for horizontal gradient ** (gnome-about:5448): WARNING **: Invalid borders specified for theme pixmap: /home/bonnies/.themes/OSX-theme/gtk-2.0/Buttons/button-default.png, borders don't fit within the image amarok: BEGIN: App::App() kbuildsycoca running... Reusing existing ksycoca kio (KService*): WARNING: Invalid Service : krenameservicemenu.desktop kio (KService*): WARNING: Invalid Service : krename_dir.desktop kio (KService*): WARNING: The desktop entry file /usr/share/applications/DefaultPlugins.desktop has Type=Link instead of "Application" or "Service" kio (KService*): WARNING: Invalid Service : /usr/share/applications/DefaultPlugins.desktop ...Too much output, ignoring rest... --------------------------------------------------
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 424980 ***