You have been subscribed to a public bug:
Audio isn't working, I have tried everything including this bug report.
Still no audio.
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.2.0-39.40~22.04.1-generic 6.2.16
Uname: Linux
Only the kernel can crash that hard, so reassigning there.
** Package changed: xorg (Ubuntu) => linux-hwe-6.2 (Ubuntu)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-6.2 in Ubuntu.
https://bugs.launchpad.net/bugs/2047388
** Summary changed:
- Screen brightness
+ [Lenovo IdeaPad Z500] Screen brightness
** Summary changed:
- [Lenovo IdeaPad Z500] Screen brightness
+ [Lenovo IdeaPad Z500] Brightness of the screen is down to minimum and I can't
change it
** Package changed: xorg (Ubuntu) => linux-hwe-6.2 (Ubuntu)
** Tags added: amdgpu
** Package changed: xorg (Ubuntu) => linux-hwe-6.2 (Ubuntu)
** Summary changed:
- [drm] *ERROR* flip_done timed out
+ [amdgpu][drm] *ERROR* flip_done timed out
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
You have been subscribed to a public bug:
Ubuntu 22.04.3 LTS
Release: 22.04
Brightness of the screen is down to minimum and I can't change it.
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.2.0-39.40~22.04.1-generic 6.2.16
Uname: Linux
You have been subscribed to a public bug:
System reboots automatically when lock screen screen enabled. The same
is tested on ubuntu-20.04 as well as ubuntu-22.04.
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.2.0-26.26~22.04.1-generic
You have been subscribed to a public bug:
amdgpu :0c:00.0: [drm] *ERROR* flip_done timed out
gru 21 16:32:25 karol.home.prv kernel: amdgpu :0c:00.0: [drm] *ERROR*
[CRTC:84:crtc-0] commit wait timed out
gru 21 16:32:36 karol.home.prv kernel: amdgpu :0c:00.0: [drm] *ERROR*
flip_done
** Changed in: linux-oem-6.5 (Ubuntu Jammy)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.5 in Ubuntu.
https://bugs.launchpad.net/bugs/2038259
Title:
Include QCA WWAN 4G
** Changed in: linux-oem-6.5 (Ubuntu Jammy)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.5 in Ubuntu.
https://bugs.launchpad.net/bugs/2043964
Title:
New China SRRC compliance
Indeed the kernel seems to be crashing in drm graphics code so I'd
recommend trying some newer kernels such as
https://kernel.ubuntu.com/mainline/?C=M;O=D
** Package changed: xorg (Ubuntu) => linux (Ubuntu)
** Tags added: amdgpu dock multimonitor
--
You received this bug notification because
You have been subscribed to a public bug:
External display is detected and X believes it is OK as the desktop
correctly extends to the 2nd monitor but said monitor remains blank. It
used to work a couple of days ago but I guess some upgrade is the cause.
I tried to downgrade amd64-microcode and
The verification of the Stable Release Update for makedumpfile has
completed successfully and the package is now being released to
-updates. Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you
This bug was fixed in the package makedumpfile - 1:1.6.7-1ubuntu2.5
---
makedumpfile (1:1.6.7-1ubuntu2.5) focal; urgency=medium
* makedumpfile falls back to cp with 5.12 kernel (LP: #1970672)
- can also fail with __vtop4_x86_64: Can't get a valid pmd_pte.
-
Ok. My understanding of this is that when (3) fails it fails for the
same reason that (2) would. We've verified that making a dumpfile works
in general, and definitely fixed (3), so I'm going to release this now.
--
You received this bug notification because you are a member of Kernel
Packages,
It's a Dell 0C11 SKU with link_mask 0x7.
All patches for 0C11 are found on mantic base
1. ASoC: Intel: soc-acpi-intel-rpl-match: add rt711-l0-rt1316-l12 support
2. ASoC: Intel: soc-acpi: add configuration for variant of 0C11 product
3. ASoC: Intel: soc-acpi: update codec addr on 0C11/0C4F product
Please check that you have Bluetooth enabled because this shows it is
disabled in software:
2: dell-bluetooth: Bluetooth
Soft blocked: yes
Hard blocked: no
Also is this a new problem since the last software update?
** Changed in: bluez (Ubuntu)
Status: New => Incomplete
Does "screen is too bright" mean the backlight brightness can't be
adjusted?
** Package changed: xorg (Ubuntu) => linux (Ubuntu)
** Changed in: linux (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed
** Summary changed:
- i am unable to pair and connect blutoothsudo apt-get install fwupd
sudo fwupdmgr update Reading package lists... Done Building dependency tree...
Done Reading state information... Done fwupd is already the newest version
(1.7.9-1~22.04.3). fwupd set to manually
On laptop screens, non-max resolutions are faked. They should work
obviously, but it's up to the display server and kernel driver to fake
it properly.
Do you experience the same issue in a Wayland session?
** Tags added: amdgpu
** Summary changed:
- Resolutions lower than max results in
You have been subscribed to a public bug:
when i try this command
sudo apt-get install xserver-xorg-video-intel
i get this
xserver-xorg-video-intel is already the newest version
(2:2.99.917+git20210115-1).
i have intel 3000 hd graphics built-in in my laptop.
but my screen is too bright and
Issue on 201711-25989 is also different. There's a timeout between
Docker and Checkbox. The system is well and alive.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-6.5 in Ubuntu.
https://bugs.launchpad.net/bugs/2046217
Title:
Issue on 201702-25401 is different. Quite likely caused by faulty CPU
fan and faulty memory.
** Description changed:
- During the jammy-hwe migration test, I found some machines failed to run
- the pm-graph.
-
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: linux-restricted-modules (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-restricted-modules in Ubuntu.
** Summary changed:
- Add Support for Broadcom 5760X Network adapters to 24.04 (patches in 6.8)
+ Add Support for Broadcom 5760X Network Controllers
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Changed in: linux (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2046074
Title:
The monitor screen appears black when connecting the PC
** Tags removed: verification-needed-jammy-linux-oem-6.1
verification-needed-jammy-linux-oem-6.5
** Tags added: verification-done-jammy-linux-oem-6.1
verification-done-jammy-linux-oem-6.5
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
** Tags added: regression-security
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/2046116
Title:
bluetooth device connected but not recognised as output device
Status in bluez package
"stick to Ubuntu 22.04"
Almost, Debian 12.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu.
https://bugs.launchpad.net/bugs/2047137
Title:
nvidia 390 driver from ppa segfault
Status in
Started the work to merge crash 8.0.4 in bug 2047861.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to crash in Ubuntu.
https://bugs.launchpad.net/bugs/2038249
Title:
The dump file parsing issue arises from structural changes in Linux
Merge is in git branch
https://code.launchpad.net/~mfo/ubuntu/+source/crash/+git/crash/+ref/merge-lp2047861-noble
Building/testing from PPA
https://launchpad.net/~mfo/+archive/ubuntu/lp2047861-noble-crash
Still in progress.
--
You received this bug notification because you are a member of
Work in progress.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to crash in Ubuntu.
https://bugs.launchpad.net/bugs/2047861
Title:
Merge crash 8.0.4-1 into Noble
Status in crash package in Ubuntu:
In Progress
Bug description:
$
Public bug reported:
$ rmadison -a source crash | grep noble
crash | 8.0.3+ds1-3ubuntu1 | noble | source
$ rmadison -a source -u debian -s unstable crash
crash | 8.0.4-1 | unstable | source
** Affects: crash (Ubuntu)
Importance: Medium
Assignee: Mauricio
Hi Chengen!
Thank you very much for the detailed test plan! It's really good.
Apologies for the extended delay in getting back to your changes.
There are some points to address in the debdiffs. In order of
importance:
1) The debdiff for Lunar and Jammy (equivalent) are for kernel 6.2, but
Public bug reported:
SRU Justification:
[Impact]
There is a SAUCE patch that addresses a mlxbf-gige RX race condition
"UBUNTU: SAUCE: Fix OOB handling RX packets in heavy traffic"
This SAUCE patch should be reverted and replaced with upstream content.
[Fix]
Bring in the following upstream
This bug is awaiting verification that the linux-nvidia-tegra-
igx/5.15.0-1007.7 kernel in -proposed solves the problem. Please test
the kernel and update this bug with the results. If the problem is
solved, change the tag 'verification-needed-jammy-linux-nvidia-tegra-
igx' to
This bug is awaiting verification that the linux-nvidia-tegra-
igx/5.15.0-1007.7 kernel in -proposed solves the problem. Please test
the kernel and update this bug with the results. If the problem is
solved, change the tag 'verification-needed-jammy-linux-nvidia-tegra-
igx' to
This bug is awaiting verification that the linux-nvidia-tegra-
igx/5.15.0-1007.7 kernel in -proposed solves the problem. Please test
the kernel and update this bug with the results. If the problem is
solved, change the tag 'verification-needed-jammy-linux-nvidia-tegra-
igx' to
This bug is awaiting verification that the linux-nvidia-tegra-
igx/5.15.0-1007.7 kernel in -proposed solves the problem. Please test
the kernel and update this bug with the results. If the problem is
solved, change the tag 'verification-needed-jammy-linux-nvidia-tegra-
igx' to
This bug is awaiting verification that the linux-nvidia-tegra-
igx/5.15.0-1007.7 kernel in -proposed solves the problem. Please test
the kernel and update this bug with the results. If the problem is
solved, change the tag 'verification-needed-jammy-linux-nvidia-tegra-
igx' to
This bug is awaiting verification that the linux-nvidia-tegra-
igx/5.15.0-1007.7 kernel in -proposed solves the problem. Please test
the kernel and update this bug with the results. If the problem is
solved, change the tag 'verification-needed-jammy-linux-nvidia-tegra-
igx' to
This bug is awaiting verification that the linux-nvidia-tegra-
igx/5.15.0-1007.7 kernel in -proposed solves the problem. Please test
the kernel and update this bug with the results. If the problem is
solved, change the tag 'verification-needed-jammy-linux-nvidia-tegra-
igx' to
This bug is awaiting verification that the linux-nvidia-tegra-
igx/5.15.0-1007.7 kernel in -proposed solves the problem. Please test
the kernel and update this bug with the results. If the problem is
solved, change the tag 'verification-needed-jammy-linux-nvidia-tegra-
igx' to
This bug is awaiting verification that the linux-nvidia-tegra-
igx/5.15.0-1007.7 kernel in -proposed solves the problem. Please test
the kernel and update this bug with the results. If the problem is
solved, change the tag 'verification-needed-jammy-linux-nvidia-tegra-
igx' to
This bug is awaiting verification that the linux-nvidia-tegra-
igx/5.15.0-1007.7 kernel in -proposed solves the problem. Please test
the kernel and update this bug with the results. If the problem is
solved, change the tag 'verification-needed-jammy-linux-nvidia-tegra-
igx' to
** Also affects: linux-bluefield (Ubuntu Jammy)
Importance: Undecided
Status: New
** Changed in: linux-bluefield (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-bluefield in Ubuntu.
** Also affects: linux-bluefield (Ubuntu Jammy)
Importance: Undecided
Status: New
** Changed in: linux-bluefield (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-bluefield in Ubuntu.
** Also affects: linux-bluefield (Ubuntu Jammy)
Importance: Undecided
Status: New
** Changed in: linux-bluefield (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-bluefield in Ubuntu.
*** This bug is a duplicate of bug 2046434 ***
https://bugs.launchpad.net/bugs/2046434
** This bug has been marked a duplicate of bug 2046434
TPM2 Problem in 6.2.0 kernel
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
The same in 22.04.3:
[0.049372] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-5.15.0-91-generic
root=UUID=... ro quiet splash crashkernel=512M-:192M vt.handoff=7
[0.049461] Unknown kernel command line parameters "splash
BOOT_IMAGE=/boot/vmlinuz-5.15.0-91-generic", will be passed to user
My issue with the zfs-dkms bug was raised by Linux Mint update giving an error
message each time
an upgrade was run. The error message has now stopped appearing. I've not seen
any news that the
issue is fixed. Does anyone have information that the corrections have migrated
through from the
Any news on this? It has been open for over ten years now. AppArmor is
on by default on Ubuntu, and if auditd is used, then the events are
logged using it. Isn't it a security bug if the events don't show up
when queried using ausearch?
--
You received this bug notification because you are a
The seeding [1] of it is also quite clear on why it is still there.
"""
# This stack is no more very relevant, but was in the early days of internet
# dialin. This stack is a candidate for demotion, but OTOH received no
# bugs/CVEs over the last years and therefore can stay as-is for now.
# ppp
Thank you for reassigning @vanvugt.
Sorry, I reported this on 6.6.5 linux kernel. Yes, this happens too in
the Ubuntu kernel (6.5.x-generic).
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Tags added: regression-update
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/2046116
Title:
bluetooth device connected but not recognised as output device
Status in bluez package in
Wait, 6.6.5-060605-generic isn't an Ubuntu kernel - do you have the same
bug in the default Ubuntu kernel?
** Changed in: linux (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Sound and display coexisting on the same HDMI cable would be a kernel
issue so reassigning...
** Package changed: mutter (Ubuntu) => linux (Ubuntu)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
You have been subscribed to a public bug:
When I connect the laptop to the sound bar hdmi and the sound bar to the
monitor, it tries to connect and Ubuntu detects it, but nothing appears
on the screen.
My HDMI works as it should, tested directly when it's connected to the
monitor. I have tried
** No longer affects: mutter (Ubuntu)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2039570
Title:
[amdgpu] Fullscreen in any Wayland / Xwayland window shows a black
screen (no
My previous comments one year ago were probably premature. And on top of
that I'm now using a different primary desktop (also Intel 12th gen, now
kernel 6.2) that periodically has a similar bug. My next plan is to try
replacing the USB-C cable with an expensive Apple Thunderbolt cable.
**
Nicolas, this bug was reported over 7 years ago against an Ubuntu
version that will reach end of life in a few months. I suggest to keep
your issue alive that it should be reported as a new bug.
** Tags added: trusty
--
You received this bug notification because you are a member of Kernel
** Changed in: linux-oem-6.5 (Ubuntu Noble)
Status: Triaged => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.5 in Ubuntu.
https://bugs.launchpad.net/bugs/2046315
Title:
oem-6.5: disable psr2 for some panels
61 matches
Mail list logo
