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 422892 - crash in Document Viewer:
crash in Document Viewer:
Status: RESOLVED DUPLICATE of bug 374750
Product: evince
Classification: Core
Component: general
0.6.x
Other All
: High critical
: ---
Assigned To: Evince Maintainers
Evince Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-03-26 06:01 UTC by lemsto
Modified: 2007-03-26 09:24 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description lemsto 2007-03-26 06:01:34 UTC 
Version: 0.6.1

What were you doing when the application crashed?



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

Memory status: size: 151412736 vsize: 151412736 resident: 24354816 share: 12828672 rss: 24354816 rss_rlim: -1
CPU usage: start_time: 1174888873 rtime: 126 utime: 115 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 47678162947440 (LWP 9531)]
[New Thread 1082132816 (LWP 9533)]
(no debugging symbols found)
0x00002b5cededd7f6 in poll () from /lib/libc.so.6

+ Trace 122272

Thread 2 (Thread 1082132816 (LWP 9533))

  • #0 waitpid
    from /lib/libpthread.so.0
  • #1 gnome_gtk_module_info_get
    from /usr/lib64/libgnomeui-2.so.0
  • #2 <signal handler called>
  • #3 FcNameRegisterObjectTypes
    from /usr/lib64/libfontconfig.so.1
  • #4 FcObjectStaticName
    from /usr/lib64/libfontconfig.so.1
  • #5 ??
  • #6 ??
  • #7 ?? 






Comment 1


Carlos Garcia Campos





          2007-03-26 09:24:53 UTC
        



Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.


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