[03:36] <TheMuso> robert_ancell: So... At-spi does have code to remove the AT_SPI_BUS X atom on shutdown, which of course happens when the user logs in, since the at-spi-bus-launcher process receives SIGTERM.
[03:36] <TheMuso> However, for some reason, it is unable to open the X display to remove the property.
[03:37] <robert_ancell> huh
[03:37] <TheMuso> I found that out after placing a debug printf statement in the code which gets put into the seat/greeter log file, and of course the message is not in the log file. Will do some extra checking and debugging, but I'm now wondering why on cleanup the X display cannot be found.
[03:41] <TheMuso> So at-spi-bus-launcher receives SIGTERM, at which cleanup is initiated, one of which is removing the AT_SPI_BUS property. XOpenDisplay is called, and if the display variable is non-NULL, the property is deleted. My debug statement was within that if block and was not executed.
[05:39] <duflu> That's odd. I join a maining list, look at its archives, and find I was already authoring most of its messages
[05:39] <duflu> Such are bug subscriptions
[05:55] <oSoMoN> good day desktoppers!
[05:55] <duflu> Hi oSoMoN
[05:56] <oSoMoN> hey duflu, how goes?
[05:59] <duflu> oSoMoN, goes OK. First day of winter, in theory :) You?
[06:01] <oSoMoN> yeah, pretty good. Had a short but restful night, and spring is in full bloom here, it’s gonna be another hot and sunny day
[06:02] <Trevinho> Hey oSoMoN and duflu
[06:02] <oSoMoN> hey Trevinho!
[06:02] <duflu> Trevinho, hello
[07:12] <didrocks> good morning
[07:38] <oSoMoN> salut didrocks
[07:44] <didrocks> salut oSoMoN
[07:53] <andyrock> morning all!
[07:55] <didrocks> hey andyrock
[07:56] <oSoMoN> hey andyrock
[08:02] <willcooke> morning
[08:05] <didrocks> hey willcooke
[08:11] <seb128> good morning desktopers
[08:11] <duflu> Morning seb128, all
[08:12] <oSoMoN> salut seb128
[08:12] <oSoMoN> good morning willcooke
[08:13] <didrocks> hey duflu
[08:13] <didrocks> re seb128
[08:13] <seb128> hey duflu oSoMoN willcooke Laney, re didrocks
[08:21] <seb128> hey robert_ancell
[08:23] <robert_ancell> seb128, hello
[08:24] <seb128> robert_ancell, how are you? doing extra hours or forgot to close IRC? ;-)
[08:24] <didrocks> good evening robert_ancell
[08:25] <robert_ancell> seb128, trying to catch up with backlog :/
[08:25] <robert_ancell> And also forgot to close IRC
[08:25] <seb128> :-)
[08:25] <seb128> robert_ancell, what's the status|plan of g-s and gdm/lightdm
[08:26] <seb128> it's not clear to me what we are aiming for
[08:26] <robert_ancell> seb128, g-s is https://trello.com/b/o3AB123B/gnome-software
[08:26] <seb128> sorry
[08:26] <seb128> shell
[08:26] <seb128> do we plan to patch gnome-shell to not use the gdm bindings
[08:26] <seb128> or to keep that and glue to lightdm at runtime?
[08:27] <seb128> (would need to promote gdm?)
[08:27] <robert_ancell> seb128, the patch would support both, I guess we want to make GDM a runtime dependency if we don't want it in main
[08:28] <seb128> is that where we are going?
[08:28] <seb128> or undecided yet?
[08:29] <robert_ancell> seb128, I'm working on getting g-s to run as a greeter in LightDM (not making good progress yet), jbicha pointed out the other day that the GDM MIR is going slow too
[08:29] <seb128> robert_ancell, why would gnome-software be a greeter?
[08:29] <seb128> :p
[08:29] <robert_ancell> seb128, !! :P
[08:30] <robert_ancell> I would have hoped we would get GDM into main so we wouldn't have to consider hacking gnome-shell until we were ready to make it fully work with LightDM
[08:30] <Laney> YO!
[08:30] <seb128> Laney!
[08:30] <Laney> soz, was at the physio
[08:30] <seb128> robert_ancell, having to support gdm ir we use lightdm seems suboptimal, or is that a transition plan?
[08:31] <robert_ancell> I would have thought that GDM would be fairly low security risk given it's in plenty of distros, but I guess we have to be thorough.
[08:31] <seb128> I think security/MIR would probably be fine to promote gdm if we demote it before release
[08:31] <seb128> but if it's stay in main they need to do their job and properly review it
[08:33] <robert_ancell> I think they're worried that second step wont get done :)
[08:33] <seb128> hehe
[08:34] <robert_ancell> seb128, hang on, can't we just get libgdm in main and the rest of GDM in universe?
[08:38] <seb128> robert_ancell, we can, but it means the gdm source is in main so security team has to support it
[08:39] <seb128> though I'm never clear how they define what we support exactly in those cases
[08:39] <robert_ancell> the whole source needs to be checked?
[08:39] <seb128> I'm not sure what security team usually does but I wouldn't be surprised if they wanted to have a look yet
[08:39] <seb128> yes
[08:46] <robert_ancell> The GDM code is really spread throughout gnome-shell, I think it would be quite hard to make it conditional
[08:52] <Laney> The lightdm work is to make equivalents for all of that stuff?
[08:54] <robert_ancell> Laney, well, in the LightDM work we'd pass equivalent objects where the GDM ones go. I was looking then at what would need to be done to have no objects.
[08:55] <robert_ancell> though perhaps you could just not load entire .js files if GDM is not there
[08:56] <robert_ancell> yeah, that seems more possible
[08:59] <Laney> robert_ancell: sorry, bit unclear :(
[09:00] <Laney> is the plan something like -> to get the seeds updated, use gdm3 at first and then plan to go back to lightdm later
[09:00] <robert_ancell> Laney, that's what I thought you guys were suggesting
[09:01] <robert_ancell> Laney, actually, run gnome-shell from lightdm+unity-greeter at first, then ideally switch out unity-greeter with the fallback being to go full gdm
[09:01] <willcooke> Do we need a quick LightDM HO to thrash this out?
[09:02] <robert_ancell> Sure
[09:02] <willcooke> Laney, seb128, robert_ancell - https://hangouts.google.com/hangouts/_/canonical.com/will?authuser=0
[09:03] <seb128> willcooke, sorry, I'm in a public place atm and didn't take my headset, I can do that in 20 min if you need me but otherwise I trust you/Laney/Robert to sort it out :-)
[09:06] <Laney> sec
[09:11] <seb128> those discussions make me wonder if we should switch to gdm after all, my initial understanding was that we could swap it for lightdm, not that we would need to keep libgdm/gdm in main in addition
[09:11] <seb128> anyway let me know if you need me
[09:15] <robert_ancell> seb128, not sure what you mean there?
[09:15] <seb128> robert_ancell, I though the plan was to have only gnome-shell and lightdm on the iso/in main, not libgdm/gdm
[09:16] <seb128> but I'm going to let you guys sort it out
[09:16] <Laney> just commented on trello with a summary of that hangout
[09:17] <seb128> thanks
[09:19] <duflu> koza: Now running 5.45 debs on artful
[09:19] <duflu> Flawless so far
[09:20] <duflu> No PPA yet. Just built from my new git
[09:20] <seb128> koza, duflu, is that about bluez? did you sort out that segfault issue?
[09:20] <robert_ancell> what does <!nocheck> mean in debian/control?
[09:20] <duflu> seb128: No one has the crashing device any more :)
[09:20] <seb128> :-/
[09:21] <seb128> robert_ancell, https://wiki.debian.org/BuildProfileSpec
[09:21] <Laney> you can pass DEB_BUILD_OPTIONS=nocheck
[09:21] <robert_ancell> ah
[09:21] <robert_ancell> because we have to remove the build-dep to be in main right?
[09:21] <Laney> nope
[09:21] <robert_ancell> ok, good
[09:22] <Laney> only Depends and Recommends
[09:22] <Laney> not Build-Depends
[09:28] <robert_ancell> Laney, oh that's weird, we'd have to make it a suggests?
[09:29] <Laney> the gir?
[09:41] <koza> duflu, it has been good except when using that single headset. but search for segfaults, ppl over mailing lists are reporting some
[09:41] <duflu> koza: Yeah, don't look too hard. Ubuntu users report problems regularly too
[09:42] <koza> seb128, yes about bluez buy yeah as duflu said i do not have the crashing device anymore (headset died last week during a heavy rain :(
[09:43] <koza> duflu, today we have when using ConnectProfile API search_completed_cb(), browse_cb()
[09:44] <koza> duflu, there are also a few reports for 5.44 and all of them show signs of similarity
[09:45] <duflu> koza, a couple of entries on errors.ubuntu.com show crashes in those
[09:47] <duflu> koza: bug 1689435 and bug 1690014
[09:47] <duflu> The latter one stopped after xenial
[09:47] <duflu> But the first one keeps happening
[09:49] <koza> duflu, indeed. the guy who reported an issue today uses 16.04
[09:49] <duflu> koza, yeah. But the important point is it's nothing new. Both crashes in those functions were happening as far back as 15.10
[09:51] <koza> duflu, roger that; tempting to close as "known issue" then :-)
[09:51] <koza> duflu, seriously though, as you said during the sync meeting, would be good to look at the stack traces and see if there is anything obvious
[09:52] <koza> duflu, i'll do my best to find time; diving into c code might be fun
[09:53] <duflu> I'm still encouraged. If you compare 16.04 to what will be in 18.04 it's dramatically better
[09:53] <duflu> Identifying things to backport is very hard, and a problem for another day
[09:54] <koza> indeed it is
[09:55] <koza> early lunch now
[10:05] <robert_ancell> woohoo, I'm running gnome-shell without gir1.2-gdm-1.0 installed
[10:05] <oSoMoN> qengho, hey, IIUC the google API keys for chromium were associated to your @canonical.com e-mail address, is that correct?
[10:08] <seb128> robert_ancell, well done
[10:09] <seb128> brb, relocating back from coffee place
[10:09] <robert_ancell> brb too
[10:11] <didrocks> Laney: do you know where the gtksettings are stored, like https://developer.gnome.org/gtk3/3.2/GtkSettings.html#GtkSettings--gtk-application-prefer-dark-theme ?
[10:11] <didrocks> I don't find any corresponding gsettings key in dconf
[10:12] <Laney> didrocks: lots of places, but I think that one is setup.ini
[10:12] <Laney> err
[10:12] <Laney> settings.ini
[10:12] <didrocks> hum
[10:12] <didrocks> I don't have any in my ~
[10:14] <didrocks> ~/.config/gtk-3.0/settings.ini
[10:14] <didrocks> thanks Laney :)
[10:14] <Laney> sure!
[10:15] <Laney> I think that flatpaks have a problem with that btw
[10:15] <Laney> as the sandbox doesn't have that file shared into it
[10:15] <Laney> https://tingping.github.io/2017/05/11/flatpak-theming.html is what I read before
[10:15] <Laney> mentions it
[10:18] <didrocks> we will need to have access to that file
[10:22] <Laney> yeh not sure why they don't share it
[10:33] <robert_ancell> Laney, seb128, willcooke, I should delete all the gnome-software cards in https://trello.com/b/0T55ivzN/ubuntu-desktop-17.10-cycle right and just use https://trello.com/b/o3AB123B/gnome-software ?
[10:34] <robert_ancell> It's getting impossible to keep things in sync
[10:34] <willcooke> I would prefer everything in one board tbh, and then use filtering to only share what you care about
[10:34] <robert_ancell> willcooke, can we make the cards show on multiple boards?
[10:34] <willcooke> I can probably work something out to move them over with a script fif that will help
[10:34] <willcooke> robert_ancell, only with the paid-for version I think.
[10:34] <robert_ancell> *!*#%!
[10:35] <willcooke> s/share/show
[10:35] <robert_ancell> Can we get the paid version?
[10:35] <willcooke> I dont think so.
[10:36] <robert_ancell> willcooke, the gnome-software board is accurate, perhaps you can make a script that picks the ones you care about and mirrors them in the 17.10 board
[10:36] <robert_ancell> And they can say "don't edit these here, edit them in the gnome-software board"
[10:36] <seb128> I'm +1 for having one board only
[10:37] <seb128> it's difficult to have an overview if everyone is creating specific boards for pieces of work
[10:37] <robert_ancell> seb128, you think I should move all the cards to the 17.10 board?
[10:37] <robert_ancell> I'm OK with that
[10:38] <willcooke> robert_ancell, if you're ok with that, I can script the move I think
[10:38] <seb128> I think I would prefer that
[10:38] <willcooke> unless its easy to do that with the tools provided
[10:38] <seb128> willcooke, Laney, wdyt?
[10:38] <robert_ancell> I'll do it by hand, it's not too hard
[10:38] <willcooke> ok, thanks
[10:39] <Laney> I don't mind checking the other one, but if you prefer - move it
[10:39] <Laney> if you put the gnome-software label on them all then it's easy to emulate the separate board using a filter
[10:39] <willcooke> robert_ancell, if you attach the yellow g-software label and add yourself to the card - then you can filter it so that it looks the same as the g-soft. board does today
[10:39] <willcooke> heh, what Laney sais
[10:40] <Laney> all that typing of the dead pays off finally
[11:11] <robert_ancell> You may get some Trello spam... I moved a lot of stuff
[11:11] <Laney> nice one
[11:13] <willcooke> thanks robert_ancell
[11:15] <willcooke> oh, the reply feature doesnt work like I thought it would
[11:15]  * willcooke deletes silly comments
[11:16] <robert_ancell> bye all
[11:17] <willcooke> night robert_ancell
[13:23] <kenvandine> didrocks, you can have the honors of updating the seed, if you like
[13:25] <seb128> kenvandine, hey, did we get the gdm case resolved?
[13:25] <seb128> oh, I see that robert uploaded g-s
[13:25] <kenvandine> yup
[13:25] <kenvandine> :)
[13:25] <kenvandine> although it's adding a patch :)
[13:25] <seb128> if the patch is not too complex to maintain...
[13:26] <seb128> when my understand is that it was more of a workaround to unblock things anyway than a proper solution
[13:26] <seb128> going to lead to non working lockscreen right?
[13:26] <didrocks> Laney: kenvandine: everything is +1 on your side, like we can update now?
[13:26] <kenvandine> yeah
[13:26] <kenvandine> didrocks, yes
[13:26] <kenvandine> http://paste.ubuntu.com/24592877/
[13:26] <kenvandine> didrocks, that's my diff to the seed, see how that looks and you can update it :)
[13:26] <didrocks> excellent!
[13:26] <kenvandine> you gave us unity... you can take it away :-p
[13:27] <didrocks> did the same for the amazon scope, starting to get used to it :)
[13:27]  * didrocks put some funeral music on
[13:27] <didrocks> puts*
[13:27] <kenvandine> i had some fun removing a bunch of my patches from packages... undoing several years of work :)
[13:28] <didrocks> https://www.youtube.com/watch?v=28sdV_DXSrU
[13:28] <kenvandine> didrocks, perfect
[13:29]  * kenvandine takes a few moments of silence in remembrance
[13:29] <Laney> weeeeeee
[13:29] <kenvandine> willcooke, ^^ didrocks is going to update the seed
[13:30] <kenvandine> willcooke, you wanted a heads up :)
[13:30] <willcooke> kenvandine, \o/
[13:30] <willcooke> thanks
[13:33] <Laney> https://www.youtube.com/watch?v=Z0GFRcFm-aY
[13:35]  * willcooke takes off his hat
[13:38] <kenvandine> seb128, btw i tested the gnome-3-24 platform snap and ghex on xenial, worked well.  However it doesn't show the proper icon in the app search
[13:39] <kenvandine> it does on artful though... which is weird
[13:39] <kenvandine> seb128, but it works with strict confinement
[13:39] <seb128> good, I was just downloading the snap to test
[13:39] <seb128> is there any reason we don't publish them to the store?
[13:39] <seb128> the gnome 3-24 I mean
[13:40] <kenvandine> seb128, nope... just wanted a good test
[13:40] <kenvandine> the ghex snap is only 1.6M :)
[13:40] <didrocks> updating the metapackage now, everyone +1?
[13:43] <willcooke> +1
[13:46] <kenvandine> +1
[13:47] <gQuigs> for those following at home - http://bazaar.launchpad.net/~ubuntu-core-dev/ubuntu-seeds/ubuntu.artful/revision/2531  ..  nice commit message
[13:48] <didrocks> thx :)
[13:48] <willcooke> :)
[13:49] <didrocks> ok, uploading
[13:50] <kenvandine> woot
[13:50] <Laney> ._.
[13:52] <didrocks> https://launchpad.net/ubuntu/+source/ubuntu-meta/1.383
[13:56]  * oSoMoN sheds a tear
[13:57] <oSoMoN> didrocks, thanks for mentioning unity2d, that brought back fun memories
[13:57] <didrocks> my pleasure :) (better with music)
[13:58] <didrocks> I didn't mention that Thursday evening were you were all going off and then I realized that the new libunitycore wasn't compatible with the unity2d and I had to fix it all alone :p
[13:58] <Laney> wait
[13:58] <willcooke> lulz
[13:58] <kenvandine> lol
[13:58] <didrocks> ahah ;)
[13:59] <oSoMoN> don’t complain, that contributed to building your legend ;)
[13:59] <didrocks> haha
[13:59] <didrocks> I see how it works :)
[14:07]  * ogra_ sees the new meta and wipes a tear away
[14:08] <Laney> I was wondering about the overlay-scrollbar-gtk2
[14:08] <Laney> should gtk2 maybe recommend that?
[14:08] <didrocks> why? do we still want it?
[14:08] <didrocks> hum
[14:09] <didrocks> that's true that gtk3 has those
[14:09] <didrocks> unsure how it will play on the long term
[14:09] <Laney> yes it's still part of the theme
[14:09] <didrocks> especially once we move to wayland
[14:19] <jbicha> speaking of gtk2, I'd like to move a bunch of dependencies to have libgtk2.0-0 depend on them LP: #1585903
[14:20] <jbicha> I've not discussed that with Debian yet
[14:20] <gQuigs> with this change, won't wayland be an option tomorrow?
[14:38] <jbicha> yay, lots of approved MIRs https://people.canonical.com/~ubuntu-archive/component-mismatches.svg
[14:52] <kenvandine> jbicha, excellent!
[15:10] <jbicha> didrocks: unless you manually hack ubuntu-meta, you'll need to wait for the new packages to be promoted to main before ./update will pick them up (since update.cfg only checks main,restricted)
[15:11] <jbicha> so ubuntu-desktop has no desktop now :) https://launchpadlibrarian.net/322078023/ubuntu-meta_1.382_1.383.diff.gz
[15:13] <jbicha> (I don't know what it has since I didn't install the update)
[15:13] <didrocks> jbicha: you are right
[15:13] <didrocks> as the Mir are accepted, I can promote them
[15:14] <didrocks> and do a quick following up upload
[15:14] <didrocks> but I wanted to have the list of packages that were pulled
[15:14] <jbicha> didrocks: the MIRs are already approved if that's what you were asking: https://people.canonical.com/~ubuntu-archive/component-mismatches.svg
[15:14] <didrocks> yeah
[15:14] <didrocks> turning on my vpn and doing
[15:16] <jbicha> I assume that was an accident, otherwise you could have set a block-proposed bug and just used component-mismatches-proposed
[15:16] <didrocks> oh, is component-mismatches-proposed new?
[15:16] <didrocks> wasn't a thing before I left the desktop team
[15:17] <didrocks> or I don't remember about it :)
[15:17] <jbicha> it might be newer than that
[15:17] <jbicha> anyway, it will be fixed soon so no big deal :)
[15:18] <didrocks> doing the promotions right now
[16:05] <didrocks> hum ? Unknown desktop package: gnome-control-center
[16:05] <didrocks> only on amd64
[16:05] <didrocks> (same with gnome-settings-daemon on every archs)
[16:06] <didrocks> however:  gnome-control-center | 1:3.24.2-0ubuntu1     | artful                   | source, amd64, arm64, armhf, i386, ppc64el, s390x
[16:06] <didrocks> (and yes, it seems that the one promoting g-s-d only promoted the source, not the binaries)
[16:14] <jbicha> didrocks: maybe g-c-c hadn't been fully published in main yet? try again?
[16:16] <didrocks> tried 3 times, but yeah, rmadison was in advanced compared to the archive source
[16:16] <didrocks> so, g-c-c is ok
[16:16] <didrocks> but as I just promoted g-s-d which was partially promoted, I need to wait for another publisher cycle
[16:17] <didrocks> (it's funny that it was promoted only on some archs, I guess either a hickup, but in any case, the one promoting it didn't check the output at the time)
[17:20]  * oSoMoN calls it a day
[17:20] <oSoMoN> have a good evening everyone
[17:28] <willcooke> night all
[17:30] <jbicha> Laney: did you self-reject ubuntu-settings?
[17:31] <Laney> Yes.
[17:31] <Laney> Why?
[17:32] <jbicha> it will need a break/replaces against unity-asset-pool
[17:36] <Laney> Yes. Thanks. I know. I messed up the paths.
[17:36] <Laney> Not going to fix it now though. Bye
[17:37] <jbicha> good night :)
[18:23] <Trevinho> Night guys.. and have nice WE (tomorrow is national holidays in Italy).


[05:23] <lamont> doko: and could you get me an address for that java guy and I'll see what I can toss his way
[05:24] <lamont> or point him at<EMAIL_ADDRESS>[05:24] <lamont> or any of my other addresses
[05:28] <doko> lamont: join #gcj on oftc


[00:32] <OvenWerks> Bug #1872250
[00:34] <OvenWerks> Eickmeyer: fix commited (like the rest of us?)
 is a fix committed for that OvenWerks?
[00:41] <OvenWerks> uploaded two minutes ago
[00:42] <OvenWerks> Maybe 8?
[00:43] <OvenWerks> change log needs to quick massage
[00:43] <OvenWerks> From unreleased to whatever and bump the version.
[00:44]  * OvenWerks wanders off to fix the next bug on the list (Ardour this time)
[00:50] <Eickmeyer> OvenWerks: Ok, I'll upload.
[01:03] <Eickmeyer> OvenWerks: Uploaded, version bumped to 1.12.4, targeted focal. Changes good on the github verison too?
[01:14] <Eickmeyer> OvenWerks: Nevermind, found out for myself.
[15:50] <Eickmeyer> Ok team. Final Freeze is Thursday. Here's the uploads in the queue that we're waiting on: darktable 3.0.1, carla 2.1 (final), and ubuntustudio-installer 0.08 (typo fix).
[15:51] <Eickmeyer> Getting the release team to simply ack these has been like talking to a brick wall. I'm getting nervous and frustrated, not gonna lie.
[16:11] <OvenWerks> LTS blues?
[16:12] <OvenWerks> so far 20.04 is a good release.... 18.04 I was ready to give up pretty much
[16:12] <Eickmeyer> I feel like we can't get rid of 18.04 fast enough.
[16:15] <OvenWerks> backports has also come a long way
[16:15] <OvenWerks> there has not been abackports since before I started
[16:16] <OvenWerks> (thankyou for fixing my typos)
[16:16] <Eickmeyer> Heh, you're welcome. Wasn't hard, just glad somebody saw it.
[16:16] <Eickmeyer> The other part of that bug is something we can't do anything about without a rewrite.
[16:18]  * OvenWerks didn't read the whole bug
[16:18] <OvenWerks> what was the other part?]
[16:18] <OvenWerks> (or a link)
[16:18] <Eickmeyer> bug 1872386
[16:22] <OvenWerks> To me the real bug is that the reboot message should not appear if it is not needed. The code in -controls should be used to check if the user has the access needed. I think if autojack is running that is probably enough even (maybe not)
[16:24] <Eickmeyer> Agreed, but in this case, the person who filed it was running Ubuntu (proper), so they were using GNOME.
[16:24] <Eickmeyer> So the message would pertain to them.
[16:24] <Eickmeyer> The scenario you brought up is if someone is already running Studio.
[16:24] <OvenWerks> yup.
[16:25] <OvenWerks> personally, for such a message, a "jarring" font and box is a good thing :)
[16:25] <Eickmeyer> Ha! Agreed.
[16:25] <Eickmeyer> Gets your attention, even if ugly.
[16:28] <OvenWerks> we could put a systemd service that removes a file that installer has created on shutdown so the next time installer runs it does not use that
[16:28] <OvenWerks> other way around
[16:28] <OvenWerks> renames a file?
[16:30] <OvenWerks> installer goes touch needs-reboot, systemd goes mv needs-reboot rebooted
[16:30] <Eickmeyer> That could work, at least in theory.
[16:30] <Eickmeyer> Or it could check to see if the current user is in @audio, which I believe is the goal anyhow.
[16:30] <OvenWerks> The only time a reboot is needed is first time run and after kernel install
[16:31] <OvenWerks> and to see if they have rt access
[16:32]  * OvenWerks thinks if there is anything else
[16:32] <OvenWerks> I guess most people will start it once choose what they want and never start it again
[16:33] <OvenWerks> when I was testing it, I was installing one bundle (get warning) then installing another bundle (another warning) etc.
[16:33] <OvenWerks> so my experience was atypical
[16:33] <OvenWerks> so leave it in there
[16:34] <Eickmeyer> Yeah. Besides that, we don't have the Ubiquity plugin anymore, so its point for Studio users is moot. It's basically strictly for adding Studio to another flavor now.
[16:35] <OvenWerks> Is thath how it was fixed?
[16:35] <OvenWerks>  :)
[16:35] <OvenWerks> some people won't like that
[16:35] <Eickmeyer> Yep. Turns out the Ubiquity plugin couldn't be maintained anymore. It was forked from an Edubuntu plugin, and we know what happened there.
[16:36] <Eickmeyer> Well, we can't do much about that. It was utterly broken.
[16:37] <OvenWerks> So things on my todo list:
[16:38] <OvenWerks> Ardour bugs/feature requests (OSC and foldback)
[16:38] <OvenWerks> kbmidi add ALSA
[16:38] <Eickmeyer> Fun. Mine is to pester the release team.
[16:39] <OvenWerks> idjc update
[16:39] <OvenWerks> -controls... stuff
[16:40] <Eickmeyer> Did they actually port idjc to Python3, or are you doing that yourself?
[16:40] <OvenWerks> I have not found anything for that
[16:40] <Eickmeyer> I haven't either.
[16:41] <OvenWerks> there are 2019 commits though
[16:41] <OvenWerks> so it is not dead
[16:42] <Eickmeyer> No, just not Python2 alive.
[16:42] <Eickmeyer> For all intents and purposes, anything still using Python2 at this point is dead.
[16:42] <OvenWerks> Yeah, but the author may (depending on which OS they use) update that for personal reasons
[16:43] <Eickmeyer> That means it can't be in Arch, Ubuntu, Debian, or Fedora at minimum. openSUSE might be in that too.
[16:44] <OvenWerks> I also have the repo for jack-mixer but I think rather than bringing that back to life, a new non-mixer like unit that uses LV2 might be better
[16:45] <OvenWerks> I would really like to add LV2 plugin hosting to the jackd ALSA back end
[16:45] <Eickmeyer> That would be nice. Though, some plugins have standalone binaries, like lsp-plugins.
[16:46] <OvenWerks> there would be no support for GUIs
[16:46] <OvenWerks> the plugins would have to be OSC or MIDI controled
[16:48] <OvenWerks> My purpose is not to add _any_ plugin but to be able to add an output volume control that can be controlled by the systray
[16:48] <OvenWerks> I may be better off just adding a level control and leaving it at that
[16:50] <OvenWerks> honestly, I would like to change the way jack works. The backend would be the dummy backend... any device would become a client.
[16:51] <OvenWerks> the backend is able to sync to one device client and to route i/o to that client
[16:51] <Eickmeyer> Just like zita-ajbridge.
[16:51] <OvenWerks> we could do that now
[16:52] <OvenWerks> but I want the dummy i/o to reflect the synced device client
[16:53] <OvenWerks> the user would be able to set up an i/o map so that (for example) dummy output 1&2 would be device output 9&10
[16:54] <Eickmeyer> Interesting concept.
[16:54] <OvenWerks> I do not know if the dummy back end would self sync to a zit-ajbridge that was set to hard sync or not
[16:54] <OvenWerks> I don't think so
[16:55] <Eickmeyer> The way it functions now? not likely.
[16:55] <OvenWerks> dummy gets sync from the CPU right now.
[16:56] <OvenWerks> I would like to see a system wide media clock
[16:57] <Eickmeyer> That would be nice, could be integrated into the transport.
[16:57] <OvenWerks> it would be able to be synced from: CPU, Network (AVB, Dante, AES67), any audio device
[16:58] <OvenWerks> The jackd dummy back end would sync from that
[16:58] <Eickmeyer> Dante support for Linux. There's something that would be nice.
[16:58] <OvenWerks> Dante uses the same meadia clocking as AES67 and AVB
[16:59] <OvenWerks> *media even
[17:00] <OvenWerks> So it is possible to set up AES67 that syncs to a Dante network and have that dante network talk to the AES67 linux endpoint... though near as controlable
[17:01] <OvenWerks> I don't know if a wine app could do the discovery and control part or not.
[17:03] <OvenWerks> I do think networked audio will trickle down to consumer levels in the next years.
[17:03] <OvenWerks> I think that probably AVB will be the one that does so first
[17:04]  * OvenWerks wanders off to breakfast with wife
[17:09] <Eickmeyer> Have a good breakfast.
[17:15] <Eickmeyer> Darktable is accepted. One down, two to go.
[17:38] <Eickmeyer> Carla is all that's left now.
[22:43] <OvenWerks> Eickmeyer: This throws a wrench in things... https://discourse.ardour.org/t/a-eq-and-a-comp-fail-on-manjaro-xfce/103122
[22:44] <OvenWerks> I just checked and yes this affects our Ardour package
[22:50] <OvenWerks> it will take at least a release note.
[22:50] <OvenWerks> The fix may be to import this directory: https://github.com/Ardour/ardour/tree/master/libs/plugins
[22:51] <OvenWerks>  I don't know if just cherry picking: https://github.com/Ardour/ardour/commit/3df530e7f6521a74d5184c6de04589cd762c5f12
[22:51] <OvenWerks> would do it.
[22:52] <OvenWerks> This has to do with the c compiler version in 18.04
[22:59] <OvenWerks> I notice that a-delay, and a-reverb are not a part of this fix and they don't work either
[23:13] <OvenWerks> Eickmeyer: I can confirm that https://nightly.ardour.org/ 64bit, optimized, free/demo, gcc5
[23:14] <OvenWerks> when installed then cp -r /opt/Ardour-6.0.pre1.294/lib/LV2/* /usr/lib/ardour5/LV2/
[23:14] <OvenWerks> does make them work.
[23:16] <Eickmeyer[m]> File a bug report, we might be able to upload. teward, might need upload powers.
[23:18] <Eickmeyer[m]> ERR:GroceryShopping
[23:21] <OvenWerks> right. rg says we should be able to just recompile
[23:22] <OvenWerks> as in when was the Ardour package last compiled?
[23:22] <OvenWerks> as compared to  the 2.31 version of the GNU C Library
[23:27] <OvenWerks> when you get home... is it possible to rebuild Ardour in our dayly or whatvere to see if that makes work ok?
[23:27] <OvenWerks> https://bugs.launchpad.net/ubuntu/+source/ardour/+bug/1872555
[23:46] <OvenWerks> Says it was built Mon, 23 Mar 2020 07:09:56 +0100
[23:47] <OvenWerks> the reason for build was: * No-change rebuild for libgcc-s1 package name change.
[23:48] <OvenWerks> I would think that should cover it...
[23:52] <OvenWerks> nope, * GCC snapshot, taken from the trunk (20200411, f883c46b487). Matthias Klose<EMAIL_ADDRESS>Sat, 11 Apr 2020 15:58:53 +0200
[23:53] <OvenWerks> This is from the changes list on the installed package. So maybe just a rebuild will work.
[23:58] <OvenWerks> added a comment to the bug report to this effect
[23:59] <OvenWerks> Eickmeyer: you may wish to boost the importance on the bug. I can't


[03:16] <ZugZug_> hello!
[03:17] <ZugZug_> I wasn't sure which room to try - but I'm thinking about building my own battery-powered system, and wanted to know how battery life gets reported to the OS
[03:17] <ZugZug_> Any idea how that works
[03:17] <ZugZug_> ?


[03:32] <jagwire_> hey, anyone around?
[03:33] <jagwire_> I've been searching for awhile regarding sound issues
[03:34] <jagwire_> I have a toshiba tecra m7-s7331 with (I'm pretty sure) a realtek alc262 driver codec
[03:34] <jagwire_> and I can't seem to get anything to work.
[13:02] <heng> does anybody know the best channel to get assistance on debugging a karmic suspend issue is? There's too much noise in #ubuntu+1
[18:34] <chsaedawg1> Hey my mouse is moving on its own, without moving anything. How do i fix that?
[20:11] <kroni__> hi
[20:11] <kroni__> i ma lost
[20:14] <kroni__> guys?
[20:14] <kroni__> can i aks u something?
[23:22] <roscoe> anyone know where I can find an up to date list of usb wireless network adapters that work out of the box?
[23:26] <The_Jag1> hi all
[23:26] <The_Jag1> anyone with a asus notebook?


[09:11] <tseliot> tjaalton: did you read my question?
[09:19] <tjaalton> tseliot: yes, I'll update wacom, and maybe a time to fix -joystick too..
[09:22] <tseliot> tjaalton: ok, I'll work on the rest then. Thanks
[10:42] <virtuald> my radeon doesn't work with modeset in karmic :/ my displays turn off when x/gdm starts
[20:21] <Duke`> where is Sarvatt? not seen him for weeks
[21:57] <AlanBell> evening all
[21:58] <AlanBell> I have an intel atom motherboard with integrated graphics. max opengl texture size is 2048. My monitor is 2048x1152
[21:58] <AlanBell> compiz worked fine in Jaunty, (except for white title bars on fully maximised windows)
[21:59] <AlanBell> in Karmic I get a black or corrupted screen when compiz starts, except for a 1 pixel strip on the far left
[21:59] <AlanBell> I can do alt-f2 metacity --replace to get working again. I would kind of like compiz though.
[22:51]  * popey does a little X shaped dance at https://bugs.edge.launchpad.net/xserver-xorg-video-intel/+bug/403530/comments/6
[22:52] <popey> if someone wants to close that, that would be groovy