Bug 1626796

Summary: packagekitd crashed in g_error_new_valist
Product: [Fedora] Fedora Reporter: Sanne Raymaekers <sraymaek>
Component: PackageKitAssignee: Richard Hughes <rhughes>
Status: CLOSED CURRENTRELEASE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 29CC: jonathan, klember, mpitt, rdieter, rhughes, smparrish
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-11-06 21:22:06 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
backtrace
none
journal none

Description Sanne Raymaekers 2018-09-08 20:29:14 UTC
Created attachment 1481812 [details]
backtrace

Crash in packagekitd. Not sure how to reproduce it, somewhere in checking for available updates without a network connection.

Version:
PackageKit-1.1.10-4.fc29.x86_64
1.1.10 with libdnf 0.17.2


Truncated bt:

Core was generated by `/usr/libexec/packagekitd'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  0x00007fca07df18c7 in __strlen_avx2 () from /lib64/libc.so.6
#1  0x00007fca07ce33c7 in vfprintf () from /lib64/libc.so.6
#2  0x00007fca07d9e7fc in __vasprintf_chk () from /lib64/libc.so.6
#3  0x00007fca07fcb1cd in g_vasprintf () from /lib64/libglib-2.0.so.0
#4  0x00007fca07fa4681 in g_strdup_vprintf () from /lib64/libglib-2.0.so.0
#5  0x00007fca07f6e826 in g_error_new_valist () from /lib64/libglib-2.0.so.0
#6  0x00007fca07f6ec1f in g_set_error () from /lib64/libglib-2.0.so.0
#7  0x00007fc9f88595bd in dnf_repo_update ()
    at /usr/src/debug/libdnf-0.17.2-1.fc29.x86_64/libdnf/dnf-repo.cpp:1819
...

Comment 1 Sanne Raymaekers 2018-09-08 20:30:24 UTC
Created attachment 1481813 [details]
journal

Comment 2 Martin Pitt 2018-11-06 21:22:06 UTC
This hasn't happened in two months, so apparently this got fixed in PackageKit 0.1.11.