Bug 378213 – crash in Text Editor: Trying to print from ged...

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 378213 - crash in Text Editor: Trying to print from ged...


Summary:	crash in Text Editor: Trying to print from ged...


Status:	RESOLVED DUPLICATE of bug 376962

Product:	gedit
Classification:	Applications
Component:	general
Version:	2.16.x
Hardware:	Other All

Importance:	High critical
Target Milestone:	---
Assigned To:	Gedit maintainers
QA Contact:	Gedit maintainers

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2006-11-22 19:28 UTC by v.simon
Modified:	2006-11-25 15:08 UTC

See Also:
GNOME target:	---
GNOME version:	2.15/2.16

Description v.simon 2006-11-22 19:28:11 UTC

Version: 2.16.1

What were you doing when the application crashed?
Trying to print from gedit with a probably badly configured local postscript printer.


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

Memory status: size: 61558784 vsize: 0 resident: 61558784 share: 0 rss: 24756224 rss_rlim: 0
CPU usage: start_time: 1164223505 rtime: 0 utime: 139 stime: 0 cutime:129 cstime: 0 timeout: 10 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 -1227426128 (LWP 25254)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 88570

Thread 1 (Thread -1227426128 (LWP 25254))

#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_print_job_print
from /usr/lib/libgnomeprint-2-2.so.0
#5 _gedit_tab_print
#6 g_cclosure_marshal_VOID__VOID
from /usr/lib/libgobject-2.0.so.0
#7 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#8 g_signal_chain_from_overridden
from /usr/lib/libgobject-2.0.so.0
#9 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#10 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#11 gtk_source_print_job_new_with_buffer
from /usr/lib/libgtksourceview-1.0.so.0
#12 g_source_set_closure
from /usr/lib/libgobject-2.0.so.0
#13 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#14 g_source_set_closure
from /usr/lib/libgobject-2.0.so.0
#15 g_source_is_destroyed
from /usr/lib/libglib-2.0.so.0
#16 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#17 g_main_context_check
from /usr/lib/libglib-2.0.so.0
#18 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#19 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#20 main
#0 __kernel_vsyscall

Comment 1 Steve Frécinaux 2006-11-25 15:08:39 UTC

Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers?


*** This bug has been marked as a duplicate of 376962 ***