*** This bug is a duplicate of bug 284298 ***
https://bugs.launchpad.net/bugs/284298
use resolvconf to setup defaults ... or use the connection editor to
set your custom DNS/gw ... its a bit tricky, b ut it works.
- Alexander
I already achieved the goal without using resolvconf or by
*** This bug is a duplicate of bug 284298 ***
https://bugs.launchpad.net/bugs/284298
On Sun, Mar 08, 2009 at 12:48:45PM -, Bassu Khan wrote:
*** This bug is a duplicate of bug 284298 ***
https://bugs.launchpad.net/bugs/284298
Unfortunately, this didn't work out like Mustafa said.
*** This bug is a duplicate of bug 284298 ***
https://bugs.launchpad.net/bugs/284298
I did pretty much all of the above, and the DNS always switched back
upon reboot. Until I found this tutorial right here. Never have that
problem anymore, PERIOD. I'm running Ubuntu 8.10 kernel 2.6.27-11
*** This bug is a duplicate of bug 284298 ***
https://bugs.launchpad.net/bugs/284298
I also spent a lot of time to figure out whats going with it...!
No wonder how many times I delete Auto eth0 or disable its automatic
connectivity, it gets recreated at the startup and changes to the static
*** This bug is a duplicate of bug 284298 ***
https://bugs.launchpad.net/bugs/284298
Unfortunately, this didn't work out like Mustafa said.
I do have a manual solution for that, but you know what, the crappy
NetworkManager sets /etc/resolv.conf's permissions back to normal and my start
up
*** This bug is a duplicate of bug 284298 ***
https://bugs.launchpad.net/bugs/284298
Sorry, but not working for me... :-(
[main]
plugins=ifupdown,keyfile
[ifupdown]
managed=true
I tried it with network-manager-gnome and it worked much bettera bit more
reliable...
--
wired
*** This bug is a duplicate of bug 284298 ***
https://bugs.launchpad.net/bugs/284298
rmedrado,
Your suggestion,
[ifupdown]
managed=true
is the only one that worked perfectly for me. I have been trying to get
a fix for this annoying bug for months. So thank you very much.
--
wired
*** This bug is a duplicate of bug 284298 ***
https://bugs.launchpad.net/bugs/284298
I had the same problem.
The procedures are:
Edit (as root) /etc/NetworkManager/nm-system-settings.conf:
1) Locate the lines
[ifupdown]
managed=false
2) And change the value for the attribute managed for
*** This bug is a duplicate of bug 284298 ***
https://bugs.launchpad.net/bugs/284298
Psy[H[] wrote:
*** This bug is a duplicate of bug 284298 ***
https://bugs.launchpad.net/bugs/284298
seems that vice versa 0_o
This one is earlier.
thats ok. thanks for pointing out though.
--
*** This bug is a duplicate of bug 284298 ***
https://bugs.launchpad.net/bugs/284298
seems that vice versa 0_o
This one is earlier.
--
wired connection settings are lost after reboot
https://bugs.launchpad.net/bugs/259214
You received this bug notification because you are a member of Ubuntu
any reason why this isnt a dupe of the MASTER bug 284298?
--
wired connection settings are lost after reboot
https://bugs.launchpad.net/bugs/259214
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
*** This bug is a duplicate of bug 284298 ***
https://bugs.launchpad.net/bugs/284298
** This bug has been marked a duplicate of bug 284298
MASTER cannot save auto connection as system settings without renaming the
connection
--
wired connection settings are lost after reboot
Here's what i did for wireless WPA(you have three options ):
A)
vim /etc/network/interfaces
add
auto wlan0
iface wlan0 inet dhcp
wpa-driver wext
wpa-conf /etc/wpa_supplicant/wpa_supplicant.conf
(the only issue is it leaves you're hard drive in a bad state i.g.
device resource
On Wed, Dec 17, 2008 at 02:29:47AM -, C David Rigby wrote:
Manually entering name server IP addresses into /etc/resolv.conf, or
installing the package resolvconf, works around the difficulty.
NetworkManager indicates there is no network connection (the ! symbol
is displayed by the applet)
On Tue, Dec 16, 2008 at 04:52:36PM -, Romano Giannetti wrote:
The workaround of deleting the auto-eth0 connection, creating a new one
and putting in it the correct HW address of the interface worked for me
(0.7~~svn20081018t105859-0ubuntu1.8.10.1). Really a nasty bug; lost
control over my
The workaround of deleting the auto-eth0 connection, creating a new one
and putting in it the correct HW address of the interface worked for me
(0.7~~svn20081018t105859-0ubuntu1.8.10.1). Really a nasty bug; lost
control over my office machine from home after a reboot...
--
wired connection
I found a simple work around that simply avoids NetworkManager without
removing it. I have not tried the workaround indicated above of deleting
the auto eth0 configuration from Networkmanager's connections list and
creating a new static configuration. In my case, eth0 is treated as
unmanaged by
I just don't want to install another version in vain like I did many
times in the past 70 days...
--
wired connection settings are lost after reboot
https://bugs.launchpad.net/bugs/259214
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
All of the others until now have been various release candidates and
source control snapshots. The one from 26 November is the actual
release package.
There are *many* changes in the code between our snapshots and now. I
can't tell from the ChangeLog if/when this issue got resolved, and
haven't
I've found deleting the auto connection, the making a new static one
from scratch works fine. It seems it's just the initial auto one that
has permission problems. Making a new one for me works fine even as a
system setting as it asked for sudo when confirming.
Hope this helps.
--
Sam Jackson /
...workaround did not survive reboot :(
waiting for new package.
--
wired connection settings are lost after reboot
https://bugs.launchpad.net/bugs/259214
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
I figured... Also waiting for new package version in the official
updates.
--
wired connection settings are lost after reboot
https://bugs.launchpad.net/bugs/259214
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
I've just tried this myself and its started working
(previously an auto connection was remade on boot up)
I don't know why the auto connection nuisance has gone away
but I'm most grateful that it has
Here's the steps I took, I deleted ALL connection
made 1 connection that was static with
On Sat, Dec 06, 2008 at 02:56:41PM -, Maurik wrote:
Hi all,
I tryed so many time to work around this bug that I'm not sure how I was able
to do that, anyway this is the procedure I used (as far as I remember):
1) edit the /etc/NetworkManager/nm-system-settings.conf file and change the
On Tue, Dec 09, 2008 at 10:25:57AM -, Vitor Lamas Gatti wrote:
Indeed, this IS a bug, because you can create a new connection, but you can't
set it to Auto Connect and System Settings.
Maybe the bug name could change the title, but it's still the same idea.
I'm sure this bug is annoying
I've talked to Dan Williams, the person that maintains this package in GNOME,
and he said that the latest version, released 27-Nov-2008, doesn't have this
bug.
You can find this version here:
http://ftp.gnome.org/pub/GNOME/sources/NetworkManager/0.7/
I couldn't manage to compile the source code
Wait a minute, if this bug is indeed fixed why is it not available in
the official updates ? huh ?! I check updates every single day and no
network-manager was updated so far... Can someone else confirm the
famous bug fix with this new version of the package PLEASE ?
--
wired connection settings
On Fri, Dec 12, 2008 at 08:49:07AM -, Miguel Telleria de Esteban wrote:
sirius56 escribió:
Static IP, dns settings etc get lost after a reboot. It gets back to
default (AUTO DHCP),
FYI, I find that the same Network Manager 0.7.0 bug exists for me in
Fedora 10, Gnome Desktop.
On Mon, Dec 15, 2008 at 01:57:31PM -, Noel J. Bergman wrote:
All of the others until now have been various release candidates and
source control snapshots. The one from 26 November is the actual
release package.
There are *many* changes in the code between our snapshots and now. I
Maybe I found workaround to disable automatic connection for default system
connections.
run nm-connection-editor from root:
sudo nm-connection-editor
you will gain root access to system connections, so you can disable autoconnect
for them.
user's connections are not accessible from root, so
Strange, but it is still not possible to create system connection from
root nm-connection-editor. System checkbox status for custom connection
cannot be saved.
--
wired connection settings are lost after reboot
https://bugs.launchpad.net/bugs/259214
You received this bug notification because you
after restart of NetworkManager and networking autoconnection checkbox
false status for system connections was saved.
--
wired connection settings are lost after reboot
https://bugs.launchpad.net/bugs/259214
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Changed in: network-manager (Ubuntu)
Status: Confirmed = Triaged
--
wired connection settings are lost after reboot
https://bugs.launchpad.net/bugs/259214
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
sirius56 escribió:
Static IP, dns settings etc get lost after a reboot. It gets back to
default (AUTO DHCP),
FYI, I find that the same Network Manager 0.7.0 bug exists for me in
Fedora 10, Gnome Desktop.
This bug has been around for a long time. Anyone have any idea of
how we can
Static IP, dns settings etc get lost after a reboot.
It gets back to default (AUTO DHCP),
FYI, I find that the same Network Manager 0.7.0 bug exists for me in
Fedora 10, Gnome Desktop.
This bug has been around for a long time. Anyone have any idea of how we can
give the Network Manager
Using network-manager 0.7.0-rc2 WITH network-manager-applet 0.7.0-rc2
from upstream
http://ftp.gnome.org/pub/GNOME/sources/NetworkManager/0.7/
http://ftp.gnome.org/pub/GNOME/sources/network-manager-applet/0.7/
seems to solve this issue. I have backported them in my PPA archive:
Indeed, this IS a bug, because you can create a new connection, but you can't
set it to Auto Connect and System Settings.
Maybe the bug name could change the title, but it's still the same idea.
I'm sure this bug is annoying a lot of people... sadly, I'm thinking
that Ubuntu 9.04 will have this
why do you try to edit or delete default connection?
just create new, it will not be lost.
--
wired connection settings are lost after reboot
https://bugs.launchpad.net/bugs/259214
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Because that seemed most logical and it let me do it.
If creating a new connection is a workaround, then I'll do it, but
that's still a bug IMO.
--
wired connection settings are lost after reboot
https://bugs.launchpad.net/bugs/259214
You received this bug notification because you are a member
I'm assuming it's the same as my problem:
Right click on Network Manager tray icon
Edit Connections
Wired
Auto eth0
Edit
IPv4 Settings
Method: Automatic (DHCP) addresses only
Enter two servers in the DNS servers field (e.g. 1.2.3.4,5.6.7.8)
Enter something in the Search Domains box
OK
Click on
Hi all,
I tryed so many time to work around this bug that I'm not sure how I was able
to do that, anyway this is the procedure I used (as far as I remember):
1) edit the /etc/NetworkManager/nm-system-settings.conf file and change the
parameter managed=false in managed=true (see below)
On Mon, Dec 01, 2008 at 12:34:30PM -, sirius56 wrote:
Psy[H[[,
Thank you for clear explanation.
The problem here is that you cannot edit Auto connections. So just
create new connectoins. This is a well known bug and I have to fix
that individually in a backport.
- Alexander
--
Psy[H[[,
Thank you for clear explanation.
--
wired connection settings are lost after reboot
https://bugs.launchpad.net/bugs/259214
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Connect automatically means this connection to be applied as soon as possible
after startup, without your assistance.
System settings means this connection is system-wide, not user's, so it is
accessible and can be turned on by any user, or even before any user login.
I see people who do not
In the Network Manager GUI, there are two boxes for checkmarks.
--Connect automatically
--System setting
Can someone please explain exactly what each of these options do?
--
wired connection settings are lost after reboot
https://bugs.launchpad.net/bugs/259214
You received this bug
I can't believe this buggy nm thing is still buggy and included with Ubuntu. Is
this a joke or what?
I had to fiddle for 30 minutes in order to have it asking me for credentials
and finally saving the configuration: how can one be sure the configuration now
will last?
What's the need for nm to
Manuel, I agree with you. This bug was first reported in August. It's
hard to complain about something that's free, but I wish a network-
manager maintainer would at least comment on why it is taking so long to
fix this bug and give some estimate of when the bug will be fixed.
Has anyone
I found a workaround... just created a new connection with my static IP. It
takes it about 30 seconds to figure out which connection to use, but then it
connects, and works fine thereafter. Its a minor annoyance to me, but to an
inexperienced user, it would be a severe headache.
- E
On Thu, Nov
Has anyone successfully disabled network manager and set up
/etc/network/interfaces manually as a temporary fix?
I think we are all using interfaces for quite a long time now ;-)
--
wired connection settings are lost after reboot
https://bugs.launchpad.net/bugs/259214
You received this bug
I agree,
I can actively use only one of my two interface cards, as the other
one does not resolve correctly. I ifdown and ifup the eppropriate
card msnually if want to use a particular card. Very annoying.
On Fri, Nov 21, 2008 at 8:06 PM, jokker [EMAIL PROTECTED] wrote:
I tried that but it
http://ftp.gnome.org/pub/GNOME/sources/NetworkManager/0.7/
--
wired connection settings are lost after reboot
https://bugs.launchpad.net/bugs/259214
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Better upadate Network Manager to latest version (0.7.0-rc2)
I built and installed this version of network-manager on my stock 8.10
system, and it screwed things up so that gnome could not launch
applications. So I uninstalled network-manager altogether and
configured manually in
I tried that but it doesn't work. I have two NICs and with both enabled
in interfaces I do not get DNS resolution. If only ONE (either) is
enabled it works, go figure...
--
wired connection settings are lost after reboot
https://bugs.launchpad.net/bugs/259214
You received this bug notification
2 jokker - this is bad idea. Better upadate Network Manager to latest
version (0.7.0-rc2)
--
wired connection settings are lost after reboot
https://bugs.launchpad.net/bugs/259214
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
where is this version ? it is not available on the official repos. Is it
on backport or proposed ?
--
wired connection settings are lost after reboot
https://bugs.launchpad.net/bugs/259214
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
On Thu, Oct 16, 2008 at 04:29:29PM -, Christian Kirbach wrote:
Citing Alex
you cannot save a auto generated connection. so you either have to rename
it or to create a new one. then it should work
This is important to know then.
Right. In fact read-only connections should be better
Can we all rollback to network-manager 0.6 on intrepid ? It used to work
soo well... Will it work with V0.6 ? Thank you
--
wired connection settings are lost after reboot
https://bugs.launchpad.net/bugs/259214
You received this bug notification because you are a member of Ubuntu
Bugs, which
Seriously, I can't believe that this annoying bug won't be fixed. 18
days have passed since Ubuntu 8.10 was released, and nothing was done.
Ok, you can configure everything in /etc/networks/interfaces, but where
is the user-friendly on that?
Somebody gave importance Medium. Medium? This is
Agreed, this has affected a large amount of people, just look at the amount of
duplicate bug reports!
I've had this issue since August and it's still a problem.
As a hack around I've had to disable auto-eth0 and setup another interface with
a static ip, but I have to log in to get it applied, so
Adjusting Importance to High according to the number of duplicates,
the fact that it affect a default ubuntu installation and due to the
/etc/network/interfaces workaround which is not accessible for a lot of
ubuntu users, specifically since nm does not support
/etc/network/interfaces anymore.
**
I can confirm that you can get the settings to save but you have to keep
fiddling till your asked for admin privileges, as has been mentioned.
It took me many times of clicking on/off of Connect Automatically -
OK and System setting - OK before this finally happened. My
manually configured
Auto eth0 will come back, because it is default config for specific card.
Problem is in gaining root privileges to save system-wide config.
In Hardy with NM from ppa everything in this area worked, so I could create new
config, assign it to specific card by mac-adress, then turn on system
]
To: [EMAIL PROTECTED]
Date: Wed, 12 Nov 2008 15:02:08 +
Subject: [Bug 259214] Re: wired connection settings are lost after reboot
Alexander, maby this bug is fixed in latest Network Manager 0.7.0-rc1 ?
http://ftp.gnome.org/pub/GNOME/sources/NetworkManager/0.7/
Can you, please build
I found that you have to delete all the auto entries, then select new
connection,
give it a name and select system tab.
Then go to the IPV4 tab and
manually enter all the IP, gateway, DNS etc and click OK
Once you reboot it's all there and the LAN connects on login.
I've already tried that
Alexander, maby this bug is fixed in latest Network Manager 0.7.0-rc1 ?
http://ftp.gnome.org/pub/GNOME/sources/NetworkManager/0.7/
Can you, please build it and upload to PPA?
--
wired connection settings are lost after reboot
https://bugs.launchpad.net/bugs/259214
You received this bug
OK, according this conversation, I set up eth0 with system interface
disabled, close the network-manager windows, open it again and set
system interface to enable. Only after that policy-tool asked me for
sudo password, so I think, that the problem is, that network-manager
does not update
I can confirm this bug. Problem persists even with latest updates.
Please, fix this.
--
wired connection settings are lost after reboot
https://bugs.launchpad.net/bugs/259214
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
I am also unable to configure nm to keep a static IP address on a wired
connection. Each reboot it changes back to dhcp.
--
wired connection settings are lost after reboot
https://bugs.launchpad.net/bugs/259214
You received this bug notification because you are a member of Ubuntu
Bugs, which is
On Wed, Oct 22, 2008 at 05:24:22AM -, Shirish Agarwal wrote:
Hi Alex,
so this would be right.
/etc/network/interfaces
auto lo
iface lo inet loopback
auth eth1
iface eth1 inet static
address 192.168.1.3
netmask 255.255.255.0
gateway 192.168.1.1
dns-nameserver
Hi Alex,
What do you know, it worked after couple of restarts, although most because of
the dns-nameserver thing the connection didn't work. I will try again.
Using sudo dhclient for the time being.
Yes, the connection is now called ifupdown (eth1)
Is there a way to name it in the file
Another query but unrelated, what is pan0 ?
--
wired connection settings are lost after reboot
https://bugs.launchpad.net/bugs/259214
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
scratch that last query, came to know pan0 are for bluetooth devices.
http://fedoraforum.org/forum/showthread.php?t=193187
--
wired connection settings are lost after reboot
https://bugs.launchpad.net/bugs/259214
You received this bug notification because you are a member of Ubuntu
Bugs, which
my comment above was half https://bugs.edge.launchpad.net/ubuntu/+source
/network-manager/+bug/259214/comments/29
Its a D-Link 502T ADSL router+modem. How I've set it up is computer
D-Link Ethernet Card (the other chipset/one is broken) ADSL
router+modem Internet.
--
wired connection
On Wed, Oct 22, 2008 at 12:34:20PM -, Shirish Agarwal wrote:
Hi Alex,
What do you know, it worked after couple of restarts, although most because
of the dns-nameserver thing the connection didn't work. I will try again.
Using sudo dhclient for the time being.
Yes, the connection
** Attachment added: generate-interfaces.txt
http://launchpadlibrarian.net/18761623/generate-interfaces.txt
--
wired connection settings are lost after reboot
https://bugs.launchpad.net/bugs/259214
You received this bug notification because you are a member of Ubuntu
Bugs, which is
On Tue, Oct 21, 2008 at 04:31:41AM -, Shirish Agarwal wrote:
Hi all,
I dunno much about stuff but I got this while restarting networking
(most of the times I think I'm on Auto DHCP but dunno how that works)
sudo /etc/init.d/networking restart
* Reconfiguring network
On Tue, Oct 21, 2008 at 05:49:15AM -, Shirish Agarwal wrote:
hmm... ok hunted around and got this file
/usr/share/doc/ifupdown/examples/generate-interfaces.pl.gz .
ran it and it gave whole lot of stuff which I have included as an
attachment
The main part I put in the
Hi Alex,
so this would be right.
/etc/network/interfaces
auto lo
iface lo inet loopback
auth eth1
iface eth1 inet static
address 192.168.1.3
netmask 255.255.255.0
gateway 192.168.1.1
dns-nameserver 192.168.1.1
Then tried this :-
sudo /etc/init.d/networking restart
*
Also changing there the dns-nameservers there but it didn't do anything.
I restarted the Network-Manager service and still it shows dhcp
connectivity .
Running into some other bugs, it seems dhcp is default for now, is this
how its going to be for times to come?
--
wired connection settings
Hi all,
I dunno much about stuff but I got this while restarting networking
(most of the times I think I'm on Auto DHCP but dunno how that works)
sudo /etc/init.d/networking restart
* Reconfiguring network interfaces...
Ok came to know that now /etc/network/interfaces also needs a dns-
nameserver . From what I understand they are the same as in the network-
applet right?
The DNS Servers where one puts stuff. This is what I've put there.
auto lo
iface lo inet loopback
auto eth1 inet static
address 192.168.1.2
ok again I had failure, I was not able to get it working through what I
tried above. Had to resort to
sudo dhclient
This is what it used for this time.
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 8
DHCPOFFER of 192.168.1.3 from 192.168.1.1
DHCPREQUEST of 192.168.1.3 on eth1 to
hmm... ok hunted around and got this file
/usr/share/doc/ifupdown/examples/generate-interfaces.pl.gz .
ran it and it gave whole lot of stuff which I have included as an
attachment
The main part I put in the /etc/network/interfaces
auto lo
iface lo inet loopback
iface eth1 inet static
On Thu, Oct 16, 2008 at 04:29:29PM -, Christian Kirbach wrote:
Citing Alex
you cannot save a auto generated connection. so you either have to rename
it or to create a new one. then it should work
This is important to know then.
Right. In fact read-only connections should be better
I'd claim this is clearly a showstopper and wonder why priority is still only
'medium'.
Someone must raise it.
I can see lost static configs after reboot, too, with latest intrepid updates
network-manager 0.7~~svn20081015
I have two Ethernet network cards, one DHCP and one static.
I
i just remove buggy Network Manager at all
and configure it manual ( /etc/networks/interfaces ) ..
all work fine! ;))
--
wired connection settings are lost after reboot
https://bugs.launchpad.net/bugs/259214
You received this bug notification because you are a member of Ubuntu
Bugs, which is
the route problem should be fixed in the follow up upload i did today.
--
wired connection settings are lost after reboot
https://bugs.launchpad.net/bugs/259214
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
Citing Alex
you cannot save a auto generated connection. so you either have to rename it
or to create a new one. then it should work
This is important to know then.
--
wired connection settings are lost after reboot
https://bugs.launchpad.net/bugs/259214
You received this bug notification
On Fri, Oct 10, 2008 at 01:11:58AM -, Saïvann Carignan wrote:
Alexander Sack : I just tested your latest update of network-manager
(0.7~~svn20081008t224042-0ubuntu1) on a clean intrepid installation and
this bug persist. This might be a policykit issue since when I try to
change the system
Alexander Sack
latest updated version of interpid.
problem exist.
--
wired connection settings are lost after reboot
https://bugs.launchpad.net/bugs/259214
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Alexander Sack : I just tested your latest update of network-manager
(0.7~~svn20081008t224042-0ubuntu1) on a clean intrepid installation and
this bug persist. This might be a policykit issue since when I try to
change the system configuration, I'm not asked for any passphrase. The
static IP
On Tue, Oct 07, 2008 at 07:37:07AM -, xoco wrote:
same problem ...
manual connection is broken ;(
Are you using hardy or intrepid? are you using NetworkManager 0.6 or
0.7?
- Alexander
--
wired connection settings are lost after reboot
https://bugs.launchpad.net/bugs/259214
You
same problem ...
manual connection is broken ;(
trick:
add AUTO eth0, save, edit, change to manual, save - solve, but i dunno what
happen after reboot ;)
--
wired connection settings are lost after reboot
https://bugs.launchpad.net/bugs/259214
You received this bug notification because you
** Changed in: network-manager (Ubuntu)
Importance: Undecided = Medium
--
wired connection settings are lost after reboot
https://bugs.launchpad.net/bugs/259214
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
workaround mentioned above by Dupond jean-Louis works for me to, so for
now i have working nonforgetting connection with NM 0.7 :)
--
wired connection settings are lost after reboot
https://bugs.launchpad.net/bugs/259214
You received this bug notification because you are a member of Ubuntu
Bugs,
i have the same issues. And i had /etc/NetworkManager/system-connections
folder, but when i change my settings, it gets applied when i choose
this connection from applet and it works.
but when i restart all settings are lost (and interface has changed to
dhcp - i had static settings) and i need
Interfaces get added automaticly in NetworkManager. But those u CAN'T
edit !
But there is a workaround :)
You have auto connection (Auto eth0 for example), you edit it, Tick off 'System
setting', and press OK.
Then u edit it again, and tick it on again.
From now on it will remember the settings
Kreso, /etc/network/interfaces are certainly never touched by
NetworkManager 0.7.
--
wired connection settings are lost after reboot
https://bugs.launchpad.net/bugs/259214
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
Made the dir and it doesn't solve the problem :(
Also upgraded to newest ppa version (where bug 261686 is fixxed) but
didn't solve it neither !
--
wired connection settings are lost after reboot
https://bugs.launchpad.net/bugs/259214
You received this bug notification because you are a member
Bug #261686 might be causing this.
--
wired connection settings are lost after reboot
https://bugs.launchpad.net/bugs/259214
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
1 - 100 of 103 matches
Mail list logo
