Bug 454454 – crash in Text Editor: 1. Open gedit 2. Configu...

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 454454 - crash in Text Editor: 1. Open gedit 2. Configu...


Summary:	crash in Text Editor: 1. Open gedit 2. Configu...


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-07-07 03:35 UTC by andrey.arapov
Modified:	2007-07-10 17:57 UTC

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

Description andrey.arapov 2007-07-07 03:35:52 UTC

Version: 2.18.0

What were you doing when the application crashed?
1. Open gedit
2. Configured printer via http://127.0.0.1:631/ (cups web interface)
3. Print test page OK (via cups web interface)

4. Retrun to gedit - press Ctrl+P - gedit crashes...



Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.2 2007-05-28 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.21-1.3228.fc7 #1 SMP Wed Jul 4 02:13:04 VLAST 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 70200000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Mist
Icon Theme: Fedora

Memory status: size: 75227136 vsize: 75227136 resident: 25714688 share: 20275200 rss: 25714688 rss_rlim: 4294967295
CPU usage: start_time: 1183778632 rtime: 217 utime: 184 stime: 33 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 -1208391968 (LWP 27957)]
(no debugging symbols found)
0x00755402 in __kernel_vsyscall ()

+ Trace 146250

Thread 1 (Thread -1208391968 (LWP 27957))

#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
#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 ??
from /usr/lib/libgtk-x11-2.0.so.0
#27 g_closure_invoke
from /lib/libgobject-2.0.so.0
#28 ??
from /lib/libgobject-2.0.so.0
#29 g_signal_emit_valist
from /lib/libgobject-2.0.so.0
#30 g_signal_emit
from /lib/libgobject-2.0.so.0
#31 gtk_accel_group_activate
from /usr/lib/libgtk-x11-2.0.so.0
#32 gtk_accel_groups_activate
from /usr/lib/libgtk-x11-2.0.so.0
#33 gtk_window_activate_key
from /usr/lib/libgtk-x11-2.0.so.0
#34 ??
#35 ??
from /usr/lib/libgtk-x11-2.0.so.0
#36 ??
from /lib/libgobject-2.0.so.0
#37 g_closure_invoke
from /lib/libgobject-2.0.so.0
#38 ??
from /lib/libgobject-2.0.so.0
#39 g_signal_emit_valist
from /lib/libgobject-2.0.so.0
#40 g_signal_emit
from /lib/libgobject-2.0.so.0
#41 ??
from /usr/lib/libgtk-x11-2.0.so.0
#42 gtk_propagate_event
from /usr/lib/libgtk-x11-2.0.so.0
#43 gtk_main_do_event
from /usr/lib/libgtk-x11-2.0.so.0
#44 ??
from /usr/lib/libgdk-x11-2.0.so.0
#45 g_main_context_dispatch
from /lib/libglib-2.0.so.0
#46 ??
from /lib/libglib-2.0.so.0
#47 g_main_loop_run
from /lib/libglib-2.0.so.0
#48 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#49 main
#0 __kernel_vsyscall


No plugin installed in $HOME.





----------- .xsession-errors (8 sec old) ---------------------
** (gedit:27957): WARNING **: Writing output pipe failed
** (gedit:27957): WARNING **: Writing output pipe failed
** (gedit:27957): WARNING **: Writing output pipe failed
** (gedit:27957): WARNING **: Writing output pipe failed
** (gedit:27957): WARNING **: Writing output pipe failed
** (gedit:27957): WARNING **: Writing output pipe failed
(gedit:27957): libgnomeprintui-CRITICAL **: gnome_paper_selector_load_paper_size: assertion `GNOME_IS_PAPER_SELECTOR (ps)' failed
(gedit:27957): GLib-GObject-WARNING **: invalid uninstantiatable type `<invalid>' in cast to `GnomePrintConfig'
--------------------------------------------------

Comment 1 palfrey 2007-07-07 21:31: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 and
reopen this bug or report a new one. Thanks in advance!

Comment 2 André Klapper 2007-07-10 17:57:12 UTC

Tom, can you PLEASE use the simple-dup-finder?

Comment 3 André Klapper 2007-07-10 17:57:32 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 ***