Comment # 6
on bug 11702
from Jim Young
Hello Carsten,
I always simply edit the preferences file directly to enable/disable the debug
console and set the error level. I suspect there is no GUI control in the
Preferences dialog because this is a pair of options that is rarely used or
recommended for most users.
In Windows to copy the output from the Wireshark Debug Console window or
Windows cmd shell you have click on the widget in the upper left corner of the
window, select Edit and then Mark. After marking the desired text you press
"Enter" to to save the marked text to the Windows clipboard.
Contrary to my earlier statement "I do not recall seeing these messages clocked
out before today", this particular issue has in fact existed for a quite some
time. I see the behavior as far back as the Qt Wireshark 1.99.0
(v1.99.0-2-g9033f13 from master). The Welcome screen for Qt based Version
1.99.0 has a different look and feel than the current Qt based Welcome screen.
In the V1.99.0 you only need to click on the "Open a recent capture file"
button and then click on the "Capture live packets from your network" button to
trigger the once-per-second messages in the console window; you do not have to
open a file. FWIW: I am running Windows 8.1 and I see the issue on both 32bit
and 64bit versions.
In hindsight this issue explains some unexplained crashes I've occasionally
experienced when running Qt based Wireshark on Windows. I primarily use OS X
systems for analysis and capture and secondarily use Windows for certain types
of Wireshark or network testing scenarios. When testing on Windows I will
often have two copies of Wireshark up and running concurrently with the first
copy open on the Welcome screen just to have the real time spark line graphs
visible for the duration of the testing while I am capture and do analysis in
the second copy. Because I never open any files in the first copy it will
often open for days with out any issues.
You are receiving this mail because:
- You are watching all bug changes.
