• Re: Bug#1062190: packagekit: locks the dpkg frontened in the middle of

    From Julian Andres Klode@21:1/5 to Julian Andres Klode on Sat Apr 5 00:10:01 2025
    Control: reassign -1 synaptic
    Control: retitle -1 synaptic: releases frontend lock while running dpkg

    On Fri, Apr 04, 2025 at 11:55:34PM +0200, Julian Andres Klode wrote:
    On Sun, Mar 23, 2025 at 11:22:43AM +0100, Paul Gevers wrote:
    On Wed, 31 Jan 2024 17:15:41 +0100 Matthias Klumpp <mak@debian.org> wrote:
    Do you have any idea how this would be possible? Both PK and Synaptic should hold the APT frontend lock, so they should never be able to run
    at the same time.

    If packagekit checks for the lock (I assume you claim it does), isn't it synaptics fault to not grab the lock? I.e. isn't this bug filed against the wrong package?

    Both synaptic and PackageKit need to support the frontend lock, I don't
    know if they do, that may involve calling UnLockInner() rather than
    UnLock(), and LockInner() rather than Lock() to regain released inner
    locks in some places.

    synaptic calls releaseLock() before running dpkg; which in turn calls
    APT's UnLock(). I believe, but am not sure, that we can drop that call
    entirely and APT should do the right thing.

    I don't quite know and I'd need to do more investigation and a trial
    and error attempt :D
    --
    debian developer - deb.li/jak | jak-linux.org - free software dev
    ubuntu core developer i speak de, en

    -----BEGIN PGP SIGNATURE-----

    wsG7BAABCgBvBYJn8FaZCRBvpFjdHbA/cUcUAAAAAAAeACBzYWx0QG5vdGF0aW9u cy5zZXF1b2lhLXBncC5vcmez/kzU6VrFvkZ4BnY6wVqMXPdkTG0a3TdD11hnvI7r UxYhBE+1iKhMLd55p0x3h2+kWN0dsD9xAAAYjhAAm8SsOX24LucnOYrwdjj52FAi N+Jo6/Kp2z6SC8QjT6VBTOQOemyrj1RaxSS22Wq9MWehx1PJWnbT9Gwu8miGSjHO GAX9YCTiwXdTrGcl40CZrq7PjEuvcS8QfhhVkFfxnTZPhX9QdgVJ+vkAohfdFjTl 9wyviHlrhE8D+PTLwfurl/5DScglFi1jjg/w7Fv7kFfVOkxidBd6tvDOj6yUHV7a N0AIg+Biggm1phZN+9wKF/0fdsbYRxFtsl1vj40dXIqQYBWwrOU6HX3M8TGEXqtD f1QNTtA7fcbWUJwvjvSq8GWtHJfzS4Hq3vCU50M+z4ctoM87jKGTNy8SVwM7OOZN v3vfUhV/Yt14IFXnlwyg5qn2nkhnXzLTGZB7oogLJLG8JcgKNj4j9Jw3RMRHtBo2 pb6EPhJGkSCJKyuNAMNMDQgnoJfyxpWwT1t/Te/QjJ2plK3lXIF7JCQT+JQc0A2z ToWaAP5+3/PN5T5W/YNWtGdrxewejbTHyrJSRNk+bLx681fVv/96Y7bDVRRE1gyQ tKa9No0jRHU5R3sqdgZoQ69ZPA0XB+278fqSyHGbc3IHiI1p42oz0ypnSs1CcRnt Ag6gX1SPLyZQBNCzQXI5HFalmNMXAKngX4x2VyemfWhdZCZ1wnjPqALcHm
  • From Michael Vogt@21:1/5 to Julian Andres Klode on Sun Apr 6 18:40:02 2025
    On Sat, Apr 5, 2025, at 00:00, Julian Andres Klode wrote:
    [..]
    synaptic calls releaseLock() before running dpkg; which in turn calls
    APT's UnLock(). I believe, but am not sure, that we can drop that call entirely and APT should do the right thing.

    I don't quite know and I'd need to do more investigation and a trial
    and error attempt :D

    Thanks for the bugreport and the help diagnosing it!
    I pushed a small change into https://github.com/mvo5/synaptic/commit/928ce5bd19bdd810a6920831a8d738d016edb2d8
    that should fix it and will upload shortly.

    Thanks,
    Michael

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)