Can't Copy Crash Report Details to Clipboard

Bug #1273752 reported by Lonnie Lee Best on 2014-01-28
This bug affects 18 people
Affects Status Importance Assigned to Milestone
apport (Ubuntu)
update-notifier (Ubuntu)

Bug Description

Often times, after receiving a crash report, if I click the "Continue" button it doesn't launch the browser for me to submit my crash to

Because of this, I'd always like to copy the crash report to my clipboard before clicking the continue button, so that I can manually provide this information into a bug report to

However, this option is not available.

More over, there is absolutely *no way* to copy any text from this crash report's dialog window!

1) You cannot ctrl-a to select all.
2) Ctrl-c doesn't copy anything
3) Right-clicking doesn't produce a context menu where you can select "Copy".

This is an unfinished design. You should always give the user the ability to copy any text displayed in the UI.

Next to the "Show/Hide details" button, I suggest adding a "Copy to Clipboard" button. If not this, please offer some way to achieve this from the GUI.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: apport-gtk 2.13.2-0ubuntu2
ProcVersionSignature: Ubuntu 3.13.0-5.20-generic 3.13.0
Uname: Linux 3.13.0-5-generic x86_64
NonfreeKernelModules: wl

ApportVersion: 2.13.2-0ubuntu2
Architecture: amd64
CurrentDesktop: Unity
Date: Tue Jan 28 10:21:00 2014
InstallationDate: Installed on 2013-10-07 (113 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
PackageArchitecture: all
SourcePackage: apport
UpgradeStatus: Upgraded to trusty on 2014-01-08 (19 days ago)

description: updated

Here's a screen shot of a crash report that I was unable to copy to my clipboard:

Where are these crash reports kept on the file system? The GUI allows no way to copy the report. Plus, you can't even maximize the windows so that you might at least do a screenshot of the entire report.

This is the kind of crap I'd expect from M$.

Jordan Bowman (jordanbowman) wrote :

I vehemently agree. This is most definitely an egregious design flaw. As even a neophyte developer, when I encounter this sort of thing it makes me smack my forehead. I understand that nobody's perfect and we can't write bug-free software, but I can't count the number of times I've tried to simply copy/paste ONE line from a crash report for a quick Google only to be reminded it isn't possible, let alone the entire report - which is exactly what a developer wants from you when trying to help solve an issue. PLEASE add this very basic and intuitive functionality!

tags: added: utopic
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in apport (Ubuntu):
status: New → Confirmed
Guntbert Reiter (guntbert) wrote :

jordanbowman, why don't you add yourself to the "affects me too" list?

Jordan Bowman (jordanbowman) wrote :

guntbert, because I didn't know it existed until you pointed it out and I went and found it ;)

Changed in apport (Ubuntu):
importance: Undecided → Low
importance: Low → Medium
tags: added: vivid
Ola Asfalt (3tub1410) wrote :

@Lonnie Lee Best #3:

The crash report is stored in:


as a .crash file. When sent a .upload and .uploaded file is added.

It includes a CoreDump: base64 field that can be quite huge though.

Here's another example:

Remmina has been crashing like crazy. When I send this report it does not pull up for me to detail what was happening when the crash happened. I have no clue whether the bug report is getting sent to or not.

Plus, getting back to the top of this bug, you can't copy any of the information details from this dialog. I'd expect this kind of crap from Microsoft Windows, but not Ubuntu!

Please add an option to this dialog so I can *copy details to clipboard*, so that I can file an explicit bug report after the the " Send error report" feature fails to launch

I never want to see any text on my screen that I cannot copy and paste! This is UI 101 stuff.

@Ola Asfalt: Thanks for telling me where these details can be copied.

Never the less, (though) however, the purpose of this bug report is so that a normal user of Ubuntu doesn't have to be told by Ola Asfalt in a bug report, where to find the details of a crash.

It should be copy and paste. Don't show a user text he cannot copy and paste. This a golden rule that should be followed.

Same problem on Xenial, Yakkety and Zesty ...

remember: to easily view crash report you may add your userid to group whoopsie:
sudo adduser your-userid whoopsie

tags: added: xenial yakkety zesty

Same problem with other system windows. see screenshot.
I know, I can copy same info from terminal using 'last' command...

also in ubuntu 17,10 artful

mgsloan (mgsloan) wrote :

Agreed that this should really be resolved. It is particularly problematic for packages that are not in ubuntu repos - when submitting bug reports to 3rd parties.

It would also be far easier to check if the report is leaking any secrets if you could easily open it in a text editor and use ctrl+f. I suppose that wouldn't handle the coredump bits, but eh.

This bug was submitted 4 years ago and still applies to each additional Ubuntu release.

What is the next step that could actually contribute progress on this issue?

To me it is kind of ironic that a bug regarding the bug reporting system itself could go so long unfixed.

tags: added: artful bionic

Still this problem in Ubuntu 18.10 Cosmic

spm2011 (spm2011) on 2018-12-14
Changed in apport:
status: New → Confirmed
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Duplicates of this bug

Other bug subscribers