vim can't expand buffer names after detaching/reattaching from a screen session

[Albert Cardona]

1 - Open an xterm
2 - open a screen with: screen
3 - open vim
4 - edit more than one file, with
       :edit some_file
       :edit some_other_file
5 - change buffer with :b some_f then type TAB key to expand the name.

works fine.

Then:

6 - detach screen with control+a control+d
7 - screen -r to reattach
8 - now change buffer with :b some_f then type TAB key: a ^ prints, but buffer names are not expanded any more.

The only known workaround:
:mksession!
:qa
vim -S Session.vim

i.e. relaunch vim with the previous open buffers.

Some information on my system:

Thinkpad T60p with FireGL 5050 using fglrx binary proprietary driver, and dist-upgraded to today 2008-02-21.

$ cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=7.10
DISTRIB_CODENAME=gutsy
DISTRIB_DESCRIPTION="Ubuntu 7.10"

[interp (ubuntu-1-lysium)]

I can't verify this in Ubuntu 8.04.

Proposed sequence of commands (screen, vim, detach, reattach, completion) works fine and as expected for me.

DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=8.04
DISTRIB_CODENAME=hardy
DISTRIB_DESCRIPTION="Ubuntu 8.04.1"

$ vim --version
VIM - Vi IMproved 7.1 (2007 May 12, compiled Jan 31 2008 12:00:11)
Included patches: 1-138
Compiled by <email address hidden>
Huge version with GTK2-GNOME GUI.

Maybe close this bug?

[Albert Cardona (cardona)]

The problem persists in Ubuntu 8.04 with fglrx and ATI FireGL.

interp: try to kill Xorg, then re-attach your screen session to see the bug.

[Anzenketh (anzenketh)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to look at all reported bugs in a timely manner.
There have been many changes in Ubuntu since that time you reported the bug and your problem may have been fixed with some of the updates. It would help us a lot if you could test the current Ubuntu development version (10.10). If you can test it, and it is still an issue, we would appreciate if you could upload updated logs by running apport-collect <bug #>, and any other logs that are relevant for this particular issue.

[Launchpad Janitor (janitor)]

[Expired for vim (Ubuntu) because there has been no activity for 60 days.]