FS#45274 - [wireshark-gtk] Border of windows not drawn

Attached to Project: Community Packages
Opened by Alejandro (mealejan) - Tuesday, 09 June 2015, 09:07 GMT
Last edited by Timothy Redaelli (tredaelli) - Monday, 30 May 2016, 15:04 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Timothy Redaelli (tredaelli)
Architecture x86_64
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
The window border and window placement is messed up. Config windows are drawn behind the main window and no window gets a border. Making it impossible to resize or move.

Additional info:
1.12.5

Steps to reproduce:
Start wireshark from the terminal
Put it on the second screen in fullscreen.
Close the programm
Start wireshark from the terminal
This task depends upon

Closed by  Timothy Redaelli (tredaelli)
Monday, 30 May 2016, 15:04 GMT
Reason for closing:  No response
Comment by Doug Newgard (Scimmia) - Wednesday, 10 June 2015, 02:10 GMT
Sounds like a WM problem.
Comment by Doug Newgard (Scimmia) - Friday, 12 June 2015, 03:55 GMT
Ping?
Comment by Alejandro (mealejan) - Monday, 15 June 2015, 15:36 GMT
  • Field changed: Percent Complete (100% → 0%)
This phenomenon only appears with wireshark. I didn't see this problem with other software.
Comment by Doug Newgard (Scimmia) - Monday, 15 June 2015, 15:36 GMT
And does it happen in another window manager? What window manager are you using now?
Comment by Alejandro (mealejan) - Monday, 15 June 2015, 15:44 GMT
Mutter.
I use gnome 3.16
Comment by Doug Newgard (Scimmia) - Monday, 15 June 2015, 17:25 GMT
OK, with mutter/gnome, we're probably talking client side decorations, so it could be wireshark.
Comment by Peter Wu (Lekensteyn) - Tuesday, 16 June 2015, 13:47 GMT
Is it possible for you to add a screenshot that demonstrates the issue?
Comment by Alejandro (mealejan) - Tuesday, 16 June 2015, 13:56 GMT
As you can see, the working border was generated by starting wireshark and moving it to the attached screen. After closing it and starting it again the border wasn't drawn.
   no border.png (151.1 KiB)
   working border.png (158.6 KiB)
Comment by Peter Wu (Lekensteyn) - Tuesday, 16 June 2015, 14:28 GMT
Confirmed with a dual-head setup on a friends laptop:
- 1600x900 primary (LVDS) with 1280x1024 on the right (VGA).
- terminal on right VGA display
- remove ~/.wireshark (or use HOME=/tmp/somedir wireshark)
- start wireshark
- drag wireshark to right (VGA) and maximize it
- close wireshark
- start wireshak again
- reproduced.

Package versions:
gnome-desktop 1:3.16.2-1
wireshark-gtk 1.12.5-2
mutter 3.16.2-1

Changes in ~/.wireshark/recent_common after dragging and closing:
--- a/recent_common
+++ b/recent_common
@@ -16,6 +16,6 @@
# Decimal numbers.
-gui.geometry_main_x: 0
-gui.geometry_main_y: 151
-gui.geometry_main_width: 1600
-gui.geometry_main_height: 836
+gui.geometry_main_x: 1600
+gui.geometry_main_y: 0
+gui.geometry_main_width: 1280
+gui.geometry_main_height: 987

@@ -31,3 +31,3 @@ gui.geometry_status_pane: 250
# Decimal number.
-gui.geometry_status_pane_right: 1100
+gui.geometry_status_pane_right: 780

After the next startup, wireshark shows the bug. Closing wireshark again, I can find this difference:
--- a/recent_common
+++ b/recent_common
@@ -19,3 +19,3 @@ gui.geometry_main_y: 0
gui.geometry_main_width: 1280
-gui.geometry_main_height: 987
+gui.geometry_main_height: 1024

@@ -23,3 +23,3 @@ gui.geometry_main_height: 987
# TRUE or FALSE (case-insensitive).
-gui.geometry_main_maximized: TRUE
+gui.geometry_main_maximized: FALSE

Changing main_height from 1024 to, say, 924 shows the title bar again. There is a bug somewhere, I don't know where exactly.
Comment by Peter Wu (Lekensteyn) - Wednesday, 24 June 2015, 00:50 GMT
Upstream bug: https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=11303
Comment by Timothy Redaelli (tredaelli) - Friday, 22 January 2016, 13:15 GMT
Is this bug still opened?

Loading...