Thank you for investigating this.

The steps that I recorded against the bug are as much detail as I can
offer.
I suppose that I might be able to reproduce the steps, but that would 
require me to first install the old Ubuntu environment and Epiphany, and 
then once again upgrade to the new version.  This would not be practical 
for me -- I have no way to reproduce my old configuration --  and it 
would probably not be practical for you either.

But my basic theory is this:  if the user should use Remove/Reinstall in 
a case where the repo for the old version is different from that of the 
new one (old was supported under Ubuntu, and new was from a different 
repo), that perhaps Synaptic can be caused to reference an invalid 
object pointer related to either the old or new version.  This would be 
because of a bad assumption that Synaptic would make, that the removal 
and the reinstall are from the same or very similar sources.  When I did 
*only* a remove, and then *only* a reinstall, each operation proceeded 
successfully.

The bug may be very obscure, because it involved (a) the package being 
supported before, and non-supported after; and (b) the user's choice to 
attempt remove/reinstall as a single operation.  The worst effect was 
confusion on the user's part.  If I were not a developer I might have 
had more trouble finding a way to bypass the problem.

So while the same bug might "bite" under other circumstances, in my case 
I would have to rate it as a minor problem.

Thanks again for your work on this,

Victor  (Phoenix Arizona USA)

Jean-Baptiste Lallement wrote:
> Thank you for taking the time to report this bug and helping to make Ubuntu 
> better. Please answer these questions:
> 1. Is this reproducible?
> 2. If so, what specific steps should we take to recreate this bug? Be as 
> detailed as possible.
> This will help us to find and resolve the problem.
>
> ** Changed in: synaptic (Ubuntu)
>        Status: New => Incomplete
>
>

-- 
Crash on "mark for reinstall"
https://bugs.launchpad.net/bugs/500679
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to