| 4 Jan 2024 |
 nbp | That's why impure systems are good sometimes :P | 12:59:01 |
| 5 Jan 2024 |
|  Sporesirius joined the room. | 15:11:27 |
| 6 Jan 2024 |
 hexa | https://www.jwz.org/blog/2024/01/my-dinosaur-just-threw-up-in-its-mouth-a-little/ | 04:07:54 |
 @aloisw:kde.org | 🤮🤮🤮🤮🤮 | 09:56:44 |
| 10 Jan 2024 |
|  ghpzin changed their display name from 9hp71n to ghpzin. | 06:33:13 |
| hexa | https://github.com/NixOS/nixpkgs/pull/280044 | 14:55:07 |
| hexa | https://github.com/NixOS/nixpkgs/pull/280114 | 21:10:17 |
| hexa | I don't like the wrapper one bit 😕 | 21:10:25 |
| 11 Jan 2024 |
| nbp | I am not sure to understand what you are talking about. | 10:56:40 |
| 13 Jan 2024 |
|  felipeggmarcelino joined the room. | 19:53:33 |
| 16 Jan 2024 |
| nbp | “Failed to open curl lib from binary, use libcurl.so instead” … why am I using Firefox nightly? 🤦 | 18:03:22 |
| nbp | colemickens: Are you seeing the same issue with nightly? | 18:04:55 |
| nbp | $ find . \! -type d -print0 | xargs -0 grep libcurl.so
grep: ./pingsender: binary file matches
grep: ./crashreporter: binary file matches
| 18:17:17 |
| nbp | https://searchfox.org/mozilla-central/source/toolkit/components/telemetry/pingsender/pingsender_unix_common.cpp#98
Not sure if this is the issue as this message is displayed after the crash reporter is shown. | 18:20:17 |
| nbp | https://searchfox.org/mozilla-central/source/toolkit/crashreporter/google-breakpad/src/common/linux/http_upload.cc#74
crash reporter it is … so this is not the original issue. | 18:21:38 |
| nbp | ok … if I evaluate the wrapped firefox without the environment provided by the wrapper, then I launches successfully, but complains about missing libraries. | 18:58:56 |
| nbp | Removing mesa from LD_LIBRARY_PATH seems to let firefox run instead of crashing. | 19:13:45 |
 K900 ⚡️ | You probably have mismatched Mesa versions between system and Firefox | 19:15:07 |
| K900 ⚡️ | It needs to match exactly, at least for now | 19:15:16 |
 colemickens | K900 ⚡️: second time this has come up and I've gotten pinged, so I assume you've probably answered it a lot. Is there a reason this is happening more now than in past bumps? An issue I can follow or something. | 20:09:30 |
| K900 ⚡️ | Mesa started hard crashing on version mismatches | 20:10:03 |
| K900 ⚡️ | Instead of warning and trying to continue | 20:10:18 |
| K900 ⚡️ | Which | 20:10:24 |
| K900 ⚡️ | Well it usually ended up crashing | 20:10:37 |
| K900 ⚡️ | But sometimes it didn't | 20:10:47 |
| colemickens | Sure would've been nice if it tried harder to alert folks as to what's happening. | 20:12:53 |
| colemickens | Maybe it does and it's just not really able to, but it sure feels like it should have a shot at spamming some useful message to stderr | 20:13:15 |
| K900 ⚡️ | It does | 20:17:16 |
| K900 ⚡️ | It's just that in the case of firefox it's the stderr of some helper proces | 20:17:30 |
| K900 ⚡️ | * It's just that in the case of firefox it's the stderr of some helper process | 20:17:31 |
