[00:17] <OvenWerks> It has gone in horizontal.
[00:17] <OvenWerks> Paul likes the contrast to "other" strips
[00:19] <OvenWerks> I have tried to get it to use application colours/theme so it should match other stuff in MB
[00:22] <Eickmeyer> Nice.
[02:05] <krytarik> Eickmeyer: https://git.launchpad.net/studio-controls/tree/debian/control#n26 - just noticed it's spelled "-contols" there. >_>  But also, nice move to make the tool distro-agnostic!
[02:06] <Eickmeyer> krytarik: Oof....
[02:06] <Eickmeyer> teward: We missed something. ^
[02:07] <Eickmeyer> Not a huge issue yet.
[02:07] <krytarik> Yeah, just as see it..
[02:07] <teward> we can REJECT the upload :p
[02:07] <Eickmeyer> True.
[02:09] <Eickmeyer> teward: typo fix pushed, feel free to reupload as soon as we get that reject.
[02:10] <Eickmeyer> krytarik: But yeah, it's something that OvenWerks and I had been contemplating for a while.
[02:14] <teward> Eickmeyer: that was rejected I just pulled from git again, this ready to go now?
[02:14] <Eickmeyer> Yes, typo is fixed.
[02:15] <teward> okay pushed again
[02:15] <Eickmeyer> Ok
[02:16] <OvenWerks> Eickmeyer: WRT bug 1872187, I have looked at the code and the docs on the same code... unless python has changed or the gi lib, I don't know what that would be.
[02:16] <OvenWerks> sorry not that one
[02:17] <OvenWerks> the one in the email I just got:
[02:17] <Eickmeyer> I feel as though that was a false positive, but I need to hear back yet. It won't let me look up the error for some strange reason.
[02:17] <OvenWerks> Bug 1867705
[02:17] <Eickmeyer> That's a private bug.
[02:17] <OvenWerks> you have now marked it as a duplicate
[02:18] <OvenWerks> Ah right
[02:18] <OvenWerks>  I remember, I can get to it
[02:18] <OvenWerks> I am wondering if this is one of those wayland things
[02:19] <Eickmeyer> Might be, but it was a prerelease version anyhow. Also, "Argument 1 does not allow None as a value" screams as though the audio device had no descriptor.
[02:20] <OvenWerks> argument 1 of __init__
[02:21] <Eickmeyer> Oh, I see, so it's dying on launch, you think?
[02:22] <OvenWerks>     def __init__(self): is what is there... maybe self is not initialized before it gets to there
[02:23] <Eickmeyer> So is it a duplicate or no?
[02:23] <OvenWerks> Except self is argument 0? I would think
[02:24] <Eickmeyer> Also StevenJayCohen hasn't reported this kind of bug, so I think it might have been an isolated incident.
[02:25] <OvenWerks> Is there a choice in vanilla to use wayland or x?
[02:25] <Eickmeyer> Yes, during login.
[02:25] <Eickmeyer> I've used it both ways myself and had no issues.
[02:26] <OvenWerks> Are there actually applications written to use wayland natively?
[02:26] <OvenWerks>  So maybe can't reproduce?
[02:26] <Eickmeyer> Yes, but ours uses Xwyaland, I think.
[02:27] <Eickmeyer> Cant reproduce.
[02:29] <OvenWerks> wayland has a x compatability layer... but it is not fully compatable... and the developers of wayland don't care "because x is wrong anyway"
[02:32] <Eickmeyer> OvenWerks: Mar 16 22:39:34 hostname gnome-shell[1859]: Connection to xwayland lost
[02:34] <Eickmeyer> Looks like they were having a plethora of video-related errors too.
[02:34] <Eickmeyer> Here's the kicker though: hostname /usr/lib/gdm3/gdm-x-session
[02:35] <Eickmeyer> They weren't even running Wayland.
[02:36] <Eickmeyer> The other thing is the date: March 16. The final version of GNOME 3.36 hadn't even hit the archive yet.
[02:36] <Eickmeyer> There's too much wrong with this bug report to say what definitively went wrong.
[02:49] <OvenWerks> So long as you have run it on vanilla both x and wl I am happy
[02:50] <OvenWerks> I would go with does it happen in 20.04 release... or something.
[02:53] <OvenWerks> Yup like that
[15:42] <Eickmeyer> OvenWerks: Ooof... that same bug appeared in the version headed into the archive: https://pastebin.ubuntu.com/p/BS8dNqknj4/
[15:42] <Eickmeyer> Definitely Wayland related.
[16:09] <Eickmeyer> OvenWerks: Nope, might not be Wayland related. I'm going to give this a few tests in Ubuntu proper and see if I can duplicate the bug. I've assigned this "critical", so, unfortunately, we're going to have to get this resolved before we can work on studio-controls by itself.
[16:34] <Eickmeyer> OvenWerks: I was able to duplicate the crash. Seems like a newer version of Python is to blame?
[16:35] <Eickmeyer> wonko: If you're around, we could use some Python help with ubuntustudio-controls
[16:35] <Eickmeyer> ALL HANDS ON DECK: This is a CRITICAL bug.
[16:36] <Eickmeyer> Launches fine from the terminal.
[16:37] <Eickmeyer> And then it's fine.
[16:37] <Eickmeyer> Strange.
[16:38] <wonko> Yeah, what's up?
[16:38] <Eickmeyer> wonko: So, we have an interesting bug in Ubuntu Studio Controls that's happening when it's first launched on Ubuntu (proper, GNOME desktop). 
[16:39] <Eickmeyer> ypeError in __init__(): Argument 1 does not allow None as a value Edit
[16:39] <Eickmeyer> *TypeError in __init__(): Argument 1 does not allow None as a value Edit
[16:39] <Eickmeyer> minus the "Edit"
[16:39] <Eickmeyer> Traceback is here: https://launchpadlibrarian.net/469360059/Traceback.txt
[16:42] <wonko> Without seeing the code or having a system to test on I'm going go guess that screen.get_active_window() is returning None and that's not valid?
[16:42] <Eickmeyer> That would make sense, but I'm no python expert.
[16:42] <wonko> do you have a link to the code?
[16:43] <Eickmeyer> wonko: https://git.launchpad.net/ubuntustudio-controls/tree/usr/bin/ubuntustudio-controls
[16:47] <Eickmeyer> Looks like it's the unused Wacom tablet settings.
[16:50] <wonko> so what you should do is get the results from screen.get_active_screen() and if it's None skip that next bit. That's just a WAG not having followed the entire progam flow, however.
[16:50] <Eickmeyer> wonko: Well, that makes logical sense.
[16:50] <Eickmeyer> OvenWerks: Thoughts? ^
[17:15] <teward> could also try/accept in that section of the code to skip on error.
[17:15] <teward> which makes more sense than attempting to store the value first before handling
[17:16] <teward> (saves memory long-run)
[17:16] <teward> (albeit a tiny bit of memory but still)
[17:17] <teward> Eickmeyer: OvenWerks: ^
[17:17] <teward> s/accept/except/
[17:18] <Eickmeyer> teward: I don't have any idea how to do that, I'm not a python coder.
[17:18] <teward> i do ;)
[17:18] <teward> OvenWerks probably does too
[17:18] <teward> but i don't want to futz with controls unless I can avoid it :)
[17:18] <teward> minor packaging issues, sure, but not the source :)
[17:18] <Eickmeyer> I totally get that.
[17:19] <Eickmeyer> I'd rather OvenWerks or wonko took this on, personally.
[17:19] <Eickmeyer> Bug 1867705 is now public.
[17:22] <wonko> yeah, try/except is probably a better way. good call teward.
[17:22] <teward> python 101 :)
[17:22] <wonko> I'm trying to write less python these days. :)
[17:24] <teward> Eickmeyer: isn't https://bugs.launchpad.net/ubuntu/+source/ubuntustudio-controls/+bug/1877612 a dupe of 1867705?
[17:26] <teward> if these're dupes then I can dupe em
[17:37] <Eickmeyer> teward: Yeah, it's a dupe. I marked it as such.
[17:37] <teward> cool
[19:07] <OvenWerks> If it is the tablet stuff... it will most likely be removed. I have found out that the tablet's "area" has nothing to do with the screen anyway.
[19:07] <OvenWerks> I have some school to do with my son for an hour or so. then I will look at it.
[19:08] <OvenWerks> Eickmeyer: do you want me to just remove the tablet code? For what direction we are planning for that it looks like I will have to start over anyway :(
[19:09] <Eickmeyer> OvenWerks: Yeah, might as well. It's causing issues. :/
[19:26] <Eickmeyer> RikMills: Are you around? I'm trying to figure out how to configure the default GTK theme.
[19:29] <Eickmeyer> OvenWerks: Let me know when you have this fixed.
[21:00] <OvenWerks> Eickmeyer: it needs testing on a problematic system
[21:01] <OvenWerks> Eickmeyer: I had another idea... but it is not de agnostic.
[21:02] <OvenWerks> I was thinking a button on the tablet page that goes to the setup applet for plasma's tablets.
[21:02] <OvenWerks> I don't know if we could have a list of known setup applets and run the first one we find...
[21:03] <OvenWerks> anyway, that is for later. The fix is in us-c but not s-c
[21:04] <Eickmeyer> OvenWerks: Yeah, I can spin-up a default Ubuntu system and do the diagnostic.
[23:45] <Eickmeyer> OvenWerks: I got the fix, looks like it worked. I'll go ahead and SRU this.
[23:47] <OvenWerks> :) thanks
[23:48] <OvenWerks> That was a bit of a long drop out... Cable is not as good as the old copper ADSL...
[23:48] <Eickmeyer> Yeah, that's the downside. The upside is, at least theoretically, it's faster.
[23:50] <OvenWerks> Much faster even upload