GNOME Bugzilla – Bug 613025
Crash when saving edited copy over the original file
Last modified: 2010-03-16 16:25:28 UTC
Evince 2.28.1 using poppler 0.12.0 (cairo). How to reproduce: 1. Download an official income tax declaration for Geneva, Switzerland: http://ge.ch/impots/portal/jcr?workspace=EtatDeGenevePublie&path=/afc/documents/IS/2010/IS%20decla10_fr.pdf 2. Edit the "Nom" field 3. Ctrl-S 4. Select the original file 5. Click Save At this point, Evince crashes. 100% reproducible across 4 tries. Also reported in bug 480668.
I can't reproduce in evince 2.29.92 poppler 0.12.4, I think this is fixed, but, Can you get us a stack trace? Please see http://live.gnome.org/GettingTraces for more information on how to do so. Thanks in advance!
1. `sudo apt-get install evince-dbg libglib2.0-0-dbg libgtk2.0-0-dbg libgnomevfs2-0-dbg bug-buddy` 2. Repeated points 2-5 above. 3. Evince crashed. At this point, I got no bug-buddy pop-up and there's nothing in /var/crash, but there's the following line in /var/log/messages: Mar 16 16:20:05 hostname kernel: [20377.836640] evince[32704]: segfault at 0 ip b76c67f0 sp bff36ac0 error 4 in libevview.so.1.0.0[b76ae000+28000]
steps ~ gdb evince (gdb) run reproduce your steps when crash type thread apply all bt
$ gdb evince GNU gdb (GDB) 7.0-ubuntu Copyright (C) 2009 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "i486-linux-gnu". For bug reporting instructions, please see: <http://www.gnu.org/software/gdb/bugs/>... Reading symbols from /usr/bin/evince...Reading symbols from /usr/lib/debug/usr/bin/evince...done. (no debugging symbols found)...done. (gdb) run Starting program: /usr/bin/evince [Thread debugging using libthread_db enabled] [New Thread 0xb5677b70 (LWP 1119)] [New Thread 0xb4a5eb70 (LWP 1120)] [New Thread 0xb3fffb70 (LWP 1123)] [New Thread 0xb10ffb70 (LWP 1124)] [New Thread 0xb08feb70 (LWP 1125)] [Thread 0xb10ffb70 (LWP 1124) exited] [Thread 0xb3fffb70 (LWP 1123) exited] [Thread 0xb4a5eb70 (LWP 1120) exited] [New Thread 0xb4a5eb70 (LWP 1126)] [New Thread 0xb3fffb70 (LWP 1127)] [Thread 0xb08feb70 (LWP 1125) exited] [Thread 0xb3fffb70 (LWP 1127) exited] [New Thread 0xb3fffb70 (LWP 1128)] [Thread 0xb3fffb70 (LWP 1128) exited] [New Thread 0xb3fffb70 (LWP 1129)] [Thread 0xb4a5eb70 (LWP 1126) exited] [New Thread 0xb4a5eb70 (LWP 1130)] [Thread 0xb4a5eb70 (LWP 1130) exited] [New Thread 0xb4a5eb70 (LWP 1131)] [Thread 0xb4a5eb70 (LWP 1131) exited] [New Thread 0xb4a5eb70 (LWP 1132)] [New Thread 0xb08feb70 (LWP 1133)] Program received signal SIGSEGV, Segmentation fault. doc_rect_to_view_rect (view=0x82b6140, page=<value optimized out>, doc_rect=0x0, view_rect=0xbfa6fb70) at ev-view.c:950 950 ev-view.c: No such file or directory. in ev-view.c (gdb) thread apply all bt
+ Trace 220983
Thread 1 (Thread 0xb65b4980 (LWP 1116))
I guess the "No such file or directory" could be because the path is not trivial - Both the directory and the file name contains spaces.
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 bug 602405 ***