[00:33] <stakewinner00_> someone knows some document about the directory tree of ubuntu touch?
[03:38] <altker128> Hey guys.  I saw the review on the octa-core Meizu and was dismayed to see comments about lag.  Any one have an idea why?  Any thoughts on if it'll be fixed?
[04:01] <talonz> altker128: i reckon by launch any issues with lag will be fixed or fixed very shortly after release
[04:13] <jamie2> well it seems my make rig worked so far, looks like compile is almost done, now to just hope to dear god its not corrupt
[06:17] <big_area> anyone had  luck with nexus 7 lte (deb) lately? I can't seem to get past "this phone needs restoring from a PC..."  using any of the tasemnice.eu images
[06:40] <altker128> talonz: Do you have any hands on experience with Ubuntu mobile?
[06:50] <talonz> very little sorry altker128 i test utouch every now and then on my nexus 5 but i do not have a dedicated device yet ... might be the meizu pro 5 and/or bq tablet
[06:50] <altker128> talonz: What is it like on your Nexus 5?
[06:51] <talonz> i am in no rush to jump right in at this point as much as i am growing to hate my android devices utouch is not ready enough for me just yet
[06:53] <talonz> last time i tried it pretty good nice and smooth had some issues with photos at the time and bluetooth didnt work at the moment i find it hard to test now tho cause multirom doesnt work with utouch
[06:54] <altker128> Is there any native GPS app for utouch yet?
[07:25] <talonz> yeah here maps and unav
[07:25] <talonz> there might be a couple of others
[07:35] <altker128> Does HERE maps work completely offline like it does for Android/iOS ?
[07:56] <talonz> your going to have to do some googling i think you have way too many questions when you should be reading
[10:08] <labsin> Anyone wanting to try the "Deezer Scope" from there phone?
[10:08] <labsin> I'd like to know if surfacing mode is working properly
[10:08] <labsin> It wasn't before
[17:22] <mimecar> I've upload a new chapter of the book "The user interface of Ubuntu Phone"
[17:23] <mimecar> you can read it on this link https://mimecar.gitbooks.io/ubuntu-phone-ui/content/en/04_installing_applications.html
[17:23] <mimecar> it is related with the installation of applications on Ubuntu Phone
[20:16] <alex______> Hi, guys. Want to port X11 app to xmir can't find any documentation. Can somebody point?
[21:17] <labsin> anybody want to  test a new version of the Deezer Scope that should have account support? The click to test is at https://drive.google.com/file/d/0B1euibKhpEeQVGdaa3ZIanBtb1k/view
[21:18] <mimecar> will you upload the new version into Ubuntu Store?
[21:19] <labsin> mimecar: I'd be nice if somebody could test it first. But if it's too much trouble
[21:19] <mimecar> I can test it, but not today
[21:20] <labsin> mimecar: of course
[21:34] <ilario> Hi all! I cracked (also) the screen of my BQ Aquaris E4.5 running latest Ubuntu Touch Krillin, it's so damaged that I can't unlock the screen, is there a way to connect (via MTP?) and recover photos?
[21:35] <mimecar> MTP won't work if you can not unlock the phone
[21:37] <ilario> so, is there no way to provide the unlock code in some other way?
[21:38] <mimecar> yes
[21:38] <mimecar> you can use a OTG cable with an usb mouse
[21:38] <mimecar> is the screen switched on?
[21:40] <ilario> yep, the screen is switched on but it's really damaged, the idea of the mouse is great but I'm not sure I could see where the digits are..
[21:41] <ilario> anyway I will buy one of these cables and I will try :) thanks!
[21:42] <mimecar> Do you get to see something on the screen ?
[21:42] <mimecar> upper part...
[21:42] <ilario> just the clock from times to times
[21:42] <mimecar> ok
[21:42] <mimecar> then you can use an USB keyboard
[21:42] <ilario> yep, but I can't see the round central part
[21:42] <mimecar> you can type de pin code
[21:42] <ilario> wowowowow a usb keyboard??
[21:42] <ilario> woowowowowowowowow!
[21:43] <ilario> that would be perfect!
[21:43] <mimecar> xD
[21:43] <ilario> but why do I need to see the upper screen part?
[21:43] <mimecar> first you unlock the phone, after you must press volume key several time in order to avoid screen lock
[21:44] <mimecar> I don't know. Have you flashed the latest firmware por E4.5?
[21:44] <mimecar> latest stable
[21:44] <ilario> I bought the phone with Ubuntu Touch on it, then I installed all the OTAs
[21:45] <mimecar> Do the screen switched on when the phone is booting?
[21:45] <ilario> yep...
[21:45] <mimecar> then, it does not look a hardware problema
[21:45] <mimecar> unlock your phone, copy data and flash your device again
[21:46] <ilario> well... hitting the ground at several km/h often causes a hardware problem on mobile screens XD
[21:47] <mimecar> your phone is not a nokia...
[21:47] <ilario> exactely, that's why now I fallback to my old nokia XD
[21:49] <mimecar> you should buy an USB host cable tomorrow
[21:51] <ilario> yep :) I will, many thanks for your help!
[22:53] <labsin> Still someone around to give a scope a quick rond from the store after I upload it?


[00:04] <Vantrax> ahh well, guess hes not around
[00:04] <Vantrax> just wanted to look at a few things that have happend while I was indisposed:P
[00:04] <Vantrax> Seems like there has been some intense debate over licensing
[00:05] <Vantrax> It also seems that our organisation needs to be improved and we need to get a structure documented and agreed on
[00:05] <Vantrax> as a matter of priority
[00:06] <cprofitt> Vantrax, https://wiki.ubuntu.com/Learning/Notes/06182009
[00:06] <Vantrax> it also looks like we need to have someone 'in charge' moderating things within the board to guide discussion and moderate the conflicts.
[00:07] <Vantrax> yeah i saw that cprofitt, its linked on the agenda right?
[00:07] <cprofitt> yep
[00:07] <Vantrax> We have been having a few conflicts lately and things have gotten a bit out of hand a few times
[00:08] <Vantrax> we dont want to create a polarised environment where we each tend to our own extremes, we want to have a sensible discussion with moderated views. Too often lately things seem to be tending toward the extreme rather than meeting in the middle
[00:09] <Vantrax> this especially applies to licencing due to its central and prickly nature
[00:11] <cprofitt> A mediator might help with that...
[00:12] <Vantrax> pleia2: what do you think
[00:13] <cprofitt> I am not sure we can get a mediator that does not have an opinion on this...
[00:15] <Vantrax> I can see the benefit of NC, but it will be harder to work with. I can also see that BY-SA is easier, and better in line with the community standards.
[00:16] <Vantrax> problem is both have a good argument
[00:16] <Vantrax> I dont think it so importaint for the mediator not to have an opinon, but to put aside his or her opinions and play devils advocate if neccesary
[00:20] <cprofitt> I see that argument having more leeway than the one for ownership transfer
[00:24] <pleia2> sorry, got dragged into a phone call, will be back soon
[00:24] <Vantrax> i think the transfer of ownership was a misunderstanding in the way that CC works, we dont need ownership, we can still do everything we want to it except for relicensing it
[00:24] <Vantrax> Im not entirely sure of the need for relicensing
[00:25] <Vantrax> if there is a legal indemnity issue that should be explored with the FSF
[00:26] <Vantrax> thats kinda not the point tho, i think we need to look at having a nominated head of the board to moderate our discussions a bit, and to resolve conflicts
[00:26] <Vantrax> we need to get some proper advice for our licensing, but that can be resolved at the meeting tomorrow.
[00:32] <cprofitt> Vantrax, ownership may have been a misunderstanding...
[00:32] <cprofitt> it may not have.
[00:32] <cprofitt> Vantrax, I would add the nomination suggestion to the agenda
[00:33] <Vantrax> yes, we will need to try and understand what bodhi was getting at. More importaintly the reason behind his position
[00:33] <cprofitt> I can concede that as long as the reverse is true.
[00:34] <cprofitt> I think such exploration may better be done after the advice is given and via the mail list... as it allows for un-interrupted explanation of the position
[00:39] <Vantrax> probably, but it should be started here first. Also I think because we tend to understand everyones position but Bodhi's we should allow him to explain himself fully so we can understand where he is coming from. At this stage I feel I am missing something.
[00:39] <cprofitt> does that sound fair Vantrax ?
[00:43] <Vantrax> cprofitt: it does indeed
[00:44] <cprofitt> k
[00:44] <cprofitt> I am going to log for a bit... be back on in about an hour or so
[00:44] <pleia2> yeah, I think the ownership thing is a misunderstanding too
[00:44] <pleia2> so hopefully that can all get out in the open
[00:46] <Vantrax> yeah, just seems there has been too much fighting, and not enough discussion
[00:48] <pleia2> yeah, that's kinda why I backed off, we hit a few spots where only more information could help, so talking wasn't doing any good
[00:49] <pleia2> I understand and sympathize with the fact that bodhi has legal concerns, but until I understand precisely the nature of them it's hard to have a discussion about it
[00:56] <Vantrax> on that we agree
[00:57] <Vantrax> from what I understand there has been a series of heated arguments that went nowhere
[00:58] <pleia2> I don't know that they were that bad
[00:58] <pleia2> I never felt upset during any of the discussions
[00:59] <pleia2> I did say that I wouldn't give up copyright *and* be forced into an NC license, which I think upset bodhi
[01:01] <pleia2> but that's simply because as an author I like to retain some rights to my own material
[01:01] <pleia2> now that NC is mostly off the table, I don't think it's much of an issue anyway
[01:21] <Vantrax> also worth noting, bodhi hasnt been around since then
[01:22] <pleia2> actually he has, talked with doctormo and dinda quite a bit
[01:22] <pleia2> was asking where you were yesterday
[01:24] <Vantrax> ahh
[01:24] <Vantrax> hopefully he will show up later and i can poke him
[01:24]  * pleia2 nods
[01:56] <doctormo> Hello?
[01:56] <pleia2> hey doctormo
[02:06] <doctormo_> grr damn system76 laptop crashed again as I was reading the backlog
[02:06] <doctormo_> ok poke away
[02:06] <doctormo_> Vantrax: I hope your ok, we should get the theme done but not if you need to rest
[02:07] <Vantrax> heya mo
[02:07] <doctormo_> We should wait for the theme for announcements and such, but a team report so long as it's not blogged wouldn't be too bad I don't think
[02:07] <Vantrax> i need a header graphic and its done, just need a test server to tweak the theme
[02:07] <Vantrax> i havent been able to see what it actually looks like yet
[02:08] <Vantrax> its all blind coded
[02:08] <doctormo_> The copyright stuff has been heated and I think we've all learned a lot from it, but I wouldn't call on a captin for such a thing, if council members can't discuss, then what hope have we got of going with the CoC never mind the leadership CoC
[02:11] <cprofitt> Vantrax, bodhi put up a test server I thought
[02:11] <Vantrax> doctormo: its useful to have someone to moderate when necessary
[02:11] <Vantrax> cprofitt: it went down last i heard, he was rebuilding it
[02:11] <cprofitt> http://learn.bodhizazen.net/moodle/login/index.php
[02:11] <Vantrax> doctormo: ive had to do that with you and bodhi once already
[02:12] <cprofitt> its loading for me now
[02:12] <doctormo_> Vantrax: I thought the idea was that we all could moderate and come into an unfortunate situation as required
[02:12] <Vantrax> soudns good
[02:12] <doctormo_> part of the skills
[02:12] <Vantrax> seems like he did get it back up
[02:13] <Vantrax> doctormo: indeed, but we are also lacking some structure, and organisation which needs to be addressed
[02:14] <Vantrax> as with everything, just an idea. Feel free to shoot me down:P
[02:17] <doctormo_> Vantrax: It's an important idea, and I like the idea of apointed aribors. But I also feel that people like yourself who come into a fight in order to control things and settle the manner of the discussion should be able to do so through self authority, not one invested. This is for timezone reasons as much as it is about people being people and anyone could possibly get into a fight, even one nominated.
[02:18] <Vantrax> good point
[02:18] <doctormo_> Perhaps we should have a declarative, "This discussion seems to be getting heated, I'm going to watch to make sure no one steps out of line"
[02:19] <doctormo_> And then that in it's self gives you the position to manage it without getting embroiled.
[02:20] <doctormo> but again, just ideas, feel free to shoot me down :-D
[02:23] <Vantrax> not a bad idea again
[02:48] <cprofitt> doctormo, do really feel our conversations got that heated?
[03:01] <cprofitt> hey guys... wb
[03:03] <doctormo_> [21:57] <doctormo> Vantrax: OK I have a banner already for the UCLP
[03:03] <doctormo_> [21:57] <doctormo> http://divajutta.com/doctormo/learning/title.png
[03:03] <doctormo_> cprofitt: hey there
[03:04] <cprofitt> doctormo, do really feel our conversations got that heated?
[03:05] <cprofitt> doctormo, Vantrax - is this one of the items we need to do - https://wiki.ubuntu.com/MOTU/MOTUReleaseCharter
[03:06] <Vantrax> thanks doctormo
[03:06] <doctormo> cprofitt: between me and botzi, or between you and botzi?
[03:07] <cprofitt> doctormo, either... I meant the group in general
[03:07] <cprofitt> so between he and I or you and I or you and him or ...
[03:07] <doctormo> Well, your argument wasn't as bad as mine, I have to admit I fouled up handling that one.
[03:07] <doctormo> Thanks to Vantrax we got it sorted, but I wouldn't like that kind of thing to happen again
[03:13] <cprofitt> k
[03:35] <Vantrax> cprofitt: i think something like that charter is not really required
[03:37] <cprofitt> k
[03:37] <cprofitt> do you have an example or a framework you would like to work from?
[03:37] <Vantrax> I think that will come under the structure & organisational roles stuff I wanted to discuss
[03:38] <Vantrax> We need to outline a structure (ala ubt) with how the team is structured, and the roles and responcibilities
[03:39] <cprofitt> I agree... just curious if there was an example?
[03:39] <Vantrax> dont know of one
[03:40] <cprofitt> k
[03:41] <Vantrax> Id rather do something that works for us instead of using something that worked for someone else
[03:42] <cprofitt> Vantrax, I am not saying straight copy...
[03:42] <Vantrax> i know
[03:42] <cprofitt> I was just thinking it would serve as an example of the type of document you want...
[03:42] <cprofitt> it would help us get on the same page perhaps
[03:44] <pleia2> would help us define some of the basic things that all teams need done, too
[03:45] <pleia2> like meetings and team reports and all that
[04:09] <bodhizazen> Vantrax, poke :)
[04:11] <cprofitt> pleia2, good points
[04:11] <cprofitt> hello bodhizazen
[04:11] <pleia2> evening bodhizazen
[04:12] <bodhizazen> hey everyone
[04:12] <bodhizazen> spent most of the day with my children, hiking and swimming
[04:12] <bodhizazen> you ?
[04:13] <cprofitt> dad's 65th was yesterday
[04:13] <cprofitt> father's day today
[04:15] <Vantrax> hiya bodhi
[04:16] <Vantrax> bodhizazen: lots of good discussion this morning
[04:19] <bodhizazen> Nice :)
[04:30] <doctormo> US Father's day right?
[04:31] <bodhizazen> yes
[04:31] <bodhizazen> my children all made a fathers day shirt
[04:31] <bodhizazen> that they wore, even Myah (almost 2 now)
[04:32] <bodhizazen> they have their # on the back (kid #1, etc) and each did a unique theme
[04:38] <cprofitt> well... good night all... early morning for me tomorrow
[04:38] <cprofitt> see you on the flip side.
[06:32] <dthacker> join #ubuntu-beginners
[06:32] <dthacker> argh.  need coffee
[07:50] <doctormo> dthacker: do you need something?
[09:01] <entered_am> gud day...
[09:02] <entered_am> any one could help me to connect for my ym
[18:03] <bodhi_zazen> 'lo everyone :)
[18:03] <bodhi_zazen> meeting later today ?
[18:05] <pleia2> yep
[18:11] <pleia2> there, sent out reminder :)
[18:11] <pleia2> and the ML seems to be working nicely \o/
[18:12] <doctormo> thanks for the reminder :-)
[21:39] <SAMER> HELLO
[21:39] <SAMER> I WANT TO CONNECT MY COMPUTER TO THE ENTERNET VIA BLUETOOTH
[21:39] <SAMER> ANY ONE CAN HELP
[22:29] <doctormo> no, not here, try #ubuntu
[22:46] <nhandler> doctormo: He left a while ago
[22:46] <doctormo> nhandler: Yea, I know, just wanted to say it as a sigh. Damn shouty, wrong channel people. :-/
[23:32] <cprofitt> hey Vantrax|Work
[23:41] <cprofitt> meeting in 19 minutes
[23:42]  * pleia2 nods
[23:45] <dthacker> argh, thought I had an hour.
[23:52] <pleia2> ok, I'm going to be a few minutes late
[23:52] <pleia2> I forgot about the whole eating thing
[23:54] <cprofitt> Vantrax|Work, did you add your items to the agenda for tonight?


[12:15] <Ubugtu> New bug: #71609 in util-linux (main) "Can't unmount UUID= volume as a user" [Undecided,Unconfirmed]  http://launchpad.net/bugs/71609
[12:16] <Ubugtu> New bug: #73399 in Ubuntu "The audio is cut when the HD "itches"" [Undecided,Unconfirmed]  http://launchpad.net/bugs/73399
[12:16] <Ubugtu> New bug: #73400 in Ubuntu "kubuntu show all directorires of "/"" [Undecided,Unconfirmed]  http://launchpad.net/bugs/73400
[12:21] <Ubugtu> New bug: #73401 in sun-java5 (multiverse) "current working directory not set correctly when launching JAR file" [Undecided,Unconfirmed]  http://launchpad.net/bugs/73401
[12:45] <Ubugtu> New bug: #73403 in firefox (main) "Firefox shutdown while trying to save an .gif image" [Undecided,Unconfirmed]  http://launchpad.net/bugs/73403
[02:32] <andresmujica> i cannot access the bug reports... i want to mark #73402, #73404 and #73405 asduplicates, but couldn't access there... pls someone mark those as dups.
[02:33] <andresmujica> thanks
[02:33] <andresmujica> #74302
[02:33] <crimsun> LP is experiencing technical difficulties atm.
[02:34] <andresmujica> hmm , i supposed that..
[02:34] <andresmujica> ok i'll wait for a bit.
[04:03] <sfllaw> Hobbsee: Did you complain to #launchpad about d_jedi?
[04:03] <sfllaw> By the time I saw your ping, you were gone.
[04:04] <Hobbsee> sfllaw: yep
[04:04] <Hobbsee> sfllaw: yes.  i do sleep occasionally, sorry :(
[04:04] <sfllaw> Same here.
[04:04] <sfllaw> :)
[04:04] <sfllaw> Thanks!
[04:04] <sfllaw> You rock.
[04:05] <Hobbsee> :)
[04:50] <TheMuso> c
[04:50] <Hobbsee> d
[04:54] <Admiral_Chicago> hmm channel is all quite
[04:54] <Admiral_Chicago> is LP still down?
[04:56] <somerville32> LP isn't down forme
[04:58] <Admiral_Chicago> somerville32: someone said it was "LP is experiencing technical difficulties atm."
[04:59] <Admiral_Chicago> so maybe the bot isn't updating the bugs or something
[04:59] <somerville32> Hmm...
[06:45] <dholbach> good morning
[06:51] <towsonu2003> I've got a question, I applied to ubuntu-qa a few weeks ago -how long does it get to get approval or denial?
[06:52] <dholbach> towsonu2003: did you ask simon about it? he does the approval normally
[06:52] <dholbach> (sfllaw that is)
[06:52] <dholbach> towsonu2003: but I saw you worked on a huge load of bugs already, I'm going to approve you now
[06:53] <towsonu2003> dholbach, oh okay thanks :)
[06:57] <towsonu2003> dholbach, is there a documentation page specific to ubuntu-qa I should read? (sorry to bother you again)
[07:04] <dholbach> towsonu2003: we should have one
[07:06] <towsonu2003> dholbach, I couldn't find one. I'll google a bit more then ,thanks :)
[07:08] <Admiral_Chicago> when is Ubugtu going to start udating from LP
[07:08] <dholbach> towsonu2003: ok, I didn't find anything
[07:09] <dholbach> towsonu2003: I'm going to add a blurb on the BugSquad page and one describing the bug statuses
[07:09] <towsonu2003> dholbach, thanks a lot :)
[07:10] <towsonu2003> dholbach, oh almost forgot, could you add a couple of notes on bug importance and when to change it? thanks again
[07:11] <dholbach> towsonu2003: your wish is my command
[07:12] <towsonu2003> dholbach, lol
[07:16] <dholbach> https://wiki.ubuntu.com/Bugs/Importance
[07:19] <dholbach> added it to https://wiki.ubuntu.com/Bugs/HowToTriage
[07:23] <towsonu2003> thanks a lot, I really appreciate it :)
[07:23] <dholbach> thanks for notifying me
[07:24] <dholbach> added the blurbs about ubuntu-qa too
[07:24] <dholbach> https://wiki.ubuntu.com/BugSquad and https://wiki.ubuntu.com/Bugs/Importance
[07:24] <towsonu2003> great
[07:24] <dholbach> super
[07:24] <towsonu2003> I'll start reading once I'm done watching Star Trek
[07:24] <dholbach> hehe
[07:24] <dholbach> enjoy it
[07:24] <towsonu2003> :p
[09:41] <palski> Shouldn't this be "fix committed"?  Bug #68074
[09:41] <Ubugtu> Malone bug 68074 in curl "Seg fault when connecting" [Undecided,Confirmed]  http://launchpad.net/bugs/68074
[09:43] <palski> the fix is already in CVS
[09:45] <somerville32> Depends if the package is upstream or not
[09:46] <palski> bug was in upstream and fix has committed to upstream cvs
[09:48] <somerville32> Hmm
[09:50] <palski> "Fix Committed: A fix has been included in the code, but this code is not necessarily available in a released version"
[09:51] <somerville32> One second
[10:15] <crimsun> palski: it can be, yes
[10:16] <somerville32> I affected it upstream
[10:17] <somerville32> crimsun: The local source package can stay at confirmed until we do an sru?
[10:17] <crimsun> that'll be fine
[10:17] <palski> if it is fixed in feisty, wouldn't that be "fix released"?
[10:18] <palski> and a new bug report should be done for sru request?
[10:19] <somerville32> Yeah, thats probably right.
[10:21] <crimsun> yes, and yes
[10:24] <somerville32> Crimsun: Will you do the sru?
[10:24] <crimsun> somerville32: I don't have time atm.
[10:24] <somerville32> k
[10:25] <crimsun> are you familiar w/ the process? I don't mind walking you through it.
[10:25] <crimsun> more people should become familiar w/ it, really.
[10:27] <somerville32> Well, I'm in Windows right now (simply because I was too lazy to reboot after the last person who was on)
[10:28] <somerville32> And I doubt it would go well using the live cd
[10:28] <somerville32> I suppose I could move downstairs to my lab
[10:29] <crimsun> you need access to a Terminal [of choice]  and some standard packaging tools (devscripts, etc.)
[10:29] <crimsun> it doesn't require much more
[10:30] <somerville32> Alrighty
[10:30] <somerville32> I'll be right back
[10:30] <palski> you really need devscripts for filling up sru?
[10:31] <crimsun> no, but it's quite convenient
[10:31] <crimsun> e.g., devscripts: /usr/bin/debdiff
[10:31] <somerville32> :]
[10:32] <somerville32> Alrighty, brb
[10:39] <somerville32> Crimsun: Alrighty.
[10:40] <crimsun> somerville32: ok, got a terminal or two open?
[10:40] <somerville32> Yup :)
[10:41] <crimsun> ok, first thing is to grab the edgy source package [wget http://archive.ubuntu.com/ubuntu/pool/main/c/curl/curl_7.15.4-1ubuntu2.dsc http://archive.ubuntu.com/ubuntu/pool/main/c/curl/curl_7.15.4.orig.tar.gz http://archive.ubuntu.com/ubuntu/pool/main/c/curl/curl_7.15.4-1ubuntu2.diff.gz ]
[10:42] <somerville32> Alrighty. :)
[10:42] <crimsun> next thing is to isolate the patch from upstream cvs that fixes the issue and to download it
[10:44] <somerville32> Got it
[10:44] <crimsun> [I presume it's http://librarian.launchpad.net/5179200/multi_expire.diff ?]
[10:45] <crimsun> ok, next thing is to extract the source package [dpkg-source -x curl_7.15.4-1ubuntu2.dsc ]
[10:45] <crimsun> then, cwd into the root of the extracted source
[10:46] <somerville32> k
[10:46] <crimsun> at this point, it's a good idea to check if the Debianised source package uses a patch management system
[10:47] <crimsun> e.g., inspect debian/{control,rules} and look for the existence of debian/patches/
[10:47] <crimsun> specifically:
[10:47] <crimsun> in debian/control, look at the Build-Depends line, and see if it uses cdbs, quilt, dpatch, etc.
[10:48] <crimsun> in debian/rules, look for *patch* target(s)
[10:48] <crimsun> and finally, if debian/patches/ exists, it's nearly always a dead giveaway that some sort of patch management system is used
[10:49] <crimsun> [in this case of curl, there's none used, so you'll patch the Debianised source directly. Normally if a patch management system is used, you'll generate the patch targeted for the specific system ]
[10:51] <crimsun> now you need to patch the Debianised source, but you'll find there's one reject
[10:51] <crimsun> [patch -p1 --dry-run <../multi_expire.diff ]
[10:51] <crimsun> [it's always sane to test using --dry-run ]
[10:53] <crimsun> at this point, you'll manually inspect the reject and hand-apply the necessary fix
[10:54] <somerville32> Is it possible to see where the rejection is occurring?
[10:55] <crimsun> yep, look at lib/multi.c.rej
[10:55] <crimsun> in another window, it helps to open lib/multi.c
[10:55] <somerville32> It didn't actually write it
[10:55] <crimsun> oh, right. apply it (no --dry-run)
[10:56] <somerville32> k
[10:57] <crimsun> once you inspect the lib/multi.c alongside lib/multi.c.rej , you'll see that the actual one-liner (the comments notwithstanding) needs to be applied 12 lines above
[10:58] <crimsun> then you'll hand-insert that line into lib/multi.c
[11:01] <crimsun> [clear so far? ]
[11:01] <somerville32> Hmm...
[11:01] <somerville32> Yeah but I'm having a hard time matching up the reject to the new code
[11:02] <crimsun> right, you have to scroll up 12 lines from the original target
[11:02] <somerville32> I did
[11:02] <crimsun> ok, do you see the if(easy) {
[11:02] <crimsun>  /* If the 'state' ...
[11:03] <somerville32> Yup
[11:03] <somerville32> Oh!
[11:03] <crimsun> yeah, fortunately this one was straightforward
[11:03] <crimsun> it can be a real PitA
[11:04] <somerville32> Do you see line 19 in the rej file?
[11:04] <somerville32> Like, 18-21
[11:04] <somerville32> Where is that stuff?
[11:04] <crimsun> yep. Those aren't in lib/multi.c , because that was added in .5
[11:05] <crimsun> (welcome to the joy of backporting fixes)
[11:05] <crimsun> note, however, that semantically the context is nearly identical in the old one [to which you're applying the fix ]
[11:06] <crimsun> the difference is an additional if(easy->easy_handle == ... )
[11:06] <somerville32> Maybe I'm still confused
[11:07] <somerville32> I thought I had to add the parts with the the plus signs in front
[11:07] <somerville32> haha
[11:07] <crimsun> yes, you do
[11:07] <crimsun> that's the portion that failed to apply
[11:08] <crimsun> the significant portion that failed to apply is just one line:  Curl_expire(easy->easy_handle, 0);
[11:08] <somerville32> Ok, thats what I thought
[11:08] <crimsun> so, noting the context prior and following that failed portion, you can see where to apply it
[11:08] <somerville32> But I don't see the other parts in that new file
[11:08] <crimsun> which other parts?
[11:08] <crimsun> (I only have one reject)
[11:09] <somerville32> Ok, in the rej file
[11:09] <somerville32> Line 6
[11:09] <crimsun> right, it's not in edgy's curl source because that was added for feisty's
[11:10] <somerville32> So...
[11:10] <crimsun> (that's why it failed to apply)
[11:10] <somerville32> I only have to add  Curl_expire(easy->easy_handle, 0); under nice to put the easy_handle in a good known state when this returns. */
[11:10] <crimsun> right
[11:10] <somerville32> haha
[11:10] <somerville32> Ok
[11:10] <somerville32> I understand now
[11:11] <somerville32> You should have told me why it failed and I would have gotten it, haha
[11:11] <somerville32> <g
[11:11] <crimsun> I did 7 minutes ago ;)
[11:11] <somerville32> You'll have to forgive me
[11:11] <crimsun> no prob
[11:11] <somerville32> It is 6:13am here
[11:12] <crimsun> 5:12a here
[11:12] <somerville32> Alrighty. manually patched
[11:12] <crimsun> ok, next, clean up the source tree by removing *.orig and *.rej
[11:13] <crimsun> [find -name '*.orig' |xargs rm && find -name '*.rej' |xargs rm ]
[11:13] <somerville32> k
[11:14] <crimsun> now you're ready to generate a changelog entry
[11:14] <somerville32> :]
[11:15] <crimsun> [dch -v7.15.4-1ubuntu2.1 -Dedgy-proposed ]
[11:16] <crimsun> (fill in the appropriate info)
[11:16] <somerville32> dch isn't installed
[11:16] <somerville32> What package do I need?
[11:16] <crimsun> devscripts :)
[11:16] <somerville32> :]
[11:18] <crimsun> [oh, emacs has tools for this, but I'm not familiar with that mode. If you're an emacs fan, you'll want to ask someone who uses emacs. ]
[11:19] <somerville32> What should I say in the changelog?
[11:20] <crimsun> the format for a -proposed entry generally references files that were changed and why
[11:20] <somerville32> Example?
[11:22] <somerville32>   * curl/lib/multi.c patched to fix bug #68074 ?
[11:22] <Ubugtu> Malone bug 68074 in curl "Seg fault when connecting" [Unknown,Unknown]  http://launchpad.net/bugs/68074
[11:23] <crimsun> e.g., http://pastebin.ca/259304
[11:24] <somerville32> Do I need a @ubuntu.com e-mail address? I read somewhere that I did.
[11:24] <crimsun> it's not strictly necessary
[11:25] <crimsun> since you aren't a dev yet, you should get a core-dev to ACK the debdiff
[11:26] <crimsun> (you'll generate the debdiff next)
[11:26] <somerville32> parsechangelog/debian: error: unrecognised line, at changelog line 4
[11:26] <somerville32> dch: fatal error at line 983:
[11:26] <somerville32> Problem executing dpkg-parsechangelog:
[11:26] <crimsun> make sure your syntax is correct
[11:26] <crimsun> note that in the pastebin, lines 5-6 are actually one line
[11:27] <somerville32> Ok, I fixed it
[11:27] <somerville32> Should I run the script again or something?
[11:27] <crimsun> which script are you referring to?
[11:27] <crimsun> (you need the changelog entry)
[11:27] <somerville32> dch
[11:27] <crimsun> you only need to run it to add the entry
[11:28] <somerville32> Alrighty.
[11:28] <somerville32> Whats next?
[11:28] <crimsun> since it failed, yes, you'll need to make sure the entry is there
[11:28] <somerville32> in debian/changelog
[11:28] <somerville32> ?
[11:28] <crimsun> yes, at the top
[11:28] <somerville32> It is there
[11:28] <somerville32> I manually edited it to fix the line break on line 4
[11:29] <crimsun> excellent. Now you have to make sure you file a bug report that will be referenced, as the SRU, in the changelog
[11:29] <crimsun> if you wish, you can use 68074 for that
[11:29] <somerville32> So I don't need to file a second bug?
[11:30] <crimsun> not necessarily, though it helps for clarity
[11:30] <crimsun> SRU policy is outlined at [https://wiki.ubuntu.com/StableReleaseUpdates ]
[11:32] <crimsun> ok, now that you have the appropriate fix applied and the changelog entry, you need to generate a debdiff to attach to #68074 (or whichever new bug report you open, if you choose)
[11:32] <somerville32> Well, I'll open a new bug report since I said I said Daniel wouldn't get anymore e-mails, haha
[11:33] <crimsun> ok, just make sure you edit debian/changelog before you generate the debdiff
[11:34] <somerville32> Can I put the SRU bug number on it's own "asterisk"?
[11:34] <crimsun> if you wish to, yes. I normally reference all the Ubuntu bug #s together by topic
[11:35] <crimsun> (so I'd place them together)
[11:35] <crimsun> fault (Closes Ubuntu: #68074, _and whatever SRU bug #_).
[11:39] <crimsun> (note that you'd attach the debdiff to this new bug that you're filing)
[11:39] <crimsun> ok, since I have to scoot in a bit, I'm going to outline what else you need to do
[11:39] <crimsun> 1) adjust debian/changelog
[11:40] <crimsun> 2) generate a debdiff
[11:40] <somerville32> How else do I have to modify debian/changelog?
[11:40] <crimsun> 3) add the relevant info, including the debdiff and diffstat info, to the new bug
[11:40] <crimsun> debian/changelog needs to reference the SRU bug #
[11:40] <crimsun> (you'll see that when you reread https://wiki.ubuntu.com/StableReleaseUpdates )
[11:42] <crimsun> now, generating a debdiff is quite straightforward. While in the root of the extracted source, you issue a ``debuild -S''
[11:43] <crimsun> that command generates several files in the parent directory, curl_7.15.4-1ubuntu2.1.diff.gz , curl_7.15.4-1ubuntu2.1.dsc , curl_7.15.4-1ubuntu2.1_source.build , curl_7.15.4-1ubuntu2.1_source.changes
[11:44] <crimsun> you should cwd to that parent directory to generate a debdiff (the previous step just generated a Debianised source package)
[11:44] <crimsun> debdiff accepts several different files; I use the dscs
[11:44] <crimsun> ``debdiff curl_7.15.4-1ubuntu2.dsc curl_7.15.4-1ubuntu2.1.dsc >curl_7.15.4-1ubuntu2.1.debdiff''
[11:45] <crimsun> and that's the debdiff that is applicable to the original edgy source package
[11:46] <crimsun> you'd attach that to the new bug report
[11:46] <crimsun> I also find it useful to include diffstat output, so whichever archive admin is reading the SRU can get a quick overview of the invasiveness of the patch
[11:47] <crimsun> (diffstat is in the diffstat package)
[11:47] <crimsun> diffstat curl_7.15.4-1ubuntu2.1.debdiff
[11:48] <crimsun> afterward, you'd attach all that info to the new bug report, following step #1 (Propose) of the SRU process
[11:49] <crimsun> always build and test your debdiff before subscribing the ubuntu-sru team
[11:50] <crimsun> (I need to return to work)
[12:05] <somerville32> Gah
[12:05] <somerville32> It isn't working
[12:13] <fernando> moin all
[12:15] <somerville32> Hi
[12:33] <fernando> seb128: hi, not is gnome-vfs2 2.16.1-0ubuntu2 the latest stable?
[12:33] <seb128> fernando: stable = upstream stable or Ubuntu stable?
[12:34] <fernando> seb128: ubuntu stable
[12:34] <fernando> apt-cache show libgnomevfs2-0 | grep -i version
[12:34] <fernando> Version: 2.16.1-0ubuntu2
[12:34] <seb128> there is a 2.16
[12:34] <fernando> seb128: you have pached the 2.16.1-0ubuntu3
[12:34] <seb128> .2.16.1-0ubuntu3 to edgy-proposed which fix the 100% CPU bug
[12:34] <fernando> s/pached/patched/
[12:34] <fernando> seb128: ah, ok
[12:34] <fernando> seb128: thanks
[12:36] <seb128> np
[12:36] <seb128> does that answer your question?
[12:36] <seb128> you are looking for that update?
[12:36] <seb128> it's to "edgy-proposed", which is not part of the default sources.list
[12:39] <fernando> seaLne: thanks
[12:39] <fernando> seb128: thanks
[12:39] <seb128> np
[12:47] <somerville32> Woot.
[12:47] <somerville32> Got it to work
[12:47] <somerville32> Alrightys, times for bed
[03:54] <bddebian> Boo
[04:09] <pirast> bddebian, boooooohooooooo!
[04:09] <bddebian> Hehe.  Hello pirast
[04:10] <pirast> hi ;-)
[04:11] <Hobbsee> hey pirast
[05:39] <dholbach> sfllaw: it'd be good to announce the next hug day in your open week session
[05:40] <sfllaw> Yes, I think so.
[05:40] <sfllaw> I should probably get fridge-devel to put it up.
[05:45] <jonh_wendell> seb128: where is this bug nowadays: https://bugzilla.ubuntu.com/2055 ??
[05:48] <joumetal> jonh_wendell Sebastian is busy now at #ubuntu-classroom. What was this bug about?
[05:48] <jonh_wendell> joumetal: it's a outdated bug... i'd want just a confirmation from sebastien
[05:49] <seb128> jonh_wendell: http://bugzilla.ubuntu.com/show_bug.cgi?id=NUMBER
[05:49] <seb128> http://bugzilla.ubuntu.com/show_bug.cgi?id=2055
[05:49] <seb128> for that one
[05:51] <jonh_wendell> seb128: thanks
[05:54] <seb128> jonh_wendell: np
[06:19] <seb128> jonh_wendell: closing old bugs like that on bugzilla is not the way to go
[06:19] <seb128> jonh_wendell: I don't really care about that vino bug, but it's likely some bugsquad guy will remove your rights if you keep doing that
[06:20] <seb128> jonh_wendell: you can't close a bug because it has been reported with an old version, but don't get automagically fixed with new versions
[06:20] <seb128> jonh_wendell: you usually ask the submitter if it still gets the issue before closing something
[06:21] <jonh_wendell> seb128: the submitter is you; i've looked the LP bug report and it was rejected in Ubuntu
[06:22] <seb128> jonh_wendell: don't use the stock reply but say that to the comment in such case then :)
[06:40] <jonh_wendell> seb128: should i reopen that vino bug?
[06:40] <seb128> jonh_wendell: no that's fine, nobody has got it for a long time apparently
[06:40] <seb128> jonh_wendell: I would just have closed it with a comment saying that the Ubuntu bug is closed and it seems to not happen with the new version
[06:41] <jonh_wendell> seb128: sure, thanks for the tip
[06:41] <seb128> saying "you used an old version, I'm closing your bug" just doesn't apply for people using GNOME 2.10
[06:41] <seb128> 80% of the GNOME 2.10 bugs are still valid on GNOME 2.16 probably
[06:41] <seb128> np!
[11:16] <Adri2000> Ubugtu dead?
[11:22] <Admiral_Chicago> Adri2000: i think so, Lp was having problems according to crimsun
[11:33] <Le-Chuck_IT1> hi all
[11:33] <Le-Chuck_IT1> I have a question about bug fixing in ubuntu in general
[11:33] <Burgwork> shoot
[11:34] <Le-Chuck_IT1> I see that edgy has been released quite in time
[11:34] <Le-Chuck_IT1> but with some bugs affecting various packages
[11:34] <Admiral_Chicago> yes
[11:34] <Le-Chuck_IT1> and I can show evidences that these bugs are really a showstopper for many people
[11:34] <Le-Chuck_IT1> and
[11:35] <Le-Chuck_IT1> can I expect that they'll ever be fixed in edgy, not in feisty
[11:35] <Le-Chuck_IT1> and if not
[11:35] <Le-Chuck_IT1> isn't this gonna repeat in feisty?
[11:35] <Admiral_Chicago> Le-Chuck_IT1: what kind of bugs
[11:35] <Admiral_Chicago> further, do you have bug reports that we can inspect
[11:35] <Le-Chuck_IT1> e.g. beagle (which is in universe) breaking yelp once installed
[11:35] <Le-Chuck_IT1> lyx
[11:35] <mc44> Le-Chuck_IT1: yes, there will always be bugs in released distros that will not be fixed as fixing them may break more things
[11:36] <Le-Chuck_IT1> which in edgy is completely broken
[11:36] <Le-Chuck_IT1> and the italian locales for synaptic
[11:36] <Le-Chuck_IT1> that have been breaking italian update-manager since a month ago
[11:37] <mc44> Le-Chuck_IT1: well they will likely be fixed if they prevent upgrading
[11:37] <Le-Chuck_IT1> well I am a bit worried by the last one
[11:37] <Le-Chuck_IT1> seems like the simple fix of removing a ' character
[11:38] <Le-Chuck_IT1> has been put apart in favour of most serious fixes
[11:38] <Le-Chuck_IT1> but
[11:38] <Le-Chuck_IT1> what does it take to change a string
[11:38] <Le-Chuck_IT1> and update the fix immediately
[11:38] <Le-Chuck_IT1> expecially because it's a "stable update" that is breaking things
[11:38] <mc44> Le-Chuck_IT1: is there a bug filed for this?
[11:39] <Le-Chuck_IT1> I can point out https://launchpad.net/distros/debian/+source/beagle/+bug/67778 for the first one I mentioned
[11:39] <Ubugtu> Malone bug 67778 in beagle "Search don't work with beagle" [Unknown,Fix released]
[11:39] <Le-Chuck_IT1> now
[11:39] <mc44> Le-Chuck_IT1: I mean the locale problem
[11:39] <Le-Chuck_IT1> yes I know :)
[11:40] <Le-Chuck_IT1> just pasting the other one
[11:40] <mc44> :)
[11:40] <Le-Chuck_IT1> yes there is a well know open bug
[11:40] <Le-Chuck_IT1> even if perhaps I am not subscribed to that since I'm not finding it
[11:41] <Le-Chuck_IT1> I don't know
[11:41] <Le-Chuck_IT1> is asking a backport the right way to proceed?
[11:41] <Le-Chuck_IT1> instead of an SRU which is more complicated, I mean
[11:42] <mc44> its depends on the problem, if it is a language pack causing it, then it is adifferent matter
[11:43] <Le-Chuck_IT1> yes
[11:43] <mc44> Le-Chuck_IT1: https://bugs.launchpad.net/distros/ubuntu/+source/update-manager/+bug/70959 ?
[11:43] <Le-Chuck_IT1> but consider beagle
[11:43] <Ubugtu> Malone bug 70959 in update-manager "update-manager doesn't install updates when Italian locale is on" [Undecided,Unconfirmed]
[11:43] <mc44> Le-Chuck_IT1: beagle is non critical and unlikely to be updated with an SRU
[11:45] <Le-Chuck_IT1> here it is! https://launchpad.net/products/update-manager/+bug/51419
[11:45] <Ubugtu> Malone bug 51419 in gksu ""Install updates"-button only refreshes update list in it_IT environement" [High,Confirmed]
[11:45] <Le-Chuck_IT1> and of course 70959 is a duplicate of this one
[11:46] <Le-Chuck_IT1> I see beagle is non critical :) The point is
[11:46] <Le-Chuck_IT1> if software is non critical why not quick fix it expecially when it breaks more important programs?
[11:46] <Le-Chuck_IT1> not to be polemic
[11:47] <mc44> Le-Chuck_IT1: becasue it may well break many other things that are working fine
[11:47] <Le-Chuck_IT1> I am just trying to figure out best practices
[11:47] <Le-Chuck_IT1> yes but it's not the case for that bug: the bug is in a cron script, the cron script is wrong, it's breaking yelp
[11:47] <Le-Chuck_IT1> ok I surrender :)
[11:48] <Le-Chuck_IT1> I already went for a backport and it looks like it will be done
[11:48] <mc44> Le-Chuck_IT1: yay :)
[11:48] <Le-Chuck_IT1> ok but now: I should consider backports sort of "ubuntu quickfixed"
[11:49] <Le-Chuck_IT1> but it's not really so
[11:49] <Le-Chuck_IT1> because it's "ubuntu quickfixed with newer versions"
[11:50] <Le-Chuck_IT1> and I am still disappointed with the fact that broken workflow in the stable release will remain broken for months even when the fix is known
[11:50] <Le-Chuck_IT1> I mean
[11:50] <Le-Chuck_IT1> if I had a software company with many users
[11:50] <Le-Chuck_IT1> I would release some fix sometime
[11:50] <Le-Chuck_IT1> for bugs, crashes
[11:50] <Le-Chuck_IT1> not only for security
[11:50] <mc44> Le-Chuck_IT1: its a consequence of 6 month release cycle
[11:50] <Le-Chuck_IT1> I understand
[11:51] <Le-Chuck_IT1> it's not gentoo
[11:51] <mc44> and limited resources
[11:51] <Le-Chuck_IT1> but I see novell releases fixes and does not break things (except for their ugly package manager)
[11:51] <Le-Chuck_IT1> maybe it's a matter that they have much more resources
[11:52] <Le-Chuck_IT1> the point is: I am experimenting with living like ubuntu is MY software
[11:52] <mc44> I think mostly it is much stricter since we broke peoples X SERVERS with an upate to dapper stable
[11:53] <Le-Chuck_IT1> well again this confirms that "non critical" software could be easily quick-fixed while critical software should not be touched
[11:54] <Le-Chuck_IT1> another problem being that I find bugs in the sofware I use every day
[11:54] <Le-Chuck_IT1> so I must choose either to use the development version or not to contribute at all
[11:55] <mc44> you can still report bugs in stable versions
[11:55] <Le-Chuck_IT1> I did this intensively and many times I found that bugs where already reported and fixed in upstream, feisty or debian testing
[11:56] <Le-Chuck_IT1> that's a dog eating its tail :)
[11:56] <mc44> see, isnt free software great :) all your bugs are fixed!
[11:56] <Le-Chuck_IT1> Don't want to bore anyone with this chat, however it is important for me to understand what's the ubuntu mood about these issues :)
[11:56] <Le-Chuck_IT1> yes but I won't benefit of the fixes until feisty which will have other bugs that will not be fixed
[11:57] <mc44> Le-Chuck_IT1: ah but new and exciting bugs
[11:57] <Le-Chuck_IT1> I left dapper for the huge number of bugs that where there and in edgy
[11:57] <Le-Chuck_IT1> I had to resist a lot to the temptation
[11:57] <Le-Chuck_IT1> because I really like ubuntu
[11:57] <Le-Chuck_IT1> however
[11:57] <Le-Chuck_IT1> not to repeat myself
[11:57] <Le-Chuck_IT1> perhaps backporting is the right thing to do
[11:58] <Le-Chuck_IT1> do you think so mc44?
[11:58] <sfllaw> In many cases, backporting is the right thing.
[11:58] <sfllaw> Although we are doing stable updates for software that has a simple patch to fix bugs.
[11:58] <sfllaw> For instance, you can search the verification-needed tag, which shows packages that I'm aggressively testing.
[11:58] <sfllaw> Those will end up in dapper-updates or edgy-updates.
[11:59] <Le-Chuck_IT1> I think I should try again to push the beagle cron script and lyx
[11:59] <Le-Chuck_IT1> s/think/feel like/
[12:00] <Le-Chuck_IT1> lyx is completely useless in its current form
[12:00] <Le-Chuck_IT1> the dapper version was better
[12:00] <Le-Chuck_IT1> "Users of the official release, in contrast, expect a high degree of stability." this is what I think too
[12:00] <sfllaw> Your best bet is to find someone on IRC or via e-mail.
[12:01] <sfllaw> Discuss what the best minimal patch is to resolve the issue.
[12:01] <sfllaw> You can't really add features, but you can unbreak things.
[12:01] <Le-Chuck_IT1> and lyx is definitely not respecting this philosophy
[12:01] <Le-Chuck_IT1> sfllaw: the problem with lyx was gcc 4.1
[12:01] <sfllaw> Is it a compilation problem?
[12:01] <Le-Chuck_IT1> no, it's "lots of crashes" :) that version of lyx should never have reached a stable release of ubuntu
[12:02] <sfllaw> Ah.  I doubt you could convince anyone to go back a version.
[12:02] <Le-Chuck_IT1> it was a "keep version 1.3 or wait for the next release"
[12:02] <Le-Chuck_IT1> feisty release works well and I am ready to bet money it won't break any other pacakge
[12:02] <sfllaw> That one is a backport, I think.
[12:03] <Le-Chuck_IT1> ok, I see. I had it approved for backport today.
[12:03] <Le-Chuck_IT1> but
[12:03] <Le-Chuck_IT1> I talk with new ubuntu users almost every week here
[12:03] <Le-Chuck_IT1> in italy
[12:03] <Le-Chuck_IT1> and
[12:04] <Le-Chuck_IT1> they're all disappointed with the high number of bugs they encounter
[12:04] <sfllaw> Edgy is a not so polished release, as we put in a number of new things in a short amount of time.
[12:04] <Le-Chuck_IT1> e.g. that damn evince not remembering double-sided printing, that update issue and evolution autocontacts broken again :(
[12:05] <Le-Chuck_IT1> dapper was much worse!
[12:05] <Le-Chuck_IT1> don't misunderstand me
[12:05] <Le-Chuck_IT1> I really like edgy


[01:04] <Bhasha> hi
[01:05] <Bhasha><EMAIL_ADDRESS><= my facebook friends :)
[01:07] <Bhasha> add me
[08:39] <sachin> Why does installing a new desktop environment or window manager mess up the notification daemon of ubuntu mate?
[08:40] <sachin> I tried xfce, gnome and i3-wm, they all ruined the mate default notification layout.
[09:22] <desas> hello
[09:34] <vlt> Hello. I have a .rar archive that works perfectly fine with unar and unrar-free. When I open it with engrampa, in around 30% of the cases I get (number_of_files + 1) times "(engrampa:6699): GLib-CRITICAL **: g_strchomp: assertion 'string != NULL' failed" and the list of files shown by engrampa is empty.
[09:34] <vlt> Any idea what might cause this?
[09:35] <vlt> (Ubuntu 16.04)
[09:41] <alkisg> vlt: unrelated to your question, but, I just noticed that the shutdown button doesn't appear in ltsp fat clients in ubuntu-mate 16.04. Is it the same for you too?
[09:42] <alkisg> Eh, only in the classic menu. While in the advanced menu, it's displayed fine and it works fine.
[09:43] <vlt> alkisg: No, it's like the opposite here ;)  We don't have fat clients, only xrdp and we do have the shutdown button. How can we remove that?
[09:43] <alkisg> If you don't have fat then you're talking about the ldm menu, not the mate-panel menu :)
[09:43] <alkisg> Ah
[09:43] <alkisg> It's xrdp, not xfreerdp :D
[09:43] <alkisg> So you actually have mate-panel, but running on the server via vnc...
[09:44] <vlt> alkisg: Correct.
[09:44] <alkisg> OK, yeah that's unrelated to my issue :D
[09:44] <vlt> In know. But do you happen to how we can remove ours?
[09:44] <vlt> +know
[09:44] <alkisg> With policykit
[09:45]  * vlt imagines police kittens
[09:45] <vlt> Sorry :-D
[09:45] <alkisg> Hehe
[09:45] <alkisg> There's a setting there that prohibits users from shutting down the server, when other users are logged in
[09:46] <vlt> I think they can't even shut down the server when they are the only one logged in. Which is exactly what I want.
[09:47] <alkisg> There's another setting for that
[09:58] <alkisg> flexiondotorg: on a normal ubuntu-mate installation, is it possible to run mate-session with some debug flag or environment variable, so that then we see all the debug messages from the code, like: g_warning ("Could not connect to session manager: %s",
[09:58] <alkisg> ...or is recompilation necessary to see those g_warning messages?
[10:02] <flexiondotorg> alkisg Good question. I don't know off the top of my head.
[10:02] <flexiondotorg> You can also ask in #mate-dev
[10:03] <alkisg> flexiondotorg: found it; I put mate-session --debug in mate.desktop
[10:03] <alkisg> ty!
[10:55] <ordo> Hey there! Firstly, I really tried to find this info, but no luck - maybe I'm not that good at googling things :/
[10:55] <ordo> Anyway, back to the question: I'm using Ubuntu MATE (default setup) 16.04 and I wonder if it is possible to make windows switching (using alt+tab) to behave as it is in Unity, that is: windows are groupped by type and I can switch between windows of the same type by using alt+tilda. Right now, all windows are separate and this is really inconvinient for me.
[11:07] <lhtd> Hello, I have a sort of bug with tilda. After using it for a while, the default hight and width change. So when i'm not of full-screen it will occupy more space on the screen than it did at the beginning.
[13:19] <ordo> (tumbleweed) :)
[17:55] <mate-in-media> Installing 16.10 mate,  after a couple hours and about 90% done, appeared to hang up. How patient should i be?
[21:03] <Slown> Hey guys
[21:03] <Slown> what's going un with the latest updates ?
[21:03] <Slown> it's really a mess
[21:06] <Slown> hey guys please
[21:10] <lmike> Slown: what latest updates?
[21:11] <Slown> the latest kernel I mean
[21:11] <Slown> 4.8.0-42
[21:11] <lmike> I've also upgraded to 4.8
[21:12] <lmike> but I see no issues...
[21:12] <Slown> the updates from today I mean
[21:13] <lmike> well, I got 4.8.0-42 a couple of days ago
[21:13] <lmike> so far so good
[22:43] <xakh> hello! Quick question, does anyone have a good resource on getting the PiTFT to work with the Ubuntu Pi edition for the 3B? A quick google hasn't yielded much information.
[22:44] <xakh> I like using Ubuntu, and the MATE environment, over Raspbian and their slightly modified LXDE they've taken to calling "Pixel" for some reason now, and I was just wondering if anyone had experience getting this sort of thing working.
[22:50] <xakh> also if this is a question more for #raspberrypi or somewhere else lemme know, but last time I posted asking for help regarding Ubuntu MATE they basically all just said "If you want it to work use Raspbian lol duh"
[23:02] <sixwheeledbeast> Is there a reason why it doesn't just work? I don't know a lot about them
[23:12] <sixwheeledbeast> Ah so looking at it they link you to an installer which installs a repo with a modified kernel to allow the TFT to work. This could be why there are no simple instructions for getting it working.
[23:15] <sixwheeledbeast> TBH neither MATE or LXDE is very touch screen friendly. They're very mouse/desktop driven.
[23:36] <fishbowlkraken> yeah, the modified kernel just crashes the thing
[23:36] <fishbowlkraken> also, yeah, MATE isn't that great for touch friendliness, though I used it without much issue on the official 7" screen.
[23:37] <fishbowlkraken> Sorry, Ididn'
[23:38] <fishbowlkraken> oops, sorry, sixwheeledbeast, I didn't see the notification you'd replied. Apparently Raspbian has support for the screen in its latest release, but I'm not sure what I specifically need to port over to get the thing running on Ubuntu.
[23:42] <fishbowlkraken> Also, I plan on using an old Xbox chatpad I picked up for cheap as a keyboard with the system, so the touchscreen would be secondary, but I'm trying to do one incredibly dumb thing at a time, haha.


[14:24] <popey> is the experimental prevalidation ppa known to be broken right now?
[14:25] <popey> I have two machines on which compiz fails to start - well, dies
[14:52] <popey> hmmm
[14:56] <popey> seems I'm not using that ppa after all, but repo unity/compiz..
[14:59] <popey> fully up to date and unity wont start in a guest session
[15:01] <popey> http://paste.ubuntu.com/5683084
[15:16] <popey> Program received signal SIGSEGV, Segmentation fault.
[15:16] <popey> 0x00007fffdafc1785 in getCompPluginVTable20090315_unityshell () from /usr/lib/compiz/libunityshell.so
[15:17] <popey> bug 1162093
[15:17] <ubot2`> Launchpad bug 1162093 in Unity "Unity broken after latest update; compiz crashed with SIGSEGV in getCompPluginVTable20090315_unityshell()" [Undecided,New] https://launchpad.net/bugs/1162093
[15:18] <popey> bug 1162075
[15:18] <ubot2`> Launchpad bug 1162075 in unity (Ubuntu) "compiz crashed with SIGSEGV in getCompPluginVTable20090315_unityshell()" [Medium,Confirmed] https://launchpad.net/bugs/1162075


[04:31] <ScottK> Riddell: If it's -DPYTHON_LIBRARY, I would tend to suspect our CMake multiarch stuff for python, but I'm not sure.
[04:32] <ScottK> Riddell: re libkdcraw: mdeslaur ping'ed me about it on #ubuntu-hardened.  Great place to hang out.
[04:43] <ScottK> Riddell: libkdcraw is also released for quantal and raring.
[06:16] <soee> good morning
[08:47] <Riddell> ScottK: has anarchy broken lose yet?
[08:48] <Tm_T> Riddell: you forget there's states that manages plenty of it all on their own AFAIK
[08:48] <Tm_T> so no, we're not that lucky, yet
[09:22] <apachelogger> yofel, debfx: do we even still use xsettigns-kde? and if not what do we use?
[09:23] <apachelogger> Riddell: what do we do with userconfig bugs now?
[09:31] <Riddell> apachelogger: there's a good argument to say we should remove userconfig from the archive
[09:31] <apachelogger> oh we didn't? :O
[09:31] <apachelogger> Riddell: want a bug for that or can you simply do that?
[09:32] <Riddell> apachelogger: a bug would be handy
[09:32] <apachelogger> because userconfig is not maintained and due to what it does it can very well break ones system
[09:32] <Riddell> apachelogger: xsettings-kde is in the active seed and should be removed, we've not used it for a while
[09:32] <apachelogger> what are we using now?
[09:34] <Riddell> gtk3-engines-oxygen ?
[09:34] <apachelogger> but how is it set as default?
[09:34] <apachelogger> isn't that what xsettings-kde did
[09:35] <Riddell> mm yes
[09:35] <Riddell> magic?
[09:35] <apachelogger> ^^
[09:36] <apachelogger> yes
[09:36] <apachelogger> but
[09:36] <apachelogger> how ^^
[09:36] <apachelogger> will have to wait for someone with insight I guess
[09:40] <Riddell>   Add gtk2-default-theme.rc.sh back so gtk2 theming doesn't break if
[09:40] <Riddell>   xsettings-kde doesn't work
[09:41] <Riddell> committed by yofel to kubuntu-settings last year
[09:41] <apachelogger> lol
[09:41] <apachelogger> Riddell: https://bugs.launchpad.net/ubuntu/+source/userconfig/+bug/1234053
[09:42] <Riddell> similar question is should we remove networkmanagement?
[09:42] <Riddell> I'm not sure since I think plasma-nm still is flaky in some use cases
[09:42] <apachelogger> yesyesyes
[09:42] <apachelogger> Riddell: then why do we use it? :O
[09:42] <Riddell> at least it is with our old networkmanager
[09:42] <Riddell> apachelogger: it's better in others?
[09:43] <apachelogger> uhm
[09:43] <apachelogger> remove them both and use the gtk thing
[09:43] <apachelogger> it's better in everything Oo
[09:44] <apachelogger> Riddell: I still think networkmanagement should be removed
[09:44] <Riddell> apachelogger: ok file a bug for that too please
[09:44] <apachelogger> iff there are deal breaking issues with plasma-nm those should/must/need to be resolved via SRUs
[09:44] <apachelogger> IMHO
[09:44] <apachelogger> the solution cannot be 'install old thing and fiddle it into your plasma'
[09:47] <apachelogger> Riddell: https://bugs.launchpad.net/ubuntu/+source/networkmanagement/+bug/1234055
[09:47] <apachelogger> which reminds me that I wanted to do an rdeps check
[09:48] <apachelogger> Riddell: one gets to wonder whether we should introduce a transitional package though
[09:48] <apachelogger> Riddell: if kubuntu-desktop is not present people could otherwise end up without network manager
[09:52] <Riddell> apachelogger: yes that would make sense
[10:08] <ovidiu-florin> hello world
[10:08] <ovidiu-florin> apachelogger: any feedback from craig?
[10:08] <ovidiu-florin> I'd like to be involved in this movement, to learn how it's done
[10:08] <ovidiu-florin> could I??
[10:09] <apachelogger> no answer yet, and yes you could do that stuff
[10:09] <apachelogger> it's mostly just filing requests anyway
[10:11] <apachelogger> https://sysadmin.kde.org/tickets/index.php?page=tickets&act=add&step=2&did=12 that thing mostly
[10:14] <BluesKaj> Hey folks
[10:17] <smartboyhw> So, no XMir
[10:18] <apachelogger> it's all ur fault
[10:18] <Riddell> no love lost there
[10:18] <Riddell> https://bugs.kde.org/show_bug.cgi?id=325460#c4  "Can I just say you guys are awesome? I've used KDE with various distributions for years (and with Kubuntu for the last ~2) but never reported a bug until now. I am amazed at how quickly it was acknowledged and came to some form of resolution. "
[10:18] <Riddell> wish we could do that with all the bugs :)
[10:18] <smartboyhw> Riddell, agreed
[10:19] <smartboyhw> apachelogger, it's other's fault not mine :P
[10:21]  * Riddell blogs http://blogs.kde.org/2013/10/02/kubuntu-beastie-fixing
[10:22] <ovidiu-florin> apachelogger: I don't have an account there
[10:27] <smartboyhw> To remind everybody: Community Council check-in is tomorrow
[10:27] <smartboyhw> 17:00 UTC, #ubuntu-meeting
[10:28] <smartboyhw> Er, everybody I think might specifically apply to KC mroe
[10:28] <smartboyhw> But I just saw it on the CC agenda enyhow
[10:28] <smartboyhw> *anyhow
[10:31] <apachelogger> Riddell: new user-manager not uploaded yet?
[10:32] <apachelogger> ovidiu-florin: identity.kde.org
[10:32] <apachelogger> ^ global kde login
[10:32] <ovidiu-florin> ok
[10:34] <ovidiu-florin> apachelogger: so I should just submit a ticket after we get a responce from craig?
[10:35] <apachelogger> ovidiu-florin: ping me first please, so the information is correct ^^
[10:35] <ovidiu-florin> ok
[10:35] <Riddell> apachelogger: yeah 0.0~git20130930-0ubuntu1  is in
[10:36] <apachelogger> ScottK: the amount of bug reports for synaptiks is scary :(
[10:36] <apachelogger> Riddell: can't change password :S
[10:36] <Riddell> apachelogger: sigh, passwords were working fine for me
[10:36] <Riddell> apachelogger: user avatars were not
[10:36] <apachelogger> oh
[10:36] <apachelogger> I am still on the july snapshot
[10:36] <apachelogger> wtf
[10:36] <Riddell> apt-get update is your friend :)
[10:37] <apachelogger> user-manager	0.0~git20130719-0ubuntu1
[10:37] <apachelogger> Riddell: that's today's ISO
[10:37] <apachelogger> http://cdimage.ubuntu.com/kubuntu/daily-live/current/saucy-desktop-i386.manifest
[10:37] <ovidiu-florin> apachelogger: Submit A Ticket -> Git repository request ?
[10:38] <apachelogger> Riddell: ah, 4 hours ago published, nevermind
[10:38] <apachelogger> ovidiu-florin: yes
[10:38] <ovidiu-florin> apachelogger: but that doesn't go to the same page that you've sent me
[10:39] <ovidiu-florin> https://sysadmin.kde.org/tickets/index.php?page=tickets&act=add&step=2 compared to https://sysadmin.kde.org/tickets/index.php?page=tickets&act=add&step=2&did=12
[10:39] <apachelogger> ovidiu-florin: does for me
[10:39] <ovidiu-florin> I don't know how mych that did=12 counts
[10:39] <apachelogger> not sure what it does :P
[10:40] <apachelogger> ah
[10:40] <ovidiu-florin> it could be something specific to your acount type
[10:40] <apachelogger> did is the actual id of the request
[10:40] <apachelogger> i.e. if you open the url without did you get to the selection screen
[10:40] <apachelogger> if you open the did url you get the actual git request page
[10:40] <apachelogger> same thing regardless
[10:40] <ovidiu-florin> oh
[10:41] <apachelogger> Riddell: so, what do we do with jockey v software-properties?
[10:41] <ovidiu-florin> there must be something up with my chrome
[10:44] <Riddell> apachelogger: what is jockey v software-properties?
[10:45] <apachelogger> Riddell: jockey is apparently deprected in ubuntu and partially broken (at least no versions are displayed) on our end... and apparenlty on ubuntu the features have been integrated into software-properties
[10:47] <apachelogger> and I smell untranslatable strings in s-p
[10:49] <Riddell> apachelogger: really? software-properties only does sources.list surely?
[10:49] <Riddell> apachelogger: last we spoke about it jon was going to add to muon but that never happened
[10:49] <apachelogger> Riddell: that's what the bug report says at least
[10:50] <Riddell> apachelogger: which bug report?
[10:50] <apachelogger> and l10n alert whooowhoooowhoooowhooooo
[10:50] <apachelogger> Riddell: bug 1078379
[11:06] <apachelogger> Riddell: http://i.imgur.com/dSJNvj4.png
[11:07] <Riddell> apachelogger: yeah, seb just confirmed the same, it uses ubuntu-drivers-common and soft-properties-gtk as frontend
[11:07] <Riddell> apachelogger: so the answer is just to add that frontend on to soft-properties-kde
[11:07] <Riddell> apachelogger: but I guess for this cycle our solution is a broken jockey unless we find a quick python coder
[11:09] <apachelogger> meh
[11:09] <apachelogger> s-p neeeds review anyway
[11:09] <apachelogger> the gtk version has no statistics tab anymore
[11:10] <apachelogger> and our l10n of it is broken because for some reason qt ui files are not extracted into the pot
[11:10] <apachelogger> so I am tempted to hide() that tab
[11:13] <Riddell> yeah that's fine
[11:18] <apachelogger> bug 1234106
[11:26] <apachelogger> #  Copyright © 2009 Harald Sitter<EMAIL_ADDRESS>[11:26] <apachelogger> :O
[11:26] <apachelogger> I totally don't remember working on s-p
[11:26] <Riddell> I'm sure it was me who did that, why you steal my glory?
[11:27] <soee> ;]
[11:27] <apachelogger> Riddell: Canonical Ltd stole your glory :P
[11:27] <soee> 4.11.2 for raring ?
[11:27] <apachelogger> that's the other copyright holder
[11:27] <apachelogger> may be that I ported to qt4
[11:34] <apachelogger> really
[11:34] <apachelogger> where is jon the taco
[11:34] <apachelogger> http://i.imgur.com/6k0SbpU.png
[11:34] <apachelogger> Riddell: that may be evil upstream polkit l10n problem there
[11:34] <apachelogger> <- scared
[11:35] <apachelogger> ARGH
[11:35] <apachelogger> there's still stuff untralsated
[11:35] <apachelogger> *untranslated
[11:37] <apachelogger> Riddell: so, bug 1234106 needs a resolution asap and I have no clue about either of the involved utils so I can't do anything about it
[11:41] <apachelogger> Riddell: do you still have the l10n statistics of the user-manager snapshot? (shoudl be in the releaseme dir)
[11:41] <apachelogger> http://i.imgur.com/D5YNond.png
[11:41] <apachelogger> not sure if those are not i18n'd or not l10n'd
[11:43] <apachelogger> http://i.imgur.com/jQd4ZxS.png
[11:43] <Riddell> apachelogger: http://starsky.19inch.net/~jr/tmp/user-manager-l10n-0.0~git20130930.html
[11:46] <apachelogger> not l10n'd then
[11:46] <apachelogger> and I think I broke my password
[11:46] <apachelogger> :O
[11:46] <ovidiu-florin> apachelogger: have you seen the mail from Craig?
[11:46] <apachelogger> and I am not sure how
[11:46] <ScottK> Riddell: Not yet.  Mostly just people being put out of work who've got nothing to do with whatever is going on.
[11:47] <ScottK> apachelogger: Sure, but it also works fine for a lot of people and there's no better alternative.  You should convince afiestas to make one.
[11:51] <apachelogger> ovidiu-florin: replied
[11:52] <apachelogger> ScottK: so sad, maybe tsdgeos should make that happen, I seem to recall him having experience with touch things ;)
[11:53] <ovidiu-florin> apachelogger: I was thinking of a diffferent name for it, but it's his project, so I guessed it's his choice.
[11:54] <apachelogger> ovidiu-florin: well, you can always send a mail with other suggestions :P
[11:54] <apachelogger> as you said, it's his project, so I don't care what it gets called
[11:55]  * apachelogger gets headache again :(
[11:55] <ovidiu-florin> apachelogger: discard my responce ... I need to set reply to all by default
[11:56] <apachelogger> ovidiu-florin: 'a' in gmail
[11:56] <ovidiu-florin> same in kmail
[11:56] <apachelogger> right, so hit a :P
[11:56]  * apachelogger never ever uses r
[12:04] <ovidiu-florin> forwarded you his responce
[12:04] <ovidiu-florin> apachelogger: ^
[12:05] <apachelogger> don't see anything
[12:07] <ovidiu-florin> apachelogger: now?
[12:07] <lordievader> Good afternoon.
[12:08] <ovidiu-florin> hello lordievader
[12:08] <apachelogger> ovidiu-florin: ufw-kde then
[12:08] <lordievader> Hey ovidiu-florin, how are you?
[12:09] <ovidiu-florin> apachelogger: ok
[12:09] <ovidiu-florin> I'll start now
[12:09] <ovidiu-florin> lordievader: learning all I can
[12:09] <ovidiu-florin> lordievader: you?
[12:10] <apachelogger> ovidiu-florin: so on the ticket site the repo name would be 'ufw-kde', the pretty name 'UFW-KDE' the initial maintainers 'craig;sitter' and the location 'playground/sysadmin'
[12:11] <lordievader> ovidiu-florin: Good luck, I'm doing fine. :)
[12:11] <apachelogger> ovidiu-florin: oh and in the description at the bottom mention that if they need confirmation they shall poke apachelogger on irc
[12:12] <ovidiu-florin> one line description: A gui for the UFW firewall
[12:12] <ovidiu-florin> apachelogger: ^
[12:12] <apachelogger> yeah
[12:12] <ovidiu-florin> Priority?
[12:12] <apachelogger> low
[12:13] <ovidiu-florin> Subject? Add git repo for UFW GUI ?
[12:13] <apachelogger> just 'git repo ufw-kde' I guess
[12:16] <ovidiu-florin> apachelogger: https://sysadmin.kde.org/tickets/index.php?page=tickets&act=view&id=WQN-2731
[12:16] <apachelogger> can't see that ^^
[12:18] <ovidiu-florin> apachelogger: then, just: Ticket ID: WQN-2731
[12:21] <smartboyhw> ovidiu-florin, I presume that not only the original maintainer will help to squash bugs but you will also maintain it yourself?
[12:21] <ovidiu-florin> I would like to do that
[12:23] <smartboyhw> Schedule for today: Now - 21:15: Homework 21:15-22:00 Piano practice 22:00-23:00 Ubuntu Reminders App meeting 23:00 - 06:45: sleep (Hmm, never got such a planned day)
[12:23] <ovidiu-florin> should I apply for developer access?
[12:23] <ovidiu-florin> smartboyhw: ^
[12:23] <smartboyhw> ovidiu-florin, well, if you are seriously opting to maintain it, yes
[12:25] <ovidiu-florin> I would, but, again, I don't know how much time I can allocate to this, since school just started + my jobs.
[12:26] <ovidiu-florin> I don't want to be responsible for something if I don't know I can handle it
[12:26] <ovidiu-florin> that's why right now I'mm just watching and learning and doing minor tasks
[12:26] <smartboyhw> ovidiu-florin, maybe we put it like this: Will you submit code often?
[12:27] <ovidiu-florin> right now (for the following few months) no
[12:27] <ovidiu-florin> not often
[12:27] <ovidiu-florin> I still have to learn how sone things in KDE work
[12:28] <ovidiu-florin> so I'll just stick to the review board for now
[12:31] <apachelogger> oh eh, meh -.-
[12:31] <apachelogger> locale kcm is still kaput
[12:33] <apachelogger> and user-manager has l10n issues -.-
[12:45] <shadeslayer> anyone working on the Raring packages?
[12:45] <shadeslayer> Riddell: ^^
[12:46] <Riddell> shadeslayer: still to get to it I'm afraid
[12:46] <shadeslayer> okie
[12:48]  * shadeslayer checks preciswe
[12:58] <soee> shadeslayer, im w... aiting for Raring packages :)
[12:59] <shadeslayer> soee: I think raring should work, except for kalzium
[12:59] <shadeslayer> which I'll fix in a bit
[13:00] <soee> ill wait for fixes, don't want to break my pc here at work
[13:00] <shadeslayer> okie
[13:00] <shadeslayer> yofel: btw any SSD recommendations?
[13:16] <shadeslayer> we have boost 1.49 as the default in raring correct?
[13:17] <tsimpson> !info libboost-dev raring
[13:40] <Riddell> shadeslayer: I'm looking at pykde in raring now
[13:40] <shadeslayer> cool
[13:40] <Riddell> shadeslayer: yes 1.49 says https://launchpad.net/ubuntu/+source/boost-defaults
[13:41] <shadeslayer> I added libboost-python1.49-dev to kalzium build-deps and it still doesn't work
[13:41] <shadeslayer> i.e pbuilder fails to satisfy deps
[13:42] <Riddell> shadeslayer: on raring?
[13:42] <shadeslayer> yep
[13:44] <shadeslayer> http://pastebin.kde.org/ptkavfswt
[13:44] <shadeslayer> ( I know it says libboost-python-dev,, but I tried it with libboost-python1.49-dev as well )
[13:44] <shadeslayer> !info libboost-python1.49-dev
[14:05] <genii> After yesterdays round of updates... Cannot ctrl-alt-Functionkey to any tty from lightdm-kde-greeter
[14:20] <shadeslayer> *farepalm*
[14:23] <Riddell> shadeslayer: looks like you worked it out, just needed the same thing done as 4.11.1 had
[14:23] <shadeslayer> yeah
[14:23] <Riddell> shadeslayer: will you add a script to kubuntu-automation/backport-hooks/stable ?
[14:23] <shadeslayer> yep
[14:25] <debfx> apachelogger: afaik the gtk theme KCM creates a gtk3 ini file to set the theme name so xsettings-kde isn't use anymore
[14:29] <shadeslayer> Riddell: done
[14:30] <Riddell> lovely, installing 4.11.2 on raring for a test
[14:30] <shadeslayer> cool
[15:09] <Riddell> running in Xephr the apps don't show anything, how annoying, probably some issue with the xephyr chroot but how do I confirm?
[15:09] <Riddell> ec2 it is
[15:11] <shadeslayer> Riddell: could you also test precise? my VBox is too slow
[15:15] <Riddell> shadeslayer: I'll fire one up
[15:15] <shadeslayer> okie
[15:44] <shadeslayer> jono: got a moment?
[15:47] <jono> shadeslayer, on the phone now
[15:47] <shadeslayer> sure
[16:11] <Riddell> shadeslayer: precise all working
[16:11] <Riddell> vnc to  ec2-107-20-106-215.compute-1.amazonaws.com:5901 foobar if you want to try :)
[16:13] <shadeslayer> cool, no need to vnc in :)
[16:21] <Riddell> shadeslayer: and raring good too
[16:21] <shadeslayer> cool
[16:22] <Riddell> shadeslayer: so time to copy them over?
[16:22] <Riddell> you want the honours or shall I?
[16:22] <shadeslayer> sure go ahead
[16:22] <cortexA9> hello
[16:22] <cortexA9> Riddell
[16:22] <cortexA9> the daily of today failed to boot
[16:23] <cortexA9> with usb key
[16:23] <cortexA9> you know ?
[16:25] <Riddell> cortexA9: nope, what's up?
[16:28] <Riddell> for asdf in `cat ~/src/kubuntu-automation/kubuntu-automation/kdesc-packages-saucy.txt`; do echo ${asdf}; ./copy-package -s raring -p kubuntu-ninjas --ppa-name=ppa -b --to-ppa=kubuntu-ppa --to-ppa-name=backports --unembargo ${asdf} -y; done
[16:28] <Riddell> should keep it busy
[16:29] <cortexA9> Riddell
[16:29] <cortexA9> it doesnt boot
[16:29] <cortexA9> idk..
[16:30] <shadeslayer> jono: still on the phone?
[16:30] <shadeslayer> Riddell: you know
[16:30] <shadeslayer> Riddell: kopypackages
[16:31] <shadeslayer> Riddell: kopypackages -a ppa:kubuntu-ninjas/ppa $RELEASE ppa:kubuntu-ppa/backports $RELEASE
[16:32] <jono> shadeslayer, nearly done
[16:32] <shadeslayer> oh okay
[16:36] <Riddell> shadeslayer: ah yes forgot about that
[16:36] <shadeslayer> :)
[16:36] <jono> hey shadeslayer
[16:36] <jono> free now
[16:36] <shadeslayer> heya, PM?
[16:36] <jono> sure
[16:49] <Riddell> shadeslayer: kopypackages doesn't seem to do anything
[16:49] <shadeslayer> how are you using it?
[16:50] <Riddell> ./kopypackages -a ppa:kubuntu-ninjas/ppa precice ppa:kubuntu-ppa/backports precise
[16:50] <shadeslayer> precice?
[16:50] <shadeslayer> :P
[16:50] <Riddell> aah
[16:51] <Riddell> ok onto l10n
[16:59] <markey> here's an update on my C++11 compilation issue: it's not just me
[16:59] <markey> the same errors happen on Mamarok's box
[16:59] <markey> it is a packaging error
[17:00] <Riddell> oh could well be but not one we have any experience with, it'll be a general ubuntu issue if it's a distro fault
[17:01] <markey> something has regressed with an update during the last 4 weeks or so
[17:01] <markey> yep
[17:03] <Riddell> last upload of clang 3.2 at end of august https://launchpad.net/ubuntu/+source/llvm-toolchain-3.2
[17:03] <markey> it would fit
[17:04] <markey> I haven't touched C++11 in a while
[17:04] <markey> interestingly, on apachelogger's computer it works correctly. I think he's using Kubuntu 13.10
[17:05] <markey> Clang 3.2.1 I think
[17:07] <markey> so I'll just upgrade to 13.10 tomorrow and hope the problem will fix itself. but I thought you might want to know about it
[17:10] <markey> especially since C++11 is going to get more real-life usage soon,
[17:11] <markey> as we want to start using it, and I think KDE in general as well
[17:11] <Riddell> ah so you think it's an update on 13.04
[17:11] <markey> http://community.kde.org/Frameworks/Policies#Frameworks_compiler_requirements_and_C.2B.2B11
[17:11] <markey> yes
[17:12] <markey> a regression
[17:12] <Riddell> no obvious candidates on https://lists.ubuntu.com/archives/raring-changes/2013-September/thread.html
[17:13] <Riddell> impressive how many SRUs are done by Kubuntu team and how few by ubuntu desktop team
[17:13] <markey> indeed...
[17:14] <markey> the direct feedback we have between developers and distro developers is really valuable. one of the aspects that make Kubuntu a joy to use for me
[17:18] <Riddell> markey: we try :)
[20:39] <Riddell> shadeslayer: good to announce 4.11.2?
[20:43] <ScottK> Canonical are using C++11, so I'm sure they do/will care.
[20:45]  * Riddell publishes kubuntu.org/news/kde-sc-4.11.2
[22:39] <snele> yellow restart button does nothing when pressed in beta2
[22:40] <snele> I mean button which appears is system tray when you install some updates
[22:41] <snele> few times popped up these days, and always when I click on it nothing happens
[22:41] <snele> I don't know against which component I should file a bug