/srv/irclogs.ubuntu.com/2021/09/15/#ubuntustudio-devel.txt

tewardCala does not do this00:00
tewardso it's impossible to debug00:00
teward*does a thing and manually executes calamares on the CLI with --debug*00:01
tewardexecuting installation with full debug00:06
tewardif it errors I'll have the full debug logs from Cala00:06
teward(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
tewardEickmeyer: RikMills: don't consider the resolution change as a problem, it's just an oddity00:06
tewardit's the least important thing, and might be impacted 'cause i'm running via qemu-kvm00:06
EickmeyerQemu is weird like thst sometimes.00:07
tewardso 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 repro00:07
tewardfound the error00:10
teward"Unable to locate package: zram-config00:10
tewardso this is pulled in as a result of apt attempting to remove zram-config but it doesn't exist at all in the apt data00:11
tewardEickmeyer: so, zram-config is NOT present on the image00:12
tewardand not pulled in anywhere so if the system doesn't do an `apt update` it doesn't know zram-config is even a package00:12
tewardit'd otherwise give a non-critical warning instead of a crash00:12
tewardso fully-offline install is not possible in the current iteration of the ISO00:12
tewardEickmeyer: RikMills: OvenWerks:  ^^ there's your installation crash00:13
tewardEickmeyer: 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 data00:14
tewardi'd do a pastebinit of the logs but it's large :P00:14
tewardfull logs: https://paste.ubuntu.com/p/KXG9JDCkrv/00:16
Eickmeyerteward: 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
tewardEickmeyer: that's why i dumped the logs00:16
tewardso you can see everything it idd00:16
tewarddid*00:16
tewardit'll also show you the command it's running (line 849, error on 856 from apt)00:17
tewardunrelated: I love how qemu-kvm has clipboard integration in *buntu images so I can copy paste links in/out of the VM xD00:17
EickmeyerOh, I do that with virtualbox all the time. Granted, it has to have a client-side module, but whatev.00:20
tewardEickmeyer: 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 seems00:20
teward855 is a noncritical info but 856 with zram-config is why it's breaking in my qemu00:21
tewardthere 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 85500:24
tewardbut 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:24
tewardthat's beyond my ability to debug 'cause DNS works - i confirmed it :P00:25
tewardso maybe chroot specific problems.00:25
Eickmeyerteward: 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
EickmeyerIn calamares-settings-ubuntu00:25
tewardcheck.  the reason it's failing to be found is the DNS resolution issues i mentioned (see line 822+)00:26
tewardlines 822 through 841)00:26
teward'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 erroring00:26
EickmeyerThat might be the reason for the hard failure, but we don't see zram-config, so no reason to remove it.00:26
tewards/841/847/00:26
tewardEickmeyer: it's probably there for a reason00:27
tewardbut probably still something to figure out.  temporary workaround, remove it from the tasks.  long term: figure out why it failed to resolve00:27
Eickmeyerteward: Probably because I copied it from the Lubuntu config of the same name.00:27
tewardhah00:27
tewardah, but the Lubuntu installer currently in Impish doesn't have the same DNS resolution in chroot problem that I can tell00:27
tewardactually i should test that00:28
teward*zsyncs the Lubuntu installer*00:28
EickmeyerWell, 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:31
tewardi touched base with Dan on the Lubuntu side, and they said you're handling settings00:36
tewardi'mma do a reinstall of Studio but with a different test00:36
teward`sudo -E` because i might've forgot something00:36
EickmeyerYeah, I'm handling settings for the Studio stuff only.00:37
EickmeyerI'm only supposed to have permission to handle it for these types of cases.00:38
tewardum00:40
tewardEickmeyer: that won't affect the Lubuntu settings right?00:40
teward'cause... they use zram :P00:40
EickmeyerNot at all. Separate subdirectories.00:40
tewardcheck00:40
tewardEickmeyer: so, i did more pokings00:54
tewardLubuntu *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 issue00:55
tewardthe failure in dns reso means apt update didn't work, and because zram-config isn't part of the image that's why it hardfailed00:55
tewardso just removing it from the cala settings for Studio *should* solve the hard fail00:55
teward(the dns reso problem inside the chroot during the processes done by Cala seems persistent on all so)00:55
EickmeyerYeah, that seems like a cala bug for sure, or at least something weird in the chroot.00:56
tewardindeed on both counts00:59
tewardalso00:59
tewardthe version strings're wrong in Cala (saying 21.04)00:59
tewardDan's fixing on the Lubuntu side but your job on the Studio side.00:59
tewardbut the dns reso problem is why yours hardfailed unexpectedly00:59
tewardso that must be a recent problem00:59
teward(just update your settings :P00:59
EickmeyerWell, it should be fixed on both sides since I just uploaded a 21.10.1 version to proposed.00:59
EickmeyerThe subdirectories divide the binary subpackages, not the source, so the version will propogate to both lubuntu and ubuntustudio.01:00
Eickmeyerteward ^01:00
tewardcheck01:01
tewardso, test the next ISO and the hard fails should go away.01:01
tewardonce it gets out of -proposed01:01
EickmeyerYep.01:02
tewardEickmeyer: as long as the settings that Lubuntu gets still include the zram-config remove then that's good.01:05
tewardi'm still catching up on the cala stuff xD01:05
EickmeyerYeah, 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
teward(I usually avoid installer bugs like the plague except during testing, but I never actually deep dive heh)01:06
tewardyepo01:06
tewardffs i can't type01:06
Eickmeyerhaha01:06
tewardEickmeyer: 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 :p01:32
teward*goes to sleep mode*01:32
teward(but on the Lubuntu instaler of course)01:33
EickmeyerYep, I know Chris. Good guy.01:36
RikMillsteward: https://bugs.kde.org/show_bug.cgi?id=40705809:25
ubottuKDE bug 407058 in KScreen "KDE Plasma5 can't change resolution in VM after last update" [Normal, Resolved: Fixed]09:25
RikMillsBIG patch to fix it in master, which I don't feel confident backporting09:27
RikMillsOvenWerks Eickmeyer FYI, konsole width thing is the same in Neon09:53
tewardRikMills: thanks for the FYI13:54
OvenWerksRikMills: 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:13
RikMillsno other apps have added such a silly toolbar ;)15:17
OvenWerksremoving the toolbars works15:38
OvenWerksbut... the menu item starts konsole with the last used profile instead of the default one :P15:41
OvenWerksThe quick launch widget is frustrating16:17
RikMillsyou could use the konsole profile widget16:31
RikMillsI don't think I have ever used multiple profiles with konsole16:35
OvenWerksRikMills: 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
OvenWerksdesktop file on my own then select that instead16:52
OvenWerksThe konsole profile widget does work. but it is two click instead of one16:52
RikMillsnice thing about linux is you can hack things like that, if the default is not to your liking :)16:54
OvenWerksThe advantage of a separate wiget is also being able to use a different icon.16:54
OvenWerksmy daily setup is still the last LTS so it has been a while since I went through this.16:55
EickmeyerOvenWerks: We have a different default profile (called Profile 1) in order to use the Materia color scheme, otherwise it looks a little funny.17:11
OvenWerksEickmeyer: default 1 is ok17:12
OvenWerksI think I make my own default of 80X25 instead of 110X2517:13
EickmeyerThe 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
EickmeyerRikMills: ^17:18
OvenWerksthe really wide size is to fit the toolbar17:18
RikMills^that17:18
OvenWerksif you select different sets of toolbars the size changes17:19
OvenWerksthere are two: main and session17:19
OvenWerksbut main is the wide one17:19
EickmeyerOk, I'll disable the toolbar per the file RikMills showed us.17:19
EickmeyerJust need to upload the fix to default-settings and we'll be good.17:20
OvenWerksEickmeyer: it seems the problem with controls 2.2.1 has gone? see #ubuntustudio comment.17:23
EickmeyerOvenWerks: Probably due to a build-time change I made to Jack with falktx's help (disabled LTO).17:24
EickmeyerOvenWerks: Still doesn't fix the pulseaudio failing to yeild issue.17:25
Eickmeyer(hence the earlier merge we did)17:25
OvenWerksI 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 controls17:25
OvenWerksI am not having trouble with pulse that I can see17:25
OvenWerks(using 2.2.1 in iso)17:26
EickmeyerWell, 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:26
OvenWerksok, I have some debugging lines added to convert to upload and then we can tag 2.2.217:30
EickmeyerSweet.\17:31
OvenWerksEickmeyer: 2.2.* is going to become a branch I think. It will be the last pulse/jack version(s). 3.* will be pw/jack17:32
EickmeyerOvenWerks: Oh, cool!17:32
EickmeyerDoes that mean we should look at switching to PW for the LTS?17:33
OvenWerksany comments on setting ffado modules to be the default install?17:34
OvenWerksThis allows people to try the ffado modules from the iso with no install and also the alsa modules are quite limiting17:35
EickmeyerAs long as it doesn't mess with USB or otherwise.17:35
OvenWerksIt should have no effect on USB or internal devices (it doesn't here for sure)17:36
EickmeyerCan we confirm that ffado works with all firewire devices?17:36
OvenWerksmore devices than alsa17:36
OvenWerksalsa is based on the prior work done by ffado17:37
EickmeyerSweet. 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
EickmeyerI'm not comfortable with either approving a FFe or asking for one in this case.17:37
RikMillsfyi, 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
EickmeyerRikMills: Awesome. Maybe that will fix most of the issue?17:42
RikMillsas 21.08.2 won't be out before release17:43
EickmeyerRight, an SRU wouldn't be frowned-upon though.17:43
RikMillsEickmeyer: not the width issue sadly17:43
EickmeyerOhhhh Ok.17:43
EickmeyerMauroGaspari[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:26
OvenWerksRikMills Eickmeyer: for settings manager->devices->input->game controlers it would be nice to have a button: "this is a tablet"19:58
EickmeyerOvenWerks: Not a bad suggestion. Probably a decent suggestion for the Plasma team.19:59
OvenWerksWe have two tablets that show up as game controlers until I modify /usr/share/X11/xorg.conf.d/70-wacom.conf20:01
EickmeyerThat sounds like a bug more than a feature request.20:05
EickmeyerOf course, feature development for kwin-x11 has ceased in favor of Wayland.20:06
OvenWerkssounds way to close to waste land21:52

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!