Description of problem: mediawriter crashesh instantly after launch (segfault) on Intel GPU, tested on two different systems. Fedora 33 clean installation. Version-Release number of selected component: mediawriter-4.2.2-2.fc33 Additional info: reporter: libreport-2.14.0 backtrace_rating: 4 cgroup: 0::/user.slice/user-1000.slice/user/app.slice/app-org.gnome.Terminal.slice/vte-spawn-31a60187-da2c-4bea-a692-855de696102d.scope cmdline: mediawriter crash_function: QScopedPointer<QObjectData, QScopedPointerDeleter<QObjectData> >::operator-> executable: /usr/bin/mediawriter journald_cursor: s=06d6dd9e27674db797a67d26a9772806;i=a65;b=860a788ac7054c53b1352ddebbee2435;m=71c165e;t=5ced9a9c48ce4;x=36a67b73fe75345c kernel: 5.8.15-301.fc33.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (9 frames) #0 QScopedPointer<QObjectData, QScopedPointerDeleter<QObjectData> >::operator-> at ../../include/QtCore/../../src/corelib/tools/qscopedpointer.h:118 #1 qGetPtrHelper<QScopedPointer<QObjectData, QScopedPointerDeleter<QObjectData> > > at ../../include/QtCore/../../src/corelib/global/qglobal.h:1135 #2 QObject::d_func at kernel/qobject.h:132 #3 QObjectPrivate::get at kernel/qobject_p.h:339 #4 doActivate<false> at kernel/qobject.cpp:3768 #5 QGuiApplication::screenAdded at .moc/moc_qguiapplication.cpp:389 #6 QtWaylandClient::QWaylandDisplay::handleScreenInitialized at qwaylanddisplay.cpp:281 #7 QtWaylandClient::QWaylandScreen::maybeInitialize at qwaylandscreen.cpp:97 #9 ffi_closure_unix64_inner at ../src/x86/ffi64.c:583
Created attachment 1835502 [details] File: backtrace
Created attachment 1835503 [details] File: core_backtrace
Created attachment 1835504 [details] File: cpuinfo
Created attachment 1835505 [details] File: dso_list
Created attachment 1835506 [details] File: environ
Created attachment 1835507 [details] File: exploitable
Created attachment 1835508 [details] File: limits
Created attachment 1835509 [details] File: maps
Created attachment 1835510 [details] File: mountinfo
Created attachment 1835511 [details] File: open_fds
Created attachment 1835512 [details] File: proc_pid_status
Proposed as a Blocker for 35-final by Fedora user lbrabec using the blocker tracking app because: Testcase "QA:Testcase USB fmw" fails on Fedora 33.
It starts fine for me in a F33 VM, so this might really be graphical driver-related.
Starts normally on Fedora 34 (bare metal, same machine where fmw segfaulted on F33).
Starts normally here on a F33 vm too.
Starts normally on fully updated Fedora 33 (bare metal, same machine where fmw segfaulted on clean installation of F33).
Segfaults on F33 1.2 RC but works fine on fully updated F33 and 34
FMW seems to be working on fully updated Fedora 33, closing.