When my internet connection is switched off and I want to start a solo training game, bzflag sits 40 seconds idling on the initial black screen before the Join...Quit menu appears. Version 2.0.0.20050117 didn't do this, it started two days ago with version 2.0.2.20050318. Reproducible: Always Steps to Reproduce: 1. disconnect the internetmodem (without ifconfig down) 2. bzflag -solo 24 Actual Results: A forty second pause before the game menu appears. When the internetmodem is connected, the pause is only slight (about one second) and this is what tcpdump then says: 10:14:53.907078 IP ordesa.local.32826 > vhost.sourceforge.net.http: S 2805711005:2805711005(0) win 5840 <mss 1460,sackOK,timestamp 1568895[|tcp]> 10:14:54.077837 IP vhost.sourceforge.net.http > ordesa.local.32826: S 2780465576:2780465576(0) ack 2805711006 win 5792 <mss 1460,sackOK,timestamp 1691011609[|tcp]> 10:14:54.077925 IP ordesa.local.32826 > vhost.sourceforge.net.http: . ack 1 win 1460 <nop,nop,timestamp 1569065 1691011609> 10:14:54.078042 IP ordesa.local.32826 > vhost.sourceforge.net.http: P 1:76(75) ack 1 win 1460 <nop,nop,timestamp 1569066 1691011609> 10:14:54.253424 IP vhost.sourceforge.net.http > ordesa.local.32826: . ack 76 win 1448 <nop,nop,timestamp 1691011785 1569066> 10:14:54.884652 IP vhost.sourceforge.net.http > ordesa.local.32826: F 604:604(0) ack 76 win 1448 <nop,nop,timestamp 1691012415 1569066> 10:14:54.884713 IP ordesa.local.32826 > vhost.sourceforge.net.http: . ack 1 win 1460 <nop,nop,timestamp 1569872 1691011785,nop,nop,[|tcp]> 10:14:54.891802 IP vhost.sourceforge.net.http > ordesa.local.32826: P 1:604(603) ack 76 win 1448 <nop,nop,timestamp 1691012415 1569066> 10:14:54.891823 IP ordesa.local.32826 > vhost.sourceforge.net.http: . ack 605 win 1762 <nop,nop,timestamp 1569880 1691012415> 10:14:54.892273 IP ordesa.local.32826 > vhost.sourceforge.net.http: F 76:76(0) ack 605 win 1762 <nop,nop,timestamp 1569880 1691012415> 10:14:55.066202 IP vhost.sourceforge.net.http > ordesa.local.32826: . ack 77 win 1448 <nop,nop,timestamp 1691012598 1569880> Expected Results: Bzflag should not try to connect, or at least not sit there so long waiting for nothing. Portage 2.0.51.19 (default-linux/x86/2004.3, gcc-3.4.3-20050110, glibc-2.3.4.20050125-r1, 2.6.10 i686) ================================================================= System uname: 2.6.10 i686 AMD Athlon(tm) XP 2800+ Gentoo Base System version 1.6.10 Python: dev-lang/python-2.3.4-r1 [2.3.4 (#1, Feb 8 2005, 12:30:54)] dev-lang/python: 2.3.4-r1 sys-devel/autoconf: 2.59-r6, 2.13 sys-devel/automake: 1.7.9-r1, 1.8.5-r3, 1.5, 1.4_p6, 1.6.3, 1.9.4 sys-devel/binutils: 2.15.92.0.2-r1 sys-devel/libtool: 1.5.10-r4 virtual/os-headers: 2.6.10 ACCEPT_KEYWORDS="x86" AUTOCLEAN="yes" CFLAGS="-march=athlon-xp -Os -pipe -fomit-frame-pointer -fstack-protector" CHOST="i686-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3.3/env /usr/kde/3.3/share/config /usr/kde/3.3/shutdown /usr/kde/3.4/env /usr/kde/3.4/share/config /usr/kde/3.4/shutdown /usr/kde/3/share/config /usr/lib/X11/xkb /usr/share/config /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-march=athlon-xp -Os -pipe -fomit-frame-pointer -fstack-protector" DISTDIR="/usr/portage/distfiles" FEATURES="autoaddcvs autoconfig distlocks maketest notitles sandbox sfperms strict test userpriv usersandbox" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/local/portage" USE="x86 3dnow X aim alsa apm arts avi berkdb bitmap-fonts cdr crypt curl dlloader emboss encode esd fam fbcon flac font-server ftp gdbm gif gpm hardened imagemagick imlib jabber jpeg kde kdeenablefinal libg++ libwww mad mbox mikmod mime mmx mp3 mpeg mysql ncurses nls oggvorbis opengl pam pdflib png python qt quicktime readline sasl sdl slang speex spell sse ssl svga tcltk tiff truetype truetype-fonts type1-fonts unicode xine xml xml2 xmms xsl xv zlib video_cards_via linguas_en linguas_eo linguas_es linguas_nl" Unset: ASFLAGS, CBUILD, CTARGET, LANG, LC_ALL, LDFLAGS
This really should be reported to the authors of the package and not to us, since it is something that they changed within the package itself. We really prefer to not change the functionality of a package, as it requires us to forward port the new functionality to any newer version of the software. http://sourceforge.net/tracker/?group_id=3248&atid=103248
> This really should be reported to the authors of the package Okay, I would do that, but in order to submit a bug it is required to login, and SF's Terms of Use are unpalatable (14. Indemnity). So I posted it to the bzflag-users list.
