Revision history [back]

Anything I can do to fix?

Look at the code and the developer mode errors, figure out what's wrong with the HTML, and fix the code that generates it.

What you can do to try to have somebody else fix it would be to file a bug report on the Wireshark issues list; it occurs with multiple browsers (I don't get a white screen with Safari or Chrome on macOS, but I don't get a map, either, just a gray display with a line that repeatedly says "North Fork Ninnescan River" in several places without showing me a river, and a green circle in the middle with a "3" inside it), so it's probably a bug.

That means it's not something you're doing wrong or that you can fix without doing Wireshark debugging and development.

Anything I can do to fix?

Look at the code and the developer mode errors, figure out what's wrong with the HTML, and fix the code that generates it.

What you can do to try to have somebody else fix it would be to file a bug report on the Wireshark issues list; it occurs with multiple browsers (I don't get a white screen with Safari or Chrome on macOS, but I don't get a map, either, just a gray display with a line that repeatedly says "North Fork Ninnescan Ninnescah River" in several places without showing me a river, and a green circle in the middle with a "3" inside it), so it's probably a bug.

That means it's not something you're doing wrong or that you can fix without doing Wireshark debugging and development.

(The Ninnescah River is, according to Open Street Map, in Kansas; is this another one of those "I can't geolocate this, so I'm going to dump you close to the geographic middle of the continental US" things, but not at the home of that unlucky couple who kept getting police showing up as a result of geolocating?)

Anything I can do to fix?

Look at the code and the developer mode errors, figure out what's wrong with the HTML, and fix the code that generates it.

What you can do to try to have somebody else fix it would be to file a bug report on the Wireshark issues list; it occurs with multiple browsers (I don't get a white screen with Safari or Chrome on macOS, but I don't get a map, either, just a gray display with a line that repeatedly says "North Fork Ninnescah River" in several places without showing me a river, and a green circle in the middle with a "3" inside it), so it's probably a bug.

That means it's not something you're doing wrong or that you can fix without doing Wireshark debugging and development.

(The Ninnescah River is, according to Open Street Map, in Kansas; is this another one of those "I can't geolocate this, so I'm going to dump you close to the geographic middle of the continental US" things, but not at the home of that unlucky couple who kept getting police showing up as a result of geolocating?)

Update: it's in the middle of the Cheney Reservoir, which is why it's gray; if I zoom out sufficiently, I can see labels for Wichita, Dodge City, Salina, etc. against a white background. But this is with the master branch of Wireshark; perhaps there's a bug in 3.4.x or 3.6.x.

Anything I can do to fix?

Look at the code and the developer mode errors, figure out what's wrong with the HTML, and fix the code that generates it.

What you can do to try to have somebody else fix it would be to file a bug report on the Wireshark issues list; it occurs with multiple browsers (I don't get a white screen with Safari or Chrome on macOS, but I don't get a map, either, just a gray display with a line that repeatedly says "North Fork Ninnescah River" in several places without showing me a river, and a green circle in the middle with a "3" inside it), so it's probably a bug.

That means it's not something you're doing wrong or that you can fix without doing Wireshark debugging and development.

(The Ninnescah River is, according to Open Street Map, in Kansas; is this another one of those "I can't geolocate this, so I'm going to dump you close to the geographic middle of the continental US" things, but not at the home of that unlucky couple who kept getting police showing up as a result of geolocating?)

Update: it's in the middle of the Cheney Reservoir, which is why it's gray; if I zoom out sufficiently, I can see labels for Wichita, Dodge City, Salina, etc. against a white background. But this is with the master branch of Wireshark; perhaps there's a bug in 3.4.x or 3.6.x.

Further update: yes, it probably dumped me in the middle of the reservoir because it couldn't find any of the IP addresses. With another capture, pinging some sites I expected would be found, it worked; I copied the file to an Ubuntu 20.04 system and opened it with Firefox, and it worked.

However, if I copied the capture to the Ubuntu system, which provides Wireshark 3.2.3, and open it with 3.2.3, the map doesn't work - it's all white, and it's all white if I copy it back to my Mac and open it with Safari. So it looks like a bug in 3.2.3, and it's probably still in 3.4.8. So please file the bug report.

Anything I can do to fix?

Look at the code and the developer mode errors, figure out what's wrong with the HTML, and fix the code that generates it.

What you can do to try to have somebody else fix it would be to file a bug report on the Wireshark issues list; it occurs with multiple browsers (I don't get a white screen with Safari or Chrome on macOS, but I don't get a map, either, just a gray display with a line that repeatedly says "North Fork Ninnescah River" in several places without showing me a river, and a green circle in the middle with a "3" inside it), so it's probably a bug.

That means it's not something you're doing wrong or that you can fix without doing Wireshark debugging and development.

(The Ninnescah River is, according to Open Street Map, in Kansas; is this another one of those "I can't geolocate this, so I'm going to dump you close to the geographic middle of the continental US" things, but not at the home of that unlucky couple who kept getting police showing up as a result of geolocating?)

Update: it's in the middle of the Cheney Reservoir, which is why it's gray; if I zoom out sufficiently, I can see labels for Wichita, Dodge City, Salina, etc. against a white background. But this is with the master branch of Wireshark; perhaps there's a bug in 3.4.x or 3.6.x.

Further update: yes, it probably dumped me in the middle of the reservoir because it couldn't find any of the IP addresses. With another capture, pinging some sites I expected would be found, it worked; I copied the file to an Ubuntu 20.04 system and opened it with Firefox, and it worked.

However, if I copied the capture to the Ubuntu system, which provides Wireshark 3.2.3, and open it with 3.2.3, the map doesn't work - it's all white, and it's all white if I copy it back to my Mac and open it with Safari. So it looks like a bug in 3.2.3, and it's probably still in 3.4.8. So please file the bug report.

Still further update: see Jaap's answer. This is a bug, but it's a bug in Ubuntu's packaging of Wireshark (which they might have inherited from Debian; I'll check).