Arch Linux User Repository

There is no new tagged (or otherwise differentiable) version to update to. Existing bumps to arbitrary revisions have been done whenever I get around to it to avoid the package falling into complete disrepair (which would cause it to be deleted and most likely recreated by some third party) and to make sure that people who don't pay attention don't get a version that is years out of date. The actual package has always been ladybird-git, and that will remain the case for the foreseeable future as well.

Hi. Ladybird 20250312 segfaults for me, and searching AUR comments below it looks like it might be a me-only problem. Any idea why? EDIT ah, a few such reports in sibling AUR pkg https://aur.archlinux.org/packages/ladybird-git .

~ gdb Ladybird
(No debugging symbols found in Ladybird)

(gdb) run
Starting program: /usr/bin/Ladybird
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/usr/lib/libthread_db.so.1".
[New Thread 0x7ffff130c6c0 (LWP 256378)]
[New Thread 0x7fffeafd46c0 (LWP 256379)]
[New Thread 0x7fffe9fd36c0 (LWP 256380)]
[New Thread 0x7fffe3fff6c0 (LWP 256381)]
[New Thread 0x7fffe2ffe6c0 (LWP 256382)]
[New Thread 0x7fffe1ffd6c0 (LWP 256383)]
[New Thread 0x7fffcffff6c0 (LWP 256384)]

Thread 1 "Ladybird" received signal SIGSEGV, Segmentation fault.
0x000055555e60e120 in ?? ()

The PKGBUILD does not properly disable vcpkg telemetry as described in https://github.com/LadybirdBrowser/ladybird/issues/3816. We should probably take care of this.

@Sateallia alright. There's also the option to build ladybird with a compilation cache, so only the changed files are recompiled if you update git commits.

@RubenKelevra I prefer not to use Chaotic-AUR as I connect to systems that aren't mine and I don't wish to expose them to any danger that comes from third party repositories. If timschumi declines my proposal/request, I will look into setting up a builder of my own so thank you for the idea.

@Sateallia you can install ladybird without the need for compilation via chaotic-aur. The only thing necessary for more up-to-date updates would be, that someone confirms that a git version is building and then move this package here up to this commit.

ladybird-git often breaks because of vcpkg updates. Even when it builds properly, it moves too fast for me since I'm on a low-powered computer and building multiple times in a day takes too much time. Considering Ladybird is planning an alpha release in 2026, it would be nice if this package could be updated at least once a month to an arbitrary random commit. This would also allow people that evaluate Ladybird every month (after the monthly TMiL bulletins) to follow Ladybird's progress.

There is no new tagged (or otherwise differentiable) version to update to. Existing bumps to arbitrary revisions have been done whenever I get around to it to avoid the package falling into complete disrepair (which would cause it to be deleted and most likely recreated by some third party) and to make sure that people who don't pay attention don't get a version that is years out of date. The actual package has always been ladybird-git, and that will remain the case for the foreseeable future as well.

This package should update more frequently. Maybe every "This Month in Ladybird"?

I crash right after installation. Not sure if it's ABI problem or something else (even if it is, why ABI problem when build locally)

#0  0x000055555e498820 in ??? ()
#1  0x00007ffff54cea7b in hb_face_reference_table () at /usr/bin/../lib/libharfbuzz.so.0
#2  0x00007ffff54ec24e in ??? () at /usr/bin/../lib/libharfbuzz.so.0
#3  0x00007ffff555c265 in hb_ot_var_get_axis_infos () at /usr/bin/../lib/libharfbuzz.so.0
#4  0x00007ffff1b091be in ??? () at /usr/lib/libpangoft2-1.0.so.0
#5  0x00007ffff05ab72a in pango_font_get_hb_font () at /usr/lib/qt6/plugins/platformthemes/../../../libpango-1.0.so.0
#6  0x00007ffff05dfc45 in ??? () at /usr/lib/qt6/plugins/platformthemes/../../../libpango-1.0.so.0
#7  0x00007ffff05d4ad0 in ??? () at /usr/lib/qt6/plugins/platformthemes/../../../libpango-1.0.so.0
#8  0x00007ffff05d5317 in pango_shape_item () at /usr/lib/qt6/plugins/platformthemes/../../../libpango-1.0.so.0
#9  0x00007ffff05c3306 in ??? () at /usr/lib/qt6/plugins/platformthemes/../../../libpango-1.0.so.0
#10 0x00007ffff05c48bb in ??? () at /usr/lib/qt6/plugins/platformthemes/../../../libpango-1.0.so.0
#11 0x00007ffff05c7195 in ??? () at /usr/lib/qt6/plugins/platformthemes/../../../libpango-1.0.so.0
#12 0x00007ffff05ba3c2 in pango_layout_get_unknown_glyphs_count () at /usr/lib/qt6/plugins/platformthemes/../../../libpango-1.0.so.0
#13 0x00007ffff0746bc2 in ??? () at /usr/lib/qt6/plugins/platformthemes/../../../libgtk-3.so.0
#14 0x00007ffff0746fe0 in ??? () at /usr/lib/qt6/plugins/platformthemes/../../../libgtk-3.so.0
#15 0x00007ffff4914b09 in g_type_create_instance () at /usr/lib/libgobject-2.0.so.0
#16 0x00007ffff48f9805 in ??? () at /usr/lib/libgobject-2.0.so.0
#17 0x00007ffff48fae7f in g_object_new_with_properties () at /usr/lib/libgobject-2.0.so.0
#18 0x00007ffff48fbed2 in g_object_new () at /usr/lib/libgobject-2.0.so.0
#19 0x00007ffff0eea382 in ??? () at /usr/lib/qt6/plugins/platformthemes/libqgtk3.so
#20 0x00007ffff0eeb694 in ??? () at /usr/lib/qt6/plugins/platformthemes/libqgtk3.so
#21 0x00007ffff0eebd42 in ??? () at /usr/lib/qt6/plugins/platformthemes/libqgtk3.so
#22 0x00007ffff76f10b2 in QApplicationPrivate::basePalette() const () at /usr/bin/../lib/libQt6Widgets.so.6
#23 0x00007ffff6d97286 in QGuiApplicationPrivate::setPalette(QPalette const&) () at /usr/bin/../lib/libQt6Gui.so.6
#24 0x00007ffff6d977a4 in QGuiApplicationPrivate::updatePalette() () at /usr/bin/../lib/libQt6Gui.so.6
#25 0x00007ffff6d8beaa in QGuiApplicationPrivate::init() () at /usr/bin/../lib/libQt6Gui.so.6
#26 0x00007ffff76f94e6 in QApplicationPrivate::init() () at /usr/bin/../lib/libQt6Widgets.so.6
#27 0x000055555861cf25 in ??? ()
#28 0x00005555586541ed in ??? ()
#29 0x0000555558b7818f in main ()

Needs to have skia-git as a dependency.