Bug 10252 - Qupzilla fails with "Illegal Instruction" on PIII computers
Summary: Qupzilla fails with "Illegal Instruction" on PIII computers
Status: RESOLVED DUPLICATE of bug 10157
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 3
Hardware: i586 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Matteo Pasotti
QA Contact:
URL:
Whiteboard:
Keywords: Triaged
Depends on:
Blocks:
 
Reported: 2013-05-24 11:58 CEST by Derek Jennings
Modified: 2013-06-10 14:26 CEST (History)
0 users

See Also:
Source RPM: qupzilla-1.4.1-1.mga3
CVE:
Status comment:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Derek Jennings 2013-05-24 11:58:35 CEST 
With qupzilla-1.4.1-1.mga3 on a laptop with a Pentium III CPU qupzilla crashes on starting with the message
"Illegal Instruction"
It looks like it is trying to use sse2/3 instructions.



Reproducible: 

Steps to Reproduce:
Manuel Hiebel 2013-05-24 20:08:11 CEST

Keywords: (none) => Triaged
Assignee: bugsquad => matteo.pasotti

Comment 1 Matteo Pasotti 2013-06-09 18:08:52 CEST 
I'm not able to test it by myself. 
Install the debuginfo pkg and add the backtrace, please.
I suspect that the problem could be related to the way QtWebKit is compiled and that this issue is not actually imputable to qupzilla.
Comment 2 Matteo Pasotti 2013-06-09 18:12:09 CEST 
Have you tried to run also another webkit based browser like arora?
Comment 3 Derek Jennings 2013-06-10 03:53:11 CEST 
It looks like neoclust has already fixed the problem in qtwebkit


http://svnweb.mageia.org/packages/cauldron/qtwebkit/current/SPECS/qtwebkit.spec?r1=428722&r2=428732
Comment 4 Matteo Pasotti 2013-06-10 07:16:01 CEST 
So, does qupzilla work now? 
If yes we should close this bug as resolved invalid.
Comment 5 Derek Jennings 2013-06-10 14:26:42 CEST 
Yes it does

Marking this as a duplicate of Bug 10157

*** This bug has been marked as a duplicate of bug 10157 ***

Status: NEW => RESOLVED
Resolution: (none) => DUPLICATE
Note You need to log in before you can comment on or make changes to this bug.