[Bug 1898352] Re: audacity kills rear microphone input on Starship/Matisse HD as soon as it starts

Another observation: The microphone input works perfectly fine with jackd, too. But if I start pulseaudio, then start and immediately quit audacity, then stop pulseaudio again and try to start jackd from qjackctl, qjackctl hangs and I have to force quit it. I also attach the log output from

[Bug 1898370] Re: obs-studio crashes with memory corruption when loading some jpg files

** Summary changed: - obs-studio crashes on startup + obs-studio crashes with memory corruption when loading some jpg files -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1898370 Title: obs-studio

[Bug 1878899] Re: Call trace from __video_do_ioctl

Same, happens on loading the v4l2loopback module: [ 1039.168432] v4l2loopback driver version 0.12.3 loaded [ 1039.172977] [ cut here ] [ 1039.172994] WARNING: CPU: 3 PID: 8520 at drivers/media/v4l2-core/v4l2-ioctl.c:1064 v4l_querycap+0x8b/0xa0 [videodev] [ 1039.172995]

[Bug 1878899] Re: Call trace from __video_do_ioctl

Argh, why did Firefox keep the contents of comment #6 in the edit box? Ignore comment #7, the relevant part is And I have since retired the AMD A10 system, same behaviour on [ 6442.968740] CPU: 0 PID: 45180 Comm: v4l_id Tainted: G W OE 5.4.0-33-generic #37-Ubuntu [ 6442.968741] Hardware name:

[Bug 1878899] Re: Call trace from __video_do_ioctl

Same, happens on loading the v4l2loopback module: [ 1039.168432] v4l2loopback driver version 0.12.3 loaded [ 1039.172977] [ cut here ] [ 1039.172994] WARNING: CPU: 3 PID: 8520 at drivers/media/v4l2-core/v4l2-ioctl.c:1064 v4l_querycap+0x8b/0xa0 [videodev] [ 1039.172995]

[Bug 1881399] Re: Kernel trace on loopback

Lauchpad is honestly completly broken. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1881399 Title: Kernel trace on loopback To manage notifications about this bug go to:

[Bug 1881398] Re: Call trace on insmod

Launchpad is broken, I reported this aginst v4l2loopback, not against linux. I'll try again. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1881398 Title: Call trace on insmod To manage

[Bug 1881402] [NEW] Launchpad bug report form is severly broken.

Public bug reported: Sorry for reporting against the wrong package, but launchpad doesn't behave predictably. Steps to reproduce: 1. Click "Report a bug" on https://bugs.launchpad.net/bugs/1878899. 2. The "Report a bug" form opens, with "linux" pre-filled as the package. 3. Change the package to

[Bug 1881399] Re: Kernel trace on loopback

** Changed in: linux (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1881399 Title: Kernel trace on loopback To manage notifications about this bug go to:

[Bug 1881398] Re: Call trace on insmod

** Changed in: linux (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1881398 Title: Call trace on insmod To manage notifications about this bug go to:

[Bug 1881399] [NEW] Kernel trace on loopback

Public bug reported: Fixed upstream: https://github.com/umlaeute/v4l2loopback/issues/257 See also: https://bugs.launchpad.net/bugs/1878899 ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs,

[Bug 1881398] [NEW] Call trace on insmod

Public bug reported: Fixed upstream: https://github.com/umlaeute/v4l2loopback/issues/257 Also https://bugs.launchpad.net/bugs/1878899 ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which

[Bug 1881403] [NEW] Call trace on insmod

Public bug reported: Fixed upstream: https://github.com/umlaeute/v4l2loopback/issues/257 See also: https://bugs.launchpad.net/bugs/1878899 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: v4l2loopback-dkms 0.12.3-1 ProcVersionSignature: Ubuntu 5.4.0-33.37-lowlatency 5.4.34 Uname: Linux

[Bug 1883493] Re: amdgpu hangs from time to time with *ERROR* Waiting for fences timed out!

What happens is that I am doing something and suddenly nothing moves except the mouse pointer and video calls become audio calls which I can only leave by switching the computer off. I tend to have obs-studio 25.0.3+dfsg1-2 running. for the last two days I had it running with AMD_DEBUG=nongg and

[Bug 1883577] Re: column layout in "sensors" is broken for voltages of 1000.00 mV

Here it is again with underscores instead of spaces: nct6798-isa-0290 Adapter:_ISA_adapter in0:___944.00_mV_(min_=__+0.00_V,_max_=__+1.74_V) in1:_1.01_V__(min_=__+0.00_V,_max_=__+0.00_V)__ALARM

[Bug 1883493] [NEW] amdgpu hangs from time to time with *ERROR* Waiting for fences timed out!

Public bug reported: un 15 08:30:42 alhazen kernel: [ 1566.155810] [drm:amdgpu_dm_commit_planes.constprop.0 [amdgpu]] *ERROR* Waiting for fences timed out! Jun 15 08:30:47 alhazen kernel: [ 1566.159792] [drm:amdgpu_dm_commit_planes.constprop.0 [amdgpu]] *ERROR* Waiting for fences timed out!

[Bug 1883493] Re: amdgpu hangs from time to time with *ERROR* Waiting for fences timed out!

This may or may not be the same issue as https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1875459 but this is not reliably reproducible, and I don't even have chrome installed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1883493] Re: amdgpu hangs from time to time with *ERROR* Waiting for fences timed out!

After running ereything with AMD_DEBUG=nongg, the "Waiting for fences" seems to be mostly gone, and I now get sdma0 timeouts. So this seems to be part of the gereral cluster of failures that seem to plague the linux navi drivers since the beginning. Jun 22 07:24:43 alhazen kernel: [ 748.740480]

[Bug 1883577] Re: column layout in "sensors" is broken for voltages of 1000.00 mV

I am running the "sensors" command by typing "sensors" into a terminal window and hitting Enter. It is a bug because the column layout is broken for some voltage values which happen to be relatively common on my system, see the "in6" value: ct6798-isa-0290 Adapter: ISA adapter in0:

[Bug 1883577] Re: column layout in "sensors" is broken for voltages of 1000.00 mV

Sorry, the web form completely killed the column layout. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1883577 Title: column layout in "sensors" is broken for voltages of 1000.00 mV To manage

[Bug 1883577] [NEW] column layout in "sensors" is broken for voltages of 1000.00 mV

Public bug reported: The sensors program tries to print all values neatly in columns, but there are some voltage values which it displays as 1000.00 mV, which is one digit too long. Severity: cosmetic ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: lm-sensors 1:3.6.0-2ubuntu1

[Bug 1878233] Re: Unable to locate package/Headers missing

So you are saying that ubuntu 20.04 is unsuitable as the basis for a developer system because the stability criteria actually forbid to fix a packaging bug that makes it unusable? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1882249] [NEW] Qt3DQuickExtras headers are never packaged

Public bug reported: All the headers for the libraries in the Qt3DQuick packages (called libqt53dquick5) are in the qt3d5-dev package, except for those for libqt53dquickextras5, which I have not been able to find. This makes it for example impossible to compile the code from qt3d5-examples:

<    1   2   3