XPost: linux.debian.bugs.dist   
   From: post@ralfj.de   
      
   Hi,   
      
   > On Wed, Dec 17, 2025 at 02:05:41PM +0100, Ralf Jung wrote:   
   >> Hi all,   
   >>   
   >> By trying out various snapshot kernels, I now got it nailed down to a single   
   >> major version bump:   
   >>   
   >> 6.13.11-1~exp1 is still good.   
   >> 6.14.6-1~exp1 has the problem.   
   >   
   > While I understand from the context you gave that might not be the   
   > easiiest thing to make possible, but I think the most effective next   
   > step would be now to try upstream 6.13 and upstream 6.14.6 and then   
   > bisect.   
      
   There's probably a subfolder I can restrict this to? Which folder has the   
   webcam   
   drivers? (And maybe the v4l infrastructure.)   
      
   > If you have a second device available maybe it is enough to join with   
   > that to the call and trigger the problem? In particular if you can   
   > take off work the device which exposes the problem.   
      
   Yeah I can probably reproduce it by joining from the browser and the native   
   client.   
      
   > I do realize this is much we ask, but you are as well the only one   
   > able to reproduce the problem on the particular hardware, so actually   
   > in the best position to find the offending change.   
      
   This is a pretty common webcam model so it's hard to believe that I am the only   
   one who is affected... but with the kernel not having a (functional) central   
   bugtracker we wouldn't even know about it. I also have to imagine it'd be   
   easier   
   to bisect this if someone familiar with webcam drivers had a clue about what   
   happens in the release wehre this broke... oh well.   
      
   I will have to see if I have time and patience for a longer bisecting session   
   over the holidays.   
      
   Kind regards,   
   Ralf   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)