[11:14] <seb128> cpaelzer, Failed to open module: /usr/lib/x86_64-linux-gnu/qemu/ui-gtk.so: undefined symbol: get_relocated_path
[11:15] <seb128> cpaelzer, somehow the qemu depends are not correct there, probably not tight enough (it's an hirsute system slightly outdated)
[11:16] <seb128> cpaelzer, it was failing on missing win32_kbd_set_window, I updated qemu-system-gui and now get that error
[11:18] <cpaelzer> seb128: interesting
[11:19] <cpaelzer> seb128: let me try to recreate - can you post a list of packages you have installed?
[11:19] <seb128> cpaelzer, https://paste.ubuntu.com/p/6bYy2gNtbM/
[11:20] <cpaelzer> thanks seb128, but I meant all of them, a full -l
[11:20] <seb128> cpaelzer, I upgraded qemu-system-x86 which required to remove -kvm (which is why I hadn't the updates yet, I didn't know if that was ok) which updated a bunch of binaries and now it starts
[11:21] <seb128> cpaelzer, https://paste.ubuntu.com/p/8t8jvGgRvP/ fixed it
[11:22] <seb128> the qemu binaries should probably be on the same version and not allow partial upgrades
[11:23] <seb128> cpaelzer, I had qemu-system-x86 outdated because it required to remove -kvm to update but qemu-system-common/data/gui were on a newer version
[11:26] <cpaelzer> qemu-kvm is only a virtual package nowadays, but even in the past didn't contain any real binaries
[11:26] <cpaelzer> from your logs I bet it is the mismatch of qemu-system-x86  to qemu-system-gui
[11:30] <cpaelzer> That is already an = 1:5.0-5ubuntu9 and such, but only a recommends no Depends
[11:30] <cpaelzer> as some people want the UI and some desperately try to avoid all the further dependencies that come with it
[11:31] <cpaelzer> maybe we need a reverse breaks to ensure this cobination will never be allowed?
[11:33] <seb128> cpaelzer, is it normal that qemu-system-gui has no depends on any other qemu package? it only ships some .so files so it's probably not useful by itself?
[11:34] <seb128> if it was depending on e.g qemu-system-x86 it could have a versioned depends
[11:34] <cpaelzer> it contains plugins extending the features of qemu-system-*
[11:35] <cpaelzer> it does nothing on its own
[11:36] <seb128> so it should probably depends on qemu-system-<something>?
[11:37] <seb128> but yeah, another way would be to qemu-system-x86 Breask -gui (>> current-version)
[11:37] <seb128> Breaks
[11:37] <cpaelzer> yeah this will look a bit awkward as it becomes useful with "either of" so probably a long list with |
[11:37] <seb128> anyway, probably not an important issue, we don't support partial upgrades
[11:37] <seb128> I just got bitten by doing an 'upgade' instead of 'dist-upgrade'
[11:38] <seb128> and I had -kvm around which blocked some binaries
[11:38] <seb128> cpaelzer, thanks for the replies!
[11:38] <cpaelzer> it is a useful report to tighten things a bit
[11:38] <cpaelzer> thank you!
[11:39] <seb128> cpaelzer, do you want a launchpad report so the conversation doesn't get lost?
[11:39] <cpaelzer> no, I'll create one if I need it
[11:41] <seb128> k, thx
[12:37] <cpaelzer> seb128: FYI https://salsa.debian.org/qemu-team/qemu/-/merge_requests/17
[12:54] <seb128> cpaelzer, thanks, great summary of the issue and the change makes sense
[15:29] <seb128> could someone from the SRU team comment on https://bugs.launchpad.net/ubuntu/+source/yaru-theme/+bug/1907844 , there yaru team asked some questions on whether some UI fixes would be acceptable for SRU or not
[15:29] <seb128> sil2100, ^
[15:46] <rbasak> I'm not really sure. Has the SRU team ever opined on the stable release acceptability for visual changes that aren't obviously bugs?
[15:47]  * rbasak would want to consult with the wider team
[17:47] <jdstrand> rick_h: hey, I noticed that my esm user is my canonical address, but that is not a valid email (my LP account is the same though). do you have a pointer as to how to fix it and if not, where to file a bug?
[18:09] <xnox> jdstrand:  maybe #canonical-sysadmin channel here on freenode, and/or community rt@ubuntu.com can help? => although that's mostly IS, and I don't know if they manage the esm/ua stuff.
[22:36] <tdaitx> is there a specific process to join/apply for membership in ubuntu-sponsors? as I indirectly "own" the team (through core-dev) I can only 'add' myself in directly with no review by the existing members, there's no option to 'request' membership
[22:40] <xnox> tdaitx:  i think there is. cause one needs to know what to do with it, which reports to monitor ects.
[22:40] <xnox> tdaitx:  can't rmemeber who managed it. like bdmurray?
[22:41] <tdaitx> I couldn't find any wiki entry documenting how to apply, neither on the team description
[22:41] <tdaitx> https://wiki.ubuntu.com/SponsorshipProcess only says "Any Ubuntu developer who is interested in acting as a sponsor is welcome to apply for membership in the appropriate team."
[22:43] <bdmurray> I do seem to be an admin