Hi Alex,
Feel free to reach out in private to me and Tomasz, or the wireshark-dev list.
We should probably set up an initial call using Jitsi or similar to discuss the
initial planning and answer any questions you may have.
For communication, we have just moved to GitLab for issue tracking and
On Aug 28, 2020, at 8:21 AM, Richard Sharpe wrote:
> I just came across this article:
>
> https://linuxreviews.org/The_Qt_5.15_Disaster_On_Multi-Monitor_Setups
>
> What it describes is similar to what I have seen from time to time
> with Wireshark (3.2.1 and earlier versions) where if Wireshark
Can’t skip, it is the base for Qt 6. Btw, cannot reproduce this on my system,
Ubuntu 20 LTS. Have to investigate if this is KDE related though, running
Cinnamon over here
Cheers
> Am 28.08.2020 um 21:03 schrieb Richard Sharpe :
>
> Hi folks,
>
> I just came across this article:
>
> https:/
Hi folks,
I just came across this article:
https://linuxreviews.org/The_Qt_5.15_Disaster_On_Multi-Monitor_Setups
What it describes is similar to what I have seen from time to time
with Wireshark (3.2.1 and earlier versions) where if Wireshark is on
my second monitor menu items will appear on the
Hi, guys.
I checked the gitlab and cloned the repo. I grepped the {missing} items and got
the list to work with. According to phase 1 I need to contact mentors and start
working on the planning. I still have some questions about the organised
process for the writers (like: who would review the
