Bug 437238 – crash in Text Editor:

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 437238 - crash in Text Editor:


Summary:	crash in Text Editor:


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:

Duplicates:	443291 445394 445851 455954 460740 474769 (view as bug list)
Depends on:
Blocks:

Reported:	2007-05-09 18:01 UTC by j.w.janssen
Modified:	2007-11-27 09:47 UTC

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

Description j.w.janssen 2007-05-09 18:01:36 UTC

Version: 2.18.1

What were you doing when the application crashed?



Distribution: Debian lenny/sid
Gnome Release: 2.18.1 2007-04-25 (Debian)
BugBuddy Version: 2.18.1

System: Linux 2.6.18-3-amd64 #1 SMP Sun Dec 10 19:57:44 CET 2006 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Gorilla
Icon Theme: Gorilla

Memory status: size: 192000000 vsize: 192000000 resident: 27234304 share: 15233024 rss: 27234304 rss_rlim: 18446744073709551615
CPU usage: start_time: 1178733638 rtime: 137 utime: 127 stime: 10 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 47470320787776 (LWP 4296)]
(no debugging symbols found)
0x00002b2c85281c9f in waitpid () from /lib/libpthread.so.0

+ Trace 133314

Thread 1 (Thread 47470320787776 (LWP 4296))

#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                  
  - gtk+                  
  - gtksourceview         
  - libgnomeui            
  - libglade              
  - libgnomeprintui       
  - gnome-vfs             
  - pygobject             
  - pygtk                 
  - gnome-python          
  - gnome-python-desktop  
  - enchant               
  - iso-codes             1.0

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





----------- .xsession-errors (438 sec old) ---------------------
** (gedit:4296): WARNING **: IPP request failed with status 1280
** (gedit:4296): WARNING **: IPP request failed with status 1280
** (gedit:4296): WARNING **: IPP request failed with status 1280
** (gedit:4296): WARNING **: IPP request failed with status 1280
** (gedit:4296): WARNING **: IPP request failed with status 1280
** (gedit:4296): WARNING **: IPP request failed with status 1280
** (gedit:4296): WARNING **: IPP request failed with status 1280
(gedit:4296): GLib-GObject-WARNING **: invalid uninstantiatable type `(null)' in cast to `GnomePrintConfig'
--------------------------------------------------

Comment 1 j.w.janssen 2007-05-09 20:51:12 UTC

Fairly good to reproduce: 

- open gedit;
- open print dialog;
  - select option "lp (via lpr)" (other options are Generic PS and Create PDF);
  - choose "configure" settings, deselect "duplex" and close this dialog;
- cancel print dialog;
- type something in the editor;
- open print dialog => crash

Comment 2 palfrey 2007-05-10 13:46:56 UTC

Thanks for taking the time to report this bug.
Unfortunately, that stack trace is missing some elements that will help a lot
to solve the problem, so it will be hard for the developers to fix that crash.
Can you get us a stack trace with debugging symbols? Please see
http://live.gnome.org/GettingTraces for more information on how to do so.
Thanks in advance!

Comment 3 palfrey 2007-06-02 23:35:52 UTC

*** Bug 443291 has been marked as a duplicate of this bug. ***

Comment 4 Pascal Terjan 2007-06-10 19:41:51 UTC

*** Bug 445394 has been marked as a duplicate of this bug. ***

Comment 5 Pascal Terjan 2007-06-10 19:42:40 UTC

*** Bug 445851 has been marked as a duplicate of this bug. ***

Comment 6 palfrey 2007-07-12 11:23:25 UTC

*** Bug 455954 has been marked as a duplicate of this bug. ***

Comment 7 Iestyn Pryce 2007-07-27 08:38:07 UTC

*** Bug 460740 has been marked as a duplicate of this bug. ***

Comment 8 Cosimo Cecchi 2007-09-11 00:06:30 UTC

*** Bug 474769 has been marked as a duplicate of this bug. ***

Comment 9 André Klapper 2007-11-27 09:47:31 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 ***