summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* gdbus: Use a static lock for metadata proxy instead of GPrivategdbusTomas Bzatek2012-06-043-79/+51
| | | | | Using GPrivate turned to be problematic wrt thread safety, better to use the standard way of locks.
* gdbus: Flush the async metadata callsTomas Bzatek2012-05-301-0/+6
| | | | | | | | | Otherwise it would not be guaranteed that the messages got actually sent if a program exits afterwards. Synchronously flushing queued messages on a shared GDBusConnection is quite risky as the queue could be rather long and we would block, however the affected calls are not that common in normal use.
* gdbus: Remove callbacks for calls where we don't care about the resultTomas Bzatek2012-05-231-18/+2
| | | | | | Found by reading GDBus sources, things are easier when not specifying a callback, e.g. g_dbus_connection_call() would set the G_DBUS_MESSAGE_FLAGS_NO_REPLY_EXPECTED flag on the outgoing message.
* gdbus: Remove shared volume monitor proxy lockingTomas Bzatek2012-05-215-28/+0
| | | | | | | | | Since it didn't work and GVolumeMonitor implementations should not be used from threads: "GVolumeMonitor is not thread-default-context aware, and so should not be used other than from the main thread, with no thread-default-context active."
* gdbus: Remove locks from volume monitor daemonsTomas Bzatek2012-05-211-37/+1
| | | | | The originally planned invocation in threads got never realized, we're sufficiently async anyway.
* gdbus: Don't wait for metadata daemon reply on file_moved/removedTomas Bzatek2012-05-211-11/+31
| | | | | We don't need the result, let's make these calls async and retain the old behaviour.
* gdbus: Watch for metadata daemon going awayTomas Bzatek2012-05-212-0/+52
| | | | ...to reflect actual state of the shared proxy
* gdbus: Use shared metadata proxy for every threadTomas Bzatek2012-05-212-31/+47
| | | | | | This helps to avoid constant metadata proxy creation for every call. Instead, create it on first use and store it as thread-local data. It gets unreff'ed on thread end automatically.
* gdbus: Remove dead codeTomas Bzatek2012-05-211-10/+0
|
* gdbus: Use g_dbus_connection_set_exit_on_close() where applicableTomas Bzatek2012-05-211-1/+1
|
* gdbus: Reuse connection from an interface skeletonTomas Bzatek2012-05-211-57/+11
| | | | And minimize roundtrips to the session d-bus daemon.
* gdbus: Remove some extra debug spewTomas Bzatek2012-05-212-7/+1
| | | | | Not needed really, leaving DEBUG_ENABLED define enabled for now, will remove more debug prints later.
* gdbus: Rename append_ functionsTomas Bzatek2012-05-211-20/+20
| | | | Since they're misleading now with GDBus
* gdbus: Use proper data type size and castingTomas Bzatek2012-05-211-4/+4
|
* gdbus: Only watch for name owner when monitor != NULLTomas Bzatek2012-05-211-4/+7
|
* gdbus: Fix up code style of d-bus interfacesTomas Bzatek2012-05-214-299/+309
| | | | | Bunch of cosmetic code-style changes, making our d-bus interface conform to generally accepted rules.
* gdbus: Make sure to build autogenerated sources firstTomas Bzatek2012-05-212-0/+4
| | | | | | This would hopefully make autotools to compile generated sources in the first place so others would be able to include them. Found by accident and haven't been able to reproduce since.
* gdbus: Publish metadata d-bus interface instrospection fileTomas Bzatek2012-05-212-0/+58
| | | | And ignore autogenerated related source files.
* gdbus: Port metadataTomas Bzatek2012-05-216-677/+458
| | | | | | | | | Some TODOs: * print better error messages when we can't own the dbus name * remove dbus.h includes and CFLAGS once gvfsdaemonprotocol.h is ported * "Get" method call unused?
* gdbus: Don't generate object manager, it's unusedTomas Bzatek2012-05-211-1/+0
|
* gdbus: Silence on_name_owner_appeared messagesTomas Bzatek2012-05-211-1/+4
| | | | | | | ... and don't scare users with correct informational messages. One of owner_appeared of owner_vanished callbacks are guaranteed to be called after name owner watching is set up and on normally functional system the former is usually called.
* gdbus: Don't warn if MountOp could not be foundTomas Bzatek2012-05-211-31/+20
| | | | | | | | | | | This typically happens when dbus eavesdrop is turned on and we receive signals that don't belong to us. So simply silence all warnings and ignore these events. See https://bugs.freedesktop.org/show_bug.cgi?id=37890 Also, the hash table might not have been initialized yet, added few tests.
* gdbus: Restore method call timeoutsTomas Bzatek2012-05-215-2/+49
| | | | | | | | Use G_PROXY_VOLUME_MONITOR_DBUS_TIMEOUT (30 minutes) timeout where applicable to match pre-gdbus volume monitor behavior. Note that I chose to wrap locking in convenient functions to avoid having the lock definition in a header file.
* gdbus: Clean autogenerated files on `make clean`Tomas Bzatek2012-05-211-0/+4
|
* gdbus: Don't handle method invocations in threadsTomas Bzatek2012-05-211-3/+0
| | | | | | Per discussion with David it was suggested this is not so good idea as long as most volume monitor operations are called async anyway and we would have to hassle with GMainContext.
* gdbus: Strip unmapped GError quark stringsTomas Bzatek2012-05-213-48/+78
| | | | | | | | Typically happens when receiving side is not aware of extra GError domains registered on sending (server) side, such as GDU_ERROR. While the receiving side will get different error (G_IO_ERROR_DBUS_ERROR) it's not usually a problem as long as the error message is preserved.
* gdbus: Port GIO side of proxy volume monitorTomas Bzatek2012-05-2114-1108/+1076
| | | | | | | | | Few leftovers: * Nuke the complicated is_supported machinery if possible * Tweak timeouts for some operations * Fix occasional GMountOperation lookup failures
* gdbus: Suppose that g_bus_watch_name() never returns zeroTomas Bzatek2012-05-211-2/+2
| | | | | g_bus_watch_name() never returns zero so we can use it to distinguish if watching has been started or not.
* gdbus: Use g_dbus_connection_emit_signal() for emitting signals to a ↵Tomas Bzatek2012-05-211-27/+156
| | | | specific owner
* gdbus: Turn MountOp volume monitor methods on client side into signalsTomas Bzatek2012-05-213-149/+70
| | | | | | | | There's no strong reason for having those as methods apart from precise message targetting (TODO). This step will also significantly ease porting of client side volume monitor. This is a gvfs d-bus api break however.
* gdbus: Add locking for local listsTomas Bzatek2012-05-211-1/+35
|
* gdbus: Port GVfs side of proxy volume monitorTomas Bzatek2012-05-213-883/+641
| | | | | | | | | Still few things to do: * wrong error passing (G_IO_ERROR_FAILED_HANDLED getting ignored) * add proper locking, review existing code to be thread-safe * enabled debug prints by default for the moment
* gdbus: Add remote volume monitor dbus interface fileTomas Bzatek2012-05-213-1/+197
|
* Updated Galician translationsFran Diéguez2012-05-201-33/+46
|
* Updated Spanish translationDaniel Mustieles2012-05-161-37/+48
|
* udisks2: Show "Eject Anyway" (not "Unmount Anyway") if ejectingDavid Zeuthen2012-05-152-1/+19
| | | | | | ... instead of unmounting. Signed-off-by: David Zeuthen <davidz@redhat.com>
* udisks2: set can_eject correctlyDavid Zeuthen2012-05-151-2/+1
| | | | | Yes, can_eject can be TRUE even if the media is not removable. Signed-off-by: David Zeuthen <davidz@redhat.com>
* gvfs-mount: add new -e option to eject a mountDavid Zeuthen2012-05-151-0/+49
| | | | | | Like the rest of gvfs-mount(1), this is mostly useful for debugging. Signed-off-by: David Zeuthen <davidz@redhat.com>
* udisks2: set timeout to INTMAX when unmounting a filesystemDavid Zeuthen2012-05-141-0/+1
| | | | | | | It may indeed take more than 25 seconds if there's a lot of data to write. Related to https://bugzilla.redhat.com/show_bug.cgi?id=819492 Signed-off-by: David Zeuthen <davidz@redhat.com>
* udisks2: also check for umount(8) saying "target is busy"David Zeuthen2012-05-081-1/+3
| | | | | | Same as http://cgit.freedesktop.org/udisks/commit/?id=d8fa361eec2706091e9d7f166f63bb5c0f663f4b Signed-off-by: David Zeuthen <davidz@redhat.com>
* udisks2: don't call g_simple_async_result_take_error() twiceDavid Zeuthen2012-05-081-1/+0
| | | | Signed-off-by: David Zeuthen <davidz@redhat.com>
* udisks2: don't show loop devices set up by other usersDavid Zeuthen2012-05-031-1/+18
| | | | Signed-off-by: David Zeuthen <davidz@redhat.com>
* udisks2: Remove support for ID_SEAT=allDavid Zeuthen2012-04-305-21/+5
| | | | | | | We might bring this back in one shape or the other, but remove it for now until I get a chance to talk to Kay and Lennart some more. Signed-off-by: David Zeuthen <davidz@redhat.com>
* Post release version bumpTomas Bzatek2012-04-301-1/+1
|
* Update NEWS for 1.13.0 release1.13.0Tomas Bzatek2012-04-301-0/+13
|
* build: Bail if gphoto support is requested but not availableArun Raghavan2012-04-301-3/+10
| | | | https://bugzilla.gnome.org/show_bug.cgi?id=578027
* afp: Use g_clear_object properlyMatthias Clasen2012-04-301-2/+2
| | | | | g_clear_object expects the address of a pointer. A recent change in its definition makes gcc complain about this.
* Updated Norwegian bokmål translationKjartan Maraas2012-04-301-95/+131
|
* Updated Galician translationsFran Diéguez2012-04-271-98/+135
|
* Updated Spanish translationDaniel Mustieles2012-04-271-2918/+2959
|
View Lorry Controller Status