[00:00] Cala does not do this [00:00] so it's impossible to debug [00:01] *does a thing and manually executes calamares on the CLI with --debug* [00:06] executing installation with full debug [00:06] if it errors I'll have the full debug logs from Cala [00:06] (the stuff Ubuntu's installer logs but also shows if you expand the details during the installer giving you full CLI logs and stuff) [00:06] Eickmeyer: RikMills: don't consider the resolution change as a problem, it's just an oddity [00:06] it's the least important thing, and might be impacted 'cause i'm running via qemu-kvm [00:07] Qemu is weird like thst sometimes. [00:07] so it's not a straight bare metal install. HOWEVER, the apt failure I did reproduce, so I'm running with full debug data to try and repro [00:10] found the error [00:10] "Unable to locate package: zram-config [00:11] so this is pulled in as a result of apt attempting to remove zram-config but it doesn't exist at all in the apt data [00:12] Eickmeyer: so, zram-config is NOT present on the image [00:12] and not pulled in anywhere so if the system doesn't do an `apt update` it doesn't know zram-config is even a package [00:12] it'd otherwise give a non-critical warning instead of a crash [00:12] so fully-offline install is not possible in the current iteration of the ISO [00:13] Eickmeyer: RikMills: OvenWerks: ^^ there's your installation crash [00:14] Eickmeyer: OvenWerks: `sudo calamares --debug 2>&1 > cala.log` in the CLI will execute Calamares and force debug output to a log file, that's how i found this data [00:14] i'd do a pastebinit of the logs but it's large :P [00:16] full logs: https://paste.ubuntu.com/p/KXG9JDCkrv/ [00:16] teward: I'll take a look at why on earth it's even attempting to uninstall zram-config. We've never had that installed and this is the first time this is showing up. [00:16] Eickmeyer: that's why i dumped the logs [00:16] so you can see everything it idd [00:16] did* [00:17] it'll also show you the command it's running (line 849, error on 856 from apt) [00:17] unrelated: I love how qemu-kvm has clipboard integration in *buntu images so I can copy paste links in/out of the VM xD [00:20] Oh, I do that with virtualbox all the time. Granted, it has to have a client-side module, but whatev. [00:20] Eickmeyer: it could be a leftover from some python config somewhere that's referring to zram-config. Because it is populated as part of one of the python tasks it seems [00:21] 855 is a noncritical info but 856 with zram-config is why it's breaking in my qemu [00:24] there also... seemed to be some "why is DNS failing here?" headscratching in the logs. My guess is that zram-config SHOULD be picked up as 'not installed' and be like line 855 [00:24] but becasue of the prior dns resolution failures, I would surmise that it's failing exceptionally hard because it didn't get package info from apt sources that would indicate zram-config is a valid package but just isn't installed. [00:25] that's beyond my ability to debug 'cause DNS works - i confirmed it :P [00:25] so maybe chroot specific problems. [00:25] teward: It's actually explicitly stated in ubuntustudio/modules/packages.config to remove at the end of the installation, for reasons I'll never know. Either way, I'm a changelog/commit away from having it fixed. [00:25] In calamares-settings-ubuntu [00:26] check. the reason it's failing to be found is the DNS resolution issues i mentioned (see line 822+) [00:26] lines 822 through 841) [00:26] 'Temporary failure resolving' is a problem, because if it can't get apt data (and yes this VM has DHCP and valid DNS) then that's why it's hard erroring [00:26] That might be the reason for the hard failure, but we don't see zram-config, so no reason to remove it. [00:26] s/841/847/ [00:27] Eickmeyer: it's probably there for a reason [00:27] but probably still something to figure out. temporary workaround, remove it from the tasks. long term: figure out why it failed to resolve [00:27] teward: Probably because I copied it from the Lubuntu config of the same name. [00:27] hah [00:27] ah, but the Lubuntu installer currently in Impish doesn't have the same DNS resolution in chroot problem that I can tell [00:28] actually i should test that [00:28] *zsyncs the Lubuntu installer* [00:31] Well, I just pushed the short-term fix, hopefully that will do the trick for the most part, but yes, if DNS reso is weird, that might have to do with something deeper. [00:36] i touched base with Dan on the Lubuntu side, and they said you're handling settings [00:36] i'mma do a reinstall of Studio but with a different test [00:36] `sudo -E` because i might've forgot something [00:37] Yeah, I'm handling settings for the Studio stuff only. [00:38] I'm only supposed to have permission to handle it for these types of cases. [00:40] um [00:40] Eickmeyer: that won't affect the Lubuntu settings right? [00:40] 'cause... they use zram :P [00:40] Not at all. Separate subdirectories. [00:40] check [00:54] Eickmeyer: so, i did more pokings [00:55] Lubuntu *does* have the same DNS resolution in chroot problem that we were seeing in the Studio ISOs. but because Lubuntu includes zram-config in the image (yes they use zram and it needs removed for install), it doesn't error. But it does see the same dns reso issue [00:55] the failure in dns reso means apt update didn't work, and because zram-config isn't part of the image that's why it hardfailed [00:55] so just removing it from the cala settings for Studio *should* solve the hard fail [00:55] (the dns reso problem inside the chroot during the processes done by Cala seems persistent on all so) [00:56] Yeah, that seems like a cala bug for sure, or at least something weird in the chroot. [00:59] indeed on both counts [00:59] also [00:59] the version strings're wrong in Cala (saying 21.04) [00:59] Dan's fixing on the Lubuntu side but your job on the Studio side. [00:59] but the dns reso problem is why yours hardfailed unexpectedly [00:59] so that must be a recent problem [00:59] (just update your settings :P [00:59] Well, it should be fixed on both sides since I just uploaded a 21.10.1 version to proposed. [01:00] The subdirectories divide the binary subpackages, not the source, so the version will propogate to both lubuntu and ubuntustudio. [01:00] teward ^ [01:01] check [01:01] so, test the next ISO and the hard fails should go away. [01:01] once it gets out of -proposed [01:02] Yep. [01:05] Eickmeyer: as long as the settings that Lubuntu gets still include the zram-config remove then that's good. [01:05] i'm still catching up on the cala stuff xD [01:06] Yeah, the binary package for lubuntu won't be affected. Think of it as akin to a no-change rebuild on that side of the source. [01:06] (I usually avoid installer bugs like the plague except during testing, but I never actually deep dive heh) [01:06] yepo [01:06] ffs i can't type [01:06] haha [01:32] Eickmeyer: i've enlisted an Lubuntu guy to see if they can repro the dns resolution notes we had during the chroot install, and then that's a task for next cycle if it is present. Unless it causes chaos like it did today :p [01:32] *goes to sleep mode* [01:33] (but on the Lubuntu instaler of course) [01:36] Yep, I know Chris. Good guy. [09:25] teward: https://bugs.kde.org/show_bug.cgi?id=407058 [09:25] KDE bug 407058 in KScreen "KDE Plasma5 can't change resolution in VM after last update" [Normal, Resolved: Fixed] [09:27] BIG patch to fix it in master, which I don't feel confident backporting [09:53] OvenWerks Eickmeyer FYI, konsole width thing is the same in Neon [13:54] RikMills: thanks for the FYI [15:13] RikMills: it did seem to be just konsole that had the trouble. all the other windows work fine. [15:13] * OvenWerks also notes the path to the profile files in the documentation does not agree with reality. [15:17] no other apps have added such a silly toolbar ;) [15:38] removing the toolbars works [15:41] but... the menu item starts konsole with the last used profile instead of the default one :P [16:17] The quick launch widget is frustrating [16:31] you could use the konsole profile widget [16:35] I don't think I have ever used multiple profiles with konsole [16:52] RikMills: when the quick launch widget is used, and the item is edited, that effects the menu item. then I make a second quick launch and make it another konsole with a different command line... but because the quick launch basically copies the desktop file from system to ~/.local/share/applications/ and changes it... it has the same name etc. So I found that I need to create a separate [16:52] desktop file on my own then select that instead [16:52] The konsole profile widget does work. but it is two click instead of one [16:54] nice thing about linux is you can hack things like that, if the default is not to your liking :) [16:54] The advantage of a separate wiget is also being able to use a different icon. [16:55] my daily setup is still the last LTS so it has been a while since I went through this. [17:11] OvenWerks: We have a different default profile (called Profile 1) in order to use the Materia color scheme, otherwise it looks a little funny. [17:12] Eickmeyer: default 1 is ok [17:13] I think I make my own default of 80X25 instead of 110X25 [17:18] The default profile has no size information (nor does konsolerc), so I don't know why it's going to that really wide size. [17:18] RikMills: ^ [17:18] the really wide size is to fit the toolbar [17:18] ^that [17:19] if you select different sets of toolbars the size changes [17:19] there are two: main and session [17:19] but main is the wide one [17:19] Ok, I'll disable the toolbar per the file RikMills showed us. [17:20] Just need to upload the fix to default-settings and we'll be good. [17:23] Eickmeyer: it seems the problem with controls 2.2.1 has gone? see #ubuntustudio comment. [17:24] OvenWerks: Probably due to a build-time change I made to Jack with falktx's help (disabled LTO). [17:25] OvenWerks: Still doesn't fix the pulseaudio failing to yeild issue. [17:25] (hence the earlier merge we did) [17:25] I think a reboot would fix it. I think for 2.3 (3.0?) I will rework the convert script and move some of that to both autojack and controls [17:25] I am not having trouble with pulse that I can see [17:26] (using 2.2.1 in iso) [17:26] Well, I am. Every time I try to start Jack, pulse doesn't restart and hogs the devices, causing autojack to default to internal audio (xrun city). Only solution was to 'systemctl --user restart pulseaudio' upon login. [17:30] ok, I have some debugging lines added to convert to upload and then we can tag 2.2.2 [17:31] Sweet.\ [17:32] Eickmeyer: 2.2.* is going to become a branch I think. It will be the last pulse/jack version(s). 3.* will be pw/jack [17:32] OvenWerks: Oh, cool! [17:33] Does that mean we should look at switching to PW for the LTS? [17:34] any comments on setting ffado modules to be the default install? [17:35] This allows people to try the ffado modules from the iso with no install and also the alsa modules are quite limiting [17:35] As long as it doesn't mess with USB or otherwise. [17:36] It should have no effect on USB or internal devices (it doesn't here for sure) [17:36] Can we confirm that ffado works with all firewire devices? [17:36] more devices than alsa [17:37] alsa is based on the prior work done by ffado [17:37] Sweet. Then I say why not, but it's beyond FF so we'll have to wait for the next dev cycle to kick that in. [17:37] I'm not comfortable with either approving a FFe or asking for one in this case. [17:42] fyi, there will be a new konsole upload coming. I am cherry picking the bugfixes from https://invent.kde.org/utilities/konsole/-/commits/release/21.08/ [17:42] RikMills: Awesome. Maybe that will fix most of the issue? [17:43] as 21.08.2 won't be out before release [17:43] Right, an SRU wouldn't be frowned-upon though. [17:43] Eickmeyer: not the width issue sadly [17:43] Ohhhh Ok. [19:26] MauroGaspari[m]: To answer your question (sorry for the late reply) I don't quite have anything to talk about yet, but Studio Controls has quite a few enhancements, including the ability to do jack via network. [19:58] RikMills Eickmeyer: for settings manager->devices->input->game controlers it would be nice to have a button: "this is a tablet" [19:59] OvenWerks: Not a bad suggestion. Probably a decent suggestion for the Plasma team. [20:01] We have two tablets that show up as game controlers until I modify /usr/share/X11/xorg.conf.d/70-wacom.conf [20:05] That sounds like a bug more than a feature request. [20:06] Of course, feature development for kwin-x11 has ceased in favor of Wayland. [21:52] sounds way to close to waste land