The "MageiaUpdate" program crashed. Drakbug-13.58 caught it. running update for the 1st time Backtrace was: SEGV standalone::bug_handler() called from /usr/lib/libDrakX/standalone.pm:220 standalone::__ANON__() called from /usr/lib/perl5/vendor_perl/5.12.3/urpm/install.pm:294 (eval)() called from /usr/lib/perl5/vendor_perl/5.12.3/urpm/install.pm:294 urpm::install::install() called from /usr/lib/perl5/vendor_perl/5.12.3/urpm/main_loop.pm:278 ::urpm::main_loop::run() called from /usr/lib/perl5/vendor_perl/5.12.3/Rpmdrake/pkg.pm:868 Rpmdrake::pkg::perform_installation() called from /usr/lib/perl5/vendor_perl/5.12.3/Rpmdrake/gui.pm:921 Rpmdrake::gui::do_action__real() called from /usr/lib/perl5/vendor_perl/5.12.3/Rpmdrake/gui.pm:936 (eval)() called from /usr/lib/perl5/vendor_perl/5.12.3/Rpmdrake/gui.pm:936 Rpmdrake::gui::do_action() called from /usr/sbin/MageiaUpdate:192 main::__ANON__() called from /usr/lib/libDrakX/mygtk2.pm:1425 (eval)() called from /usr/lib/libDrakX/mygtk2.pm:1425 mygtk2::main() called from /usr/lib/libDrakX/ugtk2.pm:767 ugtk2::main() called from /usr/sbin/MageiaUpdate:273 main::run_treeview_dialog() called from /usr/sbin/MageiaUpdate:284 GDB backtrace was (its interesting part is below Perl_pp_fork() or Perl_pp_waitpid()): Attaching to program: /usr/bin/perl, process 8420 [Thread debugging using libthread_db enabled] 0x00007fe365adae3e in waitpid () from /lib64/libpthread.so.0 #0 0x00007fe365adae3e in waitpid () from /lib64/libpthread.so.0 #1 0x00007fe36686b817 in Perl_wait4pid () from /usr/lib/perl5/5.12.3/x86_64-linux-thread-multi/CORE/libperl.so #2 0x00007fe3668d2438 in Perl_pp_waitpid () from /usr/lib/perl5/5.12.3/x86_64-linux-thread-multi/CORE/libperl.so #3 0x00007fe366880d20 in Perl_runops_standard () from /usr/lib/perl5/5.12.3/x86_64-linux-thread-multi/CORE/libperl.so #4 0x00007fe36682942e in perl_run () from /usr/lib/perl5/5.12.3/x86_64-linux-thread-multi/CORE/libperl.so #5 0x0000000000400e84 in main () A debugging session is active. Inferior 1 [process 8420] will be detached. Quit anyway? (y or n) [answered Y; input not from terminal] Kernel version = 2.6.38.7-desktop-1.mga Distribution=Mageia release 1 (Official) for x86_64 CPU=AMD Athlon(tm) II X4 635 Processor
I was running update for the 1st time
Component: Release (media, process) => RPM PackagesSource RPM: rpmdrake-5.26.10-1.mga1 => mgaonline
Source RPM: mgaonline => rpmdrake
dupe *** This bug has been marked as a duplicate of bug 2154 ***
Status: NEW => RESOLVEDResolution: (none) => DUPLICATE
*** Bug 2732 has been marked as a duplicate of this bug. ***
CC: (none) => john.valsam
different stack trace
Status: RESOLVED => REOPENEDCC: (none) => thierry.vignaudResolution: DUPLICATE => (none)Summary: MageiaUpdate segfaulted => MageiaUpdate segfaulted in urpm/install.pm:294
@ r howard @ John Were you using oxygen-gtk theme when MageiaUpdate segfaulted?
CC: (none) => marja11
*** Bug 2840 has been marked as a duplicate of this bug. ***
I used KDE and whatever the default theme is.
just run drakbug from a terminal, it'll tell you which theme is in use
I have not used mageia in a while and can't boot into it now as my system is being used remotely by others. ( Reason I am not using mageia is lack of freenx support)
In reply to Comment 5 Marja, are you asking me? ( I opened bug 2732 which is duplicate of this one). Since I don't see another John in this (current) bug report, I can give you some information. I don't know it proves useful, but here it is: 1. No, I was not using oxygen-gtk theme (yet). I was using the default (ia-ora), because it was the initial update (the "first wave of updates", if you prefer the term), after the first reboot that follows every clean install. 2. The problem happened once, during that first update, I send the bug report, then then resumed the update process, and the rest of the packages that weren't installed (due to the "problem") were downloaded and installed correctly, without any further problem, or error. 3. The only packages installed, prior that update, were: rt2870-firmware & kernel-firmware-extra because the only internet connection I have the last months, is by a usb wi-fi. The packages were downloaded with another Mageia installation, from a Mageia mirror, and copied in /home of the new -then- Mageia installation. 4. During the installation (Free DVD x86_64), the only different I did from other installations was, that I didn't chose a "typical KDE", but a "custom" one. Again, only KDE, but checked all the selections in the first category (even "network client" & "games" which were not needed). Maybe some individual packages too, but I don't remember which ones. 5. Due to the above (No4), this installation doesn't exist any more (too many and unwanted packages in a small partition). But in the same partition, I did a new Mageia KDE 64-bit installation (typical this time), without any problem until now. That's all... I hope I didn't bore you to death.
(In reply to comment #10) > That's all... I hope I didn't bore you to death. You didn't. Thanks a lot for all the details you supplied!
This bug wasn't reproduced since september. Assigning to maintainer, for him to decide what to do with this report
Assignee: bugsquad => thierry.vignaudSeverity: major => normal
Let's close it if nobody can reproduce it
Status: REOPENED => RESOLVEDResolution: (none) => OLD