[14:13] <OvenWrks> Eickmeyer[k]: thankyou for pkging controls... debugging
[14:15] <OvenWrks> USB plugging and unplugging does not seem to work in 21.10
[16:36] <OvenWrks> Huh, it seems the dbus message we monitor has changed... at least we still get some kind of message. I am guessing this is why the arch users where not getting display updates.
[16:56] <OvenWrks> changing the parsing of the dbus return fixes it... but, I am pretty sure it would no longer work in LTS. Also, it is obvious that teh dbus return string is "subject to change" anyway... so, new plan.
[16:58] <wonko> Is it a standard system dbus message?
[16:58] <wonko> because that being subject to change is kinda shitty
[16:59] <OvenWrks> wonko: I do not know if it can be considered "standard", I monmitored the system dbus while plugging usb devices in and out :)
[16:59] <wonko> That seems like a fairly standard action
[16:59] <wonko> that should hopefully not change on a whim, no?
[16:59] <wonko> who's driving this bus, anyway? :-P
[16:59] <OvenWrks> gnome...
[17:00] <OvenWrks> actually redhat
[17:02] <OvenWrks> It is ok. While it would be nice to be able to get the new/former device directly from the dbus string, I can rather look for usb devices that have a card number and do not have a PID and are not "hidden"
[17:03] <OvenWrks> And the opposite for removed
[17:07] <OvenWrks> The forced gnome sytle on all gnome applications is really bad!
[18:34] <Eickmeyer> OvenWrks: Just saw this. The joys of an ever-changing API.
[18:34] <Eickmeyer> OvenWrks: The biggest problem I see is that it won't be backwards-compatible with 20.04 if we completely change the code rather than sniffing for differences.
[18:36] <Eickmeyer> OvenWrks: Another problem I've seen is that when I stop JACK I get about 7 qasmixer instances opening.
[18:38] <OvenWrks> Eickmeyer: what I am doing is just using the dbus message to tell me I have to do something. I then look in /proc/asound/ to find out what has changed...
[18:38] <OvenWrks> Eickmeyer: the QASmixer thing sounds like you have not upgraded to 2.1.67 yet
[18:38] <OvenWrks> that did happen in .65
[18:39] <OvenWrks> But runnung impish here I can't make that happen
[18:39] <OvenWrks> (with .67)
[18:43] <Eickmeyer> OvenWrks: I'm definitely on .67.
[18:43] <Eickmeyer> I'll try to see if I can reproduce the problem.
[18:44] <Eickmeyer> OvenWrks: Can't reproduce, false alarm.
[18:44] <Eickmeyer> Fixed.