Description of problem: Just launched wireshark from the command line. Version-Release number of selected component: 1:wireshark-3.2.3-1.fc31 Additional info: reporter: libreport-2.13.1 backtrace_rating: 4 cgroup: 0::/user.slice/user-10002.slice/user/gnome-terminal-server.service cmdline: wireshark crash_function: QString::QString executable: /usr/bin/wireshark journald_cursor: s=78077ccb2868430d89e164852da96a14;i=345d3d;b=f406b0a8908c4d6c90530714ab9d2883;m=3ba9601fd6;t=5a6081ddbf09f;x=a0f4bf21534f0d9a kernel: 5.6.13-200.fc31.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 10002 Truncated backtrace: Thread no. 1 (10 frames) #0 QString::QString at ../../include/QtCore/../../src/corelib/tools/qstring.h:955 #1 QtMetaTypePrivate::QMetaTypeFunctionHelper<QString, true>::Construct at kernel/qmetatype.h:805 #2 QMetaType::construct at kernel/qmetatype.h:2248 #3 QMetaType::create at kernel/qmetatype.cpp:1614 #4 queued_activate at kernel/qobject.cpp:3633 #5 QMetaObject::activate at kernel/qobject.cpp:3755 #6 QWindow::qt_static_metacall at .moc/moc_qwindow.cpp:411 #7 QObject::event at kernel/qobject.cpp:1260 #8 QWidget::event at kernel/qwidget.cpp:9405 #9 QMainWindow::event at widgets/qmainwindow.cpp:1343
Created attachment 1690012 [details] File: backtrace
Created attachment 1690013 [details] File: core_backtrace
Created attachment 1690014 [details] File: cpuinfo
Created attachment 1690015 [details] File: dso_list
Created attachment 1690016 [details] File: environ
Created attachment 1690017 [details] File: exploitable
Created attachment 1690018 [details] File: limits
Created attachment 1690019 [details] File: maps
Created attachment 1690020 [details] File: mountinfo
Created attachment 1690021 [details] File: open_fds
Created attachment 1690022 [details] File: proc_pid_status
*** Bug 1837760 has been marked as a duplicate of this bug. ***
*** Bug 1838340 has been marked as a duplicate of this bug. ***
*** Bug 1838263 has been marked as a duplicate of this bug. ***
I think that this is the same issue as described first in bug #1836326. Closing this as a duplicate, feel free to reopen if you feel that this is a different issue. *** This bug has been marked as a duplicate of bug 1836326 ***