GNOME Bugzilla – Bug 500260
crash in Text Editor: tretreter
Last modified: 2007-12-25 12:00:52 UTC
Version: 2.18.0 What were you doing when the application crashed? tretreter 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: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 1968238592 vsize: 1968238592 resident: 14237696 share: 10579968 rss: 14237696 rss_rlim: 4294967295 CPU usage: start_time: 1196355955 rtime: 26 utime: 23 stime: 3 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/gedit' (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 -1208428832 (LWP 3254)] (no debugging symbols found) 0x0076b402 in __kernel_vsyscall ()
+ Trace 179997
Thread 1 (Thread -1208428832 (LWP 3254))
No plugin installed in $HOME. ----------- .xsession-errors --------------------- 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 GLib-ERROR **: gmem.c:135: failed to allocate 1922494565 bytes aborting... --------------------------------------------------
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find. *** This bug has been marked as a duplicate of 352099 ***