Description of problem: After the Grand update: QT5 designer crashs on start with segmentation fault Same happens with Qt Creator when trying to open a Qt UI file Development with QT5 is not possible at the moment!!! Version-Release number of selected component (if applicable): qttools5-5.9.4-1.mga6.src.rpm How reproducible: Start designer in bash -> segmentation fault Steps to Reproduce: 1. enter designer in bash and press enter 2. 3.
Thanks for you report! So I found the problem as I'm able to reproduce here! Please install lib64qt5webkitwidgets5 and lib64qt5webkit5 from Core/Updates_testing and normally it should fix this segfault. For reference bug 23032
CC: (none) => geiger.david68210
Blocks: (none) => 23032
Thank you David, that fixed it.
@ David, Shouldn't this report depend on 23032 instead of block it, or what do I miss?
Assignee: bugsquad => kdeCC: (none) => marja11
R(In reply to Marja Van Waes from comment #3) > @ David, > > Shouldn't this report depend on 23032 instead of block it, or what do I miss? Right, I thought I put it in "depends" :(
Depends on: (none) => 23032Blocks: 23032 => (none)
Why now it get from "Depends" to "Blocks"?
(In reply to David GEIGER from comment #5) > Why now it get from "Depends" to "Blocks"? It is perfect, what you saw is: Depends on: (none) => 23032 Blocks: 23032 => (none) The 1st line says you changed the "Depends on:" field from nothing to 23032 The 2nd line says you changed the "Blocks:" field from 23032 to nothing.
*** Bug 23094 has been marked as a duplicate of this bug. ***
CC: (none) => johnms
Mageia 6 changed to end-of-life (EOL) status on 2019-09-30. It is no longer maintained, which means that it will not receive any further security or bug fix updates. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Mageia version. Bug Reporter: Thank you for reporting this issue and we are sorry that we weren't able to fix it before Mageia 6's end of life. If you are able to reproduce it against a later version of Mageia, you are encouraged to click on "Version" and change it against that version of Mageia. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Mageia release includes newer upstream software that fixes bugs or makes them obsolete. If you would like to help fixing bugs in the future, don't hesitate to join the packager team via our mentoring program [1] or join the teams that fit you most [2]. [1] https://wiki.mageia.org/en/Becoming_a_Mageia_Packager [2] http://www.mageia.org/contribute/ Best regards, Aurélien Bugsquad Team
Resolution: (none) => OLDStatus: NEW => RESOLVEDCC: (none) => ouaurelien