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 481246 - 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-09-28 10:44 UTC by isabelm1970
Modified: 2007-10-08 12:40 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description isabelm1970 2007-09-28 10:44:47 UTC 
Version: 0.6.1

What were you doing when the application crashed?



Distribution: Guadalinex v4 (toro)
Gnome Release: 2.16.1 2006-10-02 (Ubuntu)
BugBuddy Version: 2.16.0

Memory status: size: 27992064 vsize: 0 resident: 27992064 share: 0 rss: 9330688 rss_rlim: 0
CPU usage: start_time: 1190976320 rtime: 0 utime: 29 stime: 0 cutime:26 cstime: 0 timeout: 3 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 -1229474128 (LWP 11720)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 166136

Thread 1 (Thread -1229474128 (LWP 11720))

  • #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 __kernel_vsyscall
  • #5 raise
    from /lib/tls/i686/cmov/libc.so.6
  • #6 abort
    from /lib/tls/i686/cmov/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 _egg_marshal_VOID__INT_INT
  • #11 ??
  • #12 ??
  • #13 _IO_stdin_used
  • #14 ??
  • #15 ??
  • #16 ??
  • #0 __kernel_vsyscall 






Comment 1


Cosimo Cecchi





          2007-10-08 12:40:36 UTC
        



Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.


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