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",
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
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
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
Touch seeded packages, which is
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
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
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
Touch seeded packages, which is
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
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
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, 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
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?
--
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
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
[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 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
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"
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-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
Touch seeded packages, which is subscribed to
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
@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
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
Touch seeded packages, which is subscribed to apt in 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
** Description changed:
- When testing WCN3980 with 20.04 and UC20, WCN3980 is not able connect to
- an AP.
+ [ Impact ]
+ When testing Qualcomm qcs410 with WCN3980 with 20.04 and UC20, WCN3980 is not
able connect to an AP.
- I tried a different libnl3 from BSP and found that WCN3980 can
I made a test build (debdiff attached) and tried it on the target
device. This version works correctly.
** Patch added: "libnl3_3.4.0-1ubuntu1.debdiff"
https://bugs.launchpad.net/ubuntu/+source/libnl3/+bug/1998765/+attachment/5634558/+files/libnl3_3.4.0-1ubuntu1.debdiff
--
You received
Public bug reported:
When testing WCN3980 with 20.04 and UC20, WCN3980 is not able connect to
an AP.
I tried a different libnl3 from BSP and found that WCN3980 can work
correctly. The version used in BSP is 3.5.0.
I bisected the commits from 3.4.0 to 3.5.0 and found this commit[1] is the root
** Tags added: orignate-from-lp1998578
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libnl3 in Ubuntu.
https://bugs.launchpad.net/bugs/1998765
Title:
libnl3 3.4.0 doesn't work with WCN3980
Status in libnl3 package in
this issue was discovered in an OEM project.
** Package changed: libnl3 (Ubuntu) => oem-priority
** Changed in: oem-priority
Assignee: (unassigned) => Robert Liu (robertliu)
** Also affects: libnl3 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notifi
I installed the updated version on the platform which needs this patch.
After updating the packages, the platform can scan and connect to a WiFi
network correctly.
I also tried other amd64, armhf and arm64 platforms which don't require
the patch originally and their wifi device still work after
Hi Oliver,
Thanks for the explanation and the PR.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/2012563
Title:
unsupported mount options: 'nofail', 'nostrictatime',
Hi Oliver,
Could you please add the options listed in comment #1 as well? They are
used by FunctionFS. Thank you.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/2012563
I also observed this issue on my laptop with 20.04.
I created a patched version in this PPA[1] and it seems the issue is resolved
with the patch mentioned in comment #5.
If anyone can confirm the patched version does help, I'll submit the patch for
SRU.
[1]
33 matches
Mail list logo
