apport sends crashfiles to nirvana

[Majestyx]

apport came up whit a crash notice, klick on: submit the bug ....
nothing happens (more)

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: apport 2.20.7-0ubuntu3.7
ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13
Uname: Linux 4.13.0-21-generic x86_64
ApportLog:
 ERROR: apport (pid 1452) Tue Jan 9 18:08:24 2018: called for pid 1449, signal 6, core limit 0, dump mode 1
 ERROR: apport (pid 1452) Tue Jan 9 18:08:24 2018: executable: /usr/lib/android-sdk/platform-tools/adb (command line "adb -P 5037 fork-server server --reply-fd 4")
 ERROR: apport (pid 1452) Tue Jan 9 18:08:24 2018: is_closing_session(): no DBUS_SESSION_BUS_ADDRESS in environment
 ERROR: apport (pid 1452) Tue Jan 9 18:08:24 2018: wrote report /var/crash/_usr_lib_android-sdk_platform-tools_adb.0.crash
ApportVersion: 2.20.7-0ubuntu3.7
Architecture: amd64
CrashReports:
 600:113:121:0:2018-01-09 18:10:13.071120741 +0100:2018-01-06 18:08:50.832819680 +0100:/var/crash/_usr_lib_android-sdk_platform-tools_adb.0.uploaded
 644:0:121:0:2018-01-09 18:10:12.011104680 +0100:2018-01-09 18:10:12.011104680 +0100:/var/crash/_usr_lib_android-sdk_platform-tools_adb.0.upload
 640:0:121:212568:2018-01-09 18:10:00.466965198 +0100:2018-01-09 18:10:01.466965198 +0100:/var/crash/_usr_lib_android-sdk_platform-tools_adb.0.crash
CurrentDesktop: XFCE
Date: Tue Jan 9 18:15:31 2018
InstallationDate: Installed on 2017-12-10 (30 days ago)
InstallationMedia: Xubuntu 17.10 "Artful Aardvark" - Release amd64 (20171017.1)
PackageArchitecture: all
ProcEnviron:
 LANGUAGE=de_DE
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
SourcePackage: apport
UpgradeStatus: No upgrade log present (probably fresh install)

[Brian Murray (brian-murray)]

Something did happen though and a crash report was sent to errors.ubuntu.com as can confirm by the existence of a .uploaded file in /var/crash/ for the android-sdk crash. Crash reports for stable releases are sent to the Ubuntu Error Tracker and no additional information is required from the crash reporter so we don't bother them with opening a web page displaying the crash.