reassign 580446 uim-prime 
found 580446 1:1.5.7-1
thanks

Looks like the proximate cause of prime dying repeatedly is that after
something goes wrong once (I haven't spotted what that might be),
uim-prime re-spawns prime and passes it an empty line, which causes
prime to immediately exit, so uim-prime re-spawns prime and passes it
another empty line ... That doesn't seem like a bug in prime so much as
a bug in uim-prime, so I'm reassigning it there.

I'm seeing prime_send_command being called repeatedly from the Scheme
bits, passed "" every time. Each time, it discovers that the child prime
process has exited, so it starts a new one and hands it "\n".

(gdb) bt full 2
#0  uim_ipc_send_command (pid=0x7fbfd386cce0, read_fp=0x7fbfd386cce8, 
    write_fp=0x7fbfd386ccf0, command=0x7fbfd366c830 "prime", str=0xbafea0 "\n")
    at uim-ipc.c:250
        tmp = <value optimized out>
        buf = (garbage)
#1  0x00007fbfd366c42c in prime_send_command (str_=<value optimized out>)
    at prime.c:213
        str = 0xba41c0 ""
        result = <value optimized out>
        ret = <value optimized out>

I see that prime-send-command in scm/prime.scm sends empty strings if it
gets an empty string on the first try, so I assume that's what happened.

I'm getting too lost in the layers of Scheme source to work out how it
got there, but here's where UIM entered the Scheme interpreter:

#44 0x00007fbfd3f592b1 in uim_scm_callf (proc=<value optimized out>, 
    args_fmt=<value optimized out>) at uim-scm-sigscheme.c:995
#45 0x00007fbfd417fbd4 in uim_create_context (ptr=0x96a4f0, 
    enc=0x7fbfd43bc565 "UTF-8", lang=0x0, engine=0xaaab30 "-", 
    conv=0x7fbfd4389b80, commit_cb=0x7fbfd43b5e20 <im_uim_commit_string>)
    at uim.c:229
#46 0x00007fbfd43b575a in im_module_create (context_id=<value optimized out>)
    at gtk-im-uim.c:1484
#47 0x00007fbfe3e38fa6 in _gtk_im_module_create (context_id=0x908ee0 "uim")
    at /gtk+2.0-2.20.0/gtk/gtkimmodule.c:693

These stack traces are from uim 1:1.5.7-1.

When this bug triggers from gnome-panel, it hangs my X session startup,
so in those cases I have to keep logging in until it works. This time it
hung empathy instead, making it easier to examine with gdb. Since it's a
pretty inconvenient bug, if there's anything I can do to help with
troubleshooting, please let me know. Thanks!

Jamey

Attachment: signature.asc
Description: Digital signature

Reply via email to