| Bug ID |
9687
|
| Summary |
The automatic updater is impolite
|
| Classification |
Unclassified
|
| Product |
Wireshark
|
| Version |
unspecified
|
| Hardware |
All
|
| OS |
Windows NT
|
| Status |
UNCONFIRMED
|
| Severity |
Trivial
|
| Priority |
Low
|
| Component |
Wireshark
|
| Assignee |
[email protected]
|
| Reporter |
[email protected]
|
Build Information:
Version 1.10.5 (SVNRev 54262 from /trunk-1.10)
Compiled (64-bit) with GTK+ 2.24.14, with Cairo 1.10.2, with Pango 1.30.1, with
GLib 2.34.1, with WinPcap (4_1_3), with libz 1.2.5, without POSIX capabilities,
without libnl, with SMI 0.4.8, with c-ares 1.9.1, with Lua 5.1, without Python,
with GnuTLS 2.12.18, with Gcrypt 1.4.6, without Kerberos, with GeoIP, with
PortAudio V19-devel (built Dec 19 2013), with AirPcap.
Running on 64-bit Windows 8, build 9200, with WinPcap version 4.1.3 (packet.dll
version 4.1.0.2980), based on libpcap version 1.0 branch 1_0_rel0b (20091008),
GnuTLS 2.12.18, Gcrypt 1.4.6, without AirPcap.
Intel(R) Core(TM) i7-4770K CPU @ 3.50GHz, with 16322MB of physical memory.
Built using Microsoft Visual C++ 10.0 build 40219
--
The automatic updater is impolite.
First it asks whether to update. If the answer is affirmative, it starts
downloading the update. Closing Wireshark during the download will abort it and
discard the partially downloaded file, all without any confirmation prompt.
Once the download is complete, Wireshark asks whether it should update itself.
If the user agrees, the next UI action (on Windows) is an elevation prompt, and
if that succeeds, a brusque demand that the user close Wireshark to let the
update proceed.
Other than declining the immediate update and digging the download out of
wherever the downloader put it (if it even puts it anywhere if an immediate
installation is declined), there is no way for the user to avoid the message
box accusing him or her of not having closed Wireshark yet.
I would like to see that changed in one of three ways:
1. The "close Wireshark now" message could be made more friendly.
2. The download could continue even if the main window is closed, followed by
the original Wireshark process exiting just after starting the update
installation.
3. The update installer could ask whether *it* should close Wireshark, taking
that weight off the user's shoulders.
Yes, "trivial" does not accurately describe just how unimportant this bug
report is. But still, I feel bad whenever I install an update and get blamed
for something I had little option to avoid.
You are receiving this mail because:
- You are watching all bug changes.