Bug#980035: [Aptitude-devel] Bug#980035: aptitude: segmentation fault when starting aptitude

On 2021-01-14 02:14:29 +0100, Axel Beckert wrote: > Since Julian has uploaded a fix as apt/2.1.18, would you mind checking > if you can still reproduce the issue in any way? I couldn't manage to reproduce it with apt 2.1.18. -- Vincent Lefèvre - Web: 100% accessible

Bug#980035: [Aptitude-devel] Bug#980035: aptitude: segmentation fault when starting aptitude

Control: clone -1 -2 Control: retitle -2 aptitude-run-state-bundle: uses some local files instead of only those from the bundle Control: tag -2 - security Control: tag -1 + moreinfo Control: severity -2 normal Hi Vincent, Vincent Lefevre wrote: > With the bundle, the crash occurs while the UI

Bug#980035: [Aptitude-devel] Bug#980035: aptitude: segmentation fault when starting aptitude

On 2021-01-13 14:46:21 +0100, Vincent Lefevre wrote: > On 2021-01-13 12:31:05 +0100, Julian Andres Klode wrote: > > Smells like 980037? Bug in APT's cache building upon mremap() in new > > code path in 2.1.16/17. > > Yes, I first rebuilt apt, and > > aptitude-run-state-bundle

Bug#980035: [Aptitude-devel] Bug#980035: aptitude: segmentation fault when starting aptitude

On 2021-01-13 12:31:05 +0100, Julian Andres Klode wrote: > Smells like 980037? Bug in APT's cache building upon mremap() in new > code path in 2.1.16/17. Yes, I first rebuilt apt, and aptitude-run-state-bundle aptitude-segv.bundle was still crashing, then applied the patch suggested at

Bug#980035: [Aptitude-devel] Bug#980035: aptitude: segmentation fault when starting aptitude

On Wed, Jan 13, 2021 at 10:29:17AM +0100, Vincent Lefevre wrote: > Package: aptitude > Version: 0.8.13-2+b1 > Severity: grave > Justification: renders package unusable > Tags: security > > I got a first "segmentation fault" just after updating ('u' in the TUI). > Now, each time I run aptitude, a