[02:28] <chrismsnz> Hi guys, I'm running 10.04 LTS on a group of servers and I'm having some trouble when it comes under high load
[02:29] <chrismsnz> the system becomes unstable and will sometimes go into a state where it responds to basic network access (i.e. ping, accepting connection) but nothing further and for all intents and purposes is down/dead
[02:30] <chrismsnz> I have a system in this state at the moment, and it's fairly easy to trigger the problem (it just takes a trip out to the colo to kick them in the pants when it happens).
[02:30] <chrismsnz> How would I start collecting data to file this as a bug report?
[02:31] <chrismsnz> is ubuntu-bug -p linux the best way to get underway?
[02:32] <RAOF> chrismsnz: Yes, that's generally a good start.
[02:32] <chrismsnz> so rebooting the server and running ubuntu-bug will pick up the old dmesg and everything?
[02:33] <bryceh> chrismsnz, check dmesg for error messages
[02:33] <bryceh> chrismsnz, no you have to run it while system is frozen
[02:34] <bryceh> chrismsnz, if it is a gpu hang, you should also gather intel register dumps as well, although frankly it's unlikely gpu hang fixes will get done for lucid.  But who knows.
[02:34] <bryceh> EOD, cya.
[02:35] <chrismsnz> right
[02:37] <chrismsnz> I actually had installed a newer kernel on this particular system to see if the problem was solved - but it was not
[02:37] <chrismsnz> I will include in bug report, thanks guys
[07:22] <smb> morning
[07:26] <abogani> smb: morning
[10:59]  * ppisati -> out for lunch
[11:40] <RAOF> apw: Could I trouble you for a kernel build with the patch from bug #753994 ?
[11:40] <ubot2> Launchpad bug 753994 in linux "[arrandale] Display is slanted when using 1360x768 resolution" [Medium,Confirmed] https://launchpad.net/bugs/753994
[12:01] <apw> RAOF, sure
[12:01] <apw> RAOF, for what series
[12:08] <apw> RAOF, ok found it, assuming natty, will let you know when its done
[12:18] <ohsix> herton: hi, i'm the guy on #793796, is this patch related to it? https://patchwork.kernel.org/patch/837692/ it's in the -11 package that just hit proposed; i won't have time to test it for a bit
[12:20] <herton> ohsix: hi. yes, the patch is related, but it wasn't sufficient to fix your case. you need also the 0004 and 0005 patches from http://people.canonical.com/~herton/lp793796/r5/
[12:21] <ohsix> ok, i read the one that was in r6 and that looked like the same, but percolated up
[12:21] <herton> ohsix: upstream did another patch trying to not having to add a lot of tests for dead queues on elevator, it was the last kernel you tested, but it didn't work. I reported your test on upstream bug report, but there is no response yet
[12:22] <ohsix> nod, saw that
[12:22] <ohsix> just saw it in -11 and figured some wizard might have just bypassed it all :}
[12:23] <herton> unfortunately no. still you shouldn't see the issues on -11 kernel as we kept reverted the patches that caused the problem for you, so you can use the new kernel
[12:25] <ohsix> those are just reverts right? who committed the patches? shouldn't be too hard to get them to try unplugging a usb drive :]
[12:27] <herton> yep, it just reverts the commit we found on bisect, plus also reverts the followup fixes to this first commit reverted
[12:30] <herton> ohsix: the reverts are being tracked on bug 802986
[12:30] <ubot2> Launchpad bug 802986 in linux "Revert upstream scsi run queue changes" [Undecided,In progress] https://launchpad.net/bugs/802986
[12:34] <ohsix> hm, didn't know about that one, thanks
[12:34] <ohsix> i'm surprised i haven't heard of a thread on the lkml about it or something
[12:38] <herton> I think there was a thread only in linux-scsi, from where the patch in r6 you tested came from, and bug https://bugzilla.kernel.org/show_bug.cgi?id=38842 is in the regressions list that is frequently posted on lkml
[12:38] <ubot2> bugzilla.kernel.org bug 38842 in Other "panic in elv_completed_request on safe remove usb hard drive" [High,Needinfo]
[12:43] <ohsix> i hope people look at the lp bug for the simple reproduction steps, instead of getting the virtual machine image D:
[12:53] <apw> RAOF, ok kernels build and published in the bug
[12:59] <apw> smb, hey where do you get old isos from
[13:00] <smb> old isos of what exactly?
[13:00] <apw> hardy for instance
[13:00] <smb> http://release.ubuntu.com
[13:00] <apw> i happen to have other releases lying around
[13:00] <smb> err
[13:00] <smb> releases
[13:02] <smb> apw, If course that only gives you latest point release and release for lts. if that is ok
[13:02] <apw> yeah just something old enough :)
[13:03] <smb> apw, could probably ship you gutsy... ;-P
[13:06] <apw> smb, so very kind
[13:08] <smb> apw, Heh, though you would be appreciating. Btw, where you want to install hw-wise. Usually hardy fails on NICs or wireless (if recent)
[13:08] <apw> on a netbook, any chance ?
[13:10] <smb> hm. could already be questionable as they always slam in latest stuff... it seems ok on the dell 1521 which has some broadcom...
[13:10] <smb> (not that you could call that recent)
[13:10] <apw> smb, well i guess i'll give it a shot and see what happens
[13:11] <smb> Yeah, you will notice quite early when the install complains about the network setup failed
[13:18] <jwi> bugs related to -virtual kconfig: 720644, 769527, 771855, 794570, 761809, 658461 </braindump>
[13:27] <apw> bug #720644 bug #769527 bug #771855 bug #794570 bug #761809 bug #658461
[13:27] <ubot2> Launchpad bug 720644 in linux "linux-virtual kernel does not allow network configuration via kernel command line" [Undecided,Confirmed] https://launchpad.net/bugs/720644
[13:27] <ubot2> Launchpad bug 769527 in linux "Missing rpcsec_gss_krb5 module" [Undecided,New] https://launchpad.net/bugs/769527
[13:27] <ubot2> Launchpad bug 771855 in linux "reiserfs module missing in linux-image-virtual" [Undecided,New] https://launchpad.net/bugs/771855
[13:27] <ubot2> Launchpad bug 794570 in linux "igbvf driver is missing from virtual-flavored kernel" [Medium,Triaged] https://launchpad.net/bugs/794570
[13:27] <ubot2> Launchpad bug 761809 in linux "Quota modules are missing from the package" [Undecided,Incomplete] https://launchpad.net/bugs/761809
[14:00] <bjf> ##
[14:00] <bjf> ## Ubuntu Kernel Team Meeting - Today @ 17:00 UTC - #ubuntu-meeting
[14:00] <bjf> ##      agenda: https://wiki.ubuntu.com/KernelTeam/Meeting
[14:00] <bjf> ##
[14:00] <bjf> J
[14:03] <apw> bjf thanks for the reminder
[14:04] <bjf> apw, and this one only once :-)
[14:04] <apw> its hard to remember its tue when its your first day of the week
[14:04] <ogasawara> bjf: I liked the morning bug report
[14:05] <ogasawara> bjf: sending it 50 times really made sure I looked at it :)
[14:05] <bjf> ogasawara, heh
[14:06]  * smb was already worried somebody sent a lot of patches...
[14:06] <bjf> hey! we take our bugs seriously!
[14:06] <ogasawara> smb: hehe, I had the same feeling for a second
[14:47]  * ogasawara back in 20
[14:49] <ogasawara> whoa, he put himself back to sleep.  lets see how long this lasts...
[14:52] <apw> ogasawara, not long :)
[15:00] <ogasawara> short lived indeed
[15:00]  * ogasawara back in 20
[15:30] <vanhoof> herton: heya
[15:30] <herton> vanhoof: hi
[15:30] <vanhoof> herton: quick q
[15:30] <vanhoof> herton: bug 774947
[15:30] <ubot2> Launchpad bug 774947 in linux "[Lenovo Edge 11 AMD] system locks up completely running the "stress" tool" [Medium,Fix released] https://launchpad.net/bugs/774947
[15:30] <vanhoof> that fix came through 2.6.38 -stable, and landed in last weeks <IP_ADDRESS> kernel
[15:31] <vanhoof> anything I need to do with it at this point? (just looking at the most recent update that was popped in there)
[15:31] <herton> vanhoof: in fact it was applied by hand, doesn't have a buglink to a stable update tracking bug
[15:32] <herton> let me check here if it was included in a stable update
[15:33] <vanhoof> herton: ah ok, thought it was from the dialog in the bug
[15:33] <apw> vanhoof, why have you closed the natty task for that bug ?  you say its cause 2.6.38-10 was released but that only contains <IP_ADDRESS>
[15:34] <vanhoof> apw: based on the testing that was done on -10, so I assumed this trickled down in <IP_ADDRESS>
[15:35] <apw> vanhoof, but you just said some 10 lines back that it was only in last weeks 38.10
[15:35] <apw> which isn't in 38-10
[15:35] <vanhoof> apw: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/774947/comments/31
[15:35] <ubot2> Ubuntu bug 774947 in linux "[Lenovo Edge 11 AMD] system locks up completely running the "stress" tool" [Medium,Fix committed]
[15:35] <vanhoof> thats what I'm going with here
[15:35] <vanhoof> if its in <IP_ADDRESS>, I'll flip it back to fix commited
[15:36] <apw> vanhoof, well if the fix is in that kernel then all is good, but thats the right reason to change the state to released
[15:37] <vanhoof> looks like it was just those fixed on-top of -10
[15:37] <herton> vanhoof: right, same fix came with <IP_ADDRESS>, I'll update the bug there, you don't need to verify
[15:37] <vanhoof> herton: cool, i flipped it back to fix commited then
[15:37]  * vanhoof mis-interpreted the testing comment, and thought it was on the -proposed kernel
[15:38] <apw> apw@dm$ git describe --contains 9ee653dce0efc6bad29f0d68b4ac74dbed093131
[15:38] <apw> Ubuntu-2.6.38-11.47~159
[15:38] <apw> as far as i can see the commit is not yet released, it is Fix Committed only
[15:38] <vanhoof> right
[15:38] <vanhoof> which I just set it back to
[15:38] <apw> and as it is correcelyt marked
[15:38] <apw> it should close itself when it releases
[15:39] <vanhoof> apw: we get a few bugs where it's just waiting on some fix in -stable, like this one, didn't know if it would be automagically closed out
[15:39] <vanhoof> in any event, we're good
[15:40] <apw> vanhoof, no often it won't get picked up if its not known before we apply stable
[15:40] <vanhoof> apw: yeah I assumed this was the case, and mis-interpreted the test results that were posted as 'fixed in -proposed' :)
[15:56] <bjf> ##
[15:56] <bjf> ## Kernel team meeting today @ 17:00 UTC
[15:56] <bjf> ##
[16:08] <cking> i'm still confused by bug 774947 - do we need to test or not? the commit is in the -proposed kernel right?
[16:08] <ubot2> Launchpad bug 774947 in linux "[Lenovo Edge 11 AMD] system locks up completely running the "stress" tool" [Medium,Fix committed] https://launchpad.net/bugs/774947
[16:19] <herton> cking: you don't need to test, yes the commit is on proposed
[17:00] <bjf> ##
[17:00] <bjf> ## Meeting starting now
[17:00] <bjf> ##
[17:30]  * bjf -> dr. appt.
[18:04] <kees> apw: none of the hardy linux CVE fixes show up in the tracker with a specific version...
[18:04] <apw> kees, got an example
[18:04] <kees> grep ^hardy_linux: CVE-2011-1170 CVE-2011-1171 CVE-2011-1172 CVE-2011-1173 CVE-2011-2534 CVE-2010-4649 CVE-2010-4073 CVE-2010-4238 CVE-2011-2484 CVE-2010-4165 CVE-2010-4249 CVE-2011-1010 CVE-2011-0711 CVE-2011-1090
[18:04] <ubot2> kees: net/ipv4/netfilter/arp_tables.c in the IPv4 implementation in the Linux kernel before 2.6.39 does not place the expected '\0' character at the end of string data in the values of certain structure members, which allows local users to obtain potentially sensitive information from kernel memory by leveraging the CAP_NET_ADMIN capability to issue a crafted request, and then reading the argument to the resulting modprobe process. (http://
[18:04] <ubot2> kees: net/ipv4/netfilter/ip_tables.c in the IPv4 implementation in the Linux kernel before 2.6.39 does not place the expected '\0' character at the end of string data in the values of certain structure members, which allows local users to obtain potentially sensitive information from kernel memory by leveraging the CAP_NET_ADMIN capability to issue a crafted request, and then reading the argument to the resulting modprobe process. (http://c
[18:04] <ubot2> kees: net/ipv6/netfilter/ip6_tables.c in the IPv6 implementation in the Linux kernel before 2.6.39 does not place the expected '\0' character at the end of string data in the values of certain structure members, which allows local users to obtain potentially sensitive information from kernel memory by leveraging the CAP_NET_ADMIN capability to issue a crafted request, and then reading the argument to the resulting modprobe process. (http://
[18:04] <ubot2> kees: The econet_sendmsg function in net/econet/af_econet.c in the Linux kernel before 2.6.39 on the x86_64 platform allows remote attackers to obtain potentially sensitive information from kernel stack memory by reading uninitialized data in the ah field of an Acorn Universal Networking (AUN) packet. (http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2011-1173)
[18:05] <kees> aaarggh
[18:05] <ubot2> kees: Buffer overflow in the clusterip_proc_write function in net/ipv4/netfilter/ipt_CLUSTERIP.c in the Linux kernel before 2.6.39 might allow local users to cause a denial of service or have unspecified other impact via a crafted write operation, related to string data that lacks a terminating '\0' character. (http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2011-2534)
[18:05] <ubot2> kees: Integer overflow in the ib_uverbs_poll_cq function in drivers/infiniband/core/uverbs_cmd.c in the Linux kernel before 2.6.37 allows local users to cause a denial of service (memory corruption) or possibly have unspecified other impact via a large value of a certain structure member. (http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2010-4649)
[18:05] <ubot2> kees: The ipc subsystem in the Linux kernel before 2.6.37-rc1 does not initialize certain structures, which allows local users to obtain potentially sensitive information from kernel stack memory via vectors related to the (1) compat_sys_semctl, (2) compat_sys_msgctl, and (3) compat_sys_shmctl functions in ipc/compat.c; and the (4) compat_sys_mq_open and (5) compat_sys_mq_getsetattr functions in ipc/compat_mq.c. (http://cve.mitre.org/cgi-bi
[18:05] <ubot2> kees: The vbd_create function in Xen 3.1.2, when the Linux kernel 2.6.18 on Red Hat Enterprise Linux (RHEL) 5 is used, allows guest OS users to cause a denial of service (host OS panic) via an attempted access to a virtual CD-ROM device through the blkback driver.  NOTE: some of these details are obtained from third party information. (http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2010-4238)
[18:05] <ubot2> kees: The add_del_listener function in kernel/taskstats.c in the Linux kernel <IP_ADDRESS> and earlier does not prevent multiple registrations of exit handlers, which allows local users to cause a denial of service (memory and CPU consumption), and bypass the OOM Killer, via a crafted application. (http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2011-2484)
[18:05] <ubot2> kees: The do_tcp_setsockopt function in net/ipv4/tcp.c in the Linux kernel before 2.6.37-rc2 does not properly restrict TCP_MAXSEG (aka MSS) values, which allows local users to cause a denial of service (OOPS) via a setsockopt call that specifies a small value, leading to a divide-by-zero error or incorrect use of a signed integer. (http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2010-4165)
[18:05] <ubot2> kees: The wait_for_unix_gc function in net/unix/garbage.c in the Linux kernel before 2.6.37-rc3-next-20101125 does not properly select times for garbage collection of inflight sockets, which allows local users to cause a denial of service (system hang) via crafted use of the socketpair and sendmsg system calls for SOCK_SEQPACKET sockets. (http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2010-4249)
[18:05] <ubot2> kees: Buffer overflow in the mac_partition function in fs/partitions/mac.c in the Linux kernel before <IP_ADDRESS> allows local users to cause a denial of service (panic) or possibly have unspecified other impact via a malformed Mac OS partition table. (http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2011-1010)
[18:05] <ubot2> kees: The xfs_fs_geometry function in fs/xfs/xfs_fsops.c in the Linux kernel before 2.6.38-rc6-git3 does not initialize a certain structure member, which allows local users to obtain potentially sensitive information from kernel stack memory via an FSGEOMETRY_V1 ioctl call. (http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2011-0711)
[18:05] <ubot2> kees: The __nfs4_proc_set_acl function in fs/nfs/nfs4proc.c in the Linux kernel before 2.6.38 stores NFSv4 ACL data in memory that is allocated by kmalloc but not properly freed, which allows local users to cause a denial of service (panic) via a crafted attempt to set an ACL. (http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2011-1090)
[18:05] <bliss> AAHHHHH
[18:05] <kees> apw: anyway, all of those CVEs are just "pending" without versions
[18:05] <apw> kees, hardy_linux: pending (2.6.24-29.92)
[18:06]  * kees does an update....
[18:06] <apw> apw@dm$ grep ^hardy_linux: active/CVE-2011-1170
[18:06] <ubot2> apw: net/ipv4/netfilter/arp_tables.c in the IPv4 implementation in the Linux kernel before 2.6.39 does not place the expected '\0' character at the end of string data in the values of certain structure members, which allows local users to obtain potentially sensitive information from kernel memory by leveraging the CAP_NET_ADMIN capability to issue a crafted request, and then reading the argument to the resulting modprobe process. (http://c
[18:06] <apw> pending without a version should mean Fix Commited but not uploaded yet
[18:06] <bliss> kees: make sure that xfs fix comes with the fix to the regression it caused
[18:07] <kees> apw: oh, ha-ha, we're out of sync with you. fixing, please ignore me...
[18:07]  * bliss bows his head in shame
[18:07] <apw> kees, np
[18:07] <kees> bliss: do you have a pointer for it?
[18:09] <bliss> i'll find the commit
[18:09] <kees> bliss: do you mean CVE 2011-0711 ?
[18:09] <ubot2> kees: The xfs_fs_geometry function in fs/xfs/xfs_fsops.c in the Linux kernel before 2.6.38-rc6-git3 does not initialize a certain structure member, which allows local users to obtain potentially sensitive information from kernel stack memory via an FSGEOMETRY_V1 ioctl call. (http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2011-0711)
[18:09] <kees> gah, I can't avoid the bot
[18:09] <bliss> yes, that's the bug
[18:09] <bliss> my fix was broken
[18:09] <bliss> i content their code was broken and my fix revealed it, but that's an argument for another day
[18:09] <bliss> contend*
[18:09] <kees> bliss: heh. it's just a memset though?
[18:10] <bliss> yeah
[18:10] <bliss> but they cast a structure to a larger size in a function call
[18:10] <bliss> so the memset caused an overflow
[18:10] <kees> *ew*
[18:10] <bliss> yes, i wrote the patch, but that was clearly their fault
[18:11] <apw> that rings a bell, we may have gotten both but worth checking
[18:11] <kees> http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=af24ee9ea8d532e16883251a6684dfa1be8eec29
[18:12] <kees> bliss: yup, looks like we've got it.
[18:12] <apw> those sha1s even look familiar
[18:13] <apw> yeah we have both marked in the tracker as needed, so we are good
[18:13]  * kees nods
[18:38] <kees> hggdh: I have a question for you about q-r-t and updates... I want to add a test for something that hasn't been fixed yet. since we no longer fix CVEs in lock-step across all releases, I don't have a good way to avoid having the test fail. any thoughts on how to add a test that isn't a regression "yet"?
[18:40] <hggdh> hum
[18:40] <hggdh> the easy way out: let it fail -- I always verify the results
[18:41] <hggdh> another option, bit more involved -- set up a table of fixed releases (and versions) and compare against
[18:41] <hggdh> kees: ^
[18:42] <kees> hggdh: yeah, we're going to need this going forward, so probably the table is the best solution. I will ponder how to best implement it. thanks!
[18:43] <hggdh> the only thing is this is probably going to explode, too many CVEs against too many different packages :-(
[18:44] <kees> heh
[18:44] <kees> hggdh: well, we have some of the data in the CVE tracker, so I'm just going to ponder how to avoid duplicating it.
[18:45] <hggdh> if the cve tracker is API-accessible by anyone...
[18:46] <hggdh> we could just grab the data on run time. If not accessible, I am not sure it is a good idea
[18:54] <kees> jhunt_: hello!
[18:55] <jhunt_> kees: hi.
[18:55] <kees> jhunt_: so, we were trying to figure out exactly what the changed behavior was so we could reproduce it.
[18:55] <kees> jhunt_: without that, we were kind of stuff. we've been looking at another set of related changes, but I couldn't find fd/-specific stuf
[18:55] <kees> *stuff
[18:56] <jhunt_> well, to be clear, I'm not 100% sure what's happening yet. So, I'd really like to know what is expected behavior wrt a root process calling setuid and attempting to open /proc/self/fd/* directly.
[18:57] <apw> i'd have expected /fd/ to continue to work, as you already have those fds open
[18:57]  * kees nods
[18:57] <kees> "self" should always be able to read its own fds I would imagine
[18:58] <jhunt_> I've got a noddy test program that attempts this and on lucid, the process can only open /proc/self/fd/0 whereas on natty+oneiric, you can open /proc/self/fd/[012]. Any fd higher than 2 gives EPERM.
[18:59] <jhunt_> apw: right. And I still think I might be going made, but the upstart session code that falls into this scenario *used* to work (on natty). however, I now cannot make the same code work on either natty or oneiric which made me think maybe a kernel or security change might be affecting things.
[18:59] <jhunt_> s/made/mad :)
[18:59] <jhunt_> (see, I'm mad me :)
[18:59] <apw> jhunt_, perhaps you could send us the test code so we can look it over
[19:00] <jhunt_> will do...
[19:00] <apw> kees, this fix:     UBUNTU: SAUCE: proc: hide kernel addresses via %pK in /proc/<pid>/stack
[19:00] <apw>     UBUNTU: SAUCE: proc: hide kernel addresses via %pK in /proc/<pid>/stack
[19:00] <apw> kees, whats the gen with that
[19:00] <kees> "gen" ?
[19:01] <apw> kees, the history, the background?
[19:01] <apw> it looks like a security related change, which we have from mainline in oneirc, backport from you in natty, but not in maverick
[19:02] <kees> apw: right, so, it's an upstream improvement for continuing to lock down things that should be hidden with %pK
[19:02] <kees> apw: it doesn't need backporting as far as I'm concerned. (i.e. I already backported it to natty which was the first the have %pK)
[19:03]  * bliss cheers
[19:03] <apw> kees, ah ok, fair enough, i'll drop teh K in the backport before that then
[19:04] <jhunt_> apw, kees: code should with you now.
[19:06] <kees> apw: I'm not sure what you mean?
[19:07] <kees> jhunt_: thanks
[19:07] <jhunt_> kees: np
[19:09] <apw> kees, just trying to introduce a %pK too early is all
[19:09] <kees> apw: ah-ha, okay
[19:22]  * jjohansen -> lunch
[19:23] <bjf> ogasawara, can you see if you can still get to the "site admin" page on voices.canonical.com? i'm not able to any more so no more blog postings for me
[19:23] <ogasawara> bjf: lemme check, just a sec
[19:24] <ogasawara> bjf: works for me, want me to post the meeting minutes?
[19:24] <bjf> ogasawara, sure, i'll pastebin them
[19:25] <bjf> ogasawara, http://pastebin.ubuntu.com/647561/
[19:26] <apw> bjf what error you get ?  internal server error?
[19:27] <bjf> apw, You do not have sufficient permissions to access this page.
[19:27] <apw> bjf odder and odder
[19:27] <ogasawara> bjf: cool, posted
[19:28] <bjf> ogasawara, thanks
[19:28] <ogasawara> apw: weren't you getting some error as well?
[19:28] <apw> bjf, nice ... i am still getting internal server error whenever i try
[19:28] <apw> we'll run out of people who can soon
[19:29] <bjf> apw, jjohansen is the community guy now, maybe only he can :-)
[19:29] <apw> bjf he will be so pleased to hear that
[19:43] <jjohansen> oh yeah so very pleased
[19:47] <jhunt_> apw, kees: just seen http://bit.ly/nRONfB which suggests the problem I'm seeing cannot be entirely caused by the /proc/self/fd/ behaviour. I'll do some more debug tomorrow and keep you posted...
[19:47] <kees> jhunt_: fwiw, even maverick shows this as a perm failure
[19:50] <jhunt_> kees: ok, thx.
[20:01] <sconklin> manjo: I'm sorry I snapped at you yesterday.
[20:01] <manjo> sconklin, hey no worries man
[20:02] <manjo> sconklin, reason I asked you the Q was ... the patch is in 3.1... I was not sure if there was a scheme to get patches down before it hit stable (which might take a few weeks)
[20:03] <manjo> sconklin, I will push thro sru process once it gets in the 3.1 tree, its got acks from most mainitaners now
[20:03] <sconklin> no, there's no scheme, and in general it's always better to just go ahead and get it out onto the mailing list instead of discussing it on IRC then having to rehash it in email
[20:04] <manjo> right .. will do
[20:06] <sconklin> and I owe you a beer. Now, who wants to be snapped at next ;-)
[20:06] <manjo> sconklin, :) no worries.. you don't 'owe' me...
[20:44] <hacksaw> I was just doing some maintenance, and therefore performing basic package updates on my 10.04 box. The explanation of why the kernel is being updated is "Bump ABI". Can anyone explain why I want to take my machine down as a result of this message? Does it mean something?
[20:45] <apw> hacksaw, that sounds like a bug in the changlog generator for update-manager ... whats the version you are being offered
[20:46] <hacksaw> <IP_ADDRESS>.39
[21:20] <bjf> tgardner, when do you want to get into the office?
[21:20] <tgardner> bjf, I should be by 0800
[21:20] <tgardner> be here*
[21:21] <bjf> tgardner, sconklin is trying to setup a mumbe meeting, you see that?
[21:21] <tgardner> bjf, yeah, but 0700 seems a bit early
[21:22] <tgardner> bjf, speaking of mumble, I'd better make sure it works on my laptop. I've been having some problems.
[21:43] <hacksaw> Okay, apw, I'm going to assume someone will look at the potential changelog bug, and make corrections in time.
[21:51] <bjf> ogasawara, we are going to try to get into the office by 8:00 a.m., that work for you?
[21:55] <ogasawara> bjf: I'll probably come in a little later then since Kai gets up around 8am.  be in likely by 9am.
[21:55] <bjf> ogasawara, sounds good


[03:52] <superm1> xivulon, for our daily builds process, is there a URL that will pull the latest wubi in all instances to make sure we get that on mythbuntu disks?
[03:53] <superm1> 514 appears to work correctly (at least using an ISO in the same directory) for me
[08:59] <xivulon_> davmor2, would you mind testing http://wubi-installer.org/devel/minefield/Wubi-8.10-rev515.exe as stand-alone?
[09:01] <davmor2> xivulon_: Yeap can do.
[09:24] <evand> cjwatson: usb-creator uploaded
[09:24] <cjwatson> thanks
[09:24]  * evand reads the rest of the scollback
[09:25] <davmor2> xivulon: did you see the bugs coming through about issues with updating wubi?
[09:27] <xivulon> evand I have a rev 515 for wubi, including mythbuntu verification key/artwork and new translations
[09:27] <xivulon> I left a msg for slangasek in #ubuntu-release yesterday night not sure if he saw that
[09:28] <xivulon> I also have a new rev for umenu adding mythbuntu. it's not critical for that to be on the ubuntu CD of course. I noticed that there are some new translations but did not get the tgz from rosetta yet.
[09:30] <xivulon> davmor2, do you mean kernel upgrades to fat32? yes I am aware of that. Changes will be too invasive, we'll do it in next release and publish a workaround
[09:31] <davmor2> https://bugs.launchpad.net/bugs/258379
[09:31] <davmor2> xivulon: ^
[09:31] <xivulon> ah no did not see that
[09:31] <CIA-2> usb-creator: evand * r50 usb-creator/debian/changelog: releasing version 0.1.10
[09:32] <xivulon> yes I did
[09:33] <xivulon> I asked for more info but did not get a reply
[09:34] <xivulon> davmor2, it would be good though to try and upgrade wubi 8.04.1 to 8.10, just in case
[09:34] <davmor2> xivulon: Yeah no probs I'll do that after rev515 test
[09:34] <xivulon> cool
[09:35] <davmor2> I got a feeling it might be the new uuid naming do loops keep the same id?
[09:36] <evand> persia> it's probably missing features rather than a bug.  The linux support is a bit lacking, but it's not as simple as just cp -r as it needs to be able to merge from multiple sources.
[09:36] <xivulon> uuid is used for the root device, and it should be the same issue whether he is using wubi or not
[09:37] <xivulon> in the case of wubi the root device is then mount moved as /host, but if you cannot mount in the first place, it should not be a wubi issue
[09:48] <evand> cjwatson: thanks for the fix on 287547
[09:49] <cjwatson> not a problem, wasn't doing anything else while on the train ...
[10:01] <davmor2> xivulon: right rev515 up and running any preference as to install?
[10:02] <xivulon> davmor2 what would be the options?
[10:03] <davmor2> Ubuntu/Kubuntu/Xubuntu/Mythbuntu
[10:04] <davmor2> xivulon: ^
[10:05] <persia> evand, ?  ENOCONTEXT
[10:07] <evand> persia: sorry, the migration-assistant issue
[10:07] <evand> whereby it didn't offer to import anything
[10:07] <cjwatson> xivulon: is wubi supported on DVDs?
[10:08] <cjwatson> (just yes/no, I'm not saying we should add it if it isn't there already; proof-reading DVD sleeve text)
[10:08] <persia> evand, Oh, right.  No worries then.  If it's not supposed to do that, no need to keep the traces :)
[10:09] <evand> cjwatson: no, we removed it a long time ago on cdimage because it's horrendously slow
[10:09] <xivulon> yep extracting a 4GB ISO does not sound like a good idea
[10:10] <evand>                         if [ "$CDIMAGE_DVD" != 1 ]; then
[10:10] <evand>                                 (fetch "$(find-live-filesystem "$arch" wubi)" \
[10:10] <evand>                                         "$LIVE_OUT/$arch.wubi.exe" || true)
[10:10] <evand>                         fi
[10:11] <evand> umenu is on the DVD though
[10:18] <davmor2> xivulon: So any preference as to which desktop I install?
[10:25] <davmor2> xivulon: myhtbuntu fails but I'm guessing that is the key issue from earlier
[10:27] <xivulon> davmor2: to install mythbuntu you need to have a mythbuntu backend running
[10:27] <xivulon> that only installs the frontend
[10:27] <davmor2> xivulon: ah right :)
[10:27] <xivulon> davmor2: go for ubuntu
[10:27] <davmor2> ubuntu is installing as we speak
[10:40] <xivulon> cool, they haven't upload the metalink / metalink md5 and signature yet for mythtv so cannot test that (I tested the key separately via gpgv though)
[11:01] <CIA-2> usb-creator: evand * r51 usb-creator/ (bin/usb-creator setup.py): Bump to 0.1.11
[11:02] <CIA-2> usb-creator: evand * r52 usb-creator/ (debian/changelog usbcreator/backend.py):
[11:02] <CIA-2> usb-creator: Strip null bytes from the CD label when parsing it from an ISO file
[11:02] <CIA-2> usb-creator: (LP: #287318).
[11:06] <davmor2> xivulon: 1 Ubuntu install everything seems fine
[11:20] <xivulon> davmor2: thx, pls let me know if you have any issue upgrading from 8.04.1 -> 8.10
[11:20] <davmor2> xivulon: np's that's next :)
[11:46] <xivulon> given that the dates are a bit tight, is there a possibility that 8.10 becomes 8.11? As the version number is hardcoded in wubi/umenu.
[11:48] <cjwatson> extremely unlikely.
[12:02] <CIA-2> usb-creator: evand * r53 usb-creator/ (3 files in 3 dirs):
[12:02] <CIA-2> usb-creator: * Fix small issue where enlarging the main window would have a different
[12:02] <CIA-2> usb-creator:  expanding effect on the top listview from the bottom listview.
[12:02] <CIA-2> usb-creator: * Add gnomevfs support to use gnome device labels and icons. This should
[12:02] <CIA-2> usb-creator:  make things more user friendly.
[15:54] <davmor2> xivulon: Finally everything finished downloading.  Everything works here I can only assume they did upgrades midst kernel updates
[15:58] <xivulon> davmor2 cool thanks a lot!
[15:59] <xivulon> cjwatson any chance for 289791 ? (I know we went through it already)
[17:01] <cjwatson> xivulon: no, sorry
[17:01] <cjwatson> it's too late
[17:01] <xivulon> np didn't have much hope anyway
[17:02] <xivulon> is it also too late for the wubi build with the mythbuntu key? (superm1 signed it)
[17:02] <xivulon> in case we can have a different build for mythbuntu cd
[17:02] <xivulon> hopefully we can include that in the stand-alone though
[17:07] <cjwatson> wubi should be easier, but the first round of images have *already built*
[17:07] <cjwatson> so it's only if they need another spin
[17:11] <xivulon> sounds good to me, if possible cool, otherwise having a separate build for mythbuntu cd + standalone would be less elegant but same thing in practice
[17:12] <cjwatson> I'm afraid I don't know the buttons to push to pull a new wubi build though
[17:15] <xivulon> that's up to evand :)
[17:20] <cjwatson> oh, yeah, it does need evand
[17:27] <evand> will do
[17:30] <xivulon> evand, wubi-selfextract in http://people.ubuntu.com/~evand/wubi/ is jun 24
[17:30] <xivulon> is that the one that goes onto the cd? that looks a bit dated
[17:30] <evand> xivulon: ignore that
[17:30] <evand> no, it is not
[17:30] <evand> they're all self-extracting
[17:30] <xivulon> ah was scared
[17:30] <cjwatson> it's the stable link there
[17:31] <xivulon> cool the standalone should not be self extracting (and definitely rev 515)
[17:31] <xivulon> the cd should be selfextracting
[17:31] <cjwatson> stable -> Wubi-8.10-rev513.exe
[17:33] <xivulon> the mythbuntu guys will probably need a link to rev515
[17:33] <evand> I'm working on building 515 and re-pointing the stable symlink to it now
[17:34] <xivulon> might be worth scanning it with http://www.virustotal.com/ or http://virusscan.jotti.org/ just in case
[17:34] <xivulon> forgot to do that
[17:35] <xivulon> the joys of the windows world
[17:39] <superm1> evand, there's a handful of *gcj* packages and an openoffice.org filter that are getting removed in the RC dvd even with all the language packs preseeded
[17:39] <superm1> evand, any ideas why they'd be getting flagged?
[17:40] <evand> superm1: removed as part of what? the blacklisting?
[17:40] <superm1> at the very end when it does that lastish step to check for packages to remove
[17:41] <cjwatson> because live-dvd includes some stuff that isn't in desktop
[17:42] <superm1> how come it isn't persisting into the resultant install then?
[17:42] <cjwatson> like icedtea6-plugin
[17:42] <cjwatson> because we have no infrastructure to make that happen ...
[17:42] <cjwatson> we don't have a "desktop-for-live-dvd"
[17:42] <superm1> then arguably should it really be in the dvd livefs?
[17:42] <cjwatson> I wouldn't mind looking at the logs in case it isn't what I think it is though
[17:43] <cjwatson> maybe not, but it's sort of useful to have icedtea6-plugin somewhere
[17:43] <superm1> well i just started a factory install run here, i'll have a log in about an hour
[17:44] <evand> note to self, don't ctrl-R commands involving linux device nodes after a reboot
[17:44] <evand> thankfully I just filled up /dev
[17:45] <superm1> what about that incomplete language support comment i had posted last week?  even with all language packs preseeded I'm getting that still..
[17:45] <evand> xivulon: new wubi is up and linked
[17:45] <xivulon> evand thanks a lot
[17:46] <evand> http://people.ubuntu.com/~evand/wubi/stable
[17:46] <xivulon> supemr1 ^
[17:46] <superm1> thanks xivulon and evand
[17:49] <evand> ArcaVir
[17:49] <evand> Found Trojan.Small.Ji
[17:49]  * evand rolls his eyes
[17:50] <cjwatson> superm1: I think that got fixed post-RC
[17:50] <cjwatson> superm1: at this point it would really be best to test daily builds if you aren't already
[17:50] <cjwatson> they will not be any less stable than RC
[17:51] <superm1> cjwatson, ah didn't realize there was a new daily for DVD at this point
[17:51] <superm1> cjwatson, will grab that then and verify
[17:52] <cjwatson> oh, maybe not DVD quite yet
[17:52] <cjwatson> it was building last I heard
[17:53] <superm1> okay, will hold off for that then
[18:24] <cjwatson> superm1: DVDs are up
[18:24] <cjwatson> err, maybe still publishing
[18:24] <cjwatson> amd64 is there, seems to be taking its time
[18:24] <cjwatson> it's on the master, maybe just taking ages to sync
[22:38] <bdmurray> If I enter the wrong proxy information when using the alternate installer what should happen?
[22:39] <bdmurray> The same incorrect information was set in my install which seemed odd.


[05:04] <hikiko> Hi
[07:12] <tjaalton> anyone know if there's a place other than under /usr where I could drop a custom keymap? I need to remap one key on an US kbd to be able to use finnish layout
[07:12] <tjaalton> so that unity would be able to show it on the gui
[07:13] <tjaalton> because xmodmap doesn't work
[07:13] <tjaalton> the layout is reset on resume etc
[07:13] <tjaalton> and .Xmodmap is not applied on login either
[07:53] <tjaalton> hah, looks like I can type <>| on US kbd afterall, a bit awkward with altgr+shift, but still.. no need for hacky layouts
[07:58] <Sweet5hark> moin
[07:59] <Sweet5hark> Laney: have a sec?
[08:00] <willcooke> Morning all.
[08:00] <willcooke> Weather update:  It's raining sideways.
[08:01] <duflu> Umm. I assume willcooke is not in South Australia where that is also true
[08:01] <willcooke> ha
[08:01] <willcooke> afternoon duflu
[08:01] <duflu> Hey willcooke
[08:02] <Laney> yo
[08:02] <TheMuso> Hey folks.
[08:02] <willcooke> hi Laney TheMuso
[08:02] <Laney> what's up
[08:03] <flexiondotorg> Morning
[08:03] <flexiondotorg> Hmmm, rainy walk this morning.
[08:03] <flexiondotorg> Laney, thank for sharing your dynamic profile tip yesterday.
[08:03] <flexiondotorg> I've recreated the same results using this - http://direnv.net/
[08:04] <Laney> why is it such a pain in the rear end to pay someone using different payment references?
[08:04]  * Laney stabs Santander
[08:04] <Laney> flexiondotorg: Nice
[08:04] <Laney> Sweet5hark: Yes, many, and they are all for you
[08:04] <duflu> Evening? TheMuso
[08:05] <Laney> What
[08:05] <tjaalton> owncloud client doesn't seem to start on login, is 'startup applications' still supported in yak?
[08:05] <Laney> "Amend Payee" rejects the name that creating a new payee previously allowed
[08:11] <Laney> tjaalton: It works
[08:11] <Laney> I think logs go into the journal now
[08:13] <tjaalton> Laney: ok, it's just the applet icon not showing, seems to be running
[08:16] <TheMuso> Later folks.
[08:19] <willcooke> night TheMuso
[09:38] <flexiondotorg> Laney, I've seen that #1624022 has new comments.
[09:38] <flexiondotorg> willcooke, Laney Am I right is saying the request is to now symlink 'browse' to xdg-open?
[09:39] <willcooke> I think that's where we are at now
[09:39] <flexiondotorg> OK
[09:39] <willcooke> xdg-open is better than sensible-browser (from the comments)
[09:39] <Laney> As you think is best
[09:39] <willcooke> and Mark wanted "browse" to be the command
[09:39] <willcooke> so combine both of those and we arrive at browse -> xdg-open
[09:39] <flexiondotorg> Right. Understood.
[09:40] <willcooke> Laney, you still think this is something worth upstreaming to Debian?
[09:40] <Laney> I would ask
[09:40] <willcooke> yeah, no harm in asking
[09:41] <willcooke> Let's start with a debdiff for Yakkety then, and go from there?
[09:42] <Laney> Mhm
[09:44] <willcooke> Laney, ?
[09:45] <Laney> that's a noise of assent
[09:45] <willcooke> :)
[09:46] <Laney> Check it's actually installed on server though
[09:47] <Laney> If it matters that this works on servers
[09:47]  * willcooke ponders
[09:48] <willcooke> I don't suppose a server has things like X.org, Unity 7, Firefox, etc etc installed by default
[09:49] <Laney> Might have lynx or w3m
[09:49] <jbicha> xdg-utils doesn't show for server in seeded-in-ubuntu but server is pretty minimal by default
[09:49] <jbicha> good morning
[09:49] <Laney> hi
[09:53] <willcooke> flexiondotorg, would suggest you comment on the bug and see if this is required on server, if so then that rather limits our options
[10:02] <Laney> I suspect it's probably not that useful there
[10:02] <Laney> But it might be smart to cover yourself :)
[10:25] <bregma>  hey willcooke a recent change to unity8-desktop-session for the bug fat MIR is blocked from landing until ubuntu-terminal-app gets uploaded to the stable overlay for Xenial...  did you poke anyone about doing that?
[10:26] <willcooke> bregma, morning!  Yeah, spoke to a few peeps in the ci-eng channel this morning.  I've asked TheMuso to take a look at a bug first:  https://bugs.launchpad.net/ubuntu-terminal-app/+bug/1628781
[10:26] <willcooke> Once that's sorted I think we should be able to land it
[12:24] <andyrock> good afternoon all
[12:37] <flexiondotorg> andyrock, o/
[12:44]  * flexiondotorg gets lunch
[13:05] <willcooke> hey andyrock
[13:27] <davmor2> willcooke, Laney: on yakkety if you open nautilus is it opening a separate icon in the launcher?
[13:28] <willcooke> that again
[13:28] <willcooke> davmor2, is that on an upgrade?
[13:28] <willcooke> *upgraded machine
[13:29] <davmor2> willcooke: I haven't upgraded today I was hoping to see the update-manager popup but it hasn't happened yet
[13:29] <willcooke> davmor2, out of interest, can you remove the icon and re add it
[13:29] <willcooke> and see if it still does it
[13:30] <davmor2> willcooke: now it doesn't
[13:31] <willcooke> davmor2, I /think/ it's probably related to an upgrade at some point, but if that's a fresh install, then.... ?
[13:33] <davmor2> willcooke: no it is my main box so it has been upgraded pretty much daily so might just be version changes in yakkety itself but it's only happened the last couple of days after proposed got unblocked by beta 2
[13:35] <willcooke> hmm, oki.. Well fingers crossed that's what it is
[13:48] <flexiondotorg> Laney I have a question about versioning.
[13:49] <flexiondotorg> I'll have a new xdg-utils package for Y
[13:49] <flexiondotorg> And one for X
[13:49] <flexiondotorg> They are currently the same package in both releases.
[13:49] <Laney> https://wiki.ubuntu.com/SecurityTeam/UpdatePreparation#Update_the_packaging
[13:49] <flexiondotorg> How should I version them for uploading to Y and SRUing to X?
[13:50]  * flexiondotorg goes to read.
[13:50] <Laney> Handy table there
[13:50] <flexiondotorg> Thanks
[13:53] <Laney> davmor2: MMMMMMMMMMMmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmm interesting
[13:53] <Laney> (maybe)
[13:59] <davmor2> hmmm launcher if I install byobu and add it to the launcher and do an upgrade byobu is removed from the launcher, I assume this is because the old version is removed and the newer version installed right?
[14:37] <flexiondotorg> Laney, can you cast an eye over these debdiffs please.
[14:37] <flexiondotorg> For Xenial SRU - paste.ubuntu.com/23251295/
[14:37] <flexiondotorg> For Yakkety - http://paste.ubuntu.com/23251300/
[14:38] <Laney> Are you forwarding it upstream?
[14:38] <Laney> If not, I'd just make a pkg.links file for debhelper to do what it will with
[14:43] <flexiondotorg> OK, I'll do that.
[14:43] <Laney> flexiondotorg: As a point of autotools nerdery (for interest), look up AC_PROG_LN_S
[14:44] <Laney> https://www.gnu.org/software/autoconf/manual/autoconf.html
[14:45] <flexiondotorg> Thanks, added to my reading list.
[14:48] <Laney> davmor2: that nautilus thing, you found a bug, well done
[14:48] <Laney> cookie for you
[14:48] <davmor2> Laney: I think byobu launcher being removed is another one too ;)
[14:48] <Laney> maybe
[14:48] <Laney> give me a break
[14:48] <Laney> check if it renames its desktop file
[14:49] <Laney> better, just file it
[14:56]  * flexiondotorg is just making a cuppa
[15:08]  * ogra_ notes the brits are a nation of potters ... where germans make coffee or tea, you guys only make cups
[15:19]  * flexiondotorg looks for a liquid to put in my cup
[15:24] <davmor2> Laney: so everything in the desktop file looks to be identical on yakkety and xenial so I'll file a bug against bybou intially
[15:26] <Laney> ok
[15:33] <davmor2> Laney: https://bugs.launchpad.net/ubuntu/+source/byobu/+bug/1628975
[15:35] <om26er> Hello! Is there a pythonic way to check if X server is running ?
[16:41] <flexiondotorg> Laney, here are the updated debdiffs for xdg-utils
[16:41] <flexiondotorg> Xenial - http://paste.ubuntu.com/23251853/
[16:41] <flexiondotorg> Yakkety - http://paste.ubuntu.com/23251856/
[16:41] <flexiondotorg> If built and tested them. So if these are suitable I'll attach them to the bug and we can discuss how to process to uploading etc.
[16:42] <flexiondotorg> I've not just been working on this BTW ;-)
[16:42] <flexiondotorg> I've got several bugs at various stages of testing
[16:45] <Laney> Looks good, although you don't need the version number for the devel release; that one can be ubuntu2
[16:45] <flexiondotorg> So Y can be ubuntu2?
[16:47] <Laney> yes
[16:48] <flexiondotorg> Like so - http://paste.ubuntu.com/23251883/
[16:48] <Laney> aye
[16:48] <flexiondotorg> OK, I'll attach those to the bug.
[16:49] <flexiondotorg> Should I subscribe this bug for sponsoring to get it uploaded?
[16:49] <Laney> That'd be the usual way
[16:49] <flexiondotorg> Cool.
[17:06] <Laney> nighty night
[17:30] <willcooke> night all
[17:32] <flexiondotorg> Night
[21:14] <dobey> desrt: around? any idea of a reason why g_app_info_get_all() would not be returning applications that are in XDG_DATA_{DIRS,HOME}/applications?
[21:34] <desrt> dobey: what *is* it returning?
[21:35] <desrt> those dirs are the only thing it uses
[21:36] <dobey> desrt: apparently nothing. in unity-scope-click we have an "applications" directory with a few .desktop files in it, for some integration tests, which we copy to a tmpdir for the tests and point XDG_DATA_HOME at. but they don't seem to be showing up in ubuntu-app-launch-appids, and there's no errors and no messages with G_MESSAGES_DEBUG=all
[21:37] <dobey> and nothing apparent in the u-a-l source code that would cause it. the .desktop files are straight copies from actual installed apps on the phone too, and they definitely show up in the click scope under the unity8 session :-/
[21:39] <dobey> yeah, it's not making any sense to me; so here i am pinging you :)
[21:41] <dobey> https://bazaar.launchpad.net/~ubuntuone-control-tower/unity-scope-click/trunk/files/head:/tests/scope-harness/applications/ <- these are the .desktop files
[21:42] <desrt> Do you set the envvar from inside the test program?
[21:42] <dobey> no, outside
[21:42] <desrt> Hmm
[21:42] <desrt> (good)
[21:42] <desrt> Oh
[21:42] <desrt> I know
[21:43] <desrt> The files in the Exec= line are missing, I bet
[21:43] <dobey> g_app_info_get_all() strips those out?
[21:43] <desrt> Change Exec=/bin/true or something and it will work
[21:44] <desrt> Ya... a subject of much controversy, I assure you
[21:44] <dobey> ugh, yeah. installed webbrowser-app and now it appears. that is indeed not nice
[21:44] <desrt> I'm on my way to dinner atm, so hopefully that works... otherwise, ping later?
[21:45] <desrt> Ah good
[21:45] <desrt> Good night!
[21:45] <dobey> thanks. you too
[23:37] <maxb> I was just discussing a Unity launcher problem new filed as bug 1629138 over in #ubuntu+1, and it was suggested to mention it here too.
[23:38] <maxb> Let me know if I can help provide more info


[00:12] <mjuszczak> Why does my purchased music folder sync to .ubuntuone/Purchased from Ubuntu One?
[11:40] <gatox> good morning!


 I gues we all get notifications from Phab, but in case not: https://phabricator.kde.org/T7018
 I've setup a KCC meeting task on phabricator with a agenda, will make a doodle for dates later
 :)
 +1
[14:09] <ahoneybun> well Google replaced my Nexus 6P with  Pixel XL
[14:09] <ahoneybun> \o/
 Fwd from Shower Thoughts 🚿: Spiders are the only web developers that enjoy finding bugs
[16:17] <tsimonq2> clivejo, acheronuk: With your ~kubuntu-dev hats on, would you be OK with me setting Kubuntu Developers<EMAIL_ADDRESS>as an Uploader to gcompris-qt in Debian? That would mean that with sponsorship (or maybe eventually with no sponsorship...) you guys can upload to gcompris-qt in Debian without needing an ack from me as long as you mark it as a "Team upload". I'd like to retain
[16:17] <tsimonq2> Maintainership though, but this marks Kubuntu as "co-maintainers".
[16:19] <tsimonq2> Comments welcome.
[16:21] <acheronuk> I'm not bothered. clivejo was interested in it, so I defer to his opinion
[16:21] <tsimonq2> acheronuk: ok
[16:21] <tsimonq2> Or I can mark clivejo directly as co-maintainer if he wants
[16:22] <tsimonq2> Like I said, I'd like to retain maintainership, but if y'all want to do an upload, you should be able to do an upload as a Co-maintainer without me needing to heavily review
[16:51]  * acheronuk shrugs
 https://twitter.com/tsimonq2/status/909091043525763073
[18:44] <clivejo> no thanks
[18:44] <tsimonq2> ok


[15:45] <ryu_> somehow 'bumblebee' managed to screw up my nvidia drivers, I think I have some remnants of it laying around, but I purged everything and did a reinstall, the driver says active but is never in use
[15:45] <ryu_> anyone have any ideas how to fix this?
[18:32] <ryu_> bumblebee messed up my X config, now the Nvidia driver taints my kernel, I was able to finally get rid of bumblebee, but the driver isn't loaded and clicking additional drivers (reinstalling) ..  any ideas/tips?
[18:33] <tjaalton> ask the bumblebee guys?
[18:33] <ryu_> I dont use bumblebee, I removed it
[18:33] <ryu_> it wont load the nvidia driver, or it taints teh kr0nel
[18:34] <tjaalton> right but they might know what's going on..
[18:35] <ryu_> ok
[18:35] <tjaalton> tainting the kernel is what loading nvidia does.. it shouldn't prevent loading it
[18:36] <ryu_> I cant run 3D
[18:36] <ryu_> so it doesnt work
[18:36] <ryu_> I screwed it up badly by installing that
[18:37] <ryu_> :(
[18:38] <ryu_> right now I have the regular driver for 12.04, not the binary for nvidia
[18:38] <tjaalton> pastebing xorg log somewhere
[18:39] <ryu_> ok
[18:39] <tjaalton> -g
[18:39] <tjaalton> like, install pastebinit and run 'pastebinit ...log'
[18:42] <ryu_> http://pastebin.com/u9gfGCZN
[18:43] <ryu_> sorta confusing
[18:43] <ryu_> not sure why it is even using noevaeu
[18:43] <tjaalton> [    27.419] (EE) Failed to load module "nvidia" (module does not exist, 0)
[18:43] <ryu_> yeah, it doesnt load
[18:43] <tjaalton> you don't have the x driver installed
[18:43] <ryu_> I know that
[18:44] <tjaalton> and the nvidia version is newer than what's in precise
[18:44] <tjaalton> or even saucy
[18:45] <tjaalton> so, not gonna even try to understand why it's like that
[18:45] <tjaalton> the nvidia blob should install a blacklist file so that nouveau doesn't load
[18:45] <tjaalton> but that's not happening either


[23:45] <broder> how do people generate the git-send-email-like messages that go to upstart-devel? by hand? bzr-send doesn't seem to want to write them in that style...


[09:17] <cjohnston> mornin... /15
[09:44] <AskUbuntu> Unable to access MAAS nodes | http://askubuntu.com/q/473350
[10:35] <ejat> ERROR bootstrap failed: cannot start bootstrap instance: could not create hosted service: POST request failed: BadRequest - The hosted service is not valid. (http code 400: Bad Request)
[10:35] <ejat> itry to bootstrap in azure
[10:35] <ejat> anyone can help me ?
[10:36] <ejat> $ juju status -e azure
[10:36] <ejat> ERROR Unable to connect to environment "azure".
[10:36] <ejat> Please check your credentials or use 'juju bootstrap' to create a new environment.
[10:36] <ejat> Error details:
[10:36] <ejat> environment is not bootstrapped
[14:11] <jcastro> anyone see this? http://manage.jujucharms.com/~fgimenez/precise/cakephp
[14:18] <lazyPower> jcastro: i saw it in the rev queue yesterday. Looks interesting
[14:21] <dvr077> \quit
[14:43] <dpb1> Hi -- how do get this into the charm store? bzr+ssh://bazaar.launchpad.net/~landscape-charmers/charms/trusty/landscape-client/trunk/
[14:44] <dpb1> I want to be able to do juju deploy cs:trusty/landscape-client and have it work
[14:44] <khuss> maas is failing to power on sever. I am using Dell PowerEdge. Any ideas on where to look for why this is happening
[14:45] <dpb1> Right now I get: $ juju deploy cs:trusty/landscape-client
[14:45] <dpb1> ERROR charm not found: cs:trusty/landscape-client
[14:47] <dpb1> khuss: look in the /var/log/maas/celery* logs
[14:48] <dpb1> khuss: iirc
[14:48] <khuss> i don't see anything in the celery logs
[14:48] <khuss> iirc?
[14:49] <khuss> the celery log shows power on request
[14:49] <khuss> but the server is not powering on
[14:49] <dpb1> iirc = if i remember correctly
[14:49] <khuss> got it
[14:50] <dpb1> khuss: good.  and what did you configure for power settings in the page for this server?
[14:50] <khuss> IPMI2
[14:50] <khuss> the power off is working
[14:50] <khuss> but not power on
[14:50] <lazyPower> dpb1: you don't have a trusty branch promulgated. There's only a precise branch afaict
[14:51] <dpb1> lazyPower: how do I get that done?  I have to submit for review?
[14:51] <lazyPower> dpb1: has anyone reviewed landscape against trusty? I know that when I looked at the precise charm, it was g2g after some minor tweaks. if you just pushed to the landscape-charmers branch of trusty, and it wasn't promulgated into teh store API - it wont show up in the store.
[14:52] <lazyPower> dpb1: yep. A charmer will need to look at it and ack the branch then promulgate it.
[14:52] <dpb1> khuss: sec, let me check
[14:52] <khuss> dbp1: ok
[14:54] <dpb1> khuss: my next step would be to try 'ipmipower' with the right options.  The script is just a shell script and it's in /etc/maas/templates/power/ipmi.template  You can see the commmands that it sends and try them by hand.
[14:55] <dpb1> lazyPower: ok, let me put that up then.  We know of no changes necessary for trusty and have been using it there for a while now
[14:56] <khuss> dbp: sure let me check ipmipower
[15:00] <dpb1> lazyPower: ok, put up the bug: https://bugs.launchpad.net/charms/+bug/1324163  thanks!
[15:00] <_mup_> Bug #1324163: Please promulgate landscape-client to trusty <Juju Charms Collection:Fix Committed by davidpbritton> <https://launchpad.net/bugs/1324163>
[15:47] <khuss> is it possible to have maas server and juju bootstrap server on the same machine
[15:48] <khuss> i guess i don't understand why we need a separate juju instance for deploying services
[15:54] <lazyPower> khuss: seperation of concerns. You can achieve what you're looking for if you do run a manual environment. but that quickly gets cumbersome if you're managing > 10 machines.
[15:54] <dpb1> khuss: no, you cannot.  but you can deploy a service "--to 0" which will put that service on the bootstrap node.
[15:59] <khuss> dpb1: lets say we have 10 nodes in the MAAS. how to tell juju to use the first node as the bootstrap node
[16:00] <dpb1> khuss: look at 'juju help constraints'.  You can even do things like "tags=foo", which will allow fine-grained placement, if you need it.
[16:01] <khuss> can we tag a machine from MAAS and then ask juju to use that machine for bootstrapping
[16:01] <dpb1> yup
[16:01] <dpb1> works
[16:02] <khuss> dpb1: i don't see an option to tag a node from MAAS GUI
[16:02] <dpb1> khuss: let me check where it's at
[16:07] <dpb1> khuss: my mistake.  tagging maas nodes is only available through the api (maas-cli package).   'maas <profile> tag -h' will give you more details.
[16:07] <dpb1> khuss: I personally like to use constraints like memory/cpu/etc if possible.
[16:10] <khuss> dpb1: thats not very useful when you have homogenous nodes
[16:10] <dpb1> khuss: agreed
[16:11] <dpb1> khuss: I actually have a script that adds a tag of the machine name to each node, which allows you to select whatever you like.
[16:12] <dpb1> khuss: FYI: http://paste.ubuntu.com/7537513/  it's pretty simple
[16:12] <khuss> dpb1: ok thanks
[16:17] <khuss> dpb1: found the problem with the ipmi power on issues. The Dell iDRAC is not reachable from MAAS server. There is a networking problem. Thanks for the tip on using ipmipower command
[16:20] <dpb1> khuss: great.  hit that many times myself. :)
[17:08] <hackedbellini> I'm writing a charm here that connects to a db relation and provides another one. In that other relation hook, I want to be able to do a 'relation-get' for the properties defined in the db relation. Is it possible? AFAIK, if I do a relation-get inside a xxx-relation-changed, it will get those values for the xxx relation, not the db.
[17:11] <lazyPower> hackedbellini: you'll have to cache them somewhere on disk on the host, you cannot receive the values from another relation's context through relation-get.
[17:12] <hackedbellini> lazyPower: hrm, I see. It's exactly that workaround I was trying to avoid =P
[17:14] <lazyPower> hackedbellini: yeah, i'm sorry I don't have better news for you. I think that's more of a scoping thing than anything else. It's reasonable to say that relationship contexts are isolated though
[17:15] <hackedbellini> lazyPower: np :)
[17:16] <lazyPower> hackedbellini: however, if you're using charmhelpers, theres a really nice caching class that just got merged in last week.
[17:17] <lazyPower> so it makes your cache lookups fairly inexpensive
[17:21] <hackedbellini> lazyPower: hrm, seems very nice! Where can I find it? I don't know exactly what is charmhelpers, although the name is familiar somehow
[17:23] <lazyPower> hackedbellini: charmhelpers is a suite of python modules that aid charm creators. Its in the config class, it auto-caches to a dictionary on disk and willc heck there first before pulling data down otw
[17:24] <lazyPower> tvansteenburgh is the man to talk to about the feature. He proposed it lastweek
[17:25] <hackedbellini> lazyPower: very nice! I'll take a look at it, lets see if it solves my problems :)
[17:30] <tvansteenburgh> hackedbellini: this is a good intro to charmhelpers: http://www.youtube.com/watch?v=6kWfLujVwNI
[17:32] <tvansteenburgh> hackedbellini: and here's the Config lazyPower mentioned, with some sample usage: http://bazaar.launchpad.net/~charm-helpers/charm-helpers/devel/view/head:/charmhelpers/core/hookenv.py#L158
[17:33] <hackedbellini> tvansteenburgh: ahhh cool! I'll take a look at the video. And the example seems very simple! So, I can import charmhelpers directly inside the hook, if I understood correctly? No need to change PYTHONPATH or include anything?
[17:34] <tvansteenburgh> hackedbellini: yes, you'll need to get it on your path. the video covers a way to do that from within your hooks module
[17:34] <hackedbellini> tvansteenburgh: nice! Thank you for the links :)
[17:35] <tvansteenburgh> hackedbellini: you're welcome!
[18:35] <mhall119> jcastro: where can I get the latest vagrant packages from?
[18:35] <mhall119> you mentioned the one in the archives is a bit out of date
[18:36] <jcastro> http://www.vagrantup.com/downloads.html
[18:37] <mhall119> no PPA?
[18:37] <jcastro> I don't think so
[18:37] <mhall119> ok
[18:37] <jcastro> you only need it until the next ubuntu release, heh
[18:39] <mhall119> that's what they always say :)
[18:42] <lazyPower> mhall119: if you're on precise, you'll want to get it from upstream
[18:42] <lazyPower> otherwise, teh trusty package is only .1 release behind last i checked.
[18:48] <marcoceppi> mhall119: I tried backporting the trusty vagrant to precise in a ppa, it ended up being a mess
[18:50] <lazyPower> There's a nice ruby dependency chain there that needs some love
[18:57] <mhall119> lazyPower: I'm on trusty, but already installed from upstream
[18:59] <lazyPower> its not a bad idea to use the latest and the greatest. hashicorp is known for making decent products. Their newer stuff with integrated proxy'ing is really nice.
[18:59] <lazyPower> jcastro discovered it shortly after our last charm school and was demo'ing it to the team. Deploy juju-gui, let other people deploy to your VM environment.
[20:09] <khuss> i've only one environment setup in juju but the juju status gives the following message
[20:09] <khuss> ERROR Unable to connect to environment "". Please check your credentials or use 'juju bootstrap' to create a new environment.  Error details: environment is not bootstrapped
[20:09] <khuss> it doesn't show the environment name
[20:11] <marcoceppi> khuss: what does juju switch say?
[20:12] <khuss> marcoceppi: juju switch says "maas"
[20:12] <khuss> marcoceppi: which is the enviornment name
[20:12] <khuss> marcoceppi: i did juju bootstrap -e maas
[20:13] <khuss> marcoceppi: it is doing the power cycle of the blade and going thru the install
[20:13] <marcoceppi> khuss: is the node on right now?
[20:13] <marcoceppi> it might still be bootstrapping
[20:13] <marcoceppi> how long ago did you run the bootstrap
[20:13] <marcoceppi> can you ssh in to the machien?
[20:14] <khuss> marcoceppi:  it failed the first time and I just started it again
[20:14] <khuss> marcoceppi: this is what I got at the first time - curl: (7) couldn't connect to host tools from http://localhost:80/MAAS/api/1.0/files/?key=aedd9246-e6a1-11e3-af69-b8ca3a5bc3f8&op=get_by_key downloaded: HTTP 000; time 0.000s; size 0 bytes; speed 0.000 bytes/s ERROR bootstrap failed: rc: 1 Stopping instance... Bootstrap failed, destroying environment
[20:15] <khuss> marcoceppi: i did resync-tools and then just tried the bootstrap
[20:15] <marcoceppi> khuss: your mass might not be configured properly. it shouldn't say localhost for URLs
[20:15] <khuss> marcoceppi: i did that configuration because the cluster controller is on the same machine.. shd I give the IP address instead
[20:16] <marcoceppi> khuss: definitely, you can run sudo dpkg-reconfigure maas-region-controller to set the IP address again
[20:17] <khuss> marcoceppi: do I need to reconfigure the region-controller? it is just on the juju environment file right? What if i change from localhost to the ip of the machine
[20:17] <marcoceppi> khuss: OH, this is in your environments.yaml
[20:18] <khuss> marcoceppi: yes
[20:18] <marcoceppi> that should be fine
[20:18] <marcoceppi> misunderstood
[20:18] <khuss> marcoceppi: let me see how the bootstrap goes this time..  i tried curl on that link (in the error message above) and it didn't work
[20:19] <marcoceppi> khuss: well it'll probably give you a new bucket id
[20:20] <khuss> marcoceppi: failed again. 2014-05-28 20:20:03 INFO juju.cmd supercommand.go:302 running juju-1.18.3-precise-amd64 [gc] 2014-05-28 20:20:03 DEBUG juju.agent agent.go:384 read agent config, format "1.18" 2014-05-28 20:20:03 DEBUG juju.provider.maas environprovider.go:30 opening environment "maas". 2014-05-28 20:20:03 ERROR juju.cmd supercommand.go:305 Get http://localhost:80/MAAS/api/1.0/nodes/?agent_name=b4a4c73b-29e3-4333-8e0b-8f82074896
[20:21] <marcoceppi> khuss: set that to the IP address that both you and the machines can get to
[20:21] <marcoceppi> khuss: once you do that, run `rm ~/.juju/environments/maas.jenv`
[20:22] <marcoceppi> then sync-tools
[20:22] <marcoceppi> then do a bootstrap
[20:22] <khuss> marcoceppi: ok
[20:23] <khuss> marcoceppi: docs http://maas.ubuntu.com/docs/juju-quick-start.html seems to be wrong.. juju ---sync-tools doesnt work.. "juju sync-tools" does
[20:24] <marcoceppi> khuss: thanks for the heads up! I'll file a bug
[20:26] <khuss> marcoceppi: np
[20:38] <khuss> marcoceppi: bootstrap completed without error. however, juju status gives this error - ERROR state/api: websocket.Dial wss://1-10-2.master:17070/: dial tcp: lookup 1-10-2.master: no such host
[20:38] <khuss> marcoceppi: may be a DNS problem?
[20:48] <khuss> marcoceppi:  juju status still doesn't work
[20:51] <khuss> marcoceppi: actually it worked after adding the host to /etc/hosts.. may be there is a better way to use the local DNS server
[20:54] <lazyPower> khuss: have you added the maas master node to your /etc/resolv.conf along with a search declaration for the local domain? in this case it appears to be search 'master'
[20:54] <lazyPower> without quotes
[20:54] <khuss> lazyPower: no i've not .. let me try that
[21:09] <khuss> lazyPower: i added it on the /etc/resolv.conf.. looks like i need to edit some other files in Ubuntu
[21:42] <lazyPower> khuss: it wont persist past a reboot
[21:43] <lazyPower> if it works, then add it to /etc/resolve.conf.d/head (i think) and it should fix you up and persist after a reboot.
[21:54] <khuss> lazyPower: ok. thanks


[00:00] <cjwatson> "last failure on grub" not a thing, not relevant
[00:00] <cjwatson> Can we move this back to #ubuntu-release to avoid a split conversation?
[00:00] <teward> cjwatson: nobody ever replied to me at all in -release
[00:00] <teward> so this is really the "start of the conversation"
[00:00] <teward> same when wxl prodded
[00:00] <cjwatson> See the conversation there _right now_
[00:01] <teward> now i see it
[00:01] <teward> thanks
[00:01] <teward> (took too long for anything to show up)
[00:01] <teward> rbasak: still looking for your answer RE: #ubuntu-server poke from hours ago
[00:02] <teward> re: nginx and lua module and whether it works, my assumption is "no" based on the bug
[07:18] <ed_> hello, can you import rust-pleaser 0.3.24 from sid please. rationale: to work around dependencies
[08:44] <seb128> hum, why is syncpackage not seeing sources uploaded to unstable yesterday?
[08:45] <seb128> $ syncpackage gnome-builder
[08:45] <seb128> Version in Debian 3.38.1-1 (unstable) isn't newer than Ubuntu 3.38.1-1build3 (hirsute-proposed)
[09:03] <ed_> seb128: might be feature freeze
[09:05] <seb128> ed_, the Debian one?
[09:10] <Laney> seb128: it's a launchpad thing, if the page on https://launchpad.net/debian/+source/gnome-builder doesn't know about it then it's not syncable
[09:11] <seb128> Laney, ah, thanks, and do you know how often those are supposed to happen? it usually takes less than half a day, it feels bogus that they didn't get picked up at this point
[09:11] <seb128> I guess I should check on the launchpad channel
[09:12] <Laney> no, but I did manage to sync glib2.0 which was uploaded yesterday
[09:13] <seb128> weird
[09:14] <ed_> Laney: what did you end up doing? rust-pleaser is also stuck
[09:16] <Laney> ed_: doing to what?
[09:21] <ed_> Laney: how did you end up syncing it, you said you managed to
[09:27] <Laney> ed_: I ran the synapackage command, which worked because Launchpad knows about this update: https://launchpad.net/debian/+source/glib2.0/2.67.5-1
[09:27] <Laney> syncpackage*
[09:27] <Laney> rust-pleaser is stuck for other reasons https://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html#rust-pleaser
[09:29] <ed_> sid updated to 0.3.24, to work around that excuse (nix). what i'm trying to do is get launchpad to 0.3.24
[09:29] <ed_> shouldn't it have syncd automatically?
[09:31] <Laney> no, Debian Import Freeze, see the topic or the release schedule, it needs to be requested manually at this point
[09:32] <ed_> Laney: i saw there was a freeze, but want to fix this. how do i get that done?
[09:34] <Laney> ed_: follow this process: https://wiki.ubuntu.com/SyncRequestProcess
[09:39] <ed_> Laney: thank you, that explains it, i'll file a bug against the package
[12:31] <cjwatson> FYI the Debian import bug above is https://bugs.launchpad.net/launchpad/+bug/1917449
[12:31]  * cjwatson shakes fist at Python 2
[12:56] <doko> Python++
[12:57] <cjwatson> Nearly there :)
[12:58] <cjwatson> (But I don't think "fix production issue as part of migrating to py3" would be a very popular approach)
[13:50] <RikMills> ed_: fyi, rust-pleaser looks available to manual sync now
[14:03] <ed_> RikMills: would you like me to raise a ticket against the package for that? i'll need to finish off some day job things first
[14:07] <RikMills> ed_: if I was to do it, then I think yes. I don't see anything much in the debian or upstream changelogs that tell me if this has any new features or what bugs/issues justify it
[14:11] <ed_> ok, the log should show that nix was downgraded as it doesn't pass migration here
[14:11] <ed_> but yeah, that wasn't explict in the log
[16:32] <rbasak> sergiodj: node-uid-number isn't aged 7 days yet
[16:34] <sergiodj> rbasak: ok, thanks
[17:09] <teward> isn't the Ubuntu pastebinit supposed to default to the paste.u.c?
[17:09] <teward> in focal, it's defaulted to pastebin.com and fails hard.
[17:10] <RikMills> it goes to ubuntu in my focal
[17:12] <teward> hmmmm
[17:12] <teward> interesting
[17:12] <teward> because it doesn't here.
[17:14] <teward> RikMills: do you have a .pastebinit.xml in your home dir perchance?
[17:15] <teward> the main reason I ask is because this is the type of output I get without a customized xml to tell it where to paste to: https://paste.ubuntu.com/p/DcYzbwmrXG/
[17:15] <teward> and it's defaulting to pastebin.com and not paste.u.c which is *different* for Focal than it was before, at least on here.
[17:15] <RikMills> teward: no. it is actually a testing VM, so a pristine then updated install
[17:15] <teward> hmmmmmmmm
[17:16] <teward> *spins a testing Focal container*
[17:16] <teward> (LXD is good for that xD)
[17:17] <teward> huh that is *weird* it's only my system that's having this problem o.O
[17:17] <teward> i wonder what went weird on here
[17:18] <teward> okay, that's *really* weird, my laptop here is Focal upgraded from 18.04 and pastebinit is *not* pointing to the paste.u.c site.  but the container that's clean is.  I wonder what that's about...
[17:20] <RikMills> teward: have you done something so it doesn't think your system is a ubuntu one?
[17:21] <teward> yes and no.
[17:21] <teward> no in that this is a Focla system
[17:22] <teward> yes in that it's a userspace python 3.9.0 build running via pyenv and didn't have 'distro' installed - meaning the setup script for that build didn't run the `pip3 install` i told it to after compiling.
[17:22] <teward> so `distro` plugin wasn't available, and pastebinit silently 'pass''s on ImportErrors for that and that's why it's falling back to pastebin.com
[17:22] <RikMills> right
[17:22] <teward> so not the bug I initially thought, becuase ERR:UserError
[17:22] <teward> but still a bug for stgraber to look at RE: Pastebin itself as the fallback failing hardcore.
[17:35] <seraph> on a launchpad bug, what does the label sts-sponsor-volunteer indicate?
[17:38] <rbasak> Anyone can set any tag on a bug
[17:38] <rbasak> The official "Ubuntu" tags are documented at https://wiki.ubuntu.com/Bugs/Tags but this probably isn't one of them.
[17:39] <rbasak> Individual people and teams can use whatever they like to mean what they want
[17:39] <rbasak> In this case it's probably the Canonical STS team
[17:39] <rbasak> (something internal to them)
[17:39] <seraph> thanks
[17:40] <rbasak> I'm guessing it's something to do with finding a sponsor for an upload internal to their team.
[17:40] <rbasak> can use whatever they like> we do try to avoid stepping on each others' toes, of course
[17:53] <ed_> RikMills: https://bugs.launchpad.net/ubuntu/+source/rust-pleaser/+bug/1917502
[17:59] <RikMills> ed_: done
[18:00] <ed_> RikMills: Thanks, much appreciated
[19:10] <ddstreet> seraph which bug in particular are you looking at?
[19:24] <seraph> ddstreet https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1876570


[19:59] -SwissBot:#ubuntu-news- ::Planet:: Ubuntu Blog: Data centre networking: SDDC @ https://ubuntu.com//blog/data-centre-networking-software-defined-data-centre
[20:02] -SwissBot:#ubuntu-news- ::OMG!Ubuntu:: TUXEDO’s Nano Pro is a Palm-Sized Linux PC @ https://www.omgubuntu.co.uk/2021/11/tuxedo-nano-pro-amd-linux-pc-specs-price (by Joey Sneddon)
[22:31] -SwissBot:#ubuntu-news- ::Portugal:: Ep 167 – Debutant @ https://podcastubuntuportugal.org/e167/


[03:37] <jose> marcoceppi: re: seb's prob. I'm gonna take a look tomorrow early morning as soon as I get there. should be an issue with apache and the local repo we have, I should be able to fix it real quick :)
[04:07] <jose> sebas5384: I'm gonna check the local repo tomorrow morning 8am. if you can be there 8:30 to test it would be amazing.
[04:07] <jose> sebas5384: I believe it's an issue with apache2, so should be easy to fix
[04:08] <jose> anyways, on my checklist
[04:08] <sebas5384> jose: great! but I think I'll deploy some wordpress
[04:08] <jose> sebas5384: using cloud resources?
[04:08] <jose> or local?
[04:09] <sebas5384> jose: I think we wont be able to deploy openstack
[04:09] <sebas5384> actually
[04:09] <sebas5384> let me try with gce
[04:09] <jose> sebas5384: so, you've got the third slot. what about if we meet at the speakers lounge during the first two slots so we can figure things out, see if they work and everything, and then maybe you will feel a bit more confident? :)
[04:10] <sebas5384> jose: I'll be there around 9am
[04:11] <jose> sebas5384: sounds good. make sure to check in to get your food tickets
[04:11] <sebas5384> already arrange with elizabeth
[04:11] <jose> woot woot
[04:12] <sebas5384> jose: good one
[04:12] <jose> feel free to ping me if you need anything or lmk if you wanna test before your session
[04:12] <sebas5384> thanks man
[04:12] <jose> no worries!
[04:12] <sebas5384> I'll test the openstack here
[04:12] <sebas5384> with gce
[04:12] <sebas5384> lets see what happen
[04:12] <jose> got your free trial?
[04:12] <jose> beware, 8 cpus limitation on free trial
[04:14] <sebas5384> yeah
[04:14] <sebas5384> jose: hmmm
[04:14] <sebas5384> didn't know about that
[04:14] <sebas5384> would it be better if we got some aws credits
[04:15] <jose> aaand... you should be all set.
[04:15] <sebas5384> i feel its more stable
[04:16] <jose> no worries, whatever you feel more comfortable working on!


[11:19] <infinity> cjwatson: http://paste.ubuntu.com/5867830/
[11:19] <infinity> cjwatson: http://paste.ubuntu.com/5867831/ <-- The product of the above.
[11:20] <infinity> cjwatson: My gut feeling is that we might also want those deps versioned, so we can force ourselves to rebuild against any new d-i component to keep sources in sync, but that seemed draconian for a first cut.
[11:21] <infinity> (And this matches what britney was already doing)
[11:24] <cjwatson> Certainly looks good for now.  Thanks!
[11:24] <cjwatson> Go for it.
[11:24] <infinity> Kay, will upload after I've tested that d-i also builds and does sane things with the linux-ppc 3.10 bump.
[11:24] <cjwatson> I suspect we'll find this is a "wow, we should have done this years ago".
[11:25] <infinity> (And possibly some lunch :P)
[11:27] <infinity> The big bonus here for removing the irriating seed skew and fiddling is that I'll be happier with the idea of rtg and apw doing ABI bump uploads of d-i, since it's just one package instead of some delicate "watch for migration and change seeds in the same publisher cycle" madness.
[11:27] <cjwatson> Indeed.
[11:40]  * apw looks up, ahh yes indee
[19:07] <infinity> Dangit my d-i change is going to make me slip off the "top contributor" list to ubuntu-seeds.
[19:07] <infinity> My precious, precious karma!
[19:07]  * infinity uploads a revert.
[20:27] <GrueMaster> Hmm.  Karma vs Quality.
[20:28] <infinity> Quality, schmality.  It's all about pointless metrics and popularity contests, right?
[21:22] <GrueMaster> THAT's why I'm no longer there!  I knew I was doing something wrong.
[22:16] <infinity> cjwatson: Bah, germinate's Kernel-Version pruning routine has thwarted me.  Updating seeds for now, but we might want to make germinate less clever.
[22:16] <cjwatson> You can't just delete the Kernel-Version seed entries?
[22:16] <infinity>     def _is_pruned(self, di_kernel_versions, pkg):
[22:16] <infinity>         """Test whether pkg is for a forbidden d-i kernel version."""
[22:16] <infinity>         if not di_kernel_versions or not di_kernel_versions.kernel_versions:
[22:17] <infinity>             return False
[22:17] <infinity>         kernvers = di_kernel_versions.kernel_versions
[22:17] <infinity>         kernver = self._packages[pkg]["Kernel-Version"]
[22:17] <infinity>         if kernver != "" and kernver not in kernvers:
[22:17] <infinity>             return True
[22:17] <infinity> I assume that's pruning anything not specified as a current/allowed kernel-version.
[22:17] <infinity>         return False
[22:18] <cjwatson> not di_kernel_versions => not pruned
[22:18] <cjwatson> first test
[22:18] <cjwatson> So if the seeds simply don't contain Kernel-Version at all ...
[22:18] <infinity> Oh, so if we specify none... Kay.
[22:18] <infinity> S'pose that's worth a test.
[22:19] <cjwatson> At least that's how it's meant to work.
[22:21] <infinity> I wonder if we'll find a bunch of modules udebs that don't show up in debian-installer-udebs and need seeding anyway.  Hrm.
[22:23] <infinity> I'm going to look at this tomorrow when I get in to London, I have an early flight and should nap instead of pondering this.
[22:25] <cjwatson> Probably.  Perhaps "Extra-Include: *-modules-di *-firmware-di" would deal with that.
[22:25] <cjwatson> Or similar.
[22:25] <infinity> Or just seed the kernel source packages wholesale.
[22:25] <cjwatson> (i.e. include all modules from the same source)
[22:25] <infinity> But I'll play around with some germinate runs and output tomorrow.  Sleep now.
[22:26] <cjwatson> There have historically been some cases where we've wanted to seed only some flavours but not others, so I'd like to make sure we still have that flexibility.
[22:26] <cjwatson> Sleep well.


[00:49] <arraybolt3[m]> Dan Simmons: That sounds like exactly what I want! Though it should be noted that the configuration changes make our config work with Calamares 3.3.0, but break compatibility with 3.2.x.
[00:49] <arraybolt3[m]> (At least, that's the intended result.)
[00:50] <kc2bez[m]> arraybolt3[m]: We can take care of that in the packaging.
[00:52] <kc2bez[m]> https://github.com/lubuntu-team/calamares-settings-ubuntu/blob/ubuntu/kinetic/debian/control#L26
[00:55] <arraybolt3[m]> Thanks! This is my first time using Git (I do program, but I used to do it without any version control or stuff like that), so you might have to help me figure out some of what I'm doing, but hopefully I'll figure it out. I'm thinking, fork that repository, replace the necessary files, and then can I use Pull Request to ask to merge my changes back into your repository?
[00:56] <kc2bez[m]> Yes, that is a good way to summarize.
[00:57] <kc2bez[m]> For good hygiene each thing you change should be a commit.
[00:58] <arraybolt3[m]> OK. Uh... crud. I'm doing that in my custom Git repo containing the /etc/calamares/modules directory, but I'm gonna lose all of that when I move it over to GitHub...
[00:58] <kc2bez[m]> Keep doing what you are doing and testing.
[00:59] <arraybolt3[m]> OK. Worst case scenario, I'll stick it in another GitHub repo all of its own and all the commit history will be there, and then everything can just be glommed into one massive "Update config for Calamares 3.3.0" commit for putting it in the main repo. (I think that's right?)
[01:02] <kc2bez[m]> Once you get it where you want you can create a new fork and just edit the files one at a time. I guess that is what I should have said, each file you edit should be a commit. You should have a changelog entry for each thing too.
[01:03] <arraybolt3[m]> Oh, I get it. That makes sense. So, one commit per file, not per logical change? I ask because at least one of my changes was moving config from fstab.conf to mount.conf, since that's where Calamares expects to find some of the config data now. So that changed two files in one logical change.
[01:04] <kc2bez[m]> Yeah, that makes sense to be one commit.
[01:04] <kc2bez[m]> @teward001 it looks like the cert on phab expired.
[01:06] <kc2bez[m]> arraybolt3 @arraybolt3:matrix.org:  when phab comes back around you will want to look at this https://phab.lubuntu.me/w/packaging/packaging-requirements/
[01:07] <arraybolt3[m]> Dan Simmons: OK. I can just force my way into Phab despite the invalid certificate, right? Or is that dangerous from a security perspective?
[01:07] <kc2bez[m]> You likely have some of that done already
[01:08] <arraybolt3[m]> Actually, I've never made a package before...
[01:08] <arraybolt3[m]> But I should learn how to do that.
[01:08] <kc2bez[m]> arraybolt3[m]: It is just an expired let's encrypt so your call.
[01:09] <kc2bez[m]> arraybolt3[m]: Hopefully we are guiding you through that ;)
[01:09] <arraybolt3[m]> OK. As long as it won't risk leaking account data, I'm fine with clicking scary buttons to make things work.
[01:09] <arraybolt3[m]> kc2bez[m]: Thanks! This is really fun, and hopefully it will work by the end of it. I'm just going through all the files, looking to see what's changed and how, then rewriting the files to do the same thing with the new syntax and option placement.
[01:11] <kc2bez[m]> arraybolt3[m]: Sounds good. With a little local testing before we upload we should know if it works, at least generally.
[01:11] <arraybolt3[m]> True. I'm not going to upload something untested. If it won't at least give me a good full disk install and a good manually partitioned install, it's no good.
[01:29] <arraybolt3[m]> OK, so, I hit a problem. Even with the updated config, I'm getting the exact same error. It told me that "name ssd_extra_mount_options" is not defined in /usr/lib/x86_64-linux-gnu/calamares/modules/fstab/main.py, line 417. So I went there, and I can see the code that's throwing a fit... but I don't know Python and am not sure what to do from here. My fstab.conf has nothing about "ssdExtraMountOptions" - I moved that into
[01:29] <arraybolt3[m]> mount.conf and formatted it as needed.
[01:33] <arraybolt3[m]> OK, I just tried modding the Python code to remove "ssd_extra_mount_options" entirely since it looked unused. Let's see how this blows up.
[01:33] <kc2bez[m]> arraybolt3[m]: It might be time for that upstream bug with logs and settings attached.
[01:34] <arraybolt3[m]> That makes sense. I'm always a bit scared of filing upstream bugs since the first time I did that it got closed instantly because I made a boffo...
[01:34] <arraybolt3[m]> But I guess I'll do that if needed. Seems odd, though, if this isn't our fault, this should have been easily caught in testing, I would have thought.
[01:35] <arraybolt3[m]> (Wow, my mod made it pass the fstab bit?!? Weird. Wonder how malformed fstab is going to be now.)
[01:36] <kc2bez[m]> arraybolt3[m]: Nobody else is running this version. It hasn't been released yet.
[01:36] <arraybolt3[m]> Ah. That makes sense. I didn't realize that.
[01:37] <kc2bez[m]> Bleeding edge ;)
[01:37] <kc2bez[m]> Keep the band-aids handy :D
 "Nobody else is running this..." <- The only other human is ade lol
[02:52] <tsimonq2> arraybolt3 @arraybolt3:matrix.org: Are you planning on sticking around enough to become a Lubuntu Member?
[02:52] <tsimonq2> Definitely wouldn't be a bad thing ;)
[02:53] <kc2bez[m]> I hope you do ;)
[02:53] <tsimonq2> ^^^^^
[03:03] <arraybolt3[m]> Simon Quigley, Dan Simmons: I'm hoping to!
[03:05] <tsimonq2> arraybolt3 @arraybolt3:matrix.org: Keep track of when you first popped in the channel and date it out minimum 3 months
[03:05] <tsimonq2> Now, you'll hear from people that oh, 6 months is the minimum, 6 months is recommended, whatever
[03:05] <tsimonq2> I would absolutely be a hypocrite if I enforced that
[03:06] <tsimonq2> When I first started contributing with all that 13 year old crackhead energy I did it in three months flat, usually takes people six :)
[03:06] <tsimonq2> As long as you can justify your contributions as significant and sustained and we can trust you to represent the project, you're eligible
[03:07] <tsimonq2> And I definitely think you're on your way
[03:07] <arraybolt3[m]> OK. I have a document where I'm tracking everything so I can survive the interview. I'm kinda scared LOL
[03:08] <tsimonq2> Nah you're good. Unless you go for Lubuntu Developer, in that case prepare for the two hour roasting session with myself, teward, and Dan ;]
[03:08] <tsimonq2> s/]/)/
[03:09] <tsimonq2> Lubuntu Member is a breeze as long as you show your face enough times
[03:09] <arraybolt3[m]> I might do that, but that's probably WAY far off.
[03:09] <tsimonq2> Yeah go for member first
[03:10] <tsimonq2> Anyway, one last thing, and that's, don't be afraid to speak up if you're not getting something. My DMs are open too if it's long-form
[03:10] <tsimonq2> We all started right where you are
[03:11] <arraybolt3[m]> OK, sounds good. So far things are going "smoothly" (well, except for the fact that Calamares is crashing for goodness-knows-why with a very obscure error message), but I definitely am thankful for help. I'll probably need some assistance with packaging.
[03:12] <tsimonq2> Sounds good. If it makes you feel any better I picked it up after basically a year or two with no packaging experience and it came right back to me after the first upload or two
[03:12] <tsimonq2> So please, reach out
[03:12] <tsimonq2> Myself, Thomas, Dan, etc.
[03:13] <tsimonq2> Well of course Cala will crash, it's early alpha you know ;) welcome to the team that gets to fix it! Yay!
[03:13] <tsimonq2> Do you have a longer error message that you can paste?
[03:18] <arraybolt3[m]> tsimonq2: Yeah, but it's all but useless. My config file is good, I think, and the code that's going wonky is a SO file, if I'm not mistaken (not a python script), so... But, I'll paste it just in case it helps. You'll also want the Calamares log if you want to make heads or tails of it.
[03:18] <arraybolt3[m]> ERROR: Installation failed: "Could not run command."
[03:18] <arraybolt3[m]>  - message: "Could not run command."
[03:18] <arraybolt3[m]>  - details: The commands use variables that are not defined. Missing variables are: i.
[03:19] <arraybolt3[m]> (And in case you're wondering, "What command?", the answer is: Yeah, right? Who knows?!?)
[03:19] <tsimonq2> Fun. Have your config anywhere yet?
[03:20] <arraybolt3[m]> Not anywhere public - I was waiting to upload it until I got one good install, but that looks hopeless, so I'll upload what I've got and we'll see what happens.
[03:20] <tsimonq2> I'll grab it then - I have a few tricks up my sleeve
[03:21] <tsimonq2> If nothing else I'll just git bisect it
[03:21] <tsimonq2> No sweat off my brow :)
[03:22] <arraybolt3[m]> OK. I'll fight with GitHub and see if I can make it happen.
[03:22] <arraybolt3[m]> (Git bisect is a good idea.)
[03:24] <tsimonq2> git clone existing-repo... (full message at https://libera.ems.host/_matrix/media/r0/download/libera.chat/14a80ed54e28f08231347fac6b3be6f9fc571891)
[03:24] <tsimonq2> That's just off the top of my head, take it with a grain of salt
[03:25] <arraybolt3[m]> Nice.
[03:25] <tsimonq2> Hope it helps
[03:26] <arraybolt3[m]> I have yet to connect git to GitHub though, I'll probably need to do that, right?
[03:27] <tsimonq2> Nope, you don't have to connect anything like a service
[03:27] <tsimonq2> Git is distributed and scalable
[03:27] <arraybolt3[m]> OK. But I do need some method of authentication - I'm looking into a GitHub Personal Access Token ATM.
[03:27] <arraybolt3[m]> (ATM = at the moment - there's no Personal Access Token Automated Teller Machine...)
[03:28] <tsimonq2> SSH keys > auth keys unless it's a server
[03:28] <tsimonq2> arraybolt3[m]: Oh I'm Gen Z, I'll lyk if I don't get ya ;)
[03:29] <tsimonq2> tsimonq2: If you have the money, a Yubikey is a great investment. They're standard issue at Altispeed (my employer, shameless plug for asknoahshow.com)
[03:29] <arraybolt3[m]> I'm looking into one of those, but for now it's kinda expensive. But that seems like a good idea for tin the future.
[03:30] <arraybolt3[m]> SSH keys > auth keys - meaning better than?
[03:30] <tsimonq2> We'll pay for one if you become a Lubuntu Member :)
[03:30] <tsimonq2> arraybolt3[m]: Yes
[03:31] <arraybolt3[m]> You can delete an SSH key from GitHub if you lose it, right?
[03:31] <kc2bez[m]> Yes
[03:31] <arraybolt3[m]> OK, then I'll do that then.
[03:32] <kc2bez[m]> Here are the add instructions https://docs.github.com/en/authentication/connecting-to-github-with-ssh/adding-a-new-ssh-key-to-your-github-account
[03:32] <arraybolt3[m]> I'm there, but I didn't see anything about being able to remove the key, and I hate when there's stuff hanging around that I can't delete that I'll never use again.
[03:32] <kc2bez[m]> Basically generate your key and add your pub key to Github
[03:33] <tsimonq2> arraybolt3[m]: I've done it before, you'll see once you add it
[03:33] <kc2bez[m]> There is a big red X for delete after you add them
[03:33] <arraybolt3[m]> OK, nice.
[03:39] <arraybolt3[m]> Alright, SSH key done.
[03:41] <arraybolt3[m]> OK, it looks like it's working!
[03:42] <tsimonq2> I'm going to go AFK for the night, thanks for everything guys :)
[03:42] <tsimonq2> Tomorrow my goals are to get the images building and to at least start the backport staging process
[03:42] <guiverc> thanks & have a good night tsimonq2
[03:43] <arraybolt3[m]> Simon Quigley: Thank you! Good night!
[03:43] <kc2bez[m]> Sounds awesome! I going to spend some time horizontal too. I too shall return tomorrow.
[03:44] <tsimonq2> Thanks guys :) take care
[03:45] <arraybolt3[m]> And I'll see if I can figure out this crazy Git thing and get something useful uploaded.
[04:08] <arraybolt3[m]> I DID IT! https://github.com/ArrayBolt3/calamares-settings-ubuntu Wow, that was hard, but there it is.
[04:10] <guiverc> well done arraybolt3[m]
[04:10] <arraybolt3[m]> guiverc: Thanks!
 i'll fix it in a bit - i blame letsencrypt xD (re @lubuntu_bot: (irc) <kc2bez[m]> @teward001 it looks like the cert on phab expired.)
 *yawns loudly*
[15:55] <arraybolt3[m]> Hey, am I the only one who Discourse is throwing a small fit with?
[15:56] <arraybolt3[m]> It keeps glitching in weird and unexpected ways (likes that I know are applied aren't showing up, notifications I've already read are popping up, pages are sometimes just not loading right, topics appearing and disappearing)
[15:57] <kc2bez[m]> I haven't noticed those issues.
[15:57] <LeoK[m]> I cannot even sign in...no error just twirling
[15:58] <arraybolt3[m]> Hmm, maybe we all need to clear our cookies and cached site data from Discourse to see if that straightens it out.
[15:59] <kc2bez[m]> Clearing cache is always a good start.
[15:59] <LeoK[m]> no luck but now the certificate warning
[15:59] <arraybolt3[m]> And now the SSL cert on Discourse is dead too.
[16:00] <kc2bez[m]> Ah, that makes sense why it was acting weird.
[16:01] <kc2bez[m]> Thomas indicated he would get them renewed when he could.
[16:33] <tsimonq2> Good morning :)
[16:44] <LeoK[m]> Daily ISO build failed
[16:45] <tsimonq2> Alright, give me some Matrix thumbs up/down... too early to roll up a new tar? Here are the new changes that would be pulled: https://github.com/calamares/calamares/compare/821a62ffbb24955287d10205f62ff62301c76eb7...calamares
[16:46] <tsimonq2> (thumbs up means yes go for it)
[16:50] <kc2bez[m]> I see some fixes there but I expect a couple of key ones are still to come. Namely the undefined variable in the fstab module and a fix to the welcome module.
[17:24] <arraybolt3[m]> I'd say build it. If I get asked to use the absolute latest version in the bug report I'm writing, that will come in handy.
[17:29] <arraybolt3[m]> Bug report on ssd_extra_mount_options bug: https://github.com/calamares/calamares/issues/1980
[17:30] <arraybolt3[m]> And I had to typo the title. Lovely.
[17:30] <arraybolt3[m]> OK fixed the title.
[18:21] <kc2bez[m]> Thanks for filing the bug arraybolt3 @arraybolt3:matrix.org:
[21:08] <tsimonq2> LXQt just migrated
[21:08] <tsimonq2> I'll kick the ISO within the hour
[22:02] <kgiii> Hmm... Discourse appears down. Let me do some additional testing.
[22:02] <kc2bez[m]> It is already mentioned here, the certificate has expired. :(
[22:04] <kgiii> I see it mentioned now. I can kinda load it (trusting the cert) in PaleMoon.  On the other hand, I also use a control panel - like cPanel - which happily deals with LetsEncrypt for me.
 kgiii: which only is as good as LE not giving an invalid response from their backends to the client
 OTHERWISE LE is set on our side with autorenew and NGINX reload hooks sooooo
 *blames LE for this one*
[22:58] <kgiii> Yeah, but if that happens it's someone else's job to fix it. ;-)
[22:59] <kgiii> Hmm... Lemme check something...
[23:19] <kgiii> FWIW, I can add and renew LE certificates via cPanel. I didn't check anything else.
[23:20] <kgiii> IE In other words, they may only be partially broken.