Your message dated Sun, 16 Apr 2023 18:41:39 +0200
with message-id 
<CAKNHny8ampMc72zkar114Pn4L12bTNOSaww=agwoj6-b0ab...@mail.gmail.com>
and subject line Re: Bug#688133: packagekit-backend-aptcc: Running apt-get 
fails after doing any system upgrade with apper.
has caused the Debian Bug report #688133,
regarding packagekit-backend-aptcc: Running apt-get fails after doing any 
system upgrade with apper.
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
688133: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=688133
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: packagekit-backend-aptcc
Version: 0.7.5-2
Severity: normal

Dear Maintainer,
When i get a notification that there are some available updates, if i use apper 
to do the updates, 
wait for it to finish, and then close it, if i run apt-get install 
<package_name> 
i get an error that "Could not get lock /var/cache/apt/archives/lock - open".
I check processes running, and i see apper-sentinel.Killing it doesn't make any 
difference.
There is however a "packagekitd" process.Killing it does the trick. 


-- System Information:
Debian Release: wheezy/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 3.2.0-3-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages packagekit-backend-aptcc depends on:
ii  app-install-data    2012.06.16.1
ii  libapt-inst1.5      0.9.7.4
ii  libapt-pkg4.12      0.9.7.4
ii  libc6               2.13-35
ii  libgcc1             1:4.7.1-7
ii  libglib2.0-0        2.32.3-1
ii  libgstreamer0.10-0  0.10.36-1
ii  libstdc++6          4.7.1-7
ii  libxml2             2.8.0+dfsg1-5
ii  python              2.7.3~rc2-1
ii  python-packagekit   0.7.5-2

Versions of packages packagekit-backend-aptcc recommends:
ii  apt-xapian-index  0.45
ii  packagekit        0.7.5-2

Versions of packages packagekit-backend-aptcc suggests:
pn  gdebi-core  <none>

-- no debconf information

--- End Message ---
--- Begin Message ---
Hi!

Please do never kill packagekitd, you might damage your sysrem with
that in case it is still performing APT operations in the background!
Newer versions of PackageKit have refined logic for locking and
release the APT lock sooner, so encountering this situation *without*
PK actually doing anything is a lot less likely. In addition, we also
updated APT to give more informative messages in case caches are
locked.

Cheers,
    Matthias

--- End Message ---

Reply via email to