[10:37] <sakrecoer> zequence: i'll test that tonight, have to deal with tons of paperwork for the unemployment office today
[16:35] <OvenWerks> Good news: qjackctl now works :) \o/
[16:36] <OvenWerks> Bad news: Qjackctl comes default dbus turned off... pulse/jack bridging no longer works out of the box :P
[16:39] <Anon1024> hi
[16:41] <OvenWerks> hey
[17:53] <zequence> OvenWerks: That truly sucks. Wonder why they did that?
[18:13] <OvenWerks> Bug #1567589 
[18:16] <OvenWerks> zequence: I do not think that was done on purpose. The older version of qjackctl used the option "Enable D-bus interface" _is_ enabled, but it no longer means "use jackdbus" it now means "allow qjackctl to be controlled vis dbus" there is a new option "Enable JACK D-Bus interface".
[18:16] <OvenWerks> The new option needs to be enabled.
[18:18] <OvenWerks> zequence: even though the indicator now works as expected, I still need to start qjackctl as:
[18:18] <OvenWerks> export XDG_CURRENT_DESKTOP=Unity; qjackctl
[18:18] <OvenWerks> to get the icon image to show correctly.
[18:19] <OvenWerks> But the main thing is that the indicator menu does work correctly and it is no longer possible to "freeze" the desktop.
[18:26] <zequence> OvenWerks: There must be a reason why Rui would disable that by default
[18:47] <OvenWerks> zequence: ubuntu packaging makes a number of default settings changes in qjackctl. including changing Rui's default of 48k (which is more correct) to 44k1 (which is generally wrong).
[18:51] <OvenWerks> Dmitry says he will fix this.
[19:12] <zequence> OvenWerks: Yes, but this was not an Ubuntu packaging change. It was upstream, or so I read from the upstream changes
[19:14] <OvenWerks> zequence: when there are upstream changes, the new package is brought into ubuntu and the former patches applied... at least for settings things like this.
[19:15] <zequence> OvenWerks: I am very well aware of the 48kHz vs 44.1kHz settings, but that is not what we are talking about
[19:15] <zequence> We are talking about the dbus settings. Why was it changed upstream? That was my question.
[19:16] <zequence> You seem to be claiming this was changed in the UBuntu packaging
[19:16] <OvenWerks> zequence: to use jackd1, jackd2 or jackdbus is a personal thing. In a case where the system has only jackd1, jackdbus would have to be off to work. But in Ubuntu's case jackdbus is shipped and the pulsejack bridge package depends on the use of jackdbus.
[19:16] <zequence> Still doesn't explain why upstream would change the setting.
[19:16] <zequence> Let me look it up
[19:17] <OvenWerks> upstream changed the _name_ of the setting, not the setting itself.
[19:17] <OvenWerks> upstream changed the name of the setting because it was unclear.
[19:17] <zequence> Ah, it was done in Debian, perhaps
[19:18] <OvenWerks> it is even less clear now because Rui added another dbus option, so Rui changed the name of the settings.
[19:18] <zequence> Or, maybe not. Maybe Dmitry tried to refresh the patch
[19:21] <zequence> Ok, so as you were saying there are two options now, instead of one, and both need to be enabled
[19:22] <OvenWerks> I think so. The problem is that the new option uses the same name as the old and the old one was changed.
[19:23] <zequence> The patch is added in Debian already, so that is the upstream for the patch
[19:24] <OvenWerks> AH, I know ubuntu adds a patch to that too. But that may be different a again I have not looked at it for a while.
[19:24] <zequence> So is the patch for the rate, I noticed
[19:25] <zequence> Ubuntu just copies the source as is from Debian
[19:25] <zequence> THink maybe the patch may have appeard in Ubuntu first, and then added to Debian
[19:30] <OvenWerks> could be. 44.1 is from the pulse team, I think.
[19:30] <zequence> Dmitrys changes will be unique for xenial. Most probably Debian packaging will do something similar later
[19:30] <OvenWerks> won't get changed
[19:30] <OvenWerks> there is still a bug in qt5 they are hoping to get fixed by release or shortly there after.
[20:16] <zequence> We need to build and test the option and give Dmitry and answer, so he can make the proper change
[20:16] <zequence> I'll give it a try
[20:19] <zequence> Ah, right, you already said use both options
[20:19] <OvenWerks> zequence: right, I thought was it would be the same as what it has been in the past.
[20:34] <OvenWerks> zequence: just noticed that my ALSA setting are no longer saved from one boot to the next.
[20:35] <OvenWerks> At first I thought it was just the first time I had used it. but it seems not. (using a d66 but any ice1712 would be the same)
[20:37] <zequence> OvenWerks: That's not fun
[20:38] <OvenWerks> zequence: I don't know what used to do that... but it seems to me we removed something like that... an xfce utility.
[20:39] <OvenWerks> knome: any thoughts about what xubuntu does with this?
[20:39] <knome> let me get back to you in some time, focusing on sth else right now
[20:40] <OvenWerks> zequence: this is somewhat hidden because internal IFs  get set dynamically by Pulse
[20:40] <OvenWerks> knome: no problem no hurry.
[20:54] <zequence> OvenWerks: Sure it's not alsa?
[20:58] <OvenWerks> zequence: not really sure, however, it seems I will not be able to look at it for a bit... one of my drives is failing and I need to move the system over to another drive.
[21:07] <OvenWerks> zequence: it is an alsa call, but I think it is another package that does that call. That is I do not think ALSA does it automatically.
[21:45] <OvenWerks> /usr/sbin/alsa-info.sh has a bug. It does not recognize jackdbus as a running jackd.
[21:46] <OvenWerks> I am not usre what package that is in (or what the CLI command to find out is.
[21:47] <OvenWerks> (it would be a simple patch to the shell to add jack_control status
[22:00] <zequence> OvenWerks: Cool tool
[22:00] <zequence> Didnt' know about that
[22:00] <zequence> IT's doing much of what I was working on for -controls
[22:01] <zequence> Except lots more