evince segfaults
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Geis |
Fix Released
|
Undecided
|
Stephen M. Webb | ||
utouch-geis (Ubuntu) |
Fix Released
|
Undecided
|
Stephen M. Webb |
Bug Description
[ 6168.402557] evince[7514] general protection ip:7fe846a7439c sp:7fffc136e4f0 error:0 in libutouch-
Evince crashes every time it starts:
$ evince
Segmentation fault
$
(Precice Pangolin)
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: evince 3.2.1-0ubuntu2
ProcVersionSign
Uname: Linux 3.1.0-999-generic x86_64
ApportVersion: 1.24-0ubuntu1
Architecture: amd64
Date: Fri Oct 21 12:45:37 2011
KernLog:
Oct 21 09:40:07 cave kernel: [ 0.000000] Command line: BOOT_IMAGE=
Oct 21 09:40:07 cave kernel: [ 0.000000] Kernel command line: BOOT_IMAGE=
Oct 21 09:40:07 cave kernel: [ 0.004049] Security Framework initialized
Oct 21 09:40:07 cave kernel: [ 0.004059] AppArmor: AppArmor disabled by boot time parameter
Oct 21 09:40:07 cave kernel: [ 0.829118] type=2000 audit(131918275
SourcePackage: evince
UpgradeStatus: No upgrade log present (probably fresh install)
Related branches
- Chase Douglas (community): Approve
-
Diff: 88 lines (+27/-13)3 files modifiedlibs/geis-dbus/geis_dbus_dispatcher.c (+5/-0)
libutouch-geis/backend/dbus/geis_dbus_locator.c (+8/-0)
libutouch-geis/geis.c (+14/-13)
Changed in utouch-geis (Ubuntu): | |
assignee: | Chase Douglas (chasedouglas) → Stephen M. Webb (bregma) |
Changed in utouch-geis: | |
status: | New → Triaged |
assignee: | nobody → Stephen M. Webb (bregma) |
milestone: | none → utouch-geis-2.2.1 |
Changed in utouch-geis: | |
status: | Triaged → In Progress |
Changed in utouch-geis (Ubuntu): | |
status: | Confirmed → In Progress |
Changed in utouch-geis: | |
status: | In Progress → Fix Committed |
Changed in utouch-geis: | |
status: | Fix Committed → Fix Released |
Thank you for taking the time to report this bug and helping to make Ubuntu better. Please try to obtain a backtrace following the instructions at http:// wiki.ubuntu. com/DebuggingPr ogramCrash and upload the backtrace (as an attachment) to the bug report. This will greatly help us in tracking down your problem.