/srv/irclogs.ubuntu.com/2016/04/07/#ubuntustudio-devel.txt

sakrecoerzequence: i'll test that tonight, have to deal with tons of paperwork for the unemployment office today10:37
OvenWerksGood news: qjackctl now works :) \o/16:35
OvenWerksBad news: Qjackctl comes default dbus turned off... pulse/jack bridging no longer works out of the box :P16:36
Anon1024hi16:39
OvenWerkshey16:41
zequenceOvenWerks: That truly sucks. Wonder why they did that?17:53
OvenWerksBug #1567589 18:13
ubottubug 1567589 in qjackctl (Ubuntu) "New qjackctl version breaks OOTB use of pulseaudio-module-jack" [Undecided,New] https://launchpad.net/bugs/156758918:13
OvenWerkszequence: 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
OvenWerksThe new option needs to be enabled.18:16
OvenWerkszequence: even though the indicator now works as expected, I still need to start qjackctl as:18:18
OvenWerksexport XDG_CURRENT_DESKTOP=Unity; qjackctl18:18
OvenWerksto get the icon image to show correctly.18:18
OvenWerksBut the main thing is that the indicator menu does work correctly and it is no longer possible to "freeze" the desktop.18:19
zequenceOvenWerks: There must be a reason why Rui would disable that by default18:26
OvenWerkszequence: 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:47
OvenWerksDmitry says he will fix this.18:51
zequenceOvenWerks: Yes, but this was not an Ubuntu packaging change. It was upstream, or so I read from the upstream changes19:12
OvenWerkszequence: 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:14
zequenceOvenWerks: I am very well aware of the 48kHz vs 44.1kHz settings, but that is not what we are talking about19:15
zequenceWe are talking about the dbus settings. Why was it changed upstream? That was my question.19:15
zequenceYou seem to be claiming this was changed in the UBuntu packaging19:16
OvenWerkszequence: 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
zequenceStill doesn't explain why upstream would change the setting.19:16
zequenceLet me look it up19:16
OvenWerksupstream changed the _name_ of the setting, not the setting itself.19:17
OvenWerksupstream changed the name of the setting because it was unclear.19:17
zequenceAh, it was done in Debian, perhaps19:17
OvenWerksit is even less clear now because Rui added another dbus option, so Rui changed the name of the settings.19:18
zequenceOr, maybe not. Maybe Dmitry tried to refresh the patch19:18
zequenceOk, so as you were saying there are two options now, instead of one, and both need to be enabled19:21
OvenWerksI think so. The problem is that the new option uses the same name as the old and the old one was changed.19:22
zequenceThe patch is added in Debian already, so that is the upstream for the patch19:23
OvenWerksAH, 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
zequenceSo is the patch for the rate, I noticed19:24
zequenceUbuntu just copies the source as is from Debian19:25
zequenceTHink maybe the patch may have appeard in Ubuntu first, and then added to Debian19:25
OvenWerkscould be. 44.1 is from the pulse team, I think.19:30
zequenceDmitrys changes will be unique for xenial. Most probably Debian packaging will do something similar later19:30
OvenWerkswon't get changed19:30
OvenWerksthere is still a bug in qt5 they are hoping to get fixed by release or shortly there after.19:30
zequenceWe need to build and test the option and give Dmitry and answer, so he can make the proper change20:16
zequenceI'll give it a try20:16
zequenceAh, right, you already said use both options20:19
OvenWerkszequence: right, I thought was it would be the same as what it has been in the past.20:19
OvenWerkszequence: just noticed that my ALSA setting are no longer saved from one boot to the next.20:34
OvenWerksAt 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:35
zequenceOvenWerks: That's not fun20:37
OvenWerkszequence: I don't know what used to do that... but it seems to me we removed something like that... an xfce utility.20:38
OvenWerksknome: any thoughts about what xubuntu does with this?20:39
knomelet me get back to you in some time, focusing on sth else right now20:39
OvenWerkszequence: this is somewhat hidden because internal IFs  get set dynamically by Pulse20:40
OvenWerksknome: no problem no hurry.20:40
zequenceOvenWerks: Sure it's not alsa?20:54
OvenWerkszequence: 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.20:58
OvenWerkszequence: 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:07
OvenWerks/usr/sbin/alsa-info.sh has a bug. It does not recognize jackdbus as a running jackd.21:45
OvenWerksI am not usre what package that is in (or what the CLI command to find out is.21:46
OvenWerks(it would be a simple patch to the shell to add jack_control status21:47
zequenceOvenWerks: Cool tool22:00
zequenceDidnt' know about that22:00
zequenceIT's doing much of what I was working on for -controls22:00
zequenceExcept lots more22:01

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!