I have verified the package in the noble-proposed and confirmed that there's no
"/EndEntire" message.
I used Ubuntu Core 24 to verify the package, becuase uc24 is using
"chainloader" which had this issue.
verification step:
1. prepare an UC24 inistance
2. upload the grubx64.efi to the system
3.
Hi Mate and Julian,
Is there a timeline for landing the fix in noble? Thank you.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2073634
Title:
[SRU] Enable suppression of /EndEntire message
To mana
** Description changed:
- Many Ubuntu Core customers require a boot sequence that displays a
+ [ Impact ]
+
+ * Many Ubuntu Core customers require a boot sequence that displays a
custom splash image up until ubuntu-frame loads. Unfortunately, GRUB
- often (if not always) interrupts this proces
** Also affects: oem-priority
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2073634
Title:
Enable suppression of /EndEntire message
To manage notificatio
** Also affects: oem-priority
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2075579
Title:
On Ubuntu Core 20+, grub shows /EndEntire when booting
To mana
Public bug reported:
With the GRUB (2.06-2ubuntu14.2) of the latest pc gadget snap (rev. 145)
for UC20, it shows "/EndEntire" whenn booting. This behavior will clear
the boot logo. But GRUB (2.04-1ubuntu44.2) of pc gadget snap (rev. 132)
doesn't have this issue. A customer has splash screen requir
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] https://launchpad.net/~robertliu/+arc
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] https://launchpad.net/~robertliu/+arc
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', 'la
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
Ti
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 up
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 up
** Also affects: oem-priority
Importance: Undecided
Status: New
** Changed in: oem-priority
Importance: Undecided => High
** Tags added: originate-from-1998894
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to cloud-in
** 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 work
** 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 work
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
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
** 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 Ubu
** Tags added: orignate-from-lp1998578
--
You received this bug notification because you are a member of Desktop
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 Ubuntu:
New
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 this
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 this
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
c
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
c
demark. In order to deal with this matter
better, it's necessary to send email to you and confirm whether this company is
your business partner in China? Best Regards
Robert Liu Service & Operations Manager
China Registry (Head Office)
Tel: +86-2161918696
Fax: +86-2161918697
Mob: +8
** 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 t
Dear Manager,
(Please forward this to your CEO, because this is urgent. Thanks)
This is Robert Liu, Senior Manager of a Network Service Company which is the
domain name registration center in Shanghai, China. On October 26, 2020, we
received an application from Runbang Holdings Ltd requested
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 sub
rsal Machine, Progress in
>> Biophysics and Molecular Biology, 2017, Vol. 131, pp. 251-260.
>> https://www.ncbi.nlm.nih.gov/pubmed/28919132
>>
>> Marchal B. Religion, science and theology, similarity and differences,
>> Dialogo Journal, 2018, Vol. 5, pp. 205-
walls. These are some of the
elementary form of Buddha’s ability to “observe”.
Sent from my iPad
> On Aug 16, 2020, at 10:03 AM, John Clark wrote:
>
>
>> On Sun, Aug 16, 2020 at 9:55 AM Beixiao Robert Liu
>> wrote:
>>
>> > Therefore, if you reject the
. I’m not preaching Buddhism. The
problem is that you risk dismissing a useful perspective prematurely, from a
purely objective and neutral standpoint.
Sent from my iPad
> On Aug 16, 2020, at 9:31 AM, John Clark wrote:
>
>
>
>
>> On Sun, Aug 16, 2020 at 9:24 AM Beixiao
at 10:36:40 PM UTC-6, Beixiao Robert Liu wrote:
>> Well, if the inquiry here concerns consciousness, then the question of
>> whether a human should trust the AI, or whether the AI has the capacity to
>> be trusted by a human, ought to be part of the inquiry, right? The movie
ote:
>
>
>
>
>> On Saturday, August 15, 2020 at 7:54:35 PM UTC-6, Beixiao Robert Liu wrote:
>> It’s available on YouTube. You could rent it for as little as $4, as long as
>> you finish viewing it within 2 days once your start playing.
>>
>> Thanks for recommending
It’s available on YouTube. You could rent it for as little as $4, as long as
you finish viewing it within 2 days once your start playing.
Thanks for recommending it. I just viewed it. My wife said that it’s stupid for
the boy to trust the AI girl, Ava, so he got what he deserved.
Sent from my
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.
https://bugs.launchpad.net
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 Ubuntu.
** 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.
https://bugs.launchpad.net/b
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
busy
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
busy
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.
https://bugs.launchpad.net/bugs/180133
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 to
** Changed in: linux (Ubuntu)
Status: Incomplete => 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/1808768
Title:
Initrd of pc-kernel snap contains out-of-date packages
** 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 no
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 resiz
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 resiz
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
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 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 devic
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 foun
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 foun
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 devic
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 te
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 te
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 n
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 n
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 Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1802260
Title:
Please
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 modu
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 in
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 in
@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 y
@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 y
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 serve
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 serve
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.
https://bug
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 ap
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 Ub
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 Ub
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"
https://bugs.launchpad.net/oem-priority/+bug/1766542/+attachment/5141168/+files/var-log-installer-16_04
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"
https://bugs.launchpad.net/oem-priority/+bug/1766542/+attachment/5141168/+files/var-log-installer-16_04
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 apt-
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 user
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: ve
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 Ubunt
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 fw
[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"
https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1735134/+attachment/50
[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"
https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1735134/+attachment/50
[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"
https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1735134/+attachment/50
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
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
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 full-up
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 full-up
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 full-up
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 back
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 back
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 back
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
Bugs,
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 Desktop
Pack
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
Touch
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?
--
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?
--
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, 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 because
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 you
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 no
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 subscribe
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 notificati
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
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
1 - 100 of 163 matches
Mail list logo
