compiz-core invalid core dump BFD Warning tmp/apport_core_6ywix5b7 is truncated: expected core file size >= 112926

Bug #1680287 reported by Ralph Gilbert
34
This bug affects 6 people
Affects Status Importance Assigned to Milestone
ubuntu-release-upgrader (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

UPGRADING TO 17.04

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: ubuntu-release-upgrader-core 1:17.04.6
ProcVersionSignature: Ubuntu 4.10.0-15.17-generic 4.10.5
Uname: Linux 4.10.0-15-generic i686
ApportVersion: 2.20.4-0ubuntu3
Architecture: i386
CrashDB: ubuntu
CurrentDesktop: Unity:Unity7
Date: Wed Apr 5 17:56:23 2017
EcryptfsInUse: Yes
InstallationDate: Installed on 2016-08-17 (231 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1)
PackageArchitecture: all
ProcEnviron:
 LANGUAGE=en_US
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: ubuntu-release-upgrader
Symptom: dist-upgrade
UpgradeStatus: No upgrade log present (probably fresh install)
VarLogDistupgradeAptlog:
 Log time: 2017-04-04 11:35:28.806363
 Starting pkgProblemResolver with broken count: 0
 Starting 2 pkgProblemResolver with broken count: 0
 Done
VarLogDistupgradeTermlog:

Revision history for this message
Ralph Gilbert (rhg3) wrote :
Revision history for this message
Ralph Gilbert (rhg3) wrote :

new at this, sorry

Revision history for this message
Brian Murray (brian-murray) wrote :

Could you give some more information about the exact problem you ran into? Based of the title of this bug it sounds like compiz crashed and the core file isn't the size that was expected. This can happen if your system ran out of memory when writing the core dump. If that's the issue then this just happens sometimes and the bug should be invalid.

Changed in ubuntu-release-upgrader (Ubuntu):
status: New → Incomplete
Revision history for this message
Brinstar (brinstar) wrote :

Gives me the same error just after boot to desktop

Revision history for this message
Brinstar (brinstar) wrote :

I have 8gb ram, pretty sure it's not running out unless there is a serious memory leak going on

Revision history for this message
Terry Relph-Knight (tarki) wrote :

I get the same problem (truncated core) every time, a few seconds after I boot 17.04.

Revision history for this message
Brinstar (brinstar) wrote :

How are we supposed to report this if the core dump is getting truncated and apport doesn't let us proceed to send the report?

Revision history for this message
Brinstar (brinstar) wrote :

This happens at boot-up after starting Ubuntu 17.04.

I'm running the official Nvidia driver (340.xx) if that has any impact.

Revision history for this message
Benjamin Wynne (bwynne) wrote :

I have this bug too. First time I checked the message it was just complaining about some out-of-date dependencies and told me to run apt-get update. I did (sorry, didn't record what was installed) but now I get this "truncated core" bug instead.

There is 32GB of RAM available, so I'm very sure it's not running out!

Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for ubuntu-release-upgrader (Ubuntu) because there has been no activity for 60 days.]

Changed in ubuntu-release-upgrader (Ubuntu):
status: Incomplete → Expired
Revision history for this message
Andrew Hershberger (macdrevx) wrote :

Just encountered this after upgrading from 16.04 to 17.10

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.