Description of problem:
The issue happened after I resumed the laptop from suspend, the app loaded for 5 seconds then crashed.
Version-Release number of selected component:
cmdline: /usr/bin/corebird --gapplication-service
pkg_fingerprint: 4089 D8F2 FDB1 9C98
pkg_vendor: Fedora Project
runlevel: N 5
Thread no. 1 (10 frames)
#0 g_main_context_ref at gmain.c:519
#1 soup_socket_set_property at soup-socket.c:338
#2 object_set_property at gobject.c:1423
#3 g_object_new_internal at gobject.c:1837
#4 g_object_new_valist at gobject.c:2042
#5 soup_socket_new at soup-socket.c:823
#6 soup_connection_connect_sync at soup-connection.c:447
#7 get_connection at soup-session.c:1957
#8 soup_session_process_queue_item at soup-session.c:1978
#9 soup_session_real_send_message at soup-session.c:2228
This is a private, duplicate bug report of bug 1436680. The report has been created because Bugzilla cannot grant access to a comment for a specific group.
Created attachment 1285367 [details]
Created attachment 1285368 [details]
Created attachment 1285369 [details]
Created attachment 1285370 [details]
Created attachment 1285371 [details]
Created attachment 1285372 [details]
Created attachment 1285373 [details]
Created attachment 1285374 [details]
Created attachment 1285375 [details]
Created attachment 1285376 [details]
Created attachment 1285377 [details]
Created attachment 1285378 [details]
Created attachment 1285379 [details]
*** This bug has been marked as a duplicate of bug 1436680 ***
Backtrace doesn't have any security sensitive information. Hence marking the bug as public so that the upstream maintainer can access it.
(In reply to Debarshi Ray from comment #15)
> Backtrace doesn't have any security sensitive information. Hence marking the
> bug as public so that the upstream maintainer can access it.
I don't have an issue with that. the ABRT selected the private checkbox for me and I didn't realize that except after the report has been added (when it alerted me it's going to be reported as duplicate instead of added as a comment to the original report.
*** This bug has been marked as a duplicate of bug 1458498 ***