New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
setenv()/putenv() are not thread-safe #432
Comments
Thanks for the feedback. I do believe that it does not really hurt. I mean: it was already the case for a long time, the upstream projects decided to display a warning since the newer version, this is a very good piece of information :-) At this stage, I'm not yet sure if this is something needs to be fixed in Ásbrú or in Gtk / Gtk-perl or Glib-introspection or maybe somewhere else ! If somebody has a better understanding of these new warnings, please let use now. |
Hi to all.
It seems to work good anyway. Thanks to all. |
Is there any way to hide these warnings? |
Hiding the warnings/errors would also be acceptable for me. The errors and warnings just clutter up the terminal window. That is actually my complaint... |
Fyi, I created an issue to the upstream project (Gtk3-perl) : https://gitlab.gnome.org/GNOME/perl-gtk3/-/issues/7 |
Some notes while searching... Message has been added recently in glib --> https://gitlab.gnome.org/GNOME/glib/-/blob/master/NEWS#L114-115 Related merge request : https://gitlab.gnome.org/GNOME/glib/-/merge_requests/1337 A very minimal code to reproduce the error is:
Added line:
on line 67 of
So the message looks to be generated in to Gio application register. Code of Gio application register can be found here https://gitlab.gnome.org/GNOME/glib/-/blob/master/gio/gapplication.c#L2175-2214 I don't see any obvious reference to the environment there... A (hopefully) similar application in python does not generate the same kind of warning:
|
Tunneling issue with windows system asking password even password is saved already and if we enter the password again then it shows wrong password and try again option. This is with Focal Fosa Ubuntu 20.04 GLib-LOG **: setenv()/putenv() are not thread-safe and should not be used after threads are created at /usr/lib/x86_64-linux-gnu/perl5/5.30/Glib/Object/Introspection.pm line 67.
THIS IS A PRIVATE COMPUTER SYSTEM. This is an official computer system and the property of One97 Communications Ltd. and It is for authorized users only. Unauthorized users are prohibited. Users (authorized or unauthorized) have no explicit or implicit expectation of privacy. Any or all uses of this system may be subject to one or more of the following actions: interception, monitoring, auditing, inspection and disclosing to security personnel and law enforcement personnel, as well as authorized officials of other agencies, both domestic and foreign. By using this system, the user consents to these actions. Unauthorized or improper use of this system may result in administrative disciplinary action and civil and criminal penalties. By accessing this system you indicate your awareness of and consent to these terms and conditions of use. Discontinue access immediately if you do not agree to the conditions stated in this notice. Permission denied, please try again. |
@master-vineet please avoid posting the same issue everywhere and stay on topic. Your issue does not seem related to setenv/putenv. As already suggest, please check your password prompt in advanced settings or create a dedicated issue. |
Good news : it looks like the root issue has been identified ! The guilty one is perl-glib that is reporting a debug message, even if the appropriate debug flag is not set. And a patch is now available, see https://gitlab.gnome.org/GNOME/perl-glib/-/merge_requests/5 Is there anyone to check if it works ? |
Confirmed bug/issue on Fedora 32 |
Thanks for the fix. It is really confusing when I first saw these warnings. |
Yes confusing and very annoying ; we'll need to wait for the next release of the upstream In the meantime, you can use a locally compiled version of that package by doing something like:
and then you can run Ásbrú with that local library with something like:
|
Fyi, a new step has been made in the right direction, see https://mail.gnome.org/archives/gtk-perl-list/2020-June/msg00002.html where you'll read the announcement of the new perl-glib package (version 1.3293) that includes the necessary fix. Next step is to have to included in the various distributions ; please contact the packagers if needed... |
Fixed in Archlinux with glib-perl 1.3293. Hope it will be soon in official repos. |
I confirm, that updating to glib-perl 1.3293, it is resolved. |
If you do not want to wait for an official release guess will work for similar debian distributions, tested on Linux Mint 20
|
@hanspr
Now everything is fine 👍 |
To summarize: the fix is available in glib-perl 1.3293, distribution has to integrate it or you have to install it manually (see instructions above). We can close this issue in Ásbrú. |
If |
Describe the bug
When starting a connection, give the following warning
GLib-LOG **: setenv()/putenv() are not thread-safe and should not be used after threads are created at /usr/lib/perl5/5.30/vendor_perl/Glib/Object/Introspection.pm line 67. GLib-LOG **: setenv()/putenv() are not thread-safe and should not be used after threads are created at /usr/lib/perl5/5.30/vendor_perl/Glib/Object/Introspection.pm line 67. GLib-LOG **: unsetenv() is not thread-safe and should not be used after threads are created at /usr/share/perl5/vendor_perl/Gtk3.pm line 555.
Desktop (please complete the following information):
The text was updated successfully, but these errors were encountered: