frescobaldi crashed with SIGSEGV after generating PDF

Bug #1235875 reported by Onno Zweers
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
frescobaldi (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

In Ubuntu 13.10, when I enter a very simple piece of Lilypond code in Frescobaldi and compile it, the PDF is generated successfully but Frescobaldi crashes. I started Frescobaldi from the commandline, and after loading the same .ly file, it crashed again:

onno@onno-Compaq-Mini-110c-1100:~$ frescobaldi
Segmentatiefout (geheugendump gemaakt)

onno@onno-Compaq-Mini-110c-1100:~$ frescobaldi --version
Frescobaldi 2.0.10

onno@onno-Compaq-Mini-110c-1100:~$ lilypond --version
GNU LilyPond 2.16.2

Copyright (c) 1996--2012
  Han-Wen Nienhuys <email address hidden>
  Jan Nieuwenhuizen <email address hidden>
  en anderen.

The Lilypond code:

\score {
  c
}

ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: frescobaldi 2.0.10+ds1-1
ProcVersionSignature: Ubuntu 3.11.0-11.17-generic 3.11.3
Uname: Linux 3.11.0-11-generic i686
NonfreeKernelModules: wl
ApportVersion: 2.12.5-0ubuntu1
Architecture: i386
Date: Sun Oct 6 09:51:34 2013
Disassembly: => 0x1: Cannot access memory at address 0x1
ExecutablePath: /usr/bin/frescobaldi
InstallationDate: Installed on 2013-08-27 (39 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release i386 (20130424)
InterpreterPath: /usr/bin/python2.7
MarkForUpload: True
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/frescobaldi
ProcEnviron:
 LANGUAGE=nl_NL
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=nl_NL.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x1: Cannot access memory at address 0x1
 PC (0x00000001) not located in a known VMA region (needed executable region)!
 Stack memory exhausted (SP below stack segment)
SegvReason: executing NULL VMA
Signal: 11
SourcePackage: frescobaldi
Stacktrace:
 #0 0x00000001 in ?? ()
 No symbol table info available.
StacktraceTop: ?? ()
Title: frescobaldi crashed with SIGSEGV
UpgradeStatus: Upgraded to saucy on 2013-09-29 (6 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
Onno Zweers (onnozweers) wrote :
information type: Private → Public
Revision history for this message
Apport retracing service (apport) wrote :

Stacktrace:
 #0 0x00000001 in ?? ()
 No symbol table info available.
StacktraceSource: #0 0x00000001 in ?? ()
StacktraceTop: ?? ()

Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
tags: added: apport-failed-retrace
tags: removed: need-i386-retrace
Revision history for this message
Onno Zweers (onnozweers) wrote :

Additional info: it happens whenever a PDF is loaded in the PDF view pane.
The PDF that was generated seems fine; I can load it in Evince from the file manager and it looks good. However, Evince does display a warning on the command line:

onno@ubuntu-vm:~$ evince test.pdf
(evince:15062): EvinceDocument-CRITICAL **: ev_document_get_n_pages:
assertion 'EV_IS_DOCUMENT (document)' failed

Not sure if it is relevant.
Okular also displays the PDF well.

Revision history for this message
Onno Zweers (onnozweers) wrote :

This issue has apparently been fixed in the official release of 13.10. Thanks, whoever did that!

Changed in frescobaldi (Ubuntu):
status: New → Fix Released
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.