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 376962 - printing a text
printing a text
Status: RESOLVED INCOMPLETE
Product: gnome-print
Classification: Deprecated
Component: gnome-cups-manager
2.10.x
Other All
: High critical
: ---
Assigned To: Jody Goldberg
Jody Goldberg
: 377030 378213 383397 386232 394286 397695 401466 402800 424239 467449 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2006-11-19 11:54 UTC by edward.vs
Modified: 2008-10-12 17:03 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16



Description edward.vs 2006-11-19 11:54:58 UTC
Version: 2.16.1

What were you doing when the application crashed?
Een poging tot afdrukken.


Distribution: Ubuntu 6.10 (edgy)
Gnome Release: 2.16.1 2006-10-02 (Ubuntu)
BugBuddy Version: 2.16.0

Memory status: size: 68628480 vsize: 0 resident: 68628480 share: 0 rss: 23937024 rss_rlim: 0
CPU usage: start_time: 1163937001 rtime: 0 utime: 245 stime: 0 cutime:223 cstime: 0 timeout: 22 it_real_value: 0 frequency: 0

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

(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 -1227663696 (LWP 7651)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

Thread 1 (Thread -1227663696 (LWP 7651))

  • #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 gnome_cups_printer_get_ppd
    from /usr/lib/libgnomecups-1.0.so.1
  • #5 gnome_cups_printer_get_options
    from /usr/lib/libgnomecups-1.0.so.1
  • #6 gnome_print__transport_get_type
    from /usr/lib/libgnomeprint/2.12.1/modules/libgnomeprintcups.so
  • #7 gnome_print_transport_close
    from /usr/lib/libgnomeprint-2-2.so.0
  • #8 gnome_print_ps2_new
    from /usr/lib/libgnomeprint-2-2.so.0
  • #9 gnome_print_context_close
    from /usr/lib/libgnomeprint-2-2.so.0
  • #10 gnome_print_job_print
    from /usr/lib/libgnomeprint-2-2.so.0
  • #11 _gedit_tab_print
  • #12 g_cclosure_marshal_VOID__VOID
    from /usr/lib/libgobject-2.0.so.0
  • #13 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #14 g_signal_chain_from_overridden
    from /usr/lib/libgobject-2.0.so.0
  • #15 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #16 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #17 gtk_source_print_job_new_with_buffer
    from /usr/lib/libgtksourceview-1.0.so.0
  • #18 g_source_set_closure
    from /usr/lib/libgobject-2.0.so.0
  • #19 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #20 g_source_set_closure
    from /usr/lib/libgobject-2.0.so.0
  • #21 g_source_is_destroyed
    from /usr/lib/libglib-2.0.so.0
  • #22 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #23 g_main_context_check
    from /usr/lib/libglib-2.0.so.0
  • #24 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #25 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #26 main
  • #0 __kernel_vsyscall

Comment 1 Christian Kirbach 2006-11-19 16:19:36 UTC
*** Bug 377030 has been marked as a duplicate of this bug. ***
Comment 2 Christian Kirbach 2006-11-19 16:45:56 UTC
Thanks for taking the time to report this bug.
Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so. Thanks in advance!

please install libgnomecups/gnome-print packages
Comment 3 Steve Frécinaux 2006-11-25 15:08:39 UTC
*** Bug 378213 has been marked as a duplicate of this bug. ***
Comment 4 Christian Kirbach 2006-12-07 15:46:26 UTC
*** Bug 383397 has been marked as a duplicate of this bug. ***
Comment 5 Felix Riemann 2006-12-15 20:18:29 UTC
*** Bug 386232 has been marked as a duplicate of this bug. ***
Comment 6 Pedro de Medeiros 2007-01-08 19:32:49 UTC
*** Bug 394286 has been marked as a duplicate of this bug. ***
Comment 7 Susana 2007-01-17 21:34:43 UTC
*** Bug 397695 has been marked as a duplicate of this bug. ***
Comment 8 Jens Granseuer 2007-01-27 22:01:22 UTC
*** Bug 401466 has been marked as a duplicate of this bug. ***
Comment 9 Christian Kirbach 2007-01-27 23:31:12 UTC
Thanks for taking the time to report this bug.
Unfortunately, that stack trace is missing some elements that will help a lot
to solve the problem, so it will be hard for the developers to fix that crash.
Can you get us a stack trace with debugging symbols? Please see
http://live.gnome.org/GettingTraces for more information on how to do so.
Thanks in advance!
Comment 10 Susana 2007-01-31 14:23:56 UTC
*** Bug 402800 has been marked as a duplicate of this bug. ***
Comment 11 Sven Arvidsson 2007-03-29 21:48:19 UTC
*** Bug 424239 has been marked as a duplicate of this bug. ***
Comment 12 devius 2007-03-30 00:34:05 UTC
(In reply to comment #9)
> Thanks for taking the time to report this bug.
> Unfortunately, that stack trace is missing some elements that will help a lot
> to solve the problem, so it will be hard for the developers to fix that crash.
> Can you get us a stack trace with debugging symbols? Please see
> http://live.gnome.org/GettingTraces for more information on how to do so.
> Thanks in advance!
> 

I'd like to help, but after browsing the dbgsym libraries available there isn't any for gnome-print, or gnome-cups-manager or even some of the ones mentioned in http://live.gnome.org/GettingTraces - gtk and gnome-vfs. I could only find a few gtk2-engines-... (is any of those the right one?) and gtk2-examples and no gnome-vfs.
Comment 13 palfrey 2007-08-17 11:12:24 UTC
*** Bug 467449 has been marked as a duplicate of this bug. ***
Comment 14 André Klapper 2008-10-12 17:03:57 UTC
Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for.
Thanks!