Jose Luis Alarcon Sanchez, le mer. 11 févr. 2026 11:00:27 +0100, a ecrit: > El Tue, 10 Feb 2026 22:53:39 +0100 > Samuel Thibault <[email protected]> escribió: > > Jose Luis Alarcon Sanchez, le mar. 10 févr. 2026 20:41:38 +0100, a > > ecrit: > > > El Tue, 10 Feb 2026 19:23:17 +0100 > > > Samuel Thibault <[email protected]> escribió: > > > > Hello, > > > > > > > > Jose Luis Alarcon Sanchez, le mar. 10 févr. 2026 15:37:08 +0100, a > > > > ecrit: > > > > > How is it possible that at the end of last year, from one > > > > > day to the next, the two best web browsers available on > > > > > GNU/Hurd, Luakit and Surf, which are very similar and based on > > > > > the same scripting language, Lua, went from working very > > > > > satisfactorily to instantly terminating when launched, with the > > > > > brief output ‘abort’? > > > > > > > > Because of a bug? The abort message would probably be very > > > > informative. Or a gdb backtrace, etc. > > > > > > > > > Is it possible to investigate why this happened?. > > > > > > > > Sure. For a simple start, you can check what package got upgraded > > > > in between, and then try to downgrade/upgrade to verify which > > > > exact package pose problems. But also simply actually pasting the > > > > abortion message would provide the list with *way* more > > > > information than just "terminates". > > > > > > I don't know how to get a "register" of the upgrades realized at > > > that time (it was last week of 2025, i'm sure of it). > > > > It's all in /var/log/dpkg.log > > > > Ok. Attached a short extract of /var/log/dpkg.log. I am 100% sure that > the changes that triggered the browsers falilure was made on December > 29th. Also including the day before and the day after.
Then you can try to downgrade/reupgrade, to confirm which one poses problem. > #6 0x0000000108e4bfcd in __GI_abort () at ./stdlib/abort.c:77 > #7 0x0000000107ae1bec in ??? () at > /usr/lib/x86_64-gnu/libjavascriptcoregtk-4.1.so.0 > #8 0x0000000107f76912 in ??? () at > /usr/lib/x86_64-gnu/libjavascriptcoregtk-4.1.so.0 So you want to install the -dbgsym package for that library, to get source code information Samuel
