Bug 8158

Created attachment 3129 [details]
Copy/paste of the konsole commands and response

Can you reproduce the segfault?
If yes, can you:
1) enable the debug media in rpmdrake,
2) then install glibc-debug, rpm-debug, perl-debug, perl-URPM-debug & gdb packages
3) run "gdb -q --args perl /usr/sbin/urpmi --auto-select"
4) type "run"
5) wait for it to segfault
6) type "bt"
7) copy the backtrace displayed by gdb in a text file you'll attach to this bug report.

I'm seeing the same.

One thing I've noticed is it doesn't happen if fewer than 500 packages or so are to be installed. 

Also of note is that installing the same packages through the GUI doesn't result in the segmentation fault. 
There is when using the GUI usually, maybe always, one or more packages that fail to install but the rest do.

CC: (none) => kbergen

Created attachment 3133 [details]
Copy/paste of konsole output according to Comment #2

This has konsole dialog has been obtained after the second segfault (problem description - the one that gives the "... Freeing read locks ..." messages).

Thank you Ken - I started having doubts why I was the only one to observe this problem.

I have now attached the konsole dialog as requested by Thierry - it is the one I obtain after the second segfault (see problem description - the one that gives the "... Freeing read locks ..." messages). Thierry, in case the original one - the one that happens immediately after the install, would help, say so. It would require doing a fresh install of my test partition, but that does not take too much time.

And thanks for correcting the subject line - it was wrong, in fact urpmi does install, but than breaks (and sounds like a headline of some of those popular journals)

Ken, I applied some kind of work-around to get back to normal on my "production" file-system with Mageia 3 Alpha:
- I used rpm -i --force to reload urpmi-7.10-1 and perl-URPM-4.15.1-1, and did rpm -e to remove the newly installed packages (no idea whether this is necessary for perl-URPM - did it to be on the safe side).
- I added urpmi and perl-URPM in the skip-list (both versioned to avoid mis-chief in case I forget to remove these items)

When I then did urpmi--auto-select, urpmi wants to redo everything - did not take excessively long since I have all but the most recent update packages on a local mirror

I need the following from someone who can reproduce thus bug:
Once you got the segfault, do not do anything but just run this:

urpmi --auto-select --bug=bug8158
tar cfa bug8158{.tar.xz,}
This way, I might be able to reproduce it and hopefully debug it

Then send me by email the bug8158.tar.xz file resulting from those commands.

That please do not do what's advised in comment #6
Else I won't be able to debug this bug report.

CC: (none) => tmb

After using drakrpm-update to update I am no longer able to reproduce the bug. 
If Mr. Harms is unable to reproduce it I could do a fresh install later in the week.

I eventually have found a way of reproducing it:
ROOT=/T
mkdir $ROOT/dev -p
urpmi.addmedia --distrib /mageia/stable/x86_64/ --urpmi-root $ROOT
# initscripts vs ppp conflicts:
echo ppp > $ROOT/etc/urpmi/skip.list
urpmi --urpmi-root $ROOT basesystem task-kde4 --auto --justdb
urpmi.removemedia --urpmi-root $ROOT -a
urpmi.addmedia --distrib /mageia/unstable/x86_64/ --urpmi-root $ROOT
urpmi --urpmi-root $ROOT --auto-select --auto --justdb

Keywords: NEEDINFO => (none)
Status: NEW => ASSIGNED
Summary: Urpmi fails to install updates (segfault) => Urpmi fails to install updates (segfault with big transactions)

Re comment #8: I did that on another OS partition, the one on which I documented the bug is in its original state, I keep it as a guinea-pig file-system.

Fixed

Status: ASSIGNED => RESOLVED
Resolution: (none) => FIXED