evince crashed with signal 5 in _XError()

Bug #510369 reported by Spyros Kavvadias on 2010-01-20
This bug affects 2 people
Affects Status Importance Assigned to Milestone
evince (Ubuntu)

Bug Description

Binary package hint: evince


Evince crashed when i was trying to edit the toolbar (add more icons).


ProblemType: Crash
Architecture: i386
Date: Wed Jan 20 23:57:10 2010
DistroRelease: Ubuntu 10.04
ExecutablePath: /usr/bin/evince
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Alpha i386 (20100113)
Package: evince 2.29.5-0ubuntu1
ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-2.6.32-10-generic-pae root=UUID=67b87461-1182-470f-be2f-fa3bf4501f2f ro quiet splash
ProcVersionSignature: Ubuntu 2.6.32-10.14-generic-pae
Signal: 5
SourcePackage: evince
 ?? () from /usr/lib/libgdk-x11-2.0.so.0
 _XError () from /usr/lib/libX11.so.6
 ?? () from /usr/lib/libX11.so.6
 _XReply () from /usr/lib/libX11.so.6
 ?? () from /usr/lib/libgdk-x11-2.0.so.0
Title: evince crashed with signal 5 in _XError()
Uname: Linux 2.6.32-10-generic-pae i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
 (gnome-settings-daemon:1855): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed
 (gnome-settings-daemon:1855): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed
 (polkit-gnome-authentication-agent-1:1925): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed

Spyros Kavvadias (thunk) wrote :
visibility: private → public

 gdk_x_error (display=0xb95f5508, error=0xbff970ac)
 _XError (dpy=0xb95f5508, rep=0xaecac5b8)
 process_responses (dpy=0xb95f5508,
 _XReply (dpy=0xb95f5508, rep=0xbff97288, extra=0, discard=1)
 _gdk_x11_get_window_child_info (display=0xb9601000,

Changed in evince (Ubuntu):
importance: Undecided → Medium
tags: removed: need-i386-retrace
Pedro Villavicencio (pedro) wrote :

Thanks for the report, could you run it under gdb with the following instructions? :

gdb evince
(gdb) set logging on evince-crash.txt
(gdb) break gdk_x_error
(gdb) run --sync
 (reproduce the crash)
(gdb) thread apply all bt

and then attach that evince-crash.txt file to the report? thanks in advance.

Changed in evince (Ubuntu):
status: New → Incomplete
Pedro Villavicencio (pedro) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to New. Thanks again!.

Changed in evince (Ubuntu):
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers