can't report crash in /var/crash with ubuntu-bug, "Network problem"

Bug #2033653 reported by Jonathan Kamens
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Launchpad itself
Expired
Undecided
Unassigned

Bug Description

Because of bug #2033652 I was trying to report a gdb crash from /var/crash. It spent a long time uploading data, then and then popped up an error dialog:

Network problem
Cannot connect to crash database, please check your internet connection.
HTTP Error ???: Bad gateway

(I don't remember the error code exactly)

I tried again and had a slightly different result: "HTTP Error 503: Service Unavailable" instead of "Bad gateway".

So... First gimp crashes (bug #2031907). I can't report the crash properly for it because gimp is wired to catch segfaults instead of letting the OS handle them. Then gdb crashes (bug #2033652) while I'm trying to debug the gimp issue. And then I can't report the gdb crash properly because of THIS issue.

Jolly good all around.

ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: apport 2.27.0-0ubuntu2
ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5
Uname: Linux 6.3.0-7-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportLog:
 INFO: apport (pid 639437) 2023-08-31 09:09:01,286: called for pid 639344, signal 11, core limit 0, dump mode 1
 INFO: apport (pid 639437) 2023-08-31 09:09:01,288: executable: /usr/bin/gdb (command line "gdb /usr/bin/gimp")
 INFO: apport (pid 639437) 2023-08-31 09:09:26,678: wrote report /var/crash/_usr_bin_gdb.1000.crash
ApportVersion: 2.27.0-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Thu Aug 31 09:19:25 2023
InstallationDate: Installed on 2019-01-02 (1702 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3)
PackageArchitecture: all
RebootRequiredPkgs: Error: path contained symlinks.
SourcePackage: apport
UpgradeStatus: Upgraded to mantic on 2023-05-20 (103 days ago)

Revision history for this message
Jonathan Kamens (jik) wrote :
Revision history for this message
Benjamin Drung (bdrung) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. Running into a series of bugs isn't the user experience to be desired.

The HTTP error Bad gateway should be error code 502. Both error codes 502 and 503 indicate a problem on the server side. So this is not a bug of the Apport client code, but the Launchpad server. So I am re-assigning it to launchpad.

affects: apport (Ubuntu) → launchpad
Revision history for this message
Guruprasad (lgp171188) wrote :

Hi Jonathan, I am sorry that you were unable to submit bug reports due to what appears like issue with Launchpad. Since it has been a few days since you reported the issue, can you retry and let us know if you still run into the same issue? Also, if you see any errors, can you share the full error message?

Changed in launchpad:
status: New → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for Launchpad itself because there has been no activity for 60 days.]

Changed in launchpad:
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.