Gnome-mud crashes when I connect in a new session after saving the mud in a previous one. Reproducible: Always Steps to Reproduce: 1. create a mud network 2. connect, play, disconnect, quit 3. reconnect agian next time you start it Actual Results: crashes with (gnome-mud:10542): Gtk-WARNING **: GtkSpinButton: setting an adjustment with non-zero page size is deprecated Expected Results: Would connect
Created attachment 254837 [details] emerge --info
works fine for me on stable x86. What's the connection you're using that fails?
All three of them. connect.vikingmud.org 2001 intermud.org 23 (this one is ok cuz it's down right now) mud.simud.org 4242 However, a connection failure shoulnd't make the whole client crash. It works when I run it the first time, or I have a fresh config. Things get screwy if I start it again from saved data.
I tried those and it works fine for me. You're going to have to track it down on your end with gdb or something since I can't reproduce the failure you're experiencing.
This might not be the same bug but here's some info from a crash on first run after install (no previous config). I haven't seen any other crashes yet... $ gnome-mud (gnome-mud:7815): Gtk-CRITICAL **: gtk_entry_set_text: assertion `text != NULL' failed (gnome-mud:7815): Gtk-CRITICAL **: gtk_font_button_set_font_name: assertion `fontname != NULL' failed (gnome-mud:7815): Gtk-WARNING **: GtkSpinButton: setting an adjustment with non-zero page size is deprecated (gnome-mud:7815): GLib-CRITICAL **: g_convert: assertion `to_codeset != NULL' failed Segmentation fault (core dumped) Program terminated with signal 11, Segmentation fault. #0 __strlen_sse2 () at ../sysdeps/x86_64/multiarch/../strlen.S:31 31 ../sysdeps/x86_64/multiarch/../strlen.S: No such file or directory. in ../sysdeps/x86_64/multiarch/../strlen.S Thread 1 (Thread 7815): #0 __strlen_sse2 () at ../sysdeps/x86_64/multiarch/../strlen.S:31 No locals. #1 0x000000000040ff4a in mud_connection_view_feed_text (view=0x1326880, message=0x0) at mud-connection-view.c:268 rlen = <value optimized out> buf = <value optimized out> #2 0x0000000000410e0b in mud_connection_view_add_text (view=0x1326880, message=0x12cdfb0 "*** Making connection to connect.vikingmud.org, port 2001.\n", type=System) at mud-connection-view.c:350 encoding = 0x0 text = 0x0 local_codeset = 0xe7c010 "UTF-8" profile_name = <value optimized out> client = 0x1092b60 remote = <value optimized out> bytes_read = 0 bytes_written = 19859248 error = 0x0 key = "/apps/gnome-mud/functionality/encoding\000coding\000\000\000\034\000\000\000\000\000\000\000\060\346\313\022\377\177\000\000\333ʝ\201\345\177\000\000,\370\016\177\345\177\000\000\364ʝ\201\345\177", '\000' <repeats 18 times>"\364, ʝ\201\345\177\000\000\000]p\200\345\177\000\000\220\343\313\022\377\177\000\000p\204\006\001\000\000\000\000\320\343\313\022\377\177\000\000@>0\001\000\000\000\000\374\343\313\022\377\177\000\000\001", '\000' <repeats 23 times>, "ޘf\327", '\000' <repeats 12 times>, "\b\344\313\022\377\177\000\000\000]p\200\345\177\000\000\360\343\313\022\377\177\000\000(\344\313\022\377\177\000\000\200\337\313\022\377\177\000\000\001\000\000\000\326\367\377\377\266\323\021\177\345\177\000\000\220\345\313\022\377\177\000\000p\345\313\022\377\177\000\000\071\000\000\000\000\000\000\000\020\347\313\022\377\177\000\000%\340߁\345"... extra_path = '\000' <repeats 511 times> #3 0x00000000004120ef in mud_connection_view_new (profile=0x426b84 "Default", hostname=<value optimized out>, port=<value optimized out>, window=<value optimized out>, tray=<value optimized out>, name=0x12b6f90 "connect.vikingmud.org") at mud-connection-view.c:1041 profile_name = <value optimized out> client = <value optimized out> key = "\000\000\000\000\000\000\000\000\001\000\000\000\000\000\000\000\000]p\200\345\177\000\000#9r\200\345\177\000\000\030\000\000\000\060\000\000\000@\351\313\022\377\177\000\000\200\350\313\022\377\177\000\000ޘf\327\r\370\264\216P\260\060\001\000\000\000\000\200\317/\001\000\000\000\000\240\313:\001\000\000\000\000PQ\"\001\000\000\000\000\060\000\000\000\000\000\000\000(\000\000\000\000\000\000\000\210\317/\001\000\000\000\000ޘf\327\r\370\264\216\230\317/\001\000\000\000\000PQ\"\001\000\000\000\000p\372/\001\000\000\000\000p\372/\001", '\000' <repeats 12 times>, "ޘf\327\r\370\264\216\000]p\200\345\177\000\000\212\222p\200\345\177\000\000\000\000\000\000\000\000\000\000ޘf\327\r\370\264\216PQ\"\001\000\000\000\000ޘf\327\r\370\264\216\200\317/\001\000\000\000\000ޘf\327\r\370\264\216\360i:\001\000\000\000\000\266\323\021\177\345\177\000\000\060\360\313\022\377\177\000\000\020\360\313\022\377\177\000\000"... extra_path = '\000' <repeats 511 times> use_proxy = <value optimized out> proxy_host = <value optimized out> version = <value optimized out> view = 0x1326880 hints = {min_width = 6, min_height = 4, max_width = 0, max_height = 0, base_width = 2, base_height = 2, width_inc = 1, height_inc = 1, min_aspect = 9.8371197329357231e-317, max_aspect = 9.4002194585808921e-317, win_gravity = 19921520} xpad = 2 ypad = 2 char_width = <value optimized out> char_height = <value optimized out> buf = 0x12cdfb0 "*** Making connection to connect.vikingmud.org, port 2001.\n" __PRETTY_FUNCTION__ = "mud_connection_view_new" #4 0x0000000000412c17 in mud_connections_connect_cb (widget=<value optimized out>, conn=0x12e2d00) at mud-connections.c:366 selected = 0x132c6a0 iter = {stamp = 219204368, user_data = 0x12fcf20, user_data2 = 0x0, user_data3 = 0x0} buf = 0x13a5fb0 "gnome-mud" mud_name = 0x12b6f90 "connect.vikingmud.org" key = <value optimized out> strip_name = 0x13acb70 "connect.vikingmud.org" profile = 0x1391de0 "Default" host = 0x12c7290 "connect.vikingmud.org" logon = 0x0 char_name = <value optimized out> port = 2001 mud_tuple = <value optimized out> len = <value optimized out> client = 0x1092b60 view = <value optimized out>
Just took a look at upstream, it's completely dead. I move that this bug be RESOLVED CANTFIX and that the package in question be given last rites.
Hold up, I just gave the upstream git repo a test. git://git.gnome.org/gnome-mud This bug appears to be fixed...maybe we should do a revbump instead of last rites?
Upstream has been deafeningly quiet. Nothing much is happening. I'll be one of the first to recommend this gets put into sunrise afterwards if it recovers, but for now I'm withdrawing my vote of confidence in this package and renominating it for reaping.
The package looks to still work for me
