=== themill_ is now known as themill === stgraber_ is now known as stgraber [03:12] Anyone here know off the top of their head where Ubiquity puts its config files? Are there even any config files? === StevenK_ is now known as StevenK [07:54] seb128: might be a bit late now, but if you still have that openssl problem... [07:58] hi, is possible an SRU of backintime 1.3.2-0.1 to jammy for solve a critical issue and few other bugs? https://bugs.launchpad.net/ubuntu/+source/backintime/+bug/1970090/comments/6 [07:59] Launchpad bug 1970090 in backintime (Ubuntu) "Backintime not launching because of python error" [Undecided, Confirmed] [10:47] jbicha: hey! As an uploader of bluebird-gtk-theme, do you feel like this debdiff could be sponsored into Debian: https://paste.ubuntu.com/p/thBHTMCgvt/ – so we could drop the Ubuntu delta? [10:47] schopin, hey, yes, it's https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1958267 , see especially #29 and #56 for details, I would like your opinion on whether you think we should consider doing something similar for Ubuntu [10:47] Launchpad bug 1958267 in wpa (Ubuntu Jammy) "'Connection failed' for WPA Enterprise network (e.g. eduroam)" [High, Confirmed] [10:50] seb128: Oh, I see. The Fedora SHA-1 patches. [10:52] IMHO this is the wrong approach. In this case, we have a context within which basically "weak algorithms don't matter". Assuming that's true, wpa_supplicant should be able to lower the security level to 0 *for this context* [10:53] Of course I have no idea how messy that approach would be, but I'm reluctant to build an escape hatch within libssl. [10:55] schopin, I've no idea either but my guess would be that RH has people knowing wpa better than we do and if decided to go with those openssl theire might be a technical reason the alternative might not be practical [10:56] one alternative would be to simply lower the security level to 0 for wpa but I'm unsure security would like that option [10:57] I'd like to have upstream's opinion on this, too (as in both wpa and openssl) [10:57] kanashiro: are we agreed to drop the SRU for bug 1874719 then? SHould I reject that from the queue? [10:57] Bug 1874719 in corosync (Ubuntu Focal) "[SRU] Use the hostname as the node name instead of hardcoded 'node1'" [Medium, In Progress] https://launchpad.net/bugs/1874719 [10:58] (as well as pacemaker) [11:01] seb128: so, there's https://github.com/openssl/openssl/issues/17662 upstream, but that's still at the design phase. [11:01] Issue 17662 in openssl/openssl "Adding a config option in openssl.cnf to enable SHA-1 signature creation and verification" [Open] [11:04] schopin, I will do an email to the wpa list, thanks for the feedback [11:05] seb128: note that it's not a hard no on shipping the patches :) [11:05] ack [11:06] I'm trying to collect opinions at this point to see what we can do [11:06] I feel like that's an issue we need to address in the LTS because today there are quite some users who can't connect to their wifi due to the issue [11:07] oh for sure! [11:29] hey folks, is it mandatory to sign up for the snapcraft dev account to build a custom image even if I don't want to publish it [11:46] lxsameer, ubuntu-image does not require authntication [11:46] +e [11:47] lxsameer, likewise you can build your own kernel and gadget snaps for th image locally witout auth ... [11:48] ogra: cool thank you [11:48] lxsameer, but to log in to the booted image you will need an account where the image can pull your ssh key from ... the account here is only used as central key storage [11:49] ogra: oh wow, is there any way to avoid that? [11:49] not easily [11:49] I just want a bootable ubuntu live image with several extra packages [11:49] (there are ways through hacks via clud.init (not recommended for production), you can read up on it at forum.snapcraft.io [11:49] ) [11:50] oh, i assumed you are after UbuntuCore, talking about snapcraft ... [11:51] ogra: i don't know what exactly ubuntucore is. [11:51] is there any other way beside ubuntu-image? [13:10] slyon: done, thanks! https://tracker.debian.org/pkg/bluebird-gtk-theme [13:10] jbicha: great, thank you very much! [14:36] schopin, http://lists.infradead.org/pipermail/hostap/2022-May/040563.html FYI [14:37] seb128: thanks for the link :) [14:37] schopin, let's see what they say [14:44] anybody suddenly having audio issues? I see no inputs nor outputs after an update today :-/ [14:47] icey: what version of Ubuntu are you using? [14:51] jbicha: kinetic ;-) [14:51] slyon: any chance we could get systemd-repart enabled in ubuntu? we've enabled it in debian late last year [14:51] icey: are you using -proposed updates? [14:51] it shouldn't pull any new dep, apart from fdisk for the test suite [14:52] in debian we just ship it in the main package [14:52] jbicha: no - think it'll be resolved with proposed? [14:52] bluca there is lp: #1897932 for repart [14:52] Launchpad bug 1897932 in systemd (Ubuntu) "systemd-repart not packaged" [Medium, Triaged] https://launchpad.net/bugs/1897932 [14:53] icey: I don't know. We are switching the default audio server to PipeWire and some things likely won't work as well until the transition is complete [14:54] "well" :-P [14:54] oh-well, I'll be portable for a while anyways after tomorrow [14:55] icey: are you using bluetooth for audio? [14:56] icey, do you have pipewire-pulse installed? [14:56] thanks ddstreet, will ping there too [14:56] yes to pipewire-pulse, no to bluetooth [14:56] icey, try installing wireplumber [14:56] usd speakerphone, as well as onboard headphone jack - none show up as devices [14:57] bluca: hey! sure. that should be more or less an automatic thing, once we merge systemd v251 from Debian. My collegue enr0n will most probably take care of that this cycle. [14:57] fdisk is already in Ubuntu main, so that's not a problem. [14:57] nothing seems to change, `killall pipewire pulseaudio pipewire-pulse; alsactl kill rescan` didn't change anything [14:58] So if it's in Debian, it will most probably land in kinetic later this cycle [14:58] nice, thanks [15:00] anyways, dropping for the day, maybe I'll figure it out tomorrow, thanks folks! [15:00] icey, bye [15:01] icey, try uninstalling pipewire-media-session and pulseaudio in case tomorrow [15:11] icey, thanks for the ping btw, it made me realize we needed to revert the chantges to pipewire-media-session we had to disable audio by default, which probably has to do with your issue [15:11] which I did now in https://launchpad.net/ubuntu/+source/pipewire-media-session/0.4.1-2ubuntu2 [15:11] jbicha, ^ fyi === jdstrand_ is now known as jdstrand [15:23] I seem to recall somebody here asking about this being updated for Kinetic. It has been done now. http://qa.ubuntuwire.com/ftbfs/ [15:34] ahasenack, enr0n: That package passed when added to big_packages https://autopkgtest.ubuntu.com/packages/golang-github-valyala-gozstd/kinetic/s390x [15:35] yay [15:35] thanks [15:36] rbasak, sorry for the delay, re corosync SRU, I think we can reject it for now until we sort this out with the Debian maintainer [16:28] kanashiro: thanks - rejected for now [17:29] kanashiro: Can we remove the section of the Release Notes which points to bug 1964025 now? [17:29] Bug 1964025 in vagrant (Ubuntu Kinetic) "Do not support OpenSSL 3" [Undecided, Triaged] https://launchpad.net/bugs/1964025 [17:30] PSA: telegraf is FTBFSing on ppc64el/riscv64 due to a golang issue, this is on my radar and I'll work on it soon [18:17] seb128: don't think I want to remove ubuntu-desktop just yet ;-) https://pastebin.ubuntu.com/p/DjNcbvHS5W/ [18:31] bdmurray, sure [18:31] do you want me to do it? [18:49] kanashiro: that'd be great [19:02] bdmurray, done