[12:25] <cpaelzer> hi party people, I found that I get multiple warnings like these in my journal
[12:25] <cpaelzer> update-notifier.desktop[9661]: [9661:9661:1122/132442.703817:ERROR:page_load_metrics_update_dispatcher.cc(120)] Invalid parse_blocked_on_script_execution_duration 0.731 s for parse duration 0.636 s
[12:26] <cpaelzer> search for this leads me to chromium https://chromium.googlesource.com/chromium/src/+/66.0.3359.158/chrome/browser/page_load_metrics/page_load_metrics_update_dispatcher.cc#108 and probably anything that renders via it
[12:26] <cpaelzer> sadly even killing update-notifier (not yet restarting) makes this not go away
[12:27] <cpaelzer> Since Nov 15th I have that way picked up 583175 of such log entries which is a bit too frequent for my taste
[12:27] <cpaelzer> any suggestions what to check/restart/debug?
[12:29] <seb128> hey cpaelzer! Urg, that seems problematic indeed
[12:29] <cpaelzer> tracking the pid it is actually chrome itself, maybe update-notifier is a red herring
[12:29] <cpaelzer> restarting that ...
[12:30] <seb128> right, I do wonder what update-notifier has to do with that
[12:30] <cpaelzer> ok, restarting chrome has stopped the flood
[12:30] <seb128> I will check with Nathan (he doesn't seem to be on IRC atm)
[12:31] <cpaelzer> the puzzle I'd like to understand is why it reported that as update-notifier.desktop in the journal
[12:31] <cpaelzer> 0  1000    8559    7280  20   0<PHONE_NUMBER>2 do_pol Sl   ?          0:28  |   \_ update-notifier
[12:31] <cpaelzer> 4  1000    9661    9660  20   0 35126560 717728 do_pol SLl ?      395:06  |   \_ /opt/google/chrome/chrome
[12:31] <seb128> I would like to understand that as well
[12:32] <cpaelzer> I can see that 9661 was chromes pid and update-notifier was 8559
[12:32] <cpaelzer> but the log above says ... update-notifier.desktop[9661]
[12:33] <seb128> is systemd/journalctl getting confused about pids somehow?
[12:33] <cpaelzer> for what it is worth, this is reliable
[12:33] <cpaelzer> the new pid of chrome is this
[12:33] <cpaelzer> 4  1000 4100307    7049  20   0 34370744 444984 do_pol SLl ?        0:12  \_ /opt/google/chrome/chrome --origin-trial-disabled-features=WebGPU --restart
[12:33] <cpaelzer> and on restart it emitted some to the log
[12:33] <cpaelzer> Nov 22 13:29:20 Keschdeichel update-notifier.desktop[4100307]: [4100307:4100307:1122/132920.667640:ERROR:CONSOLE(1)] "Uncaught SyntaxError: Unexpected token '<'", source: chrome://version//about_version.js (1)
[12:33] <cpaelzer> so it declared itself as "update-notifier.desktop" again
[12:34] <seb128> cpaelzer, https://github.com/systemd/systemd/issues/28499
[12:34] -ubottu:#ubuntu-desktop- Issue 28499 in systemd/systemd "Some log messages reported with the wrong sender in the journal" [Open]
[12:34] <seb128> not much details which are of use there though
[12:34] <cpaelzer> could be it, yep
[12:35] <seb128> but it seems similar
[12:36] <seb128> so I guess the conclusion is that chrome is spamming your log and systemd for some reason matches the wrong pid for those messages
[12:37] <seb128> I will check with Nathan if he's aware of those log spams/if he knows of a workaround
[13:42] <cpaelzer> from journalctl -v it not only believes it is update-notifier
[13:42] <cpaelzer>     SYSLOG_IDENTIFIER=update-notifier.desktop
[13:43] <cpaelzer> but also groups it in the same scope
[13:43] <cpaelzer><EMAIL_ADDRESS>[13:43] <cpaelzer>     _SYSTEMD_USER_UNIT=app-gnome-update\x2dnotifier-8559.scope
[13:45] <cpaelzer> systemd-cgls lists chrome just there, under app-gnome-update\x2dnotifier-8559.scope
[13:46] <cpaelzer> so the question is how did it get there in the first place
[13:58] <lissyx> bandali, seb128, can you verify the build process ? https://bugzilla.mozilla.org/show_bug.cgi?id=1866057
[13:58] -ubottu:#ubuntu-desktop- Mozilla bug 1866057 in Testing "Snap upstream builds missing SourceRepository / SourceStamp" [--, New]
[13:59] <lissyx> I'm stretched thin those days, and this is making mozregression broken :(
[13:59] <lissyx> and we dont have access to the build dir from the launchpad builds to investigate what was done there
[14:00] <seb128> lissyx, I've no idea what SourceRepository and SourceStamp are and I'm also quite busy with other things
[14:00] <seb128> bandali, ^ could you perhaps check that?
[14:43] <KGB-X> tracker-miners ubuntu/jammy 9da215c Jeremy Bícha (41 files in 8 dirs) * Import Upstream version 3.3.3 * https://deb.li/iUBSh
[14:43] <KGB-X> tracker-miners ubuntu/jammy b2616de Marc Deslauriers (47 files in 10 dirs) * Import Debian changes 3.3.3-0ubuntu<IP_ADDRESS> * https://deb.li/lrkN
[14:43] <KGB-X> tracker-miners signed tags b010d86 Jeremy Bicha ubuntu/3.3.3-0ubuntu<IP_ADDRESS> * tracker-miners Debian release 3.3.3-0ubuntu<IP_ADDRESS> * https://deb.li/5bFg
[14:44] <KGB-X> tracker-miners ubuntu/jammy ab6071a Jeremy Bícha debian/gbp.conf * Branch for jammy * https://deb.li/3XXNl
[14:58] <KGB-X> tracker-miners signed tags ee9ed76 Jeremy Bicha ubuntu/3.4.6-0ubuntu<IP_ADDRESS> * tracker-miners Debian release 3.4.6-0ubuntu<IP_ADDRESS> * https://deb.li/qlyD
[14:59] <KGB-X> tracker-miners ubuntu/mantic 3717711 Jeremy Bicha * pushed 39 commits (first 5 follow) * https://deb.li/38mDz
[14:59] <KGB-X> tracker-miners ubuntu/mantic 3a46114 Carlos Garnacho NEWS meson.build * Release 3.4.5 * https://deb.li/HmGl
[14:59] <KGB-X> tracker-miners ubuntu/mantic 2176094 Jeremy Bícha (40 files in 7 dirs) * New upstream version 3.4.5 * https://deb.li/3R4jI
[14:59] <KGB-X> tracker-miners ubuntu/mantic f3f7b54 Carlos Garnacho src/libtracker-miners-common/tracker-seccomp.c * libtracker-miners-common: Add custom rules through a define * https://deb.li/97Gn
[15:00] <KGB-X> tracker-miners ubuntu/mantic 9aa5d26 Carlos Garnacho src/libtracker-miners-common/tracker-seccomp.c * libtracker-miners-common: Improve "bail out" error loading seccomp rules * https://deb.li/diZC
[15:00] <KGB-X> tracker-miners ubuntu/mantic 338a15e Carlos Garnacho src/libtracker-miners-common/tracker-seccomp.c * libtracker-miners-common: Add more seccomp rules * https://deb.li/31CoG
[15:00] <KGB-X> tracker-miners ubuntu/mantic ece14df Jeremy Bícha debian/gbp.conf * Branch for mantic * https://deb.li/NoME
[15:02] <KGB-X> tracker-miners signed tags 804f6b9 Jeremy Bicha ubuntu/3.4.6-0ubuntu<IP_ADDRESS> * Debian release 3.4.6-0ubuntu<IP_ADDRESS> * https://deb.li/i3lRe
[15:02] <KGB-X> tracker-miners ubuntu/lunar e390e68 Jeremy Bicha * pushed 35 commits (first 5 follow) * https://deb.li/2Nw7
[15:02] <KGB-X> tracker-miners ubuntu/lunar 3a46114 Carlos Garnacho NEWS meson.build * Release 3.4.5 * https://deb.li/HmGl
[15:02] <KGB-X> tracker-miners ubuntu/lunar 2176094 Jeremy Bícha (40 files in 7 dirs) * New upstream version 3.4.5 * https://deb.li/3R4jI
[15:02] <KGB-X> tracker-miners ubuntu/lunar f3f7b54 Carlos Garnacho src/libtracker-miners-common/tracker-seccomp.c * libtracker-miners-common: Add custom rules through a define * https://deb.li/97Gn
[15:02] <KGB-X> tracker-miners ubuntu/lunar 9aa5d26 Carlos Garnacho src/libtracker-miners-common/tracker-seccomp.c * libtracker-miners-common: Improve "bail out" error loading seccomp rules * https://deb.li/diZC
[15:02] <KGB-X> tracker-miners ubuntu/lunar 338a15e Carlos Garnacho src/libtracker-miners-common/tracker-seccomp.c * libtracker-miners-common: Add more seccomp rules * https://deb.li/31CoG
[15:03] <KGB-X> tracker-miners ubuntu/lunar b3a4619 Jeremy Bícha debian/gbp.conf * debian/gbp.conf: Update upstream-branch name * https://deb.li/3HlYd
[15:03] <KGB-X> tracker-miners ubuntu/mantic 14ca62e Jeremy Bícha debian/gbp.conf * debian/gbp.conf: Update upstream branch name * https://deb.li/V4rF
[15:04] <KGB-X> tracker-miners signed tags 228697d Jeremy Bicha upstream/3.3.3 * Upstream version 3.3.3 * https://deb.li/3NRT1
[15:04] <KGB-X> tracker-miners upstream/3.3.x 9da215c Jeremy Bícha (41 files in 8 dirs) * Import Upstream version 3.3.3 * https://deb.li/iUBSh
[15:04] <KGB-X> tracker-miners pristine-tar 757662d Jeremy Bícha tracker-miners_3.3.3.orig.tar.xz.delta tracker-miners_3.3.3.orig.tar.xz.id * pristine-tar data for tracker-miners_3.3.3.orig.tar.xz * https://deb.li/RLth
[15:05] <KGB-X> tracker-miners ubuntu/jammy 79d47d5 Jeremy Bícha debian/gbp.conf * debian/gbp.conf: Update upstream branch name * https://deb.li/3zoBc
[17:24] <lissyx> seb128, bandali, ok it looks to affect only nightlies, so I suspect it is because we are removing .hg directory
[17:24] <lissyx> I'm testing this right now
[20:40] <lissyx> bandali, https://github.com/canonical/firefox-snap/pull/38
[20:40] -ubottu:#ubuntu-desktop- Pull 38 in canonical/firefox-snap "Bug 1866057 - Force MOZ_SOURCE_REPO/CHANGESET on Snap Nightly" [Open]
[20:41] <lissyx> bandali, I'm runnign a build but I wont have time to test before tomorrow, if you can check on your side this patch
[20:41] <lissyx> bandali, verify in about:buildconfig, you should see a link to hg repo + rev (you can see it on beta/release)


[00:00] <lynorian> A few years now
[00:06] <metalbiker> sigh, my wifi signal is pretty weak back here in the bedroom. i'm going to have to relocate to the living room soon.
[00:07] <metalbiker> so you've been with the team for a couple years now? cool. i've been with it only since December. i used to be a part of the Tennessee Team when I lived there. but, that team wasn't very active.
[00:14] <lynorian> Yeah I can understand that
[01:54] <metalbiker2> anybody around?
[01:56] <lynorian> yes
[01:57] <metalbiker2> ok, cool. is the meeting still happening? i see part of the topic says that the next meeting is july 23rd.
[01:57] <pleia2> yes, it's happening :)
[01:58] <pleia2> er
[01:58] <metalbiker2> hey, pleia2. ok, cool.
[01:58] <pleia2> Agenda: https://wiki.ubuntu.com/CaliforniaTeam/Meetings/17July09
[01:59] <nhaines> Man, I totally did not finish trying to get WWIV BBS software working in lxc.
[02:00] <nhaines> Okay, meeting time!
[02:00] <metalbiker2> pleia2, yeah, i saw that earlier in the week. i just got thrown off by the topic.
[02:00] <metalbiker2> nhaines, awesome!
[02:01] <nhaines> #startmeeting
[02:01] <nhaines> #chair pleia2 lynorian
[02:01] <pleia2> yeah, sorry about the topic :)
[02:01] <metalbiker2> pleia2, it's ok.
[02:01] <nhaines> Welcome to the Ubuntu California meeting for July 9th!
[02:02] <nhaines> Despite the channel topic, which is probably my fault anyway.  :)
[02:02] <metalbiker2> hey there!! i finally got to show up on time!! :)
[02:02] <nhaines> Today's agenda is available at https://wiki.ubuntu.com/CaliforniaTeam/Leadership/2017
[02:02] <metalbiker2> nhaines, eh, no biggie
[02:02] <nhaines> metalbiker2: we're glad to see you.  :)
[02:02] <metalbiker2> nhaines: thanks!
[02:02] <metalbiker2> i'm very happy to be here
[02:03] <nhaines> We have one item on the agenda.  Before we get to that, though...
[02:03] <nhaines> #topic Upcoming events
[02:03] <pleia2> for the first time in over a year, we're having an Ubuntu Hour in SF this week https://lists.ubuntu.com/archives/ubuntu-us-ca/2017-July/002809.html
[02:03] <nhaines> \o/
[02:03] <metalbiker2> yay!
[02:03] <pleia2> on Wednesday evening, after which everyone is welcome to come over to the Debian Dinner nearby
[02:05] <nhaines> That sounds like a great way to spend Wednesday evening!
[02:05] <nhaines> And if you're in the southern part of the state, Ubuntu Hour Pasadena is meeting at Peets coffee as usual.  Afterwards you should check out the SGVLUG meeting at DuPars. https://www.meetup.com/Ubuntu-California/events/232986296/
[02:05] <pleia2> hope so :) at the very least we'll have a lot to talk about
[02:06] <metalbiker2> i'd love to come up and attend. and i agree nhaines!
[02:06] <metalbiker2> nhaines: awesome!
[02:07] <nhaines> #topic Announcements
[02:07] <nhaines> Does anyone have any general Ubuntu announcements?
[02:07] <metalbiker2> nhaines: i don't have anything, unfortunately. maybe soon.
[02:07]  * lynorian has nothing
[02:08] <metalbiker2> i may have an event to announce soon is all.
[02:09] <pleia2> metalbiker2: hope so!
[02:09] <pleia2> I'm coming down to Irvine next week, but nothing Ubuntu-y
[02:11] <nhaines> Oh yeah!  I should probably figure out something for you to do!  There's the Orange County Zoo that's cute.  :)  I'll get back to you on that.
[02:11] <metalbiker2> i'm going to be in Oregon next week. not ubuntu related.
[02:11] <pleia2> nhaines: indeed :)
[02:11] <nhaines> Well, it's the summer slump, so we'll see how things shape up as 17.10 gets baked.
[02:11] <nhaines> #topic Review Ubuntu California leadership nominations.
[02:12] <nhaines> Two weeks ago, we put out a call for leadership nominations here: https://wiki.ubuntu.com/CaliforniaTeam/Leadership/2017
[02:12] <pleia2> it was supposed to end 12 minutes ago, but we have no nominees /o\
[02:12] <pleia2> anarchy!
[02:12] <lynorian> I read the email then completely forgot about it :(
[02:13] <nhaines> This is the second time we've failed to raise adequate nominations for LoCo leadership.
[02:13] <pleia2> well, I didn't specify a timezone for 19:00
[02:13] <metalbiker2> lmao!! ANARCHY IS THE BEST!! no, just kidding. i got the email and desperately tried to get my nominations on that page but it wasn't working for me for some reason.
[02:14] <pleia2> it is troublesome that we have no one who wishes to stand for leadership
[02:14] <pleia2> (unless lynorian's comment means they do :))
[02:14] <nhaines> Response was flat, meeting attendance is limited, the mailing list is almost completely dead.
[02:14] <metalbiker2> *hangs head* do we get to nominate now or is it required to go through the nomination page?
[02:14] <nhaines> There starts to be a time when it might be better to think about the future of the LoCo.
[02:15] <pleia2> metalbiker2: I said people can just send nominations to me, so I'd be OK with now
[02:15] <lynorian> I have had less ubuntu time a lot this year
[02:15] <nhaines> metalbiker2: we'll have to extend the nomination period again, but you can contained myself or pleia2 to get on the page if the wiki just isn't working for you.
[02:16] <pleia2> nhaines: there is still interest here and there for some kind of existence, however slight, so I'm inclined to chug on if there's anyone remotely interested in helping us move along
[02:16] <metalbiker2> pleia2: so I can nominate now? I thought I sent you that email with my nominations but maybe I didn't.
[02:17] <metalbiker2> I'm highly interested in stepping up to the plate but I'm so afraid that I lack enough knowledge for it.
[02:17] <metalbiker2> nhaines: ok, sounds good.
[02:18] <pleia2> metalbiker2: I received one from you on friday, I'm sorry I didn't respond to your question about experience x_x
[02:18] <metalbiker2> pleia2: i really want our loco to continue. i've got some good ideas to help foster attention to it.
[02:18] <nhaines> I'm not suggesting we dissolve the LoCo this minute, but it's something to keep in mind.  Hopefully we can drum up more activity.
[02:18] <pleia2> I think a fresh face on the team would help, and we all started somewhere, I'd still be around to help out
[02:18] <pleia2> as I'm sure others would
[02:18] <nhaines> Yup, I'm not disappearing any time soon.
[02:19] <metalbiker2> nhaines: ok, i really want our team to be around forever. and i'm not disappearing anytime soon either. as long as i live i'll be here and fighting hard for us.
[02:19] <pleia2> :)
[02:19] <nhaines> metalbiker2: every bit helps.  :)
[02:20] <metalbiker2> if we can nominate now, i've got some in mind.
[02:20] <nhaines> It's also important to note that the LoCo Council and Community Council are having problems as well.  So it's not just us.
[02:20] <nhaines> pleia2: what do you think?
[02:20] <pleia2> I think it's fine
[02:20] <pleia2> happy to take metalbiker2's self-nomination now
[02:21] <pleia2> metalbiker2: are you able to edit the wiki page, or can you send me the info to update it?
[02:21] <metalbiker2> yes! i'd love to self-nominate myself if that's ok? i really feel up to the challenge!
[02:22] <pleia2> and if you can't edit, we'll make sure you get edit access (have to be in a special team on launchpad, or be an ubuntu member)
[02:22] <metalbiker2> pleia2: i think i can edit it. i'll have to look again to see. i've been having some wifi issues again. sigh.
[02:22] <pleia2> ok
[02:22] <nhaines> metalbiker2: thanks for volunteering!
[02:23] <metalbiker2> nhaines: you're welcome!! my experience lies in manufacturing committees and I was a prominent voice in both so i think i can do it. i've got some good ideas to help us out some more.
[02:24] <nhaines> pleia2: do you want to extend the nomination period or just take nominations here in the meeting?
[02:24] <metalbiker2> pleia2: sweet!! i'd love that! i'll look again after we get done with our meeting.
[02:24] <pleia2> metalbiker2: ok, thanks :)
[02:24] <pleia2> nhaines: I'm ok taking nominations here in the meeting, let's just say it's 1900 hawaii time ;)
[02:24] <nhaines> Ha.  :)
[02:25] <nhaines> Okay, in that case I nominate myself.
[02:25] <nhaines> Since the "wait until late so as not to spook other potential nominees" plan didn't work out.  :[
[02:25] <metalbiker2> nhaines: awesome!
[02:26] <metalbiker2> yeah, i was excited for this election to see who would be nominated and i even kept the pages open all the time and nothing. smh. i was just debating on myself was all.
[02:27] <nhaines> Well if you believe in yourself, there are people who will help as well.  :)
[02:27] <lynorian> yes
[02:27] <metalbiker2> nhaines: i definitely believe in myself and the help will be appreciated!
[02:28] <nhaines> lynorian: are you intereted in running?
[02:28] <lynorian> no my time for ubuntu has gond down quite a bit
[02:29] <pleia2> btw, since metalbiker2 is new and we will have an election this time, I'd be interested in a candidate blurb to the mailing list this time around
[02:30] <nhaines> pleia2: good idea!
[02:30] <pleia2> each nominee sending a quick email to the list about their background and ideas for the loco
[02:30] <pleia2> nothing fancy :) just so people know who you are
[02:30] <metalbiker2> pleia2: can you explain what that means. lol i'm usually a walking dictionary but that one is like, over my head. lol
[02:30] <metalbiker2> oh, you just answered my question. cool
[02:30] <pleia2> :D
[02:31] <nhaines> pleia2's good like that.  :)
[02:31] <nhaines> pleia2: last chance to get on this nice responsibility action!  ;)
[02:31] <metalbiker2> pleia2: cool! i'll do that!
[02:31] <pleia2> haha
[02:32] <metalbiker2> pleia2: lol
[02:32] <pleia2> I need some time to myself :)
[02:32] <metalbiker2> :D
[02:32] <metalbiker2> pleia2: copy that and understood.
[02:32] <nhaines> True!  I often wonder how you do it. :)
[02:33] <metalbiker2> my personal life is rather wide open at the moment and i need something to do so this is perfect.
[02:33] <nhaines> Okay, I think we'll wrap up the nomination period.  Do we want to change the voting period at this time or go with the current schedule?
[02:33] <pleia2> I think the current schedule is fine
[02:33] <metalbiker2> i'm good here, too.
[02:35] <pleia2> I'll set up the poll, and if nhaines and metalbiker2 can get their email off to the list sooner rather than later so people can be informed, that would be good :)
[02:35] <nhaines> Thanks so much for that.  :)
[02:35] <nhaines> #topic Other business
[02:35] <nhaines> Anything else before we wrap up?
[02:35] <metalbiker2> pleia2: cool! i'll be on it tonight actually!
[02:35] <pleia2> metalbiker2: yay!
[02:36] <pleia2> and do update the wiki page too, or send me info to update it ;)
[02:36] <metalbiker2> yeah, i'd like to say something before we wrap.
[02:36] <nhaines> The floor is yours.  :)
[02:37] <metalbiker2> i appreciate you all allowing me to be here. It's been a pleasure joining the team and I love our team.  :D
[02:37] <pleia2> thank you for helping us move forward!
[02:37] <metalbiker2> pleia2: my pleasure! i'm all about this!
[02:38] <nhaines> We're glad to have you, and we're looking forward to seeing you at events.  :)
[02:38] <metalbiker2> nhaines: i look forward to those as well!! I'm excited to come to them!
[02:39] <nhaines> Alright, thanks for coming!  We'll get the nomination page up and start voting soon.
[02:39] <nhaines> Our next meeting is, indeed, July 23rd!  Hope to see everyone there!
[02:39] <nhaines> #endmeeting
[02:39] <metalbiker2> COOL!  I should be back from Oregon by then.
[02:40] <metalbiker2> yes, thanks for doing the honors, my friend!
[02:41] <nhaines> My pleasure, unlike all the wrapup stuff.  ;)  But hey, at least the channel topic's all set!
[02:42] <metalbiker2> cool! looking forward to the next time!
[02:42] <nhaines> I've been working on retro computer stuff this month.
[02:42] <nhaines> By "retro" I mean late 80s/early 90s.
[02:43] <nhaines> A friend sent me a ton of old code I'd worked on, and the comments are pretty interesting.  Only on a personal level, mostly.  :)
[02:43] <metalbiker2> oh, goodness, now I feel old. aye aye aye. i was born in 1974.
[02:43] <nhaines> But I have a pretty nice working setup now to connect to BBSes.
[02:43] <metalbiker2> oh wow! you're talking about bulletin board services??!! man, that's nostalgic!!
[02:43] <pleia2> hehe
[02:44] <metalbiker2> i'd love to see that code, too. i don't know how to code but i'd love to learn how.
[02:44] <nhaines> Well it's all QuickBASIC code for DOS.  And some of it was lost in a crash!
[02:45] <metalbiker2> i've been trying to learn how to code in python. seems pretty cool.
[02:45] <nhaines> Naturally, it was the program that had the greatest utility that crashed.
[02:45] <nhaines> Python is lots of fun and a good place to start.
[02:45] <pleia2> ++
[02:46] <pleia2> python is the right mix of ease of learning (not that it's easy, no programming is) and getting you good experience with proper coding concepts
[02:47] <nhaines> I started reading The C Programming Language by Kernighan and Ritchie.  Need to keep on top of that.
[02:47] <metalbiker2> nhaines: oh jeez! DOS at that??!! *blinks hard* oh wow!
[02:48] <metalbiker2> nhaines: yeah, python seems to be the easiest when side by side to C#/C++ so I thought I'd start with it.
[02:49] <nhaines> Well, the reference Python interpreter is written in C, so Python has some of those assumptions.
[02:49] <metalbiker2> pleia2: cool! and i'm looking into going back to school to finish out my Bachelor's degree in Computer Science in programming. I've got a different kind of programming knowledge that's very specific and I want to further that education in actual computer coding.
[02:52] <metalbiker2> nhaines: i should check into that as well.
[02:53] <metalbiker2> man, i hope i didn
[02:54] <metalbiker2> oops, sorry. i was beginning to wonder if i lost my connection again. i'm sitting about 30 feet from my router and it gets kind of sketchy back here.
[02:54] <pleia2> hehe
[02:54] <metalbiker2> 'sup, cyphase? welcome!
[02:59] <metalbiker2> did i lose my connection again? ugh. bloody router.
[02:59] <nhaines> Nope, still here!
[03:00] <metalbiker2> okie dokie, cool!
[03:18] <metalbiker2> did we get adjorned or are we still discussing matters?
[03:23] <nhaines> We got adjourned at 19:39 when I said "#endmeeting"  :)
[04:05] <metalbiker> well, guys, I'm logging off for the night. I'll chat with you all later.
[18:16] <metalbiker> I'm here pleia2.
[18:17] <pleia2> :)
[18:17] <pleia2> once nhaines adds his name to the wiki I'll get the voting stuff together and send a mail to the list
[18:18] <metalbiker> ok, sounds good. i'll look forward to that.
[18:18] <metalbiker> do we have a high resolution image that I can use for those t-shirts? I can look around and see if I can find one.
[18:19] <pleia2> we have a vector image, I'll dig it up
[18:20] <pleia2> [B[B[B
[18:20] <pleia2> derp
[18:20] <pleia2> https://code.launchpad.net/~ubuntu-california
[18:20] <pleia2> all our team stuff is in there ^
[18:20] <pleia2> can dig into logos, that has the .svg images which you can open in inkscape to edit, or gimp to create a .jpg or whatever of whatever size you want
[18:21] <metalbiker> oh! sweet! i'll take a look! thanks!
[18:21] <metalbiker> ok, i'm pretty good at using gimp. that's usually my go to software for image work.
[19:44] <metalbiker> pleia2: i finally got those files. awesome graphics! now i can get these over to a local printer for some cool swag! i'd like to give everybody that's on the team a t-shirt, too.


[06:27] <Cheri703> Unit193: my work schedule may be changing in the next few weeks, will be working wednesday nights. At some point we can discuss whether monday nights might work for ubuntu hour
[06:32] <Unit193> As long as you are willing to do them, I'm willing (but not always able) to go! Monday would work for me, but I just wouldn't be able to get there as far as I can see, but I could be wrong
[06:52] <Cheri703> ok, we can work out logistics later on, or even perhaps a different location (though I do love my bacon turkey bravo).
[06:53] <Cheri703> this coming week is still good to go on wednesday for me, so we can discuss
[06:53] <Unit193> Heh, alright


[05:20] <Guest32933> hello, I would start chromium-browser in kiosk mode start lubuntu, how can we do?
[05:30] <xsacha> hi
[05:51] <lewellyn> xsacha: hi.
[05:51] <xsacha> hi
[07:46] <Gatis> Ooh no ban here :P
[07:46] <Gatis> ikonia: and here?
[07:52] <ikonia> Gatis: just leave
[07:52] <Gatis> ok you are not op here
[07:52] <ikonia> you're trying to cause a problem - don't
[07:52] <ikonia>  I certainly can be
[07:53] <ikonia> hence why I'm asking you not to cause a problem so I don't have to
[07:53] <Gatis> Then you would ban me
[07:53] <ikonia> (please)
[07:53] <Gatis> ikonia: no you can't ban me here
[07:54] <ikonia> I don't want to ban you
[07:54] <ikonia> hence why I'm asking you to not cause a problem
[07:54] <Gatis> you already banned me from #ubuntu, #xubuntu, #kubuntu
[07:54] <Gatis> Why not #lubuntu?
[07:54] <ikonia> I know this and it has nothing to do with this channel
[07:54] <ikonia> because you've not caused a problem yet
[07:55] <Unit193> Gatis: Drop it and you won't have to have a new ban.
[07:55] <lewellyn> we could all just /ignore and have the same net effect as a ban :P
[07:55] <Gatis> what has it to do with #ubuntu #xubuntu and #kubuntu?
[07:55] <Gatis> i joined #kubuntu and you baned me in second
[07:55] <Gatis> is that reason?
[07:55] <Gatis> ikonia: but you are not admin here
[07:55] <ikonia> stop it - this is your final warning
[07:55] <Gatis> ikonia: no you stop
[07:56] <Gatis> WHy you banned me in #kubuntu in seconds and not #lubuntu?
[08:12] <Sachiru> Okay, now I'm curious
[08:13] <Sachiru> May I know (if it's not against the rules) why he was banned in all the channels that he was banned in?
[08:13] <lewellyn> i personally don't care. he was being an ass. good enough for me.
[08:19] <xsacha> lewellyn: wait, why are you here?
[08:19] <lewellyn> i'm everywhere.
[08:19] <xsacha> can you help with my lubuntu woes?
[08:20] <lewellyn> maybe. maybe not. my crystal ball can't see the question.
[08:20] <xsacha> ok so all of the sudden (after an apt-get upgrade), opengl windows like Chrome no longer update their contents
[08:21] <xsacha> so i have to use LIBGL_ALWAYS_SOFTWARE=1 to get them to work
[08:21] <lewellyn> yeah. that's outside my scope :)
[08:21] <xsacha> my setup involves two gpus, so i tried DRI_PRIME=1 but that has the same issue
[16:29] <Gassho> redshift unable to get 'location' from "provider"
[16:29]  * Gassho throws a hissy fit >8c
[16:29] <Gassho> ww
[16:36] <switchtehbeat> 2 questions, my new gfx card is coming tomorrow, if I put it in my desktop, will lubuntu detect it auto? and 2nd question; how can I change how fast my mouse is??
[16:37] <holstein> switchtehbeat: well, the issue is, you cant really ask that definitively of lubuntu. its not up to lubuntu to support the device, its more about the device supporting linux
[16:38] <holstein> switchtehbeat: graphics drivers are *much* better in linux than they used to be, but, there are typically proprietary drivers that you can try, if the open one doesnt meet your needs
[16:38] <holstein> really depends on the card, and the use case.. id say, if you are not gaming, you should be fine "plug and play"
[16:39] <switchtehbeat> yeah not gaming just want it to work, i didn't know if I had to do a fresh install or  not..
[16:40] <holstein> switchtehbeat: you shouldnt need to.. i mean, it'll either work or not.. a fresh install wont make support magically happen.. the kernel is modular
[16:41] <holstein> i would look into xset http://ubuntuforums.org/showthread.php?t=1052903 for the mouse speed
[16:42] <switchtehbeat> thanks :D
[17:13] <ianorlin> mouse sppeed is adjustable in lxinput as well for sensitivity and accelaratoin
[17:13] <ianorlin> which is called keybaord and mouse in menu ah dang he left
[17:23] <will_> bonjour, suis je seul au monde
[17:23] <will_> ?


[00:51] -SwissBot:#ubuntu-news- ::Planet:: Stephen Michael Kellat: Assessing Cord Cutting @ http://coyote.works//posts/AssessingCordCutting20191021/
[00:51] -SwissBot:#ubuntu-news- ::Planet:: Ubuntu Blog: NVIDIA GPU Operator – Simplifying AI/ML Deployments on the Canonical Platform @ http://ubuntu.com/blog/nvidia-gpu-operator-simplifying-ai-ml-deployments
[13:21] -SwissBot:#ubuntu-news- ::Planet:: Simos Xenitellis: How to add both a private and public network to LXD using cloud-init @ https://blog.simos.info/how-to-add-both-a-private-and-public-network-to-lxd-using-cloud-init/
[13:52] -SwissBot:#ubuntu-news- ::OMG!Ubuntu:: Regolith Linux Adds Support for Ubuntu 19.10 @ https://www.omgubuntu.co.uk/?p=154999 (by Joey Sneddon)
[13:58] -SwissBot:#ubuntu-news- ::Softpedia:: Ubuntu 19.10 (Eoan Ermine) Gets First Linux Kernel Security Patch, Update Now @ https://news.softpedia.com/news/ubuntu-19-10-eoan-ermine-gets-first-linux-kernel-security-patch-update-now-527934.shtml (by Marius Nestor)
[14:10] -SwissBot:#ubuntu-news- ::OMG!Ubuntu:: Firefox 70 is Here with New Logo, Secure Password Generator + More @ https://www.omgubuntu.co.uk/?p=154981 (by Joey Sneddon)
[14:23] -SwissBot:#ubuntu-news- ::Fridge:: Ubuntu Weekly Newsletter Issue 601 @ http://fridge.ubuntu.com/2019/10/21/ubuntu-weekly-newsletter-issue-601/ (by wildmanne39)
[14:40] -SwissBot:#ubuntu-news- ::Softpedia:: Ubuntu 20.04 LTS (Focal Fossa) Daily Build ISOs Are Now Available to Download @ https://news.softpedia.com/news/ubuntu-20-04-lts-focal-fossa-daily-build-isos-are-now-available-to-download-527935.shtml (by Marius Nestor)
[17:49] -SwissBot:#ubuntu-news- ::Softpedia:: Tails 4.0 Anonymous Linux OS Released, Based on Debian GNU/Linux 10 "Buster" @ https://news.softpedia.com/news/tails-4-0-anonymous-linux-os-released-based-on-debian-gnu-linux-10-buster-527938.shtml (by Marius Nestor)
[18:17] -SwissBot:#ubuntu-news- ::Planet:: Ubuntu Blog: How Ubuntu Advantage delivers top-notch Linux security @ http://ubuntu.com/blog/how-ubuntu-advantage-delivers-top-notch-linux-security
[21:21] -SwissBot:#ubuntu-news- ::Softpedia:: Canonical Outs New Linux Kernel Security Update for Ubuntu 18.04 and 16.04 LTS @ https://news.softpedia.com/news/canonical-outs-new-linux-kernel-security-update-for-ubuntu-18-04-and-16-04-lts-527939.shtml (by Marius Nestor)


[00:20] -queuebot:#ubuntu-release- New: accepted pbbam [amd64] (zesty-proposed) [0.5.0-2ubuntu1]
[00:20] -queuebot:#ubuntu-release- New: accepted pbbam [ppc64el] (zesty-proposed) [0.5.0-2ubuntu1]
[00:20] -queuebot:#ubuntu-release- New: accepted pbbam [arm64] (zesty-proposed) [0.5.0-2ubuntu1]
[00:34] -queuebot:#ubuntu-release- New: accepted onboard [amd64] (zesty-proposed) [1.3.0-1ubuntu1]
[01:04] -queuebot:#ubuntu-release- Unapproved: aces3 (yakkety-proposed/universe) [3.0.8-5build2 => 3.0.8-5.1build1] (no packageset)
[01:04] -queuebot:#ubuntu-release- Unapproved: ampliconnoise (yakkety-proposed/universe) [1.29-5build1 => 1.29-5build2] (no packageset)
[01:04] -queuebot:#ubuntu-release- Unapproved: adios (yakkety-proposed/universe) [1.9.0-12 => 1.9.0-12build1] (no packageset)
[01:06] -queuebot:#ubuntu-release- Unapproved: aster (yakkety-proposed/universe) [11.5.0+dfsg2-4build3 => 11.5.0+dfsg2-4build4] (no packageset)
[01:06] -queuebot:#ubuntu-release- Unapproved: blacs-mpi (yakkety-proposed/universe) [1.1-37ubuntu1 => 1.1-37ubuntu3] (no packageset)
[01:09] -queuebot:#ubuntu-release- Unapproved: boost1.60 (yakkety-proposed/universe) [1.60.0+dfsg-6 => 1.60.0+dfsg-6build1] (no packageset)
[01:11] -queuebot:#ubuntu-release- Unapproved: rejected aces3 [source] (yakkety-proposed) [3.0.8-5.1build1]
[01:11] -queuebot:#ubuntu-release- Unapproved: rejected ampliconnoise [source] (yakkety-proposed) [1.29-5build2]
[01:11] -queuebot:#ubuntu-release- Unapproved: rejected blacs-mpi [source] (yakkety-proposed) [1.1-37ubuntu3]
[01:11] -queuebot:#ubuntu-release- Unapproved: rejected adios [source] (yakkety-proposed) [1.9.0-12build1]
[01:11] -queuebot:#ubuntu-release- Unapproved: rejected boost1.60 [source] (yakkety-proposed) [1.60.0+dfsg-6build1]
[01:11] -queuebot:#ubuntu-release- Unapproved: rejected aster [source] (yakkety-proposed) [11.5.0+dfsg2-4build4]
[02:33] <stgraber> slangasek, pitti: confirmed that we have zesty images on images.linuxcontainers.org. For all arches except s390x. s390x failed becaues of the broken LXC. I've released the SRU, upgraded that box and triggered a new build, so we'll have s390x too in a couple hours.
[04:47] -queuebot:#ubuntu-release- New binary: petsc [s390x] (zesty-proposed/universe) [3.7.4+dfsg1-2build1] (no packageset)
[04:59] -queuebot:#ubuntu-release- New: accepted petsc [s390x] (zesty-proposed) [3.7.4+dfsg1-2build1]
[05:03] -queuebot:#ubuntu-release- New binary: petsc [ppc64el] (zesty-proposed/universe) [3.7.4+dfsg1-2build1] (no packageset)
[05:13] -queuebot:#ubuntu-release- New binary: petsc [amd64] (zesty-proposed/universe) [3.7.4+dfsg1-2build1] (no packageset)
[06:13] -queuebot:#ubuntu-release- New: accepted petsc [ppc64el] (zesty-proposed) [3.7.4+dfsg1-2build1]
[06:14] -queuebot:#ubuntu-release- New: accepted petsc [amd64] (zesty-proposed) [3.7.4+dfsg1-2build1]
[07:23] -queuebot:#ubuntu-release- New binary: openbox [amd64] (zesty-proposed/universe) [3.6.1-3] (no packageset)
[07:23] -queuebot:#ubuntu-release- New binary: openbox [ppc64el] (zesty-proposed/universe) [3.6.1-3] (no packageset)
[07:24] -queuebot:#ubuntu-release- New binary: openbox [arm64] (zesty-proposed/universe) [3.6.1-3] (no packageset)
[07:24] -queuebot:#ubuntu-release- New binary: openbox [i386] (zesty-proposed/universe) [3.6.1-3] (no packageset)
[07:24] -queuebot:#ubuntu-release- New binary: openbox [armhf] (zesty-proposed/universe) [3.6.1-3] (no packageset)
[07:25] -queuebot:#ubuntu-release- New binary: openbox [powerpc] (zesty-proposed/universe) [3.6.1-3] (no packageset)
[07:26] -queuebot:#ubuntu-release- New binary: openbox [s390x] (zesty-proposed/universe) [3.6.1-3] (no packageset)
[07:27] -queuebot:#ubuntu-release- New: accepted openbox [amd64] (zesty-proposed) [3.6.1-3]
[07:27] -queuebot:#ubuntu-release- New: accepted openbox [armhf] (zesty-proposed) [3.6.1-3]
[07:27] -queuebot:#ubuntu-release- New: accepted openbox [powerpc] (zesty-proposed) [3.6.1-3]
[07:27] -queuebot:#ubuntu-release- New: accepted openbox [s390x] (zesty-proposed) [3.6.1-3]
[07:27] -queuebot:#ubuntu-release- New: accepted openbox [arm64] (zesty-proposed) [3.6.1-3]
[07:27] -queuebot:#ubuntu-release- New: accepted openbox [ppc64el] (zesty-proposed) [3.6.1-3]
[07:27] -queuebot:#ubuntu-release- New: accepted openbox [i386] (zesty-proposed) [3.6.1-3]
[09:20] <ginggs> morning! anyone around to do some removals for openmpi2 transition? aster, p4est and deal.ii have not been fixed in debian yet
[10:17] <LocutusOfBorg> or demote ^^
[10:18] <LocutusOfBorg> pitti, I invoke you :)
[10:20] <LocutusOfBorg> if we can have openmpi2 in release, I guess it can be time for perl or boost1.62 :)
[11:40] <LocutusOfBorg> parallel=4 on arm64 breaks some haskell stuff https://launchpad.net/ubuntu/+source/haskell-src-exts/1.17.1-2/+build/11049737
[12:11] -queuebot:#ubuntu-release- New binary: linux-signed-lts-trusty [amd64] (precise-proposed/main) [3.13.0-101.148~precise1] (kernel)
[12:11] -queuebot:#ubuntu-release- New binary: linux-signed-lts-xenial [amd64] (trusty-proposed/main) [4.4.0-46.67~14.04.1] (kernel)
[12:11] -queuebot:#ubuntu-release- New binary: linux-signed-lts-vivid [amd64] (trusty-proposed/main) [3.19.0-74.82~14.04.1] (kernel)
[12:59] -queuebot:#ubuntu-release- New: accepted linux-signed-lts-trusty [amd64] (precise-proposed) [3.13.0-101.148~precise1]
[12:59] -queuebot:#ubuntu-release- New: accepted linux-signed-lts-xenial [amd64] (trusty-proposed) [4.4.0-46.67~14.04.1]
[12:59] -queuebot:#ubuntu-release- New: accepted linux-signed-lts-vivid [amd64] (trusty-proposed) [3.19.0-74.82~14.04.1]
[13:47] <clivejo> how do I upload a new package to the archive if I dont have it listed in my packageset?
[13:56] <clivejo> The package I want to upload is - https://ftp-master.debian.org/new/kirigami_1.1.0-1.html
[14:14] <clivejo> infinity: are you on the DMB?
[15:00] <apw> clivejo, you could also ask for sponsorship in the meantime
[15:00] <clivejo> apw: how can I do that?
[15:03] <apw> clivejo, if it is going to be sync from debian you can just use request-sync and it will do the required i think
[15:04] <clivejo> LP 1635842
[15:04] <ubot5`> Launchpad bug 1635842 in Ubuntu "Add kirigami to Kubuntu Packageset" [Undecided,New] https://launchpad.net/bugs/1635842
[15:05] <clivejo> how do I request a sync?
[15:09] <jbicha> clivejo: http://manpages.ubuntu.com/manpages/xenial/en/man1/requestsync.1.html
[15:10] <clivejo> :/
[15:10] <clivejo> Im not MOTU, so how does that help me?
[15:10] <jbicha> you don't have to be MOTU, just run requestsync from the command line
[15:10] <clivejo> but how do I get it in the archive?
[15:11]  * clivejo is confused
[15:12] <jbicha> requestsync opens a bug and subscribes ubuntu-sponsors to it so that it shows up on http://reqorts.qa.ubuntu.com/reports/sponsoring/ so that someone with upload rights can take a look at it
[15:14] <jbicha> but...if it's just a new package it will show up in Ubuntu automatically as long as we aren't in Debian Import Freeze https://wiki.ubuntu.com/DebianImportFreeze
[15:15] <clivejo> E: The source package 'kirigami' does not exist in the Debian primary archive in sid, sid-security, sid-updates or sid-proposed
[15:16] <jbicha> yes, I'd just wait until kirigami gets into Debian unstable and it should be automatically synced into Ubuntu without you having to do anything
[15:18] <clivejo> any idea how long that will be?
[15:21] <clivejo> can it not be added to the Kubuntu package list that I can upload it directly?
[15:23] <jbicha> new Ubuntu packages have to be manually approved and honestly it will be approved a lot faster if it's synced from Debian (so it's already been reviewed) than trying to upload to Ubuntu first
[15:24] <clivejo> we have a number of new packages this cycle, there must be an better way to do this!
[15:25] <jbicha> it's very early in the zesty release cycle; there's no need to panic yet :)
[15:26] <clivejo> LOL I seem to remember that being said about Yakkety, and lots of KDE software didnt make it in
[15:27] <jbicha> ok but the fastest way to get a new source package into Ubuntu is to upload it to Debian
[15:28] <clivejo> jbicha: its just frustrating working on packaging and not being able to get it into the archive
[15:29] <clivejo> jbicha: so where is it in Debian right now - https://ftp-master.debian.org/new/kirigami_1.1.0-1.html
[15:29] <clivejo> Maxy released it to UNSTABLE on the 3rd Oct
[15:30] <clivejo> https://anonscm.debian.org/cgit/pkg-kde/kde-extras/kirigami.git/commit/?id=458cdc2aa29811dd2a3061bbd0f38efe3fd1540d
[15:31] <jbicha> all new source packages have to be reviewed first; kirigami is waiting for a member of the Debian ftpmaster team to review it
[15:31] <clivejo> do you know where I can see that?#
[15:31] <jbicha> maybe if you wait another week or two it will be fine
[15:33] <acheronuk> clivejo: listed under pending uploads here<EMAIL_ADDRESS>[15:34] <clivejo> hummm if its anything like libdrumstick we will be waiting a LONG time
[15:37]  * clivejo wanders off to do OSM stuff
[17:59] -queuebot:#ubuntu-release- New binary: perl [s390x] (zesty-proposed/main) [5.24.1~rc3-3] (core)
[18:08] -queuebot:#ubuntu-release- New binary: perl [ppc64el] (zesty-proposed/main) [5.24.1~rc3-3] (core)
[18:09] <ginggs> any archive admins around to do some removals to complete the openmpi2 transition please? aster, p4est and deal.ii are RC in Debian and have been removed from testing
[18:11] -queuebot:#ubuntu-release- New binary: perl [i386] (zesty-proposed/main) [5.24.1~rc3-3] (core)
[18:13] -queuebot:#ubuntu-release- New binary: perl [powerpc] (zesty-proposed/main) [5.24.1~rc3-3] (core)
[18:13] -queuebot:#ubuntu-release- New binary: perl [amd64] (zesty-proposed/main) [5.24.1~rc3-3] (core)
[18:41] -queuebot:#ubuntu-release- New binary: perl [armhf] (zesty-proposed/main) [5.24.1~rc3-3] (core)
[18:43] -queuebot:#ubuntu-release- New binary: perl [arm64] (zesty-proposed/main) [5.24.1~rc3-3] (core)
[21:13] -queuebot:#ubuntu-release- Unapproved: fcitx (yakkety-proposed/main) [1:<IP_ADDRESS>-4 => 1:<IP_ADDRESS>-4ubuntu<IP_ADDRESS>] (input-methods, kubuntu, ubuntu-desktop)
[21:46] <slangasek> LocutusOfBorg: a couple packages FTBFS with the new openmpi (aster, p4est); do you have any ideas about these?
[21:48] <slangasek> and liggghts seems to have a legitimate autopkgtest failure on armhf
[21:48] <LocutusOfBorg> slangasek, I wasdoing haskell rebuilds
[21:48] <LocutusOfBorg> I saw now you are handling them
[21:49] <LocutusOfBorg> slangasek, aster and p4est needs demotions, ginggs is aware of the issue, and according to him ^^ they are broken in debian too
[21:49] <slangasek> ok
[21:49] <LocutusOfBorg> [11:20:10] <ginggs> morning! anyone around to do some removals for openmpi2 transition? aster, p4est and deal.ii have not been fixed in debian yet
[21:50] <LocutusOfBorg> so, having the package migrate might be the best thing right now
[21:51] <LocutusOfBorg> agda on ppc64el has a strange failure " sbuild-build-depends-agda-dummy : Depends: dh-elpa but it is not going to be installed"
[21:51] <LocutusOfBorg> how can a package arch:all be uninstallable?
[21:51] <slangasek> because it depends on something which is /not/ arch all?
[21:52]  * LocutusOfBorg checks, but without a real arch... and no debhelper verbosity is not trivial
[21:53] <slangasek> Depends: perl, emacs24-nox | emacs24 (>= 24~) | emacs24-lucid (>= 24~)
[21:53] <LocutusOfBorg> emacs24
[21:53] <LocutusOfBorg> yes
[21:53] <LocutusOfBorg> indeed
[21:54] <LocutusOfBorg> "memory exausted"
[21:54] <LocutusOfBorg> sigh
[21:54] <LocutusOfBorg> maybe with parallel=2 it might work
[22:10] <slangasek> LocutusOfBorg, ginggs: and gerris test results look a mess; I'm not sure what of these should be considered an openmpi bug vs. a bug in a revdep
[22:10] <slangasek> esys-particle and liggghts both have similar failures on armhf only (unexpected stderr output)
[22:14] <LocutusOfBorg> gerris is broken in debian, just the same way
[22:14] <LocutusOfBorg> not sure where is the fault
[22:22] <slangasek> haskell-attoparsec ftbfs on ppc64el, strange regression appears to be triggered solely by the rebuild
[22:26] <slangasek> there's Debian bug #814451 about openmpi and stderr
[22:26] <ubot5`> Debian bug 814451 in src:openmpi "openmpi 1.10 has stderr output by default, breaking autopkg tests" [Important,Open] http://bugs.debian.org/814451
[22:27] <slangasek> so our ARM vms have the appearance of infiniband support...?