Bug 20824 - Machine just booted, logged in and oops, got a segfault in net_applet (after overclocking CPU a bit)
Summary: Machine just booted, logged in and oops, got a segfault in net_applet (after ...
Status: RESOLVED WORKSFORME
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: x86_64 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords: NEEDINFO
Depends on:
Blocks:
 
Reported: 2017-05-10 19:45 CEST by Stig-Ørjan Smelror
Modified: 2017-05-13 18:49 CEST (History)
2 users (show)

See Also:
Source RPM: drakx-net, gtk+3.0 ?
CVE:
Status comment:


Attachments

Description Stig-Ørjan Smelror 2017-05-10 19:45:49 CEST
The "net_applet" program has segfaulted with the following error:

  SEGV
  Glibc's trace:
  4: /lib64/libperl.so.5.22(Perl_sighandler+0x213) [0x7f735aa830f3]
  5: /lib64/libpthread.so.0(+0x10bb0) [0x7f735a7b9bb0]
  6: /lib64/libperl.so.5.22(Perl_sv_clear+0x724) [0x7f735aaa0084]
  7: /lib64/libperl.so.5.22(Perl_sv_free2+0x5d) [0x7f735aaa032d]
  8: /lib64/libperl.so.5.22(Perl_gp_free+0x275) [0x7f735aa21f85]
  9: /lib64/libperl.so.5.22(Perl_sv_clear+0x823) [0x7f735aaa0183]
  10: /lib64/libperl.so.5.22(Perl_sv_free2+0x5d) [0x7f735aaa032d]
  11: /lib64/libperl.so.5.22(Perl_leave_scope+0xd41) [0x7f735aacdd11]
  12: /lib64/libperl.so.5.22(Perl_pp_leave+0xc6) [0x7f735aad84f6]
  13: /lib64/libperl.so.5.22(Perl_runops_standard+0x16) [0x7f735aa93b86]
  14: /lib64/libperl.so.5.22(Perl_call_sv+0x50e) [0x7f735aa1991e]
  15: /usr/lib/perl5/vendor_perl/5.22.2/x86_64-linux-thread-multi/auto/Glib/Glib.so(+0x26833) [0x7f7351817833]
  16: /lib/../lib64/libgobject-2.0.so.0(g_closure_invoke+0x145) [0x7f73515aef05]
  17: /lib/../lib64/libgobject-2.0.so.0(+0x2b032) [0x7f73515ca032]
  18: /lib/../lib64/libglib-2.0.so.0(+0x4a3b3) [0x7f73512d63b3]
  19: /lib/../lib64/libglib-2.0.so.0(g_main_context_dispatch+0x13a) [0x7f73512d597a]
  
  Perl's trace:
  drakbug::bug_handler() called from /usr/lib/libDrakX/drakbug.pm:41
  drakbug::__ANON__() called from /usr/lib/perl5/vendor_perl/5.22.2/MDK/Common/File.pm:151
  (eval)() called from /usr/lib/perl5/vendor_perl/5.22.2/MDK/Common/File.pm:151
  MDK::Common::File::cat_() called from /usr/lib/libDrakX/network/network.pm:76
  network::network::read_resolv_conf_raw() called from /usr/lib/libDrakX/network/network.pm:83
  network::network::read_resolv_conf() called from /usr/lib/libDrakX/network/tools.pm:215
  network::tools::get_default_connection() called from /usr/bin/net_applet:440
  main::checkNetwork() called from /usr/bin/net_applet:458
  main::__ANON__() called from /usr/lib/perl5/vendor_perl/5.22.3/Gtk3.pm:566
  (eval)() called from /usr/lib/perl5/vendor_perl/5.22.3/Gtk3.pm:566
  Gtk3::main() called from /usr/lib/perl5/vendor_perl/5.22.3/Gtk3.pm:523
  Gtk3::__ANON__() called from /usr/bin/net_applet:334

Used theme: Adwaita

To submit a bug report, click on the report button.  
This will open a web browser window on Bugzilla where you'll find a form to fill in.  The information displayed above will be transferred to that server
It would be very useful to attach to your report the output of the following command: 'lspcidrake -v'.


--

Must add that I'm just bumped the clock speed on my CPU a tad as a test. From 3.4GHz to 3.8GHz.

Running Openbox, not KDE/Plasma.
Comment 1 Marja Van Waes 2017-05-13 16:54:26 CEST
Thanks for having added that you had overclocked a bit.

Can you reproduce this issue after reverting from 3.8GHz to 3.4GHz?

If so, then please attach lspci.txt that's the result of

    lspcidrake -v > lspci.txt

Summary: Machine just booted, logged in and oops, got a segfault => Machine just booted, logged in and oops, got a segfault in net_applet (after overclocking CPU a bit)
Source RPM: (none) => drakx-net, gtk+3.0 ?
Keywords: (none) => NEEDINFO
CC: (none) => mageiatools, marja11

Comment 2 Stig-Ørjan Smelror 2017-05-13 18:49:37 CEST
No, I can't reproduce this issue after downclocking the CPU.

There was only the one time and I've now set the CPU back to normal. Don't want instabilities.

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


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