In the next few days, when I get some "spare" time... I will spin up a
few test Jammy VM's to capture what depends it has to pull in from other
repo's, so that the depends can be ID'ed and maybe those packages can be
added to that Jammy package in this new PPA.
Otherwise, as I just found out with
Works great. Tested, and a lot simpler, because there are builds for
Jammy, Mantic and Noble.
The command log for the updated work-around using the "Backports build PPA"
>>>
sudo su -
zpool export -a
zpool import -N -R /mnt rpool
zpool import -N -R /mnt bpool
UUID=$(zfs list | awk
Link to this bug, just for package 'nvidia-driver-390':
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-
drivers-390/+bug/2051436, which is a duplicate of :
https://bugs.launchpad.net/ubuntu/jammy/+source/nvidia-graphics-
drivers-390/+bug/2028165
For nvidia-driver-390, there is another
@mkukri ---
>>>
The question is, are we going to backport the fix to 2.06 and push that to the
updates channel, or can this wait for the 2.12 SRU sometimes after April?
>>>
What does that mean?
Option #1 -- The cherry picked Grub2 2.12 ZFS related commit code gets
applied to Grub2 2.06 as a
So yes. Grub2 2.12 with those patches fixes this issue for Jammy, Mantic
and Noble. We need to apply the fix to all these releases.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
The command log for the work-around for a broken jammy install:
>>>
sudo su -
zpool export -a
zpool import -N -R /mnt rpool
zpool import -N -R /mnt bpool
UUID=$(zfs list | awk '/^bpool\/BOOT\/ubuntu_/ {print $1}' | sed
's/bpool\/BOOT\/ubuntu_//g')
zfs import rpool/ROOT/ubuntu_$UUID
zfs import
@rlaager ---
When I said reconfigure, i did:
>>>
sudo grub-install --target=x86_64-efi --efi-directory=/boot/efi \
--bootloader-id=ubuntu --recheck --no-floppy
>>>
So yes, was that.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
Wahoo! Found the magic combination.
chrooted into the broken jammy system.
Add a Noble sources list.
Add the ppa. Edit the added
/etc/apt/sources.list.d/ubuntu-uefi-team-ubuntu-build-jammy.list's active line
to:
>>>
deb [trusted=yes]
Since it is also built for Mantic, I would expect it works for Mantic
Also. (Will confirm later.)
I spun up a Jammy ZFS image. Changed the sources list to Noble. Added
the PPA. Installed packages 'grub2 & shim'... Let it pull in the depends
it needed. Change the sources.list back to jammy. Did
Forgot to mention... Those "@feature" changes, that are suspected as
being the problems when enabled... unfortunately cannot be done on an
already created bpool. Those can only be set at pool "creation time".
So I'm working on a script to recreate bpool which those specific option
settings from
I'm working on trying various differing work-arounds with what is there
natively.
I tried building the newest git on Grub2 2.12. Fails building at a point
which is says way fixed for the error i am getting, but still fails on
the make at the same point. (asorti ot defined)
I'm also working on
Also affect Mantic...
** Also affects: zfs-linux (Ubuntu)
Importance: Undecided
Status: New
--
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/bugs/2051999
Title:
Grub2 2.06 has
Ubfan1 and I have talking about this out on the Forum: Were we have to help
other Users with this.
RE: https://ubuntuforums.org/showthread.php?t=2494834
I think his idea on something is genius: That if the compiler version is
brought in by the kernel on kernel updates as a dependency, so that
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: 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/2051457
Title:
Jammy 22.04.3 gcc compiler no longer builds
** Also affects: dkms (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to dkms in Ubuntu.
https://bugs.launchpad.net/bugs/2051457
Title:
Jammy 22.04.3 gcc compiler no longer builds
Public bug reported:
Fresh install...Not doing anything other than installing brave and this
error kicked off
ProblemType: Package
DistroRelease: Ubuntu 23.10
Package: nvidia-firmware-535-535.154.05 535.154.05-0ubuntu0.23.10.1
ProcVersionSignature: Ubuntu 6.5.0-15.15-generic 6.5.3
Uname: Linux
I have a user that is affected by this bug. I am asking him to post here
with his info. I ask that you reopen this... For him = His is a VM in
Hyper-V.
RE: https://ubuntuforums.org/showthread.php?t=2494675
>From what I can see, there was a Kernel Bug that was patched for this
error upstream:
full dmesg output
** Attachment added: "output of dmesg"
https://bugs.launchpad.net/ubuntu/+source/linux-hwe-6.5/+bug/2050032/+attachment/5741313/+files/dmesg
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-6.5 in Ubuntu.
Public bug reported:
[ 22.989826]
[ 22.989831] UBSAN: array-index-out-of-bounds in
/build/linux-hwe-6.5-q7NZ0T/linux-hwe-6.5-6.5.0/drivers/scsi/mpt3sas/mpt3sas_scsih.c:4667:12
[ 22.989838] index 1 is out of
I believe, as pointed out in https://bugs.launchpad.net/bugs/2032174 ,
it has to do with kernel 6.5, source package 'linux'. & source package
'linux-oem-6.5' ... This seems similar, yet a different problem.
It was there for the 6.2.0 series of kernels, but disappeared last week
when the HWE stack
This is kernel 6.2 + nvidia issue, I've fixed by this patch
https://github.com/NVIDIA/open-gpu-kernel-modules/issues/429
** Bug watch added: github.com/NVIDIA/open-gpu-kernel-modules/issues #429
https://github.com/NVIDIA/open-gpu-kernel-modules/issues/429
--
You received this bug
Is same with kernel 6.2.0-37-generic.
But, is resolved if I use boot parameter "reboot=acpi" in
/etc/default/grub
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed-hwe-6.2 in Ubuntu.
https://bugs.launchpad.net/bugs/2032136
@jimmymmick -- From LTS to a dev interim version? Maybe if other things
supported newer hardware, but I am on 13th Gen iCore and still doing
fine on 22.04.3. The HWE stack is the Lunar kernels (6.2.0-x). But Lunar
loses support soon any ways...
In fact if you update to Mantic (23.10) right now,
Wait... I seem to be confused by this:
>>>
mafoelffen@noble-d05:~$ apt-cache show zfsutils-linux | grep 'Package:\|Breaks:'
Package: zfsutils-linux
Breaks: openrc, spl (<< 0.7.9-2), spl-dkms (<< 0.8.0~rc1), zfs-dkms (>>
2.2.2-0ubuntu1...), zfs-dkms (<< 2.2.2-0ubuntu1)
>>>
Does that mean, even
Just passed on to me from FL140:
https://github.com/openzfs/zfs/issues/15586#issuecomment-1836806381
Is an updated script to manually build and install the OpenZFS native
deb packages, including 'zfs-dkms' 2.2.2.
** Bug watch added: github.com/openzfs/zfs/issues #15586
Rick and I have been testing the Proposed 2.2.2 packages in Noble since
yesterday morning. Great so far.
@fl140 --
Thanks you for the link. I'll pass that on.
Waiting to see if anything of this helps with: zfs-dkms
2.1.5-1ubuntu6~22.04.2 https://bugs.launchpad.net/ubuntu/+source/zfs-
@xnox --
Thank you!!!
This is what I see in Noble right now:
>>>
mafoelffen@noble-d05:~$ apt list -a zfsutils-linux
Listing... Done
zfsutils-linux/noble-proposed 2.2.2-0ubuntu1 amd64
zfsutils-linux/noble,now 2.2.1-0ubuntu1 amd64 [installed]
>>>
So it 2.2.1 got pushed to Noble main, with 2.2.2 to
From what I got after that... It errors in dpkg, so it leaves the old
modules built for the kernels that it did upgrade to successfully
(there).
Mine error'ed out when it tried to upgrade from 6.2.0-36 to 6.2.0-37. If
worried me also, BUT... It did reboot.
Since linux-image-6.2.0-37-generic
@seth-arnold -- Thank you for those links. Those explain a lot of what
is currently happening, and the changes coming down.
This was comforting from robn:
"If you can't get an updated ZFS (2.2.2, 2.1.14, or a patch from your vendor)
then 'dmu_offset_next_sync=0' is the next best thing."
Anyone
@toekneefan -- Our tests of 2.2.1 from Noble Proposed showed that it was
actually "enabled" by default, instead of being disabled like they said
they did in it's release notes... So the rpool installs as "active", and
any other pools created with feature=default (or just omitted) are
created as
I wondered why my old bug report has not gotten any attention. Being a
duplicate of this bug didn't help, but at least someone from the
security team marked it as a duplicate of this bug.
BUT... On Bug Reports filed against zfs-linux, there are 55 bugs, with
not one single person assigned, that
This is my merge fo a Bug Report marked as a duplicate of this one:
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/2044969
In the OpenZFS patch thread, they had said that feature@block_cloning,
because of the underlying bug, OpenZFS had said they turned that feature
off by default in
Here is the link:
https://github.com/Mafoelffen1/OpenZFS-Ubuntu-Admin/blob/main/ZFS-DKMS-WORK-AROUND.md
It is tested. It is somewhat daunting... But it works.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
I've tested it and handed it off to Rick for him to look it over and
test (second set of eyes)...
--
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/bugs/2044630
Title:
zfs-dkms
** Description changed:
On todays updates, zfs-dkms 2.1.5-1ubuntu6~22.04.2 failed to build
kernel module.
Genrated Crash report, but couldn't send it on it's own.
Error it kept throwing was:
>>>
Setting up zfs-dkms (2.1.5-1ubuntu6~22.04.2) ...
Loading new zfs-2.1.5 DKMS
<>
Rick S and I have talked a lot today... trying to remember:
I added a repo on my GitHub on: Open-ZFS-Admin > "How To Uninstall
package 'zfs-dkms' And Survive"
We had to remember:
- Why we actually started using it.
Ubuntu, in the past, did not rebuild the zfs module, so we needed zfs-
dkms
It blew 1fallen's machine out of the water.
Before doing anything, backup your bpool and rpool via rsync so you have
a fall back point.
Start a thread on UbuntuForums > Installations and Updates. I will talk
you through a work-around to uninstall zfs-dkms and everything else I
did to get around
zfs-linux 2.2.2 released tonight...
In the changelog:
dnode_is_dirty: check dnode and its data for dirtiness #15571 #15526
Which is the above patch for CVE 2023-49298
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
That blew out the ability to boot. Ended up having to remove zfs-dkms.
Reinstalling kernel and boot.
Back up.
zfs-dkms is broken big time for 22.04.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
I got tired of waiting for anyone to triage this... I removed package
zfs-dkms so I could applied my updates...
They upgraded successfully. Including building the modules for kernel
6.2.0-37-generic.
Then installed package zfs-dkms, where it failed again on building the
module for 6.2.0-37.
--
It is not just preventing upgrades, it is preventing the upgrade to Linux
kernel 6.2.0-37-generic
>>>
mafoelffen@Mikes-ThinkPad-T520:~$ modinfo zfs | grep -e '^filename\|^version'
filename: /lib/modules/6.2.0-36-generic/kernel/zfs/zfs.ko
version:2.1.9-2ubuntu1.1
To install 2.2.1, i had to enable proposed in sources, then explicitly install:
>>>
sudo apt install -y zfsutils-linux=2.2.1-0ubuntu1
libnvpair3linux=2.2.1-0ubuntu1 libuutil3linux=2.2.1-0ubuntu1
libzfs4linux=2.2.1-0ubuntu1 libzpool5linux=2.2.1-0ubuntu1
zfs-dkms=2.2.1-0ubuntu1
>>>
To get all the
** Information type changed from Private Security to Public Security
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-49298
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
Seems to also affect Mantic, if it was installed as jammy, the upgraded
to Mantic. But doesn't seem to affect Mantic system if they were
installed fresh as Mantic. All Tests, so far, show it does not affect
Noble at all (either upgraded from Mantic or installed fresh).
--
You received this bug
Posted a warning out on the Forum:
https://ubuntuforums.org/showthread.php?t=2492886=14166863#post14166863
--
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/bugs/2044630
Title:
zfs-dkms
Attempt at remove and reinstall of package zfs-dkms failed (see
attached)
No, Crashed again on zks-dkms. Can't et past it. And only affects Jammy.
** Attachment added: "reinstall-output.txt"
No. Lunar upgraded fine to that package version with the same kernel.
But:
on this 22.04.3 machine now:
>>>
mafoelffen@Mikes-B460M:/data/ISO$ apt list zfs-dkms
Listing... Done
zfs-dkms/jammy-updates,jammy-updates,jammy-security,jammy-security,now
2.1.5-1ubuntu6~22.04.2 all [installed]
N: There
This is not a problem for Noble, as it uses
>>>
fs-dkms/noble,noble 2.2.0-0ubuntu3 all
>>>
Not a problem for Mantic, as it uses:
>>>
zfs-dkms/mantic,mantic 2.2.0~rc3-0ubuntu4 all
>>>
BUT-- In today's updates for Lunar:
>>>
libzfs4linux/lunar-updates,lunar-security 2.1.9-2ubuntu1.2 amd64
I remember this error on zfs-dkms when the kernel ranges went from 5.19
to 6.2.0-X... With package zfs-dkms 2.1.5-1ubuntu6~22.04.1.
RE: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/2030100
That was fixed a few updates after that, but now we are back to this:
>>>
*** ZFS Version:
** Attachment added: "zfs-make.log"
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/2044630/+attachment/5723611/+files/zfs-make.log
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
There weer no other make logs for any other kernels present(???)
>>>
mafoelffen@Mikes-ThinkPad-T520:~/Downloads$ ls /var/lib/dkms/zfs/2.1.5/
5.15.0-89-generic source
>>>
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in
** Attachment added: "zfs-dkms-2.1.5_5.15.0-89-generic_make.log"
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/2044630/+attachment/5723604/+files/zfs-dkms-2.1.5_5.15.0-89-generic_make.log
--
You received this bug notification because you are a member of Kernel
Packages, which is
** Attachment added: "zfs-dkms.0.crash"
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/2044630/+attachment/5723603/+files/zfs-dkms.0.crash
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
Public bug reported:
On todays updates, zfs-dkms 2.1.5-1ubuntu6~22.04.2 failed to build
kernel module.
Genrated Crash report, but couldn't send it on it's own.
Error it kept throwing was:
>>>
Setting up zfs-dkms (2.1.5-1ubuntu6~22.04.2) ...
Loading new zfs-2.1.5 DKMS files...
Building for
FWIW, I switched back to ext4 and am no longer experiencing the same
issues.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed-hwe-5.19 in Ubuntu.
https://bugs.launchpad.net/bugs/2028186
Title:
zfs with encryption: sluggish
This is still affected with Linux kernel 6.2.0-33-genric on this laptop.
Nothing has changed. It still will not do a "reboot" without ending up
at a BIOS Boot menu.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed-hwe-6.2 in
Stuck on Recovering Journal (clean) after upgrading to Ubuntu 22.04.4 LTS
I have a NVIDIA Corporation GA104GL [RTX A4000] (rev a1)
Kernal: 6.2.0-35-generic.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
Public bug reported:
Now that zfs 2.2.0 has been release can you move to a released version
of zfs instead of a release candidate.
** Affects: zfs-linux (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages,
ack; filed bug 2028186.
--
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/bugs/1973827
Title:
Laptop freezes when recovering from suspend / sleep mode
Status in gnome-shell package in
Public bug reported:
I had been using Jammy on a Thinkpad T470 for months without problems.
I decided to try a fresh Ubuntu Desktop install using ZFS, using the
install-time option for full-disk encryption.
After using the fresh install for a little while, I noticed that the
system was "more
I'm seeing a similar issue on a laptop which was working fine until I
reinstalled Ubuntu Jammy with ZFS (with full-disk encryption enabled).
Sometimes it freezes for several seconds, but sometimes I wait hours and
it never recovers.
I don't think this is a gnome-shell issue, but I'm unsure how to
Workaround: boot with laptop open and close once the desktop appears.
The same problems appears when the laptop awakens from sleep mode. The
workaround for this is to CTL-ALT-F2 followed by CTL-ALT-F1.
--
You received this bug notification because you are a member of Kernel
Packages, which is
It is doing the same thing again (see original message) when trying to
run the update to kernel 6.2.0-1005.
--
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/2024113
Title:
Linux 6.2.0-20
not just
Intel cards with these linux power control speed and packet loss
symptoms...
Mike
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.14 in Ubuntu.
https://bugs.launchpad.net/bugs/1930754
Title:
e1000e extremly slow
Public bug reported:
upgrade from 22.10 to 23.04 went smoothly on my Dell laptop. I have an
external monitor that on a dock. It works fine in 22.10 but won't
activate properly with 23.04. If I boot with laptop lid closed I get the
grub screen and then, once it boots, neither screen works.
apport information
** Attachment added: "acpidump.txt"
https://bugs.launchpad.net/bugs/2008823/+attachment/5661371/+files/acpidump.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/2008823/+attachment/5661370/+files/WifiSyslog.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/2008823/+attachment/5661369/+files/UdevDb.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/2008823/+attachment/5661368/+files/ProcModules.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/2008823/+attachment/5661367/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/2008823/+attachment/5661366/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/2008823/+attachment/5661365/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "Lsusb-v.txt"
https://bugs.launchpad.net/bugs/2008823/+attachment/5661364/+files/Lsusb-v.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "Lspci-vt.txt"
https://bugs.launchpad.net/bugs/2008823/+attachment/5661363/+files/Lspci-vt.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/2008823/+attachment/5661362/+files/Lspci.txt
--
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/2008823
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/2008823/+attachment/5661361/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Tags added: apport-collected staging
** Description changed:
Looking at /sys/kernel/boot_params/data I see that much of the 4096 byte
buffer is old kernel data.
It really stood out as I saw parts of email contents in there.
It seems
Have moved status to 'Confirmed' without attaching kernel log files as I
believe these are not relevant.
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
** Description changed:
On Ubuntu 22.04.2 LTS using fully updated gcc and gdb, I find that by
default gcc produces
Public bug reported:
On Ubuntu 22.04.2 LTS using fully updated gcc and gdb, I find that by
default gcc produces DWARF5 debug files which gdb cannot read, with the
following error:
Dwarf Error: DW_FORM_line_strp used without required section
If I add the flags `-gdwarf-4 -gstrict-dwarf` to `gcc`
I can confirm this occurred on my machine, it was not an external HDD. I
have an MSI MS-7976 motherboard and a Samsung M.2 SSD.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bcmwl in Ubuntu.
https://bugs.launchpad.net/bugs/2007439
nvidia/520.56.06
virtualbox/6.1.38
zfs/2.1.6, 5.15.0-52-generic
mike@mike-think:/lib/modules$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 22.04.1 LTS
Release: 22.04
Codename: jammy
mike@mike-think:/lib/modules$ uname -a
moudles:
nvidia/520.56.06
virtualbox/6.1.38
zfs/2.1.6, 5.15.0-52-generic
mike@mike-think:/lib/modules$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 22.04.1 LTS
Release:22.04
Codename: jammy
mike@mike-think:/lib/modules$ uname -a
Linux mike
Public bug reported:
Expected on kinetic: dkms will sign built modules with MOK key if
requested.
What happens:
dkms outputs "Binary kmod-sign not found, modules won't be signed"
Fix:
update dkms to 3.0.7: https://github.com/dell/dkms/pull/242
** Affects: dkms (Ubuntu)
Importance:
Not only the resolution is wrong for the USB-C display but also the
order is different. Unplugging and plugging the connector seems to fix
the issue (Ubuntu 22 LTS).
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Can confirm on Lenovo ThinkPad L13Yoga. Kernel 5.15.0-46. Deactivating
the security chip in BIOS and other proposed solutions in different
forum and here to no avail.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Perhaps this comment from the changes log is relevant:
amd/display: set backlight only if required
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-5.15 in Ubuntu.
https://bugs.launchpad.net/bugs/1981727
Title:
kernel
For whatever reason I don't have crashdb.conf ...
kordosky@miketop5:~$ apport-collect 1981727
Traceback (most recent call last):
File "/usr/share/apport/apport-gtk", line 596, in
app = GTKUserInterface()
File "/usr/share/apport/apport-gtk", line 56, in __init__
Verified that the behavior is the same when the laptop is used stand-
alone, unconnected to a docking station.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-5.15 in Ubuntu.
https://bugs.launchpad.net/bugs/1981727
Title:
Public bug reported:
A recent update to 5.15.0-41 results in my laptop screen (Dell Precision
7520) being unable to come up to full brightness. I have verified that I
can revert to 5.13.0-52 and the problem is not there. I looked at
/sys/class/backlight/nv_backlight/max_brightness which lists
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
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/1967960
Title:
LightDM login display corrupted in 22.04 Beta
Status
The same observed with NVIDIA 470.86 driver.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-440 in Ubuntu.
https://bugs.launchpad.net/bugs/1877226
Title:
nvidia - external display unavailable after screen goes
Same here
0. Ubuntu version: Ubuntu 20.04.3 LTS
1. Laptop model: Asus TUF Gaming F15 FX506HM-HN019T
2. Touchpad manufacturer: Unknown
3. The problem started right after installing ubuntu, I realised it when I was
selecting the language the touchpad did not work at all.
--
You received this bug
This appears to be triggered by commit
4f73581836f031611b281c8c6017202f36afbf6b, the change is reported as a
bug in the 5.13 kernel as well and appears to have been brought into the
5.11 HWE kernel.
https://bugzilla.kernel.org/show_bug.cgi?id=214455
--
You received this bug notification because
Same problem here with Ubuntu 20.04 on a Dell XPS 15 9500, but in my
case it was triggered by update from kernel 5.11.0-38-generic to
5.11.0-40-generic.
Apt history shows the update as occurring last Friday morning, and the
next time I rebooted (the day after) the WiFi module stopped working,
I see the same error on HP Elitebook 820 G3 on iwlwifi_1 using linux-
firmware 1.187.20 on Ubuntu 20.04
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to thermald in Ubuntu.
https://bugs.launchpad.net/bugs/1803881
Title:
thermal
*** This bug is a duplicate of bug 1574582 ***
https://bugs.launchpad.net/bugs/1574582
** This bug has been marked a duplicate of bug 1574582
HP lt4120 Snapdragon X5 LTE USB modem not recognized by network-manager
--
You received this bug notification because you are a member of Kernel
Debug loop from Modem Manager with endless loop on modem initialization
on kernel 5.13.x.
** Attachment added: "Debug Log from Modem Manager"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950385/+attachment/5540476/+files/ModemManager.Debug.log
--
You received this bug notification
***I have a recent Fossil's ModemManager 1.16.6-2-20.04 and under kernel 5.8.x
it works:
ModemManager.service - Modem Manager
Loaded: loaded (/lib/systemd/system/ModemManager.service; enabled; vendor >
Active: active (running) since Fri 2021-11-12 14:46:59 CET; 2h 19min ago
Main PID:
apport information
** Attachment added: "acpidump.txt"
https://bugs.launchpad.net/bugs/1950385/+attachment/5540349/+files/acpidump.txt
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages,
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1950385/+attachment/5540347/+files/UdevDb.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
1 - 100 of 1096 matches
Mail list logo
