Fedora Account System
Red Hat Associate
Red Hat Customer
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: corebird-1.5-1.fc25 Additional info: reporter: libreport-2.8.0 backtrace_rating: 4 cmdline: /usr/bin/corebird --gapplication-service crash_function: g_main_context_ref executable: /usr/bin/corebird global_pid: 3524 kernel: 4.10.17-200.fc25.x86_64 pkg_fingerprint: 4089 D8F2 FDB1 9C98 pkg_vendor: Fedora Project runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: 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] File: backtrace
Created attachment 1285368 [details] File: cgroup
Created attachment 1285369 [details] File: core_backtrace
Created attachment 1285370 [details] File: dso_list
Created attachment 1285371 [details] File: environ
Created attachment 1285372 [details] File: exploitable
Created attachment 1285373 [details] File: limits
Created attachment 1285374 [details] File: maps
Created attachment 1285375 [details] File: mountinfo
Created attachment 1285376 [details] File: namespaces
Created attachment 1285377 [details] File: open_fds
Created attachment 1285378 [details] File: proc_pid_status
Created attachment 1285379 [details] File: var_log_messages
*** 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 ***