[00:56] <dabbler> How can I see what repo an installed package was installed from?
[00:58] <ravage> apt policy <packagename>
[00:59] <dabbler> ravage: thanks
[00:59] <dabbler> Why doesn't the rsync in jammy support --crtimes?
[01:12] <ravage> dabbler, it does not exist in the POSIX standard
[01:13] <ravage> some filesystems support and i there is a patch for rsync somewhere. but its just not a thing on linux
[01:13] <ravage> https://www.baeldung.com/linux/get-file-creation-date
[01:13] <sarnold> I thought ext4 had support for it?
[01:14] <sarnold> oh wow zfs xfs btrfs and jfs too? neat
[01:42] <dabbler> ravage: why would rsync need a patch to support it? It's an option built into it, as long as it's compiled with the support
[01:44] <dabbler> Even if an fs didn't support it, wouldn't it just fail at runtime?
[01:45] <dabbler> The POSIX standard is a floor for functionality, not a ceiling
[01:47] <usuario> #linux mint
[01:48] <usuario> #linux-mint
[01:48] <usuario> ops
[01:48] <Eickmeyer> !mint
[02:06] <Square> is there no way of restarting Gnome mid session like in ubuntu 20.04 in 22.04? Alt+F2 -> R
[02:07] <Square> ...or is there some alternative way?
[02:17] <Windy> anyone using LXC on ubuntu 22.04?  i installed it from apt, but can't start a container following the most basic directions.
[02:17] <SleePy> https://gist.github.com/jdarwood007/db04351b387ba3616393078a49de7385  Well that sucks...  Seems in the middle of updating systemd, the system locked up.  Anyone know if this a known issue?  I will have to get a monitor and live USB on it tomorrow to fix it
[02:18] <Windy> lxc-checkconfig looks fine except "Cgroup v1 systemd controller: missing" and "Cgroup v1 freezer controller: missing" but it's supposed to be v2 compatible anyway
[02:18] <sarnold> SleePy: eww
[02:19] <sarnold> SleePy: hmm, that kind of looks like the amd64 version is being replaced by the i386 version???
[02:20] <sarnold> Windy: I saw this bug report recently about lxc https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1990849 .. dunno if it's exactly related or not, but it might look familiar
[02:20] <SleePy> sarnold: That would explain it.. But why...
[02:21] <Windy> sarnold: hmm, doesn't look related,but tahnks.
[02:21] <sarnold> SleePy: I've seen guitar hero 5 or guitar pro 5 or whatever it was installations do *stupid* things like uninstall sudo .. did you perhaps recently add a new ppa or something?
[02:21] <sarnold> Windy: dang :(
[02:21] <SleePy> sarnold: Yup, I see that now in the output.  It was trying to put the i386 in there.
[02:23] <SleePy> I had a few PPAs.. I can't remember.  The server is in my office and I don't feel like putting a monitor on it tonight.  I'm guessing since I lost pings, I need to get a live usb going as well and it won't boot.  Although that helps to see.  Maybe if I can get a live usb, I can chroot and reconfigure systemd with x64 and maybe it will come back..
[02:23] <SleePy> No plex for me tonight..
[02:23] <Windy> i'm trying the very basic commands listed here for LXC: https://ubuntu.com/server/docs/containers-lxc and it doesn't work past 'lxc-create', i can't 'lxc-start'.
[02:24] <sarnold> SleePy: yeah, a live image feels likely to be necessary to me
[02:28] <SleePy> Yea.  I had it do a similar thing when I did a upgrade from 20.04.5? to 22.04.1.  I had chroot fun mostly because after I got the chroot going, it would get a IP but it wouldn't do DNS resolution.  I can't remember what i had to fight to get it to do that.
[02:33] <sarnold> hah, my 18.04 -> 22.04 upgrade went similar
[02:33] <sarnold> it seemed like it was going great right up until the final reboot, when it didn't come back online :(
[02:34] <sarnold> lucky for me it was just in another room rather than in a datacenter somewhere, but still :/
[02:35] <SleePy> Yea. Mines in my office at the other end of the house.  But its late, just my plex box and I can put a monitor on it tomorrow and fix it up.  No need to rush to fix it
[02:36] <SleePy> If it was an important box.  I would get a IPMI interface on it...
[02:41] <sarnold> heh, yeah.. I've got one, I did *something* with it way back when, and now I don't know the username/password for the thing. great planning!
[04:37] <user___> hello all
[04:37] <user___> i just installed ubuntu on a partition alongside an existing kde neon install
[04:37] <user___> but now i can't boot into neon at all
[04:37] <user___> any advice here?
[05:01] <alkisg> user___: what's the output of this command? sudo lsblk --fs | nc termbin.com 9999
[08:09] <dabbler> So what keeps Linux programs from setting the file creation/birth timestamps that the modern Linux filesystems support? Lack of kernel support?
[09:54] <fabtab> Is it possible to install libc6_2.35 on ubuntu 22.04/wsl I have version 2.31
[10:02] <rob0> fabtab: definitely maybe! Why do you think you need that?
[10:03] <fabtab> I was trying iperf3 3.11, It won't let me because it is asking for for version 2.35
[10:04] <fabtab> via dpkg
[10:04] <fabtab> it doesn't matter if it breaks anything it's just wsl and can just re-install in a jiffy!
[10:05] <rob0> what version does "apt install iperf3" get you?
[10:05] <fabtab> 3.9
[10:05] <rob0> btw there is also iperf3 for windows
[10:06] <fabtab> no sorry 3.7.3
[10:06] <fabtab> Yes I have version 3.10.1 for that
[10:07] <fabtab> Get spurious results etc
[10:07] <rob0> what particular feature was added that you need?
[10:07] <fabtab> well windows doesn't show the retr on windows
[10:07] <rob0> You might have to get source code and compile it. I've never tried that on ubuntu/wsl.
[10:08] <fabtab> rob0: none, I was just curious!
[10:08] <rob0> Well, rule of thumb, don't ever try to replace your libc :)
[10:09] <fabtab> lol, I get the picture
[10:09] <fabtab> :)
[10:10] <fabtab> rob0: I'll stick with 3.9 via dpkg and wait then
[10:10] <rob0> It's like what the genie in the Disney movie "Aladdin" (Robin Williams) said about bringing back the dead. "It isn't pretty." :)
[10:11] <lotuspsychje> !backports
[10:16] <fabtab> I'm taking a look
[12:14] <keiserr> hi, if i am extracting a folder from a tar.gz file, and i need to tar.gz the extracted folder, I could do it in 2 steps yes. But I was wonder if this can be made into a one liner. when i am extracting using this  tar -xzvf sample.tar.gz $i, is it possible to instead forward this to stdout and then pipe it to a tar -c and gzip directly?
[12:16] <Habbie> keiserr, look at the -O flag
[12:19] <geirha> it's technically possible, but I don't think the tar command has any options for it
[12:20] <keiserr> thanks Habbie , with the -O i believe i can experiment a bit with that.
[12:20] <Habbie> oh, wait, this is about repacking? then -O won't do the job, at least not easily
[12:20] <Habbie> that you can
[12:50] <BluesKaj> Hi all
[12:52] <fabtab> So I updated to Ubuntu 22.10 installed iperf3 via dpkg to v3.11 but iperf3 -v shows Version 3,9
[12:53] <ravage> !next | fabtab
[12:54] <fabtab> Ok thanks
[12:55] <thatfatpat> Hey there, I encountered a crash in gnome-shell on Ubuntu 22.04 which I believe was fixed by mutter in 43.rc. However, this bug can directly and realistically result in user data loss, and thus I believe should be considered a high-impact bug. I sent a crash report to Ubuntu but I believe I have more information that could be useful for the
[12:55] <thatfatpat> investigation and shorten the time to resolution. Could someone please point me in the direction of where I should share that information?
[12:55] <Habbie> !info iperf kinetic
[12:56] <ravage> thatfatpat, run "ubuntu-bug gnome-shell"
[12:56] <fabtab> ./join #ubuntu-next
[12:58] <thatfatpat> ravage I did that already, but I would like to add additional information on reproducing the bug and stress why I believe it should be classified as high-impact. Is there a place that's appropriate for such posts?
[12:59] <ravage> thatfatpat, what is your launchpad bug id?
[13:00] <thatfatpat> Would that be the user id from /var/lib/whoopsie/whoopsie-id?
[13:00] <ravage> no
[13:00] <ravage> it is the id you get assiged after the ubuntu-bug process
[13:01] <ravage> submitting a crash report is not reporting a bug to launchpad
[13:01] <thatfatpat> Oh that's helpful :)
[13:01] <thatfatpat> I'll read up on the process for reporting a bug to Launchpad. Thanks!
[13:02] <ravage> the process is "ubuntu-bug gnome-shell"
[14:08] <GSMarquis> Where is the battery scale kept? As if I wanted to rescale what upower is reporting to gnome.
[14:56] <meandrain> hi, what is the difference between `apt search` and `apt-cache search` ?
[14:59] <Reventlov> Hello. At which point ubuntu mounts the casper-rw partition when persistent is present on the kernel CLI ?
[14:59] <Reventlov> Is that done with a systemd service ? (i'd like to execute a few things before it is mounted)
[15:05] <ogra> Reventlov, casper is an initrd script ... so i'd assume it operates from the initrd
[15:08] <Reventlov> ack
[15:15] <rijndael> .
[15:20] <rijndael> @anyone who is directly involved with the ubuntu source code and releases;
[15:21] <rijndael> with a mq-deadline schedule, this renders the nice/ionice tools useless. what is the approach now for handling schedule priorities for processes? such as for throttling IO
[15:21] <rijndael> scheduler*
[15:30] <jhutchins> rijndael: Sounds like you have a question for kernel.org
[15:30] <jhutchins> rijndael: Ubuntu does not write it's own kernel.
[15:31] <rijndael> jhutchins, I will then take my question there, thank you, but doesn't ubuntu choose/compile it's kernel and decide what goes in it?
[15:31] <rijndael> actually. being debian derived, it might not
[15:32] <rijndael> I'll ask in debian as well to be sure
[15:32] <jhutchins> rijndael: You can certainly choose your kernel and configure it to your liking.
[15:32] <jhutchins> rijndael: Be sure to confirm that the behavior you're asking about is the same in Debian.
[15:32] <rijndael> I'm more concerned with what comes/is offered on the website by default.
[15:33] <jhutchins> rijndael: Also compare kernel versions between the two.
[15:33] <rijndael> e.g out of the box..
[16:01] <ogra> rijndael, ubuntu does its own kernels, we do not use debians, the kernel team can be reached in the #ubuntu-kernel channel or throug their mailing list https://lists.ubuntu.com/mailman/listinfo/kernel-team
[17:32] <Apachez> wtf!?  "The following security updates require Ubuntu Pro with 'esm-apps' enabled"
[17:33] <Apachez> https://ubuntu.com/pro     http error 404
[17:33] <Habbie> where did you find that url?
[17:33] <Apachez> when doing apt-get update just now
[17:34] <Habbie> did it print that url?
[17:34] <ogra> Apachez, did you something really bad, like enabling -proposed permanently on your system ?
[17:34] <ogra> (the ubuntu pro stuff is only in -proposed and should definitely not be installed yet)
[17:35] <Apachez> https://pastebin.com/iPaEV44u
[17:35] <Apachez> running it again its gone
[17:36] <Apachez> and it didnt install the packages named in pro
[17:37] <Habbie> i hope the page is "not there yet", and not "was there but is now gone even though many installs might print the message"
[17:37] <Apachez> ogra: been using proposed for some years without any ads in my apt so far
[17:37] <Apachez> deb http://se.archive.ubuntu.com/ubuntu/ jammy-proposed universe restricted main multiverse
[17:37] <Apachez> Habbie: its a 404
[17:37] <Apachez> 404: Page not found
[17:37] <Apachez> Can’t find page for: pro
[17:37] <ogra> Apachez, well, you should only use proposed if a dev asks you to test a fix .. it is not for permanent use
[17:38] <Apachez> ogra: never seen such recommendation previously
[17:38] <ogra> Apachez, it holds pre-release and beta software ... like the one you are currently playig with
[17:38] <Apachez> so this pro ads will hit everybody now?
[17:38] <ogra> i'm pretty sure the UI option that lest you enable proposed has a proper warning
[17:38] <Apachez> not much into any UI options
[17:39] <ogra> it is a test package that is not released to user
[17:39] <ogra> s
[17:39] <Apachez> its stored in /etc/apt/sources.list
[17:39] <ogra> well, you enabled it somehow
[17:39] <Apachez> even with the proposed line removed I get this:
[17:39] <ogra> ubuntu does nto enable it by default since it is only for temporary debugging use
[17:39] <Apachez> https://pastebin.com/XnBsDAzM
[17:39] <ogra> either way ... that package is not released anywhere yet
[17:40] <Apachez> so even with proposed disabled there are the ads about pro
[17:40] <Apachez> so something else is borked with apt as of now?
[17:40] <ogra> because you installed whatever was in proposed
[17:40] <ogra> with the last update
[17:40] <Apachez> it never installed
[17:40] <ogra> which enabled that message
[17:40] <Habbie> any chance you installed a new apt from proposed, or something like that?
[17:40] <ogra> i think it is ubuntu-advantage-tools or some such
[17:41] <Apachez> not that I know of
[17:41] <Apachez> then its a major flaw that its nagging non ubuntu-disadvantage-tools users
[17:41] <ogra> no
[17:41] <ogra> it is not released
[17:41] <Apachez> none of the python packages listed as pro has been installed
[17:42] <ogra> you pulled it from a test repo
[17:42] <Apachez> so something else is flawed with apt
[17:42] <Apachez> only using production repo
[17:42] <ogra> you have proposed enabled
[17:42] <ogra> that is not a production repo
[17:42] <Apachez> nope
[17:42] <Apachez> its disabled
[17:42] <ogra> explicitly
[17:42] <Apachez> still getting nags about "hey why dont you use ubuntu pro"
[17:42] <ogra> you mean you had it not enabled ?
[17:42] <Apachez> its disabled
[17:43] <ogra> yes, because the change landed on your disk with the last updat you did from proposed
[17:43] <Apachez> running apt-get update and apt-get dist-upgrade, still nags about ubuntu pro
[17:43] <ogra> *before* you disabled it
[17:43] <ogra> last week, month day ...
[17:43] <ogra> geez
[17:43] <Apachez> so autoclean would remove it?
[17:43] <ogra> no idea
[17:43] <ogra> it is a test package, it had no QA ... no idea how you get rid of it
[17:43] <Apachez> clean, autoclean, update, dist-upgrade - still nags about ubuntu pro
[17:44] <ogra> sure
[17:44] <Apachez> could run some bleechbit to remove any caches
[17:44] <ogra> yu will need to remove/downgrade whatever added it
[17:45] <ogra> you could check all your packages with apt-cache policy to find what comes from poposed ... then downgrade that to the official archive versions
[17:46] <ogra> that wont be trivial though ...
[17:46] <Apachez> wiping /var/cache/apt, clean, autoclean, update, dist-upgrade - still nags about pro
[17:46] <Apachez> so lucky me being an ubuntu user =)
[17:46] <ogra> why would claning a cache change that ?
[17:47] <Apachez> where else does it pick up that "hey, lets nag you about these pro packages" ?
[17:47] <ogra> you will have to explicitly remove or downgrade the updated package that came from the proposed repo
[17:47] <ogra> chanches wont hlp
[17:47] <ogra> or any of the other apt commands
[17:47] <nteodosio> You could inspect /var/log/dpkg.log to see if it was installed
[17:48] <Apachez> apt-cache policy | grep -i propose     zero hits
[17:48] <Apachez> nteodosio: what should I be looking for? any of the pro packages mentioned?
[17:48] <nteodosio> Yes
[17:49] <sarnold> if you've disabled proposed in the apt sources, packages installed via it might not show up in apt policy output
[17:49] <nteodosio> Particularly, you want to look for it in `grep ' install ' /var/log/dpkg.log`
[17:49] <Apachez> searching for python2.7 in the /var/log/dpkg.log brings zero hits, dpkg covers from 1 sept to now
[17:50] <ogra> and you look for python2.7 because ... ?
[17:50] <nteodosio> Why are you looking for python BTW? I may have missed something
[17:50] <Habbie> sarnold, any idea if apt-forktracer would?
[17:51] <Apachez> nteodosio: because of this  https://pastebin.com/iPaEV44u
[17:51] <Habbie> Apachez, those are the updates you say you did -not- install
[17:51] <Habbie> Apachez, the question is what you installed -before- this message appeared at all
[17:51] <Apachez> yes and they DID NOT install
[17:51] <Habbie> we believe that
[17:51] <Apachez> yet apt still nags about some unwanted ads about ubuntu pro
[17:51] <Habbie> and we are suggesting that is because of something you installed -before- this
[17:52] <Apachez> even if I removed the proposed line from /etc/apt/sources.list (well commented it) and cleared the apt-cache out of /var/cache/apt/*
[17:52] <Habbie> yes
[17:52] <Habbie> that does not downgrade or uninstall any package
[17:52] <nteodosio> What does `grep ' install .*pro' /var/log/dpkg.log` tell you?
[17:52] <ogra> agan, that does not change your installed packages
[17:52] <sarnold> Habbie: oh! excellent idea :) I keep hearing good things about apt forktracer :D
[17:53] <Habbie> sarnold, the debian upgrade docs say 'use forktracer and also these two magic dpkg and aptitude commands'
[17:53] <ogra> Apachez, sudo apt install --reinstall ubuntu-advantage-tools=27.10.1~22.04.1
[17:53] <ogra> try that
[17:53] <sarnold> Habbie: ooo I gotta go find those magic commands :)
[17:54] <Apachez> trigproc    libreoffice-script-provider-*    only hits in the dpkg.log regarding "pro"
[17:54] <nteodosio> Ah yes, it's called advantage, I would try `grep ' install .*advantage' /var/log/dpkg.log` instead
[17:54] <Habbie> sarnold, https://www.debian.org/releases/buster/amd64/release-notes/ch-upgrading.en.html#system-status
[17:54] <Habbie> sarnold, ah, the dpkg commands are for other purposes in other sections
[17:55] <Apachez> 2022-09-22 21:14:19 upgrade ubuntu-advantage-desktop-daemon:amd64 1.9~22.04.1 1.9~22.04.2
[17:55] <Apachez> only "advantage" hit
[17:55] <sarnold> Habbie: wow that's magic indeed :)
[17:56] <ogra> Apachez, downgrade that ... the archive has 1.9~22.04.1
[17:56] <sarnold> it might be the shortest aptitude pattern I've seen but it's not 100% clear what it means just from a glance
[17:56] <ogra> 1.9~22.04.2 i most likely from proposed
[17:56] <ogra> *si
[17:56] <ogra> bah
[17:56] <ogra> *is
[17:56] <Habbie> sarnold, :)
[18:00] <Apachez> ogra: not according to policy
[18:00] <Apachez> ii  ubuntu-advantage-tools                      27.11~22.04.1
[18:00] <Apachez> ii  ubuntu-advantage-desktop-daemon             1.9~22.04.2
[18:00] <Apachez> output of   dpkg -l | grep -i advantage
[18:01] <Habbie> !info ubuntu-advantage-tools jammy
[18:01] <ogra> Apachez, right, us the command i gave you abve
[18:01] <Habbie> !info ubuntu-advantage-tools jammy-proposed
[18:01] <Habbie> there you have it
[18:01] <Habbie> you are running the version from -proposed
[18:01] <ogra> right
[18:02] <ogra>  sudo apt install --reinstall ubuntu-advantage-tools=27.10.1~22.04.1
[18:02] <ogra> or rather: sudo apt install --reinstall ubuntu-advantage-tools=27.10.1~22.04.1 ubuntu-advantage-desktop-daemon=1.9~22.04.1
[18:02] <ogra> so you catc both in one command
[18:02] <ogra> *catch
 Apachez, well, you should only use proposed if a dev asks you to test a fix .. it is not for permanent use  <- not true according to the gui
[18:03] <wastrel> "hebbo"   my ubuntu dock is not behaving properly because it doesn't see the apps i have open in other workspaces
[18:03] <Apachez> "Use proposed updates if you're willing to report bugs or any problem that occurs"
[18:03] <Apachez> not a word of "only enable if told to"
[18:03] <ogra> Apachez, so report a bug 🙂
[18:04] <wastrel> in 21.04 when i clicked the dock it showed windows from all workspaces but in 22.04 it only shows the current workspace
[18:04] <Apachez> I started with the chat to see if its a known issue
[18:04] <ogra> (ad ten revert to the archive version)
[18:04] <ogra> Apachez, no, because most people do not enable proposed
[18:05] <Habbie> ok, apt-forktracer works to detect accidental installs from -proposed, once you remove proposed from sources.list
[18:05] <ogra> oh, awesome 🙂
[18:08] <wastrel> gsettings get org.gnome.shell.extensions.dash-to-dock isolate-workspaces  =>  "false"   , and yet workspaces are isolated
[18:09] <nteodosio> about
[18:09] <nteodosio> ^ ignore
[18:12] <ogra> nteodosio, trying hard to ... but it is written there .... and scrolls up with every new line ... AAAAAHHH !!
[18:12] <ogra> 🙂
[18:13] <nteodosio> ogra: lol
[18:13] <nteodosio> ogra: At least today I'm not changing my nick to help with /nick help
[18:13] <ogra> lol
[18:15] <sarnold> lol
[18:34] <Windy> anyone using lxc on ubuntu 22.04?  I installed from apt, but can't start a basic container because of some kind of cgroups error
[18:34] <Windy> https://bpa.st/6MUQ
[18:35] <sarnold> still no luck? :(
[18:35] <Windy> heh nah
[18:35] <ravage> i did not know there is an apt version really
[18:35] <ravage> the snap works great
[18:35] <ravage> (lxd)
[18:36] <sarnold> note lxc != lxd
[18:36] <sarnold> I made that mistake yesterday :)
[18:36] <Windy> i tried witching to cgroups v1 by adding this to my grub config in /etc/default/grub "GRUB_CMDLINE_LINUX_DEFAULT="quiet splash systemd.unified_cgroup_hierarchy=0"
[18:36] <Windy> " but it didn't seem to do anything
[18:36] <sarnold> (the main interface to lxd being a command named lxc is maximallyconfusing :)
[18:36] <ravage> true. but why would you not use lxd to setup lxc?
[18:36] <Windy> yeah, i had recently read an article on lxc vs lxd.  decided to start with lxc, but plan to experiment with both
[18:37] <sarnold> as I understand it, lxd is image based, lxc is script based. the simplicity of the scripts appeals to a lot of folks
[18:37] <ogra> well, there is no actual lxc package ...
[18:37] <ogra> only a transitional package that installs lxc-utils
[18:38] <ogra> i dont think that gives you a fully fledged setup ... just some client tools
[18:38] <wastrel> ok it's actually   gsettings get org.gnome.shell.app-switcher current-workspace-only
[18:38] <wastrel> gnome added new thing gj every body
[18:38] <wastrel> thanks for the hlp l8rz ☠
[18:38] <Windy> there is a package called 'lxc': https://ubuntu.com/server/docs/containers-lxc these instructions are what i'm working from.
[18:39] <Windy> the 'lxc' apt package should be enough tools to lxc-create an image, and lxc-start it, but lxc-start fails with cgroup errors.  i found at least one reference suggesting these commands work on 20.04, so i think something changed in 22.04 maybe
[18:39] <ogra> wow, okay i satnd corrected ... the -utils are actually able to set up a container then
[18:40] <ogra> (but 10x ore complex than with the lxd snap it seems)
[18:40] <ogra> *stand
[18:41] <ravage> i looked at it to maybe test it but thats really a lot of work compared to lxd :)
[18:41] <ogra> sudo snap install lxd && sudo lxd init --auto && lxc launch ubuntu:22.04 jammy && lc shell jammy
[18:41] <ogra> thats all it needs to run and use a 22.04 container
[18:41] <sarnold> well, it might require logging out and in to join the magic root-equiv group..
[18:41] <ogra> well s/lc/lxc/ in the last command in that line indeed
[18:41] <ogra> oh, right
[18:43] <Windy> i thought there was some difference in how they treat templates vs OCI containers etc.  can't find the original article i read at this point
[18:45] <Windy> hmm, I guess what I read is that LXD can't run OCI based application images, only 'system containers' whereas LXC can
[18:50] <Windy> oh sheesh.  it turns out that the "systemd.unified_cgroup_hierarchy=0" was the issue, i hadn't run 'update-grub'
[18:51] <sarnold> d'oh!
[18:52] <Windy> everything says lxc should work with cgroupsv2, but maybe it needs some specific config
[22:49] <z1haze> hi, I have a brand new installation of ubuntu and im just doing the initial updates and whatnot, but ive gotten into pretty much an infinite loop where i run update, it tells me to upgrade packages, i do, then it tells me they were kept back: https://bpa.st/4XDA I have not installed virtually anything yet so im confused why there issue is occurring
[22:49] <bougyman> z1haze: try apt dist-upgrade
[22:49] <z1haze> same result
[22:50] <sarnold> z1haze: new releases have 'phased updates', where only some machines will install the updates
[22:50] <sarnold> z1haze: this shows which packages are currently being phased, and what percentage they've got https://people.canonical.com/~ubuntu-archive/phased-updates.html
[22:50] <Habbie> and phased updates say 'kept back'?
[22:50] <sarnold> yup
[22:50] <bougyman> oh weird.
[22:50] <bougyman> I did not know this.
[22:50] <z1haze> so this is a non-issue for me then?
[22:50] <sarnold> z1haze: yeah
[22:50] <z1haze> sounds good, thanks
[22:50] <sarnold> unfortunately apt's messaging here is pretty poor :(
[22:50] <bougyman> Wonder if the same applies to PopOS? (I know that's not on-topic here, just wondering)
[22:50] <sarnold> hopefully this will improve in time
[22:51] <arraybolt3> z1haze: https://askubuntu.com/questions/1431940/what-are-phased-updates-and-why-does-ubuntu-use-them
[22:51] <arraybolt3> ^ info about what phased updates are and stuff like that
[22:51] <enigma9o7> does popos use ubuntu repositories?
[22:51] <bougyman> Yeah.
[22:51] <enigma9o7> then it probably applies unless they're using old or patched APT
[22:51] <bougyman> It uses ubuntu repositories _and_ pop repositories.
[22:51] <bougyman> and it uses its own apt, that's what I was about to say.
[22:51] <bougyman> has its own do_release_upgrade (pop_upgrade), etc.
[22:51] <arraybolt3> Pop!_OS just recently disabled phased updates (basically making their whole entire userbase Ubuntu's guinea pigs...).
[22:52] <arraybolt3> At least they disabled them in apt, that is.
[22:52] <bougyman> arraybolt3: thanks for the info.
[22:52] <bougyman> I was 99% sure I was gonna convert my daily driver back to ubuntu. now I'm 100% sure.
[22:52] <enigma9o7> Have any phased packages ever been recalled before full distribution?
[22:53] <arraybolt3> enigma9o7: Quite a few, actually.
[22:53] <bougyman> I jsut took the convenience because the only FDE option with the frame.work was Pop.
[22:53] <sarnold> enigma9o7: oh yeah, quite a lot
[22:53] <arraybolt3> bougyman: You can install Ubuntu with FDE on a Framework system, no problem.
[22:53] <bougyman> But I can do FDE with ubuntu on my own. It's worth it, now. I already had too much Pop weirdness.
[22:53] <sarnold> enigma9o7: sometimes it can take months to sort out :( hopefully we'll do a better job of *that*, too, now that apt respects phasing too
[22:53] <bougyman> arraybolt3: ^ yes, I know.
[22:53] <bougyman> arraybolt3: but they did it for me, with Pop.
[22:53] <arraybolt3> You just have to click the "Advanced Options" button at the right point in the installer - it's fully automatic.
[22:53] <bougyman> Plus I wanted to give pop a spin, for real.
[22:53] <arraybolt3> Select "Use LVM and encryption", and kaboom. My system uses it right now.
[22:53] <bougyman> Been using in 3 months now. It's just different enough to piss me off (and there's no popos support on IRC)
[22:53] <arraybolt3> No manual setup, commands, or guides needed.