FTBFS
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/
# random seed: R02S17152843af8
1..9
# Start of indicator-
dbus-daemon[96717]: [session uid=1000 pid=96717] Activating service name='ca.
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.
dbus-daemon[96717]: [session uid=1000 pid=96717] Activating service name='org.
dbus-daemon[96717]: [session uid=1000 pid=96717] Successfully activated service 'org.gtk.
(indicator-
(indicator-
(indicator-
dbus-daemon[96717]: [session uid=1000 pid=96717] Successfully activated service 'com.canonical.
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-
# 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.
dbus-daemon[96761]: [session uid=1000 pid=96761] Activating service name='org.
dbus-daemon[96761]: [session uid=1000 pid=96761] Successfully activated service 'org.gtk.
(indicator-
(indicator-
(indicator-
dbus-daemon[96761]: [session uid=1000 pid=96761] Successfully activated service 'com.canonical.
[Invalid UTF-8] Bail out! GLib-GObject-
(./indicator-
Trace/breakpoint trap (core dumped)
Error: GDBus.Error:
FAIL: indicator-
==================
1 of 1 test failed
==================
[1] https:/
tags: | added: ftbfs jammy kinetic |
tags: | added: update-excuse |
Changed in indicator-keyboard (Ubuntu): | |
importance: | Undecided → High |
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.