The "MageiaUpdate" program crashed. Drakbug-13.58 caught it. Partial update of notebook (which failed to accept a rather large update of 146 updates in one move (after glibc got updated)). Backtrace was: Can't call method "flag_skip" on an undefined value at /usr/lib/perl5/vendor_perl/5.12.3/i386-linux-thread-multi/URPM/Resolve.pm line 1229. standalone::bug_handler() called from /usr/lib/perl5/vendor_perl/5.12.3/i386-linux-thread-multi/URPM/Resolve.pm:1229 URPM::_find_packages_obsoleting() called from /usr/lib/perl5/vendor_perl/5.12.3/i386-linux-thread-multi/URPM/Resolve.pm:1695 URPM::__ANON__() called from /usr/lib/perl5/vendor_perl/5.12.3/i386-linux-thread-multi/URPM/Resolve.pm:1712 URPM::request_packages_to_upgrade() called from /usr/lib/perl5/vendor_perl/5.12.3/Rpmdrake/pkg.pm:362 Rpmdrake::pkg::get_updates_list() called from /usr/lib/perl5/vendor_perl/5.12.3/Rpmdrake/pkg.pm:485 Rpmdrake::pkg::get_pkgs() called from /usr/lib/perl5/vendor_perl/5.12.3/Rpmdrake/gui.pm:628 Rpmdrake::gui::pkgs_provider() called from /usr/sbin/MageiaUpdate:257 main::run_treeview_dialog() called from /usr/sbin/MageiaUpdate:284 Kernel version = 2.6.38.8-desktop586-8.mga Distribution=Mageia release 1 (Official) for i586 CPU=Intel(R) Atom(TM) CPU N270 @ 1.60GHz
Assignee: bugsquad => thierry.vignaud
Created attachment 1516 [details] try patch Can you apply the patch, run MageiaUpdate and report back any "failed to find packages obsoleting" line in the terminal: aka open a terminal and run the following commands: su - cd /usr/lib/perl5/vendor_perl/5.12.3/i386-linux-thread-multi/ patch -p0 < /where/it/was/downloaded/4425.diff MageiaUpdate
Keywords: (none) => PATCH
Keywords: (none) => NEEDINFO
On Startup (Something like 84 to go at the moment): etting lock on urpmi using mirror http://mageia.webconquest.com/distrib/1/i586 retrieved $MIRRORLIST media/core/updates media_info/MD5SUM comparing /var/cache/urpmi/partial/MD5SUM and /var/lib/urpmi/Core Updates (distrib3)/MD5SUM medium "Core Updates (distrib3)" is up-to-date retrieved $MIRRORLIST media/nonfree/updates media_info/MD5SUM comparing /var/cache/urpmi/partial/MD5SUM and /var/lib/urpmi/Nonfree Updates (distrib13)/MD5SUM medium "Nonfree Updates (distrib13)" is up-to-date retrieved $MIRRORLIST media/tainted/updates media_info/MD5SUM comparing /var/cache/urpmi/partial/MD5SUM and /var/lib/urpmi/Tainted Updates (distrib23)/MD5SUM medium "Tainted Updates (distrib23)" is up-to-date retrieved $MIRRORLIST media/core/updates media_info/MD5SUM comparing /var/cache/urpmi/partial/MD5SUM and /var/lib/urpmi/Core Updates (distrib33)/MD5SUM medium "Core Updates (distrib33)" is up-to-date retrieved $MIRRORLIST media/nonfree/updates media_info/MD5SUM comparing /var/cache/urpmi/partial/MD5SUM and /var/lib/urpmi/Nonfree Updates (distrib43)/MD5SUM medium "Nonfree Updates (distrib43)" is up-to-date unlocking urpmi database getting lock on urpmi using mirror http://mageia.webconquest.com/distrib/1/i586 examining synthesis file [/var/lib/urpmi/Core Updates (distrib3)/synthesis.hdlist.cz] examining synthesis file [/var/lib/urpmi/Nonfree Updates (distrib13)/synthesis.hdlist.cz] examining synthesis file [/var/lib/urpmi/Tainted Updates (distrib23)/synthesis.hdlist.cz] examining synthesis file [/var/lib/urpmi/Core Updates (distrib33)/synthesis.hdlist.cz] examining synthesis file [/var/lib/urpmi/Nonfree Updates (distrib43)/synthesis.hdlist.cz] warning: cleaning stale lock unlocking urpmi database
Guess it won't be reproduced... :-( I've included a fix in perl-URPM for mga2
After pressing "enter" to begin the update, I was at about 38 left to go, but it failed again. Eventually, I turned-off almost all updates and updated only a few items at a time, like xulrunner, then gimp, then.... until I was left with kdm, the latest kernel, and the latest kernel vdm. When I updated kdm all by itself, it seemed to throw the screensaver on, and then I had to login into a fresh screen again. However, it seemed to keep the update this time. Previous attempts always seemed to reset back to needing to reload and retry installing 140something updates. After installing kdm, rebooted, and was left with just the latest kernel, and vdm, which seemed to update okay. rebooted, now up to date. If I was to guess, I would guess this large update problem seemed to have problems with kdm, but that's just guessing. Right now, all is updated okay. If you want to close this bug,, go ahead, unless you think there is something else I should try (to get more/other info).
Just rereading this now... forgot to apply the patch before running mageiaupdate. Sorry about that. Sorry for the bandwidth. Thanks for your help. Machine now updated.
Closing then
Status: NEW => RESOLVEDResolution: (none) => OLD