Title says it all. Definitely used to work. pprkut in ##slackware reports that it works in version 20130409.

Running under gdb doesn't produce many useful results, but shows the segfault to come from deep in libgobject.

Running emacs in console (-no-x11) works fine.

What are the next steps?

emacs-24.3-x86_64-2

Re-tested on latest -current and it still works fine here. Do you have a special invocation you use? I'm no emacs user so I really have no clue about it...

Works here, too. Are all of your other libraries up to date?

Strange. Yes everything should be up to date. slackpkg has no interesting news and no missing packages with `install-new`, using alien's mirror. I have some blacklisted things, but I haven't touched that list in a long time and none of them are normal libraries. Just xfce/kde, the kernel, gcc and glibc because of multilib setup. Nothing related to gtk or gobject and definitely nothing changed since the last time I tried to use emacs a month ago.

I'd say multilib then. glibc in -current changed and Eric just updated those yesterday. Can you check that?

Checked that I was up to date with multilib as well.

Backtrace from emacs.

http://vpaste.net/P4lEL

I tested on a new vanilla user and it *does* work. So something crazy has happened to my setup. I have no idea what these css errors are. Something with gtk theming I guess. Investigating...

Hello,

I found this post about the same issue (but not with emacs). It seems this is related to the theme (unico) you are using which is probably not compatible with gtk+3 3.6

Hope this helps.

Greetings

--
SeB

Emacs 24.3 is the first emacs that will use gtk+ 3 by default, unless specified. The Slackbuild in current does not specify to force to gtk+ 2, but you could probably change the slackbuild from
--with-x-toolkit=gtk

which is non-specific and will default to gtk+ 3 if available, to

--with-x-toolkit=gtk2

Gtk+3 has numerous massive themeing changes in each release, making it very hard for themes to work without problems, as theme makers can't keep up. It would probably be better to just compile with gtk+2

1 members found this post helpful.

Thanks everyone. Trying to rebuild it now with gtk2. Can anyone else build emacs on 64-current? It appears there's a library issue. New errors linking against imagemagick. Undefined references everywhere.

http://vpaste.net/D7P06

Using

cmyster in ##slackware confirms that image.c fails miserably with the same errors.

I just tried using HEAD from git, but still not updated for imagemagick.

Hi,
if you run in current:
echo `pkg-config --cflags --libs MagickWand`
you get:
-DMAGICKCORE_HDRI_ENABLE=0 -DMAGICKCORE_QUANTUM_DEPTH=16 -I/usr/include/ImageMagick-6 -lMagickWand-6.Q16 -lMagickCore-6.Q16
if you do the same in the downgraded version from 14.0 you see the same 2 libs "-l" (minus 6.Q16)
Now, in the configure part, if using the downgraded version of imagemagic you see:
checking for Wand .... -I/usr/include/ImageMagick-6 ' LIBS='-lMagickWand -lMagickCore '
but in the configure part with current imagemagic you see:
checking for Wand .... -I/usr/include/ImageMagick-6 ' LIBS='-lMagickCore-6.Q16 '

missing one LIB?

2 members found this post helpful.

Aha! Thanks ponce. Testing it now.

Ok so making the change in that patch and passing --without-makeinfo to configure, I got it to build.

I guess this needs to be changed in the emacs slackbuild until upstream fixes it.