summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
...
* sftp: Handle host key / IP mismatchRoss Lagerwall2015-04-091-38/+121
| | | | | | | | | | | | | | Handle the following SSH login question by asking the user whether to continue or not: Warning: the ECDSA/RSA host key for 'hostname' differs from the key for the IP address '...' Offending key for IP in /home/username/.ssh/known_hosts:??? Matching host key in /home/username/.ssh/known_hosts:??? Are you sure you want to continue connecting (yes/no)? yes Based on a patch by Carlos Garcia Campos. https://bugzilla.gnome.org/show_bug.cgi?id=545445
* Post branch version bumpRoss Lagerwall2015-04-061-1/+1
|
* programs: Fix a couple of warningsRoss Lagerwall2015-04-052-1/+18
| | | | | | | | | | | | | | | gvfs-monitor-file.c: In function ‘file_monitor_callback’: gvfs-monitor-file.c:63:3: warning: enumeration value ‘G_FILE_MONITOR_EVENT_RENAMED’ not handled in switch [-Wswitch] switch (eflags) ^ gvfs-monitor-file.c:63:3: warning: enumeration value ‘G_FILE_MONITOR_EVENT_MOVED_IN’ not handled in switch [-Wswitch] gvfs-monitor-file.c:63:3: warning: enumeration value ‘G_FILE_MONITOR_EVENT_MOVED_OUT’ not handled in switch [-Wswitch] gvfs-monitor-dir.c: In function ‘dir_monitor_callback’: gvfs-monitor-dir.c:65:3: warning: enumeration value ‘G_FILE_MONITOR_EVENT_RENAMED’ not handled in switch [-Wswitch] switch (eflags) ^ gvfs-monitor-dir.c:65:3: warning: enumeration value ‘G_FILE_MONITOR_EVENT_MOVED_IN’ not handled in switch [-Wswitch] gvfs-monitor-dir.c:65:3: warning: enumeration value ‘G_FILE_MONITOR_EVENT_MOVED_OUT’ not handled in switch [-Wswitch]
* Updated Latvian translationRūdolfs Mazurs2015-04-031-639/+490
|
* hal: Fix a memory leak in hal-volume-monitor.David Liang2015-04-021-0/+1
| | | | https://bugzilla.gnome.org/show_bug.cgi?id=747221
* Fix build error when using HAL backendTing-Wei Lan2015-04-028-7/+22
| | | | | | gvfsdbusutils.[ch] are renamed to gvfshalutils.[ch] to prevent confusion. https://bugzilla.gnome.org/show_bug.cgi?id=722411
* Updated Russian translationStas Solovey2015-03-301-168/+142
|
* Update Czech translationPetr Kovar2015-03-251-30/+25
|
* Post release version bumpOndrej Holy2015-03-231-1/+1
|
* Update NEWS for 1.24.0 release1.24.0Ondrej Holy2015-03-231-0/+5
|
* Updated Danish translationAsk H. Larsen2015-03-211-443/+502
|
* Updated Basque languageInaki Larranaga Murgoitio2015-03-211-327/+359
|
* Updated Brazilian Portuguese translationEnrico Nicoletto2015-03-211-156/+147
|
* Updated Indonesian translationAndika Triwidada2015-03-211-447/+491
|
* Updated Norwegian bokmål translation.Kjartan Maraas2015-03-191-167/+144
|
* proxy volume monitor: Drop init warningOndrej Holy2015-03-191-1/+1
| | | | | | | | | | This caused make to fail e.g. in libgweather: (g-ir-compiler:11785): GVFS-RemoteVolumeMonitor-WARNING **: Error: The connection is closed kernel: traps: g-ir-compiler[4216] trap int3 ip:7f76f9fa2663 sp:7fff1e6a2d90 error:0 With gvfs-1.22.3 no error's https://bugzilla.gnome.org/show_bug.cgi?id=746398
* Updated Chinese (Taiwan) translationChao-Hsiung Liao2015-03-181-166/+153
|
* Updated Galician translationsFran Dieguez2015-03-181-168/+157
|
* Updated Hebrew translationYosef Or Boczko2015-03-171-166/+153
|
* Updated Spanish translationDaniel Mustieles2015-03-161-197/+180
|
* Post release version bumpRoss Lagerwall2015-03-161-1/+1
|
* Update NEWS and version for 1.23.92 release1.23.92Ross Lagerwall2015-03-162-1/+14
|
* completion: Fix parallel installationRoss Lagerwall2015-03-161-1/+1
| | | | | | | Use install-data-hook rather than install-data-local as install-data-hook runs after the other install rules have run. This is important for a parallel install so that the destination directory already exists when the symlinks are created.
* Updated French translationAlexandre Franke2015-03-151-168/+156
|
* Updated Slovenian translationMatej Urbančič2015-03-151-441/+447
|
* Updated Swedish translationJosef Andersson2015-03-151-221/+231
|
* Updated Slovenian translationMatej Urbančič2015-03-151-451/+432
|
* Updated Hungarian translationBalázs Úr2015-03-141-171/+154
|
* Updated Lithuanian translationAurimas Černius2015-03-141-177/+153
|
* dnssd: Run GSimpleAsyncResult completion in idleRoss Lagerwall2015-03-141-4/+4
| | | | | | | | | | | | g_simple_async_result_complete should only be used from the thread on which the callback should be invoked. Also, the gvfs job threads do not have their own GMainContexts which causes an assertion failure [1] when invoking g_simple_async_result_complete. Instead, use g_simple_async_result_complete_in_idle(). [1] (process:11772): GLib-CRITICAL **: g_main_context_push_thread_default: assertion 'acquired_context' failed https://bugzilla.gnome.org/show_bug.cgi?id=629345
* dnssd: Remove recursive main loopRoss Lagerwall2015-03-141-15/+16
| | | | | | | Don't run a recursive main loop on a separate thread with a shared GMainContext. https://bugzilla.gnome.org/show_bug.cgi?id=629345
* dnssd: Prevent crash when resolving serviceRoss Lagerwall2015-03-141-39/+19
| | | | | | | | | | | | | | | AvahiClient appears to require that avahi_service_resolver_new is invoked from the same thread to which its poll function is bound otherwise it can crash with a callback running while avahi_service_resolver_new is still busy. To fix this, always run avahi_service_resolver_new from the main loop. To simplify the code, any errors from the function are ignored for now. This crash could be reproduced 100% of the time by trying to mount dav+sd (via gnome-user-share) in a single-CPU VM. https://bugzilla.gnome.org/show_bug.cgi?id=629345
* Translation pa updated for GnomeA S Alam2015-03-131-438/+503
|
* Updated Korean translationChangwoo Ryu2015-03-141-100/+108
|
* Added Bosnian translationSamir Ribic2015-03-132-0/+3148
|
* Updated Serbian translationМирослав Николић2015-03-132-844/+964
|
* Updated Italian translationMilo Casagrande2015-03-131-279/+374
|
* Updated Greek translationTom Tryfonidis2015-03-121-159/+148
|
* Updated Polish translationPiotr Drąg2015-03-121-99/+103
|
* Updated Czech translationMarek Černocký2015-03-121-316/+357
|
* Updated Slovak translationDušan Kazik2015-03-121-134/+132
|
* Updated Vietnamese translationTrần Ngọc Quân2015-03-121-318/+352
| | | | Signed-off-by: Trần Ngọc Quân <vnwildman@gmail.com>
* ftp: Prevent segfault when unmountingRoss Lagerwall2015-03-111-0/+4
| | | | | | | | | | | If a job is waiting for a connection in g_vfs_ftp_task_acquire_connection and the backend is force unmounted, the queue is freed, and the function neither gets a connection nor sets an error message which causes an issue later. To fix this, set an error message if the queue is freed. https://bugzilla.gnome.org/show_bug.cgi?id=653042
* common: Increase mount timeout to 30 minutesRoss Lagerwall2015-03-113-7/+9
| | | | | | | | | Although it is probably unnecessary, wait up to 30 minutes for a mount to complete. This allows plenty of time to wait for a password dialog. It also makes it more consistent with many of the other operations which use a timeout of 30 minutes. https://bugzilla.gnome.org/show_bug.cgi?id=594500
* metadata: don't crash if tree write out failedOndrej Holy2015-03-111-3/+43
| | | | | | | | meta_tree_init can fail after we failed to write out an updated tree. Backup corrupted file and start with empty tree to avoid consequent crashes. https://bugzilla.gnome.org/show_bug.cgi?id=598561
* gphoto2: Exit cleanly when device is removedBastien Nocera2015-03-101-4/+2
| | | | | | As the other backends do, and removes 2 FIXMEs. https://bugzilla.gnome.org/show_bug.cgi?id=708316
* afc: Fix force unmount of devicesChristophe Fergeau2015-03-091-7/+17
| | | | | | | | | | | | | | | | | | | | | When unplugging an afc device without unmounting it first, the corresponding gvfsd-afc process does not go away in spite of the exit(1) workaround added for bgo#708288. This happens because idevice_event_unsubscribe() in called from the thread where the _idevice_event_cb() runs in. libimobiledevice (through libusbmuxd) creates a thread to watch for device events, and calls the idevice_event_cb_t from that thread. idevice_event_unsubscribe() then forcfully kills that thread (see usbmuxd_unsubscribe() in libusbmuxd), so exit(1) code after the call to idevice_event_unsubscribe() never gets a chance to run. Moving the call to idevice_event_unsubscribe() and the g_vfs_backend_force_unmount() call to run in the main loop through g_idle_add() avoids this issue, and allows the code handling force unmounts to run as expected. Fixes: https://bugzilla.gnome.org/show_bug.cgi?id=708288
* man: add missing deamonsOndrej Holy2015-03-091-1/+4
| | | | https://bugzilla.gnome.org/show_bug.cgi?id=745731
* metatree: always clear fd to -1Ondrej Holy2015-03-091-1/+1
| | | | | | | meta_tree_clear clears fd to 0 currently, however it should be set to -1 to avoid risk that fd 0 is closed, when meta_tree_clear is called twice. https://bugzilla.gnome.org/show_bug.cgi?id=598561
* Updated Italian translationMilo Casagrande2015-03-081-601/+545
|
View Lorry Controller Status