devices configured manually in /etc/network/interfaces are not managed
by network manager by design. Solution: remove those entires from that
file (all except the lo device imo).
** Changed in: network-manager (Ubuntu)
Status: Incomplete = Invalid
--
[Hardy] Network can not be
I think the issue reported by initial reporter is now fixed.
for all the others, please don't post your info in this catch-all bug.
Instead, if you still have problems to connect in hardy, please file a
new bug with a title like: [CHIPSET] cannot connect to (ENCRYPT_METHOD)
network.
Attach your
ok, i think i misunderstood this bug. can anyone please update the
summary to comprehensible outline the issue you are seeing? Plesea don'
use codenames like weybridge without specifying what kind of chipset
that is.
Thanks,
- Alexander
** Changed in: network-manager (Ubuntu)
Status: Fix
I'm having a problem with NM itself, not drivers or networking. eth0
comes up manually (ifup eth0). wlan0 comes up fine manually, or with
wifi-radar.
Hardy heron 8.04 from dvd iso, apt-get update 31 Mar. Rm'd all .gconf*
.gnome* subdirs; removed, installed network-manager, rebooted, same
result.
I encountered the same problem in my axioo notebook Model: M72SR/Neon
TVS612PW
I've successfully configure the LAN interface manually (Manual
Configuration), but couldn't activate it.
However the classic way below worked like charm :
# ifconfig eth0 192.168.10.10 up
# route add default gw
I encountered the same problem in my axioo notebook Model: M72SR/Neon
TVS612PW
I've successfully configure the LAN interface manually (Manual
Configuration), but couldn't activate it.
However the classic way below worked like charm :
# ifconfig eth0 192.168.10.10 up
# route add default gw
This bug still occurs on Weybridge with Hardy Beta x86_64.
--
[Hardy] Network can not be configured through the NetworkManager
https://bugs.launchpad.net/bugs/178703
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
Thank you for fixing network-manager ( all libhal hal deps issues )
Its working fine for me now
--
[Hardy] Network can not be configured through the NetworkManager
https://bugs.launchpad.net/bugs/178703
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Hi , i have the same problem , wireless would not connect , i'm using
b43 , i was told this is a libhal1 issue but i am ready using the newest
version
cat /etc/network/interfaces
auto lo
iface lo inet loopback
apt-cache policy libhal1 hal
libhal1:
Installed: 0.5.11~rc2-1ubuntu2
Hi Guys ,
I did remove networ-manager and was able to connect manually , however the fan
(CPU) is still very high , i did not try a diff kernel
this is my uname -a uname -a
Linux mawi 2.6.24-12-rt #1 SMP PREEMPT RT Thu Mar 13 00:49:29 UTC 2008 i686
GNU/Linux
--
[Hardy] Network can not be
I'm getting a problem which I think is related:
with an updated Hardy, the wifi connect button is grayed out in NM, with wifi
button on or off.
This only happens with kernels 2.6.24-12-generic and 2.6.24-12-386 .
I had to install in order to install VirtualBox. I'd even see that as a blocker
Same here.
After upgrading to network-manager 0.6.6 I can't connect as usual to ppp0 with
nm-applet (left-click ...connect ppp0...)
I've also tried to manually edit my configuration but I receive this error
message:
the configuration could not be saved /n You are not allowed to modify the
$ /bin/check-foreground-console echo yes
yes
If it works as I would imagine, which is to say it returns true when it should
be true, it's working for me :P
Try this test and see what happens, if you get no output then it returned false.
--
[Hardy] Network can not be configured through the
please post your /etc/network/interfaces as well.
--
[Hardy] Network can not be configured through the NetworkManager
https://bugs.launchpad.net/bugs/178703
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing
Will do when I arrive home, but there's not much on it, just the loop
interface IIRC. No mention of eth0 or eth1.
My problem has to do with dbus or hal permissions. Using the applets (gnome
or kde) under sudo works well...
On 06/02/2008, Alexander Sack [EMAIL PROTECTED] wrote:
please post your
OK,
normal users have to be at the console (please verify that this is in
your dbus policy).
the script used to test that is /bin/check-foreground-console ... maybe
check that this works properly if you are a normal user.
--
[Hardy] Network can not be configured through the NetworkManager
Hi Alexander,
The script doesn't produce any output, run as a normal user and through
sudo. Is this good or bad? lol
Cheers,
Luis
On 06/02/2008, Alexander Sack [EMAIL PROTECTED] wrote:
OK,
normal users have to be at the console (please verify that this is in
your dbus policy).
the script
Is it connected to this bug?
https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/172616
--
[Hardy] Network can not be configured through the NetworkManager
https://bugs.launchpad.net/bugs/178703
You received this bug notification because you are a member of Ubuntu
Bugs, which
Hardy Alpha 4 on compaq Presario v6000, intel 3945 wireless
Network manager can't configure the network settings but I was able to
configure it from the command line using only these commands:
sudo iwconfig wlan0 essid myessid key myWEPkey
sudo dhclient
This seems to be a problem with network
19 matches
Mail list logo
