[00:08] <Ricardus> I just tried running Libre Office Calc and it won't run. Anyone else seeing this? This was on a new installation of Ubuntu Studio
[00:13] <tomreyn> Ricardus: what happens when you run it from a terminal window?
[00:13] <Ricardus> it gives me a java error or something. Here, let me do it
[00:13] <tomreyn> !paste | Ricardus
[00:15] <Ricardus> tomreyn: it wasnt a java error. Heres the terminal output: https://dpaste.com/27NDUDS6P
[00:19] <tomreyn> Ricardus: that's a warning, it's possibly a side effect of the underlying issue, which we have not yet determined.
[00:19] <tomreyn> if you think it can be a problem with your system users' configurations for libeoffice, you can run   lcalc --safe-mode    which will make it start temporarily with a fresh user profile and helps to restore a broken configuration.
[00:21] <Ricardus> tomreyn: same console errors. If anyone else has any ideas please post them and I will see them in the morning. I need to get home.
[00:26] <tomreyn> Ricardus: make sure you have package default-jre installed. and maybe describe how you installed libreoffice-calc (unless it was installed as part of installing ubuntustudio)
[00:56] <penderdrill> wow hello ubuntu
[00:56] <penderdrill> irc!!!!
[00:57] <penderdrill> is anyone here
[00:58] <penderdrill> BRO
[00:58] <penderdrill> IS ANYONE HERE
[00:58] <leftyfb> penderdrill: this is a support channel. Do you need help with ubuntu?
[00:58] <penderdrill> y6es
[00:58] <penderdrill> i forget what the advantage of using a swapfile is
[00:58] <penderdrill> isn't is just like
[00:58] <penderdrill> extra ram
[00:59] <leftyfb> penderdrill: if you have a modern pc with at least 16gb of member, you don't need swap
[00:59] <penderdrill> yeah that's what i thouight
[00:59] <penderdrill> i used to have like a 2 ghz cpu
[00:59] <penderdrill> and i was running linux mint
[00:59] <penderdrill> 4 gb of ram or something
[00:59] <penderdrill> it was painful man.
[01:00] <penderdrill> i was tryna run it for a script
[01:00] <penderdrill> because i couldnt actually run a virtual machine on my main pc LOL
[01:00] <penderdrill> i had like 8 gb of ram and a terrible graphics card
[01:01] <leftyfb> penderdrill: if you'd like to just chat, feel free to /join #ubuntu-offtopic
[01:01] <leftyfb> penderdrill: we try to keep this channel specific to support questions and help
[01:06] <tomreyn> clarkk: i think i want to partially withdraw the suggestion for zsync i made previously. it is certainly helpful if you have, for example, a copy of the ubuntu 22.04.*0* iso and want to upgrade this to 22.04.1. but i just tried zsync from a 20.04.2 iso to 22.04.1 and this only saved me 1.5% of the download, while calculating what's missing took 21 minutes. So it's probably not useful for *this* use case.
[01:11] <tomreyn> clarkk: a better streategy may be to install using debootstrap (but that's complicated) or using the server installer (which is a much smaller download - but you would need to download more later)
[02:03] <Intelo> Hi
[02:03] <Intelo> How can I assign a static ip on ubuntu?
[03:01] <jhutchins> !interfaces
[03:02] <jhutchins> Sigh.  /etc/network/interfaces still works, it'll cause Network-Manager to ignore it.
[03:45] <mybalzitch> or use netplan. it should work wihtout bugging out on just a static ip
[03:51] <Intelo> mybalzitch I think I missed your first message
[03:52] <Intelo> mybalzitch I reverted to the old netplan and did apply als well but I still do not get the internet. I do get LAN ip though
[03:54] <mybalzitch> this was just in reply to "how to assign a static ip"
[03:55] <mybalzitch> are you setting a default route?
[03:55] <mybalzitch> and dns server?
[03:55] <Intelo> ok, how can I revert to workign dhcp?
[03:55] <Intelo> mybalzitch no I changed my mind. I just want my internet back now
[03:55] <mybalzitch> Intelo: restore the backup you made of the netplan config file
[03:56] <mybalzitch> https://netplan.io/examples
[04:03] <Intelo> mybalzitch this https://imgur.com/nWKkDNe.png was working before. I made changes, then reverted back. did 'sudo netplan apply'. Now I wonder why I get the ip 192...46 but no interent. I get 'ping google' message as 'Temporary failure in name resolution'. How can I fix this?
[04:06] <Intelo> mybalzitch how do I fix ?
[04:26] <mybalzitch> you don't have dns configured
[04:27] <mybalzitch> try a sudo systemctl restart systemd-networkd
[04:42] <Intelo> mybalzitch thakns
[05:44] <Rexodus> Good morning! What is a replacement for PuTTY SOCKS5? Something that runs as a service, preferably.  What is a replacement for PuTTY SOCKS5? Something that runs as a service, preferably. So I don't need to see the PuTTY-window all day long? I know it's a Windows question but only Linux people use PuTTY, so most Windows users have no clue what I'm talking about.So I don't need to see the PuTTY-window all
[05:44] <Rexodus> day long? I know it's a Windows question but only Linux people use PuTTY, so most Windows users have no clue what I'm talking about.
[05:45] <Rexodus> Dunno what happend with this paste. Hope you can read it anyway.
[05:48] <arraybolt3> Rexodus: np, I got it.
[05:49] <arraybolt3> If you want something that runs on Windows, I'm not sure what would do the trick there. It may be true that most Windows users don't know about this sort of thing, but you might just try #windows to see if tech savvy people there know better.
[05:49] <oerheks> just minimize the window?
[05:55] <tripp4h> hi! i ran the command sudo apt-get purge snapd and it deleted half of my programs, is there a way to get them back?
[05:56] <Rexodus> oerheks: It burns my eyes to see a application filling my taskbar which I don't use. But you gave me an idea. I can move it to the systemcorner. I know there is software for that. Anyway, thanks all for the answers and sry offtopicness :P
[05:57] <arraybolt3> tripp4h: What all programs vanished? Firefox most likely, what else?
[05:57] <oerheks> tripp4h, reinstall snapd?
[05:57] <oerheks> else, no
[05:58] <arraybolt3> Most likely the programs that vanished were installed as Snaps, and getting rid of snapd would likely also throw your Snap apps out the window (I don't know that for sure, but I'd assume that would happen).
[05:58] <tripp4h> i get this error trying to reinstall snapd: Err:1 http://fi.archive.ubuntu.com/ubuntu hirsute-updates/main amd64 snapd amd64 2.51.1+21.04
[05:58] <tripp4h>   404  Not Found [IP: 193.166.3.5 80]
[05:58] <oerheks> programms might stil be there, arraybolt3 ??
[05:59] <arraybolt3> Oh no. hirsute? That's an old and EOL release.
[05:59] <oerheks> tripp4h, run apt update first
[05:59] <arraybolt3> !eolupgrades
[05:59] <arraybolt3> (Back up all your data before trying an upgrade, you may just want to do a clean install of Ubuntu 22.04 after backing up to get your system back into a sane state)
[05:59] <oerheks> oh hirsute .. upgrade please
[06:08] <tripp4h> i did this apt-get purge snapd because i couldn't update snap-store in software
[06:08] <oerheks> tripp4h, that is because hirsuite is EOL.
[06:08] <arraybolt3> tripp4h: That's probably because your release went end-of-life. Once a release is no longer supported, updates don't come through anymore (at least for apt, presumably for snap also).
[06:08] <oerheks> use the eolupgrade wiki
[06:09] <arraybolt3> The only way to fix an end-of-life release is to upgrade to or install a supported release. Otherwise, problems like inability to update things are normal and to be expected.
[06:10] <arraybolt3> If you absolutely have to get back access to your original apps before upgrading, you can *try* to reinstall snapd by changing your /etc/apt/sources.list file to point to the old-releases repo, then you should be able to install snapd. But really, a clean-install would probably be the best idea at this point.
[06:10] <arraybolt3> (The eolupgrades wiki page linked to above has instructions on how to switch to the old-releases repo.)
[06:10] <oerheks> do a fresh install, much more fun
[06:14] <tripp4h> oerheks: i couldn't update snap-store because the task was always running, tried to kill it a few times.
[06:15] <tripp4h> oerheks: i want to save my configuration files and programs. and other files.
[06:23] <scribz> Hello
[06:25] <tripp4h> why when i do sudo do-release-upgrade the program cannot find all the files for the update?
[06:26] <oerheks> tripp4h, after the old-releases trick?
[06:26] <scribz> Why did it happen to me?
[06:26] <scribz> dpkg: error: error executing hook 'if { test "$DPKG_HOOK_ACTION" = add-architecture || test "$DPKG_HOOK_ACTION" = remove-architecture; } && test -x /usr/share/pkg-config-dpkghook; then /usr/share/pkg-config-dpkghook update; fi', exit code 4
[06:28] <arraybolt3> tripp4h: See https://help.ubuntu.com/community/EOLUpgrades - it explains how to get around that problem. And also, **back up your data before you do this.**
[06:28] <scribz> arraybolt3: I know this but
[06:28] <oerheks> scribz, on what ubuntu version, and what did you do?
[06:28] <scribz> How the fuck can I see the log
[06:29] <oerheks> scribz, oh please, keep teh language in this channel family friendly, thanks
[06:29] <scribz> oerheks: 22.04 LTS
[06:29] <tripp4h> oerheks: here's a paste of it: https://pastebin.ubuntu.com/p/pKvKW4JZhj/
[06:30] <scribz> oerheks: I need to see the logs but when kernel panic happens there is no logs
[06:32] <oerheks> tripp4h, pastebin your /etc/apt/sources.list ?
[06:34] <scribz> oerheks: how the fuck can i see the fucking logs
[06:35] <arraybolt3> scribz: If you've hit a kernel panic, you probably aren't going to be able to see the logs since they won't have been saved to disk. If your system works normally after a reboot, then good. If not, then you should try to boot from a live USB. And if that doesn't work, your hardware may be failing, in which case a RAM test would be the next thing to do.
[06:35] <scribz> arraybolt3: I know such fucking simple things
[06:35] <scribz> I don't know what happen after upgrading
[06:36] <scribz> But first of all I had "illegal function" then I finalised the upgrade from chroot
[06:36] <arraybolt3> scribz: Sorry, that's all the answer I have. This happens every time you try to update? (Also, please, your language is making this painful for the users in this room. I get that this is upsetting and annoying, and I do want to help you fix it.)
 pnbeast: Man it is good, but it happens automatically when I was upgrading debian ... please rant over there, thanks
[06:37] <scribz> arraybolt3: It happen from nowhere in the past I had problems with some vars in shell (by default)
[06:38] <scribz> oerheks: It happen "itself"
[06:38] <arraybolt3> scribz: So it just randomly happened and now is gone?
[06:39] <arraybolt3> Or is it happening regularly when you try to do something and is still obstructing your work?
[06:40] <scribz> First I got "illegal fuction" and I think it's due to this ->
[06:40] <scribz> Unpacking libc6:amd64 (2.31-13+deb11u4) over (2.31-13+deb11u3) ...
[06:40] <scribz> dpkg: error: error executing hook 'if { test "$DPKG_HOOK_ACTION" = add-architecture || test "$DPKG_HOOK_ACTION" = remove-architecture; } && test -x /usr/share/pkg-config-dpkghook; then /usr/share/pkg-config-dpkghook update; fi', exit code 4
[06:40] <scribz> Now I did the chroot
[06:41] <scribz> I'm not a dumb, basically I would have to set up gentoo or even LFS
[06:42] <tripp4h> oerheks: here: https://pastebin.ubuntu.com/p/Jpy66dTstB/
[06:42] <scribz> But I want to keep the install because I don't have the internet connection all the time
[06:43] <scribz> arraybolt3: ?
[06:43] <arraybolt3> tripp4h: There's your problem. You need to change fi.archive.ubuntu.com to old-releases.ubuntu.com all through that file. You can do that by running "sudo nano /etc/apt/sources.list" and then editing the file by hand.
[06:43] <scribz> oerheks: ?
[06:44] <scribz> arraybolt3: it's so simple to solve my "kernel" errors
[06:44] <oerheks> scribz, you are not using ubuntu, so no help
[06:44] <arraybolt3> scribz: I still can't understand what's gone wrong. Please explain - are you able to reliably reproduce this issue by doing the same thing again?
[06:44] <arraybolt3> scribz: Also, what OS are you using?
[06:44] <scribz> oerheks: normally i'd stab you with a knife man, you're really annoying
[06:44] <scribz> arraybolt3: debian
[06:45] <oerheks> tripp4h, you did that wrong, you need to edit current lines to old-releases..
[06:45] <oerheks> !ops
[06:45] <arraybolt3> !ops | scribz is using highly unacceptable language
[06:45] <oerheks> now please leave yourslef, thanks
[06:46] <arraybolt3> tripp4h: Apologies for the chaos, if you could wait for a bit while things stabilize, we can get back to helping your upgrade work. (Or if you want, we can keep working through this, but things may be a bit hectic.)
[06:47] <oerheks> tripp4h, else you can start over with the original sources.list > /usr/share/doc/apt/examples/sources.list
[06:48] <scribz> ubottu: because scribz left the jail in Jan of 2022
[06:49] <scribz> tobybl: kurwa slyszysz
[06:49] <scribz> tripp4h: nie wiem co mi sie zjebalo kurwa
[06:49] <arraybolt3> !ops | scribz is continuing to cause trouble
[06:49] <scribz> arraybolt3: I'm talking to him in polish
[06:49] <scribz> tripp4h: co kurwo nie odpisujesz
[06:50] <scribz> tripp4h: masz szczescie ze jestes za natem kurwo
[06:50]  * scribz is going to left the channel and eat something
[06:50] <scribz> because I'm mad
[07:25] <clarkk> great tip, tomreyn . Thank you
[07:27] <oerheks> !cookie | tomreyn
[07:34] <tripp4h> oerheks: i got this error: Err http://old-releases.ubuntu.com main Release 404  Not Found [IP: 185.125.190.40 80]
[07:37] <arraybolt3> tripp4h: Oy. That's odd. Care to show your /etc/apt/sources.list file again?
[07:47] <oerheks> there is something missing , ' hirsute'  before ' main'  https://askubuntu.com/questions/1340397/how-does-sources-list-for-hirsute-hippo-21-04-looks-like
[07:51] <akram_> hey
[07:52] <akram_> anybody there ?
[07:54] <oerheks> ..
[08:23] <varaindemian> I have two keys -> one in `apt-key list` and one under `gedit /etc/apt/sources.list.d/slack.list` and I get a warning during `sudo apt update`
[08:23] <varaindemian> https://www.irccloud.com/pastebin/V7ZFVWmL/
[08:24] <varaindemian> this is the key in the `/etc/apt/sources.list.d/slack.list` -> `deb https://packagecloud.io/slacktechnologies/slack/debian/ jessie main`
[08:25] <oerheks> varaindemian,  see this answer https://askubuntu.com/a/1403964/64683
[08:25] <oerheks> it needs some steps, as apt key add is depreciated
[08:25] <varaindemian> oerheks: so I should delete it
[08:26] <varaindemian> deleted and now I get some other warnings :(
[08:27] <varaindemian> https://www.irccloud.com/pastebin/mD67eMy6/
[08:29] <Guest89> ubuntru
[08:29] <Guest89> !
[08:31] <oerheks> no, not deleting they key ..
[08:33] <varaindemian> `sudo apt-key adv --keyserver keyserver.ubuntu.com --recv-keys C6ABDCF64DB9A0B2`
[08:34] <Guest89> why not
[08:38] <Guest89> ubuntu tealtabbycat
[08:39] <lotuspsychje> can we help you guest89 ?
[08:39] <varaindemian> oerheks: that doesn't solve my problem
[08:39] <varaindemian> I stil get the same errors after exporing the key
[08:39] <varaindemian> apparently there are two separate keys..
[08:44] <varaindemian> I keep getting this now:
[08:44] <varaindemian> https://www.irccloud.com/pastebin/cY023RXM/
[08:45] <oerheks> maybe there is no key ..
[08:46] <varaindemian> https://quan.hoabinh.vn/blog/2022/5/101-fix-missing-key-issue-for-slack-apt-repo-in-debian-ubuntu
[08:46] <varaindemian> what about this..
[08:47] <oerheks> same method, i think?
[08:47] <Guest89> yea
[08:47] <Guest89> ubuntu
[08:47] <oerheks> part one is export, part 2 is [signed-by=/etc/apt/keyrings/something.gpg]
[08:48] <Guest89> mtd utils ples
[08:48] <Guest89> please
[08:48] <varaindemian> oerheks: yeah, but I cannot see that key under `sudo apt-key list`
[08:48] <oerheks> varaindemian, correct.
[08:48] <oerheks> it is not in your keyring.
[08:50] <varaindemian> oerheks: I see some other Slack key that is in the keyring..
[08:50] <oerheks> if that one does not match, no need to remove i guess
[09:02] <lotuspsychje> !bg | Guest89
[09:05] <varaindemian> man !bg
[09:08] <Guest89> Man !bg
[09:08] <Guest89> man !bg
[09:08] <Guest89> no chanel
[09:09] <arraybolt3> lotuspsychje: ? I think you *may* have triggered the wrong factoid.
[09:13] <lotuspsychje> arraybolt3: Guest89 is from bulgaria, has a bit of problems to formulate his question, hence the redirect
[09:13] <lotuspsychje> but seems like the bg channel is empty
[09:13] <arraybolt3> lotuspsychje: Ah.
[09:14] <lotuspsychje> Guest89: so if you want volunteers to help you, please elaborate your ubuntu question, see also !details
[09:15] <Guest89> bulgaria
[09:15] <Guest89> ?
[09:35] <clarkk> OK, understood, tomreyn - thanks for testing it. It's interesting to know, anyhow. Thanks for your help
[10:07] <clarkk> what is a good partitioning scheme for an initial install on a 500GB disk on a system with 16GB? Is  /:250GB  swap: 32GB /home:250GB ok?
[10:07] <clarkk> Sorry, I mean /home: 218GB
[10:07] <clarkk> 16GB RAM
[10:08] <respawn> clarkk: for swap it goes x2 of te amount of ram
[10:08] <clarkk> 32GB then?  Got that. What about the rest?
[10:09] <respawn> clarkk: you can get that to be done automaticly in the installer
[10:09] <clarkk> I understand that. I'd like recommendations tho
[10:19] <arraybolt3> clarkk: 2x the amount of RAM used to be recommended for swap, however nowadays 2GB and smaller swapfiles are common. With 16 GB of RAM, you might not even need a swapfile, depending on what you're doing with your system.
[10:19] <arraybolt3> Also, you don't need swap to be on a separate partition - a swapfile should work just fine unless you're using a weird filesystem that doesn't support them.
[10:20] <arraybolt3> My system's default, out of the box configuration only gave me 1 GB of swap space on a 16 GB RAM system.
[10:20] <arraybolt3> (I'm on Ubuntu Desktop 22.04.)
[10:21] <arraybolt3> As for your root and home, I would recommend that you not separate out your root and /home partitions - while there may be some benefits to doing so (like the ability to share your /home with multiple different distros), those benefits are minimal, and potentially unsafe to use.
[10:22] <arraybolt3> Also, if you run out of space on either /home or /, you're going to end up trying to figure out how to move space to the filled partition. Which could be painful.
[10:22] <arraybolt3> clarkk: ^
[10:23] <arraybolt3> TL;DR: Just go with the defaults that Ubuntu gives you if you click "Erase disk and install Ubuntu". Assuming you intend on wiping the whole disk and going Ubuntu-only, that is.
[10:27] <clarkk> arraybolt3, thanks for your advice. I'll go with that
[10:28] <arraybolt3> clarkk: Glad to help! Oh, also, seriously consider enabling disk encryption. If your system gets stolen or physically accessed when powered off, that will keep people out of your data.
[10:29] <arraybolt3> Disk encryption should always be enabled on a system except in very specific circumstances. You can access it with the "Advanced options" button after selecting "Erase Disk and install Ubuntu" in the installer.
[10:30] <oerheks> with encryption, always make sure you have a backup of your precious files
[11:10] <saltd> you
[11:13] <lotuspsychje> stop that please saltd , this is the ubuntu support channel not meant for random rant
[11:16] <saltd> lotuspsychje sorry, forgot about ubuntu
[11:49] <amdj> arraybolt3: I separate out /home from / for one main reason; the ability to reinstall the OS (wiping the / filesystem) without losing the configuration for all of the programs I use. this comes in particularly useful should one commit the unfortunate mistake of attempting to install any kind of nvidia GPU driver.
[12:00] <clarkk> amdj, Good point. I've not been able to get to the install part yet, but when I do, I'll probably do that
[12:07] <amdj> pretty much everything you configure without superuser privileges (e.g. password prompt), whether it's taskbar layout, desktop background, lock screen user photo, firefox bookmarks or addons, file manager view preferences, etc etc is stored in your home directory. so not having to do that all over again every time you reinstall or clean upgrade is quite nice.
[12:10] <faeton786> Привет всем, кто может помочь?
[12:10] <oerheks> faeton786, english only please
[12:10] <oerheks> !ru
[12:11] <faeton786> Danila, i need help !
[12:12] <oerheks> state your problem, and ubuntu version ?
[12:12] <clarkk> I'm having trouble booting the ubuntu installer. It shows the very first menu of 4 options, and then goes blank/black, and then doesn't do absolutely anything more. Does anyone have any idea how I can find out what is failing?
[12:13] <oerheks> clarkk, on what videocard?
[12:13] <oerheks> nvidia gives this problem sometimes, see the nomodeset factoid
[12:13] <oerheks> !nomodeset
[12:14] <clarkk> oerheks, MSI Twin FROZR II  N460GTX Hawk, which is a GeForce GTX 460 chipset
[12:15] <oerheks> nomodeset might be your fix
[12:15] <faeton786> I have Ubuntu 20.04.5 LTS, the problem is that I have fps drops in games, Dota 2 (50-100 fps) and Worlds of Tanks (proton port 20 fps) laptop msi GT72VR video card GTX 1070 mobile. On Windows in Dota 2 I have 120 fps, I looked at the reviews on youtube and for people Dota 2 on Linux is better than on Windows, I don’t understand what my problem is. Sorry for transliteration.
[12:17] <lotuspsychje> faeton786: can you reproduce your issue by changing to a different nvidia driver version?
[12:17] <crush2> Is there any power user?
[12:19] <lotuspsychje> !ask | crush2 your ubuntu question
[12:19] <crush2> lotuspsychje: I got a kernel panic when I did the upgrade
[12:19] <crush2> In other words I can't boot debian I can't even see any log
[12:19] <faeton786> Right now I'm using NVIDIA's proprietary driver metapackage 515 software
[12:20] <murmel> crush2: are you on debian or ubuntu?
[12:20] <crush2> murmel: I'm not a newbie so debian
[12:20] <amdj> crush2: this is #ubuntu
[12:20] <lotuspsychje> faeton786: ubuntu-drivers list
[12:21] <murmel> crush2: so whay are you in #ubuntu?
[12:21] <crush2> It is almost the same distro, I can't join debian because some stupid op set the channel for registered
[12:21] <murmel> crush2: so? register?
[12:21] <crush2> Sure I can register my nick on temporary email but wouldn't waste my time on it
[12:21] <murmel> I mean you are not a newbie
[12:21] <faeton786> nvidia-driver-515, (kernel modules provided by linux-modules-nvidia-515-generic-hwe-20.04)
[12:21] <faeton786> nvidia-driver-390, (kernel modules provided by linux-modules-nvidia-390-generic-hwe-20.04)
[12:21] <faeton786> nvidia-driver-418-server, (kernel modules provided by linux-modules-nvidia-418-server-generic-hwe-20.04)
[12:21] <faeton786> nvidia-driver-470-server, (kernel modules provided by linux-modules-nvidia-470-server-generic-hwe-20.04)
[12:21] <faeton786> nvidia-driver-470, (kernel modules provided by linux-modules-nvidia-470-generic-hwe-20.04)
[12:21] <oerheks> crush2, registering is not that expensive, no help here .. see topic
[12:21] <clarkk> oerheks, I've booted the install disk. I'm at the menu with the options, "Try or Install Ubuntu", "Ubuntu (safe graphics)", "OEM install (for manufacturers", "Test Memory".  I don't see any way to add the nomodeset parameter. The second option may be the one I need, but does it just run the live disk, or the installer?
[12:22] <amdj> clarkk: press e on the option and it should let you edit the boot stanza.
[12:22] <amdj> find the "linux" or "kernel" line and add "nomodeset" to the end.
[12:22] <amdj> press F10 to boot the modified stanza.
[12:22] <clarkk> ok amdj. What does the second option boot into, out of interest? The live disk or the installer?
[12:23] <amdj> I don't actually know, I haven't used that one
[12:23] <amdj> I imagine the live session
[12:23] <oerheks> at the try ubuntu/live mode, press F6 nomodeset?
[12:24] <lotuspsychje> faeton786: try a 470 and compare your fps, see if you can reproduce
[12:26] <lotuspsychje> faeton786: use a !paste bin next time you want to share several lines to the channel
[12:27] <clarkk> oerheks, F6 doesn't seem to do anything
[12:29] <clarkk> I pressed e and added nomodeset
[12:29] <clarkk> waiting to see the result now
[12:29] <oerheks> amdj, +1
[12:31] <faeton786> Thanks a lot for the tip! Hugs!
[12:54] <clarkk> So, I added the nomodeset to the boot line, and it's booted the live disk, not the installer :(
[12:54] <oerheks> once in live mode, the install icon is on your desktop
[12:55] <clarkk> oerheks, OK, thanks - I just spotted it. Installing now :)
[12:55] <oerheks> have fun!
[12:55] <clarkk> heh
[12:55] <oerheks> and you can play a game while installing :-D
[13:02] <Guest9130> Hi, I've been searching for a while about how to create a bootable live USB installation with an encrypted persistent storage, but it looks like this isn't so straightforward. I'm willing to invest some time on this, and was wondering about how the live USB boot sequence works. I'm struggling to find technical documentation on this, could anyone
[13:02] <Guest9130> please give me some pointers about that?
[13:03] <oerheks> there are guides for persistance, but not encrypted.
[13:03] <Guest9130> Yeah, that's the point...
[13:03] <crush2_> Guest9130: you can create yourself luks or (?) dm-crypt
[13:04] <Habbie> luks uses dm-crypt, so not precisely "or"
[13:04] <Habbie> and indeed, the keywords are "luks" and "cryptsetup"
[13:04] <oerheks> use a 2nd usb ?
[13:05] <Guest9130> crush2_ Yeh, I've already been running encrypted disk with LUKS for a while now. But now I'm willing to have it done with a live USB, not a system install
[13:05] <crush2_> Yeah it's of course possible
[13:06] <Guest9130> oerheks or a second partition on the same device, it would have the same effect, but how to set up the live USB system to decrypt the persistence partition, that's the issue
[13:11] <clarkk> I've defined how I want my EFI disk. Where should the boot loader go - on /dev/sda, or on /dev/sda1, which is a fat32 partition for EFI, or on the root partition?
[13:13] <clarkk> When it says bootloader, does it mean grub?
[13:13] <arraybolt3> I believe so. I think I remember having had success telling it to put the bootloader on the EFI partition.
[13:15] <clarkk> I don't really understand what it means when it says /dev/sda. That's just the device? How does it write files to the device? Surely it would need a partition to do that, like sda1?
[13:15] <Jeremy31> grub gets installed to a drive in most cases
[13:16] <clarkk> Jeremy31, a drive, as opposed to a partition?  Where will the actual files be located (excuse if this is a silly question)
[13:16] <bougyman> clarkk: a partition, yes
[13:16] <esv> EFI needs to be a partition as it is a VFAT filesystem
[13:17] <tomreyn> clarkk: with efi, it doesn't matter what you choose for grub's target, or whether you supply one
[13:17] <bougyman> it can be in the MBR of a drive or an EFI partition.
[13:17] <bougyman> Most installs are using efi today
[13:17] <esv> not sure if you can put  the OS on a vfat one, haven't seen it done ever.
[13:17] <tomreyn> clarkk: it will just write it to the first esp it finds
[13:18] <clarkk> esv, yes, my motherboard supports EFI. I have a blank partition ready for it, formatted in fat32
[13:26] <clarkk> I'm going to put the bootloader on the root partition. Does that seem right?
[13:26] <clarkk> because I want all the grub files there
[13:29] <tomreyn> that seems wrong. but as discussed above, if you're providing the device path of the partition containing your root partition to grub-install, it will probably still work since it will likely just ignore it.
[13:31] <tomreyn> the boot loader needs to go on the ESP, and there only. but i'm not sure what exactly you are doing there (which commands you are running) to put the boot loader somewhere, anyways.
[13:32] <tomreyn> if this is the ubuntu desktop installer then the target you choose will be ignored
[13:34] <clarkk> tomreyn, I'm just hesitant to put files somewhere where I cannot access them. But it does indeed seem that the recommended way is to select the drive, not a partition, for the bootloader
[13:35] <clarkk> by, "cannot access them", I mean, cannot look at them, cannot inspect them, etc
[13:35] <clarkk> if they're on a partition, then it's more understandable to me, because I can see them there
[13:36] <Jeremy31> Most files will be in /boot/grub and /boot/efi
[13:36] <tomreyn> clarkk: The ESP is, by definition, a FAT32 file system. ubuntu can mount FAT32 file systems.
[13:36] <esv> the grub files can be on their own partition or as a subdirectory of the rootfs, I have systems with both setups.
[13:37] <Jeremy31> ESP gets mounted as /boot/efi
[13:37] <clarkk> ah, that's useful
[13:37] <esv> the EFI files need their own location as stated before MBR or a vfat partition
[13:37] <clarkk> ok, so I'll choose /dev/sda then?
[13:38] <tomreyn> choose, where?
[13:38] <esv> what's the worst it can happen? need to reinstall again?
[13:38] <clarkk> esv, yes, I'm doing this for someone, and need to finish it, and setting everything up by the end of today :D
[13:38] <arraybolt3> tomreyn: I think he's probably on the Manual Partitioning screen of Ubuntu Desktop.
[13:38] <clarkk> arraybolt3, correct
[13:38] <arraybolt3> There's a dropdown menu at the bottom of that screen that says something like "Boot loader location" or some such.
[13:39] <clarkk> correct arraybolt3
[13:39] <tomreyn> clarkk: so then it's irrelevant what you choose, as explained before
[13:39] <clarkk> sorry I didn't explain it fully
[13:39] <clarkk> ok
[13:39] <clarkk> thanks
[14:19] <tripp4h> arraybolt3: here: https://pastebin.ubuntu.com/p/T8gRWGN3hp/
[14:20] <arraybolt3> tripp4h: Yikes, that looks somewhat scrambled. One moment, I'll give you a sources.list file you can just drop in place.
[14:21] <arraybolt3> tripp4h: https://bpa.st/YMNA
[14:22] <arraybolt3> tripp4h: Run "sudo nano /etc/apt/sources.list", then when nano opens, press and hold Ctrl+K until everything is deleted out of the file. Then copy the contents of the pastebin I sent, and paste them into the file with Ctrl+Shift+V (the shift is important). Then press Ctrl+S to save, Ctrl+X to exit, then try a "sudo apt update && sudo apt full-upgrade".
[14:28] <clarkk> It seems like we're up an running :)   Now doing the initial setup. What are everyone's thoughts on livepatch?  With my own systems, I like to manage the updates myself, so I can update at a time that's convenient to me. This system is for someone else, so I'd consider this system working differently. Is there anything that I need to consider?
[14:29] <arraybolt3> clarkk: Livepatch is only free for non-commercial use, so the user should be allowed to make that choice for themselves.
[14:30] <clarkk> arraybolt3, this is non-commercial
[14:30] <arraybolt3> The system will naturally tell you when it needs to restart (at least my Ubuntu Desktop system does), so an occasional reboot should be no problem.
[14:30] <clarkk> No, I want to set up as much as I can.
[14:30] <arraybolt3> clarkk: Yeah, but what if they decide to start a small business and use their computer as the main computer for that business?
[14:31] <clarkk> arraybolt3, They're retired. Never going to happen
[14:31] <arraybolt3> clarkk: Well, at least inform them that it's on, and give them clear instructions for how to turn it off just in case.
[14:31] <clarkk> arraybolt3, fine. Are there any negative aspects of it?
[14:32] <clarkk> any considerations?
[14:32] <arraybolt3> Not that I'm aware of, but I've heard that the free version might give you beta patches or something like that? That's possibly from an unreliable source, so don't take my word for it there. I don't personally know of any downsides other than the licensing, but then again I don't use Livepatch so...
[14:33] <clarkk> arraybolt3, thanks.  I just clicked the button to set it up, and it wants authentication to Ubuntu One. Not going to do that, so I'll skip
[14:33] <arraybolt3> Someone who actually works for Canonical might have the answers you're looking for, like sarnold.
[14:33] <arraybolt3> That makes sense.
[14:34] <clarkk> arraybolt3, it's ok. The user is fairly PC literate. They can manage the updates
[14:40] <Ricardus> tomreyn: it was installed with the OS
[15:12] <pycurious> is there a cli tool that can let me define a checkpoint for the system, so that I can go back to precisely that checkpoint with a command? (I am ok with a reboot after that- but any installs/changes to the drive i want to be able to remove)
[15:13] <murmel> pycurious: did you use lvm during install?
[15:14] <lotuspsychje> !backup | pycurious
[15:15] <pycurious> lotuspsychje: can i do that on a running system, and then revert?
[15:15] <oerheks> https://ubuntu.com/tutorials/using-zfs-snapshots-clones#1-overview
[15:15] <pycurious> I only have one drive on that system
[15:15] <oerheks> using zfs means a fresh reinstall, afaik
[15:19] <pycurious> oerheks: isnt there a way in zfp to go back to a snapshot and reboot?
[15:20] <oerheks> pycurious, yes
[15:20] <oerheks> it is all in that url
[15:22] <oerheks> and tons of more sites with explanation, like  https://www.howtogeek.com/devops/how-to-install-and-configure-zfs-on-ubuntu/
[15:25] <tripp4h> arraybolt3: thanks! i upgraded to version 22.04.1! i lost my opera settings when uninstalling snapd with purge, do you think there's a way to get them back?
[15:27] <oerheks> see if there is a opera folder in ~ /snap/ ? else no.
[15:29] <tripp4h> oerheks: i re-installed it at least now there's /snap/opera folder
[15:30] <tripp4h> oerheks: other things i should do when i accidently uninstalled snapd? i hope the update restored all the files
[15:31] <arraybolt3> tripp4h: Ouch. If you purged snapd, you might have lost stuff permanently, especially if you're reinstalling stuff now.
[15:31] <arraybolt3> Make sure any important data that's left in ~/snap/ is backed up elsewhere before you start installing anything else.
[15:31] <arraybolt3> tripp4h: ^
[15:34] <oerheks> if the snap/opera folder survived upgrading, perhaps the settings are still there
[15:48] <ioria> tripp4h, afaik, the upgrade process (even about snapd) does not touch the home directory at all
[16:25] <OpenSorce> Asking to ask sucks, I know, but does anyone want to help an old man with a grub annoyance?
[16:26] <Habbie> OpenSorce, why not describe the annoyance?
[16:26] <OpenSorce> Okay, so I installed Ubuntu along with Windows 10 and everything was fine grub-wise. Then I got the bright idea to put Android in there too (androidx86 project). Android replaced my grub. I got my old menu back with 'sudo grub-install/update-grub' from the Ubuntu install but the android grub is still hiding in there somewhere. I can't set the resolution and if I hit c at the grub menu and then exit out it shows me the android grub menu.
[16:26] <OpenSorce> I'm old and not entirely up on UEFI grub yet. Where is this pesky android grub menu hiding and how should I get ride of it?
[16:26] <jhutchins> .
[16:27] <OpenSorce> s /ride/rid
[16:28] <solsTiCe> OpenSorce: it's the EFI menu netry. Chechk with efibootmgr. and delete it with it
[16:29] <OpenSorce> solsTiCe, thank you! I knew it was likely something simple.
[16:59] <jhutchins> OpenSorce: This probably isn't a problem, but it struck me that you listed "install" before "update".  That should be the other way around, do update first, then install.
[17:10] <OpenSorce> jhutchins, will do. Thanks :-)
[17:11] <OpenSorce> Sadly, I'm just doing this to get my resolution back :-P
[17:30] <jhutchins> OpenSorce: Once you've run update, the next install will reference updated/current files.
[17:32] <BluesKaj> Hi all
[17:46] <saltd> all
[18:11] <COE> Hi, I have a question. I am new to Ubuntu and updated to JJ. I am having issues with my browser Chromium & FF  crashing/freezing forcing me to reboot. Any idea on where I should look to fix this?
[18:13] <ravage> first check if you use wayland or xorg. wayland can cause problems in general. logout. click your username and them the gear icon. login with an xorg session
[18:14] <COE> Here's my system info. I am pretty stuck. Most of the time it works well, like using this webbased irc client. Then it'll randomly freeze. bc@bc-MacBook:~$ neofetch
[18:15] <COE> bc@bc-MacBook
[18:15] <COE> OS: Ubuntu 22.04.1 LTS x86_64
[18:15] <COE> Host: MacBook5,1 1.0
[18:15] <COE> Kernel: 5.15.0-47-generic
[18:15] <COE> Uptime: 13 mins
[18:18] <tomreyn> COE: feel free to share this again, but like this: neofetch | nc termbin.com 9999
[18:18] <tomreyn> this should return a url you can post here
[18:19] <COE67> yeah so I accidentally cycled my computer lol. So the GUI is infact wayland. How can I change this to improve stability
[18:20] <COE67> Change to XORG iirc is what was mentioned.
[18:20] <tomreyn> i wouldn't *generally* expect wayland to cause problems, but maybe ravage knows more than i do.
[18:21] <tomreyn> you can logout and, on the login screen, choose "Ubuntu on Xorg"
[18:21] <COE67> Well generally speaking it does not. But it will randomly freeze up doing normal things on my hardware for some reason
[18:21] <oerheks> How much memory is in that macbook? standard 2 gb?
[18:22] <COE67> no, I have 5gb
[18:22] <tomreyn> COE67: you're now assuming that the problems you're seeing are related to wayland, but i doubt you have verified this is the actual cause.
[18:22] <COE67> here lemme pull up neofetch
[18:22] <tomreyn> !paste | COE67
[18:22] <COE67> That is correct. It is an assumption
[18:22] <oerheks> ok, not a memory problem
[18:24] <COE67> As I am new to linux and ubuntu, I am trying to figure out why this would be occurring is all. Making a mental note of what to look at when I have some free time. Over all I am very happy with the OS so far.
[18:24] <ravage> just to quote myself: "wayland can cause problems ". never said *generally* ever. it is just one of the big changes when you update from 20.04
[18:26] <COE67> correct I misread your initial post. I will however take a look at wayland as it is one of the changes from 20.04 to JJ.
[18:28] <COE67> I had the issue across multiple broswers as well, so I doubt it is the browser.
[18:28] <COE67> and between 20.04 and 22.04 actally.
[18:28] <COE67> Maybe the gpu driver or something that is mostly working just isnt perfectly happy.
[18:29] <COE67> something in use that has spanned both OS versions
[18:29] <tomreyn> ravage: sorry, seems like i got you wrong there.
[18:30] <tomreyn> COE67: journalctl lets you access system logs
[18:30] <tomreyn> there's also the "Logs" GUI application for this purpose
[18:31] <COE67> ahh ok, that is great. I will leverage that the next time something goes south.
[18:32] <COE67> How would I run journalcl from terminal?
[18:32] <COE67> sudo journalctl?
[18:32] <tomreyn> COE67: you add the missing t
[18:33] <tomreyn> no need for sudo
[18:33] <tomreyn> at least if your user is member of group adm
[18:34] <COE67> it is
[18:35] <tomreyn> journalctl -f     to follow the logs as they're being added (while you're reproducing the issue)
[18:37] <tomreyn> COE67: there's something i don't understand about what you said initially: "I am new to Ubuntu and updated to JJ". Those seem to be conflicting statements - unless you installed 20.04 and then immediately upgraded to 22.04 (but why would you do that)?
[18:42] <COE> Yep, just froze up again. To rule out physical hardware, swapped the ssd into another, identical laptop
[18:42] <COE> we'll see what it does
[18:43] <root_gay> wassup
[18:43] <root_gay> im gay
[18:43] <root_gay> <--
[18:43] <clarkk> I added a user using useradd. In /etc/passwd, it has the correct home directory, of /home/<username>.  When I log in as that user, the home directory has not been created and that user's environment is really really slow. Anyone know why?
[18:43] <root_gay> No
[18:44] <root_gay> I'm "New" to linux
[18:44] <root_gay> Hello
[18:46] <ravage> clarkk, You have to use -m, otherwise no home directory will be created
[18:46] <clarkk> ok, thanks ravage
[18:47] <arraybolt3> root_gay: Do you have an Ubuntu support question?
[18:47] <ravage> you can create is not and use "chown /home/<username> <username>" to change the owner
[18:47] <EriC^^> clarkk: adduser is easier to add users with
[18:47] <ravage> is is a nice wrapper script yes :)
[18:47] <ravage> *it
[18:50] <clarkk> EriC^^, I remember now - damn, used the wrong one! :/
[18:52] <clarkk> now I've deleted the user, I can see that the user still exists in some /etc files, like group-, passwd-, shawow-, subgid- etc. How do I clean up all these files?
[18:52] <EriC^^> happens, i find it helpful to remember usermod, useradd as the raw basic ones, and so adduser is the nice wrapper one
[18:52] <root_gay> Alr, Ima try to go make my own IRC client
[18:52] <root_gay> *sighs*
[18:54] <EriC^^> clarkk: userdel -r <user> maybe?
[18:55] <COE> Yep same behavior on that macbook as well. Interesting it seems to freeze up when I go to log into my university distance learning website.
[18:55] <clarkk> EriC^^, I found out that they are userdel backup files.  I think I can just delete them all
[19:05] <LukeHoersten> I updated from the previous to the latest LTS and my uwsgi stopped working. I can start the uwsgi-app@instance.socket/service directly and it works but when I try to run via the master process uwsgi.service, it fails. Have the semantics around the master process changed?
[19:11] <tomreyn> LukeHoersten: possibly related bug 1986866
[19:12] <LukeHoersten> Oh perhaps
[19:12] <LukeHoersten> Thank you
[19:13] <tomreyn> LukeHoersten: you're welcome - it would be good to confirm this report in case it turns out to be the cause of those issues.
[19:14] <LukeHoersten> I'm not sure if this is my issue but through process of elimination am almost certain there is a bug with the master uwsgi service (which could be python3 related as you pointed to)
[19:14] <LukeHoersten> Not sure how to confirm that though
[19:15] <tomreyn> upstream (the uwsgi developers / community) may be able to help you clarify see also the linked upstream bug report
[19:16] <tomreyn> i.e. i guess you would see python error messages or warnings
[19:16] <LukeHoersten> I haven't been able to collect any useful debug output
[19:16] <LukeHoersten> Its been a struggle tbh
[19:16] <LukeHoersten> Basically log output just says "failed"
[19:17] <tomreyn> not too useful ;)
[19:17] <LukeHoersten> Haha no - I'll take a look in a bit but I'm glad I have a workaround
[19:17] <tomreyn> i'm afraid i know nothing about uwsgi, can't help
[19:17] <tomreyn> maybe try #python, too
[19:18] <LukeHoersten> They've been helping me. We had no more ideas before I came here
[19:19] <tomreyn> you probably read https://uwsgi-docs.readthedocs.io/en/latest/Logging.html
[20:45] <alxndr>    Hi, I just upgraded my Desktop installation from 20.04 to 22.04, and now the Windows/Super key switches keyboard layouts just by tapping it, all other shortcuts for that key don't seem to work. Any idea how to fix this?
[20:52] <alxndr> Ah, found it: https://winaero.com/single-key-shortcut-change-keyboard-layout-gnome-3/
[21:38] <nuala> Hello, I could need some help fixing my boot process. I had an encrypted 20.04 installation, generally following [https://help.ubuntu.com/community/Full_Disk_Encryption_Howto_2019]. I have a LUKS1 partition which I believe holds /boot and a LUKS2 partition group holding two partitions /home and /{rest}.
[21:38] <nuala> I had a defunct win partition too. I installed 22.04 (unencrypted) on this defunct partition and been very naive/ignoring to setup boot process correctly. Now GRUB only offers me to boot into 22.04 or windows, but not 20.04 anymore.
[21:38] <nuala> How can I get both 20.04 and 22.04 as boot option?
[21:43] <tomreyn> nuala: you should probably chroot repair your 20.04 installation from your running 22.04 installation. after backing up what you haven't backed up, yet.
[21:48] <nuala> I should double check the backups are in order, thanks! With chrooting you mean a process akin to https://askubuntu.com/questions/145241/how-do-i-run-update-grub-from-a-livecd ? or how would i go forward with this? I am currentlly booted into 22.04 live usb fwiw....
[21:49] <nuala> (like i assume the final magic would be `sudo update-grub` after mounting/chrooting 20.04 in a "smart way"?
[21:51] <tomreyn> nuala: yes, that's pretty much it. you would also need to mount the efi system partittion if you're booting in efi mode.
[21:51] <tomreyn> nuala: actually, if you also want to keep the 22.04 installation, you probably need to make sure that you merge both grub configurations
[21:52] <tomreyn> the one of the 20.04 installation and the one of the 22.04 installation. a way around this would be to install grub twice in case you are efi booting
[21:53] <nuala> yes, keeping both would be perfect. (i could also re-do a 22.04 installation if that would be easier, 22 installation  doesnt hold anything of value yet)  The efi system partition would be what i have in the LUKS1 container?
[21:53] <tomreyn> (this would not work so easily with classic bios booting)
[21:53] <nuala> nah, efi booting all the way I 'believe'. its a newer mashine, no need for legacy i think.
[21:53] <tomreyn> efi must be unencrypted, because the 'bios' accesses it
[21:54] <tomreyn> you'd be looking for a 100-500 MB partition with a VFAT / FAT32 file system
[21:54] <nuala> ah yes! uh... i have... two? ok. one FAT16 one FAT32. i go with the fat32 then
[21:55] <tomreyn> better double check, it could be the fat16 as well, i think
[21:56] <nuala> the 16 is empty. nods. I mean worst (reasonable) case, nothing would boot and I fix from live usb. Data loss is possible but not likely unless i delete a partion?
[21:56] <tomreyn> your 22.04 system will have in /etc/fstab a reference to what it thinks is the efi system partition as /boot, and so will the 20.04 installation
[21:56] <nuala> i see!
[21:57] <tomreyn> it's easier to accidentially delete or overwrite data on a different parttion that many think. but, yes, theoretically you'd be safe.
[21:58] <tomreyn> if your data has value to you, you'll back it up.
[21:58] <tomreyn> (and not just now, but regularly, which would also make it an easier decision now, if you did it regularly)
[21:59] <nuala> nods. (It's hard to respond to this.. still fearing I ate my own words here. But backups should be in order :> )
[22:00] <nuala> like, yeah: regular backups. and yes: also make sure they work. cause a 'backup' you can not apply is pretty much worthless!
[22:01] <tomreyn> exactly
[22:04] <nuala> so it seems both 2{0,2}.04's fstab point at /bboot/efi aka /dev/nvp1, same UUID. for 20.04 further referenfces /dev/mapper/ubuntu-vg-root for / as well as /dev/maper/LUKS_BOOT for /boot 22.04 only knows of one partition for the full system. How would i puzzles this together?
[22:07] <tomreyn> nuala: i think i would have two copies of grub and configure those differently.
[22:10] <nuala> like: on power on using "22.04's grub" which holds an option to start into "20.04's grub"? that sounds reasonable
[22:10] <tomreyn> i.e. you'd just cp -r /boot/efi/EFI/ubuntu to /boot/efi/EFI/ubuntu2  and then use sudo efibootmgr --verbose   and add a new Bootnnnn record to point to the ubuntu2
[22:11] <tomreyn> i'm just not sure how to make the installation which the ubuntu2 grub will point to aware that it should be upgrading the *ubuntu2* grub and not the *ubuntu* grub in the future
[22:12] <tomreyn> EriC^: are you around by chance, and can suggest how to have two uefi ubuntu installations side by side?
[22:12] <EriC^> on 2 disks?
[22:12] <nuala> single hard drive
[22:13] <tomreyn> one is 20.04 with encrypted /boot (LUKS1), the other is unencrypted 20.04
[22:13] <tomreyn> one is 20.04 with encrypted /boot (LUKS1), the other is unencrypted 22.04
[22:13] <nuala> ubuntu-old has LUKS1 + LUKS2 encryption. ubuntu-new doesnt need encryption but could if it makes stuf "easer". Correct &
[22:13] <nuala> ^
[22:15] <tomreyn> https://askubuntu.com/questions/617045/ discusses this
[22:16] <EriC^> you could use the encryption one's grub to boot both, and maybe hold the grub package in the unencrypted one so it doesnt overwrite the main grub that boots
[22:18] <tomreyn> so this would be the variant where you'd need to merge the configuration files
[22:19] <tomreyn> and uninstall grub from one of the ubuntu installations, to prevent them to fight with one another.
[22:19] <nuala> oh 'holding packages' is like telling apt-update to not update these packages. I try to understand the last part EriC said. That would be fine
[22:19] <EriC^> no can do i think, will want some bootloader as dependency
[22:19] <nuala> it can be semi-persistent. the idea is to try 22.04 for some time, while keeping 20.04 functional before desciding to make the change
[22:20] <EriC^> nuala: yeah apt-mark hold grub-efi-amd64.. bla bla hold the packages so grub-install never runs
[22:20] <tomreyn> ah that's because grub-install only runs automatically as a post-install hook, right
[22:21] <tomreyn> i guess this could work
[22:21] <nuala> (thanks for clearifying, just trying to keep up) :)
[22:21] <EriC^> if they share the same efi dir, just run grub-install from the encrypted one to overwrite stuff there
[22:21] <EriC^> yeah if the grub packages get updated, they'd run grub-install
[22:22] <tomreyn> EriC^: what did you think of the other approach i suggested, having two independant grub installations?
[22:23] <tomreyn> i guess i'd call one efi directory "ubuntu20.04" and the other "ubuntu22.04" hoping that grub will notice which one it is meant to keep updated
[22:23] <tomreyn> or would it keep trying to write to an "ubuntu" directory"?
[22:24] <EriC^> i think it would just by default use efi/ubuntu, he'd have to create a separate efi partition for each, not sure
[22:24] <tomreyn> :-/ okay, so then your approach is definitely better
[22:24] <EriC^> but im not aware of any config where one can rename the efi/ubuntu name so when grub-install runs it uses that name instead
[22:25] <tomreyn> right, thinking about it i'm not sure how it could actually reliably tell how it was booted
[22:26] <tomreyn> other then BootCurrent in efibootmgr i guess
[22:26] <EriC^> he'd always have to get rid of the grub-install efibootmgr part of upgrades somehow, cause that would just reset his usual booting order
[22:26] <Guest94> Haven't installed ubuntu for a while. The default gnome shell extensions are just the ubuntu shell and desktop icons correct?
[22:27] <tomreyn> i see, EriC^
[22:28] <nuala> Guest94: I assume the extensions are mostly meant for 'vanilla ubuntu' running the Gnome desktop. As in: with KDE these probably would not do much. That in extensions also effects the desktop icons.
[22:30] <tomreyn> nuala: i usually work around these boot complications by just having one OS installed, and booting what i like to try  / test  / whatever in a VM instead. had you considered this?
[22:30] <nuala> thank you a lot EriC^ i can only follow half of it but it sounds great. And while random highlighing: everyone thanks a lot for 22.04 honeslty for the past 3 LTS it always seems to become even better.
[22:30] <nuala> tomreyn: I need to take it a step further out of VM sadly :(
[22:30] <tomreyn> due to hardware limitations?
[22:31] <nuala> 3d acceleration stuff? some tools/clients do some fancy stuff I could not get working with e.g. vbox
[22:32] <nuala> but so: it could be a temperary fix. I could like keep a usb stick handy to redo whatever grub magic I do in case an update messes this up. it should just be like this for a few weeks...
[22:32] <tomreyn> if you have two GPUs you can also use kvm frame relay
[22:33] <tomreyn> for just a few weeks, i'd personally want even less to go through this pain ;)
[22:34] <nuala> blushes.idontreallyknow.ilikedodockerandphpmostly. -_- ^^;  could we kinda go this way: using the 'good old encrypted grub' and tell them about the new grub, and [holding back 22.04 grub updates/i make notes what to do when i update 22.04]
[22:34] <nuala> see, i do php i have higher pain tolerance :P
[22:34] <tomreyn> hehe
[22:35] <nuala> ok but really: if its too much to ask thats fine too. i guess i should just somehow restore the 20.04 though and scrap the 22.04 experiment
[22:35] <tomreyn> nuala: well, i think you already know how to do it, isn't it? you just summed it up.
[22:37] <nuala> 1) old grub + new grub + [hold packages/breath through the pain]? yes in laymens terms. 2) restoring 20.04: i assume thats just the fix boot process like i linked earlier mount /boot, /sys etc. and run update-grub
[22:38] <nuala> i assume 1) is not too diferent from 2) but i can not really see it. :S what i would need to mount where besides the 'obvios' /sys /proc etc. (can guess what they do but i just follow recipes here). I assume i would mount /old-boot too. and then 'merge' the files. to introduce new-boot. I dont know how to do the last part
[22:40] <tomreyn> so mount the 22.04 installation + efi system partition, copy the 22.04 installation's grub.cfg into the mount, chroot on the mount, edit the copied grub configuration so it can add to the existing grub.cfg by placing it in /etc/grub.d/40_custom (as a template) or /boot/grub/custom.cfg (as a fixed configuration)
[22:41] <tomreyn> then update-grub and grub-install (to make sure you have a grub that is compatible with the 20.04)
[22:42] <tomreyn> then leave the chroot and, back on the 22.04 installation, apt mark hold grub-efi
[22:42] <nuala> got it! thanks a bizllion times for typing that out <3
[22:43] <tomreyn> this is all theory, i hope it works out in practice ;)
[22:43] <tomreyn> you will definitely need to modify the copied grub.cfg
[22:43] <nuala> (fwiw, *mount 20.04[!] installation+efi then copy 22.04 i assume?)
[22:46] <tomreyn> nuala: right, i mixed them up again
[22:47] <tomreyn> so mount the 20.04 installation + efi system partition, copy the 22.04 installation's grub.cfg into the mount, chroot on the mount, edit the copied grub configuration so it can add to the existing grub.cfg by placing it in /etc/grub.d/40_custom (as a template) or /boot/grub/custom.cfg (as a fixed configuration)
[22:47] <tomreyn> then update-grub and grub-install (to make sure you have a grub that is compatible with the 20.04). then leave the chroot and, back on the 22.04 installation, apt mark hold grub-efi.
[22:47] <nuala> wait what? ^^ oh my the grub files are pretty different. I guess that is the hard part....? `diff grub*|wc` yields 350 lines T_T
[22:48] <nuala> good hint to modify the copied grub file...
[22:49] <tomreyn> if you'll want the templating (which you probably want, since the kernel version will be raised occasionally, breaking paths) your /etc/grub.d/40_custom should really just contain one or two "menuentry" sections. plus maybe some code to identify what the correct kerbel image is.
[22:50] <tomreyn> * kernel image (and initrd)
[22:51] <tomreyn> or you can just make grub interpret the entire 22.04 configuration file like this: https://unix.stackexchange.com/questions/65684/adding-another-linux-system-to-grub-2
[22:51] <tomreyn> maybe thats the easier and more failsafe approach
[22:52] <nuala> i see. there or some function defintions too (i assume thats what it is). if I add it as 40_custom the configs would incrementally be read in some way? The hint with the menuitems looks good. Or the link, that looks nice and sweet.
[22:53] <nuala> i mean a naive, 'max pain, way would be to pick whatever grub.cfg i would need, and to the update-grub-dance via live usb according whether i want to boot 20. or 22. (nothing holds longer than a temporary fix)
[22:53] <tomreyn> what you add to /etc/grub.d/40_custom is interpreted when update-grub runs, in the same way that all the other files there are. the linux_10 file is what generates most of the resulting grub.cfg.
[22:54] <nuala> but I feel very well equipped now. Thank you for explaining some of the details for me. To an extend also from my circle, where I can spread the knowledge once I understood :)
[22:55] <tomreyn> i think your best approach is really loading and using the original 22.04 grub.cfg off it's boot partition ("set root=...") using the "configfile" approach
[22:55] <nuala> so if two files would define the same.. lets say `function savedefault` or set something like `set boot_once=true` the {first|last} file would win.
[22:55] <nuala> ?
[22:56] <nuala> *original 20.04 grub.cfg (? sorry, it is super confusing ^^) yes. I will try this!
[22:56] <tomreyn> i think both would win, adding each of the functions' to the generated grub.cfg
[22:57] <tomreyn> i think you said you want to keep the grub installation maintained yb the encrypted 20.04 installation
[22:58] <tomreyn> if that's what you want, then this should also be the installation which runs update-grub
[22:58] <tomreyn> so the 20.04 one
[22:58] <nuala> ufff. Yes. You were referencing the last link. Yes!
[22:58] <tomreyn> right
[22:59] <nuala> I see. My bad :) Golly. I probably did not say thank you so I do it now :) And thanks to everyone else to stand my noise <3
[23:01] <tomreyn> so if the 20.04 manages the grub configuration, your easiest option to have both grub configurations available is to have the 20.04 update-grub + grub.cfg refer to the 22.04 grub.cfg by means of a custom (/boot/grub/custom.cfg) configuration which contains just something very similar to the verbatim code in the first answer of https://unix.stackexchange.com/questions/65684/adding-another-linux-system-to-grub-2
[23:02] <tomreyn> "set root=(hd0,7)" would need to be replaced by whatever grub thinks is the 22.04 /boot file system.
[23:02] <tomreyn> note that grub starts counting disks and partitions at 0.
[23:03] <tomreyn> so (hd(0,0) is the first partition on the dirst installed disk
[23:03] <tomreyn> *first
[23:04] <tomreyn> and you're welcome, good luck, nuala
[23:05] <tomreyn> and don't forget to   apt-mark hold grub-efi   on the 22.04
[23:05] <jim__> does anyone know how to configure ubuntu to recognize all cellphone types . the hard drive part of the cell phone so that when i open disk tool the cell [hones will show up as a disk automatically?
[23:05] <nuala> Looks like the easiert/most maintain free solution, yes. I feel like learning a lot more bout GRUB and booting. Awesome :) [I will probably try it tomorrow with a good sleep and ... another backup :}. <3 ]
[23:06] <llanhmod> jim__: usually, I would install the supported driver for the device....i.e samsung device driver...etc.
[23:06] <jim__> @nuala it can always be worse , to learn grub and then sleep some would say is heaven
[23:06] <nuala> (awww <3)
[23:06] <tomreyn> don't try to create the perfect grub solution, you will just go insane because it will always seem to *almost* work, but not really. ;)
[23:06] <jim__> thanks im going to try that approach , i was looking for a universal solution , thanks
[23:07] <nuala> jim__: I'd also recon it could be cellphone dependent.. Like which options are active, but that easily could have changed since android >5
[23:07] <llanhmod> silver bullets usually aren't a thing in software but...never know.
[23:10] <nuala> (( i mean... if you only hustle with Ganon silvers are optional...))
[23:10] <tomreyn> my point was: do the 'simple' configuration first, make sure this orks. you can still improve things once that's working.
[23:11] <tomreyn> *works
[23:14] <nuala> oh yes. We carved out like... 2, 3 different ways to approach this issue? I will try out some and feel like if something stops working some time away I know which place to look at <3
[23:22] <tomreyn> hehe, yes, should be so. good luck.
[23:54] <cluelessperson_> how can I disable *certain* *specific* media keys in ubuntu