** Also affects: oem-priority
Importance: Undecided
Status: New
** Changed in: oem-priority
Importance: Undecided => High
** Changed in: oem-priority
Status: New => Confirmed
** Changed in: oem-priority
Assignee: (unassigned) => Soar Huang (soarhuang)
--
You received
Hi Paride,
I verified the crash issue does exist in core20 snap on the edge channel. To be
precise, the revisions I tried are 823 for amd64 and 826 for armhf.
So I think we can close this bug.
Thank you!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Hi @mwhudson,
Thanks for your help. Do you want me to file bugs and send patches for
SRU?
Also, do you have an ETA that these updates will be landed in core20
snap? Because CE team has some deliveries are blocked by this issue.
Currently we use a patched core20 snap as temporary workaround.
--
Opened corresponding PRs on github.
1. subiquity - https://github.com/CanonicalLtd/subiquity/pull/810
2. probert - https://github.com/canonical/probert/pull/93
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
a better way is: add the mapping for CAN to _compute_type() in
probert/network.py as well as add 'can' and '???' to
NETDEV_IGNORED_IFACE_TYPES in subiquity/subiquitycore/models/network.py
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Also affects: subiquity (Ubuntu)
Importance: Undecided
Status: New
** Also affects: probert (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
On Ubuntu 20.04, I found 'busybox hwclock -s' failed with "invalid
argument" error, but hwclock of util-linux works well.
On bugzilla of busybox, there's someone reported the same/similar issue:
https://bugs.busybox.net/show_bug.cgi?id=12756
$ apt policy busybox-static
I met the issue when installing packages from a private PPA of
Launchpad. Hope this would be helpful to reproduce the issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1801338
Title:
apt fails
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1808768
Title:
Initrd of pc-kernel snap contains out-of-date packages
To manage
Public bug reported:
The build script does not install package updates during generate the
pc-kernel snap.
I met this bug #1783810 when I was verify my Ubuntu Core 18 image on KVM.
The system stuck at resizing the writable partition. the resize script of
initrd called sgdisk to achieve the
With the proposed kernel, my system passed a 30-run stress.
1. Enable the -proposed repository
2. Install the proposed kernel and reboot
3. uname -r
4.15.0-43-generic
4. sudo modprobe mei_wdt
5. for s in $(seq 30); do sudo rtcwake -v -m mem -s 15; sleep 15; done
6. verify the result is success
I tried mainline kernel 4.20-rc2, 4.18, 4.17, 4.16 and 4.15. They all passed a
50 run test.
To validate when the issue is introduced, I installed several Ubuntu kernel
packages and address the issue/regression happens between 4.15.0-34 and
4.15.0-36.
Finished the kernel bisect and probably
I commented out this patch of 876dcb and cannot reproduce the issue
afterward.
diff --git a/drivers/base/dd.c b/drivers/base/dd.c
index 2c964f5..37c0105 100644
--- a/drivers/base/dd.c
+++ b/drivers/base/dd.c
@@ -868,6 +868,13 @@ static void __device_release_driver(struct device *dev,
struct
Public bug reported:
Problem description:
System randomly hangs during suspend when mei_wdt is loaded.
Platform:
Intel Dawson Canyon I5 (NUC7i5DNHE) and I7 (NUC7i7DNHE)
Test procedure:
1. Install Ubuntu 18.04 and do apt full-upgrade
2. Enable mei_wdt:
$ sudo modprobe mei_wdt
3. Do system S3
applied this patch against lp:~ubuntu-kernel/ubuntu/+source/linux-
snap/+git/bionic then the issue is gone.
** Patch added: "add-nvme-and-usbhid.patch"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1802260/+attachment/5210613/+files/add-nvme-and-usbhid.patch
--
You received this bug
The fix would be similar with this bug #1794279
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1802260
Title:
Please include
Public bug reported:
When trying Ubuntu Core with the pc-kernel snap, the system showed
'cannot find writable partition'. The system was stopped at the initrd
stage and didn't accept any input.
My system is using a NVMe disk and it seems the pc-kernel doesn't
provide the related modules in its
@Julian,
Here is the archive of logs. Sorry I forgot to attach it before.
** Attachment added: "var-log-installer-18_04.tgz"
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1766542/+attachment/5143739/+files/var-log-installer-18_04.tgz
--
You received this bug notification because
Hi @Steve,
IMO, it would be great that the period is less than 30 seconds in total.
In this case, the updating operation is always failed. Users should know that
the Internet is not available before setting a proxy server. They may expect to
have a minimum timeout or pre-configure the proxy
Image: ubuntu-18.04-desktop-amd64.iso
Significant blockings -
"Retrieving file 1 of 3", 90 seconds
"Retrieving file 1 of 1", 32 seconds
The behavior is different from 16.04.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Here is how I setup the environment:
1. prepare a broadband gateway. This time I use LEDE with VirtualBox. I can
upload the VM image if necessary.
2. add a firewall rule on the gateway: all http/https traffic from LAN port
will be redirected to a IP which is not used by any machine.
3. install
Image: ubuntu-16.04.4-desktop-amd64.iso
Significant blockings -
"Retrieving file 1 of 93", 30 seconds
"Retrieving file 1 of 31", 3 minutes
** Attachment added: "var-log-installer-16_04.tgz"
Tried the 18.04 daily build (http://cdimage.ubuntu.com/ubuntu/daily-
live/20180424/bionic-desktop-amd64.iso), and it has the same issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1766542
Title:
Public bug reported:
When the machine is behind a proxy server, the installation will block
for a while (several minutes) to retrieve the package lists. The
timeouts are too long and makes user feels the machine may have some
problems.
The symptom is similar with bug #14599, but it seems the
Public bug reported:
Description:
oprofile failed to recognize the cpu type of platforms Dawson Cayon NUC7i3DNH,
June Canyon-NUC7PJYH and June Canyon-NUC7CJYH.
Root Cause:
For JC(GLK-NUC), v4.13 kernel doesn't support GLK-NUC. The result was expected!
For DC(KBL-NUC), v4.13 support KBL, but
The proposed version 0.8.3-0ubuntu2 has been verified. It does fix the
bug and no regression is found with my hardware.
SKU: Dell Thin client
Old version (0.7.0-0ubuntu4.3): fwupd has a open fd (/dev/bus/usb/001/007)
New version (0.8.3-0ubuntu2): fwupd doesn't have a open fd.
** Tags removed:
Hi @Brian,
The proposed version (0.8.3) has been verified. It does fix the bug as well.
SKU: Dell Thin client
Old version (0.7.0): fwupd has a open fd (/dev/bus/usb/001/007)
New version (0.8.3): fwupd doesn't have a open fd.
--
You received this bug notification because you are a member of
Hi @Brian,
I have updated the bug description. If there is something missing, please let
me know. Thanks.
** Description changed:
- In fwupd, a few of USB devices are not closed when there are some
- failures of operations. This issue will cause fwupd has some orphan USB
- nodes inside during
[hide the comment #12, update the DEP-3 headers inside the patch]
Hi @Łukasz
the comments were addressed. and re-upload the debdiff.
Thanks.
** Patch added: "gobi-set-dell-modules-as-forbidden-devices.debdiff"
Hi @Łukasz
the comments were addressed. and re-upload the debdiff.
Thanks.
** Patch added: "gobi-set-dell-modules-as-forbidden-devices.debdiff"
https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1735134/+attachment/5022490/+files/gobi-set-dell-modules-as-forbidden-devices.debdiff
--
Hi @Łukasz,
I tried to run the acc test manually, and it didn't show any error.
The environment I used is vagrant + xenial/amd64 image (not fully upgrade all
of the packages) + ppa mentioned in #18 + related packages/tools.
May I have your opinion what could be the differences?
I also did
Hi @Łukasz,
I had tried to pull the modem-manager/libqmi/libmbim of artful, just modify
some version number of dependency packages, and built those packages
successfully. Sorry, I don't remember if I touched anything about
modemmanager-qt and if they work correctly with modemmanager-qt. The
I have tried ModemManager 1.6 series mentioned in comment #18, and
Sierra MC7455, Sierra MC 7430 and Telit HE910D work fine with this
version. The signal strength issue (bug #1735134) is not observed with
this version.
--
You received this bug notification because you are a member of Ubuntu
there is a bug #1725190 which is going to backport ModemManager 1.6
series to Xenial. Yesterday, I tested the proposed packages. It resolves
the issue as well. If the release is coming soon, then I think it's not
necessary to apply the fix. If not, could you please update the 1.4
series first?
--
Current version, registered, but not connected
output of mmcli -m 0
** Attachment added: "mmcli-info-init-orig.txt"
https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1735134/+attachment/5016106/+files/mmcli-info-init-orig.txt
--
You received this bug notification because you are a
Current version, connected
output of mmcli -m 0
signal strength is 0
** Attachment added: "mmcli-info-connected-orig.txt"
https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1735134/+attachment/5016107/+files/mmcli-info-connected-orig.txt
--
You received this bug notification
Current version
log of ModemManager
** Attachment added: "mm-orig.log"
https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1735134/+attachment/5016108/+files/mm-orig.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
debdiff to forbid the Dell Wireless DW5818/5819 modules
** Patch added: "gobi-set-dell-modules-as-forbidden-devices.debdiff"
https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1735134/+attachment/5016110/+files/gobi-set-dell-modules-as-forbidden-devices.debdiff
--
You received this
Patched version, registered, but not connected
output of mmcli -m 0
** Attachment added: "mmcli-info-init-patched.txt"
https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1735134/+attachment/5016111/+files/mmcli-info-init-patched.txt
--
You received this bug notification because
Patched version, connected
output of mmcli -m 0
Signal strength is not 0
** Attachment added: "mmcli-info-connected-patched.txt"
https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1735134/+attachment/5016113/+files/mmcli-info-connected-patched.txt
--
You received this bug
Patch to forbid the Dell Wireless DW5818/5819 modules
** Patch added: "gobi-set-dell-modules-as-forbidden-devices.patch"
https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1735134/+attachment/5016109/+files/gobi-set-dell-modules-as-forbidden-devices.patch
--
You received this bug
Patched version
log of ModemManager
** Attachment added: "mm-patched.log"
https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1735134/+attachment/5016115/+files/mm-patched.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Public bug reported:
Since linux-4.4.0-98, the kernel additionally load gcserial driver for
Dell Wireless DW5818/5819. The reason behind it is to support firmware
switching and upgrading. However, the change makes ModemManager to use
Gobi plugin for this two modules. With Gobi plugin, the modules
Try the kernel mentioned in the comment #2 on the Ubuntu desktop, the
HDMI audio works normally and there is no i915 or HDMI related warning
message in dmesg
** Attachment added: "dmesg.log"
** Attachment added: "dmesg.log"
https://bugs.launchpad.net/ubuntu/+source/linux-joule/+bug/1700686/+attachment/4903893/+files/dmesg.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1700686
Public bug reported:
Attached is the patch that fixes memory leaks in the mtp-server.
This issue is original reported by Intel, and Intel also provides a patch.
NOTE that the name “Ubuntu touch” has been changed to “Intel Devices”in
the patch.
** Affects: mtp (Ubuntu)
Importance: Undecided
Hi @Ogra,
I cannot get the correct result on a all-snap system. Is this expected?
admin@caracalla:~$ lsb_release
Traceback (most recent call last):
File "/usr/bin/lsb_release", line 95, in
main()
File "/usr/bin/lsb_release", line 59, in main
distinfo =
Hi @Ogra,
I cannot get the correct result on a all-snap system. Is this expected?
$ lsb_release
Traceback (most recent call last):
File "/usr/bin/lsb_release", line 95, in
main()
File "/usr/bin/lsb_release", line 59, in main
distinfo = lsb_release.get_distro_information()
File
for Yakkety
** Patch added: "fwupd_0.7.2-0ubuntu2.debdiff"
https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/1642812/+attachment/4783972/+files/fwupd_0.7.2-0ubuntu2.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
for Xenial
** Patch added: "fwupd_0.7.0-0ubuntu4.4.debdiff"
https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/1642812/+attachment/4783973/+files/fwupd_0.7.0-0ubuntu4.4.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
for Zesty
** Patch added: "fwupd_0.7.4-3.debdiff"
https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/1642812/+attachment/4783971/+files/fwupd_0.7.4-3.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
update the patch to fix the compiling error.
** Patch added: "Close-usb-devices-before-error-returns.patch"
https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/1642812/+attachment/4781812/+files/Close-usb-devices-before-error-returns.patch
--
You received this bug notification because you
The upstream PR has been merged.
Could we have this patch also land in Ubuntu, please?
** Patch added: "Close-usb-devices-before-error-returns.patch"
https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/1642812/+attachment/4781307/+files/Close-usb-devices-before-error-returns.patch
--
You
Hi @Michael,
I have confirmed that on the edge channel, this issue does not exist.
Do you have the schedule when this update will be uploaded to the stable
channel?
** Description changed:
I am verifying backport-iwlwifi driver release/LinuxCore18 on Intel
Joule platform. Console-conf
Public bug reported:
I am verifying backport-iwlwifi driver release/LinuxCore18 on Intel
Joule platform. Console-conf crashes at the beginning of configuration.
The lastest call is fcntl.ioctl(sock.fileno(), SIOCGIWESSID, request)
and the error is "OSError: [Errno 95] Operation not supported".
Public bug reported:
In fwupd, a few of USB devices are not closed when there are some
failures of operations. This issue will cause fwupd has some orphan USB
nodes inside during fwupd is running. A orphan USB node might introduce
memory leak and block some runtime power features as well.
I
This package does fix the issue.
There is no warning anymore, and I could connect to a wifi network correctly.
$ dmesg|grep -i iwl
[ 12.296938] iwlwifi :02:00.0: enabling device ( -> 0002)
[ 12.348568] iwlwifi :02:00.0: loaded firmware version 17.352738.0
op_mode iwlmvm
[
I tried to specify the udev rule more precisely, i.e. only power up a host
controller.
Is there anybody could give it a try?
#/lib/udev/rules.d/50-bluetooth-hci-auto-poweron.rules
# Set bluetooth power up
ACTION=="add", SUBSYSTEM=="bluetooth", KERNEL=="hci[0-9]*",
ENV{DEVTYPE}=="host",
58 matches
Mail list logo
