[00:02] <leftyfb> kotgc: you've been at this for 3 days. It will be WAY easier to just install Ubuntu 22.04 from scratch and restore from backup
[00:04] <kotgc> leftyfb that means rebuilding a KVM router, tunnels, network etc
[00:05] <leftyfb> kotgc: then it's a good thing you have it documented, scripted or a playbook built with ansible
[00:05] <kotgc> leftyfb plus, I still have 4 more disks to test for damage after the 25th December 2023 storms that blew up a computer. So I need to fix as the issue will probably repeat.
[00:06] <kotgc> leftyfb What's ansible? It's all on the forums.
[00:06] <kotgc> Ants in your pants?
[00:06] <kotgc> Risible?
[00:06] <leftyfb> kotgc: https://docs.ansible.com/ansible/latest/getting_started/index.html
[00:07] <leftyfb> kotgc: https://www.digitalocean.com/community/tutorials/how-to-install-and-configure-ansible-on-ubuntu-20-04
[00:08] <kotgc> leftyfb I don't how that FOSS IT automation will help?
[00:08] <leftyfb> you would build a playbook that would rebuild your system just by running 1 command
[00:09] <leftyfb> I just built a playbook to rebuild my work laptop from scratch, restoring from backup and reconfiguring every single customization I've done to it including installing and reconfiguring all the packages I had installed
[00:10] <leftyfb> and it would do so in just a few minutes ... depending on how much data you were restoring from backup, or if
[00:11] <leftyfb> in the meantime, it will still be quicker to just rebuild it
[00:17] <kotgc> leftyfb reason 3: curiosity to find what the problem is.
[00:17] <kotgc> leftyfb  reason 4: see if it can be fixed by experts.
[00:17] <kotgc> reason 5: I'm not confident this Ansible thingy 'just works'.
[00:18] <kotgc> reason 6: running this Ansible thingy 5 more times for the other disks I test doesn't sound like the best plan.
[00:19] <leftyfb> kotgc: that's exactly why ansible was built
[00:19] <leftyfb> and yes, it "just works" if you build your playbook to do what you need it to do
[00:19] <leftyfb> kotgc: regardless, your issue is likely due to your power outage. Either something on your drive is corrupt and not easily repairable or you have a hardware issue as a result
[00:20] <kotgc> leftyfb no, the storm was at another place, not here.
[00:21] <leftyfb> kotgc: so why is your computer having a problem now? What changed?
[00:21] <kotgc> I removed SSD 3 of 4 which is an empty disk and connected a LinuxMint SSD to test if the LinuxMint SSD was fried or not. The LinuxMint SSD ran perfectly.
[00:21] <kotgc> I then shutdown, disconnected the LinuxMint SSD and reconnected SSD 3 of 4.
[00:22] <leftyfb> kotgc: remove all drives except the Ubuntu drive and try a boot repair
[00:22] <leftyfb> !bootrepair | kotgc
[00:24] <elliotanderson> hello
[00:25] <kotgc> leftyfb ok, reading up on the boot thingy.
[00:25] <elliotanderson> wow this is awsome
[00:26] <elliotanderson> like lubuntu bruhhh
[00:26] <leftyfb> kotgc: going forward, I would seriously look at ansible. It's purpose built for your exact purpose. Rebuild systems from scratch. You can even build it to run the same playbook to build multiple distro's in the same way
[00:26] <elliotanderson> can like ammm create a chat for me and my friends?
[00:26] <kotgc> leftyfb thanks, I'll put it on the ToDo list.
[00:27] <leftyfb> elliotanderson: feel free to ask for help with that in #libera. This is an Ubuntu support channel
[00:27] <kotgc> elliotanderson this is tech support, other channels are for chat.
[00:28] <elliotanderson> oh ok thanks
[00:41] <kotgc> leftyfb rn the Boot Repair, it said it fixed it, rebooted and same black screen issue.
[00:41] <kotgc> *ran
[00:42] <kotgc> I'll email BootRepair, as per instructions if it didn't fix it.
[00:43] <kotgc> I'm confused what is the bootable drive though. It's either sda1 or sda2?
[00:43] <leftyfb> kotgc: so you didn't actually do what I told you
[00:43] <leftyfb> oh wait, sda1 or sda2
[00:43] <kotgc> I was 50% sure /dev/sda2 was the boot drive, but Boot Repair says this
[00:43] <kotgc> Locked-NVram detected. Please do not forget to make your UEFI firmware boot on the Ubuntu 22.04.3 LTS entry (sda1/efi/ubuntu/grubx64.efi file) !
[00:43] <leftyfb> did you remove all the other drives?
[00:44] <kotgc> leftyfb oh, not yet, I'll try that.
[00:44] <leftyfb> kotgc: remove all drives except the Ubuntu drive and try a boot repair
[00:44] <kotgc> leftyfb ok
[00:59] <rjwiii> Ubuntu 22.04. Installed MusicPod via SNAP ... Click on the icon and nothing happens. I am able to start it via CLI ... Any ideas?
[01:08] <kotgc> leftyfb ok, ran Boot Repair with only 1 of 4 disks connected, however same outcome.
[01:11] <kotgc> Boot Repair with 4 disks https://dpaste.com/3AQ4WXAM5  Boot repair with 1 main disk https://dpaste.com/7N2KHSLRR
[04:23] <ubuntustudio> bnr list
[04:24] <ll8> tabe?? ITA - windows - ok ???
[04:25] <lotuspsychje> can we help you ll8
[04:26] <ll8> I can me - tabe windows - oll browers no no no win - apole
[04:26] <ll8> ok
[04:26] <ll8> thank
[04:33] <ll8> - bela bela bela
[04:51] <kotgc> Hello, on which file would I run the fsck command? /dev/sda2 or something else?
[04:54] <kotgc> Can I run fsck from live usb in chroot, or do I need to boot into the machine's grub?
[04:59] <Bashing-om> kotgc: fsck from another instance rather than the install - the target of fsck must be in an unmounted condition.
[05:00] <kotgc> Bashing-om whoa what? So do I run the command $ fsck /dev/ sda2 from Ubuntu's grub or from LiveUSB's chroot?
[05:03] <Bashing-om> kotgc: Neither !
[05:03] <kotgc> Bashing-om just looking up how I can tell if /dev/sda2 is mounted or unmounted.
[05:04] <Bashing-om> kotgc: If you are change rooted in -- then the target is mounted - right ?
[05:05] <kotgc> Bashing-om I don't know? From commands here, that appears to be the case I think? https://dpaste.com/BHMDYCZCZ
[05:05] <kotgc> This tells me to not chroot.
[05:06] <kotgc> However, I am looking for a command to confirm /dev/sda2 is not mounted.
[05:07] <Bashing-om> kotgc: 1. Boot from the Ubuntu Live CD; 2. Open/Run Terminal; 3. Type: sudo fdisk -l (to get the device name) then press ENTER; 4. Type: sudo fsck /dev/sda2 then press ENTER; 5. Restart the system and boot normally.
[05:09] <kotgc> Bashing-om thx.
[05:10] <kotgc> I'm unsure which disk to fsck?
[05:10] <kotgc> https://dpaste.com/3RAZPKXZC
[05:11] <kotgc> test
[05:11] <kotgc> I'm unsure if /dev/sda1 or /dev/sda2 is the root system? I guess the root system needs fsck?
[05:11] <kotgc> dpaste lines 73-75.
[05:12] <Bashing-om> kotgc: Looking again.
[05:17] <Bashing-om> kotgc: consider - sda1 is "EFI System" --- EFI is a "FAT" file system -- so that can not be your linux partition /// now  we see 2 options - sda2 OR sdb4 /// any idea what sdb4 is ?
[05:19] <kotgc> That failed.
[05:24] <Bashing-om> kotgc: "That failed." is not very helpful to know a cause.
[05:24] <kotgc> Bashing-om well, black screen remains.
[05:27] <Bashing-om> kotgc: well --- when you boot can you get to grub's boot menu ? we can here boot to a TTY on the install.
[05:28] <kotgc> Bashing-om yes, I can access grub's boot menu.
[05:31] <Bashing-om> kotgc: At the grub menu press 'e' to edit - Append: systemd.unit=multi-user.target to the linux line.
[05:31] <kotgc> ok
[05:32] <kotgcFromPhone> Test
[05:32] <kotgc> At the grub menu press 'e' to edit - Append: systemd.unit=multi-user.target to the linux line.
[05:32] <Bashing-om> kotgc: See the bottom of the screen - crl+x to comtinie the boot process.
[05:34] <kotgcFromPhone> Done
[05:34] <kotgcFromPhone> New screen: Ubuntu login:
[05:34] <Bashing-om> kotgcFromPhone: Log in :S
[05:35] <kotgcFromPhone> I logged in.
[05:36] <kotgcFromPhone> It’s not GUI, just CLI.
[05:37] <Bashing-om> kotgcFromPhone: Let's test --- run terminal command ' sudo systemctl set-default graphical.target '// what results ?
[05:38] <kotgcFromPhone> Created symlink
[05:38] <kotgcFromPhone> etc/systemd/system/default.target
[05:39] <kotgcFromPhone> ->
[05:39] <kotgcFromPhone> lib/systemd/system/graphical.target.
[05:40] <kotgcFromPhone> Note: found “system.unit” on the kernel commandline, which overrides the default unit.
[05:54] <kotgcGuest59> Bashing-om still a blackscreen.
[05:54] <kotgcFromPhone> Test
[05:58] <kotgcGuest59> Bashing-om what was the test and did it pass?
[06:02] <Bashing-om> kotgcGuest59: The test was to see if you were able to activate the GUI . //  We now know however - that there is a config issue in starting the GUI.
[06:02] <kotgcGuest59> Bashing-om ok
[06:04] <Bashing-om> kotgcGuest59: Unfortunately - I have not run Gnome as my DE in years . I really do not know how Gnome starts the GUI.
[06:05] <kotgcGuest59> Bashing-om thx, guess I'll search how Gnome starts the GUI.
[07:39] <phil> longjohn
[07:57] <Cureaon> Which Ubuntu derivative would y'all recommend for developing with machine learning/AI?
[07:57] <lotuspsychje> !ot | Cureaon
[07:58] <Cureaon> Apologies.
[08:43] <webchat39> Hi after one of last updates I experiencing suspend does not work
[08:44] <webchat39> anybody else with the same experience these days?
[10:43] <meator> Hi. When I do snap run musixmatch, nothing happens. I'm running Ubuntu in a VM. How can I get more verbose output?
[10:52] <kotgcGuest59> Hello, is there a way to copy journalctl output from grub?
[10:59] <kotgcGuest59> I can copy journalctl output from a LiveUSB, but I'm unsure that's the right information needed to show Ubuntu 22.04.3 booting to a black screen and not starting the Gnome GUI?
[11:04] <jeremy31> kotgcGuest59:  you can pipe output from a command to a text file, like>     dmesg > dmesg.txt
[11:05] <kotgcGuest59> jeremy31 can I retrieve this dmesg.txt file from LiveUSB afterwards?
[11:05] <jeremy31> Only until you reboot
[11:05] <kotgcGuest59> jeremy31 oh, I need to post the output somehow?
[11:05] <jeremy31> Could put it on paste.ubuntu.com
[11:06] <kotgcGuest59> I only have grub command control, as gnome won't start the GUI.
[11:06] <kotgcGuest59> Maybe there's a command to do that?
[11:06] <kotgcGuest59> nc|termbin or something?
[11:06] <jeremy31> kotgcGuest59: which pastebinit
[11:07] <jeremy31> kotgcGuest59:  command | nc termbin.com 9999
[11:07] <kotgcGuest59> ...actually, grub has no network, ping 1.1.1.1 fails.
[11:07] <kotgcGuest59> Only this liveUSB is working for now.
[11:07] <kotgcGuest59> I thought I might be able to retrieve the journalct.txt file from LiveUSB somehow.
[11:08] <kotgcGuest59> Otherwise, I'll have to photograph it.
[11:09] <jeremy31> kotgcGuest59: Check the USB, there may be a partition where you can save a text file
[11:12] <kotgcGuest59> jeremy31 ok
[12:35] <evan> yo
[13:33] <BluesKaj> Hi all
[14:22] <spinningCat> i am asorry but ubuntu is retard
[14:25] <McParen> go away?
[14:29] <aruns> I've got the following drop-in for notify-send in ~/.bashrc in Ubuntu 22.04.3 LTS (WSL2), https://bpa.st/E6MA, but when I run notify-send "Test", I get the error message "Could not connect: No such file or directory". Any ideas as to how to get this working?
[14:29] <aruns> I want to get notify-send to work with non-root users.
[14:44] <tomreyn> arunsis X running as root there?
[14:45] <tomreyn> i'm not really familar with WSL, but hopefully it isn't
[14:46] <tomreyn> also, on a proper ubuntu installation, the values you write into local variables there are already set in their uppercase counterparts in the environment.
[14:47] <tomreyn> and you may be missing the leading colon for DISPLAY
[14:58] <aruns> Display is :0
[14:58] <aruns> So it should be correct
[14:59] <aruns> I'm running an X11 forwarding server on Windows via MobaXTerm
[15:02] <ubuntu> hi
[15:12] <BigMo> ola amigos
[15:17] <magga> sometimes my bluetooth hangs on my machine: (https://dpaste.com/EH7N8JGGY) it just says its turned off. and i cant turn it off. ive tried through terminal and from gui in Ubuntu. anyone know a solution? i have to manually power my machine off and on again, to get it working
[15:17] <magga> happens rarely. but enough to be annoying
[15:27] <EriC^^> good evening all
[16:04] <FKAShinobi_> I want to setup a VPN on my laptop using the gnome VPN UI. There is a field for gateway, what if I don't know the gateway while on a network?
[16:06] <FKAShinobi_> Or is that the ip of the gateway the vpn client will become?
[16:09] <ravage> gateway usually means the external IP of your VPN server
[16:09] <FKAShinobi_> ok, not the LAN's default gateway... that makes more sense
[16:09] <FKAShinobi_> Thanks
[16:56] <spinningCat> i installed mssql-server it gave me hadhache
[16:56] <spinningCat> this microsoft should go to hell
[16:57] <rbox> spinningCat: okay?
[16:57] <oerheks> what guide did you follow?
[16:58] <spinningCat> official documentation
[16:58] <spinningCat> and wubuntu is trash no
[16:58] <spinningCat> w
[16:58] <spinningCat> so windows shouldnt be part of linux world :D
[16:59] <ravage> so no support question in sight here. moving on
[16:59] <rjwiii> Ubuntu 22.04. Installed MusicPod via SNAP ... Click on the icon and nothing happens. I am able to start it via CLI ... Any ideas?
[17:00] <ravage> Maybe the maintainer messed up the desktop file 
[17:00] <Slartibart> Is there a way to "debug" audio in Ubuntu? I put a stereo cable in L-out, and a stereo cable in CS-out to the subwoofer(So I guess I'm kind of aiming for 2.1 sound). However, no matter what I do(so far) there's no sound coming out of the subwoofer. If I move the cable from L-out to RS-out I do get sound when clicking on the subwoofer button in 'Test speakers' in Ubuntu settings. Long story short, I'm
[17:00] <Slartibart> at a loss how to connect things to get 2.1 sound. 2.0/stereo worked just fine before this, and still does. But how to get the subwoofer going?
[17:01] <oerheks> rjwiii, did you run  sudo snap connect musicpod:network-manager-observe >> https://snapcraft.io/musicpod
[17:02] <ravage> it starts just fine here via the launcher without any additional permissions
[17:04] <rjwiii> oerheks: I installed via Ubuntu software installer. There were no instructions to do that. When I run MusicPod via CLI, it finds my music collection and can find radio stations when I search.
[17:06] <oerheks> i see sonme issues after a mesa update, unconclusive https://github.com/canonical/snapcraft.io/issues/4489
[17:06] -ubottu:#ubuntu- Issue 4489 in canonical/snapcraft.io "Snap packages broken" [Closed]
[18:21] <dlfke> my network doesn't come up by default, how can i fix it?
[18:26] <ioria> dlfke, what's the problem with it ?
[18:26] <ioria> dlfke, it came up or you would not be here
[18:27] <dlfke> another computer
[18:27] <dlfke> adapter is just being down until I run dhclient for it
[18:28] <dlfke> it is a freshly installed sustem
[18:28] <ioria> dlfke, ok,  try to set a static ip
[18:28] <ioria> dlfke, nm-connection-editor
[18:28] <dlfke> what does ubuntu use to manage the networks anyway?
[18:29] <ioria> dlfke, network-manager
[18:29] <dlfke> that sucns
[18:29] <ioria> sucns ?
[18:30] <sem> you shouldn't have to run dhclient manually network-manager is supposed to take care of it
[18:31] <sem> can you give more info, like ethernet or wifi, what kind of network, etc
[18:33] <ioria> maybe an old install with still a /e/n/i set or ifupdown installed or worst
[18:38] <dlfke> shouldn't  netplan create the files for networkd?
[18:38] <dlfke> or why do I need netplan at alll then?
[18:38] <ioria> dlfke, if you paste your *yamls file w can have a look
[18:39] <ioria> *we
[18:46] <dlfke> I think I'll nuke that canonical crap and setup networkd
[18:47] <tomreyn> did you install ubuntu desktop, or server, or something else? which release?
[18:48] <oerheks> different problem than in #linux
[18:54] <dlfke> you can't reinstall snapd because "host hunspell" package is bugged and breaks the install script causing dpkg to fail
[18:54] <dlfke> *uninstall
[18:56] <ravage> i reinstalled snapd about 5 hours ago
[19:05] <devslash> I am on ubuntu 23.10. when i boot it, it boots ubuntu but displays info about usb but never boots the desktop environment. if i press alt f3 i can log in through a alternste terminal
[19:05] <devslash> does anyone know how to fix this ?
[19:07] <tomreyn> devslash: what's this "info about usb" it displays? which graphics card do you have there?
[19:08] <tomreyn> did this work previously on 23.10 or earlier releases (did you upgrade to 23.10?) or was it like this from the start?
[19:08] <devslash> actually
[19:09] <devslash> funny enough I was also googling it and came across a post on stack overflow that said to remove and reinstall gdm and that fixed the issue for me
[19:18] <dlfke> ubuntu still installs gtk2 by default o_O
[19:22] <oerheks> so?
[19:26] <McParen> isnt backward compatibility a good thing?
[19:28] <oerheks> some app must have pulled some parts in.
[19:29] <oerheks> still only rants, and no real support question sofar
[20:07] <Urk> what is Ubuntu's version of killall
[20:09] <oerheks> killall
[20:09] <oerheks> https://manpages.ubuntu.com/manpages/jammy/en/man1/killall.1.html
[21:17] <zetheroo> I am having problems with Transmission causing my PC to freeze up. CPU and Memory are not maxing out - not even close. The single torrent will be downloading for a few minutes at ~15-20Mb/sec and then suddenly everything freezes up, the download/upload speed drops to zero, and Transmission has to be force quit to able to use the PC.
[21:18] <tomreyn> is there anything in dmesg about it?
[21:18] <zetheroo> The only resource which increases as the torrent is downloading is the buff/cache as shown by 'free -h'.
[21:19] <sem> is your disk ok? any alerts in smart?
[21:19] <pragmaticenigma> zetheroo, this is sounding like a disk full or disk failure type situation
[21:19] <zetheroo> Disk (SSD) is not full.
[21:19] <zetheroo> 38GB free
[21:20] <zetheroo> tomreyn: I didn't think to check that.
[21:21] <zetheroo> I'll run Transmission again and check
[21:22] <tomreyn> zetheroo: you can do it now.    sudo journalctl -b     or    sudo dmesg -T     - or, to watch the logs while you're reproducing it:     sudo journalctl -f    or     sudo dmesg -w
[21:22] <pragmaticenigma> zetheroo, In linux there are two ways a disk runs out of space, either physical or inodes. If you have a lot of files on the disk, it's possible to have plenty of physical space, but be disk full in terms of inodes. Torrent creates a lot of file fragments, and if you're at the upper limit of available inodes, the disk will appear full.
[21:22] <pragmaticenigma> dmesg will hopefully clear that up
[21:27] <zetheroo> hmm... nothing from dmesg
[21:27] <zetheroo> last output from dmesg was over an hour ago
[21:27] <zetheroo> and I just reproduced the problem and no new info
[21:28] <pragmaticenigma> is transmission running as a snap or apt package install?
[21:29] <zetheroo> journalctl shows more info though
[21:29] <zetheroo> pragmaticenigma: actually not sure
[21:31] <zetheroo> how can I tell?
[21:31] <oerheks> if those persist, reset your router?
[21:31] <zetheroo> oerheks: You think this could really be caused by my router?
[21:31] <pragmaticenigma> no
[21:32] <pragmaticenigma> computers don't freeze up because of a route
[21:32] <pragmaticenigma> router
[21:34] <oerheks> if it cannot handle manny connections somehow, i tend to check if it was my router
[21:34] <zetheroo> this is what's journald while transmission is freezing up my PC: https://pastebin.com/gesCbDXr
[21:34] <pragmaticenigma> zetheroo, if it is a snap it will show up when you use `snap list` in the terminal. Or `snap list | grep -i tr` might narrow down the list
[21:35] <zetheroo> ok, it's not a snap then
[21:36] <pragmaticenigma> are you trying to torrent using WiFi?
[21:36] <zetheroo> Yes, I've done this for years on this laptop
[21:36] <zetheroo> only in the recent last could weeks or so did this start to happen.
[21:37] <zetheroo> Could it be my SSD on the fritz?
[21:37] <natewrench> im having firefox randomly freeze
[21:37] <natewrench> have to kill the process
[21:37] <pragmaticenigma> zetheroo, unfortunately anything of use was clipped in the journal message. I suspect that is possible
[21:37] <natewrench> i submitted a bug report
[21:38] <pragmaticenigma> natewrench, there is no need to inform the channel that you have filed a bug report. this channel is not monitored by Canonical or Ubuntu developers
[21:38] <natewrench> ok
[21:38] <pragmaticenigma> (well developers might be here, but they're not monitoring for bug reports)
[21:38] <natewrench> heads up
[21:39] <natewrench> hopefully 24.04 lts will have a more stable firefox build
[21:40] <tomreyn> zetheroo: sudo journalctl --since 'Jan 13 22:21:11' --until 'Jan 13 22:24:15' | nc termbin.com 9999
[21:40] <zetheroo> this is older output of dmesg ... maybe something with the disk? https://pastebin.com/XR6h1pjE
[21:41] <zetheroo> tomreyn: returns "Failed to parse timestamp: Jan 13 22:21:11"
[21:42] <tomreyn> zetheroo: you added an extra " character there
[21:43] <pragmaticenigma> pretty sure the error message put that there. Think a YYYY prefix is needed on those date ranges
[21:43] <tomreyn> not on my system
[21:43] <zetheroo> tomreyn: where?
[21:43] <pragmaticenigma> or there system is not in the same time zone as you, and thus those hours have not transpired yet
[21:43] <tomreyn> zetheroo: somewhere between   --since     and  --until
[21:44] <pragmaticenigma> their*
[21:44] <tomreyn> i took these timestamps from https://pastebin.com/raw/gesCbDXr
[21:44] <zetheroo> tomreyn: I copy/pasted what you posted here
[21:45] <tomreyn> zetheroo: okay, ignore it. your later log shows there's a different, underlying, issue, anyways
[21:45] <zetheroo> Ok
[21:46] <zetheroo> Something wrong with my disk?
[21:47] <tomreyn> zetheroo: if you look at https://pastebin.com/raw/XR6h1pjE you see there are hung tasks, the first one listed is related to ext4 file system journalling. this can be just a result of low disk performance, but should not normally happen. it can be a side effect of other issues. i'd try to look through logs and find the first "INFO:" record
[21:47] <oerheks> kworker does something too
[21:48] <tomreyn> do we know which ubuntu release this is, and whether the software is fully up to date?
[21:48] <pragmaticenigma> nope
[21:48] <oerheks> 5.15.0-91...
[21:49] <zetheroo> tomreyn: the first "INFO" record since boot?
[21:49] <tomreyn> zetheroo: yes. can you also answer the questions i just brought up, please?
[21:49] <tomreyn> (no rush)
[21:50] <zetheroo> Ubuntu 22.04 5.15.0-91-generic
[21:50] <zetheroo> Yes, full updated
[21:51] <tomreyn> https://packages.ubuntu.com/jammy/linux-image-generic says https://packages.ubuntu.com/jammy/linux-image-5.15.0-91-generic is current indeed
[21:54] <oerheks> i would add HWE to that LTS
[21:55] <oerheks> but that might not be the issue with transmission, clean the cache and try adding torrent again?
[21:56] <zetheroo> I'm still trying to find the "INFO" record in the logs ...
[21:56] <tomreyn> you type    sudo journalctl -b   then press / and type INFO: and press enter
[21:56] <zetheroo> Oh thanks :D
[21:57] <Firefly10> I been using Linux mint for a year and then switch to Ubuntu LTS to try, ran it about 10 days before I had an issue that made it unusable, I searched forum and tried what I could there, but non of it solved issue. Figured I try here before giving up.    so one day my display resolution changed to 360x480 real hard to work with and can not change
[21:57] <Firefly10> it, says "display unknown" also noticed the wifi was dongle was not visible.    I did not see any way to reinstall without losing my data, only thing I was able to do is do an install to new partition to boot to, which worked, so my hardware is fine but some how my first Ubuntu broke.
[21:57] <zetheroo> OK, first "INFO" hist are related to cron
[21:57] <tomreyn> zetheroo: this text viewer software is 'less', and this is how you search in 'less'
[21:57] <zetheroo> I guess those are not of interest
[21:58] <tomreyn> zetheroo: does it say "state:D" and "blocked for..." as well?
[21:58] <zetheroo> next hit is: whoopsie-upload-all[1837]: INFO:root:/var/crash/_usr_bin_transmission-gtk.1000.crash already marked for upload, skipping
[22:00] <zetheroo> tomreyn: this is the very first 'INFO' record: cron[1796]: (CRON) INFO (pidfile fd = 3)
[22:00] <zetheroo> second one: cron[1796]: (CRON) INFO (Running @reboot jobs)
[22:01] <tomreyn> okay, that's not "INFO:" though
[22:02] <zetheroo> third one: whoopsie-upload-all[1837]: INFO:root:/var/crash/_usr_bin_transmission-gtk.1000.crash already marked for upload, skipping
[22:02] <tomreyn> if you expect to be able to reproduce the issue after a fresh reboot, it'll be best to do that and then share the full kernel log.
[22:02] <zetheroo> OK, will do that.
[22:02] <zetheroo> bbs
[22:20] <Firefly10> I am rebuilding my ubuntu computer , is it a good idea to move the home folder to a separate partition? any tips?
[22:21] <tomreyn> it can be good to have it on a separate file system, because this can make it easy to reinstall the OS without having to copy around the data from /home (you'd just keep this partition where it is). that's not a reason not to have backups, though.
[22:23] <zetheroo> I'm back, but with slightly bad news - the torrent has been active now for over 10 minutes without the system freezing up.
[22:23] <Firefly10> that is what I ran into, I somehow broke ubuntu and can't fix it, and moving files are a pain
[22:24] <zetheroo> It's not downloading as fast as it was before (15-20Mb/s before, and now ~5-10Mb/s).
[22:24] <zetheroo> I don't know why :/
[22:26] <zetheroo> The only thing I change between reboots was that before I was on battery and after I was plugged into power.
[22:28] <zetheroo> For interest sake - here is my boot log till now https://termbin.com/ihle
[22:29] <zetheroo> Maybe there's something useful in there
[22:41] <Firefly10> I can't resize my data partition, it has free space before it, but not after
[22:43] <Firefly10> anyway to move the leading edge of partition?
[22:43] <rbox> gparted
[22:45] <Firefly10> oh wow, yes forgot gparted was there
[22:45] <Firefly10> works!
[22:45] <Firefly10> thank you!
[23:22] <tomreyn> zetheroo: there's not much to be seen on your kernel log, nothing too unusual. i'd say if it happens again, share another. and keep note of whether it coul dbe related to suspend / resume.
[23:24] <oerheks> got a transmission update just now
[23:25] <oerheks> https://changelogs.ubuntu.com/changelogs/pool/main/t/transmission/transmission_3.00-2ubuntu2.1/changelog
[23:26] <oerheks> https://bugs.launchpad.net/ubuntu/+source/transmission/+bug/1973084
[23:26] -ubottu:#ubuntu- Launchpad bug 1973084 in transmission (Debian) "transmission-daemon high RAM usage" [Unknown, New]
[23:26] <oerheks> zetheroo, ^ ^