Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 1689763 - [abrt] gnome-control-center: mem_error(): gnome-control-center killed by SIGABRT
Summary: [abrt] gnome-control-center: mem_error(): gnome-control-center killed by SIGABRT
Keywords:
Status: NEW
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-control-center
Version: 30
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Pete Walter
QA Contact: Fedora Extras Quality Assurance
URL: https://retrace.fedoraproject.org/faf...
Whiteboard: abrt_hash:7e164c66b9b79d10230c998b118...
Depends On:
Blocks: 1694979
TreeView+ depends on / blocked
 
Reported: 2019-03-18 03:20 UTC by Samuel
Modified: 2019-04-04 06:34 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:


Attachments (Terms of Use)
File: backtrace (deleted)
2019-03-18 03:20 UTC, Samuel
no flags Details
File: cgroup (deleted)
2019-03-18 03:20 UTC, Samuel
no flags Details
File: core_backtrace (deleted)
2019-03-18 03:20 UTC, Samuel
no flags Details
File: cpuinfo (deleted)
2019-03-18 03:20 UTC, Samuel
no flags Details
File: dso_list (deleted)
2019-03-18 03:20 UTC, Samuel
no flags Details
File: environ (deleted)
2019-03-18 03:20 UTC, Samuel
no flags Details
File: limits (deleted)
2019-03-18 03:20 UTC, Samuel
no flags Details
File: maps (deleted)
2019-03-18 03:20 UTC, Samuel
no flags Details
File: mountinfo (deleted)
2019-03-18 03:20 UTC, Samuel
no flags Details
File: open_fds (deleted)
2019-03-18 03:20 UTC, Samuel
no flags Details
File: proc_pid_status (deleted)
2019-03-18 03:20 UTC, Samuel
no flags Details

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.


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