** Changed in: kunpeng920/ubuntu-19.10
Status: Triaged => In Progress
** Changed in: kunpeng920/ubuntu-19.10
Assignee: (unassigned) => Ike Panhc (ikepanhc)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https
** Changed in: kunpeng920/ubuntu-19.04
Assignee: (unassigned) => Ike Panhc (ikepanhc)
** Changed in: kunpeng920/ubuntu-18.04
Assignee: (unassigned) => Ike Panhc (ikepanhc)
** Changed in: kunpeng920/ubuntu-18.04-hwe
Assignee: (unassigned) => Ike Panhc (ikepanhc)
** Changed in: linu
Tries booting with the chain disconnected from the dock, and as expected
- the system boots correctly with the dock attached and built-in USB
devices present, after which plugging the USB cable in works well.
The problem seems to only be when external USB devices are connected to
the dock.
Here's
*** This bug is a duplicate of bug 1854798 ***
https://bugs.launchpad.net/bugs/1854798
I will mark this one as a dup for bug 1854798, please feel free to revert the
status if you think this is incorrect.
Thanks
** This bug has been marked a duplicate of bug 1854798
Synaptics s3203 touchpa
Just had the "unknown event type 15" error happen again, with the
lp1766076 kernel and current firmware:
---8<---
Dec 25 11:19:34 vesho kernel: xhci_hcd :0e:00.0: ERROR unknown event type 15
Dec 25 11:19:39 vesho kernel: xhci_hcd :0e:00.0: xHCI host not responding
to stop endpoint command
tested but it's still stucking the usb hub. After the undock I need to
run the reset of the USB hub to have it working.
Undock:
[ 84.219765] usb 2-1: USB disconnect, device number 2
[ 84.225638] [drm] DM_MST: stopping TM on aconnector: da0f527b [id:
78]
[ 84.225876] [drm] DM_MST: D
I have the patch tested on Power9 node "baltar" with Disco kernel (5.0.0-37).
It's still failing with this stime01 test.
startup='Wed Dec 25 10:25:31 2019'
tst_test.c:1217: INFO: Timeout per run is 0h 05m 00s
stime_var.h:45: INFO: Testing libc stime()
stime01.c:46: INFO: pt.tv_sec: 1577269561
Public bug reported:
Laptop : Lenovo G50
I ran below command to check that touchpad package is available or not, and
couldn't find the synaptic touchpad package.
Command : cat /proc/bus/input/devices
ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: linux-image-5.3.0-24-generic 5.3.0-24.26
P
This change was made by a bot.
** 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/1857536
Title:
Touch pad is not working - Len
This problem has been known for 5 years and has not yet been resolved
https://github.com/raspberrypi/linux/issues/688
** Bug watch added: github.com/raspberrypi/linux/issues #688
https://github.com/raspberrypi/linux/issues/688
--
You received this bug notification because you are a member of
Public bug reported:
SRU justification:
[Impact]
The current kernel didn't support multitouch for LG I2C touchscreen.
[Fix]
Add LG I2C id to hid-multitouch to support it.
[Test]
Verified on hardware with a positive result.
[Regression Potential]
Low.
Add new I2C id with positive verification.
This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:
apport-collect 1857541
and then change the status of the bug to 'Confirmed'.
If, due to the nature
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => AaronMa (mapengyu)
--
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/1857541
Title:
[SRU][B/OEM-B/OEM-OSP1/D/E/F] Add LG I2C tou
** Tags added: oem-priority originate-from-1852693 sutton
--
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/1857541
Title:
[SRU][B/OEM-B/OEM-OSP1/D/E/F] Add LG I2C touchscreen multitouch
Thank you, Martin, for providing this simple but clever and VERY
effective workaround! I can confirm that it works.
I'd like to add, that you have to execute this script with 'bash fix_sound.sh'.
'sh fix_sound.sh' doesn't work because debian and ubuntu use dash as
non-interactive shell and dash c
Hello,
I suffer from the same issue, I also have HP Zbook 15 G6 with Ubuntu 19.10. I
installed the latest kernel v5.5-rc3 through ukuu utility. Now, I do not have
any sound (nor mic, nor speakers).
Here is the output from dmesg:
```
[0.00] Linux version 5.5.0-050500rc3-generic (kernel@ka
Ok so in fact the inconsistency is due to "parted" that will try to
probe devices iff the given block device return informations from
stat(), regardless if the block device is available or not.
Seems like the only trigger/criteria is the stat() return. Since the
loop device stat doesn't clear/rese
so 2 things come to my mind right now
Does the kernel (loop driver) do the right thing by not clear/reset the
loop device' stats after the umount/detached operation ?
and/or
Does parted need to smarter and not only based is detection only on
stat() ?
Let's circle back on Jan 2020.
** Also
so 2 things come to my mind right now
Does the kernel (loop driver) do the right thing by not clear/reset the
loop device' stats after the umount/detached operation ?
and/or
Does parted need to be smarter and not only based is detection on stat()
to assume if its a legit device or not to be
Hi all,
can someone tell me how to fix this issue, its getting annoying. Is it
going to be new update on this, im not sure about using the ppa. Is
there any other safety way to be patched ?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
** Changed in: dmidecode (Debian)
Status: New => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to dmidecode in Ubuntu.
https://bugs.launchpad.net/bugs/1821632
Title:
dmidecode causing system crash
Status in dmidecode
@ivanak
Bug reports aren't for support, for support options please refer to
https://discourse.ubuntu.com/t/finding-help/709
For using proposed (comment #13 and others) see
https://help.ubuntu.com/community/Repositories/Ubuntu and
https://wiki.ubuntu.com/Testing/EnableProposed
--
You received th
Bug reports aren't for support, for support options please refer to
https://discourse.ubuntu.com/t/finding-help/709
I believe kernel linux-image-4.15.0-73-generic (currently in proposed)
will move to 'main' on January 5, 2020.
For enabling proposed (suggested in comment #13 and others in the bug
Hi Ivanak,
while awaiting new kernel, browsing and testing with kernel 5.x, is working in
dell xps 9333,
here is reference how to enable
https://wiki.ubuntu.com/Kernel/LTSEnablementStack
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to l
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete => Expired
--
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
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete => Expired
--
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
*** This bug is a duplicate of bug 1854798 ***
https://bugs.launchpad.net/bugs/1854798
Hello Pratik,
please try this tool: https://github.com/Cypresslin/alt_my_grub.git
git clone https://github.com/Cypresslin/alt_my_grub.git
cd alt_my_grub
./alt_my_grub
And select the kernel that you want to
This error was reproduced under kernel v5.5-rc3
--
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/1857418
Title:
KDE Panel disappears after screen lock
Status in linux package in Ubuntu:
This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:
apport-collect 1853995
and then change the status of the bug to 'Confirmed'.
If, due to the nature
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Eoan)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Focal)
Importance: Und
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Disco)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Focal)
Importance: Un
This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:
apport-collect 1853992
and then change the status of the bug to 'Confirmed'.
If, due to the nature
Patch has been sent for review
https://lists.ubuntu.com/archives/kernel-team/2019-December/106550.html
** Changed in: linux (Ubuntu Eoan)
Status: Incomplete => In Progress
** Changed in: linux (Ubuntu Eoan)
Assignee: (unassigned) => Ike Panhc (ikepanhc)
** Changed in: linux (Ubuntu
** Changed in: ubuntu-kernel-tests
Status: In Progress => 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/1825778
Title:
False positive test result in run_afpackettest
Patch has been sent for review
https://lists.ubuntu.com/archives/kernel-team/2019-December/106550.html
** Changed in: linux (Ubuntu Focal)
Status: Incomplete => Fix Released
** Changed in: kunpeng920/ubuntu-18.04
Status: New => In Progress
** Changed in: kunpeng920/ubuntu-18.04
Hi, didn't find something directly related from above WMI events. Could
you try following to kernel parameters sets separately:
1. "module_blacklist=wmi": this will disable wmi completely
2. "wmi.debug_event=1 wmi.debug_dump_wdg=1": this will enable wmi debug
info.
--
You received this bug noti
Patch has been sent for review
** Changed in: linux (Ubuntu Disco)
Status: Triaged => In Progress
** Changed in: linux (Ubuntu Bionic)
Status: Triaged => In Progress
** Changed in: kunpeng920/ubuntu-19.04
Status: Triaged => In Progress
** Changed in: kunpeng920/ubuntu-18.04
https://lists.ubuntu.com/archives/kernel-team/2019-December/106550.html
** Description changed:
+ [Impact]
+ Some SAS devices is gone when recovering
+
+ [Test Case]
+ No known test case, stress test on SAS deivce.
+
+ [Fix]
+ e74006edd0d4 scsi: hisi_sas: Fix the conflict between device gone an
Patch has been sent for review
** Changed in: linux (Ubuntu Bionic)
Status: Triaged => In Progress
** Changed in: linux (Ubuntu Bionic)
Assignee: (unassigned) => Ike Panhc (ikepanhc)
** Changed in: linux (Ubuntu Disco)
Status: Triaged => In Progress
** Changed in: linux (Ubun
https://lists.ubuntu.com/archives/kernel-team/2019-December/106550.html
--
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/1855952
Title:
scsi: hisi_sas: Check sas_port before using it
Stat
** Description changed:
+ [Impact]
+ I/O error on blank Samsung SSD
+
+ [Test Case]
+ mkfs.ext4 on SSDs generates no I/O error
+
+ [Fix]
+ 435a05cf8c00 scsi: hisi_sas: Assign NCQ tag for all NCQ commands
+
+ [Regression Risk]
+ Patch restricted to hisi_sas driver.
+
+
"[Steps to Reproduce]
** Description changed:
+ [Impact]
+ Potential NULL-pointer dereference.
+
+ [Test Case]
+ No known test case, but the issue is clear from code reading.
+
+ [Fix]
+ 445ee2de112a scsi: hisi_sas: Fix out of bound at debug_I_T_nexus_reset()
+
+ [Regression Risk]
+ Patch restricted to hisi_sas driv
42 matches
Mail list logo
