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 Ubuntu
Touch seeded packages, which is subscribed to pcsc-lite in Ubuntu.
https://bugs.launchpad.net/bugs/19
** 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
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
snappy-hwe-snaps is a project used to track work related to system stack
snaps published by Canonical. Your bug most likely has to do with the
bluez (or related) Debian package from the Ubuntu archive.
** Project changed: snappy-hwe-snaps => bluez
** Project changed: bluez => bluez (Ubuntu)
--
** Changed in: network-manager (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1781597
Title:
[SRU] WoWLAN settings are not
I agree with Kyle that "unknown" state is pretty useless, that said, as
it's defined by QNetworkAccessManager, we can't really get rid of it
without proposing a change to QNetworkAccessManager API. Thus I agree
with Michi that for now scopes and/or the scopes framework should treat
"unknown" the s
@Michi
I guess I look at this from NetworkManager's point of view. Your either
"connected" or you're not... The network indicator reflects this, it
shows the mobile data technology if connected to the mobile operator.
If WiFi is enabled, it works like the desktop. You can easily see the
state o
@Michi
Hmmm, I expected lp to auto-link "comment #7" to the comment in this
bug, but that apparently didn't work:
https://bugs.launchpad.net/ubuntu/+source/unity-scopes-
api/+bug/1502282/comments/7
*If* it's possible for the shell to return "unknown", then yes I think
the shell should be initial
Here's the associated pull-request ( currently under-review ):
https://github.com/rilmodem/ofono/pull/214
** Changed in: ofono (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez
** Also affects: ofono (Ubuntu RTM)
Importance: Undecided
Status: New
** Changed in: ofono (Ubuntu RTM)
Status: New => Fix Committed
** Changed in: ofono (Ubuntu RTM)
Importance: Undecided => High
** Changed in: ofono (Ubuntu RTM)
Assignee: (unassigned) =>
@Thomas
What's the client component in this case, and why wasn't it responding?
Also, does this still tie into the WiFi state per the original
description?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to location-service in
** Changed in: network-manager (Ubuntu RTM)
Status: Fix Released => Incomplete
** Changed in: network-manager (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to indicator-ne
This script queries GetAllMatchRules and generates output including
warnings about less-optimal DBus match rules.
** Attachment added: "example DBus script for GetAllMatchRules usage"
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1480877/+attachment/4512384/+files/get-all-matc
Here's the two patches necessary to enable the GetAllMatchRules method,
as well as the patch that bumped the match rules limit to 5000 (
20_system_conf_limit.patch ).
** Attachment added: "Dbus patches"
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1480877/+attachment/4512383/
One of the frustrating parts about this bug is the incomplete
description, and the fact that it's been nigh impossible to nail down a
set of concrete steps to reproduce...
Also, the bug description contends that NM 'PropertiesChanged' signals
are causing the UI freezes, however we have no idea why
Forgot to add the output of the system match rules for mako. Note at
the time this was run both slpgwd and posclientd both have 616 match
rules. It looks like stopping the location service ( via upstart or the
indicator ) may have cleared the rules for ubuntu-location-servicesd.
** Attachment ad
** Also affects: location-service (Ubuntu RTM)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1480877
Title:
Access poi
So re-testing with krillin ( rc-proposed, #162 ).
Confirmed that using a patched version of dbus 1.8, the match rule
limits aren't enforced, so each of the loc processes slowly grows its
number of match rules till they cap out at 5000 each.
So, WiFi enabled & connected, with the HERE app running
Re: the xenial version of dbus, you need to be careful as although I was
able to get it to run on a krillin, it prevented the UI from coming up
on mako. This is why I backported the changes and pushed to my PPA (
1.8.12-1ubuntu5~awe3 ).
https://launchpad.net/~awe/+archive/ubuntu/ppa
@Andrea
I'
** Changed in: location-service (Ubuntu RTM)
Assignee: (unassigned) => Scott Sweeny (ssweeny)
** Changed in: location-service (Ubuntu RTM)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
@Michael
Thanks again for your help with testing this.
1) When the phone disconnects from an AP, the scan interval drops to
it's lowest possible interval ( 20s ), as the goal is re-connecting as
quick as possible. It'll eventually drift back to ~60s.
2) I also get the very brief <= 1s stutter w
@Pat
We might want to hotfix this once we come to fully understand it( and I
think we're getting close ).
While working with tvoss a fixes to location-services, we realized that
by default, the get-all-match.py script only outputs warnings. While
reviewing a test run from tvoss, I didn't see an
@taiebot65
I don't think this is related to bug #1462664. This is specifically
related to the number of processes watching individual network-manager
access point objects, and the fact that these processes leak match
rules, so they continue to add match rules to dbus for new access
points, but n
Here's a script that calls dbus-monitor with the correct match rules in
order to catch AccessPointAdded and Removed signals, as well as
PropertiesChanged signals for the Device.Wireless 'AccessPoints'
property.
** Attachment added: "monitor-aps.sh"
https://bugs.launchpad.net/ubuntu-rtm/+source
** Also affects: buteo-syncfw (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: buteo-syncfw (Ubuntu)
** Also affects: buteo-syncfw (Ubuntu RTM)
Importance: Undecided
Status: New
** Also affects: unity8 (Ubuntu RTM)
Importance: Undecided
Status: New
I just added tasks for the packages mentioned in comment #65.
Some things learned today:
- the sub-component of QNetwork that's most likely the cause is called
Bearer Management. One of it's classes, QNetworkSession includes a
plugin for NetworkManager which creates listeners for new AccessPoin
A couple of comments.
I've actually been chasing down a DBus performance issue on touch since
mid-Summer, related to NetworkManager and WiFi scanning.
The high-level summary is that we have a number of system processes
listening for NM AccessPoint DBus signals on specific AccessPoint DBus
object
@Timo
Thanks for the update. I commented on bug #1404188 regarding this bug.
I agree with you that moving to a new backend for the vivid-overlay PPA
is risky. That said, if we keep the networkmanager bug backend, this
bug really needs to be fixed.
What you say about the networkmanager backend i
Here's a first attempt at a patch, which unfortunately doesn't seem to
work...
The general idea is when an AccessPointRemoved signal is received, we
need to ensure that the associated DBus watch is removed. According to
the QDbus documentation, DBusConnection::disconnect() should do this. I
unfo
@Lorn
I don't think the blocking DBus calls are the culprit per se, although I
did see a few while looking at the NM backend. The simple issue is
that NM removes AccessPoint DBus objects on a regular basis, the the
signal watches for these objects are not being released...
I'd see your new plug
Just a quick update on my debugging.
I've verified that the NM bearer plugin's qnetworkmanagerengine class is
receiving the 'AccessPointRemoved', is matching them correctly in it's
saved list, and is called delete on the
QNetworkManagerInterfaceAccessPoint instance. The associated destructor
is c
And some more details, by adding 'env QDBUS_DEBUG=1' to the unity8
upstart job, I'm getting a lot more detail without having to further
modify the code.
I'm seeing "Adding rule" log statements produced by
QDBusConnectionPrivate, but no corresponding "Removing rule" logs, so
sounds like my previous
Some more details:
- the version of the qtbase package in touch atm is: 5.4.1+dfsg-
2ubuntu10
- I checked and didn't see significant differences in the networkmanager
bearer plugin when comparing against 5.5.1, and 5.6.
- That said, there's been quite a few changes in the QDBus code,
specifical
Note, QNetworkManagerEngine::setupConfigurations() is also suspect as it
can get called from a couple of places and has a loops over the current
devices and calls deviceAdded().
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
I grabbed your patch and incorporated most of it into my latest patch (
I left out a few of the disconnect calls for some of the other NM
interfaces not directly involved in the match rules problem ), however
it failed to build...
While trying to just pull in the pieces and resolve the conflicts w
** Changed in: qtbase-opensource-src (Ubuntu)
Assignee: (unassigned) => Tony Espy (awe)
** Changed in: qtbase-opensource-src (Ubuntu)
Importance: Undecided => High
** Changed in: qtbase-opensource-src (Ubuntu)
Status: Confirmed => In Progress
--
You received
Here's a new version of the patch with all the access-point related
signals removed.
It makes no sense for any of this logic to be present in our system, as
none of our code attempts to control the network configuration via
Bearer Mgmt. With this patch, the plugin will never receive any NM
access
Public bug reported:
The ofono upstart override file includes an updated exec line for ofono
with a different set of plugins excluded vs. the upstart job shipped as
part of the ofono package.
The '-P' argument is a comma-separated list of plugins to exclude at
startup. ofono internally uses g_p
** Branch linked: lp:~phablet-team/network-manager/lp1435776
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1450790
Title:
Phone with an APN specifying Username/Pa
** Also affects: canonical-devices-system-image
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to indicator-network in
Ubuntu.
https://bugs.launchpad.net/bugs/1447984
Title:
Sim blo
Changed ofono task to Invalid, as the bug is confirmed to be network-
manager only.
** Changed in: canonical-devices-system-image
Status: New => In Progress
** Changed in: ofono (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member o
** Changed in: ofono (Ubuntu)
Status: New => Confirmed
** Changed in: nuntium (Ubuntu)
Status: New => Confirmed
** Changed in: nuntium (Ubuntu)
Importance: Undecided => Wishlist
** Changed in: ofono (Ubuntu)
Importance: Undecided => Wishlist
** Also affects: messaging-app (U
A few comments/questions:
- what does Android do, does it temporarily enable data for the sole
purpose of uploading a MMS payload?
- what about receiving, does Android allow receiving a MMS when mobile
data is disabled?
- iOS8 doesn't allow a MMS message to be sent if mobile data is
disabled.
Updated the ofono task to Invalid, and added a task for indicator-
network.
** Changed in: ofono (Ubuntu)
Status: New => Confirmed
** Changed in: ofono (Ubuntu)
Status: Confirmed => Incomplete
** Also affects: indicator-network (Ubuntu)
Importance: Undecided
Status: New
I can confirm that WiFi EAP-SIM support is not supported by Ubuntu.
I changed this Importance to 'Wishlist' as this is a missing feature,
not a bug.
Without in-depth analysis, at minimum this would require support in
network-manager ( both the core WiFi code and ofono integration logic )
and poss
** Branch linked: lp:~phablet-team/network-manager/lp1361864
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1361864
Title:
add "Tag" property to ConnectionContext
Moved back to ofono task back to Confirmed as this is not actively being
worked on...
** Changed in: ofono (Ubuntu)
Status: In Progress => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to telephony-service in
** Changed in: network-manager (Ubuntu)
Status: New => Confirmed
** Changed in: network-manager (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-download-manager in
Ubunt
Note, as I've been using the phablet-team telephony PPA for other
testing, so although the version in the PPA has the fix, it has some
other experimental changes, so it might cause other problems when
testing. Use at your own risk...
If all goes well, we should have this in a silo in the next day
Note, as I've been using the phablet-team telephony PPA for other
testing, so although the version in the PPA has the fix, it has some
other experimental changes, so it might cause other problems when
testing. Use at your own risk...
If all goes well, we should have this in a silo in the next day
** Summary changed:
- add "Tag" property to ConnectionContext interface
+ add "Preferred" property to ConnectionContext interface
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchp
NetworkManager is supposed to handle adding a specific host route for a
MessageProxy present in a combined APN. This doesn't appear to be
happening anymore in vivid.
I checked krillin/rtm #22/sim1=ATT sim2=empty.
With WiFi off, the routing table looks like this:
default via 10.186.165.219 dev c
Attached is the NetworkManager dispatch script which is supposed to add
the MMS Proxy route. This script is part of the lxc-android-config
package. I've verified that it exists in our vivid images. For some
reason it appears to be broken.
The script is passed the modem_path ( env:DEVICE_IPATH )
@Alfonso
Updated version of the script in comment #5 looks good to me...
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1454625
Title:
Cannot send MMS messages wi
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 Ubuntu
Touch seeded packages, which is subscribed to network-manager in U
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 Ubuntu
Touch seeded packages, which is subscribed to network-manager in U
How about we start with what SIM card is installed in the phone? Is
CMCC, China Mobile?
When ofono starts, if a valid SIM is inserted in the phone, ofono will
try to read the emergency numbers from the file EF_ECC ( emergency
number list ). It tries two different formats to ensure that it's able
** Changed in: canonical-devices-system-image
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1450790
Title:
Phone with
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 Ubun
** Changed in: canonical-devices-system-image
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1435776
Title:
NM does not a
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
Please see bug #1444883 for a description of how emergency numbers
currently work in Ubuntu's version of ofono.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to telephony-service in
Ubuntu.
https://bugs.launchpad.net/bugs/14532
@Alfonso -
I just checked my Nexus5 and it the Emergency Dialer rejects the call
immediately if the number entered is not an emergency number. I didn't
go so far as checking the RIL trace, but as the dialog pops up right
away, it's doubtful it initiated a call and got a response from the
network
@Alfonso
What device did you use and what software was it running ( ie. what
version of Android )?
Regarding the SIM being programmed wrong in this case, yes it's
worrying, but it's also a fact of life that some operators will do a
poor job of programming their SIMs. This isn't the first case of
@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 Ubuntu
Touch seeded packages, which is subscribed to n
** 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 Ubuntu
Touch seeded packages, which is subscribed to netwo
@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 Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1461999
Title:
Cr
** Changed in: network-manager (Ubuntu)
Status: Confirmed => In Progress
** Changed in: network-manager (Ubuntu RTM)
Status: Incomplete => In Progress
** Changed in: network-manager (Ubuntu RTM)
Assignee: Víctor R. Ruiz (vrruiz) => Tony Espy (awe)
--
You received
I've split out some of the code I was working on for bug #1445080 (
Cellular connection isn't restored after FlightMode disabled ) and
created a proposed fix..
I've pushed a test version to my PPA for testing before I go ahead and
create a silo ( I'd like the merge proposal reviewed as well ). Yo
** Changed in: network-manager (Ubuntu RTM)
Assignee: (unassigned) => Tony Espy (awe)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1361864
Title:
** Changed in: network-manager (Ubuntu)
Assignee: (unassigned) => Tony Espy (awe)
** Changed in: network-manager (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-m
** Changed in: network-manager (Ubuntu)
Assignee: (unassigned) => Tony Espy (awe)
** Changed in: network-manager (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-m
A couple of minor comments were addressed in the merge proposal, and a
new version with an official version number has been pushed to the
telephony PPA, this package will be binary sync'd to a silo for landing
in the overlay PPA. I will post silo details when they become
available.
--
You receiv
For anyone else wanted to test, this fix has landed in silo-031:
https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/landing-031
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.
** Also affects: network-manager (Ubuntu RTM)
Importance: Undecided
Status: New
** Changed in: network-manager (Ubuntu RTM)
Status: New => Confirmed
** Changed in: network-manager (Ubuntu)
Assignee: Tony Espy (awe) => (unassigned)
--
You received this bug notifi
Changed the status of the Ubuntu task, as this has not yet been merged
for wily.
** Changed in: network-manager (Ubuntu RTM)
Status: Fix Committed => Fix Released
** Changed in: network-manager (Ubuntu)
Status: Fix Committed => In Progress
--
You received this bug notification bec
Changed the status of the Ubuntu task as the fix has not yet been merged
for wily.
** Changed in: network-manager (Ubuntu)
Status: Fix Committed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-ma
** Also affects: location-service (Ubuntu)
Importance: Undecided
Status: New
** Changed in: location-service (Ubuntu)
Status: New => Incomplete
** Changed in: network-manager (Ubuntu)
Status: Incomplete => In Progress
--
You received this bug notification because you are
** Branch linked: lp:~phablet-team/network-manager/lp1480877-wifi-rm-
dup-scan-signals
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to location-service in
Ubuntu.
https://bugs.launchpad.net/bugs/1480877
Title:
Access points
: New => In Progress
** Changed in: network-manager (Ubuntu RTM)
Assignee: (unassigned) => Tony Espy (awe)
** Changed in: network-manager (Ubuntu)
Importance: Undecided => High
** Changed in: network-manager (Ubuntu RTM)
Importance: Undecided => High
--
You recei
Note, one other observation noticed this week. If the HERE Maps
application is running and WiFi is enabled, it triggers scans every
4-5s.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to location-service in
Ubuntu.
https://bug
@Markcortbass
Do you have the latest OTA installed?
Which app were you using when you hit the bug?
Also, it's possible that bug #1480877 might have something to do with
this, as when WiFi is enabled, and HERE Maps is run, a new WiFi scan is
triggered every 4-5s, and the resulting spike in DBus t
Confirmed on krillin ( devel-proposed #206 ). The .crash file wasn't
very useful, but I should be able to diagnose fairly quick.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpa
Here's the backtrace:
#0 0x000aa24c in platform_link_added (self=self@entry=0x20bf930,
ifindex=, plink=plink@entry=0x20cbfc8) at nm-manager.c:1956
ignore = 0
factory =
device =
error = 0x0
__func__ = "platform_link_added"
#1 0x000ac02a in platform_query
The code in question is this:
/* Try registered device factories */
factory = nm_device_factory_manager_find_factory_for_link_type (plink->type);
if (factory) {
gboolean ignore = FALSE;
device = nm_device_factory_new_link (factory, plink, &ignore, &error);
if (!device) {
if (!
** Changed in: network-manager (Ubuntu)
Status: Confirmed => Won't Fix
** Changed in: network-manager (Ubuntu)
Status: Won't Fix => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in
No crash on mako ( devel-proposed #313 ).
Pretty sure this is being caused by a device factory failure when trying
to create a NMDevice instance for 'ccmni0', which is modem device,
managed by rild.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, w
Also, testing on krillin ( devel-proposed #225 ) is super painful.
Unity seems to slow to crawl while painting the Welcome screen. It take
several minutes for the phone to become usable... and spends much of the
time prior to this basically frozen on the lock screen.
--
You received this bug not
NM 0.9.10.0 included an "?" ( if ) check in the log statement that's
crashing. Apparently this got lost in the merge. Patch on the way...
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bug
1 - 100 of 674 matches
Mail list logo
