Hide Forgot
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
Created attachment 806002 [details] File: backtrace
Created attachment 806003 [details] File: cgroup
Created attachment 806004 [details] File: core_backtrace
Created attachment 806005 [details] File: dso_list
Created attachment 806006 [details] File: environ
Created attachment 806007 [details] File: limits
Created attachment 806008 [details] File: maps
Created attachment 806009 [details] File: open_fds
Created attachment 806010 [details] File: proc_pid_status
Created attachment 806011 [details] File: var_log_messages
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
Seems to happen randomly. Wasn't doing anything in particular.
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
Noticed shortly after connecting to VPN and running kinit in the terminal.
Similar to comment 14 for me but only thing I did was kinit. VPN was involved but already connected.
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.