GNOME Bugzilla – Bug 479672
crash in Open Folder: Upgrading from FC5 to Fe...
Last modified: 2007-10-06 10:19:54 UTC
Version: 2.18.1 What were you doing when the application crashed? Upgrading from FC5 to Fedora 7. This is something I have caused and not a bug. Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.0 2007-03-23 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.21-1.3194.fc7 #1 SMP Wed May 23 22:35:01 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Permissive Accessibility: Disabled GTK+ Theme: Simple Icon Theme: gnome Memory status: size: 76939264 vsize: 76939264 resident: 14520320 share: 10911744 rss: 14520320 rss_rlim: 4294967295 CPU usage: start_time: 1190499542 rtime: 39 utime: 32 stime: 7 cutime:0 cstime: 0 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 -1208842528 (LWP 2741)] (no debugging symbols found) 0x008da402 in __kernel_vsyscall ()
+ Trace 164964
Thread 1 (Thread -1208842528 (LWP 2741))
----------- .xsession-errors (7 sec old) --------------------- p.run() File "/usr/bin/puplet", line 355, in run self._getOnDbus() File "/usr/bin/puplet", line 229, in _getOnDbus "/Updatesd") File "/usr/lib/python2.5/site-packages/dbus/_dbus.py", line 410, in get_object follow_name_owner_changes=follow_name_owner_changes) File "/usr/lib/python2.5/site-packages/dbus/proxies.py", line 230, in __init__ _dbus_bindings.UInt32(0)) File "/usr/lib/python2.5/site-packages/dbus/proxies.py", line 169, in __call__ reply_message = self._connection.send_message_with_reply_and_block(message, timeout) dbus.DBusException: org.freedesktop.DBus.Error.ServiceUnknown: The name edu.duke.linux.yum was not provided by any .service files Identity added: /home/davdunc/.ssh/id_rsa (/home/davdunc/.ssh/id_rsa) (nautilus:2741): GLib-CRITICAL **: g_markup_parse_context_end_parse: assertion `context->state != STATE_ERROR' failed --------------------------------------------------
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 439593 ***