Bug 1689763

Summary: [abrt] gnome-control-center: mem_error(): gnome-control-center killed by SIGABRT
Product: [Fedora] Fedora Reporter: Samuel <samuelnhuis>
Component: gnome-control-centerAssignee: Pete Walter <walter.pete>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 30CC: 181gaming, a.dimartino1, alessandromachado.vip, anper1979, colotunbabay2010, craig, damon.blais, dsloudon, ehmario, fedora, gnome-sig, hp, jan.public, jan.vesely, JimShip, korncampus, luca.giuzzi, lucio.noldin, maggesi, marciovianna, martin.landhage, martin.lepetit, maxim.galamay, michael.c.thiel, michal-ald-redhat-bugzilla, redhat, rhiccarddo, soloeltigre, vangjelstavro, walter.pete, willschmidt182, yann
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/e0d5394b640be64ad6fb0a72861562974655500e
Whiteboard: abrt_hash:7e164c66b9b79d10230c998b1184411d6631f30e;VARIANT_ID=workstation;
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-05-26 18:03:55 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1694979    
Attachments:
Description Flags
File: backtrace
none
File: cgroup
none
File: core_backtrace
none
File: cpuinfo
none
File: dso_list
none
File: environ
none
File: limits
none
File: maps
none
File: mountinfo
none
File: open_fds
none
File: proc_pid_status none

Description Samuel 2019-03-18 03:20:30 UTC
Description of problem:
I was removing printers from the 'Printers' subpage under the 'Devices' settings page. I had gained root access via the 'Unlock' button in the top right corner, and had removed undeeded printer entries from previous misconfiguration attempts. I was browsing the 'Printing Options' entry of the printer I did not want to remove, and then settings crashed.

Version-Release number of selected component:
gnome-control-center-3.32.0.1-1.fc30

Additional info:
reporter:       libreport-2.10.0
backtrace_rating: 4
cmdline:        gnome-control-center
crash_function: mem_error
executable:     /usr/bin/gnome-control-center
journald_cursor: s=0fc810b32d064b8b8d620405fce7c931;i=193e;b=11191effe7b54e2bb38c3ba5c0b82f24;m=27fec0b9;t=584559acac562;x=30e7f19a6ce72fcd
kernel:         5.0.0-300.fc30.x86_64
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000

Potential duplicate: bug 1573653

Comment 1 Samuel 2019-03-18 03:20:34 UTC
Created attachment 1545096 [details]
File: backtrace

Comment 2 Samuel 2019-03-18 03:20:35 UTC
Created attachment 1545097 [details]
File: cgroup

Comment 3 Samuel 2019-03-18 03:20:37 UTC
Created attachment 1545098 [details]
File: core_backtrace

Comment 4 Samuel 2019-03-18 03:20:38 UTC
Created attachment 1545099 [details]
File: cpuinfo

Comment 5 Samuel 2019-03-18 03:20:40 UTC
Created attachment 1545100 [details]
File: dso_list

Comment 6 Samuel 2019-03-18 03:20:41 UTC
Created attachment 1545101 [details]
File: environ

Comment 7 Samuel 2019-03-18 03:20:42 UTC
Created attachment 1545102 [details]
File: limits

Comment 8 Samuel 2019-03-18 03:20:47 UTC
Created attachment 1545103 [details]
File: maps

Comment 9 Samuel 2019-03-18 03:20:48 UTC
Created attachment 1545104 [details]
File: mountinfo

Comment 10 Samuel 2019-03-18 03:20:49 UTC
Created attachment 1545105 [details]
File: open_fds

Comment 11 Samuel 2019-03-18 03:20:51 UTC
Created attachment 1545106 [details]
File: proc_pid_status

Comment 12 Jan Vlug 2019-04-04 06:33:39 UTC
See bug 1694979#c4 and bug 1694979#c5 on how to reproduce this crash.

Comment 13 Luca Giuzzi 2019-05-08 15:27:25 UTC
Similar problem has been detected:

I restarted cups while the printers option was beeing shown

reporter:       libreport-2.10.0
backtrace_rating: 4
cmdline:        /usr/bin/gnome-control-center printers show-jobs Follow_Me
crash_function: mem_error
executable:     /usr/bin/gnome-control-center
journald_cursor: s=5440652bbfa04bd89395f2f3d29bb946;i=36d7ff;b=d2ecee49455349258ea791d7e7bedf39;m=11511d07f6;t=5886142d871d1;x=c6f23f22742d89e3
kernel:         5.0.13-300.fc30.x86_64
package:        gnome-control-center-3.32.1-2.fc30
reason:         gnome-control-center killed by SIGABRT
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000

Comment 14 Alessandro Machado 2019-05-09 16:11:29 UTC
*** Bug 1708334 has been marked as a duplicate of this bug. ***

Comment 15 Damon Blais 2019-05-13 21:29:37 UTC
*** Bug 1709584 has been marked as a duplicate of this bug. ***

Comment 16 willschmidt182 2019-06-05 19:49:37 UTC
*** Bug 1717613 has been marked as a duplicate of this bug. ***

Comment 17 Martin Landhage 2019-06-07 07:12:32 UTC
*** Bug 1718166 has been marked as a duplicate of this bug. ***

Comment 18 Yann Droneaud 2019-06-18 15:46:59 UTC
Similar problem has been detected:

Was fiddling with the printers in the control panel.

reporter:       libreport-2.10.0
backtrace_rating: 4
cmdline:        gnome-control-center
crash_function: mem_error
executable:     /usr/bin/gnome-control-center
journald_cursor: s=0ad708db167d4a789ed83375c950b7cb;i=3e374;b=d738dfee58814efbb5ef8c72f534574a;m=94bc5c6cd;t=58b949c9adbbf;x=bf408766f12b39c1
kernel:         5.1.9-300.fc30.x86_64
package:        gnome-control-center-3.32.2-1.fc30
reason:         gnome-control-center killed by SIGABRT
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000

Comment 19 jan.vesely 2019-07-01 21:06:04 UTC
*** Bug 1725966 has been marked as a duplicate of this bug. ***

Comment 20 Maxim Galamay 2019-07-12 11:29:17 UTC
*** Bug 1729479 has been marked as a duplicate of this bug. ***

Comment 21 Don Loudon 2019-07-25 16:28:59 UTC
*** Bug 1733313 has been marked as a duplicate of this bug. ***

Comment 22 Wendell Karingal 2019-08-13 12:54:22 UTC
*** Bug 1740671 has been marked as a duplicate of this bug. ***

Comment 23 R. Antonn Tiellet 2019-08-17 12:27:48 UTC
*** Bug 1742896 has been marked as a duplicate of this bug. ***

Comment 24 Francois 2019-08-19 09:42:09 UTC
*** Bug 1743184 has been marked as a duplicate of this bug. ***

Comment 25 Evan H. 2019-08-21 19:25:19 UTC
*** Bug 1744303 has been marked as a duplicate of this bug. ***

Comment 26 Jim Shipman 2019-08-21 22:59:23 UTC
*** Bug 1744356 has been marked as a duplicate of this bug. ***

Comment 27 soloeltigre 2019-09-02 04:50:37 UTC
*** Bug 1747856 has been marked as a duplicate of this bug. ***

Comment 28 Francois 2019-09-05 09:30:58 UTC
*** Bug 1749274 has been marked as a duplicate of this bug. ***

Comment 29 lucio.noldin 2019-09-08 10:02:30 UTC
*** Bug 1750095 has been marked as a duplicate of this bug. ***

Comment 30 michael.c.thiel 2019-09-10 16:59:52 UTC
*** Bug 1750897 has been marked as a duplicate of this bug. ***

Comment 31 martin.lepetit 2019-09-10 20:27:00 UTC
*** Bug 1750954 has been marked as a duplicate of this bug. ***

Comment 32 Tony 2019-09-21 08:02:29 UTC
*** Bug 1754150 has been marked as a duplicate of this bug. ***

Comment 33 Jonatan Maggesi 2019-09-23 08:32:36 UTC
*** Bug 1754425 has been marked as a duplicate of this bug. ***

Comment 34 michal-ald-redhat-bugzilla 2019-10-05 11:11:17 UTC
*** Bug 1758752 has been marked as a duplicate of this bug. ***

Comment 35 Francois 2019-10-05 15:57:52 UTC
*** Bug 1758787 has been marked as a duplicate of this bug. ***

Comment 36 Vango Stavro 2019-10-10 09:52:16 UTC
*** Bug 1760268 has been marked as a duplicate of this bug. ***

Comment 37 Marcio 2019-10-25 14:19:04 UTC
*** Bug 1765596 has been marked as a duplicate of this bug. ***

Comment 38 Nicholas 2019-12-10 20:01:14 UTC
*** Bug 1781881 has been marked as a duplicate of this bug. ***

Comment 39 Ben Cotton 2020-04-30 20:36:57 UTC
This message is a reminder that Fedora 30 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 30 on 2020-05-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 '30'.

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 30 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 40 Ben Cotton 2020-05-26 18:03:55 UTC
Fedora 30 changed to end-of-life (EOL) status on 2020-05-26. Fedora 30 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.