| Summary: | drakconf crashed after updating webkit2, downgrading it fixes it ("Could not locate symbol webkit_web_view_new at mygtk3.pm line 621") | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Mauricio Andrés Bustamante Viveros <neoser10> |
| Component: | RPM Packages | Assignee: | Thierry Vignaud <thierry.vignaud> |
| Status: | RESOLVED DUPLICATE | QA Contact: | |
| Severity: | normal | ||
| Priority: | Normal | CC: | marja11, thierry.vignaud |
| Version: | 6 | Keywords: | NEEDINFO |
| Target Milestone: | --- | ||
| Hardware: | i586 | ||
| OS: | Linux | ||
| See Also: | https://bugs.mageia.org/show_bug.cgi?id=21814 | ||
| Whiteboard: | |||
| Source RPM: | drakconf-13.16-1.mga6, webkit2 | CVE: | |
| Status comment: | |||
|
Description
Mauricio Andrés Bustamante Viveros
2018-04-30 19:34:04 CEST
Trying to uninstall webkit2 update to see if is reproducible Downgraded the webkit2 package, the MCC opens normally Reinstalling the update to detect if was update error or package error Status:
NEW =>
UNCONFIRMED Confirmed after reinstalling the webkit2 2.20 packages (5 packages) Status:
UNCONFIRMED =>
NEW (In reply to Mauricio Andrés Bustamante Viveros from comment #1) > Trying to uninstall webkit2 update to see if is reproducible (In reply to Mauricio Andrés Bustamante Viveros from comment #2) > Downgraded the webkit2 package, the MCC opens normally > > Reinstalling the update to detect if was update error or package error (In reply to Mauricio Andrés Bustamante Viveros from comment #3) > Confirmed after reinstalling the webkit2 2.20 packages (5 packages) I was going to close this bug as duplicate of bug 21814, but this information isn't in that report. Did you reboot or restart X after every webkit2 update/downgrade ? Summary:
drakconf crashed =>
drakconf crashed after updating webkit2, downgrading it fixes it (another: Could not locate symbol webkit_web_view_new at /usr/lib/libDrakX/mygtk3.pm line 621)
Marja Van Waes
2018-05-01 09:14:59 CEST
Assignee:
bugsquad =>
mageiatools Good morning Yes, I restarted the VM fully in that qa testing and the issue was not noted because mageiaupdate worked again Yesterday, I did the same after forced downgrade and update again to validate the issue Sight... I love WebKit stability :-) Can you list the working & the non working webkit2 NVR (name-version-release) ? Thx CC:
(none) =>
thierry.vignaud HI again QA Worked with the following packages.... after the fault, I downgrade to these versions and worked again libwebkit2gtk4.0_37-2.18.6-1.mga6.i586.rpm webkit2-2.18.6-1.mga6.i586.rpm webkit2-jsc-2.18.6-1.mga6.i586.rpm Faulty version libwebkit2gtk4.0_37-2.20.1-1.mga6.i586.rpm webkit2-2.20.1-1.mga6.i586.rpm webkit2-jsc-2.20.1-1.mga6.i586.rpm That's strange as we have the same drakconf & the same webkit 2.20.1 in cauldron and that works fine I Did other tests using urpmi and rpm, with the locally downloaded files to downgrade and reinstall the update, sometimes the webkit 2.18 version segfault too This appears like an script in the rpm package that is not executed when multi transactions are required (installing multi updates in one session).... Reinstalled the webkit only (five packages) from jussieu mirror using mgaapplet, this update is working without issue.... (In reply to Marja Van Waes from comment #4) > (In reply to Mauricio Andrés Bustamante Viveros from comment #1) > > Trying to uninstall webkit2 update to see if is reproducible > > (In reply to Mauricio Andrés Bustamante Viveros from comment #2) > > Downgraded the webkit2 package, the MCC opens normally > > > > Reinstalling the update to detect if was update error or package error > > (In reply to Mauricio Andrés Bustamante Viveros from comment #3) > > Confirmed after reinstalling the webkit2 2.20 packages (5 packages) > > I was going to close this bug as duplicate of bug 21814, but this > information isn't in that report. > (In reply to Mauricio Andrés Bustamante Viveros from comment #9) > I Did other tests using urpmi and rpm, with the locally downloaded files to > downgrade and reinstall the update, sometimes the webkit 2.18 version > segfault too > Thanks for all the feedback, Mauricio :-) Closing as duplicate now. *** This bug has been marked as a duplicate of bug 21814 *** Resolution:
(none) =>
DUPLICATE |