The "net_applet" program crashed. Drakbug-13.70.2 caught it. nothing SEGV Glibc's trace: 0: /usr/lib/libDrakX/auto/c/stuff/stuff.so(XS_c__stuff_C_backtrace+0xcf) [0xb77df904] 1: /usr/lib/perl5/5.14.2/i386-linux-thread-multi/CORE/libperl.so(Perl_pp_entersub+0x56d) [0x4e13867d] Perl's trace: standalone::bug_handler() called from /usr/lib/libDrakX/standalone.pm:224 standalone::__ANON__() called from /usr/bin/net_applet:291 (eval)() called from /usr/bin/net_applet:291 Theme name: Ia Ora Night Kernel version = 3.1.4-desktop586-1.mga2 Distribution=Mageia release 2 (Cauldron) for i586 CPU=AMD Athlon(tm) II X4 640 Processor
Summary: net_applet segfaulted => net_applet segfaulted (stuff.so )
bug 3865 could be a duplicate of this one, Perl's trace is the same. Reporter is the same, too.
CC: (none) => marja11Assignee: bugsquad => tmb
Assignee: tmb => mageia
Trying to ping 41 bug reports in one move, because nothing has happened with them for more than 3 months, they still have the status NEW or REOPENED, there is no "OK" on the Whiteboard and severity and priority are "normal" or higher. Is this one still valid for Mageia 2 rc? If it is and you're the assignee, please set status to ASSIGNED if you think this bug was assigned correctly. If for work flow reasons you can't do that, then please put OK on the whiteboard instead. If it wasn't assigned correctly, please assign back to Bug Squad and explain.
Hi, This bug was filed against cauldron, but we do not have cauldron at the moment. Please report whether this bug is still valid for Mageia 2. Thanks :) Cheers, marja
Keywords: (none) => NEEDINFO
Since there are insufficient details provided in this report for us to investigate the issue further, and we have not received feedback to the information we have requested above, we will assume the problem was not reproducible, or has been fixed in one of the updates we have released for the reporter's distribution. Users who have experienced this problem are encouraged to upgrade to the latest update of their distribution, and if this issue turns out to still be reproducible in the latest update, please reopen this bug with additional information. Closing as OLD.
Status: NEW => RESOLVEDResolution: (none) => OLD