[02:12] <BarkingFish> good morning :)
[02:14] <BarkingFish> I wonder if someone could spare some time to help me please - i'm back in an old kernel because the one which came with raring's dev branch, 3.8.0-1, won't let me build ndiswrapper :(  Could someone please give me some ideas on how to fix this please?
[02:15] <BarkingFish> I can't build manually, because make can't find the kernel version in /usr/src/linux-headers-3.8.0-1/ , and dkms won't add, build or install ndiswrapper, claiming the dkms conf already has it, and i can't add it more than once :)
[02:31] <xnox> BarkingFish, I thought i fixed ndiswrapper!
[02:31] <xnox> and I now wish you didn't disappear as I need somebody to test my ndiswrapper fixes!
[02:31] <xnox> *sigh*
[03:21] <infinity> xnox: It's all the rage in #ubuntu-kernel for people to ask for help and /part less than 10 minutes later.
[03:21] <infinity> xnox: Eventually, you get so used to it, you just stop responding to people.  Even the ones who stick around.  All two of them.
[08:02] <ppisati> moin
[08:20] <smb> morning
[09:01]  * apw yawns
[09:03]  * apw waves to infinity
[10:15] <caribou_> I have a twisted C compilation situation that I'd need advise for (for makedumpfile)
[10:15] <caribou_> is here a good place to ask or #ubuntu-devel would be a better place ?
[10:15] <caribou> in short, I have source code  lines that don't get compiled, even with optimization turned off
[10:16] <smb> caribou, Both seems valid. On devel there might be even more people... Now that sounds quite odd...
[10:17] <smb> Except there is some ifdefs preventing things...
[10:18] <caribou> smb: here is an output from gdb disassemble/m : http://paste.ubuntu.com/1569182/
[10:18] <smb> caribou, which is mostly useless without the source
[10:20] <caribou> smb: hold on let me fetch it for you
[10:21] <smb> caribou, Hm, wait... I guess I remember the bits a bit
[10:22] <caribou> smb: http://goo.gl/iZWUX
[10:22] <caribou> smb: new lines are added after ...(vm_struct.addr...
[10:23] <caribou> smb: only the first one added gets compiled in, the 3 others are left out
[10:24] <caribou> smb: this is to fix makedumpfile so it can extract dmesg with the new variable-length record format btw
[10:24] <smb> caribou, You are sure its not just cleverly optimized and you only get one assembly block?
[10:24] <caribou> smb: well I removed the "-O2" out of the CFLAGS, so it shouldn't optimize
[10:26] <caribou> smb: and there is no other specific CFLAG switch used (only -g and _LARGEFILE_SOURCE macros)
[10:26] <smb> caribou, Still I would trust a printk in whatever READ_MEMBER_OFFSET is expanded to more that a disassembly. Could be figuring out that the values you are looking for are just relative to some common other offset
[10:29] <caribou> smb: ok, I'll look at that, thanks
[10:36] <caribou> smb: thanks for the tip, I think I found it !!!
[10:36] <smb> caribou, ah, cool. :)
[10:36] <caribou> smb: READ_MEMBER_OFFSET makes a call to read_vmcoreinfo_long which it typed 'long'
[10:37] <caribou> smb: those 3 struct members were defined as uint16_t as opposed to the other being u64int_t
[10:37] <caribou> smb: making them uint64_t gets them compiled...  :-/
[10:38] <caribou> smb: ok, I must revisit my structure definition then,but I'm on the good path
[10:39] <smb> Hm, still it would be useful to issue a warning at least if your destination cannot hold the return...
[10:41] <caribou> smb: well, all the struct definition for the other vmcoreinfo data is defined as long, so I suppose the new ones should be as well
[10:41] <caribou> smb: but I'll check that
[10:43] <smb> caribou, certainly it should. And maybe the code is dropped because after conversion the truncated value is always 0, but still
[10:44] <caribou> smb: I got to get a better understanding of how all this data that is put in the kernel's vmcoreinfo area is managed
[10:45] <apw> henrix, bjf, we have "lost" the amd64 .ddeb for 3.2.6-36.57 and it was only brought to my attention at 8 days, too late to find out why or fix it.  pitti would like to be told when we are doing our next builds so he can track them
[10:46] <henrix> apw: hmm... any idea how we lost them?
[10:46] <apw> henrix, no we dont
[10:46] <apw> and thats the problem, we keep losing them
[10:46] <henrix> apw: ok. so, we're currently building P and Q
[10:47] <henrix> apw: shall i ping pitti? or is he already aware of it
[10:47] <henrix> ?
[10:47] <apw> henrix, i've hold him about those two indeed
[10:48] <henrix> apw: yeah, just reading logs in #ubuntu-devel :)
[10:48] <apw> arges, you guys keep some .ddebs i beleive ... you don't happen to have linux-3.2.0-36.57 for amd64 do you ?
[10:55] <cking> apw perhaps we should also archive these .ddebs automatically
[10:56] <caribou> apw: lemme check, but I think that the .ddebs never made it to the archive
[10:57] <caribou> arges needed them last week and never found them because they never made it to the archive
[10:57] <caribou> apw: so since i mirror the archive, I didn't have it either
[10:57] <caribou> cking: I *do* think so
[10:58] <caribou> cking: I'm ENOSPACE on my own backup atm
[10:58] <cking> caribou, yep, that is the main issue with kernel .ddebs
[10:58] <caribou> cking: I'm mirroring *all* the .ddebs
[10:58] <cking> yikes
[11:00] <apw> cking, no we should get the damn thing fixed it cannot be that hard
[11:00] <apw> cking, to simply keep some files
[11:01] <cking> apw, that is very true
[11:02] <apw> cking, hell it is what the archive does, only
[11:57] <brendand> henrix, can i have links to the tracking bugs for the respun kernels?
[11:57] <henrix> brendand: sure! for P: bug #1104061 for Q: bug #1103932
[11:57] <ubot2> Launchpad bug 1104061 in linux (Ubuntu) "linux: 3.2.0-37.58 -proposed tracker" [Medium,In progress] https://launchpad.net/bugs/1104061
[11:57] <ubot2> Launchpad bug 1103932 in Kernel SRU Workflow prepare-package-meta "linux: 3.5.0-23.35 -proposed tracker" [Undecided,In progress] https://launchpad.net/bugs/1103932
[11:58] <henrix> brendand: kernels are still building.
[11:58] <cking> apw, http://smackerelofopinion.blogspot.co.uk/2012/11/non-linear-characteristics-in-draining.html
[11:59] <henrix> brendand: also, i'm still waiting for the tracking bugs for the quantal lts kernel.
[11:59] <infinity> henrix: We're vaguely blocked by IS having misplaced two thirds of our ARM buildd capacity.  I'm violently jamming the kernels through, and should have them copied out of the PPA into proposed by my morning.
[12:00] <henrix> infinity: ack, thanks. yeah, i was expecting to have all of them build "by my morning" :)
[12:28] <ppisati> infinity: "having misplaced two thirds of our ARM buildd capacity"???
[12:31] <xnox> ppisati: datacenter move / reorg.
[12:37] <apw> qevents"canonical.comu3wYhuKPCYvHs2R
[12:38] <apw> what the hell is that even
[12:38] <ohsix> a password?
[12:39] <apw> ohsix, not one of mine, it looks like a bit out of the middle of some xml data i am looking at
[12:39] <ppisati> xnox: ah ok
[12:39] <apw> but why its in my but buffer instead of the stuff i wanted ... i don't know
[14:04] <ogasawara> apw: I was gonna prep an upload for Raring.  We don't have a lot queued, but its been about a week and that brcm issue seth fixed seems reason enough.
[14:04] <ogasawara> apw: you have anything else you want included
[14:04] <apw> ogasawara, ack, nothing pending from me
[14:30] <infinity> ppisati: rebase tracking bug is up for precise/ti-omap4
[14:30] <infinity> ppisati: (quantal should be in shortly)
[14:31] <ppisati> infinity: wasn't SRU frozen?
[14:32] <infinity> ppisati: You missed all the excitement over the fsnotify reverts, apparently. :)
[14:33] <infinity> ikepanhc: Ditto to you, armadaxp for P and Q will need a quick rebase for this.
[14:33] <ikepanhc> quick rebase?
[14:34] <infinity> ikepanhc: https://bugs.launchpad.net/ubuntu/+source/linux-armadaxp/+bug/1105115
[14:34] <ubot2> Ubuntu bug 1105115 in linux-armadaxp (Ubuntu) "linux-armadaxp: <version to be filled> -proposed tracker" [Medium,In progress]
[14:34] <infinity> ikepanhc: The matching quantal bug should be up shortly.
[14:34] <ppisati> infinity: ah, k
[14:35] <ikepanhc> infinity: I've test build today and it looks good to me, can upload it in 1 day
[14:38] <infinity> ikepanhc: Kay, shiny.  I want to be able to do a rushed QA/verification next week, so landing the rebases by Monday should be fine.
[14:39] <ikepanhc> infinity: ack
[14:44]  * herton -> lunch
[14:49] <infinity> henrix: quantal rebase bugs are up (including the lts-quantal you were waiting on)
[14:50] <henrix> infinity: yep. i've just exec'ed the bot manually to speed up things ;)
[14:50] <infinity> henrix: Ahh, lovely.  Thanks. :)
[14:50] <infinity> henrix: I was already copying, based on seeing that everything was published.
[14:51] <henrix> infinity: cool. i'll have the lts building later today
[14:51] <bjf> shankbot should monitor this irc channel so we can tell it to do things
[14:51] <henrix> bjf: heh, that would be nice :)
[14:53] <infinity> Does shankbot give me a grace period after I set promote-to-proposed to Fix Released before it goes looking for stuff in the archive?  Or is it just luck of cron timing?
[14:54] <infinity> (I've been intentionally not setting it until after a publisher run and mirror push, but that does mean actually remembering to twiddle the bug an hour or so after I've done the work)
[14:55] <henrix> infinity: i don't know the answer for that question, but i'm pretty sure herton does ;)
[15:19] <infinity> henrix: Alright, I'm going to have a quick nap.  I'll look for lts-Q when I wake up. :)
[15:19] <henrix> infinity: ack, thanks!
[15:20] <infinity> (I'm also going to be naughty and Fix Release my task an hour early, let's see if the bot flips out about linux-signed not being in the archive yet)
[15:20] <infinity> Well, a half hour early, I guess.  It should hit disk in ~30m.
[15:30] <lantizia> Hi, I've noticed that the kernels shipping with 12.04 and 12.10 are coming compiled with a setting turned on that wasn't present in the config file of the kernel that shipped with 11.10
[15:31] <lantizia> that setting is CONFIG_SOUND_OSS_CORE_PRECLAIM=y    and also   CONFIG_SOUND_OSS_CORE=y
[15:31] <lantizia> given OSS was completely removed in the kernel back in 11.04 release was it?      Why has settings for it re-emerged in 12.04 onwards?   That setting it seems to preserves OSS device numbers in case you have OSS compatibility compiled in to the kernel - which clearly it doesn't any longer!!!
[15:31] <lantizia> But whilst the setting is there, it prevents people from using OSS proxy/emulation techniques such as osspd (which uses fuse/cuse to fake /dev/dsp and redirects it to pulseaudio)
[15:32] <lantizia> Can anyone help me (I'm not exactly the greatest developer ever, or know the inner workings of the ubuntu development cycle) to see if we can locate a rationale for this setting re-emerging!?
[15:35] <xnox> lantizia: well each cycle there is config review where config changes are agreed upon. i'm not kernel hacker though so somebody like ogasawara or apw will probably know about it.
[15:37] <lantizia> ok
[15:40] <lantizia> omg it's in raring too
[15:40] <lantizia> looks like raring is/was/unsure going to include an osspd package too (auto copied from debian sid which now has it)
[15:41] <lantizia> no point if this setting stays in
[15:41] <apw> lantizia, we would expect OSS to be off, so if it is on that is a fail as far as i know
[15:41] <apw> lantizia, that said if noone has noticed for 15 months, then it cannot be a huge problem
[15:42] <lantizia> apw, can I somehow petition to have it removed?  i mean it wasn't there in 11.10 (because OSS has totally been removed - let it die forever) - so someone put it back!
[15:42] <xnox> well - ndiswrapper provides went unnoticed for a long time as well.....
[15:43] <apw>   * [Config] CONFIG_SND_PCM_OSS=n using pulseaudio emulation instead
[15:43] <apw> lantizia, that one there is the one we turned off to allow userspace emulation
[15:43] <apw> of the OSS stuff
[15:43] <apw> debian.master/config/config.common.ubuntu:# CONFIG_SND_PCM_OSS is not set
[15:43] <apw> and it remains off
[15:44] <lantizia> ok I'm no expert but from what I know osspd (OSS Proxy) basically uses FUSE/CUSE TO make fake /dev/dsp /dev/adsp /dev/mixer etc... so your ancient game/app thinks it's really talking to OSS
[15:44] <apw> lantizia, if you think something else should be off, we would want a bug filed for that
[15:44] <lantizia> no need for wrappers (which only work if libc is still compaible which a lot of the time it's not)
[15:44] <apw> so we can evaluate it on its merits
[15:44] <lantizia> CONFIG_SND_PCM_OSS isn't my issue
[15:44] <lantizia> CONFIG_SOUND_OSS_CORE_PRECLAIM is
[15:44] <apw> arges, you are a sound weeny, does any of your jack pants use OSS ?
[15:45] <lantizia> as that prevents the creation of  /dev/dsp   /dev/adsp /dev/mixer
[15:45] <lantizia> i have no idea what you're on about
[15:46] <apw> lantizia, i am asking someone who does a lot of sound work if we need any OSS
[15:46] <apw> at all in his opinion
[15:47] <apw> SOUND_OSS_CORE_PRECLAIM would default on if SOUND_OSS_CORE gets turned on, but it defaults off
[15:47] <lantizia> ah sorry arges is a person (oops!) i thought you were saying you 'argues' the following :D
[15:47] <infinity> https://lists.ubuntu.com/archives/kernel-team/2010-May/010647.html
[15:47] <infinity> Looks like we intentionally disabled them way back when.
[15:47] <ogra_> well, preclaim makes sure the device numbers for things like /dev/dsp are hogged all the time by the kernel
[15:47] <apw> infinity, yeah and something has broght it back, sigh
[15:48] <apw> ogra_, indeed
[15:48] <ogra_> so if any userspace emu wants to create them the major devicenumbers are gone
[15:49] <hggdh> smb: good afternoon, I got a Q for you -- on one of our test machines, running Raning/Xen, I am seeing lowmemorykiller messages being issued (killing libvirtd, xend, and others). The machine is idling... have you seen something like that?
[15:49]  * apw tries turning it back off
[15:49] <smb> hggdh, no
[15:49] <infinity> apw: d5a54f43f357d4814f2c3d53ca3d5c3f6fddebe0
[15:50] <lantizia> ogra_, it makes me cry :(  technically I have a cold but still...CRY
[15:50] <infinity> apw: Pulled in by turning on OSS_MIXER, I suspect.
[15:50] <apw> hggdh, raring/xen, i have recently set one of those up, i think i did when i made the host too small
[15:50] <apw> smb, didn't we have to make it a bit bigger
[15:50] <lantizia> osspd is a god send for getting really old Loki ported games working
[15:50] <infinity> apw: Or, MIXER_OSS, rather.
[15:51] <lantizia> and it seems the osspd package is going to be in raring (as it was copied from debian sid, and debian just packaged it) - so without fixing the kernel setting... it'll be useless
[15:51] <smb> apw, Oh, hm, I did forget about that. Though I think I only saw some other messages not the memory killer... but not sure now
[15:51] <apw> well they seem to be options which are selected, and just turning those two off they stay off
[15:51] <apw> so i suspect we have them on for nothing ...
[15:51] <hggdh> the thing there is out of two machines with Raring/Xen, one does show it, the other does not. Both have the same setup for Xen (this is happening on Dom0)
[15:51] <apw> infinity, based on what you found i think we are justified in turning it off for raring at least and we can see what happens
[15:52] <smb> hggdh, Is dom0 set for ballooning or has it maxmem clamped?
[15:52] <apw> lantizia, can you file a bug against linux and let me know the number so i have something to track it against
[15:52] <apw> infinity, as far as i can see we have the core turned on, and no drivers using it, so its a complete waste of time
[15:52] <lantizia> apw, unfortunately I've got this far and to this channel with the knowledge I have by wildly googling... I'm no expert.. i wouldn't even know how I'd file that bug
[15:53] <apw> ogasawara, you seem to be the one who turned off OSS (the old sound thing) in maverick timeframe, a couple of core bits seem to be back on in R, know of any reason or can i slam them back off
[15:53] <apw> lantizia, run "ubuntu-bug linux" in a terminal window and folow the prompts :)
[15:53] <infinity> lantizia: https://bugs.launchpad.net/ubuntu/+source/linux/+filebug
[15:53] <infinity> lantizia: Or what apw said.
[15:54] <smb> hggdh, And for the host seeing oom killer, check ps or top to find anything with a big mem footprint
[15:54] <infinity> apw: They snuck back in in P, actually, when you pulled d5a54f43f357d4814f2c3d53ca3d5c3f6fddebe0
[15:54] <hggdh> smb: looking
[15:54] <infinity> apw: Since you're the one who did it, maybe you should ask yourself if you know why. ;)
[15:55] <hggdh> smb: well, dom0_mem is set to 512k, max=512k...
[15:55] <lantizia> infinity, is this the oss thing?
[15:55] <apw> infinity, oh yeah.  looks like some kind of total fail on my part there, then i will unilaterally fix that in R for a start
[15:55] <smb> infinity, Do you expect to remember anyone of us something that is more than 2 weeks old? ;-P
[15:55] <infinity> lantizia: Yes.
[15:56] <smb> hggdh, Ok, so that would be how I set my machine. Which runs a server install
[15:56] <smb> hggdh, wait
[15:56] <smb> hggdh, Did you say 512K?
[15:56] <infinity> He had to have meant 512M.
[15:56] <hggdh> smb: my bad. 512M
[15:56] <infinity> If you can boot a dom0 with 512K, I want your setup.
[15:57] <smb> infinity, Thats what I think he meant but better be sure
[15:57] <hggdh> :-)
[15:57] <ogra_> 512k are enough for everyone !
[15:58] <apw> lantizia, drop me the bug number here when you have it so i can add it to the commit
[15:58] <smb> hggdh, ok, so yeah 512M may be ok if dom0 does not run other services. Like mine...
[15:58] <apw> ogasawara, did you do your upload yet ?
[15:59]  * apw waits impatiently for lantizia to supply the bug number
[15:59] <smb> apw is patiently as always... :)
[16:00] <herton> infinity, yes, shank bot wait 1 hour after you set promote-to-proposed to Fix Released
[16:00] <herton> *waits
[16:00] <apw> smb, well i want to get this in before ogasawara does her thing
[16:00] <infinity> herton: Oh, cool.  That's good to know.
[16:00] <hggdh> smb: will recheck all. I can understand bzr going down on 512M, but not libvirtd
[16:01] <herton> infinity, 1 hour depends on when the cron job executes, but is a minimum of 1 hour
[16:02] <infinity> hggdh: If you have anything doing scary python things (say, something using the libvirt or xend python bindings to query/fiddle with stuff), 512M goes fast.
[16:02] <infinity> hggdh: If you don't want to let your dom0 balloon, give it a swapfile.
[16:02] <smb> hggdh, Well it does not matter what. If memory gets low *something* has to die. And if it is decided that libvirtd is worthwhile...
[16:02] <hggdh> infinity: nothing much, usually, apart from building the whole of the kernel tests
[16:04] <smb> infinity, Actually its always a good idea to have some swap file...
[16:04] <infinity> smb: Well, yes.  a dom0 without some healthy swap is probably asking for trouble.
[16:05] <infinity> smb: (for domUs, running swapless may give you exactly the behaviour you want, depending, but for a dom0, it seems silly to potentially lose the whole system to an unanticipated commit spike)
[16:06] <infinity> Well, not that you actually "lose the system" if xend or libvirt die.  But it sure looks like it to someone who doesn't know how to recover.
[16:07] <ogasawara> apw: I have not uploaded yet, was doing some test builds and boots.  feel free to shove your changes up and I'll pull it in
[16:08] <hggdh> well, just reproduced it by running 'bzr branch' -- LMK kicked in after a while, killed bzr *and* libvirtd
[16:08] <smb> infinity, Yeah, I certainly would not want any server of mine have none
[16:08] <ogasawara> apw: I'm not aware of any reason for configs to be flipped back on, other than maybe our cowboy did it
[16:09] <hggdh> which is sort of a overkill. libvird memory usage did not change (visibly), so killing bzr should have been enough
[16:09] <smb> hggdh, oom killers definition of "not important" not necessarily goes along with expectation
[16:09] <hggdh> smb: most certainly agree :-)
[16:09] <infinity> hggdh: Yeah, that's not really unexpected.  A dom0 that's also used for "real work" needs some healthy swap, and if you care about it also being performant, a ballooning config.
[16:10] <hggdh> yeah. Will review the implementation on that, and add a bit of swap/balloon
[16:11] <apw> ogasawara, give me a couple to just get this bug number in
[16:11] <infinity> smb: It's been a long time since I looked at the oomkiller.  Does it intentionally try to avoid killing things with locked pages or any other such tricks?
[16:11] <infinity> smb: (Like, it's possible xend and libvirt could be doing things to make themselves less easy prey)
[16:11] <apw> lantizia, poke
[16:12] <smb> infinity, It is probably as long or longer since I looked. I thought mlock may prevent things, but then also make the overall situation less good for other things
[16:12] <lantizia> woops sorry my boss was chatting to me on IM
[16:12] <lantizia> apw, I'm here!
[16:12] <lantizia> apw, still need me to do something?
[16:12] <apw> we are holding waiting for the bug number from you, so i can commit this change
[16:13] <lantizia> ah! that command thing
[16:13] <apw> lantizia, ^^
[16:13] <infinity> smb: locking pages isn't usually the right answer to most problems, but in the xend/libvirt/qemu cases, it would almost seem to be what you'd want anyway.
[16:13] <apw> yeah especially as probabally the guest memory is real and unswappable,
[16:13] <smb> infinity, *maybe* libvirt but xend is deprecated and written in python...
[16:13] <apw> but the "controller" for it may get shoved out
[16:13] <lantizia> apw, I'm on 12.04 still - is that ok?
[16:13] <infinity> smb: Given that your dom0 (or qemu host in the qemu case) kinda has one really important job, and everything else is secondary.
[16:14] <apw> lantizia, yes
[16:14] <infinity> smb: You can totally mlock in python.  Using ctypes.  It's evil.  Don't do it.
[16:14] <lantizia> ok.. .not donee this before - signing in...
[16:14] <smb> infinity, I did not even want to think about it.
[16:15] <lantizia> apw, is my bug that I'd like BOTH of the OSS related settings in the config to simply not be in there at all (they were not even in the config file for 11.10's kernel)
[16:15]  * smb shudders
[16:15] <infinity> smb: Heh.  They're rewriting xend in a real programming language as we speak, right?
[16:15] <apw> lantizia, you are asking for them to be turned off
[16:15] <lantizia> ok :D
[16:15] <apw> i'll put the rest of the info in
[16:15] <smb> infinity, There was an ocaml version but actually they moved the whole stack to use a library written in c
[16:16] <infinity> smb: Right.  The C library.  That was what I remembered from UDS.
[16:16] <infinity> smb: If they also write C tools that link to said library, it will be a glorious day.
[16:16] <infinity> smb: (If all I ever see is python bindings and crappy python tools, congrats on not solving the problem)
[16:17] <lantizia> apw, ok - i'm just quickly typing up the whole deal :S
[16:19] <smb> infinity, They do (xm -> xl) but initially loosing the persistent domU management by that. Ok, it is better done in libvirt the same way as for kvm but then this needs the right libvirt for it. So even more that can go wrong.
[16:19]  * smb goes into a corner and cries
[16:19] <infinity> smb: libvirt and I don't get along even remotely.
[16:19] <infinity> smb: Maybe it's matured by now, but the last time I tried using it, I just got very, very angry and went back to configuring VMs by hand.
[16:20] <apw> infinity, it works ok as far as i can tell, mostly
[16:20] <infinity> Which is, y'know, trivial anyway.  Simple config files for Xen, simple command lines for qemu.
[16:20] <infinity> Or MESSY AS HELL XML files for libvirt.
[16:20] <smb> infinity, apw also was not very amused, but mostly because of the quality of virt-manager
[16:20] <infinity> Progress?
[16:20] <smb> infinity, libvirt itself isn't that bad nowadays
[16:20] <apw> it did make me mad a few times i guess, but it does seem to do the job pretty well
[16:21] <apw> thought if i knew what the command lines for each were i might cry that i have been
[16:21] <apw> through all that pain for something that easy
[16:21] <apw> lantizia, bug # ?
[16:22] <lantizia> apw, should I tick it's a security bug?
[16:22] <infinity> lantizia: No, it's not.
[16:22] <apw> no
[16:22] <lantizia> ok :D
[16:22] <lantizia> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1105230
[16:22] <ubot2> Ubuntu bug 1105230 in linux (Ubuntu) "Removal of odd OSS options in kernel compile config file" [Undecided,New]
[16:22] <lantizia> tada!
[16:22] <lantizia> ooh i feel all warm and fuzzy
[16:23] <apw> ogasawara, ok pushed and ready for your fun
[16:23] <ogasawara> apw: awesome, thanks
[16:24]  * apw isn't sure how keen he is to SRU this back as far as P
[16:25] <infinity> apw: Seems reasonably harmless to do so.
[16:25] <apw> infinity, if it just turns off like that i guess so
[16:25] <infinity> apw: Assuming it doesn't end up disabling some esoteric driver that only built in 3.2
[16:32] <arges> apw: whats up?
[16:33] <apw> arges, wondering if your jack based setups use OSS drivers for anything
[16:33] <arges> apw: no don't use OSS, just jack/alsa/pulse
[16:36] <apw> ogasawara, i think i may have knobbed it
[16:37]  * apw is investigating
[16:37] <ogasawara> apw: ok, I'll wait to kick off new builds
[16:37] <ohsix> osspd is close to being usable, but not
[16:37] <ohsix> if you want to follow up on that :p
[16:38] <ohsix> i couldn't make sense of why some of the io 'slaves' wouldn't exit, mathematica would spawn up to 32 then pulse and osspd would start giving up
[16:39] <apw> ohsix, the problem here is the preclaim isn't it
[16:39] <ohsix> yes, i was making a comment about the bug
[16:40] <lantizia> ohsix, ossp is better (compatibility) wise than anything else out there
[16:41] <lantizia> I even have an untested patch Tejun wrote for me on the linux mailing list that re-enabled mmap support
[16:41] <ohsix> i don't disagree, but like i (sort of) said, it is almost trivial to find a case where it breaks
[16:42] <lantizia> I've got Unreal Tournament, Railroad Tycoon 2, Alpha Centauri, SimCIty 3000 and Return to Castle Wolfenstein.... classic native linux games that _really_ need it to work
[16:42] <ohsix> particularly the one open() one io slave breaks easily
[16:42] <apw> ogra_, so would we think that just turning off _PRECLAIM would be enough for the older releases to make this work, to minimise the changes there
[16:43] <lantizia> wrappers can fail due to incompatible libc implementations and such - so having something that looks like the real OSS is a god send
[16:43] <lantizia> it's a shame to throw some of the best (and very few) commercial linux games away for just a sound issue
[16:43] <apw> ogasawara, ok i have fixed raring, soz about that
[16:43] <ogasawara> apw: no worries, thanks
[16:44] <lantizia> apw, is this being fixed as far back as 12.04 then? wow
[16:44] <apw> lantizia, what you running as a test bed.  i would like to see if just turning off one of these works in the odler releases
[16:44] <lantizia> apw, I'm running 12.04 now
[16:44] <apw> lantizia, i am thinking about it, the fix i have applied to raring is not goain back
[16:44] <ogra_> apw, sounds like
[16:44] <apw> lantizia, i think it would be too much
[16:44] <apw> but if turning off _PRECLAIM is enough that we might be able to do
[16:44] <lantizia> yeah it's just PRECLAIM that is the issue
[16:45] <infinity> apw: Ah-ha, so it was due to MIXER_OSS, I was right? :P
[16:45] <ohsix> preclaim doesn't let anyone else get the major numbers for oss
[16:45] <apw> ok ... i'll get you a kernel to test
[16:45] <ohsix> in case the alsa/oss shim is loaded later
[16:45] <ohsix> if you were wondering why there needed to be a preclaim :p
[16:45] <apw> infinity, some shit i cannot see we would want on when we have OSS turned off officially, but i'll let someone testing raring confirm that :)
[16:46] <apw> ohsix, yep
[16:46] <infinity> apw: Well, it was off until that ARM merge, and no one complained in maverick or oneiric.
[16:46] <lantizia> ohsix, whats "alsa/oss shim" ?
[16:46] <apw> infinity, right i have no compunction turning it off, but if _PRECLAIM will do that is much easier to justify for SRU
[16:46] <infinity> apw: True.
[16:47] <ohsix> lantizia: it's a module from alsa that will wire up OSS to an alsa driver, with all the same drawbacks oss ever had :p (one open will block all users, oss and alsa)
[16:48] <lantizia> ohsix, ah well - nevermind then lol
[16:55] <wookey> apw: I filed current state of fix against raring:
[16:55] <wookey> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1105251
[16:55] <ubot2> Ubuntu bug 1105251 in linux (Ubuntu) "Fix cross- linux-tools build" [Undecided,New]
[16:56] <wookey> I've not checked that native builds are still correct (should be OK, but you never know)
[17:05] <ogra_> apw, oooh ! i was under the assumption you took all our patches from the qunatal nexus7 kernel, i know for sure the first kernel had loglevel=1
[17:06] <ogra_> (which didnt help for these messages either btw)
[17:06] <ogra_> using the patch you once wrote
[17:08] <ogra_> gah, yeah, the patch was dropped :(
[17:08] <ogra_> console_loglevel = 4;
[17:08] <apw> ogra_, you should be able to confirm that patch would help via 'loglevel=2' on the kernel command line
[17:09] <ogra_> will try ... but i'm pretty sure it doesnt catch "err"
[17:09] <ogra_> iirc it only swallows "info"
[17:10]  * ogra_ grumbles about the broken reply-to setup of the kernel ML
[17:25] <ogra_> apw, ok, the majority of messages is gone, i still get "Powering on wifi" "Powering off wifi" all over the screen though
[17:26] <ogra_> apw, quieten_wifi_power_message.patch quietens that bit
[17:37]  * ppisati -> rush to the gym
[18:21] <lantizia> apw, did you say there was a kernel I was going to test for you?
[18:26] <ogra_> lantizia, no, he said that the fix will go into raring with the next upload
[18:27] <lantizia> ogra_, I'm sure there was something about just putting the preclaim fix into the previous two releases
[18:27] <lantizia> and me testing that
[18:27] <lantizia> lemme find it :S
 ok ... i'll get you a kernel to test
[18:29] <ogra_> ..."some shit i cannot see we would want on when we have OSS turned off officially, but i'll let someone testing raring confirm that :)" ...
[18:30] <ogra_> that made me think its raring :)
[18:30] <ogra_> anyway, you will have a kernel test request in the SRU bug you filed
[18:30] <lantizia> but before he said what I pasted he was asking what I was running and I said 12.04
[18:30] <lantizia> o_O what do I do with that then? :D
[18:30] <ogra_> SRUs dont get into the archive unverified
[18:31] <ogra_> the bug comment will tell you :)
[18:31] <ogra_> (once it is there)
[18:31] <ogra_> if you are into gaming you should take a look at steam btw ;)
[18:32] <lantizia> ogra_, already using it :D
[18:32] <lantizia> Half-Life was released yesterday! lol took them FIFTEEN years to port it to linux :P
[18:32] <lantizia> i wonder if anything else slipped back into the kernel config options when this ARM version accident merge thing happened
[18:32] <ogra_> i remember runnning it when UT was recent
[18:33] <ogra_> and iirc it ran natively
[18:33] <lantizia> nah not HL, but UT was native
[18:33] <ogra_> hmm, wasnt there a company providing a native runtime for it
[18:33] <ogra_> UT ran native, sure
[18:34] <lantizia> ogra_, nope... hell even wikipedia is saying it was released yesterday
[18:34] <lantizia> although the original HL was kinda quake based (modified into GoldSrc)... GoldSrc itself has only just been ported to linux
[18:35] <ogra_> ah, loki was the name i was looking for
[18:36] <lantizia> yeah they ported lots... I have Unreal Tournament, Railroad Tycoon 2, Alpha Centauri, SimCIty 3000 and Return to Castle Wolfenstein to get working with OSS Proxy once this is fixed
[18:36] <ogra_> right, http://en.wikipedia.org/wiki/Loki_Software agrees with you
[18:36] <lantizia> what does SRU mean and am I supposed to see it somewhere?
[18:36] <ogra_> i thought i had HL running with a lokin installer too
[18:38] <ohsix> but not mathematica bawww
[18:38] <ohsix> see if the io slaves exit properly for all those games
[18:39] <lantizia> i hope steam on linux will resurrect UT3 lol -  not willing to place any bets though
[18:39] <lantizia> ohsix, I wouldn't even know how to check that - and RTCW needs mmap anyway so I can't test that one yet
[18:39] <lantizia> not until I recompile the kernel with tejuns latest mmap fix
[18:45]  * henrix -> EOD
[20:03] <marrusl> I'm having trouble finding definitive proof if /proc/cpuinfo reflects "cpuinfo_cur_freq" or "scaling_cur_freq" from /sys.  I think it's the former, does anyone know for sure?
[20:20] <vanhoof> marrusl: its scaling_cur_freq
[20:20] <vanhoof> cpu MHz		: 2701.000
[20:20] <vanhoof> ==> cpu1/cpufreq/scaling_cur_freq <==
[20:20] <vanhoof> 2701000
[20:30] <marrusl> vanhoof, thanks!
[20:33]  * cking -> EOW
[20:37] <vanhoof> marrusl: np!
[20:50]  * ogasawara lunch
[22:00] <catbus1> Can anyone tell me if I am right about this? The kernel SRU for 3.5.0 has entered the 2nd phase (verification), and if there is any SRU request, it won't be reviewed until 2 weeks later. And if it's good to go, it will be in the -updates at the end of 2/28, 5 weeks later?
[22:36] <lantizia> apw, arges, infinity, ogra_, ohsix:  RE: The OSS fix from earlier today....   I got in touch with Tejun (the author of osspd), joined the project on SourceForge and I'm making a mailing list (that'll include previous conversations a few of us have had over the last year or so in email)... would you be interested in being on the list and if so PM me what name/e-mail to add.


[08:17] <mup> PR snapd#13093 closed: cmd: rework configure.ac <Created by valentindavid> <Closed by valentindavid> <https://github.com/snapcore/snapd/pull/13093>
[09:43] <mup> PR snapd#13108 opened: release: 2.60.2 (#13063) <Simple 😃> <Skip spread> <Created by mvo5> <https://github.com/snapcore/snapd/pull/13108>
[12:39] <mup> PR snapd#13109 opened: tests/main/interfaces-mount-control: use auditd to match apparmor errors <Created by valentindavid> <https://github.com/snapcore/snapd/pull/13109>
[12:54] <mup> PR snapd#13110 opened: wrappers: use `Ensure` in snap linking operations for snap binaries/icons/desktop files <Needs Samuele review> <Pulse> <Created by ZeyadYasser> <https://github.com/snapcore/snapd/pull/13110>
[13:04] <mup> PR snapd#13111 opened: tests/nested: spread test added for panicing on bad plug <Run Nested -auto-> <Created by Meulengracht> <https://github.com/snapcore/snapd/pull/13111>
[13:14] <mup> PR snapcraft#4210 closed: kernel plugin: properly generate Ubuntu kernel .config <Created by arighi> <Merged by sergiusens> <https://github.com/snapcore/snapcraft/pull/4210>
[13:14] <mup> PR snapcraft#4299 closed: Sgmoore/kde neon ext updates <Created by ScarlettGatelyMoore> <Merged by sergiusens> <https://github.com/snapcore/snapcraft/pull/4299>
[15:15] <mup> PR snapd#13108 closed: release: 2.60.2 (#13063) <Simple 😃> <Skip spread> <Created by mvo5> <Merged by mvo5> <https://github.com/snapcore/snapd/pull/13108>
[15:20] <mup> PR snapd#13112 opened: cmd/configure.ac: rework <Created by valentindavid> <https://github.com/snapcore/snapd/pull/13112>
[15:54] <mup> PR snapcraft#4248 closed: spread: separate legacy tests <Created by lengau> <Closed by lengau> <https://github.com/snapcore/snapcraft/pull/4248>
[16:15] <mup> PR snapd#13023 closed: prompting/apparmor: add apparmor package for use in prompting <Created by olivercalder> <Merged by mvo5> <https://github.com/snapcore/snapd/pull/13023>
[16:15] <mup> PR snapd#13113 opened: tests: refresh and revert core and snapd having shared memory interface <Created by sergiocazzolato> <https://github.com/snapcore/snapd/pull/13113>
[23:30] <mup> PR snapcraft#4332 opened: (DRAFT) environment: error when build-for arch variable cannot be evaluated <Created by mr-cal> <https://github.com/snapcore/snapcraft/pull/4332>


[20:20] <dandrader> bregma, do you recall having looked at this merge request? -> https://code.launchpad.net/~jpakkane/geis/python3-preparation/+merge/100139
[20:22] <bregma> yes, it looks OK to me
[20:24] <dandrader> alright, thanks
[20:25] <bregma> it did not solve the original python3 problem, which was the XDG generation scripts and not the geis runtime


[04:45] <webchat95> Hi, I upgraded from Focal to Jammy. The volume icon disappeared and the indicators look messy, with some strange empty spaces: https://imgur.com/7z0E7sT.png
[04:45] <webchat95> Pretty nice default background on the login screen 👍
[04:50] <webchat95> May the missing sound icon be related with the fact Xubuntu 22.04 uses pipewire instead of pulseaudio?
[05:00] <Montresor> I'm on Debian unstable with xfce4-pulseaudio-plugin and pipewire, granted I have the PA plugin. :3
[05:07] <webchat95> Hmm... I wasn't using the plugin, it was an indicator, I think
[05:07] <webchat95> Because the plugin icon gets huge
[05:08] <webchat95> https://imgur.com/Vv7GYXf.png
[05:09] <Montresor> Huh, shouldn't because xfce4-pa-plugin has been default for a while now, -indicator-plugin shouldn't really be used for much these days.  Also wow, that's an early jump to Jammy!  They've got an OpenSSL 3.0 transition, Php 8.1, and Ruby 3.0 staged to go.
[05:09] <Montresor> Wow, OK.  Ctrl+right click and see what options you have?
[05:12] <webchat95> Properties, about, move, remove, panel. Inside the properties, there are options about keyboard shortcuts, show notifications on volume change, audio mixer program, and setting about controlling media players
[05:13] <Montresor> Sounds a bit like -pa-plugin to me, yeah.  Could try about.  Anywho, odd a bit.  Maybe the square options would work, but I don't use a virt panel either soo. :3


[01:39] <bluesabre> knome: pong
[01:39] <bluesabre> slickyma1ter
[01:39] <knome> umhumm, sorted
[01:39] <knome> xubuntu-docs 12.04.2 is in.
[01:40] <bluesabre> the dokuwiki can be updated to not say "staging", give it a more lovely facade :)
[01:40] <knome> had to dig up your .dsc and .tar.gz to get the binary images uploaded
[01:40] <bluesabre> knome: fantastic
[01:40] <knome> and everything is as supposed now
[01:40] <slickymaster> bluesabre, MenuLibre 2.0 series is completely translated into portuguese even though LP is showing 0% translated
[01:42] <bluesabre> thanks slickymaster: I'll try to figure out what the issue with lp
[01:42] <bluesabre> wish me luck ;)
[01:42] <knome> good luck
[01:42] <knome> the canonical servers have been playing games today
[01:42] <slickymaster> another thing, bluesabre, are you ok with us linking your wiki from the docs, or are you planning to move the docs?
[01:43] <bluesabre> slickymaster: I'm fine with linking to it, I have no intention of relocating them if its not necessary
[01:43] <bluesabre> mugshot and menulibre both link to the dokuwiki in their respective --help
[01:44] <bluesabre> or/ manpages
[01:44] <slickymaster> great, thanks bluesabre
[01:45] <bluesabre> catfish 1.0 is in trusty
[01:45] <bluesabre> I think mugshot should make it, it made it into debian today
[01:46] <bluesabre> not sure if we have to do anything, or if it will be pulled in with the debian sync before debian import freeze
[01:46] <ochosi> nice work bluesabre
[01:46] <bluesabre> its Noskcaj to thank
[01:46] <bluesabre> he's been a packaging machine
[01:47] <ochosi> well you've done a fair share of coding, no need to be modest about that
[01:48] <ochosi> bluesabre: if you have time on the weekend, we could try to get the greeter in shape for a release
[01:50] <bluesabre> ochosi: I might have such an opportunity saturday/sunday morning
[01:51] <ochosi> cool
[01:51] <ochosi> currently, the indicator-stuff needs some testing
[01:51] <ochosi> brainwash said that it slows down the greeter
[01:51] <ochosi> (which is hard to test on my machine)
[01:52] <ochosi> would be good to ask him to find out whether it's slower than unity-greeter
[01:56] <ochosi> only two weeks till feature-freeze...
[02:02] <ochosi> anyway, i'm out
[02:03] <Unit193> Tschau.
[02:16] <bluesabre> yeah, I'll try to get some testing in tomorrow maybe
[09:40] <elfy> hi slickyma1ter
[09:40] <elfy> sigh
[09:40] <elfy> hi slickymaster
[09:40] <slickymaster> morning elfy
[09:41]  * elfy is busy checking core testcases and raising bugs
[09:41] <elfy> again
[09:41] <slickymaster> now I'm not sure If I must had logged in as slickymaster or slickyma1ter
[09:42] <elfy> webchat is slickymaster - you're alterego on dagobah is slickyma1ter
[09:42] <slickymaster> ok, thanks elfy
[10:11] <bluesabre> woot
[10:11] <bluesabre> mugshot
[10:12] <bluesabre>      0.2-1 0
[10:12] <bluesabre>         500 http://us.archive.ubuntu.com/ubuntu/ trusty/universe amd64 Packages
[10:12] <bluesabre> back to bed to sleep like a normal human
[10:12] <slickymaster> sweet dreams bluesabre
[10:12] <Unit193> >_>
[10:13] <bluesabre> Unit193: go to bed D:
[10:27] <elfy> knome: - volman testcase - specifies opening with a bunch of different media - should we make it obvious that not having a 'type' of media is not a cause for failing the testcase
[10:27] <elfy> and that people should just note in comments what they don't have
[10:28] <knome> elfy, or the other way, always specify what they *did* test?
[10:28] <elfy> that works too - okey doke :)
[10:28] <knome> don't know. either way works for me, but you are right in the failing part.
[10:28] <elfy> yep
[12:09] <elfy> slickymaster: if you get chance to look https://code.launchpad.net/~elfy/ubuntu-manual-tests/xfcecorecheck/+merge/205140
[12:10] <slickymaster> I will after lunch elfy, scout's word
[12:10] <elfy> thanks :)
[12:10] <elfy> talking of which ...
[12:11] <slickymaster> hungry?
[12:11] <elfy> is there a Y in the day ...
[12:11] <slickymaster> :)
[12:19] <knome> bbl
[12:27] <slickymaster> ochosi: ping
[12:27] <slickymaster> you around?
[12:27] <ochosi> slickymaster: pong
[12:27] <ochosi> what up?
[12:27] <slickymaster> ochosi: I'm starting to port xfdesktop from bluesabre's wiki to xub -docs
[12:28] <slickymaster> the idea is to rewrite the existing section with just the highlights
[12:29] <ochosi> sounds cool
[12:29] <slickymaster> any thoughts on everything in particular you should think ought to be ported?
[12:29] <ochosi> you mean thoughts on what highlights to point out?
[12:29] <slickymaster> what do you see as important to be placed in the docs?
[12:29] <slickymaster> ecatly
[12:29] <ochosi> i'd explain stuff like the time-based changing of the wallpaper
[12:29] <slickymaster> exactly
[12:30] <ochosi> many settings are easy to understand in the dialog, that's one of the more complex ones
[12:30] <slickymaster> keep in mind that what's going to be rewritten is //usr/share/xubuntu-docs/desktop-guide/guide-desktop.html#customizing-appearance
[12:30] <ochosi> then, the multi-monitor handling
[12:30] <slickymaster> other than that, anything else?
[12:31] <slickymaster> did you get to finish the multi-monitor section in blusabre's wiki?
[12:31] <ochosi> afaik the "set as wallpaper" shortcut in thunar is currently broken
[12:31] <ochosi> it would have to be updated to work with xfdesktop4.11
[12:32] <ochosi> so better re-think whether that shouldn't be removed from the docs
[12:32] <ochosi> (or we get someone to write a patch)
[12:32] <slickymaster> that patch would have to be done before doc-freeze
[12:32] <ochosi> hm, sry about dropping the ball a bit on the xfdesktop docs. i was in touch with eric_the_idiot_ and NSchermer to get them merged, but the whole docs-versioning thing held everything up :/
[12:33] <ochosi> when's doc-freeze again?
[12:33] <slickymaster> 6 weeks from now
[12:33] <ochosi> ok
[12:34] <ochosi> hm, well i might be able to look into fixing that...
[12:34] <slickymaster> if I'm not mistaken
[12:34] <ochosi> currently wanna fix a few things in the greeter first though
[12:36] <ochosi> slickymaster: i'll send another email about the xfdesktop docs now...
[12:37] <slickymaster_> damn internet connection
[12:37] <slickymaster_> ochosi: I might have missed something you said
[12:38] <elfy> he said "currently wanna fix a few things in the greeter first though" "slickymaster: i'll send another email about the xfdesktop docs now..."
[12:38] <slickymaster_> thanks elfy
[12:39] <ochosi> thanks parrot-elfy :)
[12:39] <elfy> assuming that is you know what the last thing you said was :p
[12:39] <ochosi> we should get a parrot-bot that PMs the last 20 lines that were said in the channel :>
[12:39] <slickymaster_> these days one starts to even doubt that :P
[12:39] <elfy> ochosi: I was really kind too - I didn't ping that ochosi guy a bunch of times
[12:39] <elfy> ochosi: lol
[12:39] <ochosi> indeed
[12:40] <elfy> sat here doing tests for zequence - I hope he knows he owes me now :p
[12:40] <slickymaster_> so, just to wrap things up, do you think there's any chances of doing anything with the multi-monitor issue ochosi
[12:41] <zequence> elfy: I'm too poor to pay you ;)
[12:41] <elfy> that's ok - we'll be doing beta 1 tests for trusty soon :p
[12:42] <ochosi> slickymaster_: yes, i promise i'll do that today or tomorrow
[12:42] <ochosi> currently @work, so only one monitor
[12:42] <slickymaster_> ok, thanks, I'll owe you one
[12:42] <ochosi> thanks for reminding me
[12:43] <slickymaster_> np
[12:43] <elfy> zequence: I've done the install test for 32 bit - got no way to do the live session persistence test one
[12:43] <ochosi> well, i think we'll just be about even (or even i might still owe you for all the great work you did on the docs)
[12:45] <ochosi> brb
[12:48] <slickymaster> elfy: in your MP (https://code.launchpad.net/~elfy/ubuntu-manual-tests/xfcecorecheck) all the testcases number match the ones in the tracker, right?
[12:48] <elfy> I hope so - or it's going to go horribly wrong
[12:49] <slickymaster> just confirming
[12:50] <slickymaster> do you want me to review it in LP, or just give you a opinion here?
[12:51] <slickymaster> elfy: ^^^
[12:51] <elfy> best do it on LP
[12:52] <slickymaster> okie dokie, you'll have it this afternoon
[12:53] <elfy> thanks - I'll get things sorted later
[12:56] <slickymaster> lunch time
[12:56] <slickymaster> brb ->
[12:59] <ochosi> hmp, so for the thunar wallpaper plugin i'm afraid we'll have to patch thunar for ubuntu
[15:09] <elfy> knome: oh yea - why wouldn't the tracker let me mark the alternates as ready yesterday? confused ...
[15:10]  * knome shrugs
[15:12] <elfy> lol - I did that as well - didn't make the slightest difference when I did it though :)
[15:14] <knome> so... do you want a release announcement?
[15:16] <elfy> didn't have one for .3 that I remember or can see
[15:17] <knome> .4 is the last point update though, and we have the new docs in
[15:17] <knome> though i don't feel strongly either way
[15:17] <elfy> mmm - well I don't fee strongly either
[15:17] <elfy> I'd guess that those on .3 would have done the docs if they'd needed to and wouldn't likely notice
[15:18] <elfy> or .1 or .2
[15:18] <knome> was a release announcement for .1
[15:18] <knome> http://xubuntu.org/news/12-04-1-release/
[15:18] <knome> could do something similar this time, a short announcement
[15:18] <knome> (also noting that it is indeed the last point release)
[15:18] <elfy> ok
[15:19] <knome> i have about until 16UTC to draft it if you want
[15:19] <knome> http://pad.ubuntu.com/blbAPMlWQj
[15:19] <elfy> ok - I'm about to wander - will be back in a short while
[15:23] <elfy> bah - back shortly
[15:23] <knome> oki
[15:34] <knome> elfy, http://xubuntu.org/?p=2072&preview=true
[15:34] <elfy> I's back
[15:34] <slickymaster> elfy: are you back?
[15:34] <slickymaster> :)
[15:34] <knome> elfy, feel free to publish when cjwatson announces if i'm not around
[15:35] <elfy> knome: ok - looks ok to me too
[15:35] <slickymaster> elfy: Bug #1276965: Test Case 1583 ->
Click "Gear Icon" on the menu bar
 if you press the gear icon a menu won't drop down, what happens is that Application Finder opens
[15:36] <slickymaster> in order to the menu drop down what has to be clicked is the arrow icno to the right of the gear icon
[15:36] <slickymaster> s/icno/icon
[15:37] <elfy> knome: if you go - make sure you've not got it locked then - and save it :p
[15:37] <knome> oops :P
[15:37] <knome> released the lock.
[15:37] <elfy> :p
[15:38] <knome> btw, you can force unlocking
[15:38] <knome> not that it is wise, but if i would have been gone...
[15:38] <elfy> knome: I know - but I didn'ty know if it had been saved or anything :p
[15:38] <knome> it is, it is
[15:39] <elfy> slickymaster: hang on - catching up :)
[15:40] <brainwash> recent lightdm update seems to be broken here
[15:40] <elfy> slickymaster: aaah - I see that the arrow is actually seperate from the icons ...
[15:40] <slickymaster> yes
[15:41] <elfy> not very apparent for one with knackered eyes
[15:41] <slickymaster> lol
[15:41] <slickymaster> another thing, in that test you have
Click "Switch Icon" on the menu bar
 what's this icon?
[15:42] <slickymaster> because I'm not seeing it in my task manager
[15:45] <slickymaster> elfy: ^^^are you referring to the Settings for Task Manager icon?
[15:45] <elfy> the one that looks like a set of switches
[15:46] <elfy> calling these icons names that mean nothing is a matter of taste :p
[15:46] <slickymaster> well that one is the Settings for Task Manager
[15:47] <slickymaster> elfy: I think that what you intend is the the arrow icon to the right of that one
[15:47] <slickymaster> :P
[15:47] <slickymaster> they are also separate icons
[15:48] <elfy> probably - I'm in the middle of a bunch of stuff here - including hungry kids
[15:48] <elfy> at the moment - the testcase says click execute and click preferences
[15:48] <slickymaster> I'll comment it in LP
[15:48] <elfy> neither of which is actually there
[15:48] <slickymaster> yeas, you're right about that
[15:49] <elfy> but I didn't actually realise that there was a button and menu either
[15:49] <elfy> just forget that one - and look at the others
[15:49] <elfy> bbl
[15:49] <elfy> and the quit button has just disappeared as well
[15:51] <slickymaster> yes, you just have it when you right-cilik it in the panel
[16:01] <zequence> Did live session persistance work in Xubuntu 12.04.4?
[16:02] <zequence> Or, has no one tested that before?
[16:03] <elfy> I'm bad - never check it tbh - and in fact we rejigged our live testcase to read like this http://iso.qa.ubuntu.com/qatracker/testcases/1303/info
[16:03] <elfy> slickymaster: I'm back now and looking
[16:03] <slickymaster> I'm half way through my reviewing
[16:08] <elfy> don't bother with task manager - I'm redoing it as I speak
[16:08] <elfy> unless you already have :)
[16:11] <knome> elfy, i'm off, you need to publish the article :)
[16:11] <knome> ->
[16:15] <slickymaster> elfy: https://code.launchpad.net/~elfy/ubuntu-manual-tests/xfcecorecheck/+merge/205140
[16:18] <elfy> Line 140 needs to be reworded because when a user hits Ctrl+W, the note doesn't get deleted, a dialog prompts him for an answer
[16:18] <elfy> then there's a bug - it just deletes here ...
[16:18] <elfy> slickymaster: ^^
[16:18] <slickymaster> elfy: don't you get that prompt?
[16:18] <elfy> nope
[16:18] <slickymaster> I get it
[16:19] <elfy> trsuty? version 1.7.7
[16:19] <slickymaster> elfy: I have xfce4-notes:   Installed: 1.7.7-3ubuntu2
[16:19] <slickymaster> yes, in Trusty
[16:20] <elfy> mmm - definitely not here
[16:21] <slickymaster> then it's definitely a bug in yours
[16:21] <elfy> 1.7.7-3ubunt
[16:21] <slickymaster> weird, we're both with the same version
[16:22] <slickymaster> maybe brainwash could check his'
[16:22] <slickymaster> brainwash: ^^^
[16:22] <elfy> I can create notes with ctrl+n as fast as I want - then delete them with ctrl+w just as quickly
[16:22] <elfy> and that is both in this mutilated install and today's daily
[16:23] <slickymaster> well, the existence of the prompt makes all the sense
[16:23] <slickymaster> so a note won't get deleted carelessly
[16:24] <elfy> I agree
[16:24] <elfy> mmm - ok I will reset that testcase - obviously a bug then
[16:24] <slickymaster> other then those two tests I think you are to be congratulated
[16:27] <elfy> ok - I'll rejig the task manager one later, set the notes one back
[16:27] <elfy> and not assume that the testcase is incorrect :p
[16:29] <slickymaster> when Unit193 wake up, we can nag him to see the behavior he gets in his system
[16:32] <elfy> bug 1277154
[16:46] <elfy> slickymaster: done those now
[16:57] <slickymaster> elfy: https://code.launchpad.net/~elfy/ubuntu-manual-tests/xfcecorecheck/+merge/205140
[16:58] <elfy> thanks slickymaster
[16:58] <slickymaster> np
[17:19] <elfy> I beat bzr into submission
[17:19] <slickymaster> lol
[17:20] <slickymaster> no machine will defeat us
[17:20] <elfy> well I've not synced yet :p
[17:30] <elfy> synced now
[17:35] <slickymaster> \o/ elfy: 1 - bzr: 0
[17:36] <elfy> :)
[18:16] <slickymaster> bbl ->
[18:55] <knome> !team | meeting time
[18:58] <ali1234> o/
[18:58] <knome> would somebody else like to chair?
[18:59] <Noskcaj> o/
[19:00] <pleia2> o/
[19:00] <slickymaster> o/
[19:01] <jjfrv8-work> o/  can't chair - at work.
[19:02] <knome> #startmeeting
[19:02] <meetingology> Meeting started Thu Feb  6 19:02:06 2014 UTC.  The chair is knome. Information about MeetBot at http://wiki.ubuntu.com/meetingology.
[19:02] <meetingology> Available commands: #accept #accepted #action #agree #agreed #chair #commands #endmeeting #endvote #halp #help #idea #info #link #lurk #meetingname #meetingtopic #nick #progress #rejected #replay #restrictlogs #save #startmeeting #subtopic #topic #unchair #undo #unlurk #vote #voters #votesrequired
[19:02] <knome> #endmeeting
[19:02] <meetingology> Meeting ended Thu Feb  6 19:02:32 2014 UTC.
[19:02] <meetingology> Minutes (wiki):        http://ubottu.com/meetingology/logs/xubuntu-devel/2014/xubuntu-devel.2014-02-06-19.02.moin.txt
[19:02] <meetingology> Minutes (html):        http://ubottu.com/meetingology/logs/xubuntu-devel/2014/xubuntu-devel.2014-02-06-19.02.html
[19:02] <knome> #startmeeting Xubuntu community meeting
[19:02] <meetingology> Meeting started Thu Feb  6 19:02:38 2014 UTC.  The chair is knome. Information about MeetBot at http://wiki.ubuntu.com/meetingology.
[19:02] <meetingology> Available commands: #accept #accepted #action #agree #agreed #chair #commands #endmeeting #endvote #halp #help #idea #info #link #lurk #meetingname #meetingtopic #nick #progress #rejected #replay #restrictlogs #save #startmeeting #subtopic #topic #unchair #undo #unlurk #vote #voters #votesrequired
[19:02] <elfy> o/
[19:02] <knome> #topic Open action items
[19:03] <knome> will have to dig them up...
[19:03] <ali1234> gtk3 indicators
[19:04] <knome> ali1234, will we carry that on?
[19:04] <ali1234> yes. nothing further happened with the upstart porting, but something new also came to my attention recently
[19:04] <knome> oki
[19:04] <knome> #action ali1234 follows up on gtk3 indicator status
[19:04] <meetingology> ACTION: ali1234 follows up on gtk3 indicator status
[19:04] <knome> #action ali1234 and micahg to follow up on gtk3 indicator stack issues
[19:04] <meetingology> ACTION: ali1234 and micahg to follow up on gtk3 indicator stack issues
[19:05] <knome> #nick micahg
[19:05] <knome> #action     elfy to poke Noskcaj if time-admin and users-admin do not exist in the next daily
[19:05] <meetingology> ACTION: elfy to poke Noskcaj if time-admin and users-admin do not exist in the next daily
[19:05] <ali1234> namely that elementary also is a user of indicators, and they are in the same boat as us, except that they don't seem to be as well up with what is going on
[19:05] <knome> Noskcaj, did you get that sorted out with pitti?
[19:05] <ali1234> so i'm going to go and have a chat with them, if i can
[19:05] <elfy> knome: that's been put to bed now
[19:05] <knome> ali1234, ok, so we're steering that ship; thanks for keeping updated
[19:05] <knome> #undo
[19:05] <meetingology> Removing item from minutes: <MeetBot.items.Action object at 0x18d3b90>
[19:05] <Noskcaj> knome, yep. I screwed up on some DESTDIR stuff
[19:05] <knome> elfy, cheers :)
[19:05] <knome> Noskcaj, ok, great to have it sorted then
[19:06] <knome> #action knome to be in touch with people re Tech Lead position
[19:06] <meetingology> ACTION: knome to be in touch with people re Tech Lead position
[19:06] <knome> will carry one
[19:06] <knome> *on
[19:06] <knome> i think we're good with the bluetooth stuff.
[19:07] <knome> #action micahg to talk with the DMB and separate -dev from upload rights so we can allow more people to push to xubuntu branches
[19:07] <meetingology> ACTION: micahg to talk with the DMB and separate -dev from upload rights so we can allow more people to push to xubuntu branches
[19:07] <knome> micahg-work, ping, is that done?
[19:08] <micahg-work> working on it
[19:08] <knome> ok, carrying on
[19:09] <knome> #action xubuntu-qa to make sure there is a blueman testcase
[19:09] <meetingology> ACTION: xubuntu-qa to make sure there is a blueman testcase
[19:09] <knome> #nick xubuntu-qa
[19:09] <knome> and from the docs meeting:
[19:09] <knome> #action Unit193 to do merge proposals for "X performs Y" styled listings for the docs
[19:09] <meetingology> ACTION: Unit193 to do merge proposals for "X performs Y" styled listings for the docs
[19:09] <knome> #nick Unit193
[19:09] <knome> #topic Team updates
[19:10] <knome> use #info and #action as appropriate.
[19:10] <knome> floor is yours
[19:10] <slickymaster> #info slickymaster has finished porting the Mugshot documentation into the Xubuntu docs
[19:10] <elfy> knome: actioning something is great - but if we've not got any bluetooth to check - it'll get moved on
[19:10] <slickymaster> #info slickymaster started to work on porting the Xfdesktop documentation into Xubuntu docs
[19:11] <jjfrv8-work> #info Docs team held a Trusty meeting and assignments were handed out
[19:11] <elfy> #info xubuntu-qa Package testing - Settings Manager - mandatory testing +2, run-once and optional +1
[19:11] <elfy> #info xubuntu-qa 12.04.4 32bit/ Live 4 tests, Alt 5 test
[19:11] <elfy> #info xubuntu-qa 12.04.4 64bit/ Live 6 tests, Alt 6 tests
[19:11] <elfy> #info xubuntu-qa Trusty Daily 32 bit 11 tests
[19:11] <elfy> #info xubuntu-qa Trusty Daily 64 bit 18 tests
[19:11] <elfy> #info xubuntu-qa XFCE Core Package testing due next week
[19:11] <elfy> #info xubuntu-qa light-locker has seen testing now
[19:11] <knome> elfy, we should be shipping blueman
[19:11] <knome> :)
[19:11] <jjfrv8-work> #info Kudos to knome and bluesabre for getting the SRU Docs update through all the hurdles
[19:11] <knome> and i can organize testing for the testcase :)
[19:12] <knome> yeah, yay, fixed looks for the docs in 12.04!
[19:12] <pleia2> \o/
[19:12] <Noskcaj> weather plugin 12.04 status?
[19:13] <elfy> knome: blueman - mandatory, optional or run-once
[19:14] <knome> elfy, either opt or once
[19:14] <elfy> #info elfy Blueman added to Network Testsuite
[19:15] <elfy> so that's done then
[19:15] <knome> hehe, nice
[19:15] <knome> though one can argue if it's network or not >:)
[19:16] <elfy> yep - we can argue all you like - the die is cast :p
[19:16] <ali1234> i tried to use blueman today and it crashed - for a2dp/sound :(
[19:16] <knome> ali1234, did you file a bug?
[19:16] <ali1234> no, it's saucy, nobody will care
[19:17] <ali1234> probably won't be able to reproduce it either
[19:17] <knome> #info knome and pleia2 helped startubuntu create some xubuntu-branded versions of "xp to *buntu*" flyers
[19:17] <Unit193> Got indicator-sound merged.
[19:17] <knome> Unit193, caaaaan you #infoooo
[19:17] <elfy> :p
[19:17] <pleia2> #info the flyers were widely shared on social media and pleia2 is printing some up for an upcoming conference
[19:17] <pleia2> #link http://xubuntu.org/marketingresources/
[19:18] <knome> pleia2, still, you don't need #link with bare links ;)
[19:18] <pleia2> #info site updated to link to several language variations on spreadubuntu.org
[19:18]  * pleia2 shrugs
[19:18] <Unit193> #info got pavucontrol merged into indicator-sound as an alternate recommends to the control centers, so we shouldn't be pulling them in because of that at least.
[19:19] <Unit193> Just waiting to hear back from the two artists for the xubuntu-community-artwork package, also if mica has time to review it, but not sure he does.
[19:20] <knome> Unit193, this is a meeting, just proudly ping people :P
[19:20] <knome> re: #xubuntu, i have the page ready to be updated, waiting for cjwatson's ack of release
[19:21] <knome> anything else for the updates?
[19:21] <knome> #topic Announcements
[19:21] <knome> #info 12.04.4 will be released any minute!
[19:22] <pleia2> :D
[19:22] <slickymaster> I have an offtopic announcement
[19:22] <jjfrv8-work> #info With knome's help, jjfrv8 received approval for ~ubuntu-core-doc membership
[19:22] <knome> \o/
[19:22] <Unit193> \o/
[19:22] <elfy> \o/
[19:22] <slickymaster> congrats jjfrv8
[19:22] <knome> i just went and marked that as done in the blueprint
[19:22] <slickymaster> today is my Ubuntu Membership application, at 22:00 UTC, in #ubuntu-meeting. So if you guys feel like showing up and support it I would appreciate it
[19:23] <elfy> it's a bit late ... :p
[19:23] <knome> pleia2, was that at the same time as the docs meeting? :D
[19:23] <knome> too many meetings today.
[19:23] <pleia2> knome: yes
[19:23] <slickymaster> yes it is, knome :P
[19:23] <pleia2> indeed
[19:23] <knome> slickymaster, if i'm around, will be there
[19:23] <slickymaster> tks
[19:23] <Unit193> slickymaster: Since I didn't write one yet, make sure to ping me right before so I will be there?
[19:23] <knome> #info Debian Import Freeze is today
[19:23] <slickymaster> will do Unit193
[19:23] <knome> #info Feature Freeze is in 2 weeks
[19:23] <slickymaster> and also you, micahg-work
[19:24] <Unit193> Yeah, sorry.
[19:24] <knome> #info Beta 1 is in 3 weeks, freeze in the first half of that week
[19:24] <knome> #topic Agenda
[19:24] <knome> no specific agenda items.
[19:25] <knome> does anybody have something else to discuss?
[19:25] <Noskcaj> weather plugin in 12.04
[19:25] <Noskcaj> my MOTU application
[19:25] <knome> what's with the weather plugin?
[19:25] <pleia2> after yesterday's doc meeting, I'm putting together a release checklist for the website (what we need to create/update)
[19:26] <knome> pleia2, don't we have that in the wiki?
[19:26] <knome> let me dig that up.
[19:26] <knome> https://wiki.ubuntu.com/Xubuntu/Processes#Release_Cycle
[19:26] <knome> specifically, https://wiki.ubuntu.com/Xubuntu/Processes#Releasing
[19:27] <pleia2> knome: it needs updating
[19:27] <knome> yep.
[19:27] <knome> but please do it on the wiki :)
[19:27] <pleia2> "Update the website" isn't enough ;)
[19:27] <knome> i'm also thinking that could have its own subpage in Processes
[19:27] <schproodle> Testing QATracker using VirtualBox. Testing Post-Install.  Pendrive insertion fails in VM but it is mounted by the host machine.
[19:27] <knome> well there's also "wiki maintaining"
[19:27] <pleia2> we need to come up with our FAQ post, define which pages need updates, etc
[19:28] <knome> what we probably need is gather all these in one big calendar
[19:28] <knome> or, a similar table as the release schedules
[19:28] <knome> schproodle, we're in the middle of the meeting, if you can wait for 15 minutes, would be good.
[19:28] <pleia2> Unit193 could just put these milestones into the xubuntu calendar
[19:28] <knome> schproodle, feel free to take part in the meeting though
[19:28] <knome> xubuntu calendar is a bit meh :|
[19:29] <schproodle> I get the donuts eh :)
[19:29] <knome> TBH, i think the release schedule table is surprisingly good
[19:29] <Unit193> pleia2: Sure, sorry what ones?
[19:29] <pleia2> so you don't want it in a calendar? :)
[19:29] <knome> pleia2, can be *as well*
[19:29] <pleia2> Unit193: https://wiki.ubuntu.com/Xubuntu/Processes#Releasing
[19:29] <knome> pleia2, but i guess i'd also like to have a release-specific calendar
[19:29] <knome> that should of course be updated per release
[19:30] <pleia2> no moar calendars
[19:30] <knome> err,
[19:30] <knome> i mean
[19:30] <knome> wiki table
[19:30] <knome> :P
[19:30] <pleia2> ah
[19:30] <knome> ala https://wiki.ubuntu.com/TrustyTahr/ReleaseSchedule
[19:30] <elfy> :)
[19:30] <pleia2> yeah sure
[19:30] <knome> i do agree that the processes page needs updating though
[19:31] <knome> i'm more than happy to help with it any day our schedules allow to sit down together
[19:31] <knome> ...figuratively speaking
[19:31] <pleia2> ok, I'll start brainstorming when I have extra braincells, then we can flesh it out
[19:31] <knome> sure, great, thanks
[19:32] <knome> #action pleia2 starts working on getting the Processes wikipage updated and cleaned
[19:32] <meetingology> ACTION: pleia2 starts working on getting the Processes wikipage updated and cleaned
[19:32] <Unit193> In addition to, or rather than?
[19:32] <knome> Unit193, we should probably update the calendar with those milestones as well.
[19:33] <knome> and i should probably either learn using the calendar (in a non-technical way), or just dismiss all schedules after trusty ;)
[19:34] <knome> #action Unit193 to add process-related tasks as events in the xubuntu team calendar
[19:34] <meetingology> ACTION: Unit193 to add process-related tasks as events in the xubuntu team calendar
[19:35] <knome> Noskcaj, still waiting for an answer re: weather plugin
[19:35] <Noskcaj> ok
[19:35] <knome> so what's up with it in precise?
[19:36] <micahg-work> in unapproved
[19:37] <knome> is there something specific to be discussed about it, or do we just want it to move along?
[19:37] <Noskcaj> I just wanted to check the status with micahg-work
[19:37] <knome> okay
[19:38] <knome> Noskcaj, ok, motu application
[19:38] <micahg-work> if the weather plugin is needed for something, poke the SRU team, but precise-proposed has been frozen the last few days
[19:38] <Noskcaj> well weather-plugin is complete dead currently
[19:39] <Noskcaj> I've not had a reply to my motu application in three weeks
[19:39] <micahg-work> I'll try to move that forward tonight
[19:39] <Unit193> knome: OK, done more or less, might want to take a look.  Also, what additional data do you want?
[19:40] <knome> Unit193, you should talk with pleia2, or alternative me after we've refreshed the page
[19:40] <knome> Noskcaj, can you talk with the SRU team about the weather plugin?
[19:41] <Noskcaj> ok
[19:41] <elfy> once it's ready, let me know - but I should pick it up from the bug
[19:42] <knome> 12.04 is supported for one more year only (for the xubuntu part), and 14.04 is out in 6 months, so the more it stands in queues the less its impact will be
[19:42] <elfy> #action Noskcaj to ping elfy re weather plugin
[19:42] <meetingology> ACTION: Noskcaj to ping elfy re weather plugin
[19:42] <knome> #action micahg to look at Noskcaj's MOTU application
[19:42] <meetingology> ACTION: micahg to look at Noskcaj's MOTU application
[19:42] <knome> #action Noskcaj to poke the SRU team about the weather plugin
[19:42] <meetingology> ACTION: Noskcaj to poke the SRU team about the weather plugin
[19:43] <knome> any other things people want to discuss?
[19:44] <elfy> nope
[19:44] <knome> #topic Schedule next meeting
[19:44] <knome> #info Next meeting Thu, Feb 13 at 19UTC
[19:44] <knome> #endmeeting
[19:44] <meetingology> Meeting ended Thu Feb  6 19:44:58 2014 UTC.
[19:44] <meetingology> Minutes (wiki):        http://ubottu.com/meetingology/logs/xubuntu-devel/2014/xubuntu-devel.2014-02-06-19.02.moin.txt
[19:44] <meetingology> Minutes (html):        http://ubottu.com/meetingology/logs/xubuntu-devel/2014/xubuntu-devel.2014-02-06-19.02.html
[19:45] <elfy> thanks knome
[19:45] <knome> ta ta
[19:45] <jjfrv8-work> cyall
[19:45] <slickymaster> thanks knome
[19:45] <knome> will set up the meetings now
[19:47] <pleia2> thanks knome
[19:47] <knome> if only the wiki was at all faster
[19:47] <knome> might take a while with these speeds
[19:51] <knome> minutes up
[19:53] <knome> also, https://wiki.ubuntu.com/Xubuntu/Toolbox/MinutesTemplate?action=info ;)
[19:56] <pleia2> 12.04.4 \o/
[19:57] <pleia2> hey, our flyer, again http://www.itwire.com/opinion-and-analysis/the-linux-distillery/63020-still-on-windows-xp
[19:58] <elfy> knome: I've published it now
[19:59] <knome> ta
[19:59] <knome> i've just updated the download links, pointing to .4 now
[19:59] <elfy> ok
[20:00] <knome> and i'm off
[20:00] <knome> bbl
[20:01] <pleia2> I'll social media it once I finish up the ubuntu fridge post
[20:02] <brainwash> I like the flyer, it's kinda funny -> "will you buy a new computer or.."
[20:03] <Unit193> Isn't the motu application not under our umbrella, so not something we should action?
[20:04] <Noskcaj> Unit193, It's under micah's
[20:05] <Unit193> Yes, he isn't Xubuntu, he's mica.
[20:06] <elfy> Unit193: I'd agree
[20:06] <Unit193> New event added: http://goo.gl/ELP3Ud
[20:09] <elfy> schproodle: "Pendrive insertion fails in VM but it is mounted by the host machine." is probably about usb's not being setup in virtual machine
[20:10] <Unit193> schproodle: Do you have the virtualbox extension pack?
[20:13] <schproodle> elfy, I do now. Got it working. thanks
[20:15] <schproodle> elfy, I could not do the QATracker testing without vbox eh. I am trying all kinds of distros as well.  Basic FreeBSD is raw .
[20:17] <schproodle> Unit193, I installed the extension. Had to logout to get that vbox group registered. Thanks
[20:38] <schproodle> Can inserting a pendrive shut my computer off?
[20:39] <schproodle> Not a good sign.
[20:39] <elfy> it can shut one of my laptops off - but the socket's had it
[20:40] <schproodle> crap!  just avoid a particular socker then eh?
[20:41] <schproodle> by socker you mean the computer -- not the pendrive right?
[20:41] <Unit193> Socket.
[20:42] <schproodle> Seems one has to install usb pendrives for each VM for VirtualBox.
[20:42] <schproodle> Unit193, not soccer, I will get it sorted. :)
[22:16] <knome> slickymaster is now a ubuntu member!
[22:16] <elfy> woohoo
[22:16] <Unit193> I'll say it again, well deserved.
[22:16] <slickymaster> my face is red guys, all from your words
[22:17] <Unit193> He's very angry.
[22:17] <Unit193> :---D
[22:17] <elfy> :)
[22:17] <ochosi> congrats slickymaster
[22:18] <knome> like this children's show host? http://www.youtube.com/watch?v=HpmKykMT1JU
[22:18] <slickymaster> thanks ochosi
[22:18] <slickymaster> ah ah ah, just without the bottle
[22:18] <knome> "nasse-setä on hyvin hyvin vihainen" == "uncle nasse is very very angry"
[22:18] <slickymaster> correction bottles
[22:18] <knome> hehe
[22:18] <knome> well he *plays* them O:)
[22:19] <slickymaster> lol,
[22:19] <ochosi> Noskcaj: i linked a thunar-patch to the features-blueprint today, in case you can package that one in, that'd be great! (fix wallpaper-plugin with xfdesktop4.11, explanation why and what in the bugt)


 @RikMills qtwebengine finally built fine in 4072. Do you think it's ok to land it now?
 @mitya57 [@RikMills qtwebengine finally built fine in 4072. Do you think it's ok to land i …], Probably, as Qt is not migrating any time soon. Can we run the testis or the PPA though to make sure rdep tests are ok?
 I forgot how to do this :(
 @mitya57 [I forgot how to do this :(], diff and set lander signoff to approved
 after a couple of 20 min bileto bot updates, tests should run
 Doing.
 :)
 Maybe we should also ask vorlon tonight if he is happy with it landing. Our original Qt landing stomped on another transition, which vorlon reverted webengine to get through. Then the other day I bemoaned someone else's webengine rebuild that entangled re2. So to maintain good will, and in case this rebuild has picked up a dep in pro
 Asked on #-release.
 Great. This is safer. Going to need his help to get Qt through 😉
 https://bileto.ubuntu.com/excuses/4072/groovy.html — looks like Bileto does not use packages from -proposed
 "libqt5webengine5 : Depends: libqt5core5a (>= 5.14.2+dfsg~) but 5.12.8+dfsg-0ubuntu1 is to be installed"
 odd. I am sure is has before on ones I did
 vorlon said ok, so am trying to land it


[03:03] <ScottK> slangasek: ^^^ is there someone that could have a look at that?  It seems rather unfortunate.
[09:00] <ogra_> cjwatson, heh, the ubuntu-touch saucy tarball live=build produces with the latest changes is actually just tarring up the filesyste.squashfs file
[09:01] <ogra_> (instead of a tarball containing the rootfs)
[09:51] <ogra_> ugh ... why does switching ubuntu-touch to -f plain suddenly make it install oem-config on the touch build
[16:02] <slangasek> ScottK: looks to me like it should probably just be assigned to the folks who worked on the package? (mterry, jyrinki)
[16:03] <slangasek> s/jyrinki/Mirv/
[16:03] <ScottK> slangasek: OK.  thanks
[16:03] <ScottK> apachelogger: ^^^
[16:03] <slangasek> looking at the package, I don't even see the default.conf referred to in the bug report
[16:03] <slangasek> so I'm not sure what's actually going wrong
[16:12] <apachelogger> slangasek: the file is from qt4-default actually
[16:21] <slangasek> apachelogger: ok, but running 'qtchooser' doesn't try to open any such file
[16:21] <apachelogger> :O
[16:22] <apachelogger> looking again
[16:24] <apachelogger> 7427  open("/usr/share/qtchooser//default.conf", O_RDONLY) = 4
[16:25] <apachelogger> slangasek: ah, yeah, I guess it only happens when you run the qtchooser backed apps, such as qdbus
[23:14] <slangasek> ogra_: hey, so what's the status of the ubuntu-touch images?  anything I can do to help?  I see from the logs that the daily builds aren't succeeding yet on nusakan
[23:16] <slangasek> seems the livefs build output isn't being found?
[23:24] <slangasek> hmm, I guess it is found


[06:35] <AuroraAvenue> Hello I want to know how to burn a dvd mp3
[06:35] <AuroraAvenue> I start work in 25 minutes - I need this now.
[06:51] <Spass> hello AuroraAvenue, just a DVD containing mp3 files? use Xfburn
[06:58] <AuroraAvenue> Its okay - I cant even spell that one - and thats the problem.
[06:59] <AuroraAvenue> I am using devedeng or whatever - and burning WarOnDrugs at (2.0x) thanks.
[15:29] <AuroraAvenue> Hi =- I only have one email (that I cannot use here)
[15:29] <AuroraAvenue> So here is a Pentium4 problem that I found.
[15:29] <AuroraAvenue> https://youtu.be/B1upcB01sKY?t=1m25s
[20:25] <n-iCe> hi


[00:40] <tsimonq2> slangasek, cjwatson: Is MoM broken? Last update was like 40  hours ago it seems...
[00:56] <stanford_ai> I'm trying to run tensorflow on GPU, so I followed the instructions on the tensorflow official website, to install it with conda. But I get this error: ImportError: libcuda.so.1: cannot open shared object file: No such file or directory
[01:08] <teward> stanford_ai: that's less a development issue and more of a support issue, you might wish to take that question to #ubuntu (namely, "how do I install CUDA so that I can use tensorflow on GPU?"_
[01:13] <cjwatson> tsimonq2: yeah it's on my list
[01:13] <cjwatson> there are a few things that break MoM and need manual intervention
[01:15] <cjwatson> tsimonq2: I usually leave it until a weekday to sort out; but I've fixed the first thing that broke so it may work soon.  Failing that it'll keep emailing me until I fix it, so I'm not going to forget
[02:23] <tsimonq2> cjwatson: ack, thanks.
[03:58] <TxLiunx> hello anyone on that could respond. I am test my system. I had to reload everything.
[04:00] <Unit193> TxLiunx: Perhaps you are seeking the support channel, #ubuntu?
[04:04] <TxLiunx> thanks, just checking if hexchat is working
[07:05] <smb> stgraber, not that I were wishing I had not (touched fan). But I saw this recently (indirectly while waiting on iproute2 tests), iirc only i386. And the test itself looks to succeed, its just sd_bus_open_system that suddenly comes via stderr
[07:22] <smb> stgraber, the thing that is done around when the message is produced is a "systemd-resolve --status" call... the second attempt, so I read the log, is then successful
[07:50] <acheronuk> merges.ubuntu.com has not updated since Saturday morning. who to query about that?
[07:59] <Unit193> acheronuk: "yeah it's on my list" || "there are a few things that break MoM and need manual intervention" || "I usually leave it until a weekday to sort out; but I've fixed the first thing that broke so it may work soon. Failing that it'll keep emailing me until I fix it, so I'm not going to forget"
[07:59] <acheronuk> Unit193: ok. thank you :)
[08:00] <Unit193> (Scrollback here.)
[08:00] <Unit193> acheronuk: Sure thing.
[08:01] <acheronuk> Unit193: I thought I had scrolled back, but probably did it in #ubuntu-desktop in error or something
[10:27] <seb128> hum, I think that's not possible but I'm asking in case. Can we query launchpad for tags using a regexp? e.g bugs tagged "verification-needed*"?
[10:47] <jbicha> is there anyone besides Laney who can look into http://appstream.ubuntu.com/cosmic/ ? it hasn't updated in a week
[11:49] <ricotz> seb128, https://bugs.launchpad.net/bugs/+bugs?field.tag=verification-needed
[12:38] <ahasenack> when a package is known to not work with python 3.7, is this an acceptable change to d/control for us?
[12:38] <ahasenack> -X-Python3-Version: >= 3.0
[12:38] <ahasenack> +X-Python3-Version: >= 3.0, <= 3.6
[12:39] <ahasenack> plus a link to the upstream bug tracking 3.7 progress
[13:27] <seb128> ricotz, that was an example, I want to use tags like with a "keyword-<idnumber>" and script list those and extract the "idnumber". One way is to have 2 tags, one "keyword" to have a way to query then iterate over the tags from the corresponding bugs and do the split, but I was wondering if I can do without the second tag
[13:27] <seb128> jbicha, slangasek iirc was mentioning the issue/a service that didn't get restarted after an outage or something
[13:28] <seb128> jbicha, but I don't know if he/others have a knowledge of the service and how to handle it
[14:23] <stgraber> smb: I fixed this issue by setting allow_stderr in the fan package
[14:23] <stgraber> smb: so if systemd feels like being noisy, that won't cause a failure anymore
[14:24] <smb> stgraber, Yep I saw that after replying. I pulled your change into the related git repo already
[14:29] <stgraber> smb: thanks!
[16:00] <slangasek> seb128: sorry, it wasn't me mentioning it, I know nothing about appstream.u.c
[16:09] <sil2100> oSoMoN: hey!
[16:09] <sil2100> oSoMoN: remind me - is libreoffice-l10n basically always just a mirror of libreoffice?
[16:09] <oSoMoN> sil2100, hey
[16:09] <oSoMoN> sil2100, both packages are built from the same sources
[16:10] <oSoMoN> they are separate packages because at some point in time LP wasn't able to cope with everything together
[16:10] <sil2100> oSoMoN: since I'm looking at libreoffice-l10n for xenial in the SRU queue (for the trigger changes) and there's a lot of changes besides the  trigger change, as the uploaded libreoffice-l10n follows what's was in libreoffice
[16:10] <oSoMoN> not sure if this is still the case
[16:10] <sil2100> While no libreoffice-l10n uploads have been done for a while there
[16:10] <sil2100> Ok
[16:11] <tjaalton> xnox: hi, i'm testing 389-ds on cosmic, and noticed that the configured instance isn't started after a reboot, in fact systemd somehow doesn't even know about it, although everything should be the same as before reboot
[16:12] <sil2100> oSoMoN: it's a bit tricky since now basically if I accept the trigger changes upload to xenial, I'd have to 'assume' that all the libreoffice security updates that are pulled in with this upload have been successfully tested for the libreoffice-l10n package as well
[16:12] <oSoMoN> sil2100, yeah, I think I talked to bdmurray_ about it a couple of weeks ago, strictly speaking the libreoffice-l10n update is not needed as there won't be version conflicts with a newer libreoffice, but I uploaded it for consistency, so it's up to you, feel free to reject if you don't want it
[16:13] <sil2100> oSoMoN: if you don't mind I'd reject it personally, since I have no idea if in some freak accident the -l10n generated binaries will suddenly go crazy on the missed security changes
[16:13] <sil2100> Certainly not something I'd like to get in without verification
[16:13] <oSoMoN> sil2100, that's absolutely fine by me
[16:13] <oSoMoN> better to be on the safe side
[16:13] <sil2100> (and there are no SRU tracking bugs for those as those are security uploads)
[16:13] <sil2100> oSoMoN: thanks!
[17:13] <tjaalton> xnox: correction, it's just not started on boot
[18:41] <seb128> slangasek, sorry, wrong memory, indeed it was not you https://irclogs.ubuntu.com/2018/08/22/%23ubuntu-release.html#t08:47
[18:41] <seb128> slangasek, do you know if anyone in foundations has knowledge of that service? nobody does in desktop and Laney is still away for a full week
[18:42] <slangasek> seb128: no idea, sorry
[18:42] <seb128> :/
[19:47] <xnox> tjaalton, fun. i have no idea about 389-ds - can you open a detailed bug report or drop me an email?
[19:47] <xnox> tjaalton, such that i could help investigating it....
[19:53] <tjaalton> xnox: sure
[22:41] <mwhudson> hah er i guess https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1789170 translates to "we use systemd now"?