Ubuntu
cairo package

EOG crash - Aborted (core dumped)

Bug #1179735 reported by florin
158
This bug affects 31 people
Affects Status Importance Assigned to Milestone
cairo
New
Undecided
Unassigned
cairo (Ubuntu)
Fix Released
High
Unassigned
Precise
Won't Fix
Low
Unassigned

Bug Description

Many times I try to watch large jpg images, my eog crashes. I started it in terminal and it seems the exit message is "Aborted (core dumped)".

The images are 5-6-7 MB and I am forced to see them in Shotwell because eog is impossible to use. I have no idea what the first line means, but it is always there when I start eog.

eog DSC07456.JPG
eog: /build/buildd/cairo-1.12.14/src/cairo-mempool.c:160: get_buddy: Assertion `offset + (1 << bits) <= pool->num_blocks' failed.
Aborted (core dumped)

I run a fresh install of Ubuntu 13.04, all updates to date:
uname -a
Linux florin-Satellite-C650 3.8.0-19-generic #30-Ubuntu SMP Wed May 1 16:35:23 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux

ProblemType: Bug
DistroRelease: Ubuntu 13.04
Package: eog 3.6.2-0ubuntu1
ProcVersionSignature: Ubuntu 3.8.0-19.30-generic 3.8.8
Uname: Linux 3.8.0-19-generic x86_64
ApportVersion: 2.9.2-0ubuntu8
Architecture: amd64
Date: Tue May 14 03:25:52 2013
InstallationDate: Installed on 2013-04-25 (18 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
MarkForUpload: True
SourcePackage: eog
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
florin (florin-arjocu) wrote :
Revision history for this message
florin (florin-arjocu) wrote :

It seems to be the same problem this guy has: https://lists.ubuntu.com/archives/ubuntu-users/2013-February/267495.html

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

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

Changed in eog (Ubuntu):
status: New → Confirmed
Revision history for this message
Xavi Ivars (xavi-ivars) wrote :

I've got exactly the same problem, and I get the same message.

eog DSC_0599.JPG
eog: /build/buildd/cairo-1.12.14/src/cairo-mempool.c:160: get_buddy: L’asserció «offset + (1 << bits) <= pool->num_blocks» ha fallat.
Avortat (bolcat de la imatge del nucli)

Revision history for this message
Xavi Ivars (xavi-ivars) wrote :

It looks like it was already reported upstream,

http://lists.cairographics.org/archives/cairo/2013-March/024155.html

and it has been fixed

http://cgit.freedesktop.org/cairo/commit/src/cairo-mempool.c?id=01a8bf01c6508a4fea8d40371c3049e7a2f7908a

so I gess now we just need to wait for the new version to be built

Sebastien Bacher (seb128)
affects: eog (Ubuntu) → cairo (Ubuntu)
Changed in cairo (Ubuntu):
importance: Undecided → High
status: Confirmed → Fix Committed
Revision history for this message
florin (florin-arjocu) wrote :

Good that the bugfix will be soon released. It is a major bug from my point of view, I cannot watch images with the default application.

Revision history for this message
florin (florin-arjocu) wrote :

Not to make people hurry, but is there any knowledge on when the fix will be pushed? Opening large jpg files makes the computer unresponsive, there is no fun in watching photos...

Revision history for this message
florin (florin-arjocu) wrote :

Allowed proposed updates and updated. I still get errors but at least it does not hang up my system when they occur. Just got one error:

eog: /build/buildd/cairo-1.12.14/src/cairo-mempool.c:160: get_buddy: Assertion `offset + (1 << bits) <= pool->num_blocks' failed.
Aborted (core dumped)

Revision history for this message
ADHDTux (adhdtux) wrote :

Situation unchanged as of today...

Revision history for this message
Juan Simón (simonbcn) wrote :

The problem stills persist. Why an bug so important like this isn't fixed yet?

Revision history for this message
florin (florin-arjocu) wrote :

True, it is still there. The only way to conveniently watch large jpg files on my system is to open them with Shotwell Photo Viewer.

Revision history for this message
Andres Gomez (Tanty) (tanty) wrote :

Same here with raring

Revision history for this message
madbiologist (me-again) wrote :

libcairo2 1.12.16 is now available in saucy-proposed and it should fix this bug. Please test and let us know if this bug is fixed. For instructions on how to enable and use -proposed, see https://wiki.ubuntu.com/Testing/EnableProposed

Revision history for this message
Sebastien Bacher (seb128) wrote :

don't enable proposed on the unstable serie, it's not made for users but just for automated testing, just wait for it to hit saucy

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

This bug was fixed in the package cairo - 1.12.16-0ubuntu1

---------------
cairo (1.12.16-0ubuntu1) saucy; urgency=low

  * New upstream version:
    - should fix eog segfaulting on some images (lp: #1179735)
  * debian/libcairo-gobject2.symbols:
    - updated to new version
 -- Sebastien Bacher <email address hidden> Tue, 27 Aug 2013 16:31:23 +0200

Changed in cairo (Ubuntu):
status: Fix Committed → Fix Released
Revision history for this message
Juan Simón (simonbcn) wrote :

urgency=low!? A crash bug of several image applications: eog, gthumb,...?

Saucy is unreleased. Now the released version is Raring. Do you have planned to fix it in this version?

Revision history for this message
Sebastien Bacher (seb128) wrote :

> urgency=low!?

that field is not used in Ubuntu, it's coming from Debian where it's used in Debian for unstable to testing migration delay, in Ubuntu things hit the archive when they are built without delay

Sebastien Bacher (seb128)
Changed in cairo (Ubuntu Precise):
importance: Undecided → Low
status: New → Triaged
Revision history for this message
Steve Langasek (vorlon) wrote :

The Precise Pangolin has reached end of life, so this bug will not be fixed for that release

Changed in cairo (Ubuntu Precise):
status: Triaged → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.