** Package changed: bluez (Ubuntu) => ubuntu
--
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/2049958
Title:
package bluez-obexd 5.68-0ubuntu1 failed to install/upgrade: unable to
make
The kernel patch is still in progress but I also wonder if plymouthd
starts early enough to do all the console blocking? If so then it could
FBIOPUT_CON2FBMAP like con2fbmap does, to umap the console from the
framebuffer. But that's still racing with other kernel things which
might have already
** Changed in: plymouth (Ubuntu)
Status: In Progress => Invalid
--
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/1970069
Title:
Annoying boot messages interfering with splash
If it's software at all then this would be a kernel bug. But I suspect
the issue is more likely hardware since 1920x1080 @60Hz is pushing the
limits of analog VGA. Anything less than a perfect cable with perfect
connections and I'd expect display glitches like this.
Personally I'd recommend
It's been almost a week since I switched to an Apple Thunderbolt 4 Pro
cable and no signal loss so far.
--
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/1929209
Title:
[i915] external
** Summary changed:
- Apps take minutes to launch when the MediaTek wifi card is enabled
+ [mt7921e] Apps take minutes to launch when the MediaTek wifi card is enabled
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Great to hear. By chance I also fixed a laptop's broken wifi just last
night by replacing the MediaTek card with an old Intel one.
** Package changed: xdg-desktop-portal (Ubuntu) => linux-hwe-6.5
(Ubuntu)
** Summary changed:
- Apps take minutes to launch
+ Apps take minutes to launch when the
Please try booting older kernels so we can identify what the last good
version was.
Please also run:
lspci -k > lspci.txt
journalctl -b0 > journal.txt
and attach the resulting text files here.
** Package changed: gnome-shell (Ubuntu) => linux-hwe-6.5 (Ubuntu)
** Changed in: linux-hwe-6.5
** Summary changed:
- Can't change screen brightness
+ [HP Victus 15-fb0xxx] Can't change screen brightness
** Package changed: xorg (Ubuntu) => linux-hwe-6.5 (Ubuntu)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-6.5 in
"Input/output error" is probably a USB connection issue, or a flash
drive error. Please try a different drive and/or different USB port.
** Package changed: bluez (Ubuntu) => ubuntu
** Changed in: ubuntu
Status: New => Incomplete
--
You received this bug notification because you are a
Seems like it, at least for jammy:
grep -H '6\.5\.' /boot/config-6.5.*
--
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/2048827
Title:
[amdgpu] Mouse cursor theme is grey instead
** Summary changed:
- display backlight
+ [Acer eMachines D725] Display backlight
** 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.
First draft, proof of concept, fix.
** Patch added: "0001-fbcon-Defer-AND-delay-console-take-over.patch"
https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1970069/+attachment/5740765/+files/0001-fbcon-Defer-AND-delay-console-take-over.patch
--
You received this bug notification
Thanks. It looks like the GPU driver is working correctly there. Next
please try:
sudo apt install glmark2
glmark2
Does it render smoothly and display correct driver information in the
Terminal?
** Package changed: linux-hwe-6.2 (Ubuntu) => ubuntu
--
You received this bug notification
ymouth's 8 second device timeout.
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Daniel van Vugt (vanvugt)
** Changed in: linux (Ubuntu)
Status: New => In Progress
--
You received this bug noti
Perhaps try a recursive grep for '/usr/lib/bluetooth/bluetoothd'
--
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/2049708
Title:
bluez bluetoothd unable to locate executable
Status in
Am I correct in assuming the problem goes away after a reboot?
--
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/2049708
Title:
bluez bluetoothd unable to locate executable
Status in
5.71-1ubuntu3:
Binary: /usr/libexec/bluetooth/bluetoothd
SystemD: system/bluetooth.service:ExecStart=/usr/libexec/bluetooth/bluetoothd
So that's consistent, but it sounds like you might have encountered an
upgrade bug and your systemd was looking in the old path? I'm guessing
there should be a
Thanks for the bug report. It looks like the i915 kernel graphics driver
is crashing a lot, which may or may not be related. Please run these
commands in a Terminal:
sudo apt install mesa-utils
glxinfo > glxinfo.txt
and attach the resulting text file here.
** Package changed: xorg (Ubuntu)
Thanks for the bug report. It appears you no longer have an nvidia
kernel driver for the current kernel version. I'm also not sure if such
a newer kernel can be supported by the old nvidia 390 driver.
This might just be bug 1975650 so please try reinstalling the driver
using the 'Additional
Please also try kernel parameter amdgpu.dcdebugmask=0x10 to disable
panel self-refresh.
** Changed in: linux-hwe-6.5 (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-6.5 in Ubuntu.
Thanks for the bug report. I've watched the attached screencast a few
times and can't see any artifacts in it. This is unsurprising given how
screen recording works. You will probably need to take a video of the
screen externally, like with a phone.
** Summary changed:
- screen artifacts
** Attachment added: "bluez_5.72-0ubuntu1.debian.tar.xz"
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2049352/+attachment/5739878/+files/bluez_5.72-0ubuntu1.debian.tar.xz
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez
** Patch added: "bluez_5.72-0ubuntu1.debdiff"
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2049352/+attachment/5739879/+files/bluez_5.72-0ubuntu1.debdiff
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
** Attachment added: "bluez_5.72.orig.tar.xz"
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2049352/+attachment/5739877/+files/bluez_5.72.orig.tar.xz
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
** Changed in: bluez (Ubuntu)
Status: Triaged => In Progress
--
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/2049352
Title:
Package BlueZ 5.72 for Noble
Status in bluez package
** Changed in: bluez (Ubuntu)
Assignee: (unassigned) => Daniel van Vugt (vanvugt)
--
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/2049352
Title:
Package BlueZ 5.72 for Noble
Sta
Another source of noise is warnings about buggy ACPI implementations (on
some, many, machines). I feel hiding those is a bare minimum because
getting a less buggy BIOS just isn't feasible in most cases. And
displaying the warnings makes Ubuntu look bad.
--
You received this bug notification
** Tags added: noble
--
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/2049390
Title:
Please change CONFIG_CONSOLE_LOGLEVEL_QUIET to 3
Status in linux package in Ubuntu:
Confirmed
Bug
Let me know when it's safe to start work on LP: #2049352 for 5.72 or if
someone else wants to do it.
--
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/2047780
Title:
BlueZ release 5.71
Public bug reported:
ver 5.72:
Fix issue with BAP and handling stream IO linking.
Fix issue with BAP and setup of multiple streams per endpoint.
Fix issue with AVDTP and potential incorrect transaction label.
Fix issue with A2DP and handling crash on suspend.
** Tags added: amdgpu
** Summary changed:
- Video does not output to second monitor
+ [amdgpu] Video does not output to second monitor
** Package changed: xorg (Ubuntu) => linux-hwe-6.5 (Ubuntu)
--
You received this bug notification because you are a member of Kernel
Packages, which is
)
After that successfull reboot, I tried ubuntu-drivers autoinstall and got this
error again.
So I conclude that this package is in some way corrupted or no mode compatible
whith that HW.
Waiting for a solution, i desinstalled again nvidia*
Thanks for your help.
Daniel
ProblemType: Package
** Also affects: linux via
https://gitlab.freedesktop.org/drm/amd/-/issues/2803
Importance: Unknown
Status: Unknown
** Changed in: linux-hwe-6.2 (Ubuntu)
Importance: Undecided => Low
** Changed in: linux-hwe-6.2 (Ubuntu)
Status: New => Triaged
** Tags added:
Sounds like it was fixed in kernels 6.6 and 6.5.4
--
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/2048827
Title:
[amdgpu] Mouse cursor theme is grey instead of black
Status in
See also:
https://gitlab.freedesktop.org/drm/amd/-/issues/2803
https://gitlab.freedesktop.org/drm/amd/-/issues/1513
** Bug watch added: gitlab.freedesktop.org/drm/amd/-/issues #2803
https://gitlab.freedesktop.org/drm/amd/-/issues/2803
** Bug watch added:
Zooming in on the cursor images in GIMP I find they do contain gradients
- both Yaru and DMZ-Black. Therefore some greyness is correct.
I think the remaining bug here is that either the kernel (amdgpu) or
mutter is under-saturating the cursor plane with an alpha component
below 1.0. That's why I
> Force pushing my local commits over, sorry not sorry. :)
Yeah it's fine this time. :)
--
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/2047780
Title:
BlueZ release 5.71
Status in
BTW, having the previous Ubuntu version 5.71-0ubuntu3 on line 415 of the
changelog doesn't feel ideal for people wanting to read the Ubuntu
release history.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
Ideally please open a new bug for the merge. This bug should remain Fix
Released because we're already past the point in time when it was
released to Noble.
Please also remember to commit proposed changes to
https://git.launchpad.net/~bluetooth/bluez
** Changed in: bluez (Ubuntu)
Status:
** Description changed:
+ [ Workaround ]
+
+ 1. Set ClassicBondedOnly=false in /etc/bluetooth/input.conf
+ 2. Run: systemctl restart bluetooth # or reboot
+
+ [ Original Description ]
+
Once my Ubuntu updated bluez package to 5.64-0ubuntu1.1 I was not able
to connect my PS3 Sixasis
** Summary changed:
- Xorg freeze
+ [i915] Screen freeze, kernel crash
--
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/2048701
Title:
[i915] Screen freeze, kernel crash
Status
Thank you for working over the weekend on this. I would have resolved it
myself on the Monday if someone answered the question in comment #11.
Also I've sent a bug report to Debian about their orig tarball not
matching the upstream release tarball. I feel that's a discussion they
need to have
It looks like most of you are members of ~bluetooth already via ~ubuntu-
core-dev so feel free to commit directly to
https://git.launchpad.net/~bluetooth/bluez in future.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
I appreciate everyone is frustrated. BlueZ isn't really staffed, it's
just something I look at once or twice a year. The diff to Debian is
shrinking over the long term, but again that's something I don't look at
very often.
The justification for Ubuntu using a separate process for the past 6
Turns out it's not as simple as the above comments suggest.
> https://salsa.debian.org/systemd-team/systemd/-/commit/ee83b5721
> https://salsa.debian.org/DebianOnMobile-team/modemmanager/-/commit/367180c3
udev changes are not relevant to the failures in
** Summary changed:
- Screen crashes in a wierd way
+ [amdgpu] Screen crashes in a weird way
** Tags added: amdgpu
** Package changed: xorg (Ubuntu) => linux (Ubuntu)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Actually the issue I'm thinking of might be fixed by
https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2620 coming in
mutter 46... If not already fixed in the kernel because it looks like
this bug only affects jammy?
--
You received this bug notification because you are a member of Kernel
The build is failing:
https://launchpad.net/ubuntu/+source/bluez/5.71-0ubuntu1
But I don't know how to reproduce the failure. Certainly it builds on
both noble and mantic, and installs, and works for me. Is this because
Launchpad is using a focal toolchain?
--
You received this bug notification
** Bug watch added: gitlab.freedesktop.org/drm/amd/-/issues #2693
https://gitlab.freedesktop.org/drm/amd/-/issues/2693
** Also affects: linux via
https://gitlab.freedesktop.org/drm/amd/-/issues/2693
Importance: Unknown
Status: Unknown
** Changed in: linux (Ubuntu)
Importance:
Thinking about the most common cause of this error I've seen, can anyone
with multiple monitors confirm that it happens more on monitors that the
mouse pointer isn't on?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-5.19 in
Is there a reason why this hasn't been marked as a duplicate of bug
2042867?
--
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/2046504
Title:
Fix AMDGPU display on lower resolution
** No longer affects: xorg-server (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/2046224
Title:
[amdgpu] Resolutions lower than max results in corrupted screen
Status in linux
It's usually Seb sponsoring these, but he's on vacation. To avoid any
future complaints in case he's away again I will also include debdiffs
in future.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
Here's the debdiff. We don't usually use them for major updates though
because of the size. 34174 lines in this case is not plausibly
reviewable.
** Patch added: "bluez_5.71-0ubuntu1.debdiff"
** Attachment added: "bluez_5.71-0ubuntu1.debian.tar.xz"
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2047780/+attachment/5735865/+files/bluez_5.71-0ubuntu1.debian.tar.xz
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez
Updated source files are attached above. And the source is in:
https://git.launchpad.net/~bluetooth/bluez/log/
--
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/2047780
Title:
BlueZ
** Attachment added: "bluez_5.71.orig.tar.xz"
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2047780/+attachment/5735864/+files/bluez_5.71.orig.tar.xz
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
** Changed in: bluez (Ubuntu)
Status: Triaged => In Progress
--
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/2047780
Title:
BlueZ release 5.71
Status in bluez package in Ubuntu:
What is the make and model of the machine? It seems to identify itself
as "Default string".
** Package changed: xorg (Ubuntu) => linux-hwe-6.2 (Ubuntu)
** Changed in: linux-hwe-6.2 (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of
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
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
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
** 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 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.
** 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
.
** Changed in: mutter (Ubuntu)
Status: Fix Released => Confirmed
** Tags added: jammy
** Changed in: mutter (Ubuntu)
Assignee: Daniel van Vugt (vanvugt) => (unassigned)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
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
PPAs are not supported, but also the 390 driver is not supported by any
Ubuntu release after 23.04 (which explains why you're using a PPA).
If you require Nvidia driver 390 then please stick to Ubuntu 22.04 where
it is formally supported until April 2032.
** No longer affects: xorg (Ubuntu)
**
Public bug reported:
Release BlueZ 5.71 to noble.
** Affects: bluez (Ubuntu)
Importance: Medium
Assignee: Daniel van Vugt (vanvugt)
Status: Triaged
** Tags: noble
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed
I can login from another box and do any diagnostic work that you need.
Just let me know what you want. BTW, Software Rendering lets me login
and get a desktop.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
I realize now we had a second issue on arm64 on Ubuntu 20.04 a bit
before that resulted from the same patch, we got around that one without
looking deeply by changing kernels. At the time we declined to
investigate.
So, I have a further question: so, I suspect the reason this slipped
through
This sounds like it might be a feature and the bug was that previous
versions DIDN'T ask. Try entering PIN:
** Changed in: bluez (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in
** Tags added: jammy regression-update
** Changed in: bluez (Ubuntu)
Assignee: (unassigned) => Nishit Majithia (0xnishit)
--
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/2045931
It looks like the problem was just no response provided to:
Configuration file '/etc/bluetooth/input.conf'
==> File on system created by you or by a script.
==> File also in package provided by package maintainer.
어떻게 하시겠습니까? 다음 중에 하나를 선택할 수 있습니다:
Y 또는 I : 패키지 관리자의 버전을 설치합니다
N 또는 O :
** Summary changed:
- [Intel Corporation Raptor Lake PCH CNVi WiFi] Bluetooth issues in Ubuntu 23.10
+ [Intel AX211] Bluetooth issues in Ubuntu 23.10
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
It looks like kwin didn't crash until after the kernel errors started so
let's make this about the kernel errors.
** Summary changed:
- Graphics card driver crash
+ [A770] Graphics card driver crash
** Package changed: xorg (Ubuntu) => linux (Ubuntu)
** Summary changed:
- [A770] Graphics card
** Summary changed:
- Bluetooth issues in Ubuntu 23.10
+ [Intel Corporation Raptor Lake PCH CNVi WiFi] Bluetooth issues in Ubuntu 23.10
** Package changed: bluez (Ubuntu) => linux (Ubuntu)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
Please open a new bug about that because this one is closed.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-470 in Ubuntu.
https://bugs.launchpad.net/bugs/1799679
Title:
Nvidia driver causes Xorg to use 100%
Yes I noticed that but it's already covered by the nvidia-graphics-
drivers-535 and linux-hwe-6.2 tasks here.
Assuming this isn't a hardware problem I think you're probably waiting
for a driver fix from Nvidia, or a kernel fix.
--
You received this bug notification because you are a member of
Thanks. I don't see any relevant crashes but either of these repeating
issues might be related to freezes:
Des 06 11:43:39 zengi kernel: xhci_hcd :01:00.2: xHC error in resume,
USBSTS 0x401, Reinit
Des 06 11:43:39 zengi kernel: usb usb3: root hub lost power or was reset
Des 06 11:43:39 zengi
Alright, I will do what I did, if it comes up again. I will try to
augment our tests to include an apt upgrade with -proposed. Thank you.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Looking at Jason Wang's commits, it seems like it must work at least a
little with qemu (because he committed it) but either 1) not *that* well
or 2) someone else told him about trying to run firecracker or some
other VMM that more closely assumes the specification in this area,
since he modified
> I might try to set the kernel parameter next. For clarification: I would add
> amdgpu.mcb=0 to
> GRUB_CMDLINE_LINUX_DEFAULT in /etc/default/grub and then run 'sudo
> update-grub' (or update-grub2?).
> Afterwards I can just reboot?
Yes that sounds correct other than a typo - it should be
Indeed, it boots after following your instructions.
ubi@vm1fmdye:~$ uname -a
Linux vm1fmdye 5.15.0-91-generic #101-Ubuntu SMP Tue Nov 14 13:30:08 UTC 2023
x86_64 x86_64 x86_64 GNU/Linux
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
We can check it out, I have a question though, is there a way to get a
pre-captured image with -proposed in it? We could integrate this into a
CI system to do more monitoring.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
It looks like the -proposed kernel has picked up that missing patch:
~/c/linux ((Ubuntu-5.15.0-91.101))> git log --grep='virtio-net: set queues
after driver_ok'
commit c6c83b9055f44bcb2bc2fae32323c0a1510c7656
Author: Jason Wang
Date: Wed Aug 9 23:12:56 2023 -0400
virtio-net: set queues
Can you boot completely with 'nomodeset'?
--
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/2043203
Title:
Kernel 5.15.0-86 causes LightDM to disappear after 1s
Status in linux package in
Public bug reported:
I use a non-qemu VMM, cloud-hypervisor. It looks like a patch was
applied, that introduced a bug, a week later another patch got written
to fix that bug, and that second patch was not applied in Ubuntu's
release, but is seen in Greg KH's 5.15 branch.
The result of the bug is
** 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/2045072
Title:
[Samsung Galaxy Book2 750XED] Screen goes black
Status in
The amdgpu kernel driver here doesn't seem to be from Ubuntu so we can't
track its bugs here.
Please consider uninstalling the drivers that are presumably from AMD,
then reboot and report new bugs to Ubuntu for any issues you find.
** Changed in: linux-hwe-6.2 (Ubuntu)
Status: New =>
Thanks. It sounds like perhaps the laptop lid switch or LCD backlight
are misbehaving.
When the screen goes black, do you notice if:
* The machine is sleeping (power light has changed); or
* There is still a picture on screen you can see with a flashlight only.
Either way, please try the
The corruption also feels like something is broken with mid command
buffer preemption so please try this kernel parameter:
amdgpu.mcbp=0
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
301 - 400 of 8794 matches
Mail list logo
