[14:40] <mup> Bug #1773384 opened: [2.5, 2.4, UI] Power status wraps to second line <MAAS:Triaged by deadlight> <MAAS 2.4:Triaged> <https://launchpad.net/bugs/1773384>
[14:40] <mup> Bug #1773385 opened: [2.5, 2.4, UI] Error as a notification in pod refresh <MAAS:Triaged by deadlight> <MAAS 2.4:Triaged> <https://launchpad.net/bugs/1773385>
[14:40] <mup> Bug #1773387 opened: [2.5, 2.4, UI] Pod 'Configuration' formatting for 'Type' doesn't match  <MAAS:Triaged by deadlight> <MAAS 2.4:Triaged> <https://launchpad.net/bugs/1773387>
[15:49] <mup> Bug #1773405 opened: MAAS conflates untagged vlans with vid 0 <MAAS:New> <https://launchpad.net/bugs/1773405>
[16:13] <enrico_> hello, I have a problem with my maas-dhcp
[16:13] <enrico_> it does not responding to dhcp requests
[16:14] <enrico_> I see the request getting till my maas-rack/region-controller
[16:14] <enrico_> but no offers
[16:14] <enrico_> I reserved a dynamic range on the subnet
[16:14] <enrico_> what could I explore?
[17:49] <mup> Bug #1773422 opened: Discover fabric from LLDP when available <foundations-engine> <MAAS:New> <https://launchpad.net/bugs/1773422>
[19:23] <mup> Bug #1773437 opened: [2.5, UI] Adding a second resource pool after adding a previous one doesn't clear form <MAAS:Triaged by bjornt> <https://launchpad.net/bugs/1773437>
[19:53] <mup> Bug #1773442 opened: [2.5] MAAS should use python3-libvirt instead of virsh <MAAS:Triaged> <https://launchpad.net/bugs/1773442>
[21:14] <mup> Bug #1773454 opened: [2.5, UI] Assigning multiple machines to a newly created pool only does for the first machine <resource-pools> <MAAS:Triaged by bjornt> <https://launchpad.net/bugs/1773454>
[21:17] <mup> Bug #1773455 opened: [2.5, UI] Action menu for 'Set resource pools' has too much whitespace <resource-pools> <MAAS:Triaged> <https://launchpad.net/bugs/1773455>
[21:17] <mup> Bug #1773456 opened: [2.5, UI] Resource pool listing page should link to the machine listing with a filter <resource-pools> <MAAS:Triaged> <https://launchpad.net/bugs/1773456>


[06:31] <tarzeau> Eickmeyer: oh great, thanks! i'd definitely have suggestions for the ubuntustudio/fonts part
[06:32] <Eickmeyer> tarzeau: Awesome! Can you throw it into an email? That'd help.
[06:32] <tarzeau> replace fonts-beteckna with either fonts-inter or fonts-league-spartan, ttf-aenigma is fonts-aenigma now. drop ... sure where to?
[06:32] <Eickmeyer> Are you subscribed to the ML?
[06:32] <tarzeau> nope, but can subscribe (or maybe i am, don't know)
[06:33] <Eickmeyer> https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel
[06:33] <tarzeau> fonts-fandoow (sure is a typo) should be fonts-fanwood ;)
[06:33] <Eickmeyer> Then send the email to<EMAIL_ADDRESS>[06:33] <Eickmeyer> Subscribing keeps you from getting auto-moderated.
[15:53] <Eickmeyer> tarzeau: Thanks for the email! I plan on going through that fairly soon, but jammy's dev cycle hasn't opened yet.
[15:54] <tarzeau> yep, i also have some more fonts in the new queue stuck as well. it'd be great to discuss replacements of fonts, and adding new ones.
[16:53] <Eickmeyer> Jammy's archive just opened, so I'll likely get things sorted in the next day or two.
[16:58] <OvenWerks> Eickmeyer: do you know if there are large changes in plasma expected for 22.04?
[16:59] <Eickmeyer> OvenWerks: Not sure, but RikMills would have more information. I do know that 5.24 is expected to release during the cycle.
[17:00] <Eickmeyer> I'm considering some changes in the theming. Having a kvantum-based theme is hard to work with.
[17:00] <Eickmeyer> Hard in that it's hard to utilize some of the newer features for theming properly.
[17:01] <RikMills> https://mail.kde.org/pipermail/plasma-devel/2021-October/121106.html
[17:01] <RikMills> from the 5.24 meeting today
[17:02] <Eickmeyer> RikMills: Awesome. As I read that, no huge changes for 5.24.
[17:02] <Eickmeyer> Unless my assessment is off.
[17:04] <RikMills> yeah, I think any big changes will be coordinated with Qt6/KF6 as the did in the 4 -> 5 transition
[17:06] <OvenWerks> theming I am not worried about as I tend to setup a CDE based theme for ease of use.
[17:06] <OvenWerks> Eickmeyer: I am thinking to switch my daily drive to 22.04 soonish to make dev work easier.
[17:08] <Eickmeyer> OvenWerks: Yeah, I probably need to do the same for a couple of reasons, one of which is the very reason you are consideirng it.


[02:46] <m4t> is anyone using google-chrome deb on 22.04? can someone please confirm that the window freezes after downloading a file (e.g. save as dialog)
[02:47] <m4t> seeing the same in google-chrome-beta too. there's a known issue affecting marco that is slated to be fixed in 101, this is different though
[02:50] <m4t> iirc this wasn't happening on 20.04, even using fresh-mate ppa :(
[03:00] <m4t> https://askubuntu.com/questions/1402530/running-any-chromium-based-browser-in-ubuntu-22-04-freezes
[03:04] <m4t> actually, it appears fixed in google-chrome-beta (101), phew. wasn't actually using it when i tested it :P
[03:12] <m4t> er weird, no it works with a fresh profile, but not the existing one. anyhow, would appreciate it if someone could test. pretty easy to repro
[12:07] <Watter> Hello everyone. I have a question regarding the behavior of the MATE Desktop. My desire is to disable any automountig facility. I disabled every dconf entry regarding automounting but my PC still mounts my external harddrive. Luckily it is mounted by ntfs-3g, which shows up in htop. htop shows the following realationship: lightdm invokes systemd --user which calls ntfs-3g. How can I prevent systemd user from automounting?
[12:11] <sixwheeledbeast> I have never done this but imagine it's udisks mounting the drives there will be a systemd unit for it.
[12:15] <sixwheeledbeast> `systemctl status udisks2` will tell you if it's running and then you can `stop` it and check if that works, before disabling it.
[12:16] <Watter> Thanks for the reply. I have considered that too. The internet says that udisks2 does not automount but needs a wrapper like udiskie
[12:17] <sixwheeledbeast> is it one drive you want to stop or any?
[12:18] <Watter> Any device. Stopping udisks2 works. But maybe a yet undiscovered service depends on udisks2
[12:19] <sixwheeledbeast> mask it
[12:19] <sixwheeledbeast> if it's masked it should only start if a user enables it manually
[12:27] <sixwheeledbeast> oh sorry I got it backwards. `mask` completely disables it. `disable` only disables auto start. It seems backwards syntax...
[12:32] <Watter> Yeah, I was searching what masks might actually do...
[12:33] <Watter> In /proc/<ID>/cgroup it says 0::/system.slice/udisks2.service
[12:51] <sixwheeledbeast> a mask will point that unit to /dev/null
[14:22] <sixwheeledbeast> So does ambient theme get removed if you upgrade? I get the impression it will replace it with the nearest yaru from a blog post.
[15:27] <m4t> sixwheeledbeast: it gets removed, it does not exist in the new ubuntu-mate-artwork packages
[15:27] <m4t> i just installed the 20.04 pkgs
[15:28] <m4t> someone replied to https://askubuntu.com/questions/1402530/running-any-chromium-based-browser-in-ubuntu-22-04-freezes, apparently the gtk3 file choose steals mouse events which is why chrome is completely unresponsive after downloading a file
[15:28] <sixwheeledbeast> Yer don't like the look of Yaru really.
[15:31]  * m4t trying the chrome flatpak, maybe it doesn't have a busted gtk3 version or whatever is causing it
[15:33] <superkuh> gtkfilechooserwidget.c strikes again!
[15:37] <m4t> i feel somehow like the fix here is weeks off. maybe not
[15:39] <m4t> yeah, flatpak is unaffected by the issue even with my existing profile
[16:01] <m4t> nice now it's even themed (had to copy /usr/share/themes/Ambiant-MATE-Dark to ~/.themes and allow that path + add GTK_THEME=Ambiant-MATE-Dark with 'flatpak override com.google.Chrome')
[16:56] <m4t> https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1970047 there we go. /me gives some spice
[16:56] <m4t> *heat
[20:17] <wildlander> I tried ubuntu mate 22.04 live, without installing, and the Apps Applet  gave some error and failed to load on screen.


[11:51] <persia> Team meeting in 10 minutes.
[11:56] <ogra> bah, persia files evil bugs in my direction
[13:04] <NCommander> lool, I have experience with running archive builds in an emulator for m68k (as well as running qemu/arm for debugging and stuff ...)
[13:04] <lool> NCommander: Spec first
[13:04] <NCommander> yup, just noting
[13:05] <ogra> and take a look at http://beagleboard.org/project/qemu-omap3/ ...
[13:05] <ogra> it worked reliable in my tests
[13:05] <NCommander> I'm there now
[13:05]  * NCommander had googled for ARMv6 QEMU, but didn't find this
[13:05] <lool> Right, that's the one I had in mind, it's recommended for n810
[13:05] <lool> n810 is currently broken in ubuntu
[13:05] <ogra> but needs the rootfs in flash
[13:05] <ogra> which limits a lot in size
[13:06]  * NCommander compiles omap3 QEMU now
[13:06] <ogra> oh ... twl4030 support seems to have been added now
[13:07] <ogra> so MMC support might actually work
[13:07]  * NCommander searches for a usable kernel binary
[13:07] <ogra> that indeed changes a lot
[13:07] <NCommander> ogra, well I do qemu -hda /dev/USBstick
[13:07] <ogra> http://code.google.com/p/qemu-omap3/wiki/UserManual
[13:07] <ogra> that doesnt help if qemu only adresses flash space inside your usb stick ;)
[13:08] <ogra> but MMC emu should overcome the size restrictions
[13:09] <NCommander> I think I'm going to run into the same issue
[13:09] <NCommander> Kernel and initramfs versions mismatch
[13:09] <ogra> ??
[13:10] <ogra> there are kernel and initramfs links on the page i gave you
[13:10] <NCommander> No, that's not the problem
[13:10] <NCommander> mojo's d-i is based around a .22 kernel
[13:10] <lool> NCommander: Just build the disk and fs support in the kernel; it should actually be in current jaunty kernels
[13:10] <lool> Oh for mojo
[13:10] <NCommander> and udev breaks into many pieces when it tries to probe for devices, breaking partman and making it uninstallable
[13:10] <ogra> http://elinux.org/BeagleBoardHandheldsMojo
[13:11] <ogra> Debian Installer QEMU (hasty-armv5el or hasty-armv6el)
[13:11] <ogra> isnt that what you look for ?
[13:11] <NCommander> yeah, but QEMU doesn't support arm6el-vfp ...
[13:11] <ogra> qemu-omap3 should
[13:12] <NCommander> they're using qemu in versalite
[13:12] <NCommander> Oh
[13:12] <ogra> versatile
[13:12] <NCommander> I see
[13:12] <ogra> :)
[13:12] <NCommander> -cpu arm1136
[13:12] <NCommander> O_o;
[13:13] <NCommander> When did QEMU support the cortex-a8
[13:13]  * NCommander sees it on the list of CPUs ...
[13:13] <ogra> since quite a while, though our packaged verysion might not work with that
[13:13] <ogra> i think lool tried
[13:13] <NCommander> I use SVN snapshots
[13:13] <NCommander> lool, remember what I said about doing ARMv6/ARMv7 builds? Forgot about it, it will work just peachy since QEMU has the necessary support.
[13:14] <lool> NCommander: Not sure it's working
[13:14] <NCommander> I'm testing an SVN snapshot
[13:14] <lool> Which is not what we have in the archive
[13:14] <ogra> right
[13:14] <lool> I think you should not be spending time on this
[13:15] <ogra> please test the packaged versions if you want to test
[13:15] <NCommander> Er, I'm just doing this to build an ARMv6 image
[13:15] <ogra> same as for kexec
[13:15] <ogra> if you find bugs in the packaged versions, file them ... improve what we have instead of always taking upstream directly
[13:15] <ogra> that isnt really helpful
[13:16] <ogra> if lool wants to use EC for that we need to have a package that works
[13:16] <ogra> if we want to use kexec for oftboot loading, it needs to work with our package
[13:16] <lool> NCommander: Oh ok, feel free to try out new qemu for your armv6 research of course
[13:16] <lool> NCommander: Would be nice to fix it in Ubuntu too though
[13:17] <ogra> right
[13:17] <NCommander> I'll look into it later, but if I can finish those benchmarks, its a massive CHECK off my todo list
[13:18] <NCommander> and an ARMv6 kernel boots
[13:18]  * NCommander sighs
[13:18] <NCommander> THis is what I get for googling for ARMv7 vs. specific boards
[13:18]  * NCommander feels like an idiot :-/
[13:18] <ogra> (that whole conversation should be in -arm btw)
[13:18] <lool> ogra: Eh right, I thought we were there
[13:51] <NCommander> Celtiore, ping
[13:53] <NCommander> Celtiore, I was pointed to you as someone who's had luck getting Ubuntu working well on jax10, and I was curious if you had any documentation on the process or could give me some help.
[14:45] <Celtiore> hi NCommander
[14:47] <Celtiore> http://public.celtiore.fr/aigo-2.6.24-23.img.torrent
[14:47] <Celtiore> and read ho to activte touchscreen : http://www.midwiki.com/index.php?option=com_fireboard&Itemid=53&func=view&catid=4&id=311&limitstart=12
[14:49] <NCommander> Celtiore, how's this different then the base Hardy images if you don't mind me asking
[14:49] <Celtiore> ?
[14:50] <NCommander> What was changed in the image vs. the stock Hardy MID images?
[14:50] <Celtiore> nothing
[14:50] <Celtiore> just add the wifi and touchscreen drivers
[14:51] <Celtiore> but the most important for mid hardware :)
[14:51] <NCommander> ah
[14:51] <NCommander> Right
[14:51] <NCommander> Next stupid question, how can I install this over MIDLinux?
[14:51]  * NCommander has already blown that away on my jax10 ...
[14:51] <amitk> did you save an image?
[14:51] <NCommander> I think I have one somewhere.
[14:51] <amitk> coz you can't download it from anywhere
[14:52] <NCommander> Ouch.
[14:52] <Celtiore> just copy the img on usb-stick anb boot the stick
[14:52] <Celtiore> http://public.celtiore.fr/aigo-2.6.24-23.img.torrent
[14:52] <NCommander> Is that the MIDLINUX image?
[14:53] <Celtiore> no, the ubuntu 2.6.24-23
[14:53] <NCommander> THen what's moblin_install_aigo?
[14:54] <Celtiore> do you have a compal recovery image ?
[14:54] <NCommander> no
[20:09] <plars> anyone here tried and/or succeeded in running Ubuntu on a sony mylo?


[09:24] <jibel> davmor2, hey latest isos are on the tracker
[09:25] <davmor2> jibel: I'd just run my update script too :)
[09:38] <davmor2> jibel: do you know if they managed to get the lo fix landed in it?
[09:44] <jibel> davmor2, it idodn't land
[09:45] <jibel> didn't*
[09:45] <davmor2> jibel: no worries
[11:20] <jibel> davmor2, expect another respin in the afternoon
[11:21] <davmor2> jibel: what!!! why now, and will it effect netboot?
[11:26] <jibel> davmor2, no, not netboot. it'll fix bug 1508075 and maybe bug 1436861 if it's uploaded on time
[11:29] <davmor2> jibel: does that mean there is a chance that the LO fix could land too?
[11:30] <davmor2> jibel: or is that definitely sru territory
[11:32] <davmor2> jibel: in that case I will once again concentrate on netboot and get that passed again
[11:34] <jibel> davmor2, is the LO fix uploaded? what is the bu #?
[11:34] <jibel> bug*
[11:34] <davmor2> jibel: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1508177
[11:35] <jibel> davmor2, okay, if there is no fix yet it'll be an SRU
[11:36] <davmor2> jibel: fix is at the bottom of the bug comments I think
[11:36] <jibel> yeah but it is not uploaded anywhere
[11:36] <jibel> and it takes ages to build LO
[11:36] <davmor2> true
[11:37] <jibel> it is just available in bjorn's ppa AFAICS
[13:23] <davmor2> jibel, infinity: any idea when the next respin will happen?
[13:52] <balloons> good morning all
[13:53] <davmor2> balloons: pffff good.....it is morning on the t'interwebz though, so morning
[13:54] <balloons> in the same vein as 5 o'clock somewhere, there's a perpetual morning happenig round the world :-)
[13:55] <balloons> My little one is currently on new zealand time I think
[13:55] <davmor2> balloons: when ever people arrive on the internet they always say morning, so the only logical outcome is it is always morning on the interwebz
[13:57] <davmor2> jibel, infinity: back to my earlier question any idea on when the final image will be done?
[15:30] <flocculant> davmor2: Friday next at this rate :p
[15:30] <davmor2> flocculant: I blame you entirely ;)
[15:31] <flocculant> good good
[15:32] <flocculant> I can take it :p
[15:32] <flocculant> I mean
[15:32] <flocculant> everyone does that so why not you too :p
[15:32] <davmor2> https://www.youtube.com/watch?v=E-PIidaqCyU
[15:35] <flocculant> :D
[15:42] <davmor2> jibel, infinity: https://www.youtube.com/watch?v=Vr_YVQctXVg or at least a final image ;)
[15:47] <flocculant> wasn't sure of the meaning here ...  **** WARNING: REBUILDING THE WORLD ****
[15:47] <jpds> flocculant: Every single package is being rebuilt from sauce?
[15:48] <flocculant> jpds: as long as it's HP and not tomato
[15:48] <flocculant> every sauce is just a pail imitation of HP Sauce
[15:49] <flocculant> though HP is a pale imitation now too said the old man
[16:23] <jibel> davmor2, ^
[16:23] <jibel> davmor2, it is not in current yet
[16:23] <jibel> automated tested are still running
[16:23] <jibel> tests*
[16:24] <davmor2> \o/ https://www.youtube.com/watch?v=k6JHaBVySTA
[17:28] <jibel> davmor2, the 2 changes are https://launchpad.net/ubuntu/+source/udisks2/2.1.6-2ubuntu1 and https://launchpad.net/ubuntu/+source/unity-settings-daemon/15.04.1+15.10.20151021-0ubuntu1 so a sanity check of desktop images and we are good
[17:29] <jibel> davmor2, I had a looked at server too and they look fine
[17:30] <davmor2> jibel: is this the final final image no more respins?
[17:34] <jibel> davmor2, it should be unless you discover something horrid
[18:01] <davmor2> note to self find nothing horrid
[18:07] <davmor2> jibel: boot from first drive isn't working on kvm I will try it on hardware in a minute so ensure it is functioning
[20:26]  * flocculant sometimes feels bad when he's noticed a bug a while back and forgotten and then sees people warbling about the same thing the day before release
[20:43] <balloons> :|
[20:46] <davmor2> flocculant: that'll be day before release ;)
[20:50] <flocculant> :)
[20:51] <flocculant> not sure why I'd even tried to boot with the hard drive from there tbh now
[20:51] <flocculant> not something that I would generally do
[20:56] <flocculant> evening balloons
[20:57] <balloons> howdy
[20:58] <flocculant> well - I at least am quite relaxed about releasing :D
[20:59]  * davmor2 pictures balloons in a stetson and chaps
[21:00] <davmor2> unfortunate not the butch cowboy more https://www.dees-fancydress.co.uk/catalog/images/63012.jpg
[21:01] <balloons> ohh boy
[21:01] <flocculant> why did I open that even though I saw the fancydress in the url ...
[21:02] <balloons> sterotypes are fun
[21:02] <balloons> lol, inline previews mean I had not choice.


[00:47] <skylite> why does sudo -u someuser bash -c "for i in {1..5}; do echo $i; done" not work the way expected?
[00:57] <jerichowasahoax> skylite: because you didn't escape the $
[00:58] <jerichowasahoax> skylite: so $i was expanded when the command line was processed, and since $i was empty then, you ended up with "for i in {1..5}; do echo ''; done"
[00:58] <skylite> but it prints 5 five times
[00:59] <jerichowasahoax> because of your for loop, yes
[00:59] <jerichowasahoax> it set $i to 1, then ran an empty echo line, then set $i to 2, etc etc
[01:01] <skylite> I dont really see how escaping solves this issue
[01:02] <jerichowasahoax> it prevents $i from being expanded when processing the inital command line
[01:02] <skylite> I tought escaping makes the shell interpret $ as a character and not as a variable sign
[01:02] <jerichowasahoax> yes
[01:02] <jerichowasahoax> the shell you're typing your command line into no longer interprets that as a variable to expand
[01:03] <jerichowasahoax> so, it passes the string $i as a command line parameter
[01:03] <skylite> I see
[01:03] <jerichowasahoax> and THAT shell that you're running sees "$i", and goes "oh, a variable!"
[01:03] <jerichowasahoax> remember, there's two shells here
[01:03] <jerichowasahoax> the "bash -c" in your command line, and the shell you're running that command line in
[01:06] <skylite> jerichowasahoax: thx
[01:15] <jerichowasahoax> skylite: np
[05:38] <ShriHari> hello