Bug 2274928

Summary: [abrt] musescore: dri2_wl_swap_buffers_with_damage(): mscore killed by SIGSEGV
Product: [Fedora] Fedora Reporter: Hécate <hecate+fedora>
Component: musescoreAssignee: Jerry James <loganjerry>
Status: CLOSED ERRATA QA Contact:
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 39CC: hecate+fedora, loganjerry
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/b5ce8a0e5624ab7fd009abd49bf2f3a51dfcca3
Whiteboard: abrt_hash:6514539e3c4e2d8ca55e81f362942c1c1a2eb93e;VARIANT_ID=kde;
Fixed In Version: musescore-4.3.0-10.fc40 musescore-4.3.0-10.fc39 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2024-05-16 01:51:52 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: proc_pid_status
none
File: maps
none
File: limits
none
File: environ
none
File: open_fds
none
File: mountinfo
none
File: os_info
none
File: cpuinfo
none
File: core_backtrace
none
File: exploitable
none
File: var_log_messages
none
File: backtrace none

Description Hécate 2024-04-13 18:35:20 UTC 
Version-Release number of selected component:
musescore-4.2.1-9.fc39

Additional info:
reporter:       libreport-2.17.11
type:           CCpp
reason:         mscore killed by SIGSEGV
journald_cursor: s=d9f12b4b7f7244e4a9db5aae307ae100;i=193aefc;b=1393f3bc99d243e595503398fc6ecf34;m=ec225f07;t=615fce6bf43be;x=491ab52f710d4c7
executable:     /usr/bin/mscore
cmdline:        /usr/bin/mscore
cgroup:         0::/user.slice/user-1000.slice/user/app.slice/app-org.musescore.MuseScore-6951aa774f574823956fc218d5e6cb4b.scope
rootdir:        /
uid:            1000
kernel:         6.8.4-200.fc39.x86_64
package:        musescore-4.2.1-9.fc39
runlevel:       N 5
dso_list:       /usr/bin/mscore musescore-4.2.1-9.fc39.x86_64 (Fedora Project) 1712933698
backtrace_rating: 4
crash_function: dri2_wl_swap_buffers_with_damage

Truncated backtrace:
Thread no. 0 (10 frames)
 #0 dri2_wl_swap_buffers_with_damage at ../src/egl/drivers/dri2/platform_wayland.c:1625
 #1 dri2_swap_buffers at ../src/egl/drivers/dri2/egl_dri2.c:1958
 #2 eglSwapBuffers at ../src/egl/main/eglapi.c:1443
 #3 QtWaylandClient::QWaylandGLContext::swapBuffers at ../../../../hardwareintegration/client/wayland-egl/qwaylandglcontext.cpp:502
 #4 QSGRenderThread::syncAndRender at scenegraph/qsgthreadedrenderloop.cpp:869
 #5 QSGRenderThread::run at scenegraph/qsgthreadedrenderloop.cpp:1042
 #6 operator() at thread/qthread_unix.cpp:350
 #7 (anonymous namespace)::terminate_on_exception<QThreadPrivate::start(void*)::<lambda()> > at thread/qthread_unix.cpp:287
 #8 QThreadPrivate::start at thread/qthread_unix.cpp:310
 #10 clone3 at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:78
Comment 1 Hécate 2024-04-13 18:35:23 UTC 
Created attachment 2026729 [details]
File: proc_pid_status
Comment 2 Hécate 2024-04-13 18:35:24 UTC 
Created attachment 2026730 [details]
File: maps
Comment 3 Hécate 2024-04-13 18:35:25 UTC 
Created attachment 2026731 [details]
File: limits
Comment 4 Hécate 2024-04-13 18:35:26 UTC 
Created attachment 2026732 [details]
File: environ
Comment 5 Hécate 2024-04-13 18:35:27 UTC 
Created attachment 2026733 [details]
File: open_fds
Comment 6 Hécate 2024-04-13 18:35:28 UTC 
Created attachment 2026734 [details]
File: mountinfo
Comment 7 Hécate 2024-04-13 18:35:30 UTC 
Created attachment 2026735 [details]
File: os_info
Comment 8 Hécate 2024-04-13 18:35:31 UTC 
Created attachment 2026736 [details]
File: cpuinfo
Comment 9 Hécate 2024-04-13 18:35:32 UTC 
Created attachment 2026737 [details]
File: core_backtrace
Comment 10 Hécate 2024-04-13 18:35:33 UTC 
Created attachment 2026738 [details]
File: exploitable
Comment 11 Hécate 2024-04-13 18:35:35 UTC 
Created attachment 2026739 [details]
File: var_log_messages
Comment 12 Hécate 2024-04-13 18:35:36 UTC 
Created attachment 2026740 [details]
File: backtrace
Comment 13 Jerry James 2024-05-08 00:27:29 UTC 
I am about to push version 4.3.0 to testing.  Could you please try it and see if it fixes this issue for you?
Comment 14 Fedora Update System 2024-05-08 00:28:29 UTC 
FEDORA-2024-41a95f1379 (musescore-4.3.0-10.fc39) has been submitted as an update to Fedora 39.
https://bodhi.fedoraproject.org/updates/FEDORA-2024-41a95f1379
Comment 15 Fedora Update System 2024-05-08 00:28:30 UTC 
FEDORA-2024-fe029d9f84 (musescore-4.3.0-10.fc40) has been submitted as an update to Fedora 40.
https://bodhi.fedoraproject.org/updates/FEDORA-2024-fe029d9f84
Comment 16 Fedora Update System 2024-05-08 19:36:01 UTC 
FEDORA-2024-fe029d9f84 has been pushed to the Fedora 40 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2024-fe029d9f84`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2024-fe029d9f84

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
Comment 17 Fedora Update System 2024-05-09 02:49:29 UTC 
FEDORA-2024-41a95f1379 has been pushed to the Fedora 39 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2024-41a95f1379`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2024-41a95f1379

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
Comment 18 Fedora Update System 2024-05-16 01:51:52 UTC 
FEDORA-2024-fe029d9f84 (musescore-4.3.0-10.fc40) has been pushed to the Fedora 40 stable repository.
If problem still persists, please make note of it in this bug report.
Comment 19 Fedora Update System 2024-05-17 01:30:25 UTC 
FEDORA-2024-41a95f1379 (musescore-4.3.0-10.fc39) has been pushed to the Fedora 39 stable repository.
If problem still persists, please make note of it in this bug report.