Bug 419005 – crash in Document Viewer:

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 419005 - crash in Document Viewer:


Summary:	crash in Document Viewer:


Status:	RESOLVED DUPLICATE of bug 374277

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:	2007-03-16 15:43 UTC by jhuesos
Modified:	2007-03-17 12:17 UTC

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

Description jhuesos 2007-03-16 15:43:15 UTC

Version: 0.6.1

What were you doing when the application crashed?



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

Memory status: size: 68984832 vsize: 0 resident: 68984832 share: 0 rss: 16822272 rss_rlim: 0
CPU usage: start_time: 1174059263 rtime: 0 utime: 116 stime: 0 cutime:93 cstime: 0 timeout: 23 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 -1229207888 (LWP 6432)]
[New Thread -1231107168 (LWP 6434)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 119156

Thread 2 (Thread -1231107168 (LWP 6434))

#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 Christian Kirbach 2007-03-17 12:17:31 UTC

Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.


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