commit | 0a0ac9f050819ce50b8457113756e7b5b86fc534 | [log] [tgz] |
---|---|---|
author | Benjamin Berg <bberg@redhat.com> | Mon Jul 27 22:22:32 2020 +0200 |
committer | Benjamin Berg <bberg@redhat.com> | Tue Mar 22 11:36:57 2022 +0100 |
tree | e2bd0a13af24415516c84bd7315fa644202b71f1 | |
parent | cade87b9fd03a2d3e234c55a413476a49a7edbe4 [diff] |
gdesktopappinfo: Move launched applications into transient scope Try to move the spawned executable into its own systemd scope. To avoid possible race conditions and ensure proper accounting, we delay the execution of the real command until after the DBus call to systemd has finished. From the two approaches we can take here, this is better in the sense that we have a child that the API consumer can watch. API consumers should not be doing this, however, gnome-session needs to watch children during session startup. Until gnome-session is fixed, we will not be able to change this. The alternative approach is to delegate launching itself to systemd by creating a transient .service unit instead. This is cleaner and has e.g. the advantage that systemd will take care of log redirection and similar issues.
GLib is the low-level core library that forms the basis for projects such as GTK and GNOME. It provides data structure handling for C, portability wrappers, and interfaces for such runtime functionality as an event loop, threads, dynamic loading, and an object system.
The official download locations are: https://download.gnome.org/sources/glib
The official web site is: https://www.gtk.org/
See the file ‘INSTALL.in’
Only the most recent unstable and stable release series are supported. All older versions are not supported upstream and may contain bugs, some of which may be exploitable security vulnerabilities.
See SECURITY.md for more details.
API documentation is available online for GLib for the:
If you have a question about how to use GLib, seek help on GNOME’s Discourse instance. Alternatively, ask a question on StackOverflow and tag it glib
.
Bugs should be reported to the GNOME issue tracking system. You will need to create an account for yourself. You may also submit bugs by e-mail (without an account) by e-mailing incoming+gnome-glib-658-issue-@gitlab.gnome.org, but this will give you a degraded experience.
Bugs are for reporting problems in GLib itself, not for asking questions about how to use it. To ask questions, use one of our discussion forums.
In bug reports please include:
tests/
subdirectory, that will be most convenient. Otherwise, please include a short test program that exhibits the behavior. As a last resort, you can also provide a pointer to a larger piece of software that can be downloaded.Please follow the contribution guide to know how to start contributing to GLib.
Patches should be submitted as merge requests to gitlab.gnome.org. If the patch fixes an existing issue, please refer to the issue in your commit message with the following notation (for issue 123):
Closes: #123
Otherwise, create a new merge request that introduces the change. Filing a separate issue is not required.
main
The default development branch of GLib has been renamed to main
. To update your local checkout, use:
git checkout master git branch -m master main git fetch git branch --unset-upstream git branch -u origin/main git symbolic-ref refs/remotes/origin/HEAD refs/remotes/origin/main