*** This bug is a duplicate of bug 1436330 ***
https://bugs.launchpad.net/bugs/1436330
** This bug has been marked a duplicate of bug 1436330
Network Manager doesn't set metric for local networks any more, causing
connection issues
--
You received this bug notification because you are a
Ubuntu)
Importance: Undecided => Medium
** Changed in: network-manager (Ubuntu)
Assignee: Mathieu Trudel-Lapierre (mathieu-tl) => (unassigned)
** Changed in: network-manager (Ubuntu Quantal)
Assignee: Mathieu Trudel-Lapierre (mathieu-tl) => (unassigned)
** Summary changed:
-
Reassigning to Linux. NM is not responsible for negotiating duplex;
performance issues caused by this would probably warrant looking into
what the driver does.
** Package changed: network-manager (Ubuntu) => linux (Ubuntu)
--
You received this bug notification because you are a member of Desktop
*** This bug is a duplicate of bug 1436330 ***
https://bugs.launchpad.net/bugs/1436330
** This bug has been marked a duplicate of bug 1436330
Network Manager doesn't set metric for local networks any more, causing
connection issues
--
You received this bug notification because you are a
ged in: network-manager (Ubuntu)
Status: Confirmed => Triaged
** Changed in: network-manager (Ubuntu)
Importance: Undecided => High
** Changed in: network-manager (Ubuntu)
Assignee: (unassigned) => Mathieu Trudel-Lapierre (mathieu-tl)
--
You received this bug notification be
Please include /var/log/syslog (after reproducing the upgrade which
causes the system to not boot), so that we can see what fails.
Thanks!
** Changed in: network-manager (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Desktop
Packages,
** Also affects: modemmanager (Ubuntu Precise)
Importance: Undecided
Status: New
** Changed in: modemmanager (Ubuntu)
Assignee: Mathieu Trudel-Lapierre (mathieu-tl) => (unassigned)
** Changed in: modemmanager (Ubuntu Quantal)
Assignee: Mathieu Trudel-Lapierre (mathieu
f
you feel strongly about it being fixed for a particular release, please
follow the steps at http://wiki.ubuntu.com/StableReleaseUpdates to
request an update.
** Changed in: network-manager (Ubuntu)
Status: Confirmed => Fix Released
** Changed in: network-manager (Ubuntu)
Assignee: M
We fixed this, but it must have been missing a LP: tag to close the bug
automatically.
Tony, could you confirm this is indeed resolved?
** Changed in: network-manager (Ubuntu)
Assignee: Mathieu Trudel-Lapierre (mathieu-tl) => (unassigned)
** Changed in: network-manager (Ubu
was a backup, to import it explicitly from
evolution's Import option.
** Changed in: evolution (Ubuntu)
Assignee: Mathieu Trudel-Lapierre (mathieu-tl) => (unassigned)
** Changed in: evolution (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification b
I can easily reproduce this on a generic ppc64el virtual machine; policykit-1
may have trouble starting up:
Error getting authority: Error initializing authority: Error calling
StartServiceByName for org.freedesktop.PolicyKit1: Timeout was reached
(g-io-error-quark, 24)
In my case however it ha
Could you attach /var/log/syslog from the phone when it's connected to
both wifi and 3G? We should be able to know from there whether it
includes all the nameservers it should.
>From there, it's up to whichever responds faster among all the
nameservers, which will be used.
--
You received this b
Closing as Invalid: there is an Import option, it's now under the Add...
button, at the very bottom of the drop-down list.
** Changed in: network-manager (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed
Closing as Invalid then, since this would be a linux/kernel bug anyway.
Thanks!
** Changed in: network-manager (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bug
I'd think this is either a driver or an applet issue; NM really only
tries to connect to wireless networks if they are selected in the UI or
showing up in scan results.
When you're seeing this issue, could you please run "iw dev wlan0 scan
dump" and see if the AP shows up there? That could indicat
hanged in: network-manager (Ubuntu)
Importance: Undecided => High
** Changed in: network-manager (Ubuntu)
Assignee: (unassigned) => Mathieu Trudel-Lapierre (mathieu-tl)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-
Assignee: (unassigned) => Mathieu Trudel-Lapierre (mathieu-tl)
--
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/1272321
Title:
Network Manager should only request new secrets duri
** Changed in: network-manager (Ubuntu)
Status: Confirmed => Triaged
** Also affects: network-manager via
https://bugzilla.gnome.org/show_bug.cgi?id=721776
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Desktop
Packages,
Reassigning to nm-applet, it only needs to support setting the
connection in mode=ap, which NM already understands.
** Package changed: network-manager (Ubuntu) => network-manager-applet
(Ubuntu)
** Changed in: network-manager-applet (Ubuntu)
Importance: Undecided => Medium
** Changed in: net
Thanks!
Maybe there is a config that isn't being read properly by NM at the time
where the connections are getting matched?
I think this indicates where the problem is:
Jan 26 20:12:12 desktop NetworkManager[851]: [1390763532.45734]
[nm-manager.c:2950] nm_manager_activate_connection(): Activati
rtance: Undecided => Medium
** Changed in: network-manager (Ubuntu)
Assignee: (unassigned) => Mathieu Trudel-Lapierre (mathieu-tl)
--
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
I haven't forgotten about this, just having some issues with the build
for armhf, tests aren't passing...
This makes me think however, isn't that going to break the case where
the secrets expire for the wired connection? What happens if you need to
change to a different password, either because it
** Tags removed: verification-done
** Tags added: verification-needed
--
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/1186273
Title:
DUN via bluetooth with a password fails
St
Please add additional information to this bug using:
apport-collect 1275053
So as to add the necessary logs and details about your system for the
developers to debug the issue.
Thanks!
** Changed in: network-manager (Ubuntu)
Status: New => Incomplete
** Changed in: network-manager (Ubun
Do you remember which network you were suspending on at that point?
I see some fairly old scan results, but nothing extraordinary (4, 14, 24
seconds, which seems consistent with NM's scanning thresholds). Still,
the timing is such that there may have been a scan request or an
automatic scan by the
Or trusty...
** Changed in: network-manager (Ubuntu)
Status: Triaged => 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/1292605
Title:
Fix wrong IP6 addres
in: lxc-android-config (Ubuntu)
Assignee: Mathieu Trudel-Lapierre (mathieu-tl) => (unassigned)
** Changed in: network-manager (Ubuntu)
Assignee: Mathieu Trudel-Lapierre (mathieu-tl) => (unassigned)
--
You received this bug notification because you are a member of Desktop
Packages
This is fixed in vivid now, by way of 0.9.10.0. Should we also work on a
SRU to utopic?
--
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/1292605
Title:
Fix wrong IP6 addresses i
No, I don't think it's an issue anymore -- so I'll remove the bug
assignment.
Jelmer, you filed the bug initially, do you still see such issues?
** Changed in: evolution (Ubuntu)
Assignee: Mathieu Trudel-Lapierre (mathieu-tl) => (unassigned)
** Changed in: evolution (Ubu
eted,
feel free to assign it to yourself and start up the dicussion again to
see if we can enable connectivity checking. This may be useful for
Ubuntu Touch as well.
** Changed in: network-manager (Ubuntu)
Assignee: Mathieu Trudel-Lapierre (mathieu-tl) => (unassigned)
** Changed in: netwo
** 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/1431471
Title:
NetworkManager uses ofono GPRS co
rk (Ubuntu)
Status: Confirmed => Incomplete
** Changed in: network-manager (Ubuntu)
Status: Confirmed => In Progress
** Changed in: network-manager (Ubuntu)
Importance: Low => High
** Changed in: network-manager (Ubuntu)
Assignee: (unassigned) => Mathieu Trudel-Lapierre
Please provide screenshots of the lists, as well as /var/log/syslog.
It would also be useful if you could compare the output from other
devices with the output of 'nmcli dev wifi list', comparing it to the
contents of the indicators would be useful.
Finally, when you mention the indicator on PC,
** Changed in: network-manager (Ubuntu Vivid)
Assignee: (unassigned) => Mathieu Trudel-Lapierre (mathieu-tl)
** Changed in: network-manager (Ubuntu Vivid)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Desktop
Packages, wh
Reassigning to the correct package. Use as Hotspot isn't something that
comes from NM; the underlying APIs do seem to work properly.
** Package changed: network-manager-applet (Ubuntu) => gnome-control-
center (Ubuntu)
--
You received this bug notification because you are a member of Desktop
Pac
That looks as though you don't have sufficient access to use these
options; have you changed anything in the system's policykit
configuration recently? Is this a corporate system where system policy
could change without your knowledge?
** Changed in: network-manager-applet (Ubuntu)
Status:
This is on purpose, upstream. We'll be making a conscious decision of
hiding these virtual devices given that NM isn't supposed to manage
them, and showing them might confuse users.
** Changed in: network-manager-applet (Ubuntu)
Status: Confirmed => In Progress
** Changed in: network-manag
Wireless APs are removed after a while, based on whether we receive an
AP removal signal from the supplicant, or if not, after a reasonable
amount of time. This time is currently defined as three times the
maximum scan interval (2 min), so after 6 minutes of the AP not changing
strength or other pr
Connecting to the upstream bug report as well, as per the merge
proposal.
** Bug watch added: GNOME Bug Tracker #743957
https://bugzilla.gnome.org/show_bug.cgi?id=743957
** Also affects: gnome-screenshot via
https://bugzilla.gnome.org/show_bug.cgi?id=743957
Importance: Unknown
Sta
ll get the changes in Ubuntu.
I'm unassigning myself from this bug since it doesn't look like I'll be
able to get to it any time soon, but regardless, it should be
approachable to all to work on a fix.
** Changed in: network-manager (Ubuntu)
Assignee: Mathieu Trudel-Lapierre (m
** Changed in: modemmanager (Ubuntu)
Assignee: Mathieu Trudel-Lapierre (mathieu-tl) => (unassigned)
** Changed in: modemmanager (Ubuntu Precise)
Assignee: Mathieu Trudel-Lapierre (mathieu-tl) => (unassigned)
--
You received this bug notification because you are a member of D
That means this is probably some issue with carrier detection. I wonder
if it's since been fixed in NM?
** Changed in: network-manager (Ubuntu)
Milestone: ubuntu-13.04-beta-1 => None
** Changed in: network-manager (Ubuntu)
Assignee: Mathieu Trudel-Lapierre (mathieu-tl) =>
n-m-pptp was updated to 0.9.10.0 in vivid; closing as Fix Released.
** Changed in: network-manager-pptp (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager-pptp in Ubuntu.
https
*** This bug is a duplicate of bug 1416635 ***
https://bugs.launchpad.net/bugs/1416635
We've fixed this as bug 1416635; so I'll mark this bug as a duplicate of
it now, thanks!
** This bug has been marked a duplicate of bug 1416635
NetworkManager crashed with signal 5 in ASSERT_VALID_PATH_C
I think we fixed this a long time ago with urfkill, unassigning myself
(though this should still be confirmed).
** Changed in: network-manager (Ubuntu)
Assignee: Mathieu Trudel-Lapierre (mathieu-tl) => (unassigned)
--
You received this bug notification because you are a member of Desk
in general. Feel free to comment here if there is
anything to add for the Infineon modems, I will still see the bug report
comments and be able to respond as appropriate. Thanks!
** Changed in: ubuntu-nexus7
Status: Triaged => Invalid
** Changed in: ubuntu-nexus7
Assignee: Mathieu Tru
It would really be quite surprising for unity-greeter to have any effect
on nm-applet without breaking a whole lot of other things. The one thing
pointed out that looked the most promising were the D-Bus errors, and
the "no agent available" message in syslog -- that's really where we
should be look
Fix Committed since it's now in the bzr branch, will make it with the
next release of network-manager-applet or the next bug we fix...
** Changed in: network-manager-applet (Ubuntu)
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of Desktop
Lucid has been EOL for desktop for a while, so I'll mark this as Won't
Fix. I'm sorry we couldn't get to it :(
** Changed in: network-manager (Ubuntu Lucid)
Assignee: Mathieu Trudel-Lapierre (mathieu-tl) => (unassigned)
** Changed in: network-manager (Ubuntu L
** Changed in: network-manager (Ubuntu Vivid)
Assignee: Mathieu Trudel-Lapierre (mathieu-tl) => (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/1383357
Ti
Hum, I must have been drunk or something, because it's obviously a
correct patch and it should have been included long ago. This doesn't
need any further checking. GSLists should be initialized to NULL.
--
You received this bug notification because you are a member of Desktop
Packages, which is s
Except NetworkManager itself doesn't make any new interfaces available
to you, and much less available of ifconfig.
As for the ccmni0 and the state of the ril device, that looks like
something that was fixed recently, but you seem to be running the most
recent revision (though it should be confirm
** Description changed:
+ [Impact]
+ NM changed its method of setting routes on systems, and no longer attaches a
metric value specific to the type of device being used. These values were used
to prioritize connections, so that for example, when connected to both wired
and wireless at the same
This appears to be a crash; could you please check /var/crash for a file
named _usr_sbin_NetworkManager.0.crash or something similar, and run
"ubuntu-bug ". This will automatically open a new bug with the
crash details and all the necessary information. Thanks!
--
You received this bug notificati
27; is unknown, try 'nmcli help'.
** Changed in: network-manager (Ubuntu)
Status: New => Triaged
** Changed in: network-manager (Ubuntu)
Importance: Undecided => High
** Changed in: network-manager (Ubuntu)
Assignee: (unassigned) => Mathieu Trudel-Lapierre (mathieu-
** Changed in: network-manager (Ubuntu)
Status: Confirmed => In Progress
** Changed in: network-manager (Ubuntu)
Assignee: (unassigned) => Mathieu Trudel-Lapierre (mathieu-tl)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscri
I've seen some reports of these; but without logs this is the kind of
thing that is impossible to debug.
Could someone seeing this enable debug logs in NetworkManager (editing
/etc/init/network-manager.conf and adding --log-level=debug --log-
domains=core,mb to the Exec line) as well as enabling
Reassigning to the right package.
** Package changed: installation-guide (Ubuntu) => simple-scan (Ubuntu)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to simple-scan in Ubuntu.
https://bugs.launchpad.net/bugs/1403196
Title:
does not s
Reassigning to xorg, since this is more likely the correct package.
** Package changed: installation-guide (Ubuntu) => xorg (Ubuntu)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1237421
** Changed in: network-manager (Ubuntu)
Status: Triaged => 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/1436330
Title:
Network Manager doesn't set metric
My understanding was that there would be packet loss all the time
without the patches applied, due to packets being sent in a round-robin
fashion between two links to the same default gateway.
This said, I'm able to reproduce the apparent "packet loss", but I say
apparent here because it seems to
Patch looks fine to me, but so far there is nothing here for ubiquity.
Do you need any changes to ubiquity after all?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-desktop3 in Ubuntu.
https://bugs.launchpad.net/bugs/1382291
Title
** Changed in: network-manager-applet (Ubuntu)
Status: Triaged => In Progress
** Changed in: network-manager-applet (Ubuntu)
Assignee: (unassigned) => Mathieu Trudel-Lapierre (mathieu-tl)
--
You received this bug notification because you are a member of Desktop
Packages, wh
** Changed in: network-manager-applet (Ubuntu Vivid)
Assignee: (unassigned) => Mathieu Trudel-Lapierre (mathieu-tl)
** Changed in: network-manager-applet (Ubuntu Vivid)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Desktop
Pa
** Description changed:
+ [Impact]
+ If for any reason ModemManager is unavailable or unable to understand the
modem device that pops up as broadband (also, in the case of Desktop-Next),
NM-applet may crash due to expecting that there is always a devinfo object from
the ModemManager data.
+
+
You need to look for network-manager-applet, not network-manager.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager-applet in Ubuntu.
https://bugs.launchpad.net/bugs/1418260
Title:
nm-applet crashed with SIGSEGV in add_me
** Also affects: network-manager-applet (Ubuntu)
Importance: Undecided
Status: New
** Changed in: network-manager-applet (Ubuntu)
Status: New => In Progress
** Changed in: network-manager-applet (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification b
please follow the steps in comment #11. If you had a space in your
command between the name of the package and /, then this could explain
why the command did not work.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager-applet
Marking the ubiquity task as Invalid; let's switch it back if it turns
out there are some needed changes in ubiquity (as for wallpaper in
ubiquity-dm?)
** Changed in: ubiquity (Ubuntu Trusty)
Status: Confirmed => Invalid
** Changed in: ubiquity (Ubuntu)
Status: Incomplete => Invalid
** Changed in: wpa (Ubuntu)
Status: Confirmed => In Progress
** Changed in: wpa (Ubuntu)
Assignee: (unassigned) => Mathieu Trudel-Lapierre (mathieu-tl)
** Changed in: wpa (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a
So, looks like this is still broken, reopening...
** Changed in: network-manager-applet (Ubuntu)
Status: Fix Released => New
** Information type changed from Private to Public
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to netwo
** Changed in: network-manager-applet (Ubuntu)
Status: New => Triaged
** Bug watch added: GNOME Bug Tracker #747785
https://bugzilla.gnome.org/show_bug.cgi?id=747785
** Also affects: network-manager-applet via
https://bugzilla.gnome.org/show_bug.cgi?id=747785
Importance: Unknown
** Changed in: network-manager (Ubuntu)
Status: New => In Progress
** Changed in: network-manager (Ubuntu)
Importance: Undecided => High
** Changed in: network-manager (Ubuntu)
Assignee: (unassigned) => Mathieu Trudel-Lapierre (mathieu-tl)
--
You received this bug not
There isn't much we can do with NetworkManager for this: different
providers implement their plans differently. Here in Canada, many
providers will still let you stay connected (or successfully create a
new connection) even if your "plan" as run out, but you'll be charged
extra credit on a prepaid
Shih-Yuan; the "ubiquity_hidpi.patch" patch you attached doesn't seem to
be directly related to HiDPI support. Maybe I'm misreading, but those
seem to be nothing more than some of the changes that aren't yet in
Trusty.
As for the changes to unity-settings-daemon, I can only let you finish
those si
It seems like this would possibly be a good candidate for SRU; but this
requires that the bug be also fixed in the development release. Given
that there's already a tag for utopic and reports that it doesn't work
there, I suspect it also doesn't work yet in Vivid.
Alistair, maybe you'd be interest
No need to report this again on the gnome lists; this is already fixed
in evolution/e-d-s 3.6.2.
We'll ship 3.6.2 as a SRU shortly.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to evolution in Ubuntu.
https://bugs.launchpad.net/bugs/1055
ssion Potential]
** Affects: evolution-data-server (Ubuntu)
Importance: Medium
Assignee: Mathieu Trudel-Lapierre (mathieu-tl)
Status: In Progress
** Changed in: evolution-data-server (Ubuntu)
Assignee: (unassigned) => Mathieu Trudel-Lapierre (mathieu-tl)
** Changed in
** Description changed:
Update evolution-data-server to 3.6.2 to get latest fixes from upstream,
including the evolution fix for the signatures being doubled (bug
1055497), e-d-s 3.6.2 is required for evolution 3.6.2.
There is a micro-release exception for GNOME that encompasses evoluti
* Make contact maps work again. (Matthew Barnes)
[Test Case]
- Run evolution; add calendars with some future events existing,
- Verify that the events appear in indicator-datetime.
[Regression Potential]
** Affects: evolution (Ubuntu)
Importance: Medium
Assignee: Mathieu Trudel-La
** Branch unlinked: lp:~mathieu-tl/network-manager/0.9.4.0-0ubuntu4.2
--
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/1004775
Title:
NetworkManager restarts dnsmasq and adds ho
Ansus; it doesn't mean we can't send patches. I can't possibly see every
comment of every bug, there's just too many.
This can't be shipped as SRU; it depends on rather intrusive changes to
NM and would furthermore need changes to nm-applet (including new
strings that would have to be translated)
** Description changed:
Binary package hint: network-manager
+
+ [Impact]
+ Any users of network-manager (Ubuntu Desktop) with a broadcom chipset
requiring the wl driver.
+
+ [Test Case]
+ 1) run desktop
+ 2) make sure the wifi signal level appears.
+
+ [Regression Potential]
+ This is a fix
For the curious; that's just by adding the "apt-setup/proposed=true"
boot parameter as you boot from an alternate CD -- you don't need to
download any special installer image (you don't need the first link in
the wiki page mentioned above).
--
You received this bug notification because you are a
You don't need to apply anything; you can test this by simply running an
install (provided you have IPv6 connectivity when you do so; reproducing
the actual bug), and enabling proposed for the install: see
https://wiki.ubuntu.com/Testing/EnableProposed (the section
"Installation testing with -propo
What this needs is basically a workaround to keep the non-multiarch path
for pango available through the installation, although it's definitely
not needed at any point after the system is upgraded and rebooted.
Perhaps just providing that symlink which we can remove in later
upgrades of pango1.0.
This is most likely NetworkManager, if anything. However, it seems to me
like this always work, and hasn't changed sufficiently to be likely to
be broken.
Are you sure the routes are configured properly to allow access to the
wireless network?
Please attach the ouput of the following two commands
Closing as Invalid; since we don't know what caused it.
If it happens again, please don't hesitate to file a new bug report;
including the information I asked for above. The two most likely causes
I think would be routing issues, or a problem with the MTU if you're
using a home router from one of
** Changed in: network-manager (Ubuntu)
Status: Confirmed => In Progress
** Changed in: network-manager (Ubuntu)
Assignee: (unassigned) => Mathieu Trudel-Lapierre (mathieu-tl)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscri
m (canonical-dx-team) => Mathieu
Trudel-Lapierre (mathieu-tl)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to evolution-indicator in Ubuntu.
https://bugs.launchpad.net/bugs/1051882
Title:
NBS: Needs porting to latest evolution-data-
=> High
** Changed in: libdbusmenu (Ubuntu)
Assignee: (unassigned) => Charles Kerr (charlesk)
** Changed in: network-manager-applet (Ubuntu)
Assignee: (unassigned) => Mathieu Trudel-Lapierre (mathieu-tl)
** Changed in: network-manager-applet (Ubuntu Precise)
Assignee: Charl
Adrian, the underlying bug is still going to be fixed; but we need to
separate fixing something in nm-applet and fixing something in another
package.
The leaks are fixed in Raring, marking as Fix Released for that release.
** Changed in: network-manager-applet (Ubuntu)
Status: Confirmed =>
t least from the fact that the behavior shows in ip monitor when NM is
running, and doesn't show when it's not running, indicates to me that
it's likely a bug in NM.
** Changed in: network-manager (Ubuntu)
Assignee: (unassigned) => Mathieu Trudel-Lapierre (mathieu-tl)
--
You
Quickly, from the NetworkManager logs, I'd tentatively say that the
modem can't find signal; but there's too little information to be able
to know for sure.
Can you please provide debugging logs for ModemManager, see
http://wiki.ubuntu.com/DebuggingNetworkManager for how you can get these
logs.
R
: network-manager (Ubuntu)
Status: New => Confirmed
** Changed in: network-manager (Ubuntu)
Importance: Undecided => Medium
** Changed in: network-manager (Ubuntu)
Assignee: (unassigned) => Mathieu Trudel-Lapierre (mathieu-tl)
--
You received this bug notification because
The device is having a hard time scanning, and it seems to be because of some
issues at the kernel level:
Apr 9 17:14:50 palmer kernel: [ 1303.637409] ath: phy0: Unable to reset
channel, reset status -5
Apr 9 17:14:50 palmer kernel: [ 1303.637421] ath: phy0: Unable to set channel
Apr 9 17:14:5
No, not Fix Released for Precise just yet:
This change requires the an update to dnsmasq currently in precise-
proposed (https://launchpad.net/ubuntu/+source/dnsmasq/2.59-4ubuntu0.1)
which needs to be verified by someone having the issue, to go along with
the network-manager - 0.9.4.0-0ubuntu4.3~
Can you please run bluez in debug at the time (sudo stop bluetooth, then
sudo bluetoothd -d -n ), as well as NetworkManager in debug mode (see
http://wiki.ubuntu.com/DebuggingNetworkManager) ?
Seems to me like there may be some further information in bluez debug
logs that could point to an issue,
Are you sure the network is open? Seems to me like it's failing to auth due to
cached auth data:
#define WLAN_REASON_PREV_AUTH_NOT_VALID 2
Apr 4 15:19:15 ubuntu-gnome NetworkManager[1958]: (wlan0): supplicant
interface state: completed -> authenticating
Apr 4 15:19:15 ubuntu-gnome kernel: [
Does this mean you can now see the wireless device, and we can close
this bug report?
--
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/1164193
Title:
Wireless not a network opti
1 - 100 of 2151 matches
Mail list logo
