Version 2.6.1 released.

1 Mar

Version 2.6.1 released.

Tonight I was able to finish up both the dump1090-mutability and dump1090-fa Raspbian Stretch images. With the completion of the images I can officially announce the release of v2.6.1. Being labeled as a minor version this release contains only bug fixes. However, the fixes include many major bug fixes which should be welcome news to those who are having or had issues with the previous v2.6.0 release. Also included are the ability to update to the most recent ARM client version 3.7.40 and FlightAware’s PiAware v3.5.3. The images and source code making up this release can as always be found in the projects GitHub repository. Click here to visit the GitHub page related to this release. The following is the full CHANGELOG for this release.

  • Readded missing RTL-SDR kernel module blacklist to dump1090-mutability script.
  • Password recovery token column used for password retrieval not added properly in the past.
  • Postfix package installation was removed at some point and is now reintroduced.
  • When created remote database users are now allowed to access the server remotely.
  • Fixes to issues contained within (thanks to @mkrzysztofowicz)
  • Consolidated simple queries which run on both MySQL and SQLite in
  • Dump1090-mutability wget permission error fixed. (thanks to SCX77)
  • Latitude and longitude sent to get altitude was hard coded in ADS-B Exchange script.
  • The ADS-B Exchange script was not getting latitude and longitude from dump1090-mutability.
  • Fixed RTLSDR device permissions issue by downloading rtl-sdr.rules if not present.
  • The option to upgrade the Planefinder client now appears when one is available.
  • Updated to install ARM client version 3.7.40.
  • Updated to install PiAware version 3.5.3.
  • The version of mlat-client installed has been reverted back to v0.2.6 from v0.2.9.
  • Fixed path variable to where the built dump1090-mutability packages are archived.
  • Fixed path variable used to check if the ADS-B Exchange build directory exists.
  • Simplified and fixed lines killing existing ADS-B Exchange processes during reinstallation.
  • Simplified and fixed lines killing existing AboveTustin processes during reinstallation.
  • Simplified and fixed lines killing existing BeastSplitter processes during reinstallation.
  • Fixed many minor bash script output syntax and formatting issues.
  • Some Whiptail dialogs have been expanded to be more descriptive.
  • AboveTustin script was not retrieving the current longitude when upgrading it.

Feel free to report any further bugs which I may have missed in testing either in the forums located on this site or to the projects GitHub issue tracker.



  1. hi Joe
    good to see you’re back

    have installation problem with
    Lubuntu 17.01 (see below)

    VERSION=”17.10 (Artful Aardvark)”
    PRETTY_NAME=”Ubuntu 17.10″

    while trying to install dump1090-mutability
    I get this error

    /usr/include/x86_64-linux-gnu/bits/stdio2.h:64:10: note: ‘__builtin___snprintf_chk’ output between 5 and 11 bytes into a destination of size 6
    return __builtin___snprintf_chk (__s, __n, __USE_FORTIFY_LEVEL – 1,
    __bos (__s), __fmt, __va_arg_pack ());
    cc1: all warnings being treated as errors
    Makefile:49: recipe for target ‘interactive.o’ failed
    make[2]: *** [interactive.o] Error 1
    make[2]: Leaving directory ‘/home/lubudu/adsb-receiver/build/dump1090-mutability/dump1090’
    dh_auto_build: make -j1 “EXTRACFLAGS=-DHTMLPATH=\\\”/usr/share/dump1090-mutability/html\\\” -DMODES_DUMP1090_VARIANT=\\\”dump1090-mutability\\\”” returned exit code 2
    debian/rules:21: recipe for target ‘override_dh_auto_build’ failed
    make[1]: *** [override_dh_auto_build] Error 2
    make[1]: Leaving directory ‘/home/lubudu/adsb-receiver/build/dump1090-mutability/dump1090’
    debian/rules:30: recipe for target ‘build’ failed
    make: *** [build] Error 2
    dpkg-buildpackage: error: debian/rules build gave error exit status 2

    Configuring dump1090-mutability to start automatically….
    Installing the dump1090-mutability package…

    dpkg: error: cannot access archive ‘/home/lubudu/adsb-receiver/build/dump1090-mutability/dump1090-mutability_1.15~dev_*.deb’: No such file or directory

    any help will be appreciated
    thanks / Evangel

  2. Hi Joe
    I re-installed dump1090-mutability after your additions, still no joy.
    error was again :
    dpkg: error: cannot access archive ‘/home/lubudu/adsb-receiver/build/dump1090-mutability/dump1090-mutability_1.15~dev_*.deb’: No such file or directory

    The solution I found….
    I installed the whole thing in a Debian 8 VM, and I copied the 2 .deb files to the Lubuntu Hard Disk installation and it worked !

    apparently the to .deb were not created.


    1. Must be something missing as far as packages needed to build dump1090-mutability. Will take a look at it today on an Ubuntu 17.10 image.

      1. thanks Joe
        and while at it can you please fix where it says metric in the \html\config.js , I keep changing (“false;”) to (false;) without quotes in order to display feet. :=)

        1. OK here is what I am thinking is the deal with both the mutability version of dump1090 versions on Ubuntu 17.10. It looks as though Unbuntu 17.10 is using a newer version of gcc than in previous versions of Ubuntu. This is causing the error “… directive output may be truncated…” which halts the build of both of the mutability version of dump1090 package. Being this is an issue between the dump1090-mutability/dump1090-fa source code and the new gcc compiler there is nothing I can do as far as the scripts are concerned other than try to compile an older version of gcc that plays nice with the dump1090 source code.

          What I can do is open an issue in the dump1090 issue trackers and hope for a fix to come down the line there. I have opened an issue pertaining to the matter on the dump1090-mutability issue tracker.

          As far as dump190-fa is concerned that was fixed with the addition of another version variable in case dump1090-fa and piawares version numbers do not match each other. I have commited a fix to the repository addressing this issue.

          I will take a look at the configuration issue this evening.

Leave a Reply

Your email address will not be published. Required fields are marked *