summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* 1.18.01.18.0Matthias Clasen2013-09-232-1/+5
|
* l10n: Update Japanese translationvictory2013-09-231-199/+181
|
* Updated slovak translationPeter Mráz2013-09-191-15/+21
|
* Updated Indonesian translationDirgita2013-09-191-401/+492
|
* Updated slovak translationPavol Klačanský2013-09-151-234/+210
|
* Finnish translation update by Jiri GrönroosVille-Pekka Vainio2013-09-071-229/+221
|
* Update NEWS for releaseAlexander Larsson2013-09-031-0/+4
|
* daemon: Catch thumbnail files in large directory as wellDebarshi Ray2013-09-021-6/+16
| | | | | | | | | | | | | | | | | | 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
* post release version bumpAlexander Larsson2013-08-221-1/+1
|
* NEWS: Update for release1.17.90Alexander Larsson2013-08-221-0/+5
|
* Change version to 1.17.90Alexander Larsson2013-08-221-1/+1
|
* http: Replace deprecated SoupRequester by SoupSessionOndrej Holy2013-08-222-12/+5
| | | | https://bugzilla.gnome.org/show_bug.cgi?id=702624
* archive: Update to libarchive new apiOndrej Holy2013-08-221-2/+2
| | | | https://bugzilla.gnome.org/show_bug.cgi?id=703561
* gvfs-test: Update GPhoto test case record for libgphoto 2.5Martin Pitt2013-08-013-0/+0
| | | | | | | | libgphoto 2.5 changed the ioctls that get sent to the camera. Refresh test/files/powershot.ioctl.xz with a record with libgphoto 2.5. Also add the two test files on the SD card to test/files/source-gphoto/, so that it's easier to reconstruct that SD card and re-record the ioctl trace.
* Post release version bumpOndrej Holy2013-07-081-1/+1
|
* Update NEWS for 1.17.3 release1.17.3Ondrej Holy2013-07-081-0/+6
|
* Post release version bumpOndrej Holy2013-07-081-1/+1
|
* Implement clean shutdown in obexftp backendTimothy Arceri2013-07-081-6/+9
| | | | https://bugzilla.gnome.org/show_bug.cgi?id=511802
* Implement clean shutdown in mtp backendTimothy Arceri2013-07-081-2/+1
| | | | https://bugzilla.gnome.org/show_bug.cgi?id=511802
* Implement clean shutdown in afc backendTimothy Arceri2013-07-081-2/+1
| | | | https://bugzilla.gnome.org/show_bug.cgi?id=511802
* gvfs-test: Add first test for mtp backendMartin Pitt2013-07-023-0/+413
| | | | | | | | | | | | | | | | | | | | | | | Add umockdev dump and ioctl trace for a Sony Xperia Mini mobile phone (with CyanogenMod), with some small demo files and the ioctls from these commands recorded: gvfs-mount 'mtp://[usb:001,017]' gvfs-ls 'mtp://[usb:001,017]/SD-Karte' gvfs-ls 'mtp://[usb:001,017]/SD-Karte/Music' gvfs-ls 'mtp://[usb:001,017]/SD-Karte/Music/GStreamer - The Test Sine' gvfs-info 'mtp://[usb:001,017]/SD-Karte/Music/GStreamer - The Test Sine' gvfs-info 'mtp://[usb:001,017]/SD-Karte/Music/GStreamer - The Test Sine/sine.ogg' gvfs-cat 'mtp://[usb:001,017]/SD-Karte/Music/GStreamer - The Test Sine/sine.ogg' gvfs-cat 'mtp://[usb:001,017]/SD-Karte/hello.txt' gvfs-info 'mtp://[usb:001,017]/SD-Karte/hello.txt' gvfs-info 'mtp://[usb:001,017]/SD-Karte/DCIM/100CANON/IMG_0001.JPG' gvfs-cat 'mtp://[usb:001,017]/SD-Karte/DCIM/100CANON/IMG_0001.JPG' If umockdev is available, use it to simulate that device and check that we can get the directory and file info, and access the file contents. This bumps the (optional) umockdev dependency to >= 0.2.10.
* gvfs-test: Drop dbus startup from gvfs-testbedMartin Pitt2013-06-202-32/+38
| | | | | | | | Drop the D-BUS launch in the gvfs-testbed wrapper, and always launch the test session D-BUS in gvfs-test. This makes both scripts easier and more consistent, and also makes the GPhoto test work under gvfs-testbed. This bumps the (optional) umockdev dependency to >= 0.2.9.
* gvfs-test: Support calling this in an unbuilt treeMartin Pitt2013-06-201-3/+7
| | | | | Instead of failing all over the place and complaining about a missing session.conf, run the tests against the installed gvfs.
* afc: Bump libimobiledevice dependencyOndrej Holy2013-06-194-73/+1
| | | | | https://bugzilla.redhat.com/show_bug.cgi?id=951731 https://bugzilla.gnome.org/show_bug.cgi?id=702577
* afc: Update to libimobiledevice new apiOndrej Holy2013-06-183-13/+80
| | | | https://bugzilla.redhat.com/show_bug.cgi?id=951731
* Update NEWS for release1.17.2Alexander Larsson2013-06-141-0/+8
|
* metadata: Fix short journal checkAlexander Larsson2013-06-141-6/+11
| | | | | | | This was reading the size in the wrong place *sizep, not *(sizep-1), plus the out of bounds checks were wrong. https://bugzilla.gnome.org/show_bug.cgi?id=637095
* goa: export the activation root for volumesGiovanni Campagna2013-06-132-13/+22
| | | | | | | | Now that we can be in charge of mounts even if we have the shadow mount infrastructure, we should export it so that tracking of the associated GDaemonMount works correctly. https://bugzilla.gnome.org/show_bug.cgi?id=696279
* GProxyVolume: extend the protocol so the volume monitor can force a call to ↵Giovanni Campagna2013-06-133-7/+28
| | | | | | | | | | | Mount Some volume monitors, like gnome-online-accounts, want their mount implementation to be called even though the volume has an activation root. Allow them to advertise so using the expansion fields of the volume DBus representation. https://bugzilla.gnome.org/show_bug.cgi?id=696279
* GDaemonFile: fix relative path handling to account for mount_prefixGiovanni Campagna2013-06-131-16/+69
| | | | | | | | | | | | If two files have two different origins (say, one from g_mount_get_root() and one from g_file_new_for_uri()), the mount_spec they use could expose a different mount_prefix, even if the represent the same URI and network object. This in particular fixes the handling of shadow mounts for dav (which rewrites the mount_spec during mount to find the right prefix) https://bugzilla.gnome.org/show_bug.cgi?id=696279
* gvfs-test: Add first test for gphoto2 backendMartin Pitt2013-06-134-3/+400
| | | | | | | | | | | | | | | | | | | | | | Add umockdev dump and ioctl trace for a Canon PowerShot SX200 digicam, with ioctls from these commands recorded: gvfs-mount -li gvfs-mount gphoto2://[usb:001,011]/ gvfs-info gphoto2://[usb:001,011] gvfs-info gphoto2://[usb:001,011]/DCIM gvfs-info gphoto2://[usb:001,011]/DCIM/100CANON/IMG_0001.JPG gvfs-info gphoto2://[usb:001,011]/DCIM/100CANON/IMG_0002.JPG gvfs-cat gphoto2://[usb:001,011]/DCIM/100CANON/IMG_0001.JPG gvfs-cat gphoto2://[usb:001,011]/DCIM/100CANON/IMG_0002.JPG (With two tiny test images, not actual big photos) If umockdev is available, use it to simulate that device and check that we can get the directory and file info, and access the pictures. Note that this does not yet work under gvfs-testbed, as we somehow need to inject the $UMOCKDEV_ROOT into the spawned d-bus.
* gvfs-test: More robust cleanup of temporary home directoryMartin Pitt2013-06-131-1/+13
| | | | | | | Especially the trash:// tests have a tendency to leave the gvfs-metadata child around a little while after killing the D-BUS daemon, and thus leaving the temporary home directory busy. Retry for a few times to allow gvfsd-metadata to clean up itself.
* http: Don't send a SoupMessage if we only want the thumbnail pathDebarshi Ray2013-06-061-0/+7
| | | | https://bugzilla.gnome.org/show_bug.cgi?id=701714
* Use GOnce for interface type registrationTomas Bzatek2013-05-291-4/+5
| | | | Related to https://bugs.freedesktop.org/show_bug.cgi?id=65130
* gvfs-test: Drop assumption about local consolesMartin Pitt2013-05-291-6/+0
| | | | | Drop the check that mounting a CD fails without the fake polkit. This worked in ConsoleKit times, but not with logind any more.
* gvfs-test: Do not assume that /run/udev/rules.d/ existsMartin Pitt2013-05-292-1/+3
| | | | | Create the directory if necessary. Recent udev versions do not create it automatically any more.
* gvfs-test: Fix for Python 3.3Martin Pitt2013-05-291-3/+5
| | | | | | | Use read() instead of readall() for reading from subprocess, as this is a BufferedReader() now. This also works for older Python versions. Also, add another missing Popen.stdin.flush(), like in the previous commit.
* gvfs-test: Fix communication with gvfs CLI toolMartin Pitt2013-05-291-0/+4
| | | | | Flush the stdin stream to "gvfs-mount" after writing to it. Apparently Python 3.3's buffering behaviour has changed to require this now.
* gvfs-test: Avoid deadlocks when waiting for CLI user promptsMartin Pitt2013-05-291-0/+7
| | | | | Force subprocess' stdout to be non-blocking, so that we do not potentially wait forever, but time out properly.
* smb: Add support for specifying custom portTomas Bzatek2013-05-283-24/+88
| | | | | | | | | | Thanks to the work by Jeremy Allison we should be able to connect to a non-standard port through new enough Samba version. This patch adds a port argument to smburi parser and both smb and smb-browse backends. https://bugzilla.gnome.org/show_bug.cgi?id=698071
* Post release version bumpOndrej Holy2013-05-271-1/+1
|
* Update NEWS for 1.17.1 release1.17.1Ondrej Holy2013-05-241-0/+12
|
* metadata: Downgrade journal short-read to debugColin Walters2013-05-221-1/+1
| | | | | | | | | | | Because multiple clients can be concurrently writing to the journal, it's possible to see partially written journal entries. Emitting g_warning() here breaks test cases. The real fix would be safe concurrent access to the journal, but that's harder. https://bugzilla.gnome.org/700785
* sftp: Fix two compilation warningsColin Walters2013-05-211-2/+2
|
* Updated slovak translationRichard Stanislavský2013-05-211-1902/+1736
|
* metadata: Flush all scheduled writeouts on daemon exitTomas Bzatek2013-05-131-6/+40
| | | | | | | | This patch ensures that we safely write all data from journals to metatrees on exit. E.g. if anything happens to session bus or we get replaced by some other instance. https://bugzilla.gnome.org/show_bug.cgi?id=637095
* metadata: Use shorter writeout timeout on NFSTomas Bzatek2013-05-133-3/+16
| | | | | | | Since we've moved journal to a non-volatile storage, let's flush more often to minimize a chance of data loss. https://bugzilla.gnome.org/show_bug.cgi?id=637095
* metadata: Put journal in $XDG_RUNTIME_DIR for shared NFS homedir caseTomas Bzatek2013-05-133-105/+136
| | | | | | | | | | | | | | | | | | | This essentially moves is_on_nfs() from metatree.c in metabuilder.c as the more appropriate place for shared functions. It's used in meta_builder_get_journal_filename() to determine whether to use original metadata directory or temporary $XDG_RUNTIME_DIR location to work around certain NFS issues. The idea behind this change is to have separate journals for every client that is accessing shared homedir. Then the only possible point of conflict is on rotation which is backed up by atomic file rename. Without this, there were multiple metadata daemons writing to the same journal file, overwriting changes to each other and being racy in flush and rotation. There will always be a conflict between clients, overwriting tree file data by flushing their journals. https://bugzilla.gnome.org/show_bug.cgi?id=637095
* metadata: Create new journal if it doesn't existTomas Bzatek2013-05-133-6/+18
| | | | | | | | | | | | | | | With concurrent access of multiple daemons there may be a moment when tree file exists but not the journal file. The daemon can't write anything without journal and is doomed until next rotation. Missing journal file can also happen on system crash etc. This patch tries to create new journal file only when it doesn't exist, other errors still lead to inability to store anything. This will also allow us to have journal file somewhere else, e.g. on a non-persistent storage. https://bugzilla.gnome.org/show_bug.cgi?id=637095
* metadata: Be more resistive to broken journal filesTomas Bzatek2013-05-131-0/+12
| | | | | | | | | | | | | | | | | | | In shared NFS homedir case with multiple clients writing to the same mmaped journal file data can get easily corrupted. The daemon iterates over a journal file on flush taking in account variable entry size and advances according to the data read. However in certain case invalid data are read making us to jump out of bounds. In case of zero entry size we would stand at the same place leading to infinite loop. This patch checks if the indicated entry size is at least the size of the structure we're getting the size from (it's a first element) and breaks the iteration cycle if it's not. This may lead to partial data loss on flush as we don't process the rest of the journal file. Old data from existing tree file will be preserved of course, only few recent changes would get lost. https://bugzilla.gnome.org/show_bug.cgi?id=637095
View Lorry Controller Status