summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* Fix indentation mishapportalMatthias Clasen2016-07-061-5/+5
|
* Remove an extraneous castsMatthias Clasen2016-07-061-2/+2
| | | | Spotted by Cosimo.
* Be more truthful about network availabilityMatthias Clasen2016-07-061-0/+2
| | | | | If flatpak-info exists, but we don't have the shared key, then the network is not available. Pointed out by Cosimo.
* Use g_build_filenameMatthias Clasen2016-07-061-3/+2
| | | | Instead of manual path construction. Pointed out by Cosimo.
* Remove debug spewMatthias Clasen2016-07-061-1/+0
| | | | Spotted by Cosimo.
* Avoid an extraneous castMatthias Clasen2016-07-061-1/+1
| | | | Cosimo pointed out that this is unnecessary.
* Set an error on failureMatthias Clasen2016-07-061-0/+4
| | | | | 'has no owner' seems close enough, that is what we are seeing here.
* network monitor portal: Fix indentationMatthias Clasen2016-07-061-6/+6
| | | | Pointed out by Cosimo Cecchi.
* Avoid a use-after-freeMatthias Clasen2016-07-061-11/+6
| | | | | | | | | Instead of pulling parent_window out of a copy of the environment and having it go bad when we free the copy, move the definition of GAppLaunchContextPrivate up and use the envp member without copying in. Pointed out by Cosimo Cecchi.
* Avoid type name clashMatthias Clasen2016-07-043-29/+29
| | | | | | GIO should not install types whose names don't start with 'g'. This was causing the xdg-desktop-portal to crash, since it was also trying to register Xdp types.
* Add a portal backend for GNotificationMatthias Clasen2016-07-033-0/+101
| | | | This will talk to a portal api instead of directly to the shell.
* portal support: Flush the connectionMatthias Clasen2016-07-031-6/+7
| | | | | As Mario pointed out, this is common practice for uses of the bus singleton inside GIO.
* portal support: Don't wait for the replyMatthias Clasen2016-07-031-16/+16
| | | | | | | It does not really make sense for g_app_info_launch_default_for_uri to block on an interactive dialog. If we want that, we can should introduce a proper async variant of this API with a cancellable and a finish().
* portal support: handle errorsMatthias Clasen2016-07-031-1/+3
| | | | | Return an error when we don't have a session bus connection. Pointed out by Cosimo and Mario.
* portal support: Use g_get_user_runtime_dir()Matthias Clasen2016-07-031-2/+2
| | | | Pointed out by Cosimo Cecchi and Mario Sanchez Prada.
* proxy: Redo the network availability checkMatthias Clasen2016-07-031-3/+18
| | | | | | | Do this more like for the network monitor: We keep using the portal proxy, but we neuter all results. Eventually, we can do this on the portal side, but we need some systemd infrastructure for it.
* Avoid a criticalMatthias Clasen2016-07-031-2/+5
| | | | The key might not be present in flatpak-info. Deal with that.
* Add a portalized proxy resolver implementationMatthias Clasen2016-07-035-4/+240
| | | | | The backend for this lives in xdg-desktop-portal, and is in turn using GProxyResolver.
* Move some portal support to its own filesMatthias Clasen2016-07-035-63/+106
| | | | | This is better than copying these utility functions around to multiple places.
* network monitor portal: Respect sandbox setupMatthias Clasen2016-07-031-7/+36
| | | | | | | When network is not available in the sandbox, there is no point in reporting accurately about the network status outside the sandbox. Just return 'no connection' in this case.
* Add a portalized network monitor implementationMatthias Clasen2016-07-035-0/+300
| | | | | The backend for this lives in xdg-desktop-portal, and is in turn using GNetworkMonitor.
* Use the new portal nameMatthias Clasen2016-07-031-1/+1
| | | | The portal got renamed to org.freedesktop.portal.OpenURI.
* Revert "Add portal support to g_app_info_launch_uris"Matthias Clasen2016-07-031-49/+0
| | | | This reverts commit c980bd2bc416f6762c49497ddc042cea11a30bf2.
* Revert "Take the parent window id from the environment"Matthias Clasen2016-07-031-10/+3
| | | | This reverts commit 4b44094309efe9a86bc0f3e6e687059ee55a90ab.
* Add portal support to g_app_info_launch_default_for_uriMatthias Clasen2016-07-031-0/+69
| | | | | | | We need to patch in the portal support at a high enough level that GAppInfo is not involved - a sandboxed app may not be able to see any applications, so it can just launch the defaults.
* Take the parent window id from the environmentMatthias Clasen2016-07-031-3/+10
| | | | GTK+ will set this for when showing URIs in a sandbox.
* Add portal support to g_app_info_launch_urisMatthias Clasen2016-07-031-0/+49
| | | | Call out to the org.freedesktop.portal.AppChooser portal.
* Document the gio toolMatthias Clasen2016-07-013-8/+731
| | | | Add a man page, and integrate it in the reference docs.
* Add new files to POTFILESMatthias Clasen2016-07-011-0/+17
|
* Add a new gio commandline toolMatthias Clasen2016-07-0119-0/+4368
| | | | | | | | This command collects the various commandline utilities that are currently shipped in gvfs, and unifies them under a single, command-style binary. The tools just use GIO APIs, so it makes sense for them to live here.
* Trivial: documentation wording fixMatthias Clasen2016-06-301-1/+1
| | | | There was a stray 'of' here.
* gmessages: Simplify _g_log_abort() in gmessages.c a littlePhilip Withnall2016-06-291-4/+12
| | | | https://bugzilla.gnome.org/show_bug.cgi?id=744456
* gio: Add source tags to various GTasks constructed in GLibPhilip Withnall2016-06-2945-2/+103
| | | | | | | | This makes them easier to identify when debugging and profiling. This patch was somewhat less than interesting to write. https://bugzilla.gnome.org/show_bug.cgi?id=767765
* gmain: Add G_PID_FORMATPhilip Withnall2016-06-294-0/+17
| | | | | | This will be useful for printing out GPids in printf()-style functions. https://bugzilla.gnome.org/show_bug.cgi?id=767765
* build: Simplify dtrace configurationPhilip Withnall2016-06-291-4/+1
| | | | | | | Apply the same changes as in commit 7563ab473468fecefc388ae2ed06afab8ead6211 to gio/Makefile.am. https://bugzilla.gnome.org/show_bug.cgi?id=725902
* build: Rename SystemTap scripts to include the LT versionPhilip Withnall2016-06-294-20/+17
| | | | | | | | | | | | | | | | | | | In a vague attempt at ensuring the .stp scripts can be closely associated with the .so files which they hard-code references to, rename the scripts so they include the LT version — so that they are the .so file name plus .stp. This does not fix the fact that our .stp scripts will not work on multiarch systems, as they are installed in an architecture-independent directory (/usr/share/systemtap/tapset). At the moment, it is recommended that any distribution who package the .stp files should install them in the architecture-specific subdirectories of this (for example, /usr/share/systemtap/tapset/x86-64). A better long-term solution for this is under discussion upstream: https://sourceware.org/bugzilla/show_bug.cgi?id=20264 https://bugzilla.gnome.org/show_bug.cgi?id=662802
* build: Ensure gio.stp.in is always distributedPhilip Withnall2016-06-291-2/+3
| | | | | | Even if systemtap is not enabled in configure when running distcheck. https://bugzilla.gnome.org/show_bug.cgi?id=662802
* vfs: Fix copying default schemes listFlorian Müllner2016-06-281-3/+2
| | | | | | | | The list of supported schemes is not known at compile-time, so it is wrong to iterate the list with G_N_ELEMENTS() and we miss all but the first scheme. Fix by checking for the %NULL sentinel instead. https://bugzilla.gnome.org/show_bug.cgi?id=768119
* vfs: Fix return value of get_supported_uri_schemes()Florian Müllner2016-06-282-0/+5
| | | | | | | | The function is expected to return a %NULL-terminated array, but commit 375b4ca65c dropped the sentinel when adding support for additional custom schemes. Add it back. https://bugzilla.gnome.org/show_bug.cgi?id=768119
* fileinfo: Add G_FILE_ATTRIBUTE_FILESYSTEM_REMOTE attributeOndrej Holy2016-06-284-1/+16
| | | | | | | | | Add filesystem attribute to detect remote filesystems in order to replace hardcoded filesystem types in GtkFileSystem. Set this attribute also for GLocalFile appropriately. Bump version to 2.49.3, so that early adopters of new API have a version number to target.
* gvfs: fix possible infinite loop in parse_name_internal()Ernestas Kulik2016-06-251-4/+3
| | | | | | | | | | | If none of the closures in the hash table return a non-null value, the loop never ends. Since the end of the hash table has been reached at that point, g_hash_table_iter_next() starts asserting. The possible fix is making the return value of g_hash_table_iter_next() the condition in the loop. https://bugzilla.gnome.org/show_bug.cgi?id=768029
* vfs: add g_vfs_register_uri_scheme()Cosimo Cecchi2016-06-254-13/+403
| | | | | | | | | | | | | | Add a new API to allow clients to register a custom GFile implementation handling a particular URI scheme. This can be useful for tests, but also for cases where a different URI scheme is desired to be used with another custom GFile backend. As an additional cleanup, we can use this to register the "resource" URI scheme too. Based on a patch by Jasper St. Pierre <jstpierre@mecheye.net>. https://bugzilla.gnome.org/show_bug.cgi?id=767887
* Updated Indonesian translationAndika Triwidada2016-06-241-286/+313
| | | | (cherry picked from commit 7cb5b02e6ab662e6cb384a3d68acdd81a3c15515)
* tests: fix uint64 argument to g_object_set() callAllison Lortie2016-06-231-1/+1
| | | | | | | | | | | 5cea1c861def0251a10cd4de01908aaf3276c72d introduced accessors for 64bit ints to gsettings, at which point the testcases were expanded. Unfortunately, the expanded tests contained a bug: integer constants passed to g_object_set() for a 64-bit property need an up-cast. Add that now. Problem found by Iain Lane.
* build: Add gio_probes.d to sources list so it ends up in the tarballPhilip Withnall2016-06-221-0/+1
| | | | | | The probes.d file should be distributed even if GLib is build with dtrace disabled. This is what’s done in the glib and gobject directories.
* gkeyfile: add g_key_file_load_from_bytes() APICosimo Cecchi2016-06-204-0/+74
| | | | | | | | This makes it easier to use GKeyFile from language bindings, and makes the API more consistent and modern with the new data type available in GLib. https://bugzilla.gnome.org/show_bug.cgi?id=767880
* build: simplify dtrace configurationRyan Lortie2016-06-202-7/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | The ability to pass libtool via $(CC) to dtrace and have it respect this appears to be a feature that is only present in the systemtap version of the tool. In particular, FreeBSD (which seems to be using a copy of the tool from Solaris) doesn't support this. The result is that, with $(CC) ignored, and a .lo file specified in -o, we get an ELF written to the .lo. Instead of trying to have dtrace run libtool we can have libtool run dtrace. dtrace is really just a compiler that produces an object file here, and it even understands -o, so libtool can make the appropriate adjustments. There appears to be some prior art for this approach. A quick search shows that at least QEMU is using this approach. It also appears to work on Linux with systemtap's dtrace and on FreeBSD. This may regress cross-compilation because the dtrace command will have no way of knowing which compiler we intend for it to use to produce the object file. I say "may" because I don't know if dtrace ever worked in the first place under cross-compilation. https://bugzilla.gnome.org/show_bug.cgi?id=725902
* 2.49.22.49.2Matthias Clasen2016-06-201-1/+1
|
* UpdatesMatthias Clasen2016-06-201-0/+21
|
* Visual Studio builds: Fix .pc generationChun-wei Fan2016-06-201-8/+5
| | | | | The previous update did not account for when no exec_prefix is spcified, so update that, and use ${prefix} by default. Clean up a bit as well.
View Lorry Controller Status