[00:25] <studiobot> <Eickmeyer> (New chat photo, 640x640) https://i.imgur.com/jYVJj6U.jpg
[17:32] <OvenWerks> Eickmeyer: dumb question time... If I start -controls for the first time (no rc file) and jack is already running by some means... what should -controls do?
[17:33] <Eickmeyer> OvenWerks: Without any interaction?
[17:34] <OvenWerks> The default in the case of a config save is to save the default jack state which is stopped.
[17:34] <OvenWerks> This will also stop jack (probably wrong)
[17:34] <Eickmeyer> If it detects Jack is running, then it should make the RC keep that seting.
[17:34] <Eickmeyer> That's just my opinion.
[17:35] <OvenWerks> It would not be hard to set jack to True. but should it also say something about having started jack some other way?
[17:36] <Eickmeyer> Perhaps. At least as a warning that a non-default setup was detected?
[17:36] <OvenWerks> Eickmeyer: if someone started jack by commandline or qjackctl there is probably not a problem... cadence that is a problem
[17:37] <OvenWerks> cadence is blacklisted so maybe not a problem.
[17:37] <Eickmeyer> Yeah, cadence is also a conflict in the package.
[17:39]  * OvenWerks just tried rm .config/autojackrc for the first time :)
[17:42] <Eickmeyer> Nice. Debugging for first-use, I take it.
[17:49] <OvenWerks> Ya, I actually think it didn't check what I want to check... but realize what I wanted to check doesn't matter
[17:50] <OvenWerks> Eickmeyer: now if the user has used -controls at least once and turned jack off and the next startup of -controls finds jack running... same thing?
[17:51]  * OvenWerks thinks so
[17:52] <OvenWerks> I think that because the jack indicator shows jack is running, the saved value should be set that way.
[17:52] <Eickmeyer[m]> I agree. I think if someone makes a change outside of Ubuntu Studio, it should warn them.
[17:52] <Eickmeyer[m]> Rather, outside of -controls
[17:53]  * Eickmeyer had ot jump over to Matrix for a screenshot of the shenanigans in #ubuntustudio
[17:54] <OvenWerks> warning may be added later
[17:55] <OvenWerks>  If the person starts -controls and finds jack is running, they can puzzle over how that may have happened...
[17:55] <OvenWerks> :)
[17:56] <Eickmeyer[m]> Right. We want this to be user-friendly, which means making sure they understand what their system is doing.
[18:10] <Eickmeyer[m]> M_aD, OvenWerks : RE: that reddit post: I did a little bit of trimming of an old, outdated, and horribly written wiki article. And by a little trimming, I mean practically replaced the whole thing: https://help.ubuntu.com/community/UbuntuStudioPreparation
[18:52]  * OvenWerks has built a new -controls for people to break if possible.
[18:53] <OvenWerks> Eickmeyer: please take a look at the new jack status indicator.
[18:56] <Eickmeyer> OvenWerks: updating now
[19:00] <Eickmeyer> OvenWerks: Looks like it's built but not published. I'll be waiting for paint to dry.
[19:36] <Eickmeyer> OvenWerks: We have a problem. https://paste.ubuntu.com/p/5wcRw2Dg9d/
[19:38] <OvenWerks> which version OS?
[19:39] <Eickmeyer> 19.04
[19:39] <OvenWerks> Ok
[19:39] <OvenWerks> 18.04 here.
[19:44] <Eickmeyer> OvenWerks: So, it won't start unless Jack is already running.
[19:49] <OvenWerks> Can you stop jack after it is started?
[19:50] <Eickmeyer> I could start Jack from qjackctl, and then start it. After that, I could stop it and start it.
[19:50] <Eickmeyer> However, if I stopped it, closed it, and tried reopening it, it wouldn't reopen.
[19:50] <OvenWerks> Ok, I don't think I have tried that :)
[19:51] <Eickmeyer> Only workaround was to start Jack manually and then opening it.
[19:51] <OvenWerks> nope, I need to fix it
[19:51] <Eickmeyer> Okay.
[19:51] <Eickmeyer> I have some errands to run. I should be back in a couple hours.