I see that got fixed already in 7f2a32fa
We are seeing one of those errors also on Ubuntu Noble trying to rebuild 1.44 https://launchpadlibrarian.net/713988908/buildlog_ubuntu-noble-amd64.network-manager_1.44.2-7ubuntu2~build2_BUILDING.txt.gz
ok 7 /config/warnings
PASS: src/core/tests/config/test-config 7 /config/warnings
# (src/core/tests/config/test-config.c:1107) invalid value in config-data .intern.with-whitespace.key2 = (null) (instead of " b c\, d ")
exec "./src/core/tests/config/test-config" failed with exit code 133
ERROR: src/core/tests/config/test-config - too few tests run (expected 14, got 7)
ERROR: src/core/tests/config/test-config - exited with status 5
Could be some depends which changed since the same package was working before (we have glib 2.79 there for example)
is there more information we could provide that would help there? the test failure is a blocker to get the new version in Debian or Ubuntu
Usually the ppc64el Ubuntu builders are quite performant so it's probably not a slow machine type of problem, perhaps the contrary?
For reference the corresponding test took 1.39s on armhf which is our slowest architecture and here we hit the 60s timeout
The testlog.txt dump is in the build log referenced in the report, let me know if that someone lacks information/if there is a more verbose mode that we could turn on
The 1.2.0-1 version failed to build on amd64 and i386 in Debian on similar timeout errors (1.1.0 didn't hit that issue).
Build log example on https://buildd.debian.org/status/fetch.php?pkg=libei&arch=i386&ver=1.2.0-1&stamp=1701901975&raw=0
command: UBSAN_OPTIONS=halt_on_error=1:abort_on_error=1:print_summary=1:print_stacktrace=1 MALLOC_PERTURB_=52 ASAN_OPTIONS=halt_on_error=1:abort_on_error=1:print_summary=1 LD_LIBRARY_PATH=/<<PKGBUILDDIR>>/obj-i686-linux-gnu/src:/<<PKGBUILDDIR>>/obj-i686-linux-gnu/subprojects/munit /<<PKGBUILDDIR>>/obj-i686-linux-gnu/test/eierpecken --log-visible debug --enable-sigalarm
----------------------------------- stdout -----------------------------------
Running test suite with seed 0x03585bc1...
test_passive_ei_flush_frame
==============================================================================
The same package built fine on Ubuntu amd64 but is failing on the ppc64el builders reliably, it seems it might be racy and depending of the machine rather than of the architecture.
I've no be able to reproduce the issue building locally or on a porter machine which makes it difficult to get more debugging information...
The bug was reported on Ubuntu 23.10 with gstreamer-vaapi 1.22.6
Totem fails to play some webm videos with gst-vaapi installed but plays those fine without that package
Example video https://bugs.launchpad.net/ubuntu/+source/gstreamer-vaapi/+bug/2037874/+attachment/5709058/+files/prova3.webm
Totem debug log https://bugs.launchpad.net/ubuntu/+source/gstreamer-vaapi/+bug/2037874/+attachment/5709045/+files/totem-debug.txt
Launchpad bug report https://launchpad.net/bugs/2037874
Similar to !113 but our accountsservice package include that fix so probably another similar issue
==56020== Invalid read of size 8
==56020== at 0x4A70D41: g_type_check_instance (gtype.c:4270)
==56020== by 0x4A63567: g_signal_handlers_disconnect_matched (gsignal.c:3067)
==56020== by 0x4BEF9A7: act_user_manager_finalize (act-user-manager.c:2639)
==56020== by 0x4A59E4B: g_object_unref (gobject.c:3938)
==56020== by 0x112D3A: im_accounts_service_dispose (im-accounts-service.c:80)
==56020== by 0x4A59D9F: g_object_unref (gobject.c:3891)
==56020== by 0x111E52: im_application_list_dispose (im-application-list.c:567)
==56020== by 0x4A59D9F: g_object_unref (gobject.c:3891)
==56020== by 0x11143D: main (messages-service.c:290)
==56020== Address 0x56dc930 is 0 bytes inside a block of size 64 free'd
==56020== at 0x484620F: free (in /usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so)
==56020== by 0x4A6F66B: g_type_free_instance (gtype.c:2062)
==56020== by 0x4A4C00F: g_closure_invoke (gclosure.c:832)
==56020== by 0x4A793D5: signal_emit_unlocked_R.isra.0 (gsignal.c:3802)
==56020== by 0x4A69699: g_signal_emit_valist (gsignal.c:3555)
==56020== by 0x4A69922: g_signal_emit (gsignal.c:3612)
==56020== by 0x4A56DC3: g_object_dispatch_properties_changed.lto_priv.0 (gobject.c:1428)
==56020== by 0x4A5D09E: UnknownInlinedFun (gobject.c:1552)
==56020== by 0x4A5D09E: g_object_notify (gobject.c:1602)
==56020== by 0x4BF85DD: load_seat_incrementally (act-user-manager.c:2271)
==56020== by 0x4AF336E: UnknownInlinedFun (gmain.c:3460)
==56020== by 0x4AF336E: g_main_context_dispatch (gmain.c:4200)
==56020== by 0x4B4E177: g_main_context_iterate.constprop.0 (gmain.c:4276)
==56020== by 0x4AF2BDE: g_main_loop_run (gmain.c:4479)
==56020== Block was alloc'd at
==56020== at 0x4848A13: calloc (in /usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so)
==56020== by 0x4AF8550: g_malloc0 (gmem.c:163)
==56020== by 0x4A74B7C: g_type_create_instance (gtype.c:1965)
==56020== by 0x4A5C20F: g_object_new_internal (gobject.c:2246)
==56020== by 0x4A5D7B7: g_object_new_with_properties (gobject.c:2409)
==56020== by 0x4A5E560: g_object_new (gobject.c:2055)
==56020== by 0x4BF1751: create_new_user (act-user-manager.c:738)
==56020== by 0x4BF7564: act_user_manager_get_user (act-user-manager.c:1982)
==56020== by 0x1134CD: on_user_manager_loaded (im-accounts-service.c:149)
==56020== by 0x4A4C00F: g_closure_invoke (gclosure.c:832)
==56020== by 0x4A793D5: signal_emit_unlocked_R.isra.0 (gsignal.c:3802)
==56020== by 0x4A69699: g_signal_emit_valist (gsignal.c:3555)
the ayatana indicator source for reference is https://github.com/AyatanaIndicators/ayatana-indicator-messages/blob/main/src/im-accounts-service.c
In Ubuntu Lunar we started receiving reports of ayatana-indicator-messages segfaulting, which seems to be triggered at logout for most users (but then the reporting utility prompt them at next login).
The package itself and accountsservice didn't change so maybe changes in the stack are making the problem visible?
Valgrind shows invalid read error, log from the current git master (d603f80c) doing those steps
$ valgrind /usr/libexec/ayatana-indicator-messages/ayatana-indicator-messages-service
$ sudo kill -9 `pidof accounts-daemon`
$ gnome-control-center user-accounts
the g-c-c call is having for effect to respawn the service, the error are then displayed
==50297== Invalid read of size 8
==50297== at 0x4C0B26A: UnknownInlinedFun (act-user-manager.c:1824)
==50297== by 0x4C0B26A: on_user_manager_maybe_ready_for_request (act-user-manager.c:1814)
==50297== by 0x4A6100F: g_closure_invoke (gclosure.c:832)
==50297== by 0x4A8E3D5: signal_emit_unlocked_R.isra.0 (gsignal.c:3802)
==50297== by 0x4A7E699: g_signal_emit_valist (gsignal.c:3555)
==50297== by 0x4A7E922: g_signal_emit (gsignal.c:3612)
==50297== by 0x4A6BDC3: g_object_dispatch_properties_changed.lto_priv.0 (gobject.c:1428)
==50297== by 0x4A7209E: UnknownInlinedFun (gobject.c:1552)
==50297== by 0x4A7209E: g_object_notify (gobject.c:1602)
==50297== by 0x4C05A34: UnknownInlinedFun (act-user-manager.c:1321)
==50297== by 0x4C05A34: on_name_owner_changed (act-user-manager.c:2525)
==50297== by 0x4A6100F: g_closure_invoke (gclosure.c:832)
==50297== by 0x4A8E3D5: signal_emit_unlocked_R.isra.0 (gsignal.c:3802)
==50297== by 0x4A7E699: g_signal_emit_valist (gsignal.c:3555)
==50297== by 0x4A7E922: g_signal_emit (gsignal.c:3612)
==50297== Address 0x5800e68 is 56 bytes inside a block of size 64 free'd
==50297== at 0x484620F: free (in /usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so)
==50297== by 0x4C0405F: on_user_destroyed (act-user-manager.c:733)
==50297== by 0x4A6A4E6: weak_refs_notify (gobject.c:3286)
==50297== by 0x4AE84FB: g_data_set_internal (gdataset.c:410)
==50297== by 0x4A6BE14: g_object_real_dispose.lto_priv.0 (gobject.c:1364)
==50297== by 0x4A6ED9F: g_object_unref (gobject.c:3891)
==50297== by 0x4A6100F: g_closure_invoke (gclosure.c:832)
==50297== by 0x4A8E3D5: signal_emit_unlocked_R.isra.0 (gsignal.c:3802)
==50297== by 0x4A7E699: g_signal_emit_valist (gsignal.c:3555)
==50297== by 0x4A7E922: g_signal_emit (gsignal.c:3612)
==50297== by 0x4A6BDC3: g_object_dispatch_properties_changed.lto_priv.0 (gobject.c:1428)
==50297== by 0x4A7209E: UnknownInlinedFun (gobject.c:1552)
==50297== by 0x4A7209E: g_object_notify (gobject.c:1602)
==50297== Block was alloc'd at
==50297== at 0x4843828: malloc (in /usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so)
==50297== by 0x4B0C948: g_malloc (gmem.c:130)
==50297== by 0x4C0B444: UnknownInlinedFun (act-user-manager.c:1888)
==50297== by 0x4C0B444: act_user_manager_get_user (act-user-manager.c:1994)
==50297== by 0x1134CD: on_user_manager_loaded (im-accounts-service.c:149)
==50297== by 0x4A6100F: g_closure_invoke (gclosure.c:832)
==50297== by 0x4A8E3D5: signal_emit_unlocked_R.isra.0 (gsignal.c:3802)
==50297== by 0x4A7E699: g_signal_emit_valist (gsignal.c:3555)
==50297== by 0x4A7E922: g_signal_emit (gsignal.c:3612)
==50297== by 0x4A6BDC3: g_object_dispatch_properties_changed.lto_priv.0 (gobject.c:1428)
==50297== by 0x4A7209E: UnknownInlinedFun (gobject.c:1552)
==50297== by 0x4A7209E: g_object_notify (gobject.c:1602)
==50297== by 0x4C05A34: UnknownInlinedFun (act-user-manager.c:1321)
==50297== by 0x4C05A34: on_name_owner_changed (act-user-manager.c:2525)
==50297== by 0x4A6100F: g_closure_invoke (gclosure.c:832)
==50297==
==50297== Invalid read of size 1
==50297== at 0x4849CA6: strlen (in /usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so)
==50297== by 0x4C86317: __printf_buffer (vfprintf-process-arg.c:435)
==50297== by 0x4CA85F3: __vasprintf_internal (vasprintf.c:102)
==50297== by 0x4B5D8C1: UnknownInlinedFun (stdio2.h:169)
==50297== by 0x4B5D8C1: g_vasprintf (gprintf.c:340)
==50297== by 0x4B2ABE0: g_strdup_vprintf (gstrfuncs.c:553)
==50297== by 0x4B0C2F6: UnknownInlinedFun (gmessages.c:3363)
==50297== by 0x4B0C2F6: g_logv (gmessages.c:1318)
==50297== by 0x4B0C7A2: g_log (gmessages.c:1460)
==50297== by 0x4C0B279: UnknownInlinedFun (act-user-manager.c:1824)
==50297== by 0x4C0B279: on_user_manager_maybe_ready_for_request (act-user-manager.c:1814)
==50297== by 0x4A6100F: g_closure_invoke (gclosure.c:832)
==50297== by 0x4A8E3D5: signal_emit_unlocked_R.isra.0 (gsignal.c:3802)
==50297== by 0x4A7E699: g_signal_emit_valist (gsignal.c:3555)
==50297== by 0x4A7E922: g_signal_emit (gsignal.c:3612)
==50297== Address 0x5800f00 is 0 bytes inside a block of size 14 free'd
==50297== at 0x484620F: free (in /usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so)
==50297== by 0x4C03F90: free_fetch_user_request (act-user-manager.c:1780)
==50297== by 0x4C0405F: on_user_destroyed (act-user-manager.c:733)
==50297== by 0x4A6A4E6: weak_refs_notify (gobject.c:3286)
==50297== by 0x4AE84FB: g_data_set_internal (gdataset.c:410)
==50297== by 0x4A6BE14: g_object_real_dispose.lto_priv.0 (gobject.c:1364)
==50297== by 0x4A6ED9F: g_object_unref (gobject.c:3891)
==50297== by 0x4A6100F: g_closure_invoke (gclosure.c:832)
==50297== by 0x4A8E3D5: signal_emit_unlocked_R.isra.0 (gsignal.c:3802)
==50297== by 0x4A7E699: g_signal_emit_valist (gsignal.c:3555)
==50297== by 0x4A7E922: g_signal_emit (gsignal.c:3612)
==50297== by 0x4A6BDC3: g_object_dispatch_properties_changed.lto_priv.0 (gobject.c:1428)
==50297== Block was alloc'd at
==50297== at 0x4843828: malloc (in /usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so)
==50297== by 0x4CA8677: __vasprintf_internal (vasprintf.c:116)
==50297== by 0x4B5D8C1: UnknownInlinedFun (stdio2.h:169)
==50297== by 0x4B5D8C1: g_vasprintf (gprintf.c:340)
==50297== by 0x4B2ABE0: g_strdup_vprintf (gstrfuncs.c:553)
==50297== by 0x4B2AC9C: g_strdup_printf (gstrfuncs.c:583)
==50297== by 0x4C0B49A: UnknownInlinedFun (act-user-manager.c:1895)
==50297== by 0x4C0B49A: act_user_manager_get_user (act-user-manager.c:1994)
==50297== by 0x1134CD: on_user_manager_loaded (im-accounts-service.c:149)
==50297== by 0x4A6100F: g_closure_invoke (gclosure.c:832)
==50297== by 0x4A8E3D5: signal_emit_unlocked_R.isra.0 (gsignal.c:3802)
==50297== by 0x4A7E699: g_signal_emit_valist (gsignal.c:3555)
==50297== by 0x4A7E922: g_signal_emit (gsignal.c:3612)
==50297== by 0x4A6BDC3: g_object_dispatch_properties_changed.lto_priv.0 (gobject.c:1428)
==50297== Invalid read of size 2
==50297== at 0x484DAC0: memmove (in /usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so)
==50297== by 0x4C7CB67: __printf_buffer_write (Xprintf_buffer_write.c:39)
==50297== by 0x4C84CD4: __printf_buffer (vfprintf-process-arg.c:501)
==50297== by 0x4CA85F3: __vasprintf_internal (vasprintf.c:102)
==50297== by 0x4B5D8C1: UnknownInlinedFun (stdio2.h:169)
==50297== by 0x4B5D8C1: g_vasprintf (gprintf.c:340)
==50297== by 0x4B2ABE0: g_strdup_vprintf (gstrfuncs.c:553)
==50297== by 0x4B0C2F6: UnknownInlinedFun (gmessages.c:3363)
==50297== by 0x4B0C2F6: g_logv (gmessages.c:1318)
==50297== by 0x4B0C7A2: g_log (gmessages.c:1460)
==50297== by 0x4C0B279: UnknownInlinedFun (act-user-manager.c:1824)
==50297== by 0x4C0B279: on_user_manager_maybe_ready_for_request (act-user-manager.c:1814)
==50297== by 0x4A6100F: g_closure_invoke (gclosure.c:832)
==50297== by 0x4A8E3D5: signal_emit_unlocked_R.isra.0 (gsignal.c:3802)
==50297== by 0x4A7E699: g_signal_emit_valist (gsignal.c:3555)
==50297== Address 0x5800f08 is 8 bytes inside a block of size 14 free'd
==50297== at 0x484620F: free (in /usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so)
==50297== by 0x4C03F90: free_fetch_user_request (act-user-manager.c:1780)
==50297== by 0x4C0405F: on_user_destroyed (act-user-manager.c:733)
==50297== by 0x4A6A4E6: weak_refs_notify (gobject.c:3286)
==50297== by 0x4AE84FB: g_data_set_internal (gdataset.c:410)
==50297== by 0x4A6BE14: g_object_real_dispose.lto_priv.0 (gobject.c:1364)
==50297== by 0x4A6ED9F: g_object_unref (gobject.c:3891)
==50297== by 0x4A6100F: g_closure_invoke (gclosure.c:832)
==50297== by 0x4A8E3D5: signal_emit_unlocked_R.isra.0 (gsignal.c:3802)
==50297== by 0x4A7E699: g_signal_emit_valist (gsignal.c:3555)
==50297== by 0x4A7E922: g_signal_emit (gsignal.c:3612)
==50297== by 0x4A6BDC3: g_object_dispatch_properties_changed.lto_priv.0 (gobject.c:1428)
==50297== Block was alloc'd at
==50297== at 0x4843828: malloc (in /usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so)
==50297== by 0x4CA8677: __vasprintf_internal (vasprintf.c:116)
==50297== by 0x4B5D8C1: UnknownInlinedFun (stdio2.h:169)
==50297== by 0x4B5D8C1: g_vasprintf (gprintf.c:340)
==50297== by 0x4B2ABE0: g_strdup_vprintf (gstrfuncs.c:553)
==50297== by 0x4B2AC9C: g_strdup_printf (gstrfuncs.c:583)
==50297== by 0x4C0B49A: UnknownInlinedFun (act-user-manager.c:1895)
==50297== by 0x4C0B49A: act_user_manager_get_user (act-user-manager.c:1994)
==50297== by 0x1134CD: on_user_manager_loaded (im-accounts-service.c:149)
==50297== by 0x4A6100F: g_closure_invoke (gclosure.c:832)
==50297== by 0x4A8E3D5: signal_emit_unlocked_R.isra.0 (gsignal.c:3802)
==50297== by 0x4A7E699: g_signal_emit_valist (gsignal.c:3555)
==50297== by 0x4A7E922: g_signal_emit (gsignal.c:3612)
==50297== by 0x4A6BDC3: g_object_dispatch_properties_changed.lto_priv.0 (gobject.c:1428)
On Ubuntu Kinetic using n-m 1.39.90, after switching from wpa to iwd (1.29) n-m doesn't connect anymore to the wifi. Picking a connection in nm-applet trigger a password dialog with the password correctly remembered, but it needs a manual click on 'connect'. After that connecting again to the AP works without prompting, until a system restart when the first connection prompts again for the password.
journal log when picking a connection to connect
NetworkManager[2750]: <info> [1663270277.2962] device (wlan0): Activation: starting connection 'TestAp1' (c2d91522-a513-452f-a0fe-d75f229167de)
NetworkManager[2750]: <info> [1663270277.2964] audit: op="connection-activate" uuid="c2d91522-a513-452f-a0fe-d75f229167de" name="TestAp1" pid=8971 uid=1000 result="success"
NetworkManager[2750]: <info> [1663270277.2965] device (wlan0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
NetworkManager[2750]: <info> [1663270277.2968] manager: NetworkManager state is now CONNECTING
NetworkManager[2750]: <info> [1663270277.2971] device (wlan0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
NetworkManager[2750]: <info> [1663270277.2984] device (wlan0): state change: config -> need-auth (reason 'no-secrets', sys-iface-state: 'managed')
connection.type: 802-11-wireless
connection.interface-name: wlan0
connection.autoconnect: yes
connection.autoconnect-priority: 0
connection.autoconnect-retries: -1 (default)
802-11-wireless.mode: infrastructure
802-11-wireless.band: --
802-11-wireless.channel: 0
802-11-wireless-security.key-mgmt: wpa-psk
802-11-wireless-security.psk: <hidden>
(shows the correct password using --show-secrets)
Trying to meson dist on master, the tests fail with that error
Bail out! ERROR:../dist-unpack/ModemManager-1.19.1/tools/tests/test-stub.c:138:add_modem_completion_cb: assertion failed (error == NULL): GDBus.Error:org.freedesktop.DBus.Python.ValueError: Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/dbus/service.py", line 715, in _message_cb
retval = candidate_method(self, *args, **keywords)
File "/build/ModemManager/build/meson-private/dist-unpack/ModemManager-1.19.1/tools/test-modemmanager-service.py", line 406, in AddModem
self.modem = Modem(self.bus, add_sim, iccid)
File "/build/ModemManager/build/meson-private/dist-unpack/ModemManager-1.19.1/tools/test-modemmanager-service.py", line 233, in __init__
self.__props = self.__init_default_props()
File "/build/ModemManager/build/meson-private/dist-unpack/ModemManager-1.19.1/tools/test-modemmanager-service.py", line 247, in __init_default_props
props[PM_STATE_FAILED_REASON] = dbus.UInt32(ModemManager.ModemStateFailedReason.UNKNOWN)
File "/usr/lib/python3/dist-packages/gi/module.py", line 155, in __getattr__
setattr(wrapper, value_name, wrapper(value_info.get_value()))
ValueError: invalid enum value: 4
(g-io-error-quark, 36)
What do you mean by
but the outcome of that non-validated,
?
what you wrote sounds like the debian/ubuntu package is doing some undocumented hacks but in fact it's just build using the upstream option for 'Free Kernel Build' (see corresponding section on https://github.com/intel/media-driver/)
Thanks. Could you explain or give details on what you mean by 'this is somehow expected since the it removes blobs that might be needed for certain media processing'? Does it mean they removed support for some formats which they shouldn't and that it should be reported against intel-media-driver?
I'm seeing the issue on a gen10 intel cpu so it's not specific to alderlake...
ok, thanks for the feedback!
The issue is also there on an alderlake config
Interesting finding though, installing intel-media-driver-non-free makes it work correctly
Trying on a video from https://github.com/chthomos/video-media-samples it also fails to play it with the free version of the driver
right, that's the idea
the update you mention seems to be about #1137 (closed) , the fix doesn't resolve the current issue
For Ubuntu we would like to have a way to change the plymouth bgrt logo which doesn't involve regenerating the initramfs (which is slow and creating issue for FDE). We thought that maybe allowing to specify a logo using a kernel parameter would be an option, would that be acceptable from an upstream perspective. The dimensions would need to be identical to avoid having to also require new alignment values but we think that's acceptable. What do you think?
The Ubuntu bug submitter is also on intel but on wayland