#177 Closed medit

[viliksar]

Hello! I have ubuntu 14.04, I installed medit.
The program itself is closed for no reason. Help fix this error, Please!
I took video, the program - https://www.youtube.com/watch?v=rEzN029Rw_4&feature=youtu.be

[Yevgen Muntyan]

How did you install it, using apt or built from sources? I tried ubuntu-14.04 and medit package which comes with it, that didn't crash. What's your medit version?

[viliksar]

medit 1.2.0
Installed from source

[Yevgen Muntyan]

Yep, I can repro it, with both medit-1.1.1 and 1.2.0. It looks like Ubuntu's Gtk tricks are somehow incompatible with medit.

[Yevgen Muntyan]

I opened a bug for Ubuntu: https://bugs.launchpad.net/ubuntu/+source/unity-gtk-module/+bug/1313184

[viliksar]

Thank you for your response!
Please let me know when the problem will be solved.

[viliksar]

My ubuntu 14 often received updates, but the problem is not solved unfortunately

[Yevgen Muntyan]

Ubuntu bug is still there, see the link above.

[EMah]

As a workaround you must disable the local menu
/usr/share/applications/medit.desktop
Exec=env UBUNTU_MENUPROXY= medit %F

[viliksar]

I entered this code in the file medit.desktop but Medit still does not start.

[Hibou57]

Should be tested again. The bug report on LaunchPad says unity-gtk-module was fixed on 2014-07-16 : https://bugs.launchpad.net/ubuntu/+source/unity-gtk-module/+bug/1313184/comments/5

[Makronas]

I suppose that unity-gtk-module fix was only for Ubuntu 14.10.
In my Ubuntu 14.04.02 32bit with all updates medit still crashes.

medit version is 1.1.1-2 i386

Here the result of running medit in gdb after clicking button 'Create new file' in toolbar:

Program received signal SIGSEGV, Segmentation fault.
0xb737b9ea in g_str_hash () from /lib/i386-linux-gnu/libglib-2.0.so.0
(gdb) bt
#0  0xb737b9ea in g_str_hash () from /lib/i386-linux-gnu/libglib-2.0.so.0
#1  0xb737a87a in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
#2  0xb6546e2c in ?? () from /usr/lib/i386-linux-gnu/libunity-gtk2-parser.so.0
#3  0xb653f885 in ?? () from /usr/lib/i386-linux-gnu/libunity-gtk2-parser.so.0
#4  0xb65419e0 in ?? () from /usr/lib/i386-linux-gnu/libunity-gtk2-parser.so.0
#5  0xb74613de in g_cclosure_marshal_VOID__PARAM () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
#6  0xb745ea7e in g_closure_invoke () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
#7  0xb7471029 in ?? () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
#8  0xb7478963 in g_signal_emit_valist () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
#9  0xb7478bf3 in g_signal_emit () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
#10 0xb7462aef in ?? () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
#11 0xb74654d0 in g_object_notify () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
#12 0xb7af6bec in gtk_widget_show () from /usr/lib/i386-linux-gnu/libgtk-x11-2.0.so.0
#13 0x080ff088 in ?? ()
#14 0xb7388c50 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
#15 0xb738c0a7 in g_main_context_dispatch () from /lib/i386-linux-gnu/libglib-2.0.so.0
#16 0xb738c468 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
#17 0xb738c76b in g_main_loop_run () from /lib/i386-linux-gnu/libglib-2.0.so.0
#18 0xb79c1450 in gtk_main () from /usr/lib/i386-linux-gnu/libgtk-x11-2.0.so.0
#19 0x08193592 in moo_app_run ()
#20 0x0808449c in main ()

[Marisano James]

I had the same problem with medit crashing just after opening under Ubuntu 14.04. Then I decided to try using sudo to launch medit (because it was complaining about some MooEditConfig attributes it had tried to adjust after the class had been initialized). It worked, both for version 1.2 and for the somewhat older 1.1.93-devel I also have installed. That means the error may not have to do with GTK, at least not in the expected manner.