[Bug 570828] Re: gnome-network-admin on UbuntuStudio doesnt allow to configure either wired networks or wireless
sudhir, See my posts above. In post #14 I give a command you can run on the command line which should get networking up and going. This solution is only temporary. It does not carry over on reboot. You should now be able to update packages. If the issue is fixed in the update packages, you should be able to go in and configure a network interface. In post #15 I give a more permanent fix. If the updates don't fix the problem you can use this one. -- gnome-network-admin on UbuntuStudio doesnt allow to configure either wired networks or wireless https://bugs.launchpad.net/bugs/570828 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-system-tools in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 570828] Re: gnome-network-admin on UbuntuStudio doesnt allow to configure either wired networks or wireless
Yes, actually, my other machines are are Kubuntu Lucid, the KDE flavor of Ubuntu. However, I did boot a regular Ubuntu Lucid live CD disc on the machine that is now running Lucid Studio and the same was true, no entries other than 'lo' in '/etc/network/interfaces'. -- gnome-network-admin on UbuntuStudio doesnt allow to configure either wired networks or wireless https://bugs.launchpad.net/bugs/570828 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-system-tools in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 570828] Re: gnome-network-admin on UbuntuStudio doesnt allow to configure either wired networks or wireless
Also, adding the following to '/etc/network/interfaces' brings the interface up on boot. However, I'm not sure this is the 'right' way to fix the problem since my other Lucid machines do no have this entry. auto eth0 iface eth0 inet dhcp -- gnome-network-admin on UbuntuStudio doesnt allow to configure either wired networks or wireless https://bugs.launchpad.net/bugs/570828 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-system-tools in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 580744] Re: Broadcom BCM57780 Enet broken in Lucid Studio
*** This bug is a duplicate of bug 570828 *** https://bugs.launchpad.net/bugs/570828 Also, adding the following to '/etc/network/interfaces' brings the interface up on boot. However, I'm not sure this is the 'right' way to fix the problem since my other regular Lucid machines do no have this entry. auto eth0 iface eth0 inet dhcp -- Broadcom BCM57780 Enet broken in Lucid Studio https://bugs.launchpad.net/bugs/580744 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-system-tools in ubuntu (via bug 570828). -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 570828] Re: gnome-network-admin on UbuntuStudio doesnt allow to configure either wired networks or wireless
I think I reported the same bug (#580744). In my case with a wired interface I am able to run 'sudo dhclient eth0' to get my network interface up and running with a dynamic ip address. -- gnome-network-admin on UbuntuStudio doesnt allow to configure either wired networks or wireless https://bugs.launchpad.net/bugs/570828 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-system-tools in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 580744] Re: Broadcom BCM57780 Enet broken in Lucid Studio
*** This bug is a duplicate of bug 570828 *** https://bugs.launchpad.net/bugs/570828 Turns out in my case running 'sudo dhclient eth0' configures the interface. I am using a wired interface. Not sure if this is holds true for others reporting in the other ticket. Bottom line, there's something broken in the released Ubuntu STUDIO 10.04 distro. -- Broadcom BCM57780 Enet broken in Lucid Studio https://bugs.launchpad.net/bugs/580744 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-system-tools in ubuntu (via bug 570828). -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 548891] Re: keyboard input broken due to invalid "SKIP" keyboard model
Martin, To clarify my post above, note that I got "SKIP" from the 'xprop' command above ***after I was logged into a gnome session***. I cannot get to a text console from gnome login screen using CTL+ALT+F1. I had to login first, then CTL+ALT+F1 to a text console, then run the 'xprop' command. If I run the 'xprop' command in a Gnome terminal window within a logged in gnome session, I get 'SKIP' as well. dpkg-recongure + reboot seems to fix the problem. I now have 'pc101' where 'SKIP' was before on the 'xprop' output. -- keyboard input broken due to invalid "SKIP" keyboard model https://bugs.launchpad.net/bugs/548891 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 548891] Re: keyboard input broken at gnome login prompt after package updates
One further note to the developer, I did not specify in my original post that I was using 64-bit Ubuntu as the guest OS and XP 32-bit as the host OS. VMWare Player 3.0.1 build-227600 Host OS: Windows XP SP3 (32-bit) Guest OS: Ubuntu 10.04 Beta (64-bit), Kernel 2.6.32-17-generic It may be helpful for the developer if the others chime in with 32/64-bit specifics on the guest/host OS they're using. -- keyboard input broken at gnome login prompt after package updates https://bugs.launchpad.net/bugs/548891 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 548891] Re: keyboard input broken at gnome login prompt after package updates
Charles, There's a user in a forum at the link below that had similar behavior regarding the on-screen keyboard not working. This user said the on- screen keyboard would come up, then close immediately. If they left it alone for 15 minutes after boot, then they can get the on-screen keyboard to work. That's not really a practical solution ongoing, but it may get you past the hump for now if it works. http://ubuntuforums.org/showthread.php?p=9022898#post9022898 -- keyboard input broken at gnome login prompt after package updates https://bugs.launchpad.net/bugs/548891 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 548891] Re: keyboard input broken at gnome login prompt after package updates
* keyboard layout: I have to be logged in via the on-screen keyboard in order to do the Ctrl+Alt+F1. After logging in and Ctrl+Alt+F1 to get the terminal screen I logged in and executed the requested 'sudo DISPLAY=:0 xprop -root |grep NAMES.S' command. Here is the output: _XKB_RULES_NAMES(STRING) = "evdev", "SKIP", "us", "", "terminate:ctrl_alt_bksp" * plymouth (splash screen): I have to be logged in in order to get a Ctrl+Alt+F1 text terminal, if I go back (i.e. Ctrl+Alt+F7), I get back to my logged in session where the keyboard works normally(as it did before I went to the text terminal). If I wait long enough before going back from the text terminal I get the Ubuntu screensaver password dialog and I am able to type in my password there without problem. Ctrl+Alt+F8 from the text terminal goes to a blank text screen with a blinking cursor, but doesn't respond to any keyboard input. Interesting side note: If I login, Ctrl+Alt+F1 to a text terminal, then resize my vmware window, it goes to the Ubuntu login screen, however, the keyboard input still doesn't work. "sudo apt-get purge plymouth" and a reboot did nothing to resolve the issue. * libxklavier when changing the password: Keyboard does not work before selecting a user. Cannot cursor up/down to select menu items after clicking power button icon. Cannot enter anything after selecting 'Other' user. 'Cap Lock' and 'Num Lock' do nothing. -- keyboard input broken at gnome login prompt after package updates https://bugs.launchpad.net/bugs/548891 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 548891] Re: keyboard input broken at gnome login prompt after package updates
Oops, I missed part of your first set of questions. The 'caps lock' and 'num lock' keys do not appear to do anything while at the Ubuntu login screen. The indicator LEDs do not respond to pressing the respective keys. -- keyboard input broken at gnome login prompt after package updates https://bugs.launchpad.net/bugs/548891 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 548891] Re: keyboard input broken at gnome login prompt after package updates
After getting logged in there are no issues at all with the keyboard. I only see the problem at the login screen. 1) The keyboard does not appear to react at all to key presses at the Ubuntu login screen. 2) I cannot Ctrl+Alt+F1 to get to a console when booted to the login screen 3) During a normal boot if I hit keys while it is booting I can see those key presses output to the terminal before it switches to the Ubuntu splash screen 4) booting in recovery mode I can navigate the text 'Recovery Menu' and drop into a root shell and the keyboard works fine. 5) I have not tried uninstalling the vmware guest tools, but I have upgraded the kernel twice, which breaks the vmware tools (i.e. they are not compiled to work with the new kernel yet) and requires you to re-run the tools config program. After installing the new kernel and rebooting the vmware tools are not running. The same keyboard problem is observed. I login and reconfigure the tools for the new kernel and get them up and running, then if I logout or reboot at this point, I see the same keyboard problem when I get back to the login screen. 6) keyboard input seems to work fine before the login screen and after logging in. I just doesn't work at the Ubuntu login screen. >From the link someone posted above and a similar post I found on the vmware site (link below), others are seeing the problem as well. http://communities.vmware.com/message/1503455#236418 (note the original post may not be related, but a few of the later posts look like the same situation I describe) -- keyboard input broken at gnome login prompt after package updates https://bugs.launchpad.net/bugs/548891 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
