mpd: Test that "list album foo" responds correctly

Previously, test_list_album_with_artist_name would only test that the
command didn't fail. Now it also checks that the response is correct.
That is, that the response contains albums.

This makes the test detect the error reported in #817.

(cherry picked from commit 9771eda23068f4581a30059ac597f1360d349dcd)
mpd: Fix list commands with 3 arguments (fixes #817)

List commands with 3 arguments should return albums, not artists.

(cherry picked from commit ec413126f1670ccf4f5853e6ee375239cdb374e6)
docs: Add the mpd list command fix to the changelog

(cherry picked from commit 92fa75325d968bb271b8601447080c29bccbde5f)

Conflicts:
	docs/changelog.rst
docs: Fix formatting

(cherry picked from commit 26cfd24e113801b23a00bfb5d6706ee66e643e5b)
docs: Add note Debian package distro support (fixes #820)
log: Don't disable loggers when loading fileConfig

The default when loading config for logging from a file is to disable
existing loggers. Since some loggers are created before logging is set
up, these loggers were disabled if logging/config_file is set.

(cherry picked from commit cb0387c46d7c65d141355ce716764f7b05ef3f3f)

Conflicts:
	docs/changelog.rst
docs: Use :confval:-syntax, add fixes for logging issue

(cherry picked from commit 524043f6b7ee4c3120d6e7e00bad154e4ad82668)

Conflicts:
	docs/changelog.rst
main: Return status code 1 if {Backend,Frontend,Mixer}Error is raised
config: Support passing directories to mopidy --config
docs: Return exit status 1 on initialization error
config: Only load .conf-files when loading directories
docs: Add directories to --config in man page
docs: Fix grammar
Merge branch 'trygveaa/feature/mopidy-config-dirs' into release/v0.19.x

Conflicts:
	docs/changelog.rst
main: Ensure that exit_status_code always is assigned

KeyboardInterrupts are not always catched in commands.py. As far as I
have seen, if I/O operations are ongoing, a KeyboardInterrupt may be
raised there instead of in commands.py. In some cases, this may cause
loop.run() to return, which previously resulted in exit_status_code
being referenced before assignment.
network: disable_recv before telling actor to close connection

As of d62ad96, when the connection can't receive more data from the
client, it tells the actor to stop the connection and calls
disable_recv(). The actor operates in it's own thread and when it stops
the connection, disable_recv is being called again from a different
thread. Since the actor is told to stop the connection before
disable_recv is called, the two calls to disable_recv may happen
simultaneously.

This causes a race condition issue where both threads can reach past the
check that recv_id is not None before either of them set it to None. If
one of them set it to None before the other one tries to use it, an
error is raised.

This commit calls disable_recv before telling the actor to stop the
connection. Since disable_recv is a blocking call, this ensures that
recv_id is being set to None before the actor thread begins to stop the
connection.

Fixes #781
#818 Remove mopidy lux from documentation

(cherry picked from commit 06d7d650f870dfe55e02bc091f6f344df2762ef9)
tests: Test call order in test_recv_callback_gets_no_data
main: Log uncaught exceptions

(cherry picked from commit 027b7a53fe9212853062da352c464c4277ade510)
Merge pull request #827 from trygveaa/fix/network-thread-issue

network: disable_recv before telling actor to close connection