[SOLVED] Here we are again, back in the mire

[rodgoslin]

I've recently updated my Mageia 3 with glibc. No probelems, plus all the stuff that came after it. Hoever, tonight on booting up my netbook, to check for more updates. I was a bit puzzled at the lack of the pop-up to thell me there were some. I was even more puzzled to note that this was because the Wi-Fi link was down. I brought up Network Centre and re-connected. 30 seconds later, and it was unconnected. I re-connected, for thirty more seconds, again and again. I brought up the monitor. seconds later, it disconnected, but this time there was a bug report to send off. Snag here was that with the Wi-Fi disconnecting after 30 seconds, I couldn't get the bug report out. I had to copy and paste the dialogue to a memory stick and pull it off on this machine, and here it is:-

Code: Select all

The "draknetcenter" program has segfaulted with the following error:

  SEGV
  Glibc's trace:
  4: /usr/lib/perl5/5.16.3/i386-linux-thread-multi/CORE/libperl.so(Perl_sighandler+0x1d0) [0xb761b490]
  5: /usr/lib/perl5/5.16.3/i386-linux-thread-multi/CORE/libperl.so(Perl_csighandler+0x99) [0xb7616ce9]
  6: linux-gate.so.1(__kernel_sigreturn+0) [0xffffe400]
  7: /lib/libgtk-x11-2.0.so.0(+0x7727a) [0xb5bbb27a]
  8: /lib/libgtk-x11-2.0.so.0(gtk_button_set_label+0x9b) [0xb5bbc5eb]
  9: /usr/lib/perl5/vendor_perl/5.16.2/i386-linux-thread-multi/auto/Gtk2/Gtk2.so(+0xac090) [0xb6050090]
  10: /usr/lib/perl5/5.16.3/i386-linux-thread-multi/CORE/libperl.so(Perl_pp_entersub+0x602) [0xb7635232]
  11: /usr/lib/perl5/5.16.3/i386-linux-thread-multi/CORE/libperl.so(Perl_runops_standard+0x18) [0xb762d138]
  12: /usr/lib/perl5/5.16.3/i386-linux-thread-multi/CORE/libperl.so(+0xea122) [0xb7668122]
  13: /usr/lib/perl5/5.16.3/i386-linux-thread-multi/CORE/libperl.so(Perl_pp_entertry+0x64) [0xb7677774]
  14: /usr/lib/perl5/5.16.3/i386-linux-thread-multi/CORE/libperl.so(Perl_runops_standard+0x18) [0xb762d138]
  15: /usr/lib/perl5/5.16.3/i386-linux-thread-multi/CORE/libperl.so(Perl_call_sv+0x1c5) [0xb75b94d5]
  16: /usr/lib/perl5/5.16.3/i386-linux-thread-multi/CORE/libperl.so(Perl_call_method+0x59) [0xb75b9ae9]
  17: /usr/lib/perl5/vendor_perl/5.16.2/i386-linux-thread-multi/auto/Net/DBus/DBus.so(_message_filter+0x1d8) [0xb58651d8]
  18: /lib/libdbus-1.so.3(dbus_connection_dispatch+0x383) [0xb57fe143]
  19: /usr/lib/perl5/vendor_perl/5.16.2/i386-linux-thread-multi/auto/Net/DBus/DBus.so(+0xfde0) [0xb5862de0]
 
  Perl's trace:
  standalone::bug_handler() called from /usr/lib/libDrakX/standalone.pm:225
  standalone::__ANON__() called from /usr/lib/libDrakX/network/connection_manager/gtk.pm:118
  (eval)() called from /usr/lib/libDrakX/network/connection_manager/gtk.pm:118
  network::connection_manager::gtk::update_on_status_change() called from /usr/lib/libDrakX/network/connection_manager.pm:261
  network::connection_manager::update_networks() called from /usr/lib/libDrakX/network/connection_manager/gtk.pm:169
  network::connection_manager::gtk::update_networks() called from /usr/lib/libDrakX/network/connection_manager.pm:296
  network::connection_manager::__ANON__() called from /usr/lib/perl5/vendor_perl/5.16.2/i386-linux-thread-multi/Net/DBus/Binding/Connection.pm:530
  Net::DBus::Binding::Connection::_message_filter() called from /usr/lib/perl5/vendor_perl/5.16.2/i386-linux-thread-multi/Net/DBus/Binding/Connection.pm:257
  Net::DBus::Binding::Connection::dispatch() called from /usr/lib/libDrakX/dbus_object.pm:62
  dbus_object::__ANON__() called from /usr/lib/libDrakX/mygtk2.pm:1461
  (eval)() called from /usr/lib/libDrakX/mygtk2.pm:1461
  mygtk2::flush() called from /usr/lib/libDrakX/mygtk2.pm:1451
  mygtk2::main() called from /usr/lib/libDrakX/ugtk2.pm:767
  ugtk2::main() called from /usr/lib/libDrakX/network/netcenter.pm:212
  network::netcenter::main() called from /usr/sbin/draknetcenter:28

Used theme: oxygen-gtk

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'.

Any ideas, anyone?

[rodgoslin]

Umm. It seems to be promarily a modem/router problem. Why I don't know. I've replaced the modem/router with another and the problem seems to have gone. Odd. The modem/router is new, I bought it as a spare, set it up, tested it and put it away. I'd swapped it in when I thought the old one was giving trouble. It ran ok for a week than decided it didn't like Wi-Fi devices and refused to talk to them