Wireshark worked fine, till I run dnf update. Then keeps crashing after "Finding local interfaces". I.e. I cannot open any captures. That happens right after updating, without restart. And keeps crashing after restart, too.

When using Wayland:

$ /usr/bin/wireshark 
QSocketNotifier: Can only be used with threads started with QThread
Segmentation fault (core dumped)

On X.Org it crashes, too.

Interestingly, when starting with sudo then it works fine. That is surprising, as Qt libs are the same, though settings may differ. Deleting ~/.config/wireshark does not help.

Wireshark from Flathub crashes, too.

I tried on another computer with Fedora 32, running X.Org with Gnome. Wireshark crashes with this in journalctl:

`abrt-notification[2986]: Process 2881 (wireshark) crashed in QtMetaTypePrivate::QMetaTypeFunctionHelper<QString, true>::Construct(void*, void const*)()`

Hi,

so if you see the "Finding local interfaces" message, does it mean that the GUI at least starts up for a short time and then it crashes? If wireshark actually works with sudo, one thing that could be a problem is you not being in the wireshark group? Try adding your username to the wireshark group and start wireshark after logging-out and logging back in.

1. sudo usermod -aG wireshark <username>
2. log out and log back in
3. run wireshark

When my non-root username was not in the wireshark group, wireshark did not crash but it caused an error when I was trying to capture anything because it cannot access any interfaces. Maybe in your case this is causing the crash, but this is a wild guess at most.

Also, can you please provide the version of qt5-qtbase-devel package?

Thanks and regards,
Michal

Hey Michal,

I'm having the exact same issue as the others, after upgrading to Fedora 32 (might have done a system update via Gnome Software since then too). The GUI does show up for a split second, until it get's to "Finding local interfaces", then it crashes.

My user is already part of the wireshark group, coming from Fedora 31 where I had that configured and working. Just to be sure I removed / readded myself to the group, but nothing changed (and logging in / out too).

It does work correctly as root and more strangely it even works if I run 'su -l MYUSERNAME' first or with 'sudo -u MYUSERNAME wireshark' too.

I don't have qt5-qtbase-devel installed, and installing it doesn't make a difference.

Backtrace on gdb via 'coredumpctl -1 debug' after installing the required debuginfos shows:

(gdb) bt
#0  QString::QString (other=..., this=0x55b611660030) at ../../include/QtCore/../../src/corelib/tools/qstring.h:955
#1  QtMetaTypePrivate::QMetaTypeFunctionHelper<QString, true>::Construct (where=0x55b611660030, t=0x1b15808ff08f3200) at kernel/qmetatype.h:805
#2  0x00007f23cf7792d5 in QMetaType::construct (copy=0x1b15808ff08f3200, where=<optimized out>, this=0x7ffc3c89a780) at kernel/qmetatype.h:2248
#3  QMetaType::create (type=<optimized out>, copy=0x1b15808ff08f3200) at kernel/qmetatype.cpp:1614
#4  0x00007f23cf78b6a5 in queued_activate (locker=..., argv=0x7ffc3c89a890, c=0x55b61178efb0, signal=<optimized out>, sender=0x55b61138e800) at kernel/qobject.cpp:3633
#5  QMetaObject::activate (sender=0x55b61138e800, signalOffset=<optimized out>, local_signal_index=<optimized out>, argv=<optimized out>) at kernel/qobject.cpp:3755
#6  0x00007f23cf78c352 in QObject::event (this=0x55b61138e800, e=<optimized out>) at kernel/qobject.cpp:1260
#7  0x00007f23d04f4e76 in QApplicationPrivate::notify_helper (this=<optimized out>, receiver=0x55b61138e800, e=0x55b6137a1de0) at kernel/qapplication.cpp:3703
#8  0x00007f23cf7658a0 in QCoreApplication::notifyInternal2 (receiver=0x55b61138e800, event=0x55b6137a1de0) at ../../include/QtCore/../../src/corelib/kernel/qobject.h:143
#9  0x00007f23d0553681 in QWidgetWindow::event (this=0x55b61193f4b0, event=0x55b6137a1de0) at /usr/include/c++/10/bits/atomic_base.h:420
#10 0x00007f23d04f4e76 in QApplicationPrivate::notify_helper (this=<optimized out>, receiver=0x55b61193f4b0, e=0x55b6137a1de0) at kernel/qapplication.cpp:3703
#11 0x00007f23cf7658a0 in QCoreApplication::notifyInternal2 (receiver=0x55b61193f4b0, event=0x55b6137a1de0) at ../../include/QtCore/../../src/corelib/kernel/qobject.h:143
#12 0x00007f23cf768b43 in QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x55b6110a0fa0) at kernel/qcoreapplication.cpp:1840
#13 0x00007f23cf7b1187 in postEventSourceDispatch (s=s@entry=0x55b6113601c0) at kernel/qeventdispatcher_glib.cpp:277
#14 0x00007f23cff4f7cf in g_main_dispatch (context=0x7f23b8005010) at ../glib/gmain.c:3309
#15 g_main_context_dispatch (context=0x7f23b8005010) at ../glib/gmain.c:3974
#16 0x00007f23cff4fb58 in g_main_context_iterate (context=context@entry=0x7f23b8005010, block=block@entry=1, dispatch=dispatch@entry=1, self=<optimized out>) at ../glib/gmain.c:4047
#17 0x00007f23cff4fc23 in g_main_context_iteration (context=0x7f23b8005010, may_block=may_block@entry=1) at ../glib/gmain.c:4108
#18 0x00007f23cf7b0c06 in QEventDispatcherGlib::processEvents (this=0x55b61133dba0, flags=...) at kernel/qeventdispatcher_glib.cpp:423
#19 0x00007f23cf76421b in QEventLoop::exec (this=this@entry=0x7ffc3c89ad50, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:140
#20 0x00007f23cf76bdf6 in QCoreApplication::exec () at ../../include/QtCore/../../src/corelib/global/qflags.h:120
#21 0x000055b610727e41 in main (argc=<optimized out>, qt_argv=<optimized out>) at /usr/src/debug/wireshark-3.2.3-1.fc32.x86_64/ui/qt/main.cpp:964


Best regards,
Balazs

I am, too, member of wireshark group. For me the issue appeared on Friday, 15 May, after I run dnf update. Wireshark had worked fine on Fedora 32 before.

$ dnf history info 366
Transaction ID : 366
Begin time     : Thu 14 May 2020 06:59:07 PM CEST
Begin rpmdb    : 2123:752d9e64e346bf9fd808c8b567db5bc4b1473d08
End time       : Thu 14 May 2020 07:01:39 PM CEST (152 seconds)
End rpmdb      : 2123:b3db5d72b7bdae2899bd134cad42118dd40061cc
User           : Derba <derba>
Return-Code    : Success
Releasever     : 32
Command Line   : update

I could not rollback the whole upgrade. I tried some manually, e.g. qgnomeplatform, but that did not solve the issue.

I experience this crash too since updating to Fedora 32. My package versions at the latest check are:

wireshark-cli-3.2.3-1.fc32.x86_64
wireshark-3.2.3-1.fc32.x86_64
qt5-srpm-macros-5.13.2-2.fc32.noarch
qt5-qtlocation-5.13.2-2.fc32.x86_64
qt5-qtserialport-5.13.2-2.fc32.x86_64
qt5-qtbase-gui-5.13.2-5.fc32.i686
qt5-qtbase-gui-5.13.2-5.fc32.x86_64
qt5-qtx11extras-5.13.2-2.fc32.x86_64
qt5-qtbase-5.13.2-5.fc32.x86_64
qt5-qtwebkit-5.212.0-0.42.alpha3.fc32.x86_64
qt5-qtwebchannel-5.13.2-2.fc32.x86_64
qt5-qtmultimedia-5.13.2-2.fc32.x86_64
qt5-qtdeclarative-devel-5.13.2-2.fc32.x86_64
qt5-qtenginio-1.6.2-28.fc32.x86_64
qt5-qtxmlpatterns-5.13.2-2.fc32.x86_64
qt5-qtwebsockets-5.13.2-2.fc32.x86_64
qt5-qtconnectivity-5.13.2-2.fc32.x86_64
qt5-qttools-libs-help-5.13.2-5.fc32.x86_64
qt5-rpm-macros-5.13.2-2.fc32.noarch
qt5-qtsensors-5.13.2-2.fc32.x86_64
python3-qt5-base-5.13.2-5.fc32.x86_64
qt5-qttools-libs-designer-5.13.2-5.fc32.x86_64
qt5-qtbase-5.13.2-5.fc32.i686
qt5-qtdeclarative-5.13.2-2.fc32.x86_64
python3-qt5-5.13.2-5.fc32.x86_64
qt5-qtbase-common-5.13.2-5.fc32.noarch
qt5-qtquickcontrols-5.13.2-2.fc32.x86_64
python3-pyqt5-sip-4.19.21-1.fc32.x86_64
qt5-qtwayland-5.13.2-5.fc32.x86_64
qt5-qtbase-devel-5.13.2-5.fc32.x86_64
qt5-qtsvg-5.13.2-2.fc32.x86_64
adwaita-qt5-1.1.3-1.fc32.x86_64
python-qt5-rpm-macros-5.13.2-5.fc32.noarch
qt5-qttools-common-5.13.2-5.fc32.noarch
qgnomeplatform-0.6.1-1.fc32.x86_64

As an aside, VirtualBox-5.2-5.2.40_137108_fedora29-1.x86_64 crashes too in my machine, without showing any GUI, and also uses QT5. However scribus, mediawriter and audacious also use Qt5 and do not crash at all.

As a workaround, if I uninstall qgnomeplatform-0.6.1-1.fc32 and its dependency adwaita-qt5-1.1.3-1.fc32 , wireshark starts correctly.

VirtualBox-5.2-5.2.40_137108_fedora29-1.x86_64 starts if I unset WAYLAND_DISPLAY from the environment (under GNOME Shell/Wayland). Observed crashes under Cinnamon/X11 could be because of the qgnomeplatform or adwaita-qt5 package.

*** Bug 1837659 has been marked as a duplicate of this bug. ***

The issue is fixed with adwaita-qt5-1.1.3-2, which is currently in testing.

https://koji.fedoraproject.org/koji/buildinfo?buildID=1508738

Reproduced with adwaita-qt5-1.1.2-2, issue no longer visible when upgraded to adwaita-qt5-1.1.3-2. I will keep this open until the latest version gets to stable. This bug can be sort of a tracker for all the duplicates out there.

*** Bug 1837766 has been marked as a duplicate of this bug. ***

*** Bug 1838513 has been marked as a duplicate of this bug. ***

adwaita-qt5-1.1.3-2 was just in my list of updates and having installed it wireshark starts without segfaulting. Thank you!

Fixed with latest adwaita-qt, closing. If you encounter this problem again, feel free to reopen or create a new bug.