[03:01] <hallyn> uh, huh.  i don't know whether this is related to the new cve fix today, but my usb bus seems to be dead -plugging in either my trackpad or my yubikey does nothing. no power.
[03:02] <sarnold> yikes
[03:08] <hallyn> yeah i've never seen that before -plug in the yubikey and it doesn't light up.  very weird.  nothing in dmesg.  i guess if this doesn't ring a bell, i'll have to do an ubuntu-bug
[14:37] <chiluk> hallyn... you might just have an actual hardware problem.  
[14:38] <chiluk> if you go back to a previous kernel does it start working again?
[15:17] <hallyn> boy that would suck
[15:17] <hallyn> well it was working at first with this kernel.  It was happened after some suspends
[15:18] <hallyn> So I' mnot sure how to reproduce it
[15:18] <hallyn> Also having trouble updating the firmware to the latest version.  (has failed twice).  maybe something to do with that.
[15:29] <chiluk> yuck.. yeah that might be part of it.. 
[16:58] <Guest56> hi there, dumb question, maybe we are "holding it wrong", but, currently "linux-generic-hwe-20.04-edge" meta package does not point to the latest security release (fixing "dirtypipe"), is that a bug, or intended or are we using the "wrong" metapackage?
[17:00] <Guest56> currently it points to "Version: 5.13.0.27.29~20.04.13" but in "USN-5317-1" it says this is fixed in "5.13.0.35.40~20.04.20" but the security announcement is also missing the "edge" hwe kernel..so.. we are confused :D
[17:06] <SvenKieske> above question is from me, I'm now properly registered
[17:15] <SvenKieske> we are really not sure if we are somhow using the wrong kernel packages or this is just a minor hiccup in the release process of the new kernel? we just want to be sure that we didn't introduce any errors on our side
[17:17] <SvenKieske> will be offline/afk for now, you can also mail me at s.kieske attt mittwald.de, thanks in advance! (I guess my IRC client will auto disconnect)
[18:50] <sarnold> hallyn: a pal who did a debian upgrade the other day had huge troubles with one of his displays.. the problem went away with reseating the hdmi, the guess is that fans cycling or similar were enough to take an 'almost problem' and turn it into an 'actual problem'..
[21:11] <hallyn> external display?  reseated hdmi plug?  or are you talking about a chip?
[21:15] <sarnold> the hdmi cable had come ever so slightly loose..
[21:20] <hallyn> i don't want to test it right now, but i'm wondering whether this kernel balks if i unplug the usb trackball while it's suspended
[22:17] <hans109h> How can I request/track if an upstream kernel patch commit can be/is added to a Ubuntu kernel for 21.10?
[22:20] <sarnold> hans109h: it's not the easiest trees to navigate, but there's a https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/impish that probably has the answers you need
[22:20] <sarnold> it's a good idea to git clone --reference ... linus's linux kernel tree, and re-use that for all the other releases you're interested in, too
[22:22] <hans109h> sarnold, thank you I'll explore that link.  Specifically I am interested in 4e6f55120c7eccf6f9323bb681632e23cbcb3f3c I did try to cherry-pick it, but I was unsuccessful in building and can't invest the time to debug right now.
[22:23] <sarnold> hans109h: git show 4e6f55120c7eccf6f9323bb681632e23cbcb3f3c on my own local checkout of that tree shows it, but I don't know enough about git to know if it came from my linus reference or not :) sigh
[22:25] <hans109h> sarnold, I hear you.  From that I've gathered it was added around linus's 5.17 rc4, so I was wondering what the chances are that it could possibly end up in a Ubuntu kernel in the 21.10 repo