This is a serious issue for us, since it causes FAI to break. We can't
use 2.6.22 because it breaks unionFS, and we can't use earlier kernels
because the driver for the new intel network cards isn't in there.
The status says fix released but the packages linux-image from gutsy
are still broken.
This problem still existing in gutsy is a showstopper for us at the
moment. We want to upgrade from Dapper to Gutsy through FAI on about 100
desktops, but this bug is preventing us.
Please consider raising the priority of this bug to critical.
--
feisty and gutsy, amd64: kernel oops during boot
This is still broken in gutsy's vmlinuz-2.6.22-14-generic.
--
unionfs bug when on nfs
https://bugs.launchpad.net/bugs/137765
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-bugs@lists.ubuntu.com
On our current testing desktops (running feisty) it seems to work.
--
Network connection failed after booting (Dapper 6.0.6)
https://bugs.launchpad.net/bugs/54911
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs
I have had the same problem for quite a while, it seems like the cause
is the same as Bram Metsch. Unfortunately, i cannot apply the fix
provided in the STR you linked, so i am hoping to find a workaround. Is
there any way to sanitize a document before it's passed to IPP?
--
ipp jobs not purged;
This problem is dhcp3-client related. Setting a fixed ip-address in
/etc/network/interfaces is a workaround, and installing pump fixes the problem,
allowing me to use dhcp with these network controllers.
Is pump the default in edgy/festy by any chance, because dhcp-client has been
causing so
This problem is dhcp3-client related. Setting a fixed ip-address in
/etc/network/interfaces is a workaround, and installing pump fixes the
problem, allowing me to use dhcp with these network controllers.
Is pump the default in edgy/festy by any chance, because dhcp-client has
been causing so much
Pretty much default:
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).
# The loopback network interface
auto lo
iface lo inet loopback
# The primary network interface
auto eth0
iface eth0 inet dhcp
--
This is still a problem, at least for me. I've bought 2 new Dell desktop
machines to test, so hopefully they can replace our old custom-built
desktop machines. These machines are Dell optiplexes 745 with a broadcom
onboard network (exact type unknown atm, uses the tg3 driver)
However, with our
This is still an issue. I run dapper on all desktops here, and never had
this problem, until now.
Purchased 2 dell optiplex machines to use as test machines to replace
some old desktops, and when it boots there is no network up whatsoever.
The /etc/init.d/networking script hangs for quite a while
No, unfortunately this is a live system. I'd guess it would be fixed in
feisty, but we're not just ready yet to upgrade our server.
It will be replaced in a few months or so, so i'm hoping it's fixed in
edgy.
--
ipp jobs not purged; purging causes 100% cpu usage
https://launchpad.net/bugs/43352
It recommends IPP, but that's most likely because the printers have lpd
and tck disabled to prevent abuse.
They're all network printers, so sockets are no option. If the problem
persists i might switch to using ldp, but it's not preffered.
Just one question: does the snmp backend in feisty also
result of the snmp backend fyi:
[EMAIL PROTECTED]:~# /usr/lib/cups/backend-available/snmp
INFO: Using default SNMP Address @LOCAL
INFO: Using default SNMP Community public
network ipp://xxx.xxx.xxx.xxx:631/ipp HP Color LaserJet 4550 HP Color
LaserJet 4550 xxx.xxx.xxx.xxx
We are encountering the following bug as well. Every now and then 2 ipp
processes keep running on the cups server and eating 100% cpu time.
Stracing the processes show the following:
recvfrom(4, , 2048, 0, NULL, NULL)= 0
time(NULL) = 1173275152
recvfrom(4, ,
14 matches
Mail list logo
