ec AIC7xxx Fast -> U160 support (New Driver)" ?
--
James D. Freels, Ph.D.
Oak Ridge National Laboratory
[EMAIL PROTECTED]
the 64-bit side and
amanda-server on the 32-bit side. But, if this bug is fixed, all would
be in the 64-bit side.
Am I making any sense ?
On Thu, 2005-11-10 at 08:57 -0700, Bdale Garbee wrote:
> On Wed, 2005-11-09 at 11:12 -0500, James D. Freels wrote:
> > Include here are error messages t
chroot environment ?
On Wed, 2005-11-09 at 11:47 -0500, Lennart Sorensen wrote:
On Wed, Nov 09, 2005 at 11:02:13AM -0500, James D. Freels wrote:
> I set up a crontab for user backup (to run amanda) in the chroot 32-bit
> environment. It does not seem to run. Is it a requirement to run
>
-server package that require it to run in 32-bit mode. I am getting ready to submit a bug report about this.
--
James D. Freels, Ph.D.
Oak Ridge National Laboratory
[EMAIL PROTECTED]
:29 -0400, James D. Freels wrote:
Hello folks I have a working Debian/Sarge/amd64 system and I am very happy with it. I have also installed a chroot 32-bit subsystem and have openoffice running fine on it. So, I think I understand how this interface works as well.
I have obtained a
1:22 +0200, Thomas Steffen wrote:
On 9/6/05, James D. Freels <[EMAIL PROTECTED]> wrote:
Gdk: locale not supported by Xlib
Gdk: cannot set locale modifiers
Gdk: Error converting from UTF-8 to STRING: Could not open converter from 'UTF-8' to '
set 'UTF-8' to 'ISO-8859-1' is not supported
Gdk: Error converting from UTF-8 to STRING: Conversion from character set 'UTF-8' to 'ISO-8859-1' is not supported
ASSERT /build/mts/release/bora-15576/bora/apps/lib/lui/button.cc:166
Gdk: Error converting from UTF-8 to STRING: Conversion from character set 'UTF-8' to 'ISO-8859-1' is not supported
Gdk: Error converting from UTF-8 to STRING: Conversion from character set 'UTF-8' to 'ISO-8859-1' is not supported
--
James D. Freels, Ph.D.
Oak Ridge National Laboratory
[EMAIL PROTECTED]
:18:14AM -0400, James D. Freels wrote:
>I have double-checked with another Debian/Sarge/i386 and made sure the
>remote-desktop server is set up identical with that of the
>Debian/Sarge/amd64 remote desktop server. I can access the desktop
>remotely on the i386, but n
Debian/Testing/amd64 or Debian/Unstable/amd64 acknowledged this bug ?
On Wed, 2005-08-24 at 13:01 -0400, James D. Freels wrote:
I have tried to get this working in amd64. I am running identically to the setup on my i386, but it seems to misbehave. In particular, I set up the server to allow
-08-24 at 13:01 -0400, James D. Freels wrote:
I have tried to get this working in amd64. I am running identically to the setup on my i386, but it seems to misbehave. In particular, I set up the server to allow uninvited guests at port 5900 with a password. Then on the client, I attempt to
and then on to ask for the password. After I enter the password, the authenticate step comes back up without opening the remote desktop. At that point, it is completely dis-functional.
Anyone else got this working ? If so, what is the trick here ?
--
James D. Freels, Ph.D.
Oak Ridge
Is there a bug-tracking
> now via Debian specifically for AMD-64 ? I would be happy to resubmit
> this bug if need be.
>
> --
> James D. Freels, Ph.D.
> Oak Ridge National Laboratory
> [EMAIL PROTECTED]
>
>
a to install. I would prefer to stay at Sarge and not have to upgrade to testing or unstable. Is there a bug-tracking now via Debian specifically for AMD-64 ? I would be happy to resubmit this bug if need be.
--
James D. Freels, Ph.D.
Oak Ridge National Laboratory
[EMAIL PROTECTED]
13 matches
Mail list logo
