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 529508 - crash in Document Viewer: opened the print window ...
crash in Document Viewer: opened the print window ...
Status: RESOLVED DUPLICATE of bug 460887
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-23 09:08 UTC by skully
Modified: 2008-04-23 16:46 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22



Description skully 2008-04-23 09:08:17 UTC
Version: 2.20.2

What were you doing when the application crashed?
opened the print window and the network printer was missing


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

System: Linux 2.6.24 #1 SMP Thu Apr 3 19:54:42 CEST 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: SphereCrystal
Icon Theme: SphereCrystal

Memory status: size: 83984384 vsize: 83984384 resident: 56451072 share: 14692352 rss: 56451072 rss_rlim: 4294967295
CPU usage: start_time: 1208941738 rtime: 55 utime: 49 stime: 6 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/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0xb6a7b720 (LWP 7717)]
[New Thread 0xb68a9b90 (LWP 7718)]
0xffffe410 in __kernel_vsyscall ()

Thread 1 (Thread 0xb6a7b720 (LWP 7717))

  • #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 _gtk_printer_prepare_for_print
    at /tmp/buildd/gtk+2.0-2.12.9/gtk/gtkprinter.c line 796
  • #7 gtk_print_job_constructor
    at /tmp/buildd/gtk+2.0-2.12.9/gtk/gtkprintjob.c line 232
  • #8 g_object_newv
    from /usr/lib/libgobject-2.0.so.0
  • #9 g_object_new_valist
    from /usr/lib/libgobject-2.0.so.0
  • #10 g_object_new
    from /usr/lib/libgobject-2.0.so.0
  • #11 IA__gtk_print_job_new
    at /tmp/buildd/gtk+2.0-2.12.9/gtk/gtkprintjob.c line 297
  • #12 ??
  • #13 ??
  • #14 ??
  • #0 __kernel_vsyscall


----------- .xsession-errors ---------------------
cairo context error: NULL pointer
cairo context error: NULL pointer
cairo context error: NULL pointer
cairo context error: NULL pointer
opera: Activated running instance
opera: Activated running instance
opera: Activated running instance
(evince:7717): GLib-GObject-CRITICAL **: g_object_ref: assertion `G_IS_OBJECT (object)' failed
(evince:7717): Gtk-CRITICAL **: gtk_printer_accepts_ps: assertion `GTK_IS_PRINTER (printer)' failed
(evince:7717): Gtk-CRITICAL **: gtk_printer_get_backend: assertion `GTK_IS_PRINTER (printer)' failed
(evince:7717): GLib-GObject-CRITICAL **: g_object_ref: assertion `G_IS_OBJECT (object)' failed
--------------------------------------------------
Comment 1 skully 2008-04-23 09:11:32 UTC
Using cupsys and cupsys crashed after i printed 1 page (didnt notice that).
Wanted to print another page and opened print dialog and then it crashed.
Comment 2 Gianluca Borello 2008-04-23 16:46:46 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 460887 ***