Bug 1627968 - packagekitd: terminate called after throwing an instance of 'SQLite3::LibException'
Summary: packagekitd: terminate called after throwing an instance of 'SQLite3::LibExce...
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: PackageKit
Version: 29
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Richard Hughes
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-09-12 02:12 UTC by Chris Murphy
Modified: 2019-11-27 19:27 UTC (History)
5 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2019-11-27 19:27:11 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
journal snippet (34.37 KB, text/plain)
2018-09-12 02:13 UTC, Chris Murphy
no flags Details
coredumpctl stack trace (4.40 KB, text/plain)
2018-09-12 02:14 UTC, Chris Murphy
no flags Details
coredumpctl gdb (26.29 KB, text/plain)
2018-09-12 02:50 UTC, Chris Murphy
no flags Details
coredumpctl gdb (25.88 KB, text/plain)
2018-09-12 03:02 UTC, Chris Murphy
no flags Details

Description Chris Murphy 2018-09-12 02:12:21 UTC
Description of problem:

I've got three PackageKit crashes reported in abrt and systemd-coredump.

System was successfully upgraded, and updated Fedora 28 -> Fedora 29.


Version-Release number of selected component (if applicable):
PackageKit-1.1.10-4.fc29.x86_64

How reproducible:
Three crashes today, but I have no idea what's triggering it. I'm not launching GNOME Software, and automatic updates are disabled.

Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

See attached journal excerpt, and also the coredumpctl info stack trace. Both abrt and coredumpctl say the coredump is not usable, so processing with gdb isn't possible for any of the three collected coredumps. That sounds like a problem too.

Comment 1 Chris Murphy 2018-09-12 02:13:47 UTC
Created attachment 1482520 [details]
journal snippet

Comment 2 Chris Murphy 2018-09-12 02:14:12 UTC
Created attachment 1482521 [details]
coredumpctl stack trace

Comment 3 Chris Murphy 2018-09-12 02:50:51 UTC
Created attachment 1482523 [details]
coredumpctl gdb

OK figured out how to get coredumpctl gdb to cooperate...

Comment 4 Chris Murphy 2018-09-12 03:02:36 UTC
Created attachment 1482524 [details]
coredumpctl gdb

couple debuginfos were missing

Comment 5 Ben Cotton 2019-10-31 20:42:31 UTC
This message is a reminder that Fedora 29 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 29 on 2019-11-26.
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 '29'.

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 29 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.

Comment 6 Ben Cotton 2019-11-27 19:27:11 UTC
Fedora 29 changed to end-of-life (EOL) status on 2019-11-26. Fedora 29 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.