Bug 9584 - Qupzilla browser only shows blank screen
Summary: Qupzilla browser only shows blank screen
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Matteo Pasotti
QA Contact:
URL:
Whiteboard:
Keywords: Triaged
Depends on:
Blocks:
 
Reported: 2013-04-01 12:36 CEST by Shawn Peterson
Modified: 2013-04-08 01:42 CEST (History)
1 user (show)

See Also:
Source RPM: qupzilla
CVE:
Status comment:


Attachments

Description Shawn Peterson 2013-04-01 12:36:18 CEST
The webbrowser qupzilla only shows a blank screen when browsing.  If you click on the blank page, qupzilla will crash.  This is true regardless of the webpage.  

On a fresh install of Mageia 3, it works fine.  However, after the first system update, something (I don't know what, sorry) seems to be breaking it.  This has happened on three different installs.  

I checked qupzilla's website, and found a similar reference here:  https://github.com/QupZilla/qupzilla/wiki/FAQ.  However, it is referreing to freeBSD, so I am not sure if that is relevant.  I am also not using proprietary drivers.  

No idea if this helps, but here is the output of the latest crash log.

Time: Mon Apr 1 06:29:42 2013
Qt version: 4.8.4 (compiled with 4.8.4)
QupZilla version: 1.3.5
WebKit version: 537.21

============== BACKTRACE ==============
#0: qupzilla() [0x804a4f2]
#1: linux-gate.so.1(__kernel_sigreturn+0) [0xffffe400]
#2: /lib/libQtWebKit.so.4(+0xaa6217) [0xb5e3d217]
#3: /lib/libQtWebKit.so.4(+0x17e9cf) [0xb55159cf]
#4: /lib/libQtWebKit.so.4(_ZNK9QWebFrame14hitTestContentERK6QPoint+0x17a) [0xb551607a]
#5: /lib/libQtWebKit.so.4(_ZNK8QWebPage7frameAtERK6QPoint+0x6b) [0xb552b79b]
#6: /lib/libQupZilla.so.1(_ZN7WebView15mousePressEventEP11QMouseEvent+0x177) [0xb75922e7]
#7: /lib/libQtGui.so.4(_ZN7QWidget5eventEP6QEvent+0xde6) [0xb4a5da96]
#8: /lib/libQtWebKit.so.4(_ZN8QWebView5eventEP6QEvent+0x6f) [0xb5532d6f]
#9: /lib/libQtGui.so.4(_ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent+0xbc) [0xb4a03d1c]
#10: /lib/libQtGui.so.4(_ZN12QApplication6notifyEP7QObjectP6QEvent+0xc79) [0xb4a09209]
#11: /lib/libQtCore.so.4(_ZN16QCoreApplication14notifyInternalEP7QObjectP6QEvent+0x8e) [0xb475c28e]
#12: /lib/libQtGui.so.4(_ZN19QApplicationPrivate14sendMouseEventEP7QWidgetP11QMouseEventS1_S1_PS1_R8QPointerIS0_Eb+0xef) [0xb4a04b7f]
#13: /lib/libQtGui.so.4(+0x1c30f5) [0xb4a8d0f5]
#14: /lib/libQtGui.so.4(_ZN12QApplication15x11ProcessEventEP7_XEvent+0xb29) [0xb4a8bbb9]
#15: /lib/libQtGui.so.4(+0x1eb4e4) [0xb4ab54e4]
#16: /usr/lib/libglib-2.0.so.0(g_main_context_dispatch+0x143) [0xb3587823]
#17: /usr/lib/libglib-2.0.so.0(+0x46bc0) [0xb3587bc0]
#18: /usr/lib/libglib-2.0.so.0(g_main_context_iteration+0x41) [0xb3587ca1]
#19: /lib/libQtCore.so.4(_ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE+0x61) [0xb478e101]
#20: /lib/libQtGui.so.4(+0x1eb0ca) [0xb4ab50ca]
#21: /lib/libQtCore.so.4(_ZN10QEventLoop13processEventsE6QFlagsINS_17ProcessEventsFlagEE+0x4c) [0xb475ad5c]
#22: /lib/libQtCore.so.4(_ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE+0x141) [0xb475b051]
#23: /lib/libQtCore.so.4(_ZN16QCoreApplication4execEv+0x9a) [0xb476045a]
#24: /lib/libQtGui.so.4(_ZN12QApplication4execEv+0x24) [0xb4a01b94]
#25: qupzilla() [0x8049fd0]
#26: /lib/i686/libc.so.6(__libc_start_main+0xf5) [0xb4340a35]
#27: qupzilla() [0x804a2a1]
Shawn Peterson 2013-04-01 13:12:50 CEST

CC: (none) => shawn.peterson

Manuel Hiebel 2013-04-07 15:24:39 CEST

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

Comment 1 Matteo Pasotti 2013-04-07 19:54:14 CEST
wip
Matteo Pasotti 2013-04-07 19:54:27 CEST

Hardware: i586 => All

Comment 2 Matteo Pasotti 2013-04-08 01:42:03 CEST
qupzilla 1.4.1 was pushed cause version 1.3.5 doesn't build on cauldron anymore.
I've tested it and the bug is fixed.
I'm  going to close this bug report as resolved fixed.
Thank you for reporting.

Status: NEW => RESOLVED
Resolution: (none) => FIXED


Note You need to log in before you can comment on or make changes to this bug.