I have the same problem on 12.04.1 with tftpd-hpa version 5.2-1ubuntu1.
I have a single interface, eth0, which gets its address via DHCP. On
boot, tftpd-hpa fails to start with the "cannot resolve local IPv4 bind
address:0.0.0.0".
"sudo status tftpd-hpa" returns "tftpd-hpa start/running", but wi
I can confirm that this bug still occurs. Although I've been using this
configuration for ~6 months, it bit me today. This is on a box running
Ubuntu server, with two bonded interfaces. Bond0 failed to come up after
a reboot, while bond1 did come up. After I got onto the box via bond1, a
reboot wor
*** This bug is a duplicate of bug 148466 ***
https://bugs.launchpad.net/bugs/148466
** This bug has been marked a duplicate of bug 148466
Won't boot on a DELL Poweredge 2500
--
Install Lock-up Dell PowerEdge 2500
https://bugs.launchpad.net/bugs/131095
You received this bug notification b
I'd really like to run Ubuntu server 8.04 on a Dell Poweredge 2500, and
it would be great if it could be fixed for 8.04.1 - however, I see no
indication that it will be. So I'm going to have to install FreeBSD.
--
Won't boot on a DELL Poweredge 2500
https://bugs.launchpad.net/bugs/148466
You rece
The behaviour Wari Wahab described above is definitely a regression (and
I can confirm that it works on 7.10, using nm-applet 0.6.5; and the
interface is marked as static in /etc/network/interfaces) - it really
needs to continue to work in 8.04.
--
Can't use static ip address with network-manager
If it is not possible to set a static IP address in 8.04 - or possible
only by bringing up interfaces manually with ifconfig, then this is a
serious regression. Please fix this.
--
Can't use static ip address with network-manager (and thus no VPN connections
menu for static users)
https://bugs.l
*** This bug is a duplicate of bug 5364 ***
https://bugs.launchpad.net/bugs/5364
This _is_ a bug, not a "wouldn't-it-be-nice" wished-for feature. Network
manager should have remained an optional item to install, until it had
this capability. Once it became part of the standard install, useful
The problem is also present in Ubuntu 7.10, ssh version OpenSSH_4.6p1
Debian-5build1. The above suggestion of using "ssh -a" does not work for
me (and "ForwardAgent" is set to "no" anyway in ssh_conf). Either doing
"unset LANG" or editing /etc/ssh/ssh_config and commenting out the
"SendEnv" line do
*** This bug is a duplicate of bug 5364 ***
https://bugs.launchpad.net/bugs/5364
I agree with tilman's comment: this functionality should not depend on
whether the address is statically defined or provided via dhcp.
--
VPN menu not accessible when not using dhcp
https://bugs.launchpad.net/bu
I can confirm this bug is still present in Gutsy Desktop Beta1.
--
dell dimension 9200 - reboot doesn't work
https://bugs.launchpad.net/bugs/131292
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu
dmidecode (on Feisty) attached - pretty much the same as Krzysztof's,
except the BIOS is at a later revision (2.5.1 vs 2.5.0)...
** Attachment added: "dmidecode.txt"
http://launchpadlibrarian.net/9713047/dmidecode.txt
--
dell dimension 9200 - reboot doesn't work
https://bugs.launchpad.net/bu
OK, attached is the output of "lspci -vvnn" on my 9200 running Gutsy:
Linux ubuntu 2.6.22-10-generic #1 SMP Wed Aug 22 08:11:52 GMT 2007 i686
GNU/Linux
** Attachment added: "gutsy-9200-lspci.txt"
http://launchpadlibrarian.net/9290036/gutsy-9200-lspci.txt
--
dell dimension 9200 - reboot doesn
I can make it reboot successfully by adding "reboot=b" to the grub
kernel line in menu.lst:
kernel /boot/vmlinuz-2.6.20-16-generic
root=UUID=4efbf7b3-1188-4769-8e69-e9e131ac1936 ro quiet splash reboot=b
--
dell dimension 9200 - reboot doesn't work
https://bugs.launchpad.net/bugs/131292
Further confirmation of this problem on quad-core Dell 9200
[EMAIL PROTECTED]:~# uname -a
Linux nono 2.6.20-16-generic #2 SMP Fri Aug 31 00:55:27 UTC 2007 i686 GNU/Linux
[EMAIL PROTECTED]:~#
--
dell dimension 9200 - reboot doesn't work
https://bugs.launchpad.net/bugs/131292
You received this bug
The cause of the linux-restricted package not being updated was due to the
security-related lines in /etc/apt/sources.list only having the "main" flag
rather than "main restricted", i.e.
deb http://security.ubuntu.com/ubuntu dapper-security main
deb-src http://security.ubuntu.com/ubuntu dapper-se
Thanks - I've tried doing an update - nothing available. I guess it
could be a mirror thing, since my /etc/apt/sources.list file points to
the Australian mirrors. It's curious that they have the kernel updates
but not the linux-restricted updates.
--
6.06 with kernel update 2.6.15-25 loses ath0 w
Thanks - linux restricted modules are installed (I re-installed just in
case): however, it appears this package is kernel-version-specific
(linux-restricted-modules-2.6.15-23-386, and this is the latest
available according to synaptic). It looks as though Atheros support -
and support for other dev
OK - further info. It looks as though none of the madwifi or madwifi-ng
kernel modules are available with 2.6.15-25. /lib/modules/2.6.15-23-386
contains madwifi and madwifi-ng subdirectories, whereas
/lib/modules/2.6.15-25-386 does not. Has support been dropped?
--
6.06 with kernel update 2.6.15-
Public bug reported:
IBM Thinkpad T41p with Atheros wireless a/b/g card. Wireless works fine
with fresh install of 6.06 (kernel 2.6.15-23) from the 6.06 release live
CD. After applying recommended updates including kernel 2.6.15-25 and
rebooting, interface ath0 does not appear. The device manager
19 matches
Mail list logo
