[Bug 1815187] Re: Fix crash when opening DepCache before Cache
Julian Andres Klode
1815187 at bugs.launchpad.net
Wed Feb 13 13:25:13 UTC 2019
Broken in security (ubuntu2.19), fixed in proposed (ubuntu2.20).
root at tt:~# apt search -o RootDir=/dev/null foobar
Segmentation fault (core dumped)
root at tt:~# apt install apt libapt-pkg4.12
[...]
Unpacking libapt-pkg4.12:amd64 (1.0.1ubuntu2.20) over (1.0.1ubuntu2.19) ...
Unpacking apt (1.0.1ubuntu2.20) over (1.0.1ubuntu2.19) ...
[...]
root at tt:~# apt search -o RootDir=/dev/null foobar
W: Unable to read /dev/null/etc/apt/sources.list.d/ - DirectoryExists (20: Not a directory)
W: Unable to read /dev/null/etc/apt/sources.list - RealFileExists (20: Not a directory)
E: Could not open file /dev/null/var/lib/dpkg/status - open (20: Not a directory)
E: The package lists or status file could not be parsed or opened.
** Tags removed: verification-needed verification-needed-trusty
** Tags added: verification-done verification-done-trusty
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1815187
Title:
Fix crash when opening DepCache before Cache
Status in apt package in Ubuntu:
Fix Released
Status in apt source package in Trusty:
Fix Committed
Bug description:
[Impact]
apt search and probably other code crashes some time, as GetDepCache() in trusty does not call BuildCaches() first.
[Test case]
Run apt search -o RootDir=/dev/null foobar, make sure it does not crash.
[Regression potential]
There may be some locking implications, as we build caches when opening depcache first, without locks. That said, the same code is in use in all post-trusty releases, and they work fine.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1815187/+subscriptions
More information about the foundations-bugs
mailing list