@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
Public bug reported:
Razer Megalon headset this device is not working on Ubuntu
ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 4.2.0-34.39-generic 4.2.8-ckt4
Uname: Linux 4.2.0-34-generic x86_64
ApportVersion: 2.19.1-0ubuntu5
Arch
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
Dear Christopher,
sorry , that is far too complicated for me to cope with, or even to
understand. I will just have to live with logging in twice.
thanks for your efforts
regards
Ton Morton
On 04/03/16 15:29, Christopher M. Penalver wrote:
> Tony Morton, in order to allow additional upstr
Dear Christopher,
the output is;
A11
10/14/2013
On 03/03/16 22:10, Christopher M. Penalver wrote:
> Tony Morton: Please provide the output of the following terminal > command
> (not perform an apport-collect): sudo dmidecode -s >
bios-version && sudo dmidecode
in problem.
regards
Tony Morton
On 02/03/16 02:02, Christopher M. Penalver wrote:
> Tony Morton, thank you for reporting this and helping make Ubuntu
> better.
>
> As per http://www.dell.com/support/home/us/en/19/product-support/product
> /inspiron-660s/drivers?os=biosa an
I am hitting this issue too on a fresh 15.10 install, exactly as
everyone else has described. This really needs to be triaged and looked
at IMHO, although not a major issue it is a pretty poor experience.
--
You received this bug notification because you are a member of Desktop
Packages, which i
Public bug reported:
Since kernel 70.113 came in I have to log in twice at start up. After
the first log in the desktop screen appears for a few seconds then
crashes back to a black screen and then the log in screen appears again.
After the second log in the system works normally. This is Ubuntu
1
@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
Public bug reported:
Just upgraded to Ubuntu 15.10
The individual menu bar menu options are very small. I am not talking
about the menu bar title or the menu names e.g. "File" "Edit" etc., I'm
talking about the individual options within each menu. I expect the
text of the menu items to be the s
@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
Public bug reported:
Short story:
I have a CyberPower 825AVR (USB attached) when attaching my iPhone or iPad (via
USB) to charge, the Unity (gnome power manager?) displays a message saying the
UPS battery is critically low and the system will shut down immediately. It
does shut down immediatel
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
Just a quick update to mention that the change to the NM bearer plugin
seems to have caused a regression when qtbase is installed from the PPA
onto a desktop ( for UI development work ).
To reproduce, the overlay PPA needs to be added as a software source,
then ubuntu-system-settings installed/upg
The fix has landed in silo-026, as part of location-services version:
2.1+15.04.20151202.1-0ubuntu1
** Changed in: location-service (Ubuntu RTM)
Status: In Progress => Fix Committed
** No longer affects: sync-monitor (Ubuntu RTM)
** No longer affects: maliit-framework (Ubuntu RTM)
** No
The latest version of the patch is now in a silo-026, included as part
of a new qtbase version 5.4.1+dfsg-2ubuntu11~vivid1.
** Changed in: qtbase-opensource-src (Ubuntu)
Status: In Progress => Fix Committed
** Changed in: sync-monitor (Ubuntu RTM)
Status: New => Incomplete
--
You
The associated version for the dbus-cpp in silo-026 is:
4.3.0+15.04.20151126-0ubuntu1
--
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/1480877
Title:
Access points' "PropertiesC
@Timo
As previously mentioned, I'd like to get this change out as a hot-fix,
and then do proper evaluation of the new connectivity API based plugin
with the goal to land it as part of OTA9.
@Lorn
I'll take a look at that the line you mentioned, however we need to draw
the line at some point and
Note, I've also pushed a new version based on your latest patch to my
PPA if anyone's interested in testing before it lands in silo-026:
https://launchpad.net/~awe/+archive/ubuntu/ppa
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to netwo
@Lorn
Thanks for the update.
I usually do all my testing on rc-proposed, as it's latest and greatest.
I wasn't aware of the "ubuntu-developer" channel. I've tested on rc-
proposed/bq-aquaris.en ( #188 ) with the full set of packages from
silo-026, and everything seemed good to me.
Thar said, I'
@Lorn
Can you add some details regarding what image channel you actually used
and device for testing? rc-proposed is probably the best base for you
to use.
The "GetAll" behavior you're describing is similar to what I was seeing
with the AccessPoint objects. The code would see a "PropertiesChang
@Mike
Small stutters when transitioning from mobile to WiFi or visa versa, or
stutters when scanning. The fixes to location-services and Qt both are
applicable to the latter case only...
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to n
@Lorn
Did you see this recently? If so, what device and image?
As I mentioned, the mobile connection on touch doesn't support IPv6
connections.There was a bug in NM that falsely reported that a
default IPv6 route was available, but this was fixed awhile back.
Please see bug #1444162 for deta
@Lorn
Thanks for the updated patch.
The only significant difference besides the DeviceModem destructor fix
was the change you mentioned about default routes. Is there a touch-
specific bug that this fixes? On our system, the modem connection will
never be IPv6, whereas it is possible to get a
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
** 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
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
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 Desktop
Packages, which is subscribed to network-mana
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
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
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
@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
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
@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
dpkg: warning: trying to overwrite '/usr/share/man/man1/djpeg.1.gz', which is
also in package libjpeg-turbo-progs 1.3.0-0ubuntu2
dpkg: warning: trying to overwrite '/usr/share/man/man1/exifautotran.1.gz',
which is also in package libjpeg-turbo-progs 1.3.0-0ubuntu2
dpkg: warning: trying to overwri
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
** 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
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
@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
@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
@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
** 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 Desktop
Packages, which is subscribed to network-mana
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'
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
For me the gvm blackscreen could be fixed by installing ubuntu-gnome-
desktop and then running "sudo dpkg-reconfigure lightdm". However, this
created an endless login loop for all users. The way to fix the endless
loop problem was to select the Mate desktop environment before logging
in. Then every
** Also affects: location-service (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/1480877
Title:
Access points' "Proper
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
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
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
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/
** 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 Desktop
Packages, which is subscribed to network-manager in Ubunt
This is still an issue for me on 15.04. I have to alt-f1, log in and
kill gnome-screensaver. Then I need to save everything and reboot
because every few seconds the screen will turn black after doing this.
I don't use ecryptfs, I don't have several copies of gnome-screensaver
running when this h
*** This bug is a duplicate of bug 1422004 ***
https://bugs.launchpad.net/bugs/1422004
The does not appear to be a duplicate to me - the issue is not one of
Cups crashing with HP printers as per #1422004 , but is one where you
are unable to install the driver to begin with. How is that a
dupl
Unfortunately this is the way NetworkManager works. It's goal is to
establish a network connection using the highest priority device and
connection available. Success is defined as connection established and
networking configuration successful ( ie. IP address assigned, routing
table setup, ... )
** Changed in: network-manager (Ubuntu RTM)
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/1480877
Title:
Access points' "Propertie
201 - 300 of 886 matches
Mail list logo
