Description of problem: I was printing a page from gedit while having gnome control center opened on the printers page. Version-Release number of selected component: control-center-3.26.0-1.fc27 Additional info: reporter: libreport-2.9.2 backtrace_rating: 4 cmdline: gnome-control-center printers crash_function: mem_error executable: /usr/bin/gnome-control-center journald_cursor: s=5f16c1c5e6ee42bb89ab5d511982a9bf;i=537e3;b=62b9d74a6efd47aeb9aaa800a00785cd;m=a395dbb;t=55aca1b581dd4;x=876f769fd5f3f8fd kernel: 4.13.4-300.fc27.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 1000
Created attachment 1334733 [details] File: backtrace
Created attachment 1334734 [details] File: cgroup
Created attachment 1334735 [details] File: core_backtrace
Created attachment 1334736 [details] File: cpuinfo
Created attachment 1334737 [details] File: dso_list
Created attachment 1334738 [details] File: environ
Created attachment 1334739 [details] File: limits
Created attachment 1334740 [details] File: maps
Created attachment 1334741 [details] File: open_fds
Created attachment 1334742 [details] File: proc_pid_status
Created attachment 1334743 [details] File: var_log_messages
Similar problem has been detected: Added a printer and then sent a test page. Crash happened while waiting for test page job to finish. reporter: libreport-2.9.2 backtrace_rating: 4 cmdline: gnome-control-center --overview crash_function: mem_error executable: /usr/bin/gnome-control-center journald_cursor: s=2f65b00e0f494bb6b2c596b1a9877d2e;i=4ffd;b=e389ed9ebefb4628b5c7648c82cc58a0;m=2921de999;t=55c8971127a9f;x=d1895906aa30a2b8 kernel: 4.13.9-300.fc27.x86_64 package: control-center-3.26.1-1.fc27 reason: gnome-control-center killed by SIGABRT rootdir: / runlevel: N 5 type: CCpp uid: 1000
Similar problem has been detected: I printed a testpage to a printer located in a samba share. The worked fine. Then I wanted to unlock and then it crashed. reporter: libreport-2.9.3 backtrace_rating: 4 cmdline: gnome-control-center --overview crash_function: mem_error executable: /usr/bin/gnome-control-center journald_cursor: s=35337db141a14718b405472531eb4cb6;i=5d44;b=9fc1ab69a99d44cba0f4682bccf2b5ac;m=3a255a57;t=55f1f606d215a;x=ab4edb5102389787 kernel: 4.13.15-300.fc27.x86_64 package: control-center-3.26.2-2.fc27 reason: gnome-control-center killed by SIGABRT rootdir: / runlevel: N 5 type: CCpp uid: 1000
*** Bug 1527377 has been marked as a duplicate of this bug. ***
Similar problem has been detected: I was checking the bug 1527174 <https://bugzilla.redhat.com/show_bug.cgi?id=1527174> after setting the execmem selinux permission for cups and reboot I got to settings applet-> devices -> printers and click on unlock button reporter: libreport-2.9.3 backtrace_rating: 4 cmdline: gnome-control-center --overview crash_function: mem_error executable: /usr/bin/gnome-control-center journald_cursor: s=185f7807c60748448e5498adfb74a352;i=4cb5;b=3294c79e272841139583d9a47fdaead2;m=1d0e7a44;t=5622d415e3400;x=b0bcbae21b944be7 kernel: 4.14.11-300.fc27.x86_64 package: control-center-3.26.2-2.fc27 reason: gnome-control-center killed by SIGABRT rootdir: / runlevel: N 5 type: CCpp uid: 1001
Similar problem has been detected: Attempted to print a test page from Control Center. After starting the job, I clicked the "1 Job(s)" button to monitor its progress. Eventually, Control Center crashed, though the job did print successfully. reporter: libreport-2.9.3 backtrace_rating: 4 cmdline: gnome-control-center printers crash_function: mem_error executable: /usr/bin/gnome-control-center journald_cursor: s=4006433a88fc4e5ea1a3600f4c3a1ff9;i=16174;b=ead4a0af710c4d2bb059fdf4878963e5;m=42911a2d4;t=5625724f6325d;x=806d8e603c34a2b1 kernel: 4.14.11-300.fc27.x86_64 package: control-center-3.26.2-2.fc27 reason: gnome-control-center killed by SIGABRT rootdir: / runlevel: N 5 type: CCpp uid: 1000
Similar problem has been detected: Out of nowhere while settings panel was opened. Beforehand I tried several times to print a test page on my Canon MF3010 printer, but it did nothing. reporter: libreport-2.9.3 backtrace_rating: 4 cmdline: gnome-control-center --overview crash_function: mem_error executable: /usr/bin/gnome-control-center journald_cursor: s=e9e93ee8773b43518477609242f0f600;i=2165;b=7f48c1a64d544b36b68e630c7d537e20;m=710782bb;t=562a9c2ad9c68;x=4eaa04be6ad0d74d kernel: 4.14.13-300.fc27.x86_64 package: control-center-3.26.2-2.fc27 reason: gnome-control-center killed by SIGABRT rootdir: / runlevel: N 5 type: CCpp uid: 1000
Similar problem has been detected: input HP printer reporter: libreport-2.9.3 backtrace_rating: 4 cmdline: gnome-control-center --overview crash_function: mem_error executable: /usr/bin/gnome-control-center journald_cursor: s=8f6979827b8341e98cee88d19d4301ef;i=f17;b=1d2471ea36024baeb7be96dba2284917;m=58cd4931;t=5667f3ba12170;x=e2d3b5de7e272d70 kernel: 4.15.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
*** Bug 1552215 has been marked as a duplicate of this bug. ***
*** Bug 1562475 has been marked as a duplicate of this bug. ***
*** Bug 1565254 has been marked as a duplicate of this bug. ***
*** Bug 1566320 has been marked as a duplicate of this bug. ***
Similar problem has been detected: While configuring my printers and trying to add a new network printer with static IP address I selected the auto-discovered entry under the 'Add'-menu. This returned an error which states that no driver could be found and suggests to install them from the store (all drivers presented are already installed). Several seconds after the error occured the control center crashed entierly. reporter: libreport-2.9.3 backtrace_rating: 4 cmdline: gnome-control-center printers crash_function: mem_error executable: /usr/bin/gnome-control-center journald_cursor: s=46a5a5017f214aacb8dae7d1307580bb;i=142dc;b=00872e1beea14359abaa343cfe7a8b46;m=1bd13b731b;t=569f6cc6006e2;x=2c96ca68ed582b03 kernel: 4.15.13-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
Similar problem has been detected: I was trying to get a printer I added yesterday, that worked yesterday, to print today. Instead of printing, it just registered the job as "stopped" despite the printer listing as "accepting jobs". So I deleted the printer and tried to re-add it, and it crashed. reporter: libreport-2.9.3 backtrace_rating: 4 cmdline: gnome-control-center printers crash_function: mem_error executable: /usr/bin/gnome-control-center journald_cursor: s=61a9c6a7c51c4d358f6bd567740bbfcd;i=2576a;b=ef57b1c689c647c3bf17ee16efbbc1e9;m=121f3a9b2e8;t=56c03b5329697;x=3086ef7673eaa435 kernel: 4.16.3-200.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
*** Bug 1613994 has been marked as a duplicate of this bug. ***
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.
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.