Bug 1459168

Summary: [abrt] corebird: g_main_context_ref(): corebird killed by SIGSEGV
Product: [Fedora] Fedora Reporter: Anass Ahmed <anass.1430>
Component: corebirdAssignee: Ryan Lerch <rlerch>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 25CC: debarshir, rlerch
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/1b344a401e14840be76ec364333a0fa9bbcabcee
Whiteboard: abrt_hash:c5344dd597b7f1b984c478bd99cbc3a59fcf1522;VARIANT_ID=workstation;
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-06-06 12:56:40 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace
none
File: cgroup
none
File: core_backtrace
none
File: dso_list
none
File: environ
none
File: exploitable
none
File: limits
none
File: maps
none
File: mountinfo
none
File: namespaces
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description Anass Ahmed 2017-06-06 12:55:14 UTC 
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.
Comment 1 Anass Ahmed 2017-06-06 12:55:20 UTC 
Created attachment 1285367 [details]
File: backtrace
Comment 2 Anass Ahmed 2017-06-06 12:55:22 UTC 
Created attachment 1285368 [details]
File: cgroup
Comment 3 Anass Ahmed 2017-06-06 12:55:24 UTC 
Created attachment 1285369 [details]
File: core_backtrace
Comment 4 Anass Ahmed 2017-06-06 12:55:26 UTC 
Created attachment 1285370 [details]
File: dso_list
Comment 5 Anass Ahmed 2017-06-06 12:55:31 UTC 
Created attachment 1285371 [details]
File: environ
Comment 6 Anass Ahmed 2017-06-06 12:55:41 UTC 
Created attachment 1285372 [details]
File: exploitable
Comment 7 Anass Ahmed 2017-06-06 12:55:43 UTC 
Created attachment 1285373 [details]
File: limits
Comment 8 Anass Ahmed 2017-06-06 12:56:29 UTC 
Created attachment 1285374 [details]
File: maps
Comment 9 Anass Ahmed 2017-06-06 12:56:31 UTC 
Created attachment 1285375 [details]
File: mountinfo
Comment 10 Anass Ahmed 2017-06-06 12:56:33 UTC 
Created attachment 1285376 [details]
File: namespaces
Comment 11 Anass Ahmed 2017-06-06 12:56:34 UTC 
Created attachment 1285377 [details]
File: open_fds
Comment 12 Anass Ahmed 2017-06-06 12:56:36 UTC 
Created attachment 1285378 [details]
File: proc_pid_status
Comment 13 Anass Ahmed 2017-06-06 12:56:38 UTC 
Created attachment 1285379 [details]
File: var_log_messages
Comment 14 Anass Ahmed 2017-06-06 12:56:40 UTC 

*** This bug has been marked as a duplicate of bug 1436680 ***
Comment 15 Debarshi Ray 2017-06-06 13:33:53 UTC 
Backtrace doesn't have any security sensitive information. Hence marking the bug as public so that the upstream maintainer can access it.
Comment 16 Anass Ahmed 2017-06-06 14:37:17 UTC 
(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.
Comment 17 Debarshi Ray 2018-06-05 10:50:41 UTC 

*** This bug has been marked as a duplicate of bug 1458498 ***