I have the same issue on Ubuntu 22.04.4 LTS after the kernel update from:
Linux laptop 6.5.0-26-generic to Linux laptop 6.5.0-27-generic
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Tags added: upgrade-software-version
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to wireless-regdb in Ubuntu.
https://bugs.launchpad.net/bugs/2052441
Title:
2024.01.23 new upstream release
Status in wireless-regdb package in
*** This bug is a duplicate of bug 2039772 ***
https://bugs.launchpad.net/bugs/2039772
** This bug has been marked a duplicate of bug 2039772
package linux-image-6.2.0-31-generic 6.2.0-31.31 failed to install/upgrade:
run-parts: /etc/kernel/postinst.d/dkms exited with return code 11
--
I conquer with chris (platoscave). Pretty all my problems went a away
with time by magic. It is obvious that many bugs plagued us and where
fixed by the different projects composing Ubuntu as time passed by.
22.04 just wasn't ready went it came out.
My only issue that remains is when waking up
** Also affects: fabric-manager-510 (Ubuntu)
Importance: Undecided
Status: New
** Tags added: package-conflict
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to fabric-manager-515 in Ubuntu.
The conclusion at
https://github.com/prometheus/node_exporter/issues/2500 was that the
relevant kernel change that caused this was `- epoll: autoremove wakers
even more aggressively`.
There is a small bug reproduction script in that issue too.
** Bug watch added:
I just noticed that when I simply move the mouse, gnome-shell CPU jumps
up 30% CPU. For those of you suffering from this problem, this is the
issue to follow: https://gitlab.gnome.org/GNOME/gnome-
shell/-/issues/4130
** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #4130
Three days after I commented here (2022-09-26), after and update with
reboot and switching back to Wayland, I notice a good performance
improvement. I cannot explain why.
I still suffer from Video stuttering and lagging across all players
(probably another bug though) and when my system resume
Like everyone else, I am experiencing the same issues.
"intel_iommu=off" in Grub does not help.
Here are some symptoms I suffer; not sure if they are related to this
bug or not, but worth mentioning since they all degrade my Ubuntu
experience since I upgraded from 20.04 to 22.04.
- Overall
Note if someone wants to build a kernel with:
https://lore.kernel.org/linux-pci/20220512202511.34197-2-hdego...@redhat.com/
This patch applies on top of the 3 patches from:
https://git.kernel.org/pub/scm/linux/kernel/git/helgaas/pci.git/log/?h=pci/resource
--
You received this bug notification
Sorry that it is taking so long to fix this. There have been several
attempts at fixing this upstream already, but all of them had to be
reverted/dropped because they were causing issues on other laptop
models.
The latest attempt at fixing this is here:
Sorry that it is taking so long to fix this. There have been several
attempts at fixing this upstream already, but all of them had to be
reverted/dropped because they were causing issues on other laptop
models.
The latest attempt at fixing this is here:
Sorry that it is taking so long to fix this. There have been several
attempts at fixing this upstream already, but all of them had to be
reverted/dropped because they were causing issues on other laptop
models.
The latest attempt at fixing this is here:
Sorry that it is taking so long to fix this. There have been several
attempts at fixing this upstream already, but all of them had to be
reverted/dropped because they were causing issues on other laptop
models.
The latest attempt at fixing this is here:
Sorry that it is taking so long to fix this. There have been several
attempts at fixing this upstream already, but all of them had to be
reverted/dropped because they were causing issues on other laptop
models.
The latest attempt at fixing this is here:
** Also affects: nvidia-graphics-drivers-390 (Ubuntu)
Importance: Undecided
Status: New
** Tags added: package-conflict
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu.
** Package changed: linux (Ubuntu) => initramfs-tools (Ubuntu)
** Changed in: initramfs-tools (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Note I've also filed a bug against initramfs-tools in Debian for this,
see: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1001409
** Bug watch added: Debian Bug tracker #1001409
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1001409
--
You received this bug notification because you
The component here should be initramfs-tools which I selected at the "Report a
bug" page, but I got at that page from the link at:
https://bugs.launchpad.net/ubuntu/+source/linux/ so I guess launchpad just
decided to ignore my answer to "In what package did you find this bug?",
because I came
Public bug reported:
Starting with kernel 5.17 the kernel supports the builtin privacy
screens built into the LCD panel of some new laptop models.
This means that the drm drivers will now return -EPROBE_DEFER from their
probe() method on models with a builtin privacy screen when the privacy
Thanks for reporting.
I was unable to reproduce this bug, iotop installed without any issues
for me. I suspect that this and bug 1951578 might have some common root
cause. Could you please attach the output from `apt policy iotop` to see
if it knows about the package at all? Also could you check
Kai-Heng, thank you for providing the test kernel.
Folks, if you need to add pci=nocrs to your kernel-commandline to get
your touchpad to work, please test this kernel:
https://people.canonical.com/~khfeng/lp1878279/
With pci=no_e820 on the kernel commandline (replacing pci=nocrs). If the
*** This bug is a duplicate of bug 1946108 ***
https://bugs.launchpad.net/bugs/1946108
** This bug has been marked a duplicate of bug 1946108
touchpad is not wokring at all, does not get recognized
--
You received this bug notification because you are a member of Kernel
Packages, which
Please test a kernel build with this patch, combined with adding
"pci=no_e820" added to the kernel commandline. See comment 133 for more
details.
** Patch added: "[PATCH] x86/PCI: Add pci=no_e820 cmdline option to ignore E820
reservations for bridge windows"
This is a follow-up to comment #123
Sorry for the long silence on this bug. I was hoping one of the upstream
pci-subsys devs would help out with this...
Since that did not happen I've been looking into fixing this myself now.
I've come up with a solution which still involves a kernel cmdline
so that the device is fully in tablet mode; and then back to laptop mode again ?
3.3 perhaps it stops responding after a suspend/resume?
Regards,
Hans
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.ne
Possibly fixes the issue reported in bug 1931432 as wel...
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to crash in Ubuntu.
https://bugs.launchpad.net/bugs/1935679
Title:
crash: build failure on RISC-V
Status in crash package in
I've been working with a Fedora reporter to try and solve the case where
pci=nocrs helps to get a working touchpad, see:
https://bugzilla.redhat.com/show_bug.cgi?id=1868899
Thanks to the latest set of logs attached there, I now am finally
starting to understand what is going on here.
Your BIOS
Ratul, the patch which I attached won 't help you. The patch is
basically no good, because the problem is not what I thought it was.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed-hwe in Ubuntu.
Bernhard, no in the mean time I've learned that my patch is no good. I'm
currently debugging this with a Fedora user who also needs pci=nocrs to get the
touchpad to work:
https://bugzilla.redhat.com/show_bug.cgi?id=1868899
But this is going quite slow because the cycle between me providing the
*** This bug is a duplicate of bug 1933762 ***
https://bugs.launchpad.net/bugs/1933762
** This bug has been marked a duplicate of bug 1933762
Brightness hotkeys(Fn+F5 for decrease and Fn+F6 for Increase) are not
working on Ubuntu 20.04. Hardware Lenovo Ideapad-5-15ITL05
--
You received
** Also affects: linux-oem-5.10 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.10 in Ubuntu.
https://bugs.launchpad.net/bugs/1933762
Title:
Brightness hotkeys(Fn+F5 for
*** This bug is a duplicate of bug 1931432 ***
https://bugs.launchpad.net/bugs/1931432
** This bug has been marked a duplicate of bug 1931432
crash FTBFS on riscv64
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to crash in Ubuntu.
Seems to fail with a seg fault on the version in 21.04,
https://bugs.launchpad.net/ubuntu/+source/crash/7.2.9-2ubuntu2 . Not
rebuilt on Impish, but would assume the same might happen there.
** Tags added: focal ftbfs groovy hirsute impish
--
You received this bug notification because you are a
** Also affects: linux-firmware (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/1930868
Title:
Package firmware-sof-signed
** Tags added: upgrade-software-version
--
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/1923564
Title:
BlueZ 5.58 release
Status in bluez package in Ubuntu:
New
Bug description:
@kaihengfeng, can you perhaps build a 5.9.xx kernel with:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=d823346876a970522ff9e4d2b323c9b734dcc4de
added for @dacto from comment 25 to test ?
His device gets intel-vbtn SW_TABLET_MODE support enabled based on the
chassis_type 31 is "Convertible", so we expect the intel-vbtn
SW_TABLET_MODE reporting to work there.
There was one other HP model which had a bit of a weird issue, this was
fixed by:
*** This bug is a duplicate of bug 1904294 ***
https://bugs.launchpad.net/bugs/1904294
** This bug has been marked a duplicate of bug 1904294
package linux-firmware 1.157.23 failed to install/upgrade: subprocess
installed post-installation script returned error exit status 1
--
You
@burritojohn, if you are seeing this on an Asus device then you are hit
by a different variant of what is in essence the same bug.
The Asus case is fixed by this upstream commit:
This has been fixed in the upstream 5.4.71 stable series release, so as
soon as the Ubuntu kernels pick up the fixes from that release then this
should be resolved.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
@tjaalton, note the fix which I originally wrote for this causes
regressions on some devices, a follow up fix is necessary, see:
https://lore.kernel.org/linux-i2c/20201014144158.18036-1-hdego...@redhat.com/
https://lore.kernel.org/linux-i2c/20201014144158.18036-2-hdego...@redhat.com/
--
You
The underlying problem is that the file '/usr/share/nvidia/nvidia-
application-profiles-450.80.02-key-documentation' is present in both
packages, so they run into a conflict when attempting to install both.
** Also affects: nvidia-graphics-drivers-450 (Ubuntu)
Importance: Undecided
I just got an email from gkh that both patches have also been added to
the various stable kernel series, including 5.4.x and 5.8.y, so they
should show up in the next stable series release for those kernels.
Thus if the Ubuntu kernel follows the stable series then this will get
fixed through
@handyboy, my fix for this has been merged by Linus for inclusion into
5.9. If one of the Ubuntu devs can add the 2 mentioned fixes to the next
20.04 kernel build then this issue should be resolved/fixed.
--
You received this bug notification because you are a member of Kernel
Packages, which is
For everyone who is seeing this issue with the intel-vbtn driver,
if you do:
cat /sys/class/dmi/id/chassis_type
On your laptop, and the output is NOT "31" or "32" then the
fix, which I linked above, should work for you.
If the output actually is "31" or "32 (which I do not expect),
then please
This should be fixed by this upstream commit, which landed in Linus'
tree a couple of hours ago:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/platform/x86?id=8169bd3e6e193497cab781acddcff8fde5d0c416
Note for the Ubuntu kernel devs: a similar bug was
Public bug reported:
hans@hans-Lenovo-ThinkBook-14-IIL:~$ cat /proc/bus/input/devices
I: Bus=0019 Vendor= Product=0005 Version=
N: Name="Lid Switch"
P: Phys=PNP0C0D/button/input0
S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0D:00/input/input0
U: Uniq=
H: Handlers=event0
B: PR
Gaurav, did you reboot into the patched kernel?
And what is the output of "uname -r" in a terminal (after rebooting),
does that show that you are running the patched kernel now?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
@ferenc-szabo, thank you for figuring out the issue with the _STA
method.
@kaihengfeng, it looks like we are both working on the same issue again
:)
I've written a simple, clean kernel patch fixing this, and I just got
confirmation from the reporter of:
** Tags added: regression-update
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/1893694
Title:
Latest update breaks booting
Status in linux-firmware package in Ubuntu:
New
It was solved, yet I am now on kernel 5.4.0-43 and I am hitting this now
again since a week when using Jetbrains products. Clearly a regression,
how could this 've happened. The linux-image* package changelog is
pretty much worthless to investigate this.
--
You received this bug notification
You still can't edit comments on LP :S?
I am running kernel 5.4.0-42 instead of the earlier mentioned 5.4.0-43
--
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/1872001
Title:
*** This bug is a duplicate of bug 1887623 ***
https://bugs.launchpad.net/bugs/1887623
** This bug has been marked a duplicate of bug 1887623
Atheros QCA9377 WiFi Not detected on Ubuntu 20.04
--
You received this bug notification because you are a member of Kernel
Packages, which is
** Tags added: focal
--
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/1887623
Title:
Atheros QCA9377 WiFi Not detected on Ubuntu 20.04
Status in linux package in Ubuntu:
New
Bug
Thanks for reporting this.
owfs was packaged in Debian (see the attached bug watch) and has been
available in Ubuntu for a while
https://launchpad.net/ubuntu/+source/owfs
** Bug watch added: Debian Bug tracker #606189
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=606189
** Also affects:
Hi All,
We (upstream kernel devs) are currently working with Realtek to get to
the bottom of this, once we know what the exact settings are which need
to be applied we can then add a quirk to the kernel to do this
automatically.
Realtek is asking for people with an affected laptop model to test
** Also affects: nvidia-graphics-drivers-340 (Ubuntu)
Importance: Undecided
Status: New
** Tags added: focal package-conflict
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-435 in Ubuntu.
*** This bug is a duplicate of bug 1873280 ***
https://bugs.launchpad.net/bugs/1873280
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1873280, so it is being marked as such. Please
Ok, good :) Thanks for checking.
I must admit I am not sure what caused the lock in the first place,
though it may have been a check for updates running in the backgorund. I
believe this sometimes happens right after booting, so if it became ok
after waiting a while that might have been it. In
Thanks for reporting.
Based on the error message, this doesn't seem to be directly caused by
firmware-b43-installer. It looks like there's a different apt-get
process currently running, perhaps installing other packages in a
different terminal? Could you check if all other apt-get processes are
Looks like `zfsutils-linux` is part of the source package `zfs-linux`
** Package changed: zfsutils (Ubuntu) => zfs-linux (Ubuntu)
** Tags added: focal
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
#57 this works.
Hard to install on 18.04 though, you need the headers package (linux-
headers-5.3.0-48_5.3.0-48.41_all.deb) from eoan
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Well the "[drm:intel_dsi_vbt_gpio_init [i915]] *ERROR* Failed to own
gpio for panel control" error is gone.
I just noticed you describe the problem as "blank screen with a cursor"
, I should have noticed this before. I assume with a cursor you mean a
mouse cursor (and not a Linux text console
p.s.
There is another issue with 5.5.y and 5.6 kernels on Cherry Trail
hardware, at least with Fedora I'm seeing regular GPU freezes; and
specifically on the T100HAN also spontaneous reboots. I've seen the GPU
freezes on multiple Cherry Trail devices (these require ssh-ing in and
killing
I have a T100HAN in my personal hw collection, so I just booted up a
nightly build of the Fedora 32 workstation livecd on it and that works
fine for me. This nightly build is using a 5.6 kernel.
So the 5.6 kernel can work on this hardware. AFAIK Ubuntu, like Fedora
puts the i915 driver in the
** Bug watch added: Debian Bug tracker #947191
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947191
** Also affects: hwdata (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947191
Importance: Unknown
Status: Unknown
--
You received this bug notification because
>From the original report:
"When the device is under load and more than 1 hardrive is acessed, the
USB enclosure frequently restarts."
So this very much sounds like a hardware problem. UAS allows having
multiple outstanding commands (read/write requests) and thus *actually*
accessing multiple
I've been dealing with this issue for two years now, happens about 30% of the
time when I put it on the dock, after a restart it works fine. Since I don't
have the time or knowledge to help identify this issue, at least I wanted to
share the workaround I recently found:
- Just never dock or
** Tags added: upgrade-software-version
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to iproute2 in Ubuntu.
Matching subscriptions: iproute2
https://bugs.launchpad.net/bugs/1848008
Title:
eoan needs iproute2 v5.3.0
Status in iproute2
hits the bug all
the time, and where it doesn't hit it anymore with the patch.
Thanks, Hans
--
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/1830440
Title:
Xen guest time corrupted after
@Maurizio, could you test a newer Kernel? 5.1 for example to see if it's
already solved, it is in my case.
--
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/1822913
Title:
Kernel 5.0.0-8
@Boris please test kernel 5.1.0-050100rc3-generic (or above) at least
#1822913 was solved with this kernel
--
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/1821564
Title:
b44 Ethernet
problem is solved in kernel 5.1.0-050100rc3-generic
Is it necessary the bisect?
--
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/1822913
Title:
Kernel 5.0.0-8 unable to handle kernel
I just tested Kernel 4.20.17 an it is good. I will do the bisect but I
don't have much time at this moment
--
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/1821564
Title:
b44 Ethernet
I saw in the comments that #1821564 was with kernel 5 it might be a dupe
of it then.
--
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/1822913
Title:
Kernel 5.0.0-8 unable to handle kernel
I cannot run apport-collect because when I have this issue I don't have
wifi connectiom. I will try to connect via cable an do apport-collect,
but It will take some time. Giving that 19.04 with Kernel 5 is almost
ready to be delivered, I will change to confirm anyway.
I'm not sure is a dupe of
forgot to add info about the audio and wifi:
*-multimedia
description: Audio device
product: NM10/ICH7 Family High Definition Audio Controller
vendor: Intel Corporation
physical id: 1b
bus info: pci@:00:1b.0
version:
Public bug reported:
With Kernel 5.0.0-8 I have strange behaivour. I have no wifi and no sound,
typing sudo doesn't work.
kern.log attached, include a boot with kernel 5 and one with 4.19 (which works
ok)
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Tags:
To change this run gnome-tweaks and go to: "Keyboard & Mouse" then under
"Mouse Click Emulation" select "Area" that should give you a right click
at the bottom right area of the touchpad.
Regards,
Hans
--
You received this bug notification because you are a me
Good news (hopefully) it looks like we finally have found a fix which is
not an ugly hack / does not disable runtime pm for other devices which
will hopefully fix this.
Kai-Heng Feng, can you build a kernel with this patch:
https://patchwork.kernel.org/patch/10597519/
Added for reporters of
As Bas already told: we have a production site with 2 (identical) servers,
configured as loadbalancer.
At first the network problems occurred at the primary loadbalancer, but after
rebooting that one the problems migrated to the second server.
Only after rebooting both servers with the previous
Hi, patch author here. You can ask BTRFS maintainers by mailing to the
linux-bt...@vger.kernel.org mailing list. Also, the patch author email
address is in the commit itself, for quick questions. :-)
I just stumbled across this ubuntu issue while being bored and reading
I haven't tried with other DE, since it is an old computer I have only
tried lxde. I could easily try with openbox alone, installing another DE
could be a little longer. Is there one better to test with?
--
You received this bug notification because you are a member of Kernel
Packages, which is
Update to #138:
My problem seems to be related to Bug #1752053 and Bug #1773113. And for
me now everything more or less works again by using this workaround from
Bug #1752053 posting #123:
-snip
I found a silly workaround (after trying many many other suggestions / driver
I just realize that it only happen after login (lxde, lubuntu) in
lightdm this does not happen.
--
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/1773718
Title:
mouse pointer disappear
Hi,
I've seen this problem since I install linux in this computer (2 years ago),
but my workaround was to use the nvidia propietary driver. Now that nvidia stop
developing the 304 driver, I will have to use nouveau.
I installed 4.17.0-041700rc7-generic and the problem still is there. It might
I have a variant of this problem that I can not find anywhere else:
I have the same problem of black screen (white cursor not blinking in
the left upper corner) when I do a lock screen!
Suspend problem is also present. Computer goes down correctly after
pressing suspend, but when it is supposed
I didn't knew which log to attach. Already done what you asked for. I'm
also attaching lspci -vnvn log
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
** Attachment added: "lspci -vnv"
Public bug reported:
With nouveau driver (doesn't happened with propietary nvidia) after
screen switch off because of power management, the mouse pointer
disappear. Mouse still works, you can hover, select, click, but the
pointer is invisible.
In a dual monitor configuration, this only happened
David Perez Millan,
Please run gnome-tweaks and go to: "Keyboard & Mouse" then under "Mouse
Click Emulation" select "Area" that should give you a right click at the
bottom right area of the touchpad.
Regards,
Hans
--
You received this bug notification
Olivier, thank you excellent work. I've mailed the upstream developers
and the author of the patch of which the older version fixes things.
Kai-Heng, can you perhaps do a test Ubuntu kernel build with the patch
from comment 158, then other users with different (but similar) model
laptops can test
please? (I need your email address) then I will start an email
discussion about this with you in the Cc.
Regards,
Hans
--
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/1728244
Title
What would also be helpful is an acpidump of your Thomson X6 as well the
output of:
ls -l /sys/bus/i2c/devices
--
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/1728244
Title:
Touchpad
Olivier Fock,
Thanks for your work on this, that is some excellent detective work.
Also good to know that the "incomplete report" errors are also happening
in a working setup.
The buttons starting to work after you updating the drivers/hid
directory is expected, I have done several fixes to the
And a dmesg directly after boot with the non-working 4.14-rc7 + another
one with the working 4.14-rc8 based one would also be good.
--
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/1728244
Can people with this problem please boot with:
i2c_designware_core.dyndbg=+p i2c-hid.debug=1
Added to their kernel commandline and then directly after boot run:
dmesg > dmesg.log
And attach the generated dmesg.log file here?
--
You received this bug notification because you are a member of
led) failed to
install/upgrade: subprocess new pre-installation script returned error
exit status 128
Status in linux package in Ubuntu:
Confirmed
Bug description:
sorry, but Iḿ not very versed in ubuntu
hans@hans-NUC:~$
hans@hans-NUC:~$ cat/proc/version>version.log
bash: ca
Public bug reported:
sorry, but Iḿ not very versed in ubuntu
hans@hans-NUC:~$
hans@hans-NUC:~$ cat/proc/version>version.log
bash: cat/proc/version: No such file or directory
hans@hans-NUC:~$ sudo lspci-vnvn.log
[sudo] password for hans:
sudo: lspci-vnvn.log: command not found
hans@hans-
** Tags added: bionic manpage
--
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/1767971
Title:
No such man page: kernel_lockdown.7
Status in linux package in Ubuntu:
New
Bug
1 - 100 of 378 matches
Mail list logo
