Bug 1646636

Created attachment 1502129 [details]
File: backtrace

Created attachment 1502130 [details]
File: cgroup

Created attachment 1502131 [details]
File: core_backtrace

Created attachment 1502132 [details]
File: cpuinfo

Created attachment 1502133 [details]
File: dso_list

Created attachment 1502134 [details]
File: environ

Created attachment 1502135 [details]
File: limits

Created attachment 1502136 [details]
File: maps

Created attachment 1502137 [details]
File: mountinfo

Created attachment 1502138 [details]
File: open_fds

Created attachment 1502139 [details]
File: proc_pid_status

*** Bug 1650924 has been marked as a duplicate of this bug. ***

Similar problem has been detected:

This problem happened suddenly, no warning.

reporter:       libreport-2.9.6
backtrace_rating: 4
cmdline:        gnome-control-center
crash_function: mem_error
executable:     /usr/bin/gnome-control-center
journald_cursor: s=1c241956efed4d379b7101046481f5b1;i=efb6;b=86c04dec3c684f31be6d8f1d11f1e810;m=156267f110;t=57bd626956233;x=d276155abef6f3f6
kernel:         4.19.4-300.fc29.x86_64
package:        gnome-control-center-3.30.2-1.fc29
reason:         gnome-control-center killed by SIGABRT
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000

Similar problem has been detected:

Not sure what I was doing here, something with printers.

reporter:       libreport-2.9.6
backtrace_rating: 4
cmdline:        gnome-control-center printers
crash_function: mem_error
executable:     /usr/bin/gnome-control-center
journald_cursor: s=e948043895694ed2bffa867c150a0622;i=5212a2;b=5502490d900e427189c635e0183adee8;m=1b322c4b6;t=57c6db6861a48;x=264d937118177d9b
kernel:         4.19.6-300.fc29.x86_64
package:        gnome-control-center-3.30.2-1.fc29
reason:         gnome-control-center killed by SIGABRT
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            500

*** Bug 1662161 has been marked as a duplicate of this bug. ***

*** Bug 1662585 has been marked as a duplicate of this bug. ***

*** Bug 1669755 has been marked as a duplicate of this bug. ***

*** Bug 1671970 has been marked as a duplicate of this bug. ***

*** Bug 1676320 has been marked as a duplicate of this bug. ***

*** Bug 1677072 has been marked as a duplicate of this bug. ***

Similar problem has been detected:

I was trying to print a test page after setting up the printer app and selecting HP Photosmart c4700 series from the database.

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=29fa8da22c154dca86402e1264505180;i=8383b;b=fd4293869e684b23bef90ac9452337b6;m=d990dc16;t=582d08a40584b;x=8a82e313b9b2fd4d
kernel:         4.20.11-200.fc29.x86_64
package:        gnome-control-center-3.30.3-1.fc29
reason:         gnome-control-center killed by SIGABRT
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1001

*** Bug 1684132 has been marked as a duplicate of this bug. ***

Just installed a new printer HP M281fdw. Trying to configure it and printing a test page. No test page has been succesfully printed until now.

Similar problem has been detected:

Configuring new HP printer and trying to print a test page.

reporter:       libreport-2.10.0
backtrace_rating: 3
cmdline:        gnome-control-center
crash_function: mem_error
executable:     /usr/bin/gnome-control-center
journald_cursor: s=9ade0f814ca940aa8c47de318bc6d34a;i=e603c;b=0cb345b4756f4905ad1b4cd73d0fbfe5;m=143ceb8982;t=582f553e9ceb0;x=63176b283112626
kernel:         4.20.11-200.fc29.x86_64
package:        gnome-control-center-3.30.3-1.fc29
reason:         gnome-control-center killed by SIGABRT
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000

*** Bug 1684896 has been marked as a duplicate of this bug. ***

Similar problem has been detected:

I was working with printers in GNOME Settings.
I unlocked the Printers page.
Then I deleted all my printers. The two network printers were discovered and added automatically again via DNS-SD.
For both these printers I tried to print a test page. But no page was printed.
Then I searched for a driver for one of these printers, but this resulted in "No suitable driver found".
I think GNOME Settings crashed at the moment that I clicked on the other printer.


reporter:       libreport-2.10.0
backtrace_rating: 3
cmdline:        gnome-control-center
crash_function: mem_error
executable:     /usr/bin/gnome-control-center
journald_cursor: s=9ade0f814ca940aa8c47de318bc6d34a;i=15ab2f;b=a99d97f8a2fe47939ad11285ec198469;m=7f52b0dd2;t=5858cf202f8d2;x=fa47a50598790663
kernel:         5.0.4-200.fc29.x86_64
package:        gnome-control-center-3.30.3-1.fc29
reason:         gnome-control-center killed by SIGABRT
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000

This bug might be a duplicate of bug 1573653.

*** Bug 1696047 has been marked as a duplicate of this bug. ***

See bug 1694979#c4 and bug 1694979#c5 on how to reproduce this crash.

*** Bug 1702612 has been marked as a duplicate of this bug. ***

*** Bug 1703172 has been marked as a duplicate of this bug. ***

*** Bug 1703174 has been marked as a duplicate of this bug. ***

*** Bug 1703549 has been marked as a duplicate of this bug. ***

*** Bug 1706473 has been marked as a duplicate of this bug. ***

Similar problem has been detected:

I tried to print a test page on a Canon MP 250 printer.

reporter:       libreport-2.10.1
backtrace_rating: 4
cmdline:        gnome-control-center
crash_function: mem_error
executable:     /usr/bin/gnome-control-center
journald_cursor: s=745be607f1e342d5bd8fca99ccf007ff;i=1081e;b=7cd2786a898245b7aadf44a317c52675;m=a2f396a;t=59146efae7ca2;x=c7e22532d20d731a
kernel:         5.2.7-100.fc29.x86_64
package:        gnome-control-center-3.30.3-1.fc29
reason:         gnome-control-center killed by SIGABRT
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000

*** Bug 1749340 has been marked as a duplicate of this bug. ***

This message is a reminder that Fedora 29 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 29 on 2019-11-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 '29'.

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 29 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 29 changed to end-of-life (EOL) status on 2019-11-26. Fedora 29 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.