Bug 1603234

Created attachment 1460041 [details]
File: backtrace

Created attachment 1460042 [details]
File: cgroup

Created attachment 1460043 [details]
File: core_backtrace

Created attachment 1460044 [details]
File: cpuinfo

Created attachment 1460045 [details]
File: dso_list

Created attachment 1460046 [details]
File: environ

Created attachment 1460047 [details]
File: limits

Created attachment 1460048 [details]
File: maps

Created attachment 1460049 [details]
File: mountinfo

Created attachment 1460050 [details]
File: open_fds

Created attachment 1460051 [details]
File: proc_pid_status

Created attachment 1460052 [details]
File: var_log_messages

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

Similar problem has been detected:

Occurred during login. First I noticed was when ABRT reported that the shell had crashed.

reporter:       libreport-2.9.5
backtrace_rating: 3
cmdline:        /usr/bin/gnome-software --gapplication-service
crash_function: __libc_sigaction
executable:     /usr/bin/gnome-software
journald_cursor: s=0ec91349e7024a71b1f0c18e6b1fc906;i=f472cb;b=cdcdc0c1abb24c48b1c3a072791ac75d;m=52c1052;t=571951a520c09;x=16e7486ac27274c9
kernel:         4.17.6-200.fc28.x86_64
package:        gnome-software-3.28.2-1.fc28
reason:         gnome-software killed by SIGABRT
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            501

Similar problem has been detected:

The message arrived when I signed onto Gnome after booting the system.

reporter:       libreport-2.9.5
backtrace_rating: 3
cmdline:        /usr/bin/gnome-software --gapplication-service
crash_function: __libc_sigaction
executable:     /usr/bin/gnome-software
journald_cursor: s=13e7e9306a034ca4bcee91fe8dbd45df;i=558b4;b=718a9cd474a942ec9939bc98a4da31eb;m=208578f;t=571dcd848eea1;x=4a953e99691ae3c3
kernel:         4.17.7-200.fc28.x86_64
package:        gnome-software-3.28.2-1.fc28
reason:         gnome-software killed by SIGABRT
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000

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

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

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

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

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

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

Similar problem has been detected:

1. Run 'ssh -lroot x.x.x.x' thru the default gnome terminal to a raspberrypi running arch. 
2. Execute the command 'pacman -Syu' (Full system uppgrade).

90% of the times this results in complete system lockup and powercord needs to be pulled from computer.

reporter:       libreport-2.9.5
backtrace_rating: 3
cmdline:        /usr/bin/gnome-software --gapplication-service
crash_function: __libc_sigaction
executable:     /usr/bin/gnome-software
journald_cursor: s=556500b91f39496ea07a7b3bc893ce7d;i=a15;b=1eb1019d502c4182886e4fc30f089821;m=1d03aa7;t=573f7af937940;x=724c58c85006ed68
kernel:         4.17.14-202.fc28.x86_64
package:        gnome-software-3.28.2-1.fc28
reason:         gnome-software killed by SIGABRT
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000

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

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 28 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.

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

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 28 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.

(In reply to Mikael Larsson from comment #22)
> Similar problem has been detected:
> 
> 1. Run 'ssh -lroot x.x.x.x' thru the default gnome terminal to a raspberrypi
> running arch. 
> 2. Execute the command 'pacman -Syu' (Full system uppgrade).
> 
> 90% of the times this results in complete system lockup and powercord needs
> to be pulled from computer.
> 
> reporter:       libreport-2.9.5
> backtrace_rating: 3
> cmdline:        /usr/bin/gnome-software --gapplication-service
> crash_function: __libc_sigaction
> executable:     /usr/bin/gnome-software
> journald_cursor:
> s=556500b91f39496ea07a7b3bc893ce7d;i=a15;b=1eb1019d502c4182886e4fc30f089821;
> m=1d03aa7;t=573f7af937940;x=724c58c85006ed68
> kernel:         4.17.14-202.fc28.x86_64
> package:        gnome-software-3.28.2-1.fc28
> reason:         gnome-software killed by SIGABRT
> rootdir:        /
> runlevel:       N 5
> type:           CCpp
> uid:            1000

Please disregard the report i filed against this module. I later found that a motherboard (Asus B350 prime) bios update had introduced a cpu (Amd Ryzen 7 1800X) core sleep bug that only triggered on low system load when "on demand" sceduler was used. That bug has now been corrected and it's working again.

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