Bug reports keep popping up on login, not entirely sure why

[John D]

Bug reports pop up on login. There are three or four of them, they occur on all logins, even if I just log out and log in again.

I did rebuild unity from a modified source to suport touch controls through touchegg, so if these are caused by unity, you should ignore them.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: linux-image-3.13.0-20-generic 3.13.0-20.42
ProcVersionSignature: Ubuntu 3.13.0-20.42-generic 3.13.7
Uname: Linux 3.13.0-20-generic x86_64
ApportVersion: 2.13.3-0ubuntu1
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: john 2004 F.... pulseaudio
 /dev/snd/pcmC1D0p: john 2004 F...m pulseaudio
 /dev/snd/controlC0: john 2004 F.... pulseaudio
CurrentDesktop: Unity
Date: Mon Mar 31 14:12:39 2014
EcryptfsInUse: Yes
HibernationDevice: RESUME=UUID=92cd549d-6672-4f29-bf76-c1e39e93812f
InstallationDate: Installed on 2014-03-30 (1 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1)
MachineType: LENOVO 20A7CTO1WW
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-20-generic.efi.signed root=UUID=322273b3-4567-4897-a1a7-3c789fe96d24 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-3.13.0-20-generic N/A
 linux-backports-modules-3.13.0-20-generic N/A
 linux-firmware 1.126
SourcePackage: linux
UpgradeStatus: Upgraded to trusty on 2014-03-31 (0 days ago)
dmi.bios.date: 03/05/2014
dmi.bios.vendor: LENOVO
dmi.bios.version: GRET34WW (1.11 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20A7CTO1WW
dmi.board.vendor: LENOVO
dmi.board.version: SDK0E50512 Std
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: dmi:bvnLENOVO:bvrGRET34WW(1.11):bd03/05/2014:svnLENOVO:pn20A7CTO1WW:pvrThinkPadX1Carbon2nd:rvnLENOVO:rn20A7CTO1WW:rvrSDK0E50512Std:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 20A7CTO1WW
dmi.product.version: ThinkPad X1 Carbon 2nd
dmi.sys.vendor: LENOVO

[Brad Figg (brad-figg)]

This change was made by a bot.

[penalvch (penalvch)]

John D, thank you for reporting this and helping make Ubuntu better. However, your crash report is missing. Please follow these instructions to have apport report a new bug about your crash that can be dealt with by the automatic retracer. First, execute at a terminal:
cd /var/crash && sudo rm * ; sudo apt-get update && sudo apt-get -y upgrade && sudo service apport start force_start=1

If you are running the Ubuntu Stable Release you might need to enable apport in /etc/default/apport and restart.

Now reproduce the crash, then open your file manager, navigate to your /var/crash directory and open the crash report you wish to submit.
If this fails you will have to open a terminal and file your report with 'ubuntu-bug /var/crash/_my_crash_report.crash' where _my_crash_report.crash is the crash you would like to report. If you get an error that you aren't allowed to access this report you will have to file it with 'sudo ubuntu-bug /var/crash/_my_crash_report.crash'. If you run the command against the crash report and a window pops up asking you to report this, but then never opens a new report, you would be affected by https://bugs.launchpad.net/ubuntu/+source/apport/+bug/994921 . In order to WORKAROUND this, one would need to open the following file via a command line:
gksudo gedit /etc/apport/crashdb.conf

and comment out the line:
'problem_types': ['Bug', 'Package'],

by changing it to:
# 'problem_types': ['Bug', 'Package'],

Save, close, and try to file the crash report again via:
ubuntu-bug /var/crash/_my_crash_report.crash

I'm closing this bug report since the process outlined above will automatically open a new bug report which can then dealt with more efficiently.

Thank you for your understanding.

Helpful bug reporting tips:
https://wiki.ubuntu.com/ReportingBugs