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 sh
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 Ubun
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 co
*** 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
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://bug
*** 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 someth
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.
I
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 helpfu
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
* 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(STRI
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://
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
12 matches
Mail list logo
