Bug 1008915

Summary: [abrt] gnome-session-3.9.91-1.fc20: _g_log_abort: Process /usr/bin/gnome-session was killed by signal 6 (SIGABRT)
Product: [Fedora] Fedora Reporter: Nicolas Mailhot <nicolas.mailhot>
Component: gnome-sessionAssignee: Ray Strode [halfline] <rstrode>
Status: CLOSED WORKSFORME QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 22CC: atodorov, cschalle, ignatenko, rstrode
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:391097794e14e190ae7f19fd2aff0b0ecc796c28
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-03-20 10:17:31 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 Nicolas Mailhot 2013-09-17 10:36:41 UTC 
Description of problem:
probably fallout from systemd-207-2 breakage, but gnome3 should be more resilient

Version-Release number of selected component:
gnome-session-3.9.91-1.fc20

Additional info:
reporter:       libreport-2.1.7
backtrace_rating: 4
cmdline:        /usr/bin/gnome-session --autostart /usr/share/gdm/greeter/autostart
crash_function: _g_log_abort
executable:     /usr/bin/gnome-session
kernel:         3.12.0-0.rc0.git26.1.fc21.x86_64
runlevel:       N 5
type:           CCpp
uid:            42

Truncated backtrace:
Thread no. 1 (5 frames)
 #2 _g_log_abort at gmessages.c:255
 #5 gsm_manager_quit at gsm-manager.c:533
 #6 end_phase at gsm-manager.c:591
 #7 remove_clients_for_connection at gsm-manager.c:1720
 #8 gsm_manager_bus_filter at gsm-manager.c:1804
Comment 1 Nicolas Mailhot 2013-09-17 10:36:45 UTC 
Created attachment 798722 [details]
File: backtrace
Comment 2 Nicolas Mailhot 2013-09-17 10:36:48 UTC 
Created attachment 798723 [details]
File: cgroup
Comment 3 Nicolas Mailhot 2013-09-17 10:36:51 UTC 
Created attachment 798724 [details]
File: core_backtrace
Comment 4 Nicolas Mailhot 2013-09-17 10:36:54 UTC 
Created attachment 798725 [details]
File: dso_list
Comment 5 Nicolas Mailhot 2013-09-17 10:36:57 UTC 
Created attachment 798726 [details]
File: environ
Comment 6 Nicolas Mailhot 2013-09-17 10:36:59 UTC 
Created attachment 798727 [details]
File: limits
Comment 7 Nicolas Mailhot 2013-09-17 10:37:03 UTC 
Created attachment 798728 [details]
File: maps
Comment 8 Nicolas Mailhot 2013-09-17 10:37:06 UTC 
Created attachment 798729 [details]
File: open_fds
Comment 9 Nicolas Mailhot 2013-09-17 10:37:08 UTC 
Created attachment 798730 [details]
File: proc_pid_status
Comment 10 Nicolas Mailhot 2013-09-17 10:37:11 UTC 
Created attachment 798731 [details]
File: var_log_messages
Comment 11 Igor Gnatenko 2013-09-27 08:56:50 UTC 
Confirm on 3.10.0
Comment 12 Alexander Todorov 2013-10-11 11:37:35 UTC 
Same for me on 3.10. 

I'm not sure if this is a stand alone issue or related to:
https://bugzilla.gnome.org/show_bug.cgi?id=709810

which I was debugging and then after reboot I saw ABRT reporting this bug.
Comment 13 Jaroslav Reznik 2015-03-03 15:04:23 UTC 
This bug appears to have been reported against 'rawhide' during the Fedora 22 development cycle.
Changing version to '22'.

More information and reason for this action is here:
https://fedoraproject.org/wiki/Fedora_Program_Management/HouseKeeping/Fedora22
Comment 14 Igor Gnatenko 2016-03-20 10:17:31 UTC 
no comments for long time.