Bug 516837 – crash in Text Editor: just opening a shell scr...

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 516837 - crash in Text Editor: just opening a shell scr...


Summary:	crash in Text Editor: just opening a shell scr...


Status:	RESOLVED DUPLICATE of bug 352099

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:	2008-02-16 12:37 UTC by martyn
Modified:	2008-02-16 14:29 UTC

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

Description martyn 2008-02-16 12:37:39 UTC

Version: 2.18.2

What were you doing when the application crashed?
just opening a shell script


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

System: Linux 2.6.23.8-34.fc7 #1 SMP Thu Nov 22 23:05:33 EST 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 168497152 vsize: 168497152 resident: 19476480 share: 14639104 rss: 19476480 rss_rlim: 4294967295
CPU usage: start_time: 1203165229 rtime: 111 utime: 81 stime: 30 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 -1208174880 (LWP 4881)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

+ Trace 189398

Thread 1 (Thread -1208174880 (LWP 4881))

#0 __kernel_vsyscall
#1 __waitpid_nocancel
from /lib/libpthread.so.0
#2 ??
from /usr/lib/libgnomeui-2.so.0
#3 <signal handler called>
#4 __kernel_vsyscall
#5 raise
from /lib/libc.so.6
#6 abort
from /lib/libc.so.6
#7 g_logv
from /lib/libglib-2.0.so.0
#8 g_log
from /lib/libglib-2.0.so.0
#9 g_malloc
from /lib/libglib-2.0.so.0
#10 g_convert_with_iconv
from /lib/libglib-2.0.so.0
#11 g_convert
from /lib/libglib-2.0.so.0
#12 ??
#13 gedit_convert_to_utf8
#14 ??
#15 ??
#16 ??
from /lib/libglib-2.0.so.0
#17 g_main_context_dispatch
from /lib/libglib-2.0.so.0
#18 ??
from /lib/libglib-2.0.so.0
#19 g_main_loop_run
from /lib/libglib-2.0.so.0
#20 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#21 main
#0 __kernel_vsyscall


No plugin installed in $HOME.

Module versions:
  - glib                  2.12.13
  - gtk+                  2.10.14
  - gtksourceview         
  - libgnomeui            
  - libglade              2.6.0
  - libgnomeprintui       
  - gnome-vfs             
  - pygobject             
  - pygtk                 
  - 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 (20 sec old) ---------------------
localuser:root being added to access control list
SESSION_MANAGER=local/unix:/tmp/.ICE-unix/2487
Window manager warning: Invalid WM_TRANSIENT_FOR window 0x4d specified for 0x100050c ().
** (nautilus-cd-burner:2732): WARNING **: Unable to prepare tracks for burning
** (nautilus-cd-burner:2806): WARNING **: Unable to prepare tracks for burning
gnome-mount 0.6
** (nautilus-cd-burner:2834): WARNING **: Unable to prepare tracks for burning
wine: could not load L"Z:\\root\\VP_Suite_Linux_3_2_20080206.sh": Bad EXE format for 
GLib-ERROR **: gmem.c:135: failed to allocate 128561631 bytes
aborting...
--------------------------------------------------

Comment 1 Gianluca Borello 2008-02-16 14:29:08 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 352099 ***