[06:47] <luna__> There was no Daily or Canary builds of 22.10 yesterday, any specific reason?
[06:51] <luna__> got an answer from @seb128 mirrors was down yesterday
[10:32] <Habbie> hello! latest systemd-resolved on ubuntu:kinetic in Docker fails to install because it can't overwrite/move /etc/resolv.conf - because Docker does not allow that
[10:32] <Habbie> I looked in launchpad but did not see a ticket
[10:32] <Habbie> has anybody perhaps already looked into this problem?
[11:23] <athos> Habbie: this is an interesting one :) Would you mind filing a bug in https://bugs.launchpad.net/ubuntu-docker-images ?
[11:24] <athos> What is happening there is that /etc/resolv.conf is a special file in docker containers (it is mounted in the running container)
[11:27] <athos> now, during systemd-resolved installation, dpkg tries to create a link of the file (note that overwritting the file is not an issue), which fails because we cannot create hard links across mounts
[11:34] <Habbie> indeed, i was aware of that docker property
[11:34] <Habbie> will file
[11:35] <Habbie> (was not aware of the separate project)
[11:39] <athos> I am unsure if that should be the proper place to file it, since right now I am unsure about where a fix should go (could be dpkg, systemd, docker, ...)
[11:39] <Habbie> same
[11:39] <Habbie> i also couldn't figure out how 'apt install devscripts' pulled resolved in
[11:39] <Habbie> --no-install-recommends stops that
[11:40] <athos> But I'd say, let's bring this to the folks building the images, and we can expand from there :)
[11:40] <Habbie> (i don't need resolved - i just need devscripts)
[11:40] <Habbie> yes
[11:40] <athos> let me know when you have a bug!
[11:41] <athos> Habbie: oh, I was wondering why you needed systemd-resolved at all in a docker image, now I get it
[11:41] <Habbie> i'll note that in the ticket too
[11:42] <Habbie> https://bugs.launchpad.net/ubuntu-docker-images/+bug/1988300
[11:42] <ubottu> Launchpad bug 1988300 in Ubuntu Docker Images "systemd-resolved in kinetic image tries to replace resolv.conf" [Undecided, New]
[11:44] <Habbie> athos, ^
[11:49] <athos> btw, I was about to suggest that not installing recommended packages would be a workaround for you :) I see you added that to the bug! thanks
[11:52] <Habbie> yes
[11:52] <Habbie> currently testing that in my CI over all debian/ubuntu-variants
[11:52] <Habbie> because it would not be a surprise if that dropped something i did need
[12:08] <Habbie> it worked :)
[13:24] <luna__> and no new images today as the Canonical datacenter in London has sad network today
[19:15] <nteodosio> nicolasbock: A normal apt upgrade, not a dist-upgrade, correct?
[19:20] <nicolasbock> Well it was a dist upgrade
[19:20] <nicolasbock> Let me paste the logs 
[19:23] <tomreyn> is there some place to read the first part of your conversation? i *did* read the part in #ubuntu
[19:23] <jbicha> I missed the earlier discussion too
[19:25] <tomreyn> (don't worry if you'd just like to sort it out between yourselves, though.)
[19:25] <nicolasbock> Sorry tomreyn , we switched channels. I ran a `dist-upgrade` yesterday which among other packages upgrade `gnome-shell`. Since then `gdm3` throws an error message.
[19:25] <nicolasbock> It's just a grayish screen with a general message stating that "something went wrong"
[19:25] <nicolasbock> I have logs and will paste those in a second
[19:26] <jbicha> when was the last time you upgraded that machine?
[19:26] <nicolasbock> The day before yesterday
[19:27] <nicolasbock> I typically upgrade every day at least once
[19:27] <nicolasbock> However I do not log out of gnome every day
[19:27] <nicolasbock> Only if I am told that a reboot is required
[19:27] <nicolasbock> This might have broken earlier and I didn't notice
[19:28] <jbicha> we did a big upgrade of evolution-data-server stuff that landed around Monday evening. Before that, gnome-shell 43 Beta landed on Thursday of last week
[19:29] <nicolasbock> evolution-data-server is still being kept back
[19:29] <nicolasbock> But the 43-beta is installed
[19:29] <nicolasbock> Jee, that log is pretty long
[19:29] <nicolasbock> Can't I upload a file to paste.ubuntu.com?
[19:29] <jbicha> that's your problem. You definitely need evolution-data-server 43 to be updated
[19:30] <jbicha> It's not possible to run apps or services that directly link against both libsoup2 and libsoup3 simultaneously
[19:30] <nicolasbock> How should I do that upgrade?
[19:30] <nicolasbock> A regular upgrade keeps it back
[19:30] <jbicha> you should do a   sudo apt dist-upgrade
[19:30] <nicolasbock> Ad is a dist-upgrade
[19:31] <nicolasbock> Right now `evolution-data-server gnome-calendar gnome-clocks gnome-initial-setup libgweather-4-0` are being held back by a dist-upgrade
[19:31] <jbicha> please post a paste of the exact error
[19:32] <nicolasbock> https://paste.ubuntu.com/p/76D6nQy2Tw/
[19:32] <jbicha> I probably should have added more Breaks relationships to the evolution-data-server transition. What I added was enough if you were able to upgrade everything
[19:32] <tomreyn> did you actually mean to do a release upgrade to kinetic, though, or did you actually do that, or were you already on kinetic (on purpose)?
[19:32] <jbicha> sudo apt install evolution-data-server
[19:34] <nicolasbock> https://paste.ubuntu.com/p/z5H6nVWPN8/
[19:34] <nicolasbock> tomreyn: I am already on kinetic
[19:34] <nicolasbock> And yes, on purpose :)
[19:35] <jbicha> sudo apt update; sudo apt dist-upgrade
[19:36] <jbicha> the version of gnome-settings-daemon available in kinetic is 43~beta-1ubuntu3
[19:36] <nicolasbock> Same thing jbicha 
[19:36] <jbicha> sudo apt install gnome-settings-daemon
[19:37] <nicolasbock> https://paste.ubuntu.com/p/Cxt37GzyWk/
[19:37] <jbicha> you shouldn't be using Pop!_OS repos on Ubuntu
[19:38] <nicolasbock> Ok, let me disable those
[19:38] <jbicha> sudo apt install --mark-auto gnome-settings-daemon gnome-settings-daemon-common/kinetic
[19:38] <jbicha> just disabling isn't enough. You need to get back to the Ubuntu versions
[19:38] <nicolasbock> https://paste.ubuntu.com/p/XHSFJKPZkg/
[19:39] <arraybolt3[m]> nicolasbock: If this is Pop!_OS that you're trying to morph into Ubuntu Kinetic... you are going to have a lot more work to do than just disabling repos.
[19:39] <jbicha> sudo apt install --mark-auto gnome-settings-daemon/kinetic gnome-settings-daemon-common/kinetic
[19:39] <arraybolt3[m]> You'll probably want to just download a Kinetic daily ISO and install from scratch. (And if you can't do that because this is a production system, then you should probably wipe everything and install a stable version of Ubuntu.)
[19:39] <jbicha> ppa-purge is great for disabling PPAs & trying to get back to baseline. The PPA needs to be enabled first. I've never tried if ppa-purge works for other apt repos
[19:39] <nicolasbock> That last one worked jbicha 
[19:40] <nicolasbock> arraybolt3[m]: Hmm, I am starting to realize that :/
[19:40] <jbicha> that /kinetic suffix (or whatever series of Ubuntu you are on) is really useful for trying to get back to the baseline if you know exactly which packages you need to change
[19:40] <nicolasbock> I didn't know that trick jbicha 
[19:40] <jbicha> If you're using Pop!_OS, you're on your own. Pop!_OS wouldn't be able to adapt to our changes that quickly
[19:41] <nicolasbock> I wasn't really on Pop!_OS but was using their power manager only
[19:41] <nicolasbock> Which I guess I'll need to stop
[19:41] <jbicha> nicolasbock: are you using a PPA for that?
[19:41] <nicolasbock> Yes theirs
[19:41] <jbicha> I encourage you to run ppa-purge on their PPA (like I said, it needs to be enabled first)
[19:42] <nicolasbock> For a while I was using my own PPA and built packages from theirs for kinetic
[19:42] <nicolasbock> Ok will do that jbicha 
[19:42] <nicolasbock> I'll try gmd3 now
[19:42] <jbicha> ideally, they would get their improvements upstream into Ubuntu (perhaps even into Debian) but honestly, they haven't done much of that yet
[19:43] <jbicha> perhaps they see some competitive advantage to have unique fixes in their repos. Or perhaps they're really busy. Or perhaps they just don't see the benefit yet
[19:47] <jbicha> your system could have been broken for a while. We did the gnome-desktop transition 3 weeks ago
[19:48] <jbicha> but maybe it didn't break good until this week's evolution-data-server transition
[19:52] <nicolasbock> Thanks jbicha for your help!
[19:52] <nicolasbock> It's working again
[19:53] <nicolasbock> I purged all of the POP!_OS packages
[19:53] <nicolasbock> I agree, it would be nice if they upstreamed their changes
[19:54] <nicolasbock> I think I didn't notice the breakage until I rebooted the system
[19:54] <jbicha> the power management thing is interesting because GNOME went a different way with power-profiles-daemon
[19:54] <nicolasbock> The one thing I care about are their charging thresholds
[19:54] <nicolasbock> You can set a max chanrge on your laptop
[19:54] <jbicha> is it a system76 computer?
[19:54] <nicolasbock> Yes
[19:56] <jbicha> you could file an issue with system76/pop about the conflict. But honestly, you might just need to stick with distro releases System76 supports (so no Ubuntu alpha for you)
[19:56] <nicolasbock> Yeah :/ 
[19:57] <nicolasbock> They seem to be moving away from a more vanilla Ubuntu experience to doing their own thing
[19:58] <nteodosio> Ah, glad to see this was solved already! Going forward, it should be a good idea to mention non-official sources upfront since many times they are the cause of the issue.
[20:04] <nicolasbock> Yes good point
[20:12] <nicolasbock> OMG it's nice to be on Gnome after having to use KDE for a while :)
[21:06] <enigma9o7[m]> Apperantly epiphany is testing extensions, I hope when it's released to regular beta, there'll be an extension to use the gnome extensions website integration.
[21:06] <enigma9o7[m]> It has seemed odd to me that site would tell me it doesnt detect gnome when i was using gnome web!
[21:24] <jbicha> enigma9o7[m]: yeah, it doesn't look like the Firefox extension works for Epiphany yet. Also Epiphany 43 currently disables extensions by default.