Bug 19396 – Python-mode for emacs hangs X when viewing the IM-Python menu.

• Product: Gentoo Linux
• Status: RESOLVED WONTFIX

[Description Daniel Armyr 2003-04-15 20:53:06 UTC]

When editing python code, specifically emerge and portage.py, viewing the
declared functions using the IM-Python menu at times hangs parts of X. The error
is reproductible perhaps one time in ten. When this happens, X accepts no mouse
or keyboard input except the Ctrl-Alt-F1 sequence. 
I use python-mode 4.6 and emacs 21.3-r2, compiled without most optimisations.

[Comment 1 Seemant Kulleen (RETIRED) 2003-04-16 02:03:18 UTC]

which xfree are you running

[Comment 2 Daniel Armyr 2003-04-16 03:25:49 UTC]

*x11-base/xfree-4.2.1-r2 
Compiled with -O3 -mcpu=pentium3 -pipe. 

[Comment 3 Seemant Kulleen (RETIRED) 2003-04-16 03:42:48 UTC]

I don't suppose you're willing to try xfree-4.3.0-r2 are you?

[Comment 4 Matthew Kennedy (RETIRED) 2003-04-16 12:32:21 UTC]

hi. what graphical toolkit is your emacs compiled against? motif? (output of ldd /usr/bin/emacs). 

Matt

[Comment 5 Matthew Kennedy (RETIRED) 2003-04-16 12:48:50 UTC]

waiting on user input

[Comment 6 Daniel Armyr 2003-04-16 20:28:51 UTC]

I have compiled the sugested xfree-4.3.0 with 
CFLAGS="-O2 -mcpu=pentium3 -pipe -fomit-frame-pointer -funroll-loops -falign-fun
ctions=4"

I don't recognise any of these names as any toolkit I know of, so here is the complete list.
ldd /usr/bin/emacs:
        libXm.so.3 => /usr/X11R6/lib/libXm.so.3 (0x41358000)
        libXpm.so.4 => /usr/X11R6/lib/libXpm.so.4 (0x40001000)
        libXp.so.6 => /usr/X11R6/lib/libXp.so.6 (0x40010000)
        libXmu.so.6 => /usr/X11R6/lib/libXmu.so.6 (0x40018000)
        libXt.so.6 => /usr/X11R6/lib/libXt.so.6 (0x4002e000)
        libSM.so.6 => /usr/X11R6/lib/libSM.so.6 (0x40081000)
        libICE.so.6 => /usr/X11R6/lib/libICE.so.6 (0x4008a000)
        libXext.so.6 => /usr/X11R6/lib/libXext.so.6 (0x400a1000)
        libtiff.so.3 => /usr/lib/libtiff.so.3 (0x400ba000)
        libjpeg.so.62 => /usr/lib/libjpeg.so.62 (0x41d09000)
        libpng.so.3 => /usr/lib/libpng.so.3 (0x41cb3000)
        libz.so.1 => /usr/lib/libz.so.1 (0x40101000)
        libm.so.6 => /lib/libm.so.6 (0x4132a000)
        libungif.so.4 => /usr/lib/libungif.so.4 (0x40112000)
        libX11.so.6 => /usr/X11R6/lib/libX11.so.6 (0x4011a000)
        libncurses.so.5 => /lib/libncurses.so.5 (0x401f9000)
        libc.so.6 => /lib/libc.so.6 (0x41016000)
        libdl.so.2 => /lib/libdl.so.2 (0x41147000)
        /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x41000000)

I will test how emacs behaves under new xfree and get back when I feel I can make a statement on the continued status of this bug.

[Comment 7 Daniel Armyr 2003-04-17 03:06:04 UTC]

yes, got XFree-4.3 to work acceptably, loaded the emerge and emergehelp.py into emacs. Some vigorous usage of the IM-python menu gave the described results. 

[Comment 8 Matthew Kennedy (RETIRED) 2003-04-18 03:42:12 UTC]

okay. the problem is with open motif. open motif has trouble with emacs. in fact, i've seen this problem with the menu bar in general. we really should build with lesstiff these days anyway (no time atm to add that, ebuild patches welcome).

You can get around this problem by using a athena-based build. To do that, try:

   USE='-motif Xaw3d' emerge emacs

(you can verify that motif support wasn't compiled in by ldd /usr/bin/emacs afterwards). I'll leave this bug open.

[Comment 9 Matthew Kennedy (RETIRED) 2003-08-24 13:49:04 UTC]

if you have to use motif, maybe linking with lesstiff rather that openmotif will help.