Mastodon

C++NowC++Now 2025 SESSION ANNOUNCEMENT: Using TLA+ to Fix a Very Difficult glibc Bug by Malte Skarupke<a href="https://schedule.cppnow.org/session/2025/using-tla-to-fix-a-very-difficult-glibc-bug/" target="_blank" rel="nofollow noopener" translate="no">https://schedule.cppnow.org/session/2025/using-tla-to-fix-a-very-difficult-glibc-bug/</a>Register now at <a href="https://cppnow.org/registration/" target="_blank" rel="nofollow noopener" translate="no">https://cppnow.org/registration/</a><a href="https://mastodon.social/tags/coding" class="mention hashtag" rel="tag">#coding</a> <a href="https://mastodon.social/tags/cplusplus" class="mention hashtag" rel="tag">#cplusplus</a> <a href="https://mastodon.social/tags/glibc" class="mention hashtag" rel="tag">#glibc</a> <a href="https://mastodon.social/tags/TLA" class="mention hashtag" rel="tag">#TLA</a>

BoudThe <a href="https://framapiaf.org/tags/Maneage" class="mention hashtag" rel="nofollow noopener" target="_blank">#Maneage</a> <a href="https://framapiaf.org/tags/reproducibility" class="mention hashtag" rel="nofollow noopener" target="_blank">#reproducibility</a> system for scientific research papers that starts from a minimal POSIX-like host OS does not yet build [1] the <a href="https://framapiaf.org/tags/GNUCLibrary" class="mention hashtag" rel="nofollow noopener" target="_blank">#GNUCLibrary</a> = <a href="https://framapiaf.org/tags/GLibC" class="mention hashtag" rel="nofollow noopener" target="_blank">#GLibC</a> . We have a draft implementation building glibc *after* <a href="https://framapiaf.org/tags/GCC" class="mention hashtag" rel="nofollow noopener" target="_blank">#GCC</a> [2]; and an alternative proposal arguing that building glibc *first* and gcc second would be more long-term sustainable [[1] comment18].Should GLibC be built first? Why (or why not)?[1] <a href="https://savannah.nongnu.org/task/?15390" rel="nofollow noopener" translate="no" target="_blank">https://savannah.nongnu.org/task/?15390</a> [2] <a href="https://gitlab.com/maneage/project-dev/-/blob/glibc/reproduce/software/make/core-gnu.mk#L718" rel="nofollow noopener" translate="no" target="_blank">https://gitlab.com/maneage/project-dev/-/blob/glibc/reproduce/software/make/core-gnu.mk#L718</a>

Kevin Karhan :verified:<a href="https://mstdn.jp/@landley" class="u-url mention" rel="nofollow noopener" target="_blank">@landley</a> <a href="https://todon.nl/@burnoutqueen" class="u-url mention" rel="nofollow noopener" target="_blank">@burnoutqueen</a> Yeah...<a href="https://infosec.space/tags/GPLv3" class="mention hashtag" rel="nofollow noopener" target="_blank">#GPLv3</a> is a desaster as it's 99% ideology and 1% license text and alongside <a href="https://infosec.space/tags/AGPLv3" class="mention hashtag" rel="nofollow noopener" target="_blank">#AGPLv3</a> completely ignores the reality of how <a href="https://infosec.space/tags/licensing" class="mention hashtag" rel="nofollow noopener" target="_blank">#licensing</a> and <a href="https://infosec.space/tags/patents" class="mention hashtag" rel="nofollow noopener" target="_blank">#patents</a> and <a href="https://infosec.space/tags/IP" class="mention hashtag" rel="nofollow noopener" target="_blank">#IP</a> works.<ul><li>Not that I like the status-quo, but we'd rather see businesses steer clear of anything GPLv2+ or GPLv3 or worse.</li></ul>And on the flipside we basically get "source available" stuff like <a href="https://infosec.space/tags/SSPL" class="mention hashtag" rel="nofollow noopener" target="_blank">#SSPL</a> which only serves as a means to commit <a href="https://infosec.space/tags/AssetDenial" class="mention hashtag" rel="nofollow noopener" target="_blank">#AssetDenial</a> and monopolize commercial offerings...<ul><li>I think <a href="https://infosec.space/tags/Linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#Linux</a> being <a href="https://infosec.space/tags/GPLv2only" class="mention hashtag" rel="nofollow noopener" target="_blank">#GPLv2only</a> is a good compromise and my personal gripes with <a href="https://infosec.space/tags/FSF" class="mention hashtag" rel="nofollow noopener" target="_blank">#FSF</a> & <a href="https://infosec.space/tags/GNUtils" class="mention hashtag" rel="nofollow noopener" target="_blank">#GNUtils</a> as well as <a href="https://infosec.space/tags/GlibC" class="mention hashtag" rel="nofollow noopener" target="_blank">#GlibC</a> are something different...</li></ul>

datenwolfInteresting things happen, when you attempt building an older version of the <a href="https://chaos.social/tags/glibc" class="mention hashtag" rel="nofollow noopener" target="_blank">#glibc</a> with a recent version of <a href="https://chaos.social/tags/GCC" class="mention hashtag" rel="nofollow noopener" target="_blank">#GCC</a> 🤢 <a href="https://asciinema.org/a/o5vaV6gvHSq49V3QpjORDfSaR" rel="nofollow noopener" translate="no" target="_blank">https://asciinema.org/a/o5vaV6gvHSq49V3QpjORDfSaR</a>

AskUbuntuHow to Use dlopen to Avoid GLIBC Version Mismatch? #2404 <a href="https://ubuntu.social/tags/sharedlibrary" class="mention hashtag" rel="nofollow noopener" target="_blank">#sharedlibrary</a> <a href="https://ubuntu.social/tags/glibc" class="mention hashtag" rel="nofollow noopener" target="_blank">#glibc</a><a href="https://askubuntu.com/q/1544183/612" rel="nofollow noopener" translate="no" target="_blank">https://askubuntu.com/q/1544183/612</a>

Christian Brauner 🦊🐺Who at <a href="https://mastodon.social/tags/glibc" class="mention hashtag" rel="tag">#glibc</a> do we need to bribe to get <a href="https://fosstodon.org/@codonell" class="u-url mention">@codonell</a> :"I think we really need to expose some sort of clone/clone3 wrapper, with some guardrails against unsupportable scenarios (such as spawning new threads in the current process)."finally implemented! It really is missing! <a href="https://patchwork.sourceware.org/project/glibc/patch/20230803163558.991832-7-adhemerval.zanella@linaro.org" target="_blank" rel="nofollow noopener" translate="no">https://patchwork.sourceware.org/project/glibc/patch/20230803163558.991832-7-adhemerval.zanella@linaro.org</a>

unixbhaskarUmmm 🤔<a href="https://fosstodon.org/tags/glibc" class="mention hashtag" rel="nofollow noopener" target="_blank">#glibc</a> <a href="https://fosstodon.org/tags/libc" class="mention hashtag" rel="nofollow noopener" target="_blank">#libc</a> <a href="https://fosstodon.org/tags/programming" class="mention hashtag" rel="nofollow noopener" target="_blank">#programming</a> <a href="https://fosstodon.org/tags/binary" class="mention hashtag" rel="nofollow noopener" target="_blank">#binary</a> <a href="https://fosstodon.org/tags/opensource" class="mention hashtag" rel="nofollow noopener" target="_blank">#opensource</a> <a href="https://jangafx.com/insights/linux-binary-compatibility" rel="nofollow noopener" translate="no" target="_blank">https://jangafx.com/insights/linux-binary-compatibility</a>

unixbhaskarUmmm 🤔<a href="https://mastodon.social/tags/glibc" class="mention hashtag" rel="tag">#glibc</a> <a href="https://mastodon.social/tags/libc" class="mention hashtag" rel="tag">#libc</a> <a href="https://mastodon.social/tags/programming" class="mention hashtag" rel="tag">#programming</a> <a href="https://mastodon.social/tags/binary" class="mention hashtag" rel="tag">#binary</a> <a href="https://mastodon.social/tags/opensource" class="mention hashtag" rel="tag">#opensource</a> <a href="https://jangafx.com/insights/linux-binary-compatibility" target="_blank" rel="nofollow noopener" translate="no">https://jangafx.com/insights/linux-binary-compatibility</a>

Kevin Karhan :verified:<a href="https://kitsunes.club/@Jessica" class="u-url mention" rel="nofollow noopener" target="_blank">@Jessica</a> <a href="https://mstdn.social/@BrodieOnLinux" class="u-url mention" rel="nofollow noopener" target="_blank">@BrodieOnLinux</a> +9001%The reason I don't use <a href="https://infosec.space/tags/GlibC" class="mention hashtag" rel="nofollow noopener" target="_blank">#GlibC</a> on <a href="https://infosec.space/@OS1337" class="u-url mention" rel="nofollow noopener" target="_blank">@OS1337</a> is because it's <a href="https://infosec.space/@kkarhan/114175034719920644" rel="nofollow noopener" target="_blank">constantly breaking userspace</a>…

Несерьёзный ВыдумщикПерестал работать <a class="hashtag" href="https://idealists.su/tag/portal2" rel="nofollow noopener" target="_blank">#Portal2</a> или что-то другое из игрушек на обновившемся <a class="hashtag" href="https://idealists.su/tag/linux" rel="nofollow noopener" target="_blank">#linux</a> ? При запуске в терминале пишет:<pre><code>failed to dlopen <a href="http://engine.so" rel="nofollow noopener" target="_blank">engine.so</a> error=engine.so: cannot enable executable stack as shared object requires: Invalid argument ... AppFramework : Unable to load module <a href="http://engine.so" rel="nofollow noopener" target="_blank">engine.so</a>! </code></pre>Почти наверняка это из-за того, что изменилась версия <a class="hashtag" href="https://idealists.su/tag/glibc" rel="nofollow noopener" target="_blank">#glibc</a><pre><code>/usr/lib/libc.so.6 GNU C Library (GNU libc) stable release version 2.41. </code></pre>И вот раз так — раз оно уже 2.41, тогда можно спокойно пропатчить два бинарника:<pre><code>patchelf --clear-execstack /path/to/Portal2/game/bin/linux32/engine.so patchelf --clear-execstack /path/to/Portal2/game/bin/linux32/valve_avi.so </code></pre>Всё, будет работать как и раньше :)<a class="hashtag" href="https://idealists.su/tag/linuxgaming" rel="nofollow noopener" target="_blank">#LinuxGaming</a> <a class="hashtag" href="https://idealists.su/tag/игры" rel="nofollow noopener" target="_blank">#игры</a> <a class="hashtag" href="https://idealists.su/tag/games" rel="nofollow noopener" target="_blank">#games</a> <a class="u-url mention" href="https://mastodon.social/@russian_mastodon" rel="nofollow noopener" target="_blank">@russian_mastodon</a> <a class="u-url mention" href="https://lor.sh/@ru" rel="nofollow noopener" target="_blank">@ru</a> <a class="u-url mention" href="https://3zi.ru/@Russia" rel="nofollow noopener" target="_blank">@Russia</a>

ParleurHo, un problème de mise à jour de <a href="https://mastodon.parleur.net/tags/glibc" class="mention hashtag" rel="nofollow noopener" target="_blank">#glibc</a> avec <a href="https://mastodon.parleur.net/tags/Debian" class="mention hashtag" rel="nofollow noopener" target="_blank">#Debian</a> unstable. Je crois que ça fait des années que ça ne m'était pas arrivé

Douglas J HunleyTuning the <a href="https://fosstodon.org/tags/glibc" class="mention hashtag" rel="nofollow noopener" target="_blank">#glibc</a> memory allocator (for <a href="https://fosstodon.org/tags/Postgres" class="mention hashtag" rel="nofollow noopener" target="_blank">#Postgres</a>) <a href="https://vondra.me/posts/tuning-the-glibc-allocator-for-postgres/" rel="nofollow noopener" translate="no" target="_blank">https://vondra.me/posts/tuning-the-glibc-allocator-for-postgres/</a>

GNU/Trinukso ۞Pues ya tengo respuesta, por temas técnicos que no explicare aquí (pues no los entendí del todo, je je) el tiempo de ejecución de <a href="https://masto.ai/tags/Steam" class="mention hashtag" rel="nofollow noopener" target="_blank">#Steam</a> no cubre / alcanza la librería <a href="https://masto.ai/tags/glibc" class="mention hashtag" rel="nofollow noopener" target="_blank">#glibc</a> y lo que son los controladores gráficos. Por eso que al actualizar (principalmente distribuciones de liberación continua) esta librería muchos juegos (nativos principalmente, al parecer) se rompieron.<a href="https://www.gamingonlinux.com/2025/02/the-glibc-2-41-update-has-been-causing-problems-for-linux-gaming/" rel="nofollow noopener" translate="no" target="_blank">https://www.gamingonlinux.com/2025/02/the-glibc-2-41-update-has-been-causing-problems-for-linux-gaming/</a>

NerdNextDoor :Blobhaj:Making a <a href="https://mastodon.social/tags/Linux" class="mention hashtag" rel="tag">#Linux</a> <a href="https://mastodon.social/tags/Distro" class="mention hashtag" rel="tag">#Distro</a> from the <a href="https://mastodon.social/tags/LFN" class="mention hashtag" rel="tag">#LFN</a> guide by MapleCircuit. (Great guy, search up the series <a href="https://mastodon.social/tags/LinuxfromNothing" class="mention hashtag" rel="tag">#LinuxfromNothing</a> and go follow him!!!)I’m using <a href="https://mastodon.social/tags/Musl" class="mention hashtag" rel="tag">#Musl</a> instead of <a href="https://mastodon.social/tags/Glibc" class="mention hashtag" rel="tag">#Glibc</a> for funsies.I’m <a href="https://mastodon.social/tags/Nerdy" class="mention hashtag" rel="tag">#Nerdy</a> as shit, and that’s pretty cool.<a href="https://mastodon.social/tags/Tech" class="mention hashtag" rel="tag">#Tech</a> <a href="https://mastodon.social/tags/Technology" class="mention hashtag" rel="tag">#Technology</a> <a href="https://mastodon.social/tags/Nerd" class="mention hashtag" rel="tag">#Nerd</a>

Gardiner BryantThe glibc disaster, Wayland HDR update, and more Linux Gaming News! <a href="https://subscribeto.me/videos/watch/ab8c04fe-8247-4844-88eb-4af189b21c42" rel="nofollow noopener" translate="no" target="_blank">https://subscribeto.me/videos/watch/ab8c04fe-8247-4844-88eb-4af189b21c42</a>

hubertfOn thread vs. process permissionsIn common Unix and POSIX systems, all threads in a process are supposed to have the same permission. So why does the vortex8 program work as exploited, where one thread sets different permissions than another one using setresuid/setresgid?Reference: <a href="https://man7.org/linux/man-pages/man2/setresuid.2.html" target="_blank" rel="nofollow noopener" translate="no">https://man7.org/linux/man-pages/man2/setresuid.2.html</a>Answer in thread.<a href="https://mastodon.social/tags/ctf" class="mention hashtag" rel="tag">#ctf</a> <a href="https://mastodon.social/tags/cybersecurity" class="mention hashtag" rel="tag">#cybersecurity</a> <a href="https://mastodon.social/tags/posix" class="mention hashtag" rel="tag">#posix</a> <a href="https://mastodon.social/tags/linux" class="mention hashtag" rel="tag">#linux</a> <a href="https://mastodon.social/tags/glibc" class="mention hashtag" rel="tag">#glibc</a> <a href="https://mastodon.social/tags/syscall" class="mention hashtag" rel="tag">#syscall</a> <a href="https://mastodon.social/tags/overthewire" class="mention hashtag" rel="tag">#overthewire</a> <a href="https://mastodon.social/tags/vortex" class="mention hashtag" rel="tag">#vortex</a>

mgorny-nyan (on) :autism:🙀🚂🐧Jeżeli kiedyś zastanawialiście się, jak szybko rośnie `packaging.tags.sys_tags()` na GNU / <a href="https://pol.social/tags/Linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#Linux</a>, to mam formułkę (chyba że coś popieprzyłem). Dla <a href="https://pol.social/tags/CPython" class="mention hashtag" rel="nofollow noopener" target="_blank">#CPython</a> 3.x na <a href="https://pol.social/tags/glibc" class="mention hashtag" rel="nofollow noopener" target="_blank">#glibc</a> 2.y, łączną liczbę tagów wyraża wyrażenie:2xy + x + 3y + 3Albo równoważnie:x(2y + 1) + 3y + 3 y(2x + 3) + x + 3Co za tym idzie, jeżeli nic innego się nie zmienia, to każda nowa wersja Pythona dodaje (2y + 1) tagów, a każda nowa wersja glibc dodaje (2x + 3) tagów. Dla glibc 2.41, daje to 83 nowe tagi na nową wersję CPythona. Dla CPythona 3.13, mamy 29 nowych tagów na nową wersję glibc.No i dla porównania: CPython 3.13 na architekturze x86_64 z glibc 2.41 ma już 1205 zgodnych tagów paczek wheel.<a href="https://pol.social/tags/Python" class="mention hashtag" rel="nofollow noopener" target="_blank">#Python</a>

mgorny-nyan (he) :autism:🙀🚂🐧If you were ever wondering how fast `<a href="https://social.treehouse.systems/tags/packaging" class="mention hashtag" rel="nofollow noopener" target="_blank">#packaging</a>.tags.sys_tags()` are growing on GNU / <a href="https://social.treehouse.systems/tags/Linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#Linux</a>, I have a formula for you (unless I screwed up the maths). For <a href="https://social.treehouse.systems/tags/CPython" class="mention hashtag" rel="nofollow noopener" target="_blank">#CPython</a> 3.x on <a href="https://social.treehouse.systems/tags/glibc" class="mention hashtag" rel="nofollow noopener" target="_blank">#glibc</a> 2.y, the total number of tags is:2xy + x + 3y + 3Or equivalently:x(2y + 1) + 3y + 3 y(2x + 3) + x + 3So all other things equal, every new minor version of <a href="https://social.treehouse.systems/tags/Python" class="mention hashtag" rel="nofollow noopener" target="_blank">#Python</a> introduces (2y + 1) tags, and every new minor version of glibc introduces (2x + 3) tags. For glibc 2.41, this means 83 new tags per CPython version. For CPython 3.13, this means 29 new tags per glibc version.Oh, and for a good measure: CPython 3.13 on x86_64 with glibc 2.41 features 1205 compatible wheel tags.

GNU/Trinukso ۞¡Ayuda jugones como <a href="https://social.hardlimit.com/@pos_yo" class="u-url mention" rel="nofollow noopener" target="_blank">@pos_yo</a> y <a href="https://mastodon.social/@edlinks" class="u-url mention" rel="nofollow noopener" target="_blank">@edlinks</a>!<a href="https://www.gamingonlinux.com/2025/02/the-glibc-2-41-update-has-been-causing-problems-for-linux-gaming/" rel="nofollow noopener" translate="no" target="_blank">https://www.gamingonlinux.com/2025/02/the-glibc-2-41-update-has-been-causing-problems-for-linux-gaming/</a>Sale <a href="https://masto.ai/tags/glibc" class="mention hashtag" rel="nofollow noopener" target="_blank">#glibc</a> 2.41 y rompe algunos juegos nativos (antiguos), al parecer, con librerías <a href="https://masto.ai/tags/FMOD" class="mention hashtag" rel="nofollow noopener" target="_blank">#FMOD</a> en Mono (Unity). Uno de ellos es <a href="https://masto.ai/tags/Celeste" class="mention hashtag" rel="nofollow noopener" target="_blank">#Celeste</a>. Yo tengo <a href="https://masto.ai/tags/ArchLinux" class="mention hashtag" rel="nofollow noopener" target="_blank">#ArchLinux</a> con dicha actualización. Pero, claro, uso la versión <a href="https://masto.ai/tags/flatpak" class="mention hashtag" rel="nofollow noopener" target="_blank">#flatpak</a> de <a href="https://masto.ai/tags/Steam" class="mention hashtag" rel="nofollow noopener" target="_blank">#Steam</a>. Y me funciona bien el juego.Lo que no entiendo es si el tiempo de ejecución que usa Steam (que no es precisamente de estar al día) como se le rompe los juegos a la gente.

Liam @ GamingOnLinuxThe glibc 2.41 update has been causing problems for Linux gaming <a class="hashtag" href="https://bsky.app/search?q=%23Linux" rel="nofollow noopener" target="_blank">#Linux</a> <a class="hashtag" href="https://bsky.app/search?q=%23glibc" rel="nofollow noopener" target="_blank">#glibc</a> <a class="hashtag" href="https://bsky.app/search?q=%23LinuxGaming" rel="nofollow noopener" target="_blank">#LinuxGaming</a> <a href="https://www.gamingonlinux.com/2025/02/the-glibc-2-41-update-has-been-causing-problems-for-linux-gaming/" rel="nofollow noopener" target="_blank">The glibc 2.41 update has been...</a>

Recent searches

Search options

Administered by:

Server stats:

#glibc