apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1763144/+attachment/513/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad
apport information
** Attachment added: "PulseList.txt"
https://bugs.launchpad.net/bugs/1763144/+attachment/515/+files/PulseList.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/
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1763144/+attachment/514/+files/ProcModules.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/b
Note that the thermal limit seems to be rewritten by the EC at random
times.
The person originally discovering the issue wrote a userspace daemon to
write the proper stuff in memory from time to time -
https://github.com/erpalma/lenovo-throttling-fix - but this should best
get fixed in the kernel
An actually useful dmesg log (from journalctl -k)
** Attachment added: "dmesg.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1763144/+attachment/520/+files/dmesg.txt
** Summary changed:
- Significantly lower power and thermal limits on T480s (and probably others)
than on Wind
I have seen this problem on all bionic kernels I have tested. The
machine has never seen anything older than bionic. I installed it from a
daily end of March.
The mainline kernel does not fix the bug.
** Tags added: bug-exists-upstream
** Changed in: linux (Ubuntu)
Status: Incomplete => C
Sorry, messed up the tag a bit.
--
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/1763144
Title:
Significantly lower power and thermal limits on ThinkPad T480s (and
probably others) than
Sure, it's not designed for 44W by Intel. I only measured 27W maximum
when configured to 44W. It's just that the laptop is likely configured
for an overall thermal limit of 44W because it can house a MX150 with
the same cooling system (dual heat pipe). In any case, on Windows it is
not bound by 15W
Public bug reported:
@apw Permissions changed from 600 to 644 in proposed:
-rw--- 1 root root 8263536 Mar 7 17:36 /boot/vmlinuz-4.15.0-12-generic
-rw--- 1 root root 8265464 Mar 16 10:49
/boot/vmlinuz-4.15.0-12-generic.efi.signed
-rw--- 1 root root 8267632 Mar 16 18:49 /boot/vmlinuz-
Confirmed fixed in -20 and that reached release.
** Changed in: linux-signed (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed in Ubuntu.
https://bugs.launchpad.net/bugs/176
depmod failed here when configuring linux image, reassigning
** Package changed: ndiswrapper (Ubuntu) => linux (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/1750480
Title:
pac
I cannot possibly imagine how a blank screen on installing nvidia
drivers is an apt problem, so I'm marking that as invalid.
** Changed in: apt (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to n
** Package changed: apt (Ubuntu) => dkms (Ubuntu)
--
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/1780885
Title:
hangs at Building initial module for 4.15.0-23-generic (promptless
passwo
This bug was about different power limits for the non-dGPU version
compared to Windows. It turned out that the power limits in Windows are
broken, and the ones in Linux are correct, so this bug is in fact
Invalid.
For the dGPU, I'm not sure what the intention is. Maybe report a bug
against the nvi
This bug was about different power limits for the non-dGPU version
compared to Windows. It turned out that the power limits in Windows are
broken, and the ones in Linux are correct, so this bug is in fact
Invalid.
For the dGPU, I'm not sure what the intention is. Maybe report a bug
against the nvi
bionic:
before (1.6.6..)
Removing unused kernel packages: linux-headers-generic linux-image-generic
after (1.6.8):
Removing unused kernel packages: linux-headers-generic
and just to verify, if you install dkms:
No packages found that can be upgraded unattended and no pending auto-removals
(the
(in practice the headers do not matter - if you have dkms installed, it
will keep the headers alive)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-meta in Ubuntu.
https://bugs.launchpad.net/bugs/1787460
Title:
Unattended upgrade
cosmic:
before (1.7.0ubu...)
Removing unused kernel packages: linux-headers-generic linux-image-generic
after (1.7.2):
Removing unused kernel packages: linux-headers-generic
That does the job well enough, even if the headers end up being removed
in this particular test case.
--
You received thi
** Also affects: linux-hwe (Ubuntu)
Importance: Undecided
Status: New
** Package changed: linux-hwe (Ubuntu) => linux-meta-hwe (Ubuntu)
** Also affects: linux-meta (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ke
As Adam mentioned, the top-level kernel meta packages should change
their section to metapackages, so we don't mark linux-image-generic for
autoremoval if linux-generic is removed.
I'm looking into adding additional NeverAutoRemove entries for the
metapackages to apt as
"^linux-image-[a-z
apt-side fix in
https://salsa.debian.org/apt-
team/apt/commit/a4b0ce5a4f5068f780b3aa94473230b5093a837d
** Changed in: apt (Ubuntu)
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-meta in Ubu
** CVE removed: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2019-3462
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-meta in Ubuntu.
https://bugs.launchpad.net/bugs/1787460
Title:
Unattended upgrades removed linux-image-generi
** Also affects: apt (Ubuntu Trusty)
Importance: Undecided
Status: New
** Also affects: linux-meta (Ubuntu Trusty)
Importance: Undecided
Status: New
** Also affects: linux-meta-hwe (Ubuntu Trusty)
Importance: Undecided
Status: New
** Changed in: apt (Ubuntu Xenial)
Broken again in disco, let's update the state.
** Also affects: linux (Ubuntu Disco)
Importance: Medium
Assignee: Tim Gardner (timg-tpi)
Status: Fix Released
** Also affects: linux-hwe (Ubuntu Disco)
Importance: Undecided
Status: Confirmed
** Also affects: linux (Ubuntu
** Also affects: apt (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: linux-meta (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: linux-meta-hwe (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: apt (Ubuntu Cosmic
** Description changed:
- On a fairly fresh install of 18.04 with no modifications whatsoever to
- the unattended-upgrades configuration, it decided to remove linux-image-
- generic which also removed linux-modules-extra which caused sound
- drivers to disappear, etc.
+ [Impact]
+ If a user accide
Been running for 1d 15h sofar and it seems to be fine
--
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/1896091
Title:
[i915] Noise-like lines of graphics corruption when moving windows in
I think we've gotten enough (independent) verifications of this now to
mark it as done.
** Tags removed: verification-needed-groovy
** Tags added: verification-done-groovy
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
h
That's correct. 33 was a hot fix release for a data loss in 31 that did
not include the changes from 32. They'll come back in 34.
--
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/1896091
Tit
Why are we looking at focal now? The change to systemd only happened
after the opening of groovy.
Data is tricky. There are a ton of different cpufreq drivers that are
affected, and they all have different behavior. pstates alone has
different behavior on newer intels that do pstates in hardware (
For example, the measurements on the X220 do not reflect situation on
modern Intel systems, as they scale differently from Skylake and newer,
as they do not have HWP.
A CPU with HWP (hardware P-states) behaves as you'd expect sort of - it
runs at close to max frequency all the time, and scales dow
There were no changes in that grub update affecting normal boot, only
microcode loading was disabled for recovery boots and a feature to
reorder kernels was added.
** Package changed: grub2 (Ubuntu) => linux (Ubuntu)
--
You received this bug notification because you are a member of Kernel
Packag
That's correct, the menu should not show automatically, you either
configure it to do so or you press Esc during boot. Marking as invalid.
** Changed in: casper (Ubuntu)
Status: New => Invalid
** Changed in: grub2 (Ubuntu)
Status: New => Opinion
** Changed in: zfs-linux (Ubuntu)
Public bug reported:
I left my desktop (T480s thinkpad docked to ThinkVision P24h-10)
unattended for a while, and then got the error message and now have
funny lines on activity, e.g. red lines flashing on top of gnome-shell
bar when switching windows, or white blocks/lines around typing text.
Th
That said, hmm, it took an hour or so after the backtrace for it to
cause visual distortion or I misremember, or it gets worse over time.
--
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/1896
apport information
** Attachment added: "Lsusb-v.txt"
https://bugs.launchpad.net/bugs/1896091/+attachment/5411752/+files/Lsusb-v.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/1896
apport information
** Attachment added: "Lsusb-t.txt"
https://bugs.launchpad.net/bugs/1896091/+attachment/5411751/+files/Lsusb-t.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/1896
apport information
** Attachment added: "CRDA.txt"
https://bugs.launchpad.net/bugs/1896091/+attachment/5411746/+files/CRDA.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/1896091
Ti
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1896091/+attachment/5411756/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad
apport information
** Attachment added: "IwConfig.txt"
https://bugs.launchpad.net/bugs/1896091/+attachment/5411747/+files/IwConfig.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/18
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1896091/+attachment/5411753/+files/ProcCpuinfo.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/b
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1896091/+attachment/5411748/+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/1896091
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1896091/+attachment/5411755/+files/ProcEnviron.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/b
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1896091/+attachment/5411754/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.l
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1896091/+attachment/5411750/+files/Lsusb.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/1896091
apport information
** Attachment added: "Lspci-vt.txt"
https://bugs.launchpad.net/bugs/1896091/+attachment/5411749/+files/Lspci-vt.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/18
apport information
** Tags added: apport-collected
** Description changed:
I left my desktop (T480s thinkpad docked to ThinkVision P24h-10)
unattended for a while, and then got the error message and now have
funny lines on activity, e.g. red lines flashing on top of gnome-shell
bar when
apport information
** Attachment added: "RfKill.txt"
https://bugs.launchpad.net/bugs/1896091/+attachment/5411759/+files/RfKill.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/1896091
apport information
** Attachment added: "acpidump.txt"
https://bugs.launchpad.net/bugs/1896091/+attachment/5411762/+files/acpidump.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/18
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1896091/+attachment/5411760/+files/UdevDb.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/1896091
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1896091/+attachment/5411757/+files/ProcModules.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/b
apport information
** Attachment added: "PulseList.txt"
https://bugs.launchpad.net/bugs/1896091/+attachment/5411758/+files/PulseList.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/
Attached dmesg from journalctl. To the best of my knowledge, this is all
that's missing, as apport now has no raw dmesg access anymore and missed
to upload the dmesg.
** Attachment added: "kernel.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1896091/+attachment/5411764/+files/kerne
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1896091/+attachment/5411761/+files/WifiSyslog.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/bug
Attached dmesg from journalctl. To the best of my knowledge, this is all
that's missing, as apport now has no raw dmesg access anymore and missed
to upload the dmesg.
** Attachment added: "kernel.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1896091/+attachment/5411763/+files/kerne
The corruption also happens in build
5.9.0-050900rc4drmintelnext20200915-generic but the error in dmesg does
not, and it's less, it only happens on window management actions (switch
window
Surprisingly with that, restarting gnome-shell actually fixes the issue
(it did not with normal kernel).
--
Public bug reported:
In a recent merge from Debian we lost ondemand.service, meaning all CPUs
now run in Turbo all the time when idle, which is clearly suboptimal.
The discussion in bug 1806012 seems misleading, focusing on p-state vs
other drivers, when in fact, the script actually set the defau
Someone probably needs to look at non-pstate systems as I have no idea
about them.
--
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/1885730
Title:
Bring back ondemand.service or switch ker
@rbalint As said before the kernel messages and bugs are irrelevant and
wrong. They pretend like intel_pstate is different, when in fact it's
this script that is configuring it here. And yes, it needs OS config.
Nor do other distros not do this, but we do it differently. We set the
CONFIG_CPU_FREQ
** Changed in: linux (Ubuntu)
Status: Incomplete => New
** Changed in: linux (Ubuntu)
Status: New => 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/1885730
Title:
Andreas, I've not gotten it more isolated, the minimum I had was running
debian/tests/gnome-desktop-testing in a flatpak-builder source tree (apt
source/pull-lp-source flatpak-builder).
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux
The performance governor is the right choice for servers, but it's not
the right choice on non-server platforms, it's also not the default
kernel setting, it was set because we have the ondemand.service in
userspace that can change it back to ondemand (or well we have the
service because of that ch
passing intel_pstate=disable_hwp on the kernel commandline causes the
kernel to scale the Core i5-8250U down to 1.6 GHz in performance mode,
but that's still a bit off from the 900 MHz it scales down to in
powersave mode.
I believe Windows also does not run the CPUs in performance mode by
default
XPS 13 (Core i5-10210U) with performance governor idles (0.2% usage) at
4 GHz instead of 900 MHz.
--
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/1838141
Title:
intel_pstate not working.
@Colin: I agree with all of that.
Our kernel-side default is not powersave, but performance, across
generic and oem, at the very least:
$ grep CPU_FREQ_DEFAULT_GOV_.*=y /boot/config-5.*
/boot/config-5.4.0-26-generic:CONFIG_CPU_FREQ_DEFAULT_GOV_PERFORMANCE=y
/boot/config-5.4.0-42-generic:CONFIG_CP
Public bug reported:
Okt 07 20:45:43 jak-t480s kernel: BUG: kernel NULL pointer dereference,
address: 002c
Okt 07 20:45:43 jak-t480s kernel: #PF: supervisor read access in kernel mode
Okt 07 20:45:43 jak-t480s kernel: #PF: error_code(0x) - not-present page
Okt 07 20:45:43 jak-t480
The bug report title is the start of a chrome error message, and I can't
see any bug in the dmesg output, so I don't see how this is a bug in the
kernel. I suggest you open an issue on the Chrome bug tracker
https://crbug.com/ for your Chrome issue.
** Changed in: linux (Ubuntu)
Status: Con
Actually I did at
https://bugs.chromium.org/p/chromium/issues/detail?id=1136411 as I see
it too
--
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/1898797
Title:
[1006/183929.019360:ERROR:na
Also adding a gnome-shell task. This happens on 5.8.0-21-generic from
proposed too, and restarting gnome-shell stops the corruptions, so it's
possible this is a gnome issue.
** Also affects: gnome-shell (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification be
Corrupt lines, red flashing across the top bar:
https://photos.app.goo.gl/TgYxkVHRnsrV5wCR9
I use Xorg, and almost exclusively see it on my external monitor. After
locking the screen and having it locked for a while. Saw it once on the
internal one in a week, but like daily on external.
--
You r
Oh, drmtip exists too, I thought you said drmnext which was stuck on
09-18 (and I tested 09-15 which was more stable but not perfect). I'm
currently just running the 5.9.1 mainline kernel for testing purposes,
which so far (2 days in seems stable), but might just break later today,
who knows.
--
It happened a lot more when docked (ext USB-C monitor) than on the
laptop itself.
Kernel 5.9.1 seems good so far. I've not seen the issue yet and my
uptime is 3 days 15 hours without any suspending in between, just screen
locked.
--
You received this bug notification because you are a member of
Well it booted fine to the kernel so I'll reassign it there, some mode
setting going wrong ai assume.
** Package changed: grub2 (Ubuntu) => linux (Ubuntu)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launc
It's possible you see a different bug, I'd suggest opening a new bug
report about it with ubuntu-bug so the kernel team actually has some
data about the system rather than just small comments.
I think we can all agree that the patch (well removal of patch :)) made
a vast improvement in terms of st
The proposed debdiff is wrong, it reverts a patch in the patch series by
adding a new patch. I think we can probably remove the vt-handoff.patch
from the patch series for groovy without much checking, but any SRU will
need to consult with flavours to check if they need the handoff.
--
You receive
Removed spurious grub task.
** No longer affects: grub2 (Ubuntu)
** No longer affects: grub2 (Ubuntu Focal)
--
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/1850130
Title:
zpools fai
Removing bootloader tasks, as the kernel has loaded successfully.
** No longer affects: grub2 (Ubuntu)
** No longer affects: syslinux (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/bu
Given that it boots to the kernel, but the kernel can't setup the drm
device, I'm inclined to believe this is a kernel bug.
** Package changed: grub2 (Ubuntu) => linux (Ubuntu)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubun
Fixed that for now in unattended-upgrades and update-notifier by adding
case "$DPKG_MAINTSCRIPT_PACKAGE::$DPKG_MAINTSCRIPT_NAME" in
linux-image-extra*::postrm)
exit 0;;
esac
We can then still decide if we want to run postinst.d scripts in linux-
image-extra removals or not, but let's
A better (IMO) code to check this is:
case "$DPKG_MAINTSCRIPT_PACKAGE::$DPKG_MAINTSCRIPT_NAME" in
linux-image-extra*::postrm)
exit 0;;
esac
I uploaded update-notifier and unattended-upgrades with that for bug
1458204.
--
You received this bug notification because you are a member of
*** This bug is a duplicate of bug 1724869 ***
https://bugs.launchpad.net/bugs/1724869
** This bug has been marked a duplicate of bug 1724869
ndiswrapper 1.60-3~ubuntu16.04.1 ADT test failure with linux-hwe-edge
4.13.0-16.19~16.04.3
--
You received this bug notification because you are a
Public bug reported:
A friend's card reader in his ThinkPad L430 [10ec:5229] was not
automatically recognized in 4.10.0-40-generic (amd64) on 16.04. He had
to manually load the rtsx_pci module.
** Affects: linux (Ubuntu)
Importance: Undecided
Status: Confirmed
** Attachment added:
*** This bug is a duplicate of bug 1625089 ***
https://bugs.launchpad.net/bugs/1625089
This was fixed in bug 1625089
** Changed in: linux (Ubuntu)
Status: Confirmed => Invalid
** Changed in: linux-hwe (Ubuntu)
Status: Confirmed => Invalid
** This bug has been marked a duplicat
Apparently you have the kernel installed but somehow deleted all its
modules.
** Package changed: apt (Ubuntu) => linux (Ubuntu)
** Changed in: linux (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscrib
*** This bug is a duplicate of bug 1625089 ***
https://bugs.launchpad.net/bugs/1625089
** This bug has been marked a duplicate of bug 1625089
ndiswrapper <= 1.60-2 ADT test failure with linux 4.8.0-11.12
--
You received this bug notification because you are a member of Kernel
Packages, wh
kernel 3.14
-- Julian Andres Klode Wed, 19 Mar 2014 16:08:06
+0100
** Changed in: ndiswrapper (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to irda-utils in Ubuntu.
ht
There is unfortunately nothing we can do here. The bug might be fixed in
newer versions though, I suggest trying them. If not, there is nothing
we can do about it, as ndiswrapper is weird stuff and upstream is not
active.
** Changed in: ndiswrapper (Ubuntu)
Status: New => Opinion
--
You r
Reassigning to dkms, something fishy going on with tmpfiles.
** Package changed: ndiswrapper (Ubuntu) => dkms (Ubuntu)
--
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/1594224
Title:
packa
I have not tried this in recent Ubuntu yet, but I can tell you that
pstate seems to work very well in Debian's 3.10 kernel on my Ivy Bridge
laptop. The problem thus might not be caused by intel_pstate itself but
by a combination with some other option(s) and/or patch. It seems to
increase the frequ
Hi ybdjkfd I don't really understand what you are doing and how it's
relevant. This issue should be fixed in lunar-proposed 2.06-2ubuntu16,
please only add comments if you have meaningful insights regarding the
verification of that update.
--
You received this bug notification because you are a m
The term you're looking for is workaround, not triage or fixes. Triage
is the process of understanding the bug and marking it the correct
things.
Not using the same language as everyone else and writing very long
comments makes it hard to understand.
First I thought you reported an out of memory
The entire upload will be uploaded to all older releases but we do have
a security upload already in the unapproved queues that should go out
first, but that needs approving those first, them passing the SRU
verification, a resigning against the new signing key the new shim
needs, and finally someo
Reproduced issue and dumped test case into https://salsa.debian.org/apt-
team/apt-tests/-/blob/main/edsp/fail-ubuntu-1992513.edsp.log for future
analysis when doing solver work.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphi
I think we debugged this recently but I'm not sure where the end result
of this is that we do not mark packages for removal that have an upgrade
available, hence we end up without a removal request after the first
stage solver, and the Conflicts solver that runs after can't solve that.
--
You rec
** Changed in: apt (Ubuntu)
Status: Triaged => Won't Fix
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-470-server in
Ubuntu.
https://bugs.launchpad.net/bugs/1992513
Title:
apt will not install nvidia-dri
I'm going to set this to Won't Fix because that seems to be an important
part of the solver logic, and the workarounds - running upgrade first,
or using ubuntu-drivers - are easy to do and the potential for
regression significantly outweighs them.
This will get solved eventually by a nicer solver
Various dkms weirdness
"Error! The module acpi-call 1.1.0 is not currently installed."
But there are also like 3 services failing to start in the log, so maybe
the system is just misconfigured somewhere that affects all of them.
The bug also indicates that EFI variables are not supported by the
Public bug reported:
system failed to suspend, see attached logs
ProblemType: Bug
DistroRelease: Ubuntu 21.10
Package: linux-image-5.13.0-19-generic 5.13.0-19.19
ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
Uname: Linux 5.13.0-19-generic x86_64
NonfreeKernelModules: zfs zunicode zavl
** Also affects: grub2 (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: grub2-unsigned (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: grub2 (Ubuntu Jammy)
** Tags removed: rls-mm-incoming
** Changed in: systemd (Ubuntu)
Importance: High => Medium
--
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/2036968
Title:
Mantic minimized/minimal clo
101 - 200 of 340 matches
Mail list logo