I found that may be caused by hardware failure. I have tried with windows and
it doesn't work too. I had replaced the WIFI card with a new one.
Thanks for you help, and please close the bug.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed t
Thank you.
--
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/2080583
Title:
Wifi adapter has been removed
Status in linux package in Ubuntu:
Incomplete
Bug description:
24.14 upgrade
Hi,
Yes, I used the following commands in the terminal:
sudo apt install broadcom-sta-dkms broadcom-sta-source
sudo apt install firmware-b43-installer
reboot.
After the reboot, the wifi icon appeared immediately and everything
worked as before the update.
Hope this helps.
John
--
You rece
@magnusjohn could you share what packages you installed exactly? Was
broadcom-sta-dkms enough?
--
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/2080583
Title:
Wifi adapter has been removed
On 10/12/24 1:29 PM, Van Svensson wrote:
> Has anyone successfully managed to get this working on Ubuntu 24.04? I
> tried the Mainline build of kernel 6.11
> (https://kernel.ubuntu.com/mainline/v6.11/), but the dell-uart-backlight
> is not present. When looking at Ubuntu 22.04 I see that it is incl
This worked for me! Thanks Eugene!
--
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/2080583
Title:
Wifi adapter has been removed
Status in linux package in Ubuntu:
Incomplete
Bug descr
Going over advises found in @juergh links I messed around with
blacklisting in `/etc/modprobe.d/` and noticed that it has a file named
`broadcom-sta-dkms.conf`. I checked and I don't have `broadcom-sta-dkms`
installed. In fact, I don't have `dkms` installed. Yet those packages
are available. So I i
Hi Danilo, thanks for pointing me to that bug, that was indeed the
problem, and the solution was to install `systemd-cryptsetup`. Booting
is now fast again, and now my swap space is working! The warning
messages with the kernel traces for memcpy field spanning writes remain,
but they do not cause a
** Changed in: linux (Ubuntu Noble)
Status: Fix Committed => Fix Released
--
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/2064176
Title:
LXD fan bridge causes blocked tasks
Status
Has anyone successfully managed to get this working on Ubuntu 24.04? I
tried the Mainline build of kernel 6.11
(https://kernel.ubuntu.com/mainline/v6.11/), but the dell-uart-backlight
is not present. When looking at Ubuntu 22.04 I see that it is included
in the linux-modules-extra package, but that
Same problem for me, Lenovo ThinkPad P50. Tried kernel 6.11, same issue.
Kernel 6.7 (from https://kernel.ubuntu.com/mainline/v6.7/amd64/linux-
image-unsigned-6.7.0-060700-generic_6.7.0-060700.202401072033_amd64.deb)
works for me. Had to disable secure boot. This seems like something that
ought to b
I can reproduce the pairing loss by suspending my laptop. The
kernel: Bluetooth: hci0: Invalid link address type 1 for
60:ab:d2:43:49:4d
message appears on resume, even when the headset is not connected at
that moment (and is in fact switched off).
Also, the link key changed after my last p
All autopkgtests for the newly accepted linux-meta-gcp (5.4.0.1139.141) for
focal have finished running.
The following regressions have been reported in tests triggered by the package:
r8168/8.048.00-1ubuntu0.20.04.2 (amd64)
systemd/245.4-4ubuntu3.24 (amd64, arm64)
Please visit the excuses page
Thank you to report this bug and make Ubuntu better!
In order to pull relevant system logs into your existing bug please
enter this command
in your terminal: apport-collect 2081384
so the developers can debug your bug a better way.
Thank you!
--
You received this bug notification because you
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: bluez (Ubuntu)
Status: New => Confirmed
--
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/2081384
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: linux (Ubuntu)
Status: New => Confirmed
--
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/2081384
That stackexchange link suggests
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=aae6b81260fd9a7224f7eb4fc440d625852245bb
might be to blame for this. I'm not sure how to test that.
Also, this bug might be a duplicate of
https://bugs.launchpad.net/ubuntu/+source/bluez
One notable difference between 24.04 (kernel 6.8.0) and 24.10 (kernel
6.11.0) is that the new kernel is outputting
spal. 11 09:44:52 blynas kernel: Bluetooth: hci0: Invalid link
address type 1 for 60:ab:d2:43:49:4d
These messages never showed up on 24.04.
Searching for that message led me to
Hello Andrea, or anyone else affected,
Accepted iproute2 into oracular-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/iproute2/6.10.0-2ubuntu1 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
http
Public bug reported:
I've Bose QuietComfort 35 II bluetooth headphones/headset that I've been
using with Ubuntu for several years now. Since I upgraded to Ubuntu
24.10 yesterday, the headset refuses to connect to Ubuntu until I pair
it again, every time.
This is how things worked with 24.04 LTS:
This bug is awaiting verification that the linux-
oracle-6.8/6.8.0-1015.15~22.04.1 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-
oracle-6.8' to 'verification-done-jammy-
This bug is awaiting verification that the linux-
oracle-6.8/6.8.0-1015.15~22.04.1 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-
oracle-6.8' to 'verification-done-jammy-
This bug is awaiting verification that the linux-
oracle-6.8/6.8.0-1015.15~22.04.1 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-
oracle-6.8' to 'verification-done-jammy-
This bug is awaiting verification that the linux-
oracle-6.8/6.8.0-1015.15~22.04.1 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-
oracle-6.8' to 'verification-done-jammy-
This bug is awaiting verification that the linux-
oracle-6.8/6.8.0-1015.15~22.04.1 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-
oracle-6.8' to 'verification-done-jammy-
This bug is awaiting verification that the linux-
oracle-6.8/6.8.0-1015.15~22.04.1 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-
oracle-6.8' to 'verification-done-jammy-
This bug is awaiting verification that the linux-
oracle-6.8/6.8.0-1015.15~22.04.1 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-
oracle-6.8' to 'verification-done-jammy-
This bug is awaiting verification that the linux-
oracle-6.8/6.8.0-1015.15~22.04.1 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-
oracle-6.8' to 'verification-done-jammy-
This bug is awaiting verification that the linux-
oracle-6.8/6.8.0-1015.15~22.04.1 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-
oracle-6.8' to 'verification-done-jammy-
This bug is awaiting verification that the linux-
oracle-6.8/6.8.0-1015.15~22.04.1 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-
oracle-6.8' to 'verification-done-jammy-
This bug is awaiting verification that the linux-
oracle-6.8/6.8.0-1015.15~22.04.1 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-
oracle-6.8' to 'verification-done-jammy-
This bug is awaiting verification that the linux-
oracle-6.8/6.8.0-1015.15~22.04.1 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-
oracle-6.8' to 'verification-done-jammy-
This bug is awaiting verification that the linux-
oracle-6.8/6.8.0-1015.15~22.04.1 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-
oracle-6.8' to 'verification-done-jammy-
This bug is awaiting verification that the linux-
oracle-6.8/6.8.0-1015.15~22.04.1 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-
oracle-6.8' to 'verification-done-jammy-
This bug is awaiting verification that the linux-
oracle-6.8/6.8.0-1015.15~22.04.1 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-
oracle-6.8' to 'verification-done-jammy-
This bug is awaiting verification that the linux-
oracle-6.8/6.8.0-1015.15~22.04.1 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-
oracle-6.8' to 'verification-done-jammy-
This bug is awaiting verification that the linux-
oracle-6.8/6.8.0-1015.15~22.04.1 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-
oracle-6.8' to 'verification-done-jammy-
This bug is awaiting verification that the linux-
oracle-6.8/6.8.0-1015.15~22.04.1 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-
oracle-6.8' to 'verification-done-jammy-
This bug is awaiting verification that the linux-
oracle-6.8/6.8.0-1015.15~22.04.1 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-
oracle-6.8' to 'verification-done-jammy-
This bug is awaiting verification that the linux-
oracle-6.8/6.8.0-1015.15~22.04.1 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-
oracle-6.8' to 'verification-done-jammy-
This bug is awaiting verification that the linux-
oracle-6.8/6.8.0-1015.15~22.04.1 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-
oracle-6.8' to 'verification-done-jammy-
This bug is awaiting verification that the linux-
oracle-6.8/6.8.0-1015.15~22.04.1 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-
oracle-6.8' to 'verification-done-jammy-
This bug is awaiting verification that the linux-
oracle-6.8/6.8.0-1015.15~22.04.1 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-
oracle-6.8' to 'verification-done-jammy-
** Attachment added: "dmesg-6.8.0.48-Lockup.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2081685/+attachment/5827496/+files/dmesg-6.8.0.48-Lockup.log
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https:/
** Attachment added: "dmesg-6.8.0.48-No-Lockup.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2081685/+attachment/5827495/+files/dmesg-6.8.0.48-No-Lockup.log
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
h
Hi Paolo.
Here is the feedback for the question:
I cannot commit it occurs 100%, with the latest Noble kernel is
Ubuntu-6.8.0-48.48, the issue occurs 7/10 times. There is no change on HW
config nor FW code, just Reboot. The issue does not occur in random, but once
it occurs, it always later the
Hi James, can you check if the boot delay you mentioned happened due to
this? https://bugs.launchpad.net/ubuntu/+source/subiquity/+bug/2084089
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad.net/
The names of the files in /var/crash are:
_usr_bin_update-notifier.1000.crash
_usr_bin_update-notifier.1000.upload
_usr_bin_update-notifier.1000.uploaded
_usr_libexec_packagekitd.0.crash
_usr_libexec_packagekitd.0.upload
_usr_libexec_packagekitd.0.uploaded
_usr_libexec_tracker-extract-3.1000.crash
Seems not to affect Oracular, which I've now upgraded to - so I can't
provide any more info here sorry.
--
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/2056111
Title:
Bluetooth disabled
This bug is awaiting verification that the linux-
aws-6.8/6.8.0-1018.19~22.04.1 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-
aws-6.8' to 'verification-done-jammy-linux-
This bug is awaiting verification that the linux-
aws-6.8/6.8.0-1018.19~22.04.1 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-
aws-6.8' to 'verification-done-jammy-linux-
This bug is awaiting verification that the linux-
aws-6.8/6.8.0-1018.19~22.04.1 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-
aws-6.8' to 'verification-done-jammy-linux-
This bug is awaiting verification that the linux-
aws-6.8/6.8.0-1018.19~22.04.1 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-
aws-6.8' to 'verification-done-jammy-linux-
This bug is awaiting verification that the linux-
aws-6.8/6.8.0-1018.19~22.04.1 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-
aws-6.8' to 'verification-done-jammy-linux-
This bug is awaiting verification that the linux-
aws-6.8/6.8.0-1018.19~22.04.1 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-
aws-6.8' to 'verification-done-jammy-linux-
This bug is awaiting verification that the linux-
aws-6.8/6.8.0-1018.19~22.04.1 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-
aws-6.8' to 'verification-done-jammy-linux-
This bug is awaiting verification that the linux-
aws-6.8/6.8.0-1018.19~22.04.1 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-
aws-6.8' to 'verification-done-jammy-linux-
This bug is awaiting verification that the linux-
aws-6.8/6.8.0-1018.19~22.04.1 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-
aws-6.8' to 'verification-done-jammy-linux-
This bug is awaiting verification that the linux-
aws-6.8/6.8.0-1018.19~22.04.1 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-
aws-6.8' to 'verification-done-jammy-linux-
This bug is awaiting verification that the linux-
aws-6.8/6.8.0-1018.19~22.04.1 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-
aws-6.8' to 'verification-done-jammy-linux-
This bug is awaiting verification that the linux-
aws-6.8/6.8.0-1018.19~22.04.1 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-
aws-6.8' to 'verification-done-jammy-linux-
This bug is awaiting verification that the linux-
aws-6.8/6.8.0-1018.19~22.04.1 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-
aws-6.8' to 'verification-done-jammy-linux-
This bug is awaiting verification that the linux-
aws-6.8/6.8.0-1018.19~22.04.1 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-
aws-6.8' to 'verification-done-jammy-linux-
This bug is awaiting verification that the linux-
aws-6.8/6.8.0-1018.19~22.04.1 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-
aws-6.8' to 'verification-done-jammy-linux-
This bug is awaiting verification that the linux-
aws-6.8/6.8.0-1018.19~22.04.1 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-
aws-6.8' to 'verification-done-jammy-linux-
This bug is awaiting verification that the linux-
aws-6.8/6.8.0-1018.19~22.04.1 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-
aws-6.8' to 'verification-done-jammy-linux-
This bug is awaiting verification that the linux-
aws-6.8/6.8.0-1018.19~22.04.1 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-
aws-6.8' to 'verification-done-jammy-linux-
This bug is awaiting verification that the linux-
aws-6.8/6.8.0-1018.19~22.04.1 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-
aws-6.8' to 'verification-done-jammy-linux-
This bug is awaiting verification that the linux-
aws-6.8/6.8.0-1018.19~22.04.1 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-
aws-6.8' to 'verification-done-jammy-linux-
This bug is awaiting verification that the linux-
aws-6.8/6.8.0-1018.19~22.04.1 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-
aws-6.8' to 'verification-done-jammy-linux-
This bug is awaiting verification that the linux-
aws-6.8/6.8.0-1018.19~22.04.1 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-
aws-6.8' to 'verification-done-jammy-linux-
This bug is awaiting verification that the linux-
aws-6.8/6.8.0-1018.19~22.04.1 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-
aws-6.8' to 'verification-done-jammy-linux-
This bug is awaiting verification that the linux-
aws-6.8/6.8.0-1018.19~22.04.1 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-
aws-6.8' to 'verification-done-jammy-linux-
This bug is awaiting verification that the linux-
aws-6.8/6.8.0-1018.19~22.04.1 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-
aws-6.8' to 'verification-done-jammy-linux-
Adding just the "splash" option to GRUB_CMDLINE_LINUX_DEFAULT does the
trick for me. Although you can't see the full boot log, at least it
reboots and shutdowns fully.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https:
75 matches
Mail list logo