=== housecat is now known as dax
[02:08] <Eickmeyer> OvenWerks: New response on bug 1872187
[02:08] <ubottu> bug 1872187 in ubuntustudio-controls (Ubuntu Groovy) "ubuntustudio-controls crashed with IndexError in refresh_dropdowns(): list index out of range" [High,In progress] https://launchpad.net/bugs/1872187
[04:25] <OvenWerks> Eickmeyer:  different bug. The -controls part is fixed
[04:27] <OvenWerks> The "Ubuntu Studio Controls" window is now visible and I can select the Jack Master Device (no USB) "chtrt5646,0,0 playback and capture device".
[04:27] <OvenWerks> That is what I was fixing
[04:39] <OvenWerks> Eickmeyer: I think the bug is fixed, the rest of things is pure support or a hw/firmware/user error. (pick one)
[04:41] <Eickmeyer> Yeah. This sounds like a support issue now. I'll upload and start the SRU process in the morning.
[04:42] <OvenWerks> no hurry, I think
[04:42] <OvenWerks> I am glad to have it pointed out to me
[04:43] <Eickmeyer> I've never known an audio device not to identify itself to the system like that.
[04:44] <OvenWerks> I think it is actually hdmi or something
[13:19] <studiobot> <azbulutlu> (Riot.im is still having issues so please do tag me with telegram for now - re-plasma it just does come with a wacom utility of its own, and indicator, (doesn't take away from ubuntu-controls having its own version through)
[13:21] <studiobot> <azbulutlu> and re-panel eickmeyer can you please explain the context of the question of the panel (and what you refer to as the panel? :) )
[15:11] <studiobot> <Eickmeyer> @azbulutlu [and re-panel eickmeyer can you please explain the context of the question of the …], I think the entire panel discussion had more to do with how OvenWerks does his workflow. He was looking for a replacement for cairo.
[15:12] <OvenWerks> yes, I like to have some sort of control to start apps when I log in with ssh -Y
[15:16] <OvenWerks> The last time I installed cairo-pannel on xfce it brought in a lot of extra gnomish stuff... I figgured it would be worse with kubuntu.
[15:16] <OvenWerks> latte-dock wocks just great
[17:09] <OvenWerks> Eickmeyer: I would say that the regression potential on the -controls bug fix is next to nil :)
[17:11] <OvenWerks> I would note that it has been tested on a system without this problem as well
[17:11] <OvenWerks> (should you need to know that)
[17:11] <Eickmeyer> OvenWerks: We can't say "none" because then it won't even get looked at.
[17:13] <OvenWerks>  :)
[17:14] <Eickmeyer> From https://wiki.ubuntu.com/StableReleaseUpdates: "If this section is None it is grounds for rejection..."
[17:34] <studiobot> <azbulutlu> plasma has its own widget system as far as I know
[17:34] <studiobot> <azbulutlu> so you don't have to use cairo at all
[17:34] <studiobot> <azbulutlu> ovenwerks and eickmeyer
[17:34] <studiobot> <azbulutlu> but then it would be plasma specific
[17:35] <studiobot> <Eickmeyer> @azbulutlu I'm pretty sure this was for his own use and nothing to be a default.
[17:35] <studiobot> <azbulutlu> aah
[17:35] <studiobot> <azbulutlu> in that case, KDE plasma has its own widgets
[17:35] <studiobot> <azbulutlu> so no need to use cairo there
[17:35] <studiobot> <azbulutlu> :)
[17:35] <studiobot> <azbulutlu> sorry. its been a strange week
[17:36] <studiobot> <Eickmeyer> Well, latte-dock seems to be working (it's a KDE project).
[17:36] <studiobot> <azbulutlu> and riot.im is stuck at the moment so I realized belatedly that I missed posts from you
[17:36] <studiobot> <azbulutlu> ah
[17:52] <OvenWerks> Hmm, maybe instead of setting up known tablets, I would be better off making invisible tablets visible...
[17:55] <OvenWerks> My tablet shows up as a game controller... 
[17:56] <OvenWerks> but all it shows is which button is pressed, no way to asign it, does not show position... blah
[18:00] <OvenWerks> xsetpointer -l aside from my keyboard, mouse, webcam, power button, etc. also shows: 13: "HID 256c:006e Pad" [XExtensionPointer]
[18:00] <OvenWerks> 14: "HID 256c:006e Pen" [XExtensionDevice]
[18:48] <Eickmeyer> Well, I think we can all ignore that last FTB on the CD image. Seems as though Launchpad went down at just the wrong time.
[19:37] <OvenWerks> @azbulutlu: I do not think I can come anywhere close to what KDE's tablet setup does. It is very good. The one area I can do though, is to make devices that are wacom compatable but do not show up for the KDE applet, show up.
[19:51] <OvenWerks> @azbulutlu: I do seem to have managed to get buttons 2 and 3 reversed with no way of getting back to the screen where I set it up. :P (clumsy fingers)
[20:06] <OvenWerks> now I can't find the file where the profile is stored :P
[20:12] <OvenWerks> Oh, they go from being called wacom to being called tablet
[20:28] <OvenWerks> @azbulutlu: a question for you... my screen is 1600x900 but somehow xsetwacom is using "Area" as 0 0 50800 31750
[20:28] <OvenWerks> do you know who that relates?
[20:29] <OvenWerks> It does seem to work correctly as only my left screen... 
[20:31] <OvenWerks> So what do these numbers really mean?
[20:37] <OvenWerks> when setting buttons on my tablet, the kde applet will not allow me to put in + even from the num pad it will show up as = I have to put in shift = I need to try it to see if it works. I guess
[20:45] <OvenWerks> no, shift = does not equal +, I just have to put in =