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 527142 - crash in Document Viewer: si stava aprendo un file...
crash in Document Viewer: si stava aprendo un file...
Status: RESOLVED DUPLICATE of bug 510802
Product: evince
Classification: Core
Component: general
2.20.x
Other All
: High critical
: ---
Assigned To: Evince Maintainers
Evince Maintainers
Depends on:
Blocks:
 
 
Reported: 2008-04-09 14:05 UTC by pennacg
Modified: 2008-04-09 14:47 UTC
See Also:
GNOME target: ---
GNOME version: 2.19/2.20



Description pennacg 2008-04-09 14:05:50 UTC
Version: 2.20.2

What were you doing when the application crashed?
si stava aprendo un file .pdf


Distribution: Debian lenny/sid
Gnome Release: 2.20.3 2008-01-12 (Debian)
BugBuddy Version: 2.20.1

System: Linux 2.6.22-3-k7 #1 SMP Sun Feb 10 21:04:14 UTC 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome

Memory status: size: 61923328 vsize: 61923328 resident: 39895040 share: 13041664 rss: 39895040 rss_rlim: 4294967295
CPU usage: start_time: 1207749971 rtime: 291 utime: 270 stime: 21 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/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0xb6b4f6c0 (LWP 4706)]
[New Thread 0xb699db90 (LWP 4707)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

Thread 1 (Thread 0xb6b4f6c0 (LWP 4706))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/i686/cmov/libpthread.so.0
  • #2 g_spawn_sync
    from /usr/lib/libglib-2.0.so.0
  • #3 g_spawn_command_line_sync
    from /usr/lib/libglib-2.0.so.0
  • #4 ??
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #5 <signal handler called>
  • #6 TextLine::visitSelection
    from /usr/lib/libpoppler.so.2
  • #7 TextBlock::visitSelection
    from /usr/lib/libpoppler.so.2
  • #8 TextPage::visitSelection
    from /usr/lib/libpoppler.so.2
  • #9 TextPage::getSelectionRegion
    from /usr/lib/libpoppler.so.2
  • #10 TextOutputDev::getSelectionRegion
    from /usr/lib/libpoppler.so.2
  • #11 poppler_page_get_selection_region
    from /usr/lib/libpoppler-glib.so.2
  • #12 ??
  • #13 ??
  • #14 ??
  • #15 ??
  • #16 ??
  • #17 ??
  • #18 ??
  • #19 ??
  • #20 ??
  • #21 ??
  • #22 ??
  • #23 ??
  • #24 ??
  • #25 ??
  • #26 ??
  • #27 ??
  • #0 __kernel_vsyscall


----------- .xsession-errors (11 sec old) ---------------------
(gecko:3796): GLib-GObject-WARNING **: instance of invalid non-instantiatable type `(null)'
(gecko:3796): GLib-GObject-CRITICAL **: g_signal_handler_disconnect: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed
(gecko:3796): GLib-GObject-WARNING **: invalid uninstantiatable type `(null)' in cast to `GtkObject'
(gecko:3796): GLib-GObject-WARNING **: instance of invalid non-instantiatable type `(null)'
(gecko:3796): GLib-GObject-CRITICAL **: g_signal_handler_disconnect: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed
(gecko:3796): GLib-GObject-WARNING **: instance of invalid non-instantiatable type `(null)'
(gecko:3796): GLib-GObject-CRITICAL **: g_signal_handler_disconnect: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed
Avviso del window manager: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x2a00003 (Visualizza)
Avviso del window manager: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
--------------------------------------------------
Comment 1 palfrey 2008-04-09 14:47:45 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 510802 ***