Bug 389814 – crash in Document Viewer: using Lyx

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 389814 - crash in Document Viewer: using Lyx


Summary:	crash in Document Viewer: using Lyx


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-12-26 19:38 UTC by sudeep7
Modified:	2006-12-26 20:13 UTC

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

Description sudeep7 2006-12-26 19:38:44 UTC

Version: 0.6.1

What were you doing when the application crashed?
using Lyx


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

Memory status: size: 66502656 vsize: 0 resident: 66502656 share: 0 rss: 16752640 rss_rlim: 0
CPU usage: start_time: 1167161839 rtime: 0 utime: 411 stime: 0 cutime:346 cstime: 0 timeout: 65 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 -1229199696 (LWP 8803)]
[New Thread -1230443616 (LWP 8805)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 97132

Thread 2 (Thread -1230443616 (LWP 8805))

#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 djvu_links_get_links_model
#8 djvu_links_get_links_model
#9 _egg_marshal_VOID__INT_INT
#10 ??
#11 ??
#12 ??
#13 pthread_mutex_destroy
from /lib/tls/i686/cmov/libpthread.so.0
#14 ??
#15 ??
#16 ??
#17 __lll_mutex_unlock_wake
from /lib/tls/i686/cmov/libpthread.so.0
#18 _L_mutex_unlock_269
from /lib/tls/i686/cmov/libpthread.so.0
#19 ??
#20 ??
#21 __pthread_mutex_unlock_usercnt
from /lib/tls/i686/cmov/libpthread.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 Carlos Garcia Campos 2006-12-26 20:13: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.


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