Bug 406463 – crash in Text Editor: I send task to printer

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 406463 - crash in Text Editor: I send task to printer


Summary:	crash in Text Editor: I send task to printer


Status:	RESOLVED DUPLICATE of bug 405900

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

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

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2007-02-10 18:14 UTC by sszzz
Modified:	2007-02-10 19:54 UTC

See Also:
GNOME target:	---
GNOME version:	2.17/2.18

Description sszzz 2007-02-10 18:14:28 UTC

Version: 2.17.4

What were you doing when the application crashed?
I send task to printer


Distribution: Fedora release 6.90 (Rawhide)
Gnome Release: 2.17.90 2007-01-21 (Red Hat, Inc)
BugBuddy Version: 2.17.3

System: Linux 2.6.20-1.2922.fc7 #1 SMP Sun Feb 4 18:53:10 EST 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 70200000
Selinux: No
Accessibility: Disabled

Memory status: size: 101470208 vsize: 0 resident: 101470208 share: 0 rss: 21524480 rss_rlim: 0
CPU usage: start_time: 1171130541 rtime: 0 utime: 167 stime: 0 cutime:146 cstime: 0 timeout: 21 it_real_value: 0 frequency: 0

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

(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1208424736 (LWP 14335)]
(no debugging symbols found)
0x0068c402 in __kernel_vsyscall ()

+ Trace 109590

Thread 1 (Thread -1208424736 (LWP 14335))

#0 __kernel_vsyscall
#1 waitpid
from /lib/libpthread.so.0
#2 ??
from /usr/lib/libgnomeui-2.so.0
#3 <signal handler called>
#4 gpa_node_set_path_value
from /usr/lib/libgnomeprint-2-2.so.0
#5 gnome_print_config_set
from /usr/lib/libgnomeprint-2-2.so.0
#6 gnome_print_config_set_int
from /usr/lib/libgnomeprint-2-2.so.0
#7 ??
#8 g_cclosure_marshal_VOID__PARAM
from /lib/libgobject-2.0.so.0
#9 g_closure_invoke
from /lib/libgobject-2.0.so.0
#10 ??
from /lib/libgobject-2.0.so.0
#11 g_signal_emit_valist
from /lib/libgobject-2.0.so.0
#12 g_signal_emit
from /lib/libgobject-2.0.so.0
#13 ??
from /lib/libgobject-2.0.so.0
#14 ??
from /lib/libgobject-2.0.so.0
#15 g_object_newv
from /lib/libgobject-2.0.so.0
#16 g_object_new_valist
from /lib/libgobject-2.0.so.0
#17 g_object_new
from /lib/libgobject-2.0.so.0
#18 gedit_print_job_new
#19 _gedit_cmd_file_print
#20 g_cclosure_marshal_VOID__VOID
from /lib/libgobject-2.0.so.0
#21 g_closure_invoke
from /lib/libgobject-2.0.so.0
#22 ??
from /lib/libgobject-2.0.so.0
#23 g_signal_emit_valist
from /lib/libgobject-2.0.so.0
#24 g_signal_emit
from /lib/libgobject-2.0.so.0
#25 ??
from /usr/lib/libgtk-x11-2.0.so.0
#26 gtk_action_activate
from /usr/lib/libgtk-x11-2.0.so.0
#27 g_cclosure_marshal_VOID__VOID
from /lib/libgobject-2.0.so.0
#28 g_closure_invoke
from /lib/libgobject-2.0.so.0
#29 ??
from /lib/libgobject-2.0.so.0
#30 g_signal_emit_valist
from /lib/libgobject-2.0.so.0
#31 g_signal_emit_by_name
from /lib/libgobject-2.0.so.0
#32 ??
from /usr/lib/libgtk-x11-2.0.so.0
#33 g_cclosure_marshal_VOID__VOID
from /lib/libgobject-2.0.so.0
#34 g_closure_invoke
from /lib/libgobject-2.0.so.0
#35 ??
from /lib/libgobject-2.0.so.0
#36 g_signal_emit_valist
from /lib/libgobject-2.0.so.0
#37 g_signal_emit
from /lib/libgobject-2.0.so.0
#38 gtk_button_clicked
from /usr/lib/libgtk-x11-2.0.so.0
#39 ??
from /usr/lib/libgtk-x11-2.0.so.0
#40 g_cclosure_marshal_VOID__VOID
from /lib/libgobject-2.0.so.0
#41 ??
from /lib/libgobject-2.0.so.0
#42 g_closure_invoke
from /lib/libgobject-2.0.so.0
#43 ??
from /lib/libgobject-2.0.so.0
#44 g_signal_emit_valist
from /lib/libgobject-2.0.so.0
#45 g_signal_emit
from /lib/libgobject-2.0.so.0
#46 gtk_button_released
from /usr/lib/libgtk-x11-2.0.so.0
#47 ??
from /usr/lib/libgtk-x11-2.0.so.0
#48 ??
from /usr/lib/libgtk-x11-2.0.so.0
#49 ??
from /lib/libgobject-2.0.so.0
#50 g_closure_invoke
from /lib/libgobject-2.0.so.0
#51 ??
from /lib/libgobject-2.0.so.0
#52 g_signal_emit_valist
from /lib/libgobject-2.0.so.0
#53 g_signal_emit
from /lib/libgobject-2.0.so.0
#54 ??
from /usr/lib/libgtk-x11-2.0.so.0
#55 gtk_propagate_event
from /usr/lib/libgtk-x11-2.0.so.0
#56 gtk_main_do_event
from /usr/lib/libgtk-x11-2.0.so.0
#57 ??
from /usr/lib/libgdk-x11-2.0.so.0
#58 g_main_context_dispatch
from /lib/libglib-2.0.so.0
#59 ??
from /lib/libglib-2.0.so.0
#60 g_main_loop_run
from /lib/libglib-2.0.so.0
#61 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#62 main
#0 __kernel_vsyscall



----------- .xsession-errors (7392 sec old) ---------------------
==========================================================================
Opening audio decoder: [liba52] AC3 decoding with liba52
Using SSE optimized IMDCT transform
Using MMX optimized resampler
AUDIO: 48000 Hz, 2 ch, s16le, 192,0 kbit/12,50% (ratio: 24000->192000)
Selected audio codec: [a52] afm: liba52 (AC3-liba52)
==========================================================================
AO: [oss] 48000Hz 2ch s16le (2 bytes per sample)
Starting playback...
VDec: vo config request - 720 x 576 (preferred colorspace: Planar YV12)
VDec: using Planar YV12 as output csp (no 0)
Movie-Aspect is 1,33:1 - prescaling to correct movie aspect.
VO: [xv] 720x576 => 768x576 Planar YV12 
A:   0,2 V:   0,0 A-V:  0,121 ct:  0,000   1/  1 ??% ??% ??,?% 0 0              
A:   0,2 V:   0,1 A-V:  0,120 ct:  0,004   2/  2 ??% ??% ??,?% 0 0              
A:   0,2 V:   0,1 A-V:  0,086 ct:  0,0
...Too much output, ignoring rest...
--------------------------------------------------

Comment 1 Susana 2007-02-10 19:54:27 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 405900 ***