[00:00] <Booda> o/
[00:00] <yukiup> \o
[00:12] <mago> Hello, will altVR work in ubuntu?
[00:13] <mago> Hello. Will altspaceVR work in ubuntu?
[00:13] <yukiup> can you get it from the repo?
[00:14] <mago> Well I saw they have a github.. Will it work if I clone from there?
[00:16] <oerheks> mago, url?
[00:16] <yukiup> https://docs.microsoft.com/en-us/windows/mixed-reality/altspace-vr/getting-started/system-requirements
[00:16] <oerheks> if it is not in our repos, we officially do no support it.
[00:16] <yukiup> looks like a no
[00:16] <mago> It seems its all for windows, thats what i thought..
[00:16] <mago> oerheks they have this github: https://github.com/orgs/AltspaceVR/repositories
[00:16] <sarnold> you could try it with wine but I wouldn't spend any money on trying it..
[00:19] <Mago84> Someone stole my nick? But i have it registered..
[00:20] <oerheks> how is that an ubuntu support issue?
[00:20] <oerheks> you seem like logged in
[00:20] <Mago84> Well that was not ubuntu related, ill give you that..
[00:22] <Guest94> sarnold It's been on pause.  I started getting frustrated and hungry, so I ate.  Now I'm back.
[00:22] <sarnold> Guest94: woo, I think I did much the same :) lunch and then a few meetings..
[00:23] <Guest94> I've wasted the entire day on this.
[00:24] <Guest94> somebody wanted me to modify grub.cfg and start from there instead of what you suggested.  That's more or less when I took a break.
[00:25] <Guest94> sarnold  I'm not even really sure what he wanted me to do or how it would help.
[00:25] <mago> Going back to AltspaceVR will the mac version work easier in Ubuntu than the windows one?
[00:25] <sarnold> they may have had a good reason for their suggestion; my suggestion was based on the strong hope that you were 100% right by nailing it down to the kernel packages
[00:25] <Guest94> Did you see the packages I posted?
[00:25] <oerheks> downgrading 5.11 on 20.04 ,..
[00:26] <Guest94> yes, that's what I need to do.  Downgrade back to 5.8
[00:26] <oerheks> i'd say reinstall
[00:26] <Guest94> And then after that, I have no idea how I'm supposed to get updates.
[00:26] <Guest94> oerheks ugh.  Why?
[00:28] <oerheks> did you use the testing kernels ? or linux-hwe-5.11 from the ppa kernel team
[00:28] <Guest94> I used whatever came down.  But I can be more specific....  https://paste.ubuntu.com/p/z9CwgRjpVW/
[00:33] <sarnold> yay for specifics :) that's indeed the HWE kernel stack, it matches what's in my apt lists from yesterday
[00:33] <sarnold> (my archive mirror is off at the moment, so I'm a day out of date)
[00:36] <Guest94> log from /var/log/dpkg.log https://paste.ubuntu.com/p/cndsnPTXRR/
[00:37] <Guest94> so... do I proceed with the sarnold plan?
[00:39] <sarnold> Guest94: well, hard to say. I can see some real benefit to the idea of modifying the grub configuration so that you ought to be able to more easily select fallback kernels, etc
[00:39] <Guest94> OK
[00:39] <Guest94> What do I modify?
[00:39] <sarnold> Guest94: I'd suggest doing that by editing /etc/default/grub instead of the grub.cfg file
[00:40] <Guest94> ok
[00:41] <sarnold> Guest94: I'm not 100% sure what to put in there, this is what I've got in mine: https://paste.ubuntu.com/p/WY87qg8YzB/ and I think the GRUB_TIMEOUT=5 is most immediately useful, but perhaps some of the others are important in your case
[00:41] <Guest94> This is the file I was looking for!  I couldn't find it before, didn't know where it was or what it was called but... this is more or less the contents I couldn't seem to find.  Thanks!
[00:42] <Guest94> It's the quiet splash for one thing...
[00:44] <Guest94> and this  GRUB_TIMEOUT_STYLE=hidden
[00:44] <Guest94> I think
[00:46] <sarnold> I wish I had kept better notes of which changes I introduced vs what was already there :)
[00:46] <Bashing-om> Guest94: My grub file " GRUB_TIMEOUT_STYLE=menu " As I do multi-boot and I want to always see the menu.
[00:46] <Guest94> Bashing-om Thank you!  I was just searching through the info doc and not finding it.
[00:46] <Bashing-om> sarnold: I do have my original grub file - want it ?
[00:47] <sarnold> Bashing-om: oh that'd be handy yeah, thanks :)
[00:49] <Bashing-om> sarnold: Guest94: My original grub file: https://termbin.com/w69i .
[00:50] <Guest94> ok, running update-grub unless someone has an objection?
[00:50] <sarnold> Bashing-om: man I mangled mine. heh. thanks
[00:52] <Bashing-om> sarnold: Should see how I have mangled up mine - I make it a practice to alwsys make a back-up of any system file I edit :D
[00:52] <Guest94> Seeing no objections... I am now running update-grub
[00:54] <Guest94> I wish someone had objected...  I'm not in the chroot environment.
[00:54] <Guest94> Luckily, I didn't run it.
[00:54] <Guest94> Phew
[00:54] <Guest94> So.... is this going to work w/out running update-grub?
[00:55] <Bashing-om> Guest94: My excuse - I have not kept a close eye on what you are doing :P
[00:55] <Guest94> No... I guess I need to chroot
[00:55] <Guest94> Bashing-om Nobody is.  Good thing I don't have any matches.
[00:55] <sarnold> Guest94: nice catch :)
[00:56] <Guest94> so we agree on chroot then?
[00:56] <sarnold> yes
[01:06] <Guest94> ok
[01:07] <sarnold> were you able to get to a menu of previous kernels with this change?
[01:07] <sarnold> or did it all go even more sideways?
[01:07] <Guest94> not ready yet
[01:07] <sarnold> aha
[01:08] <Guest94> busy losing my mind
[01:18] <Guest94> argh
[01:19] <Guest94> sarnold https://paste.ubuntu.com/p/HFG6XZgh6v/
[01:19] <sarnold> Guest94: hmm, did mounting your root filesystem on to /mnt fail?
[01:20] <Guest94> I was wondering how it was supposed to be mounted!  Let me add that in.
[01:21] <Guest94> sarnold OK, that worked... as far as all the errors are concerned.
[01:23] <sarnold> Guest94: good good
[01:24] <Guest94> OK, I have entered the environment
[01:24] <Guest94> expected device mounted on root.  So far so good.
[01:25] <Guest94> so.... grub-update here?
[01:25] <sarnold> just to double-check, did you edit the /etc/default/grub that's in this chroot environment?
[01:26] <Guest94> sarnold Yes.  Thank you for making it easy.  Bouncing back and forth between files let alone environments is confusing.
[01:27] <Guest94> So... grub-update.
[01:27] <sarnold> update-grub
[01:27] <Guest94> which of course isn't in the environment :/
[01:28] <sarnold> on my focal system, it's in /usr/sbin/update-grub
[01:28] <Guest94> uh oh... grub or grub2?
[01:29] <sarnold> on my system, update-grub2 is a symlink to update-grub
[01:29] <Guest94> let me verify
[01:30] <Guest94> yes, same here
[01:30] <Guest94> here goes.
[01:33] <Guest94> sarnold https://paste.ubuntu.com/p/jSkJSyJ6xr/
[01:34] <Guest94> sdd1 appears to be my CDROM so, that's fine I guess.
[01:35] <Guest94> maybe run it again after I reboot?
[01:35] <sarnold> Guest94: woo, looks promising
[01:36] <sarnold> Guest94: I'm a bit surprised by the 16.04 messages, but maybe that makes sense. heh.
[01:36] <sarnold> Guest94: you probably don't need to re-run it after the reboot
[01:36] <Guest94> I have multiple disks, I've not yet cleaned out the older ones.
[01:36] <sarnold> cool
[01:36] <sarnold> then it makes sense :D
[01:36] <Guest94> well I presume I want to get my cdrom in there too?
[01:37] <Guest94> Nah, I guess that doesn't matter.
[01:37] <Guest94> I don't boot off that drive.
[01:37] <sarnold> nah, that probably won't happen much :)
[01:37] <sarnold> and you can always fiddle with uefi boot order in case you're actually booting to a cd
[01:37] <Guest94> besides... it will fix itself next kernel update
[01:37] <Guest94> ok, so... reboot now?
[01:37] <sarnold> I think so, yeah
[01:38] <Guest94> OK, see you on the other side.  Back soon I hope.
[01:53] <alzgh> On a machine with 1 cpu and 4 real cores (with hyper threading enabled 8 cores), when I look at the cpu load averages, should I measure it against the 4 real cores or the 8 hyper threaded cores?
[01:54] <matsaman> neither
[01:55] <sarnold> alzgh: well, it's not exactly related... load average shows you how many processes are runnable or waiting for .. long IO? disk IO? something similar .. and doesn't really matter about how many CPUs are online to run those processes
[01:57] <Guest94> sarnold Still won't boot.  still doesn't show menu.  Just a blank screen after I choose the boot device.  With that said, I'm exhausted and exasperated and I need a nap.  Appreciate you and everyone else helping.  BBL
[01:57] <sarnold> Guest94: dang :( twenty minutes, I was getting worried, heh
[01:57] <sarnold> Guest94: good luck
[01:57] <alzgh> sarnold I'm talking about load average from `top`s first line. Doesn't a "1" in the load average roughly corresponds to on cpu core load of work?
[01:58] <alzgh> I mean the 1 minute, 5 minute, and 15 minute from `top`'s first line.
[01:58] <sarnold> alzgh: it could also be one process stuck waiting on disk io, waking up, doing something with it, then doing another disk io
[02:00] <alzgh> this would even out when we look at the 15 minute average, no?
[02:00] <sarnold> it depends what the processes are doing and for how long they do it :)
[02:00] <alzgh> true
[02:00] <sarnold> it's just one way of viewing the system, and it's not really the most useful
[02:01] <sarnold> I think it was more useful on other unix systems but even then, it's a pretty minimal view of things
[02:02] <sarnold> for example, when I got a dual-xeon system, I did a bunch of kernel compiles to try to figure out what it could do, and running "make -j 300" in the kernel sources gave me the *best* performance; it brought the load average around 300 for almost three minutes, but it was the fastest; I only had 16 cores, 32 threads.
[02:05] <alzgh> That makes sense sarnold. What other more reliable ways are there to monitor a system for resources?
[02:07] <sarnold> vmstat 1 is very handy -- it shows runnable and blocked processes, a rough guideline of how memory and swap is being used, how much disk traffic there is, and percentages of cpu utilization
[02:07] <sarnold> oh yeah, I prefer vmstat -w 1  .. I'm not quite accustomed to it yet :)
[02:08] <sarnold> I've heard good things about the netdata package, some screenshots on https://github.com/netdata/netdata
[02:09] <sarnold> and this suite of tools (in the bpfcc-tools package) is fantastic for seeing different cross-sections of your computer https://github.com/iovisor/bcc#tools
[02:09] <sarnold> but there's dozens or hundreds of choices, all with various pros and cons
[02:10] <sarnold> I'm off for the night, have fun :)
[02:10] <alzgh> thanks, this gives me a good start
[02:10] <alzgh> good night
[02:11] <sarnold> o/ :)
[02:49] <koala_man> does ubuntu not let you set up encrypted LVM via the manual installer anymore? I tried on 21.04 and I can choose "physical volume for encryption" but there's nothing related to LVM before or after
[03:32] <hynix> Hello
[03:33] <hynix> Does any one know about RUBERHOUSE?
[03:33] <hynix> Is the file System from julian assange.
[03:40] <soloslinger> Does not compute.
[03:41] <p0indexter> i know of one package called "surf raw" originally maintained by assange
[06:18]  * ash_worksi hopes people are alive atm
[06:40] <polve> ash_worksi: just ask your question :-)
[06:41] <ash_worksi> polve: haha, sorry, yes, I was going to but got distracted by another channel :P
[06:42] <ash_worksi> it was recommended that I use `shopt -u progcomp` in order to ease tab-completion for tedious file prefixes (timestamps); seeing as how ymmv between linux distros I wanted to check with the pros if they thought that was a good idea?
[06:46] <ash_worksi> understand that I use ubuntu pretty close to just out-of-the-box; so when it comes to such a recommendation I get afraid that it might intefere with other ubuntu-specific niceties
[06:46] <geirha> I just purge bash-completion instead
[06:47] <alkisg> The system won't be affected in any case, it's just about your own personal preference...
[06:49] <ash_worksi> geirha: what do you mean by 'purge' ?
[06:51] <alkisg> ash_worksi: sudo apt purge bash-completion
[06:51] <alkisg> I.e. uninstall the bash completion package
[06:51] <ash_worksi> I see
[06:52] <ash_worksi> that shopt does kill docker autocomplete
[06:52] <geirha> you can probably override the completions for that single command
[06:53] <geirha> assuming bash-completion does not override it again
[06:53] <geirha> complete -o default -o bashdefault ymmv
[06:56] <ash_worksi> geirha: is that assuming i use the shopt ?
[06:56] <geirha> no, the shopt disables programmable completion completely, leaving you with default completions for all commands
[06:57] <ash_worksi> okay; so the idea is supposed to be `complete -o ... ls_or_something` ?
[06:57] <ash_worksi> oh no, I see
[06:57] <ash_worksi> I think
[07:02] <geirha> ah, I somehow read ymmv as the command with broken completions
[07:02] <geirha> so if it's for multiple commands, then maybe the shopt is a good idea. You can re-enable it with -s instead of -u
[07:10] <ash_worksi> geirha: yeah; well, it's only when I jump into a directory with timestamp prefixes
[07:11] <ash_worksi> I just hate that I can't every autocomplete more than like 3 characters before having to really peer at the ls of everything
[07:11] <ash_worksi> and a jumble of numbers is not exactly easy for me to read
[07:12] <geirha> what format are the timestamps in? seconds since epoch?
[07:18] <ash_worksi> geirha: genearlly $(date +'%Y%m%d_%H%M%S')_something.ext
[07:19] <geirha> ok, I don't quite see the problem, then
[07:22] <locsmif> Can I use apt-listchanges to see the changes in packages which are current candidates for apt upgrade?
[07:29] <locsmif> This is pretty stupid https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1927078
[07:30] <locsmif> How about the bug gets fixed in systemd instead, rather than imposing something this drastic on the entire userbase when the bug report even says: "Users may have scripts that are currently using numeric usernames and these scripts will break as a consequence of this deliberate change in stable Ubuntu releases."
[07:32] <locsmif> "ooh but the user names look like uids, we don't like it and we're changing it anyway"  .. sigh .. shades of Firefox dev team imposing their preferences on the user base
[07:35] <geirha> I'm more curious why they were allowed to begin with
[07:36] <locsmif> That's a way better argument, but it doesn't change anything about the lack of care imposing a drastic change which will break things across the board
[07:37] <kushal> How to list only the available security updates in Focal?
[07:37] <locsmif> Seth Arnold in the bug report uses a Perl example to argue ambiguity. sudo perl -e 'print "muahaa\n" if $< == "0x0";'   .. and then says: " the language sure doesn't help " ... which is highly misleading, since the proper string comparison is done with "eq"  not with "==" and fails as expected.
[07:42] <locsmif> Anyways, I know FOSS, and I know how stubborn devs are about imposing high impact changes and delegating the PITA to the user base. This is one of those incidents where there is no accomodation whatsoever, and no consideration of cross-distro compatbility. I don't even use numeric user names, I'm just irritated with the flippancy of the decision.
[07:43] <locsmif> And with the apparent approach of (not) fixing bugs in one subsystem by imposing restrictions on another
[07:48] <locsmif> Also, regarding the Perl example, why the hell would one *ever* compare the real *uid* of a process to a user *name*. The example is so deliberately contrived.
[07:48] <geirha> though looking closer, it's really only user{add,mod,del} that will be affected. numeric usernames will still work, you just can't create them with useradd anymore
[07:49] <locsmif> Yeah
[07:49] <locsmif> Que sera sera, I guess
[08:53] <ash_worksi> geirha: sorry, I got side-tracked again
[08:54] <ash_worksi> the probalem is that I generally can't use the <tab> button when I want to autocomplete files and it's hard for me to read timestamps in a list of other timestamps
[08:55] <ash_worksi> so rather than having to type `vi 20210805_025456_add_^I` I'd rather type `vi *_add^I`
[08:55] <ash_worksi> I feel like you probably already saw me saying that in #bash
[08:56] <ash_worksi> but I guess `shopt -u progcomp` is pretty good for that
[10:20] <ilmais1n> https://askubuntu.com/questions/1245020/xrdp-on-ubuntu-20-04
[10:21] <ilmais1n> wondering why it is so problematic with those remote desktop things nowadays on ubuntu
[10:22] <ilmais1n> that whole "universe" repository does not seem to be a very good concept, so much stuff is simply left to rot there without much maintenance :/
[10:58] <alkisg> Programs in universe are mostly maintained upstream, not in Ubuntu
[10:59] <ilmais1n> yeah, it's kind of an anachronism
[11:02] <iLinux-OS-User> Ubuntu is an anachronism these days...
[11:11] <sunyuhao> Hi
[11:11] <sunyuhao> I am here from China
[11:12] <sunyuhao> emmm.Bye
[12:09] <arkanoid> hello! emergency here: mount: /: cannot remount /dev/sda1 read-write, is write-protected.
[12:09] <arkanoid> I've logged into a system and I've found I/O error in dmesg and / in read-only
[12:09] <arkanoid> remounting / does not work
[12:10] <arkanoid> how can I run fsck here?
[12:12] <iLinux-OS-User> Try running gnome-disks as root.
[12:13] <arkanoid> I'm at command line
[12:14] <arkanoid> everything I do is an input/output error
[12:14] <arkanoid> also reboot doesn't work
[12:14] <arkanoid> gonna try with sysrq
[12:16] <McE> Hi.., i have a question on ubuntus repository..., there seems to be repeatedly the version 8.04.1 in the all the directories of version 8.04.XXXX , no matter if 8.04.1 or 8.04.2 , 8.04.3 , or 8.04.4...., that seems to be redundant data.., right ?
[12:17] <McE> link old-releases.ubuntu.com/releases-8.04.4/
[12:18] <McE> link old-releases.ubuntu.com/releases/8.04.4/
[12:19] <lotuspsychje> McE: those releases are long eol, whats your purpose with this exactly?
[12:21] <McE> no..., its only about the redundant data.., or is the data not redundant ? that is all i want to know for now...., seems to be a lack of proper maintaining to me..., or am i wrong... ?
[12:22] <McE> so the content of 8.04.1 is exactly the same as the content of 8.04.4 .....
[12:23] <McE> as far as directories are concerned...
[12:25] <McE> even the links to 8.04.1 pc-isos , are not pointing to 8.04.1 but to 8.04.4...,
[12:48] <KsamaDa> Hello
[12:48] <KsamaDa> I have a problem
[12:48] <lotuspsychje> ask away KsamaDa
[12:49] <KsamaDa> lotus|NUC where ?
[12:49] <KsamaDa> lotuspsychje
[12:50] <lotuspsychje> here in the channel KsamaDa ask your issue with all your details
[12:50] <KsamaDa> lotuspsychje ok
[12:50] <KsamaDa> I can't seem to have both the micro and output audio  working in the same time.
[12:50] <KsamaDa> I'm using ubuntu 20.04
[12:50] <KsamaDa> audio device : 00:1b.0 Audio device: Intel Corporation 8 Series/C220 Series Chipset High Definition Audio Controller (rev 04)
[12:52] <KsamaDa> HP EliteDesk 800 G1
[12:53] <lotuspsychje> !rootirc | root_
[12:55] <lotuspsychje> KsamaDa: whats your current kernel please?
[12:55] <KsamaDa> 5.11.0-25-generic
[12:55] <lotuspsychje> KsamaDa: we are seeing some recent bug reports on audio on kernel 5.11 so it seems lately
[12:55] <KsamaDa> * the problem still when using headphones as well
[12:56] <lotuspsychje> KsamaDa: like this for example bug #1939010 can you check if this is you?
[12:56] <BluesKaj> Hi all
[13:04] <lotuspsychje> KsamaDa: and idea could be perhaps booting a previous kernel from your list and see if your issue persists
[13:05] <KsamaDa> lotuspsychje ok I'll try it
[13:06] <KsamaDa> ubottu I'm using Desktop not laptop
[13:07] <KsamaDa> I'll try 5.8 for now
[14:25] <lsm5> hi, just curious when golang 1.16.6 will be available on ubuntu 20.04 and 21.04
[14:29] <oerheks> lsm5, for 20.04 unlikely, only bugfixes will be backported
[14:30] <lsm5> oerheks: thanks, there's CVE-2021-34558 (and maybe a bunch of others) all public, which have been fixed in 1.16.6
[14:31] <oerheks> lsm5, one could ask for the update, if you have a reason, see !SRU
[14:31] <oerheks> !sru
[14:31] <oerheks> 1.16.6 12 juli
[14:32] <lsm5> oerheks: are you saying it's already released? i can't seem to find it using `golang-1.16` package
[14:32] <lsm5> it only installs 1.16.2
[14:32] <oerheks> no, it is not in our repos, yet
[14:32] <oerheks> but attention could speed things up
[14:33] <lsm5> ack, i see, thanks
[14:33] <ioria> lsm5, i think 1.16.6 is available via snap, if i'am not mistaken
[14:34] <lsm5> ioria: ack, trouble is I need to build a few packages like podman/buildah etc. on OBS, unlikely I can use snap for i
[14:34] <lsm5> it*
[14:34] <oerheks> oh correct; https://snapcraft.io/go
[14:35] <lsm5> anyway, thanks oerheks and ioria  i'll try to follow the SRU
[14:35] <oerheks> have fun!
[14:39] <lsm5> :)
[15:06] <zteam> Hi, I can't mount one of my ext4 partitions using mount command any longer, it tells me either the Superblock or partition table is corrupted.
[15:07] <zteam> TestDisk doesn't seem to have any complains about either hoewever
[15:13] <oerheks> zteam, how about fsck ?
[15:13] <oerheks> https://help.ubuntu.com/community/FilesystemTroubleshooting
[15:14] <zteam> oerheks, just a moment
[15:20] <zteam> oerheks, the weird thing is that it appears to be happening randomly, sometimes the partition is automounted just as it's supposed to do, other times it fails for some weird reason
[15:22] <zteam> oerheks, no complains from fsck this time around
[15:25] <zteam> dmesg -wH doesnt seem to list any complains either, I will try to reboot and see if still mounts as expected
[15:37] <zteam> Nope, my problem is still here, it just happens randomly :/
[15:37] <oerheks> journalctl -b -0 shows messages from the current boot, journalctl -b -1 from the previous boot
[15:47] <zteam> oerheks, interesting thanks :)
[15:51] <TJ-> zteam: how os the file-system configured? in /etc/fstab, as a systemd.mount unit, and automount ?
[15:52] <zteam> TJ-, I need to doublecheck this, just a moment
[15:53] <TJ-> zteam: also of importance, does the system shutdown/roboot cleanly each time or is something hanging - its possible the journal isn't being closed
[15:54] <zteam> TJ-, /etc/fstab how to tell if it's using systemd.mount or not?
[15:55] <zteam> I'm not really sure what to look for with journalctl either
[15:56] <TJ-> zteam: it'd be either/or ... at start-up systemd, before anything else, executes its generators. one such is systemd-fstab-generator which converts fstab entries into systemd.mount units
[15:56] <TJ-> zteam: since there is a .mount unit for your device there is a log you can look at for it. Identify the .mount unit name and then do "journalctl -u XXXX.mount"
[15:57] <TJ-> zteam: .mount unit names are the path to the device with / replaced with -
[15:58] <zteam> TJ-, okey, this is fair beyond my knowkedge, I can post my fstab if you like :-)
[15:58] <TJ-> zteam: correction. path to mountpoint! as in "/dev/mapper/containers /var/lib/containers ext4 ..." would result in var-lib-containers.mount unit
[15:59] <TJ-> zteam: so as you'll know your mountpoint path, you can check the log. In my example above I'd o "journalctl -u var-lib-containers.mount"
[16:00] <TJ-> what is nice is that system-fstab-generator /also/ creates an fsck unit to check the mount before it is mounted
[16:01] <zteam> TJ-, I'm using a luks-encrypted harddrive it's indeed inside a /dev/mapper/
[16:01] <TJ-> zteam: what's the mountpoint ?
[16:04] <zteam> TJ-, /media/Ny%20volym
[16:04] <genii> Hm, %20
[16:04] <TJ-> zteam: so the unit would be media-Ny%20volym.mount
[16:05] <TJ-> zteam: try "journalctl -u media-Ny%20volym.mount"
[16:05] <TJ-> zteam: you'll likely need to jump to the end of the log. Easiest is to press capital G in the pager
[16:05] <zteam> here is a dump of /etc/fstab  https://paste.ubuntu.com/p/MtcPvDhdbt/
[16:10] <zteam> TJ-, it complains about the superblock https://paste.ubuntu.com/p/HM8NShGNhs/
[16:11] <TJ-> zteam: are you booting multiple OSes that each access this same file-system?
[16:13] <zteam> TJ-, nope, only Ubuntu 21.04, also this paste is in English (sorry for the mistake) https://paste.ubuntu.com/p/3dyXmg9g7k/
[16:15] <robertparkerx> https://www.linkedin.com/pulse/non-nonsense-way-configure-apache-ssl-termination-varnish-gjoko-pargo/
[16:15] <robertparkerx> I follow the last setup for systemctl and I get errors
[16:16] <robertparkerx> failed to load environment files: no such file or directory
[16:16] <TJ-> zteam: that's ok, I can read it :)
[16:16] <zteam> genii, Yep, it's because the mount point contains a space
[16:17] <zteam> fstab doesn't like normal spaces :P
[16:17] <TJ-> zteam: the only thing I can think of seeing as the log seems to show unmounting being done is that some process is writing random data to the file-system's metadata area whilst in normal use. That'll not be detected until the file system is next checked
[16:20] <genii> zteam: I'm mostly wondering why /media/Ny%20volym instead of /media/Ny\ volym
[16:21] <zteam> TJ-, sometimes the system indeed shows some error about that, now that you mention it, would that be logging in /var/log/syslog ?
[16:23] <zteam> genii, yeah I know, it works as intended for bash and stuff, but it doesn't look to pretty in Nautilus for example
[16:23] <genii> Ah, ok
[16:29] <zteam> genii, Yep, you can't use mount-points with spaces in /etc/fstab but you can add %20 to a mount point this way you can still reach it as if it was named "Ny volym" :-)
[16:29] <TJ-> zteam: it's be in the main journal. If you have an idea of some unique text in those errors you could try grep-ing for it with "journalctl | grep 'search-term' to narrow down the time range, then use journalctl --since="<some-starting-date>" --before="<some-ending-date>" to look at all messages around that time
[16:29] <m1dnight> Hi all. I'm running an app in Wine, and when I start it as regular user my audiocard drops out for a second. When I start wine as root it doesnt.
[16:29] <TJ-> %20 is just the hexadecimal encoding of the ASCII value of a space (32 decimal, 0x20 hexadecimal)
[16:30] <m1dnight> When I run winecfg as regular user I dont see any errors printed on stdout/err though.
[16:31] <genii> zteam: I think if it's encapsulated within single quotes it works, but I haven't tinkered with the fstab in a while to remember exxactly
[16:34] <zteam> m1dnight, never run wine as root, I personally just use PlayOnLinux or Lutris then using wine, it makes it easy to follow the logs from Wine as well as tinkering with Wine for you
[16:38] <zteam> TJ-, isn't there any trick to ask the journal about which files got created last?
[16:48] <zteam> I'm back
[17:27] <mago> Hello, how do i rename all files in folder?
[17:27] <matsaman> mago: how? why?
[17:28] <mago> Im trying to batch convert acc files to mp3 but the regex breaks...
[17:28] <mago> Cuz my file names have spaces and quotes ' " in them...
[17:28] <mago> So in need to rename to easier file names..
[17:28] <matsaman> using bash is one easy way: for i in *.aac; do echo "$i" "${i%.aac}.mp3"; done
[17:29] <matsaman> the 'rename' package in universe is also a lovely perl app
[17:29] <matsaman> you can do things like: rename 's/\.aac/\.mp3/g' *.aac -n
[17:29] <matsaman> (-n is dry run, re-run without if you like the output)
[17:30] <mago> matsaman im not sure if that did something.. I runned the command but the files stayed the same..
[17:30] <matsaman> you might have a rename.ul executable already installed, too, and that's ... mostly inferior to everything, IMO =P
[17:30] <matsaman> mago: yes the echo one uses echo instead of 'mv' on purpose, so you can ease into it
[17:30] <matsaman> the 'rename' one uses -n, which is for dry run
[17:31] <mago> I understand not..
[17:31] <matsaman> for i in *.aac; do mv -n "$i" "${i%.aac}.mp3"; done would probably be okay to do the actual rename
[17:31] <mago> But that will just rename not convert..
[17:31] <matsaman> oh convert, then you want ffmpeg
[17:31] <mago> I think i need to change the file name not the extension.. Yes but ffmpeg break cuz they have weird names...
[17:31] <leftyfb> mago: you were asking about renaming, you didn't mention converting. Do you want to rename or convert?
[17:32] <matsaman> for i in *.aac; do ffmpeg -i "$i" "${i%.aac}.mp3" </dev/null; done
[17:32] <mago> Thats what i was trying: for i in *.aac; do ffmpeg -i "$i" -vn -ar 44100 -ac 2 -b:a 192k "${$i/aac/mp3}"; done
[17:32] <matsaman> there are GUIs, too
[17:32] <matsaman> like um... what is it called
[17:32] <oerheks> aac to mp3, only possible if it is unencrypted
[17:32] <mago> Thats an example filename: '5 Aug, 18.29(2).aac'
[17:33] <matsaman> mago: filename won't likely matter
[17:33] <oerheks> else you end up with a 64 bit mp3 :-D
[17:33] <mago> Can you help me correct that command: for i in *.aac; do ffmpeg -i "$i" -vn -ar 44100 -ac 2 -b:a 192k "${$i/aac/mp3}"; done
[17:33] <leftyfb> mago: https://stackoverflow.com/questions/22766111/ffmpeg-not-working-with-filenames-that-have-whitespace
[17:33] <mago> Probably is the regex
[17:33] <matsaman> mago: why do you care about -ar and -ac and -b:a ?
[17:33] <mago> Someone is requesting those specs..
[17:34] <matsaman> oh okay
[17:34] <mago> Like im making an audio for an online radio program..
[17:34] <matsaman> mago: if you add </dev/null before '; done', does it work? What is the error
[17:34] <matsaman> mp3}" </dev/null; done
[17:35] <fling> What is the sources package for linux modules?
[17:35] <mago> matsman it says bad substitution
[17:36] <oerheks> fling, on launchpad
[17:36] <mago> matsaman it says bad substitution
[17:36] <mago> Sorry: bash: ${$i/aac/mp3}: bad substitution
[17:36] <matsaman> mago: do it the way I said, then
[17:37] <matsaman> for i in *.aac; do ffmpeg -i "$i" YOUR_OTHER_OPTIONS_HERE "${i%.aac}.mp3" </dev/null; done
[17:38] <matsaman> mago: if you want a GUI there's 'handbrake' in the 'universe' repo
[17:38] <matsaman> you'll have to hunt down the little places to specify all your rate options and that
[17:38] <matsaman> but you won't have to worry about substitutions
[17:38] <mago> Ok, that was working, it was a regex issue then..?
[17:39] <mago> Thanks a lot matsaman :)
[17:40] <oerheks> check the quality of the 1st mp3?
[17:41] <matsaman> mago: something in the substitution syntax possibly yeah
[17:41] <matsaman> it's (trivially) less efficient, but if you want to avoid having to deal with bash's weird syntax, you can instead do things like: "$(echo "$i" | perl -pe 's/\.aac/\.mp3/g')"
[17:44] <fling> oerheks: do you have a link?
[17:44] <oerheks> oh you could have found it by now
[17:44] <oerheks> google linux-modules launchpad
[17:45] <fling> oerheks: zfs is there right?
[17:45] <fling> zfs.ko
[18:13] <alzgh> Reading the man pages is a not so easy skill in itself
[18:15] <webchat52> hello
[18:15] <varaindemian> how can I remove keys added with `wget -q https://www.virtualbox.org/download/oracle_vbox_2016.asc -O- | sudo apt-key add -`
[18:16] <varaindemian> ?
[18:16] <webchat52>  sort of a low-tech guy, wanting to dual boot my laptop (win10/ubuntu 21)... however, my main question is how to do this with 2 hd's? i want one only for starting up (which is my smallest) but then i want my large one as main hd for running everything within ubuntu
[18:18] <varaindemian> anyone?
[18:19] <Mekaneck> !patience | varaindemian
[18:19] <alzgh> `apt-key list` gives you the list, `apt-key del {{key_id}}` removes a particular key from apt's store
[18:22] <varaindemian> alzgh which one is the key id?
[18:22] <varaindemian> I see too many things there
[18:22] <varaindemian> uid
[18:22] <varaindemian> ?
[18:23] <alzgh> haha, I want to that too. I'll search that if no one chimes in.
[18:23] <alzgh> *to know
[18:23] <tarzeau__> ok i've got ubuntu 20.04, i have systemd-networkd, and networkctl gives me:   2 eth0 ether    routable    pending, runlevel says unknown
[18:24] <tarzeau__> and resolv.conf tells me # No DNS servers known. and i wonder how i'd debug/fix that?
[18:24] <tarzeau__> first systemd failed booting because there was /etc/rc.local (that file is gone now)
[18:26] <leftyfb> tarzeau__: server or desktop?
[18:26] <tarzeau__> leftyfb: i call it desktop, but it's mounted in the serverroom
[18:26] <leftyfb> tarzeau__: ok, so desktop. Why can't you use the Network Manager GUI to connect to a network?
[18:27] <tarzeau__> leftyfb: ugh, because when i have 200 machines, i don't want interactive guis?
[18:27] <tarzeau__> so we don't have network manager, it's removed/purged/gone/nonexistant
[18:27] <leftyfb> tarzeau__: ok, so have you completely disabled Network Manager and are just using netplan/networkd to manage the network?
[18:28] <tarzeau__> leftyfb: no netplan, just systemd-networkd
[18:28] <leftyfb> tarzeau__: why not netplan?
[18:28] <tarzeau__> leftyfb: because some collegues think, we don't need another layer on top of it
[18:28] <alzgh> @varaindemian Do you have access to the desktop? If so, Software & Updates -> Other Software -> remove the checkmark for the rep key you want to remove.
[18:29] <tarzeau__> but that's how the config file looks: https://bootes.ethz.ch/host.network
[18:32] <tarzeau__> i wonder how can i tell systemd-networkd or networkctl to retry to do the same as when i had dhclient and would run it
[18:32] <tarzeau__> normally i'm able to google such things myself. but whatever is related to systemd, i'm having trouble to find anything useful
[18:32] <tomreyn> alzgh: varaindemian is looong gone. ;-) something along the lines of this could have worked:  mkdir /tmp/x; gpg --home /tmp/x --list-keys &>/dev/null; wget -qO- https://www.virtualbox.org/download/oracle_vbox_2016.asc | gpg --home /tmp/x --import &>/dev/null; gpg --home /tmp/x --list-keys --fingerprint; rm -r /tmp/x
[18:33] <tomreyn> (hopefully there's an easier way)
[18:34] <alzgh> there is the `apt-key del {{key_id}}` command. But I'm not sure what the `key_id` exactly is tomreyn
[18:35] <oerheks> `wget -q https://www.virtualbox.org/download/oracle_vbox_2016.asc -O- | sudo apt-key del -`
[18:35] <oerheks> easy
[18:35] <tomreyn> alzgh: oh that's not in there, yet, you'd need to add that, yet. i just tried to show how to get the key id / fingerprint of the key published at the given http location
[18:36] <alzgh> O, thank. I'm going decipher that hoping to learn from it :D
[18:36] <sarnold> it's *so* much easier to just add the key to the /etc/apt/trusted.gpg.d directory instead -- then deleting it is a simple 'rm'
[18:37] <tomreyn> yes, but i think the task here was removing a key that was in the joint keyring
[18:42] <tarzeau__> will there be 30.04? 40.04 of ubuntu?
[18:42] <sarnold> tomreyn: yeah.. the best time for this would have been several years ago :)
[18:43] <leftyfb> !yy.mm | tarzeau__
[18:43] <aniketgm> tarzeau__: you're way into the future.
[18:43] <tarzeau__> aniketgm: planning retirement...
[18:49] <aniketgm> tarzeau__: there won't be any retirements for ubuntu. I might change to something else, but it's gonna live on.
[18:50] <aniketgm> btw, ubuntu was my first linux distro ever.
[18:51] <alzgh> ubuntu has the largest market share rn among normal users
[18:51] <alzgh> I guess
[18:51] <oerheks> i wish there were reliable stats about that.
[18:53] <alzgh> rn ubuntu has (if not the lowest) one of the lowest barriers of entry into the linux world.
[18:53] <alzgh> also my armchair thoughts
[18:53] <alzgh> no proof
[18:54] <aniketgm> oerheks: I think there is. https://ubuntu.com/desktop/statistics#user-report, If i'm not mistaken
[18:54] <aniketgm> * I mean stats
[18:54] <oerheks> yes, known statistics, but limited. there used to be https://stats.wikimedia.org/wikimedia/squids/SquidReportOperatingSystems.htm but it is discontinued in 2015
[18:55] <oerheks> still those stats are not complete too, nor iso downloads, nor updates
[18:55] <aniketgm> yeah, that's a bummer.
[18:56] <oerheks> say 4% market share desktop, 40-50% ubuntu
[18:57] <aniketgm> SquidReports were really good one. Not sure why they discontinued. maybe they got lazy. idk. :p
[19:00]  * srv running ubuntu apps on windows think windows still beter Os than linux but nice to run ubuntu apps in windows
[19:04] <aniketgm> Windows turned to linux simply because they know they'd loose the game.
[19:04] <leftyfb> Feel free to take the discussion to #ubuntu-offtopic
[19:05] <aniketgm> leftyfb: *thumbsup*
[19:21] <coke> windows turned to linux cause microsoft saw that developers needed stuff windows couldn't give them
[19:42] <alzgh> tomreyn the keyid for `apt-key del` is the 8 last characters of the fingerprint that you get from `apt-key get`. That's kinda weird bc one expects it to be the first characters. But you probably know that already :]
[19:52] <jcd_> Hi. Is there anything like xdmx, but for wayland instead of X ?
[19:53] <poop> hey
[19:55] <sarnold> jcd_: pipewire maybe?
[19:59] <tomreyn> alzgh: you can actually pass the whole fingerprint (which is the safest approach). the last 8 characters are the "short key id", this should no longer be used, it's insufficiently unique, because a key with the same short key id can be generated on demand. then there's the "long key id", last 16 characters of the fingerprint, this is currently being used to identify keys where it does not seem necessary to match the full fingerprint.
[20:02] <alzgh> I passed in the whole fingerprint to `apt-key del` and it didn't work. I didn't try the 16 character version though
[20:06] <tomreyn> alzgh: if it contained blank spaces you'd need to enclose it in single or double quotes. also, i find that apt-key often acts strangely
[20:07] <tomreyn> tarzeau__: in case it helps, systemd-networkd configuration on a pretty much freshly installed 20.04 server virtualbox vm https://i.imgur.com/GStrgIT.png
[20:08] <alzgh> Ahh, that's it. I didn't enclose it in quotes. Also, `apt-key` output can't be parsed. What are the alternatives for scripting and stuff? tomreyn
[20:12] <tomreyn> alzgh: using gpg directly, i guess.
[20:21] <EandC> Hi everyone. Can anyone help me with a booting issue? I've tried a few things but at this point I'm all ???
[20:23] <JoshMulliken> What exactly is happening?
[20:24] <EandC> The machine is running 18.04 with a fully encrypted drive, but can't boot after I've unlocked the drive. I've tried using an older kernel from GRUB's advanced settings page thing, and the same thing results. I tried using recovery mode to fix things and that still hasn't helped. I moved into root and mounted the LVM, etc, proc, and all of that and tried a dist upgrade, but still nothing. Right now I have a black screen with a flashing
[20:24] <EandC> cursor.
[20:25] <EandC> I figure it's an issue with GRUB somewhere because I was able to access the drive as an extrnal and pull the files from it. Not sure if there's corruption in that sector fo the drive because I did find a bad block a few restarts ago.
[20:27] <EandC> One failure message I noticed was "Failed to start Load Kernel Modules"
[20:27] <EandC> Two show up, but the other moves so quickly I can't catch it
[20:28] <JoshMulliken> Can you run the ubuntu installer and perform an upgrade? It should keep you r files but it will refresh the system
[20:28] <EandC> From a LiveUSB?
[20:29] <JoshMulliken> Yeah
[20:30] <EandC> Ok, I'll try
[20:30] <JoshMulliken> I don't know if it will like the encrypted filesystem but it might be worth a try
[20:32] <EandC> Really all I'm after are firefox tabs that I didn't have bookmarked, and some log and settings files. So it's nto a gigantic issue if I can't get back in, but it would also be nice to know a method to do so if I encounter this in a worse situation somehow later
[20:34] <tomreyn> EandC: apparently it's related to kernel modules, probably third party kernel modules, posing problems. does this ring a bell in terms of recent changes you made? the best way to recover from this is probably a chroot from a current 18.04 LTS live / installer system
[20:34] <EandC> Yeah, doesn't seem like a LiveUSB install will play nice with the existing system in any way
[20:34] <tomreyn> i dont think it would, no
[20:34] <EandC> I did a chroot process
[20:34] <EandC> Let me find the tab
[20:35] <EandC> Nothgin really rings a bell regarding installs I did around that time
[20:35] <EandC> I was able to get into the system fine one day, adn then on next reboot it froze up, adn then I couldn't get back in
[20:35] <tomreyn> do you know that you're using out of tree modules, though?
[20:35] <EandC> so I think the bad block messed something up, and then I might've troubleshot myself into a worse situation?
[20:36] <tomreyn> you'll rarely ever have a single bad block, and if you have any, you really should replace the disk asap
[20:37] <EandC> Yeah, fortunately I was already doing a backup when this happened. I just wanted to see if I could snag a few more files before runnigng diagnostics on it and then sending it in for RMA
[20:37] <EandC> This is the chroot process I went through https://askubuntu.com/questions/857028/how-can-i-install-a-boot-for-my-encrypted-root-partition
[20:38] <EandC> I also tried grub-install and update-grub
[20:39] <EandC> Of course, I did it with vg root mounted instead of just generic sda
[20:44] <tomreyn> EandC: is this an uefi booting or (legacy) BIOS booting system?
[20:45] <tomreyn> you may also want to bind mount /run
[20:45] <EandC> uefi I think
[20:45] <tomreyn> for uefi you'll aos want to mount the ESP
[20:45] <EandC> but it has legacy support mode enabled
[20:45] <tomreyn> aos -> also
[20:45] <EandC> ok
[20:45] <tomreyn> make sure you boot the recovery system in the same boot mode as the installed system
[20:46] <EandC> Yeah
[20:46] <EandC> Alright, thanks. I'll fiddle with it for a while longer
[20:46] <tomreyn> if its legacy bios then legacy bios, and then you don't need (and cannot) moiunt the ESP, because there wont be one.
[20:46] <EandC> Right
[20:47] <tomreyn> also    dpkg --configure -a && apt update && apt -f install && apt update && apt upgrade && apt full-upgrade
[20:47] <tomreyn> then update-grub, then grub-install
[20:48] <tomreyn> make sure you mount /boot though
[20:50] <tomreyn> EandC: while in the chroot, you can also inspect what was logged about the previous boot (-1, -2 would be last but one) using: journalctl -b -1
[20:59] <TJ-> tomreyn: FYI even without a chroot you can do "journalctl --root=/path/to/root-fs-mount ..." and read the logs as normal
[21:00] <TJ-> tomreyn: (assuming ./var/log/journal/ exists there and persistent logging of course)
[21:00] <tomreyn> TJ-: thanks. they were going to chroot anyways, though
[21:03] <TJ-> right - just thought I'd mention it since it can come in very useful
[21:04] <TJ-> for example, on foreign architectures where you can't easily execute programs in the chroot
[21:05] <tomreyn> yes, indeed that'd be helpful
[21:12] <EandC> Ok, I got tired of it and I'm just going to reformat and install Ubuntu 20.04 and see what I can find out about the disk's status
[21:13] <EandC> Thanks for the help
[21:42] <solar_sea> Hi. I am trying to boot a 20.04 server lts image written with the rpi imager to a headless rpi 4. It successfully gets an ip from my dhcp server but it seems that its sshd is disabled as I cannot open a shell to it (ssh times out). Is there a way to make it send its console over tcp ? I would really like to avoid plugging in a monitor and a keyboard. Thanks!
[21:43] <sarnold> solar_sea: there's a chance that it's just taking an eternity to generate initial host keys
[21:44] <matsaman> solar_sea: ssh as ... a user, or root?
[21:44] <sarnold> solar_sea: without a keyboard there might not be a great way for the kernel to gather entropy; I'm not sure if the sshd startup sequence uses the blocking random or the non-blocking urandom, but I bet it's the blocking random
[21:44] <solar_sea> sarnold, the thought crossed my mind, perhaps not having enough entropy due to no peripherals attached..
[21:44] <solar_sea> yeah, same
[21:45] <sarnold> solar_sea: exactly :) maybe just plug in a keyboard, and hit space backspace space backspace etc a bunch?
[21:45] <solar_sea> matsaman, doesn't matter as the ssh socket/handshake is timing out :)
[21:45] <sarnold> hehe
[21:45] <toddc> RPI ssh is disabled for root by default
[21:46] <matsaman> keys =P
[21:46] <matsaman> what a pain
[21:46] <sarnold> we should all just use the same one, save all kinds of trouble
[21:47] <matsaman> hehehe
[21:47] <tomreyn> one key to rule them all, generated by aws.
[21:47] <solar_sea> thermal entropy should be enought for a first-boot one, heh
[21:49] <matsaman> well
[21:49] <matsaman> being able to ssh in in the first place
[21:49] <matsaman> that should be a priority over key generation
[21:59] <Guest18> hey dudes
[22:00] <Guest18> can I put ubuntu on this one https://www.dateks.lv/cenas/datorkomplekti/711127-dateks-intel-core-i7-gen11-gmng-core-i7-11700k-16gb-2x8-ddr4-radeon-rx-6800-xt-1tb-nvme-bez-os?utm_source=salidzini&utm_medium=ad_item
[22:00] <Guest18> 2,5k PC :d
[22:00] <Guest18> it should work quite okay? :d
[22:00] <leftyfb> Guest18: I don't think anyone is going to be able to answer that with 100% confidence. You'll probably be ok
[22:01] <sarnold> Guest18: when computers are sold without an OS it usually means it'll work okay with linux
[22:02] <TJ-> sarnold: or alternatively, it won't work with MS Windows :P
[22:05] <sarnold> TJ-: hah, I hadn't thought of that :)
[22:07] <toddc> what computers will not work with linux is a short list
[22:08] <sarnold> you might be in trouble with video cards or network cards etc
[22:08] <sarnold> but I think the modern radeons have okay support
[22:13] <Guest18> I'm seriously just buying new PC
[22:13] <Guest18> and linux is just a thingI am used to
[22:13] <Guest18> can't decide at all
[22:14] <Guest18> this laptop looks kinda on spot
[22:14] <Guest18> https://www.xnet.lv/lv/elektronika/portativie-datori/portativie-datori/acer-nitro-5-an515-44-r8vf-black_0ec283d1
[22:15] <SnoopJ> I suffered a power loss earlier today, and both gdm and GNOME appear to be broken now, I get what looks like an indefinite startup loop with gdm, and a "Oh no! Something went wrong" message with GNOME when invoking it from lightdm (which works fine). Any obvious things I should try?
[22:17] <Guest18> going into TTY
[22:17] <leftyfb> SnoopJ: boot with a live cd/usb and run fsck
[22:17] <leftyfb> !fsck | SnoopJ
[22:17] <Guest18> finding if You have free space
[22:24] <SnoopJ> Hadn't done a fsck, but no joy after having run one, same problem.
[22:30] <tomreyn> SnoopJ: check logs, journalctl -b
[22:45] <SnoopJ> hmm, I'd done that before and not seen anything, but after another attempt at logging in, I'm seeing a segfault along with some dbus errors that seem fairly benign. https://bpa.st/UZDA
[22:53] <tomreyn> SnoopJ: do you have third party apt repositories configured? which? gnome-shell extensions?
[22:54] <tomreyn> the process that failed is gjs, more info: apt show gjs
[22:57] <tomreyn>  ~/.local/share/gnome-shell/extensions contains your manually installed gnome shell extensions
[22:57] <SnoopJ> Directory does not exist, no extensions that I'm aware of.
[22:58] <SnoopJ> Have a few third-party repositories: docker, nvidia-docker, signal-xenial (what the heck?), ubuntu-toolchain-r-ubuntu-test-focal, yubico-ubuntu-stable-focal
[23:00] <tomreyn> SnoopJ: so this is 20.04 LTS?  what's the output of     apt policy gdm3 gjs gnome-shell libffi7    - on a pastebin?
[23:01] <SnoopJ> 20.04.2, yes. policies: https://bpa.st/REMQ
[23:02] <SnoopJ> Not sure why groovy is showing up there, seems a little suspect.
[23:03] <tomreyn> SnoopJ: can you show just     apt policy   as well, and    apt list --installed | grep ',local\]$' | nc termbin.com 9999
[23:04] <tomreyn> yes, "groovy" looks like you're mixing ubuntu releases
[23:05] <tomreyn> lsb_release -ds; cat /proc/{version*,cmdline}
[23:07] <SnoopJ> lsb_release/version/cmdline: https://bpa.st/WACA apt policy: https://bpa.st/PHLQ local packages (just one: zoom): https://bpa.st/6NGQ
[23:08] <SnoopJ> can switch paste services if bpaste is unwanted, it's just what I have handy
[23:09] <tomreyn> bpa.st works for me, i just took the stuff with termbin off a cheat sheet
[23:10] <SnoopJ> I don't recall doing anything with groovy since this install was brand-new. I did do some mix-and-match on the previous (eoan) install because I was trying to get to gcc-10. It went poorly, but the upshot is that I'm no longer running a deprecated release :)
[23:10] <tomreyn> yes, you're now running two recent releases
[23:10] <SnoopJ> should I knock out groovy and re-install ubuntu-desktop and friends, maybe?
[23:11] <tomreyn> probably, yes
[23:11] <SnoopJ> ta, will have a go
[23:11] <tomreyn> remove anything too  'groovy' there, then downgrade all package versions that are of unknown origin
[23:12] <tomreyn> apt list --installed | grep ',local\]$'   will list those after removing the 'groovy' apt repositories and running apt update
[23:12] <tomreyn> (groovy is actuall EOL by now)
[23:13] <SnoopJ> ...yep, definitely have a chimera running. I think this is the source of my grief here, especially because I installed gnome-tweaks today and it appears to have been the groovy package.
[23:13] <tomreyn> i'm not sure what those nvidia repositories provide, which seem to be made for ubuntu 18.04 LTS - those might introduce dependency issues as well
[23:14] <SnoopJ> I think that's for libnvidia-container-tools, for GPU pass-through.
[23:14] <tomreyn> well, your gdm, gnome-shell and gjs are also groovy's, so it's surprising you got this far
[23:15] <SnoopJ> I too am consistently surprised by how readily my computers attract hexes. I think it's got something to do with the user. Okay, let me see about cleaning up the packaging mess, thanks for the pointer on ,local], that's handy.
[23:15] <tomreyn> you should read up on apt pinning if you'll ever consider mixing ubuntu release apt sources again
[23:16] <SnoopJ> I think I did my first real pinning in the gcc-10 adventure, because what I was doing was deeply evil. I truly have no idea how groovy stuff got in this install, though, I feel like I'd at least remember the anxiety over mixing like that, considering how recently it destroyed my system.
[23:16] <tomreyn> yes, it doesn't seem to be OSI layers 1-7 that would have introduced these issues.
[23:18] <SnoopJ> 😅
[23:21] <tomreyn> SnoopJ: you know how to downgrade, right?  apt -t focal install <package>
[23:21] <tomreyn> or maybe "focal-updates"
[23:22] <SnoopJ> Don't think I've ever tried one
[23:25] <SnoopJ> oh gjs itself is from groovy. makes sense
[23:26] <ice9> was anyone able to use apple airpod pro as head set with linux?
[23:28] <tomreyn> ice9: i assume you already searched the web? i ran into discussions on the topic at some point - don't rmeember the details, but do try that if you haven't, i bet there will be some suggestions.
[23:28] <ice9> tomreyn, i tried that already but it didn't work as full headset, only as speaker
[23:29] <tomreyn> i see
[23:30] <tomreyn> ah right, this is what i read. the workaround is really ugly, though. https://reckoning.dev/blog/airpods-pro-ubuntu/
[23:31] <tomreyn> better try this first https://askubuntu.com/questions/922860/pairing-apple-airpods-as-headset
[23:31] <tomreyn> there are different hardware models / generations, though, so YMMV
[23:33] <guzzlefry> Is it generally okay to do a release upgrade with the desktop environment running?
[23:34] <tomreyn> guzzlefry: as long as you do it with the tools meant to be used for it, and after preparing for the release upgrade, yes
[23:35] <tomreyn> update-manager -c   should get you started for the upgrade, but i'd recommend removing all third party packages (i.e. downgrade packages to ubuntu's) and versions before you get started
[23:36] <tomreyn> and, of course, have backups
[23:38] <guzzlefry> Is there a guide on removing third party stuff?
[23:40] <tomreyn> not that i know of. the general process i would use is: disable / remove third party repositories, run    sudo apt update    and make sure it doesn't remooprt anything but ubuntu repositories, and no warnings or errors, then go through the packages listed by    apt list --installed | grep ',local\]$' | nc termbin.com 9999    and either purge or downgrade them
[23:42] <tomreyn> remooprt -> report
[23:43] <jeffmr_> any reason tty should not work in 18.04.5?
[23:44] <tomreyn> guzzlefry: apt policy <package1> <package2> <...>    lets you check which apt source provides the package version you currently have ("/var/lib/dpkg/status" means: this is currently installed; if this is not the same version as the "archive.ubuntu.com" or "security.ubuntu.com" one, then you need to downgrade this package).
[23:45] <jeffmr_> I try ctrl + alt + F1 - F6 and I get nothing.
[23:45] <tomreyn> jeffmr_: nothing generic
[23:46] <jeffmr_> I'm using a new apple keyboard with an option (alt) key but it works for opening a terminal, ctrl + alt + t
[23:46] <tomreyn> maybe it needs another function key or something to use F keys
[23:47] <SnoopJ> oh boy, pkgProblemResolver is choking on trying to swap out all the wrong/weird packages in one go. Might be a bigger surgery than I'd hoped.
[23:47] <jeffmr_> aha
[23:47] <tomreyn> SnoopJ: see, that's why i suggested fixing it first ;)
[23:48] <jeffmr_> that was it.  I didn't see the fn key over by the keypad.
[23:48] <jeffmr_> thx
[23:48] <SnoopJ> tomreyn, I may not have understood what you were suggesting. Nothing's really changed since it barfed on the problem and bailed out.
[23:48] <tomreyn> SnoopJ: actually i mixed you up with guzzlefry there, spologies
[23:49] <tomreyn> SnoopJ: what'S the command you ran, and its output?
[23:49] <SnoopJ> ah. well, it's not like my system got this way by not touching the live wire, groovy didn't just come out of nowhere
[23:49] <tomreyn> most likely not ;)
[23:50] <SnoopJ> tomreyn, I ran `sudo apt install $(cat allow_pkgs.txt)` where that file is a list of local packages minus the ones it previously said it couldn't even recognize for focal (a goodly number of num)
[23:50] <SnoopJ> sec on output
[23:51] <SnoopJ> https://bpa.st/LDUA
[23:55] <tomreyn> SnoopJ: looks like you forgot to ask it to downgrade gcc-10 (to focal's version 10.3.0-1ubuntu1~20.04)
[23:56] <tomreyn> libhdf5-cpp-103 libhdf5-103 also need to be downgraded to focal's version
[23:56] <tomreyn> i don't know how you assembled allow_pkgs.txt or what's (not) on it, though
[23:57] <tomreyn> i suspect ppa:ubuntu-toolchain-r/test may be getting in the way
[23:57] <SnoopJ> looks like I just didn't bang on helping the resolver enough with constraints, then. Did a few iterations of dropping in the stuff it was complaining about and have a solution. Thanks for that
[23:59] <SnoopJ> Going to start the fireworks now and see how it goes...


[00:57] <effie-jayx> hello all
[00:59] <cjohnston> o/
[01:08] <JanC> hello effie-jayx, long time ago since I saw you on-line  ☺
[09:30] <YoBoY> bonjour
[09:31] <leoquant> YoBoY, comment t'allez vous?
[09:31] <YoBoY> :D
[09:31] <YoBoY> i'm fine, and you ?
[09:31] <leoquant> va bien?
[09:32] <leoquant> comme ci comme ca...
[09:32] <leoquant> ツ
[09:32] <YoBoY> playing with lanchpad this morning and our locoteam subteams
[09:33] <YoBoY> too many subteams ^^"
[10:59] <AbhiJit> hello all
[11:00] <AbhiJit> this is our language trranslation team
[11:00] <AbhiJit> https://launchpad.net/~ubuntu-l10n-mr
[11:00] <AbhiJit> and it is not active
[11:01] <AbhiJit> there is only one author. and now mjembers are growing.; and he is busy doing his work. so can i become operator?
[11:01] <AbhiJit> so that i can approve all those members and get team to work?
[11:01] <czajkowski> AbhiJit: have you talked to him?
[11:01] <AbhiJit> i cannot contact to team because email to mailig list is moderated
[11:01] <AbhiJit> czajkowski, ^^^^
[11:01] <AbhiJit> thats why iu cant talk to him
[11:01] <AbhiJit> i send 3 eamils
[11:01] <AbhiJit> all are waiting
[11:01] <AbhiJit> because he not there to approve
[11:02] <AbhiJit> there are 35 members in waiting to approve
[11:02] <czajkowski> AbhiJit: https://launchpad.net/~onkarshinde  mail him  his details are there
[11:02] <AbhiJit> czajkowski, ok
[11:04] <AbhiJit> czajkowski, ok what is my option if he not reply? how many days should i wait?
[11:05] <czajkowski> AbhiJit: well give him a chance, a few days, maybe a week to reply
[11:05] <AbhiJit> ok
[11:05] <czajkowski> people do work and may not check their mail or could be on holiday etc
[11:06] <AbhiJit> he is inactive since 4 monyhd
[11:06] <AbhiJit> months
[11:06] <czajkowski> AbhiJit: mail him and talk to him :)
[11:07] <AbhiJit> czajkowski, yah doing that only
[11:07] <AbhiJit> thank you
[11:08] <czajkowski> np
[11:10] <AbhiJit> czajkowski, if i want to create our local ubuntu channel then should i get permission from someone or just i can create directly?
[11:14] <czajkowski> AbhiJit: you need to talk to someone in the irc ops I dont know sorry.
[11:14] <AbhiJit> ok
[11:46] <trinikrono> hey guys we at the trinidad and tobago loco team have done our first ubuntu hour yay!
[12:08] <YoBoY> great trinikrono :)
[12:08] <YoBoY> how many people ?
[12:18] <trinikrono> like 8 YoBoY
[12:18] <trinikrono> :D
[12:19] <trinikrono> they really gave me a good bashing though
[12:19] <trinikrono> about how ubuntu does work too good on umpc's
[12:19] <trinikrono> *does not
[15:42] <TrickyJ> HI all :)
[15:46] <trinikrono> o/
[16:08] <TrickyJ> Ronnie: Hey buddy howzz u doing
[16:08] <Ronnie> in the middle of a IRL team meeting
[23:56] <Ronnie> mhall119: i created some specifications for the maps library for django-foundations. can you review them https://blueprints.launchpad.net/ubuntu-django-foundations/+spec/maps-jquery-plugin
[23:56] <Ronnie> if someone else also want to review it, be my guest :)


[14:02] <psusi> are there any release managers for lubuntu and ubuntustudio around?  Their cd images aren't being built right ( missing pool; see #1633913 )


[14:20] <seb128> could someone trigger a repack for git.launchpad.net/network-manager ?
[15:07] <cjwatson> seb128: done
[15:07] <seb128> cjwatson, thanks


[14:29] <sarnold> good morning
[14:29] <eslerm> hello
[14:29] <dviererbe> o/
[14:30] <didrocks> hey
[14:31] <cpaelzer> hi
[14:31] <didrocks> seems it will be only us again?
[14:31] <didrocks> ah cpaelzer is back :)
[14:31] <didrocks> wb!
[14:31] <cpaelzer> give me a sec to start
[14:31] <joalif> o/
[14:31] <didrocks> hey joalif!
[14:32] <cpaelzer> #startmeeting Weekly Main Inclusion Requests status
[14:32] <meetingology> Meeting started at 14:32:41 UTC.  The chair is cpaelzer.  Information about MeetBot at https://wiki.ubuntu.com/meetingology
[14:32] <meetingology> Available commands: action, commands, idea, info, link, nick
[14:33] <cpaelzer> Ping for MIR meeting - didrocks joalif slyon sarnold cpaelzer jamespage ( eslerm dviererbe )
[14:33] <cpaelzer> #topic current component mismatches
[14:33] <cpaelzer> Mission: Identify required actions and spread the load among the teams
[14:33] <cpaelzer> #link https://people.canonical.com/~ubuntu-archive/component-mismatches-proposed.svg
[14:33] <cpaelzer> #link https://people.canonical.com/~ubuntu-archive/component-mismatches.svg
[14:33] <dviererbe> wow
[14:33] <sarnold> omg
[14:33] <cpaelzer> wut
[14:34] <didrocks> spamassin is assassinating us :p
[14:34] <cpaelzer> the moment you zoom out and realize the thing at the top is yours
[14:34] <cpaelzer> oh no :-/
[14:34] <cpaelzer> let me pass that to the team
[14:34] <cpaelzer> and then we look what else is in the report
[14:35] <didrocks> hopefully, we don’t care about the recommends and then, no big deal
[14:35] <sarnold> I assume it's on this graph because we do care about recommends
[14:35] <eslerm> is this MIR still valid? https://bugs.launchpad.net/ubuntu/+source/libnet-idn-encode-perl/+bug/1494890
[14:35] -ubottu:#ubuntu-meeting- Launchpad bug 1494890 in libnet-idn-encode-perl (Ubuntu) "[MIR] libnet-idn-encode-perl (b-d of libio-socket-ssl-perl)" [Undecided, Fix Released]
[14:35] <didrocks> sarnold: yeah, I mean, just a question of removing the recommends
[14:35] <sarnold> afterall, we have to teach users about apt install --no-install-recommends all the time :(
[14:35] <sarnold> ahhh
[14:36] <cpaelzer> ok, looking at others
[14:36] <cpaelzer> libww-perl -> libhttp-cookiejar-perl
[14:36] <cpaelzer> ruby-rack
[14:37] <cpaelzer> ruby is a transiton to 3.0 which kanashiro[m] is on top already
[14:37] <cpaelzer> ruby-rack I should say
[14:37] <cpaelzer> which was even a requirement in the pcs MIR last cycle
[14:37] <cpaelzer> so consider that under control
[14:37] <cpaelzer> how about this www-perl?
[14:37] <cpaelzer> slyon isn't here, that sounds like foundations
[14:38] <cpaelzer> let me ping mclemenceau ^^
[14:38] <cpaelzer> mclemenceau: could you have someone look after the component mismatch in mantic-proposed please
[14:38] <sarnold> woah looks like launchpad got a stylesheet refresh
[14:38] <cpaelzer> did it?
[14:38] <cpaelzer> indeed
[14:39] <cpaelzer> libhttp-cookiejar-perl: libhttp-cookiejar-perl
[14:39] <cpaelzer> [Reverse-Depends: libwww-perl (MAIN)]
[14:39] <cpaelzer> mclemenceau: that is the one you could look at
[14:39] <cpaelzer> everything else is known
[14:39] <cpaelzer> no further action
[14:40] <cpaelzer> except me finding someone to unbreak this massive tree behind spamassassin
[14:40] <cpaelzer> #topic New MIRs
[14:40] <cpaelzer> Mission: ensure to assign all incoming reviews for fast processing
[14:40] <cpaelzer> #link https://bugs.launchpad.net/ubuntu/?field.searchtext=&orderby=-date_last_updated&field.status%3Alist=NEW&field.status%3Alist=CONFIRMED&assignee_option=none&field.assignee=&field.subscriber=ubuntu-mir
[14:40] <cpaelzer> 4 in the queue
[14:40] <dviererbe> There is also https://bugs.launchpad.net/ubuntu/+source/boot-managed-by-snapd/+bug/2023366
[14:40] -ubottu:#ubuntu-meeting- Launchpad bug 2023366 in boot-managed-by-snapd (Ubuntu) "[MIR] boot-managed-by-snapd" [Undecided, New]
[14:40] <cpaelzer> all of them we have seen before
[14:40] <cpaelzer> dviererbe: that is subscribed to the wrong team
[14:40] <didrocks> yeah, some for quite some time as I was the only available MIR reviewer around and can only take 2 by pulse
[14:41] <cpaelzer> today myself and joalif can take a few if possible
[14:41] <didrocks> so, for next pulse, I can take 2 of them (I guess cairo/pango in the order of deps, apart if someone else can parallelize those)
[14:41] <joalif> yup
[14:41] <cpaelzer> and it is fair to limit the number per pulse or whatever cycle you plan for
[14:41] <seb128> technically those are new version of packages already in main but I guess you want to review them again?
[14:42] <cpaelzer> dviererbe: we are the "MIR approval team" not the "Mir development team"
[14:42] <cpaelzer> dviererbe: I fixed the subscription
[14:42] <dviererbe> thanks
[14:42] <dviererbe> weirdly that was the only team that popped up when I searched for mir
[14:42] <cpaelzer> I'd take boot-managed-by-snap
[14:42] <cpaelzer> as I'm curious by the name
[14:43] <cpaelzer> didrocks: is "next pulse" today or next week or even later?
[14:43] <dviererbe> its mostly just a transitional package
[14:43] <didrocks> cpaelzer: next week
[14:43] <cpaelzer> ok
[14:43] <cpaelzer> joalif: pick one of your choice please
[14:43] <cpaelzer> in case one seems nicer than the other to you
[14:43] <joalif> i can take whatever, let's say the first one
[14:44] <cpaelzer> it is important to consider the comment of seb128
[14:44] <cpaelzer> usually if this is just a foo1 to foo2
[14:44] <cpaelzer> it is a fast path
[14:44] <cpaelzer> and not a full review
[14:44] <sarnold> \o/
[14:44] <cpaelzer> we do sanity checks, ensuer the old reviews didn't say "just this time" or such
[14:44] <cpaelzer> and then approve
[14:44] <cpaelzer> joalif: ok you take pangomm2.48 then
[14:45] <joalif> yes
[14:45] <cpaelzer> joalif: if your check on this confirms that it is "the same as we have, just versioned source and all is fine"
[14:45] <cpaelzer> then we can next week assign the rest assuming they are similar fast paths
[14:45] <cpaelzer> does that work for everyone?
[14:45] <didrocks> sounds good to me
[14:45] <joalif> ok
[14:46] <cpaelzer> ok, let us go on then
[14:46] <cpaelzer> #topic Incomplete bugs / questions
[14:46] <cpaelzer> Mission: Identify required actions and spread the load among the teams
[14:46] <cpaelzer> #link https://bugs.launchpad.net/ubuntu/?field.searchtext=&orderby=-date_last_updated&field.status%3Alist=INCOMPLETE_WITH_RESPONSE&field.status%3Alist=INCOMPLETE_WITHOUT_RESPONSE&field.subscriber=ubuntu-mir
[14:46] <sarnold> man that's a lot of incompletes
[14:47] <cpaelzer> not that many recent though
[14:47] <cpaelzer> We haven't closed incompletes for a while
[14:48] <cpaelzer> I think we had some number of days to mark them invalid
[14:48] <sarnold> yeah, we tend to focus on the happy end of the list (for good reasons :) .. but some of these oolldd things make me sad, heh
[14:48] <cpaelzer> let me close all pre 2023
[14:48] <cpaelzer> I think they are incomplete and got no update for so long
[14:48] <cpaelzer> it is correct for expectation management
[14:48] <cpaelzer> to call them incomplete
[14:49] <cpaelzer> WDYT?
[14:49] <sarnold> yeah, it's probably fine to just blanket set them all invalid. it might be a nice reminder to the folks who might sitll be around
[14:49] <didrocks> yeah, sounds like the correct approach to me
[14:50] <cpaelzer> give me a minute
[14:51] <sarnold> heh, argyll, updated a few months ago, opened in 2011
[14:52] <eslerm> I think conditinal ACK requirements like autopkgtests should be met before promotion so that we don't get into this state, but that can be specified by MIR/Security reivews going forward
[14:54] <cpaelzer> dine
[14:54] <sarnold> thanks
[14:54] <sarnold> probably some of these are changing business needs
[14:54] <sarnold> others might be simply overlooked TODO items that were never fulfilled
[14:54] <cpaelzer> eslerm: yes, conditional ack requirements are meant to be met
[14:54] <cpaelzer> ack on the chance for overlook
[14:54] <cpaelzer> that was the reason we started to number them
[14:54] <cpaelzer> it made it easier to track them
[14:55] <cpaelzer> I need to continue in the matter of time
[14:55] <cpaelzer> #topic Process/Documentation improvements
[14:55] <cpaelzer> Mission: Review pending process/documentation pull-requests or issues
[14:55] <cpaelzer> #link https://github.com/canonical/ubuntu-mir/pulls
[14:55] <cpaelzer> #link https://github.com/canonical/ubuntu-mir/issues
[14:55] <cpaelzer> I have today reviewed and merged a few
[14:56] <cpaelzer> there is effort for me and dviererbe before the remaining PRs are re-reviewed here
[14:56] <cpaelzer> on the issues
[14:56] <cpaelzer> one is a discussion on the same topic as the re-review PR
[14:56] <cpaelzer> and let me - for now - just say yes, we do not speak about resourcing yet
[14:56] <cpaelzer> but we need to have in place how we think it works before I combine myself and other directors to be the meta-VP and make a decision
[14:57] <cpaelzer> sarnold: are you ok to go into https://github.com/canonical/ubuntu-mir/issues/24 when there is more time left?
[14:57] -ubottu:#ubuntu-meeting- Issue 24 in canonical/ubuntu-mir "More team members" [Open]
[14:57] <sarnold> cpaelzer: yes
[14:57] <cpaelzer> thanks
[14:57] <cpaelzer> #topic MIR related Security Review Queue
[14:57] <cpaelzer> Mission: Check on progress, do deadlines seem doable?
[14:57] <cpaelzer> Some clients can only work with one, some with the other escaping - the URLs point to the same place.
[14:57] <cpaelzer> #link https://bugs.launchpad.net/~ubuntu-security/+bugs?field.searchtext=%5BMIR%5D&assignee_option=choose&field.assignee=ubuntu-security&field.bug_reporter=&field.bug_commenter=&field.subscriber=ubuntu-mir
[14:57] <cpaelzer> #link https://bugs.launchpad.net/~ubuntu-security/+bugs?field.searchtext=[MIR]&assignee_option=choose&field.assignee=ubuntu-security&field.bug_reporter=&field.bug_commenter=&field.subscriber=ubuntu-mir
[14:57] <cpaelzer> Internal link
[14:57] <cpaelzer> - ensure your teams items are prioritized among each other as you'd expect
[14:57] <cpaelzer> - ensure community requests do not get stomped by teams calling for favors too much
[14:57] <cpaelzer> #link https://warthogs.atlassian.net/jira/software/c/projects/SEC/boards/594
[14:57] <cpaelzer> nothing too surprising here
[14:58] <sarnold> we've got MIRs assigned around, so far I think there's happy thoughts
[14:58] <cpaelzer> indeed
[14:58] <cpaelzer> LGTM
[14:58] <cpaelzer> #topic Any other business?
[14:58] <seb128> o/
[14:58] <cpaelzer> the PRs and issues nowadays cover most of the usual AOB topics
[14:58] <cpaelzer> seb128: have you been waiting for this and brought something new?
[14:59] <cpaelzer> or just seen the highlight that happened a while ago?
[14:59] <seb128> no, I've topics
[14:59] <seb128> first is https://bugs.launchpad.net/ubuntu/+source/webp-pixbuf-loader/+bug/1979121 ... what's the status?
[14:59] -ubottu:#ubuntu-meeting- Launchpad bug 1979121 in webp-pixbuf-loader (Ubuntu Jammy) "[MIR] webp-pixbuf-loader" [Undecided, New]
[14:59] <seb128> it is assigned to you since decembre but didn't get any activity so I wonder if it got forgotten somehow?
[14:59] <cpaelzer> this is a classic fallen therough the cracks
[14:59] <cpaelzer> sorry
[14:59] <cpaelzer> I'll look at it
[15:00] <seb128> thanks
[15:00] <cpaelzer> you said topicS
[15:00] <cpaelzer> next?
[15:00] <seb128> the other topic is that I stated a discussion about symbols for c++ libraries on ubuntu-devel@
[15:00] <seb128> unsure if you guys follow the list of if I should cross reference to github?
[15:00] <seb128> started*
[15:01] <eslerm> link please
[15:01] <sarnold> https://lists.ubuntu.com/archives/ubuntu-devel/2023-June/date.html
[15:01] <eslerm> thanks
[15:01] <seb128> eslerm, https://lists.ubuntu.com/archives/ubuntu-devel/2023-June/042600.html
[15:02] <sarnold> I keep hearing that the kde symbols handling is really nice stuff; I don't understand why it's not the default for all our packages
[15:02] <seb128> if you didn't read it yet it's probably better to discuss it another time after people had time to read
[15:02] <sarnold> perhaps that's a better question on the list, though :)
[15:03] <seb128> that was mentioned, still it doesn't solve most of the issues raised
[15:03] <seb128> like the difference between architectures and how tedious the process is
[15:03] <sarnold> it sounds almost as bad as debian/copyright
[15:04] <sarnold> I'll throw some questions on the list, I don't know nearly enough about what these files provide for us
[15:05] <sarnold> hopefully that'll keep the conversation moving :) (or cause everyone to roll their eyes at me, either way)
[15:05] <cpaelzer> FYI - I'm double booked now, less focus :-/
[15:05] <didrocks> (I guess the biggest blocker is the multi-arch aspect with different symbols)
[15:06] <seb128> that's not a topic that needs to be discussed/resolved here or now, I just wanted to check if you follow devel or if I should start the same discussion as a github ticket or something
[15:06] <sarnold> https://github.com/canonical/ubuntu-mir/issues/26  :D
[15:06] -ubottu:#ubuntu-meeting- Issue 26 in canonical/ubuntu-mir "Decide if we get enough value from symbols tracking to keep doing it" [Open]
[15:07] <seb128> sarnold, thanks!
[15:07] <sarnold> seb128: and thank you :D
[15:07] <cpaelzer> which means we will revisit it every week
[15:07] <seb128> sarnold, update the title to mention c++
[15:07] <cpaelzer> until we find qorum and enough time to tihnk deep enough about it
[15:07] <seb128> we don't have those issues for plain C
[15:07] <cpaelzer> C symbols are worth for sure
[15:07] <sarnold> ack, done
[15:07] <cpaelzer> C++ symbols would be worth if only they would work
[15:07] <seb128> thx
[15:07] <cpaelzer> thank
[15:07] <cpaelzer> s
[15:08] <seb128> and that was it from me for today :p
[15:08] <sarnold> pfew :D
[15:08] <cpaelzer> great
[15:08] <cpaelzer> we are over time
[15:08] <cpaelzer> let me close it here
[15:08] <cpaelzer> and we all handle more next week
[15:08] <cpaelzer> thank you!
[15:08] <cpaelzer> #endmeeting
[15:08] <meetingology> Meeting ended at 15:08:36 UTC.  Minutes at https://ubottu.com/meetingology/logs/ubuntu-meeting/2023/ubuntu-meeting.2023-06-13-14.32.moin.txt
[15:08] <didrocks> thanks!
[15:08] <eslerm> bye all o/
[15:08] <joalif> thanks cpaelzer, all :)
[15:08] <sarnold> thanks cpaelzer, all :)
[15:08] <dviererbe> thank you, all!
[15:23] <mclemenceau> Ack cpaelzer
[15:24] <cpaelzer> thanks mclemenceau
[18:59] <amurray> o/
[18:59] <seb128> hey! :)
[19:00] <rbasak> o/
[19:00] <sil2100> o/
[19:01]  * vorlon waves
[19:01] <vorlon> looks like I'm chairing today
[19:01] <vorlon> #startmeeting
[19:01] <meetingology> Meeting started at 19:01:31 UTC.  The chair is vorlon.  Information about MeetBot at https://wiki.ubuntu.com/meetingology
[19:01] <meetingology> Available commands: action, commands, idea, info, link, nick
[19:01] <vorlon> #topic Apologies
[19:02] <vorlon> looks like maybe we're all here?
[19:02] <vorlon> apparently :)
[19:02] <vorlon> #topic Action review
[19:02] <vorlon> ACTION: amurray to follow up with backporters team on Mattia's draft charter proposal
[19:03] <vorlon> is this done?  is there anything further we need to do?
[19:03] <amurray> backporters discussed and approved this in their last meeting - https://lists.ubuntu.com/archives/technical-board/2023-June/002740.html - I think they just want a formal ack from us
[19:03] <rbasak> We should have somewhere to document these
[19:03] <rbasak> As we expect other teams to get some documentation too
[19:04] <rbasak> I can take an action I guess, unless someone else wants to volunteer?
[19:04] <vorlon> happy to let you have it
[19:04] <amurray> thanks rbasak :)
[19:04] <vorlon> do you want this under https://wiki.ubuntu.com/TechnicalBoard/ ? somewhere else?
[19:04] <seb128> thanks rbasak!
[19:05] <rbasak> I was going to put it there to start with
[19:05] <amurray> sounds like a good place to me
[19:06] <vorlon> #action rbasak to get agreed backporter charter https://lists.ubuntu.com/archives/technical-board/2023-June/002740.html documented under https://wiki.ubuntu.com/TechnicalBoard/
[19:06] <meetingology> ACTION: rbasak to get agreed backporter charter https://lists.ubuntu.com/archives/technical-board/2023-June/002740.html documented under https://wiki.ubuntu.com/TechnicalBoard/
[19:06] <vorlon> rbasak: thanks
[19:06] <vorlon> ACTION: seb128 to help draft an exception to the "must build on all architectures" requirement for snaps
[19:06] <vorlon> seb128: any news?
[19:06] <seb128> yes
[19:06] <seb128> we updated the document with rbasak
[19:06] <rbasak> I think that action item is done.
[19:06] <seb128> so that can be considered as done
[19:06] <rbasak> The snap appendix needs a general cleanup but I'd like to push on with the main body first.
[19:08] <vorlon> #done seb128 to help draft an exception to the "must build on all architectures" requirement for snaps
[19:08] <vorlon> ACTION: seb128/amurray/sil200 to help drafting the snap-store Ubuntu-specific tracks usage
[19:08] <vorlon> how about this?
[19:08] <rbasak> It sounded like there were still some loose ends on this?
[19:09] <amurray> yeah - I added a suggestion for this - there's some feedback from seb128 and kenvandine that I need to look over still
[19:10] <vorlon> carry-over, then?
[19:10] <sil2100> Yes please, I'm looking through it right now
[19:10] <vorlon> #action seb128/amurray/sil200 to help drafting the snap-store Ubuntu-specific tracks usage
[19:10] <meetingology> ACTION: seb128/amurray/sil200 to help drafting the snap-store Ubuntu-specific tracks usage
[19:10] <vorlon> ACTION: sil2100 to start a draft summarizing the OEM archive portion of the meeting which x-nox and TB will review, edit, and ratify before we move on to figuring out the next step
[19:11] <vorlon> sil2100: ?
[19:11] <sil2100> vorlon: still didn't have time to finalize the docs, only the 'start' of the draft here https://wiki.ubuntu.com/OEMArchive
[19:11] <sil2100> I know what to write, but still require some time. So sadly another carry over
[19:11] <vorlon> #action sil2100 to start a draft summarizing the OEM archive portion of the meeting which x-nox and TB will review, edit, and ratify before we move on to figuring out the next step
[19:11] <meetingology> ACTION: sil2100 to start a draft summarizing the OEM archive portion of the meeting which x-nox and TB will review, edit, and ratify before we move on to figuring out the next step
[19:11] <vorlon> ACTION: rbasak to draft a proposal of the DMB-proposed inactivity expiration policy for TB ratification
[19:12] <vorlon> rbasak: ?
[19:13] <rbasak> Carry over please, sorry
[19:13] <vorlon> #action rbasak to draft a proposal of the DMB-proposed inactivity expiration policy for TB ratification
[19:13] <meetingology> ACTION: rbasak to draft a proposal of the DMB-proposed inactivity expiration policy for TB ratification
[19:13] <vorlon> ACTION: the TB members have until the next meeting to review the third party repository requirements document and raise concerns
[19:14] <rbasak> I trust that the TB members have done their homework? :)
[19:14] <vorlon> hmm I think I failed to do this fwiw
[19:14] <rbasak> Does the TB have any further questions or comments on the main body of the document - excluding the appendices? Can I take the current text to be the TB's draft position, for wider consultation?
[19:14] <sil2100> I was generally fine with it during my last read through, so you can consider me being +1 on it
[19:15] <vorlon> oh to have git diff <range> for google docs
[19:15] <rbasak> It is still subject to change subject to feedback of course.
[19:15] <rbasak> But I would like to present it as the TB's starting point.
[19:15] <seb128> I reviewed it and I'm fine with moving forward with the main text
[19:16] <seb128> we (as desktop) have concerns about the appendix C - requirement A though
[19:16] <amurray> rbasak from the last meeting when I mentioned testing I thought we were going to add something about that as well... but I am struggling to remember the the specifics
[19:16] <seb128> so I think that is going to need more discussion, but as you said it's an appendix and not what we focus on atm
[19:17] <rbasak> That rings a bell. Maybe I missed an edit.
[19:17] <amurray> https://irclogs.ubuntu.com/2023/05/30/%23ubuntu-meeting.html#t19:33
[19:17] <seb128> maybe my fault for not recording that in the actions, sorry :/
[19:18] <vorlon> in the list of exceptions for specific packages, I think it should list what architectures the package is supposed to be available on.  For Ubuntu desktop installer, it doesn't say *which* other arches we're missing a runtime on; and both amd64 and arm64 are important for desktop flavors.  But this is also all in an appendix
[19:18] <vorlon> otherwise, skimming the recent differences, it looks fine to me
[19:18] <rbasak> amurray: ah yes, sorry. This is related to the process for eg. adding a new snap, right? Not about making changes to an existing one?
[19:19] <amurray> yes, we ended up saying that the package should have a review by some other (MIR-like) team
[19:19] <rbasak> OK. That's also for the snap appendix, right?
[19:19] <amurray> I would prefer it to be in the main document as a proposed requirement
[19:20] <rbasak> OK. Let me take an action to get that in. I think I was supposed to do it last time, like you said.
[19:20] <rbasak> Then I'll check with you out of band.
[19:20] <seb128> in fact the stability point is also requirement A and not only in the appendix...
[19:20] <amurray> ie like an issue/bug tracker, we/I also want it to be reviewed to approve that it is "maintainable" / "testable" etc when updates need to be done
[19:20] <rbasak> If amurray is happy with that edit, then I'll go ahead and open wider discussion. Does that sound OK?
[19:21] <vorlon> do we want to take 'Proposed' out of the 'Proposed requirement'?
[19:21] <rbasak> Sure, if you like. The whole thing is proposed :)
[19:21] <vorlon> right that's what I was thinking
[19:22] <amurray> re stability - having a requirement that something remain stable is not the same as saying "it needs to be testable" so that if/when someone has to do an update we can have some confidence that it is not going to break on delivery to users
[19:22] <vorlon> made that edit
[19:22] <rbasak> seb128: it is requirement A in the main body, but I think it should remain there as the baseline, with an exception either in general or specifically for snaps under some more specific criteria. Doesn't matter which since snaps are the only approved "third party type" at the moment.
[19:23] <rbasak> amurray: you're talking about QA?
[19:23] <seb128> ack
[19:23] <amurray> yep
[19:24] <rbasak> I'm not sure we're in a position to be able to dictate anything about QA really, because we already delegate that to snap publishers entirely. What sort of assurance do you think we could define?
[19:24] <rbasak> This might fit under:
[19:24] <rbasak> Requirement C: the package maintainer agrees to maintain the package for the lifetime of the Ubuntu release.
[19:25] <rbasak> What that means exactly, including QA, is down to them I think.
[19:25] <amurray> my personal preference would be that for each approved third-party package, there should be a documented test plan that can be exercised by other Ubuntu members if / when they need to make an update to the package in question
[19:25] <rbasak> Or, maybe we could require as part of snap-MIR for some QA plan to be written down and committed to by the snap maintainer?
[19:26] <rbasak> OK. I think that would be great to have.
[19:26] <rbasak> But I'm concerned it might be too much friction.
[19:26] <rbasak> I don't feel strongly about whether or not the requirement should be in there initially though.
[19:27] <vorlon> having firefox document a test plan for their binary releases would not mean it's particularly practical for Ubuntu to reproduce it
[19:27] <sil2100> hm, it's an interesting idea, but seeing that we don't require such things for packages we have in the archive, seems a bit 'much'
[19:27] <rbasak> IMHO MIR process goes a bit further actually by requiring automated testing, which is de-facto a test plan.
[19:28] <seb128> MIR also give the alternative option of a manual testplan
[19:28] <vorlon> it does? eew
[19:28] <vorlon> :)
[19:29] <seb128> (most desktop applications don't have automated testing because we don't have a good framework to automate UI testing in our infra)
[19:29] <amurray> I don't think this is too much to ask - we want everyone to have confidence in whatever third-party packages they are consuming from us
[19:30] <amurray> my real concern here is that someday the security team will have to patch one of these snaps and we won't have a good way to test the thing at the end of that before releasing it
[19:30] <seb128> it's a bit unfair to require more there than what we require today for things we ship by default though no?
[19:30] <rbasak> I wrote this down here so we don't forget it's outstanding: https://docs.google.com/document/d/1apUKR4gtOrfPGCWmtoebaQUhoy-fG8Cyo3VKJyhnpD0/edit#heading=h.v2cstw9iikqj
[19:31] <amurray> thanks rbasak
[19:31] <sil2100> We also need to remember that other flavors might want to pre-install their own snaps too, and they can build out of universe - so even if in main we do have some requirements, we need to make sure that we don't go instantly over-board. But I do agree the more emphasis we can have on quality, the better
[19:32] <sil2100> Anyway, it's certainly an idea worth thinking about
[19:32] <rbasak> OK I think this needs some further discussion. Let me document the ideas there at least, before we try to establish consensus
[19:33] <rbasak> So leave that with me for now.
[19:33] <vorlon> does that need resolved before we push this out for wider discussion?
[19:33] <rbasak> I was about to ask that.
[19:33] <rbasak> Can we do both simultaneously?
[19:33] <rbasak> It's fine for there to be some documented loose ends IMHO
[19:33] <vorlon> #action rbasak to follow up on finding consensus on question of test plans for third party apps
[19:33] <meetingology> ACTION: rbasak to follow up on finding consensus on question of test plans for third party apps
[19:33] <rbasak> I need to restructure the docs a bit to make the status clearer
[19:34] <vorlon> is that also an action?
[19:34] <rbasak> But once done I think we can open wider discussion if others are OK with it.
[19:34] <sil2100> +1
[19:34] <rbasak> vorlon: yes, sure
[19:34] <amurray> +1
[19:34] <vorlon> #action rbasak to restructure the third-party repo doc to make the status clearer
[19:34] <meetingology> ACTION: rbasak to restructure the third-party repo doc to make the status clearer
[19:34] <vorlon> are those the actions for now?
[19:35] <rbasak> And maybe another for me to open wider discussion?
[19:35] <rbasak> Now that you wrote that I'm not sure what the others +1'd :)
[19:35] <vorlon> #action rbasak to open wider discussion on third-party repo policy
[19:35] <meetingology> ACTION: rbasak to open wider discussion on third-party repo policy
[19:35] <vorlon> :)
[19:35] <rbasak> Everyone happy with that plan?
[19:35] <seb128> +1
[19:35] <rbasak> That's a bad question.
[19:35] <rbasak> Any objections to that plan? :)
[19:35] <amurray> yes, thanks :)
[19:35] <amurray> sorry I mean, yes I am happy, no objection from me
[19:35] <rbasak> :-P
[19:35] <vorlon> excellent, moving on
[19:36] <vorlon> #done seb128 to resend the 'core teams governance' email to the public techboard list
[19:36] <rbasak> I'll reply shortly
[19:36] <vorlon> per previous discussion, it's now on the rest of us to replay our responses
[19:36] <vorlon> I don't know how soon I'll get to that on my part, so maybe an action there
[19:36] <seb128> I just did today, sorry for the delay but I was waiting on getting ack from people I'm quoting in the email (since there was some extract from private emails)
[19:37] <vorlon> #action rbasak, vorlon, amurray to replay their responses to Key Ubuntu teams discussion
[19:37] <meetingology> ACTION: rbasak, vorlon, amurray to replay their responses to Key Ubuntu teams discussion
[19:37] <vorlon> #topic Scan the mailing list archive for anything we missed (standing item)
[19:37] <vorlon> #link https://lists.ubuntu.com/archives/technical-board/2023-June/thread.html
[19:37] <vorlon> nothing there which we haven't already addressed
[19:38] <vorlon> #topic Check up on community bugs and techboard bugs
[19:38] <vorlon> #link https://bugs.launchpad.net/ubuntu-community/+bugs?field.assignee=techboard
[19:38] <vorlon> clear
[19:38] <vorlon> #link https://bugs.launchpad.net/techboard
[19:38] <vorlon> two bugs that are also both captured in our actions
[19:38] <vorlon> #topic Select a chair for the next meeting (next from https://launchpad.net/~techboard/+members)
[19:39] <vorlon> I believe the rotation is chair: sil2100, backup: amurray
[19:39] <sil2100> ACK o/
[19:40] <vorlon> #agreed next meeting chair: sil2100, backup: amurray
[19:40] <meetingology> AGREED: next meeting chair: sil2100, backup: amurray
[19:40] <vorlon> #topic AOB
[19:40] <vorlon> anything else for today?
[19:40] <amurray> nothing from me
[19:40] <rbasak> Nothing from me.
[19:41] <rbasak> Thank you for chairing!
[19:41] <rbasak> And thank you everyone for the productive discussion.
[19:41] <vorlon> #endmeeting
[19:41] <meetingology> Meeting ended at 19:41:51 UTC.  Minutes at https://ubottu.com/meetingology/logs/ubuntu-meeting/2023/ubuntu-meeting.2023-06-13-19.01.moin.txt
[19:41] <vorlon> thanks, all!
[19:41] <sil2100> Thanks vorlon! Thanks everyone o/
[19:42] <amurray> thanks vorlon
[19:42] <seb128> thanks!


[02:23] <Derpmeister> Hi. I've got HTTPS working but I'm trying to get the MAAS web UI to work over HTTPS. Any pointers in enabling this?
[02:27] <Derpmeister> Note: the fact that there isn't much documentation on this is somewhat surprising. Lots of Squid docs in enabling this with regards to MAAS but surprisingly little on getting Apache to run with MAAS on HTTPS.
[07:41] <filiplt> Hello. I very need help - total failure to deploy node (hp proliant dl360g9) - curtin fails to create partition: "An error occured handling 'sdg-part2': ProcessExecutionError - Unexpected error while running comman: ['sgdisk', '--new', '2:976896.0:15550463.0', '--typecode=2:8300', '/dev/sdh']
[07:41] <filiplt> WTF? Asked for sdg-part2, and device is sgdisk is /dev/sdh ???
[10:50] <mup> Bug #1680790 opened: [Device discovery - Enable/Disable toggle] The tooltip works as a button to interact with the toggle <ui> <MAAS:New> <https://launchpad.net/bugs/1680790>
[10:50] <mup> Bug #1680795 opened: [Device discovery] Move the tooltipinbetween the label and the toggle <ui> <MAAS:New> <https://launchpad.net/bugs/1680795>
[11:26] <mup> Bug #1680812 opened: [UX Improvement]  Formally design the sticky table header as a pattern <MAAS:New> <https://launchpad.net/bugs/1680812>
[11:38] <mup> Bug #1680812 changed: [UX Improvement]  Formally design the sticky table header as a pattern <MAAS:New> <https://launchpad.net/bugs/1680812>
[11:50] <mup> Bug #1680812 opened: [UX Improvement]  Formally design the sticky table header as a pattern <MAAS:New> <https://launchpad.net/bugs/1680812>
[11:50] <mup> Bug #1680816 opened: [UX Improvement] The navigation bar should be sticky <ui> <MAAS:New> <https://launchpad.net/bugs/1680816>
[12:14] <mup> Bug #1680819 opened: [MAAS 2.2.0 (beta4) - Nodes] The tooltip on the machines tab goes off the screen <ui> <MAAS:New> <https://launchpad.net/bugs/1680819>
[13:47] <mup> Bug #1680856 opened: [MAAS 2.2(beta 4) - Nodes] When I select to view the machines by MAC address, the MAC address is not visible in the table and all the columns are shifted to the left  <ui> <MAAS:New> <https://launchpad.net/bugs/1680856>
[13:50] <akossh> Hello
[13:50] <akossh> I have a problem using MAAS Version 2.2.0~rc1
[13:51] <akossh> I always get timeout at commissioning script 99-maas-02-capture-lldp
[13:52] <akossh> 20 to 25 seconds after completing the previous script, this script gets a timeout
[13:53] <mup> Bug #1680856 changed: [MAAS 2.2(beta 4) - Nodes] When I select to view the machines by MAC address, the MAC address is not visible in the table and all the columns are shifted to the left  <ui> <MAAS:New> <https://launchpad.net/bugs/1680856>
[13:54] <akossh> However the script waits until a file created by the LLDPD gets 60 seconds old,
[13:54] <akossh> which does never happen within 20 seconds
[13:57] <mup> Bug #1680859 opened: [2.2, UX] The tables should maintain the sorting information <MAAS:Incomplete> <https://launchpad.net/bugs/1680859>
[14:05] <pmatulis> akossh, fwiw, it works here
[14:06] <akossh> I have no idea why I'm getting a timeout
[14:07] <akossh> From the start of commissioning it takes less then 5 minutes, and I get a timeout
[14:08] <akossh> from the start of that script, it's like 20 to 25 sec
[14:08] <akossh> I do not know if it's a global timeout, or "per script" timeout
[14:09] <akossh> In older versions, there was a script called 99-maas-01-wait-for-lldpd which was run before the 99-maas-02-capture-lldp
[14:10] <akossh> But now that script is missing, and tha later one times out
[14:10] <pmatulis> akossh, checked logs?
[14:10] <akossh> I chacked the commissioning tab of the node
[14:11] <akossh> Wher do I find the logs to check?
[14:12] <akossh> https://pastebin.com/kcEAAs88
[14:12] <akossh> This is what I see
[14:14] <pmatulis> i would start with /var/log/maas/rsyslog/<node>/<date>/messages
[14:15] <mup> Bug #1680859 changed: [2.2, UX] The tables should maintain the sorting information <MAAS:Incomplete> <https://launchpad.net/bugs/1680859>
[14:15] <mup> Bug #1680856 opened: [MAAS 2.2(beta 4) - Nodes] When I select to view the machines by MAC address, the MAC address is not visible in the table and all the columns are shifted to the left  <ui> <MAAS:New> <https://launchpad.net/bugs/1680856>
[14:15] <pmatulis> akossh, (on the region API server)
[14:17] <akossh> This kind of messages dominate the log: Apr  7 13:51:08 micro18 ureadahead[574]: ureadahead:39/cmdline: Ignored relative path
[14:18] <mup> Bug #1680856 changed: [MAAS 2.2(beta 4) - Nodes] When I select to view the machines by MAC address, the MAC address is not visible in the table and all the columns are shifted to the left  <ui> <MAAS:New> <https://launchpad.net/bugs/1680856>
[14:18] <mup> Bug #1680859 opened: [2.2, UX] The tables should maintain the sorting information <MAAS:Incomplete> <https://launchpad.net/bugs/1680859>
[14:32] <akossh> How can I downgrade to an older, working version?
[14:33] <akossh> Is it possible, or the update changed the DB?
[14:34] <pmatulis> downgrading maas isn't supported
[14:35] <akossh> :(
[14:36] <pmatulis> akossh, what kind of machine are you using for the failing node?
[14:37] <akossh> A supermicro blade
[14:38] <akossh> x86_64
[14:38] <akossh> And I think, the only problem is that the timeout is too short
[14:41] <akossh> The other nodes were commissioned before updating maas, it worked good
[14:42] <pmatulis> interesting
[14:43] <akossh> the HW is the same
[14:43] <pmatulis> you're sure the same h/w worked in the previous version?
[14:44] <pmatulis> to be clear, what 2 versions are we talking about?
[14:44] <akossh> it was last year november
[14:44] <akossh> I think 2.0.0 beta something
[14:46] <pmatulis> possible to install a second environment with the earlier version and see if it works?
[14:46] <akossh> Now measured more precisely, from start to getting a timeout, takes 3 minutes 6 seconds
[14:47] <akossh> While I read about 20 minute commissioning timeout on google
[14:47] <akossh> pmatulis: no chance for a second environment right now
[14:55] <akossh> If I do not let the machine boot, it does not get a timeout after 3 minutes
[14:56] <akossh> So it's not a timeout counted from the start of commissioning
[14:59] <akossh> Interesting, when I delayed the boot, the script had only 1 second to run before getting timeout
[15:00] <pmatulis> akossh, consider filing a bug
[15:09] <akossh> pmatulis: i will consider it, thank you for the help so far
[15:09] <mup> Bug #1680876 opened: [2.2, UI] Cannot update storage tags over the UI <MAAS:New> <https://launchpad.net/bugs/1680876>
[15:15] <pmatulis> welcome
[15:16] <vogelc> pmatulis: Hey, hows it going. I have some questions on the DHCP Relay.
[15:17] <vogelc> pmatulis: When we configure it for an untagged vlan, the host is discovered and during commissioning it set the interfaces to unconfigured and the commissioning just stops.  is that expected?
[15:18] <vogelc> pmatulis: when the interfaces get set to unconfigured it pulls an ip from the wrong subnet.
[15:20] <pmatulis> vogelc, otp, be back soon
[15:39] <mup> Bug #1680886 opened: [2.2] After aborting a deployment, the machine cannot be deployed via the CLI <MAAS:New> <https://launchpad.net/bugs/1680886>
[15:42] <mup> Bug #1680886 changed: [2.2] After aborting a deployment, the machine cannot be deployed via the CLI <MAAS:New> <https://launchpad.net/bugs/1680886>
[15:45] <mup> Bug #1680886 opened: [2.2] After aborting a deployment, the machine cannot be deployed via the CLI <MAAS:New> <https://launchpad.net/bugs/1680886>
[15:45] <pmatulis> vogelc, a node cannot commission if it's not connected to a network. did you do that?
[15:50] <vogelc> pmatulis:  Let me take some screen shots and post it for you.  that might help.
[17:11] <Guest5285> hi
[17:12] <Guest5285> does anyone know how to import custom kernel and initrd in MAAS 2.1.x?
[17:26] <kiko> Guest5285, AIUI that's only doable through providing your own simplestreams channel
[17:48] <mup> Bug #1680917 opened: Machine fails to boot if MAAS server is not available <MAAS:Incomplete> <https://launchpad.net/bugs/1680917>
[17:51] <Guest5285> kiko: if I provision my own simplestreams then also I couldn't find any simple documentation steps. Do you know of anything?
[17:56] <Guest5285> Any quick start on how these images can be pushed via simplestreams?
[19:21] <mup> Bug #1680939 opened: [2.2rc1] When rack controller is down, machines power status shows 'green' <MAAS:New> <https://launchpad.net/bugs/1680939>
[20:21] <cmd_pancakes> so i have an issue with a server that is connected to an 84 disk array...when the array is connected, the host cannot mount the iscsi mount from the rack controller, eventually fails to a busybox shell and enlistment fails...when i turn off the array, everything works fine
[21:06] <roaksoax> cmd_pancakes: maybe duplicate iscsi initiator names ?
[21:08] <cmd_pancakes> roaksoax: could be! im setting up the hardware to test a known working config and bad config...i'll keep an eye on your suggestion
[21:10] <roaksoax> cmd_pancakes: maybe the hardware has a duplicate iscsi initiator same as maas' tgt
[21:11] <cmd_pancakes> i'm not super familiar with iscsi, are there iscsi commands in the enlistment image that i could test it out? i assume i could only really dig in once it fails to the busy box shell
[21:12] <cmd_pancakes> haha i could also just google for that :P
[22:42] <mup> Bug #1680979 opened: [2.2] Edited notifications reappear to users who have dismissed them and cannot be dismissed <MAAS:Triaged by allenap> <https://launchpad.net/bugs/1680979>