Bug 2327

Summary: mgaapplet segfaulted
Product: Mageia Reporter: gil gil <puntogil>
Component: New RPM package requestAssignee: Mageia Bug Squad <bugsquad>
Status: RESOLVED DUPLICATE QA Contact:
Severity: normal    
Priority: Normal    
Version: Cauldron   
Target Milestone: ---   
Hardware: i586   
OS: Linux   
Whiteboard:
Source RPM: mgaonline-2.77.30-2.mga2 CVE:
Status comment:

Description gil gil 2011-07-29 12:11:53 CEST
The "mgaapplet" program crashed. Drakbug-13.60 caught it.

system upgarde

Backtrace was:
SEGV
standalone::bug_handler() called from /usr/lib/libDrakX/standalone.pm:220
standalone::__ANON__() called from /usr/bin/mgaapplet:924
(eval)() called from /usr/bin/mgaapplet:924
main::setState() called from /usr/bin/mgaapplet:881
main::go2State() called from /usr/bin/mgaapplet:722
main::silentCheck() called from /usr/bin/mgaapplet:875
main::checkUpdates() called from /usr/bin/mgaapplet:284
main::__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 3709
[Thread debugging using libthread_db enabled]
0xffffe430 in __kernel_vsyscall ()
#0  0xffffe430 in __kernel_vsyscall ()
#1  0x4817d123 in __waitpid_nocancel () from /lib/i686/libpthread.so.0
#2  0x46f322d8 in Perl_wait4pid ()
   from /usr/lib/perl5/5.14.1/i386-linux-thread-multi/CORE/libperl.so
#3  0x46fa69f4 in Perl_pp_waitpid ()
   from /usr/lib/perl5/5.14.1/i386-linux-thread-multi/CORE/libperl.so
#4  0x46f50068 in Perl_runops_standard ()
   from /usr/lib/perl5/5.14.1/i386-linux-thread-multi/CORE/libperl.so
#5  0x46ee8fac 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 3709] will be detached.

Quit anyway? (y or n) [answered Y; input not from terminal]
Kernel version = 3.0.0-desktop586-1.mga2
Distribution=Mageia release 2 (Cauldron) for i586
CPU=AMD Athlon(tm) II X4 640 Processor
Comment 1 Manuel Hiebel 2011-07-29 15:35:01 CEST
duplicate

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

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