Bug 1527174 - [abrt] control-center: g_malloc0(): gnome-control-center killed by SIGABRT
Summary: [abrt] control-center: g_malloc0(): gnome-control-center killed by SIGABRT
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: control-center
Version: 27
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Control Center Maintainer
QA Contact: Fedora Extras Quality Assurance
URL: https://retrace.fedoraproject.org/faf...
Whiteboard: abrt_hash:49dba7b43dd521223bce12aba15...
: 1533197 1565224 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-12-18 17:44 UTC by strust+erqungohtmvyyn
Modified: 2018-11-30 21:06 UTC (History)
18 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-11-30 21:06:30 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (83.81 KB, text/plain)
2017-12-18 17:44 UTC, strust+erqungohtmvyyn
no flags Details
File: cgroup (321 bytes, text/plain)
2017-12-18 17:44 UTC, strust+erqungohtmvyyn
no flags Details
File: core_backtrace (22.48 KB, text/plain)
2017-12-18 17:44 UTC, strust+erqungohtmvyyn
no flags Details
File: cpuinfo (1.35 KB, text/plain)
2017-12-18 17:44 UTC, strust+erqungohtmvyyn
no flags Details
File: dso_list (27.72 KB, text/plain)
2017-12-18 17:44 UTC, strust+erqungohtmvyyn
no flags Details
File: environ (1.59 KB, text/plain)
2017-12-18 17:44 UTC, strust+erqungohtmvyyn
no flags Details
File: limits (1.29 KB, text/plain)
2017-12-18 17:44 UTC, strust+erqungohtmvyyn
no flags Details
File: maps (126.66 KB, text/plain)
2017-12-18 17:44 UTC, strust+erqungohtmvyyn
no flags Details
File: mountinfo (3.77 KB, text/plain)
2017-12-18 17:44 UTC, strust+erqungohtmvyyn
no flags Details
File: open_fds (2.20 KB, text/plain)
2017-12-18 17:44 UTC, strust+erqungohtmvyyn
no flags Details
File: proc_pid_status (1.27 KB, text/plain)
2017-12-18 17:44 UTC, strust+erqungohtmvyyn
no flags Details

Description strust+erqungohtmvyyn 2017-12-18 17:44:24 UTC
Description of problem:
Trying to print a test page on the printer (usb connection): Brother DCP-L2520DW. Drivers used:
http://download.brother.com/welcome/dlf101757/dcpl2520dwlpr-3.2.0-1.i386.rpm
http://download.brother.com/welcome/dlf101758/dcpl2520dwcupswrapper-3.2.0-1.i386.rpm
I had 'printers' window open, and tried adding/removing the same printer, and changing it's driver between the one above and 'generic text-only printer' which was active by default.
I do not have a consistent way to reproduce the crash, but it did happen multiple times, and persisted after reboots and driver reinstalls.
Feel free to contact me about this strust+erqungohtmvyyn

Version-Release number of selected component:
control-center-3.26.2-2.fc27

Additional info:
reporter:       libreport-2.9.3
backtrace_rating: 4
cmdline:        gnome-control-center printers
crash_function: g_malloc0
executable:     /usr/bin/gnome-control-center
journald_cursor: s=e12f40e70b6042449afdd72735a7b7c2;i=2bb9e;b=eba333d2ba18454ebc25035c54a31fba;m=745e84e1;t=560986c0bdbfa;x=216af04a7c4a3a7d
kernel:         4.14.3-300.fc27.x86_64
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000

Comment 1 strust+erqungohtmvyyn 2017-12-18 17:44:34 UTC
Created attachment 1369604 [details]
File: backtrace

Comment 2 strust+erqungohtmvyyn 2017-12-18 17:44:35 UTC
Created attachment 1369605 [details]
File: cgroup

Comment 3 strust+erqungohtmvyyn 2017-12-18 17:44:37 UTC
Created attachment 1369606 [details]
File: core_backtrace

Comment 4 strust+erqungohtmvyyn 2017-12-18 17:44:39 UTC
Created attachment 1369607 [details]
File: cpuinfo

Comment 5 strust+erqungohtmvyyn 2017-12-18 17:44:40 UTC
Created attachment 1369608 [details]
File: dso_list

Comment 6 strust+erqungohtmvyyn 2017-12-18 17:44:42 UTC
Created attachment 1369609 [details]
File: environ

Comment 7 strust+erqungohtmvyyn 2017-12-18 17:44:44 UTC
Created attachment 1369610 [details]
File: limits

Comment 8 strust+erqungohtmvyyn 2017-12-18 17:44:46 UTC
Created attachment 1369611 [details]
File: maps

Comment 9 strust+erqungohtmvyyn 2017-12-18 17:44:47 UTC
Created attachment 1369612 [details]
File: mountinfo

Comment 10 strust+erqungohtmvyyn 2017-12-18 17:44:49 UTC
Created attachment 1369613 [details]
File: open_fds

Comment 11 strust+erqungohtmvyyn 2017-12-18 17:44:50 UTC
Created attachment 1369614 [details]
File: proc_pid_status

Comment 12 StefanM 2018-01-07 10:13:16 UTC
Similar problem has been detected:

trying to set-up my printer
after I installed the divers provided by Brother via
$> dnf localinstall mfc9140cdncupswrapper-1.1.4-0.i386.rpm mfc9140cdnlpr-1.1.2-1.i386.rpm
my printer appeared automagically into my setup as cups printer
from there I tried to send a test page and the settings applet crushed and I got the abrt message

here the status reported by systemctl:

[root@lacktop Downloads]# systemctl status -l cups.service 
● cups.service - CUPS Scheduler
   Loaded: loaded (/usr/lib/systemd/system/cups.service; disabled; vendor preset: disabled)
   Active: active (running) since Sun 2018-01-07 09:22:39 CET; 1h 18min ago
     Docs: man:cupsd(8)
 Main PID: 1859 (cupsd)
   Status: "Scheduler is running..."
    Tasks: 3 (limit: 4915)
   CGroup: /system.slice/cups.service
           ├─1859 /usr/sbin/cupsd -l
           ├─3438 /usr/lib/cups/notifier/dbus dbus://
           └─5404 /usr/lib/cups/notifier/dbus dbus://

Jan 07 10:40:40 lacktop.acasa.net cupsd[1859]: /opt/brother/Printers/mfc9140cdn/lpd/filtermfc9140cdn: line 63:  6009 Done                    eval cat $INPUT_TEMP
Jan 07 10:40:40 lacktop.acasa.net cupsd[1859]: 6010                       | $PSCONV $PSCONV_OP
Jan 07 10:40:40 lacktop.acasa.net cupsd[1859]: 6011 Segmentation fault      | $BRCONV $BRCONV_OP
Jan 07 10:40:40 lacktop.acasa.net cupsd[1859]: PID 5975 (/usr/lib/cups/filter/brother_lpdwrapper_mfc9140cdn) exited with no errors.
Jan 07 10:40:40 lacktop.acasa.net cupsd[1859]: PID 5976 (/usr/lib/cups/backend/dnssd) exited with no errors.
Jan 07 10:40:40 lacktop.acasa.net cupsd[1859]: time-at-completed=1515318040
Jan 07 10:40:40 lacktop.acasa.net cupsd[1859]: Job completed.
Jan 07 10:40:41 lacktop.acasa.net cupsd[1859]: Unloading...
Jan 07 10:40:44 lacktop.acasa.net cupsd[1859]: Loading attributes...
Jan 07 10:40:44 lacktop.acasa.net cupsd[1859]: cupsdLoadJob: job->file_time=1515404440, time-at-completed=1515318040, JobFiles=86400


journalctl reports a selinux issue:
Jan 07 10:40:40 lacktop.acasa.net audit[5997]: AVC avc:  denied  { execmem } for  pid=5997 comm="brcupsconfpt1" scontext=system_u:system_r:cupsd_t:s0-s0:c0.c1023 tcontext=system_u:system_r:cupsd_t:s0-s0:c0.c1023
Jan 07 10:40:40 lacktop.acasa.net audit[5997]: ANOM_ABEND auid=4294967295 uid=4 gid=7 ses=4294967295 subj=system_u:system_r:cupsd_t:s0-s0:c0.c1023 pid=5997 comm="brcupsconfpt1" exe="/opt/brother/Printers/mfc9140
Jan 07 10:40:40 lacktop.acasa.net cupsd[1859]: /usr/lib/cups/filter/brother_lpdwrapper_mfc9140cdn: line 133:  5997 Segmentation fault      /opt/brother/Printers/mfc9140cdn/cupswrapper/brcupsconfpt1 MFC9140CDN $P
Jan 07 10:40:40 lacktop.acasa.net audit[6011]: AVC avc:  denied  { execmem } for  pid=6011 comm="brmfc9140cdnfil" scontext=system_u:system_r:cupsd_t:s0-s0:c0.c1023 tcontext=system_u:system_r:cupsd_t:s0-s0:c0.c10
Jan 07 10:40:40 lacktop.acasa.net audit[6011]: ANOM_ABEND auid=4294967295 uid=4 gid=7 ses=4294967295 subj=system_u:system_r:cupsd_t:s0-s0:c0.c1023 pid=6011 comm="brmfc9140cdnfil" exe="/opt/brother/Printers/mfc91
Jan 07 10:40:40 lacktop.acasa.net cupsd[1859]: /opt/brother/Printers/mfc9140cdn/lpd/filtermfc9140cdn: line 63:  6009 Done                    eval cat $INPUT_TEMP
Jan 07 10:40:40 lacktop.acasa.net cupsd[1859]: 6010                       | $PSCONV $PSCONV_OP
Jan 07 10:40:40 lacktop.acasa.net cupsd[1859]: 6011 Segmentation fault      | $BRCONV $BRCONV_OP
Jan 07 10:40:40 lacktop.acasa.net cupsd[1859]: PID 5975 (/usr/lib/cups/filter/brother_lpdwrapper_mfc9140cdn) exited with no errors.
Jan 07 10:40:40 lacktop.acasa.net cupsd[1859]: PID 5976 (/usr/lib/cups/backend/dnssd) exited with no errors.
Jan 07 10:40:40 lacktop.acasa.net cupsd[1859]: time-at-completed=1515318040
Jan 07 10:40:40 lacktop.acasa.net cupsd[1859]: Job completed.
Jan 07 10:40:41 lacktop.acasa.net cupsd[1859]: Unloading...
Jan 07 10:40:43 lacktop.acasa.net dbus-daemon[834]: [system] Activating service name='org.fedoraproject.Setroubleshootd' requested by ':1.160' (uid=0 pid=811 comm="/usr/sbin/sedispatch " label="system_u:system_r
Jan 07 10:40:43 lacktop.acasa.net dbus-daemon[834]: [system] Successfully activated service 'org.fedoraproject.Setroubleshootd'
Jan 07 10:40:44 lacktop.acasa.net setroubleshoot[6054]: SELinux is preventing brcupsconfpt1 from using the execmem access on a process. For complete SELinux messages run: sealert -l 2c364abd-5fcb-4462-b4b5-8ceee
Jan 07 10:40:44 lacktop.acasa.net python3[6054]: SELinux is preventing brcupsconfpt1 from using the execmem access on a process.
                                                 
                                                 *****  Plugin catchall_boolean (89.3 confidence) suggests   ******************
                                                 
                                                 If you want to allow cups to execmem
                                                 Then you must tell SELinux about this by enabling the 'cups_execmem' boolean.
                                                 
                                                 Do
                                                 setsebool -P cups_execmem 1
                                                 
                                                 *****  Plugin catchall (11.6 confidence) suggests   **************************
                                                 
                                                 If you believe that brcupsconfpt1 should be allowed execmem access on processes labeled cupsd_t by default.
                                                 Then you should report this as a bug.
                                                 You can generate a local policy module to allow this access.
                                                 Do
                                                 allow this access for now by executing:
                                                 # ausearch -c 'brcupsconfpt1' --raw | audit2allow -M my-brcupsconfpt1
                                                 # semodule -X 300 -i my-brcupsconfpt1.pp
                                                 
Jan 07 10:40:44 lacktop.acasa.net setroubleshoot[6054]: SELinux is preventing brcupsconfpt1 from using the execmem access on a process. For complete SELinux messages run: sealert -l 2c364abd-5fcb-4462-b4b5-8ceee
Jan 07 10:40:44 lacktop.acasa.net python3[6054]: SELinux is preventing brcupsconfpt1 from using the execmem access on a process.
                                                 
                                                 *****  Plugin catchall_boolean (89.3 confidence) suggests   ******************
                                                 
                                                 If you want to allow cups to execmem
                                                 Then you must tell SELinux about this by enabling the 'cups_execmem' boolean.
                                                 
                                                 Do
                                                 setsebool -P cups_execmem 1
                                                 
                                                 *****  Plugin catchall (11.6 confidence) suggests   **************************
                                                 
                                                 If you believe that brcupsconfpt1 should be allowed execmem access on processes labeled cupsd_t by default.
                                                 Then you should report this as a bug.
                                                 You can generate a local policy module to allow this access.
                                                 Do
                                                 allow this access for now by executing:
                                                 # ausearch -c 'brcupsconfpt1' --raw | audit2allow -M my-brcupsconfpt1
                                                 # semodule -X 300 -i my-brcupsconfpt1.pp
                                                 
Jan 07 10:40:44 lacktop.acasa.net cupsd[1859]: Loading attributes...
Jan 07 10:40:44 lacktop.acasa.net cupsd[1859]: cupsdLoadJob: job->file_time=1515404440, time-at-completed=1515318040, JobFiles=86400
Jan 07 10:41:45 lacktop.acasa.net cupsd[1859]: Unloading...
Jan 07 10:42:34 lacktop.acasa.net cupsd[1859]: PID 5404 (/usr/lib/cups/notifier/dbus) exited with no errors.





reporter:       libreport-2.9.3
backtrace_rating: 4
cmdline:        gnome-control-center --overview
crash_function: g_malloc0
executable:     /usr/bin/gnome-control-center
journald_cursor: s=185f7807c60748448e5498adfb74a352;i=3bc5;b=e2ba9476b6824c2d8edc5e16eb001010;m=10be03e26;t=5622c6d28b26c;x=fb30664b4c7ded34
kernel:         4.14.11-300.fc27.x86_64
package:        control-center-3.26.2-2.fc27
reason:         gnome-control-center killed by SIGSEGV
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1001

Comment 13 StefanM 2018-01-07 10:35:13 UTC
After I set the selinux flag:

setsebool -P cups_execmem 1

 and reboot (well, the reboot was not necessarily related but I couldn't check before) it worked

Comment 14 Kenzo 2018-01-10 17:24:17 UTC
*** Bug 1533197 has been marked as a duplicate of this bug. ***

Comment 15 Dagan McGregor 2018-03-27 02:57:01 UTC
Similar problem has been detected:

I was trying to update my printer settings and the settings UI crashed. 

The new UI seems less user friendly than the previous version, it makes it harder to find information like IP addresses.

Out of a list of four printers listed as "MP-C504".

I added the correct network printer, Ricoh MP-C4504, successfully. 

I deleted a previous printer displaying the same name. I had to look at CUPS admin tool (....) to see the MAC address was different.

The information hidden from the user makes it impossible to tell printers apart otherwise, and searching by IP address doesn't always seem to work.

I was also checking for job status of a test page printing. This printed successfully, after the UI had crashed.

reporter:       libreport-2.9.3
backtrace_rating: 4
cmdline:        gnome-control-center --overview
crash_function: g_malloc0
executable:     /usr/bin/gnome-control-center
journald_cursor: s=a98d9ac6f1e1451cad9bf3595af49893;i=6cef0;b=5ed41a1c8ca942a6be3b84440fb5986e;m=46ef0c6e0;t=5685ba9d235f2;x=50f0043a7d8faaf6
kernel:         4.15.10-300.fc27.x86_64
package:        1:control-center-3.26.2-2.fc27
reason:         gnome-control-center killed by SIGABRT
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            3767

Comment 16 aekryz 2018-04-09 16:26:16 UTC
*** Bug 1565224 has been marked as a duplicate of this bug. ***

Comment 17 Vincenzo Luongo 2018-04-18 08:36:02 UTC
Similar problem has been detected:

run my fedora 26
open slack and thunderbird
crash gnome

reporter:       libreport-2.9.3
backtrace_rating: 4
cmdline:        gnome-control-center --overview
crash_function: g_malloc0
executable:     /usr/bin/gnome-control-center
journald_cursor: s=7a67b7f3a03f4ac785074c1dae2621ff;i=d6d1;b=835cc1b2c51d4cd09034c8e9f10dd7c2;m=19834a7c4;t=56a083db5f998;x=98dd79f14c17471e
kernel:         4.14.6-300.fc27.x86_64
package:        1:control-center-3.26.2-2.fc27
reason:         gnome-control-center killed by SIGABRT
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000

Comment 18 Ben Cotton 2018-11-27 16:07:16 UTC
This message is a reminder that Fedora 27 is nearing its end of life.
On 2018-Nov-30  Fedora will stop maintaining and issuing updates for
Fedora 27. 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 '27'.

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 27 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 19 Ben Cotton 2018-11-30 21:06:30 UTC
Fedora 27 changed to end-of-life (EOL) status on 2018-11-30. Fedora 27 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.