Bug 417839 – crash in Document Viewer: Wanted to view an dvi fi...

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 417839 - crash in Document Viewer: Wanted to view an dvi fi...


Summary:	crash in Document Viewer: Wanted to view an dvi fi...


Status:	RESOLVED DUPLICATE of bug 395037

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-13 12:45 UTC by udo_hortian
Modified:	2007-04-07 15:09 UTC

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

Description udo_hortian 2007-03-13 12:45:53 UTC

Version: 0.6.1

What were you doing when the application crashed?
Wanted to view an dvi file (dvi viewer started out of mutt to view an email attachment).


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

Memory status: size: 75444224 vsize: 0 resident: 75444224 share: 0 rss: 33955840 rss_rlim: 0
CPU usage: start_time: 1173789848 rtime: 0 utime: 130 stime: 0 cutime:114 cstime: 0 timeout: 16 it_real_value: 0 frequency: 322

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 -1229715792 (LWP 8164)]
[New Thread -1230722144 (LWP 8166)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 118263

Thread 2 (Thread -1230722144 (LWP 8166))

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

Comment 1 palfrey 2007-04-07 15:09:29 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 395037 ***