[00:13]  * infinity cleans out component-mismatches.
[00:14] <infinity> ... and wonders why nvidia-settings-updates wants to drop from restricted to multiverse.
[00:15]  * infinity fixes the seeds.
[00:16] <slangasek> where was it seeded before?
[00:17] <infinity> Nowhere, I suspect it was previously a depends/recommends of something.
[00:18] <infinity> Since it's been in restricted for a couple of releases, and one would expect us to have noticed by now if germinate didn't love it.
[00:18] <slangasek> nvidia-settings* themselves seem to be the only relevant packages uploaded today
[00:20] <infinity> Maybe having them conflict with each other is what developed the demotion hatred?
[00:20] <slangasek> huh, did I really just crash this machine by trying to feed it a fat partition over PXE?
[00:20] <infinity> But seeding it explicitly should fix that, since an explicit seeding of experimental seems to have stuck.
[00:21] <xnox> remember the bug with ubiquity "preferring" usb-drive for grub install? now there is recipocal bug filed, with internal drive being the preference now *sigh* bug 1066173
[00:21] <ubot2> Launchpad bug 1066173 in ubiquity "whole disk install puts grub in wrong place" [Undecided,New] https://launchpad.net/bugs/1066173
[00:22]  * xnox wants to sleep...
[00:23] <slangasek> are we sure that's a bug, and not by design?
[00:24] <xnox> cjwatson should look at it =) he is the master of picking the right grub device ;-)
[00:24] <xnox> slangasek: I can see an argument going for "by design"
[00:25] <slangasek> well, the one thing that's obviously sketchy there is installing to the internal MBR but referencing the external disk for boot/grub
[00:25] <xnox> slangasek: yeah, we used to have a bug of reverse ;-)
[00:26] <xnox> imho the mbr of the disk which has /boot should be the "right" grub destination, regardless of how the machine was booted.
[00:27] <slangasek> that's probably reasonable
[00:30] <ScottK> I can report that yesterday's bmcwl problem is solved.  It installs from the live media, works right away, and installs/works with the installed system too.
[00:30] <ScottK> wgrant: Thanks.
[00:31] <xnox> fair enough. good night everyone =)
[00:37] <doko_> slangasek, infinity: I assume the armel buildd issue is solved?
[00:37] <skaet> ScottK,  good to know.  thanks.
[00:40] <infinity> doko_: "The armel buildd issue" being?
 Could we have another armel builder or so.  What we have isn't keeping up.
 infinity, doko: ^^ if one of you can make magic happen?
[00:41] <infinity> doko_: Oh, well, I see no queue, so yes. :)
[00:41] <infinity> We get to rebalance sanely soon anyway, the armhf rebuild is finally almost done.
[00:41] <doko_> nd just 371 armhf builds left
[00:43] <phillw> Hi, anyone else getting disconnects from the ether pad?
[00:46] <infinity> Only for the last year or so.
[00:49] <skaet> phillw,  when you go to the page,  hit refresh before typing.  That usually avoids most of the silliness.
[00:50] <skaet> (only most,  not all)
[02:38] <TheLordOfTime> official Q release date decided yet, or no?
[02:39] <TheLordOfTime> i know this month, i am seeking a specific day ;P
[02:46] <skaet> TheLordOfTime, October 18th.   schedule for this cycle is: https://wiki.ubuntu.com/QuantalQuetzal/ReleaseSchedule
[02:48]  * skaet --> EOD
[02:49] <slangasek> skaet: 'night!
[02:50] <skaet> good night slangasek,  thanks for keeping it sorted this afternoon.  :)
[03:45] <infinity> cjwatson: FYI, I'm uploading quantal chroot tarballs with bootstrapping disabled for release, will re-enable in r-series chroots if/when we need it.
[04:42] <plars> yay, panda lives!
[04:42] <plars> but looks really funny without the slideshow :)
[04:43] <plars> I am slightly worried about this "fix" though, of just killing the slides
[08:35] <jibel> xnox, I'm still get bug 1065502 with ubiquity 2.12.11
[08:35] <ubot2> Launchpad bug 1065502 in ubiquity "Ubiquity failed to proceed to partman (dup-of: 1065034)" [Undecided,Confirmed] https://launchpad.net/bugs/1065502
[08:35] <ubot2> Launchpad bug 1065034 in ubiquity "'ubuntu ubiquity: umount: /tmp/tmp.h3NCLhoxSh: not mounted' during a Reinstall attempt on a previously manually partioned vm installation" [High,Fix released] https://launchpad.net/bugs/1065034
[09:13] <stgraber> slangasek: not too jetlagged actually though I've been busy with some social stuff ;)
[09:14] <stgraber> anyway, I tested the new shim yesterday and my laptop booted without the error message from the firmware, so the shim looks good
[09:14] <stgraber> I think I saw a couple of messages from grub though (non-blocking) relating to secureboot (looked like some grub modules that wouldn't load because of secureboot)
[09:14] <stgraber> I'll try and grab an updated server image later today and see if I can boot that one
[09:37] <ogra_> damned
[09:37] <ogra_> seems the slideshow hangs on ac100 as well :/
[09:54]  * ogra_ updates the pad for the above upload and related re-spin
[10:16] <knome> why aren't flavors visible in http://status.ubuntu.com/ubuntu-quantal/ ?
[13:06] <skaet> knome,  should be showing back up on next refresh of status.ubuntu.com.    Turns out to be a "feature" that marking them complete removes from display.  :P
[13:07] <knome> skaet, heh, right. thanks. :)
[13:16]  * smartboyhw is surpised....
[13:16] <smartboyhw> There are 3 days left in the current cycle. That means that in order to complete all the work 198.00 workitems must be completed per day.
[13:16] <smartboyhw> 198 workitems PER day?
[13:21] <skaet> smartboyhw,  it illustrates that teams aren't as good about managing the workitems as they need to be thats all.   Note it doesn't mean they must be completed,  if its clear they aren't going to happen they should be postponed, and then it would show up ok, from status perspective.
[13:21] <skaet> (although,  not from the original intent of what was wanted to be done :/ )
[13:21]  * smartboyhw is waiting for status.ubuntu.com to be updated to see the progress for the Ubuntu Studio blueprints:D
[13:22] <doko> this boy doesn't sound that smart
[13:22] <smartboyhw> doko, is it a personal attack/assualt?
[13:25] <skaet> smartboyhw, http://status.ubuntu.com/ubuntu-quantal/group/topic-quantal-flavor-ubuntustudio.html - the info is still there, not just linked from the to page until the next update happens.
[13:25] <smartboyhw> thx skaet
[13:25] <skaet> UbuntuStudio is in pretty good shape.    Its clear what's been postponed.
[13:25] <skaet> (so can be used for planning for UDS-R ;) )
[13:26] <smartboyhw> skaet, actually that page is not updated at all
[13:26]  * skaet looks at it closely,  and realizes,  yeah.
[13:26] <smartboyhw> skaet, last update time is 7th Oct, while in this past 6 days we changed quite a lot of workitems...Anyway to request a refresh
[13:26] <smartboyhw> ?
[13:26] <skaet> it should be updated on that next run.
[13:26] <smartboyhw> yeah
[13:27] <skaet> however the data on it generally indicates it is basically complete from a status point of view,  not that much left unsorted.
[13:28] <smartboyhw> :)
[14:02] <skaet> slangasek, cjwatson - around?
[14:11] <smartboyhw> skaet, ha after the update of that page Ubuntu Studio got 100% YEAH!
[14:11] <skaet> :)
[14:12] <smartboyhw> First actually to reach 100% sounds like we did follow skaet's instructions very well:D
[14:12] <skaet> Thank you.  :D
[14:13] <smartboyhw> :D
[14:34] <skaet> morning summary:   testing in progress.   Some bugs need further investigation/discussion.   latest knowledge is on the pad.
[14:35]  * skaet --> saturday errands,  bbl
[14:45] <smartboyhw> skaet, not sure if this is a blocker
[14:46] <smartboyhw> I don't think so but
[14:46] <smartboyhw> Bug 1066302
[14:46] <ubot2> Launchpad bug 1066302 in ubiquity "'update this installer' link on the welcome page shows no response to a mouse click" [Undecided,New] https://launchpad.net/bugs/1066302
[15:55] <ScottK> I tried out the chromium in quantal-proposed and it seems fine.  If there's a Lubuntu respin, I'd copy it over.
[15:57] <ScottK> Sine the rebuild is done on armhf, having more than one working armel builder would be nice.
[16:04] <xnox> i am confused about bug 1066302 was the installer update been enabled on the mirror?
[16:04] <ubot2> Launchpad bug 1066302 in ubiquity "'update this installer' link on the welcome page shows no response to a mouse click" [Undecided,New] https://launchpad.net/bugs/1066302
[16:05] <xnox> jibel: if you are still seeing that /tmp/ mounting bug or similar please file a new bug with logs. And I'l look into that.
[17:09] <hggdh> humpf. On my panda setup, desktop installation does not show up until I ctrl-alt-f1/ctrl-alt/f7
[17:10] <hggdh> not critical, but perhaps we should release-note it
[17:10] <hggdh> skaet: ^ I will open a bug on it as soon as the install is done, want to grab dmesg and install logs
[17:17] <xnox> hggdh: i'm sure we have seen that bug already.... please search for it first.
[17:17] <xnox> me & ogra were discussing it yesterday.
[17:18] <hggdh> xnox: will do, thanks.
[17:48] <hggdh> xnox: yes, bug 1065902. I will tag on the ISO test result
[17:48] <ubot2> Launchpad bug 1065902 in linux-ti-omap4 "black/blue screen before installer, tty switch fixes it" [Medium,Confirmed] https://launchpad.net/bugs/1065902
[17:51] <slangasek> stgraber: cool - does the server image boot for you now too?
[17:51] <xnox> hggdh: thanks =)
[17:51] <slangasek> skaet: ish
[17:53] <slangasek> ogra_: so the livecd-rootfs change only impacts the ac100 image?
[18:32] <slangasek> hggdh: for bugs you think should be release-noted, don't hesitate to mark them on the ubuntu-release-notes project directly (done now for bug #1065902)
[18:32] <ubot2> Launchpad bug 1065902 in linux-ti-omap4 "black/blue screen before installer, tty switch fixes it" [Medium,Confirmed] https://launchpad.net/bugs/1065902
[18:41] <hggdh> slangasek: will do; I tend to be careful on that ;-)
[18:43] <slangasek> hggdh: if by "careful" you mean "reluctant to do so", it's far better for us to have it visible that you think it should be release-noted... we can always wontfix if we disagree ;)
[18:44] <hggdh> heh. Indeed, it would be more like "reluctant to do without additional confirmation". But I will be more, ah, careless in the future
[19:08] <stgraber> slangasek: testing now
[19:17] <infinity> cjwatson: Oh wow, it was passing -lc?  That would explain it.
[19:18] <infinity> And pypy failed after 2 days, 3 hours, 4 minutes, 58.8 seconds.  Sadness.
[19:18] <plars> hggdh: heya, have you tried server on arm?
[19:19] <plars> hggdh: I'm trying to double-check now, but I think there might be an issue now with encrypted partitions
[19:19] <plars> hggdh: now that the keyboard works for server installs, we can get to this, and it looked like keyboard doesn't work for entering the password
[19:20] <plars> hggdh: installation about to finish up here
[19:20] <stgraber> need to find another usb key, that fancy usb3 ssd won't show up in my "bios"...
[19:20] <plars> hmm, yeah no keyboard
[19:21] <stgraber> cjwatson: I got some secure boot errors from grub at boot time now. I'll send you a photo
[19:21] <stgraber> (first checking that I'm up to date)
[19:22] <plars> infinity: any ideas on this? Is it possibly a missing module or something in the uinitrd?
[19:22] <infinity> plars: I'm confused.  That seems to boil down to "now that the keyboard works, the keyboard doesn't work"?
[19:23] <plars> infinity: well, the keyboard works during install now (previously I could only do installs over serial)
[19:23] <plars> infinity: so I can get it installed, and if I do a normal guided partitioning, everything is fine
[19:23] <infinity> stgraber: Wait, is there some assumption that current server should work for you, while the previous didn't?
[19:24] <plars> infinity: but if I select lvm+crypt then when it reboots and asks for the passphrase to unlock the disk, I cannot enter anything
[19:24] <stgraber> infinity: where previous is from a few days ago, yes
[19:24] <stgraber> infinity: basically hoping that new shim + grub will let me boot it
[19:24] <infinity> stgraber: That seems unlikely, given that d-i wasn't rebuilt, and server's boot bits come from d-i...
[19:25] <stgraber> hmm, indeed...
[19:25] <stgraber> slangasek: ^
[19:25] <infinity> plars: Oh, I see.  Post-install, no keyboard in the initrd.  Hrm.  I'm not sure why that would be different on ARM than x86, unless the keyboard bits are all built in to the x86 kernels.
[19:25] <stgraber> cjwatson, slangasek: http://www.stgraber.org/download/2012-10-13_21-18-56_512.jpg
[19:25] <stgraber> cjwatson, slangasek: btw, I don't actually have to press a key, there appears to be a 15-30s timeout
[19:26] <plars> infinity: likely config madness, keyboard didn't work on server installs until just recently, so even different between arm desktop and arm server
[19:26] <stgraber> cjwatson, slangasek: (that's on my installed system with up to date grub2 and shim)
[19:26] <stgraber> good news is, I'm not getting the access denied message from the firmware though :)
[19:27] <infinity> plars: Yeah, but I know the reason for that, since I fixed it. :P
[19:27] <infinity> plars: (It wasn't kernel configs, it was the d-i initrd)
[19:27] <plars> infinity: right, sorry
[19:28] <plars> infinity: but back to my original question... do you have some idea why the keyboard would work during the installer, and post install on non-encrypted installs, but not at this point?
[19:28] <infinity> plars: Yes, no keyboard modules in the initrd.  But I'm trying to sort out why.
[19:29] <plars> I do see a message on the screen right before it asks for the password: cryptsetup evms_activate is not available
[19:29] <plars> but I suspect that's unrelated
[19:29] <infinity> plars: (The installer includes them explicitly, that was the bug I fixed earlier, and you don't NEED a keyboard in the initrd when you're not running crypt, so you didn't notice the lack of keyboard)
[19:29] <infinity> plars: What's the bug # for this?
[19:30] <plars> infinity: haven't filed it yet, doing that now.  Just put it in linux-ti-omap4?
[19:30] <infinity> plars: No, initramfs-tools, probably.
[19:31] <infinity> plars: The kernel is fine (though, I suppose we could "fix" it by building in the USB-HID stack, that seems heavy-handed and unnecessary).
[19:33]  * infinity was pretty sure none of that was built in for x86 either, though, and is now a bit curious...
[19:33] <stgraber> infinity: the new server image actually boots fine, so looks like the new shim and grub made their way there somehow
[19:34] <infinity> stgraber: Curious, maybe it doesn't use the d-i cdrom bits, like it used to.
[19:34] <plars> infinity: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1066376
[19:34] <ubot2> Launchpad bug 1066376 in initramfs-tools "keyboard doesn't work to enter password with panda and encrypted partitions" [Undecided,New]
[19:34] <infinity> So, yeah.  USB HID stuff is modular on x86 too...
[19:34] <infinity> plars: Can you confirm that this work on x86 with a USB keyboard?
[19:35] <infinity> plars: Let me amend that.  Can you confirm this works on x86 with a USB keyboard and no BIOS USB->PCAT compat emulation? :P
[19:35] <infinity> plars: (Cause it really shouldn't)
[19:35] <plars> infinity: it worked in a VM with x86, haven't tried on hardware but it's probably pretending to be a usb keyboard
[19:35] <plars> infinity: I can try it though, of course
[19:35] <infinity> plars: I suspect that the VM is actually giving you an AT or PS/2 keyboard.
[19:35] <hggdh> plars: I have not yet started with encrypted disk on arm server, it is the next
[19:35] <infinity> plars: And most people's BIOSes also do "early boot keyboard emulation" which, again, is giving you a fake AT/PS2 keyboard.
[19:36] <infinity> plars: With that option off, this should fail hard on x86 too.
[19:36] <stgraber> infinity: so the shim's md5 on the media matches mine so it's clearly up to date, grub's doesn't, so I guess I have something slightly more recent on mine (or something...)
[19:36] <hggdh> plars: whole disk encryption, or justg home?
[19:37]  * infinity ponders how best to sort this keyboard mess... Adding the whole USB-HID stack to every initrd seems like some crazy bloat.
[19:37] <infinity> hggdh: Whole disk.
[19:37] <plars> hggdh: whole disk
[19:37] <infinity> hggdh: And I'm sure you'll have the same problem.
[19:37] <infinity> hggdh: I'm more curious for confirmation that it's also broken on x86 without BIOS keyboard emulation (which it should be).
[19:40] <hggdh> on it now on ARM, will try later on AMD64
[19:40] <infinity> This probably only *looks* like an ARM-specific bug because ARM doesn't ever provide you with fake keyboards, while PCs unhelpfully usually do, and sometimes don't. :P
[19:40] <infinity> hggdh: Kay.  Assuming your amd64 machine has a BIOS option to disable keyboard emulation (might be called "early USB keyboard support" or similar), that's what needs to be off.
[19:41] <hggdh> infinity: I will check
[19:41] <infinity> And if it's a laptop, all bets are off, cause laptops refuse to let you disable the internal keyboard, for sanity reasons.
[19:41] <infinity> (Though, you can still test with an external USB keyboard and emulation off)
[19:42] <infinity> Anyhow.  I need to pack and be on a plane, but I have a good handle on what the bug *is*, not so much a good plan as to where/how it should be fixed right now.
[19:42] <infinity> I'll think about it while I'm bored in the air. :P
[19:42] <plars> infinity: have a good flight, and thanks
[19:44] <infinity> Hrm.  The input-modules udeb is only 70k.  So, that leads me to believe I could add everything in that to the initrd and only grow it by, well, 70k.
[19:44] <infinity> That might not be awful.
[19:45] <infinity> And maybe worth doing universally, since I hear people like having keyboards in their initrds.  Though, I'd still prefer to believe that most omap4/server users would use serial consoles...
[19:45] <infinity> plars: I assume this all works smashingly if you do it via serial instead?
[19:46] <plars> infinity: it used to, but I haven't tried yet with this image
[19:47] <infinity> plars: Right, well.  Please file the bug on initramfs-tools, assign it to me, and mention some of the above (It works in the installer's initrd, it works after a full boot (so, post-initrd), but doesn't work for crypted root (so, in the post-installed initrd))
[19:47] <infinity> plars / hggdh: And if one of you can confirm that an x86 machine without BIOS emulation suffers the same issue, I'll just fix it universally, if not, I'll make it ARM-specific for minimal impact.
[19:48] <infinity> plars: Oh, and once filed, throw it in the pad in the "consideration" section, so people bug me about it (or, so I can bug myself). :P
[19:48] <plars> infinity: will do, thanks
[19:49] <infinity> stgraber: Well, regardless of which bits come from where, we'll want one last d-i respin before one last image respin, once the grub/shim stuff's definitely settled, I think.
[19:49] <infinity> stgraber: If you want to make a note of that so we don't forget, that would be snazzy.
[19:52] <stgraber> infinity: I'll make a not locally and put it on the pad once it's all setup for release
[19:52] <stgraber> *note
[20:03] <hggdh> crap. Just locked myself out of the amd64
[20:04] <plars> hggdh: ?
[20:04] <hggdh> infinity: the only option I have on my system is "disable USB emulation"
[20:04] <infinity> hggdh: That's likely the one.
[20:04] <infinity> hggdh: If changing that makes it so you can no longer, for instance, fiddle with GRUB boot menus, that's what we want.
[20:04] <hggdh> plars: I disabled USB emulation, now the keyboard does not work anymore. On anything (will try reboot, and F2)
[20:05] <hggdh> infinity: I cannot even login to the system
[20:05] <infinity> hggdh: Oh?  Once a system boots completely, the USB-HID stuff should be loaded.
[20:05] <infinity> hggdh: Maybe your system is extra special. :P
[20:06] <hggdh> infinity: it is a Dell, so yes, it is special ;-)
[20:07] <hggdh> but BIOS setup works. Since this system had a Quantal B2, I will reboot on it, and grab dmesg via SSH
[20:09] <hggdh> infinity: this might be related to the issue
[20:09] <infinity> Well, if it doesn't work without BIOS emulation even post-boot, that's an entirely different bug/problem than the ARM one I was hoping to verify, and likely the answer is just "don't do that on that BIOS, then".
[20:10] <infinity> Cause the Panda keyboard work fine post-boot, just not in early boot.
[20:10] <infinity> s/work/works/
[20:11] <plars> I just double checked, and if I enable serial console in the preEnv on panda, I can enter the password just fine
[20:11] <infinity> plars: Right, that's expected.
[20:11] <plars> yeah, but I said I'd check
[20:11] <infinity> plars: And a fair workaround/recommendation, if I can't fix this before release.
[20:11] <plars> yeah
[20:11] <infinity> Since, well.  A "server" with a keyboard is wrong anyway. :P
[20:12] <plars> well, for panda at least
[20:12] <infinity> For anything with workable serial or ethernet management, really.
[20:12] <infinity> So, anything other than a whitebox PC that needs a KVM cause it's crap.
[20:13] <hggdh> oh, another bug -- on the install, when you get to the selection ((install Ubuntu server, Multiple servers installs with MAAS, etc), select "Boot from first hard disk" -- and you are thrown back into the "select language", and then to the install menu
[20:13] <infinity> That entry probably just shouldn't be there.
[20:14] <hggdh> well it has been there for quite a long time
[20:14] <infinity> (You're still talking ARM?)
[20:14] <infinity> If x86, then yeah, that's a bug that it doesn't work.
[20:14] <hggdh> nope, AMD64 install, server
[20:14] <infinity> Oh!
[20:14] <infinity> Yeah, that's a bug.
[20:14] <infinity> Please file.
[20:14] <hggdh> I am oppening one against D-I
[20:15] <infinity> Possible cdimage, but d-i works for now, especially if you note it in the pad so we can hunt it.
[20:15] <infinity> s/possible/possibly/
[20:16] <infinity> Oh, wait.  To be sure, this is on a system where there's something bootable on the first hard disk?
[20:16] <infinity> Like, it's not trying to chain out and failing, is it?
[20:16] <infinity> Cause if the system wouldn't boot anything without install media, there's nothing for us to chain into and boot for that option.
[20:17] <infinity> Which should/would produce the sort of "loop back to the menu" behaviour.
[20:17]  * infinity packs more.
[20:17] <hggdh> infinity: https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1066387
[20:17] <ubot2> Launchpad bug 1066387 in debian-installer "D-I install menu, select "Boot from first hard disk" and it goes back to Language selection" [Critical,New]
[20:19] <hggdh> in the pad now
[20:20] <infinity> hggdh: Did you see the above?  Is/was there actually something bootable installed?
[20:20] <infinity> hggdh: (ie: without the boot media in the drive/port, does it boot an OS?)
[20:21] <hggdh> infinity: this system has B2 installed
[20:21] <infinity> Alright.  They, yeah, sounds like a real bug.
[20:21] <slangasek> infinity: what now?  d-i absolutely was rebuilt after the latest shim upload
[20:21] <infinity> slangasek: After the last shim, not after the last grub2.
[20:21] <infinity> slangasek: And yeah, I guess stgraber's bug was shim-related, which explains why his bug went away.
[20:22] <infinity> slangasek: But we still probably need a rebuild for grub2-signed, too.
[20:22] <hggdh> infinity: and I just confirmed it does have an installed system
[20:22] <slangasek> infinity: mm; we ought to be rebuilding d-i to use the current grub, was that the issue you spotted the other night with grub2-signed landing much later than expected?
[20:22] <slangasek> but yes, it was shim that we changed for stgraber, not grub2
[20:23] <infinity> slangasek: No, this was a new grub2, a day after that non-issue.
[20:23] <slangasek> ok
[20:23] <infinity> slangasek: When you respun the world yesterday afternoon.
[20:23] <slangasek> right
[20:24]  * slangasek double-checks the grub changelog to refresh his memory
[20:24] <infinity> Maybe I'll just do a d-i bump right now with a hope/dream that it'll be the last.
[20:24] <infinity> And then future cdimage builds will just pick it up without thinking.
[20:25] <slangasek> stgraber: are those errors when booting the image, or after install?
[20:25] <slangasek> (the insmod errors)
[20:25] <infinity> I have a sneaking suspicion there may still be a last-minute ti-omap4 revert or something, but I've lost t context on where Paolo is at with debugging recent oddities.
[20:25] <infinity> Cause, well, weekend.
[20:26] <slangasek> infinity: I would fully expect the USB-HID stack to be in the initrd and am surprised it's not
[20:27] <infinity> slangasek: Alright, then we should just fix that.
[20:27] <slangasek> infinity: so as for d-i, there's no reason to think grub and shim aren't already settled by this point; if a d-i upload and image respin is needed, we should do that ASAP
[20:28] <infinity> slangasek: d-i's up.
[20:28] <slangasek> "up"?
[20:28] <plars> infinity: hmm, if I disable legacy support for usb, then I just end up at the grub menu with no keyboard control
[20:28] <plars> infinity: but it looks like it's moot now
[20:28] <infinity> slangasek: As in, uploaded.
[20:28] <slangasek> and already accepted?  or still waiting to hit the queue?
[20:29] <infinity> slangasek: It'll hit the queue in 45s.
[20:29] <slangasek> ok
[20:30]  * infinity eyeballs his ~/build/initramfs-tools directory and notes that it's nothing but Debian uploads.
[20:31] <slangasek> infinity: although, note that fixing the module-loading errors in grub that stgraber just posted requires a new round of grub2
[20:31] <infinity> slangasek: Hahaha.
[20:31] <slangasek> cjwatson: do you think loadenv and keystatus are safe to add to the SB images?  (and while we're at it, what about tftp?)
[20:31] <infinity> slangasek: Well, just leave that d-i in the queue, then.  Or reject it and wait.
[20:32] <slangasek> infinity: so let's just leave that d-i sitting in the queue for the moment, yeah
[20:32] <infinity> slangasek: Reject it, so no one's tempted to accept it and get all excited about respins.
[20:32] <slangasek> done
[20:32] <slangasek> stgraber: did the server image install successfully for you under SB, too?
[20:33] <infinity> slangasek: Wouldn't tftp in grub provide a simple bypass?  signed-grub->tftp->new-bootloader->chain to whatever?
[20:34] <infinity> Unless it would check that whatever it got from tftp was also signed before loading it.
[20:34] <slangasek> infinity: tftp only implements a filesystem interface, it doesn't let you bypass the security checks on module loading or chaining
[20:34] <infinity> Ahh.
[20:34] <infinity> Kay.
[20:34] <slangasek> but it does mean you suddenly have a network filesystem in your signed image, which is a potential source of bugs, and RH/Fedora are currently *not* including this in their SB images :)(
[20:34] <plars> hmm, but I can still enter the password with legacy support disabled
[20:35] <infinity> plars: "The password"?
[20:35] <infinity> plars: You mean for a crypted root?
[20:35] <plars> infinity: yes
[20:35] <infinity> plars: Alright, then this may only be ARM that's missing those modules in the initrd.  Add this debugging bit to the bug for me?
[20:35] <plars> in both cases, usbhid is loaded after boot
[20:35] <infinity> plars: I'll mangle this first thing Monday.
[20:35] <plars> ok
[20:36] <slangasek> infinity: but basically we have no UEFI netboot support at present, and I'm trying to get that all sorted.  If you're not doing SecureBoot you can just drop the kernel and initrd in your memdisk, cook a custom grub.cfg, and go from there; but if you need SB, grub needs a way to access a kernel and initrd that are *not* included in the image
[20:36] <infinity> (Though, *why* ARM would be missing those modules and not x86, I dunno... Not a lot of arch-specific stuff in initramfs-tools)
[20:37] <slangasek> stgraber: if you have the time, I would appreciate a bug on grub2 with that screenshot, asking for keystatus+loadenv to be added to the UEFI images
[20:37] <infinity> slangasek: Is doing this from the bootloader the expected way to do netboot on UEFI, or is this just a hackish workaround until we can build UEFI netboot images to complement the current PXE ones?
[20:38] <infinity> slangasek: (Seems odd to me to ask one's bootloader to implement a network filesystem)
[20:39] <slangasek> infinity: it's all debatable
[20:39] <slangasek> infinity: regardless, I'm concerned about having SB-enabled grub support loading the kernel from the network, because that's how cobbler needs it to work
[20:39] <slangasek> but I also have no idea if UEFI firmware is going to support the shim model
[20:40] <slangasek> if it *can't*, then maybe making this work with signed images distributed from the archive doesn't actually matter
[20:40] <slangasek> but I still don't want cobbler to have to work by implementing "here's a monolithic image containing all the possible kernel and initrds that you might want to boot, download this all at once and enjoy"
[20:46] <infinity> plars: Can you give me the initrd from that affected system?
[20:47] <plars> infinity: sure thing, I'll attach it
[20:48] <infinity> plars: And lsmod from the running system.
[21:02] <skaet> thanks hggdh
[21:04] <infinity> plars: And dmesg from the system too.
[21:08] <slangasek> xnox, jibel: is there a new critical ubiquity/partman bug report in our future?
[21:24] <hggdh> plars: you have abug for the usb keyboard not working on arm?
[21:27] <ScottK> Someone should let Mark know that he's already made the milestone of too late to update all the tools to know about the new release name, so he can announce it anytime now.
[21:42] <skaet> ScottK, done.
[21:56] <stgraber> slangasek: (replying in order of backlog). The errors are showing up on my installed system. I don't think they were showing up when booting from media, though I booted from media in debug mode, so they might have gone unnoticed in the rest of the log messages flying by
[21:57] <stgraber> slangasek: I didn't install the server build as I don't have enough USB disks around to both boot and install on USB (and don't quite want to wipe my laptop). I just checked that d-i started fine and then rebooted
[21:58] <stgraber> slangasek: I'll file a grub2 bug now
[22:02] <stgraber> slangasek: bug 1066399
[22:02] <ubot2> Launchpad bug 1066399 in grub2 "grub2 fails to insmod keystatus and loadenv when running with secureboot" [Undecided,New] https://launchpad.net/bugs/1066399
[22:03] <stgraber> you may want to target/milestone if you think this should be fixed for release. It seems release notable to me as the machine boots fine and doesn't require any user interaction (though the error seems to indicate otherwise)
[22:04] <stgraber> if you think this should be fixed, let me know once you have a signed grub2 around and I'll reboot to check the fix
[22:08] <skaet> stgraber, have set it up with Release Notes project targetted to quantal so we don't forget it, at any rate
[22:13] <stgraber> skaet: ok
[22:14] <stgraber> I guess it'll end up depending on how much we care about the first boot experience on those systems
[22:15] <stgraber> if we want it perfect, then we'll need the change (grub2 + grub2-signed) and respin the images, otherwise, a zero-day SRU will fix it post-install
[22:16]  * skaet nods
[22:16] <stgraber> oh, though I guess there's also the thing where it's likely that those errors will also show up whenever you boot the install media, so potentially more than just a one time thing for those using live medias pretty often
[22:17] <stgraber> (but the intersection of people using live media extensively, on non-persistent storage and on systems with secure boot enabled, will likely be pretty small for 12.10 ;))
[22:17] <skaet> will wait for slangasek's opinion, at any rate - its irritating, but not a real blocker.
[22:18] <skaet> agree about the user pool forecast,  and scope of risk.    :)
[23:09] <infinity> stgraber: We need to respin d-i and images for the previous grub2 upload anyway, so it's more a question of "do we want to make these grub changes", not "do we want to re-spin images".
[23:09] <infinity> stgraber: And I think slangasek was mulling that over before deciding when to unreject my d-i upload.
[23:54] <doko> lovely, traded two arm build failures for an amd64 one


[19:31] <yogoyo> friendly greetings, i get oopses when i try to link launchpad to ubuntu one
[19:32] <yogoyo> i can post the ID when that helps
[19:33] <yogoyo> i am assuming the problem could have raised, because i used to have a launchpad account with that gmail account until several months ago. and i used that email to sign up for ubuntu one today
[19:40] <tomwardill> yogoyo: if you email<EMAIL_ADDRESS>including your email address and the ID from the OOPS, someone will look at it when we’re at work next week
[19:40] <tomwardill> your account username would be useful also
[19:41] <yogoyo> the entire rest-of-the-weekend no launchpad plumber. okay.
[19:42] <yogoyo> tomwardill: thanks for letting me know
[19:45] <yogoyo> happy times to you all: o/


[03:10] <paultag> gilbert: thanks :D
[03:10] <paultag> gilbert: I need to add a better fail-over page :)
[03:10] <paultag> gilbert: zack thought it was /.'d :)
[12:28] <paultag> hey gilbert -
[12:28] <paultag> gilbert: There's a debian RT ticket now -- > Please make Paul Richards Tagliamonte (currently a DM) an uploading DD.


[00:21] <cherylj> mgz: http://paste.ubuntu.com/13840643/
[00:42] <mup> Bug #1524135 opened: 'debug-log' fails when logs are large when using db-log <logging> <juju-core:Triaged> <https://launchpad.net/bugs/1524135>
[00:51] <mup> Bug #1524135 changed: 'debug-log' fails when logs are large when using db-log <logging> <juju-core:Triaged> <https://launchpad.net/bugs/1524135>
[00:54] <mup> Bug #1524135 opened: 'debug-log' fails when logs are large when using db-log <logging> <juju-core:Triaged> <https://launchpad.net/bugs/1524135>
[03:54] <mup> Bug #1524171 opened: make preupgrade disk space checks smarter <juju-core:Triaged> <https://launchpad.net/bugs/1524171>
[04:06] <mup> Bug #1524171 changed: make preupgrade disk space checks smarter <juju-core:Triaged> <https://launchpad.net/bugs/1524171>
[04:12] <mup> Bug #1524171 opened: make preupgrade disk space checks smarter <juju-core:Triaged> <https://launchpad.net/bugs/1524171>
[06:15] <mup> Bug #1524190 opened: Undocumented update-status hook <juju-core:New> <https://launchpad.net/bugs/1524190>
[09:59] <voidspace> frobware: I need coffee and the loo (bad timing)
[10:00] <voidspace> frobware: can we postpone ten minutes?
[10:00] <frobware> sure
[10:17] <voidspace> frobware: omw
[11:18] <voidspace> frobware: just a note
[11:18] <voidspace> frobware: my internet switches over to fibre tomorrow
[11:18] <voidspace> frobware: so I expect to be offline for some of tomorrow whilst the switch happens
[11:25] <mup> Bug #1524297 opened: juju behaviour in multi-hypervisor OpenStack clouds <juju-core:New> <https://launchpad.net/bugs/1524297>
[11:25] <frobware> voidspace, ack
[11:25] <frobware> voidspace, pretty sure you'll like the net result though
[11:26] <voidspace> frobware: :-)
[11:36] <voidspace> frobware: gah, worked out the difference between my code and master
[11:36] <frobware> voidspace, rebase gone awry, or something else?
[11:36] <voidspace> frobware: it's not strictly between my code and master - it's my code and the apiserver/spaces stuff
[11:37] <voidspace> frobware: there is a type mismatch, but we have this horrible piece of code called stateShim that works as an adaptor
[11:37] <voidspace> From the code: stateShim forwards and adapts state.State methods to Backing   method.
[11:37] <voidspace> *sigh*
[11:38] <voidspace> so I'll move the common code first and then adapt the new api to use it
[14:55] <mup> Bug #1524369 opened: i386 github.com/juju/juju/upgrades_test constant overflows int <blocke> <ci> <i386> <test-failure> <juju-core:Triaged> <https://launchpad.net/bugs/1524369>
[15:35] <mup> Bug #1524385 opened: local precise cannot be upgraded <ci> <local-provider> <precise> <regression> <upgrade-juju> <juju-core:Triaged> <https://launchpad.net/bugs/1524385>
[15:38] <mup> Bug #1524385 changed: local precise cannot be upgraded <ci> <local-provider> <precise> <regression> <upgrade-juju> <juju-core:Triaged> <https://launchpad.net/bugs/1524385>
[15:41] <mup> Bug #1524385 opened: local precise cannot be upgraded <ci> <local-provider> <precise> <regression> <upgrade-juju> <juju-core:Triaged> <https://launchpad.net/bugs/1524385>
[17:04] <dimitern> frobware, hey there
[17:05] <dimitern> frobware, I'm currently bootstrapping with your branch on 1.9 with 1 phys and 2 vlan nics on the vm
[17:06] <dimitern> frobware, I'm not sure though if we should add multiple bridges by default in master yet, rather than do it in maas-spaces first
[17:07] <dimitern> voidspace, o/
[17:07] <voidspace> dimitern: o/
[17:07] <dimitern> voidspace, how's the discovery going ? :)
[17:08] <voidspace> dimitern: stateShim is an abomination
[17:08] <voidspace> dimitern: I'm still moving code into common
[17:08] <voidspace> dimitern: nearly done with the apiserver - don't think I'll get it finished today but nearly
[17:10] <dimitern> voidspace, right, that's great
[17:11] <dimitern> frobware, well, it worked like charm!
[17:11] <voidspace> better in Python isn't it :-D
[17:11] <dimitern> voidspace, indeed :)
[17:13] <dimitern> frobware, uhm.. however it didn't create multiple bridges, just juju-br0
[17:16] <frobware> dimitern, ping
[17:18] <frobware> dimitern, can you pastebin your /e/n/i that didn't work
[17:18] <dimitern> frobware, just a sec
[17:19] <dimitern> frobware, http://paste.ubuntu.com/13863808/
[17:20] <frobware> dimitern, so I was wondering about this a little earlier. the expectation is that eth0.100 becomes juju-br-eth0.100
[17:21] <frobware> dimitern, much in the same way we do for eth0/juju-br0?
[17:21] <dimitern> frobware, it did work and connectivity is there, but I kinda expected I guess, to see juju-br0 for eth0, juju-brXYZ for eth0.50, juju-brUXV for eth0.100 (names of the bridges do not matter)
[17:22] <frobware> dimitern, so just a naming concern?
[17:22] <frobware> dimitern, I was conscious of len(name)
[17:22] <dimitern> frobware, yeah - the point is to be able to enslave an lxc NIC per bridge, such that if the host has IPs on eth0, eth0.50, and eth0.100, the container can mirror that with its eth0, eth1, and eth2 (as seen inside the container)
[17:23] <dimitern> frobware, am I making sense ? :)
[17:23] <frobware> nope
[17:23] <frobware> :)
[17:23] <dimitern> frobware, sorry, let me try again..
[17:23] <frobware> dimitern, any way we can HO or not very practical?
[17:23] <frobware> dimitern, alternatively annotate your pastebin with your expectations
[17:24] <dimitern> frobware, we're in a session and it won't work very well I'm afraid
[17:24] <dimitern> frobware, sure, let me do that
[17:30] <frobware> dimitern, you also said: "I'm not sure though if we should add multiple bridges by default in master yet" - agreed, though the script in my branch is so much better than either on master of 1.25 that I would like to get some of it there soon-ish. Also, I'm not sure what the net affect is addressable containers, which is why I wanted to chat.
[17:31] <dimitern> frobware, right, addressable containers in maas a less of a concern to me, as with the bridges we get addressability (for the primary nic now, with this script for all nics, which is even better)
[17:34] <frobware> dimitern, do we foresee a case where ethN is not active (ie. it is manual) but the vlans associated with it are active (ie. "static/dhcp")? Because that won't bridge atm...
[17:35] <frobware> dimitern, before catering for that case I wanted to know it that's in any way a reality as the parsing would have to hold more state to make this work.
[17:37] <dimitern> frobware, any vlans have to be on an active, link up device
[17:37] <dimitern> frobware, if the raw device is down, there won't be any possibility to pass vlan traffic on it
[17:38] <dimitern> frobware, I'm preparing /e/n/i example, just a few minutes and I'll paste it
[17:38] <frobware> dimitern, so from a re-rendering perspective if the raw device is not active we won't add a bridge. or should not.
[17:38] <frobware> thx
[17:53] <dimitern> frobware, we're making some experiments with dooferlad here to figure out what we can do with bridges and vlans
[17:55] <dimitern> frobware, if it gets late, don't stay up :) we'll stay in touch by mail
[17:55] <dimitern> frobware, the open question is can "juju-br0.50" be both a vlan virtual device AND a bridge we ca use for container nics
[17:56] <dimitern> or it has to be e.g. juju-br0-50 as a bridge, which has vlan-raw-device and vlan_id on
[18:06] <frobware> dimitern, the latter was mostly my question when I was doing this; I'll experiment a little after dinner too.
[19:45] <cherylj> can I get a review?   http://reviews.vapour.ws/r/3346/
[20:17] <mup> Bug #1524190 changed: Undocumented update-status hook <juju-core:Invalid> <https://launchpad.net/bugs/1524190>
[20:20] <mup> Bug #1524190 opened: Undocumented update-status hook <juju-core:Invalid> <https://launchpad.net/bugs/1524190>
[20:32] <mup> Bug #1524190 changed: Undocumented update-status hook <juju-core:Invalid> <https://launchpad.net/bugs/1524190>
[21:47] <menn0> thumper: git merge-base upstream/<parent-branch> HEAD should give you the commit that's the common ancestor
[21:47] <menn0> thumper: then git log <sha>.. or git log <sha>..
[21:47] <menn0> diff
[22:00] <perrito666> how can I find out what provider is one running? never thought of that
[23:03] <mup> Bug #1494951 changed: Panic "unexpected message" in vivid and wily tests <bug-squad> <ci> <intermittent-failure> <panic> <unit-tests> <wily> <juju-core:Triaged by cherylj> <https://launchpad.net/bugs/1494951>
[23:03] <mup> Bug #1524527 opened: deploy incompatible charm using --to should error earlier <juju-core:Triaged> <https://launchpad.net/bugs/1524527>
[23:14] <jw4> wq
[23:16] <perrito666> jw4: vi ftw
[23:18] <jw4> heh
[23:18] <jw4> don't tell katco
[23:43] <perrito666> seems that we didn't thought much how to upgrade stuff in the provider side
[23:47] <rick_h_> cccccceefhiubfgdelvcctfftfklkugnjciiefbtcvkl
[23:48] <perrito666> rick_h_: yeah, I agree


[06:40] <lordievader> Good morning.
[06:53] <Guest73031> huj
[09:17] <Naphatul> is there a way to make the splash screen match the background or login screen background?
[09:20] <lordievader> Naphatul: Yes, copy the splash screen change the background and set it to use that splash screen.
[10:05] <Guest57214> anyone tried to make a custom kubuntu cd with just updated software? I got ton of errors once I run "apt-get upgrade" :/
[11:16] <BluesKaj> Hiyas all
[11:27] <shattingduck> hi
[11:34] <BluesKaj> hi shattingduck
[12:28] <tobiasschoel> Hi, I have a problem with kontact downloading dates from citadel groupware server
[12:29] <alvin> Since Choqok is not actively developed anymore, what do you use as twitter client? (besides the website)
[12:32] <BluesKaj> alvin, try the social desktop
[12:33] <alvin> The social desktop? Is that a widget?
[12:34] <alvin> I found it (more or less)
[12:34] <BluesKaj> oops sorry , I thought it was on 14.04 too
[12:35] <BluesKaj> it's in system settings>account details here (14.10)
[12:39] <alvin> BluesKaj: I'm on 14.04. It's in Account Details -> Social Desktop. But I don't know the URL for the Twitter provider, if it exists.
[12:45] <BluesKaj> alvin, I don't know it either ...not a twitter person
[12:46] <alvin> I did not know what this "Social Desktop" was. I do like the idea, but documentation is sparse.
[12:46] <BluesKaj> it's new
[12:48] <alvin> All I really want is seeing twitter messages arrive on my desktop without that program crashing. The KDE microblog widget and Choqok do not fit that description. (Although I really liked Choqok's functionality)
[12:50] <BluesKaj> maybe choqok is still available
[12:50] <BluesKaj> !choqok
[12:50] <BluesKaj> !info choqok
[12:51] <BluesKaj> yup, just optional
[12:54] <alvin> It's still there. Unchanged. It crashed (and recovered) every x seconds when I last tried it.  Let's retry
[12:56] <BluesKaj> do you use pidgin, there's a twitter plugin for that
[12:57] <alvin> No, Telepathy
[12:58] <alvin> Didn't crash so far.
[12:58] <BluesKaj> ok
[14:08] <lorange> hi! is it normal that disk segmentation going so long?
[14:09] <lorange> mb 30 minuts already. i am instaling distro with fleshcard
[14:12] <lorange> Anyone?
[14:15] <lorange> ktnks
[14:50] <MaraManishi> Hi Everyone
[17:55] <l_r> hello
[17:55] <l_r> hawhat's the version of kde in kubuntu?
[17:55] <l_r> 14.04
[17:56] <darktori> 4.13.3
[18:19] <lordievader> Good evening.
[18:47] <amichair> is there a link somewhere to a list of tablet models that can run kubuntu?
[19:12] <MCHammer> hey
[19:13] <lordievader> o/
[20:15] <l_r> i have a  big choice to do: debian7.6 +kde vs kubuntu 14.04
[22:43] <skinux> How can we change the background color of the bottom panel??
[23:51] <valorie> valorie2, why are you unable to speak
[23:51] <valorie2> ha
[23:51] <valorie> ok, just general ignorance, sorry for the noise
[23:54] <wheezy123> Hello, No installed Icons other than Oxygen and Hicolor are showing up in GTK Icon Themes Options, anybody can help?


[06:15] <lamont-away> *** glibc detected *** double free or corruption (!prev): 0x00021050 ***
[06:15] <lamont-away> grumble
[06:15] <lamont-away> iproute build on hpa
[06:15] <lamont-away> hppa
[06:22] <lamont-away> make[1] : Entering directory `/build/buildd/klibc-1.0.14'
[06:22] <lamont-away> MCONFIG:90: klibc/arch/parisc64/MCONFIG: No such file or directory
[06:22] <lamont-away> make[1] : *** No rule to make target `klibc/arch/parisc64/MCONFIG'.  Stop.
[06:22] <lamont-away> jbailey broke my kernel
[06:23] <fabbione> lamont-away: check if there is a parisc dir instead
[06:23] <fabbione> i had a similar issue with sparc/sparc64
[06:24] <lamont-away> yep
[06:24] <fabbione> and check the contents of the 2 :)
[06:24] <fabbione> in sparc64 there were basically empty files
[06:24] <fabbione> the sparc one was correct
[06:24] <lamont-away> heh
[12:32] <doko> infinity: ping
[12:33] <doko> any way to get the config.log from the ncurses upload for i386? I cannot reproduce it here on a real 32bit system
[01:07] <infinity> As opposed to a fake one?
[01:09] <infinity> Oh, I had that same problem with glibc.
[01:10] <infinity> doko : s/-m64/-m64 -march=x86-64 -mtune=x86-64/
[01:10] <infinity> doko : gcc-opt on the buildds sets -march/-mtune to CPUs that GCC thinks can't do -m64, so you need to reset it.
[01:11] <infinity> doko : Either that, or fix GCC to stop whining. :)
[01:19] <doko> ohh, thanks
[01:51] <doko> infinity: is this necessary for powerpc as well?
[03:29] <infinity> doko : We don't use -mtune and -march on PPC...
[03:29] <infinity> doko : PPC looks to be failing for entirely different reasons.
[03:30] <doko> yes, I see it. strange. and that's not even the -m64 build ...
[03:33] <infinity> Yeah, I'm giving it a retry to see if it's just the kernel hating me.
[03:33] <infinity> If it fails the same, I'll give it a spin on a PPC machine at home where I can debug a bit.
[03:34] <doko> infinity, lamont-away: gcc-opt should not add anything, when it sees -m64 or -m32 ...
[03:45] <infinity> Okay, NOW it failed on the configure check.  Meh.  Time to save a build tree and look at it, I guess.
[03:59] <infinity> Erm.   cc1: error: invalid option 'arch=powerpc64'
[03:59] <infinity> doko : But we don't set -mtune and -march on powerpc anyway, so you shouldn't need to try to reset them.
[04:00] <doko> ok
[04:00] <doko> that was ncurses?
[04:01] <infinity> Yes.
[04:02] <infinity> Alternately, find out what GCC sets as the "baseline" on -m64, and set it to that.
[04:02] <doko> we should fix that stupidity on the buildd ...
[04:02] <infinity> That's what I did for glibc on amd64, to make sure we got what we wanted.
[04:03] <infinity> s/fix/alter/
[04:03] <doko> lamont-away, wake up! ^^^
[04:03] <doko> :)
[04:03] <infinity> I'll make sure that we have -mtune/-march parameters for "default", "-m32" and "-m64"... But right now, we don't.
[04:14] <doko> yes, I think we only need them for a few packages now
[04:19] <doko> infinity: please could you requeue openoffice.org2 on powerpc? I didn't see that failure before ...
[06:13] <lamont-away> doko: yeah - I know
[06:14] <lamont-away> doko: we taught it to not add -march for glibc - what else?
[06:14] <lamont-away> I need to actually teach it about -m{64,32} equivalence stuff
[06:18] <doko> I think that's all. At least for the three packages I build ...
[08:07] <elmo> lamont/infinity: FYI, I'm firing up a rebuilt of main on breezy-at
[08:23] <jbailey> elmo: Will the results for that just be in the usual ~lamont/... ?
[08:23] <elmo> I don't know how the logging stuff works, sorry
[08:23] <jbailey> 'k.
[08:24] <jbailey> lamont-away, infinity: ^^


[00:52] <lovelace> Hey if anyone here is interested, TriLUG has a meeting *right* *now* about the future of the lug
[00:52] <lovelace> And people can call into the conference call
[00:53] <lovelace><PHONE_NUMBER> x40
[00:53] <lovelace> 1 to toggle mute
[01:03] <holstein> cool


[22:08] <johnc4510> The new issue of the Ubuntu Weekly Newsletter is now available here:
[22:08] <johnc4510> https://wiki.ubuntu.com/UbuntuWeeklyNewsletter/Issue168


[19:45] <paddy> i have a complaint
[19:47] <paddy> now that rww was invited to the show we can begin - can we, topyli?
[19:47] <rww> yes hello, rww_man here
[19:47] <paddy> rww, please try to contribute to the problem or shut up.
[19:48] <rww> paddy: I stopped contributing to problems a long time ago, that's why I left Ubuntu.
[19:48] <paddy> i had a situation with this rww person on #ubuntu-offtopic
[19:48] <paddy> and i was asked by IdleOne to stop
[19:48] <paddy> and i agreed
[19:48] <paddy> after i agreed topyli came and set a mode without a reason
[19:49] <rww> You are aware this isn't the ban resolution channel for #ubuntu-ops, yes?
[19:49] <paddy> part of the problem was that rww used disrespectful language
[19:49] <rww> for #ubuntu-offtopic, even
[19:49] <paddy> e.g. he/she/it used the term "troll" to describe me as person
[19:49] <paddy> things like that
[19:49] <rww> I prefer the pronoun "it", no need for the other two.
[19:49] <paddy> right now you act like an "it", sorry.
[19:49] <topyli> paddy: if rww was a problem, it was fixed when he stopped actively operating our channels
[19:50] <paddy> topyli, WHY did you set a mode when i agreed to stpo?
[19:50] <topyli> if you believe i set +q for you in #ubuntu-offtopic without a reason, you should bring it up in #ubuntu-ops
[19:50] <rww> paddy: because you're a persistant nuisance who should be exiled from everywhere you join, probably
[19:50] <paddy> i asked WHY.
[19:50] <rww> and thankfully the freenode illuminati is making good progress on that front
[19:50] <IdleOne> I saw the entire conversation. What I saw was you trying to bait rww, if anything rww alerted the channel ops to a known problem user. Rather helpful if you ask me.
[19:51] <paddy> and what role does this "rww" person play in the ubuntu community to have a word like this?
[19:51] <Myrtti> are you one then? it usually cuts the chaff and goes to the point, some trolls acknowledge their trolldom
[19:51] <paddy> i ask again, what role does this person havE?
[19:51] <rww> paddy: I sit outside it and throw rocks at it.
[19:51] <rww> paddy: I'm like you except not a creep.
[19:51] <paddy> this will come to shuttleworth by ding dong i promise.
[19:52] <IdleOne> I'm sure he looks forward to reading your email
[19:52] <rww> also I delude myself that I'm somewhat more sensical
[19:52] <topyli> paddy: rww has no official role afaik these days. that makes no difference however
[19:52] <paddy> so you guys have a sexual online relationship with rww, is that "it"?
[19:52] <topyli> not yet!
[19:52] <rww> paddy: topyli and IdleOne don't, at least
[19:52] <paddy> for sure?
[19:52] <rww> topyli: sorry dear, I'm taken
[19:52] <IdleOne> not with rww
[19:52] <paddy> your word on it?
[19:53] <IdleOne> he's cute but not my type
[19:53] <paddy> i am not part of a gay mafia game or something?
[19:53] <rww> paddy: I limit my Ubuntu operator sexchats to heterosexual encounters, sorry. I hope that doesn't curtail your fantasy life too much.
[19:53] <IdleOne> well I think you have just proven why the quiet in -offtopic was a good decision
[19:53] <topyli> paddy: if you're not, there's nothing wrong about that!
[19:53] <paddy> 3 people it takes to troll me. 3.


[04:24] <ShellcatZero1> TJ-: I'm not very familiar with PXE, but my understanding was that it is generally used for OS installation over a network. Can you refer me to any documentation where it can be used as you described, loading GRUB and performing automatic /boot/ unlocking?


[01:28] <len_1304> Lumpy, new version of Pulse out. I have been playing with PA+linphone+jack+idjc.
[01:31] <len_1304> Machine = a-bit MB with P4 at 2.4Gh with 2.5G ram. Running US Version R. Bios has hyperthreading turned off (allows -p16 to work with guitarix).
[01:33] <len_1304> For this experiment Jack is running at -p 512 for 23 ms latency.
[01:34] <len_1304> jack and pulse (even bridged) are idling at about 1% cpu each. The pa-jack bridge is stereo only.... I don't know if mono would help.
[01:38] <len_1304> Pulse is set to have all audio cards turned off so that the jack bridge will always be default when the phone connects.... and to avoid any weird behaviour of PA/jack interacting with two cards at once might introduce.
[01:41] <len_1304> At idle, phone hung up, idjc streaming but not playing any music file... idjc runs about 10% cpu. With music playing, that goes up to 40ish%, closer to 50% if the sample rate of jack and the file are different.
[01:42] <len_1304> for this reason I am running rate of 44100.
[01:43] <len_1304> Opening the mic seems to have no effect (it shouldn't) so the act of introducing audio from the phone to idjc would be the same.
[01:47] <len_1304> The phone rings, gets answered and the phone opens ports to pulse. The phone starts using 50% or so cpu. Idjc also goes up. The audio from/to the phone gets choppy even though jack is not yet showing xruns, so the chop is all the pa/phone side.
[01:49] <len_1304> If idjc is also playing music... the whole audio chain goes into oscillation... I can recover from it by backing out one app at a time, but the set up is not usable.
[01:58] <len_1304> Lumpy, this set up would require more cpu horse power than I have. I do not know if two cores would be enough or not.
[02:06] <len_1304> The phone on gmail is much better but the latency is up around .5 or more sec.
[02:30] <len_1304> Nope I got it wrong, streaming takes 30% cpu. The player doesnt take that much unless the rate is different from jack.
[04:23] <shai_halud> holstein: earlier you mentioned something about a wav to midi program. what is the phg name i need to look for?
[04:23] <shai_halud> er pkg
[04:24] <holstein> http://stackoverflow.com/questions/5852102/software-to-convert-audio-to-midi ?
[04:51] <shai_halud> that must be it. installing kxstudio, btw
[04:51] <shai_halud> er, doing the updates from that repo. 500 megs worth
[04:52] <holstein> i havent added them yet
[04:52] <holstein> but i might...
[04:54] <shai_halud> that was just the updates. now i'm going for the kxstudio packages, THEN the mutltimedia software. this must be a few gigs altogether or something
[04:55] <shai_halud> pkgs are 173 megs
[04:56] <shai_halud> probably 1 gig at the end of the day
[04:56] <shai_halud> aha there he is
[04:56] <shai_halud> hey whippersnapper
[04:57] <shai_halud> sirriffsalot: talking to you....
[04:57] <sirriffsalot> What?
[04:57] <shai_halud> almost done installing kxstudio
[04:57] <sirriffsalot> Rofl
[04:58] <sirriffsalot> Hahahah
[04:58] <sirriffsalot> You're such a slut
[04:58] <shai_halud> whoa
[04:58] <shai_halud> kinds keep that to yourself, eh?
[04:58] <sirriffsalot> A joke ofc
[04:58] <sirriffsalot> Why are you going for kxstudio already?
[04:59] <sirriffsalot> I mentioned it an hour ago and you're reverting.. Without even getting ardour and jack worked out in Ubuntu Studio??
[04:59] <sirriffsalot> A little rushy for me anyway
[05:05] <shai_halud> holy cow. this .... changed my entire DE
[05:05] <shai_halud> without a reboot
[05:09] <shai_halud> well. i'm in this far. might as well go for broke
[08:17] <mick_> hello?
[08:17] <smartboyhw> Hello mick_
[08:17] <mick_> hey, hows things
[08:18] <mick_> i have a problem with getting a us122 (old) to work with usb, it works sometimes, then it fails
[08:20] <mick_> can anyone help?
[08:21] <mick_> or at least suggest an upgrade?
[08:35] <sirriffsalot> mick_: Us122?
[08:36] <mick_> yes its a tascam external sound card
[09:50] <mick_> what is a good interface to use with studio?
[10:43] <mick_> Can someone give me some clues as to which sound card I should consider?
[10:55] <shai_halud> greetings!
[10:59] <zequence> mick_: https://help.ubuntu.com/community/UbuntuStudio/SupportedHardware
[11:00] <mick_> Thank you :)
[11:00] <zequence> mick_: http://wiki.linuxmusicians.com/doku.php?id=hardware_matrix
[11:00] <shai_halud> hi Zeke
[11:02] <zequence> shai_halud: Hi. I was wondering who Zeke was :)
[11:03] <shai_halud> haha
[11:03] <shai_halud> that's YOU
[11:03] <shai_halud> are you terribly busy?
[11:05] <shai_halud> i am trying to compile latest vers of lmms and after having gotten through about a gig of dependencies, still come across some errors. i have a paste ready to upload if you can sort of enlighten me as to what  the remaining errors mean
[11:05] <zequence> shai_halud: shoot
[11:05] <shai_halud> one sec
[11:06] <shai_halud> http://pastebin.ca/2327606
[11:06] <zequence> shai_halud: I would recommend #lad and #opensourcemusicians also. Many of the application developers hang out at #lad
[11:06] <shai_halud> ok
[11:09] <zequence> shai_halud: Did you do this? "after installing missing packages, remove CMakeCache.txt before"
[11:09] <shai_halud> every time
[11:09] <zequence> Ok, just checking
[11:10] <shai_halud> (about 20-30 times)
[11:10] <shai_halud> i exaggerate slightly
[11:10] <zequence> shai_halud: Oh, try this btw. sudo apt-get build-dep lmms
[11:11] <zequence> That'll install all build dependencies
[11:11] <shai_halud> SWEET
[11:11] <shai_halud> that's what i was wishing existed
[11:11] <zequence> Yeah, it's handy
[11:13] <shai_halud> Only 31 megs to dl
[11:13] <shai_halud> wheeee
[11:15] <shai_halud> ok. i think cmake got far enough that time
[11:16] <shai_halud> Looking for pthread_create in pthreads - not found
[11:16] <shai_halud>     and QS_WIN also
[11:16] <shai_halud> process.h
[11:16] <shai_halud> seems nothing fatal
[11:17] <shai_halud> oh, and this:
[11:17] <shai_halud> ooking for include file /usr/src/sys/gnu/i386/isa/sound/awe_voice.h
[11:19] <shai_halud> woohoo. running make
[11:24] <zequence> shai_halud: Why are you building lmms, btw?
[11:24] <shai_halud> because i couldn't find a precompiled version of 4.13
[11:24] <zequence> Ok
[11:24] <zequence> could be kxstudio repos have it
[11:24] <shai_halud> nope
[11:25] <shai_halud> i am compiling theirs now
[11:25] <shai_halud> LMMS website is same
[11:26] <shai_halud> i figured ksstudio might be a little beefier. it is 1 meg larger
[11:26] <shai_halud> 80% make, no errors
[11:27] <shai_halud> 2 erros
[11:27] <shai_halud>  i wonder what they are
[11:28] <shai_halud> wine errors
[11:28] <zequence> 64bit might not work with wine
[11:29] <shai_halud> ok make install finished. now to see what it made
[11:33] <shai_halud> crap . it has no presets
[11:34] <shai_halud> hm
[11:34] <shai_halud> everything else seems fine
[11:36] <zequence> shai_halud: Would you be interested in helping out with Ubuntu Studio development/PR/testing? It's not a big question really, and doesn't require much involvement. I'm on the verge of trying to get more people involved. We have all kinds of things we'd like more people helping out with
[11:37] <shai_halud> i certainly would, if i am able
[11:37] <shai_halud> though i'm afraid my skills are rather meager.
[11:37] <zequence> shai_halud: Check out the wiki https://wiki.ubuntu.com/UbuntuStudio/
[11:38] <shai_halud> if there are ways I can help, I will glady do so
[11:38] <zequence> We don't need skills. Only will in most cases :)
[11:38] <zequence> we hang out at #ubuntustudio-devel
[11:39] <shai_halud> well, will i have in plenty
[11:39] <zequence> shai_halud: This is our team structure https://wiki.ubuntu.com/UbuntuStudio/TeamStructure
[11:39] <zequence> As you might notice, we have more teams than members
[11:40] <shai_halud> and if there are opportunities for me to learn, EXCELSIOR!
[11:40] <shai_halud> hehe
[11:40] <zequence> The teams are not only categories for splitting up responsibilities. We work with launchpad a lot, and each team is also a launchpad team
[11:40] <zequence> It has some benefits doin it that way
[11:41] <zequence> shai_halud: If you haven't got a launchpad account, get one. https://launchpad.net/
[11:41] <shai_halud> k
[11:41] <shai_halud> on it
[11:41] <zequence> you could begin by joining https://launchpad.net/~ubuntustudio
[11:42] <zequence> But, from there, it's really up to what you'd be interested in doing
[11:42] <zequence> shai_halud: join #ubuntustudio-devel, and I'll talk more
[11:42] <shai_halud> ok
[11:42] <shai_halud> gimme 5 to reggy
[11:46] <mick_> ok ill bite, got anything that will take around 20 mins of my time per day?
[11:46] <mick_> maybe more
[11:47] <zequence> mick_: We don't have a good structure for handing out work right now, also, I think one needs to get a look at the big picture a bit first, to see how we work, and then, hopefully, one can work independently a lot
[11:48] <zequence> testing for instance is not very structure right now. It should be, and we need to make it so in the future
[11:48] <zequence> We need a vivid PR team, who posts stuff on mail lists, our website and social channels
[11:49] <mick_> hmm
[11:49] <zequence> We need people who work on our workflows, audio, graphics, video, etc to do research on what applications are available, and if we are using the right ones, if they are well configured, etc - more of a user related job
[11:50] <zequence> Right now, we have too few people working on too many things.
[11:50] <zequence> Software development, and handling Ubuntu Studio source is not the biggest part of what we do
[11:50] <zequence> We have our own kernel, and right now, I'm the maintainer of it.
[11:51] <zequence> I will want for more people to learn that stuff too, and am preparing documentation
[11:51] <zequence> Oh, yeah. we need people who write docs too
[11:53] <zequence> mick_: The team structure let's you know what areas we work in https://wiki.ubuntu.com/UbuntuStudio/TeamStructure
[11:53] <zequence> mick_: shai_halud: blueprints is where we organize what we work on, who works on what, etc https://wiki.ubuntu.com/UbuntuStudio/PermanentBlueprintOverview
[11:54] <shai_halud> all pages bookmarked
[11:54] <zequence> All of the blueprints are at launchpad, so that is just an overview
[11:54] <zequence> shai_halud: I've been making sure everything you need is avaible from the wiki, so shouldn't be hard to find stuff
[11:54] <shai_halud> k
[11:55] <zequence> The important sources of info are really: blueprints, IRC and mail lists
[11:56] <zequence> some launchpad teams have special privileges, so if you need to post on the website, the PR team allows for that. That's why we have the teams
[11:57] <zequence> So, the first step is: become a member of launcpad. login to #ubuntustudio-devel, and subscribe to at least the Ubuntu-Studio-devel mail list
[11:57] <shai_halud> i'm in the channel now
[11:57] <zequence> mick_: You're welcome too
[11:57] <shai_halud> and perusing for the mail list
[12:03] <mick_> what was that link again I clicked on it and got lost, the getting started link
[12:04] <zequence> mick_: You have all the info from here https://wiki.ubuntu.com/UbuntuStudio
[12:04] <zequence> Next to the orange developer section
[12:04] <mick_> thanks
[12:04] <zequence> mick_: login to #ubuntustudio-devel
[12:04] <mick_> ty
[12:05] <zequence> mick_: I'm going away for a little while, but maybe someone else can answer any questions you have
[12:05] <zequence> bb in 30 or so
[12:05] <mick_> ok, ill see what i can find
[12:35] <zequence> mick_: why don't you join #ubuntustudio-devel too. I'm just talking with shai_halud there
[12:36] <mick_> join #ubuntustudio-devel
[12:36] <mick_> woops
[13:06] <studio-user992> bheey
[18:40] <iorec> helos, is there an easy way to upgrade from ubuntu to ubuntustudio without a complete reinstall?
[18:44] <Unit193> You can install the metapackage(s)
[18:45] <iorec> how would i go about doing that?
[18:46] <Unit193> You could install ubuntustudio-desktop, but they have several others as well, apt-cache search ubuntustudio   to see all.
[18:47] <iorec> and thats the full ubuntustudio "experience" then or just a hack?
[18:50] <zequence> iorec: Depends on what you mean. You could easily just install the packages you want/need, but if you want a clean install, the only way is to use the official ISO
[18:50] <Unit193> It's how you'd go from one to the other.  However, you will have "leftover" applications you may not need.
[18:51] <zequence> There may also be some conflicts in user settings, if you have many desktop systems installed in paralell
[18:51] <zequence> If you don't need the desktop, just install the packages you want
[18:51] <iorec> k, it is mainly that i am having troubles with jack all the time. sometimes works, sometimes not, without changes...i am hoping that would improve with ubuntustudio!?
[18:51] <zequence> To get realtime privilege, you'll need to add yourself to audiog group
[18:51] <zequence> To get low latency, install linux-lowlatency
[18:52] <zequence> iorec: That's a bug
[18:52] <zequence> iorec: It crashes sometimes when you try to stop it
[18:52] <iorec> ja, probably..at the moment it just won't start anymore.
[18:52] <zequence> To kill it, do: killall -9 jackdbus
[18:52] <zequence> It's probably frozen in the background
[18:52] <iorec> starts with built-in soundcard, but no more with external usb-audio device
[18:53] <zequence> And, also, it might not start, if pulseaudio is using the same device for something
[18:53] <zequence> That's also a bug, btw
[18:53] <iorec> i had pulseaudio killed completely..didn't change anything.
[18:54] <iorec> also several restarts of usb-device and pc didn't help
[18:54] <iorec> will try the killall -9 jackdbus
[18:54] <zequence> How did you kill pulseaudio?
[18:54] <iorec> how to start it then?
[18:54] <zequence> How to start jackdbus?
[18:55] <zequence> Either with qjackctl, using the default settings, or from a command line: jack_control start
[18:55] <iorec> found a blogpost about how to completely shutdown pulseaudio when having troubles with jack..followed that. pulse was obviously dead, but still no jack.
[18:55] <iorec> k, i have qjackctl
[18:55] <zequence> And each time, the onboard would work?
[18:55] <iorec> jes onboard works
[18:56] <zequence> what does this show you? cat .jackdrc
[18:56] <zequence> That should be: cat ~/.jackdrc
[18:56] <zequence> Mine is: /usr/bin/jackd -dalsa -dhw:M66 -r44100 -p1024 -n2
[18:57] <HelloWorld321> this one will be a little obscure: does anybody know if ~/.rstudio-desktop/sdb is supposed to have any .eml files in it?  I ran an unfortunate find script last night, and I'm trying to unwind it.
[18:57] <zequence> HelloWorld321: Sorry. Don't know what that is
[18:59] <iorec> this i get: /usr/bin/jackd -v -P1 -dalsa -dhw:0 -r44100 -p1024 -n2 -Xseq
[18:59] <HelloWorld321> zequence: tx.
[18:59] <HelloWorld321> If you're running rstudio under ubuntu, would you please type "ls -lart ~/.rstudio-desktop/sdb/prop/" and tell me if that directory contains files with no extension, or files with .eml extension
[19:00] <HelloWorld321> I think in a normal installation, they would have no extension; but I've accidentally renamed some to .eml
[19:02] <zequence> iorec: Well, it's not too low buffer anyway.
[19:02] <zequence> iorec: Which device is it?
[19:03] <iorec> maudio quattro
[19:03] <iorec> first error i get on starting: ERROR: Cannot lock down 82241434 byte memory area (Cannot allocate memory)
[19:03] <iorec> then it goes on
[19:03] <iorec> next errro: RROR: ALSA: could not start playback (Broken pipe)
[19:04] <zequence> iorec: The memory error would indicate you don't have realtime privilege
[19:04] <iorec> mkay, but why? since when?
[19:04] <zequence> iorec: Check if you're in audio group: groups
[19:04] <iorec> how can i check that?
[19:05] <zequence> Use the command "group" and see if "audio" is one of the results
[19:05] <zequence> groups
[19:05] <zequence> ..I mean
[19:06] <iorec> nope. apparently i am not in the audio group
[19:07] <iorec> how can i get an invite there?
[19:07] <zequence> iorec: So, Quattro is probably not usb2.0 supported, right? Which would mean, you can't get 4 I/O, as the older usb specification doesn't allow for that
[19:07] <zequence> iorec: sudo usermod -a -G audio $USER
[19:07] <zequence> The file for groups is in /etc/group
[19:07] <zequence> You can also edit it manually
[19:08] <iorec> i only uses 2 i/o's (haven't tried 4 at all)
[19:08] <zequence> On Debian, from where jack is imported, users are already members of audio group
[19:08] <iorec> *used
[19:08] <zequence> iorec: So, do you specify that in qjackctl settings?
[19:08] <iorec> yes
[19:09] <zequence> ok, well. I've tried using the quattro, only quickly, and even though it started, I got static, just cause I didn't specify I/O
[19:09] <zequence> anyway..
[19:09] <iorec> it worked for me.on and off..
[19:10] <zequence> Something that I've heard a lot is that using a Periods/Buffer of 3 is better for some usb devices
[19:10] <zequence> But, that would probably not help
[19:11] <zequence> iorec: Does it work at all with pulseaudio?
[19:11] <iorec> k, will now try to get me in that audiogroup
[19:11] <iorec> not sure about pulseaudio..
[19:11] <zequence> iorec: You'll need to log out and in again for that change to take effect
[19:12] <iorec> ok. now also waiting for the ubuntu 12.10 update to finish
[19:18] <zequence> iorec: So, whenever you try starting jackdbus, if it told you it could stop, make sure to kill it before attempting again
[19:18] <zequence> iorec: No PPAs, btw?
[19:18] <zequence> ..couldn't stop the, the previous time you tried to stop it, I mean
[19:19] <iorec> PPAs`
[19:19] <iorec> ?
[19:19] <zequence> !PPA
[19:19] <zequence> I'm getting a little tired. Been writing Wiki pages the whole day
[19:19] <iorec> you're asking if i am using one?
[19:19] <zequence> iorec: Yes
[19:20] <iorec> ok, guess not then...since i wasn't aware of them
[19:20] <iorec> well anyway thanks for your help sofar


[03:23] <user|13> Hello - I'm trying to download an older version (20.04.3) of Kubuntu, but all the links redirect to 20.04.4.
[03:23] <user|13> http://cdimage.ubuntu.com/kubuntu/releases/
[03:28] <arraybolt3[m]> user|13: Sadly, while I can find Ubuntu 20.04.3, I can't find Kubuntu 20.04.3. Is there a particular reason you need the older stack (cybersecurity testing)?
[03:30] <user|13> Yes, that and compatibility with third-party drivers.
[03:31] <arraybolt3[m]> user|13: If you can live without the KDE desktop, you may be able to use Ubuntu 20.04.3, which I can link to. If KDE is required, there might be another solution, which I'll try to help figure out.
[03:32] <user|13> KDE would be preferred, if possible.
[03:34] <arraybolt3[m]> OK. My first idea is to install Ubuntu Server 20.04.3, then install kubuntu-desktop on top of that, however that's likely to pull in a ton of updates, which kinda defeats the point. I'm trying to see if there's a way to force the use of the old version.
[03:37] <arraybolt3[m]> user|13: Shoot, I can't seem to find a way to avoid updating the whole system when pulling in KDE.
[03:37] <user|13> That might work, but having a clean image would be ideal. Any idea why the releases between 20.04 and 20.04.3 have been removed from the repo?
[03:38] <arraybolt3[m]> user|13: Probably for security. Most people need to use the most updated software in order to keep from getting hacked. But as someone doing cybersecurity, you want something that's hackable, and AFAICT, Canonical intentionally makes it tricky to make yourself hackable so that you don't get hacked by accident, which also throws a wrench in the works for those who want to get hacked on purpose.
[03:40] <arraybolt3[m]> This post has info on why they removed them: https://askubuntu.com/questions/1298239/all-kubuntu-releases (I wouldn't trust the link given for where to find all the releases, since it's an untrusted third party and may have far worse problems than just being out of date.)
[03:41] <user|13> Ack
[03:41] <arraybolt3[m]> user|13: Would Kubuntu 18.04 be sufficient for your use case? Un-updated and out of the box, that's likely to be insecure enough, and it will come with KDE.
 My tuch screen is not working
[03:42] <arraybolt3[m]> Argh, come to think of it, they probably will only have the latest point releases for that, too...
[03:43] <user|13> Yeah, I was thinking the same.
[03:44] <arraybolt3[m]> user|13: I have an idea.
[03:44] <arraybolt3[m]> user|13: Try using an EOL Ubuntu Server non-LTS release and installing kubuntu-desktop on that.
[03:45] <arraybolt3[m]> user|13: https://old-releases.ubuntu.com/releases/21.04/
[03:45] <arraybolt3[m]> Or if you need pre-20.04:
[03:45] <arraybolt3[m]> user|13: https://old-releases.ubuntu.com/releases/19.10/
[03:46] <arraybolt3[m]> Once kubuntu-desktop is installed, you should be able to install your nVidia drivers. You may have to tweak your sources.list file so you can access software (like nVidia drivers or whatever).
[03:47] <arraybolt3[m]> (Or whatever drivers you need - I'm used to "third-party driver = nVidia", but WiFi drivers should also be there... you get what I'm trying to say.)
[03:47] <user|13> Roger that. I'll give it a shot. Thanks for the assistance!
[03:48] <arraybolt3[m]> user|13: No problem. I'd give you a warning about EOL software, but as a CSec person, you probably don't need that, LOL.
[03:50] <user|13> loll
[03:51] <arraybolt3[m]> Oov: What brand and model of computer are you using? Something like "Dell Inspiron 7000" is what I'm looking for.
 Dell latitude 5480 (re @IrcsomeBot: <arraybolt3[m]> Oov: What brand and model of computer are you using? Something like "Dell Inspiron 7000" is what I'm looking for.)
 Can I turn it on from system sit or something?
[03:55] <user|13> LOL - If were still at my previous employer, then it would have definitely been a Dell. I'm on a Lenovo X1
[03:58] <arraybolt3[m]> Oov: I don't think so, you're probably missing a driver or something. Let me look up that system and see what I can find
 Ok (re @IrcsomeBot: <arraybolt3[m]> Oov: I don't think so, you're probably missing a driver or something. Let me look up that system and see what I can find)
[04:03] <arraybolt3[m]> Oov: Hmm. Can you run "xinput | nc termbin.com 9999" and send the link it spits out? This will let me see if the touchscreen is being detected or not.
[04:03] <arraybolt3[m]> (That command should be run in a terminal, which you can open with Ctrl+Alt+T.)
 https://termbin.com/8ftm
[04:06] <oerheks> https://old-releases.ubuntu.com/releases/20.04.3/
[04:06] <oerheks> oh he is gone
[04:06] <arraybolt3[m]> Oov: Aha! It is detecting your touchscreen. Maybe try mapping it to your monitor. I'm going to find the command to do that.
[04:06] <arraybolt3[m]> oerheks: He needed Kubuntu 20.04.3, not Ubuntu, sadly.
[04:08] <arraybolt3[m]> Oov: Can you run "xrandr | nc termbin.com 9999" and send me that link? This will tell me the ID of your monitor.
 https://termbin.com/dku3
[04:10] <arraybolt3[m]> Oov: OK, try this command: "xinput --map-to-output 'Melfas LGDisplay Incell Touch' eDP-1"
[04:10] <arraybolt3[m]> (The single quotes around the touchscreen name are important.)
 done
[04:12] <arraybolt3[m]> Oov: And? Does your touchscreen do stuff now?
 it is working
[04:12] <arraybolt3[m]> Oov: Nice. Last step is probably to make that command run on every boot. Let me find a good solution for that.
 ok
[04:15] <arraybolt3[m]> Oov: OK, run "nano .profile"
[04:15] <arraybolt3[m]> Oov: This will open a text editor, carefully type the xinput command from earlier on its own line at the very end of the file.
[04:16] <arraybolt3[m]> When that's done, press Ctrl+S to save, Ctrl+X to exit, then reboot and see if your touchscreen is working out of the box.
[04:16] <arraybolt3[m]> (Or... whatever, not out of the box, but you get my point. Man, I phrase stuff bad a lot.)
 lol
 ok man
[04:17] <arraybolt3[m]> 👍
 what to write after this (re @IrcsomeBot: <arraybolt3[m]> Oov: OK, run "nano .profile")
 haa (re @IrcsomeBot: <arraybolt3[m]> Oov: This will open a text editor, carefully type the xinput command from earlier on its own line at the very end of the file.)
[04:18] <arraybolt3[m]> Oov: xinput --map-to-output 'Melfas LGDisplay Incell Touch' eDP-1
 ok
 It is working
 Thanks you are the best
[04:21] <arraybolt3[m]> Oov: Fantastic!
[04:21] <arraybolt3[m]> Oov: Thanks for coming here!
 is there any way to make task bar transparent on kubuntu?
 Guys my laptop shutdown suddenly when reaches 50 percent! I think battery isnt calibration? How can i fix it?
 Hi, I've just installed Kubuntu and I get a strmge problem with samba, it's not posible to come into the folders, always get the same trobule,
 I don't have any access to folder
 I'm ussing the same cfg file, with my other linux and there will be ok
[12:25] <BluesKaj> Hi all
[12:26] <Dragnslcr> So now that it looks like Google has completely killed off Jabber connections for Chat, are there are any KDE programs that can connect to Google Chat?
[13:16] <floown> Hello. Installing a snap on KDE neon, and so on in Kubuntu, does'nt create a menu entry in Kickoff, or I do somethings wrong? Thanks.
[15:03] <floown> Hi! Which tool to search and find a file or set of files on various partitions in one step?
[15:09] <floown> Ok, Kfind do the job well
[19:23] <R13ose> When I try to open browser links to applications the link is not opening the application or doing anything.  Did I change settings that I need to revert?
[19:30] <mmikowski_> R13ose: What is the link? Can you paste the address here?
[19:32] <R13ose> I'm trying to open Zoom links.  So I will click the link and then it will popup a box that allows me to open the link in the Zoom application but when I click that, this doesn't nothing.
[19:44] <oerheks> zoom plugin in your browser?
[19:50] <R13ose> I don't use any zoom plugin in my browser
[19:51] <oerheks> now it does not work..
[19:52] <oerheks> zoom can do perfect browser crashes too
[19:53] <R13ose> Wonderful
[20:32] <mmikowski_> R13ose: Zoom can work with the browser fine.  We did integration work for the Kubuntu Focus.
[20:33] <R13ose> My last zoom meeting was done in the browser but want to make the application work again too.
[20:33] <mmikowski_> My first guess is you need to upgrade the zoom that you have installed. It does NOT upgrade automatically, and the older version had a broken electron container shortcut.
[20:35] <mmikowski> Let me check, but that alone should fix it; just download the zoom package from the site and install it again.
[20:39] <mmikowski> R13ose: Confirmed. The Kfocus team used to provide a wrapper for Zoom to fix the issue, but that is no longer needed and just updating shoud fix it.
[20:40] <R13ose> mmikowski: which Zoom version would I need to be at?
[20:44] <mmikowski> Mine show <IP_ADDRESS>11, and that works. Whatever is the latest from their site should be the same or greater than that.  Zoom Ubuntu Linux support is actually quite good, although it would be nice to see it auto-upgrade through a repo. We'll add that if it comes available.
[20:44] <mmikowski> We = Kubuntu Focus team :) Zoom is not officially supported by Kubuntu for obvious reasons.
[20:46] <R13ose> mmikowski: My Zoom version is at 5.11.0 (3540) which I download from the Zoom website whenever check my update says there's a new update.
[20:49] <Eickmeyer> R13ose: Which version of Kubuntu are you running?
[20:49] <Eickmeyer> !yy.mm
[20:50] <R13ose> Eickmeyer: 22.04
[20:50] <Eickmeyer> Ok, just checking.
[20:51] <Eickmeyer> Also, FYI: Third-party apps from outside of the repository are not supported here, so you may need to seek support from Zoom, R13ose.
[20:55] <R13ose> Eickmeyer: totally understand.  This is a totally Zoom issue and not an overall I did something wrong with Kubuntu or all applications are broken when opening links from browsers?
[20:55] <Eickmeyer> R13ose: A reinstall of Zoom could go a long way to fixing the link association issue.
[20:56] <mmikowski> R13ose: So that should be good. You may want to look at file associations and make sure x-zoom is there. And yes, you will want try other link types.
[20:57] <R13ose> Eickmeyer: as a last resort, I will do that.
[20:58] <Eickmeyer> R13ose: To be honest, it's really safe as there are basically no settings that will get overwritten by doing that, aside from fixing the file/link associations. I'd do that first.
[20:58] <enigma9o7[m]> try reinstalling as a last resort?
[20:58] <R13ose> Yep
[20:58] <enigma9o7[m]> thats one of the easiest things to try, but unlikely to do anything anyway.
[20:58] <R13ose> I will do that now :)
[20:59] <R13ose> mmikowski: I looked into x-zoom and that's there.  Which file/link association would be do the same to test?
[21:00] <Eickmeyer> R13ose: Best thing to do is reinstall Zoom to get the file/link associations back. It's hard to say what got it messed up.
[21:00] <Eickmeyer> It's safe to try.
[21:06] <R13ose> I uninstalled and reinstalled and still browsers are not pointing to that.
[21:13] <Eickmeyer> R13ose: https://askubuntu.com/questions/1410174/how-to-open-zoom-meeting-link-in-firefox-in-ubuntu-22-04
[21:15] <R13ose> Thanks Eickmeyer
[21:19] <R13ose> Eickmeyer: to let you know, this happened in another browser.
[21:20] <Eickmeyer> R13ose: Yeah, no idea then.
[21:20] <R13ose> I'm talking to Zoom now :)  Thanks everyone for your help.
[21:34] <R13ose> The issue for the other browser was that I needed to close and re-open for some reason.  I will see what they say about Firefox.
[21:44] <R13ose> With Firefox seems to be a wide issue that is already posted multiple places so I will let others figure that out as I don't use Firefox that often.
[21:50] <cbreak> the new snap firefox is a pain in the ass with interoperability
[21:51] <enigma9o7[m]> ya it seems there certainly wasnt enough testing before forcing it upon everyone
[21:53] <oerheks> firefox was a snap in 21.10 too?
[21:54] <oerheks> and all zoom users and forumposts point to the use of the official zoom plugin for your browser.
[21:57] <enigma9o7[m]> I think with 21.10 it started out as deb package, and then at some point new installs starting trying the snap
[23:04] <cbreak> oerheks: no
[23:04] <cbreak> I had native firefox in 21.10
[23:35] <luis_> Heloo heloo
[23:35] <arraybolt3[m]> luis_: Hello, and how can we help you?
[23:36] <luis_> i am trying to bypass ipad 2nd gen's activation lock using linx since its the only way that works on ios 9, im on kubuntu with TDE installed as its desktop environment
[23:37] <luis_> but it wont load up
[23:37] <oerheks> byassing ipads locks is not the scope of this channel.
[23:37] <arraybolt3[m]> luis_: Hmm. Sadly, I don't think this is a Kubuntu support question, since it's a problem with iOS, not Kubuntu in particular. You might have luck on the r/jailbreak subreddit.
[23:37] <arraybolt3[m]> (If that's what you're trying to do.)
[23:37] <enigma9o7[m]> Is it kubuntu that wont load up?
[23:38] <enigma9o7[m]> or what is "it"?
[23:38] <oerheks> we cannot tell you are the genuine owner, good luck dude.
[23:38] <arraybolt3[m]> (I don't actually know what an ipad activation lock is.)
[23:38] <oerheks> some got linux running on an ipad recently, but that is also offtopic.
[23:53] <luis_> welp guys i think thats gonna wrap it up. my ipad just bricked and had smoke coming out of it for a while but it stopped
[23:53] <luis_> so yea thats the end of the ipad and  i am going to dispose of it and probably buy a 1st gen instead /:
[23:54] <luis_> god damn it