| Summary: | PackageKit: hif_sack_add_sources(): packagekitd killed by SIGSEGV | ||
|---|---|---|---|
| Product: | PackageKit | Reporter: | Ankur Sinha (FranciscoD) <sanjay.ankur> |
| Component: | General | Assignee: | Richard Hughes <richard> |
| Status: | RESOLVED INVALID | QA Contact: | |
| Severity: | major | ||
| Priority: | medium | ||
| Version: | unspecified | ||
| Hardware: | x86-64 (AMD64) | ||
| OS: | Linux (All) | ||
| Whiteboard: | |||
| i915 platform: | i915 features: | ||
|
Description
Ankur Sinha (FranciscoD)
2014-08-26 03:18:22 UTC
[asinha@localhost ~]$ rpm -qa \*PackageKit\* PackageKit-command-not-found-0.9.4-4.fc21.x86_64 PackageKit-gstreamer-plugin-0.9.4-4.fc21.x86_64 PackageKit-0.9.4-4.fc21.x86_64 PackageKit-glib-0.9.4-4.fc21.x86_64 PackageKit-gtk3-module-0.9.4-4.fc21.x86_64 [asinha@localhost ~]$ Thanks for reporting this: I've added a missing error path in libhif, but the root issue must be something to do with something in /etc/yum.repos.d/ -- can you install/rebuild the libhif package here http://people.freedesktop.org/~hughsient/fedora/20/ please, install it then report the error back to this bz please? A simple "pkcon search name power" should trigger the error. It'll probably involve something like a "corrupt"/invalid .repo file, and if so, can you attach that file also to this bz please so I can add it to the self tests. Cheers. Hi Richard, Thanks for looking into this so quickly. You were right, I had a stray line in one of the repo files due to a copy paste error. The file looked like this: ---------------------- [dnf-nightlies] name=DNF nightlies for $releasever - $basearch baseurl=http://jenkins.cloud.fedoraproject.org/job/DNF/lastSuccessfulBuild/artifact/fedora-$releasever-$basearch-build/ cost=3000 enabled=1 skip_if_unavailable=True gpgcheck=0 It gives me: ---------------------- The last line being the stray one. I guess I didn't catch it because yum/dnf continued to ignore it and work properly. My mistake. Sorry :( Warm regards, Ankur Closing as invalid. |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.