After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 724070 - Should not use g_setenv
Should not use g_setenv
Status: RESOLVED OBSOLETE
Product: at-spi
Classification: Platform
Component: at-spi2-core
unspecified
Other Linux
: Normal normal
: ---
Assigned To: At-spi maintainer(s)
At-spi maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2014-02-10 21:04 UTC by Colin Walters
Modified: 2021-07-05 10:45 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Colin Walters 2014-02-10 21:04:08 UTC
https://git.gnome.org/browse/at-spi2-core/commit/?id=72b5b573

Is really quite evil (as you mention in the FIXME), but it has a real concrete problem: setenv() is racy if threads exist.

See the chain of bugs:
https://bugs.freedesktop.org/show_bug.cgi?id=65681
Comment 1 Matthias Clasen 2014-02-10 21:09:40 UTC
You should be able to use e.g. g_dbus_connection_new_for_address to test a bus connection without setting an environment variable.
Comment 2 GNOME Infrastructure Team 2021-07-05 10:45:07 UTC
GNOME is going to shut down bugzilla.gnome.org in favor of gitlab.gnome.org.
As part of that, we are mass-closing older open tickets in bugzilla.gnome.org
which have not seen updates for a longer time (resources are unfortunately
quite limited so not every ticket can get handled).

If you can still reproduce the situation described in this ticket in a recent
and supported software version, then please follow
  https://wiki.gnome.org/GettingInTouch/BugReportingGuidelines
and create a new ticket at
  https://gitlab.gnome.org/GNOME/at-spi2-core/-/issues/

Thank you for your understanding and your help.