ANNOUNCEMENT: Live Wireshark University & Allegro Packets online APAC Wireshark Training Session
July 17th, 2024 | 10:00am-11:55am SGT (UTC+8) | Online

Wireshark-bugs: [Wireshark-bugs] [Bug 12237] Cannot resize panes

Date: Fri, 04 Mar 2016 16:06:02 +0000

changed bug 12237


What Removed Added
Priority Low Medium
Severity Major Critical

Comment # 1 on bug 12237 from
Just so you know, I'm running Mageia 5 Linux on Parallels Desktop 11 for Mac
v11.1.3 (32521) on OS X El Capitan v10.11.3 on a Mid 2012 13 inch MacBook Air.

When my distro updated my Wireshark to the new QT UI version (v2.0.1) I
immediately discovered I could not resize the 3 panes (packet list, details,
bytes) in the main window.  The list and details panes default to a fairly
small size (each about 20% of screen height), and the bytes pane defaults to a
fairly large size (about 60% of screen height).  The mouse pointer changes
appropriately when placed over the bar separating the panes, but as soon as you
click the mouse it reverts to the normal mouse pointer and thus you cannot drag
the bars to resize the panes.  This make the application just barely useable. 
This is quite annoying, especially as I am using a 24 inch screen in extended
desktop configuration in order to display lots of data.

I found bug 11951 which someone had submitted for this, and decided to simply
wait until Mageia had a new version.  Tonight when I updated to Wireshark 2.0.2
(from the Mageia repository of course), I was hoping that the problem had been
fixed, only to discover that I still could not resize the panes.

The old GTK version worked ok, pane resizing worked as expected.  I am running
the KDE desktop in my Mageia 5, so I would have expected the new QT UI version
of Wireshark to run even better than the older GTK version.  But alas, not so.

In as much as there is at least one other reported bug on this (11951), can I
assume that this is being worked on already, and it's just a matter of time
till you have a fix?

Over to you.  Thanks.

John H.


You are receiving this mail because:
  • You are watching all bug changes.