Ubuntu 14.04 3.13.6-031306-generic #201403070154 SMP Fri Mar 7 07:14:26
UTC 2014 i686 i686 i686 GNU/Linux.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-font-viewer in Ubuntu.
https://bugs.launchpad.net/bugs/1052164

Title:
  gnome-font-viewer crashed with SIGSEGV in ft_mem_qalloc()

Status in “gnome-font-viewer” package in Ubuntu:
  Confirmed

Bug description:
  in use

  ProblemType: Crash
  DistroRelease: Ubuntu 12.10
  Package: gnome-font-viewer 3.5.91-0ubuntu1
  ProcVersionSignature: Ubuntu 3.5.0-14.19-generic 3.5.3
  Uname: Linux 3.5.0-14-generic x86_64
  ApportVersion: 2.5.1-0ubuntu7
  Architecture: amd64
  Date: Mon Sep 17 22:06:07 2012
  Disassembly: => 0xc1: Cannot access memory at address 0xc1
  ExecutablePath: /usr/bin/gnome-font-viewer
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120910)
  ProcCmdline: gnome-font-viewer
  SegvAnalysis:
   Segfault happened at: 0xc1:  Cannot access memory at address 0xc1
   PC (0x000000c1) not located in a known VMA region (needed executable region)!
   Stack memory exhausted (SP below stack segment)
  SegvReason: executing NULL VMA
  Signal: 11
  SourcePackage: gnome-font-viewer
  StacktraceTop:
   ?? ()
   ft_mem_qalloc () from /usr/lib/x86_64-linux-gnu/libfreetype.so.6
   ft_mem_alloc () from /usr/lib/x86_64-linux-gnu/libfreetype.so.6
   FT_Stream_New () from /usr/lib/x86_64-linux-gnu/libfreetype.so.6
   FT_Open_Face () from /usr/lib/x86_64-linux-gnu/libfreetype.so.6
  Title: gnome-font-viewer crashed with SIGSEGV in ft_mem_qalloc()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-font-viewer/+bug/1052164/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to     : [email protected]
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to