Bug 470376 – crash in Text Editor: About to do a second pri...

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 470376 - crash in Text Editor: About to do a second pri...


Summary:	crash in Text Editor: About to do a second pri...


Status:	RESOLVED DUPLICATE of bug 448751

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-08-26 08:45 UTC by simon
Modified:	2007-09-05 17:53 UTC

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

Description simon 2007-08-26 08:45:26 UTC

Version: 2.18.1

What were you doing when the application crashed?
About to do a second printing of the page open


Distribution: Gentoo Base System release 1.12.9
Gnome Release: 2.18.2 2007-08-21 (Gentoo)
BugBuddy Version: 2.18.1

System: Linux 2.6.21.5 #1 Wed Jun 27 22:21:01 BST 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 70200000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome

Memory status: size: 204931072 vsize: 204931072 resident: 35233792 share: 24793088 rss: 35233792 rss_rlim: 18446744073709551615
CPU usage: start_time: 1188117154 rtime: 808 utime: 764 stime: 44 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 47982839259584 (LWP 6129)]
0x00002ba3dbd78b0f in waitpid () from /lib/libpthread.so.0

+ Trace 157962

Thread 1 (Thread 47982839259584 (LWP 6129))

#0 waitpid
from /lib/libpthread.so.0
#1 ??
from /usr/lib/libgnomeui-2.so.0
#2 <signal handler called>
#3 gpa_node_set_path_value
from /usr/lib/libgnomeprint-2-2.so.0
#4 gnome_print_config_set_int
from /usr/lib/libgnomeprint-2-2.so.0
#5 ??
#6 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#7 ??
from /usr/lib/libgobject-2.0.so.0
#8 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#9 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#10 ??
from /usr/lib/libgobject-2.0.so.0
#11 g_object_newv
from /usr/lib/libgobject-2.0.so.0
#12 g_object_new_valist
from /usr/lib/libgobject-2.0.so.0
#13 g_object_new
from /usr/lib/libgobject-2.0.so.0
#14 gedit_print_job_new
#15 _gedit_cmd_file_print
#16 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#17 ??
from /usr/lib/libgobject-2.0.so.0
#18 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#19 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#20 ??
from /usr/lib/libgtk-x11-2.0.so.0
#21 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#22 ??
from /usr/lib/libgobject-2.0.so.0
#23 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#24 g_signal_emit_by_name
from /usr/lib/libgobject-2.0.so.0
#25 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#26 ??
from /usr/lib/libgobject-2.0.so.0
#27 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#28 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#29 ??
from /usr/lib/libgtk-x11-2.0.so.0
#30 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#31 ??
from /usr/lib/libgobject-2.0.so.0
#32 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#33 g_signal_emit
from /usr/lib/libgobject-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 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#37 ??
from /usr/lib/libgobject-2.0.so.0
#38 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#39 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#40 ??
from /usr/lib/libgtk-x11-2.0.so.0
#41 gtk_propagate_event
from /usr/lib/libgtk-x11-2.0.so.0
#42 gtk_main_do_event
from /usr/lib/libgtk-x11-2.0.so.0
#43 ??
from /usr/lib/libgdk-x11-2.0.so.0
#44 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#45 ??
from /usr/lib/libglib-2.0.so.0
#46 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#47 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#48 main
#0 waitpid
from /lib/libpthread.so.0


No plugin installed in $HOME.

Module versions:
  - glib                  2.12.12
  - gtk+                  2.10.13
  - gtksourceview         1.8.5
  - libgnomeui            2.18.1
  - libglade              2.6.1
  - libgnomeprintui       2.18.0
  - gnome-vfs             2.18.1
  - pygobject             2.12.3
  - pygtk                 2.10.4
  - gnome-python          2.18.2
  - gnome-python-desktop  2.18.0
  - enchant               1.2.5
  - iso-codes             0.58

Python module versions:
  - python                2.4.4
  - pygtk                 2.10.4 (GTK+ 2.10.13)
  - gnome-python          2.18.2





----------- .xsession-errors (639 sec old) ---------------------
Debug: Loading Beagle.Util.Conf+SearchingConfig from searching.xml
** Message: drive = 0
** Message: volume = 0
Unhandled Exception: System.TypeInitializationException: An exception was thrown by the type initializer for Evolution.SourceList ---> System.DllNotFoundException: libedataserver-1.2.so.7
  at (wrapper managed-to-native) Evolution.Source:e_source_get_type ()
  at Evolution.Source.get_GType () [0x00000] 
  at GtkSharp.EvolutionSharp.ObjectManager.Initialize () [0x00000] 
  at Evolution.SourceList..cctor () [0x00000] --- End of inner exception stack trace ---
  at <0x00000> <unknown method>
  at Beagle.Daemon.EvolutionDataServerQueryable.SourcesHandler..ctor (System.String gconf_key, System.Type container_type, Beagle.Daemon.EvolutionDataServerQueryable.EvolutionDataServerQueryable query
CalDAV Eplugin starting up ...
No running windows found
/usr/share/themes/Clearlooks/gtk-2.0/gtkrc:63: error: unexpected identifier `style', expected character `}'
--------------------------------------------------

Comment 1 palfrey 2007-09-05 17:53:16 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 448751 ***