Bug 473414 – crash in Text Editor: trying to print.... also...

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 473414 - crash in Text Editor: trying to print.... also...


Summary:	crash in Text Editor: trying to print.... also...


Status:	RESOLVED DUPLICATE of bug 443083

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

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

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2007-09-04 02:09 UTC by adrian
Modified:	2007-09-05 17:57 UTC

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

Description adrian 2007-09-04 02:09:40 UTC

Version: 2.18.0

What were you doing when the application crashed?
trying to print.... also my printer doesn't works after updete system fc6


Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.0 2007-03-23 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.21-1.3194.fc7 #1 SMP Wed May 23 22:47:07 EDT 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Enforcing
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 352911360 vsize: 352911360 resident: 29888512 share: 20025344 rss: 29888512 rss_rlim: 18446744073709551615
CPU usage: start_time: 1188871014 rtime: 134 utime: 113 stime: 21 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

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

(no debugging symbols found)
Using host libthread_db library "/lib64/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 46912496419696 (LWP 3292)]
(no debugging symbols found)
0x0000003c4bc0d89f in waitpid () from /lib64/libpthread.so.0

+ Trace 160273

Thread 1 (Thread 46912496419696 (LWP 3292))

#0 waitpid
from /lib64/libpthread.so.0
#1 g_free
from /usr/lib64/libgnomeui-2.so.0
#2 <signal handler called>
#3 gnome_print_config_unref
from /usr/lib64/libgnomeprint-2-2.so.0
#4 g_datalist_clear
from /lib64/libglib-2.0.so.0
#5 ??
#6 g_object_unref
from /lib64/libgobject-2.0.so.0
#7 gtk_text_layout_set_buffer
from /usr/lib64/libgtk-x11-2.0.so.0
#8 g_free
from /usr/lib64/libgtk-x11-2.0.so.0
#9 g_object_unref
from /lib64/libgobject-2.0.so.0
#10 g_free
from /usr/lib64/libgtk-x11-2.0.so.0
#11 g_free
from /usr/lib64/libgtk-x11-2.0.so.0
#12 g_closure_invoke
from /lib64/libgobject-2.0.so.0
#13 g_free
from /lib64/libgobject-2.0.so.0
#14 g_signal_emit_valist
from /lib64/libgobject-2.0.so.0
#15 g_signal_emit
from /lib64/libgobject-2.0.so.0
#16 g_free
from /usr/lib64/libgtk-x11-2.0.so.0
#17 g_object_run_dispose
from /lib64/libgobject-2.0.so.0
#18 g_free
from /usr/lib64/libgtk-x11-2.0.so.0
#19 g_free
from /usr/lib64/libgtk-x11-2.0.so.0
#20 g_closure_invoke
from /lib64/libgobject-2.0.so.0
#21 g_free
from /lib64/libgobject-2.0.so.0
#22 g_signal_emit_valist
from /lib64/libgobject-2.0.so.0
#23 g_signal_emit
from /lib64/libgobject-2.0.so.0
#24 g_free
from /usr/lib64/libgtk-x11-2.0.so.0
#25 g_object_run_dispose
from /lib64/libgobject-2.0.so.0
#26 g_free
from /usr/lib64/libgtk-x11-2.0.so.0
#27 g_free
from /usr/lib64/libgtk-x11-2.0.so.0
#28 g_closure_invoke
from /lib64/libgobject-2.0.so.0
#29 g_free
from /lib64/libgobject-2.0.so.0
#30 g_signal_emit_valist
from /lib64/libgobject-2.0.so.0
#31 g_signal_emit
from /lib64/libgobject-2.0.so.0
#32 g_free
from /usr/lib64/libgtk-x11-2.0.so.0
#33 g_object_unref
from /lib64/libgobject-2.0.so.0
#34 g_free
from /usr/lib64/libgtk-x11-2.0.so.0
#35 gedit_window_close_all_tabs
#36 ??
#37 g_closure_invoke
from /lib64/libgobject-2.0.so.0
#38 g_free
from /lib64/libgobject-2.0.so.0
#39 g_signal_emit_valist
from /lib64/libgobject-2.0.so.0
#40 g_signal_emit
from /lib64/libgobject-2.0.so.0
#41 g_closure_invoke
from /lib64/libgobject-2.0.so.0
#42 g_free
from /lib64/libgobject-2.0.so.0
#43 g_signal_emit_valist
from /lib64/libgobject-2.0.so.0
#44 g_signal_emit
from /lib64/libgobject-2.0.so.0
#45 g_free
from /usr/lib64/libgtk-x11-2.0.so.0
#46 g_closure_invoke
from /lib64/libgobject-2.0.so.0
#47 g_free
from /lib64/libgobject-2.0.so.0
#48 g_signal_emit_valist
from /lib64/libgobject-2.0.so.0
#49 g_signal_emit
from /lib64/libgobject-2.0.so.0
#50 g_free
from /usr/lib64/libgtk-x11-2.0.so.0
#51 g_free
from /usr/lib64/libgtk-x11-2.0.so.0
#52 g_closure_invoke
from /lib64/libgobject-2.0.so.0
#53 g_free
from /lib64/libgobject-2.0.so.0
#54 g_signal_emit_valist
from /lib64/libgobject-2.0.so.0
#55 g_signal_emit
from /lib64/libgobject-2.0.so.0
#56 g_free
from /usr/lib64/libgtk-x11-2.0.so.0
#57 gtk_propagate_event
from /usr/lib64/libgtk-x11-2.0.so.0
#58 gtk_main_do_event
from /usr/lib64/libgtk-x11-2.0.so.0
#59 g_free
from /usr/lib64/libgdk-x11-2.0.so.0
#60 g_main_context_dispatch
from /lib64/libglib-2.0.so.0
#61 g_free
from /lib64/libglib-2.0.so.0
#62 g_main_loop_run
from /lib64/libglib-2.0.so.0
#63 gtk_main
from /usr/lib64/libgtk-x11-2.0.so.0
#64 main
#0 waitpid
from /lib64/libpthread.so.0


No plugin installed in $HOME.





----------- .xsession-errors (48 sec old) ---------------------
ImportError: No module named cups
Loading "installonlyn" plugin
Traceback (most recent call last):
  File "/usr/share/system-config-printer/system-config-printer.py", line 40, in <module>
    import cups
ImportError: No module named cups
Traceback (most recent call last):
  File "/usr/share/system-config-printer/system-config-printer.py", line 40, in <module>
    import cups
ImportError: No module named cups
** (gedit:3292): WARNING **: IPP request failed with status 1280
** (gedit:3292): WARNING **: IPP request failed with status 1280
Model not found, discarding config
--------------------------------------------------

Comment 1 palfrey 2007-09-05 17:57:45 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 443083 ***