sigabrt when font face set to Inconsolata

Was bitten by this too - or something very similar at least.

If I start emacs-snapshot -Q, then M-x customize-face, default, set font-family to unknown-inconsolata, it would work as long as I don't complete anything.
But completing anything would trigger it: e.g., C-x C-f, hit TAB after the "~/".
Leads to a different signal though - segmentation fault (11).

Note that xfontsel thinks that inconsolata has "spc" equal to "p" for proportional. That seems strange. The full XLFDs are:
-unknown-inconsolata-medium-r-normal--17-120-100-100-p-0-iso8859-1
-unknown-inconsolata-medium-r-normal--17-120-100-100-p-0-iso8859-15
-unknown-inconsolata-medium-r-normal--17-120-100-100-p-0-iso10646-1

I can confirm that I am having the same issue as Erik Postma.

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please try to obtain a backtrace following the instructions at [WWW] http://wiki.ubuntu.com/DebuggingProgramCrash and upload the backtrace (as an attachment) to the bug report. This will greatly help us in tracking down your problem.

Hmmmmmm... it looks like for me it was simply a matter of having a bad package installed...

At one point I installed emacs-snapshot version 1:20080228-2~gutsy from Alex Vassalotti. I realized at some point that emacs-snapshot in the regular archives were now also built with xft support, and removed avassalotti's repository from my sources.list. But apparently I never "downgraded" to a version in the main repositories.

By installing emacs-snapshot-dbgsym, I was forced to realize this and downgrade to 1:20080228-1ubuntu1, which does not have this problem.

Kevin, can you confirm this as well?

backtrace attached. I'm not sure I understand the -dbgsym packages, it installed something in /usr/lib/debug/usr/bin that says "cannot execute binary file" if I try to run it or ldd it, though "file" identifies it as an ELF executable.

So here's gdb output from running the thing in /usr/bin (does it magically know to find symbols in /usr/lib/debug/usr/bin?)

the other thing to note is that there is no dbgsym version of the current version 22.1-0ubuntu10.1, so this is 22.1-0ubuntu10.

backtrace of emacs-snapshot attached. (should this be filed under a different bug than the emacs22?)

Ok, on *another* machine, I *do* still have the same problem. Seems to be the same thing that Kevin has. I saw that it references xterm.c so I (foolishly) thought it might have something to do with the TERM environment variable and also got a backtrace with

env -i DISPLAY=$DISPLAY XAUTHORITY=$XAUTHORITY gdb /usr/bin/emacs-snapshot-gtk 2>&1 | tee ....

which does not seem to make much of a difference as I should have figured out immediately. Attaching both anyway.

Same here, but different action leads to it:
open emacs22-gtk, run: m-x customize-face, default, and change height to 10
then click "set":
b7710b96 in kill () from /lib/tls/i686/cmov/libc.so.6
#2 0x080fd54b in abort () at emacs.c:432
#3 0x080c73a5 in recompute_basic_faces (f=0x2198) at xfaces.c:959
#4 0x0807f640 in init_iterator (it=0xbf8c38d4, w=0x9594fd8, charpos=-1,
    bytepos=-1, row=0x0, base_face_id=DEFAULT_FACE_ID) at xdisp.c:2533
#5 0x08082957 in x_consider_frame_title (frame=<value optimized out>)
    at xdisp.c:9079
#6 0x08082ae0 in prepare_menu_bars () at xdisp.c:9138
#7 0x08085e30 in redisplay_internal (preserve_echo_area=<value optimized out>)
    at xdisp.c:11043
#8 0x0810efc1 in command_loop_1 () at keyboard.c:1531
#9 0x08169860 in internal_condition_case (bfun=0x810e270 <command_loop_1>,
    handlers=137608889, hfun=0x8107920 <cmd_error>) at eval.c:1484
#10 0x08106d75 in command_loop_2 () at keyboard.c:1330
#11 0x0816993a in internal_catch (tag=137605073,
    func=0x8106d50 <command_loop_2>, arg=137563417) at eval.c:1224
#12 0x08107779 in command_loop () at keyboard.c:1309
#13 0x08107b3a in recursive_edit_1 () at keyboard.c:1007
#14 0x08107c36 in Frecursive_edit () at keyboard.c:1068
#15 0x080fe37f in main (argc=1, argv=0xbf8c4bb4) at emacs.c:1770

The beginning was cut off
Program received signal SIGABRT, Aborted.
[Switching to Thread 0xb7384700 (LWP 8600)]
0xb80c5430 in __kernel_vsyscall ()
(gdb) bt
#0 0xb80c5430 in __kernel_vsyscall ()
...