Bug 1015534

Summary: [abrt] gnome-session-3.8.4-1.fc19: g_settings_set_property: Process /usr/bin/gnome-session was killed by signal 5 (SIGTRAP)
Product: [Fedora] Fedora Reporter: Gergely Polonkai <gergely>
Component: gnome-sessionAssignee: Ray Strode [halfline] <rstrode>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 19CC: cschalle, rstrode
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:a61bd2ff699b5ccee147a48b0302df8a50ed00c2
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-02-17 17:30:37 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: limits
none
File: maps
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description Gergely Polonkai 2013-10-04 13:06:31 UTC
Description of problem:
Setting XDG_DATA_DIRS to /usr/local/share

According to #gtk+@GIMPNet, I should set it to include even the default values, so actually my bad. But it would be nice to see an error message instead of a crash.

Version-Release number of selected component:
gnome-session-3.8.4-1.fc19

Additional info:
reporter:       libreport-2.1.7
backtrace_rating: 4
cmdline:        gnome-session
crash_function: g_settings_set_property
executable:     /usr/bin/gnome-session
kernel:         3.11.1-200.fc19.x86_64
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (10 frames)
 #2 g_settings_set_property at gsettings.c:492
 #3 object_set_property at gobject.c:1358
 #4 g_object_constructor at gobject.c:1869
 #6 g_object_new_valist at gobject.c:1836
 #8 g_settings_new at gsettings.c:869
 #9 gsm_manager_init at gsm-manager.c:2820
 #10 g_type_create_instance at gtype.c:1917
 #11 g_object_constructor at gobject.c:1855
 #12 gsm_manager_constructor at gsm-manager.c:2431
 #14 g_object_new_valist at gobject.c:1836

Comment 1 Gergely Polonkai 2013-10-04 13:06:35 UTC
Created attachment 807630 [details]
File: backtrace

Comment 2 Gergely Polonkai 2013-10-04 13:06:38 UTC
Created attachment 807631 [details]
File: cgroup

Comment 3 Gergely Polonkai 2013-10-04 13:06:41 UTC
Created attachment 807632 [details]
File: core_backtrace

Comment 4 Gergely Polonkai 2013-10-04 13:06:45 UTC
Created attachment 807633 [details]
File: dso_list

Comment 5 Gergely Polonkai 2013-10-04 13:06:48 UTC
Created attachment 807634 [details]
File: environ

Comment 6 Gergely Polonkai 2013-10-04 13:06:51 UTC
Created attachment 807635 [details]
File: limits

Comment 7 Gergely Polonkai 2013-10-04 13:06:55 UTC
Created attachment 807636 [details]
File: maps

Comment 8 Gergely Polonkai 2013-10-04 13:06:58 UTC
Created attachment 807637 [details]
File: open_fds

Comment 9 Gergely Polonkai 2013-10-04 13:07:01 UTC
Created attachment 807638 [details]
File: proc_pid_status

Comment 10 Gergely Polonkai 2013-10-04 13:07:04 UTC
Created attachment 807639 [details]
File: var_log_messages

Comment 11 Fedora End Of Life 2015-01-09 20:07:06 UTC
This message is a notice that Fedora 19 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 19. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained. Approximately 4 (four) weeks from now this bug will
be closed as EOL if it remains open with a Fedora 'version' of '19'.

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 19 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 12 Fedora End Of Life 2015-02-17 17:30:37 UTC
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 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.