Bug 374880 – crash in Document Viewer: Kile: DVI hat "Laden..."...

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 374880 - crash in Document Viewer: Kile: DVI hat "Laden..."...


Summary:	crash in Document Viewer: Kile: DVI hat "Laden..."...


Status:	RESOLVED DUPLICATE of bug 374277

Product:	evince
Classification:	Core
Component:	backends
Version:	0.6.x
Hardware:	Other All

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

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2006-11-13 21:49 UTC by xyxy
Modified:	2006-11-14 10:13 UTC

See Also:
GNOME target:	---
GNOME version:	2.15/2.16

Description xyxy 2006-11-13 21:49:14 UTC

Version: 0.6.1

What were you doing when the application crashed?
Kile: DVI hat "Laden..." angezeigt - wollte Fenster schließen	


Distribution: Ubuntu 6.10 (edgy)
Gnome Release: 2.16.1 2006-10-02 (Ubuntu)
BugBuddy Version: 2.16.0

Memory status: size: 53747712 vsize: 0 resident: 53747712 share: 0 rss: 23867392 rss_rlim: 0
CPU usage: start_time: 1163453274 rtime: 0 utime: 4454 stime: 0 cutime:4175 cstime: 0 timeout: 279 it_real_value: 0 frequency: 790

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)
[Thread debugging using libthread_db enabled]
[New Thread -1229797712 (LWP 6912)]
[New Thread -1231455328 (LWP 6914)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 86196

Thread 2 (Thread -1231455328 (LWP 6914))

#0 __kernel_vsyscall
#1 __waitpid_nocancel
from /lib/tls/i686/cmov/libpthread.so.0
#2 gnome_gtk_module_info_get
from /usr/lib/libgnomeui-2.so.0
#3 <signal handler called>
#4 g_type_check_instance_cast
from /usr/lib/libgobject-2.0.so.0
#5 djvu_links_get_links_model
#6 djvu_links_get_links_model
#7 djvu_links_get_links_model
#8 djvu_links_get_links_model
#9 djvu_links_get_links_model
#10 djvu_links_get_links_model
#11 _egg_marshal_VOID__INT_INT
#12 ??
#13 ??
#14 ??
#15 g_param_spec_types
from /usr/lib/libgobject-2.0.so.0
#16 g_type_check_instance_cast
from /usr/lib/libgobject-2.0.so.0
#17 ??
#18 ??
#19 ??
#20 ??
#21 g_queue_pop_head
from /usr/lib/libglib-2.0.so.0
#22 ??
#23 ??
#24 ??
#25 pthread_mutex_unlock
from /lib/tls/i686/cmov/libpthread.so.0
#26 g_thread_create_full
from /usr/lib/libglib-2.0.so.0
#27 start_thread
from /lib/tls/i686/cmov/libpthread.so.0
#28 clone
from /lib/tls/i686/cmov/libc.so.6

Comment 1 Wouter Bolsterlee (uws) 2006-11-13 22:15:20 UTC

Thanks for taking the time to report this bug.
Without a stack trace from the crash it's very hard to determine what caused it.
Can you get us a stack trace? Please see http://live.gnome.org/GettingTraces for more information on how to do so. Thanks in advance!

Comment 2 Nickolay V. Shmyrev 2006-11-14 10:13:34 UTC

Should be a dup

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.


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