Should this be reassigned to network-manager-openvpn?
--
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/1430077
Title:
[vivid] VPN connection breaks /etc/resolv.conf
Status in n
** Changed in: network-manager (Ubuntu)
Status: In Progress => 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/1003842
Title:
dnsmasq sometimes fails to resolve priv
> Now, it is being pushed instead to /etc/resolv.conf.
>
> nameserver 10.99.244.1
> nameserver 127.0.1.1
>
> [...]
> Connecting to the VPN also pushes search paths to /etc/resolv.conf -
> overriding the search
> domains that I have already configured, and which should take precedence.
Is this b
Does this bug still affect anyone?
** 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.net/bugs/434477
Title:
A workaround may be to edit /etc/NetworkManager/NetworkManager.conf and
comment out the line "dns=dnsmasq".
** Description changed:
- Using a laptop with a hardware switch for enable/disable WLAN.
- Connected to two different LANs using DHCP on ETH/WLAN.
+ I have a laptop with a hardware switch t
Christian, the workaround is to comment out the line "dns=dnsmasq" in
/etc/NetworkManager/NetworkManager.conf.
--
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/1003842
Title:
dn
** Package changed: network-manager (Ubuntu) => network-manager-applet
(Ubuntu)
--
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/1096600
Title:
Clicking "Edit Connections
@tombert: Probably not the same issue, since the issue being discussed
here is not fixed by restarting. Please file a new bug report against
dnsmasq with a detailed description of your problem.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed
/etc/resolv.conf containing 127.0.0.1 was correct, provided you have a
local nameserver running that listens at IP address 127.0.0.1.
In Ubuntu 12.10, the dnsmasq process controlled by NetworkManager
listens at 127.0.1.1, not at 127.0.0.1, so it wasn't NetworkManager that
registered 127.0.0.1 with
Not a NM problem; probably a dupe of #933723.
** Package changed: network-manager (Ubuntu) => bind9 (Ubuntu)
--
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/1098152
Title:
DNS
It's true. Looking at current NM src/nm-device.c line 1978:
static guint32
reserve_shared_ip (void)
{
guint32 start = (guint32) ntohl (0x0a2a0001); /* 10.42.0.1 */
guint32 count = 0;
This is upstream source code. Please file a bug report upstream.
https://bugzilla.gnome
To reduce administration, closed the report in Launchpad.
--
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/1098362
Title:
DHCP settings for network manager shared connection are
Possibly a driver issue
** Summary changed:
- WIFI disconnects then can not connect to any network
+ Wi-Fi disconnects then cannot connect to any network -- Broadcom BCM43224 bcma
** Package changed: network-manager (Ubuntu) => linux (Ubuntu)
--
You received this bug notification because you a
Possibly a driver issue
** Summary changed:
- network-manager fails to detect link status change
+ NetworkManager fails to detect link status change -- Intel 82577LM e1000e
** Description changed:
Steps to reproduce:
1.) Start Ubuntu, with LAN plugged in, login
- 2.) Verify Network Manag
Please run "apport-collect 1093622" to provide more information.
** Changed in: network-manager (Ubuntu)
Status: New => Incomplete
** Changed in: ac100
Status: New => Incomplete
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed
Possibly a driver issue
** Summary changed:
- NetworkManager disconnects wifi and can't reconnect
+ NetworkManager disconnects Wi-Fi and can't reconnect -- Broadcom BCM4312 wl
** Package changed: network-manager (Ubuntu) => linux (Ubuntu)
--
You received this bug notification because you are a
*** This bug is a duplicate of bug 1003842 ***
https://bugs.launchpad.net/bugs/1003842
** This bug has been marked a duplicate of bug 1003842
dnsmasq sometimes fails to resolve private names in networks with
non-equivalent nameservers
--
You received this bug notification because you are
** Summary changed:
- nm-applet doesn't appear to be connecting after resume
+ nm-applet doesn't appear to be connecting after resume -- Intel Centrino
Wireless-N 2230 iwlwifi
** Description changed:
- After I resume, nm-applet seems to go from disconnected to connected, not
giving any feedba
** Description changed:
The relevant part of the IPv6 routing table looks like this:
- fe80::/64 dev wlan0 proto kernel metric 256
- default via fe80::5054:ff:fe64:aad0 dev wlan0 proto static metric 1
+ fe80::/64 dev wlan0 proto kernel metric 256
+ default via fe80::5054:ff:fe64:aad0
*** This bug is a duplicate of bug 1004775 ***
https://bugs.launchpad.net/bugs/1004775
"This bug was fixed in the package network-manager -
0.9.6.0~git201207271115.edb85e9-0ubuntu1".
** Description changed:
- I have been getting random "site not found" errors when web browsing on the
campus
** Package changed: network-manager (Ubuntu) => network-manager-applet
(Ubuntu)
--
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/1100445
Title:
wireless network name in n
** Changed in: network-manager (Ubuntu)
Status: Invalid => 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/1098362
Title:
DHCP settings for network manager shared co
*** This bug is a duplicate of bug 1098362 ***
https://bugs.launchpad.net/bugs/1098362
** This bug has been marked a duplicate of bug 1098362
DHCP settings for network manager shared connection are hard-coded source,
should be editable
--
You received this bug notification because you ar
** Summary changed:
- Disables virtual machine manager's virbr0
+ NM disables virtual machine manager's virbr0
--
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/1099949
Title:
N
** Summary changed:
- Raring network manager msg false out of range WPA network
+ NetworkManager falsely reports WPA network "out of range"
** Description changed:
- On boot, Raring amd64 Broadcom BCM43225 the network manager correctly
- detects the network name, then network manager falsely rep
** Description changed:
- when I try to connect with connection named Hutch which is asocited with
- 3G dongle and HSPA connection.
+ I try to connect with connection named "Hutch" which is associated with
+ a 3G dongle and HSPA service.
- at first time it connects.but if it is disconnected and
** Package changed: network-manager (Ubuntu) => network-manager-applet
(Ubuntu)
--
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/1077079
Title:
network-manager doesn't di
** Summary changed:
- fails to connect to wifi for a while after suspend
+ Fails to connect to Wi-Fi several times after resume from suspend -- Ralink
RT3090 rt2800pci
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in
Possibly a driver issue.
** Summary changed:
- Wireless network stopped working after resume from suspend
+ Wireless network not working after resume from suspend -- Intel Centrino
Advanced-N 6235 iwlwifi
** Package changed: network-manager (Ubuntu) => linux (Ubuntu)
--
You received this bug
I see this too. Looking at the logs on my machine I see that the message
is printed once or twice per day.
** Changed in: network-manager (Ubuntu)
Status: New => Confirmed
** Summary changed:
- Unknown username "dnsmasq" in message bus configuration file
+ Message in /var/log/upstart/dbus
** Summary changed:
- network-manager: Connecting to a wifi network requires
org.freedesktop.NM.settings.modify.system privileges
+ network-manager: pkla file missing -- Connecting to a wifi network requires
org.freedesktop.NM.settings.modify.system privileges
--
You received this bug notifica
** Also affects: network-manager via
https://bugzilla.gnome.org/show_bug.cgi?id=692279
Importance: Unknown
Status: Unknown
--
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/
(For future reference) Reading the syslog I see 5 boots.
1. Jan 21 22:25:34
Kernel boots and dhclient starts and gets a reply. Seems that network-
manager is not installed yet.
2. Jan 21 22:41:32
Kernel boots and dhclient starts but doesn't get a reply right away.
Then there's a "NETDEV WATCHDO
Do you have connectivity on graphical login, just no indicator in the
menu bar?
--
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/1103042
Title:
network-manager service stopped a
** Summary changed:
- network-manager service stopped at boot
+ network-manager not started at boot after installing Ubuntu Server and then
ubuntu-desktop
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https:
I followed the instructions and couldn't reproduce (i.e., I *can* enter
the IP address at step 7).
** Summary changed:
- networkmanager stops accepting keyboard input
+ nm-applet stops accepting keyboard input
** Package changed: network-manager (Ubuntu) => network-manager-applet
(Ubuntu)
--
Y
Hmm. Do you have multiple user accounts on your system? Are you logged
in to an account other than the initial one?
--
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/1102317
Title
** Summary changed:
- GUI drops out when restarting networking services.
+ "sudo service networking restart" causes the GUI to crash
--
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/bu
I understand that it was once commonplace to do "/etc/init.d/networking
restart" but (the latter's Upstart replacement) "sudo restart
networking" is deprecated.
** Changed in: network-manager (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of
/etc/init/networking.conf is in ifupdown
** Package changed: network-manager (Ubuntu) => ifupdown (Ubuntu)
** Changed in: ifupdown (Ubuntu)
Status: Invalid => New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in
** Summary changed:
- wifi connection loss on Realtek RTL8191SEvA
+ Using NM, Wi-Fi disconnects with heavy traffic; doesn't happen with wicd or
Windows 7 -- Realtek RTL8191SEvA
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-man
Note: The ZTE MF 118 isn't listed upstream
https://live.gnome.org/NetworkManager/MobileBroadband
as supported, but the ZTE MF 110 is listed.
** Description changed:
- The connection is established properly and signal is strong, yet I cannot
access any website or other network service. Usin
Are the credentials in a file in /etc/NetworkManager/system-connections/
?
** Summary changed:
- network manager looses connection, reconnect not possible
+ NM loses connection and can't reconnect; "No keyring secrets" -- Intel
PRO/Wireless 2200BG ipw2200
--
You received this bug notification
*** This bug is a duplicate of bug 31286 ***
https://bugs.launchpad.net/bugs/31286
** This bug has been marked a duplicate of bug 31286
Displays repeated keyring dialogs on resume from suspend and login
--
You received this bug notification because you are a member of Desktop
Packages, wh
>From bug #1067555:
"I found to reproduce this bug by 2 ways:
1. When not connected to a secured (without password saved) wifi, try to
connect to the secured wifi (do not type password or do anything), go
take a rest, unlock computer and see a lot of nm-applet dialog.
2. When not connected to a
This bug needs to be reopened because there are new reports of the
problem.
--
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/31286
Title:
Displays repeated keyring dialogs on re
Update. The bug has been fixed, but not in Precise.
--
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/31286
Title:
Displays repeated keyring dialogs on resume from suspend and lo
*** This bug is a duplicate of bug 31286 ***
https://bugs.launchpad.net/bugs/31286
Reported fixed in quantal.
--
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/1067555
Title:
** Bug watch added: GNOME Bug Tracker #665503
https://bugzilla.gnome.org/show_bug.cgi?id=665503
** Changed in: network-manager
Importance: Medium => Unknown
** Changed in: network-manager
Status: Invalid => Unknown
** Changed in: network-manager
Remote watch: GNOME Bug Tracker #676
@Rob Gar EsP: Do you see the same symptoms as in bug #1104173?
** Package changed: network-manager (Ubuntu) => network-manager-vpnc
(Ubuntu)
** Summary changed:
- VPNC not working
+ NM-VPNC stopped working; Cisco client still works
--
You received this bug notification because you are a member
*** This bug is a duplicate of bug 366780 ***
https://bugs.launchpad.net/bugs/366780
** This bug is no longer a duplicate of bug 46123
Define priorities for different networks
** This bug has been marked a duplicate of bug 366780
Please provide a mechanism whereby Wi-Fi networks can be p
*** This bug is a duplicate of bug 366780 ***
https://bugs.launchpad.net/bugs/366780
** This bug is no longer a duplicate of bug 46123
Define priorities for different networks
** This bug has been marked a duplicate of bug 366780
Please provide a mechanism whereby Wi-Fi networks can be p
*** This bug is a duplicate of bug 366780 ***
https://bugs.launchpad.net/bugs/366780
** This bug is no longer a duplicate of bug 46123
Define priorities for different networks
** This bug has been marked a duplicate of bug 366780
Please provide a mechanism whereby Wi-Fi networks can be p
*** This bug is a duplicate of bug 366780 ***
https://bugs.launchpad.net/bugs/366780
** Changed in: network-manager (Ubuntu)
Status: Invalid => New
** This bug has been marked a duplicate of bug 366780
Please provide a mechanism whereby Wi-Fi networks can be prioritized
--
You rec
*** This bug is a duplicate of bug 366780 ***
https://bugs.launchpad.net/bugs/366780
** This bug is no longer a duplicate of bug 46123
Define priorities for different networks
** This bug has been marked a duplicate of bug 366780
Please provide a mechanism whereby Wi-Fi networks can be p
Quote from upstream report
(https://bugzilla.gnome.org/show_bug.cgi?id=359556):
There won't ever be user-defined priorities in NM. NM connects to the last
network you've connected to that it can find. When you connect, NM timestamps
the network, and it will first connect to the most recent netwo
I notice a possibly unrelated problem in your syslog. NM can't
communicate with its slave dnsmasq. To work around this, comment out
"dns=dnsmasq" in /etc/NetworkManager/NetworkManager.conf and then "sudo
restart network-manager".
Jan 18 23:12:50 samsung NetworkManager[987]: DNS: starting dnsmasq.
Please shut down; disconnect Ethernet cable; boot; enable Wi-Fi; attempt
to connect to Wi-Fi network (and presumably fail); plug in Ethernet
cable. Then run "apport-collect 1101534" to submit more information
including a useful syslog.
** Package changed: network-manager-applet (Ubuntu) => network
** Package changed: gnome-control-center (Ubuntu) => network-manager
(Ubuntu)
--
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/1034725
Title:
System will not create adhoc networ
> the current default installation wherein network-manager starts
> an instance of dnsmasq to act as a DHCP, DNS and TFTP server.
NetworkManager starts an instance of dnsmasq to act only as a non-
caching DNS nameserver forwarder. This instance listens only on the
loopback interface 127.0.1.1.
If
> In my network dnsmasq should not try to connect directly
> to the DNS root servers(which it looks like it does),
It doesn't. Dnsmasq only ever forwards DNS requests to other nameservers which
can do iterative queries.
> But there is nothing telling it to use them, since both
> /var/run/nm-d
By the way...
You wrote:
> [...]from /run/resolvconf/interface/lo.dnsmasq. The problem
> goes away after removing this file and restarting resolvconf
If you change something in resolvconf's database then don't restart
resolvconf; just do "sudo resolvconf -u".
--
You received this bug notificati
> the LTSP server defers to the router handling DHCP.
OK, I get it.
> I don't understand what you said about standalone dnsmasq
> conflicting with network-manager's instance of dnsmasq
> when /etc/dnsmasq.d/network-manager is removed.
When /etc/dnsmasq.d/network-manager is present, standalone d
Question: Why did everything work on your machine when standalone
dnsmasq wasn't in bind-interfaces mode but /etc/NM/NM.conf contained
"dns=dnsmasq"?
Hypothesis: Standalone dnsmasq started first; network-manager second. NM
tried to start NM-dnsmasq but this failed because of the address
conflict a
Ron: You report that manually-added-in-NetworkManager DNS search domain
names are not added to resolv.conf. Can you please give step-by-step
instructions for reproducing this bug (as Uqbar did)? Also, please post
the output of this command:
ls -l /etc/resolv.conf
** Changed in: network-manag
What was originally reported is expected behavior. NetworkManager starts
a dnsmasq process to forward DNS queries. NM puts (via resolvconf)
"nameserver 127.0.0.1" in resolv.conf and sends the upstream nameserver
addresses to the dnsmasq process over D-Bus.
On the other hand, if DNS search domain n
That the last syslog entries are made by ntpd doesn't necessarily mean
that the machine is hanging because of ntpd. It could be hanging at the
next step, for example.
Bug #999725 reports that ntp doesn't work properly when it is started
before NIS, which is not to be confused with DNS. Probably no
Public bug reported:
I get this error message in the syslog when I authenticate succesfully
in the screensaver.
---
ApportVersion: 2.6.1-0ubuntu6
Architecture: amd64
DistroRelease: Ubuntu 12.10
EcryptfsInUse: Yes
GnomeSessionIdleInhibited: No
GnomeSessionInhibitors: None
GsettingsGnomeSession:
o
apport information
** Attachment added: "GsettingsGnomePowerManager.txt"
https://bugs.launchpad.net/bugs/1085706/+attachment/3449987/+files/GsettingsGnomePowerManager.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-screensa
apport information
** Attachment added: "XorgLogOld.txt"
https://bugs.launchpad.net/bugs/1085706/+attachment/3449990/+files/XorgLogOld.txt
** Description changed:
I get this error message in the syslog when I authenticate succesfully
in the screensaver.
- Ubuntu 12.10.
- ---
+ ---
apport information
** Attachment added: "GsettingsGnomeScreensaver.txt"
https://bugs.launchpad.net/bugs/1085706/+attachment/3449988/+files/GsettingsGnomeScreensaver.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-screensave
apport information
** Attachment added: "Dependencies.txt"
https://bugs.launchpad.net/bugs/1085706/+attachment/3449985/+files/Dependencies.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-screensaver in Ubuntu.
https://bugs.
apport information
** Attachment added: "GsettingsGnomeLockdown.txt"
https://bugs.launchpad.net/bugs/1085706/+attachment/3449986/+files/GsettingsGnomeLockdown.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-screensaver in U
apport information
** Attachment added: "XorgLog.txt"
https://bugs.launchpad.net/bugs/1085706/+attachment/3449989/+files/XorgLog.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-screensaver in Ubuntu.
https://bugs.launchpad.
>there's still the unresolved question
> of whether re-enabling --strict-order
> will suffice as a workaround, since
> 12.10 relies on DBus to populate the
> nameservers. Is there any extra
> information on this?
Please try it and report back. :-)
(Put "strict-order" in a file in /etc/NetworkMa
This may also help:
http://www.thinkwiki.org/wiki/Installing_Ubuntu_11.04_(Natty_Narwhal)_on_a_ThinkPad_X220#Fix_for_hotkey_shortcomings
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-settings-daemon in Ubuntu.
https://bugs.launch
Simon in #49:
> It doesn't work [...] the order of servers given to the DBus
> interface isn't preserved internally
Aha, so the answer to my question
> Will switching on strict-order have the same effect
> now that nameserver addresses are sent over D-Bus?
(in comment #42) is "No". So switching
Try this. Edit the connection using the Connection Editor and set IPv4
Settings | Method to "Automatic (DHCP) addresses only" instead of
"Automatic (DHCP)". Make sure 8.8.8.8 is still included in the
"Additional DNS servers" field.
Another thing to try is to disable the local forwarding nameserver
What is the exact model number of your device?
Googling for your USB device IDs I found, e.g., this:
http://www.draisberghof.de/usb_modeswitch/bb/viewtopic.php?t=155.
** Changed in: network-manager (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a
** Description changed:
- After Upgrading from 11.04 to 12.10 the wifi Network named "300" isn't
- available anymore in networkmanager.
+ After upgrading from 11.04 to 12.10 the Wi-Fi network named "300" isn't
+ available any more in NetworkManager.
** Summary changed:
- wifi network named as nu
** Summary changed:
- No way to customize built-in dnsmasq configuration in 12.04
+ Please backport ability to customize NM-dnsmasq to 12.04
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpa
** Changed in: gnome-shell (Ubuntu)
Status: New => Invalid
** Description changed:
- Trying to connect using a GSM modem that lacks a SIM card does just give
- the user a general connection failure message without any hints about
- the missing SIM card.
-
- This can fool the user into thi
Could bug #1102092 be related?
** Package changed: network-manager (Ubuntu) => network-manager-applet
(Ubuntu)
--
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/1102317
Tit
>From WifiSyslog.txt (eth1 is the Wi-Fi interface):
Jan 31 19:50:37 samsung wpa_supplicant[1307]: eth1: Trying to associate with
2e:c7:9f:d6:30:40 (SSID='[...]' freq=2412 MHz)
Jan 31 19:50:37 samsung wpa_supplicant[1307]: eth1: Association request to the
driver failed
Jan 31 19:50:37 samsung Net
Possible wl driver problem
** Package changed: network-manager (Ubuntu) => linux (Ubuntu)
--
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/1101534
Title:
Cannot connect to WiFi
Am I correct in understanding that the Wi-Fi device in question is a
Ralink and the driver is rt2800usb?
** Summary changed:
- NM doesn't react to disconnect and connect commands for WiFi networks for
very long time (or ever)
+ NM doesn't react to disconnect and connect commands for WiFi network
What is the exact model name of your dongle.
Please reboot, reproduce the failure, connect and then run "apport-
collect 1099696" in a terminal to provide more information.
** Changed in: network-manager (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you
Please reboot and then run "apport-collect 1114600" to provide more
information about the affected system.
--
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/1114600
Title:
Wi-Fi
** Changed in: network-manager-applet (Ubuntu)
Status: New => Incomplete
--
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/1103809
Title:
nm-applet stops accepting
I can reproduce this.
** Changed in: network-manager-applet (Ubuntu)
Status: New => Confirmed
--
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/1099633
Title:
netw
Hi Simon.
Before I forget to ask: can you please update dnsmasq(8) to include
under "--strict-order" a description of what happens when nameserver
addresses are passed in via D-Bus instead of via a file?
You wrote,
> you can very easily provide the same behaviour - only pass the first
> nameserv
[...cont'd after "in order to fix"...] bug #1072899, dnsmasq will have
to be enhanced such that proposition #1 is true. But we can discuss the
details of that in bug #1072899.
There is a close analogy between the problem here (bug #1003842) and a problem
we have with avahi. Avahi resolves names
Simon wrote:
> Consider
[...]
> server=/google.com/3.3.3.3
> server=/google.com/4.4.4.4
[...]
> Queries sent to *google.com will be sent 3.3.3.3 or 4.4.4.4 in the
> same way as if strict order was set, ie, to 3.3.3.3 first, and only to
> 4.4.4.4 if 3.3.3.3 returns a SERVFAIL or REFUSED error, or do
Earlier there was some dispute about what the RFCs say about multiple
nameservers.
I found the following RFC which does have something to say about these
issues.
http://www.zoneedit.com/doc/rfc/rfc2182.txt
Here are a couple of passages...
Request for Comments: 2182
Category: Best Current Pr
The target milestone should be adjusted, I guess.
--
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/1003842
Title:
dnsmasq sometimes fails to resolve private names in networks wi
** Summary changed:
- problem in wifi network configuration
+ NM fails to recognize already configured Wi-Fi connection
--
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/1123829
T
The Huawei EC1260 is not listed upstream as a supported model
https://live.gnome.org/NetworkManager/MobileBroadband
Nevertheless, I found a bug report in the upstream bugzilla related to
this model.
https://bugzilla.gnome.org/show_bug.cgi?id=663535
** Bug watch added: GNOME Bug Tracker
** Package changed: network-manager (Ubuntu) => network-manager-applet
(Ubuntu)
--
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/1125016
Title:
Stacked menus unaccessible
*** This bug is a duplicate of bug 47379 ***
https://bugs.launchpad.net/bugs/47379
** This bug has been marked a duplicate of bug 47379
NM assigns a lower metric to the default route over wlan than ifup assigns
to the default route over eth.
--
You received this bug notification because
What version of netwok-manager do you have? I cannot reproduce the
problem with network-manager 0.9.7.995+git201301311547.17123fc-0ubuntu1.
Does upgrading to this version fix it for you?
** Changed in: network-manager (Ubuntu)
Status: New => Incomplete
--
You received this bug notificati
1 - 100 of 2047 matches
Mail list logo
