Bug 500314 – crash in Text Editor: Trying to print a text f...

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 500314 - crash in Text Editor: Trying to print a text f...


Summary:	crash in Text Editor: Trying to print a text f...


Status:	RESOLVED DUPLICATE of bug 405900

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-11-28 22:52 UTC by stephanie.wurdinger
Modified:	2007-12-25 12:02 UTC

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

Description stephanie.wurdinger 2007-11-28 22:52:18 UTC

Version: 2.18.2

What were you doing when the application crashed?
Trying to print a text file


Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.3 2007-07-02 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.23.1-21.fc7 #1 SMP Thu Nov 1 21:09:24 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Permissive
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 75255808 vsize: 75255808 resident: 30642176 share: 21041152 rss: 30642176 rss_rlim: 4294967295
CPU usage: start_time: 1196289725 rtime: 430 utime: 391 stime: 39 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 "/lib/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1208277280 (LWP 4013)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

+ Trace 180028

Thread 1 (Thread -1208277280 (LWP 4013))

#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
from /lib/libgobject-2.0.so.0
#32 gtk_widget_activate
from /usr/lib/libgtk-x11-2.0.so.0
#33 gtk_menu_shell_activate_item
from /usr/lib/libgtk-x11-2.0.so.0
#34 ??
from /usr/lib/libgtk-x11-2.0.so.0
#35 ??
from /usr/lib/libgtk-x11-2.0.so.0
#36 ??
from /usr/lib/libgtk-x11-2.0.so.0
#37 ??
from /lib/libgobject-2.0.so.0
#38 g_closure_invoke
from /lib/libgobject-2.0.so.0
#39 ??
from /lib/libgobject-2.0.so.0
#40 g_signal_emit_valist
from /lib/libgobject-2.0.so.0
#41 g_signal_emit
from /lib/libgobject-2.0.so.0
#42 ??
from /usr/lib/libgtk-x11-2.0.so.0
#43 gtk_propagate_event
from /usr/lib/libgtk-x11-2.0.so.0
#44 gtk_main_do_event
from /usr/lib/libgtk-x11-2.0.so.0
#45 ??
from /usr/lib/libgdk-x11-2.0.so.0
#46 g_main_context_dispatch
from /lib/libglib-2.0.so.0
#47 ??
from /lib/libglib-2.0.so.0
#48 g_main_loop_run
from /lib/libglib-2.0.so.0
#49 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#50 main
#0 __kernel_vsyscall


No plugin installed in $HOME.

Module versions:
  - glib                  2.12.13
  - gtk+                  2.10.14
  - gtksourceview         1.8.5
  - libgnomeui            2.18.1
  - libglade              2.6.0
  - libgnomeprintui       2.18.0
  - gnome-vfs             2.18.1
  - pygobject             2.12.3
  - pygtk                 2.10.6
  - gnome-python          
  - gnome-python-desktop  2.18.0
  - enchant               
  - iso-codes             

Python module versions:
  - python                2.5
  - pygtk                 2.10.6 (GTK+ 2.10.14)
  - gnome-python          2.18.1





----------- .xsession-errors (10 sec old) ---------------------
** (gedit:4013): WARNING **: could not set the value of Settings.Document.Filter, node not found
(gedit:4013): libgnomeprintui-CRITICAL **: gnome_paper_selector_load_paper_size: assertion `GNOME_IS_PAPER_SELECTOR (ps)' failed
(gedit:4013): libgnomeprintui-CRITICAL **: gnome_paper_selector_load_paper_size: assertion `GNOME_IS_PAPER_SELECTOR (ps)' failed
** (gedit:4013): WARNING **: could not set the value of Settings.Document.Filter, node not found
(gedit:4013): libgnomeprintui-CRITICAL **: gnome_paper_selector_load_paper_size: assertion `GNOME_IS_PAPER_SELECTOR (ps)' failed
(gedit:4013): libgnomeprintui-CRITICAL **: gnome_paper_selector_load_paper_size: assertion `GNOME_IS_PAPER_SELECTOR (ps)' failed
** (gedit:4013): WARNING **: could not set the value of Settings.Document.Filter, node not found
(gedit:4013): GLib-GObject-WARNING **: invalid uninstantiatable type `(null)' in cast to `GnomePrintConfig'
--------------------------------------------------

Comment 1 Teppo Turtiainen 2007-12-25 12:02:30 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 405900 ***