Bug 1349518

It looks like this is caused by my exclude= line in /etc/yum.repos.d/fedora.repo which is:

exclude=kernel-devel kernel-debug-devel

If I comment out that line then it works.

Any word on this? To summarize:

packagekit (and therefore gnome-software) crashes if any packages are excluded via exclude= in the base Fedora repo (/etc/yum.repos.d/fedora.repo).

Same here I'm running kde and when I run packagekitd in the foreground and initiate an update check through the plasma widget packagekitd crashes with the following message: packagekitd: /builddir/build/BUILD/hawkey-0.6.3/src/sack.c:838: hy_sack_add_excludes: Assertion `excl->size >= nexcl->size' failed

I'm now running PackageKit 1.1.3-1.fc24, the latest update, and this issue still persists.

I have what appears to be the same issue. However, I have different "excludes":

$ fgrep -i exclude *
fedora-updates.repo:exclude=xpra
rpmfusion-nonfree.repo:exclude=nautilus-dropbox


Similar log:
Aug  1 07:02:41 aschmidt packagekitd: packagekitd: /builddir/build/BUILD/hawkey-0.6.3/src/sack.c:838: hy_sack_add_excludes: Assertion `excl->size >=
 nexcl->size' failed.
Aug  1 07:02:41 aschmidt audit: ANOM_ABEND auid=4294967295 uid=0 gid=0 ses=4294967295 subj=system_u:system_r:rpm_t:s0 pid=14151 comm="PK-Backend" ex
e="/usr/libexec/packagekitd" sig=6
Aug  1 07:02:41 aschmidt abrt-hook-ccpp: Process 14113 (packagekitd) of user 0 killed by SIGABRT - dumping core
Aug  1 07:02:43 aschmidt plasmashell: PK error: "The PackageKit daemon has crashed" type: "process-kill"
Aug  1 07:02:43 aschmidt audit: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=packagekit comm="
systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'
Aug  1 07:02:43 aschmidt systemd: packagekit.service: Main process exited, code=killed, status=6/ABRT
Aug  1 07:02:43 aschmidt systemd: packagekit.service: Unit entered failed state.
Aug  1 07:02:43 aschmidt systemd: packagekit.service: Failed with result 'signal'.


"pkcon update" has a somewhat different behavior:

# pkcon update
Getting updates               [========                 ] (35%)

...and here it will stay, silent, until killed.

This bug seems to have flown under the radar. Some suggestions for the OP. 

1). Change the topic to "Excludes crashes PackageKit and Gnome Software". 

2). Set the priority severity of the bug to "High" 

Maybe that will catch the attention of maintainers. It's a shame this bug has existed for months now with no acknowledgement.

In the end, though, the impact to the end user isn't high.

The only real problem is that plasma-pk-updates runs by default, and there's no obvious replacement that uses a stable back-end.

dnf-automatic works fine. It just isn't ... you know ... sexy.

@mystilleef I was told in the IRC channel (albeit, several weeks ago) that this was being looked into. But I'll try changing the title.

Personally this doesn't bother me a ton because I do not use any packagekit frontends for updates, I only use dnf, but I agree that this is a pretty nasty bug that has existed for too long.

Had the same issue with:

gnome-software-3.20.4-1.fc24.x86_64
PackageKit-1.1.3-2.fc24.x86_64

The Software app would start, but nothing would load inside the "All" or "Installed" tabs. `pkcon refresh` would crash as described above.

Removing these exclude lines fixed `pkcon refresh`:

$ grep "exclude" *
fedora.repo:exclude=postgresql*
fedora-updates.repo:exclude=postgresql*

The Software app worked properly again after I commented out the exclude lines, ran `pkcon refresh`, and rebooted.

Bug 1377969 might be a duplicate of this one.

I say "might" because I'm seeing similar a similar backtrace at:

https://retrace.fedoraproject.org/faf/reports/1324126/

...and that references Bug 1377969, but I'm not allowed to see it. Ours is older, and it would be cuckoo-bananas to lock that one up but not this one, but there you go.

Same behavior here. Please fix it :(

Hmmm I guess it works on 25?

Yep, this appears to be fixed for me now on F25.

Can we go ahead and close this? Is anyone else still having the problem? It seems to be fixed for since upgrading to F25.

*** Bug 1350732 has been marked as a duplicate of this bug. ***

Not fixed in F24 

The daemon crashed mid-transaction!

(In reply to Sergio Monteiro Basto from comment #16)
> Not fixed in F24 
> 
> The daemon crashed mid-transaction!

This has been fixed in F25, and the F25 RPMS will install in F24. You'll need
PackageKit
PackageKit-glib
PackageKit-gstreamer-plugin

(In reply to Devin Henderson from comment #14)
> Can we go ahead and close this? Is anyone else still having the problem? It
> seems to be fixed for since upgrading to F25.

Sadly no. Although the crash issue is resolved, the side effect is "exclude" parameter is not honoured by PackageKit inside repo file. 

For example, I use copr repository for the kernel 4.9.x and exclude an upgrade from fedora-updates.repo to kernel 4.10.x as illustrated below:
$ grep "exclude" *
fedora-updates.repo:exclude=kernel*

$ dnf check-update | grep kernel

Despite clearing the cache with "pkcon refresh force"

$ pkcon get-updates | grep kernel
Available    kernel-4.10.6-200.fc25.x86_64 (updates)
Available    kernel-core-4.10.6-200.fc25.x86_64 (updates)
Available    kernel-headers-4.10.6-200.fc25.x86_64 (updates)
Available    kernel-modules-4.10.6-200.fc25.x86_64 (updates)

This message is a reminder that Fedora 24 is nearing its end of life.
Approximately 2 (two) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 24. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '24'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 24 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged  change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

@Luya Tshimbalanga:

Is that happening to you on F25 or F26? Lets keep this ticket open and reassign it to the correct Fedora version and hopefully we'll get a response on that issue.

(In reply to Devin Henderson from comment #20)
> @Luya Tshimbalanga:
> 
> Is that happening to you on F25 or F26? Lets keep this ticket open and
> reassign it to the correct Fedora version and hopefully we'll get a response
> on that issue.

Not sure yet. If it safe to assign "version" to 26 for the time being.

Sadly it is still happening. PackageKit does not honour exclude parameter.

I'm marking as duplicated becuase there is no point have 2 bugs where we talk of same thing ...

*** This bug has been marked as a duplicate of bug 1256108 ***