[00:53] <OvenWerks> Eickmeyer[m]: I think I may have found a way. I think all DEs use indicator-application.service. (would have to check)
[00:56] <OvenWerks> It seems indicators-pre.target goes away after starting indicators... if I look for the right combination of targets and services running or not, I should be able to detect one of the indicator servoces dying and use that to que an exit.
[01:18] <OvenWerks> Maybe indicator-sound.service would be better for us.
[01:18] <OvenWerks> Eickmeyer[m]: if I come up with a fix for de stuff like this, which package should it end up in?
[01:24] <OvenWerks> I am thinking of making a session_monitor.service that requires one of the indicators (which seem to die on their own when the session manager goes away) and use the stopping command to exit the session.
[01:37] <Eickmeyer[m]> OvenWerks: I'm pretty sure Gnome doesn't use any indicators.
[01:47] <OvenWerks> so such a file should go in the setting package for a DE
[01:53] <Eickmeyer[m]> I'm up for any solution. Let's give it a shot.
[05:39] <OvenWerks> well, I have a service running sleep infinity... I just have to figure the command to get the session to fully die. I am trying a systemctl start first, but it may not run if it is not a human running it in which case I will have to try a dbus-send message.
[05:40] <OvenWerks> Of course the update box was there so now I am waiting for the update to finish :)
[05:50] <OvenWerks> cool, that was easy.
[05:52] <OvenWerks> systemd[1473]: Reached target Shutdown.
[05:53] <OvenWerks> and in autojack.log.old: 2020-01-31 21:46:05,298 - root - WARNING - Got signal number: 15 - Dying.
[05:54] <OvenWerks> Very satisfying
[06:32] <OvenWerks> ok Eickmeyer[m]: this seems quite solid. It will work for any DE that loads indicator-sound.service 
[06:32] <OvenWerks> I need to put this file (and it's link) in some package. Which one?
[06:36] <OvenWerks> and having done so there will need to be a postinstall that A: runs systemctl enable on the servce or B: creates a symlink. I would prefer to create the symlink as then it could go in /usr/lib/systemd/user/ rather than /etc/* which is more apropriate for a package solution.
[06:37] <OvenWerks> this applies to studio.service as well though of course it for sure belongs in the -controls package.
[06:39] <OvenWerks> I have looked over your paste of a gnome screen session and I am not sure what happens in the case of logout and in as a different user. It does not look like the systemd --user session goes all the way down. The second login does not pass through basic and default targets.
[06:40] <OvenWerks> So while it may work ok when logging out and then back in as the same user, I wonder what it does with a different user.
[08:04] <OvenWerks> quick note... we need to save the alsa settings for audio cards somehow. I keep getting the device turned allmost all the way down. I think it has to do with pulse turning it down in the other user's session.
[16:52] <Eickmeyer[m]> OvenWerks: since it has to do directly with the operation of autojack, I'd say it belongs in the ubuntustudio-controls package.
[16:53] <Eickmeyer[m]> As far as the alsa issue, I think that'
[16:53] <Eickmeyer[m]> s a known bug in alsa.
[17:36] <OvenWerks> ok, I will put it in -controls.
[17:38] <OvenWerks> I think it would be possible to use the same idea to make gnome screen work too.
[17:38] <OvenWerks> (properly)
[19:15] <Eickmeyer[m]> OvenWerks: I switched out a few gnome tools for mate tools in the seed to match what Xubuntu has.
[19:20] <OvenWerks> ok
 @azbulutlu Have you made a new default wallpaper yet? Or is that even on your radar?
[20:55] <Eickmeyer[m]> I just figured it's February, less than a month to Feature Freeze, let's get a wallpaper contest going.
[23:21] <Eickmeyer[m]> JackWinter: To answer your question, yes we have Ross Gammon (He's a Debian Developer) but he doesn't have very much time on his hands to deal with pushing stuff upstream. Anytime I do an RFP it's met with silence, so I've given up there.
[23:21] <Eickmeyer[m]> I've done a lot of packaging just over the past year, and it's landed in Ubuntu.
[23:34] <Eickmeyer[m]> Oh, wrong Jack.
[23:34] <DalekSec> Well yes, RFP is simply "someone somewhere has interest", someone else has to actually see that and also have interest.
[23:37] <Eickmeyer[m]> DalekSec: There lies the problem. Nobody sees it and/or has interest. I've had much better luck getting sponsorship on Ubuntu, especially now that teward is on the team. That said, I try not to bog him down except the once-in-a-while "OH CRAP WE'RE SCREWED".
[23:38] <DalekSec> ...Sponsorship isn't the same as a RFP, the latter is "Will you package and maintain it for me?"
[23:39] <Eickmeyer[m]> Well, I've gone down the sponsorship road too with no avail.
[23:43] <DalekSec> Ah, that's quite unfortunate. :/
[23:44] <DalekSec> Sometimes one can have better luck if one can find a team as an umbrella to put it under, I've had some luck with that at least.
[23:48] <teward> Well the thing about RFP is if you take maintainership and the wuality of the package is good in Debian its trivial to get sponsors
[23:48] <teward> Case in point xca or vmfs6-tools which I maintain in Debian
[23:49] <teward> I submit a new revision or version its sponsored within 48h max
[23:49] <teward> But yeah same thing there, if theres an overarching team to stick it under that helps.
[23:49] <teward> Sometimes you also have to be annoying in Debian to get a sponsor
[23:49] <teward> :P
[23:50] <teward> You also can specify multiple uploaders in Debian
[23:50] <teward> So if you needed me with my evilness to help you can designate me an uploader
[23:50] <teward> Or a maintainer
[23:50] <teward> Sponsor finding in Debian is easy when you nag em on IRC like I do xD
[23:51] <teward> Everything i get sponsored goes through Mentors too so it gets a little more visibility and automatic tests
[23:51] <teward> But thats just a tiny segment of it :P