Bug 374805 – crash in Document Viewer: Viewing DVI output from ...

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 374805 - crash in Document Viewer: Viewing DVI output from ...


Summary:	crash in Document Viewer: Viewing DVI output from ...


Status:	RESOLVED DUPLICATE of bug 361696

Product:	evince
Classification:	Core
Component:	general
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 18:31 UTC by praem.phulwani
Modified:	2006-11-13 22:13 UTC

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

Description praem.phulwani 2006-11-13 18:31:45 UTC

Version: 0.6.1

What were you doing when the application crashed?
Viewing DVI output from Lyx


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

Memory status: size: 82898944 vsize: 0 resident: 82898944 share: 0 rss: 16359424 rss_rlim: 0
CPU usage: start_time: 1163442606 rtime: 0 utime: 110 stime: 0 cutime:89 cstime: 0 timeout: 21 it_real_value: 0 frequency: 0

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 -1229592912 (LWP 22744)]
[New Thread -1230816352 (LWP 22746)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 86142

Thread 2 (Thread -1230816352 (LWP 22746))

#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 font_find_mapped
#5 font_find_mapped
#6 font_find_mapped
#7 font_find_mapped
#8 font_find_mapped
#9 djvu_links_get_links_model
#10 djvu_links_get_links_model
#11 _egg_marshal_VOID__INT_INT
#12 ??
#13 ??
#14 ??
#15 pthread_mutex_destroy
from /lib/tls/i686/cmov/libpthread.so.0
#16 ??
#17 ??
#18 ??
#19 __lll_mutex_unlock_wake
from /lib/tls/i686/cmov/libpthread.so.0
#20 _L_mutex_unlock_269
from /lib/tls/i686/cmov/libpthread.so.0
#21 ??
#22 ??
#23 __pthread_mutex_unlock_usercnt
from /lib/tls/i686/cmov/libpthread.so.0
#24 ??
#25 ??
#26 ??
#27 pthread_mutex_unlock
from /lib/tls/i686/cmov/libpthread.so.0
#28 g_thread_create_full
from /usr/lib/libglib-2.0.so.0
#29 start_thread
from /lib/tls/i686/cmov/libpthread.so.0
#30 clone
from /lib/tls/i686/cmov/libc.so.6

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

Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers?


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