[00:00]  * enyc meows
[00:00] <jeremy31> enyc: wrong channel
[00:01] <enyc> I wonder if ubuntu have release-critical-bugs style thing like debian has graph of ...
[00:51] <mega> hi i may have made a small mistake with my os can someone help me fix/repair someting?
[00:52] <rbox> you would have to tell us the problem first...
[00:53] <mega> sure thing, so i may have deleted my networkmanager.conf file trying to get my wifi adapter working on ubuntu
[00:53] <mega> and im not so sure on how to reconfigure it, i am currently using an ethernet cable.
[00:54] <rbox> what networkmanager.conf did you delete
[00:55] <rbox> and how do you "may" have deleted a file
[00:55] <rbox> you either deleted it or you didnt
[00:55] <mega> oh boy did i delete it
[00:56] <mega> and i wish i didnt
[00:56] <ravage> there is not much in that file really
[00:56] <mega> etc/NetworkManager
[00:57] <sarnold> mega: try: apt download network-manager ; sudo dpkg -i --force-confmiss ./network-manager*deb
[00:57] <rbox> mine is all commented out
[00:57] <mega> when i reboot i have to unplug and replug my ethernet for it to activate
[00:58] <mega> maybe i am having another issue well anyway thanks for informing me that the file may not be the culprate
[00:58] <mega> thanks sarnold i will give that a shot
[01:03] <mega> hey thank you so much sarnold that resolved my problem the .conf file has been restored
[01:05] <sarnold> mega: any luck with fixing your actual problem?
[01:05] <mega> i will reboot and let u know shortly
[01:08] <mega> working thank you.
[01:08] <sarnold> yay :D
[01:11] <mega> my real problem is i have been spending all day trying to get my wif adapter to work. do you have any insight on how to get drivers for Broadcom BCM4364 internal wifi adapter?
[01:11] <Zed`> p
[01:14] <mybalzitch> looks like it works under arch
[01:15] <mybalzitch> https://wiki.t2linux.org/guides/wifi-bluetooth/
[01:15] <mega> oh i see
[01:16] <sarnold> heh, when step one is "boot macos and then run this script" :(
[01:16] <sarnold> I had an airport card that was similar, it didn't work at all in linux, I had to boot os x and use it there and *then* it could work in linux
[01:16] <mega> i tried that step but on my mac it is apfs file system and it says it failed to mount
[01:17] <mega> i have full functionality just no wifi. touch bar even working
[01:18] <Bashing-om> !BCM | mega
[01:19] <mega> my mac os has several partitioned drives because of the OS do u know the correct one? is it the storage hdd that i should attempt to mout it to? maybe if i download an old mac os  iso and try it in a a non apfs file system it could run the adapter script
[01:19] <mega> thank u for the link i have not came across this one yet
[01:21] <sarnold> oh dude Bashing-om's got a link for everything :)
[01:21] <sarnold> nice nice
[01:23] <Bashing-om> mega: BCM is proprietary - so we have to make a sacrificial offering :(
[01:25] <mega> yeah my right intex finger and my first born i would give that up to find this driver >:(
[01:25] <mega> index*
[01:26] <mega> proprietary meaning its not redistributed anywhere?
[01:27] <Bashing-om> mega: Been a while since I read the ^ docs - but yeah got to get the driver - at least the doc tells how :D
[01:28] <mega> yeah im looking into the windows ndiswrapper now but im not sure if any other windows laptops have ever used this adapter before
[01:30] <Bashing-om> mega: IIRC we are told that the ndiswrapper work-a-round is highly depreciated.
[01:35]  * oerheks reading https://github.com/reynaldliu/macbook16-1-wifi-bcm4364-binary
[01:35] <mega> you are a legend let me give this a go
[01:36] <oerheks> no, it is ugly
[01:37] <mega> it doesnt look simple but it seems feasable
[01:38] <oerheks> that t2 url should work
[01:38] <islam> helo
[01:38] <mega> i tried the t2 but with my version of mac os the script it tells me to run doesnt work with my file type, I have trued unencryping it same result
[01:39] <mega> pardon my typos
[01:40] <mcmlxxxi> whats up?
[08:40] <serverprotonico> hello ubuntuers
[08:40] <serverprotonico> i am a ubuntu users
[08:41] <serverprotonico> anyone here?
[09:15] <alcor> I've noticed that "apt download"'ing a package for which an ESM update is available fails with an "Unauthorized" error. It seems that "apt download" does not send the authorization token when attempting to download from the ESM repository.
[09:38] <ogra_> alcor, you should report that as a bug
[09:41] <alcor> Yeah, probably is a bug. Not a very critical one, but still a minor issue. FWIW "apt install" and "apt (dist)-upgrade" aren't affected.
[09:41] <alcor> I'm just not exactly sure against which package it should be reported
[09:42] <alcor> But I'm kind of leaning towards `ubuntu-advantage-tools' since that's where all the ESM management machinery is provided
[10:07] <ogra_> alcor, i'D start with apt ... apt maintainer and advantage-tools maintainer can then make it out among them 😉
[12:25] <oerheks> libssl update
[12:54] <pickanick> I would like to attempt to troubleshoot an 2015 Apple Macbook Pro SSD drive. It's attached to what I read is a proprietary PCIe socket. Booting Ubuntu from USB I do not see the drive mentioned in dmesg output.  A repair place said that when they ask for drive ID the drive signals BUSY. Are there utilities I can use to see more status than dmesg provides? Or even to issue low-level commands? Seems I cannot use smartctl because it is not assigned a device.
[12:59] <lotuspsychje> pickanick: for hd's try disk-tools or bonnie++
[13:01] <pickanick> lotuspsychje: thanks I'll explore those.
[13:03] <lotuspsychje> pickanick: but if smartctl doesnt see device, you might not have luck with other tools neither
[13:04] <lotuspsychje> pickanick: sudo lshw -C storage, might be handy
[13:22] <JanC> pickanick: if it's a SCSI/SATA/SAS drive then some of the tools in 'lsscsi' & 'scsitools' might be able to get more info; in case of an NVME drive there is 'nvme'; I'm sure there are also ways to talk to PCIE directly (in the 'pcitools' package maybe?)
[13:22] <JanC> but be careful with low-level tools: they can make things worse...
[13:23] <JanC> maybe the first thing to try is to remove the drive & put it back in (if that's possible)
[13:23] <JanC> if you're lucky it was just the connector that came a bit loose or something...
[13:25] <BluesKaj> Hi all
[13:31] <pickanick> lotuspsychje: yes, it seems that bonnie++ is a higher level tool looking at file IO.
[13:37] <pickanick> JanC : yes sometimes that works. In this case, cleaning the contacts did not help, and a new drive is detected.  I've read that in some cases, powering on the drive without accessing data gives it the chance to sort itself out.  So looking for some way to do that in situ, under an Ubuntu or other linux boot.
[13:38] <pickanick> lotuspsychje: in U 22.04.4, 'apt search disk' does not find disk-tools , do you know where I can find it?
[13:38] <JanC> even the firmware (UEFI) would access data...
[13:38] <JanC> so there is little Ubuntu can do to prevent it
[13:40] <JanC> unless the firmware has an option to disable the drive or remove it from the boot order maybe
[13:42] <JanC> in linux you'd need a distro that doesn't do any hotplugging (so no udev or similar)
[13:43] <pickanick> ooh thats good to know.  I don't know what Mac firmware can do, and what options they have besides choosing a boot partition.
[13:44] <JanC> I'm sure the drive gets powered on by just booting into the firmware
[13:44] <ogra_> pickanick, gnome-disk-utility ... it is pre-installed on ubuntu-desktop (and you can open it by typink "disk" in the dresktop search)
[13:46] <JanC> ogra_: when it's not mentioned in dmesg logs that would not really help, right?
[13:48] <JanC> pickanick: what did you look for in dmesg?
[13:50] <ogra_> JanC, i was only reacting to the "apt search disk" ...
[13:51] <pickanick> JanC: I booted a Ubuntu live USB with the old SSD, "dmesg > old.out"; then replaced with a new blank drive, and booted again, "dmesg > new.out";  and found that the second log contained references to a nvme drive. These lines did not appear in old.out.
[13:52] <pickanick> consequently the new drive would appear in the standard disk tools, but the old drive would not.
[13:54] <pickanick> apparently on SATA drives one can attach the power cable without attaching the data cables; I don't know of a way to do that with PCIe interface.
[13:55]  * pickanick looks for the dmesg outputs
[13:55] <JanC> yeah, you'd have to look up the PCIe lanes & only connect the power lines or something
[13:56] <JanC> and then hope that that proprietary connector has them in the same order...
[13:58] <pickanick> sounds like I'd have to have a fake card that fits into the motherboard slot and then connections running (or not running) to a new slot.   Or do the same thing to an external adapter
[13:59] <pickanick> But I was hoping for something a little more off the shelf.
[13:59] <JanC> if you know the connectors, you might be able to power it on without a motherboard too...
[14:00] <pickanick> oh right, its just the power connection
[14:01] <JanC> although I don't know how PCIE works and if it needs some sort of confirmation on a data lane to stay powered on or increase the power or whatever  :)
[14:01] <JanC> or voltage negotiations like USB has...
[14:02] <JanC> probably betetr ask someone more experienced with hardware for that  :)
[14:13] <pickanick> dmesg with the new blank drive has 7 extra lines (here are the four most obvious:)  nvme nvme0: pci function 0000:01:00.0  //  nvme nvme0: allocated 64 MiB host memory buffer. // nvme nvme0: 8/0/0 default/read/poll queues // nvme nvme0: Ignoring bogus Namespace Identifiers
[14:19] <JanC> my guess is that the drive is dead
[14:24] <pickanick> a repair shop says that it signals READY and when asked for drive ID it says BUSY. So its not completely dead. There's several months of work not backed up on it, so I'm hoping for the best and fearing the worst
[14:27] <pickanick> This Samsung drive MZ-JPV512S/0A4 : S4LN058A01-8030 is sadly not supported by what seems to be a popular drive recovery system.
[15:23] <jongsta> is there a way to extract 7zip files on ubuntu?
[15:23] <jongsta> i see old versions of p7zip but nothing newer than 2016
[15:24] <oerheks> !find 7zip
[15:25] <oerheks> jammy 22.04 gives 21.07, next lts 23.01
[15:26] <oerheks> it comes from universe repo, https://launchpad.net/ubuntu/+source/7zip/23.01+dfsg-8
[15:27] <jongsta> hmm, machine in question is running 20.0.4
[15:27] <oerheks> !find 7zip focal
[15:27] <oerheks> !info 7zip focal
[15:28] <oerheks> oh
[15:28] <oerheks> !info p7zip focal
[15:29] <jongsta> yah, that's the version i'm currently running and i'm getting errors when trying to extract a .7 file
[15:30] <jongsta> ERROR: Unsupported Method :
[15:31] <jongsta> not sure how to figure out what the actual problem is other than an outdated tool
[15:32] <oerheks> or damaged archive?
[15:32] <jongsta> it extracts fine on a windows machine
[15:32] <Walex> jongsta: try 'backports' archive
[15:33] <jongsta> what's that
[15:33] <oerheks> and why would it be outdated? https://sourceforge.net/projects/sevenzip/files/7-Zip/
[15:33] <Walex> jongsta: or 'p7zip-rar'
[15:33] <JanC> jongsta: do you mean a .7z file?
[15:33] <oerheks> some rar archives are not compatible, AFAIK
[15:33] <JanC> .7 ≠ .7z
[15:34] <Walex> jongsta: it is unlikely newer versions of '7-Zip' have newer compression format. It is more likely it the archive has some RAR files.
[15:34] <JanC> .7z ≠ .rar either  :)
[15:34] <Walex> using RAR compression with 7-Zip is not a good idea
[15:35] <JanC> AFAIK that wouldn't be a legal 7zip file
[15:36] <JanC> one with .7z extension
[15:37] <Walex> jongsta: https://www.7-zip.org/history.txt check here
[15:38] <Walex> ULTS 20.04 has 16.02
[15:42] <Walex> from 16.,02 to 23.01 there are no new compression formats, 24.01 adds RAR and ZSTD
[15:43]  * Walex is amazed that 7z can extract also from UDF and NTFS and many other formats.
[15:44]  * oerheks tends to avoid .rar
[15:44] <JanC> Walex: it can extract some on its own and uses external tools for other formats
[15:45] <JanC> or plugins
[15:45] <Walex> I avoid RAR compression too, dubious status and ZSTD and LZ4 are in different ways very good anyhow.
[15:47] <oerheks> indeed, impressive
[15:47] <JanC> also, p7zip ≠ 7zip (they are different packages)
[15:48] <JanC> I guess focal didn't have 7zip yet
[15:48] <oerheks> " P7zip is an unmaintained fork of 7z"
[15:48] <oerheks> indeed
[15:50] <JanC> jongsta: it doesn't say anything else about the "unsupported method"?
[15:50] <alcor> So we should the "7zip" package instead of p7zip?
[15:51] <alcor> `file-roller' still suggests p7zip-full though :/
[15:52] <JanC> I'm not sure it matters for 7z format (except maybe for speed?)
[15:53] <alcor> It matters for things that depend on it though
[15:53] <JanC> and maybe compression ratio in some cases
[15:53] <Walex> 'apt-cache search 7zip' on ULTS 20 shows only 'p7zip'
[15:54] <JanC> I was looking over the changelog & haven't seen anything about compatibility-changes yet (but I'm not at the end yet)
[15:54] <alcor> 7zip provides /usr/bin/7zz whereas p7zip provides /usr/bin/7zr
[15:54] <alcor> + /usr/bin/7z
[15:55] <alcor> So it matters for GUI frontends like file-roller and anything that expects /usr/bin/7zr or /usr/bin/7z to exist
[15:56] <JanC> right
[15:57] <JanC> maybe it's just the package dependencies though
[15:57] <JanC> that are outdated, I mean
[15:58] <alcor> I'm not sure, the program names are clearly different. file-roller and all the dependencies need to be changed to use /usr/bin/7zz
[15:58] <alcor> Or the 7zip package should provide compatibility symlinks
[15:59] <JanC> alcor: you checked that fileroller actually doesn't know about 7zz?
[15:59] <alcor> JanC: I didn't check the code, just the package dependencies on 22.04
[16:00] <JanC> dependencies can be outdated  :)
[16:00] <JanC> package dependencies
[16:01] <alcor> file-roller >= 43 seems to support 7zz (aka official 7zip) according to the NEWS entry https://gitlab.gnome.org/GNOME/file-roller/-/blob/master/NEWS#L118
[16:02] <oerheks> yes, when installed
[16:02] <alcor> Jammy's file-roller is v42 though
[16:03] <JanC> so it's "only" a packaging bug
[16:03] <JanC> ah
[16:03] <JanC> right
[16:03] <alcor> It's a packaging bug starting from lunar
[16:03] <JanC> if that version has the same dependencies
[16:04] <alcor> The dependency only made sense up to jammy. Starting from lunar, file-roller knows about 7zz and a 7zip package is available
[16:05] <alcor> Anyway it's just a "Suggests"-Dependency, it makes no sense but won't actively break anything
[16:06] <JanC> I wonder if the increase in maximum dictionary size in 7zip at some point can cause trouble for older versions to decompress...
[16:07] <JanC> and whether filters are needed when decompressing too?
[18:00] <root> p
[18:00] <root> nmap
[18:00] <root> nmap
[18:03] <fathomstory> Hi, I have about 60gb on my root drive and for some reason have only 14gb free. I do not know what is eating my root drive
[18:04] <kawal> try baobab or another disk space analyser,
[18:05] <kawal> probably cache thumbnails, /var stuff
[18:06] <fathomstory> This is a problem unique to Ubuntu. On Debian, I have a lot of space on the root drive.
[18:06] <fathomstory> I removed snap and hoped that would free up space
[18:06] <fathomstory> not really
[18:07] <oerheks> probably your swapfile
[18:07] <fathomstory> When I am down to 10 gb of free space, I guess I will just re-install debian
[18:07] <oerheks> ls -l /
[18:08] <fathomstory> oerheks, https://pastebin.com/9Sm9m5WJ
[18:19] <fathomstory> Anyway, 60gb ought to be plenty for a root drive. This is an ongoing issue with Ubuntu OS, for whatever reason and it sucks.
[18:20] <bind> https://live.novoeradio.by:444/live/narodnoeradio_aac128/icecast.audio Народное Радио
[18:20] <lotuspsychje> not here please bind
[18:23] <leftyfb> fathomstory: sudo apt install ncdu ; sudo ncdu /
[18:23] <leftyfb> fathomstory: use that to determine what is using space
[18:27] <fathomstory> leftyfb, it shows /home drive, but not really what is eating root
[18:27] <leftyfb> fathomstory: it shows a lot more than /home
[18:31] <fathomstory> leftyfb, I think it's an Ubuntu thing, some runaway process is just eating things up. Maybe a log file that keeps growing...
[18:31] <leftyfb> fathomstory: This is a support channel. Do you want support?
[18:31] <fathomstory> Debian has other issues, like it breaks easily
[18:32] <fathomstory> leftyfb, I want Canonical to fix their OS
[18:32] <fathomstory> : - )
[18:32] <leftyfb> fathomstory: let us know when you'd like community support
[18:33] <fathomstory> leftyfb, You don't have to answer. If anyone has similar issues where the root is being gobbled up and what done to resolve, please share.
[18:34] <leftyfb> fathomstory: I tried to help you. Run: sudo ncdu /      that will tell you exactly how much space everything on your system is taking, sorted by what's taking the most space
[18:34] <lotuspsychje> fathomstory: you already get advice to findout here, did you try them?
[18:34] <elSmith-> ncdu is solid
[18:35] <fathomstory> lotuspsychje, yeah, nothing really comes up
[18:35] <leftyfb> false
[18:36] <leftyfb> fathomstory: Run: sudo ncdu /
[18:37] <fathomstory> 128.3 TiB means terrabytes?
[18:37] <esra> what else
[18:37] <fathomstory> Yeah, this thing is borked
[18:38] <plastikman> never heard of ncdu i always us du -ah / --max-depth=1
[18:39] <plastikman> but im an old man that yells at clouds
[18:39] <fathomstory> plastikman, Love your handle
[18:39] <fathomstory> spastik
[18:39] <plastikman> :)
[18:40] <leftyfb> fathomstory: ok, so what did ncdu tell you?
[18:40] <plastikman> I prefer sheet one, but to each their own
[18:40] <fathomstory> plastikman, Well, the fuse project i dig
[18:40] <fathomstory> the old stuff is my fave
[18:40] <leftyfb> !ot
[18:40] <fathomstory> hallwaymonitor
[18:40] <leftyfb> fathomstory: what did ncdu tell you?
[18:41] <plastikman> yes yes tgat is why i hesitated to reply :)
[18:41] <fathomstory> leftyfb, I cannot pastebin it
[18:41] <fathomstory> How do I paste it to you?
[18:41] <plastikman> https://termbin.com/
[18:41] <leftyfb> fathomstory: you don't need to. It should tell you exactly how much space each directory is taking starting at root
[18:41] <leftyfb> ncdu is not meant for pasting
[18:42] <leftyfb> fathomstory: it should be pretty easy for you to determine what's taking space by starting at the top of the ncdu results and then navigate down into the directory structure if needed
[18:42] <fathomstory> Yeah, the top shows /home
[18:43] <leftyfb> and how much space is it taking?
[18:46] <Bogdar> Hello! I'm expirincing Wayland crashes on 22.04 while sharing screen in Google Meet with Firefox. Should I just follow 'report bug' guidelines or there something specific for Wayland I can add to the issue?
[18:47] <fathomstory> leftyfb, 212.1 gb
[18:47] <leftyfb> fathomstory: you said you have a 60GB drive
[18:47] <fathomstory> leftyfb, a root drive is different from home drive
[18:47] <fathomstory> .
[18:48] <leftyfb> fathomstory: Run: sudo ncdu -x /
[18:48] <lotuspsychje> Bogdar: you can check if a crash exists in your /var/crash dir
[18:49] <lotuspsychje> Bogdar: you can also browse existing wayland bugs; https://bugs.launchpad.net/ubuntu/+source/xwayland/+bugs?orderby=importance&start=0
[18:50] <leftyfb> Bogdar: have you tested with xorg?
[18:53] <fathomstory> cuda takes 5 g /lib takes 8g  share takes 3g
[18:53] <fathomstory> so what is taking everythinfg else????
[18:54] <fathomstory> i am going to smash this machine.
[18:54] <leftyfb> fathomstory: ncdu should be telling you that
[18:54] <Bogdar> leftyfb, Just have a call over 40 minutes with sharing on Xorg, no problems so far. Maybe first time for last 2 years I'm running xorg session. No problem with Wayland without screen capture in Firefox. Zoom's screen sharing works very well. I'm on latest firmware for HP 865 G9 (Ryzen 6800) and recent 6.5.0-21 kernel.
[18:54] <leftyfb> fathomstory: also, did you happen to mount your /home drive on top of /home before deleting everything in the original /home?
[18:55] <Bogdar> Bt it is just Wayland crushes, I can change vt to plain text console and gather some information ad-hoc, but I don't even know what to look for except dmesg :/
[18:56] <leftyfb> Bogdar: it could verywell be the fact that firefox is a snap and lacks permissions. Did you try another browser and/or the apt version of Firefox?
[19:00] <DarkenedGentlema> After using hostnamectl set-hostname host.domain.com is the only way to see the update to logout/in or to run bash?
[19:00] <leftyfb> DarkenedGentlema: correct
[19:00] <plastikman> fathomstory: just do du -ah /home --max-depth=1
[19:00] <Bogdar> leftyfb, if fact it is sharing of the another window of firefox. And sharing works well, but Waylay dies suddenly in few minutes, usually no more then 15. So from functional perspective sharing works, but after a while Wayland dies and I see black screen with ~20-40 random symbols
[19:00] <leftyfb> plastikman: /home is a separate drive
[19:00] <plastikman> so?
[19:01] <plastikman> he wants to know what is taking up all his space on /home
[19:01] <plastikman> or did i read taht wrong
[19:01] <DarkenedGentlema> leftyfb: thanks, it looks like the hostname is set permenately too?
[19:01] <leftyfb> plastikman: so du and ncdu should not be run on /home as it's only going to show space being taken up by the non-root drive, which isn't what they're trying to address
[19:01] <leftyfb> DarkenedGentlema: until the next time you change it
[19:02] <plastikman> then i read that incorrectly.  I assumed that he wanted to know waht was taking up /home
[19:02] <leftyfb> plastikman: They do not want to know what's taking up space on /home. They want to know what's taking up space on their root drive, which is separate from home
[19:04] <plastikman> ah, so then i would jsut use du to keep searching.  although to be fair i would assume that someone that knows how to split up partitions would know how to find this
[19:04] <leftyfb> ncdu
[19:04] <plastikman> fathomstory: did you migrate data from home to this new drive then never delete what used to be there
[19:04] <leftyfb> plastikman: I already asked that
[19:05] <plastikman> k then ill stfu
[19:10] <fathomstory> plastikman, I wipe the root partition when I install, always check that box.
[19:11] <fathomstory> plastikman, It is a glitch, something to do with maybe the graphics drivers or the programs i use don't mesh with Ubuntu that well. On Debian it is a non-issue, but Ubuntu, something goes off...
[19:11] <leftyfb> fathomstory: lets not
[19:12] <plastikman> that is not real
[19:12] <plastikman> its nothign to do with ubuntu in *that way*
[19:13] <leftyfb> fathomstory: there is clearly an issue, one of which you have not yet learned the origin of. Lets not speculate, especially when you're trying to blame the entire OS
[19:13] <fathomstory> That's why I went to debian, because I ran out of space in root with Ubuntu. Debains was fine until I installed a library that broke the system and I tried Ubuntu and had the same problem with /root
[19:13] <leftyfb> fathomstory: stop
[19:13] <plastikman> lsblk | nc termbin.com 9999
[19:13] <leftyfb> fathomstory: would you like further help troubleshooting?
[19:13] <fathomstory> https://termbin.com/mv23
[19:14] <leftyfb> fathomstory: you have a LOT going on there that you failed to mention
[19:14] <fathomstory> leftyfb, I also blame some of it on Nvidea
[19:14] <leftyfb> also, you have TB's of space and only gave 60GB to your OS?
[19:15] <fathomstory> leftyfb, Wow, your info is actually wrong
[19:15] <leftyfb> fathomstory: what info is that exactly?
[19:15] <fathomstory> I have 500gb approx for Ubuntu, 60gb for root drive
[19:15] <fathomstory> some space for swap and the rest for /home
[19:16] <fathomstory> If that is the info you got...then it is wrong
[19:16] <plastikman> I would bet its likely snaps related
[19:16] <leftyfb> your nvme drive is 1.8TB
[19:16] <fathomstory> yes, and 500gb is for ubuntu
[19:16] <fathomstory> 60gb for /root
[19:17] <leftyfb> fathomstory: boot an ubuntu live usb, mount your root partition, run ncdu on it
[19:51] <younder> I have a problem booting ubuntu. When trying to boot I errors and everything stops booting. When I boot in secure mode I need to run start with networking and then resume. Then everything works fine. It seems boot with networking detects and fixes some missing file by restoring a default configuration. Any Idea what this is?
[19:56] <plastikman> need to be more specific on where is stops
[19:56] <bprompt> younder: or what kind of errors
[19:57] <bprompt> younder: if you have a log of the boot errors, that may help
[21:08] <Idrogeno> Hello again friends.  How can I disable the "update notifier" that tells me about all the glorious things I can get if I subscribe to ubuntu pro?  Not looking to start a big discussion about it, just don't want to get a notification of updates that I'm not going to be installing.
[21:08] <Idrogeno> There doesn't appear to be any checkbox in settings
[21:12] <leftyfb> Idrogeno: I don't think there is a way currently
[21:12] <Idrogeno> That seems like a... giant oversight :)
[21:13] <plastikman> not for canonical
[21:13] <leftyfb> plastikman: lets not
[21:13] <Idrogeno> Okay, looks like I can just disable software-updater application entirely and I'll be good
[21:14] <plastikman> that was a joke
[21:14] <plastikman> jeez
[21:29] <daydrinking> I haven't gotten any of those notifications. Is one of your apt sources pro or something? And yeah disabling software-updater seems like a good choice for me as well. I always use shell to do updates.
[21:34] <Idrogeno> I don't know what changed to make them start appearing.  using 22.04 LTS, they just started showing up relatively recently.  I would receive a "software update" notification for all the things I could update, and then a second one with the pro updates
[21:40] <daydrinking> I would check your apt sources, but I'm not on LTS though
[21:41] <plastikman> I also dont get that, not on my kubuntu desktop, or any of my rpi devices, or my VM's
[21:41] <plastikman> maybe i just ignored it?
[21:42] <bprompt> plastikman: what version of kubuntu?
[21:43] <plastikman> 23.10 (Mantic Minotaur)
[21:43] <bprompt> ohh ok
[21:44] <bprompt> I never got it, or get it either
[21:51] <Idrogeno> those are all for "apt" related information, not update manager, as far as I can tell from that AI generated website
[21:52] <Idrogeno> maybe disabling ubuntu advantage will work..
[23:31] <oerheks> lots of updates today, just saying ..
[23:32] <oerheks> libssl3 and more
[23:33] <PeGaSuS> hello guys.. so, I've used clonezilla to clone one disk to another but I'm unable to boot from it. here's what I see on GParted: https://imgur.com/oeuZApt.png
[23:33] <PeGaSuS> any help is greatly appreciated
[23:36] <leftyfb> !boot-repair | PeGaSuS
[23:36] <leftyfb> !bootrepair | PeGaSuS
[23:36] <PeGaSuS> it doesn't work
[23:37] <jeremy31> PeGaSuS: Does the source drive work?
[23:37] <leftyfb> PeGaSuS: define doesn't work. Where is it failing? what error message(s) are you seeing? Can you mount the drive? Is it EFI or MBR? Is this PC different from before?
[23:39] <oerheks> copieingto a new disk, changes UUID
[23:39] <oerheks> *HINT*
[23:39] <PeGaSuS> if  I try to boot fro the cloned disk, I go into the grub command line, directly. I don't seem to be able to mount the drive, no. the source disk works. I think it's EFI? the PC is different but same brand and almost same specs
[23:40] <oerheks> no, not efi, you can tell if you used efi
[23:40] <oerheks> update frub with the real UUID's
[23:40] <PeGaSuS> I definitely used GPT, that's a fact
[23:40] <oerheks> or grub
[23:41] <PeGaSuS> sorry, but I don't know how to do that
[23:42] <oerheks> 'ubuntu show uuid update grub'