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
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
** 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
** 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
** 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
@Alfonso
Updated version of the script in comment #5 looks good to me...
--
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/1454625
Title:
Cannot send MMS messages with combined
Ubuntu RTM)
Importance: Undecided => High
** Changed in: network-manager (Ubuntu RTM)
Assignee: (unassigned) => Tony Espy (awe)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launch
Ubuntu RTM)
Importance: Undecided => Critical
** Changed in: network-manager (Ubuntu RTM)
Assignee: (unassigned) => Tony Espy (awe)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launch
** Changed in: canonical-devices-system-image
Status: Confirmed => 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/1435776
Title:
NM does not activate ofon
** Changed in: canonical-devices-system-image
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/1450790
Title:
Phone with an APN speci
Ubuntu RTM)
Status: New => In Progress
** Changed in: network-manager (Ubuntu RTM)
Importance: Undecided => High
** Changed in: network-manager (Ubuntu RTM)
Assignee: (unassigned) => Tony Espy (awe)
--
You received this bug notification because you are a member of Desktop
er (Ubuntu)
Importance: Undecided
Assignee: Tony Espy (awe)
Status: Confirmed
** Changed in: network-manager (Ubuntu)
Assignee: (unassigned) => Tony Espy (awe)
** Changed in: network-manager (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because
@Will
Thanks for your comment. I was just able to reproduce this using a
devel image from two weeks ago ( ubuntu-touch/rc-proposed/ubuntu #171 ).
I'm pretty sure this is an unrelated problem. Could you please file a
new bug against ofono? Also please add if you had one or two SIMs
installed?
@Will
It appears that this may be related to an enhancement/fix which auto-
unlocks the phone when FlightMode was toggled and a PIN-locked SIM was
inserted. This works well ( at least with one PIN-locked SIM
installed... I didn't try two ).
--
You received this bug notification because you are
So regarding the original bug, there are two scenarios that can happen
when FlightMode is enabled on arale. These same scenarios could also
occur on other platforms as well, which would explain why @Ricardo was
able to reproduce on mako.
1. When FlightMode is enabled, often the first event NM see
** Changed in: network-manager (Ubuntu)
Importance: Undecided => Critical
** Changed in: network-manager (Ubuntu)
Assignee: (unassigned) => Tony Espy (awe)
** Also affects: network-manager (Ubuntu RTM)
Importance: Undecided
Status: New
** Changed in: network-manager (
** Attachment added: "Victor's list-contexts output"
https://bugs.launchpad.net/ubuntu-rtm/+source/network-manager/+bug/1461593/+attachment/4409481/+files/list-contexts.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manag
** Attachment added: "Victor's list-modems output"
https://bugs.launchpad.net/ubuntu-rtm/+source/network-manager/+bug/1461593/+attachment/4409480/+files/list-modems.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager i
@Victor
Could you please reproduce and attach the system directly ( ie. not via
past.ubuntu.com )?
** Changed in: network-manager (Ubuntu RTM)
Status: New => Incomplete
** Changed in: network-manager (Ubuntu RTM)
Assignee: Tony Espy (awe) => Víctor R. Ruiz (vrruiz)
--
You re
Victor's list-modems output shows the modem registered to Yoigo (
mcc/mnc: 214/04 ), and the RadioSettings TechnologyPreference property
set to "umts" ( 3g ). None of the contexts are active, which means
NetworkManager has probably disabled the connection due to the
autoconnect_retry limit being h
Thanks for the log @Victor.
So the smoking gun is:
Jun 4 14:26:41 ubuntu-phablet NetworkManager[1408]: Disabling
autoconnect for connection '/214040113340577/context2'.
There's only one of these in the log. When this happens, NetworkManager
has seen a disconnect for the modem, but hasn't yet
** Also affects: ofono (Ubuntu RTM)
Importance: Undecided
Status: New
** Changed in: ofono (Ubuntu RTM)
Status: New => In Progress
** Changed in: ofono (Ubuntu RTM)
Importance: Undecided => High
** Changed in: ofono (Ubuntu RTM)
Assignee: (unassigned) => Alfonso Sanchez-
At a meeting this week, we decided that all of the components that may
activate and/or use a context, should set the 'Preferred' flag for the
context if it's successfully activated and/or used ( eg. a context is
used by ofono for the INITIAL_ATTACH APN request; if this succeeds,
ofono will set the
** Changed in: network-manager (Ubuntu)
Assignee: (unassigned) => Tony Espy (awe)
--
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/1461999
Title:
Crash changing SIM s
Moved back to Incomplete until we better understand the bug.
** 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-manager in Ubuntu.
https://bugs.launchpad
Thanks for the feedback Jamie!
A couple of comments in return...
1. NetworkManager polkit allows full access to sudo: I assume you meant
that the decision was taken *before* we had proper polkit support on the
phone?
2. urfkill polkit - allows active seat to call Block: The policy also
allows B
@Jean-Baptiste
Can you reproduce this reliably?
Also, it sounds like your steps are:
1. Boot the phone w/WiFi enabled, and in range of a remembered access point
2. Disable WiFi
3. Verify the mobile data connection comes up
4. After several minutes, the data connection will drop; sometimes it's
Updated status of the ofono (Ubuntu) task to Invalid. The network-
manager task had already gone from Incomplete to Expired, but there
doesn't seem to be any way for me to mark the ofono (Ubuntu) task
Expired.
@Dave
If you can re-create still, please feel free to re-open.
** Changed in: ofono (
So to summarize, I see the following problems being reported here:
1. vivid/krillin: when mobile data is active, and radio technology
preference is changed, mobile data connection is not always restored.
2. vivid/mako: disable wifi, mobile data connection takes >= 6m to be
restored. Note, when
Also, running mako/vivid-devel/#122, I was able to re-create Jonas'
original bug.
I see a delay of 5-6m between changing radio technology and mobile data
being re-established. I see it going from 2g -> 3g and visa versa.
Looking at the log, when the technology changes, the NM SCPlugin-Ofono
run
** Summary changed:
- NM fails to create a cellular data connection for a unacceptably long time
+ After radio technology is changed, mobile-data takes ~5m to re-connect
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in
Changed the summary to include "[krillin]" as the report doesn't include
any mention of other devices.
** Summary changed:
- Data connection doesn't switch from Wifi to Cellular (3G/4G)
+ [krillin] Data connection doesn't switch from Wifi to Cellular (3G/4G)
--
You received this bug notificatio
Based upon tvoss' findings in comment #13, I'm closing out the network-
manager tasks as Invalid. If anyone disagrees, feel free to re-open,
but please provide updated logs and/or steps to reproduce if doing so.
** Changed in: network-manager (Ubuntu)
Assignee: Ricardo Mendoza (ricmm) => (un
** Changed in: network-manager (Ubuntu Utopic)
Status: Confirmed => Incomplete
** Changed in: network-manager (Ubuntu Vivid)
Status: Triaged => Incomplete
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in U
I just made both NM tasks Incomplete as:
* there's no device information, nor reference to branch or image
number. In fact, it's hard to tell that this is a "touch" bug.
* there are no "steps to reproduce"
* comment #11 says NM is failing to send a proper signal, yet the
signal name is not m
OK, I'll take a dive into the network-test-session logs later today.
>From your description in comment #9, it sounds like this is the same
issue as bug #1418077, where something causes the mobile data connection
to drop and NM takes ~5m to restore the connection. If the logs concur
with my theory
So what seems to be happening, is that the radio technology switch
causes the modem to unregister from the current carrier, and attempt to
re-register using the new tech preference ( eg. umts, lte, gsm, ... ).
This will cause the ofono ConnectionManager 'Attached' property to
return FALSE until the
So it looks you indeed have hit #1418077.
This is pretty obvious by looking in the attached nmlog file, and search
for connection '/208150102671184/context1'. You'll see it get disabled
at 18:41:24 after a bunch of failed attempts ( modem-no-carrier ). It
gets successfully auto-activated again i
I need some confirmation from Mathieu before I change this bug to
Confirmed and re-title it...
--
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/1425987
Title:
Cellular data conn
** Attachment added: "NM log messages from network-test-session_20150603_102306"
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1425987/+attachment/4341813/+files/nmlog-lp1425987.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is s
So confirmed that adding a case for
NM_DEVICE_STATE_REASON_MODEM_NO_CARRIER in device_state_changed ( nm-
device-modem.c ), causes the connection to be blocked from auto-
connecting.
I still see the initial retries decrement log message in
device_state_changed ( nm-policy.c ), I mentioned this is
** Attachment added: "session log from network-test-session_20150603_102306"
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1425987/+attachment/4341834/+files/network-test-session.log
--
You received this bug notification because you are a member of Desktop
Packages, which is
** Summary changed:
- After radio technology is changed, mobile-data takes ~5m to re-connect
+ After connection drops, mobile-data takes ~5m to re-connect
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https:/
*** This bug is a duplicate of bug 1418077 ***
https://bugs.launchpad.net/bugs/1418077
** This bug has been marked a duplicate of bug 1418077
After connection drops, mobile-data takes ~5m to re-connect
--
You received this bug notification because you are a member of Desktop
Packages, whi
** Description changed:
+ If the mobile data connection drops due to signal loss or modem reset (
+ eg. changing radio technology, setting 3g slot, ... ), there's a delay
+ of 5m before NetworkManager attempts to re-connect.
+
+ The original bug pertained to changing the radio technology ( which
Public bug reported:
NetworkManager incorrectly uses GPRS contexts from any SIM directory
instead of limiting the GPRS contexts used to those the currently active
SIM.
This bug was discovered on krillin while trying to determine whether bug
#1425987 was a duplicate of bug #1418077.
I've attached
*** This bug is a duplicate of bug 1418077 ***
https://bugs.launchpad.net/bugs/1418077
I created bug #1431471 to track the wrong SIM problem mentioned in
comment #11.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in
** Attachment added: "NM log messages from network-test-session_20150603_102306"
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1431471/+attachment/4343088/+files/nmlog-lp1425987.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is s
** Attachment added: "session log from network-test-session_20150603_102306"
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1431471/+attachment/4343089/+files/network-test-session.log
** Also affects: canonical-devices-system-image
Importance: Undecided
Status: New
-
*** This bug is a duplicate of bug 1427205 ***
https://bugs.launchpad.net/bugs/1427205
** This bug has been marked a duplicate of bug 1427205
indicator shows (dozens of) out of range access points
--
You received this bug notification because you are a member of Desktop
Packages, which is
** Changed in: indicator-network (Ubuntu)
Importance: Low => High
** Also affects: canonical-devices-system-image
Importance: Undecided
Status: New
** Changed in: canonical-devices-system-image
Status: New => In Progress
--
You received this bug notification because you are
** This bug is no longer a duplicate of bug 1427205
indicator shows (dozens of) out of range access points
--
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/1425172
Title:
Net
Changed to Incomplete, as there's insufficient detail ( device, image
type/#, steps to reproduce, ... ).
** 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-man
Maguro is a deprecated platform.
** Changed in: network-manager (Ubuntu)
Status: New => Won't Fix
--
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/1215528
Title:
Network
@Jamie
Apparently this bug list hasn't been triaged in a long time...
Can you still reproduce this on current RTM or vivid-devel images?
** Changed in: network-manager (Ubuntu)
Status: New => Incomplete
** Changed in: network-manager (Ubuntu)
Assignee: (unassigned) => Jamie Strandbo
Changed to Incomplete, as this was reported against an ancient version
of Touch, and I'm pretty sure a fix was released for this. If it can be
reproduced on a current image RTM or vivid-devel, please add an updated
description.
** Changed in: network-manager (Ubuntu)
Status: New => Incompl
** Changed in: network-manager (Ubuntu)
Status: New => Incomplete
** Changed in: network-manager (Ubuntu)
Assignee: (unassigned) => Tony Espy (awe)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in
ofono was actually changed to allow GPRS contexts with empty
AccessPointNames to be used for data connections. Changing this to
Invalid.
** Changed in: network-manager (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Desktop
Packages, whic
er (Ubuntu)
Status: New => Confirmed
** Changed in: network-manager (Ubuntu)
Assignee: (unassigned) => Tony Espy (awe)
--
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/bug
** Also affects: network-manager (Ubuntu RTM)
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/1410113
Title:
[krillin] Data connecti
** Tags added: connectivity
--
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 auto-switch to available, known WiFi
Status in the base for Ubuntu
@Alfonso
I changed the NM task to Incomplete, as I'm not sure NM is still
involved. The original NM/ofono patches actually would toggle the
ConnectionManager's 'Powered' attribute, however this code was removed,
so I think this can be considered 'FixReleased'.
** Changed in: network-manager (Ubu
@Jonas
There's really not enough information in your bug report for us to
reproduce it.
Can you please add your device and image ( RTM? vivid-devel?, # )
details?
What device are you using to create a hotspot? What type of security
did you specify? What band of WiFi was used ( 2.4? 5? )?
** C
@costales
There's insufficient detail in your bug report for us to reproduce this
problem.
Can you please add your device, and image details ( RTM? vivid-devel?
image #? ).
** Changed in: network-manager (Ubuntu)
Status: New => Incomplete
** Changed in: network-manager (Ubuntu)
Assi
** Changed in: network-manager (Ubuntu)
Assignee: (unassigned) => Tony Espy (awe)
** Also affects: network-manager (Ubuntu RTM)
Importance: Undecided
Status: New
** Also affects: canonical-devices-system-image
Importance: Undecided
Status: New
** Changed in: netw
** Tags added: connectivity
** Changed in: network-manager (Ubuntu)
Assignee: (unassigned) => Tony Espy (awe)
--
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/1435776
Ti
** Tags added: connectivity
--
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/1436427
Title:
Turning off WiFi doesn't set a route after the modem connects data
Status in the bas
** Tags added: connectivity
--
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/1307981
Title:
[touch] randomly messed up routing
Status in lxc-android-config package in Ubuntu:
Updated status to WontFix, this should've been reported to the OEM. The
original bug report is > 5 years old as well...
** Changed in: network-manager (Ubuntu)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed
Updated status to FixReleased; confirmed by Alfonso on Ubuntu RTM.
** Changed in: network-manager (Ubuntu)
Status: Incomplete => 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.
** Changed in: network-manager (Ubuntu RTM)
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/1436427
Title:
Turning off WiFi doesn't set a route
I'm removing the 'connectivity' tag, as this bug was specifically for
the issue where the routing table ends up with multiple conflicting
routes, and thus this is a slightly different problem than the current
problems seen with RTM ( empty routing table when switching from WiFi to
mobile data ). I
** Changed in: network-manager (Ubuntu)
Assignee: Tony Espy (awe) => Alfonso Sanchez-Beato (alfonsosanchezbeato)
--
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/1435
This sounds similar to bug #1410113, which is a more generic bug. I'm
not going to mark this a duplicate however as it has a reproducible
scenario.
Also confirmed this bug for RTM, as I reproduced it on the third try. I
verified that there was a mobile data connection and that it worked (
ie. I
This may be the same as bug #1436427. Since that bug has a specific
scenario ( which has been Confirmed for RTM ), I'm going to leave these
as separate bugs.
I'm pretty sure another scenario is when a user walks out of range of a
WiFi access point, NM doesn't seem to failover to the mobile data
Also, due to the use of hybris to disable/enable WiFi on krillin, the
WiFi device's numeric component is incremented every time WiFi is power
cycled ( eg. wlan0, wlan1, wlan2, ... ).
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network
This doesn't seem to be easily reproducible, which strengthens the
theory that this is a race condition between rild and Network Manager.
When the mobile data connection is active, and WiFi connected, the main
routing table looks like this:
# ip route show
default via dev wlanX proto static
dev
** Description changed:
I just switched off WiFi in order to test if the device switches
successfully to a mobile data connection. After disabling WiFi the
indicator showed "H" in no time. So it would seem all is fine. I opened
the browser and no data went through.
Here's the output o
** Changed in: nuntium (Ubuntu)
Status: New => Confirmed
** Changed in: network-manager (Ubuntu)
Status: New => Confirmed
** Changed in: network-manager (Ubuntu)
Assignee: (unassigned) => Tony Espy (awe)
--
You received this bug notification because you are a
I lowered the priority to High, as this problem is hard to reproduce.
Also, the one time I was able to reproduce it, the connection was re-
established after some time.
** Changed in: network-manager (Ubuntu)
Importance: Critical => High
** Changed in: network-manager (Ubuntu RTM)
Importan
@MIchael
When this happened, did you wait and see whether or not the connection
came back on it's own?
If not, the next time you see it happen, can you check periodically for
a few minutes to see if the connection is restored. There's a 5m
internal timeout in NetworkManager that may be involved.
@Michael
Thanks for the feedback.
I'd like keep this bug specifically for the problem that occurs when
WiFi is toggled off ( as per the bug description and summary ). The
problem when going out of range of the access point may be something
completely different, and is being addressed in bug #14
The attached script is a simple stress test that's run on the phone. It
toggles WiFi on, sleeps for 10 seconds, then toggles WiFi off and checks
for an empty routing table, and then sleeps for another 10 seconds. I
currently has a hard-coded loop count.
The script enables/disables WiFi by toggli
** Changed in: network-manager (Ubuntu)
Assignee: Alfonso Sanchez-Beato (alfonsosanchezbeato) => Tony Espy (awe)
--
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/1435
OK, after a quick look... my gut tells me that this error is caused by
the fact that the 'giffgaff' APNs define a 'Username' but not a
'Password'. Working on confirming this theory now.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ne
Just confirmed this theory on mako running vivid-devel image #155 by
modifying my ATT Phone APN and adding a 'Username'. No more mobile data
connection, and I get the same error pointed out by Alfosno in comment
#6.
** Changed in: network-manager (Ubuntu)
Importance: Undecided => High
** Cha
This is another 0.9.10 related regression. This works just fine on mako
with RTM image #17.
--
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/1435776
Title:
NM does not activate
After discussion with Alfonso, this was fixed. Moving the network-
manager Status to 'FixReleased'.
** Changed in: network-manager (Ubuntu)
Status: Incomplete => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to networ
I wasn't able to reproduce this with RTM.
That said, there's a pending version of network-manager that fixes a
separate issue with the WiFi access point list showing APs that
shouldn't be there anymore. See bug #1427205.
There's a version of NM in a PPA that fixes this bug. @taiebot65, not
sur
@Michael
I just tested this with mako/RTM #17, and this seems to be working
fairly well for me.
My test consisted of walking downstairs to the first floor of my
building and then walking down a hallway till the phone eventually
disconnected from WiFi, I then took the elevator back upstairs and as
@costales
Was it only data that didn't recover? Or was voice and SMS also
affected?
Also, do you recall whether or not your phone displayed an icon for
mobile data ( eg. '3g' or 'H' ), or did it just display the icon that
looks like an empty WiFi icon?
Finally, if you do hit this problem again,
@Jean-Baptiste
One other question... when this happens, does the indicator show that
you're connected to 3G, or does it show a WiFi connection with minimal
signal strength ( eg. one bar...which looks like a dot )?
When the device is at the extreme extent of an access point's range, it
can get in
** Tags added: connectivity
--
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/1438402
Title:
wifi can stay connected to network while out of range
Status in network-manager pack
@Jean-Baptiste
A few more questions...
How many SIMs were installed? If more than one, do both have active
data plans? Which SIM is selected for mobile data ( see Cellular
Settings ).
Finally, if you can reproduce this again, can you please add the
following to the bug:
1) The output of /us
*** This bug is a duplicate of bug 1413672 ***
https://bugs.launchpad.net/bugs/1413672
Based on comment #11, I'm making this a duplicate of bug #1413672. If
there are any objections, please feel free to un-dup, but please provide
an explanation if doing so.
** This bug has been marked a dupl
** 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/1438402
Title:
wifi can stay connected to network while
@costales
One other thing to check... did you have more than one SIM installed in
the phone? We've been working on a bug where the mobile-data SIM
selection can switch to the wrong SIM after a reboot or operator switch
/re-registration ( such as what can happen when signal is lost ).
See bug #14
** Also affects: ubuntu-system-settings (Ubuntu)
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/1361864
Title:
add "Tag" property t
** Changed in: ubuntu-system-settings (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/1361864
Title:
add "Tag" property to ConnectionCo
** Changed in: ofono (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/1361864
Title:
add "Tag" property to ConnectionContext
1 - 100 of 520 matches
Mail list logo
