Bug 1598313 - [abrt] gnome-abrt: g_settings_set_property(): python3.6 killed by SIGTRAP
Summary: [abrt] gnome-abrt: g_settings_set_property(): python3.6 killed by SIGTRAP
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-abrt
Version: 28
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: abrt
QA Contact: Fedora Extras Quality Assurance
URL: https://retrace.fedoraproject.org/faf...
Whiteboard: abrt_hash:eaa757befdaeaa039451291c863...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-07-05 06:08 UTC by Christian Stadelmann
Modified: 2019-05-28 18:55 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2019-05-28 18:55:33 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (159.19 KB, text/plain)
2018-07-05 06:08 UTC, Christian Stadelmann
no flags Details
File: core_backtrace (29.19 KB, text/plain)
2018-07-05 06:08 UTC, Christian Stadelmann
no flags Details
File: cpuinfo (1.32 KB, text/plain)
2018-07-05 06:08 UTC, Christian Stadelmann
no flags Details
File: dso_list (14.14 KB, text/plain)
2018-07-05 06:08 UTC, Christian Stadelmann
no flags Details
File: limits (1.29 KB, text/plain)
2018-07-05 06:08 UTC, Christian Stadelmann
no flags Details
File: proc_pid_status (1.31 KB, text/plain)
2018-07-05 06:08 UTC, Christian Stadelmann
no flags Details

Description Christian Stadelmann 2018-07-05 06:08:00 UTC
Version-Release number of selected component:
gnome-abrt-1.2.6-4.fc28

Additional info:
reporter:       libreport-2.9.5
backtrace_rating: 4
cmdline:        /usr/bin/python3 /usr/bin/gnome-abrt -p /var/spool/abrt/ccpp-2018-07-04-21:05:41.90900-31412
crash_function: g_settings_set_property
executable:     /usr/bin/python3.6
journald_cursor: s=32f7a5ebac454e659491152646c4b3ba;i=f770f;b=f0eae2bf66d64291ac19434d01c81cb6;m=67ca4a6d3;t=570311ee2367f;x=4b2242bf8b518534
kernel:         4.17.3-200.fc28.x86_64
rootdir:        /
runlevel:       N 5
type:           CCpp

Truncated backtrace:
Thread no. 1 (10 frames)
 #4 g_settings_set_property at gsettings.c:590
 #5 object_set_property at gobject.c:1441
 #6 g_object_new_internal at gobject.c:1833
 #8 pygobject_constructv at gobjectmodule.c:1000
 #9 pygobject_init at pygobject-object.c:1305
 #10 wrap_init at /usr/src/debug/python3-3.6.5-1.fc28.x86_64/Objects/descrobject.c:1172
 #11 wrapper_call at /usr/src/debug/python3-3.6.5-1.fc28.x86_64/Objects/descrobject.c:1172
 #12 _PyObject_FastCallDict at /usr/src/debug/python3-3.6.5-1.fc28.x86_64/Objects/abstract.c:2331
 #13 wrapperdescr_call at /usr/src/debug/python3-3.6.5-1.fc28.x86_64/Objects/descrobject.c:334
 #14 PyObject_Call at /usr/src/debug/python3-3.6.5-1.fc28.x86_64/Objects/abstract.c:2261

Potential duplicate: bug 1224307

Comment 1 Christian Stadelmann 2018-07-05 06:08:10 UTC
Created attachment 1456665 [details]
File: backtrace

Comment 2 Christian Stadelmann 2018-07-05 06:08:13 UTC
Created attachment 1456666 [details]
File: core_backtrace

Comment 3 Christian Stadelmann 2018-07-05 06:08:14 UTC
Created attachment 1456667 [details]
File: cpuinfo

Comment 4 Christian Stadelmann 2018-07-05 06:08:16 UTC
Created attachment 1456668 [details]
File: dso_list

Comment 5 Christian Stadelmann 2018-07-05 06:08:19 UTC
Created attachment 1456669 [details]
File: limits

Comment 6 Christian Stadelmann 2018-07-05 06:08:21 UTC
Created attachment 1456670 [details]
File: proc_pid_status

Comment 7 Ben Cotton 2019-05-02 19:22:15 UTC
This message is a reminder that Fedora 28 is nearing its end of life.
On 2019-May-28 Fedora will stop maintaining and issuing updates for
Fedora 28. 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 '28'.

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 28 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 8 Ben Cotton 2019-05-02 20:46:46 UTC
This message is a reminder that Fedora 28 is nearing its end of life.
On 2019-May-28 Fedora will stop maintaining and issuing updates for
Fedora 28. 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 '28'.

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 28 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 9 Ben Cotton 2019-05-28 18:55:33 UTC
Fedora 28 changed to end-of-life (EOL) status on 2019-05-28. Fedora 28 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.