Opera 6.1 Preview 5 for Linux (Red Hat 8.0, Mandrake 9.0 and SuSE 8.1)
Espen Sand
Here is the second special preview for Red Hat 8.0, Mandrake 9.0 and SuSE 8.1
The main change in this preview is improved anti-aliasing support in the
document area.
The package is build with qt-mt 3.0.5 using gcc 3.2 and with rtti support.
The rtti support is important for KDE style support.
We have not tested this on SuSE 8.1 yet so if you do please report your
observations
I would also like to know if you have problems with KDE style integration
or any other problems.
Download from:
http://web.opera.com/download/unix/untested/intel-linux/268-20021023-6.1-P5/
The whatpackage.txt and changelog.txt on the page seems to be disabled at
the moment:
whatpackage.txt
------------------------
This release is for :
------------------------
Redhat 8.0 (psyche)
Mandrake 9.0 (dolphin)
SuSE 8.1
------------------------
Changelog (since Preview 4 for Linux (Red Hat 8.0, Mandrake 9.0 and SuSE 8.1))
- Improved anti-aliasing in document area. This should now work properly.
- Fixed a problem that caused new windows (Shift+Click and from the
link context menu) to be opened without any toolbars if the
"Show address bar" setting was turned off and Opera was running
in SDI mode.
- Added support for configurable control of Drag (Drag and Drop)
of links and bookmarks. This is configurable from opera6.ini only.
Enable Drag=<number>|255(x)
255: All drag operations enabled
1: Drag link in document enabled
2: Drag bookmarks enabled
4: Drag from "Location" label on address bar enabled.
You can use a combination, eg,
6: Bookmark and "Location" label enabled while links disabled.
Example:
[User prefs]
Enable Drag=2
- Fixed a problem that caused the progress indication (progress bar)
not to be hidden in some cases when a download was complete.
- Modified default (hardcoded) shared path for FreeBSD to
/usr/local/share/opera
- Fixed a layout problem in the menubar. The MDI controls at the
right edge of the menubar were not properly hidden when all
windows were normalized or minimized.
Enjoy!
--
Espen Sand
es...@opera.com
Aldemir Akpinar
Espen Sand
>
> I mean no offence but why there are no packages for debian?
Because we have to test out builds using gcc 3.2 + adjustments
for those systems.
--
Espen Sand
es...@opera.com
Christian Wallraven
> Hi all,
>
> Here is the second special preview for Red Hat 8.0, Mandrake 9.0 and SuSE
> 8.1 The main change in this preview is improved anti-aliasing support in
> the document area.
mmmh, the glory of aa-fonts! Works fine for me on RH8! Thanks a lot!!!
>
> The package is build with qt-mt 3.0.5 using gcc 3.2 and with rtti support.
> The rtti support is important for KDE style support.
>
> We have not tested this on SuSE 8.1 yet so if you do please report your
> observations
>
> I would also like to know if you have problems with KDE style integration
> or any other problems.
KDE style integration seems to work fine for me (changed to Keramik).
Great work, guys!
Best,
Christian
Don Smith
Java!!! I did a opera -debugjava and got the "instructions" but it does not
say where to put those lines in the script! Also, in /usr/bin/opera the
comments there do not match!
Dennis Tuchler
> Hi all,
>
> Here is the second special preview for Red Hat 8.0, Mandrake 9.0 and
> SuSE 8.1 The main change in this preview is improved anti-aliasing
> support in the document area.
>
> The package is build with qt-mt 3.0.5 using gcc 3.2 and with rtti
> support. The rtti support is important for KDE style support.
>
> We have not tested this on SuSE 8.1 yet so if you do please report your
> observations
>
If it works on SuSE 8.1, will it work as well on SuSE 8.0?
dj tuchler
Tais M. Hansen
"Espen Sand" <es...@opera.com> wrote in message
news:3DB6AFEC...@opera.com...
> The package is build with qt-mt 3.0.5 using gcc 3.2 and with rtti support.
Damn! Could you please do a static version or a gcc-2.95.3 build? I was so
happy when I read you finally used qt-mt but that joy quickly ended with
gcc3.2. :(
Regards,
Tais M. Hansen
tbt
seconded. i dont have qt 3 on mandrake 8.2
tbt.
To mail me, turn cc into com
--
Utah. Land of the caffeine addicted Mormons.
From Craig Kilborn: (President Bush): "God bless Kickass Seal Land!"
Wolfgang
> We have not tested this on SuSE 8.1 yet so if you do please report your
> observations
>
> I would also like to know if you have problems with KDE style integration
> or any other problems.
Nice AA-fonts and good Style integration with KDE 3.04
here (Unted Linux 1.0 Beta= SuSE 8.1), but no plugins work.
operamotiv seems not to work, tried with operamotiv.wrapper
from beta1:
flash and acrobat worked but realplayer not, Java crashes Opera
Best regards Wolfgang
Eirik Byrkjeflot Anonsen
I suppose you mean the instructions about LD_PRELOAD and
possibly OPERA_JAVA_FORCE_ENABLED?
The easiest thing is to put them above, but close to
${OPERA} "$@"
eirik
Eirik Byrkjeflot Anonsen
Do you get any information from
opera -debugjava
Does Java get disabled every time you start up Opera?
eirik
Don Smith
Can I be a weenie and ask you to post an opera start up script with the
correct entries in it? I will try it, but none of my efforts have worked
so far.
Erich J. Wahl
> Wolfgang writes:
>
>
> >Espen Sand wrote:
> >
> >
> >
> >>We have not tested this on SuSE 8.1 yet so if you do please report your
> >>observations
> >>
> >>I would also like to know if you have problems with KDE style
> integration
> >>or any other problems.
> >
> >Nice AA-fonts and good Style integration with KDE 3.04
> >here (Unted Linux 1.0 Beta= SuSE 8.1), but no plugins work.
> >operamotiv seems not to work, tried with operamotiv.wrapper
> >from beta1:
> >flash and acrobat worked but realplayer not, Java crashes Opera
> >
> >Best regards Wolfgang
>
>
>
> Do you get any information from
>
> opera -debugjava
>
>
> Does Java get disabled every time you start up Opera?
>
> eirik
I have 6.1P5 running on a Gentoo box compiled with gcc-3.2. I had to
load all the necessary environment variables into /opt/opera/bin/opera
and use the forced Java statement. So, Java and Flash now work.
Good job...
Erich
Espen Sand
Ther problem is that there is no "correct" entries. It varies from machine
to machine.
> I will try it, but none of my efforts have worked
> so far.
Where is Java located on your machine?
--
Espen Sand
es...@opera.com
D Smith
> >>>Java!!! I did a opera -debugjava and got the "instructions" but it
> does
> >>>not
> >>>say where to put those lines in the script! Also, in
> /usr/bin/opera the
> >>>comments there do not match!
> >>
> >>
> >>I suppose you mean the instructions about LD_PRELOAD and
> >>possibly OPERA_JAVA_FORCE_ENABLED?
> >>
> >>The easiest thing is to put them above, but close to
> >>
> >>${OPERA} "$@"
> >
> >Can I be a weenie and ask you to post an opera start up script with the
> >correct entries in it?
>
>
> Ther problem is that there is no "correct" entries. It varies from
> machine
> to machine.
>
>
> >I will try it, but none of my efforts have worked
> >so far.
>
>
> Where is Java located on your machine?
I did not get to play with it last night, but my java is in
/usr/java/j2re1.4.1_01/lib/i386 .
I did not mean custom to me, but one with "path/to/java" for everyone.
If I get a custom one, that is great :) Sorry to be a pain.
Danny Smith
from this release. I've tried every possible combination
of LD_PRELOAD this, and OPERA_JAVA_FORCE_ENABLE that,
what have you, all to no avail.
"opera -debugjava" still gripes about libXt (? this is from
memory) and disables java independent of OPERA_JAVA_FORCE_ENABLE.
I hesitate to make much of this, since I'm running
Redhat 8.0/2.4.18-17.8.0
(see https://rhn.redhat.com/errata/RHSA-2002-206.html)
and KDE 3.0.4 from hand-built binary rpms, thus my environment
may be unique.
But then I've seen little encouraging info from anyone else,
either.
I don't mind too much: Konqueror is getting better each
release. :-)
Gunther
Levi Ramsey
tbt <tbt...@yahoo.cc> wrote:
> seconded. i dont have qt 3 on mandrake 8.2
qt3 rpms can be had from unsupported on your friendly neighborhood
mirror (as can kde3, gnome2, and other goodies...)
--
Levi Ramsey
lra...@student.umass.edu le...@cygnetnet.net
Love lies in pools of questions.
GPG Key Fingerprint: 354C 7A02 77C5 9EE7 8538 4E8D DCD9 B4B0 DC35 67CD
Currently playing: Megadeth - Breadline
Linux 2.4.19-16mdk
22:00:02 up 4 days, 13:03, 7 users, load average: 0.19, 0.25, 0.36
Don Smith
Same thing here (except for the KDE). I cannot make it work.
Eirik Byrkjeflot Anonsen
I think it's OPERA_JAVA_FORCE_ENABLED. But I thought the
message given by opera -debugjava was supposed to say that...
If Opera doesn't crash when you enable Java and visit a
Java site, then your LD_PRELOAD is probably correct.
eirik
Eirik Byrkjeflot Anonsen
I don't know what the current opera start up script actually
looks like, but if it has a line containing LD_PRELOAD, probably
looking similar to:
# export LD_PRELOAD=${OPERA_JAVA_DIR}/libawt.so
you can just remove the '#' at the beginning of that line.
I'm not entirely sure how much is working (or not), though...
Try to start Opera, enable java, and open the Java Console
(windows->special->java console). If this crashes Opera, then
it's time to try the LD_PRELOAD trick...
eirik
Espen Sand
>
> Well, I can't speak for anyone else, but I'm getting no joy
> from this release. I've tried every possible combination
> of LD_PRELOAD this, and OPERA_JAVA_FORCE_ENABLE that,
> what have you, all to no avail.
> "opera -debugjava" still gripes about libXt (? this is from
> memory) and disables java independent of OPERA_JAVA_FORCE_ENABLE.
>
> I hesitate to make much of this, since I'm running
> Redhat 8.0/2.4.18-17.8.0
> (see https://rhn.redhat.com/errata/RHSA-2002-206.html)
> and KDE 3.0.4 from hand-built binary rpms, thus my environment
> may be unique.
I can only say what I do to enable this on my Red Hat 8.0
(stock install). I do not normally use Red Hat but I tried to
configure java right now and I got it working (I justed tested
some games at games.yahoo.com)
1) I have jre1.3.1_04 downloaded from SUN in /opt/java/jre1.3.1_04/
2) In File | Preferences | Multimedia I typed in "/opt/java/jre1.3.1_04"
in the java path and pressed "Validate Java path" and the path
"/opt/java/jre1.3.1_04/lib/i386" was suggested which I used.
3) Then I have to make sure that LD_PRELOAD was set because on Red Hat 8.0
the shipped Qt library depends on Xt. That can cause problems for Opera
because Java is picky about what Xt it wants to use so I set in the
terminal from where I run opera
export OPERA_JAVADIR=/opt/java/jre1.3.1_04/lib/i386/
export LD_PRELOAD=${OPERA_JAVADIR}/libawt.so
so that "libawt.so" is loaded before Xt when Opera starts
4) Then I have to specify where the special libraries that Java needs
are located. I do this with the LD_LIBRARY_PATH in the same terminal window
again.
export LD_LIBRARY_PATH=${OPERA_JAVADIR}:${OPERA_JAVADIR}/client/
5) Then I set the OPERA_FORCE_JAVA_ENABLED flag to avoid having to
enable java each time I start Opera (Java will be disabled when the detection
mechanism believes it can cause problems) again in the same terminal window.
export OPERA_FORCE_JAVA_ENABLED=1
All the commands are listed below. Once I set them like
below (I use bash) Opera uses Java. On my regular machine
I use a Qt that is build so that is does not require Xt and
the only thing I have to set then is the LD_LIBRARY_PATH
export OPERA_JAVADIR=/opt/java/jre1.3.1_04/lib/i386/
export LD_PRELOAD=${OPERA_JAVADIR}/libawt.so
export LD_LIBRARY_PATH=${OPERA_JAVADIR}:${OPERA_JAVADIR}/client/
export OPERA_FORCE_JAVA_ENABLED=1
Once you have a working Java you should update the /usr/bin/opera
script with the settings above so that they are executed if you
do not start opera from a terminal.
You can test that java is working by opening the Java console from
Window | Special | Java console
--
Espen Sand
es...@opera.com
Gunther
> Danny Smith wrote:
> >
> > Well, I can't speak for anyone else, but I'm getting no joy
> > from this release. I've tried every possible combination
> > of LD_PRELOAD this, and OPERA_JAVA_FORCE_ENABLE that,
>
> I can only say what I do to enable this on my Red Hat 8.0
> (stock install). I do not normally use Red Hat but I tried to
> configure java right now and I got it working (I justed tested
> some games at games.yahoo.com)
>
....
Ok, I finally got all the nuts and bolts right, and it seems
to work (Sun J2RE 1.4.1).
Now, is there any chance that future builds won't require
this tomfoolery with environment variables first?
Gunther
Espen Sand
As far as I know the main problem is that we have to make
sure Java uses the right Xt library, which is a problem if the
Qt library you use is build with support for Xt. On my machine
I use a Qt without Xt dependency and I only have to set the
LD_LIBRARY_PATH to tell Java where its own libraries are located.
--
Espen Sand
es...@opera.com
D Smith
> >Ok, I finally got all the nuts and bolts right, and it seems
> >to work (Sun J2RE 1.4.1).
> >Now, is there any chance that future builds won't require
> >this tomfoolery with environment variables first?
>
>
> As far as I know the main problem is that we have to make
> sure Java uses the right Xt library, which is a problem if the
> Qt library you use is build with support for Xt. On my machine
> I use a Qt without Xt dependency and I only have to set the
> LD_LIBRARY_PATH to tell Java where its own libraries are located.
His question is still valid: the next release how about we do not have
to do all this? Maybe we expect more from you guys because it is a
commercial product and not open source. I expect commercial products to
work without much effort. I know, this is a beta, I just hope it
improves with the next release.
BTW, mine still does not work.
Espen Sand
The solution is to use the static version. Then one only have to
deal with the LD_LIBRARY_PATH setting which the /usr/bin/opera
script tries to do, but if Java is installed somewhere on the
machine where the script does not look then it will not work.
Had Java been installed to a standardized location on all
distributions then this would been much simpler, but unfortunately
this is not the case.
>
> BTW, mine still does not work.
Try to follow the description I made on "Sat, 26 Oct 2002 13:40:52"
in the same tread as this.
--
Espen Sand
es...@opera.com
James Finnall
Downloaded the standard tar file and installed it on SuSE 8.1 and it appears
to be working great and running stable. Document fonts looked really bad
at first, but made some changes in the preferences and it is OK now. Or at
least OK for a LCD panel, it is running on my notebook computer.
Keep up the great work. Thank you.
Cheers!
Helge Hafting
>
> Aldemir Akpinar wrote:
> >
> > I mean no offence but why there are no packages for debian?
>
> Because we have to test out builds using gcc 3.2 + adjustments
> for those systems.
gcc-3.2 is available, at least in debian unstable.
I hope at least the release will be available as a .deb
too.
Helge Hafting