HTTP Error 502: Bad Gateway when reporting a bug with apport
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Apport |
New
|
Undecided
|
Unassigned | ||
| apport (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned | ||
Bug Description
When trying to report a bug using Apport on Raring, I get a "HTTP Error 502: Bad Gateway" error even though I am properly connected to the internet at the time (browsing web pages and sending/receiving email).
My connection to the Internet is via an ADSL router, IP address and gateway
Steps to reproduce:
1. Open a terminal
2. Type ubuntu-bug apport
3. Apport starts and collects data
Expected bahaviour:
Apport opens a browser window as normal to enable the user to complete the bug report.
Actual behaviour:
Apport shows the error message in the attached screenshot.
For information, here is the output I get regarding my network connection:
$ ifconfig wlan0
wlan0 Link encap:Ethernet HWaddr 00:24:d7:c7:b9:94
inet addr:192.168.0.3 Bcast:192.168.0.255 Mask:255.255.255.0
inet6 addr: fe80::224:
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:1071072 errors:0 dropped:0 overruns:0 frame:0
TX packets:360755 errors:0 dropped:0 overruns:0 carrier:0
RX bytes:704047081 (704.0 MB) TX bytes:92144451 (92.1 MB)
$ route
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
default 192.168.0.1 0.0.0.0 UG 0 0 0 wlan0
link-local * 255.255.0.0 U 1000 0 0 wlan0
192.168.0.0 * 255.255.255.0 U 9 0 0 wlan0
| Bruno Girin (brunogirin) wrote | #1 |
| Launchpad Janitor (janitor) wrote | #2 |
| Changed in ubuntu: | |
| status: | New → Confirmed |
| affects: | ubuntu → apport (Ubuntu) |
Status changed to 'Confirmed' because the bug affects multiple users.