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 325986 - Critical Warning when viewing postscript file
Critical Warning when viewing postscript file
Status: RESOLVED FIXED
Product: evince
Classification: Core
Component: general
git master
Other All
: Normal minor
: ---
Assigned To: Evince Maintainers
Evince Maintainers
Depends on:
Blocks:
 
 
Reported: 2006-01-06 14:36 UTC by Don Scorgie
Modified: 2006-01-06 18:37 UTC
See Also:
GNOME target: ---
GNOME version: 2.13/2.14



Description Don Scorgie 2006-01-06 14:36:40 UTC
Please describe the problem:
Create a longish postscript file.  View it in evince and scroll down to a page
further on.

Now overwrite the postscript file with a new, shorter document.  When viewing
this in evince, a collection of CRITICALs appears in the terminal:
** (evince:17524): CRITICAL **: ev_page_cache_get_page_label: assertion `page >=
0 && page < page_cache->n_pages' failed

(evince:17524): Gtk-CRITICAL **: gtk_entry_set_text: assertion `text != NULL' failed

** (evince:17524): CRITICAL **: ev_page_cache_get_size: assertion `page >= 0 &&
page < page_cache->n_pages' failed

** (evince:17524): CRITICAL **: ev_page_cache_get_size: assertion `page >= 0 &&
page < page_cache->n_pages' failed

** (evince:17524): CRITICAL **: ev_page_cache_get_size: assertion `page >= 0 &&
page < page_cache->n_pages' failed

** (evince:17524): CRITICAL **: ev_page_cache_get_size: assertion `page >= 0 &&
page < page_cache->n_pages' failed


Steps to reproduce:
1. Load up the user guide in Yelp.  Select print Document and save it to a
postscript file.
2. View in evince and scroll to any page > 1
3. Restart yelp with the user guide.  Select print page and save it over the
same file.
4. View again in evince


Actual results:


Expected results:


Does this happen every time?


Other information:
Maybe not a big deal but since Critical warning now crash, it gets a little
frustrating
Comment 1 Nickolay V. Shmyrev 2006-01-06 14:43:24 UTC
Thanks for reporting, Don. 

Since you got crashes now, can you provide backtrace? Of alternatively you can run evince under gdb and set breakpoint on g_log function 
Comment 2 Don Scorgie 2006-01-06 15:17:15 UTC
Stack trace:

  • #0 IA__g_log
    at gmessages.c line 516
  • #1 IA__g_return_if_fail_warning
    at gmessages.c line 532
  • #2 ev_page_cache_get_page_label
    at ev-page-cache.c line 467
  • #3 page_changed_cb
    at ev-page-action.c line 190
  • #4 IA__g_cclosure_marshal_VOID__INT
    at gmarshal.c line 216
  • #5 IA__g_closure_invoke
    at gclosure.c line 490
  • #6 signal_emit_unlocked_R
    at gsignal.c line 2449
  • #7 IA__g_signal_emit_valist
    at gsignal.c line 2208
  • #8 IA__g_signal_emit
    at gsignal.c line 2252
  • #9 ev_page_cache_set_current_page
    at ev-page-cache.c line 302
  • #10 ev_window_load_job_cb
    at ev-window.c line 635
  • #11 IA__g_cclosure_marshal_VOID__VOID
    at gmarshal.c line 77
  • #12 IA__g_closure_invoke
    at gclosure.c line 490
  • #13 signal_emit_unlocked_R
    at gsignal.c line 2449
  • #14 IA__g_signal_emit_valist
    at gsignal.c line 2208
  • #15 IA__g_signal_emit
    at gsignal.c line 2252
  • #16 ev_job_finished
    at ev-jobs.c line 207
  • #17 notify_finished
    at ev-job-queue.c line 67
  • #18 g_idle_dispatch
    at gmain.c line 3761
  • #19 IA__g_main_context_dispatch
    at gmain.c line 1913
  • #20 g_main_context_iterate
    at gmain.c line 2544
  • #21 IA__g_main_loop_run
    at gmain.c line 2748
  • #22 IA__gtk_main
    at gtkmain.c line 991
  • #23 main
    at main.c line 295

Comment 3 Nickolay V. Shmyrev 2006-01-06 18:37:40 UTC
It should be fixed in CVS. Thanks for wonderful testing.