GNOME Bugzilla – Bug 414935
crash in Open Folder: Opening folder from Desk...
Last modified: 2007-03-05 20:18:06 UTC
What were you doing when the application crashed? Opening folder from Desktop Distribution: CentOS release 4.4 (Final) Gnome Release: 2.16.2 2006-11-30 (Linux Para Todos, Inc) BugBuddy Version: 2.16.1 System: Linux 2.6.9-42.0.10.EL #1 Tue Feb 27 09:24:42 EST 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 60802000 Selinux: Enforcing Accessibility: Disabled Memory status: size: 92110848 vsize: 0 resident: 92110848 share: 0 rss: 24154112 rss_rlim: 0 CPU usage: start_time: 1173101355 rtime: 0 utime: 422 stime: 0 cutime:379 cstime: 0 timeout: 43 it_real_value: 0 frequency: 0 Backtrace was generated from '/usr/bin/nautilus' (no debugging symbols found) Using host libthread_db library "/lib/tls/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread -1208805088 (LWP 5116)] [New Thread -1211372624 (LWP 5124)] 0x002387a2 in _dl_sysinfo_int80 () from /lib/ld-linux.so.2
+ Trace 116029
Thread 1 (Thread -1208805088 (LWP 5116))
----------- .xsession-errors --------------------- QObject::connect: No such slot GDBDebugger::GDBBreakpointWidget::slotAddBlankBreakpoint() QObject::connect: (sender name: 'gdbBreakpointWidget') QObject::connect: (receiver name: 'gdbBreakpointWidget') QObject::connect: No such slot ProblemReporter::configWidget(KDialogBase*) QObject::connect: (sender name: 'unnamed') QObject::connect: (receiver name: 'problemReporterWidget') ASSERT: "part && parent" in partwidget.cpp (41) ** (nautilus:5116): CRITICAL **: nautilus_file_get_uri: assertion `NAUTILUS_IS_FILE (file)' failed ** (bug-buddy:20546): WARNING **: No se pudo cargar el icono para Abrir carpeta ICE default IO error handler doing an exit(), pid = 6609, errno = 0 ICE default IO error handler doing an exit(), pid = 6624, errno = 0 Variable "got_ownership" is not available. Variable "pid" is not available. --------------------------------------------------
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 343488 ***