Qupzilla dies with SIGILL ('Illegal instruction') in libQtWebKit.so.4

Bug #1184640 reported by Ronald
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
qtwebkit-source (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

When I try to run qupzilla (or probably any other libqtwebkit4 browser), I get this in gdb:

 Program received signal SIGILL, Illegal instruction.
 0xb739f773 in ?? () from /usr/lib/i386-linux-gnu/libQtWebKit.so.4

I asked the author of qupzilla first, and he confirmed my suspicion that it's QtWebKit's who's at fault.

'QtWebKit 2.3 needs to be built with no-force-sse2 flag on x86 to prevent this issue.'

Yes, this box does not contain the SSE2 instruction set. Still, it should work, right??

Ronald (ronald645)
affects: xorg (Ubuntu) → qtwebkit-source (Ubuntu)
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in qtwebkit-source (Ubuntu):
status: New → Confirmed
Revision history for this message
J G Miller (jgmiller) wrote :

In the Debian rules file one can see that --no-force-sse2 is enabled for platforms which never have sse2 eg armhf

override_dh_auto_build:
#disable JIT assembler on powerpc/arm64 where it doesn't compile
#disable WTF_USE_3D_GRAPHICS on ARM where it doesn't compile
#disable forcing SSE2 on all other platforms
#http://www.mentby.com/Group/webkit-qt-list/qtwebkit-231-tagged.html
ifneq (,$(filter arm64 powerpc ppc64el,$(DEB_HOST_ARCH)))
        ./Tools/Scripts/build-webkit --qt DEFINES+=ENABLE_JIT=0 DEFINES+=ENABLE_YARR_JIT=0 DEFINES+=ENABLE_ASSEMBLER=0
else ifeq ($(DEB_HOST_ARCH),armhf)
        ./Tools/Scripts/build-webkit --qt DEFINES+=ENABLE_JIT=0 DEFINES+=ENABLE_YARR_JIT=0 DEFINES+=ENABLE_ASSEMBLER=0 DEFINES+=WTF_USE_3D_GRAPHICS=0
else
        ./Tools/Scripts/build-webkit --qt --no-force-sse2
endif

There should be a test eg grep sse2 /proc/cpuinfo for i386 and amd64 to see if sse2 is available, and if not, then the --no-force-sse2 should also be added to the build options.

Why has the maintainer of the package not responded to this bug in nearly 2 years with this simple fix?

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.