 |
Hello. I can't reproduce, I tried running wireshark, I can capture packets, I can save to file, I can then load this file. No problem. I tried wireshark as root and non-root. I ran my test on a up-to-date Kali Rolling VM, and I can confirm that I have the same versions as you ( Can you please make sure that your system is up-to-date ( Note that I could only test on a amd64 VM, I don't have a arm64 machine around to test... It could be that you're hitting a arch-specific bug. |
|
|
There are indeed arm64 qt6 bugs reported on the Debian bugtracker, similar to your bug:
Assuming you run Wayland, you could try to switch to X11 instead (the exact procedure to do that depends on whether you run GNOME, KDE, XFCE) |
|
|
I tried both X11 session or Wayland session with GNOME, amd64 VM, and I still can't reproduce, so it really seems to be specific to arm64 |
 |
Yes, I'm quite sure it is arm64 specific. The system is up to date and I have also rebooted. Also, to cross check, I've reinstalled from a fresh image. This works fine. Then, I upgraded only wireshark and Qt and I got the same crash as on the fully up-to-date system. The Debian bug reports look very much like the same problem. I'm using XFCE, which only supports X11, I believe. |
|
|
You are correct. If you're motivated, you could try another install with GNOME, check that you can reproduce the issue. If so, then enable Wayland (by default Kali's GNOME runs X11), and check that the bug can still be reproduced. That would help to know if it's a bug that is specific to X11 or Wayland, and maybe it would help us to find if a patch is available already. Or at least, it would help to refine the existing bug report. To make sure you run wayland or x11, you can run: To enable Wayland on Kali's GNOME, check the file
The thing is, we can't roll back this change, now latest Qt6 is in kali-rolling, and it will be released in Kali 2024.4 in around 2 weeks or so. |
|
|
OK, I tried the instructions, but I couldn't get a Wayland session to run. GDM still only offered to start X11 sessions. Again, the arm64 build for Raspberry may be a bit of a special case here ... |
|
|
I know that the instructions work for amd64, I just tried it myself when I wrote the message, but that was for a amd64 VM, indeed, I didn't test arm64. However I don't think arm64 should be special in that regard... Do you use an image downloaded from https://www.kali.org/get-kali/#kali-arm?
After enabling Wayland, I just log in without touching any setting, I didn't even notice that GDM offers to start X11. By default it should log you in Wayland. |
|
|
OK, I was missing the "dtoverlay=vc4-kms-v3d" line in /boot/config.txt Now, I also tested with Wayland: Exactly the same crash happens there as well. |
- Anonymous
