False alarm, the client being unable to connect to the NBD server was
actually related to this problem:
https://bugs.launchpad.net/ltsp/+bug/589034
--
UDHCPC not fetching lease from Windows DHCP server
https://bugs.launchpad.net/bugs/505916
You received this bug notification because you are a me
I found with ltsp-server version 5.2.1-0ubuntu9 on Ubuntu 10.4 I still
needed to remove the "-c" option because when the clientid was specified
as a kernel parameter the client did receive an IP address but was not
able to connect to the nbd-server?
To rebuild the initrd RAMDISK imagine I needed t
Hi Gadi
I've changed the UDHCP client ID to "LTSP-i386" and the LTSP clients
continued to work.
My concern with making the client ID a kernel parameter is that its very
unlikely that anyone would think to have to add an ID to the kernel
parameters in order to be able to boot their Ubuntu thin cli
Hi
I'm running Ubuntu 9.10 with all the latest updates (LTSP version
5.1.90-0ubuntu3), using a Windows 2003 RC1 server as the DHCP.
Ubuntu 8.10 and 9.04 worked fine with the Windows DHCP server, upgraded
to 9.10 and it couldn't even fetch an IP address from the Windows DHCP
server.
--
UDHCPC no
Public bug reported:
Only the first terminal to boot is assigned a lease. Other terminals are
unable to.
By changing the following line in /scripts/init-premount/udhcp in the
initrd file:
if udhcpc -n -c '' -s /tmp/dhcp-script.sh -i $i $clientid_param
$hostname_param $ip_param > /dev/null; then
Guess you could run a supported Linux distribution as a XEN virtualized
server in Ubuntu, or just use a supported distribution for the Zimbra
server side?
--
missing message in the inbox folder
https://bugs.launchpad.net/bugs/160142
You received this bug notification because you are a member of U
I am having the same problem with 9.04, just ran a default ltsp-build-
client, then ssh into the thin client and see this:
# cat /etc/resolv.conf
cat: /etc/resolv.conf: Input/output error
# ls -l /etc/resolv.conf
-- 1 root root 0 2009-05-13 12:34 /etc/resolv.conf
#
Also noticed this in
I'd imagine the reason these problems are receiving so little attention
is because Zimbra Desktop is a far better MUA than Evolution, and a
Zimbra server now fully integrates into an Exchange environment.
--
missing message in the inbox folder
https://bugs.launchpad.net/bugs/160142
You received t
I'm experiencing similar problems with Exchange server 2003, Evolution
2.24.3 using the Exchange Plugin on Ubuntu 8.10.
There seems to be three issues regarding missing emails:
1. A few times a month a few emails can be seen in OWA but not in Evolution,
eventually they do appear in Evolution.
2.
I've added an IMAP account to check the same Exchange account for emails to
verify if it is an evolution-exchange specific problem.
The thing is the problem is very intermittent, I'd guess its around 1 in
a hundred emails don't display on time, and if the email shows up a few
hours or even a day
The Exchange server that I am connecting is one of several Exchange servers
used by several hundred people. These Exchange servers have been working for
years.
There are a few people that have started using Evolution to connect to
the Exchange servers and they are the only people having this pr
Just some more info on my Evolution setup:
"Check new messages for Junk contents" has never been enabled and is still
disabled.
"Apply filters to new messages in Inbox" was enabled, I've now disabled it.
"Synchronise account locally" was enabled, I've now disabled it.
--
Some emails are not dis
I'm also experiencing this problem with Exchange server 2003, Evolution
2.24.3 using the Exchange Plugin.
To make a missing email display, I can go into Outlook Web Access, move
the affected email to another folder, then move it back again.
Clicking Send/Receive in Evolution then displays the mis
13 matches
Mail list logo
