how do i install opera browser? get-opera script is not working; it can't connect to mirror.

Have you tried downloading the source tarball (tar.gz) from opera directly? What is your experience with it? I'm slightly wary of a few dependencies though, but shouldn't be anything that's not in the repos.

Hi,

Opera requires shared qt3 since version 10. There is not qt3 in slitaz repo. Compiling & Installing qt3 is tiresome. So easiest way is to use outer resource such as arch linux.

Here I write how to install opera10 in easy way.

1. Get opera
opera-10.00.gcc4.shared.qt3.i386.rpm
http://www.opera.com/download/get.pl?id=32229&location=300¬hanks=yes&sub=marine

2. Get qt3 from arch repo:
http://mirrors.kernel.org/archlinux/extra/os/i686/qt3-3.3.8-13-i686.pkg.tar.gz

3. Get tools:
get arch2taz(my site):
http://sites.google.com/site/asimo1234lab/home/slitaz/cooking/unofficial-cooking-packages/stuff/arch2taz?attredirects=0

# chmod +x arch2taz

get-opera-hacked(hacked version - my site):
http://sites.google.com/site/asimo1234lab/home/slitaz/cooking/unofficial-cooking-packages/stuff/get-opera-hacked?attredirects=0

# chmod +x get-opera-hacked

4. Convert arch package to slitaz package:

# ./arch2taz qt3-3.3.8-13-i686.pkg.tar.gz

5. Install qt3:

# tazpkg install qt3-3.3.8-13-arch_i686.tazpkg

6. Install opera:

# ./get-opera-hacked opera-10.00.gcc4.shared.qt3.i386.rpm

7. add & update library path.
edit /etc/ld.so.conf:
/opt/qt/lib

update library path:

# ldconfig

8. run opera
Menu -> Internet -> Opera

**EDIT**:
qt4 version:
wget ftp://get.opera.com/pub/opera/linux/1000/final/en/i386/opera-10.00.gcc4.qt4.i386.rpm

Opera shared qt4 version is not necessary to outer resource.

asimo

Does "upgrade" upgrade slitaz 1 to slitaz 2?

How do we know how much hd space the upgrade will take?

i asked on the old forum a few months ago but did not get any answers.

Thank you.

Hi pascal,

Upgraded get-opera works in SliTaz cooking.
As get-opera installs beta3 version, I installed final version(10.00qt4). It worked very well.
Thank you.

asimo

thank you all. if i go asimo's way, will it conflict with future get-opera scripts?

Hi tikbalang,

My way is only installing opera from local disk. There is not any other difference.

If you edit get-opera a bit, you can get final version.

- edit line 23 in /usr/bin/get-opera: 'tail -2' to 'tail -5'

line23: set -- $(wget -O - $URL 2>/dev/null | grep href= | tail -5 | sed 's|.*href="\(.*\)/".*|\1|')

tail -5 outputs last 5 lines and the fifth line (href="1000/") is 10.00 final version.

asimo

thank you again. i went with the last option and edited get-opera script. i now have opera 10 final installed.

i spoke too soon. opera10 final needed two dependencies: libOtgui and libOtcore - i said yes to install both. now when i login as "tux" my icons are lost and some programs fron the menu does not run. it says i needed an xsettings manager. what did i break and how do i fix it?

libQtgui and libQtcore are Qt4 libraries. These libraries work only for Qt applications such as Opera.

These things are probably dbus & hal related issues.

Please check using ps.

ps ax | grep hald
ps ax | grep dbus

If these daemons didn't run, start them.

/etc/init.d/dbus start
/etc/init.d/hald start

Then open xterm and run pcmanfm if both daemons work well.

asimo

both seem to be running. the problem is with the tux account only. everything is working fine with root.

hum... it may be permission issue.

check /tmp and /home/tux

1.) /tmp
ls -l /
drwxrwxrwt ... tmp is OK. If not, fix it.

# chmod 1777 /tmp

2.) /home/tux
find /home/tux ! -user 'tux'. If other than tux found, fix it.

# chown -R tux:tux /home/tux

Hope this helps.

asimo

that last one did it. after installing opera and libs from root, /home/tux was destroyed. what i did was i copied the /home/tux tree from original slitaz iso then reset permissions as per your instructions.

thank you!!!

something is destroying /home/tux. after i fix the permissions, set my preferences, i run "tazusb writefs gzip" and manually replace rootfs.gz with the new one. when i reboot and login to tux, the same problem appears and i have to reconstruct /home/tux once again from the original iso.

Maybe home= points to the wrong place.

http://www.slitaz.org/en/doc/handbook/livecd.html

i can't use "home=" bootcode because it requires an ext3 partition. i run slitaz frugally from DOS on fat32. i looked into tazusb script and it looks like only the folder names of some temp folders including /home is saved. i guess slitaz relies on the existing ext3 partition for persistence.

here is another strange part. on the original rootfs.gz from slitaz 2.0, /home is empty so takes default preferences from /etc/skel - correct? now, in my new rootfs.gz (after running the updates above, installing opera) /home is also empty but the default preferences for tux is screwed up.

lastly, is root exempted from /etc/skel?

"i run "tazusb writefs gzip" and manually replace rootfs.gz"
"i can't use "home=" bootcode because it requires an ext3 partition. i run slitaz frugally from DOS on fat32. "

http://www.slitaz.org/en/doc/manuals/tazusb.en.html says fat32 is ok but then says, "The command 'format' is used for formatting a device for use as a LiveUSB device. Currently, it only supports formatting as EXT3."

"here is another strange part. on the original rootfs.gz from slitaz 2.0, /home is empty so takes default preferences from /etc/skel - correct?"

Probably but I do not know.

"now, in my new rootfs.gz (after running the updates above, installing opera) /home is also empty but the default preferences for tux is screwed up."

I tried using tazusb writefs to get around tazlito errors to make a frugal or custom flavor but tazusb and tazlito (live cd iso) did not mix well.

"lastly, is root exempted from /etc/skel?"

I do not know.