[07:39] <knome> any specific reason -testers is subscribed to librabbitmq and telepathy-farstream?
[07:39] <knome> i'm sure most of the testers do not appreciate bugmail for those packages...
[07:46] <Unit193> I saw that, no idea why it should be.  If anything at all, it'd be the xubuntu-bugs team.
[07:47] <knome> the -qa team is a potential candidate as well.
[07:49] <Unit193> So just think about it like this, not seeded in Xubuntu, not going to be, so no reason to have it subscribed.
[07:54] <elfy> no idea either
[07:57] <elfy> and we're not
[07:57] <knome> elfy, drop librabbitmq while you're at it
[07:57] <knome> cool.
[07:58] <elfy> I did :)
[07:58] <elfy> I wondered where those reports were coming from - but wasn't interested enough to go looking
[08:01] <elfy> could subscribe -testers to things like the xfpm/lid close thing - possibly get more people seeing that something needs testing
[08:01]  * elfy never thought of that
[08:07] <Unit193> ochosi, knome: OK, well I'll mention it then be done.  Trello bot is done, less spammy and works.  Could get more features or have things worded better, but nevertheless.
[09:47] <ochosi> Unit193: nice!
[16:01] <bluesabre> Unit193: poke
[16:03] <bluesabre> https://bugs.launchpad.net/ubuntu/+source/lightdm-gtk-greeter/+bug/1320830
[16:03] <bluesabre> I'm not getting the same build error that dholbach is...
[16:04] <bluesabre> are my debdiffs bad?
[16:05] <bluesabre> ...
[16:05] <bluesabre> is he trying to use 1.8.4 with the 1.8.5 source?
[16:18] <ochosi> bluesabre: tried pinging dholbach yet?
[16:18] <bluesabre> not yet
[16:19] <bluesabre> want to make sure I'm not doing something stupid
[16:19] <bluesabre> :D
[16:24] <pleia2> http://linuxluddites.com/shows/episode-16/
[16:24] <pleia2> haven't listened yet (soon!) but I was interviewed about Xubuntu there
[16:31] <pleia2> my part is only like 25 minutes. whole thing is 2 hours
[16:31]  * pleia2 listens to all
[16:32] <ElderDryas> Xubuntu/Interview starts about 1:30:00
[16:35] <ElderDryas> Interview at 1:35:10
[16:36] <pleia2> thanks ElderDryas :)
[16:36] <ElderDryas> huh, after an hour and a half of the show, /me thinks pleia2 has a funny accent :)
[16:41]  * bluesabre listens
[16:41] <bluesabre> gnu* things always trick me
[16:42] <pleia2> ElderDryas: lol
[16:42] <bluesabre> now the name *gnumeric makes sense hearing somebody else say it
[16:42] <ochosi> bluesabre: hey, instead of listening you should get the xfpm/lls patch up for 14.10! >:D
[16:42] <bluesabre> working on that right now
[16:43] <bluesabre> >:)
[16:44]  * ochosi is an evil slave driver
[16:45] <ochosi> so everyone who voted for me, joke's on you!
[16:45] <ElderDryas> So...how's that Hopey Changy thing working for you? :)
[16:45] <ochosi> bluesabre: i'm aware you didn't vote for me, so yeah, go complain to the others ;)
[16:46] <bluesabre> lol
[16:46] <bluesabre> didn't want you to win too easily
[16:46]  * bluesabre had to put up a fight
[16:49] <ochosi> :)
[16:54]  * elfy was just part of the subversion element
[16:54] <elfy> let someone else be xpl
[16:54] <elfy> blame them :p
[16:58] <bluesabre> :D
[17:02] <ElderDryas> nice interview pleia2 :)
[17:07] <bluesabre> yeah, good stuff pleia2 :D
[17:16] <pleia2> thanks guys
[17:21] <bluesabre> ochosi: https://bugs.launchpad.net/ubuntu/+source/light-locker-settings/+bug/1323368
[17:21] <bluesabre> ochosi: https://bugs.launchpad.net/ubuntu/+source/xfce4-power-manager/+bug/1323367
[17:29] <ochosi> bluesabre: great, thanks!
[18:26] <brainwash> elfy: no ibus included in the daily iso bug 1318319
[18:29] <brainwash> we need to re-assign bug 1310380
[18:29] <elfy> brainwash: haven't noticed if it's gone again tbh
[18:30] <brainwash> elfy: maybe mark as incomplete/invalid then?
[18:30] <brainwash> the 2nd report is caused by the nvidia gpu, so not sure which package to choose
[18:30] <brainwash> just "linux"?
[18:31] <elfy> brainwash: juts booting one
[18:31] <elfy> and why would I mark it like that - when I reported it - it WAS there :)
[18:31] <knome> brainwash, nouveau?
[18:32] <brainwash> knome: yes, xserver-xorg-video-nouveau
[18:32] <brainwash> right
[18:32] <brainwash> elfy: mmh, we need to confirm it then
[18:32] <knome> check the gnome-bluetooth deps
[18:33] <elfy> amazing how many people say stuff like that
[18:33] <knome> like what?
[18:33] <brainwash> we don't install gnome-bluetooth anymore
[18:34] <elfy> like 'we need to confirm x' which I generally take to mean 'someone other than me should confirm x'
[18:34] <knome> lol
[18:34] <knome> i'm eating
[18:35] <brainwash> I cannot confirm it
[18:35] <knome> i can look at it later if you think i'm being lazy ;)
[18:35] <brainwash> so it's +1/-1
[18:35] <elfy> nah
[18:35] <elfy> I'm just looking now
[18:35] <brainwash> thanks :)
[18:35] <elfy> hopefully it got removed
[18:35] <knome> elfy, generally, if you feel like i'm avoiding to do things, feel free to call that out and tell me i need to do it
[18:35] <elfy> no idea how the damn thing got back in either
[18:35] <knome> :P
[18:36] <elfy> knome: lol
[18:36] <knome> except take the XPL hat...
[18:37] <bluesabre> knome: you know you miss it
[18:37] <knome> bluesabre, of course i do. but then i also definitely don't :)
[18:37] <elfy> generally I feel that the majority of team could do more testing - it appears that 8 of team reported on the trackers
[18:38] <elfy> but if I set a cutoff- get listed if you do more than 2 it would be less :p
[18:38] <knome> mmh
[18:38] <knome> i seriously promise to do more testing this cycle when we hit the milestones
[18:38] <elfy> :p
[18:40] <knome> it's just really hard to keep all the strings somewhat in your hands and then be able to dig deep in all areas, especially those that require relatively lot of time, even if they were easy and/but important things
[18:41] <elfy> I know :)
[18:41] <knome> it's a completely different story when you basically "only" need to make sure your own work items get done :)
[18:41] <elfy> not when you're work items depend on everyone else ;)
[18:42] <elfy> anyway - enough of that
[18:44] <knome> yeah... that's not the ideal situation either :)
[18:44] <elfy> well it's a bit hard for QA to be in any other position really :)
[18:45] <knome> but i do think that with the current XPL term policy (ends with LTS), the last LTS release *is* going to be "the definitive" release that defines how well you generally did running the project
[18:45] <elfy> kind of depends on other people checking things :)
[18:45] <knome> and you don't want that to be crap...
[18:45] <elfy> ha ha ha
[18:45] <elfy> indeed not :)
[18:45] <elfy> oh yea that knome - he released THAT one !
[18:45] <elfy> :p
[18:46] <knome> hehe
[18:46] <knome> yeah
[18:46] <knome> it would have been really sad to NOT see the new things prepared for many cycles in 14.04
[18:46] <knome> including light-locker, even if it might seem, for some people, to only bring problems
[18:47] <bluesabre> problems which will be fixed soon
[18:47] <knome> yep
[18:47] <bluesabre> or, are fixed, just need to be uploaded
[18:48] <knome> mhm, part of the "ll is crap" attitude is because not all people know how we ended up here
[18:48] <elfy> knome: I agree
[18:48] <knome> and what's happening now
[18:48] <knome> parole improvements are also great, even if i don't really use non-gmb media players
[18:49] <knome> menulibre *will* be awesome and is already better than alacarte
[18:49] <knome> and it was a nice touch to get mugshot and gtk-theme-config in
[18:49] <elfy> well it does actually do things - I gave up with alacarte
[18:49] <knome> hehe
[18:49] <knome> yeah...
[18:49] <knome> i even went to the extreme of not using menus at all
[18:49] <knome> now i'm using them a bit
[18:50] <elfy> I got so used to using shortcuts to start things
[18:50] <elfy> I probably use menu for 2 or 3 things that I use
[18:51] <elfy> when we can search for 'settings' apps in menulibre - that will be great
[18:51] <elfy> on the other hand I really don't want things to change too much :)
[18:52] <elfy> so bluesabre - you can only change things if it means the testcase can stay the same :p
[18:52] <bluesabre> :)
[18:52] <bluesabre> the plan for this cycle was just bug fixes and tiny improvements
[18:52] <bluesabre> and code optimization
[18:52] <bluesabre> (for my apps)
[18:52] <elfy> yea
[18:52] <elfy> I sort of got the gist of that
[18:53] <knome> bluesabre, sounds like something you should have done for the LTS cycle
[18:53]  * knome hides
[18:54] <bluesabre> I am doing it for the LTS cycle...
[18:54] <bluesabre> 16.04
[18:54] <elfy> lol
[18:54] <knome> yeah sure
[18:54] <knome> i'm sure you are completely rewriting menulibre to release 6.0 then!
[18:54] <bluesabre> :D
[18:55] <elfy> bluesabre: just checking here - you do know the meeting is in 66 minutes not 6 ...
[18:55] <bluesabre> if anything, I'll write my own menu parser since the gnome one is cruel
[18:55] <bluesabre> elfy, yeah, figured I'd tell everybody to wake up in 6 minutes anyway ;)
[18:55] <elfy> that's gnomes for you
[18:55] <elfy> heh
[19:11] <knome> oh right, the meeting
[19:11] <knome> could probably do that one in the balcony if it's not too cool there
[19:12] <elfy> you'd get electrocuted here
[19:14] <knome> huhu?
[20:00] <ochosi> crap, my connection is a bit wonky
[20:00] <ochosi> anyhoo
[20:01] <knome> :)
[20:01] <ochosi> !team | meeting time!
[20:01] <ochosi> (and everyone else ofc)
[20:01] <ochosi> #startmeeting
[20:01] <meetingology> Meeting started Mon May 26 20:01:30 2014 UTC.  The chair is ochosi. Information about MeetBot at http://wiki.ubuntu.com/meetingology.
[20:01] <meetingology> Available commands: action commands idea info link nick
[20:01] <bluesabre> \o/
[20:01] <knome> oh boo, i'm soon running out off battery
[20:01] <ochosi> indeed, boo
[20:01] <elfy> o/
[20:01] <ochosi> i think we were a bit lazy in terms of adding stuff to the agenda :)
[20:02] <ochosi> anyway, i'll quickly tell you about my action items from last time: staging PPA: done.
[20:02] <ochosi> continuing the voting on the ML was done, but we should discuss the result today i think
[20:03] <ochosi> and i sent an email about how to do team meetings
[20:03] <ochosi> bluesabre: how about your open action items?
[20:03] <ochosi> (greeter and menulibre SRU)
[20:03] <bluesabre> #info lightdm-gtk-greeter 1.8.5 is stuck, working on it
[20:04] <bluesabre> #info menulibre SRU in progress
[20:04] <bluesabre> #link https://bugs.launchpad.net/ubuntu/+source/menulibre/+bug/1323405
[20:04] <knome> bluesabre, if you need help with getting the black screen in, poke me
[20:04] <knome> err, black screen fix
[20:04] <ochosi> hehe
[20:04] <bluesabre> knome: will do
[20:04] <ochosi> knome breaks everyone's install, if needed
[20:04] <bluesabre> support i'll link those as well
[20:05] <bluesabre> or, wait until announcements for those
[20:05] <ochosi> yup, or team updates :)
[20:05] <ochosi> elfy: what about your open action items?
[20:05] <elfy> do I have any?
[20:05] <ochosi> nah, i think they're all done
[20:06] <ochosi> just wanted to make sure
[20:06] <ochosi> #topic Team updates
[20:06] <elfy> the one action thing from the last meeting was done before the meeting finished :p
[20:06] <ochosi> any team updates ppl?
[20:06] <elfy> #info QA is slow - hardly any movement at all
[20:06] <elfy> done
[20:07] <knome> ;)=
[20:07] <pleia2> oh hi
[20:07] <knome> oh hi pleia2!
[20:07] <bluesabre> black screen fix should go here or announcements?
[20:08] <bluesabre> hey pleia2!
[20:08] <knome> bluesabre, here's good
[20:08] <bluesabre> ok
[20:08] <ochosi> #info Artwork: Our icon-theme is being worked on currently, hopefully a new release soon. Fixed a few visual bugs, like bluetooth status not showing correctly in the panel (blueman) and fix for indicator-power and bright panels.
[20:08] <ochosi> #info Artwork: Work on Gtk3.12 support in our themes is currently blocked by Gtk3.12 not being in the repos yet.
[20:08] <pleia2> #info Marketing: pleia2 did an interview for Linux Luddites Episode #16 on Xubuntu http://linuxluddites.com/shows/episode-16/
[20:08] <knome> pleia2, ooh, can we SOME that?
[20:08] <bluesabre> #info Development: The light-locker black screen fix is in the sponsors queue
[20:09] <bluesabre> #link https://bugs.launchpad.net/ubuntu/+source/light-locker-settings/+bug/1323368
[20:09] <bluesabre> #link https://bugs.launchpad.net/ubuntu/+source/xfce4-power-manager/+bug/1323367
[20:09] <ochosi> iirc links are picked up automatically now
[20:09] <ochosi> no need for #link anymore
[20:09] <pleia2> knome: hm?
[20:09] <ochosi> (just saying)
[20:09] <knome> pleia2, social media
[20:09]  * bluesabre rocks it old school
[20:10] <ochosi> heh
[20:10] <pleia2> knome: done!
[20:10] <knome> at least links with nothing else on the line...
[20:10] <ochosi> bluesabre: sure, however you prefer ;)
[20:10] <knome> pleia2, cool :)
[20:10] <pleia2> knome: did you #info the external CSS yet?
[20:10] <knome> bluesabre, i've bumped the importance to critical.
[20:10] <knome> pleia2, oh noes
[20:10] <knome> i need power
[20:10] <knome> brb
[20:10] <bluesabre> thanks knome
[20:10]  * Unit193 been skimming.
[20:10] <ochosi> any further team updates?
[20:11] <knome> y
[20:11] <ochosi> ok, will wait for you then
[20:11] <ochosi> just wanted to say in advance that despite the empty schedule, there are a few things worth discussing
[20:11] <pleia2> #info Website new static.xubuntu.org CSS page was added to theme so we can do some of our own CSS updates without waiting on IS
[20:11] <knome> oh duh
[20:11] <knome> i was writing a much more verbose one
[20:11] <ochosi> \o/ nice pleia2 and knome
[20:12] <knome> ochosi, that was my item ;)
[20:12] <pleia2> verbose--
[20:12] <pleia2> :)
[20:12] <knome> nah
[20:12] <knome> depends!
[20:12] <ochosi> ok, any other updates?
[20:12] <knome> bluesabre, btw, i'm not sure if you should set the bug confirmed
[20:13] <pleia2> I'm done
[20:13] <knome> bluesabre, that might not be the way the SRU team tracks the bugs...
[20:13] <bluesabre> knome: those two aren't for SRU yet
[20:13] <bluesabre> gotta go to utopic, the SRU back to trusty
[20:13] <ochosi> #topic Announcements
[20:13] <bluesabre> so more bugs in the future :)
[20:13]  * ochosi assumes that when pleia2 is done, everyone is
[20:13] <ochosi> any announcements?
[20:14] <knome> bluesabre, hmm, sponsors what i meant ;)
[20:14] <bluesabre> ok, then it's good for sponsors ;)
[20:14] <knome> bluesabre, i somehow thought sru...
[20:14] <elfy> ochosi: should there not be an announcement from you
[20:14] <elfy> on the mailing list thing
[20:14] <knome> and debian liaison?
[20:14] <knome> or did that get two weeks
[20:14] <ochosi> elfy: i actually wanted to wait for discussion for that one
[20:15] <bluesabre> anybody else going to apply for tech lead?
[20:15] <knome> who knows... ;)
[20:15]  * elfy will just so there is someone else
[20:15] <bluesabre> oh good
[20:15] <elfy> what is it?
[20:15] <knome> haha
[20:15] <bluesabre> ;)
[20:15] <ochosi> knome: debian liaison has a week, so thursday...
[20:15] <knome> ochosi, practically this is "next week", but okay ;)
[20:16] <ochosi> i can of course always prematurely announce it if you insist ;)
[20:16] <knome> go as you please
[20:16] <elfy> there are 3 replies - that's generally about it ;)
[20:16] <knome> just a thought that popped into my mind
[20:16] <Unit193> ochosi: I hear Noskcaj_ wanted that. ;)
[20:16] <ochosi> ok, i'll wait one more minute (or two) for further announcements, then i'll carry on
[20:16] <knome> Unit193, wanted to cheer you? yeah...
[20:17] <ochosi> Unit193: that's not how i interpreted his email ;)
[20:17] <Noskcaj_> Unit193, What do i want?
[20:17] <ochosi> and hi Noskcaj_ :)
[20:17] <ochosi> any announcements from you?
[20:17] <Noskcaj_> hey ochosi
[20:17] <knome> Unit193, stop being a slimey amoeba;)
[20:17] <Noskcaj_> I'm back?
[20:17] <knome> welcome
[20:17] <bluesabre> yay!
[20:17] <ochosi> hehe, good announcement :)
[20:17] <ochosi> better #info that ;)
[20:17] <knome> another dictator ruling the project now
[20:17] <Unit193> bluesabre: Also, yes, don't set it to confirmed.
[20:17]  * knome hides
[20:18] <knome> hehe, he's back and he's off
[20:18] <ochosi> just stopping by to say i'm back! bye! :)
[20:18] <ochosi> ok, let's carry on...
[20:18] <bluesabre> oh, I guess confirmed is only for sponsored merges
[20:18] <ochosi> #topic Discussion
[20:19] <ochosi> #suptopic Mailinglist proposal by knome
[20:19] <ochosi> as you all know, we voted on knome's proposal last time
[20:19] <ochosi> the result wasn't quite as unanimous as i'd have hoped
[20:20] <ochosi> we discussed this outside the meetings and i came to the following conclusion/proposal:
[20:20] <ochosi> especially in the light of the ML being rather slow lately and strangely since we started discussing closing the ML the offtopic stuff got reduced, i think we can leave it open for now
[20:21] <ochosi> but we try a "two strikes, and you're flagged" model (or X strikes, if ppl have good reasons that 2 is not ok)
[20:21] <ochosi> so when somebody sends inappropriate or offtopic stuff Ã  la "Install LibreOffice by default" to the ML
[20:21] <ochosi> or something that is a bugreport, or a support request
[20:21] <knome> ( ^ technically, set the moderation flag for the email address so further mails from that person needs moderation)
[20:21] <ochosi> a moderator of the list gets in touch with the "offender" directly and personally
[20:22] <ochosi> if the person ignores that and offends again, he/she gets flagged
[20:22] <ochosi> good, i don't have to explain flagging anymore, thanks knome :)
[20:22] <knome> ( ^ messages should also be sent CC to<EMAIL_ADDRESS>so other moderators know it's been dealt with)
[20:22] <ochosi> so yeah, that'd be the proposal, and if everyone can live with it, i'd say we try that for at least a month
[20:23] <ochosi> generally, this would be a very dynamic policy anway though
[20:23] <ochosi> if there's no offtopic stuff, there's nothing to moderate
[20:23] <elfy> but only admins can flag - is that right?
[20:23] <bluesabre> sounds reasonable to me
[20:23] <knome> and finally, if you aren't sure, ask other moderators
[20:23] <ochosi> if the offtopic stuff takes over, we flag lots of people
[20:23] <knome> elfy, only owners can flag, that's me and pleia2 atm
[20:23] <ochosi> knome: care to list the moderators, so that everyone knows?
[20:24] <knome> owners are (can set flags): knome, pleia2
[20:24] <knome> moderators are: elfy, unit193, bluesabre (+owners)
[20:24] <pleia2> I'd also appreciate discussion about this, if someone thinks someone is borderline, let me and knome know, I have a tendancy to give folks reams of rope to hang themselves with :)
[20:25] <knome> sending a mail to xubuntu-devel-owner@lists ... sends a mail to everybody in those two groups.
[20:25] <knome> i'm the bad cop, pleia2 is the good cop
[20:25] <elfy> and I have a tendency to use very short rope - having other things to do than baby people
[20:25] <pleia2> hehe
[20:25] <knome> but i'll promise to try to be as prompt as possible if people request moderation flags
[20:25] <knome> also,
[20:25] <elfy> if we're going to be going - ooh shall we, not sure,, mmm
[20:25] <knome> we should set a policy...
[20:26] <Unit193> elfy: I tend to just ignore, because it's "Ubuntu, so gotta give so much rope you lose sight of them."
[20:26] <elfy> then I don't want to be involved in that at all
[20:26] <knome> when moderator X sends the mail and CC's other owners
[20:26] <knome> the same moderator should take care of noticing the second strike
[20:26] <knome> (if at all possible)
[20:26] <ochosi> i'd personally prefer if we wouldn't vote on this again, cause it slows things down, if the owners and moderators of the list are ok with this proposal, i'd like to put it in effect now/today
[20:27] <knome> and i guess once that happens and anybody notices that, send another mail to -owner
[20:27] <knome> so other moderators know that's it's going to happen, and we owners can act accordingly and add the flag
[20:27] <ochosi> if needed, we can document this, i just wanna "get on with it!" and talk about other things :)
[20:27] <knome> if everybody is happy with the proposal, i can document it under Processes in the wiki today
[20:28] <ochosi> sweet, thanks knome
[20:28] <ochosi> (i hoped you'd say that ;))
[20:28] <knome> but of course! ;)
[20:28] <ochosi> pleia2: +1/0/-1? :)
[20:28] <ochosi> moderators?
[20:28]  * elfy can see this getting completely wishy washy
[20:28] <bluesabre> +1
[20:28] <knome> if we need to flag loads of people, we can always reassess the need for full moderation.
[20:28] <ochosi> exactly
[20:29] <Unit193> Policy++
[20:29] <elfy> I'll just in whichever way gets this moving
[20:29] <knome> yeah, i can +1 this one as well, but i'll want one from pleia2 too, because this is clearly more work for *owners* then the previous proposal.
[20:29] <ochosi> elfy: well there's only one obvious way to get this moving... ;)
[20:29] <pleia2> should be ok
[20:29] <elfy> +0
[20:29] <elfy> I'll sit on the fence then ;)
[20:30] <ochosi> heh
[20:30] <pleia2> we can reassess if it's annoying/awful :)
[20:30] <ochosi> fine
[20:30] <ochosi> #info The mailinglist will get moderated on a per-offender basis, "two strikes and you're flagged".
[20:30] <knome> #action knome to describe the -devel ML moderation policy to Processes in the wiki
[20:30] <meetingology> ACTION: knome to describe the -devel ML moderation policy to Processes in the wiki
[20:30] <ochosi> #action knome will document the new moderation policy against offenders on the wiki
[20:30] <meetingology> ACTION: knome will document the new moderation policy against offenders on the wiki
[20:30] <ochosi> garr
[20:30] <ochosi> :)
[20:30] <knome> #undo
[20:31] <ochosi> thanks
[20:31] <knome> hmm, only chair can undo
[20:31] <ochosi> #undo
[20:31] <meetingology> Removing item from minutes: ACTION
[20:31] <ochosi> ok, let's move on
[20:31] <ochosi> #subtopic Trello
[20:32] <ochosi> as it wasnt announced, i thought we could quickly talk about it
[20:32] <ochosi> there's a big trello board now that elfy set up
[20:32] <ochosi> bluesabre also used it already
[20:32] <ochosi> elfy: wanna do a few #infos?
[20:33] <ochosi> so my proposal with this one is that we try it out
[20:33] <ochosi> it can't really be much worse than the launchpad blueprints in terms of up-to-dateness
[20:33] <bluesabre> :)
[20:33] <ochosi> try it for one cycle and then re-assess how it helped us and what would be needed for it to work better
[20:33] <ochosi> #info Unit193 set up a Trello bot for interaction with the board from within IRC.
[20:34] <knome> does that need a trello account?
[20:34] <elfy> unfortunately yes
[20:34] <knome> or how's the interaction done
[20:34] <ochosi> Unit193: further infos on that? will it always reside in a different channel? how does it work?
[20:35] <elfy> there's currently 5 team members not there - knome, skellat, michah, lionel and jackson
[20:35] <elfy> 2 of those are not about for sure anyway
[20:35] <ochosi> has anyone talked to skellat lately? how long is he MIA?
[20:35]  * knome has been slacking
[20:36] <knome> ochosi, probably not getting back very son
[20:36] <knome> *soon
[20:36] <elfy> ochosi: from what I saw - another cycle
[20:36] <ochosi> actually micah mentioned that he got promoted at work, so he's busier than before
[20:36] <elfy> which begs the question - if missing for 2 cycles
[20:36] <ochosi> don't wanna jump to conclusions, but i don't think he (=micahg) will be around much during U
[20:37] <ochosi> elfy: you mean wrt team membership status?
[20:37] <elfy> ochosi: I got that impression
[20:37] <elfy> ochosi: yea
[20:37] <ochosi> right, iirc knome did something before leaving me this moldy chair that ii'm currently residing on
[20:37] <ochosi> something with respect to team membership running out if there are no contributions for X cycles
[20:38] <knome> ochosi, whatever you do, don't smell it!
[20:38] <knome> i haven't done very strict cleaning.
[20:38] <ochosi> but i don't remember whether the policy was put into place or just thought about
[20:38] <elfy> "Anyone with no contributions for more than a complete cycle (6 months) should deactivate themself from the team as well as all subteams and reapply if/when they are willing to rejoin. "
[20:38] <knome> i've asked some people whether they think they will continue contributing
[20:38] <elfy> https://wiki.ubuntu.com/Xubuntu/StrategyDocument#Xubuntu_Team
[20:38] <knome> by that definition, skellat and mr_pouit should be probably dropped.
[20:39] <ochosi> i think mr_pouit did one upload of shimmer-themes in the trusty cycle
[20:39] <ochosi> depends now on what you count as "contributing"
[20:39] <knome> otoh, lionel *has* popped up now and then (and has said that since he really can't follow IRC, it's hard to follow the development generally)
[20:39] <knome> so it all depends how strictly you want to force that rule
[20:39] <ochosi> but yeah, i think it's fair that without contributions, you lose your voting rights for the time being
[20:39] <knome> i still think it's a good idea to keep that in place.
[20:39] <elfy> knome: he said that in the m/l discussion I think
[20:40] <knome> ochosi, that's the reason why it is there in the first place
[20:40] <knome> also if n people are absent, it gets harder and harder to get a quorum
[20:40] <knome> since they are never around
[20:40] <ochosi> yup
[20:40] <knome> well, "never"
[20:40] <ochosi> i think we should ask a few ppl to seize their voting rights then
[20:41] <ochosi> just have to take the time to write understanding appreciative emails with the right tone i guess...
[20:41] <knome> i'd prefer if the people deactivated themself
[20:41] <elfy> knome: +1
[20:41] <ochosi> yeah, but we still have to ask them to do it
[20:41] <knome> sure
[20:41]  * ochosi wasn't suggesting anything else
[20:41] <knome> no, no
[20:41] <knome> though if we ask them, and they don't answer in six months...
[20:41] <Unit193> ochosi: It's in read only mode, it's in a different channel as it's not been invited in one of the 'official' channels.
[20:42] <ochosi> Unit193: i know, i meant: #info a few infos plz ;)
[20:42]  * elfy wishes he'd not taken this trello thing offtopic lol
[20:42] <ochosi> before we move on, cause trello seems to be going away as a topic atm...
[20:42] <knome> ochosi, maybe point out that "ex" team members will most probably get their membership back much quicker than new developers
[20:42] <ochosi> elfy: yeah...
[20:43] <ochosi> knome: yeah, thought of that
[20:43] <ochosi> ok, anything else ppl wanna talk about wrt Trello?
[20:43] <elfy> #info Those in -team not yet on the trello access list to get account so they can be added
[20:43] <knome> ochosi, and that it's not really about excluding them, mostly for practical reasons (because that's how it is)
[20:43] <knome> #action knome to create a Trello account
[20:43] <meetingology> ACTION: knome to create a Trello account
[20:43] <Unit193> ochosi: Like?
[20:43] <ochosi> #info Whoever has questions to Trello can get in touch with elfy.
[20:44] <elfy> can you undo that please
[20:44] <ochosi> Unit193: what did you plan/think the bot would be used for? etc.
[20:44] <knome> elfy, why does Trello start with T and end with o?
[20:44] <ochosi> elfy: awwwwh :)
[20:44] <ochosi> #undo
[20:44] <meetingology> Removing item from minutes: INFO
[20:44] <elfy> then add slickymaster to it - he knows as much as me :)
[20:44] <knome> slickymaster, why does Trello start with T and end with o?
[20:44] <ochosi> well i think somebody should be the "trello contact", even if i don't think there'll ever be questions
[20:44] <elfy> you can also add the other admin - which is ochosi :p
[20:44] <knome> :P
[20:45] <Unit193> ochosi: If it's useful, how you want, etc.  I like IRC, so this makes sense to me.  If we want to get more from it, we can.
[20:45] <elfy> ochosi: ok then
[20:45] <ochosi> meh, knome made me admin on so many things already...
[20:45] <elfy> pleia2 uses it as well
[20:45] <ochosi> anyway, let's carry on if there are no further #infos
[20:45] <elfy> so there are a few of us
[20:46] <elfy> #info Whoever has questions to Trello can get in touch with elfy.
[20:46] <ochosi> #subtopic Meeting times during the U cycle
[20:46] <ochosi> righty, i quickly wanted to bring that up
[20:46] <knome> ochosi, did that come as a surprise to you? :P
[20:46] <ochosi> conveniently the person who will hold the next meeting isnt here tonight :p
[20:46] <knome> skip it then
[20:46]  * ochosi looks at slickymaster
[20:47] <knome> and select the next one from the list
[20:47] <knome> this needs to be dynamic:)
[20:47] <ochosi> heh
[20:47] <elfy> or get them to do it tomorrow
[20:47] <ochosi> well i also didn't announce the next meeting on the day of the previous meeting
[20:47] <knome> or call them in their phone!
[20:47]  * knome hides
[20:47] <ochosi> don't think that's a huge problem
[20:47] <knome> then just info that person X does it ;)
[20:47] <ochosi> just wanted to give ppl another chance to object (since there were no comments made on it on the ML)
[20:48] <knome> cycling chairs and times is a great idea.
[20:48] <bluesabre> +1
[20:48] <ochosi> #action slickymaster to announce the next meeting time ASAP
[20:48] <meetingology> ACTION: slickymaster to announce the next meeting time ASAP
[20:48] <elfy> though I did just have a thought about this cycling thing - 75% of the leads are EU of some sort :)
[20:48] <ochosi> after that it'll be elfy's turn i think
[20:49] <elfy> ochosi: you forget -dev :)
[20:49] <ochosi> elfy: yeah, but that hasn't been voted on yet ;)
[20:49] <knome> elfy, 100% of XPL was EU the last time, wasn't a problem then...
[20:49] <ochosi> we also skipped our to-be Debian Liaison
[20:49] <elfy> ochosi: indeed - but it will have been by the time it gets to me :p
[20:50] <ochosi> sure, so most likely bluesabre and then elfy
[20:50] <elfy> not that I *really* mind I add
[20:50] <ochosi> do we need a list for that or will we make it clear at the end of every meeting who chairs the next one?
[20:50] <knome> who's gonna update the wiki for the new policy?
[20:50] <ochosi> the one who asks?
[20:50] <knome> ochosi, the list could be in the meetings page comments
[20:50] <ochosi> :)
[20:51] <elfy> knome: whoever is in there doing the m/l stuff?
[20:51] <knome> :P
[20:51]  * knome sighs
[20:51] <elfy> lol
[20:51] <ochosi> knome: in due time, we'll create a wiki-team for you ;)
[20:51] <knome> #action knome updates the Processes page for the new meeting chair/scheduling policy
[20:51] <meetingology> ACTION: knome updates the Processes page for the new meeting chair/scheduling policy
[20:51] <elfy> +1 to having list in meeting page comments
[20:52] <ochosi> thanks knome!
[20:52] <knome> #Action knome adds a list of cycling chairs in the Meetings page
[20:52] <meetingology> ACTION: knome adds a list of cycling chairs in the Meetings page
[20:52] <ochosi> ok, any other things we wanna discuss?
[20:52]  * ochosi is through with his topics for tonight
[20:52] <elfy> oh yea
[20:52] <ochosi> ah right
[20:53] <ochosi> there's one left on the meeting page :D
[20:53] <ochosi> sorry elfy
[20:53] <elfy> I only just remembered
[20:53] <ochosi> #subtopic Route testing requirements through xubuntu-qa
[20:53] <ochosi> elfy: you got the floor
[20:53] <knome> elfy, show us your best moves
[20:53] <elfy> so - simple enough - if you want something testing - talk to me
[20:53] <elfy> and
[20:54] <elfy> before you talk to me - you can check on trello calendar to see when we can fit things in :)
[20:54] <bluesabre> :)
[20:54] <elfy> please don't let me wake up to testing calls on the mailing list - I have to keep cleaning tea of the monitor ;)
[20:55] <ochosi> hehe
[20:55] <bluesabre> yeah, I'll behave
[20:55] <ochosi> elfy: good you're not drinking substances that are harder to clean off though ;)
[20:55] <elfy> bluesabre: well - you know where the calendar is :)
[20:55] <elfy> ochosi: lol
[20:55] <ochosi> any #infos for that?
[20:55] <knome> ochosi, like oil?
[20:55] <elfy> #info Talk to QA for testing requirements
[20:56] <Unit193> elfy: OK, so contact you if/when for -core?
[20:56] <ochosi> also, that sounded more like an announcement than a discussion
[20:56] <elfy> #info Check Trello calendar before talking to QA
[20:56] <ochosi> or is it just my ears... :>
[20:56] <elfy> ochosi: no - it's the time :)
[20:56] <ochosi> heh
[20:56] <elfy> if people want to try and persuade me that they can call for testing at any time - they are welcome to try :)
[20:57] <elfy> Unit193: mmm - as you are in the QA team I'd hope you'd be able to see when we've got space :D
[20:58] <ochosi> righty, anything else to "discuss"? :}
[20:58] <elfy> ochosi: we can discuss it if you want - but I'm pretty much sat here with feet in concrete
[20:58] <ochosi> nah, i'm fine with this
[20:59] <elfy> :)
[20:59] <ochosi> other topics/discussions?
[20:59] <elfy> none from me
[21:00] <bluesabre> good here
[21:01] <ochosi> ok, in that case, thanks everyone!
[21:01] <ochosi> #endmeeting
[21:01] <meetingology> Meeting ended Mon May 26 21:01:24 2014 UTC.
[21:01] <meetingology> Minutes:        http://ubottu.com/meetingology/logs/xubuntu-devel/2014/xubuntu-devel.2014-05-26-20.01.moin.txt
[21:01] <Unit193> ochosi: Danke.
[21:01] <elfy> ty ochosi
[21:01] <ochosi> yw
[21:07] <ochosi> minutes are up (thanks for this painless process lderan and knome!)
[21:07] <elfy> we missed an action in the m/l discussion :p
[21:08] <elfy> no action to mail the list to say what was going to happen lol
[21:08] <knome> i guess i can do that...
[21:08] <ochosi> right :)
[21:08] <ochosi> thanks
[21:12] <elfy> night all
[21:14] <Unit193> ochosi: So, what's the plan for trellobot?
[21:14] <ochosi> well, i would wanna ask you
[21:14] <ochosi> personally i don't know
[21:15] <ochosi> i'd say we add it here
[21:15] <ochosi> and if it gets too spammy, we move it to another channel
[21:17] <Unit193> Right, if you didn't see I made the help command PM the user (even if asked in channel.)
[21:18] <knome> ochosi, was the cycling alphabetical by team name?
[21:18] <ochosi> knome: yeah
[21:19] <ochosi> well, actually by team lead role title :)
[21:19] <knome> aha
[21:19] <ochosi> but it doesn't matter as for now it was the same
[21:20] <ochosi> since we have teams>roles, i think we should probably switch to team name
[21:23] <knome> ochosi, so:
[21:24] <knome> XPL, art, debian, doc, marketing, qa, release (?), technical, website
[21:25] <ochosi> sounds good to me
[21:26] <ochosi> actually, i'm wondering whether we should remove the xfce4 liaison post from the leaders page
[21:26] <ochosi> i can't see anyone doing that again anytime soon
[21:26] <knome> we can do that if you feel like it
[21:26] <ochosi> i think it was mostly introduced for JPohlmann
[21:28] <knome> probably yeah
[21:29] <knome> processes + meetings should be fine now
[21:43] <ochosi> nice
[21:43] <ochosi> that was fast
[21:46] <knome> ochosi, mail on -devel about moderation
[21:51] <Unit193> ochosi: So, there you go, xubutrello.
[22:14] <bluesabre> knome: care to elevate these two as well?
[22:14] <bluesabre> https://bugs.launchpad.net/ubuntu/+source/menulibre/+bug/1323405
[22:14] <bluesabre> https://bugs.launchpad.net/ubuntu/+source/xfce4-power-manager/+bug/1323367
[22:15] <bluesabre> Logan_, feeling uploady? :)
[22:16] <knome> bluesabre, left you some words
[22:24] <bluesabre> thanks knome!
[22:25] <knome> bluesabre, np
[22:25] <knome> bluesabre, all deserved
[23:18] <Logan_> bluesabre: always
[23:19] <bluesabre> hey Logan_
[23:19] <ochosi> hi Logan_
[23:19] <bluesabre> so, we have a few things that need to be uploaded...
[23:20] <bluesabre> https://bugs.launchpad.net/ubuntu/+source/menulibre/+bug/1323405 to trusty-proposed
[23:20] <bluesabre> https://bugs.launchpad.net/ubuntu/+source/xfce4-power-manager/+bug/1323367 to utopic
[23:20] <ochosi> that one is important ^
[23:20] <ochosi> critical bugfix
[23:20] <bluesabre> https://bugs.launchpad.net/ubuntu/+source/light-locker-settings/+bug/1323368 to utopic
[23:20] <Logan_> dear lord
[23:20] <ochosi> yeah, that one too
[23:21] <bluesabre> ^^ these two go together since they are two components of the same bugfix
[23:25] <Logan_> okay so
[23:26] <Logan_> uhhhh
[23:26] <ochosi> huhu, someone's happy here :)
[23:34] <bluesabre> :)
[23:34] <bluesabre> I'd suggest not looking at the menulibre one first
[23:35] <bluesabre> the other two are quite simpler
[23:35] <bluesabre> menulibre is a backport from utopic
[23:44] <sergio-br2> ochosi?
[23:44] <sergio-br2> I think you talked to me, sorry for the delay
[23:44] <sergio-br2> :)
[23:46] <ochosi> hey sergio-br2
[23:46] <ochosi> no worries
[23:47] <sergio-br2> i saw the updates
[23:47] <ochosi> yup, mostly wanted to ask how it's going and what the ETA was on the webapps branch
[23:47] <ochosi> also pulled in a few more icons from upstream
[23:48] <sergio-br2> well, slow, but it's going
[23:48] <ochosi> and got in touch with daniel again, he pulled a lot upstream btw
[23:49] <sergio-br2> wow, a lot of
[23:49] <sergio-br2> i'm seeing
[23:49] <sergio-br2> ah, r1223
[23:50] <sergio-br2> cool
[23:50] <ochosi> also would like to pull in the new shotwell icon
[23:51] <sergio-br2> are there other sizes?
[23:52] <sergio-br2> before i forget it, could you touch that Liviu, to create a trusty version of the ppa?
[23:53] <sergio-br2> and other thing, this number in the package does not help very much... 13.10.3 > 13.10~git[...]
[23:53] <sergio-br2> i have to force and lock in synaptic, to install
[23:54] <ochosi> hm, i think we also have another daily icon theme repo with saner versioning
[23:54] <ochosi> bluesabre: ^ ?
[23:55] <bluesabre> https://launchpad.net/~shimmerproject/+archive/daily
[23:55] <sergio-br2> nahh, ok
[23:56] <sergio-br2> great, thanks
[23:56] <bluesabre> YYYYMMDDHHMM
[23:57] <sergio-br2> yeah, better to upgrade :)


[00:01] <pavlix> xnox: So what are your main interests?
[00:02] <xnox> pavlix, volleyball and skiing =)
[00:02]  * xnox giggles
[00:04] <xnox> pavlix, been around since about 2012. DD, Ubuntu Core Developer, ex SPI director. Mostly code in C and Python. Did a bit of upstart, a bit of systemd, currently doing a bit of s390x.
[00:06] <pavlix> xnox: That sounds nice. I joined Red Hat in May 2012 as a core NetworkManager developer at that time but later worked with the packagers of various network services and recently left to go back freelance.
[00:07] <xnox> pavlix, fun!
[09:31] <sunweaver> LocutusOfBorg: what do you need to know about Ayatana Indicators?
[09:35] <JackFrost> sunweaver: Problem for remmina was that remmina is in main and ayatana indicators aren't.
[09:42] <sunweaver> ouch.
[09:42] <sunweaver> why is remmina main?
[09:42] <sunweaver> it would require a ubuntu series file then I guess that reverts the upstream patch in remmina.
[09:43] <ginggs> flexiondotorg: would you add Conflicts: telegram-desktop to your telegram PPA packages please?  It would prevent future bugs like LP: #1740708
[09:44] <JackFrost> sunweaver: https://ubuntudiff.debian.net/q/package/remmina just have to flip deps really.
[10:03] <sunweaver> we could do a libappindicator3-dev (>= <ubuntu-version) | libayatana-appindicator3-dev in the Debian package, so that patch would be unnecessary.
[10:03] <sunweaver> I am in touch with remmina upstream, so I could ask to get the translations.patch upstreamed, too.
[10:07] <sunweaver> JackFrost: I just pinged mfv from Debian on this who maintains remmina in Debian and lives "next door" to upstream of remmina.
[10:08] <JackFrost> Ooooh, fancy.
[10:08] <JackFrost> Thanks, sunweaver.
[10:08] <sunweaver> we hang out on #debian-remote (OFTC)
[10:08]  * sunweaver loves shrinking the ubuntudiff website...
[10:11] <JackFrost> sunweaver: Indeed, though in the past I didn't want to push any indicator stuff on to Debian.
[10:13] <sunweaver> that's why I started a fork....
[10:14] <sunweaver> because Inidicators from Launchpad do not work on non-Ubuntu systems.
[10:14] <JackFrost> sunweaver: I'm Unit193, btw..
[10:15] <sunweaver> this man(?) is confusing me...
[11:47] <bdrung_work> mvo, hi. can you merge initramfs-tools from Debian unstable to bionic (you are the last uploader) or should i do it?
[11:49] <bdrung_work> apw, ^
[11:50] <mvo> bdrung_work: you are welcome to merge it, my contribution was mostly a drive-by fix
[12:00]  * apw is happy for anyone to merge it indeed
[12:26] <rbasak> slangasek: ahasenack pointed out to me that the Breaks in Xenial seems to be holding back distro-info-data. I had noticed that but ignored it previously.
[12:26] <rbasak> slangasek: I think it's because the Breaks in distro-info-data for Xenial is wrong.
[12:26] <rbasak> Because on Xenial, juju-core is a 1.x series transitional package.
[12:27] <rbasak> So those of us who upgraded into Xenial with juju 1.x previously installed have a blocked distro-info-data package.
[12:29] <ahasenack> https://pastebin.ubuntu.com/26325364/ ^
[14:27] <bdrung_work> apw, done
[14:27] <bdrung_work> ubuntu carries a huge amount of change. many of them should be upstreamed.
[14:35] <apw> bdrung_work, yes, yes it should
[16:51] <slangasek> rbasak: it certainly appears that distro-info-data's Breaks don't have a version of juju-core in xenial that satisfies them, so something needs fixed...
[16:53] <slangasek> rbasak: so distro-info-data probably needs to Breaks: juju-2.0 (<< 2.2.6) instead?
[16:53] <rbasak> slangasek: that sounds about right. But only in Xenial.
[16:54] <rbasak> Unless future series have the same arrangement in Juju?
[16:54] <rbasak> Otherwise that'll be painful for future distro-info-data imports :-(
[16:54] <slangasek> rbasak: it only matters for xenial
[16:55] <slangasek> rbasak: well, it mattered also for zesty, but EOL
[16:56] <rbasak> slangasek: OK. I'm not really familiar with the details. Just passing on the report :)
[17:10] <slangasek> rbasak: distro-info-data reuploaded, if you want to review
[17:31] <rbasak> slangasek: diff looks empty apart from changelog?
[17:32] <slangasek> rbasak: but is it a good changelog? ;)
[17:32] <slangasek> looking
[17:36] <slangasek> rbasak: rejected/reuploaded, thanks
[17:47] <rbasak> slangasek: looks good, but do you know any reason for distro-info-data 0.28ubuntu0.3 to be in the security pocket?
[17:48] <slangasek> rbasak: not offhand
[17:49] <rbasak> Seems like some distro-info-data updates were deliberately being put in there.
[17:49] <rbasak> So now I don't know whether it's correct for this fix to go in there, or all fixes to distro-info-data should go into the security pocket :-(
[17:58] <mdeslaur> rbasak: if you're sruing it, just get someone to pocket-copy it to -security after
[17:58] <rbasak> mdeslaur: ah, OK. I was under the impression that a pocket copy in that direction wasn't always safe.
[17:58] <rbasak> (though seems unlikely to be an issue for distro-info-data)
[17:58] <mdeslaur> it isn't, but this package only has data in it
[17:59] <rbasak> I'm happy with your ack then. Thanks :)
[18:02] <mdeslaur> rbasak: oh, was that a regression only in post 0.3?
[18:02] <mdeslaur> sorry, I lack a bit of context
[18:03] <rbasak> I'll need to check the versions.
[18:03] <mdeslaur> you need to make sure you don't break juju-core users that don't have -updates enabled
[18:03] <rbasak> A distro-info-data update caused a regression in Juju which was parsing the data wrong.
[18:03] <rbasak> We have a Breaks: for it now.
[18:04] <mdeslaur> is the breaks on a version that is in -security?
[18:04] <rbasak> And juju is fixed now.
[18:04] <rbasak> Looking
[18:05] <rbasak> The version of distro-info-data in xenial-security won't break any version of Juju.
[18:05] <mdeslaur> right, so if you push the new distro-info-data to -security, environments that have -updates disabled will break, no?
[18:05] <mdeslaur> because the new juju won't be available
[18:05] <rbasak> But if we did pocket copy the version of distro-info-data I just accepted into xenial-proposed to xenial-security, then the version of src:juju-core in xenial-security won't work with it.
[18:06] <rbasak> Right
[18:06] <rbasak> So better not do that.
[18:06] <mdeslaur> right
[20:48] <tsimonq2> doko: Looking at GCC 8 failures, fixing Debian bug 885128 should fix a few failing Qt packages, and qtlocation is interesting because it could (not sure) be a GCC segfault. Otherwise the rest of the Qt failures should be fixed upstream...
[20:48] <tsimonq2> All I have for now :)


[05:13] <floatsmahgoat> hello all and please welcome me
[05:20] <floatsmahgoat> https://tinyurl.com/v3f4m65
[05:28] <floatsmahgoat> yalk are hinestly pretty boring
[05:28] <floatsmahgoat> love you tho
[19:44] <mehmet> selam arkadaşlar


[00:04] <arraybolt3> I see both bugs and may be able to help debug. If we just found a real Openbox bug that would be pretty interesting, given that it's been mostly unchanged for, what, 13 years?
[01:25] <arraybolt3> Umm... Firefox has gone GNOME on us in the latest Lunar ISO.
[01:26] <arraybolt3> https://i.imgur.com/YGETP90.png
[01:26] <arraybolt3> The title bar is all wonky.
[01:33] <teward> any chance the fact that Firefox is now a snap on every flavor has something to do with it?
[01:33] <guiverc> teward, all having snap'd firefox isn't new; been that way since jammy
[01:33] <teward> ye but weird things happen with snaps from release to release :P
[01:35] <guiverc> there is i suspect a recent change... having issues with firefox on box to my left..
[01:35] <guiverc> box to my left just had openbox crash....   (one I reported didn't have issue before..)
[01:37] <guiverc> that box had qterminal only in F11; not a snap package
[01:39] <arraybolt3> Just did a test installation. The fact that possibly Snap-related Openbox crashes and Firefox weirdness with the theming are happening at the same time, that doesn't feel like a coincidence.
[01:39] <arraybolt3> (btw we need some sort of "Express Installation" coolness like what exists for Windows and Ubuntu Desktop to be a thing for Lubuntu too :P)
[01:40]  * guiverc concurs given issues on box to my left.. no issues on this (my primary) box outside of openbox here though
[01:48] <arraybolt3> Oddly the list of preinstalled snaps on the latest Lubuntu Lunar exactly matches the list on a Kubuntu Jammy installation.
[01:49] <arraybolt3> I guess I'm going to start by reporting the Firefox bug and we'll see what happens from there.
[02:05] <arraybolt3> https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/2011758
[02:05] -ubottu:#lubuntu-devel- Launchpad bug 2011758 in snapd (Ubuntu) "Firefox is ignoring Lubuntu's theme settings entirely" [Undecided, New]
[09:37] <arraybolt3> @kc2bez: Right, but up until just recently, the title bar still looked Lubuntu-y. Now it looks... not.
[09:38] <arraybolt3> Chromium looks right. VSCode looks right. Firefox is the only offender.
[09:41] <arraybolt3> It's frustrating that this had to happen *after* User Interface Freeze, otherwise we might have been able to try and make a Snap to fix it possibly.
[09:41] <arraybolt3> But whatever. There's a bug filed, hopefully it will get input. If nothing else we'll live with a weird Firefox this cycle.
[17:56] <Eickmeyer[m]> FWIW, UIF hasn't actualy taken place yet (email was premature). Furthermore, freezes don't apply to bugs.
[17:58] <Eickmeyer[m]> Best way to make Firefox integrate well is to make sure there's an equivalent theme in the gtk-common-themes snap.
[17:59] <Eickmeyer[m]> Firefox needs it anyway, so no sense in being anti-gtk on this one.
[18:11] <arraybolt3> Eickmeyer[m]: I thought UIF was yesterday according to the timeline?
[18:11] <arraybolt3> Er, no, today. https://discourse.ubuntu.com/t/lunar-lobster-release-schedule/27284 But still, yeah we could try and help fix it.
[18:12] <Eickmeyer[m]> Freezes don't actually take place until an email is sent out. This one is an exception because it was premature.
[18:12] <arraybolt3> Huh. Will file that mentally for future reference.
[18:13] <Eickmeyer[m]> See discussion in #ubuntu-devel and on ubuntu-devel@ ML.
[18:14] <arraybolt3> Jjust saw it.
[18:19] <arraybolt3> Anyway, I might be able to work on that later, but for now I'm mostly concerned with Openbox weirdness. Gonna do some debugging and hopefully report on our private bug with results.
[18:36] <arraybolt3> This is weird, but it looks like the last calamares-settings-ubuntu upload isn't being grabbed?
[18:37] <arraybolt3> 23.04.5 is on the ISO, 23.04.7 is in LP and published. Hmm.
[18:37] <arraybolt3> Probably will pass with time then. If it's still not getting pulled in tomorrow, I'll look more closely.
[18:38] <arraybolt3> Ah, I see it, the daily images aren't building. I think that's what Eickmeyer was pointing out in -flavors.
[18:39] <arraybolt3> er, no, that was RikMills.
[18:39]  * arraybolt3 gets confused, then takes a detour to fix our ISO not building
[18:39] <Eickmeyer> Yeah, it was Rik. All flavors need to update that. However, having that other snap seeded probably isn't a bad idea for theming reasons.
[18:40] <Eickmeyer> But, the ISOs not building was another issue too (two issues, really).
[18:40] <Eickmeyer> vorlon fixed that last one.
[18:41] <arraybolt3> If that has a theming effect, this may be the way to fix our Firefox weirdness.
[18:41] <arraybolt3> OK, I'll update the seed and meta, then hopefully respin the ISO once the meta publishes.
[18:42] <Eickmeyer> Do you set a gtk theme anywhere at all?
[18:42] <arraybolt3> I have no clue :P
[18:59] <arraybolt3> And down the rabbit hole I go :P now I have to install and set up LXD in order to get a Lunar container to use for updating the lubuntu-meta package :P
[18:59] <arraybolt3> Anyway, seed updated.
[19:28] <Eickmeyer> vorlon just got the seeds building again, he forgor something last night.
[19:32] <arraybolt3> Nice, then hopefully the update I'm running now will work.
[19:35] <arraybolt3> lol, I just realized I'm trying to update a metapackage when the seed change I made was a snap. Well, hey, there were some changes to the metepackage anyway so I guess it was overall positive.
[19:37] <arraybolt3> Anyway, I guess I'll keep an eye on the seed in ubuntu-archive-team.ubuntu.com and then respin once that's updated.
[19:37] <Eickmeyer> Yeah, you don't need to update the metas if you change a snap in the seed.
[19:38] <arraybolt3> When I ran the update script, it did pull in some things related to riscv64 and armhf. Since there are things to be updated, I'm thinking about pushing it, but I'm not sure if that would violate Feature Freeze?
[19:39] <arraybolt3> Stuff like "Added libreoffice-writer to desktop-recommends [riscv64]" and "Removed fwupd-signed from desktop-recommends [armhf]".
[19:39] <Eickmeyer> No, it wouldn't. That's perfectly fine to do, means there were changes made. Changes aren't necessarily features.
[19:40] <arraybolt3> Makes sense. And I guess having LibreOffice present on riscv64 now is a good thing (if there is anyone out there who actually installs lubuntu-desktop on their riscv64 boards).
[19:41] <Eickmeyer> Dependencies getting refreshed and stuff getting updated in metas doesn't mean you've added a new feature, it just means changes were made that make changes in the metas.
[19:41] <arraybolt3> +1
[21:42] <arraybolt3> OK, the seed change happened, I *think* I just triggered a rebuild though I'm not entirely sure :P so we'll find out.
[21:45] <arraybolt3> Uh... actually...
[21:45] <arraybolt3> Eickmeyer: How on earth do you request a rebuild of an ISO? I'm looking at the admin page on the ISO tracker and see a bunch of scary buttons that it looks like I probably shouldn't press.
[21:46] <arraybolt3> I *think* I'm supposed to click the Builds tab, check the Lubuntu Desktop amd64 box, enter a version number of 20230314.1, and then click "Add these builds to the tracker", but I don't know if that's right.
[21:47] <RikMills> you don't do that!
[21:47] <arraybolt3> Well good thing I didn't do it :D
[21:47] <RikMills> go to http://iso.qa.ubuntu.com/qatracker/milestones/441/builds
[21:48] <arraybolt3> Yeah, I see it
[21:48] <RikMills> tick the checkbox next to the lubuntu amd64 build item
[21:48] <arraybolt3> Ohhhhhh. I didn't even notice those checkboxes :P
[21:48] <arraybolt3> And *then* use "Request a rebuild"?
[21:48] <RikMills> then use the menu at the bottom of the page to request a rebuild
[21:49] <RikMills> yep
 ooh i see that too xD
 nice
 *bonks arraybolt3 for no reason*
[21:49] <arraybolt3> Got it. The first thing I did was use the button expecting that it would ask me what ISO to rebuild, and then I stared at the page in confusion when it appeared to do nothing...
[21:49] <arraybolt3> (The button at the bottom of the screen for requesting rebuilds)
[21:50] <arraybolt3> There, that did what I hoped.
[21:50] <arraybolt3> RikMills: Thank you!
[21:50] <RikMills> I am not sure if lubuntu-dev will give you perms though
[21:50] <arraybolt3> I'm in Lubuntu Council, and therefore also in lubuntu-product-managers, so it let me do it.
[21:51] <RikMills> arraybolt3: ah yes. says 'rebuilding' next to the lubuntu entry now
[21:51] <arraybolt3> (I figure a rebuild to test a fix for a totally broken ISO is a good thing.)
[21:52] <arraybolt3> Thanks for bailing me out of that, I felt like I was holding a loaded gun and had no clue where the safety was, how to fire it, or what it was pointed at XD thus why I asked for help
[21:54] <RikMills> there is one quirk with this though. if the livefs fails on a build retriggered by this, then often requesting another one will not work until after the build from the normal cron job has run again
[21:55] <arraybolt3> Oh, weird. So basically, if the cron job fails, I get one shot, and if that fails I have to wait till tomorrow for it to actually work?
[21:55] <Eickmeyer> I'm able to request a rebuild as a result of being in ~edubuntu-release and ~ubuntustudio-release, but only for those images.
[21:55] <Eickmeyer> arraybolt3: That's correct, but only due to a bug in the system.
[21:55] <RikMills> arraybolt3: seems to work like that
[21:55] <RikMills> yes it is a bug
[21:56] <arraybolt3> Got it. Here's hoping that the Snap change does the trick then.
[21:56] <teward> i'm indirectly joined to the testcase team/group so i think i have access to everything
[22:02] <RikMills> it's building the squashfs, so looks like it will succeed :D
[22:02] <arraybolt3> \o/
[22:03]  * arraybolt3 hopes it doesn't spit out a blackened lump of charcoal
[22:04] <arraybolt3> Says "successfully built" woot!
[22:05] <arraybolt3> RikMills: Where do you see it building the squashfs? I can see the livefs build logs but not sure what logs you're looking at.
[22:06] <RikMills> arraybolt3: you know when you look at a running build and it shows you a short part of the current build log?
[22:07] <RikMills> when I looked at that I just happend to do it at the time when it said it was making the squashfs
[22:07] <arraybolt3> Ah.
[22:07] <arraybolt3> OK then we're looking at the same file.
[22:11] <arraybolt3> Woot, we have a new ISO!
[22:12] <arraybolt3> Aaaand... all of the links are 404'ing. Guess some patience is required.


[00:01] <ompaul> nickellery, never saw your nick before - how long have you been on IRC?
[00:01] <ompaul> or at least never noticed it
[00:03] <nickellery> ompaul: I'm not overly active, but I have been quite recently
[00:04] <ompaul> ack
[00:11] <PriceChild> jussi01: could you +i ubottu and join #ubuntuforums? 8-)
[00:12] <Jucato> ubottu: join #ubuntuforums
[00:12] <Jucato> hm..
[00:12] <Jucato> ubottu: join #ubuntuforums
[00:12] <Jucato> bah!
[00:14] <Jucato> sorry PriceChild, seems like I've been removed from the admin list for ubottu (btw, it's +i already)
[00:15] <PriceChild> Jucato: I don't think it is..
[00:15] <PriceChild> Jucato: I'm no god on this network yet see it in a few channels I'm not in afaict..
[00:16] <PriceChild> Jucato: maybe you should try identifying to the bot? ;) its been restarted since you last did most probably
[00:16] <Jucato> I'm identified, but not admin anymore... anyway. gtg
[00:16] <Jucato> [Whois] ubottu is an identified user
[00:16] <PriceChild> Jucato: i meant identified to ubottu, not nickserv
[00:16] <PriceChild> have fun
[00:18] <PriceChild> nickellery: people are invited to the ubuntu-irc team on launchpad "after observing the sustained positive contribution of an operator in one or more Ubuntu channels." ie you become an op somewhere, *then* join that team.
[00:19] <PriceChild> that quote didn't fit in as I meant it to... should be "after the irc council has observed"
[00:20] <stdin> ubottu: join #ubuntuforums
[00:21] <stdin> Jucato: you should be able to make it join/part now too
[00:23] <PriceChild> !test
[00:24] <jdong> !jdong
 jdong: yes, but you're FULL OF CRACK!
[00:24] <jdong> heh :)
[00:24] <jdong> always keep the most important factoids :)
[00:27]  * jdong gives up after 5 tries of making the bot say an innuendo
[00:27] <jdong> today's just not my day
[00:28] <jdong> there we go.
[00:28] <jdong> and I'm amused for the day
[02:14] <Jucato> stdin: um.. ok... thanks...
[02:15] <Jucato> PriceChild: oh I confused +i w/ identify... sorry
[02:15] <stdin> Jucato: we cleared out the "everyone is jussi" thing because it was interfering with some plugins
[02:15] <Jucato> waaah? I'm no longer jussi01? that sucks ;(
[02:15] <stdin> @whoami
[02:16] <stdin> neither am I :)
[02:16] <Jucato> @whoami
[02:16] <Jucato> pfft
[02:16] <jdong> that's doubleplusjucato to you ubottu
[02:22] <Amaranth> @whoami
[02:23] <Amaranth> uh oh
[02:23] <Amaranth> jussi01: Either I don't have an account or I forgot my password :/
[02:23] <tritium> Hello, Amaranth.
[02:23] <Amaranth> Also, can someone give me back access in +1 now? :)
[02:23] <Amaranth> hey tritium
[02:24]  * tritium needs access to +1 as well
[02:27] <nalioth> tritium: um, you _have_ access
[02:28] <tritium> Yeah, sorry, my bad.
[02:28] <tritium> I had been kicked out, and assumed I had lost it.
[02:29] <tritium> So does Amaranth, for that matter.
[02:29] <nalioth> no, amaranth kept rejoining and seveas pulled his acl entry
[02:29] <Seeker`> can I have access in some channels? I dont have enough to abuse my power in atm :P
[02:30] <tritium> nalioth: *shrug*, that's not what chanserv told me
[02:30] <stdin> Amaranth: try @login ?
[02:30] <bazhang> @whoami
[02:30] <bazhang> ;]
[02:31] <Amaranth> @whoami
[02:31] <Amaranth> ah, i was trying @identify
[02:31] <stdin> that only works when you know the pass ;)
[02:32] <stdin> the passwords are random (if I read the script right)
[02:32] <Amaranth> thanks nalioth
[02:32] <Amaranth> and stdin :)
[03:03] <eboyjr> Someone should remove the !anything factoid.
[03:04] <eboyjr> Because when you type !blah, It says Factiod blah not found, not I dont know about blah.
[03:04] <eboyjr> Or at least change it
[03:10] <stdin> maybe the default "I don't know" reply will be changed to what it was with ubotu, I'd rather not delete !anything just yet
[03:12] <wgrant> !anything
[03:13] <eboyjr> !notafactoid
[05:08] <eboyjr> What is the command for ubottu when people aren't saying who they are talking to?
[05:08] <eboyjr> !who
[05:08] <eboyjr> Okay, thanks, bye
[06:16] <bazhang> the ubotu factoids page seems to be missing
[06:31] <nalioth> bazhang: yeah, everything hosted in the netherlands can be expected to be that way
[06:31] <bazhang> thanks nalioth
[07:01] <eboyjr> Error: There are no larts in my database for #ubuntu-offtopic.
[07:02] <eboyjr> There needs to be some.
[07:02] <tonyyarusso> eboyjr: Our bots do not have the capacity for games right now.  Frankly, that plugin shouldn't even be awake and responding.
[07:03] <tonyyarusso> I wish we could, but just don't have the resources at the moment.
[07:03] <eboyjr> I understand.
[07:03] <eboyjr> Is that why ubotu is replaced with ubottu?
[07:04] <tonyyarusso> Well, it's a long story of insufficient botness and administrative problems.  The name change is just one of the chapters, and will likely happen more.
[07:05] <eboyjr> lol: botness
[07:05] <eboyjr> Okay

[10:04] <Myrtti> remember that factoid that Lynoure suggested to have about the gethostname() thing with sudo?
[10:05] <Myrtti> I think that although that bug number cant be inserted to the rootsudo factoid, we need some factoid for the issue
[11:33] <AfroRowan> SWAT... Ben je er ?
[12:07] <SWAT> AfroRowan: what's up?
[12:12] <bazhang> AfroRowan: do you have an issue?
[12:15] <bazhang> !idle | AfroRowan
[12:16] <SWAT> bazhang: I'm wondering about that myself.
[12:17] <bazhang> AfroRowan: if you have no pressing issues, please depart the channel
[12:20] <bazhang> SWAT: he is away
[12:21] <SWAT> bazhang: I don't know him and atm don't know what he needs me for. He basically asked in dutch "Are you there?
[12:23] <SWAT> AfroRowan: if you have any pressing issues (operator related), please contact me (you may PM me).
[12:23] <SWAT> that should suffice
[12:24] <bazhang> SWAT: should remove him? he has been idling for nearly an hour here
[12:26] <SWAT> bazhang: if I can be honest, I don't care atm. If there was anything pressing, he should've included that in his opening statement. He doesn't bother anyone, so I let him idle a bit (give him time to get back and read the messages. He can always be removed at any given time)
[12:27] <bazhang> SWAT: he is online and speaks english perfectly well
[12:29] <PriceChild> bazhang: heard of him before he entered this channel?
[12:29] <bazhang> PriceChild: seen him in #ubuntu before yes
[12:30] <SWAT> go right ahead then
[12:33] <stdin> for those that care, factoid web database is up now http://jussi01.com/web/factoids.cgi
[12:34] <bazhang> PriceChild: should he be removed?
[12:35] <PriceChild> bazhang: I don't think there's any pressing reason atm.
[12:35]  * PriceChild has a dig around.
[12:35] <bazhang> okay thanks PriceChild
[12:36] <PriceChild> Seems like he's banned in #ubuntu-nl
[12:37] <PriceChild> So when he returns, point him to wfh
[12:38] <SWAT> will do
[13:23] <AfroRowan> Hey SWAT, bazhang... i was downstairs we had visitors... So... But anyway, what pricechild said 'bout i am banned at #ubuntu-nl is true
[13:23] <AfroRowan> i thought it was just an temporarily ban but im banned now for like 2 dayz...
[13:24] <AfroRowan> and i have an issue with my ubuntu and i can't even ask it there :(
[13:24] <bazhang> AfroRowan: aha; well in 2 days time you should talk to wfh
[13:25] <AfroRowan> yeah but wdh isnt in any channel of ubuntu that i visited now
[13:25] <AfroRowan> not even in this one
[13:25] <SWAT> AfroRowan: I will unban you, but if you fall back to your old habits...
[13:26] <stdin> for loco channels (the -xx ones) you usually ask in #ubuntu-irc
[13:26] <AfroRowan> well, i wont i learned my lessons now
[13:29] <PriceChild> Cool, anything else we can help you with AfroRowan?
[13:29] <PriceChild> Thanks SWAT.
[13:29] <AfroRowan> No thanks, im fine now :)
[13:30] <SWAT> PriceChild: np
[14:26] <ompaul> bazhang, ping
[14:26] <ompaul> see pm
[15:14] <ompaul> LjL, best bug of the week: <FloodBot1> ubottu: Please don't flood, use http://paste.ubuntu.com to paste, don't use Enter as punctuation.
[15:15] <Hobbsee> hah
[15:19] <bazhang> ompaul: got the cloak thanks
[15:19] <ompaul> bazhang, you sure I don't see it
[15:20] <bazhang> ompaul maybe not in the chat window but in all the channel windows it shows up as unaffiliated
[15:20] <ompaul> bazhang, just a sec
[15:21] <stdin> [bazhang] (n=bazhang@unaffiliated/bazhang): B. A. Zhang
[15:21] <ompaul> good
[15:21] <bazhang> thanks again
[15:50] <jpatrick> hi BunnyRevolution, how can we help?
[15:51] <Daviey> jpatrick:  -!- BunnyRevolution [n=supybot@2 <------
[15:52] <jpatrick> Daviey: ctcp version it and you get chatzilla
[15:52] <Daviey> !
[16:06] <Seeker`> BunnyRevolution keeps on joining here and then just parting without saying anything
[16:06] <Seeker`> but talks in ##club-ubuntu
[16:22] <Seeker`> BunnyRevolution: hello?
[17:12] <stdin> it's a "real" person, was active in #k yesterday, but I have no clue why they keep joining/parting
[17:12] <stdin> and ignoring question about why
[17:13] <jdong> Seeker`: the<EMAIL_ADDRESS>tells me that it probably won't talk to you :D
[17:13] <stdin> jdong: it's not a bot
[17:13] <jpatrick> jdong: and it talks in other channels?
[17:13] <jdong> odd
[17:15] <Seeker`> jdong: it talks in other channels, I have seen it talk in ##c-u
[17:15] <jpatrick> "An access level of [10]" :-/
[17:20] <Nafallo> why did I read attack level :-P
[17:30] <bazhang> I have a theory.
[17:33] <stdin> stop building the suspense ;)
[17:34] <bazhang> have to wait until the rbt departs :)
[17:37]  * bazhang points to the bunny -->
[17:41] <Seeker`> bazhang: anything you say in here appears in the logs anyway
[17:41] <bazhang> Seeker`: oh right. d'oh!
[18:02] <Myrtti> hejssan allihopa
[18:03]  * jpatrick wonders how one prounces that
[18:43] <ompaul> !idle | BunnyRevolution
[18:43]  * ompaul looks tough the list - I know the rest
[18:44] <ompaul> spinning bunnies on a stick
[18:44] <ompaul> woops said that wrong
[18:44] <ompaul> spinning rabbits on a stick
[18:47] <ompaul> anyone know what #ubuntu-ph is?
[18:47] <gnomefreak> nope maybe locale channel?
[18:47] <Myrtti> philippines? /me shrugs
[18:47] <JonathanD> wc
[18:48] <bazhang> aye phillipines
[18:48] <ompaul> ahh
[18:48] <gnomefreak> ahh i wasnt sure what ph was :(
[18:48] <gnomefreak> other than acid/base scale
[18:48] <ompaul> cos the only ip sharing with that bunny is an ip for an Ahmuck
[18:48] <ompaul> always with the supybot
[18:49]  * gnomefreak the only moron that answered the email on the ML ;)
[18:51] <ompaul> bazhang, Seeker`  a person can log into a bot and "talk though it"
[18:52] <ompaul> nalioth, that appears to be a bot that is not registered in accordance with freenode guidelines about having bots on the network (if you want a complaint)
[18:53] <bazhang> ompaul: that answers a lot of question then
[18:53]  * ompaul pokes nalioth in the cloak
[18:53] <ompaul> hehehe
[18:53] <gnomefreak> who + where is bot?
[18:53] <ompaul> I booted it
[18:53] <Seeker`> ompaul: if it is a bot, whoever controls it seems to spend a lot of time talking through it
[18:53] <Seeker`> gnomefreak: BunnyRevolution
[18:53] <gnomefreak> that bunny
[18:53] <bazhang> bunnyrevolution gnomefreak
[18:53] <gnomefreak> oh damn
[18:53]  * gnomefreak hates bots :)
[18:54] <ompaul> Seeker`, perhaps but it is a way to have a single connection 24/7 to irc and then be able to log in and out and do stuff based on materials found there - as in whatever you can think of doing with data in IRC
[18:55] <Seeker`> ompaul: Just in the same way that irssi + screen can
[18:55] <Seeker`> 3
[18:55] <Seeker`> woops
[18:56] <ompaul> Seeker`, yes
[18:56] <ompaul> Seeker`, but then again the bot can be made do things most likely easier than irssi can
[18:56] <ompaul> but then they both are just calling scripts
[18:56] <Myrtti> lies
[18:57] <Myrtti> I've had an irssi running as an auto-opper for years
[18:57] <Myrtti> also handling situations that require silencing the channel with +m
[18:57] <ompaul> Myrtti, not the kind if nutty stuff I am thinking of
[18:58] <ompaul> Myrtti, but lets leave that for another day - it was nice today in park walking around and looking at the trees
[19:00] <ompaul> the clouds were thick but moving fast so there was a lot of light changing effects and thus many fantastic shades as leaves went from some kind of medium green in the shade to translucent objects almost glowing as the sun whipped its photons though the filter that was these leaves and left one with quite a pretty picture
[19:00] <ompaul> it was nice
[19:00]  * ompaul reminds self that this is not -ot
[19:20] <jussi01> Hello all!
[19:21] <ompaul> hello 1
[19:21] <Myrtti> hello luv
[19:22] <bazhang> Hi jussi01!
[19:22] <jussi01> heya :D
[19:22] <bazhang> nice factoids thanks jussi01
[19:22] <jussi01> bazhang: ?
[19:23] <bazhang> the link you gave--the new home jussi01
[19:23] <jussi01> oh, yeah. the bot runs from my server, so makes sense
[19:24] <bazhang> great to see the bot back
[19:24] <Myrtti> should we revise the bot factoid?
[19:24] <Myrtti> with the link to the factoid database
[19:24] <ompaul> !bot
[19:24] <ompaul> not just yet
[19:25] <ompaul> I think wait until LjL and PriceChild are here to suggest a form of words and them Pici can factoid smith it ;-)
[19:25] <ompaul> !pici
[19:26] <Myrtti> just as long we all remember the !-bot
[19:26] <Myrtti> !-bot
[19:26] <ompaul> ack
[19:27] <ompaul> I think the nick is going to migrate to the new bot at some stage
[19:27] <Myrtti> I hope not
[19:27] <Myrtti> actually perhaps it would be better if we do NOT include the url
[19:28] <ompaul> Myrtti, the original bot had its name robbed
[19:28] <Myrtti> since ubottu's supposed to be only a temporary solution
[19:28] <ompaul> iirc ;-) well hijacked or some such
[19:28] <ompaul> well lets see what happens
[19:29] <Myrtti> well I certainly hope ubottu's not going to be a longstanding solution
[19:29] <Myrtti> but we'll see
[19:30] <jussi01> oh, be kind to it...
[19:31] <Myrtti> I love it dearly
[19:31] <Myrtti> but I wish canonical or some other official instance would take care of the core bots
[19:48] <PriceChild> Myrtti: talks have begun about that
[19:48] <Myrtti> PriceChild: I know
[20:05] <jrib> bazhang: why so wide a ban?
[20:05] <bazhang> jrib: did you see the picture
[20:06] <jrib> bazhang: no, but I'm just asking why the "+b<EMAIL_ADDRESS>instead of a specific address
[20:06] <bazhang> jrib: did I do wrong?
[20:07] <jrib><EMAIL_ADDRESS>would catch just ubuntuG.  *.cg.shawcable.net matches more people
[20:07] <ompaul>  *.cg.shawcable.net" should be<EMAIL_ADDRESS>[20:07] <ompaul><EMAIL_ADDRESS>[20:08] <bazhang> so lift it and then change to the new one?
[20:08] <ompaul> bazhang, I fixed it look a the change ;-)
[20:08] <jrib> ompaul's got your back :)
[20:08] <bazhang> thanks so much guys ;)
[20:08] <ompaul> bazhang, you'll get there (sooner than you imagine)
[20:12] <jussi01> <sif
[20:12] <jussi01> gah
[20:13]  * jussi01 sigh's
[20:14] <jussi01> PriceChild: see ~10 mins ago in #kubuntu for a radom fujisan sample.
[20:29] <nalioth> jussi01: are you on the ubuntu irc mailing list?
[20:29] <nalioth> who else runs a bot for Ubuntu ?
[20:29] <jussi01> nalioth: yes I am. I just saw it ~? hor ago, havent had time to reply yet
[20:31] <Myrtti> nalioth: except you and LjL?
[20:32] <Seeker`> I'm responsible for mootbot, if thats worth anything
[20:33] <jussi01> stdin: has one, but its more for testing purposes iirc.
[20:33]  * gnomefreak tried that but failed badly so no more bots for me
[20:34] <stdin> I think it'd explode if it went into #ubuntu, my server's getting old
[22:37] <Amaranth> great way to start intrepid, some X breakage :)
[22:37] <Amaranth> that'll scare off the newbie
[22:37] <Amaranth> +s
[22:37] <Seeker`> Amaranth: ?
[22:37] <Amaranth> libxfont1 in intrepid breaks X
[22:37] <Seeker`> I thought the repos weren't open until after UDS
[22:38] <Amaranth> no, they've been open a couple days now
[22:38] <Amaranth> libxfont1 1:1.3.2-1 == bad
[22:40] <Amaranth> !info libxfont1 intrepid
[22:40]  * Amaranth is sad
[22:40] <Amaranth> no intrepid support here either :P
[23:06] <Mez> !ping
[23:06] <Mez> hmmles
[23:08] <ompaul> !-ping
[23:12] <Amaranth> ompaul: that just shows who set it originally
[23:12] <Amaranth> it used to say "pong!"
[23:12] <ompaul> Amaranth, yea
[23:12] <Amaranth> then i made it say "ping: unknown host"
[23:13] <Amaranth> then someone made it say what it does now
[23:13] <Amaranth> !test
[23:19] <PriceChild> jussi01: thanks for the ping earlier btw.
[23:22] <Myrtti> no test is "OH NO THE IT TURNED BLUE!"
[23:22] <Myrtti> s/THE//
[23:23] <Amaranth> !test
[23:23] <Myrtti> iz rilly too tired, riiiilly riiilly goz to bed, shuts eyz and siiz pictahs of kyyyuuuut linux geeks.
[23:23] <Amaranth> !no test is <reply> OH NO IT TURNED BLUE!
[23:23] <ompaul> chehers
[23:23] <Amaranth> !test
[23:23] <jdong> thats what she said!
[23:23]  * Amaranth likes that one
[23:24] <ompaul> na we want something more like
[23:24] <ompaul> sorry we have no results yet call back in a week
[23:25] <Myrtti> congratulations, you'll be a parent of the cutest little FLOSS project... written all in Haskell.
[23:25] <ompaul> hahaha
[23:25] <Myrtti> lisp?
[23:25] <ompaul> Myrtti, SLEEP
[23:25] <Myrtti> or ada
[23:25] <Myrtti> yes daddy
[23:25] <ompaul> hehehe
[23:26] <Myrtti> /me shuts the computer without checking any bright yellow pm's :-P
[23:30] <jdong> ALL good programs are written in Java!
[23:31] <ompaul> so the bot does not know me
[23:38] <ompaul> jdong, you are wrong
[23:38] <ompaul> jdong, but you already know that
[23:38] <ompaul> jdong, what are we to do with you :)


 How one may get rid of screen saver (via CLI)? It is really irritating on VMs.
 (I also opened https://askubuntu.com/questions/1387389/how-can-i-get-rid-of-a-screensaver-on-lubuntu-20-04-using-cli )
 How to setup fingerprint in lubuntu lxqt if fingerprint is listed on fprint?
[12:23] <guiverc> @matkoniecz, and I gave a response on the askubu  (~an hour ago)
 Thanks! I will look for xscreensaver config (started search for files with xscreensaver in ~ for start)
[19:22] <can> all of these users are human or bots?
 We are human
[19:24] <can> glad to hear that. i am new on linux universe. can i get support from humans here ? if i need ?
[19:25] <oerheks> see topic
 is there any way to install ms office fonts on lubuntu. there was a way to install it on ubuntu
 /topic@lubuntu_bot
 /topic@lubuntu_bot
[19:51] <oerheks> ttf-mscorefonts-installer does that, it is part of the lubuntu-restricted-extras package
[19:51] <Maik> sudo apt install ubuntu-restricted-extras which should pull in the ms core fonts
[19:52] <can> thank you so much. if i copy these commands does it works ?
[19:53] <oerheks> you might want to reboot after that, yes
[19:54] <can> thank you i will


[00:44] <sadmac> Keybcz: https://code.launchpad.net/~cjdahlin/upstart/sadmac
[00:45] <sadmac> New event_pending_handle_jobs (with some misc. helpers in tow). It passes the unit tests


[15:16] <h00k> bigbash: I'm looking through vSphere 5 notes, contemplating on planning an upgrade
[15:16] <h00k> bigbash: and migrating to a distributed vSwitch
[16:44] <bigbash> h00k, Is it pretty easy to upgrade from v4 to v5
[16:44] <h00k> bigbash: sure, but I have to convince the purchasing department an upgrade is worthy ;)
[16:45] <bigbash> lol
[16:45] <bigbash> it is always worth it
[16:47] <h00k> Yep.
[16:49] <bigbash> Did you see VMWare Project Octopus?
[16:50] <bigbash> like a dropbox but by vmware
[16:51] <h00k> No
[16:51] <h00k> I haven't seen it
[17:14] <bigbash> h00k, http://www.vmwareoctopus.com/
[17:16] <h00k> bigbash: I want that! Sweet!
[17:25] <h00k> bigbash: we were just talking about this, this is perfect.
[17:25] <h00k> or, needing something like it
[17:25] <bigbash> I signed up to hopefully get the tech preview
[17:26] <h00k> me too