Bug 21234

Summary: Konqueror crashes at startup
Product: Mageia Reporter: Frédéric "LpSolit" Buclin <LpSolit>
Component: RPM PackagesAssignee: David GEIGER <geiger.david68210>
Status: RESOLVED FIXED QA Contact:
Severity: critical    
Priority: High CC: geiger.david68210, marja11
Version: Cauldron   
Target Milestone: Mageia 6   
Hardware: All   
OS: Linux   
Whiteboard: MGA6TOO
Source RPM: konqueror-16.12.3-1.mga6 CVE:
Status comment:

Description Frédéric "LpSolit" Buclin 2017-07-12 17:38:21 CEST
When starting konqueror, it crashes immediately. From a shell:

$ konqueror 
Trying to create view for "KonqAboutPage" "konq_aboutpage"
Found requested service "konq_aboutpage"
Trying to open lib for requested service  "konq_aboutpage"
KonqAboutPage(0x127ba10) QUrl("")
KonqAboutPage(0x127ba10) "khtml"
New current view KonqView(0x127b5f0)
url= QUrl("about:konqueror") locationBarURL= ""
 HTML :  "<?xml version=\"1.0\" encoding=\"utf-8\"?>\n<!DOCTYPE html PUBLIC \"-//W3C//DTD XHTML 1.0 Transitional//EN\"\n    ...</body>\n</html>\n<!-- vim:set sw=2 et nocindent smartindent: -->\n"
kf5.kio.core: Refilling KProtocolInfoFactory cache in the hope to find ""
Preloading next Konqueror instance
finishedLoading "file:///usr/share/kf5/infopage/kde_infopage.css"
finishedLoading "file:///usr/share/konqueror/about/konq.css"
QWidget::paintEngine: Should no longer be called
QPainter::begin: Paint device returned engine == 0, type: 1
QPainter::translate: Painter not active
QPainter::setClipRect: Painter not active
QPainter::font: Painter not active
QPainter::setFont: Painter not active
QPainter::setPen: Painter not active
KCrash: Application 'konqueror' crashing...
KCrash: Attempting to start /usr/libexec/drkonqi from kdeinit
sock_file=/run/user/1000/kdeinit5__0
QWidget::paintEngine: Should no longer be called
QWidget::paintEngine: Should no longer be called
QWidget::paintEngine: Should no longer be called
QWidget::paintEngine: Should no longer be called
QWidget::paintEngine: Should no longer be called
QWidget::paintEngine: Should no longer be called
QWidget::paintEngine: Should no longer be called
QWidget::paintEngine: Should no longer be called
QWidget::paintEngine: Should no longer be called
QWidget::paintEngine: Should no longer be called
QWidget::paintEngine: Should no longer be called
QWidget::paintEngine: Should no longer be called
QWidget::paintEngine: Should no longer be called
QWidget::paintEngine: Should no longer be called
QWidget::paintEngine: Should no longer be called
QWidget::paintEngine: Should no longer be called
QWidget::paintEngine: Should no longer be called
QWidget::paintEngine: Should no longer be called
kf5.kio.core: Refilling KProtocolInfoFactory cache in the hope to find ""
url "b" filtered into QUrl("error:/?error=105&errText=b#b")
kf5.kio.core: Refilling KProtocolInfoFactory cache in the hope to find "error"
kf5.kio.core: Refilling KProtocolInfoFactory cache in the hope to find "error"
kf5.kio.core: Refilling KProtocolInfoFactory cache in the hope to find "error"
Trying to create view for "text/html" ""
"webenginepart"  : X-KDE-BrowserView-AllowAsDefault is valid :  false
KonqFrame(0x1272910) QObject(0x0)
Could not find QtWebEngineProcess
KCrash: Application 'konqueror' crashing...
KCrash: Attempting to start /usr/libexec/drkonqi from kdeinit
sock_file=/run/user/1000/kdeinit5__0

[2]+  Stoppé                 konqueror
Comment 1 David GEIGER 2017-07-12 17:49:06 CEST
the package qtwebengine5 is needed to fix this crash.

I'll add this dependency for konqueror.

CC: (none) => geiger.david68210

Comment 2 Frédéric "LpSolit" Buclin 2017-07-12 19:45:03 CEST
(In reply to David GEIGER from comment #1)
> the package qtwebengine5 is needed to fix this crash.

I confirm that installing qtwebengine5 fixes the crash. Thanks!
Comment 3 Marja Van Waes 2017-07-13 00:03:30 CEST
(In reply to David GEIGER from comment #1)
> the package qtwebengine5 is needed to fix this crash.
> 
> I'll add this dependency for konqueror.

Thanks, David.

If this counts as a critical fix,  then it can be pushed to cauldron updates_testing and assigned to QA, as Thomas said on dev ml in the "How to handle Mageia 6 security updates before full branching" thread.

I don't know how/when it can/should be pushed to cauldron core release, though.

CC: (none) => marja11
Version: 6 => Cauldron
Whiteboard: (none) => MGA6TOO
Assignee: bugsquad => geiger.david68210

Comment 4 David GEIGER 2017-07-15 09:55:05 CEST
Fixed now for mga6!

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