Please try the glibc test version jdk116_v3 which has a set resizable fix
(and a vanishing frame fix).
We test with a variety of Window Managers. Some use fvwm2, some use KDE
1.0, some use KDE Beta 4 (myself), AfterStep, MWM, etc. Some problem exist
only under some window managers. We are wor
On Mon, 31 Aug 1998, Ninewands wrote:
> Which Window Manager(s) was/were used in developing the JDK 1.1.6v2 AWT?
> I am using KDE, and whenever my application opens a window, it fades out
> as if the KDE desktop was painting over it ...
>
> I am trying to figure out if th
Which Window Manager(s) was/were used in developing the JDK 1.1.6v2 AWT?
I am using KDE, and whenever my application opens a window, it fades out
as if the KDE desktop was painting over it ...
I am trying to figure out if the problem is in Java, the Window Manager
of my application (ICQJava
Hello!
JDK 1.1.6 (glibc version) does not work with glibc-2.0.95 (it's glibc 2.1
AFAIK?) :((( It's because of incompatibilites between supplied with JDK
libc.so.6 and my own libc.so.6. I tried to solve them by manipulating some of my
libraries, but is was useless :(
--
Nickolay G.
Richard Jones wrote:
> org.omg.CORBA.UNKNOWN[completed=MAYBE]
> at com.visigenic.vbroker.orb.SE.read(SE.java:28)
Sorry to answer my own question :-) This topic seemed
to cause more discussion about how I ever managed to
get VBJ working on Linux than on the original problem.
Anyway, I solv
On Thu, Jul 16, 1998 at 05:53:39, Richard Jones said:
> I wrote to Borland about this and they said that was
> fine but (a) they wouldn't support it and (b) they wouldn't
> port osagent to Linux because of `lack of interest'. Yeah ...
> right ... Maybe you should write to them too and if enough
>
Richard,
I hope you don't mind me asking but
Where did you download it from, what was the URL ?
How much space does it need ?
Is it easy to install, what are the procedures you used ?
I'm sure loads of people will be interested in this..
Many thanks
Matt
Shane P. McCarron wrote:
>
> Can I read this message to imply that Visibroker is available to run
> natively on Linux?
Yup. Of course, I'm not *really* running the mythical
`Visibroker for Linux'. Rather I'm running the commercial
Visibroker for Solaris, but I tarred up all the files and
copied
Hi:
I get the following message occasionally from a client
trying to talk to a CORBA server. Both client and server
are built using Visibroker and running on Linux with
JDK 1.1.6v2 (glibc 2.0.7-13).
I added a message to the server which indicates that
the server's impl method is being c
> Toni Nikkanen wrote:
>
>> lots of these: TYA:CompiledCodeSignalHandler_hook--context at offset =60
>> 0x42ca73b8 0xb
>> Signal catched by TYA: hook for 11
>
> I got these too with Hotjava... It looks like 1.1.6v2 is using sig 11 to
> detect double-freeing memory. Commenting out the
Toni Nikkanen wrote:
> lots of these: TYA:CompiledCodeSignalHandler_hook--context at offset =60
> 0x42ca73b8 0xb
> Signal catched by TYA: hook for 11
I got these too with Hotjava... It looks like 1.1.6v2 is using sig 11 to
detect double-freeing memory. Commenting out the EXCEPTION_BY
For everyone using libdl.so.1.9.9 and JDK 1.1.6v2.
Try remove the libdl.so.1 and libc.so.5 from your
$JAVA_HOME/lib/i686/green_threads/
Assuming you are using a newer libc5 like libc.so.5.4.44 of course.
In any case, read the README.linux file.
Cheers,
Paul
Had this problem with both JDK 1.1.6v1 and v2. 1.1.5v7 works wonderfully,
though. And btw, the JRE is broken on v2 - can't load libjava. It gives
the full path to libjava.so (the correct path) but it says it can't load
it. Thought I'd let ya know... I know it can't be my libc, since it's
using a p
13 matches
Mail list logo
