Bug 23470 - drakconf crashed
Summary: drakconf crashed
Status: RESOLVED DUPLICATE of bug 21814
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 6
Hardware: x86_64 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-08-21 12:37 CEST by Andrew Lord
Modified: 2018-08-21 13:19 CEST (History)
0 users

See Also:
Source RPM:
CVE:
Status comment:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Andrew Lord 2018-08-21 12:37:06 CEST 
The "drakconf" program crashed. Drakbug-17.88.3 caught it.

Installed Mageia 6, then did update to all software using Mageia Control Centre.  
Then shut down (hard boot due to mouse pointer disappearing).
Then went to normal user and attempted to open Mageia Control Centre.
Repeatedly shut down laptop and rebooted but problem occurred every time. At this point, I am unable to update the software on my laptop using the Control Center.



Could not locate symbol webkit_web_view_new at /usr/lib/libDrakX/mygtk3.pm line 621.
Perl's trace:
drakbug::bug_handler() called from /usr/lib/perl5/5.22.3/Carp.pm:166
Carp::croak() called from /usr/lib/perl5/vendor_perl/5.22.2/x86_64-linux-thread-multi/Glib/Object/Introspection.pm:67
Glib::Object::Introspection::__ANON__() called from /usr/lib/libDrakX/mygtk3.pm:621
mygtk3::_gtk__WebKit_WebView() called from /usr/lib/libDrakX/mygtk3.pm:610
mygtk3::_gtk__WebKit2_WebView() called from /usr/lib/libDrakX/mygtk3.pm:122
mygtk3::_gtk() called from /usr/lib/libDrakX/mygtk3.pm:59
mygtk3::gtknew() called from /usr/libexec/drakconf:687

Theme name: Adwaita
Kernel version = 4.14.65-desktop-1.mga6
Distribution=Mageia release 6 (Official) for x86_64
CPU=Intel(R) Core(TM) i7-2760QM CPU @ 2.40GHz
Comment 1 Frédéric "LpSolit" Buclin 2018-08-21 13:19:03 CEST 
dupe

*** This bug has been marked as a duplicate of bug 21814 ***

Status: NEW => RESOLVED
Resolution: (none) => DUPLICATE
Note You need to log in before you can comment on or make changes to this bug.