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 529869 - crash in Document Viewer: I was filling a PDF form...
crash in Document Viewer: I was filling a PDF form...
Status: RESOLVED DUPLICATE of bug 518831
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-25 11:16 UTC by mikko.i.nurminen
Modified: 2008-04-27 20:41 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22



Description mikko.i.nurminen 2008-04-25 11:16:59 UTC
Version: 2.20.2

What were you doing when the application crashed?
I was filling a PDF form at  http://primetieto.fi/files/resourcesmodule/@random470496efba636/1209022981_hakemuscad08.pdf .Midway down the first page there is a section called "KIELITAITO JA OHJELMISTO-OSAAMINEN ". Under the header "Osaaminen" there are drop-down boxes. Trying to set any value from the a drop-down box results in Evince crashing. 



Distribution: Debian lenny/sid
Gnome Release: 2.22.1 2008-04-08 (Debian)
BugBuddy Version: 2.22.0

System: Linux 2.6.24-1-686 #1 SMP Sat Apr 19 00:37:55 UTC 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10400090
Selinux: No
Accessibility: Disabled
GTK+ Theme: Gorilla
Icon Theme: Gorilla

Memory status: size: 54210560 vsize: 54210560 resident: 20951040 share: 13176832 rss: 20951040 rss_rlim: 4294967295
CPU usage: start_time: 1209111411 rtime: 1074 utime: 1028 stime: 46 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/bin/evince'

(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0xb6978720 (LWP 9058)]
[New Thread 0xb66e7b90 (LWP 9059)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

Thread 1 (Thread 0xb6978720 (LWP 9058))

  • #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 ??
  • #7 ??
  • #8 ??
  • #9 ??
  • #0 __kernel_vsyscall


----------- .xsession-errors (316 sec old) ---------------------
"!prefs_key=/apps/panel/applets/applet_1/prefs;background=pixmap:14680345,-1,-1;orient=down;size=small;locked_down=false":n selvittäminen tai laajentaminen epäonnistui
** (gksu:3960): CRITICAL **: fcntl error
** (gksu:3960): WARNING **: Lock taken by pid: -1. Exiting.
** (gksu:5228): CRITICAL **: fcntl error
** (gksu:5228): WARNING **: Lock taken by pid: -1. Exiting.
** (gksu:5236): CRITICAL **: fcntl error
** (gksu:5236): WARNING **: Lock taken by pid: -1. Exiting.
Ikkunointiohjelman varoitus:Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x2400003 (Evince-asi)
Ikkunointiohjelman varoitus:meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
--------------------------------------------------
Comment 1 Gianluca Borello 2008-04-25 17:55:35 UTC
what version of poppler are you using?

There is no crash using evince 2.22.1.1 and poppler 0.6.4.
Comment 2 mikko.i.nurminen 2008-04-26 07:46:43 UTC
(In reply to comment #1)
> what version of poppler are you using?
> 
> There is no crash using evince 2.22.1.1 and poppler 0.6.4.
> 

I'm using Debian testing, and the currently installed version of libpoppler2 is 0.6.4-1. Since I'm using Evince 2.20.2, maybe the bug I'm seeing has already been fixed in 2.22.1.1? Damn the speedy development!-)
Comment 3 Gianluca Borello 2008-04-26 22:55:50 UTC
This is possible...but if you can please provide a full stacktrace by installing debug packages.
Comment 4 mikko.i.nurminen 2008-04-27 18:05:31 UTC
What follows is the tragic outcome of me trying to understand what is a full stacktrace and how to get one using evince-dbg and gbd. Hopefully the needed information is here. :-)

-begin of log-

Starting program: /usr/bin/evince 
[Thread debugging using libthread_db enabled]
[New Thread 0xb6974720 (LWP 13048)]
[New Thread 0xb6729b90 (LWP 13051)]
[New Thread 0xb5d83b90 (LWP 13052)]
[Thread 0xb5d83b90 (LWP 13052) exited]

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0xb6974720 (LWP 13048)]
0x0807724d in ev_view_form_field_choice_changed (widget=0x82bba18, 
    field=0x84d6c88) at /build/buildd/evince-2.20.2/./shell/ev-view.c:1882
1882    /build/buildd/evince-2.20.2/./shell/ev-view.c: No such file or directory.
        in /build/buildd/evince-2.20.2/./shell/ev-view.c

Thread 1 (Thread 0xb6974720 (LWP 13048))

  • #0 ev_view_form_field_choice_changed
    at /build/buildd/evince-2.20.2/./shell/ev-view.c line 1882
  • #1 g_cclosure_marshal_VOID__VOID
    from /usr/lib/libgobject-2.0.so.0
  • #2 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #3 ??
    from /usr/lib/libgobject-2.0.so.0
  • #4 ??
  • #5 ??

-end of log-
Comment 5 Gianluca Borello 2008-04-27 20:40:41 UTC
Thank you for the stack trace (even if it is not full, next time i suggest you the reading at http://live.gnome.org/GettingTraces), i caught the duplicate.

Comment 6 Gianluca Borello 2008-04-27 20:41:16 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 518831 ***