Apport automatically starter opening Google Chrome

Bug #1442875 reported by karolus
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
systemd (Ubuntu)
New
Undecided
Unassigned

Bug Description

I launched Google Chrome and Apport started automatically

ProblemType: Crash
DistroRelease: Ubuntu 15.04
Package: systemd 219-6ubuntu1
ProcVersionSignature: Ubuntu 3.19.0-12.12-generic 3.19.3
Uname: Linux 3.19.0-12-generic i686
ApportVersion: 2.17-0ubuntu1
Architecture: i386
CrashCounter: 1
Date: Sat Apr 11 11:39:26 2015
ExecutablePath: /lib/systemd/systemd
InstallationDate: Installed on 2015-04-06 (4 days ago)
InstallationMedia: Ubuntu-MATE 15.04 "Vivid Vervet" - Beta i386 (20150326)
MachineType: TOSHIBA TOSHIBA NB100
ProcCmdline: /sbin/init splash
ProcEnviron:
 TERM=linux
 PATH=(custom, no user)
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-12-generic root=UUID=a18366f0-b60f-4919-b961-1bef60a8a542 ro quiet splash vt.handoff=7
SegvAnalysis: Skipped: missing required field "Disassembly"
Signal: 11
SourcePackage: systemd
UdevLog: Error: [Errno 2] File o directory non esistente: '/var/log/udev'
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

dmi.bios.date: 02/17/2009
dmi.bios.vendor: INSYDE
dmi.bios.version: 1.90
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: Portable PC
dmi.board.vendor: TOSHIBA
dmi.board.version: Base Board Version
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Insyde
dmi.chassis.version: None
dmi.modalias: dmi:bvnINSYDE:bvr1.90:bd02/17/2009:svnTOSHIBA:pnTOSHIBANB100:pvrPLL10E-00S03QIT:rvnTOSHIBA:rnPortablePC:rvrBaseBoardVersion:cvnInsyde:ct10:cvrNone:
dmi.product.name: TOSHIBA NB100
dmi.product.version: PLL10E-00S03QIT
dmi.sys.vendor: TOSHIBA

Revision history for this message
karolus (prof-carlobetta) wrote :
Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1441446, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.

information type: Private → Public
tags: removed: need-i386-retrace
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.