GNOME Bugzilla – Bug 472916
crash in Open Folder: i dont kow
Last modified: 2007-10-19 02:01:23 UTC
Version: 2.19.5 What were you doing when the application crashed? i dont kow Distribution: Fedora release 7.90 (Rawhide) Gnome Release: 2.19.5 2007-07-08 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.23-0.61.rc1.git9.fc8 #1 SMP Tue Jul 31 17:23:22 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Enforcing Accessibility: Enabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 89325568 vsize: 89325568 resident: 28487680 share: 14835712 rss: 28487680 rss_rlim: 4294967295 CPU usage: start_time: 1188774009 rtime: 1031 utime: 681 stime: 350 cutime:1 cstime: 3 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 -1208719600 (LWP 2694)] (no debugging symbols found) 0x0012d402 in __kernel_vsyscall ()
+ Trace 159895
Thread 1 (Thread -1208719600 (LWP 2694))
----------- .xsession-errors (689 sec old) --------------------- self.doRefresh() File "/usr/sbin/pirut", line 387, in doRefresh self.doRefreshRepos(self._onlyrepo) File "/usr/lib/python2.5/site-packages/pirut/__init__.py", line 268, in doRefreshRepos self.reposSetup(pbar, thisrepo) File "/usr/lib/python2.5/site-packages/pirut/__init__.py", line 247, in reposSetup self.doGroupSetup() File "/usr/lib/python2.5/site-packages/yum/__init__.py", line 426, in doGroupSetup return self._getGroups() File "/usr/lib/python2.5/site-packages/yum/__init__.py", line 474, in _getGroups self._comps.add(groupfile) File "/usr/lib/python2.5/site-packages/yum/comps.py", line 349, in add for event, elem in parser: File "<string>", line 68, in __iter__ SyPackage cdparanoia - alpha9.8-27.2.i386 already installed and latest version --------------------------------------------------
Thanks for taking the time to report this bug. Unfortunately, the stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Could you please help fixing this by installing some debugging packages [1], start the application as normal, and try to reproduce the crash, if possible? Once bug-buddy pops up, you can find the stacktrace in the 'Details', now containing way more information. Please copy that stacktrace and paste it as a comment here. Thanks in advance! [1] Please install the following debug packages provided by Fedora: nautilus-debuginfo, glib2-debuginfo, gtk2-debuginfo, pango-debuginfo, gnome-vfs2-debuginfo, libgnome-debuginfo, and libgnomeui-debuginfo. More details can be found here: http://live.gnome.org/GettingTraces
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 485771 ***