Bug 1374672

Summary: [abrt] gnome-shell: gtk_recent_manager_enabled_changed(): gnome-shell killed by SIGSEGV
Product: [Fedora] Fedora Reporter: David Novák <novak.david>
Component: gnome-shellAssignee: Owen Taylor <otaylor>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 24CC: christianklomp, crius, fmuellner, otaylor
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/b193b71651198b712cce83c505e75eeaa79cae59
Whiteboard: abrt_hash:a222c7ee422858a7aaa49d5225299efdb82ddf5f;VARIANT_ID=workstation;
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-08-08 17:12:46 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
File: backtrace
none
File: cgroup
none
File: core_backtrace
none
File: dso_list
none
File: environ
none
File: exploitable
none
File: limits
none
File: maps
none
File: mountinfo
none
File: namespaces
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description David Novák 2016-09-09 11:51:59 UTC
Description of problem:
Right after logon.

Version-Release number of selected component:
gnome-shell-3.20.4-1.fc24

Additional info:
reporter:       libreport-2.7.2
backtrace_rating: 4
cmdline:        /usr/bin/gnome-shell
crash_function: gtk_recent_manager_enabled_changed
executable:     /usr/bin/gnome-shell
global_pid:     1407
kernel:         4.7.2-201.fc24.x86_64
pkg_fingerprint: 73BD E983 81B4 6521
pkg_vendor:     Fedora Project
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (7 frames)
 #0 gtk_recent_manager_enabled_changed at gtkrecentmanager.c:435
 #6 g_object_notify_by_spec_internal at gobject.c:1155
 #7 g_object_notify_by_pspec at gobject.c:1265
 #8 _gtk_settings_handle_event at gtksettings.c:2860
 #9 gtk_main_do_event at gtkmain.c:1640
 #10 _gdk_event_emit at gdkevents.c:73
 #16 meta_run at core/main.c:537

Comment 1 David Novák 2016-09-09 11:52:05 UTC
Created attachment 1199400 [details]
File: backtrace

Comment 2 David Novák 2016-09-09 11:52:07 UTC
Created attachment 1199401 [details]
File: cgroup

Comment 3 David Novák 2016-09-09 11:52:08 UTC
Created attachment 1199402 [details]
File: core_backtrace

Comment 4 David Novák 2016-09-09 11:52:10 UTC
Created attachment 1199403 [details]
File: dso_list

Comment 5 David Novák 2016-09-09 11:52:12 UTC
Created attachment 1199404 [details]
File: environ

Comment 6 David Novák 2016-09-09 11:52:13 UTC
Created attachment 1199405 [details]
File: exploitable

Comment 7 David Novák 2016-09-09 11:52:15 UTC
Created attachment 1199406 [details]
File: limits

Comment 8 David Novák 2016-09-09 11:52:17 UTC
Created attachment 1199407 [details]
File: maps

Comment 9 David Novák 2016-09-09 11:52:19 UTC
Created attachment 1199408 [details]
File: mountinfo

Comment 10 David Novák 2016-09-09 11:52:20 UTC
Created attachment 1199409 [details]
File: namespaces

Comment 11 David Novák 2016-09-09 11:52:23 UTC
Created attachment 1199410 [details]
File: open_fds

Comment 12 David Novák 2016-09-09 11:52:24 UTC
Created attachment 1199411 [details]
File: proc_pid_status

Comment 13 David Novák 2016-09-09 11:52:26 UTC
Created attachment 1199412 [details]
File: var_log_messages

Comment 14 David Novák 2016-10-29 15:40:37 UTC
It happens over and over again - nearly every login.. Can I find out somehow, if it's caused by some extension and which?

Comment 15 Christian Klomp 2016-12-11 10:22:00 UTC
The same thing has been happening to me for a while, but only when I disable the recently used files after some usage:
- gsettings set org.gnome.desktop.privacy remember-recent-files false

In my case this often causes the shell to crash and I need to manually replace it to continue. Unfortunately, after it happens it is gone for a while (most likely some history needs to be collected again) and I cannot reproduce this in a VM.

You say this happens during logins. Do you have the Gnome-Shell's history function enabled or disabled? Check it via:
- gsettings get org.gnome.desktop.privacy remember-recent-files

Comment 16 Fedora End Of Life 2017-07-25 22:55:38 UTC
This message is a reminder that Fedora 24 is nearing its end of life.
Approximately 2 (two) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 24. 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 '24'.

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 24 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 17 Fedora End Of Life 2017-08-08 17:12:46 UTC
Fedora 24 changed to end-of-life (EOL) status on 2017-08-08. Fedora 24 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.