GNOME Bugzilla – Bug 443083
[2.18] crash in Text Editor: closing the app
Last modified: 2008-02-29 13:17:30 UTC
Version: 2.18.0 What were you doing when the application crashed? closing the app 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: Enforcing Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 65622016 vsize: 65622016 resident: 20185088 share: 13647872 rss: 20185088 rss_rlim: 4294967295 CPU usage: start_time: 1180742326 rtime: 76 utime: 71 stime: 5 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 -1209063712 (LWP 22330)] (no debugging symbols found) 0x00738402 in __kernel_vsyscall ()
+ Trace 137393
Thread 1 (Thread -1209063712 (LWP 22330))
No plugin installed in $HOME. ----------- .xsession-errors (30 sec old) --------------------- _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 You can not run beagle as root. Beagle is designed to run from your own user account. If you want to create multiuser or system-wide indexes, use the beagle-build-index tool. You can override this setting using the beagle-config or beagle-settings tools. /usr/share/themes/Clearlooks/gtk-2.0/gtkrc:34: error: lexical error or unexpected token, expected valid token Data Dir: /usr/share/gnome-applets/invest-applet ** (gedit:22330): WARNING **: IPP request failed with status 1030 ** (gedit:22330): WARNING **: IPP request failed with status 1030 --------------------------------------------------
Thanks for taking the time to report this bug. Unfortunately, that 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. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so. Thanks in advance!
Thanks for taking the time to report this bug. Unfortunately, that 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. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so and reopen this bug or report a new one. Thanks in advance! (Changing bad_stacktrace bugs from NEEDINFO -> INCOMPLETE as discussed in gnome-bugsquad. Search for "needinfo-to-incomplete-spam" to clean your inbox.)
*** Bug 449223 has been marked as a duplicate of this bug. ***
*** Bug 449064 has been marked as a duplicate of this bug. ***
*** Bug 449032 has been marked as a duplicate of this bug. ***
*** Bug 446830 has been marked as a duplicate of this bug. ***
*** Bug 449270 has been marked as a duplicate of this bug. ***
*** Bug 451824 has been marked as a duplicate of this bug. ***
*** Bug 451881 has been marked as a duplicate of this bug. ***
*** Bug 453563 has been marked as a duplicate of this bug. ***
*** Bug 455746 has been marked as a duplicate of this bug. ***
*** Bug 458699 has been marked as a duplicate of this bug. ***
*** Bug 456528 has been marked as a duplicate of this bug. ***
*** Bug 457974 has been marked as a duplicate of this bug. ***
*** Bug 459379 has been marked as a duplicate of this bug. ***
*** Bug 460919 has been marked as a duplicate of this bug. ***
*** Bug 463099 has been marked as a duplicate of this bug. ***
*** Bug 463530 has been marked as a duplicate of this bug. ***
*** Bug 465629 has been marked as a duplicate of this bug. ***
*** Bug 469533 has been marked as a duplicate of this bug. ***
*** Bug 469981 has been marked as a duplicate of this bug. ***
*** Bug 466350 has been marked as a duplicate of this bug. ***
*** Bug 470004 has been marked as a duplicate of this bug. ***
*** Bug 470013 has been marked as a duplicate of this bug. ***
*** Bug 466908 has been marked as a duplicate of this bug. ***
*** Bug 473414 has been marked as a duplicate of this bug. ***
*** Bug 473996 has been marked as a duplicate of this bug. ***
*** Bug 474580 has been marked as a duplicate of this bug. ***
*** Bug 475347 has been marked as a duplicate of this bug. ***
*** Bug 476838 has been marked as a duplicate of this bug. ***
*** Bug 477772 has been marked as a duplicate of this bug. ***
*** Bug 482047 has been marked as a duplicate of this bug. ***
*** Bug 489136 has been marked as a duplicate of this bug. ***
Reporters, 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 debug packages for gedit, gtk, glib, gnome-vfs, libgnome, libgnomeui, pango and gtksourceview (as far as those packages are provided by your distribution). More details can be found here: http://live.gnome.org/GettingTraces
*** Bug 481171 has been marked as a duplicate of this bug. ***
*** Bug 487693 has been marked as a duplicate of this bug. ***
*** Bug 490126 has been marked as a duplicate of this bug. ***
*** Bug 488027 has been marked as a duplicate of this bug. ***
*** Bug 489648 has been marked as a duplicate of this bug. ***
*** Bug 489622 has been marked as a duplicate of this bug. ***
*** Bug 477754 has been marked as a duplicate of this bug. ***
*** Bug 487029 has been marked as a duplicate of this bug. ***
*** Bug 495285 has been marked as a duplicate of this bug. ***
*** Bug 495354 has been marked as a duplicate of this bug. ***
*** Bug 495955 has been marked as a duplicate of this bug. ***
Bug #495955 had in the .xsession-errors : (gedit:6881): GLib-GObject-CRITICAL **: g_object_set: assertion `G_IS_OBJECT (object)' failed (gedit:6881): GLib-GObject-CRITICAL **: g_object_set: assertion `G_IS_OBJECT (object)' failed (gedit:6881): GnomePrint-CRITICAL **: gnome_print_filter_reset: assertion `GNOME_IS_PRINT_FILTER (f)' failed (gedit:6881): GnomePrint-CRITICAL **: gnome_print_filter_flush: assertion `GNOME_IS_PRINT_FILTER (f)' failed ** (gedit:6881): WARNING **: could not set the value of Settings.Document.Filter, node not found
*** Bug 494024 has been marked as a duplicate of this bug. ***
And bug #494024 had : ** (gedit:5055): WARNING **: could not set the value of Settings.Document.Filter, node not found (gedit:5055): libgnomeprintui-CRITICAL **: gnome_paper_selector_load_paper_size: assertion `GNOME_IS_PAPER_SELECTOR (ps)' failed
*** Bug 492706 has been marked as a duplicate of this bug. ***
*** Bug 498241 has been marked as a duplicate of this bug. ***
*** Bug 497534 has been marked as a duplicate of this bug. ***
*** Bug 499867 has been marked as a duplicate of this bug. ***
*** Bug 503553 has been marked as a duplicate of this bug. ***
*** Bug 503412 has been marked as a duplicate of this bug. ***
*** Bug 492337 has been marked as a duplicate of this bug. ***
*** Bug 492611 has been marked as a duplicate of this bug. ***
*** Bug 493228 has been marked as a duplicate of this bug. ***
*** Bug 500139 has been marked as a duplicate of this bug. ***
*** Bug 500958 has been marked as a duplicate of this bug. ***
*** Bug 504703 has been marked as a duplicate of this bug. ***
*** Bug 504959 has been marked as a duplicate of this bug. ***
*** Bug 505260 has been marked as a duplicate of this bug. ***
*** Bug 456841 has been marked as a duplicate of this bug. ***
Dear reporters, 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 debug packages for gedit, gtk, glib, gnome-vfs, libgnome, libgnomeui and libgnomeprint (as far as those packages are provided by your distribution). More details can be found here: http://live.gnome.org/GettingTraces
all reports are either from Fedora, Mandriva and Debian. the Gedit version is always <=2.18.2, there has not been a single 2.20 report so far. most likely this issue has been fixed in the meantime.
*** Bug 508696 has been marked as a duplicate of this bug. ***
Hello, The bug is closed because it is related to the component libgnomeprint, and the developers decide to not support this component anymore. Regards
*** Bug 519506 has been marked as a duplicate of this bug. ***