Bug 330130 – Crash on "reload" in evince

After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.

Bug 330130 - Crash on "reload" in evince


Summary:	Crash on "reload" in evince


Status:	RESOLVED DUPLICATE of bug 314986

Product:	evince
Classification:	Core
Component:	general
Version:	unspecified
Hardware:	Other other

Importance:	High critical
Target Milestone:	---
Assigned To:	Evince Maintainers
QA Contact:	Evince Maintainers

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2006-02-06 14:57 UTC by elm
Modified:	2006-02-06 15:46 UTC

See Also:
GNOME target:	---
GNOME version:	2.11/2.12

Description elm 2006-02-06 14:57:54 UTC

Distribution: Ubuntu 5.10 (breezy)
Package: evince
Severity: Normal
Version: GNOME2.12.1 unspecified
Gnome-Distributor: Ubuntu
Synopsis: Crash on "reload" in evince
Bugzilla-Product: evince
Bugzilla-Component: general
Bugzilla-Version: unspecified
BugBuddy-GnomeVersion: 2.0 (2.12.0)
Description:
Description of the crash:
Trying to reload PDF documents being changed (e.g. written in LaTeX)
will cause evince to either spit out error messages (see below) or, on
occasion, crash. 

Error message:
(evince:9367): GLib-GObject-CRITICAL **: g_object_unref: assertion
`G_IS_OBJECT (object)' failed

Steps to reproduce the crash:
1. Open a PDF file being changed
2. Change the PDF (recompile with LaTeX)
3. Reload with evince

Expected Results:
The PDF document output in evince should be updated to reflect the
changes in the .tex file (or whatever was used to update the file).

How often does this happen?
Error message: most of the time.
Crash: sometimes.

Additional Information:
Related to (or equivalent to) Bug 171582.


Debugging Information:

Backtrace was generated from '/usr/bin/evince'

(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
`system-supplied DSO at 0xffffe000' has disappeared; keeping its
symbols.
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1228175680 (LWP 9367)]
[New Thread -1229714512 (LWP 9368)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 65946

Thread 1 (Thread -1228175680 (LWP 9367))

#0 __kernel_vsyscall
#1 waitpid
from /lib/tls/i686/cmov/libc.so.6
#2 libgnomeui_module_info_get
from /usr/lib/libgnomeui-2.so.0
#3 <signal handler called>
#4 g_type_check_instance_is_a
from /usr/lib/libgobject-2.0.so.0
#5 g_object_unref
from /usr/lib/libgobject-2.0.so.0
#6 g_object_set_valist
from /usr/lib/libgobject-2.0.so.0
#7 g_object_set
from /usr/lib/libgobject-2.0.so.0
#8 ev_page_action_set_document
#9 ev_window_open_uri
#10 g_cclosure_marshal_VOID__VOID
from /usr/lib/libgobject-2.0.so.0
#11 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#12 g_signal_stop_emission
from /usr/lib/libgobject-2.0.so.0
#13 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#14 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#15 ev_job_finished
#16 ev_document_types_add_filters
#17 g_child_watch_add
from /usr/lib/libglib-2.0.so.0
#18 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#19 g_main_context_check
from /usr/lib/libglib-2.0.so.0
#20 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#21 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#22 main
#0 __kernel_vsyscall





------- Bug created by bug-buddy at 2006-02-06 14:57 -------

Comment 1 Karsten Bräckelmann 2006-02-06 15:46:55 UTC

Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.


Same stacktrace as bug 324575, duplicate of bug 314986.

*** This bug has been marked as a duplicate of 314986 ***