Bug 433631 – crash in Text Editor: rien

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


Summary:	crash in Text Editor: rien


Status:	RESOLVED DUPLICATE of bug 352099

Product:	gedit
Classification:	Applications
Component:	general
Version:	2.15.x
Hardware:	Other All

Importance:	High critical
Target Milestone:	---
Assigned To:	Gedit maintainers
QA Contact:	Gedit maintainers

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2007-04-26 15:53 UTC by mohamed_daoudi
Modified:	2007-04-26 16:02 UTC

See Also:
GNOME target:	---
GNOME version:	2.15/2.16

Description mohamed_daoudi 2007-04-26 15:53:47 UTC

Version: 2.15.9

What were you doing when the application crashed?
rien


Distribution: Fedora Core release 6 (Zod)
Gnome Release: 2.16.0 2006-09-04 (Red Hat, Inc)
BugBuddy Version: 2.16.0

System: Linux 2.6.18-1.2798.fc6 #1 SMP Mon Oct 16 14:54:20 EDT 2006 i686
X Vendor: The X.Org Foundation
X Vendor Release: 70101000
Selinux: Enforcing
Accessibility: Disabled

Memory status: size: 1300770816 vsize: 0 resident: 1300770816 share: 0 rss: 934002688 rss_rlim: 0
CPU usage: start_time: 1177602654 rtime: 0 utime: 641 stime: 0 cutime:511 cstime: 0 timeout: 130 it_real_value: 0 frequency: 0

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 -1208255744 (LWP 4740)]
(no debugging symbols found)
0x0061d402 in __kernel_vsyscall ()

+ Trace 130717

Thread 1 (Thread -1208255744 (LWP 4740))

#0 __kernel_vsyscall
#1 __waitpid_nocancel
from /lib/libpthread.so.0
#2 gnome_gtk_module_info_get
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_strndup
from /lib/libglib-2.0.so.0
#11 gedit_convert_from_utf8
#12 gedit_convert_to_utf8
#13 gedit_document_new
#14 gedit_document_new
#15 g_source_get_current_time
from /lib/libglib-2.0.so.0
#16 g_main_context_dispatch
from /lib/libglib-2.0.so.0
#17 g_main_context_check
from /lib/libglib-2.0.so.0
#18 g_main_loop_run
from /lib/libglib-2.0.so.0
#19 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#20 main
#0 __kernel_vsyscall



----------- .xsession-errors (359 sec old) ---------------------
** (gnome-terminal:2850): WARNING **: Aucune manipulation définie pour la séquence de contrôle « device-control-string ».
** (gnome-terminal:2850): WARNING **: Aucune manipulation définie pour la séquence de contrôle « device-control-string ».
** (gnome-terminal:2850): WARNING **: Aucune manipulation définie pour la séquence de contrôle « device-control-string ».
** (gnome-terminal:2850): WARNING **: Aucune manipulation définie pour la séquence de contrôle « device-control-string ».
** (gnome-terminal:2850): WARNING **: Aucune manipulation définie pour la séquence de contrôle « device-control-string ».
** (gnome-terminal:2850): WARNING **: Aucune manipulation définie pour la séquence de contrôle « device-control-string ».
Avertissement du gestionnaire de fenêtres : Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x3a00003 (Visionneur)
Avertissement du gestionnaire de fenêtres : meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
Avertissement du gestionnaire de fenêtres : Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x3a00053 (Visionneur)
Avertissement du gestionnaire de fenêtres : meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
--------------------------------------------------

Comment 1 palfrey 2007-04-26 16:02:10 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 ***