Bug 1625465

Summary: [abrt] bluez: cmd_advertise(): bluetoothctl killed by SIGSEGV
Product: [Fedora] Fedora Reporter: Angie <angelapuget>
Component: bluezAssignee: Don Zickus <dzickus>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 28CC: bnocera, dwmw2, dzickus, spacewar
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/ba5cbdf57720f118f9bd0ecf9a9b937b5f6d1db6
Whiteboard: abrt_hash:30e1bfc40aa608844d52ca83c4c59250fb9e2704;VARIANT_ID=workstation;
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-05-28 22:19:07 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: cpuinfo
none
File: dso_list
none
File: environ
none
File: exploitable
none
File: limits
none
File: maps
none
File: mountinfo
none
File: open_fds
none
File: proc_pid_status none

Description Angie 2018-09-05 03:44:51 UTC 
Version-Release number of selected component:
bluez-5.50-1.fc28

Additional info:
reporter:       libreport-2.9.5
backtrace_rating: 3
cmdline:        bluetoothctl
crash_function: cmd_advertise
executable:     /usr/bin/bluetoothctl
journald_cursor: s=8fae5782deae48258f5a70c8c4b5a8aa;i=12db7;b=2bf6598a1ab44397b9e23144fb8686a7;m=2922ad5ac;t=575178ae2b28f;x=9da9dbdc7caff885
kernel:         4.17.19-200.fc28.x86_64
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (10 frames)
 #0 cmd_advertise at client/main.c:2177
 #1 cmd_exec at src/shared/shell.c:373
 #2 menu_exec at src/shared/shell.c:400
 #3 shell_exec at src/shared/shell.c:443
 #4 rl_handler at src/shared/shell.c:590
 #5 rl_callback_read_char
 #6 input_read at src/shared/shell.c:1097
 #7 watch_callback at src/shared/io-glib.c:170
 #8 g_main_context_dispatch
 #9 ??
Comment 1 Angie 2018-09-05 03:44:56 UTC 
Created attachment 1480962 [details]
File: backtrace
Comment 2 Angie 2018-09-05 03:44:57 UTC 
Created attachment 1480963 [details]
File: cgroup
Comment 3 Angie 2018-09-05 03:44:58 UTC 
Created attachment 1480964 [details]
File: core_backtrace
Comment 4 Angie 2018-09-05 03:44:59 UTC 
Created attachment 1480965 [details]
File: cpuinfo
Comment 5 Angie 2018-09-05 03:45:00 UTC 
Created attachment 1480966 [details]
File: dso_list
Comment 6 Angie 2018-09-05 03:45:02 UTC 
Created attachment 1480967 [details]
File: environ
Comment 7 Angie 2018-09-05 03:45:03 UTC 
Created attachment 1480968 [details]
File: exploitable
Comment 8 Angie 2018-09-05 03:45:04 UTC 
Created attachment 1480969 [details]
File: limits
Comment 9 Angie 2018-09-05 03:45:06 UTC 
Created attachment 1480970 [details]
File: maps
Comment 10 Angie 2018-09-05 03:45:07 UTC 
Created attachment 1480971 [details]
File: mountinfo
Comment 11 Angie 2018-09-05 03:45:08 UTC 
Created attachment 1480972 [details]
File: open_fds
Comment 12 Angie 2018-09-05 03:45:10 UTC 
Created attachment 1480973 [details]
File: proc_pid_status
Comment 13 Ben Cotton 2019-05-02 19:17:35 UTC 
This message is a reminder that Fedora 28 is nearing its end of life.
On 2019-May-28 Fedora will stop maintaining and issuing updates for
Fedora 28. It is Fedora's policy to close all bug reports from releases
that are no longer maintained. At that time this bug will be closed as
EOL if it remains open with a Fedora 'version' of '28'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 28 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.
Comment 14 Ben Cotton 2019-05-02 20:59:07 UTC 
This message is a reminder that Fedora 28 is nearing its end of life.
On 2019-May-28 Fedora will stop maintaining and issuing updates for
Fedora 28. It is Fedora's policy to close all bug reports from releases
that are no longer maintained. At that time this bug will be closed as
EOL if it remains open with a Fedora 'version' of '28'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 28 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.
Comment 15 Ben Cotton 2019-05-28 22:19:07 UTC 
Fedora 28 changed to end-of-life (EOL) status on 2019-05-28. Fedora 28 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.