[21:58] <belkinsa> #startmeeting Project Harvest Development Planning Meeting
[21:58] <meetingology> Meeting started Fri Feb 27 21:58:58 2015 UTC.  The chair is belkinsa. Information about MeetBot at http://wiki.ubuntu.com/meetingology.
[21:58] <meetingology> Available commands: action commands idea info link nick
[21:59] <belkinsa> Who is all for the meeting?
[22:01] <belkinsa> o/ Sakti
[22:01] <Sakti> Hi Svetlana! How are you?
[22:02] <belkinsa> I'm fine, just waiting for the other one t o show up
[22:02] <Sakti> There she is. Hi Sugetha!
[22:03] <belkinsa> How are you?
[22:03] <belkinsa> Prefect.
[22:03] <sugetha> Hi everyone
[22:03] <belkinsa> You guys ready for the meeting?
[22:03] <Sakti> yeah.
[22:03] <sugetha> yup
[22:03] <belkinsa> Okay.  The bugs are here;
[22:04] <belkinsa> #link https://bugs.launchpad.net/harvest
[22:05] <Sakti> Okay. how do we go about picking them?
[22:05] <belkinsa> I think we need to tackle the high importance ones first
[22:05] <Sakti> what does the status denote?
[22:05] <belkinsa> Sakti, I think we look at them and figure out if you can do it.
[22:05] <Sakti> incomplete, confirmed and so on?
[22:06] <belkinsa> We are looking at comnfirmed ones.
[22:06] <belkinsa> We can start with this one: https://bugs.launchpad.net/harvest/+bug/617256
[22:07] <Sakti> that makes sense
[22:07] <belkinsa> Who wants this bug?
[22:07] <Sakti> dumb question, which is the website these bugs are assigned to?
[22:08] <belkinsa> #link http://harvest.ubuntu.com/
[22:08] <belkinsa> This one
[22:08] <belkinsa> Code is here:
[22:08] <belkinsa> #link https://code.launchpad.net/harvest
[22:09] <sugetha> And how do I go about knocking these bugs out? And what version control do you use? How do I incorporate the changes into the code?
[22:10] <belkinsa> You submit patches and Daniel Holbach  will look at them.
[22:10] <sugetha> Is there some documentation that could help newbies like myself knock out bugs?
[22:10] <belkinsa> There should be, give me a sec
[22:11] <Sakti> where do we submit the patches?
[22:11] <belkinsa> #link https://help.launchpad.net/Bugs/BugBranchLinks
[22:12] <belkinsa> And also
[22:12] <belkinsa> #link https://help.launchpad.net/Bugs
[22:14] <sugetha> are there any guidelines for posting patches?
[22:14] <Sakti> these bugs are the bugs on the harvest webpage or ubuntu?
[22:14] <belkinsa> Sakti, harvest and sugetha, I think there isn't.
[22:17] <Sakti> I am thinking out loud here, if I am to solve that bug, which says ./opportunities page has some bugs,
[22:17] <Sakti> i would go look for it's code, http://bazaar.launchpad.net/~harvest-dev/harvest/trunk/files/head:/harvest/
[22:17] <Sakti> there right?
[22:17] <belkinsa> Oh, the patches are through your own personal branch that goes to LP
[22:18] <belkinsa> Yes, but you need to check out the code to work on it
[22:18] <Sakti> ya the code inside opportunities folder
[22:19] <belkinsa> Yup, it sould be organized based on what it is of harvest
[22:21] <sugetha> Is there any documentation to build the entire project and see if my code fixes the project?
[22:22] <belkinsa> Yes.
[22:22] <belkinsa> #link http://bazaar.launchpad.net/~harvest-dev/harvest/trunk/view/head:/INSTALL
[22:23] <belkinsa> #link http://bazaar.launchpad.net/~harvest-dev/harvest/trunk/view/head:/HACKING
[22:23] <belkinsa> This too.
[22:24] <sugetha> alright thanks
[22:24] <belkinsa> Not a problem.
[22:24] <Sakti> Svetlana, to be sure, I should start with the first branch in https://code.launchpad.net/harvest right?
[22:25] <belkinsa> Yes, I think those other ones are pathes
[22:25] <belkinsa> patches*
[22:25] <belkinsa> The first one is the main one.
[22:26] <Sakti> alright cool. so when we start submitting patches, our branches will be listed down right?
[22:26] <belkinsa> I think so.
[22:26] <sugetha> cool
[22:27] <belkinsa> Sorry for not giving the information before the meeting.
[22:28] <sugetha> I will take one bug for now and see how I fare and then take in more once I knock that off?
[22:28] <belkinsa> Sure.
[22:28] <belkinsa> Sakti, you may also.
[22:29] <sugetha> I will take this: #886171
[22:29] <Sakti> I will do the same aswell. I haven't worked with launchpad before. So it will be a good starting point to get used to it
[22:29] <Sakti> I will take #617256
[22:29] <belkinsa> Perfect, assign yourselves to those two.
[22:30] <sugetha> Done
[22:30] <belkinsa> And I saw/
[22:30] <belkinsa> And before we close, can we set a deadline for these two?
[22:31] <belkinsa> And I will work on this one: https://bugs.launchpad.net/harvest/+bug/1426574
[22:33] <Sakti> Sure.
[22:34] <belkinsa> How long long do you think it needs to be?
[22:34] <Sakti> before committing to anything, can we take a look at the codebase over the weekend and come up with a deadline next week?
[22:34] <belkinsa> Sure, that works.
[22:35] <sugetha> I am not sure how to commit to a deadline. I have no idea how to use the interface and I don't know how long that would take m
[22:35] <sugetha> *me
[22:35] <Sakti> awesome
[22:35] <sugetha> yes that seems like a good idea, sakti
[22:35] <belkinsa> sugetha, right, I forgot but let's try Sakti's idea.
[22:36] <belkinsa> We can have a follow up meeting or we can do it via e-mail for the deadline.
[22:36] <sugetha> yes
[22:37] <Sakti> Ya either works. :)
[22:37] <belkinsa> Perfect.
[22:37] <belkinsa> Anything else?
[22:37] <belkinsa> Actually, afterthought, it will be done via e-mail as I have a class and an exam to study for.
[22:37] <Sakti> No that'd be all I think from myside. Am sure I might have more questions once I bite into the codebase
[22:38] <Sakti> email works too :)
[22:38] <belkinsa> Sakti, alright, Daniel Holbach can help you also.
[22:38] <sugetha> email works good too
[22:38] <belkinsa> Perfect.
[22:38] <sugetha> how do we reach out to him?
[22:39] <belkinsa><EMAIL_ADDRESS>is his e-mail
[22:39] <Sakti> Got it..
[22:39] <sugetha> alrighty
[22:40] <belkinsa> Anything else?
[22:40] <sugetha> no that would be all
[22:40] <belkinsa> Afterthought.  Do you guys use Trello by any chance?
[22:40] <Sakti> No that's it I think
[22:40] <sugetha> yes we do
[22:40] <Sakti> Ya I do..
[22:41] <belkinsa> You want to use a board on there for the deadlines?
[22:41] <sugetha> sure
[22:41] <Sakti> Ya that's ideal too.
[22:41] <belkinsa> E-mails please
[22:41] <belkinsa> Never mind, I have them
[22:42] <belkinsa> Sent.
[22:42] <Sakti> Added!
[22:42] <belkinsa> Thank you.
[22:44] <sugetha> Done aswell
[22:44] <belkinsa> Thank you
[22:44] <sugetha> Is there anything else?
[22:45] <belkinsa> Nope. I will end the meeting if we are set.
[22:45] <Sakti> Ya I think we are set. Lets continue adding to trello board if you think of some activity that we might have missed.
[22:45] <belkinsa> Thank you all for coming to this meeting and sure, I will.
[22:46] <belkinsa> #endmeeting
[22:46] <meetingology> Meeting ended Fri Feb 27 22:46:20 2015 UTC.
[22:46] <meetingology> Minutes:        http://ubottu.com/meetingology/logs/ubuntu-women-project/2015/ubuntu-women-project.2015-02-27-21.58.moin.txt
[22:46] <Sakti> Sure. Thanks Svetlana!
[22:47] <belkinsa> Not a problem.
[22:49] <sugetha> Alright then. TTY.
[22:49] <belkinsa> Enjoy your weekend you two.
[22:50] <Sakti> Thanks! You too. :)


[22:57] <zpmorgan> ts2, Do you know anything about the ASPM overheating regression??
[22:58] <ts2> zpmorgan: best to ask in #ubuntu this channel is no longer active
[22:59] <zpmorgan> okay thanks; I asked #ubuntu-kernel
[23:05] <zpmorgan> hi AlanBell
[23:05] <AlanBell> hi
[23:06] <zpmorgan> Do you know anything about the ASPM overheating regression?
[23:06] <zpmorgan> my laptop keeps overheatingl dunno what to do
[23:06] <AlanBell> in precise?
[23:06] <zpmorgan> I don't even know if that bug still exists in the latest oneiric kernel
[23:07] <AlanBell> I would suggest cleaning the fans and vents and upgrade to precise as soon as you dare
[23:08] <AlanBell> it isn't very scary at the moment to be honest
[23:08] <zpmorgan> Do you know if it will eventually be fixed in Oneiric?
[23:08] <AlanBell> no idea
[23:08] <AlanBell> there is a kernel boot parameter you can set to turn it on
[23:08] <zpmorgan> I tried that
[23:08] <zpmorgan> pcie_aspm=force or something
[23:08] <AlanBell> yeah, that
[23:08] <zpmorgan> And it still overheats with just one core doing something productive
[23:09] <AlanBell> and there are a heap of other tweaks mostly fixed in precise
[23:09] <zpmorgan> What's the state of precise? How likely is it to basically break unbootably?
[23:10] <zpmorgan> (in your experience)
[23:10] <AlanBell> more to the point what would your reaction be if it did?
[23:10] <zpmorgan> boot off a usb key and google it
[23:11] <AlanBell> if you were to boot up to a black screen and think "hmm, thats interesting" then go for it
[23:11] <zpmorgan> okay :)
[23:11] <AlanBell> there is support in #ubuntu+1
[23:11] <zpmorgan> I don't think I've installed an ubuntu+1 since 2006
[23:12] <AlanBell> ts2: I am going to have to grab nalioth or someone to forward this channel, I will do it tomorrow or sometime
[23:12] <AlanBell> zpmorgan: this is a relatively stable cycle, they are not doing any scary changes really
[23:12] <zpmorgan> cool! thanks for the advice
[23:13] <AlanBell> and there is a lot more testing going on before stuff gets released
[23:16] <zpmorgan> AlanBell, ts2, for whatever you've done for ubuntu, thank you!


[05:09] <alex_mayorga> Hi, is there a patch coming to let me tell firefox I want to see notifications even when in full screen?
[05:14] <vish> alex_mayorga: you need to ask MacSlow ;)  he'd probably be here in a fwe hrs
[05:15] <vish> alex_mayorga: but it seems to be planned for lucid
[05:16] <alex_mayorga> I also believe that the whole urgency level should be left up for we users to decide
[05:16] <alex_mayorga> make those available as "System > Preferences > Notifications"
[05:19] <vish> alex_mayorga: the min you say "prefs" the idea is most likely to be shot down ;)
[05:21] <alex_mayorga> well whomever is in charge might want to take a look at #ubuntu+1 log from moments ago
[05:22] <alex_mayorga> I believe this would serve as a summary "I think is plainly arrogant to decide for users, what's important or not or how fast they should read and such"
[05:25] <vish> alex_mayorga: i agree the prefs are needed... But , *i think* , what they are trying to do is to get the default settings perfect before allowing the users to tweak at will... the default seems to be the high priority for canonical and the config/prefs are probably not in their schedule [unless someone outside works on them]
[05:26] <alex_mayorga> why try to get it to perfect for me, when just I will know what's perfect for *me*
[05:26] <alex_mayorga> and then "perfection" would be in the eye of the beholder in the end
[05:27] <alex_mayorga> but yeah, from the wiki I can tell configuration is not at the top of the priority list if at all
[05:27] <vish> alex_mayorga: well,  you can of course switch/use the notification daemon :)
[05:27] <alex_mayorga> I've kind of got to that conclusion from what I've seen so far
[05:28] <alex_mayorga> just wanted to say once more that if you make it 100% configurable then you're done ;)
[05:29] <alex_mayorga> otherwise just get ready to deal with loads of "incorrect urgency" bug reports
[05:30] <alex_mayorga> as what is "important" for Jon Doe might not be for Jane Doe
[05:30] <ScottK> alex_mayorga: I totally agree with you, but that's not been the perspective of this project.
[05:31] <alex_mayorga> this is only being pushed in ubuntu, not upstream right?
[05:31] <vish> Ubuntu is upstream for notify-osd
[05:32] <alex_mayorga> ScottK, and is not turning over for what I see
[05:32] <ScottK> vish: Actually no.  Ayatana is upstream for notify-osd.  It's a separate project from Ubuntu (but also sponsored by Canonical)
[05:32] <alex_mayorga> vish: what are OSD "competitors" then?
[05:32] <vish> ScottK: argh! slipped Ubuntu==canonical ;)
[05:33] <vish> alex_mayorga: i dont think there are any competitors... unless you consider the gnome3 notifications/ message tray ...
[05:35] <vish> alex_mayorga: if you have been following the ayatana discussions.. any mention of a pref/gconf is most definitely shot down.. there is nothing much to say after that.. its their[canonical] money and their choosing of how they spend it...
[05:42] <alex_mayorga> I guess the last comment on https://wiki.ubuntu.com/NotifyOSD/Comments should do then
[05:43] <RAOF> alex_mayorga: It's already 100% configurable; you've got access to lp:notify-osd.  Nothing else will be 100% configurable.
[05:44] <alex_mayorga> RAOF, mind elaborating on lp:notify-osd?
[05:46] <RAOF> That's the source branch.
[05:46] <RAOF> I'm suggesting that “100% configurable” and “useful” are in opposition.
[05:54] <alex_mayorga> RAOF, so you mean the only configuration point one has is the source code?
[06:01] <RAOF> alex_mayorga: No, I mean the only way that you can have a 100% configurable application is with the source code.  But it's also true that the only configuration at the moment is the source code.
[06:01] <RAOF> alex_mayorga: I'm just disagreeing with your “if you make it 100% configurable then you're done” statement.
[06:03] <alex_mayorga> RAOF: I believe making it that way would render the "problem" non-existant
[06:09] <RAOF> At the cost of introducing new problems, yes.
[06:15] <ScottK> RAOF: Certainly, but OTOH, it's also equally impossible to design the one true configuration for all users.
[16:30] <seg|ars> djsiegel1: are you around?
[16:30] <djsiegel1> hey
[16:31] <seg|ars> what do you think of this: http://gwibber.com/screenshots/misc/gwibber-navbar.ogg
[16:35] <djsiegel1> seg|ars: dude, ace
[16:35] <seg|ars> you like it? :-)
[16:35] <djsiegel1> yeah
[16:36] <seg|ars> awesome
[16:36] <djsiegel1> but I don't think you should use colors for the full treeview
[16:36] <djsiegel1> because you have indentation
[16:36] <seg|ars> yeah, I agree. I wasn't sure whether to keep it or not
[16:38] <djsiegel1> seg|ars: can you make the message entry like pidgin's?
[16:39] <seg|ars> where it auto-expands?
[16:39] <djsiegel1> 1/2 lines tall by default with auto-grow?
[16:39] <djsiegel1> yeah, it's a very tall entry by default (what you have now)
[16:39] <djsiegel1> would be nice to make it lighter
[16:39] <seg|ars> yeah
[16:39] <seg|ars> I'm not sure that I want to implement the auto-grow
[16:39] <djsiegel1> yeah, would be a nice bonus
[16:39] <seg|ars> it's a very non-standard behavior for gtk and it creates tons of technical problems in pidgin
[16:40] <djsiegel1> and it's already implemented, you just need to port from pidgin
[16:40] <djsiegel1> it may only be a few lines
[16:40] <djsiegel1> yeah
[16:40] <seg|ars> that's unfortunately not the case
[16:40] <seg|ars> the implementation they have is very specific to their UI
[16:40] <djsiegel1> you are sure?
[16:40] <seg|ars> yeah, I've looked at it before and I've talked to one of the developers about it
[16:40] <djsiegel1> ok
[16:40] <seg|ars> the gwibber team has been discussing that feature for about a year now
[16:41] <seg|ars> and it's just not practical to include it in the program at this time
[16:41] <djsiegel1> right
[16:41] <djsiegel1> good call
[16:41] <seg|ars> personally, I think that upstream gtk needs to provide native support for it in a way that is not a complete hack
[16:41] <djsiegel1> then maybe go with a static, 2-line entry
[16:42] <djsiegel1> yeah upstream gtk needs to move forward
[16:42] <djsiegel1> they limit the imaginations of all app developers
[16:42] <seg|ars> it's really a very bad toolkit.  I made gwibber because I wanted a native alternative to AIR apps, but more and more of the gwibber UI is html
[16:45] <seg|ars> wrt to the static 2-line entry, that's something I'll consider
[16:45] <djsiegel1> ok, cool
[16:45] <djsiegel1> 3 is just large
[16:45] <seg|ars> a lot of users really like having a resizable entry, but I think it creates too many problems
[16:45] <djsiegel1> yeah
[16:45] <seg|ars> at the very least, the default behavior needs to be much better
[16:52] <djsiegel1> ok seg|ars
[16:53] <djsiegel1> seg|ars: this week's paperjam is gwibber
[16:55] <djsiegel1> seg|ars: https://bugs.edge.launchpad.net/hundredpapercuts/+milestone/lucid-round-5
[16:56] <seg|ars> ok
[16:57] <seg|ars> the one that interests me most on that list is the one about gwibber jumping to the top of the page
[16:57] <seg|ars> I'd love to find a good solution to that problem
[16:57] <djsiegel1> seg|ars: can you assign someone on your team to work with me to collect 10 paper cuts?
[16:57] <djsiegel1> if you have any juicy papercuts that you plan to fix for lucid, you can file them, or tell me and I will file and assign to you.
[16:58] <seg|ars> ok
[16:58] <seg|ars> for all of the papercuts relating to account management and creation, you can talk to kenvandine. He's working on our new account UI
[16:59] <seg|ars> I'll help you find other things to fill out the list
[17:02] <djsiegel1> thank you, much appreciated
[17:02] <djsiegel1> the only problem is getting people to hack on gwibber
[17:02] <djsiegel1> since it's not easily hackabale atm
[17:02] <seg|ars> yeah
[17:02] <djsiegel1> I think gwibber is an awesome place for newcomers to learn to write patches
[17:02] <djsiegel1> it's so easy to hack and run
[17:02] <seg|ars> I've made some fixes to the overhaul branch that might make it runnable
[18:24] <vish> djsiegel1: hi... do you want to include this bug > Bug 253452
[18:24] <ubot4> Launchpad bug 253452 in empathy "Confusing error message when ICQ users have different encodings" [Low,Triaged] https://launchpad.net/bugs/253452
[18:25] <djsiegel1> vish: we already have ten for the paper jam
[18:25] <djsiegel1> but I would add it as a paper cut but not schedule it
[18:26] <vish> ok sure
[20:12] <tedg> bratsche: What do you think about this API for fallback to StatusIcon?  http://bazaar.launchpad.net/~ted/indicator-application/fallback/revision/47
[20:13] <tedg> bratsche: I was figuring folks who want to do custom stuff, they can just subclass.
[20:15] <bratsche> tedg: So what would this do exactly?  If you don't have the applet installed then it returns a GtkStatusIcon?
[20:16] <tedg> bratsche: Yeah.
[20:16] <tedg> bratsche: And if it comes back we'd get rid of it.
[20:17] <bratsche> tedg: Cool
[20:18] <tedg> bratsche: I've been debating signal or function, and I think a function makes the most sense.  As the default functionality can be totally removed.
[20:19] <bratsche> So then does the application need to check for this and then set the GtkStatusIcon image and menu stuff itself, or does libappindicator do this internally?
[20:21] <tedg> The idea is that appindicator would do that automatically.
[20:21] <tedg> But, if you wanted to do something different than just having the menu hanging off the icon.
[20:21] <tedg> You could do that yourself by subclassing.
[20:21] <bratsche> Cool.


[00:00] <fta> i wish gwibber had a way to show URLs fully resolved, like the Attachments in the identi.ca web pages
[00:02] <BUGabundo> me too
[00:02] <BUGabundo> I hate short links
[00:03] <BUGabundo> I think I have a bug for that
[00:08] <fta> hm, sometimes, when i want to submit a dent, gwibber just adds a carriage return in the textfield but doesn't send anything
[00:12] <BUGabundo> eheh
[00:12] <BUGabundo> I'm back on 1.2
[00:12] <BUGabundo> I couldn't take it anymore
[00:38] <fta> http://arstechnica.com/tech-policy/news/2009/09/does-less-evening-internet-mean-europeans-lead-better-lives.ars
[01:31] <andv> asac, all-in didnt appear on NEW
[01:31] <andv> asac, plus I received no NEW mail
[01:32] <andv> asac, something went wrong then
[01:32] <andv> going to sleep
[01:32] <andv> cya tomorrow
[08:46]  * asac goes and gets some coffee
[09:45] <asac> ejat: there?
[09:45] <asac> bdrung: hi!
[09:45] <asac> bdrung: saw you got added to the team ... congrats ;)!
[09:53] <asac> bdrung: did your MOTU application work out well?
[10:08] <fta_> asac, aren't MOTU nearly dead? i mean, with the archive reorg in progress
[10:14] <fta_> d'oh! http://www.youtube.com/watch?v=0qqxjO5nr8k&feature=featured
[11:00] <eagles0513875> morning gnomefreak
[11:08] <andv> asac, hi
[11:09] <andv> asac, had a problem with the upload yesterday? :)
[11:26] <asac> andv: no orig
[11:26] <asac> its now done
[11:27] <andv> asac, yeah :)
[11:27] <andv> saw it on new
[11:32] <eagles0513875> hey asac :)
[11:45] <asac> hi eagles0513875
[11:46] <eagles0513875> how goes it asac
[11:48] <asac> pretty good ... still catching up a bit on vacation stuff ;)
[12:23] <gnomefreak> ok how the hell do i get normal gwibber back?
[12:27] <bdrung> asac: thanks. the MOTU application was deferred because they had no quorum
[12:28] <asac> bdrung: during meeting?
[12:28] <asac> hmm
[12:28] <asac> gnomefreak: no way ... just keep using it ;)
[12:29] <gnomefreak> asac: i cant figure out how to send message
 brings you down to next line to type
[12:29] <bdrung> asac: no, before :)
[12:29] <asac> gnomefreak: i dented about that and got an answer
[12:30] <asac> gnomefreak: http://identi.ca/notice/9277389
[12:30] <gnomefreak> thanks lookinhg
[12:30] <asac> http://identi.ca/conversation/9276118#notice-9277389
[12:30] <gnomefreak> I DONT LIKE IT
[12:31] <gnomefreak> asac: i cant move it up
[12:31] <fta2> there's a pref in the menu
[12:32] <gnomefreak> not here there isnt
[12:32] <gnomefreak> at least not in pref
[12:32] <gnomefreak> i have same ui for new as was for old versions
[12:33] <gnomefreak> for pref
[12:33] <fta2> not in pref, just View / Editor
[12:33] <gnomefreak> fta2: i can typw but i cant send it
[12:33] <gnomefreak> s/typw/type
[12:33] <fta2> it's enter, as before
[12:33] <gnomefreak> fta2: brings me down a line in editor
[12:33] <fta2> but sometimes, it just adds a carriage return
[12:33] <fta2> it's a bug
[12:34] <fta2> scroll up, and enter
[12:34] <gnomefreak> same thing
[12:35] <asac> gnomefreak: you can drag it up ... just try a bit more ... its  tiny grab thing like where the separator line is right at bottom
[12:36] <gnomefreak> asac: not here it just brings the text back to editor as if it is not permitted
[12:36] <asac> well then you already have the editor
[12:36] <asac> which was what i didnt have
[12:36] <asac> sending worked for me
[12:36] <gnomefreak> i have editor since i typed in it but no way to send it
[12:37] <fta2> iirc, View / Editor is disabled by default, which is bad
[12:37] <asac> gnomefreak: i hit enter and it works
[12:37] <gnomefreak> i have the editor that part i knew from other releases its sending it that isnt working
[12:38] <asac> fta2: for the searchplugins we actually should add replaces to all lower firefox versions on all firefox branches i think
[12:39] <asac> or we should get rid of the common firefox-addons/searchplugins dir
[12:40] <fta2> asac, or make a dedicated src package
[12:40] <asac> yeah
[12:40] <gnomefreak> cant clear window either let me see if there is an update for it
[12:42] <gnomefreak> bug in apturl too :(
[12:45] <fta2> asac, i like the dedicated source package, so we can add/remove/update searchplugins independently of ff
[12:46] <asac> fta2: technically i agree. problem is that it bears the risk that we miss if upstream changes their default searchplugins
[12:47] <asac> and we are obliged to have them unless we explicitly applied/communicated for a change
[12:47] <asac> wonder if there is a way to add a safety net
[12:47] <asac> like "if we are package that ship default package, verify that the searchplugins in the other package are all the same"
[12:48] <fta2> we can just pull that from trunk, like today
[12:51] <asac> thats not what we do today
[12:51] <asac> we pull them from the branch of the package installed
[12:51] <asac> the package with highest version is supposed to win
[12:51] <asac> but in default install we have the plugins of firefox-3.5 as shipped by upstream unless someone installs firefox-3.7 et al
[12:52] <asac> so i guess we should need to pull them from current default branch
[12:52] <fta2> 3.7 doesnt provide those searchplugins, just a link
[12:52] <asac> as thats where mozilla wants trademark being inforced
[12:53] <asac> fta2: yes. so i think what we should do is provide a firefox-searchplugins package which is produced from the same package where we have the meta package
[12:53] <asac> does that sound about right?
[12:53] <asac> and everything depends on firefox-searchplugins in turn
[12:53] <fta2> yes
[12:54] <asac> ok so no standalone source package
[12:54] <asac> just an unversioned package for the current METAPACKAGE thing
[12:54] <asac> at some point we probably want to assemble debian/control on-the-fly ;)
[12:54] <asac> hehe
[12:58] <asac> jdstrand: so at best the apparmore profile feature would become independent from the firefox version by some template magic
[12:58] <asac> i would like to able to just land it in firefox-(3.0?)/3.5/3.6/3.7
[12:59] <asac> jdstrand: ok ... so i think the general 3.* and 1.9* things can be kept that way
[12:59] <asac> but the firefox-3.5.* would probably be better replaced during build with<EMAIL_ADDRESS>or something
[13:00] <asac> if it makes things cleaner (as we use templating anyway) we could also replace the 1.9* and 3.* with proper template things
[13:01] <jdstrand> asac: I'm cool with that conceptually, but will it make it too easy to not verify it? I intentionally did it this way so someone would need to look at it. ie, 3.0's profile didn't work with 3.5
[13:01] <jdstrand> it mostly worked, but needed tweaking
[13:04] <asac> jdstrand: yes. but we usually have those branches right from day zero where 3.5 == 3.6 for instance
[13:04] <asac> jdstrand: so its more a continous process anyway
[13:04] <asac> so assume we have it for firefxo-3.6 and then 3.7 got created the files would be the same anyway without verification needed
[13:04] <asac> only while upstream changes we need to adjust
[13:04] <asac> so i dont think it provides a safety net for us
[13:05] <jdstrand> asac: if that works better with your process then I'll update it
[13:05] <asac> would be precious. let me check if i can see something else
[13:12] <asac> jdstrand: not sure if i am just confused, but isnt
[13:12] <asac> +        if [ ! -e "$APP_CONFFILE" ]; then
[13:12] <asac> +            ln -sf $APP_CONFFILE $APP_DISABLE
[13:12] <asac> wrong?
[13:13] <asac> e.g. APP_CONFFILE does not exist => then we link it?
[13:13] <jdstrand> it looks wrong but isn't
[13:13] <asac> shouldnt it be the other way around?
[13:13] <jdstrand> it is based on https://wiki.ubuntu.com/ApparmorProfileMigration
[13:13] <jdstrand> the idea is this happens in preinst, and we know our package supplies the file after unpacking
[13:14] <jdstrand> so yes it dangles for a second, but then is resolved at unpack
[13:15] <jdstrand> keep in mind ApparmorProfileMigration is mostly geard for files moving from apparmor-profiles to a package which provides its own profile, but many of the ideas are the same
[13:16] <asac> you think we can use $0 in the pre/post stuff to prevent templating there?
[13:16] <asac> e.g. for firefox-3.5 etc.
[13:16] <asac> ?
[13:18] <asac> hmm postinst.in is alrady a template. so i guess we are fine with making .in out of everything
[13:19] <jdstrand> asac: I should be able to do something with preinst
[13:19] <jdstrand> asac: I'll work on making it all generalized
[13:20] <asac> jdstrand: thanks. i dont like all the maintainer script stuff, but if its really needed then i am fine with the changes once they are generic
[13:22] <jdstrand> asac: the idea is to protect the user. if they upgrade from jaunty to karmic, the profile is disabled. if they already have a profile they wrote or they upgrade from karmic to karmic-security we don't want to automatically disable it again
[13:23] <jdstrand> that said, I'm confident I can generalize it
[13:25] <asac> jdstrand: yes. i figured that and accepted it ;)
[13:25] <asac> all fine
[13:26] <asac> jdstrand: you might want to investigate at some point if you can do some debhelper magic to automatically add the right snippets
[13:26] <asac> so you dont need to duplicate all the things in all maintainer scripts ;)
[13:26] <asac> but not karmic topic of course
[13:26] <asac> dh_installapparmor ;)
[13:26] <asac> or something
[13:27] <jdstrand> yeah, the problem is they tend to be different enough for each package... but it has been something I've thought about
[13:27] <jdstrand> thanks :)
[13:28] <asac> no problem ;) /me likes giving easy advices for not-so-easy things :)
[13:30] <gnomefreak> !grub2
[13:46] <asac> jdstrand: you think i should wait for the karmic ppa security upload for your new merge request?
[13:47] <asac> i think release is still 1-2 weeks away so we can wait a bit if you would like to get that into the first .14 upload
[13:48] <jdstrand> asac: well, I'd personally like it sooner than later, but I'll leave ff release management up to you :)
[13:48] <asac> jdstrand: we only ship profile in firefox package right? not xulrunner?
[13:48] <jdstrand> asac: correct
[13:48] <asac> jdstrand: when do you think can you do the generalization?
[13:48] <jdstrand> asac: I'm building a package with my changes right now
[13:48] <jdstrand> so... soon?
[13:48] <jdstrand> :)
[13:50] <asac> great
[13:50] <asac> i will wait a bit then
[13:50] <jdstrand> asac: do you have any objections to me adding something to the apport hook?
[13:51] <jdstrand> asac: I did it with evince and it has worked out fantastically
[13:51] <jdstrand> (is that a word?)
[13:53] <asac> jdstrand: i am happy to retrieve apport hook love
[13:53] <asac> ;)
[13:53] <asac> of course depends on what you want to append ;)
[13:53] <jdstrand> cool, I get that going then too
[13:53] <asac> no root passwords for instance :)
[13:53] <jdstrand> heh
[13:54] <asac> in general who last touched the hook owns it until someone else touches it ;)
[13:54] <jdstrand> eek
[13:54] <jdstrand> that is a big committment!
[13:55] <asac> not so big
[13:55] <asac> just a joke ;)
[13:55] <jdstrand> :)
[14:18] <asac> fta2: i think there are localized search plugins in the locale hg tree ... which are not in the .xpi translation packages we ship
[16:09] <jdstrand> asac: ok, I committed r459 for apparmor/firefox
[16:10] <jdstrand> asac: it should be generalized completely
[16:10] <jdstrand> asac: it also will add apparmor stuff to the apport report if the profile is not disabled
[16:11] <jdstrand> asac: https://code.launchpad.net/~jdstrand/firefox/firefox-3.5-apparmor/+merge/11061
[16:12] <asac> let me check
[16:12] <jdstrand> asac: I think I did all the LP right this time too, so the 'Review Diff' should now be accurate
[16:12] <asac> yeah saw that the other is properly marked as superseded ... well done ;)
[16:12] <jdstrand> heh
[16:12] <asac> jdstrand: have you tested the apport hook?
[16:13] <asac> this also smeels like something that could be factored into apport general package i think
[16:13] <jdstrand> asac: yes, works great (both when disabled and enabled)
[16:13] <asac> we have similar generic functions for wifi etc in there now
[16:13] <asac> jdstrand: thx for confirming
[16:13] <jdstrand> asac: yeah, I thought of that too, but too late for FF
[16:13] <jdstrand> (on my todo)
[16:13] <asac> imo thats not FF relevant ;)
[16:14] <asac> but thats just me ;)
[16:14] <jdstrand> I'll talk to pitti when I have more time, and if I can get to it, I will and will update this packaging
[16:14] <asac> the feature is there ... just not in the central apport hook library ;)
[16:14]  * jdstrand nods
[16:15] <asac> jdstrand: no problem
[16:16] <asac> [ Jamie Strandboge<EMAIL_ADDRESS>]  -> wrong (i will fix it during merge)
[16:16] <asac> ;)
[16:17] <jdstrand> asac: fyi, I compared all the old maintainer scripts with the newly generated ones and they're the same
[16:17] <jdstrand> asac: re changelog> oops! :)
[16:17] <jdstrand> thanks
[16:19] <jdstrand> asac: fyi, I fixed the typo in debian/changelog in r460
[16:20] <asac> jdstrand: there is also DEBIAN_NAME_OTHER ... for abrowser ... not sure if we can make that work easily ... without copying the full block
[16:20] <jdstrand> asac: oh, I forgot-- you probably should wait to upload until the next kernel is uploaded
[16:20] <asac> jdstrand: what will happen with old kernels?
[16:21] <jdstrand> asac: as it is disabled by default, nothing, but if someone enables it, it won't load cause I use PUx for evince
[16:22] <asac> jdstrand: there is no new dependency added
[16:22] <asac> is that because its installed by default?
[16:22] <asac> since when are the binaries used available?
[16:22] <jdstrand> asac: not a huge issue-- the patches are committed to the kernel and just awaiting upload
[16:22] <asac> like aa-... ?
[16:23] <jdstrand> asac: this will work fine without apparmor installed, so no Depends or Recommends. sometimes I add a Suggests, but didn't here
[16:23] <jdstrand> (tried to keep the packaging changes to a minimum)
[16:24] <asac> jdstrand: but it calls apparmor_parser and aa-status without checking that the binaries actually exist
[16:24] <asac> hmm ... but only if APP_PROFILE exists for postinst
[16:24] <asac> jdstrand: point is that we build the .head branch everywhere: hardy - karmic
[16:25] <asac> so if possible it would not break there ;)
[16:25] <asac> ok seems ok
[16:25] <jdstrand> asac: well, 'aa-status' will fail if it isn't around
[16:25] <asac> do you see anything that might break?
[16:25] <asac> yeah true
[16:25] <jdstrand> and I 2>/dev/null it
[16:26] <micahg> asac: I'm reminding you about the fixed-3.5.3 and fixed-3.0.14 tags
[16:26] <jdstrand> asac: this is the same recipe I use all over the place
[16:26] <micahg> I saw the branches committed for the next ff release
[16:26] <asac> micahg: huh ;)
[16:26] <jdstrand> asac: I have tested it here and am comfortable with it
[16:26] <asac> thanks
[16:26] <asac> micahg: that was last minute ;9
[16:26] <jdstrand> asac: I'll of course fix anything that breaks
[16:26] <asac> micahg: though i already uploaded xulrunner ;)
[16:26] <asac> but thats ok i guess
[16:26] <asac> next time i should remember it better
[16:27] <asac> jdstrand: ok. i think its ok. lets merge it and see if the daily mob shouts ;)
[16:27] <jdstrand> heh
[16:28] <asac> jdstrand: but we need to fix abrowser later
[16:28] <asac> does the name need to match the binary? or just this: /usr/lib/<EMAIL_ADDRESS>{ ?
[16:28] <asac> oh its referring to firefox
[16:28] <jdstrand> /usr/lib/<EMAIL_ADDRESS>[16:28] <asac> so i guess only question is if usr.bin.firefox.apparmor
[16:28] <asac> has any meaing
[16:28] <asac> but i guess not
[16:29] <asac> ok great
[16:29] <asac> lets go for it
[16:29] <jdstrand> whatever uses that binary is confined
[16:30] <asac> jdstrand: ok merged ... i will check if its easy to just pull that over to 3.7 and 3.6 branch and if not i will poke you ;M)
[16:30] <jdstrand> asac: if it makes sense to rename the profile to simply apparmor.profile, we can do that.
[16:30] <jdstrand> asac: cool, I will be more than happy to fix anything wrt this
[16:30] <jdstrand> asac: thanks for the review and merge! :)
[16:31] <asac> micahg: bug 236853 ... is that really fixed by ffox? not by nss?
[16:31]  * asac checks upstream bug
[16:32] <asac> ok its fixed in ffox/xul
[16:32] <asac> thx
[16:33] <micahg> I just followed whatever they said upstream
[16:36] <asac> micahg: documented. thanks a bunch for that ;)
[16:36] <asac> micahg: you were right.
[16:43] <micahg> are they actually releasing 3.0.14 or did it go t oRC?
[16:48] <micahg> asac: I made my patch better, but now it fails to build for bug 66015
[16:48] <micahg> http://launchpadlibrarian.net/31218684/buildlog_ubuntu-jaunty-amd64.xulrunner-1.9.1_<IP_ADDRESS>%2Bnobinonly-0ubuntu<IP_ADDRESS>~ppa10_FAILEDTOBUILD.txt.gz
[16:48] <asac> micahg: beta
[16:48] <micahg> ok
[16:48] <asac> usually it goes 1-2 weeks before release to beta channels
[16:48] <asac> thats when i try to upload stuff to PPA
[16:48] <asac> if all goes well they dont respin and the same binary will be the release
[16:49] <asac> jdstrand: remember to mark your branch as merged (if launchpad didnt do that yet)
[16:51] <jdstrand> asac: done
[16:52] <micahg> asac, here's the new patch http://pastebin.com/f3982e877
[16:53] <micahg> Apparently, I don't have PRUniChar loaded
[16:55] <asac> micahg: but thats still the same approach
[16:55] <asac> how about the idea replacing _ with - (or vice versa)
[16:55] <asac> and then checking whether a dictionary with that name is alread in the mDictionaries map?
[16:55] <asac> btw its PRUnichar
[16:55] <micahg> ah
[16:56] <micahg> why not stop it at the source though
[16:56] <micahg> prevent the file from loading
[16:56] <asac> the file isnt loaded if you dont put it in the dictionarie
[16:56] <micahg> my original patch actually worked
[16:57] <micahg> ok
[16:57] <micahg> why not use a simpler patch though?
[16:57] <asac> because its fragile
[16:57] <asac> nobody knows what is wanted
[16:57] <micahg> why?
[16:57] <asac> _ or -
[16:57] <micahg> ah
[16:57] <asac> so better safe than sorry
[16:57] <asac> and allow both
[16:57] <micahg> I can add a commet
[16:57] <micahg> oh
[16:58] <micahg> that's what you mean
[16:58] <micahg> I looked at the upstream binaries
[16:58] <micahg> and they ship - in the files
[16:58] <micahg> it seems to be a mozilla thing
[16:58] <asac> just allow both variants, but just normalize the key
[16:58] <asac> (e.g. dict)
[16:58] <asac> the other alternative is to resolve an eventual link first
[16:58] <micahg> well
[16:59] <asac> like if file == link -> resolve ... then use leafName, normalize like discussed (e.g. replace _ by -)
[16:59] <micahg> what I'm wondering is why it doesn't display the whole name for the _ dicts but does for -
[16:59] <asac> micahg: that logic was at the other place
[16:59] <micahg> ah
[16:59] <asac> what bug id was it again?
[16:59] <micahg> bug 66015
[16:59] <asac> the other patch touched the source that assembles the name
[17:00] <micahg> would that type of patch be worthy of upstreaming then?
[17:00] <asac> content/global/inlineSpellCheckUI.js
[17:00] <asac> micahg: http://launchpadlibrarian.net/31020349/inlineSpellCheckUI.patch shows that it only shows the full name for "-" most likely
[17:00] <asac> at least thats what is processed properly
[17:00] <asac> (without that patch)
[17:01] <micahg> ok
[17:01] <asac> micahg: what are the links for us?
[17:01] <micahg> so I'll work on it tongiht
[17:01] <asac> the _ or the -?
[17:01] <micahg> -
[17:01] <micahg> _ is the normal file
[17:01] <asac> - are links to the _ files?
[17:01] <asac> hmm
[17:01] <micahg> apparently the ISO standard is _
[17:01] <micahg> but mozilla likes -
[17:01] <asac> ok so what we want is to use the dict key normalization to use "-" (because thats what mozilla uses)
[17:01] <micahg> ok
[17:02] <micahg> I have to leave for work soon
[17:02] <asac> and then we want to first split with "-"
[17:02] <micahg> so I'll work on this tonight
[17:02] <asac> so i think in best case we dont need to touch the .js
[17:02] <asac> yeah
[17:02] <asac> i think you dont need to resolve the link
[17:02] <asac> though upstream might want us to do that
[17:03] <asac> but lets first try to just normalize to use "-" as the key
[17:03] <asac> and check that for (var i = 0; i < list.length; i ++) {
[17:03] <micahg> ok
[17:03] <asac> list here is that key
[17:03] <asac> but i think its right then
[17:03] <asac> as long as we normalize to use -
[17:03] <micahg> ok
[17:03] <micahg> BTW, is ABrowser the official branded name of the unbranded browser?
[17:04] <micahg> we have bug 413076
[17:04] <asac> its our unbranded browser name
[17:04] <asac> there is no official unbranded branding ;)
[17:04] <micahg> so, can we change the menu to ABrowser vs A Web Browser so it doesn't seem so weird on other languages?
[17:06] <asac> abrowser was ment to be short for "A Web Browser"
[17:06] <asac> it was considered rougue to just use "Web Browser"
[17:06] <asac> because other browsers would then want that name too
[17:06] <micahg> yes, but if it's like that, it would seem that it should be localized in other langauges
[17:06] <asac> i will think about it
[17:07] <asac> not if "A Web Browser" is considered a brand name
[17:07] <asac> but well
[17:07] <micahg> oh
[17:07] <micahg> oops
[17:07] <asac> ;)
[17:07] <micahg> got it mixed up
[17:07] <micahg> it is translating it
[17:07] <asac> yeah
[17:07] <micahg> but only patially
[17:07] <asac> so technically its right
[17:07] <micahg> *partially
[17:07] <asac> question is if the bug has a point about confusion. i dont think so for now
[17:07] <asac> but have to think more
[17:08] <micahg> ok
[17:08] <micahg> ok to mark as triaged then?
[17:08] <asac> yes assign it to me and triaged stating this is pending decision
[17:09] <asac> you can also project that we probably won't go for just "WebBrowser"
[17:09] <asac> Rather "A Browser" ;)
[17:09] <asac> given the rational against taking Web Browser from above
[17:09] <micahg> I was thinking without the space and have it be an actually name - ABrowser
[17:09] <asac> Yeah
[17:10] <asac> but firefox == "Firefox Web Browser" .... abrowser = "A Web Browser" or "ABrowser Web Browser"
[17:10] <asac> which would be odd too ;)
[17:10]  * micahg likes the last one actually
[17:10] <micahg> ABrowser web browser
[17:10] <micahg> then the description can be localized
[17:10] <micahg> but the name remains
[17:10] <asac> we intentionally picked the most generic name so we wont need to enforce any trademarks on it as its probably not trademarkable on its own
[17:11] <asac> yeah
[17:11] <asac> but ABrowser Web Browser is double ;)
[17:12] <micahg> do you think it's worth throwing up on brainstorm?
[17:12] <asac> definitly not
[17:12] <asac> thtough branding discussion in the wild and you get a fully raged rant
[17:12] <asac> everybody in the end being unhappy
[17:12] <micahg> ah, right
[17:12]  * micahg remembers the Shiretoko rants
[17:34] <asac> micahg: fyi: https://developer.mozilla.org/en/XPCOM/Strings
[17:34] <asac> Mozilla internal string guide
[17:35] <asac> https://developer.mozilla.org/en/String_Quick_Reference
[17:47]  * mac_v seems nothing rogue about using "Web Browser"
[17:47] <mac_v> *sees
[18:12] <asac> mac_v: we would claim a generic name that other browsers would want to use if it was open for discussion
[18:12] <asac> so everyone agrees to not use such a generic name
[18:39] <mac_v> hmm... too bad , now we have to confuse the user ;p
[18:49] <micahg> mac_v: ??
[18:50] <mac_v> micahg: the "AWeb Browser" , i was replying to asac ;)
[18:50] <micahg> sorry, I must've caught the last line of that
[19:49] <fta> asac, http://launchpadlibrarian.net/31252914/buildlog_ubuntu-intrepid-i386.firefox-3.7_3.7~a1~hg20090902r32157%2Bnobinonly-0ubuntu1~umd1~intrepid_FAILEDTOBUILD.txt.gz
[19:54] <andv> asac, all-in-one accepted
[19:55] <andv> asac, I pinged a friend, who is ftp-assistant
[19:55] <andv> ;)
[21:55] <sveinung> andv and asac: thanks a lot for your help and sponsorship getting all-in-one-sidebar into Debian
[21:55] <andv> ;)
[21:56] <andv> sveinung, np
[21:56] <sveinung> :)
[21:56] <andv> sveinung, let me know when there will be a new upstream release
[21:57] <sveinung> andv: sure
[21:57] <andv> sveinung, I gonna sponsor the package from now on
[22:07] <andv> sveinung, do you know how Debian BTS work?
[22:08] <sveinung> andv: yes, at least part of it
[22:08] <andv> ok, both me and you will receive bug mails
[22:08] <sveinung> ok
[22:08] <andv> so if you don't know what to do, ping me
[22:08] <sveinung> sure


[01:37] <squish102> https://github.com/JamieKnight/dash-hue
[01:38] <squish102> to get that working, I tried a "apt-get install node.js npm"
[01:38] <squish102> and then I get an error when doing "npm install"
[01:38] <squish102> after a git clone
[01:43] <squish102> https://bin.snyman.info/mmmw29hu
[02:57] <superfly> squish102: install nodejs-legacy
[02:58] <superfly> actually, I don't think that's going to solve your error, but it's often useful anyway (due to conflicts between packaging and upstream)
[02:58] <superfly> squish102: it looks like you need the development libraries for pcap installed
[02:59] <superfly> squish102: sudo apt install libpcap-dev
[04:11] <squish102> Thanks superfly, that looks to have gotten me past that error
[04:15] <squish102> the libpcap-dev
[04:15] <squish102> I had also done the nodejs-legacy earlier (and i needed that too)
[04:20] <superfly> squish102: the compiler error said it was looking for a header file and couldn't find it. Classic "you don't have the -dev package installed" symptom
[05:46] <superfly> Night Kilos
[05:47] <Kilos> night superfly
[05:47] <Kilos> rest well
[05:47] <Kilos> morning everyone else
[06:41] <nsnzero> morning all
[07:57] <smile> Hi Kilos
[07:57] <Kilos> hi smile
[07:58] <smile> How're you feeling?
[08:00]  * smile hugs Kilos
[08:00] <Kilos> feeling with my hands still
[08:00] <Kilos> hehe
[08:00] <Kilos> ty for the hug
[09:14] <smile> you're welcome
[09:14] <smile> what did you do to your hands, Kilos?
[10:10] <inetpro> good mornings
[10:11] <inetpro> oops, it's lunchtime already?
[10:19] <Kilos> feel
[10:48] <inetpro> good sign if you still have feeling in your hands oom Kilos
[11:20] <Kilos> hahaha
[11:20] <Kilos> my feet feel as well when i step on dubbeltjies
[11:21] <Kilos> spending lots of time digging their bulbs out so next year prob is less
[11:21] <Kilos> and putting all seeds on braai place so they can be cremated
[12:23] <Kilos> wb hibana
[12:24] <Kilos> work hard sir
[13:22] <paddatrapper> Well.... Today has been interesting. Managed to fry all the electrical systems in my dad's bakkie. (wired the terminals of the battery the wrong way round for a few seconds)...
[13:23] <Kilos> oh my
[13:24] <paddatrapper> And all the fuses were the wrong values, so they were of no use
[13:24] <Kilos> there is a + and - on the battery
[13:24] <Kilos> and connectors different sizes
[13:24] <paddatrapper> Which I noticed _after_ the sparks flew
[13:24] <Kilos> how you managed to do that
[13:24] <Kilos> eish
[13:25] <Kilos> now you gotta become a sparky as well
[13:26] <paddatrapper> It still runs, luckily and front lights work, but dash, indicators, all cab stuff and, judging by my dad's face, the alternator are all fried
[13:35] <inetpro> hiho, hiho it's home we go
[14:15] <hibana> goodbye
[14:26] <Kilos> ouch paddatrapper
[14:27] <Kilos> later inetpro
[15:08] <inetpro> Kilos: waar gaan jy?
[15:52] <Kilos> here
[15:53] <Kilos> you went home man
[16:24] <Kilos> hi poppingtonic nsnzero
[16:54] <nsnzero> hi Kilos
[17:31] <nsnzero> evening all
[17:48] <nsnzero> what are the good icon set for ubuntu ?
[18:03] <inetpro> Kilos: are you ok?
[18:04] <nsnzero> hi inetpro
[18:04] <inetpro> hi nsnzero
[18:23] <smile> hi inetpro and nsnzero :)
[18:23] <inetpro> eh
[18:24] <smile> inetpro: you surprised by seeing me? :p
[18:24] <smile> the serial killer you sent at me didn't do its job very well then
[18:24] <inetpro> ai!
[18:25] <smile> is he still out there waiting for me? :o
[18:26] <inetpro> better be on the lookout
[18:26] <smile> yeah, figured that out already
[18:27] <smile> But I'll have to leave my house early in the morning to go working
[18:27] <smile> So no more hiding then
[18:28] <inetpro> no worries smile, I called him to stop, now that you figured the plan
[18:28] <smile> it became to risky, I understand
[18:28] <smile> * too
[18:29] <inetpro> keep smiling sir
[18:30] <smile> I'll try :)
[18:30] <smile> Otherwise I'll have to change my nickname
[18:31] <smile> inetpro: what did you do today?
[18:32] <nsnzero> hi smile
[18:32] <smile> hi nsnzero, I'm going to grab a bite and come back after that :)
[18:33] <nsnzero> still using serial inetpro -> its slow ;)
[18:39] <smile> serial connections are slow by definition :)
[18:39] <smile> that's why they've invented parallel connections :P
[18:42] <nsnzero> on the contrary  - usb is serial smile
[18:43] <nsnzero> parallel can be defined as many serial connections
[18:43] <smile> nsnzero: I googled serial vs parallel, and you're right :) I'll admit I was wrong - https://www.howtogeek.com/171947/why-is-serial-data-transmission-faster-than-parallel-data-transmission/
[18:44] <smile> "Serial transmission is slower than parallel transmission given the same signal frequency." -> that's what I thought
[18:49] <nsnzero> i dabble in electronics
[18:51] <nsnzero> i have a folder with lots of linked files how do i copy it and preserve the links ?
[19:41] <theblazehen> maaz tell nsnzero look at rsync, and how it get work with links. One of the ways must work for you
[19:41] <Maaz> theblazehen: Okay, I'll tell nsnzero on freenode
[20:40] <smile> Good night everyone
[20:43] <Kilos> night all. sleep tight


[04:34] <indeedwatson> I just installed 20.10 on an old laptop and it's been in the initial lubuntu logo for 20 minutes. Any ideas before I try another distro?
[04:35] <tomreyn> hit escape, see what happens
[04:35] <tomreyn> or reboot, and hit escape earlier, and select failsafe graphics from the grub menu
[04:35] <tomreyn> of course, you should also have verified your downloaded .iso file, and the the installation media you wrote from it.
[05:01] <indeedwatson> i pressed escape and i had two options to boot, both named the same. The second booted fine, but if I reboot and just let it run it gets stuck on "powered by lubuntu" again
[05:10] <tomreyn> indeedwatson: if you run   journalctl -b -1 | nc termbin.com 9999    this will upload your log from the failed boot to termbin.com , a pastebin-like website, so that you can share it.
 i paired a bluetooth headset with lubuntu and one day it doesnt get paired automatically also i cannot see my headset in list of available devices in bluedevil wizard app. i checked with my other devices the bluetooth device is shown there but its not shown in bluedevil wizard. i tried uninstalling the app and reinstalling also but it didnt work
 someone please help me with this (re @anonid: i paired a bluetooth headset with lubuntu and one day it doesnt get paired automatically also i cannot see my headset in list of available devices in bluedevil wizard app. i checked with my other devices the bluetooth device is shown there but its not shown in bluedevil wizard. i tried uninstalling the app and reinstalling also but it didnt work. what should i do now.
 version lubuntu 20.04.1 lts x86_64
 kernal 5.4.0-58 generic)
[12:39] <simon> work?
[12:41] <simon> work.
[13:07] <inpanic> can someone please help me?
[13:08] <indeedwatson> i couldn't solve my problem last night, after a fresh install my laptop gets stuck on "powered by lubuntu". If I press escape as it's booting and select the second option (even tho they're both named the same), it boots; but I need it to just boot regularly without having to do that
[13:09] <indeedwatson> would be helpful to know what that second option changes, but they're named exactly the same
[13:57] <KGIII> You could look at /etc/default/grub to figure it out, though I'd personally use the GUI tool grub-customizer.
[14:10] <indeedwatson> what should I look at? The only thing that seems relevant is maybe GRUB_DEFAULT=0, if I change that to 1 would it select the 2nd option by default instead?
[14:20] <indeedwatson> mm still stuck. I guess xubuntu it is
[14:22] <KGIII> It's much easier to use grub-customizer. Your favorite search engine will show you how to get it installed and how to use it. It's not difficult.
[14:23] <indeedwatson> there's no internet on it, does that come by default?
[14:34] <indeedwatson> ok got a lan cable. Turns out the 2nd option is recovery mode. Obviously I don't want to boot into that by default. Any other ideas?
[14:41] <KGIII> Do you have multiple kernels listed?
[14:41] <indeedwatson> no, it's the same kernel in both
[14:42] <KGIII> And you're just now connecting it to the internet?
[14:42] <indeedwatson> im guessing it's gpu drivers
[14:42] <indeedwatson> yeah
[14:42] <indeedwatson> but the package manager program decided not to launch anymore
[14:42] <KGIII> Oh, then just start with 'sudo apt get update && sudo apt upgrade -y' from the terminal.
[14:43] <indeedwatson> alright
[14:45] <KGIII> Which version of Lubuntu is this, by the way?
[14:46] <indeedwatson> 20.10
[14:48] <KGIII> Thanks. When it's done updating, try rebooting normally. We can go from there. I should warn you that I'm still on 18.04 until the first part of next year. There are others here more qualified but we've all got different schedules.
[14:51] <indeedwatson> is there a way to know for sure if this laptop has a wifi card? (from within lubuntu)
[14:51] <indeedwatson> I don't know the laptop model
[14:57] <KGIII> Check 'ifconfig -a'.
[14:59] <kc2bez> I am not sure that net-tools is installed anymore.
[14:59] <KGIII> Ah, see? LOL They really need someone with something newer than 18.04.
[15:00] <KGIII> I am not making the switch until early next year - 2nd week of January.
[15:00] <kc2bez> `lspci -nnk` will report pci devices
[15:01] <kc2bez> I don't have a laptop handy but you can likely refine that output with `lspci -nnk | grep Ethernet`
[15:01] <KGIII> You catching this indeedwatson?
[15:06] <indeedwatson> i installed net-tools, i set up a lan cable for now
[15:06] <indeedwatson> what do i look for in the outpot of ifconfig -a?
[15:09] <KGIII> How many devices do you have listed?
[15:09] <indeedwatson> if there's no wlan it means there's no wifi card? There's only enp0s4 and lo
[15:09] <apt-ghetto> It is maybe easier to start with `ip link` to see, whether a wireless interface exists or not
[15:09]  * KGIII points up - listen to them
[15:09] <indeedwatson> same two with that command
[15:11] <apt-ghetto> Try `lspci -nnk | grep -i net -A2`
[15:13] <indeedwatson> well i'm rebooting normally after the upgrade and it's stuck in "powered by lubuntu" again. Only thing I can think of is boot back into safe mode and see what the package manager suggests in terms of gpu drivers
[15:13] <apt-ghetto> If you see the plymouth splash screen ("powered by lubuntu"), then press the ESC key
[15:14] <apt-ghetto> You should see some messages and maybe a reason, why it is blocked
[15:18] <indeedwatson> i'll do that if this fails. I'm in the package manager rn, how do i figure out what to install in terms of video drivers?
[15:21] <apt-ghetto> You should have the "correct" open-source driver for your GPU. If you have some problems with the open-source driver, you have to check the hardware and find out, what is the correct proprietary driver
[15:22] <apt-ghetto> Often, you have two different GPUs, one in the processor and one on a dedicated graphic card
[15:22] <apt-ghetto> Usually, only the GPU on the processor is used
[15:22] <indeedwatson> i don't think this has a dGPU
[15:22] <indeedwatson> I'm only assuming it's a driver issue
[15:25] <indeedwatson> apt-ghetto nothing happens if i press Esc in the powered by lubuntu screen
[15:29] <apt-ghetto> That is not good and quite unusual. In this case reboot into the working entry (recovery) and please upload the system log with `journalctl -b -1 | pastebinit` and share the link here. But first you should check, that your logfile does not contain any "sensitive" infos
[15:32] <indeedwatson> i think i'm going with xubuntu, i'm setting this laptop for someone else and if i'm having so much trouble already it might not be the best to stick to lubuntu. However you've been helpful, so if xubuntu presents similar difficulties I'll go back to lubuntu and keep troubleshooting
 hi guys
 I'm trying to launch Lutris but I get this error
 Unsupported locale setting. Fix your locales
 then I tried to configure my locals using the command
 sudo dpkg-reconfigure locales
 and this is the output I'm getting
 https://paste.ubuntu.com/p/ZM5g3KfxCM/
 I can't fix my locals
 But I have to confess that yesterday I removed LibreOffice-core
 I fear that I removed a file or two too much 😬
 it sounds like you need to regen your locales.  Or generate the specific locale errors you're getting
 (locale failures typically aren't caused by removal of libreoffice)
 so sudo dpkg-reconfigure locales
 is something else? (re @Michaël: then I tried to configure my locals using the command
 sudo dpkg-reconfigure locales)
 USUALLY you need to run sudo locale-gen or sudo locale-gen [YOUR LOCALE HERE]
 and you've got two locales currently
 so you need to make sure both are generated
 yes
 I wanted my terminal and GUI in English in case something went wrong
 I don't know always how to translate something to English (re @teward001: and you've got two locales currently)
 well then you may want to double check that both locales're generated
 sudo locale-gen en_US.UTF-8 and sudo locale-gen nl_BE.UTF-8 (becuase the NL locale is not generated by the straight localegen you're using)
 so sudo locale-gen
 finished without errors
 I'll try those 2 (re @teward001: sudo locale-gen en_US.UTF-8 and sudo locale-gen nl_BE.UTF-8 (becuase the NL locale is not generated by the straight localegen you're using))
 so
 sudo locale-gen en_US.UTF-8
 and
 sudo locale-gen nl_BE.UTF-8
 both completed without errors
 and yet Lutris complains with the same error ... (re @Michaël: hi guys
 I'm trying to launch Lutris but I get this error
 Unsupported locale setting. Fix your locales)
[21:36] <wxl> does `locale -a | egrep '(en_US|nl_BE).UTF-8'` return both?
[21:37] <wxl> er wait that's not right
[21:37] <wxl> does `locale -a | egrep '(en_US|nl_BE)'` return both?
 *gives wxl a second "You Failed" ribbon*
 first was for not posting the original one here ;)
[21:38] <wxl> wow it's remarkable how many of those you have
[21:40] <wxl> LC_ALL being unset seems problematic
 both (re @lubuntu_bot: (irc) <wxl> does `locale -a | egrep '(en_US|nl_BE)'` return both?)
 it might just be an error with lutris too
[21:44] <wxl> see if running it like `LC_ALL=C lutris` doesn't help
[21:44] <wxl> but yes quite possibly an issue with lutris
 no probs then :) (re @lubuntu_bot: (irc) <wxl> see if running it like `LC_ALL=C lutris` doesn't help)
[21:44] <wxl> afaik that doesn't exist in the ubuntu repositories outside of the development version, so your best place for support would be via lutris
[21:45] <wxl> wait, that worked????
 yes :) (re @lubuntu_bot: (irc) <wxl> wait, that worked????)
[21:45] <wxl> ok so you can add `export LC_ALL=C` to .bashrc or the like
[21:46] <wxl> it's possible that may cause problems elsewhere
[21:46] <wxl> (because that would set it globally)
 in that case
 I'll stick with LC_ALL=C lutris
 Thank you very much :)
[21:47] <wxl> if you want it to set that only when lutris runs, find the desktop entry (probably in /usr/share/applications, but perhaps in $HOME/.share/applications) and edit the Exec line
 I'll try that
 thank you :) (re @lubuntu_bot: (irc) <wxl> if you want it to set that only when lutris runs, find the desktop entry (probably in /usr/share/applications, but perhaps in $HOME/.share/applications) and edit the Exec line)
[21:48] <wxl> yeppers


[05:52] <hikiko> hi
[05:53] <TheMuso> Hey hikiko.
[05:54] <hikiko> hi TheMuso
[09:01] <seb128> good morning desktopers
[09:01] <willcooke> morning seb128
[09:01] <willcooke> How are you feeling today?
[09:01] <seb128> hey willcooke! I had a good night, feeling less tired/feverish which is good
[09:01] <seb128> still having the cold annoyance, sneezing, etc
[09:02] <seb128> but it's already an improvement :-)
[09:02] <willcooke> :)
[09:03] <Laney> morning
[09:03] <seb128> hey Laney, how are you?
[09:03] <Laney> hey seb128
[09:03] <Laney> good thanks!
[09:03] <Laney> it got really foggy last night
[09:03] <Laney> was cool
[09:04] <Laney> how about you?
[09:04] <seb128> cool like "can't find the road anymore so I'm biking in the middle of nowhere"? ;-)
[09:05] <seb128> I'm fine, had a good night sleep and I'm feeling a bit better today!
[09:05] <flexiondotorg> Morning seb128 Laney willcooke hikiko_
[09:05] <seb128> hey flexiondotorg
[09:05] <willcooke> hey flexiondotorg
[09:06] <flexiondotorg> Stepping out for a bit. Back in a hour...
[09:08] <davmor2> Morning all
[09:12] <flexiondotorg> davmor2 o/
[09:13] <TheMuso> Hey folks.
[09:13] <willcooke> evening TheMuso
[09:14] <TheMuso> seb128: Could you do me a favour? I've got MIRs filed for espeak-ng and pcaudiolib, bug 1656741 and bug 1656742 respecitvely. COuld you please add them to the desktop-packagers team for bug mail?  Thankfull a southerly buster came through and the evening is a pleasant one.
[09:38] <TheMuso> thankfully*
[09:42] <Laney> TheMuso: I read soemthing about a record run of high temperature
[09:45] <TheMuso> Laney: That certainly may be the case in other parts of Aus.
[09:46] <TheMuso> Laney: We did have a record breaking overnight temperature a week or so back, 26 or so degrees C.
[09:46] <TheMuso> Thats in Sydney.
[09:47] <Laney> TheMuso: https://www.theguardian.com/weather/2017/jan/24/sydney-heatwave-expected-to-shatter-weather-record-set-before-federation <- that's the one I read
[09:50] <TheMuso> No idea if we got there but I wouldn't be surprised if we did.
[09:51] <TheMuso> Oh thats for today.
[09:51] <TheMuso> Yeah well in my local area I think it got to about 36.
[09:51] <TheMuso> Still darn hot.
[09:53] <Laney> Yep yep yep
[10:59] <sil2100> Trevinho: hey! I see your appmenu silo is ready for release since a while - I generally leave such no-packaging-changes silos to be released by the landers, you want me to press the button?
[11:05] <Sweet5hark> ahh, libreoffice-l10n finally completed the build. now for keeping stuff afloat ...
[15:30] <willcooke> ding ding
[15:30] <seb128> hoi
[15:30] <willcooke> #startmeeting Desktop Team Weekly Meeting - 2017-01-24
[15:30] <meetingology> Meeting started Tue Jan 24 15:30:37 2017 UTC.  The chair is willcooke. Information about MeetBot at http://wiki.ubuntu.com/meetingology.
[15:30] <meetingology> Available commands: action commands idea info link nick
[15:30] <Sweet5hark> grmbl,  something is fscked up about epoxy and i dont even know what that is.
[15:30] <willcooke> Roll call: andyrock, attente, desrt,  dgadomski, fjkong (out), flexiondotorg (meeting), happyaron (out), hikiko, laney, qengho, seb128, sweet5hark, themuso (out), tkamppeter, trevinho, robert_ancell (out)
[15:30] <qengho> Aiee!
[15:30] <Sweet5hark> o/
[15:31] <hikiko> hello
[15:31] <desrt> yup
[15:31] <andyrock> hey
[15:32] <willcooke> 1 more minute...
[15:32] <hikiko> :)
[15:33] <willcooke> oki, let's start
[15:33] <willcooke> #topic andyrock
[15:33] <andyrock> hey
[15:33] <andyrock> #1. Proposed a branch for recording failing test on jenikins for unity8
[15:34] <andyrock> #2. Worked a little bit for the a11y problem with compiz
[15:34] <andyrock> #3. Reviewing a comping branch
[15:34] <andyrock> eow
[15:34] <willcooke> thanks andyrock, good stuff
[15:34] <willcooke> #topic attente
[15:34] <attente> hey
[15:34] <attente> apparmor dconf patch testing and review with desrt, meeting with security team to figure out missing requirements
[15:34] <attente> mir patch backporting from gtk4 to gtk3 to reduce the delt
[15:34] <attente> started debugging combo box problems in gtk-mir/miral-shell: https://bugs.launchpad.net/miral/+bug/1655997
[15:35] <attente> (eof)
[15:35] <willcooke> great! thanks to you and desrt for the work with the sec. team
[15:35] <willcooke> #topic desrt
[15:35] <desrt> hey
[15:36] <desrt> attente mostly covered it.  got together last week to discuss the interface between the proxy and what is needed from apparmor
[15:36] <desrt> and indeed, had a security team meeting.  imho, that didn't go very well
[15:36] <desrt> the one thing that we really needed from them was not delivered (even though they delivered some other things)
[15:36] <desrt> so that's completely clear now
[15:36] <desrt> work continues....
[15:36] <desrt> eof
[15:36] <willcooke> thanks desrt #
[15:36] <willcooke> #topic dgadomski
[15:36] <dgadomski> hey
[15:36] <dgadomski> * backported fix to #1550983 from Debian to Xenial/Yakkety
[15:37] <dgadomski> * investigated a blank screen issue with intel vga on vesa driver, no conclusions yet
[15:37] <dgadomski> * checking a potential usblp issue
[15:37] <dgadomski> eof
[15:37] <willcooke> thanks dgadomski
[15:37] <willcooke> #topic FJKong
[15:37] <willcooke> bug tracing:
[15:37] <willcooke> #1656450
[15:37] <willcooke> Desktop notifications stop working
[15:37] <willcooke> should be notify-daemon crash
[15:37] <willcooke> #1656071
[15:37] <willcooke> Expect Preview in 16.10 When I Press Space, Instead, Nothing Happens.
[15:37] <willcooke> #1644781
[15:37] <willcooke> Sushi-start fails with 16.10 upgrade, both Unity and Mate
[15:37] <willcooke> due to sushi-start crash
[15:37] <willcooke> #topic flexiondotorg
 Time appropriate greetings!
 · If you seen Dell and Barton George getting coverage in blogs and podcasts over the last couple of weeks, I've been working with Barton in the evenings to help broaden the exposure of the new Ubuntu Powered line-up from Dell.
 · About a dozen upstreams and ISVs on the go.
   · Helping upstreams and ISVs unblock snap progress now that dbus support in snapd is in much better shape.
   · Snapcraft assistance for several projects who've shown interest but lack the time to get started.
 · Testing Zesty themes. Aside from Firefox Notebooks (upstream issue) everything is in good shape.
 · Testing Xenial dailies and liasing with System 76 who said they wanted to be more involved in the HWE testing last October.
   · System 76 have smoke tested all their supported computers, both upgrades and oem-installs.
 🎬
[15:38] <willcooke> #topic happyaron
[15:38] <willcooke> 1. nm bug #1647283
[15:38] <willcooke> 2. opencc SRU to yakkety, bug #1657677
[15:38] <willcooke> 3. opencc arch dependent data files, debian #851733
[15:38] <willcooke> 4. zfs-linux linux 4.9 compatibility
[15:38] <willcooke> 5. prepare information for bug #997200
[15:38] <willcooke> #topic hikiko
[15:38] <hikiko> hey :) low gfx: I am still trying to figure out what's missing from compizconfig and it doesn't update the profiles instantly + extend the lib, +sick leave monday
[15:38] <hikiko> eof
[15:39] <willcooke> thanks hikiko
[15:39] <willcooke> #topic Laney
[15:40] <Laney> JUST IN TIME
[15:40] <Laney> • Reviewed/gave feedback/eventually uploaded a branch to add Scale=2 directories to Humanity
[15:40] <Laney> • Debugged ubiquity-dm being broken (broke oem-config and only-ubiquity/maybe-ubiquity mode), turned out to already have been fixed so poked ubiquity developers to merge that, done now
[15:40] <Laney> • Little bit more work on prepping gnome-software patches to go upstream
[15:40] <Laney> • Think some of the iso builds are hitting https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=838441, looking to debug atm
[15:40] <Laney> • autopkgtest:
[15:40] <Laney> ∘ made blacklisted packages be more visible (e.g. in excuses)
[15:40] <Laney> ∘ got some patch reviews: lxd reboot detection fix, fix for fetching packages if "Package-List" is last in the apt-cache showsrc output
[15:40] <Laney> ∘ made a reproducer package for not killing the infrastructure if a test causes a kernel panic - panic() hell yeah, just need to fix it now
[15:40] <Laney> ⚜
[15:40] <willcooke> thanks Laney
[15:41] <willcooke> #topic qengho
[15:41] <qengho> * chromium beta arm fixes. No upstream stable release this week.
[15:41] <qengho> * browser-test snap, debugging audio problems in confinement. Icky.
[15:41] <qengho> * tor-middle-relay snap updated, 10 minutes this morning. launchpad build+upload of snaps is *so nice*.
[15:41] <qengho> EOF
[15:42] <willcooke> :) thanks qengho
[15:42] <willcooke> #topic seb128
[15:42] <seb128> • contributed to some snap mailing list discussions
[15:42] <seb128> • archive admin reviews
[15:42] <seb128> • tweaks to the snapd desktop launchers
[15:42] <seb128> • xenial desktopish SRU verifications and tried to get some items unstucked
[15:42] <seb128> • cleaned a bit the sponsoring queue
[15:42] <seb128> • usual rounds of launchpad bugstriaging, IRC discussions, etc

[15:42] <willcooke> thanks seb128
[15:42] <willcooke> #topic Sweet5hark
[15:42] <Sweet5hark> - sick on friday
[15:42] <Sweet5hark> - LibreOffice 5.3.0~rc1 as snap (on amd64 only), bumped to 5.3.0~rc2 then
[15:42] <Sweet5hark> - temporarily disabled some tests to pass snap on armhf
[15:42] <Sweet5hark> - temporarily disabled some more tests to pass snap on i386
[15:42] <Sweet5hark> - LibreOffice 5.3.0~rc1 as dpkg (but missing dbg symbols) -- initial merge for 5.3/zesty
[15:42] <Sweet5hark> - some fixes to get LibreOffice 5.3.0~rc1 l10n to build too (allow root builds)
[15:42] <Sweet5hark> - various more tweaks and fixes, some removal of delta to Debian
[15:42] <Sweet5hark> - bumped/merged dpkg to 5.3.0~rc2 and enabled dbgsyms in ppa builder (currently building)
[15:42] <Sweet5hark> - TDF Board, ESC, AB calls
[15:42] <Sweet5hark> - some TDF admin: budget approvals, tenders, PR coodination
[15:42] <Sweet5hark> - some trusty backporting forwarded to Debian
[15:42] <Sweet5hark> - backlog: didnt get to some backporting for precise still :/
[15:43] <willcooke> thanks Sweet5hark
[15:43] <willcooke> #topic TheMuso
[15:43] <willcooke> * Got PulseAudio v10 uploaded to Zesty. All my bluetooth hardware and audio hardware in general working ok.
[15:43] <willcooke> * More discussion with Konrad and Seb about getting new bluetooth stack and pulseaudio bluetooth fixes into Xenial.
[15:43] <willcooke> * Started going through upstream pusleaudio bluetooth patches, and put together a source package based on the Xenial updates source package. Need to set up a Xenial environment to test properly to see if they break anything.
[15:43] <willcooke> #topic tkamppeter
[15:44] <tkamppeter> - CUPS snap: Studied current state of the snapcraft docs and applied some stuff to the snap
[15:44] <tkamppeter> - cups-filters: Release of 1.13.3
[15:44] <tkamppeter> - Google Summer of Code 2017: Put up student project ideas for OpenPrinting, posted the mentoring organization application for the Linux Foundation, video conference student interview.
[15:44] <tkamppeter> - Bugs.
[15:44] <willcooke> thanks tkamppeter
[15:44] <willcooke> #topic Trevinho
[15:44] <Trevinho> · Added some cancellable to unity temporary dbus proxies (fixing crashes)
[15:44] <Trevinho> · Testing compizconfig for profile switching
[15:44] <Trevinho> · Looking at the new fdo StatusNotifierItem implementation
[15:44] <Trevinho> . Some more fixes to upstream Remmina to work with snap
[15:44] <Trevinho> . Workaround to snap-desktop-helpers to create missing $XDG_RUNTIME_DIR
[15:44] <Trevinho> · Add again remote indicators to snap-desktop-helpers
[15:44] <Trevinho> · Created a travis cron job that builds daily the Remmina snap, pushing latest git commit to edge and latest release tag to stable (using docker for both i386 and amd64)
[15:44] <Trevinho> · Remmina is then now in snap store (and got also some unexpected OMG! ubuntu coverage)
[15:44] <Trevinho> · Fixed snapcraft to detect proper arch when building in a 32bit userspace with a 64bit kernel (normally in a container)
[15:44] <Trevinho>  EOF
[15:45] <willcooke> thanks Trevinho
[15:45] <willcooke> #topic robert_ancell
[15:45] <willcooke> - Working on snapd-glib regression tests (will be required to get SRU exception)
[15:45] <willcooke> - Landed snapd-glib Qt/QML bindings
[15:45] <willcooke> - Bug diagnosing work
[15:45] <willcooke> #topic AOB
[15:45] <willcooke> Anyone got anything to share?
[15:45] <willcooke> Some news to pass on...
[15:46] <willcooke> What was Phonedations - now IOTdations - are helping with Network Manager and BlueZ
[15:46] <seb128> \o/
[15:46] <attente> nice
[15:46] <willcooke> so we should get paper cuts fixes over the next couple of weeks, and them I working with them to solidify the plan going forwards
[15:47] <willcooke> *tehn
[15:47] <willcooke> then
[15:47] <Trevinho> cool
[15:47] <willcooke> but generally we are already getting more involvement and it's working out well
[15:47] <willcooke> no doubt there will be SRUs to help with soon
[15:48] <willcooke> Have a couple of new feature requirements coming down the line around live patching.  Will get the full details and let you all know
[15:48] <willcooke> anyone got anything else?
[15:49] <willcooke> going once
[15:50] <willcooke> twice
[15:51] <willcooke> thrice, and sold.
[15:51] <willcooke> #endmeeting
[15:51] <meetingology> Meeting ended Tue Jan 24 15:51:21 2017 UTC.
[15:51] <meetingology> Minutes:        http://ubottu.com/meetingology/logs/ubuntu-desktop/2017/ubuntu-desktop.2017-01-24-15.30.moin.txt
[15:51] <willcooke> thanks all
[15:51] <seb128> thanks!
[15:52] <qengho> :)
[15:52] <Trevinho> :-)
[15:52] <Trevinho> sil2100: ah, well... Those... I was waiting for code review from ltinkl, but maybe you can proceed with code checks too.. Or andyrock could
[16:04] <andyrock> Trevinho: links?
[16:04] <Trevinho> andyrock: https://bileto.ubuntu.com/#/ticket/2363
[17:30] <jcastro> are there any open bugs on snap desktop apps not putting the icon in the right place?
[17:31] <jcastro> someone commented on the keespassxc snap on HN today that it didn't install an icon for them
[17:32] <jcastro> and I've seen some snaps not do this but I thought it was just me.
[17:32] <davmor2> jcastro: I have icons unless they expected it to appear in the launcher like it does with deb installed software, I don't have keespassxc installed though so can't confirm on that one
[17:33] <jcastro> he just said "menu item" so I'm assuming the dash
[17:35] <davmor2> jcastro: installing and trying here
[17:36] <jcastro> I've seen that the dash sometimes takes a while to realize that there's a new .desktop file
[17:37] <davmor2> jcastro: I see it in dash
[17:38] <davmor2> jcastro: and that is searching straight after install
[17:44] <jcastro> should I just tell him to file a bug?
[17:44] <jcastro> I wonder if he's using another desktop
[17:44] <davmor2> jcastro: http://people.canonical.com/~davmor2/personal-screenshots/keepassxc-crop.png
[17:45] <davmor2> jcastro: if he is on another desktop that might have an effect but in theory shouldn't
[17:45] <jcastro> ok I'll just ask him to do that and then say which desktop, the new place for bugs is snapd in launchpad right? not github?
[17:55] <davmor2> jcastro: right
[18:03] <willcooke> nigtha ll
[18:15] <seb128> k, enough for today, have a nice evening desktopers!