xournal crashed with SIGSEGV in memset()

Bug #226942 reported by Josh Lee
18
This bug affects 3 people
Affects Status Importance Assigned to Milestone
xournal (Ubuntu)
Fix Released
Medium
Unassigned

Bug Description

Binary package hint: xournal

Whenever I try to draw anything (with XInput turned on), Xournal consumes massive amounts of memory and then crashes.

ProblemType: Crash
Architecture: i386
CrashCounter: 1
Date: Mon May 5 11:29:23 2008
DistroRelease: Ubuntu 8.04
ExecutablePath: /usr/bin/xournal
NonfreeKernelModules: nvidia
Package: xournal 0.4.1-0ubuntu1
PackageArchitecture: i386
ProcCmdline: xournal
ProcEnviron:
 SHELL=/bin/bash
 PATH=/home/username/bin:/home/username/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=en_US.UTF-8
Signal: 11
SourcePackage: xournal
StacktraceTop:
 memset () from /lib/tls/i686/cmov/libc.so.6
 art_uta_new () from /usr/lib/libart_lgpl_2.so.2
 art_uta_new_coords () from /usr/lib/libart_lgpl_2.so.2
 art_uta_from_vpath () from /usr/lib/libart_lgpl_2.so.2
 art_uta_from_svp () from /usr/lib/libart_lgpl_2.so.2
Title: xournal crashed with SIGSEGV in memset()
Uname: Linux 2.6.24-17-generic i686
UserGroups: adm admin audio cdrom dialout dip floppy fuse lpadmin netdev plugdev powerdev pulse sambashare scanner video

Tags: apport-crash

Related branches

Revision history for this message
Josh Lee (jleedev) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:memset () from /lib/tls/i686/cmov/libc.so.6
art_uta_new (x0=-33781, y0=-13806, x1=<value optimized out>,
art_uta_new_coords (x0=-33781, y0=466831788,
art_uta_from_vpath (vec=0x82c7350) at art_uta_vpath.c:307
art_uta_from_svp (svp=0x82c7000) at art_uta_svp.c:51

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
Changed in xournal:
importance: Undecided → Medium
Revision history for this message
Denis Auroux (auroux) wrote :

This is getting so ridiculous, and I'm so upset with Ubuntu's release cycle. The patch has been available for 2 months, and the new release including it has been around for almost as long. Xournal 0.4.1 is completely broken with Hardy because of incompatible changes in X.org, and nobody seems to be willing to update the package to 0.4.2.1...

Feature freeze shouldn't mean bugfix freeze.

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

This bug was fixed in the package xournal - 0.4.2.1-0ubuntu1

---------------
xournal (0.4.2.1-0ubuntu1) intrepid; urgency=low

  * New upstream release:
    - allow XInput and core events in reverse order, LP: #184996, #234240.
    - also fixes LP: #226942.

 -- Vincenzo Ciancia <email address hidden> Sun, 18 May 2008 00:15:35 +0200

Changed in xournal:
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