SliTaz SliTaz Forum

You are not logged in.

#1 2012-04-22 00:32:36

Darjeeling
Member
Registered: 2012-02-06
Posts: 210

Opera Installation in Slitaz 4.0

Has anyone figured out yet, what can be done about Opera crashing on exit?

A short while ago I posted here the following bug report, based on experiments I had made with one of the last rolling releases before Slitaz 4.0 came out ...

After installation, Opera can be started in "Core Live" but not in "GTKonly Live", which returns in the terminal "Could not initialize Opera". There seem to be missing dependencies, either in the Opera package or in "GTKonly Live". In "Core Live" Opera works well until one tries to close it, which brings up an ugly looking Qt box saying:

It appears another Opera instance is using the same configuration directory because its lock file is active: /home/tux/.opera/lock  Do you want to start Opera anyway? y/n

... at the same time the terminal says:

opera [crash logging]: Crash log writing failed, error writing to file

/var/tmp/crash20120321000553.txt! Illegal instruction

Offline

#2 2012-04-22 07:01:56

mojo
Administrator
Registered: 2011-03-29
Posts: 2,174

Re: Opera Installation in Slitaz 4.0

Don't use the xorg-xf86-video-vesa driver and Opera 11.62.1347 will not crash when you Exit.

User's shouldn't notice this issue if they have nvidia or intel graphics using the nv or intel video drivers which are included on slitaz-4.0.iso

I was only having the problem on computers with ati graphics which are forced into using vesa as there are no ati graphics drivers on slitaz-4.0 iso

Install the correct xorg-xf86-video driver for your gpu.

Log out/in to X session and verify the gpu specific driver is active by looking at /var/log/Xorg.0.log

Opera 11.62.1347 runs for me on gtkonly without any additional depends.

All my testing is done by clean booting slitaz-4.0.iso burned to cdr on real hardware.

Offline

Registered users online in this topic: 0, guests: 1
[Bot] ClaudeBot

Board footer

Powered by FluxBB
Modified by Visman

[ Generated in 0.019 seconds, 7 queries executed - Memory usage: 1.53 MiB (Peak: 1.77 MiB) ]