| Summary: | mgaapplet segfaulted while connecting to a wireless access point | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Franklin Weng <franklin> |
| Component: | RPM Packages | Assignee: | Mageia Bug Squad <bugsquad> |
| Status: | RESOLVED DUPLICATE | QA Contact: | |
| Severity: | normal | ||
| Priority: | Normal | CC: | mageia, marja11 |
| Version: | Cauldron | ||
| Target Milestone: | --- | ||
| Hardware: | i586 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | mgaonline-2.77.30-2.mga2 | CVE: | |
| Status comment: | |||
| Attachments: | output of lspcidrake -v | ||
|
Marja Van Waes
2011-11-01 07:46:19 CET
Attachment 708 mime type:
application/octet-stream =>
text/plain (In reply to comment #0) > ---- > I was doing nothing while crashed. It just connected a wi-fi AP automatically. > > It crashed once and I launched it again with Alt+F2 and typed net_applet. It > crashed again. > > lspcidrake -v output attached. @ Olivier This bug was filed against mgaonline, but is it sure this can't be a drakx-net(-applet) issue? CC:
(none) =>
mageia, marja11 @ Olivier Forget about my question, Thierry is the assignee of another mgaapplet segfaulted bug, 1846, against an older version of mgaonline in Mga 1, I'll set this bug as a duplicate of 2218 (another mgaapplet segfaulted one with already 4 duplicates) and see whether I can get away with assigning it to Thierry ;) @ Franklin Thanks for the bug report. This particular issue has already been reported in our bug tracking system, but please feel free to report any further bugs you find. In general it is welcome to search for existing reports first to avoid filing duplicates. *** This bug has been marked as a duplicate of bug 2218 *** Status:
NEW =>
RESOLVED |
Created attachment 708 [details] output of lspcidrake -v The "mgaapplet" program crashed. Drakbug-13.61 caught it. Doing nothing. It connected a wi-fi AP automatically. It crashed once and I launched it again with Alt+F2 and typed net_applet. It crashed again. Backtrace was: SEGV standalone::bug_handler() called from /usr/lib/libDrakX/standalone.pm:220 standalone::__ANON__() called from /usr/bin/mgaapplet:297 (eval)() called from /usr/bin/mgaapplet:297 GDB backtrace was (its interesting part is below Perl_pp_fork() or Perl_pp_waitpid()): Attaching to program: /usr/bin/perl, process 1462 [Thread debugging using libthread_db enabled] 0xffffe424 in __kernel_vsyscall () #0 0xffffe424 in __kernel_vsyscall () #1 0xb76a3123 in __waitpid_nocancel () from /lib/i686/libpthread.so.0 #2 0xb77e62d8 in Perl_wait4pid () from /usr/lib/perl5/5.14.1/i386-linux-thread-multi/CORE/libperl.so #3 0xb785a9f4 in Perl_pp_waitpid () from /usr/lib/perl5/5.14.1/i386-linux-thread-multi/CORE/libperl.so #4 0xb7804068 in Perl_runops_standard () from /usr/lib/perl5/5.14.1/i386-linux-thread-multi/CORE/libperl.so #5 0xb779cfac in perl_run () from /usr/lib/perl5/5.14.1/i386-linux-thread-multi/CORE/libperl.so #6 0x08048c0e in main () A debugging session is active. Inferior 1 [process 1462] will be detached. Quit anyway? (y or n) [answered Y; input not from terminal] Kernel version = 3.0.0-server-1.mga2 Distribution=Mageia release 2 (Cauldron) for i586 CPU=Intel(R) Core(TM)2 Duo CPU T5870 @ 2.00GHz ---- I was doing nothing while crashed. It just connected a wi-fi AP automatically. It crashed once and I launched it again with Alt+F2 and typed net_applet. It crashed again. lspcidrake -v output attached.