Program segfaults whenever I try to type anything into the text box on the bottom after logging into a mush. Reproducible: Always Steps to Reproduce: 1. Open gnome-mud 2. Connect to a server 3. Start typing Actual Results: Segfault Expected Results: Keep running allowing text to be entered root@ranthog gnome-mud # emerge info Portage 2.0.49-r15 (default-x86-1.4, gcc-3.2.3, glibc-2.3.2-r1, 2.4.20-gentoo-r8) ================================================================= System uname: 2.4.20-gentoo-r8 i686 AMD Athlon(tm) XP 1600+ Gentoo Base System version 1.4.3.10 ACCEPT_KEYWORDS="x86" AUTOCLEAN="yes" CFLAGS="-O2 -mcpu=i686 -pipe" CHOST="i686-pc-linux-gnu" COMPILER="gcc3" CONFIG_PROTECT="/etc /var/qmail/control /usr/kde/2/share/config /usr/kde/3/share/config /usr/X11R6/lib/X11/xkb /usr/kde/3.1/share/config /usr/share/texmf/tex/generic/config/ /usr/share/texmf/tex/platex/config/ /usr/share/config" CONFIG_PROTECT_MASK="/etc/gconf /etc/env.d" CXXFLAGS="-O2 -mcpu=i686 -pipe" DISTDIR="/usr/portage/distfiles" FEATURES="sandbox ccache autoaddcvs" GENTOO_MIRRORS="http://gentoo.oregonstate.edu http://distro.ibiblio.org/pub/Linux/distributions/gentoo" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="" SYNC="rsync://rsync.namerica.gentoo.org/gentoo-portage" USE="apm crypt foomaticdb libg++ mad mikmod motif ncurses nls truetype xml2 zlib gdbm berkdb slang readline arts tetex tcltk X sdl gpm tcpd pam libwww perl python esd imlib gtk2 cdr offensive aavm -3dfx 3dnow avi cups dga doc dvd encode ggi gif gnome gtk java jpeg -kde kerbos mmx mozilla mpeg oggvorbis opengl oss -pcmcia pdflib png -qt quicktime samba sasl spell sse ssl svga tiff true type usb -voodoo3 wmf x xmms xv x86" Here are the back traces I got from Gnome on the program. Application "gnome-mud" (process 16179) has crashed due to a fathal error. (segmenation fault) Backtrace was generated from '/usr/games/bin/gnome-mud' (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...[New Thread 16384 (LWP 16179)] (no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... 0x4021d137 in waitpid () from /lib/libpthread.so.0 #0 0x4021d137 in waitpid () from /lib/libpthread.so.0 #1 0x40079d68 in libgnomeui_module_info_get () from /usr/lib/libgnomeui-2.so.0 Thread 1 (Thread 16384 (LWP 16179)): #0 0x4021d137 in waitpid () from /lib/libpthread.so.0 No symbol table info available. #1 0x40079d68 in libgnomeui_module_info_get () from /usr/lib/libgnomeui-2.so.0 No symbol table info available. #0 0x4021d137 in waitpid () from /lib/libpthread.so.0 Backtrace was generated from '/usr/games/bin/gnome-mud' (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...[New Thread 16384 (LWP 23438)] (no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... 0x4021d137 in waitpid () from /lib/libpthread.so.0 #0 0x4021d137 in waitpid () from /lib/libpthread.so.0 #1 0x40079d68 in libgnomeui_module_info_get () from /usr/lib/libgnomeui-2.so.0 #2 <signal handler called> #3 0x0805d22a in destroy () #4 0x0817cc30 in ?? () Thread 1 (Thread 16384 (LWP 23438)): #0 0x4021d137 in waitpid () from /lib/libpthread.so.0 No symbol table info available. #1 0x40079d68 in libgnomeui_module_info_get () from /usr/lib/libgnomeui-2.so.0 No symbol table info available. #2 <signal handler called> No symbol table info available. #3 0x0805d22a in destroy () No symbol table info available. #4 0x0817cc30 in ?? () No symbol table info available. #0 0x4021d137 in waitpid () from /lib/libpthread.so.0
*** Bug 33640 has been marked as a duplicate of this bug. ***
Does gnome-mud-0.10.2 work ok?
Aparantly 0.10.2-r1 doesn't work for me right now which is rather interesting, considering it did last time I installed Gentoo. (My hard drive decided to die a while back and I've just reinstalled on the new one.) However, I did run gnome-mud from the terminal and it spit out these errors when it started up: (gnome-mud:30412): GLib-CRITICAL **: file gstrfuncs.c: line 1774 (g_ascii_strncasecmp): assertion `s1 != NULL' failed (gnome-mud:30412): GLib-CRITICAL **: file gstrfuncs.c: line 1774 (g_ascii_strncasecmp): assertion `s1 != NULL' failed ** Message: Plugin error (/usr/share/gnome-mud): No such file or directory
Oh, and the 0.10.2 ebuild has always given me scroll keeper errors, and still does to this day.
I have nearly the same setup as you do and it works fine for me. Please post the host and port of the mush that you're trying so I can reproduce your environment exactly. Or, if things are working for you let me know so I can close this bug. Thanks.
Unfortunatly it isn't working right, and I've tried it without USE or CFLAGS. I'm trying to connet to metro.spork.com port:4201.
Hmmm. That specific mush works fine for me as well. My only idea is for you to do emerge -e gnome-mud and see if that clears things up for you.
You have some interesting things in your USE flags, btw. You should probably take out "x" "true" and "type", they look like typos.
Alright. If I wasn't running some processor intensive stuff on my computer righ now for school, I'd probably have done it. And yeah, I've been meaning to clean the USE flags out. They were my original flags from my first install of Gentoo, but I didn't have time to fix it originally. Thanks for pointing that out. I'll get back to you on it later.
I have the same problem. When starting gnome-mud I have following errors spam: (gnome-mud:3050): GLib-CRITICAL **: file gstrfuncs.c: line 1774 (g_ascii_strncasecmp): assertion `s1 != NULL' failed (gnome-mud:3050): GLib-CRITICAL **: file gstrfuncs.c: line 1774 (g_ascii_strncasecmp): assertion `s1 != NULL' failed Then it crashes when I try to type anything in, or just switch desktops.
What are your USE flags and CFLAGS?
in /etc/make.conf: USE="adns apache2 autofs cjk dga doc fbcon ffmpeg foreign-package freetype \ fs gtk2 ipv6 java javascript mmx regexp socks5 speedo sse type1 \ unicode usb v4l wolk-supermount -foomaticdb -slang -berkdb -ruby \ -postgres -imlib -cdr" CFLAGS="-O3 -march=pentium3 -fprefetch-loop-arrays -funroll-loops -pipe"
I am experiencing exactly the same problem. The system I am using is based on a new 1.4 installation.
What are your USE flags and CFLAGS? Also, do you get these errors if you run gnome-mud from the terminal? (gnome-mud:3050): GLib-CRITICAL **: file gstrfuncs.c: line 1774 (g_ascii_strncasecmp): assertion `s1 != NULL' failed (gnome-mud:3050): GLib-CRITICAL **: file gstrfuncs.c: line 1774 (g_ascii_strncasecmp): assertion `s1 != NULL' failed
Also I'm on a brand new gentoo 1.4 install. It is less than a month old. I wonder if that could be a factor. I'm going to see what happens if I use another version of GCC.
I only get one message, as shown below, rather than the two posted in your note. (gnome-mud:18296): GLib-CRITICAL **: file gstrfuncs.c: line 1774 (g_ascii_strncasecmp): assertion `s1 != NULL' failed This message is produced as soon as the package is launched, rather than when it crashes during connection to any mud. The reason I may not be getting the second message is because I have a /usr/share/gnome-mud directory (I suspect I manually created this at some point) although it is empty, perhaps the problem has something to do with missing files in this directory?
Need some more special help of the gnome variety over here please. Seems to be a gconf issue of some kind I believe.
This seems to fix it for me: rm -rf ~/.gconf/apps/gnome-mud killall gconfd-2 This removes the gconf settings for gnome-mud so if you want to keep those make a backup first.
you just reset the settings to the default... would be interesting to know what exactly caused it. It's only user upgrading gnome-mud that see this problem ? Suggests an invalid entry in the users gconf db, could someone with the problem check it out using gconf-editor ?
I had the problem, and still have the problem after following the steps mentioned in the above note. I have noticed a few other problems with the defaults for the preferences, there seem to be a number of errors as follows for a fresh install: No terminal type is set as default and as I try to type in a value such as xterm I get the following output to the screen for every character typed, even when the string matches something I would expect to be a valid terminal type. ** (gnome-mud:3067): CRITICAL **: file vtetc.c: line 530 (_vte_termcap_find): assertion `termcap != NULL' failed The default font is set to sans however the correct entry should be Sans (Or maybe one of the better looking fonts Like maybe Courier 10 Pitch at size 10), I believe this the following error message: ** (gnome-mud:3295): CRITICAL **: file vte.c: line 10169 (vte_terminal_set_font_from_string): assertion `name != NULL' failed The default separator is not set to anything at all. ANSI colours are all configured as black, this includes the default foreground and background colours. The default separator is not set to anything at all. I realise that most of these problems are probably nothing at all to do with the crashing problem and should be logged as separate bugs however it makes me wonder if there is something fundamentally wrong with the way new account defaults are set up, which might be responsible for causing the crash to occur. Just for information my original installation of gnome-mud was/is the latest version, so I do not think this has anything to do with people patching up older versions of the program.
Please give 0.10.4a a try.
Seems to have fixed the problem for me, I can now connect and type without a crash. Just one point, when trying to install the new package I originally got the following error message: configure: error: XML::Parser perl module is required for intltool !!! ERROR: games-mud/gnome-mud-0.10.4a failed. !!! Function econf, Line 339, Exitcode 1 !!! econf failed This was due to a missing dependency of: dev-perl/XML-Parser Perhaps the above package should be included as a dependency of the package. Regards, Robert Thorneycroft
Great, thanks for trying it out. I've added that dependency. I'll go ahead and close this bug since it seems to be working for now. ;-)
xml-parser isn't a dep, try running intltoolize --force, inside the src_compile/unpack stages.
Not sure if intltoolize works, but when I checked out the code, the error I received was due to the failure of the following command during the checks before compilation: perl -e "require XML::Parser" This turns out to be looking for the file Parser.pm which in turn was included in the dev-perl/XML-Parser package. That was the reason I suggested it as a dependency.
it should :) the problem is that upstream uses a new (and slightly broken) version of intltool when generating the tarball, which includes this dependency. by using intltoolize those parts of the build process are replaced with locally generated ones without said dep.
No, you're thinking of the error that looks like this: "The OrigTree module doesn't seem to be properly installed" The configure script for gnome-mud actually has this check in it: configure:if ! `perl -e "require XML::Parser" 2>/dev/null`; then configure: { { echo "$as_me:$LINENO: error: XML::Parser perl module is required for intltool" >&5 so the dependency stays.
okay, in that case it should stay. I thought it was another one of those "in compile" deps.
hmm yeah or fix the configure stuff (regenerate), this dep is added because of the 0.28 intltool macros most likely and isn't needed by our intltool (and most likely not by newer intltools than 0.28 either).
check gimp-2.0_pre1 or gnumeric-1.2.4 for a way to get around the XML-Parser dep introduced by intltool.
