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 368840 - crash in Document Viewer: Selecting Chinese text
crash in Document Viewer: Selecting Chinese text
Status: RESOLVED DUPLICATE of bug 362110
Product: evince
Classification: Core
Component: general
0.6.x
Other All
: High critical
: ---
Assigned To: Evince Maintainers
Evince Maintainers
Depends on:
Blocks:
 
 
Reported: 2006-11-01 13:12 UTC by Alexander Hunziker
Modified: 2006-11-01 19:59 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16



Description Alexander Hunziker 2006-11-01 13:12:33 UTC
Version: 0.6.1

What were you doing when the application crashed?
Selecting Chinese text


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

Memory status: size: 92934144 vsize: 0 resident: 92934144 share: 0 rss: 31035392 rss_rlim: 0
CPU usage: start_time: 1162386142 rtime: 0 utime: 148 stime: 0 cutime:134 cstime: 0 timeout: 14 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 -1229523280 (LWP 13048)]
[New Thread -1230996576 (LWP 13050)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

Thread 1 (Thread -1229523280 (LWP 13048))

  • #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 poppler_page_render_selection
    from /usr/lib/libpoppler-glib.so.1
  • #5 pdf_selection_render_selection
  • #6 _egg_marshal_VOID__INT_INT
  • #7 ??
  • #8 ??
  • #9 ??
  • #10 ??
  • #11 ??
  • #12 ??
  • #0 __kernel_vsyscall

Comment 1 André Klapper 2006-11-01 19:59:54 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 362110 ***