[14:19] <cristian_c> tomreyn, I suppose it's the right channel (a bit little)
[14:20] <cristian_c> I'm trying to install to a gpt disk as target
[14:20] <cristian_c> partitionmanager, file manager and fdisk properly detect and mount gpt disk and its partitions
[14:21] <cristian_c> but calamares installeer does not detect gpt disk
[14:21] <cristian_c> I don't know why, how to configure calamares in order to do that and allowing os installation?
[14:21] <cristian_c> any ideas?
[14:22] <tomreyn> for reference, cristian_c previously asked about this - apparently a Lubuntu 23.10 installation - in #ubuntu, and i suggested to ask in the flavor channel for greater experience with Calamares.
[14:25] <tomreyn> cristian_c: please be patient, it *can be* hours or rarely days before someonee who knows gets around to answer
 Try manual partitioning?
[14:28] <cristian_c> tomreyn, it's not properly suitable monitoring this channel for days all the time
[14:29] <tomreyn> cristian_c: you already got qualified feedback
[14:29] <cristian_c> tomreyn, I was talking about last line
[14:30] <tomreyn> i understand. could you respond to tsimonq2's question?
[14:30] <cristian_c> ah, didn't know someone had replied to me
[14:31] <cristian_c> tsimonq2, yeah, selected but calamares doesn't detect the gpt disk
[14:31] <cristian_c> even if I click next after selecting manual partitioning
[14:31] <cristian_c> drop-down menu does not detect gpt disk in all the screens
[14:32] <cristian_c> (sorry for having typed many lines)
[14:34] <arraybolt3> cristian_c: Are you trying to install to the same disk you booted from?
[14:35] <arraybolt3> Calamares specifically hides the disk you booted from so you don't overwrite the installation media, and that behavior cannot (currently) be overridden.
[14:35] <cristian_c> arraybolt3, no, I don't
[14:36] <cristian_c> it's not the live media
[14:36] <cristian_c> live media has msdos partition table
[14:36] <arraybolt3> hmm...
[14:37] <arraybolt3> ok, can you share the output of `fdisk -l` with us via a pastebin?
[14:37] <arraybolt3> fdisk -l | nc termbin.com 9999
[14:37] <tomreyn> you might need to run fdisk with sudo
[14:39] <cristian_c> yes
[14:39] <cristian_c> I've to enable network before
[14:41] <cristian_c> arraybolt3, uhm, live media is gpt, you was right, i didn't know
[14:42] <arraybolt3> It being GPT isn't an issue, it's only a problem if you booted from the USB drive and now want to install to that same USB drive.
[14:43] <arraybolt3> I'm fuzzy on the detail, it might refuse to install to any drive with an ISO9660 partition on it, but I'm not sure.
[14:43] <cristian_c> ok, https://termbin.com/c8xj
[14:44] <cristian_c> Disk /dev/sdd: 931.51 GiB, 1000204886016 bytes, 1953525168 sectors
[14:44] <arraybolt3> I assume /dev/mapper/ventoy is your USB drive you booted Lubuntu from, right?
[14:44] <cristian_c> it's the live media
[14:44] <cristian_c> sdb
[14:44] <cristian_c> sdd target gpt disk
[14:45] <arraybolt3> right, then Cala *should* show it, obviously it doesn't though, lemme see...
[14:45] <arraybolt3> also did you boot in UEFI or BIOS mode, do you know?
[14:45] <cristian_c> I've created /dev/sdd2 yesterday IIRC
[14:46] <cristian_c> arraybolt3, there is only bios mode but I get these issues only with calamares and 23.10
[14:47] <cristian_c> it didn't happen using ubiquity
[14:47] <arraybolt3> hmm, om
[14:47] <arraybolt3> *ok
[14:49] <arraybolt3> What drop-down are you looking for your GPT disk in? Can you screenshot it?
[14:49] <cristian_c> gpt is more suitable than msdos when you have to create multiple partitions
[14:49] <arraybolt3> I notice you have only one msdos disk and none of the gpt disks have a bios-boot partition.
[14:49] <arraybolt3> So i'm wondering if you're trying to select a gpt disk for bootloader installation, which won't work in this configuration.
[14:50] <cristian_c> Partitions module has two drop down menus: one for selecting the target disk, the other for installing bootloader
[14:50] <cristian_c> the first in the top, the second in the bottom
[14:50] <arraybolt3> Right.
[14:51] <arraybolt3> I'm wondering which of the two is missing the gpt disk.
[14:51] <cristian_c> first drop-down menu: "select a storage device:"
[14:51] <cristian_c> arraybolt3, both
[14:51] <cristian_c> sorry, the first: "storage device:"
[14:52] <cristian_c> the second: "install boot loader to:"
[14:53] <cristian_c> the first menu shows only /dev/sda, the second shows /dev/sda and "don't install boot loader"
[14:53] <cristian_c> arraybolt3, I don't know if screen is needed
[14:54] <arraybolt3> Ah, that makes more sense.
[14:54] <arraybolt3> Except it doesn't really... I'm smelling a Calamares bug.
[14:55] <cristian_c> arraybolt3, to be sure, I've connected another msdos disk before and it's detected by calamares
[14:55] <cristian_c> so I think there is an issue with gpt disks
[14:55] <arraybolt3> The top menu *should* display all disks, but yeah, it looks like it only shows MSDOS ones.
[14:55] <arraybolt3> hmm... so now the question is how to work around that.
[14:56] <cristian_c> I could try to use another installation method, different by calamares
[14:56] <arraybolt3> This is Lubuntu 22.04?
[14:56] <cristian_c> 23.10
[14:56] <arraybolt3> kk
[14:56] <cristian_c> but I don't knw a different installation method on *buntus
[14:57] <arraybolt3> Well... there is one way we could do it, it's hacky but it might work.
[14:57] <arraybolt3> install Ubuntu via debootstrap and chrooting, then add the lubuntu-desktop package on top
[14:58] <cristian_c> I'm used to use hacky methods to get results, nothing new
[14:58] <arraybolt3> K. Also, we'll try and diagnose why it's glitchy here and hopefully get it fixed.
[14:58] <cristian_c> arraybolt3, I'd like to get the same final result as I was installing lubuntu through live media
[14:59] <arraybolt3> OK, got to an actual computer so I can say what to do.
[14:59] <cristian_c> I mean: with the same installed packages, not just a minimal installation
[14:59] <arraybolt3> Correct. That's the intended end goal.
[14:59] <cristian_c> ok, thanks
[14:59] <arraybolt3> lemme look at the disk layout...
[14:59] <arraybolt3> which partition are you trying to install Lubuntu into?
[14:59] <cristian_c> I've chosen to install lubuntu 23.10 in order to prevent to make a very loooong post-installation
[14:59] <cristian_c> and configuration
[15:00] <arraybolt3> are you trying to install it to /dev/sdd2?
[15:00] <cristian_c> arraybolt3, I've created /dev/sdd2 of about 100 GB
[15:00] <cristian_c> ext4
[15:01] <arraybolt3> kk, make good and sure that's the right partition, since that's what I'll tell you to modify from this point forward.
[15:01] <cristian_c> (I've accidentally labeled it 2304 during formatting :P)
[15:01] <arraybolt3> heh, I've done stuff like that too
[15:01] <arraybolt3> OK, so open a terminal if you don't have one open already, and run `sudo su -` to get a root shell.
[15:01] <cristian_c> it's empty currently, I can mount it in pcmanfm and it's empty
[15:01] <arraybolt3> +1
[15:02] <cristian_c> ok (I've got already a connection active, if needed)
[15:02] <cristian_c> ok, done
[15:02] <cristian_c> (I don't remember the meaning of dash)
[15:03] <arraybolt3> nice, next let's unmount /dev/sdd2, then make a directory at /install so we know where we're installing things into, then mount /dev/sdd2 to /install. `umount /dev/sdd2; mkdir /install; mount /dev/sdd2 /install`
[15:03] <cristian_c> I0ve unmounted from pcmanfm to save time
[15:04] <arraybolt3> The dash tells "su" to start a login shell, so basically "sudo su -" means "run as root, run a login root shell".
[15:04] <arraybolt3> I think it has a bit more predictable behavior than `sudo bash`.
[15:05] <arraybolt3> anyway, with that done, let's put the base install on the drive. `debootstrap mantic /install`
[15:06] <arraybolt3> this is a very minimal Ubuntu installation that's missing almost everything, we're going to install the Lubuntu packages on top in order to make it a non-minimal Lubuntu installation instead.
[15:07] <cristian_c> ah, ok mantic minotaur 23.10
[15:07] <cristian_c> ok, I install debootstrap, first
[15:08] <cristian_c> ok, it's making the job
[15:08] <arraybolt3> nice, that'll download things for a bit and unpack them into /install, which should be putting them on /dev/sdd2.
[15:09] <cristian_c> until now, it's the easiest part
[15:10] <cristian_c> arraybolt3, apart lubuntu-desktop meta-package I don't exactly how to get a standard (complete?) desktop
[15:10] <cristian_c> aka lbuuntu installed by live media
[15:10] <arraybolt3> right, that's part of the process.
[15:10] <arraybolt3> debootstrap however gives us an install that is way too minimal to just add lubuntu-desktop on top of and be done. We have to do things like installing the kernel and bootloader, adding users, etc. manually.
[15:11] <arraybolt3> I have a guide I made on how to do this for VMs, I'm basically taking the concepts from that and applying it to a physical system.
[15:11] <cristian_c> I'd like to make things properly
[15:11] <arraybolt3> That's what this will do.
[15:12] <cristian_c> base system installed successfully
[15:12] <arraybolt3> nice. Alright, now run the following five commands, one at a time, to "enter" the installed system:
[15:12] <arraybolt3> mount --bind /dev ./vdisk/dev
[15:12] <arraybolt3> er, no
[15:12] <arraybolt3> gah, copypasting from my guide :P
[15:12] <arraybolt3> mount --bind /dev /install/dev
[15:12] <arraybolt3> mount --bind /dev/pts /install/dev/pts
[15:12] <arraybolt3> mount --bind /sys /install/sys
[15:12] <arraybolt3> mount --bind /proc /install/proc
[15:13] <arraybolt3> chroot /install
[15:13] <arraybolt3> That will give the installed system access to some critical files it needs for things to work, then chroot in so you can run commands within it.
[15:14] <cristian_c> done
[15:15] <cristian_c> yeah, I've get binded some directories from host system (live media) to (chrooted) target system
[15:15] <arraybolt3> alright, this is the tricky part. By default only the `main` repo is enabled, we need all four repos (main, universe, restricted, and multiverse) for this to be right, plus we need all four repo pockets (release, security, updates, backports) enabled. So... run `apt install nano` so we can do that easily.
[15:15] <cristian_c> luckily it's not vi(m)
[15:16] <arraybolt3> also what country are you in? That will affect which Ubuntu mirror you want to use.
[15:16] <cristian_c> nano installed
[15:17] <cristian_c> arraybolt3, I don't know what's the best mirror, I think most used standard mirror it's ok
[15:17] <cristian_c> arraybolt3, but european mirror it's ok
[15:18] <cristian_c> arraybolt3, nano /etc/apt/sources.list?
[15:18] <arraybolt3> yep
[15:18] <cristian_c> there is just one line, sigh
[15:18] <arraybolt3> we'll use nl.archive.ubuntu.com, should be somewhat close to where you are
[15:19] <cristian_c> ok
[15:19] <arraybolt3> right, that's what we're going to fix.
[15:19] <arraybolt3> OK, so press Ctrl+K to get rid of that one line.
[15:19] <arraybolt3> then type:
[15:19] <arraybolt3> deb http://nl.archive.ubuntu.com/ubuntu mantic main universe restricted multiverse
[15:20] <cristian_c> maybe using pastebin it's the best way
[15:20] <arraybolt3> easy, one sec
[15:20] <cristian_c> in order to save time
[15:20] <cristian_c> so, i can copy-paste if needed
[15:20] <arraybolt3> https://dpaste.com/5JT7N3VTE
[15:21] <cristian_c> thanks
[15:21] <arraybolt3> once that's in the file, save and close, then run `apt update`.
[15:24] <cristian_c> the page didn't load, now it's ok
[15:26] <cristian_c> 29 packages can be upgraded
[15:26] <cristian_c> too many little
[15:27] <arraybolt3> Right, we don't need to worry about that right now.
[15:27] <arraybolt3> We just needed those repos since that's what allows us to install lubuntu-desktop at all.
[15:27] <arraybolt3> OK, with that done, this command should install most of everything, then we just need some final clean-up work after.
[15:27] <arraybolt3> apt install lubuntu-desktop linux-generic grub-pc network-manager
[15:28] <arraybolt3> that will download a huge amount of stuff and will take a while to install it all
[15:30] <cristian_c> 1618 new packages to install
[15:31] <cristian_c> it's making the job
[15:31] <cristian_c> arraybolt3, maybe, I've made a mistake
[15:31] <arraybolt3> how so?
[15:32] <arraybolt3> The number of packages it wants to install sounds about right.
[15:32] <cristian_c> I mean, maybe I should not install grub-pc since I should change target bootloader disk
[15:32] <cristian_c> I always can reinstall bootloader next
[15:32] <cristian_c> (I hope)
[15:33] <arraybolt3> oh, installing grub-pc won't install the bootloader yet.
[15:33] <arraybolt3> It will install the packages for it though.
[15:33] <arraybolt3> Installing the bootloader to a disk is a later step.
[15:33] <cristian_c> (probably installing bootloader to /dev/sda is a better choice)
[15:34] <cristian_c> arraybolt3, I thought installing linux-generic will run update-grub too
[15:34] <cristian_c> without interaction by user
[15:34] <arraybolt3> update-grub doesn't actually install the bootloader either.
[15:34] <arraybolt3> It generates a configuration file.
[15:34] <cristian_c> sorry, grub-install
[15:35] <arraybolt3> hmm, you might be right, though currently grub would have to just guess at which disk you wanted to install to, which I don't think it will do (it hasn't done it to me).
[15:35] <cristian_c> consider, it's a wifi g network card
[15:36] <cristian_c> arraybolt3, I hope it will not abort entirely when it wll find efi partition
[15:36] <cristian_c> on /dev/sdd
[15:36] <arraybolt3> it shouldn't, I do BIOS installations into virtual machines quite a bit on my UEFI-based machine.
[15:36] <cristian_c> or make some mess installing on /dev/sdd gpt
[15:37] <cristian_c> *or making
[15:37] <arraybolt3> I've tried to install GRUB onto drives it shouldn't install on before, it's pretty good at determining when it might make a mess and refusing to do so.
[15:37] <cristian_c> as I said, it's MY mistake, I had to specify before running apt install, sorry
[15:39] <cristian_c> btw, I'm downloading linux-firmware package, currently
[15:41] <cristian_c> ok, now linux-modules 6.5.0
[15:42] <cristian_c> arraybolt3, do you know if linux 6.6 is already available in ubuntu official repo
[15:42] <cristian_c> ?
[15:42] <arraybolt3> I don't know for sure, however 6.5 is the only generic kernel Mantic will have since it doesn't get HWE kernels.
[15:42] <arraybolt3> HWE = hardware enablement, LTS releases get newer kernels every so often so they work on newer machines
[15:42] <cristian_c> ok, so deb from ppa kernel team
[15:43] <arraybolt3> whereas interim releases like Mantic just get one kernel and then they're so short-lived you're expected to upgrade to the next release when it comes out
[15:44] <cristian_c> ok, it has almost finished the download of packages
[15:45] <cristian_c> I suppose I've install language packs
[15:45] <cristian_c> *to install
[15:45] <arraybolt3> LXQt has most translations built into it.
[15:45] <arraybolt3> About the only program you'll need extra translations for is LibreOffice.
[15:46] <arraybolt3> we can do that pretty easily here.
[15:46] <cristian_c> ok, it's not needed, then
[15:46] <cristian_c> I just hoped to avoid extra work for most parts, so, it's ok
[15:47] <arraybolt3> that makes senese
[15:47] <arraybolt3> *sense
[15:53] <cristian_c> unpacking step has finished
[15:53] <cristian_c> setting up linux-modules 6.5.0
[15:54] <arraybolt3> nice, sounds like we're close
[15:54] <cristian_c> setting up linux-image 6.5.0
[15:54] <cristian_c> 60% progress
[15:58] <cristian_c> progress 99%
[15:59] <cristian_c> processing triggers for linux-image 6.5.0
[16:00] <cristian_c> arraybolt3, done
[16:00] <arraybolt3> nice
[16:00] <arraybolt3> ok, so now for the bootloader, we can't install it to /dev/sdd since it's a gpt disk without bios-boot
[16:00] <arraybolt3> so lemme refer to the drive layout again...
[16:01] <cristian_c> https://termbin.com/c8xj
[16:01] <arraybolt3>  /dev/sda is your boot drive right?
[16:01] <cristian_c>  /dev/sda is built-in disk
[16:01] <cristian_c>  /dev/sdd is target gpt disk
[16:01] <arraybolt3> right
[16:02] <arraybolt3> so the bootloader should be on /dev/sda and then it can boot the system from /dev/sdd2 (and the other systems you have installed if any)
[16:02] <cristian_c> it's preferable to install grub to /dev/sda because it can brings less trouble at boot
[16:02] <arraybolt3> kk, `grub-install /dev/sda && update-grub` should work
[16:02] <cristian_c> arraybolt3, because grub lists boot entries on both disks
[16:03] <arraybolt3> right. The config file with all your distros will be on /dev/sdd2 but it should be able to boot any of your operating systems.
[16:03] <cristian_c> so, it's not important if lubuntu is installed on a different disk than bootloader
[16:03] <arraybolt3> correct
[16:04] <arraybolt3> (I've done installs with the bootloader on one drive and then everything else on a different drive in order to work with limitations before, worked just fine.)
 kk, `grub-install /dev/sda && update-grub` should work <- should I type this now (inside chroot)?
[16:04] <arraybolt3> yes
[16:05] <arraybolt3> once that's done, we need to tell Lubuntu which drive it should mount as root. There are a few ways of doing this, the one I prefer is to label the installed partition (/dev/sdd2 in this instance) and then use that in fstab.
[16:05] <cristian_c> installing for i386-pc platform
[16:06] <cristian_c> installation finished. No error reported.
[16:06] <cristian_c> this is output from first command, I guess
[16:06] <arraybolt3> correct
[16:07] <cristian_c> sourcing file, sourcing file ... grub theme ...
[16:07] <arraybolt3> that's the update-grub command, sounds normal
[16:07] <arraybolt3> one line you do want to look for is something about os-prober not being run. If you see that, we need to fix something real quick.
[16:08] <cristian_c> found linux image ... 6.5.0 ... found initrd image ... 6.5.0 ... grub-probe: error: cannot find a grub drive for /dev/sdb2 check your device map
[16:08] <cristian_c> arraybolt3, but it's expected since sdb it's live media
[16:09] <arraybolt3> sounds like os-prober probably was used
[16:09] <cristian_c> adding boot menu entry for uefi firmware settings ... done
[16:09] <cristian_c> yeah, there was warning os-prober will be executed to detect other bootable partitions
[16:09] <cristian_c> but I've omitted that
[16:10] <arraybolt3> kk, that sounds right
[16:10] <cristian_c> arraybolt3, so grub-install and update-grub have finished
[16:11] <cristian_c> arraybolt3, I think it lacks all the user/sysem configuration before exiting chroot
[16:11] <arraybolt3> true, we're not done quite yet
[16:11] <arraybolt3> Next we need to label the partition we just installed Lubuntu to so Lubuntu can mount it at boot.
[16:11] <cristian_c> I'm not sure if hostname and suchlike are needed
[16:11] <arraybolt3> yeah, that's probably important
[16:12] <arraybolt3> e2label /dev/sdd2 lubuntu-drive
[16:12] <cristian_c> users and groups and similar
 e2label /dev/sdd2 lubuntu-drive <- done
[16:13] <arraybolt3> echo "LABEL=lubuntu-drive / ext4 defaults 0 1" > /etc/fstab
[16:13] <arraybolt3> that will tell Lubuntu to mount the partition you just installed to when it boots
[16:14] <arraybolt3> after that we'll configure the user and hostname
[16:14] <cristian_c> I've made a mistake
[16:15] <cristian_c> I've not closed the "
[16:15] <cristian_c> arraybolt3, how to abort the command?
[16:15] <arraybolt3> Ctrl+C
[16:15] <arraybolt3> that's the "cancel" button in Bash
[16:16] <cristian_c> ok, i've repeated the command fixed but it has not added that line to /etc/fstab
[16:17] <cristian_c> it shows #UNCONFIGURED FSTAB FOR BASE SYSTEM
[16:17] <cristian_c> and nothing elese
[16:17] <cristian_c> *else
[16:17] <arraybolt3> odd, most likely a slash got forgotten somewhere
[16:17] <arraybolt3> nano /etc/fstab
[16:17] <arraybolt3> delete everything in it
[16:17] <arraybolt3> and then type:
[16:17] <arraybolt3> LABEL=lubuntu-drive / ext4 defaults 0 1
[16:17] <arraybolt3> save and close
[16:17] <cristian_c> ah, ok < instead of >
[16:18] <cristian_c> sorry, i missed that
[16:18] <arraybolt3> no problem
[16:18] <cristian_c> ok, now /etc/fstab is correct
[16:18] <arraybolt3> nice. For your username, use `adduser user`, replacing "user" with your intended username
[16:19] <arraybolt3> it will prompt you for some information, you can provide any of it you want, and leave any fields you don't want to fill out blank (except for the password).
[16:19] <arraybolt3> (it will ask for all sorts of odd stuff like what office you're in, I guess it's info that might be handy in a mainframe environment but that you don't need here)
[16:20] <cristian_c> info: adding user mantic to group users
[16:21] <arraybolt3> once that's done, `adduser mantic sudo` will allow your new user to run commands as root
[16:21] <cristian_c> done
[16:22] <cristian_c> arraybolt3, which groups calamares installer makes the user added to?
[16:22]  * arraybolt3 checks
[16:23] <cristian_c> so, I don't get rouble when rnning applications/stuff
[16:23] <arraybolt3> https://git.lubuntu.me/Lubuntu/calamares-settings-ubuntu/src/branch/ubuntu/noble/lubuntu/modules/users.conf
[16:23] <cristian_c> ok
[16:23] <arraybolt3> the list of groups is in the defaultGroups section
[16:23] <arraybolt3> so adm, cdrom, dip, lpadmin, plugdev, sambashare, and sudo
[16:23] <cristian_c> ah, should I add them masnually?
[16:24] <cristian_c> ah, ok
[16:24] <cristian_c> ok, always adduser
[16:25] <cristian_c> adduser mantic ad cdrom dip lpadmin plugdev samabashare
[16:25] <cristian_c> without permission attributes
[16:25] <cristian_c> (sudo was already added)
[16:25] <cristian_c> sorry, sambashare
[16:25] <cristian_c> *adm
[16:26] <cristian_c> ok, it doesn't work
[16:27] <arraybolt3> I think you need to do them one at a time
[16:27] <cristian_c> yep
[16:27] <arraybolt3> adduser doesn't take a list of groups unfortunately
[16:28] <cristian_c> done
[16:28] <arraybolt3> nice, next choose what hostname you want and then run `hostnamectl set-hostname computer`, replacing "computer" with your intended hostname
[16:29] <cristian_c> error, i guess
[16:30] <cristian_c> arraybolt3, System has not been booted with systemd as init system (PID 1). Can't operate
[16:30] <cristian_c> Failed to connect to bus: Host is down
[16:30] <arraybolt3> oh. Right, since we're in a chroot.
[16:30] <arraybolt3> in that instance we'll set the hostname later
[16:31] <cristian_c> arraybolt3, ah, not why lubuntu-desktop or network-manager didn't have that as dependency?
[16:31] <arraybolt3> when you install using debootstrap, it uses the parent system's hostname by default
[16:31] <cristian_c> ah, ok
[16:31] <arraybolt3> so currently the installed system's hostname is "lubuntu" since that's the live system's hostname
[16:32] <cristian_c> I thought hostname was a requirement though
[16:32] <cristian_c> to make system booting with the given user
[16:32] <arraybolt3> It is, but debootstrap took care of it already
[16:32] <arraybolt3> installers do usually require you to set the hostname yourself
[16:32] <arraybolt3> but in this instance it was chosen for us automatically and we can change it later.
[16:33] <cristian_c> so, what else is left (in chroot9
[16:33] <cristian_c> *(in chroot)?
[16:33] <arraybolt3> There's one file that might inhibit networking that we probably should move out of the way.
[16:33] <arraybolt3> mv /usr/lib/NetworkManager/conf.d/10-globally-managed-devices.conf /usr/lib/NetworkManager/conf.d/10-globally-managed-devices.old
[16:35] <cristian_c> arraybolt3, done
[16:36] <arraybolt3> and just one last thing, adduser did make you set a password, correct?
[16:36] <arraybolt3> If so, we can exit the chroot, and reboot.
[16:37] <cristian_c> conf.d lists just 10-dns-resolved.conf no-mac-addr-change.conf and 10-globally-managed-devices.old
[16:37] <arraybolt3> good
[16:37] <cristian_c> arraybolt3, ok, so just to type exit to exit the chroot?
[16:37] <arraybolt3> yep
[16:38] <cristian_c> root@lubuntu:~# instead of root@lubuntu:/#
[16:39] <cristian_c> arraybolt3, it has changed / into ~
[16:39] <arraybolt3> seems normal, type exit again
[16:39] <cristian_c> logout
[16:39] <arraybolt3> there's three shells - the one you started with, the one you got from sudo su -, and the one you got from chroot
[16:39] <cristian_c> yep
[16:39] <arraybolt3> and at this point try `reboot` and see what happens
[16:39] <cristian_c> I didn't remember I had typed sudo su -
[16:39] <cristian_c> ok
[16:40] <cristian_c> btw, I don't notice the partition in pcmanfm
[16:41] <cristian_c> I reboot
[16:41] <arraybolt3> that should be fine
[16:42] <cristian_c> ok, it appears a lubuntu fancy grub
[16:42] <cristian_c> not just the usual B&W text grub
[16:42] <arraybolt3> nice
[16:42] <cristian_c> ubuntu
[16:42] <cristian_c> advanced options for ubuntu
[16:42] <cristian_c> ....
[16:43] <arraybolt3> select Ubuntu
[16:43] <arraybolt3> the topmost Ubuntu is the boot entry for the new installation
[16:44] <cristian_c> it5 seems it has been fixed the alpine linux 3.19 entry generated from 40_custom by another os
[16:45] <cristian_c> (I've pressed 'e' to look under the entries under the hood)
[16:45] <cristian_c> -under
[16:45] <cristian_c> yeah, now I select ubuntu
[16:45] <cristian_c> (the top entry)
[16:46] <cristian_c> arraybolt3, first boot has been very long
[16:46] <cristian_c> grub screen has disappeared just now
[16:46] <arraybolt3> might just be a slow drive if it took that long for the GRUB screen to disappear
[16:47] <cristian_c> I'm on greeter screen, I suppose, I notice the pointer
[16:47] <arraybolt3> if it doesn't boot to a login screen, then probably something went awry with the fstab file
[16:47] <arraybolt3> ah, that's hopeful
[16:47] <cristian_c> it seems openbox/lxqt greeter screen
[16:48] <arraybolt3> nice
[16:48] <cristian_c> arraybolt3, ah, ok, there is a bug I've found also with alpine linux greeter scdreen (lxqt) layout is always us in greeter screen, it doesn't matter which layout is selected in the os
[16:48] <cristian_c> (i think it's sddm, btw)
[16:49] <arraybolt3> I think that's a known bug (it sounds vaguely familiar)...
[16:49] <cristian_c> *'us' (stars and stripes)
[16:49] <arraybolt3> I bet that's something we can fix
[16:50] <cristian_c> I don't know but greeter screen it's not important, I've just noticed it's a common issue between oses
[16:50] <arraybolt3> I'll look into it more, did it instantly change to the right layout when you started typing?
[16:50] <cristian_c> arraybolt3, now, i'm on lxqt desktop I guess, update notifier has been appared
[16:50] <arraybolt3> sounds like everything worked!
[16:50] <cristian_c> *appearing
[16:51] <cristian_c> arraybolt3, no, featherpad shows it's wrong (still 'us')
[16:51] <arraybolt3> oh, right, we didn't set the locale specifically yet
[16:51] <arraybolt3> one sec
[16:52] <cristian_c> timezone seems utc
[16:52] <cristian_c> from the clock
[16:52] <arraybolt3> I forgot about those parts needing to be set.
[16:52] <arraybolt3> Calamares does this all automatically, but manual installatiosn don't
[16:52] <cristian_c> and network connection is not set
[16:52] <arraybolt3> sorry about that
[16:52] <arraybolt3> I'm looking for what settings to change to fix that
[16:53] <cristian_c> no problem, it's my fault but it doesn't seems a big problem if I can do that easily from DE
[16:53] <arraybolt3> ok, so click on the application menu -> Preferences -> LXQt Settings -> Locale
[16:53] <arraybolt3> that should let you fix the language and keyboard layout
[16:53] <arraybolt3> and then application menu -> Preferences -> LXQt Settings -> Date and Time for fixing the timezone
[16:54] <arraybolt3> and it's not your fault, I'm the one who forgot those parts of the setup were important :P
[16:54] <cristian_c> There are upgrades available. Do you want to do a system upgrade? This will mean packages could be upgraded, installed or removed. 6 are security upgrades
[16:55] <arraybolt3> that's how Lubuntu lets you know updates are available. Generally it's a good idea to install those.
[16:55] <cristian_c> arraybolt3, I'm more worried by other things, btw
[16:55] <cristian_c> arraybolt3, ok, I do what you sugggested at first, before upgrading
[16:56] <arraybolt3> once the locale is changed, log out and log back in and your chosen language should be used
[16:56] <arraybolt3> and now my whole test system is in German and I can't see what I'm doing 😆
[16:57] <cristian_c> I leave rtc disabled
[16:58] <arraybolt3> the locale settings only change what language things display in, the keyboard layout has its configuration under application menu -> Preferences -> LXQt Settings -> Keyboard and Mouse
[16:58] <cristian_c> arraybolt3, odd, clock in the tray has a different gui than lxqt settings -> date and time
[16:59] <cristian_c> I've set timezone in date and time but world clock from tray shows timezone is empty
[16:59] <cristian_c> odd
[16:59] <arraybolt3> right, the date and time settings are for changing the actual date and time of the system, the clock settings are for changing how it's displayed to the user
[16:59] <arraybolt3> it is a slightly strange design decision by LXQt.
[16:59] <cristian_c> ok, I'm adding timezone in worldclock
[17:00] <cristian_c> ok, clock updated, now keyboard
[17:02] <cristian_c> arraybolt3, I suppose I've to select 'no dead keys' when I add the language
[17:02] <cristian_c> there was just us
[17:02] <cristian_c> ah, ok, none as variant, not no dead keys
[17:02] <cristian_c> sorry
[17:03] <cristian_c> and lifted up as primary and not secondary
[17:03] <cristian_c> arraybolt3, ok, featherpad shows the updated keyboard layout, no need to log out
[17:04] <arraybolt3> nice
[17:04] <cristian_c> arraybolt3, something else commonly to fix or can I apply upgrades in update notifier?
[17:04] <arraybolt3> if you changed the locale to get a different user interface language, that will need a logout and login, but if you don't want that, then you should be good to go.
[17:04] <arraybolt3> You should be able to apply upgrades.
[17:04] <arraybolt3> oh, though you said you had no Internet connection?
[17:05] <arraybolt3> You should be able to just click on the network icon in the system tray and select which network to connect to.
[17:05] <cristian_c> yeah, I've to set up a new connection again
[17:06] <cristian_c> arraybolt3, I'm feared I've to setup things as bluetooth, gvfs but pretty much audio mixer
[17:06] <cristian_c> am I wrong?
[17:06] <arraybolt3> That should all "just work" in Lubuntu.
[17:06] <cristian_c> ah, ok
[17:06] <arraybolt3> Alpine and distros like that require more setup than Lubuntu generally needs.
[17:06] <arraybolt3> The only reason Lubuntu needed this much setup was because Calamares didn't work.
[17:07] <cristian_c> *udisks
[17:08] <arraybolt3> You can connect Bluetooth devices by going to application menu -> Internet -> the bluetooth stuff is in here. udisks just works out of the box, no additional config. Audio also should just work, and there's an audio mixer icon in the system tray.
[17:08] <cristian_c> ok, usb flash drive has appeared in pcmanfm wiithout installing exfat or vfat packages
[17:09] <cristian_c> ok, I've given a look at pavucontrol
[17:11] <cristian_c> ok, connection estavblished, I can start upgrade now
[17:11] <arraybolt3> nice!
[17:12] <cristian_c> in the meantime, I check if bt adapter is detected
[17:12] <cristian_c> ok, it detets nearby devices
[17:13] <cristian_c> there isn't a bt icon in the tray but it's not an issue
[17:14] <cristian_c> arraybolt3, upgrade finished
[17:14] <arraybolt3> nice
[17:14] <cristian_c> bt device connected (I've not tested but it's a promising result, though)
[17:15] <arraybolt3> No released version of Lubuntu has a bluetooth icon in the tray unfortunately. Lubuntu 24.04 (which we're still developing) will have one.
[17:15] <cristian_c> arraybolt3, upgrade finished, I guess I can reboot instead of log out
[17:15] <arraybolt3> yep
[17:16] <cristian_c> rebooted
[17:17] <cristian_c> lubuntu-drive clean ...
[17:17] <cristian_c> systemd shows an eror in dmi field
[17:17] <cristian_c> btw, greeter appears
[17:18] <arraybolt3> usually errors like that are harmless if everything still works
[17:18] <cristian_c> arraybolt3, ok, there is always just 'us' layout in greeter screen, no other coice is shown in drop-down menu, so it's a bug shared between oses
[17:18] <cristian_c> *choice
[17:18] <arraybolt3> sadly that seems to be so
[17:19] <arraybolt3> I'll find out if that's a known bug in Lubuntu and maybe we can get it fixed for us and other distros
[17:19] <cristian_c> but clock is correct in grreter screen, it reflects the right timezone
[17:19] <cristian_c> probably it's a sddm bug, I suppose
[17:20] <arraybolt3> and we'll definitely look into the Calamares issue, it should have let your GPT drive show and it's confusing that it didn't.
[17:21] <cristian_c> arraybolt3, ok, I've not tested the system extensively but apparently it seems well working
[17:21] <cristian_c> arraybolt3, you've done a great work
[17:21] <arraybolt3> Thanks :) And thanks for your patience with the installer bug
[17:22] <cristian_c> arraybolt3, you've had to waste time with me, btw
[17:23] <cristian_c> arraybolt3, I've noticed a problem now
[17:23] <cristian_c> choosing internet -> Bluetooth file transfer does nothing
[17:23] <cristian_c> no windows appare
[17:23] <cristian_c> *appear
[17:24] <arraybolt3> oof, that seems bad
[17:24]  * arraybolt3 looks at something
[17:24] <cristian_c> also, I can't check bluetooth connected devices, so i can't manage for example bt audio devices
[17:24] <cristian_c> I've not a gui to do that, I mean
[17:24] <cristian_c> in case, I'd like to add a bt audio device
[17:25] <cristian_c> i don't know if I've to uninstall bluedevil and install blueman
[17:25] <cristian_c> with its burden of gtk stuff
[17:25] <arraybolt3> That would probably be a good idea.
[17:25] <arraybolt3> Blueman is actually what we switched to in Lubuntu 24.04 since Bluedevil is limiting.
[17:26] <cristian_c> good move!
[17:26] <arraybolt3> You should be able to just "sudo apt remove bluedevil; sudo apt install blueman"
[17:26] <cristian_c> arraybolt3, btw, it would be good if there would be a blueman-qt wrapper
[17:26] <cristian_c> *there was
[17:26] <cristian_c> ok
[17:26] <arraybolt3> Definitely agreed. We were going to try to make one ourselves for 24.04 and *might* still manage to do that.
[17:26] <arraybolt3> Our team is small so it's hard to do everything though.
[17:26] <cristian_c> since there is pavucontrol-qt
[17:26] <cristian_c> and pcmanfm-qt
[17:27] <arraybolt3> So right now it has Blueman with GTK and then we added a theme to make it look more uniform with other Qt apps.
[17:27] <cristian_c> yeah, you're right, it depends on blueman team to separate backend and gui
[17:28] <cristian_c> maybe, just a blueman-applet-qt is enough
[17:28] <arraybolt3> If you want the same theme, you can install breeze-gtk-theme and then in the Appearance options, set the GTK3 and GTK2 themes to Breeze
[17:28] <arraybolt3> that will make Blueman look more like a Qt app
[17:28] <arraybolt3> (the GTK theme options in the Appearance settingss are hiding - there's a sidebar on the left that you scroll down - when you scroll down, then you see the GTK theme section)
[17:28] <cristian_c> i think the current theme is better than in lubuntu 20.xx and lubuntu 22.xx
[17:29] <cristian_c> I guess there has been much progress for the theme since then
[17:29] <cristian_c> becuase I was good with lxde desktop
[17:30] <cristian_c> *because
[17:30] <cristian_c> when lubuntu switched to lxqt I had some trouble for the next release
[17:30] <cristian_c> sorry for the rant (END of the rant)
[17:31] <arraybolt3> LXQt was... rough... to begin with. It's gotten a lot better.
 You should be able to just "sudo apt remove bluedevil; sudo apt install blueman"
[17:34] <cristian_c> I guess remove without purge is enough
[17:34] <arraybolt3> you can purge if you'd like, but I don't expect there to be config files that need purging
[17:34] <arraybolt3> but yeah, using purge instead is fine
[17:36] <cristian_c> bluedevil* and lubuntu-desktop*
[17:36] <cristian_c> since it's meta-package it should not hurt
[17:36] <cristian_c> am I wrong?
[17:37] <cristian_c> (I've used --purge argument for remove command)
[17:38] <arraybolt3> Removing lubuntu-desktop could make upgrades go awry
[17:38] <arraybolt3> I forgot it would do that
[17:38] <arraybolt3> sigh, I think you can have both installed side-by-side without issues
[17:38] <cristian_c> I can still install lubuntu-desktop now
[17:38] <arraybolt3> yeah, probably do that
[17:39] <arraybolt3> That's another thing we fixed in 24.04 (most packages are recommends of lubuntu-desktop rather than depends, making it so that removing things won't take out lubuntu-desktop too, I believe)
[17:39] <cristian_c> ah, yep, it reinstall bluedevil too, but it's not an issue
[17:40] <cristian_c> I noticed that when upgrading from lxde to lxqt
[17:40] <cristian_c> many double apps
[17:40] <cristian_c> so, I'm used to :D
[17:42] <cristian_c> arraybolt3, I don't think I need to qt-ify blueman gui, it's not bad this way
[17:42] <cristian_c> it could be a matter of gtk dependencies, not just appearance issue
[17:44] <cristian_c> it's showing bt device already connected in blueman, so i've not to make it again
[17:44] <cristian_c> arraybolt3, thanks for the time you wasted with me today, I hope at least I've exchanged your help with a further feedback from user
[17:45] <arraybolt3> Glad to help, and thank you for coming so we'd be aware of the bug in Calamares!
[17:45] <arraybolt3> I'll try and test it more and see if we can get it fixed.
[17:50] <cristian_c> (one more thing: I've just configured blueman to receive files from other bt devices. Now, it finally works but lxqt notifications are not a big deal)
[17:51] <cristian_c> arraybolt3, I mean, when you click on a button in a lxqt notification you can't know if this action is triggered
[17:51] <cristian_c> the notification doesn't disappear, etc...
[17:52] <cristian_c> a different experience compared to something as xfce, for example...
[17:52] <cristian_c> I mean about notifications (I have not the right to says so but I think it's an area to improve)
[17:52] <cristian_c> *to say
[17:54] <arraybolt3> Ah, good point.
[17:54] <arraybolt3> LXQt notifications don't do anything when you click them unless you click the Close button in the upper-right corner.
[17:54] <arraybolt3> (which just dismisses the notification, it doesn't trigger additional actions)
[17:54] <arraybolt3> That's an LXQt limitation, it might be fixable at some point.
[17:55] <arraybolt3> (depending on whether LXQt is interested)
[17:55] <cristian_c> the problem is bigger when there are buttons embedded in the notifications (as for example bluetooth transfers, or pairing)
[17:55] <cristian_c> accept/pair, I mean
[17:55] <cristian_c> or other applications I'm not aware of
[17:56] <cristian_c> (I guess when I press a button in a notification, a user expects that to disappear, commonly)
[17:57] <cristian_c> but you're right , it's not ubuntu fault, it's just due to DE's decision
[18:00] <cristian_c> https://postimg.cc/JsznKLyM
[18:00] <cristian_c> (transferred by bluetooth)
[18:01] <cristian_c> arraybolt3, thanks again (this time, I've really stopped to write :D)
[18:01] <arraybolt3> Really glad to be able to help! Thanks for all the feedback, it really helps us know what to work on.