Bug 2174968

Summary: [abrt] qmidiarp: std::__glibcxx_assert_fail(): qmidiarp killed by SIGABRT
Product: [Fedora] Fedora Reporter: manunyo <undefineduncertainty>
Component: qmidiarpAssignee: Guido Aulisi <guido.aulisi>
Status: NEW --- QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 37CC: brendan.jones.it, esteban.xandri, guido.aulisi, weldon
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/0faabc5d7f9400e995050e6c9ce13a4fc2b4ce1b
Whiteboard: abrt_hash:60f7ff923e58752f20216d39518767a4f0ab72d7;VARIANT_ID=workstation;
Fixed In Version: Doc Type: ---
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 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: core_backtrace
none
File: cpuinfo
none
File: dso_list
none
File: environ
none
File: limits
none
File: maps
none
File: mountinfo
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description manunyo 2023-03-02 18:22:33 UTC
Description of problem:
Opening the app and creating an arp work fine but the app just terminate (GUI  gone)  as soon as I try to add an LFO or Sequence

Version-Release number of selected component:
qmidiarp-0.6.5-13.fc37

Additional info:
reporter:       libreport-2.17.4
backtrace_rating: 3
cgroup:         0::/user.slice/user-1000.slice/user/app.slice/app-gnome-qmidiarp-11731.scope
cmdline:        qmidiarp
crash_function: std::__glibcxx_assert_fail
executable:     /usr/bin/qmidiarp
journald_cursor: s=afb2210226374b91af44b0b529165029;i=18f75;b=a38e09749a1d4d3397cf0f372cf75e6d;m=243147103;t=5f5dcd1bb46d4;x=8f2fb72bc8adfbde
kernel:         6.1.14-200.fc37.x86_64
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000

Comment 1 manunyo 2023-03-02 18:22:36 UTC
Created attachment 1947563 [details]
File: backtrace

Comment 2 manunyo 2023-03-02 18:22:37 UTC
Created attachment 1947564 [details]
File: core_backtrace

Comment 3 manunyo 2023-03-02 18:22:38 UTC
Created attachment 1947565 [details]
File: cpuinfo

Comment 4 manunyo 2023-03-02 18:22:39 UTC
Created attachment 1947566 [details]
File: dso_list

Comment 5 manunyo 2023-03-02 18:22:41 UTC
Created attachment 1947567 [details]
File: environ

Comment 6 manunyo 2023-03-02 18:22:42 UTC
Created attachment 1947568 [details]
File: limits

Comment 7 manunyo 2023-03-02 18:22:43 UTC
Created attachment 1947569 [details]
File: maps

Comment 8 manunyo 2023-03-02 18:22:44 UTC
Created attachment 1947570 [details]
File: mountinfo

Comment 9 manunyo 2023-03-02 18:22:45 UTC
Created attachment 1947571 [details]
File: open_fds

Comment 10 manunyo 2023-03-02 18:22:47 UTC
Created attachment 1947572 [details]
File: proc_pid_status

Comment 11 manunyo 2023-03-02 18:22:48 UTC
Created attachment 1947573 [details]
File: var_log_messages

Comment 12 Weldon Goree 2023-08-07 05:55:19 UTC
I turned off hardening (and probably a lot of other stuff) in the spec file, viz:

%build
export CXXFLAGS="-fPIC -DPIC -g"
%configure --enable-nsm
make %{?_smp_mflags}

The resulting build does not crash when an LFO or sequencer are added.