crash in evince and eog when using trusted X forwarding

Bug #1266144 reported by Martin Uecker
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
geis (Ubuntu)
New
Undecided
Unassigned

Bug Description

eog and evince crash in libgeis1 when started using a un-trusted X connection (ForwardX11Trusted no in .ssh/config)

(gdb) run
Starting program: /usr/bin/eog
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x7fffebc32700 (LWP 29920)]
[New Thread 0x7fffeb225700 (LWP 29921)]
[New Thread 0x7fffeaa24700 (LWP 29923)]
[New Thread 0x7fffe9d58700 (LWP 29924)]

Program received signal SIGSEGV, Segmentation fault.
0x00007ffff1d87e10 in ?? () from /usr/lib/x86_64-linux-gnu/libgeis.so.1
(gdb) bt
#0 0x00007ffff1d87e10 in ?? () from /usr/lib/x86_64-linux-gnu/libgeis.so.1
#1 0x00007ffff1d898b6 in geis_filter_new () from /usr/lib/x86_64-linux-gnu/libgeis.so.1
#2 0x00007ffff654741d in ?? () from /usr/lib/x86_64-linux-gnu/libgrip.so.0
#3 0x00007ffff6547927 in ?? () from /usr/lib/x86_64-linux-gnu/libgrip.so.0
#4 0x00007ffff5ffa39c in ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
#5 0x00007ffff46fc188 in g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#6 0x00007ffff470db1d in ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#7 0x00007ffff47154f9 in g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#8 0x00007ffff4715ae2 in g_signal_emit () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#9 0x00007ffff611b794 in ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
#10 0x00007ffff5ffa22e in gtk_main_do_event () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
#11 0x00007ffff5c26fb2 in ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
#12 0x00007ffff44333b6 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#13 0x00007ffff4433708 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#14 0x00007ffff44337ac in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#15 0x00007ffff56eda8c in g_application_run () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
#16 0x000000000041e530 in main (argc=1, argv=0x7fffffffe658) at main.c:187

ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: libgeis1 2.2.16+13.10.20130919.4-0ubuntu1
ProcVersionSignature: Ubuntu 3.11.0-15.23-generic 3.11.10
Uname: Linux 3.11.0-15-generic x86_64
ApportVersion: 2.12.5-0ubuntu2.2
Architecture: amd64
Date: Sat Jan 4 18:20:39 2014
InstallationDate: Installed on 2012-04-26 (618 days ago)
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425)
LsInput: Error: command ['pkexec', 'lsinput'] failed with exit code 127: Cannot run program lsinput: No such file or directory
MachineType: System76, Inc. Lemur Ultra
MarkForUpload: True
MtDevices: SynPS/2 Synaptics TouchPad: /dev/input/event9
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-15-generic root=UUID=96551326-e461-4071-ab9c-0e81ad7015d7 ro quiet splash acpi_os_name=Linux acpi_osi= vt.handoff=7
SourcePackage: geis
UpgradeStatus: Upgraded to saucy on 2014-01-04 (0 days ago)
XInput: Error: command ['xinput', 'input'] failed with exit code 1: X Input extension not available.
Xrandr: Error: command ['xrandr', '--verbose'] failed with exit code 1: RandR extension missing
dmi.bios.date: 06/25/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 4.6.5
dmi.board.asset.tag: Tag 12345
dmi.board.name: Lemur Ultra
dmi.board.vendor: System76, Inc.
dmi.board.version: lemu4
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: No Enclosure
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd06/25/2012:svnSystem76,Inc.:pnLemurUltra:pvrlemu4:rvnSystem76,Inc.:rnLemurUltra:rvrlemu4:cvnNoEnclosure:ct10:cvrN/A:
dmi.product.name: Lemur Ultra
dmi.product.version: lemu4
dmi.sys.vendor: System76, Inc.

Revision history for this message
Martin Uecker (muecker) wrote :
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.