Downloaed portage 1.1a iso started from stage3 tar.gz as instructions emerge kde emerge vim I'd reboot, but x still not configured. first vim coughed badly as gpm wasnt started, killed vim took a "kill -9" though. started gpm and all ok. dont understand why this caused so many problems with vim. occasionally when using the local console, rather than x, i get **debug** [/var/tmp/portage/gpm-1.20.0-r1/work/gpm-1.20.0/src/gpm.c(677)]: or the same, except liblow.c vim hangs and only an "kill -9" on the vim process will stop vim. Once this happens vim wont work until gpm is restarted. My log.... Apr 15 02:15:01 [/usr/sbin/gpm] info: [/var/tmp/portage/gpm-1.20.0-r1/work/gpm-1.20.0/src/gpm.c(766)]: Apr 15 02:15:01 [/usr/sbin/gpm] Connecting at fd 5 Apr 15 02:15:01 [/usr/sbin/gpm] info: [/var/tmp/portage/gpm-1.20.0-r1/work/gpm-1.20.0/src/gpm.c(668)]: Apr 15 02:15:01 [/usr/sbin/gpm] Request on 5 (console 0) Apr 15 02:15:01 [/usr/sbin/gpm] info: [/var/tmp/portage/gpm-1.20.0-r1/work/gpm-1.20.0/src/gpm.c(677)]: Apr 15 02:15:01 [/usr/sbin/gpm] Closing Apr 15 02:15:09 [/usr/sbin/gpm] info: [/var/tmp/portage/gpm-1.20.0-r1/work/gpm-1.20.0/src/gpm.c(766)]: Apr 15 02:15:09 [/usr/sbin/gpm] Connecting at fd 5 Apr 15 02:15:09 [/usr/sbin/gpm] info: [/var/tmp/portage/gpm-1.20.0-r1/work/gpm-1.20.0/src/gpm.c(668)]: Apr 15 02:15:09 [/usr/sbin/gpm] Request on 5 (console 0) Apr 15 02:15:09 [/usr/sbin/gpm] info: [/var/tmp/portage/gpm-1.20.0-r1/work/gpm-1.20.0/src/gpm.c(677)]: Apr 15 02:15:09 [/usr/sbin/gpm] Closing Apr 15 02:15:13 [/usr/sbin/gpm] info: [/var/tmp/portage/gpm-1.20.0-r1/work/gpm-1.20.0/src/gpm.c(766)]: Apr 15 02:15:13 [/usr/sbin/gpm] Connecting at fd 5 Apr 15 02:15:13 [/usr/sbin/gpm] info: [/var/tmp/portage/gpm-1.20.0-r1/work/gpm-1.20.0/src/gpm.c(668)]: Apr 15 02:15:13 [/usr/sbin/gpm] Request on 5 (console 0) Apr 15 02:15:13 [/usr/sbin/gpm] info: [/var/tmp/portage/gpm-1.20.0-r1/work/gpm-1.20.0/src/gpm.c(677)]: Apr 15 02:15:13 [/usr/sbin/gpm] Closing Apr 15 02:15:13 [/usr/sbin/gpm] info: [/var/tmp/portage/gpm-1.20.0-r1/work/gpm-1.20.0/src/gpm.c(766)]: Apr 15 02:15:13 [/usr/sbin/gpm] Connecting at fd 5 Apr 15 02:15:13 [/usr/sbin/gpm] info: [/var/tmp/portage/gpm-1.20.0-r1/work/gpm-1.20.0/src/gpm.c(668)]: Apr 15 02:15:13 [/usr/sbin/gpm] Request on 5 (console 0) Apr 15 02:15:13 [/usr/sbin/gpm] info: [/var/tmp/portage/gpm-1.20.0-r1/work/gpm-1.20.0/src/gpm.c(677)]: Apr 15 02:15:13 [/usr/sbin/gpm] Closing Apr 15 02:15:14 [/usr/sbin/gpm] info: [/var/tmp/portage/gpm-1.20.0-r1/work/gpm-1.20.0/src/gpm.c(766)]: Apr 15 02:15:14 [/usr/sbin/gpm] Connecting at fd 5 Apr 15 02:15:14 [/usr/sbin/gpm] info: [/var/tmp/portage/gpm-1.20.0-r1/work/gpm-1.20.0/src/gpm.c(668)]: Apr 15 02:15:14 [/usr/sbin/gpm] Request on 5 (console 0) Apr 15 02:15:14 [/usr/sbin/gpm] info: [/var/tmp/portage/gpm-1.20.0-r1/work/gpm-1.20.0/src/gpm.c(677)]: Apr 15 02:15:14 [/usr/sbin/gpm] Closing Apr 15 02:15:14 [/usr/sbin/gpm] info: [/var/tmp/portage/gpm-1.20.0-r1/work/gpm-1.20.0/src/gpm.c(766)]: Apr 15 02:15:14 [/usr/sbin/gpm] Connecting at fd 5 Apr 15 02:15:22 [/usr/sbin/gpm] info: [/var/tmp/portage/gpm-1.20.0-r1/work/gpm-1.20.0/src/gpm.c(668)]: :
You know, this kind of thing happens with mc as well. I spoke to the gpm guy about this. He wasn't especially helpful. Might I strongly suggest that you bug the gpm author? (as in the actual author of the gpm application). Perhaps you might receive a better response. And then please let me know
*** Bug 2064 has been marked as a duplicate of this bug. ***
Aron, I would rather you take a look at this one. What I have tried locally is to not patch it at all, it seems to go fine with gpm. But I am not in tune with the finer points of that. Thanks, Seemant
I've noticed a problem similar to this, but only when using aterm or rxvt--not xterm.
Fixed in vim-6.1-r7 by removing gpm support.
