Bug 452618 – 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 452618 - crash in Document Viewer:


Summary:	crash in Document Viewer:


Status:	RESOLVED DUPLICATE of bug 438180

Product:	evince
Classification:	Core
Component:	general
Version:	0.8.x
Hardware:	Other All

Importance:	High critical
Target Milestone:	---
Assigned To:	Evince Maintainers
QA Contact:	Evince Maintainers

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2007-06-30 18:41 UTC by vzabalza
Modified:	2007-07-01 11:06 UTC

See Also:
GNOME target:	---
GNOME version:	2.17/2.18

Description vzabalza 2007-06-30 18:41:07 UTC

Version: 0.8.1

What were you doing when the application crashed?



Distribution: Unknown
Gnome Release: 2.18.2 2007-06-01 (Archlinux)
BugBuddy Version: 2.18.1

System: Linux 2.6.21-ARCH #1 SMP PREEMPT Tue Jun 12 02:55:15 CEST 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome

Memory status: size: 147156992 vsize: 147156992 resident: 21422080 share: 14471168 rss: 21422080 rss_rlim: 18446744073709551615
CPU usage: start_time: 1183228966 rtime: 64 utime: 53 stime: 11 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

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 47709008811312 (LWP 5767)]
[New Thread 1082132816 (LWP 5768)]
(no debugging symbols found)
0x00002b641b8cf618 in __lll_mutex_lock_wait () from /lib/libpthread.so.0

+ Trace 144903

Thread 2 (Thread 1082132816 (LWP 5768))

#0 waitpid
from /lib/libpthread.so.0
#1 libgnomeui_segv_handle
from /usr/lib/libgnomeui-2.so.0
#2 <signal handler called>
#3 raise
from /lib/libc.so.6
#4 abort
from /lib/libc.so.6
#5 __assert_fail
from /lib/libc.so.6
#6 CairoOutputDev::drawImageMask
from /usr/lib/libpoppler-glib.so.1
#7 Gfx::doImage
from /usr/lib/libpoppler.so.1
#8 Gfx::opBeginImage
from /usr/lib/libpoppler.so.1
#9 Gfx::go
from /usr/lib/libpoppler.so.1
#10 Gfx::display
from /usr/lib/libpoppler.so.1
#11 Gfx::doShowText
from /usr/lib/libpoppler.so.1
#12 Gfx::opShowText
from /usr/lib/libpoppler.so.1
#13 Gfx::go
from /usr/lib/libpoppler.so.1
#14 Gfx::display
from /usr/lib/libpoppler.so.1
#15 Page::displaySlice
from /usr/lib/libpoppler.so.1
#16 poppler_page_render_to_pixbuf
from /usr/lib/libpoppler-glib.so.1
#17 ??
#18 ev_job_thumbnail_run
#19 ??
#20 ??
#21 g_thread_create_proxy
from /usr/lib/libglib-2.0.so.0
#22 start_thread
from /lib/libpthread.so.0
#23 clone
from /lib/libc.so.6



----------- .xsession-errors ---------------------
Qt: Warning: QObject::disconnect: Unexpected null parameter
Qt: Warning: QObject::disconnect: Unexpected null parameter
X Error: BadWindow (invalid Window parameter) 3
  Major opcode:  7
  Minor opcode:  0
  Resource id:  0x3a00321
kio (KIOConnection): ERROR: Could not write data
kio (KIOConnection): ERROR: Could not write data
kio (KIOConnection): ERROR: Could not write data
ICE default IO error handler doing an exit(), pid = 5304, errno = 0
Avís del gestor de finestres: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x2e00003 (Visualitza)
Avís del gestor de finestres: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
Avís del gestor de finestres: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x2e00003 (Visualitza)
Avís del gestor de finestres: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
evince: CairoOutputDev.cc:685: virtual void CairoOutputDev::drawImageMask(GfxState*, Object*, Stream*, int, int, GBool, GBool): L'asserció «n == 0» ha fallat.
--------------------------------------------------

Comment 1 Christian Kirbach 2007-07-01 11:06:14 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 438180 ***