Bug 739102 – Gedit-plugins embedded terminal makes Gedit crash on startup

After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.

Bug 739102 - Gedit-plugins embedded terminal makes Gedit crash on startup


Summary:	Gedit-plugins embedded terminal makes Gedit crash on startup


Status:	RESOLVED DUPLICATE of bug 732422

Product:	gedit-plugins
Classification:	Other
Component:	General
Version:	3.14.x
Hardware:	Other Linux

Importance:	Normal normal
Target Milestone:	---
Assigned To:	Gedit maintainers
QA Contact:	Gedit maintainers

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2014-10-24 03:12 UTC by ebkalderon
Modified:	2019-03-23 20:54 UTC

See Also:
GNOME target:	---
GNOME version:	---

Description ebkalderon 2014-10-24 03:12:02 UTC

I've had quite a few issues with several applications since upgrading from GNOME 3.12 to 3.14. I had built up a workflow while using Gedit as my programming editor of choice, and I had grown accustomed to using the embedded terminal frequently for debugging my programs.

Now, whenever I try to open Gedit while gedit-plugins is installed and the embedded terminal plugin is enabled, I am greeted with an immediate and inexplicable coredump. I am running Arch Linux x86-64 stable, fully updated, and have all the necessary dependencies installed (including vte, vte3, and vte290).

Here is the error message I receive when I launch Gedit from the terminal:

(gedit:21285): GLib-GIO-ERROR **: Settings schema 'org.gnome.Terminal.Legacy.Profile' does not contain a key named 'word-chars'
Trace/breakpoint trap (core dumped)

Comment 1 ebkalderon 2014-10-24 03:13:03 UTC

+ Trace 234253

#0 g_logv
from /usr/lib/libglib-2.0.so.0
#1 g_log
from /usr/lib/libglib-2.0.so.0
#2 ??
from /usr/lib/libgio-2.0.so.0
#3 ??
from /usr/lib/libgio-2.0.so.0
#4 g_settings_get_value
from /usr/lib/libgio-2.0.so.0
#5 g_settings_get_string
from /usr/lib/libgio-2.0.so.0
#6 ffi_call_unix64
from /usr/lib/libffi.so.6
#7 ffi_call
from /usr/lib/libffi.so.6
#8 ??
from /usr/lib/python3.4/site-packages/gi/_gi.cpython-34m.so
#9 ??
from /usr/lib/python3.4/site-packages/gi/_gi.cpython-34m.so
#10 ??
from /usr/lib/python3.4/site-packages/gi/_gi.cpython-34m.so
#11 PyObject_Call
at Objects/abstract.c line 2067
#12 do_call
at Python/ceval.c line 4463
#13 call_function
at Python/ceval.c line 4261
#14 PyEval_EvalFrameEx
at Python/ceval.c line 2836
#15 fast_function
at Python/ceval.c line 4331
#16 call_function
at Python/ceval.c line 4259
#17 PyEval_EvalFrameEx
at Python/ceval.c line 2836
#18 PyEval_EvalCodeEx
at Python/ceval.c line 3585
#19 function_call
at Objects/funcobject.c line 632
#20 PyObject_Call
at Objects/abstract.c line 2067
#21 method_call
at Objects/classobject.c line 347
#22 PyObject_Call
at Objects/abstract.c line 2067
#23 slot_tp_init
at Objects/typeobject.c line 6023
#24 type_call
at Objects/typeobject.c line 869
#25 PyObject_Call
at Objects/abstract.c line 2067
#26 do_call
at Python/ceval.c line 4463
#27 call_function
at Python/ceval.c line 4261
#28 PyEval_EvalFrameEx
at Python/ceval.c line 2836
#29 fast_function
at Python/ceval.c line 4331
#30 call_function
at Python/ceval.c line 4259
#31 PyEval_EvalFrameEx
at Python/ceval.c line 2836
#32 PyEval_EvalCodeEx
at Python/ceval.c line 3585
#33 function_call
at Objects/funcobject.c line 632
#33 function_call
at Objects/funcobject.c line 632
#34 PyObject_Call
at Objects/abstract.c line 2067
#35 method_call
at Objects/classobject.c line 347
#36 PyObject_Call
at Objects/abstract.c line 2067
#37 slot_tp_init
at Objects/typeobject.c line 6023
#38 type_call
at Objects/typeobject.c line 869
#39 PyObject_Call
at Objects/abstract.c line 2067
#40 do_call
at Python/ceval.c line 4463
#41 call_function
at Python/ceval.c line 4261
#42 PyEval_EvalFrameEx
at Python/ceval.c line 2836
#43 PyEval_EvalCodeEx
at Python/ceval.c line 3585
#44 function_call
at Objects/funcobject.c line 632
#45 PyObject_Call
at Objects/abstract.c line 2067
#46 PyEval_CallObjectWithKeywords
at Python/ceval.c line 4111
#47 ??
from /usr/lib/python3.4/site-packages/gi/_gi.cpython-34m.so
#48 ffi_closure_unix64_inner
from /usr/lib/libffi.so.6
#49 ffi_closure_unix64
from /usr/lib/libffi.so.6
#50 peas_extension_set_foreach
from /usr/lib/libpeas-1.0.so.0
#51 ??
from /usr/lib/gedit/libgedit.so
#52 g_type_create_instance
from /usr/lib/libgobject-2.0.so.0
#53 ??
from /usr/lib/libgobject-2.0.so.0
#54 g_object_new_valist
from /usr/lib/libgobject-2.0.so.0
#55 g_object_new
from /usr/lib/libgobject-2.0.so.0
#56 ??
from /usr/lib/gedit/libgedit.so
#57 gedit_app_create_window
from /usr/lib/gedit/libgedit.so
#58 ??
from /usr/lib/gedit/libgedit.so
#59 ??
from /usr/lib/gedit/libgedit.so
#60 ??
from /usr/lib/libgobject-2.0.so.0
#61 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#62 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#63 ??
from /usr/lib/gedit/libgedit.so
#64 ffi_call_unix64
from /usr/lib/libffi.so.6
#65 ffi_call
from /usr/lib/libffi.so.6
#66 g_cclosure_marshal_generic_va
from /usr/lib/libgobject-2.0.so.0
#67 ??
from /usr/lib/libgobject-2.0.so.0
#68 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#69 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#70 ??
from /usr/lib/libgio-2.0.so.0
#71 ??
from /usr/lib/libgio-2.0.so.0
#72 g_application_run
from /usr/lib/libgio-2.0.so.0
#73 main

Comment 2 Garrett Regier 2014-10-24 03:54:22 UTC

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.

Looks like you need to also update gedit-plugins to 3.14

*** This bug has been marked as a duplicate of bug 732422 ***