commit 1c5ae07f1d866be3830abbd318c3dcce91f48d69
Author: Alexander Larsson <alexl@redhat.com>
Date:   2013-11-13

    Update NEWS for release

M	NEWS

commit cfa747bc5733e46ecfa45b55698dc5ec3b70263c
Author: Ross Lagerwall <rosslagerwall@gmail.com>
Date:	2013-11-05

    programs: Escape string properly

    Use an unsigned char to avoid implementation-defined behavior of
    a right
    shift.
    Shift by 4 rather than 8 to get the second half of a byte.

    https://bugzilla.gnome.org/show_bug.cgi?id=711457

M	programs/gvfs-info.c

commit 4e9e6f85f951412e269e35c47488c527fded007d
Author: Ross Lagerwall <rosslagerwall@gmail.com>
Date:	2013-11-05

    client: Fix SIGSEGV in fallback copy

    If the daemon is killed during the fallback copy, it is possible that
    proxy is NULL which causes a segfault when unrefing it.  Use
    g_clear_object() instead.

    https://bugzilla.gnome.org/show_bug.cgi?id=711454

M	client/gdaemonfile.c

commit d8381ef51bfbb2148d31eaeb674f75e8cafb1fe0
Author: Ross Lagerwall <rosslagerwall@gmail.com>
Date:	2013-10-26

    sftp: Return the correct error code on failed symlink creation

    If the symlink path already exists, return the correct error code of
    G_IO_ERROR_EXISTS.

    https://bugzilla.gnome.org/show_bug.cgi?id=710935

M	daemon/gvfsbackendsftp.c

commit 4ba6016158cbf6b40900d6e4594be5c820016480
Author: Ross Lagerwall <rosslagerwall@gmail.com>
Date:	2013-10-23

    http: Set error to NULL to possibly prevent crash on close

    https://bugzilla.gnome.org/show_bug.cgi?id=710678

M	daemon/gvfsbackendhttp.c

commit 686f611affc7ac474efc5fc30d39b56b80db9f20
Author: Ross Lagerwall <rosslagerwall@gmail.com>
Date:	2013-10-08

    fuse: Use the big_writes option to speed up writes

    Without the big_writes option, fuse uses a block size of 4096 bytes
    which results in poor write performance.  So use the big_writes option
    to write blocks up to 64KiB in size.

    https://bugzilla.gnome.org/show_bug.cgi?id=652540

M	client/gvfsfusedaemon.c
M	daemon/main.c

commit b889e6af4daf1b0b851d6087438df00c98934c85
Author: Alexander Larsson <alexl@redhat.com>
Date:	2013-10-08

    gphoto2: Allow seek past end of file

    https://bugzilla.gnome.org/show_bug.cgi?id=709432

M	daemon/gvfsbackendgphoto2.c

commit 640a2b99b5cadfcb4df7581d397e77bc27c5eb62
Author: Alexander Larsson <alexl@redhat.com>
Date:	2013-10-08

    cdda: Allow seek past end of file

    https://bugzilla.gnome.org/show_bug.cgi?id=709432

M	daemon/gvfsbackendcdda.c

commit 1578ee5cdb90f6980954ba7cb9c7fc555dde80e0
Author: Alexander Larsson <alexl@redhat.com>
Date:	2013-10-08

    sftp: Allow seek past end of file

    also, don't query for the file size unless required for SEEK_END

    https://bugzilla.gnome.org/show_bug.cgi?id=709432

M	daemon/gvfsbackendsftp.c

commit a764153ad2479370015c14f53b1c1e98f1754e11
Author: Alexander Larsson <alexl@redhat.com>
Date:	2013-10-03

    client: Don't user g_source_remove() on non-default main context

    We created a GSource, attached it to a non-default main context and
    then removed it via g_source_remove, which removed the source with the
    same id on the main context, which typically was the X fd, causing
    everything to stop working!

    Non-default main contexts must use g_source_destroy()

    https://bugzilla.gnome.org/show_bug.cgi?id=708744

M	client/gdaemonfileenumerator.c

commit 6b76836e994b9fc77e09bc43b86f1d50f456670e
Author: Ross Lagerwall <rosslagerwall@gmail.com>
Date:	2013-09-25

    fuse: Make file nonseekable if it actually is

    Instead of failing in read() with ENOTSUPP after the lseek on a
    nonseekable stream succeeds, make the lseek fail with ESPIPE, as it
    should.  This is important for applications which test the return
    value
    of lseek to determine if the file descriptor is seekable.

M	client/gvfsfusedaemon.c

commit b3f2a3cec077b62111ba6d8ed33b13cb9764dea2
Author: Ross Lagerwall <rosslagerwall@gmail.com>
Date:	2013-09-25

    fuse: Enforce sync_read

    When running multithreaded, fuse can issue readahead requests out of
    order which can cause subsequent reads to fail with ENOTSUPP
    (if seeking
    backward is not supported on the stream).

    Force readahead to occur in order to prevent this problem.

M	client/gvfsfusedaemon.c

commit 8ed7ab705715523467162283dd4357442655412b
Author: Ross Lagerwall <rosslagerwall@gmail.com>
Date:	2013-09-25

    fuse: Fix seek offset calculation

    Since fh->pos is already incremented by n_bytes_skipped, check if
    offset == fh->pos.

    This error was hidden by the fact that the operation is retried when
    -EIO is returned.  When it was retried, the stream was already in the
    correct position and so no seek operation was required.

M	client/gvfsfusedaemon.c

commit ee2a74ce572209b746438b9faf558c009f037a78
Author: Ross Lagerwall <rosslagerwall@gmail.com>
Date:	2013-09-21

    daemon: Emit signal before returning dbus value

    In gvfsjobopenforread.c, the dbus method returns a value in
    create_reply
    which eventually results in a GVfsJobRead job to be sent to the
    backend.
    This could happen before the "new-source" signal is emitted.  If this
    happens, the job is not queued because the "new_job" signal would not
    have been connected to a job source yet.  The read then hangs because
    the GVfsJobRead is lost.

    This is hit often when performing large smb transfers (see
    https://bugzilla.gnome.org/show_bug.cgi?id=697782 and
    https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1075923).
    It can be reproduced by putting a small sleep before the
    g_signal_emit_by_name call.

    Fix this by emitting the "new-source" signal *before* the dbus method
    value is returned.	This ensures that the "new_job" signal is set up
    before any further jobs are sent.

    Note that the same problem and solution applies for
    gvfsjobopenforwrite.c.

M	daemon/gvfsjobopenforread.c
M	daemon/gvfsjobopenforwrite.c

commit 67273972b54823584b5abb7945652a0bbf46200e
Author: Ondrej Holy <oholy@redhat.com>
Date:	2013-09-26

    gdbus: fix compilation warnings

    https://bugzilla.gnome.org/show_bug.cgi?id=591228#c21

M	client/gvfsdaemondbus.c

commit 0f4ba6734fd7760a8070a0ef8efa3dd891fc632f
Author: Ondrej Holy <oholy@redhat.com>
Date:	2013-09-26

    GDaemonFileEnumerator: fix compilation warning

    https://bugzilla.gnome.org/show_bug.cgi?id=591228

M	client/gdaemonfileenumerator.c

commit fd0feb2d8a6a74854232c9344402c871da8e5bb5
Author: Alexander Larsson <alexl@redhat.com>
Date:	2013-09-26

    GVfsDaemon: Don't deadlock on cliend disconnect

    There was a deadlock that could happen on client disconnect in
    peer_connection_closed(). If the cancelled job immediately called
    back into
    job_finished_callback() we would deadlock on daemon->mutex.

    So, make sure we cancel jobs without holding the lock, just like
    handle_cancel() does.

    https://bugzilla.gnome.org/show_bug.cgi?id=708816

M	daemon/gvfsdaemon.c

commit 1b51c45d19a62148d7cdaffbc4a70b3748598b45
Author: Alexander Larsson <alexl@redhat.com>
Date:	2013-09-26

    client: Remove unused code for dbus vfs filters

    This code is not used anymore

    https://bugzilla.gnome.org/show_bug.cgi?id=708744

M	client/gdaemonfile.c
M	client/gdaemonfilemonitor.c
M	client/gdaemonmount.c
M	client/gvfsdaemondbus.c
M	client/gvfsdaemondbus.h
M	client/gvfsiconloadable.c

commit 62e82b8c67ff662eab0904373d15e67bedfaf488
Author: Alexander Larsson <alexl@redhat.com>
Date:	2013-09-26

    GDaemonFileMonitor: Only recieve events on one dbus connection

    There is no need to register for monitor evens on all dbus
    connections,
    just the one we send the request on.

    https://bugzilla.gnome.org/show_bug.cgi?id=708744

M	client/gdaemonfilemonitor.c

commit 4402ba3e5c7f75b2d03e7663bc34b64767247339
Author: Alexander Larsson <alexl@redhat.com>
Date:	2013-09-26

    GDaemonFileEnumerator: Only listen to messages one connection

    There is no need to listen to messages on other connections than
    the one we sent the request on. In fact, doing so is bad as it
    can cause
    locking issues as per bug 708721.

    https://bugzilla.gnome.org/show_bug.cgi?id=708744

M	client/gdaemonfile.c
M	client/gdaemonfileenumerator.c
M	client/gdaemonfileenumerator.h

commit 1ce0987f7fd0aa601ea50de9d8b11d9008c786b6
Author: Debarshi Ray <debarshir@gnome.org>
Date:	2012-11-20

    daemon: Catch thumbnail files in large directory as well

    When building the file attribute table info, use thumbnail paths in
    $XDG_CACHE_DIR/thumbnails/large in addition to
    $XDG_CACHE_DIR/thumbnails/normal.

    Failing to do this would cause an application that creates large
    thumbnails by default to never find any value for
    G_FILE_ATTRIBUTE_THUMBNAIL_PATH, with no
    G_FILE_ATTRIBUTE_THUMBNAILING_FAILED set, which might cause the
    application to either think thumbnailing is still in progress, or
    blindly requeue thumbnail operations in a loop.

    Large thumbnails are generally preferred, so we now default to
    the path
    of a large thumbnail (in case both are present).

    Fixes: https://bugzilla.gnome.org/688685

M	daemon/gvfsbackend.c

commit 32a77af9ce68178c0e1e79801bd8da33ed5a7ead
Author: victory <victory.deb@gmail.com>
Date:	2013-11-03

    l10n: Update Japanese translation

M	po/ja.po

commit d0af1cd5009720132b8aa0e66a5419b5b237717b
Author: Andika Triwidada <andika@gmail.com>
Date:	2013-09-23

    Updated Indonesian translation

M	po/id.po

commit d71c6108901460842de25012d5ece727a0c70d27
Author: Ondrej Holy <oholy@redhat.com>
Date:	2013-06-11

    afc: Update to libimobiledevice new api

    https://bugzilla.redhat.com/show_bug.cgi?id=951731
    https://bugzilla.gnome.org/show_bug.cgi?id=702577

M	configure.ac
M	daemon/gvfsbackendafc.c
M	monitor/afc/afcvolume.c
M	monitor/afc/afcvolumemonitor.c

commit 4378aaf8522bf8381ba05ab717c9baaca2f1287a
Author: Alexander Larsson <alexl@redhat.com>
Date:	2013-06-14

    Post release version bump

M	configure.ac