** Changed in: plasma-discover (Ubuntu)
Status: Confirmed => Fix Released
** Changed in: plasma-discover (Ubuntu Bionic)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Already in Cosmic
https://launchpad.net/ubuntu/+source/packagekit/1.1.10-1ubuntu7
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1790613
Title:
Regression: packagekit crashes updating itself to a
Has it been fixed in/checked for 18.10 (Cosmic)?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1790613
Title:
Regression: packagekit crashes updating itself to a new version
To manage
This bug was fixed in the package packagekit - 1.1.9-1ubuntu2.18.04.3
---
packagekit (1.1.9-1ubuntu2.18.04.3) bionic; urgency=medium
* Pass --no-restart-after-upgrade to dh_installsystemd to avoid PackageKit
restarting while upgrading under PackageKit (LP: #1790613)
packagekit
>From release to updates:
# pkcon install packagekit
Resolving [=]
Testing changes [=]
Finished [ ] (0%)
The following packages have to be updated:
Hello Rik, or anyone else affected,
Accepted packagekit into bionic-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/packagekit/1.1.9-1ubuntu2.18.04.3
in a few hours, and then in the -proposed repository.
Please help us by testing this new package.
This bug was fixed in the package packagekit - 1.1.10-1ubuntu7
---
packagekit (1.1.10-1ubuntu7) cosmic; urgency=medium
* Pass --no-restart-after-upgrade to dh_installsystemd to avoid PackageKit
restarting while upgrading under PackageKit (LP: #1790613)
-- Julian Andres Klode
FWIW, the option to pass is --no-restart-after-upgrade
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1790613
Title:
Regression: packagekit crashes updating itself to a new version
To manage
Uploaded, both in unapproved
** Changed in: packagekit (Ubuntu)
Status: Triaged => Fix Committed
** Changed in: packagekit (Ubuntu Bionic)
Status: Triaged => In Progress
** Changed in: packagekit (Ubuntu)
Status: Fix Committed => In Progress
--
You received this bug
** Description changed:
+ [Impact]
Bionic: 18.04
Version: 1.1.9-1ubuntu2 upgrading itself to 1.1.9-1ubuntu2.18.04.1
Updating with pkcon upgrade or plasma-discover crashes packagekit mid
transaction, requiring user intervention on the command line.
In plasma-discover the gui
Yes, I completely missed that change, this needs to be changed.
I need to prepare a new upload for Debian anyway, maybe I can change this
behavior on the weekend at Debian.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
The default changed to restart in debhelper 10. I think we need (one
of?) --no-restart-on-upgrade --no-restart-after-upgrade passed to
dh_installsystemd.
--
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to the bug report.
Of course we do:
if [ "$1" = "configure" ] || [ "$1" = "abort-upgrade" ] || [ "$1" =
"abort-deconfigure" ] || [ "$1" = "abort-remove" ] ; then
if [ -d /run/systemd/system ]; then
systemctl --system daemon-reload >/dev/null || true
if [ -n "$2" ]; then
We don't actively kill PackageKit when updating it, we just tell the daemon to
quit itself as soon as possible if it can do so.
Also, a packagekitd times out automatically when inactive.
So this crash really shouldn't happen...
--
You received this bug notification because you are a member of
>> I don't think there is a solution for this problem.
So why has it only started to happen recently?
What about treating it like a kernel update - don't restart the process
but schedule/request a reboot?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I don't think there is a solution for this problem. We can stop
restarting packagekit to fix the crash, but then you end up with old
packagekitd's running. So if there is a security update in packagekit or
one of its libraries, it would not take effect. Not sure how to fix this
properly.
--
You
** Summary changed:
- Regression: packagekit crashes updating itself to 1.1.9-1ubuntu2.18.04.1
+ Regression: packagekit crashes updating itself to a new version
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
17 matches
Mail list logo
