FTBFS

Bug #1968333 reported by Alexandre Ghiti
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
indicator-keyboard (Ubuntu)
New
High
Unassigned
Kinetic
Won't Fix
High
Unassigned

Bug Description

All archs have build from 2020, except riscv64 which does not have any available: I tried to rebuild this package in my PPA [1] and it fails. I fixed all vala compilation errors that I was seeing locally (but not in the build logs above) and fixed an outdated path to dconf-service: you can find the diff attached.

But then tests fail and I fail to fix this:

make check-TESTS
make[5]: Entering directory '/home/ubuntu/indicator-keyboard/indicator-keyboard/tests'
# random seed: R02S17152843af8958ff21f0460bf77a5d11
1..9
# Start of indicator-keyboard-service tests
dbus-daemon[96717]: [session uid=1000 pid=96717] Activating service name='ca.desrt.dconf' requested by ':1.1' (uid=1000 pid=96722 comm="gsettings set org.gnome.desktop.input-sources curr" label="unconfined")
dbus-daemon[96717]: [session uid=1000 pid=96717] Successfully activated service 'ca.desrt.dconf'
dbus-daemon[96717]: [session uid=1000 pid=96717] Activating service name='com.canonical.indicator.keyboard' requested by ':1.0' (uid=1000 pid=96716 comm="./indicator-keyboard-tests " label="unconfined")
dbus-daemon[96717]: [session uid=1000 pid=96717] Activating service name='org.gtk.vfs.Daemon' requested by ':1.4' (uid=1000 pid=96735 comm="/home/ubuntu/indicator-keyboard/indicator-keyboard" label="unconfined")
dbus-daemon[96717]: [session uid=1000 pid=96717] Successfully activated service 'org.gtk.vfs.Daemon'

(indicator-keyboard-service:96735): IBUS-CRITICAL **: 12:09:45.004: ibus_bus_call_sync: assertion 'ibus_bus_is_connected (bus)' failed

(indicator-keyboard-service:96735): IBUS-CRITICAL **: 12:09:45.005: ibus_bus_call_sync: assertion 'ibus_bus_is_connected (bus)' failed

(indicator-keyboard-service:96735): IBUS-CRITICAL **: 12:09:45.005: ibus_bus_call_sync: assertion 'ibus_bus_is_connected (bus)' failed
dbus-daemon[96717]: [session uid=1000 pid=96717] Successfully activated service 'com.canonical.indicator.keyboard'
current = 2
output = "uint32 2
"
A connection to the bus can't be made
# GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created
# GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created
# GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created
# GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created
# GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created
# GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created
ok 1 /indicator-keyboard-service/activate-input-source
# GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created
# GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created
# GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created
# GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created
# GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created
# GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created
# GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created
# GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created
# GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created
# GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created
dbus-daemon[96761]: [session uid=1000 pid=96761] Activating service name='com.canonical.indicator.keyboard' requested by ':1.0' (uid=1000 pid=96716 comm="./indicator-keyboard-tests " label="unconfined")
dbus-daemon[96761]: [session uid=1000 pid=96761] Activating service name='org.gtk.vfs.Daemon' requested by ':1.1' (uid=1000 pid=96763 comm="/home/ubuntu/indicator-keyboard/indicator-keyboard" label="unconfined")
dbus-daemon[96761]: [session uid=1000 pid=96761] Successfully activated service 'org.gtk.vfs.Daemon'

(indicator-keyboard-service:96763): IBUS-CRITICAL **: 12:09:46.792: ibus_bus_call_sync: assertion 'ibus_bus_is_connected (bus)' failed

(indicator-keyboard-service:96763): IBUS-CRITICAL **: 12:09:46.793: ibus_bus_call_sync: assertion 'ibus_bus_is_connected (bus)' failed

(indicator-keyboard-service:96763): IBUS-CRITICAL **: 12:09:46.793: ibus_bus_call_sync: assertion 'ibus_bus_is_connected (bus)' failed
dbus-daemon[96761]: [session uid=1000 pid=96761] Successfully activated service 'com.canonical.indicator.keyboard'
[Invalid UTF-8] Bail out! GLib-GObject-FATAL-WARNING: g_object_notify: object class 'Service' has no property named '\xc0[u\x1d\x9fU'

(./indicator-keyboard-tests:96716): GLib-GObject-WARNING **: 12:09:46.826: g_object_notify: object class 'Service' has no property named '\xc0[u\u001d\x9fU'
Trace/breakpoint trap (core dumped)
Error: GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message recipient disconnected from message bus without replying
FAIL: indicator-keyboard-test
==================
1 of 1 test failed
==================

[1] https://launchpad.net/~alexghiti/+archive/ubuntu/riscv/+sourcepub/13417179/+listing-archive-extra

Revision history for this message
Alexandre Ghiti (alexghiti) wrote :
description: updated
Jeremy Bícha (jbicha)
tags: added: ftbfs jammy kinetic
tags: added: update-excuse
Changed in indicator-keyboard (Ubuntu):
importance: Undecided → High
Revision history for this message
Jeremy Bícha (jbicha) wrote :

I'm doing an upload now to ignore the build test failures since I need to rebuild indicator-keyboard to complete the gnome-desktop 43 library transition.

Build tests are a very useful QA element so please try to get these tests working again this release cycle.

Revision history for this message
Utkarsh Gupta (utkarsh) wrote :

Ubuntu 22.10 (Kinetic Kudu) has reached end of life, so this bug will not be fixed for that specific release.

Changed in indicator-keyboard (Ubuntu Kinetic):
status: New → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.