Bug 356920 – crash in Document Viewer: Ik gaf een printopdracht...

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 356920 - crash in Document Viewer: Ik gaf een printopdracht...


Summary:	crash in Document Viewer: Ik gaf een printopdracht...


Status:	RESOLVED DUPLICATE of bug 325759

Product:	atk
Classification:	Platform
Component:	gail
Version:	1.12.x
Hardware:	Other All

Importance:	High critical
Target Milestone:	---
Assigned To:	bill.haneman
QA Contact:	bill.haneman

URL:
Whiteboard:

Duplicates:	357536 413359 414439 417079 446163 (view as bug list)
Depends on:
Blocks:

Reported:	2006-09-20 15:50 UTC by Robert Hensing
Modified:	2007-06-13 17:22 UTC

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

Description Robert Hensing 2006-09-20 15:50:31 UTC

Version: 0.6.0

What were you doing when the application crashed?
Ik gaf een printopdracht vanuit OpenOffice.		


Distribution: Gentoo Base System version 1.12.5
Gnome Release: 2.16.0 2006-09-18 (Gentoo)
BugBuddy Version: 2.16.0

Memory status: size: 74051584 vsize: 0 resident: 74051584 share: 0 rss: 25649152 rss_rlim: 0
CPU usage: start_time: 1158767365 rtime: 0 utime: 167 stime: 0 cutime:148 cstime: 0 timeout: 19 it_real_value: 0 frequency: 0

Backtrace was generated from '/usr/bin/evince'

(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1230293328 (LWP 27558)]
[New Thread -1232397408 (LWP 27592)]
0xffffe410 in __kernel_vsyscall ()

+ Trace 72841

Thread 1 (Thread -1230293328 (LWP 27558))

#0 __kernel_vsyscall
#1 __waitpid_nocancel
from /lib/libpthread.so.0
#2 gnome_gtk_module_info_get
from /usr/lib/libgnomeui-2.so.0
#3 <signal handler called>
#4 __kernel_vsyscall
#5 raise
from /lib/libc.so.6
#6 abort
from /lib/libc.so.6
#7 g_logv
from /usr/lib/libglib-2.0.so.0
#8 g_log
from /usr/lib/libglib-2.0.so.0
#9 g_assert_warning
from /usr/lib/libglib-2.0.so.0
#10 gail_tree_view_new
from /usr/lib/gtk-2.0/modules/libgail.so
#11 g_source_is_destroyed
from /usr/lib/libglib-2.0.so.0
#12 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#13 g_main_context_check
from /usr/lib/libglib-2.0.so.0
#14 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#15 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#16 main
#0 __kernel_vsyscall

Comment 1 Karsten Bräckelmann 2006-09-24 23:49:25 UTC

*** Bug 357536 has been marked as a duplicate of this bug. ***

Comment 2 bill.haneman 2006-09-25 09:20:51 UTC

Thanks for the bug report. Unfortunately, that stack trace is not very useful in determining the cause of the crash. Can you get us one with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so.

Comment 3 bill.haneman 2006-09-25 12:30:49 UTC

I can't be sure without a better stack trace but I suspect this is a dup of bug 326759.   If the bug reporter or someone who can reproduce the bug can update their copy of libgail (cvs module gail) and re-test I'd appreciate it.

If updating gail (from cvs as of Sep 13) does not fix this bug, please reopen.

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

Comment 4 Christian Kirbach 2007-03-04 16:04:08 UTC

*** Bug 414439 has been marked as a duplicate of this bug. ***

Comment 5 Pascal Terjan 2007-03-17 19:26:45 UTC

*** Bug 413359 has been marked as a duplicate of this bug. ***

Comment 6 Pascal Terjan 2007-03-17 19:26:56 UTC

*** Bug 417079 has been marked as a duplicate of this bug. ***

Comment 7 Susana 2007-06-13 17:22:31 UTC

*** Bug 446163 has been marked as a duplicate of this bug. ***