Bug 493445 – 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 493445 - 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:

Depends on:
Blocks:

Reported:	2007-11-04 17:39 UTC by lakhterman
Modified:	2007-11-05 08:53 UTC

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

Description lakhterman 2007-11-04 17:39:22 UTC

Version: 2.18.2

What were you doing when the application crashed?



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.21-1.3194.fc7 #1 SMP Wed May 23 22:35:01 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Crux
Icon Theme: Echo

Memory status: size: 114311168 vsize: 114311168 resident: 45002752 share: 34365440 rss: 45002752 rss_rlim: 4294967295
CPU usage: start_time: 1194197377 rtime: 395 utime: 339 stime: 56 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 -1208883488 (LWP 5507)]
(no debugging symbols found)
0x001c7402 in __kernel_vsyscall ()

+ Trace 175165

Thread 1 (Thread -1208883488 (LWP 5507))

#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_preview
#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         
  - 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 (458067 sec old) ---------------------
 Genre: Lo-Fi
==========================================================================
Opening audio decoder: [mp3lib] MPEG layer-2, layer-3
AUDIO: 44100 Hz, 2 ch, s16le, 128.0 kbit/9.07% (ratio: 16000->176400)
Selected audio codec: [mp3] afm: mp3lib (mp3lib MPEG layer-2, layer-3)
==========================================================================
[AO OSS] audio_setup: Can't open audio device /dev/dsp: Device or resource busy
** Message: Could not connect to power manager: Could not get owner of name 'org.gnome.PowerManager': no such name
AO: [alsa] 48000Hz 2ch s16le (2 bytes per sample)
Video: no video
Starting playback...
A:   0.0 (00.0) of 542.0 (09:02.0) ??,?%                                        
A:   0.0 (00.0) of 542.0 (09:02.0) ??,?%                                        
A:   0.1 (00.0) of 542.0 (09:02.0) ??,
Reusing existing ksycoca
A:   0.7 (00.6) of 542.0 (09:02.0)  1.3%                                        
A:   0.7 (00.6) of 542.0 (09:02.0)  1.4%                                        
A:   0.7 (00.7) of 542.0 (09:02.0)  1.
...Too much output, ignoring rest...
--------------------------------------------------

Comment 1 Christoph Wolk 2007-11-05 08:53:21 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 ***