[01:26] <OvenWerk1> zequence: can we use "replaces" in audio meta to get rid of the two old ones?
[02:06] <OvenWerk1> The bug with qjackctl.... Last week it worked (32 bit), but I am noticing on my 13.10 machine it doesn't. I will check the 14.04 again though. I am wondering if this is an upgrade thing? Just looking at the bug original install date...
[03:58] <len-test> zequence, Re back drops. The config file points to the exact file. more than once. Would it be better to have the config file point to ubuntustudio-default.png and have that be a link to whatever the current default is?
[03:59] <len-test> I am not sure which is more work, to change the link or the config file. Or which would upgrade better.
[04:00] <len-test> zequence, Re: the qjackctl in the systray. My fresh install of 14.04 had that systray icon working properly.
[04:11] <len-test> Ok, I just upgraded my 14.04 with the latest and the systray still works with qjackctl
[04:13] <len-test> A funny thing did happen though, When I logged out to log in so I could restart xfce, I ended up with two lightdm listed in panel one. (killed them)
[04:29] <len-test> Back to backdrops  :P  there are two places that backdrops might be kept that are specific to xfce and a generic one. I was unable to find anywhere that the actual path to icons was stored though, so it is probably pulled from the path of the file name in use.... let me test this... but I think that if we just put our backdrop in the generic directory and have the system config point at it, we will become standard.
[04:41] <len-test> zequence, To confirm, if we would put our backdrops in /usr/share/backgrounds/ and then use that in our config file
[04:42] <len-test> The next problem is that KDE, for example, uses /usr/share/wallpapers/
[04:45] <DalekSec> len-test: bug 1290575
[04:45] <len-test> lubuntu seems to use /usr/share/lubuntu/wallpapers.
[04:45] <len-test> That could very well be it yes.
[04:46] <DalekSec> It is, if you can reliably reproduce it, that would be helpful. (So far no one has had luck there.)
[04:49] <len-test> I added my "this affects me"
[04:49] <len-test> I will try one more time, but I have to go, if it happens a second time that would be great (I guess).
[13:21] <knome> zequence, https://code.launchpad.net/~ubiquity-slideshow/ubiquity-slideshow-ubuntu/html/+merge/211502
[13:21] <knome> zequence, is that all you want in the slideshow, or still some changes coming?
[15:20] <len-test> DalekSec, No joy with getting consistent lightdm troubles. Though it does seem to happen more often if I make use of one of the VTs in the login screen (c-a-F1).
[15:21] <len-test> The most I got was two in one boot, but not twice in a row.
[15:31] <len-test> zequence, new kernel today, jack initially seemed more stable, but I am getting popups telling me I am getting KernelOops. When those happen I get xruns
[15:32] <len-test> No surprise I guess
[15:39] <len-test> I tried looking through the log files (syslog and kern.log) but found nothing.
[15:42] <len-test> I am seeing more xruns again, but they seem to be at intervals.
[15:43] <len-test> Many of them seem related to pulse.
[15:47] <len-test> Part of that may be that the audio devices switched numbers... to normal and so pulse reactivated the one I had turned off.
[15:49] <len-test> Launchpad coughed on taking the bug report with a time out.
[15:49] <zequence> len-test: If you find a kernel bug, please report it
[15:49] <zequence> Ah
[15:49] <len-test> I will try another boot.
[15:49] <zequence> knome: I'm ready with all changes, yep
[15:50] <zequence> len-test: I'll look at the "replaces" option. Would be nice to get rid of those two metas.
[15:51] <zequence> len-test: which bug with qjackctl?
[15:51] <zequence> len-test: about the wallpapers, I've put the actual wallpapers in /usr/share/backgrounds/ubuntustudio, and symlinks to /usr/share/xfce4/backdrops
[15:52] <len-test> I am not sure at this point, it came in my email while I was away and reading tiny print on the phone
[15:52] <zequence> You can get lp:ubuntustudio-look to see it
[15:53] <len-test> Oops kernel problem showed again... another try for bug report...
[15:53] <len-test> jack has been stable for a while now
[15:54] <len-test> Untill I said that of course :)
[15:54] <zequence> I once had a problem BECAUSE of rtirq
[15:54] <zequence> Never happened again
[15:55] <len-test> But that may be the bug reporter thing. It is much more stable than the old kernel.
[15:56] <len-test> Bug #1294729 
[16:00] <len-test> The bug dialog has come up 4 times since boot. I am having trouble thinking of this one as usable.
[16:02] <len-test> Latency is better for sure, though still not as good as in the past, but I have not even tried tweaking at all.
[16:10] <len-test> zequence, I think the xruns may have been more to do with the kernel oops data logging/bug tracking. I am running jack on the edge of what it would normally do with hyperthreading turned on.
[16:12] <len-test> Turning hyperthreading off allows me to set -p 16.