Re: Hardy Alpha-3 networking
The problem shown below appears to have been resolved with tonight's update. tnx -rich On Jan 15, 2008 9:39 PM, Richard Mancusi [EMAIL PROTECTED] wrote: On Jan 15, 2008 8:40 PM, Richard Mancusi [EMAIL PROTECTED] wrote: On Jan 15, 2008 6:43 PM, Emilio Pozuelo Monfort [EMAIL PROTECTED] wrote: (``-_-´´) -- Fernando wrote: On Monday 14 January 2008 17:14:29 Brian Murray wrote: You should have to authenticate before modifying the network configuration. On my Hardy systems and a daily build of the Live CD, there is an Unlock button and selections remain greyed out until I unlock the application. If your system is fully up to date and the Unlock button is not there then you should submit a bug report. Your issues regarding changing the network configuration are probably a direct result of your not being authenticated. Thanks, I'm up to date, and using the menus, I just get a full grayed window and cant manage my networks options. If I try the old Network Monitor 2.12.1, it just says that the interface (either and both eth0 and eth1) doesnt exist. That sounds like bug 176060. Now that gnome-system-tools uses PolicyKit, you need to run it as a normal user, and not through gksu. Could you verify that you have network-manager-gnome 0.6.5-0ubuntu11, which fixed this issue, and that running 'gksu network-admin' keeps it greyed out, and that running 'network-admin' you can unlock it? Regards, Emilio Tonight's upgrade included several PolicyKit pkgs and I did verify that I am running network-manager-gnome 0.6.5-0ubuntu11 and network-manager 0.6.5-0ubuntu17. Now clicking on Unlock yields a window stating: Could not authenticate An unexpected error has occurred. This occurs by simply clicking on the Unlock button - not given the chance to enter a password. -rich I need to reply to my own email to add info. I attempted to re-start a service and received the same error - so it has nothing to do with networking but rather authentication. You had already assumed that, I am simply proving it. System/Administration/Services click on Unlock and receive the following message Could not authenticate An unexpected error has occurred. -rich -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
Re: Hardy Alpha-3 networking
On Monday 14 January 2008 17:14:29 Brian Murray wrote: You should have to authenticate before modifying the network configuration. On my Hardy systems and a daily build of the Live CD, there is an Unlock button and selections remain greyed out until I unlock the application. If your system is fully up to date and the Unlock button is not there then you should submit a bug report. Your issues regarding changing the network configuration are probably a direct result of your not being authenticated. Thanks, I'm up to date, and using the menus, I just get a full grayed window and cant manage my networks options. If I try the old Network Monitor 2.12.1, it just says that the interface (either and both eth0 and eth1) doesnt exist. -- BUGabundo :o) (``-_-´´) http://Ubuntu.BUGabundo.net Linux user #443786GPG key 1024D/A1784EBB My new micro-blog @ http://BUGabundo.net ps. My emails tend to sound authority and aggressive. I'm sorry in advance. I'll try to be more assertive as time goes by... signature.asc Description: This is a digitally signed message part. -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
Re: Hardy Alpha-3 networking
(``-_-´´) -- Fernando wrote: On Monday 14 January 2008 17:14:29 Brian Murray wrote: You should have to authenticate before modifying the network configuration. On my Hardy systems and a daily build of the Live CD, there is an Unlock button and selections remain greyed out until I unlock the application. If your system is fully up to date and the Unlock button is not there then you should submit a bug report. Your issues regarding changing the network configuration are probably a direct result of your not being authenticated. Thanks, I'm up to date, and using the menus, I just get a full grayed window and cant manage my networks options. If I try the old Network Monitor 2.12.1, it just says that the interface (either and both eth0 and eth1) doesnt exist. That sounds like bug 176060. Now that gnome-system-tools uses PolicyKit, you need to run it as a normal user, and not through gksu. Could you verify that you have network-manager-gnome 0.6.5-0ubuntu11, which fixed this issue, and that running 'gksu network-admin' keeps it greyed out, and that running 'network-admin' you can unlock it? Regards, Emilio signature.asc Description: OpenPGP digital signature -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
Re: Hardy Alpha-3 networking
On Jan 15, 2008 6:43 PM, Emilio Pozuelo Monfort [EMAIL PROTECTED] wrote: (``-_-´´) -- Fernando wrote: On Monday 14 January 2008 17:14:29 Brian Murray wrote: You should have to authenticate before modifying the network configuration. On my Hardy systems and a daily build of the Live CD, there is an Unlock button and selections remain greyed out until I unlock the application. If your system is fully up to date and the Unlock button is not there then you should submit a bug report. Your issues regarding changing the network configuration are probably a direct result of your not being authenticated. Thanks, I'm up to date, and using the menus, I just get a full grayed window and cant manage my networks options. If I try the old Network Monitor 2.12.1, it just says that the interface (either and both eth0 and eth1) doesnt exist. That sounds like bug 176060. Now that gnome-system-tools uses PolicyKit, you need to run it as a normal user, and not through gksu. Could you verify that you have network-manager-gnome 0.6.5-0ubuntu11, which fixed this issue, and that running 'gksu network-admin' keeps it greyed out, and that running 'network-admin' you can unlock it? Regards, Emilio Tonight's upgrade included several PolicyKit pkgs and I did verify that I am running network-manager-gnome 0.6.5-0ubuntu11 and network-manager 0.6.5-0ubuntu17. Now clicking on Unlock yields a window stating: Could not authenticate An unexpected error has occurred. This occurs by simply clicking on the Unlock button - not given the chance to enter a password. -rich -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
Re: Hardy Alpha-3 networking
On Jan 15, 2008 8:40 PM, Richard Mancusi [EMAIL PROTECTED] wrote: On Jan 15, 2008 6:43 PM, Emilio Pozuelo Monfort [EMAIL PROTECTED] wrote: (``-_-´´) -- Fernando wrote: On Monday 14 January 2008 17:14:29 Brian Murray wrote: You should have to authenticate before modifying the network configuration. On my Hardy systems and a daily build of the Live CD, there is an Unlock button and selections remain greyed out until I unlock the application. If your system is fully up to date and the Unlock button is not there then you should submit a bug report. Your issues regarding changing the network configuration are probably a direct result of your not being authenticated. Thanks, I'm up to date, and using the menus, I just get a full grayed window and cant manage my networks options. If I try the old Network Monitor 2.12.1, it just says that the interface (either and both eth0 and eth1) doesnt exist. That sounds like bug 176060. Now that gnome-system-tools uses PolicyKit, you need to run it as a normal user, and not through gksu. Could you verify that you have network-manager-gnome 0.6.5-0ubuntu11, which fixed this issue, and that running 'gksu network-admin' keeps it greyed out, and that running 'network-admin' you can unlock it? Regards, Emilio Tonight's upgrade included several PolicyKit pkgs and I did verify that I am running network-manager-gnome 0.6.5-0ubuntu11 and network-manager 0.6.5-0ubuntu17. Now clicking on Unlock yields a window stating: Could not authenticate An unexpected error has occurred. This occurs by simply clicking on the Unlock button - not given the chance to enter a password. -rich I need to reply to my own email to add info. I attempted to re-start a service and received the same error - so it has nothing to do with networking but rather authentication. You had already assumed that, I am simply proving it. System/Administration/Services click on Unlock and receive the following message Could not authenticate An unexpected error has occurred. -rich -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
Re: Hardy Alpha-3 networking
On Sunday 13 January 2008 05:45:22 Richard Mancusi wrote: Desktop i386 install Is the following a bug or can anyone change network settings via System/Administration/Network And can you verify it really changed by looking in the appropriate file. I have experience this since late alpha 2. -- BUGabundo :o) (``-_-´´) http://Ubuntu.BUGabundo.net Linux user #443786GPG key 1024D/A1784EBB My new micro-blog @ http://BUGabundo.net ps. My emails tend to sound authority and aggressive. I'm sorry in advance. I'll try to be more assertive as time goes by... signature.asc Description: This is a digitally signed message part. -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
Re: Hardy Alpha-3 networking
On Sat, Jan 12, 2008 at 11:45:22PM -0600, Richard Mancusi wrote: Desktop i386 install Is the following a bug or can anyone change network settings via System/Administration/Network And can you verify it really changed by looking in the appropriate file. You should have to authenticate before modifying the network configuration. On my Hardy systems and a daily build of the Live CD, there is an Unlock button and selections remain greyed out until I unlock the application. If your system is fully up to date and the Unlock button is not there then you should submit a bug report. Your issues regarding changing the network configuration are probably a direct result of your not being authenticated. Thanks, -- Brian Murray @ubuntu.com signature.asc Description: Digital signature -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
Re: Hardy Alpha-3 networking
On Jan 14, 2008 11:14 AM, Brian Murray [EMAIL PROTECTED] wrote: On Sat, Jan 12, 2008 at 11:45:22PM -0600, Richard Mancusi wrote: Desktop i386 install Is the following a bug or can anyone change network settings via System/Administration/Network And can you verify it really changed by looking in the appropriate file. You should have to authenticate before modifying the network configuration. On my Hardy systems and a daily build of the Live CD, there is an Unlock button and selections remain greyed out until I unlock the application. If your system is fully up to date and the Unlock button is not there then you should submit a bug report. Your issues regarding changing the network configuration are probably a direct result of your not being authenticated. Thanks, -- Brian Murray @ubuntu.com The Unlock button is there and works exactly as you state ... all greyed out until my password is accepted. However, I still get the same results. Any change sends the gui into a status bar loop - back and forth never stopping. I killed it. I was curious to see if the Unlock button was actually doing anything so open it back up and fed it the wrong password. It was refused. Opened the Details tab hoping to find an error but it only states: Application: /usr/bin/network-admin Action: org.freedesktop.systemtoolsbackends.set My system was up to date, but there were more updates tonight. The following occurred: Could not install 'libflickrnet2.1.5-cil' Could not install the upgrades. The upgrade aborts now. Your system could be in an unusable state. A recovery will run now (dpkg --configure -a) Re-running Update Manager showed the following 5 updates remaining. evolution, evolution-common, evolution-plugins, gdb, libglib2.0-0 I tried Network Settings again - same problems, nothing changed. Since you are not experiencing this problem it implies that there is something different between our systems. Either you are benefiting from residual, non-clean install data or I am missing something. Is it possible for me to get a download of exactly what you are using? I would be happy to test it with a clean installation. -rich -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
Hardy Alpha-3 networking
Desktop i386 install Is the following a bug or can anyone change network settings via System/Administration/Network And can you verify it really changed by looking in the appropriate file. Install took a DHCP address. When completed I tried to change the settings to a static with different DNS, etc. The box came up stating Changing Interface Configuration and the status bar went back and forth for 10 min before I killed it. In order to properly config my network connection it was necessary to edit: /etc/network/interface /etc/resolv.conf /etc/hosts Notes: 1. This is the same problem I had with Alpha-2. 2. Same results installing on 3 different computers at two locations 20 miles apart. -rich -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
