Bug 1014225

Summary: [abrt] gnome-online-accounts-3.8.3-3.fc19: clear_scheduled_wakeups: Process /usr/libexec/goa-daemon was killed by signal 6 (SIGABRT)
Product: [Fedora] Fedora Reporter: Jason Elwell <elwellj>
Component: gnome-online-accountsAssignee: Debarshi Ray <debarshir>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 19CC: amit.shah, benl, bnocera, brian, brian.murrell, cbredesen, debarshir, djuran, fweimer, jturner, mikem, sgraf, todoleza
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:5cc62254776c32eecc1ac0aaaead79718282a57e
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-12-30 15:48:44 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 Jason Elwell 2013-10-01 14:34:56 UTC 
Description of problem:
Tried to open a SMB/CIFS share after suspending the system.  I was initially on the network, but on VPN when it happened.

Version-Release number of selected component:
gnome-online-accounts-3.8.3-3.fc19

Additional info:
reporter:       libreport-2.1.7
backtrace_rating: 4
cmdline:        /usr/libexec/goa-daemon
crash_function: clear_scheduled_wakeups
executable:     /usr/libexec/goa-daemon
kernel:         3.11.1-200.fc19.x86_64
runlevel:       N 5
type:           CCpp
uid:            2746

Truncated backtrace:
Thread no. 1 (2 frames)
 #4 clear_scheduled_wakeups at goaalarm.c:163
 #5 async_alarm_cancel_idle_cb at goaalarm.c:264
Comment 1 Jason Elwell 2013-10-01 14:35:05 UTC 
Created attachment 806002 [details]
File: backtrace
Comment 2 Jason Elwell 2013-10-01 14:35:09 UTC 
Created attachment 806003 [details]
File: cgroup
Comment 3 Jason Elwell 2013-10-01 14:35:12 UTC 
Created attachment 806004 [details]
File: core_backtrace
Comment 4 Jason Elwell 2013-10-01 14:35:15 UTC 
Created attachment 806005 [details]
File: dso_list
Comment 5 Jason Elwell 2013-10-01 14:35:18 UTC 
Created attachment 806006 [details]
File: environ
Comment 6 Jason Elwell 2013-10-01 14:35:21 UTC 
Created attachment 806007 [details]
File: limits
Comment 7 Jason Elwell 2013-10-01 14:35:24 UTC 
Created attachment 806008 [details]
File: maps
Comment 8 Jason Elwell 2013-10-01 14:35:27 UTC 
Created attachment 806009 [details]
File: open_fds
Comment 9 Jason Elwell 2013-10-01 14:35:31 UTC 
Created attachment 806010 [details]
File: proc_pid_status
Comment 10 Jason Elwell 2013-10-01 14:35:34 UTC 
Created attachment 806011 [details]
File: var_log_messages
Comment 11 David Juran 2013-10-03 08:33:06 UTC 
The abrt message just came up shortly after un-suspending laptop and authenticating to WLAN

reporter:       libreport-2.1.7
backtrace_rating: 4
cmdline:        /usr/libexec/goa-daemon
crash_function: clear_scheduled_wakeups
executable:     /usr/libexec/goa-daemon
kernel:         3.11.2-201.fc19.x86_64
package:        gnome-online-accounts-3.8.3-3.fc19
reason:         Process /usr/libexec/goa-daemon was killed by signal 6 (SIGABRT)
runlevel:       N 5
type:           CCpp
uid:            500
Comment 12 Mike McLean 2013-10-08 19:51:04 UTC 
Seems to happen randomly. Wasn't doing anything in particular.
Comment 13 Amit Shah 2013-10-10 17:01:55 UTC 
Issued kinit and updated the validity of the ticket.  This crash happened soon after.

reporter:       libreport-2.1.7
backtrace_rating: 4
cmdline:        /usr/libexec/goa-daemon
crash_function: clear_scheduled_wakeups
executable:     /usr/libexec/goa-daemon
kernel:         3.11.3-201.fc19.x86_64
package:        gnome-online-accounts-3.8.3-3.fc19
reason:         Process /usr/libexec/goa-daemon was killed by signal 6 (SIGABRT)
runlevel:       N 5
type:           CCpp
uid:            1000
Comment 14 David Kovalsky 2013-10-14 23:06:47 UTC 
Noticed shortly after connecting to VPN and running kinit in the terminal.
Comment 15 Chris Bredesen 2013-11-18 13:01:37 UTC 
Similar to comment 14 for me but only thing I did was kinit. VPN was involved but already connected.
Comment 16 Brian J. Murrell 2013-11-24 13:07:25 UTC 
I just got this yet again.

Since this keeps happening, and to multiple people, any chance of getting a fix for it?  It doesn't look like it's even been triaged.