I enabled -proposed on jammy, and updated pcscd to 1.9.5-3ubuntu1. I
verified that the socket is now enabled:
$ systemctl status pcscd.socket
● pcscd.socket - PC/SC Smart Card Daemon Activation Socket
Loaded: loaded (/lib/systemd/system/pcscd.socket; enabled; vendor preset:
enabled)
Act
** Description changed:
[ Impact ]
The pscc-lite package provides an open source implementation of PC/SC,
the de-facto standard to interface Personal Computers with Smart
Cards/Readers.
This bug is in the upstream debian packaging, and results in the
pcscd.socket being disabled a
** Description changed:
- Ubuntu Mate 22.04 with the latest updates.
- Problem is present with internal smart-card reader and also external usb
smart-card reader.
+ [ Impact ]
- eid-viewer sees no card reader,but When i do:
+ The pscc-lite package provides an open source implementation of PC/S
** Summary changed:
- pcscd 1.9.5-3 do not start automatically, only manual
+ pcscd.socket is disabled after installation
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pcsc-lite in Ubuntu.
https://bugs.launchpad.net/bugs/1971984
Title
I ran into this bug earlier this week while trying to setup my new
Nitrokey HSM2 (https://docs.nitrokey.com/hsm/linux/) on a Thinkpad
running 22.04 LTS.
I've confirmed that the upstream commit from 1.9.9-2 fixes the problem,
and am uploading this as a patch.
** Patch added: "Backported packaging
** Changed in: network-manager (Ubuntu)
Assignee: Tony Espy (awe) => (unassigned)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1407928
Title:
[phone] Does not a
** Changed in: network-manager (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1781597
Title:
[SRU] WoWLAN settings are not supported
Re-opened, as there's some interest from OEMs in seeing NM teaming
support land in 18.04.
** Description changed:
Availability:
The package is available in universe, built on all architectures.
Rationale:
- The package is a new (Build-)Depends for network-manager, for network device
bon
My point is that we shouldn't release these patches as an SRU without
being able to reproduce the bugs that the patches claim to fix first.
Otherwise we risk introducing additional regressions.
So if we want to consider an SRU for NM with one or more of Aaron's
patches, then yes we need to go thro
There's no evidence (ie. syslogs, package versions, output of wpa_cli)
provided which is a basis for re-opening the bug.
Also, please point us to the *exact* patch that is supposed to fix the
problem.
--
You received this bug notification because you are a member of Desktop
Packages, which is su
This bug was marked FixReleased based on the upload of network-manager
1.2.6-0ubuntu0.16.04.1 to xenial updates and the comments from a many
people that the issue was resolved.
Recently there were two comments (#96 and #97) that claim that the bug
still exists. Comment #96 doesn't even list which
@Kevin
NetworkManager already has code to monitor system signals related to
suspend/resume, so no adding additional scripts to /usr/lib/systemd
/system-sleep isn't the answer.
@Dan
Different bug... this bug is caused by NetworkManager's WiFi scanning
logic stalling due to a race condition. You
Updated the Status to "FixReleased" as it's not possible to do this
anymore on the latest 16.04 LTS release with NetworkManager 1.2.x, as
guest users no longer have sufficient permission to add new connections.
Retrofitting this to the version of NM in 14.04 might be a challenging as the
version
** Changed in: network-manager (Ubuntu)
Status: Triaged => Won't Fix
** Changed in: network-manager (Ubuntu)
Status: Won't Fix => Fix Released
** Changed in: network-manager (Ubuntu)
Status: Fix Released => Incomplete
--
You received this bug notification because you are a
Ugh, and then I wake my Thinkpad 410s just now, and I hit the bug on the
201st cycle. ;(-
Guess I'll go back to dropping the patch again from 1.2.6 and see how
many cycles I can run on it.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
@taiebot65
Thanks. I'll take a look.
Regarding this bug, it turns out that when I was testing my version of
NM with the dropped 'ScanDone' patch (wifi-Signal-on-the-wifi-
device...), I'd been doing so on top of the newly re-based 1.2.6, and it
turns out there was an actual fix in 1.2.6 which see
** Changed in: oem-priority/xenial
Status: New => Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1585863
Title:
WiFi malfunction after suspend & resume stress
I've reproduced this on a Thinkpad 410s running 16.04 LTS. The version
of network-manager I used is the latest from xenial-updates:
1.2.2-0ubuntu0.16.04.3.
A few comments:
1) The fwts s3 test uses a low-level API to exercise suspend/resume.
I've been working with the fwts maintainer on an extens
Just moved this to Incomplete, as it's been posited that the fix for bug
#1104476 resolves the issue.
If anyone can confirm that this is still broken, we can investigate
further.
** Changed in: network-manager (Ubuntu)
Status: Triaged => Incomplete
--
You received this bug notification b
@Alfonso
Let's put this on the agenda for this weeks' net/telephony meeting.
I'm not sure I'm comfortable with releasing your workaround just yet as
it introduces latency when the APs are properly configured for roaming.
--
You received this bug notification because you are a member of Desktop
** Changed in: network-manager (Ubuntu)
Assignee: Tony Espy (awe) => (unassigned)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager-pptp in Ubuntu.
https://bugs.launchpad.net/bugs/1551823
Title:
PPTP connection d
New => Fix Committed
** Changed in: network-manager (Ubuntu)
Status: Fix Committed => Confirmed
** Changed in: network-manager (Ubuntu RTM)
Importance: Undecided => High
** Changed in: network-manager (Ubuntu RTM)
Assignee: (unassigned) => Tony Espy (awe)
** Changed in: n
The fix is currently in silo 005, and was just marked 'Lander Approved'.
The version containing the fix will be 1.2.2-0ubuntu1~xenial3, and
should hopefully land in the next few days.
** Changed in: network-manager (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug n
** Changed in: network-manager (Ubuntu)
Status: Confirmed => In Progress
** Changed in: indicator-network (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
http
-config (Ubuntu)
Status: New => In Progress
** Changed in: network-manager (Ubuntu)
Status: In Progress => Invalid
** Changed in: lxc-android-config (Ubuntu)
Assignee: (unassigned) => Tony Espy (awe)
--
You received this bug notification because you are a member of Desk
So... a long time ago, when Ubuntu Touch was first being developed, we
hit a bug with certain rild implementations that would configure the
routing table when a data call was established, and this caused problems
with NM's routing logic.
The workaround was the creation of a NM dispatcher script c
** Also affects: network-manager (Ubuntu)
Importance: Undecided
Status: New
** Changed in: network-manager (Ubuntu)
Assignee: (unassigned) => Tony Espy (awe)
** Changed in: phablet-tools (Ubuntu)
Status: Confirmed => Invalid
** Changed in: network-manager (
** Changed in: network-manager (Ubuntu)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1597681
Title:
[CTA] Enable WAPI support
Status
I just updated bug #1593686 ( WPA-PSK limit introduced in OTA11 ) with
the root cause which confirms Pete's theory about timeouts.
That said, *if* a user had successfully connected to an AP prior to the
update to OTA11. This *shouldn't* have caused issues, as the psk would
already have been prese
I just confirmed that this is a regression is caused by the final
deprecation of dbus-glib in NM 1.2x, and it's replacement by gdbus. As
part of this work, the code which requests secrets from a secret-agent,
now uses code generated from the introspection XML to make the actual
DBus method call.
** Changed in: ubuntu-system-settings (Ubuntu)
Status: Confirmed => Invalid
** Changed in: canonical-devices-system-image
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ub
@Andrea
Can you provide the info requested on comment #25 too?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1580146
Title:
[touch] Internet connection stops working while W
@Andrea
There are two tests I'd like you to run for me.
First, let's verify the baseline by flashing OTA10 ( pre-NM 1.1.93
landing ) on a spare krillin, and then set the WiFi connection to the
opposite as earlier suggested, this time setting ipv4.method to ignore.
This will validate that IPv6 con
** Changed in: network-manager (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1565717
Title:
No connection after returning
** Changed in: network-manager (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1579098
Title:
[touch] Mobile data connectio
** Attachment added: "Screenshot of Hotspot setup dialog"
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1594938/+attachment/4688157/+files/hotspot-spinning.png
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-m
** Attachment added: "indicator-network log file from arale after start failed"
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1594938/+attachment/4688158/+files/indicator-network.log
** Also affects: canonical-devices-system-image
Importance: Undecided
Status: New
-
Public bug reported:
Although the hotspot logic was vastly improved in OTA11, there are still
intermittent issues with enabling hotspot on arale.
On a freshly flashed phone running rc-proposed / 356, when I first
attempt to setup a hotspot, when I click the "Start" button, the spinner
shows up an
** Changed in: network-manager (Ubuntu)
Status: Confirmed => In Progress
** Changed in: canonical-devices-system-image
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubun
** Changed in: network-manager (Ubuntu)
Status: Incomplete => In Progress
** Changed in: network-manager (Ubuntu)
Assignee: (unassigned) => Tony Espy (awe)
** Changed in: network-manager (Ubuntu)
Importance: Undecided => High
--
You received this bug notification becaus
OK, so there are two low-level problems:
1. InProgress error returned by SetProperty('Active',true) call to ofono
for a gprs-context.
Alfonso's first syslog shows that this can happen, but I'm not sure
exactly how to reproduce. NM would've had to start activation, then
Attached bounced down and
@Pat
The reason I asked was that two of the three scenarios listed by Alfonso
in the bug involved a crash or restart of NetworkManager, and the
resulting state was that the mobile data connection gets stuck trying to
activate an already active ( or activating ) connection.
I wasn't sure if he was
I'm able to reproduce this on arale ( rc-proposed, 334 ) by either
toggling cellular technology ( 2/3g -> 2g only, and back ), or by
putting the device into a faraday cage.
This is partially a regression in 1.1.93 ( we dropped a related patch ),
and partially a day-one problem.
I have what looks
@Andrea
Can you try adding the following setting to the NetworkManager
connection file for "Canonical-2.4GHz-g" in /etc/NetworkManager/system-
connections:
[ipv6]
method=ignore
"[ipv6]" should already be there, so just add "method=ignore", and
remove any other settings under "ipv6".
Restart the
So from @Andrea's latest pastebin:
- NM shows both modem and wlan0 as connected
- syslog shows one DHCP renewal period
- a do-add-ip4-address error is logged, however the IP address is still
configured ( ip addr show confirms this ); need to investigate whether
the error log message is correc
@Alfsonso
One more note, although comment #2 isn't a valid scenario, it does
trigger the same behavior.
The root cause of the bug is that the current NM wwan plugin doesn't
properly handle already activated contexts.
** Changed in: network-manager (Ubuntu)
Status: Confirmed => In Progress
@Alfonso
The scenario in comment #2 isn't valid. That said, I am able to
reproduce by killing NetworkManager, so I agree this is a valid bug that
needs to be fixed.
@Pat
As Alfonso pointed out, your problem is different, as there's no active
context, nor does NetworkManager appear stuck. Could
** Changed in: network-manager (Ubuntu)
Assignee: (unassigned) => Tony Espy (awe)
** Changed in: network-manager (Ubuntu)
Importance: Undecided => Critical
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-mana
@Andrea
Let's try and work together to get the description of the bug (
including steps to reproduce ) accurate.
The initial description was network "stops working" when WiFi is "still
connected". This implies the network was actually connected and working
before the bug occurred, true? It'd al
@Andrea
One last thing... did you check for crash files?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1580146
Title:
Internet connection stops working while WiFi is still c
@Andrea
Re: comment #3, please review bug #1533508, to see if your hitting the
same. If not, please file a new bug and include output from
/usr/share/ofono/scripts/list-modems and list-contexts.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscri
@Andrea
Finally, you might also want to consider "forgetting" some of the saved
access points on your device. NetworkManager shows a seriously long
list of WiFi connections.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manage
@Andrea
Let's keep this bug specific to the original problem described.
Does this problem only occur at the office?
Can you reproduce it reliably? If so, how long after you initially
connect does it take to manifest itself?
>From what you provided in your initial pastebin, both the indicator a
** Changed in: network-manager (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1580146
Title:
Internet connection stops working while
** Changed in: network-manager (Ubuntu)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1579915
Title:
network-manager 1.2 uses more
Two things I noticed while testing the powersave fix from silo-77:
1) On mako ( rc-proposed / 434 ), iwconfig doesn't report anything at
all for powersave. This may be a driver limitation.
2) On frieza ( rc-proposed / 101 ), the powersave period is set to 0,
which may be a less than ideal value
I've confirmed that the default powersave patch included in xenial is
wrong, as it patches libnm-util which is deprecated, as opposed to
patching the new libnm0.
I've update the version of NM in the silo for VPN with an updated patch
which restores WiFi powersave by default.
https://launchpad.net
Note, it looks like the problem is that the original patch fixes up the
libnm-util version of nm-settings-wireless.c which has been deprecated.
Instead the libnm-core version of nm-settings-wireless.c needs to be
updated. I'm testing this now for a touch build and will report back
here if it works
To be clear from discussions with Andrea, the network is accessible, but
it appears that DNS isn't working correctly. He's able to ping an IPv4
address, but trying to ping a hostname results in an immediate'unknown
host' being displayed.
--
You received this bug notification because you are a me
So NM 1.1.93-0ubuntu1 includes the patch default_powersave_on.patch,
which is pretty simple, it just modifies the NMSettingWireless code to
default powersave to 1:
===
--- a/libnm-util/nm-setting-wireless.c
+++ b/libnm-util/nm-setting
@Amr
Thanks for the pointer. I just added a comment to bug #1557026
regarding the xenial powersave regression, and it applies to Touch as
well.
I'm working on an updated patch for Touch, and then will see about
SRU'ing for xenial as soon as possible.
--
You received this bug notification becau
Just flashed OTA10 and 'iwconfig wlan0' when associated to an AP shows:
Power Management period:2
phablet@ubuntu-phablet:~$ system-image-cli -i
current build number: 32
device name: krillin
channel: ubuntu-touch/stable/bq-aquaris.en
--
You received this bug notification because you are a memb
@Amr
Yes, this could be related to bug #1557026. I checked, and we're
including default_powersave_on.patch, however it doesn't appear to be
working properly in NM 1.1.93.
I just confirmed on krillin ( rc-proposed / 325 ) that even though the
device is associated to an AP, iwconfig show 'Power Ma
@Selene
Are the devices associated to WiFi access points when the testing is
performed?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1579915
Title:
network-manager 1.2 uses
@Ken
I see the same thing on krillin running rc-proposed / #320.
That said, looks like we made a poor choice of properties to use as
'IP4Address' was marked as deprecated as far back as NM 0.9:
https://developer.gnome.org/NetworkManager/0.9/spec.html#org.freedesktop.NetworkManager.Device
Looks
I see this on mako running stable / #30 plus the a test version of
NetworkManager 1.1.93 that I'm using for the VPN bug #1579222. When I
go to the access point details page in system settings, I also see the
following message logged to the upstart log file application-legacy-
ubuntu-system-setting
@Jonas
Nope. NM is responsible for monitoring the 'Preferred' properties of
all the APN/gprs_contexts for a particular SIM *and* enforcing that the
first APN/context found with 'Preferred=true' is activated. NM never
changes the value of 'Preferred'.
--
You received this bug notification bec
@Avishay
Can you try removing the 'gateway-ping-timeout' line from one of your
connections and retry? From the error you originally reported, it looks
like the Plasma networking code is mangling this value and NM
complains...
--
You received this bug notification because you are a member of Des
One other note, I tried installing Kubuntu, but wasn't able to do so
with today's daily image. This makes debugging a bit difficult...
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/
@Avishay
Were you connected to WiFi before you rebooted, or were you trying to
connect to a network from the network menu for the first time?
Does the failure occur for *any* networks you're trying to connect to
via WiFi?
I don't have Kubuntu installed on any of my machines, but I was able to
br
** Summary changed:
- Fail to connect to wifi after a recent update
+ [Kubuntu] Fail to connect to wifi after a recent update
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1569
Re-tested krillin with stable #27 ( OTA-8 ), and got the exact same
behavior. Also went much further back to stable #21 ( almost a year-to-
the-date ) and same behavior, ATT WAP is chosen yet again.
The only difference between our devices is that you have a non-working
T-Mobile SIM present, and I
** Changed in: network-manager (Ubuntu)
Status: New => Incomplete
** Changed in: ofono (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net
OK, strike the last bit about nameservers being added vs. replaced. I
was the one who misunderstood how the VPN IPv4v6 dialogs work, and thus
wasn't finding the "User this connection only for the resources on this
network" checkbox. Once I did, the VPN DNS works as expected.
--
You received th
I've re-based Mathieu's branch on rc1:
lp:~awe/network-manager/update-1.2
I've pushed a version to my PPA:
https://launchpad.net/~awe/+archive/ubuntu/ppa
The original issue ( no DNS ) seen with the Canonical VPN seems to have
been resolved, although the behavior seems to be slightly different t
Just tested with krillin ( rc/bq-aquaris.en #48 ) plus a single AT&T
SIM. Made sure to clear all of the 'Preferred' flags and rebooted. To
do this, as root:
# stop network-manager
# stop ofono
# cd /var/lib/ofono//
# vi gprs
( change any 'Preferred=true' -> 'Preferred=false' )
# reboot
I see
NM 1.1.93 ( 1.2-rc1 ) was just released.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1552424
Title:
[FFE] NetworkManager 1.2-beta
Status in network-manager package in Ubun
The openvpn failure is actually a symptom of a larger problem which can
affect *any* DNS server ( ie. not just servers associated with a VPN )
that includes a domain. The updated gdbus patch mentioned in the
previous comment adds the DBus parameters to the dnsmasq SetServersEx
method in the wrong
The openvpn failure to setup DNS is due to an error returned to the DBus
call to dnsmasq:
dnsmasq update failed:
GDBus.Error:org.freedesktop.DBus.Error.InvalidArgs: Invalid IP address:
'buildd': bad address
So, pretty sure this is a bug in the patch [1] that adds DBus support to
dnsmasq, and that
@Bryan
Thanks for the reply.
I actually did a fresh xenial install on my Thinkpad 410s this
afternoon, installed the packages from Mathieu's PPA, and then
configured the Canonical VPN. I'm able to start it, but once active,
I'm not also not able to access the network. This is most likely a bug
@Bryan
Thanks for the test results.
Let's not open any new bugs for now, as Mathieu was able to reproduce
the Canonical VPN issue and noticed that the problem is probably related
to the dnsmasq DBus changes that were made as part of the upgrade to
NM1.2. I'll take a look at this later today and
It should be noted that we just landed a new version of NetworkManager
into rc-proposed ( 0.9.10.0-4ubuntu15.1.10 ) which fixed a couple of
race conditions that existed in the interactions between NM and
wpa_supplicant that could potentially cause the phone to stop scanning
on WiFi after a disconne
@Julia
Thanks for the testing report!
So when you say, "you gave it 10/15 minutes of time to reconnect on its
own". I assume during this time you were assuming that the device would
re-connect automatically when the screen was off?
Then you say you woke the phone, and it was offline until you s
@Jean-Baptiste
This was reported quite awhile back. Is this behavior still
reproducible with OTA9?
** Changed in: network-manager (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-m
@Vincent, @Yanik,
Please refer to comments #8 and #11. This is not a bug and has been
closed.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1489154
Title:
NetworkManager do
@Matthew
That's correct.
The E4.5 is not able to use data on one SIM and voice on the other SIM
simultaneously. This is a limitation of a dual-standby modem design.
That said, if the phone is registered on one of it's SIMs using 3G or
greater, it *can* use data and voice simultaneously on the
** Also affects: canonical-devices-system-image
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/615239
Title:
Every Wi-Fi disconnect
We could, although the problem is actually related to any data usage,
not just hotspot...
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1536195
Title:
Can't receive calls and
@tuxboson
Your welcome... the semantics of dual-SIM modems are tricky, and
frankly this isn't fully discussed in the phone's user manual. That
said, I ended up fixing one of our telephony test plans, as there was
simple note about dual-standy modems that didn't give a full description
either!
R
@tuxboson
The modem in the BQ Aquaris E4.5 is dual-standby, which means it's not
able to use both SIMs simultaneously.
If you're using one of the SIMs for data, and data is actually being
transferred on the connection, incoming calls will be blocked on the
other SIM. As you discovered, you can m
** Changed in: ofono (Ubuntu)
Status: New => Incomplete
** Changed in: network-manager (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net
@Michael
Does the WiFi re-connect delay and/or failure occur in both places?
When it actually does connect, is the delay the same in both places? Is
the delay *always* ~9m???
Is "eduroam" one of the APs you're actually using at work or home? I
ask, as I notice that the security settings indicat
@Dubstar_04
Can you please let us know what device you're using? Also, in addition
to the information requested in comment #4, could you please include
details about what software you're running on the device? Please
either grab a screenshot of Settings::About This Phone::OS, or the
output from
@Jean-Baptiste
Do you end up with the same network-menu as shown in screenshot included
with comment #1?
The network icon shown on the menu indicates that WiFi is off, and no
mobile data connection.
If you can reproduce again, can you please include the output of these
commands:
% /usr/share/of
@Allan
Can you please re-test with a current image?
I just tried this on my arale ( rc-proposed/meizu.en #216 ) which was
updated two days ago. I can't recreate.
I verified that WiFi was enabled, then enabled FlightMode, verifying
that WiFi had been disabled before rebooting.
I ran this scenar
@Pete
Flight mode persistence is actually handled by urfkill.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1512831
Title:
Flight mode: Wi-Fi re-enabled upon reboot
Status
@Lorn
It was designed this way in order to make the switching from WiFi back
to the mobile data connection fast. Re-working this fundamental design
decision IMHOP would be a significant amount of work, and it's not like
our current queue of NM related is empty...
I think in the short term if we
ged in: qtbase-opensource-src (Ubuntu RTM)
Status: New => Fix Released
** Changed in: qtbase-opensource-src (Ubuntu RTM)
Assignee: (unassigned) => Tony Espy (awe)
** Changed in: qtbase-opensource-src (Ubuntu RTM)
Importance: Undecided => High
** Changed in: qtbase-opensou
@Selene
Just wanted to confirm that we don't need any more investigation re:
your comment #131 ( I think that may be the largest comment # I've seen
in a LP bug ), as your latest update to bug #1524133 indicated that
you'd isolated the problem to a SIM with an expired data plan?
@Timo
We should
So the latest changes in Lorn's signals6 patch can be summarized as:
1) remove QNetworkManagerEngine::requestUpdate (), which is a public
method which can trigger a WiFi scan request to NM.
This method doesn't appear to be called internally by the bearer plugin,
so if we think extra WiFi scans ar
1 - 100 of 520 matches
Mail list logo
