Bug 373170 – crash in GNOME Commander: searching for gladeui

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 373170 - crash in GNOME Commander: searching for gladeui


Summary:	crash in GNOME Commander: searching for gladeui


Status:	RESOLVED DUPLICATE of bug 356666

Product:	gnome-commander
Classification:	Other
Component:	application
Version:	1.2.x
Hardware:	Other All

Importance:	High critical
Target Milestone:	1.2.2
Assigned To:	epiotr
QA Contact:	epiotr

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2006-11-09 22:54 UTC by drufus2002
Modified:	2006-11-09 23:01 UTC

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

Description drufus2002 2006-11-09 22:54:38 UTC

Version: 1.2.0

What were you doing when the application crashed?
searching for gladeui


Distribution: Mandriva Linux release 2007.0 (Official) for i586
Gnome Release: 2.16.0 2006-09-04 (Mandriva)
BugBuddy Version: 2.16.0

Memory status: size: 67608576 vsize: 0 resident: 67608576 share: 0 rss: 39260160 rss_rlim: 0
CPU usage: start_time: 1163112728 rtime: 0 utime: 3210 stime: 0 cutime:1717 cstime: 0 timeout: 1493 it_real_value: 0 frequency: 0

Backtrace was generated from '/usr/bin/gnome-commander'

(no debugging symbols found)
Using host libthread_db library "/lib/i686/libthread_db.so.1".
(no debugging symbols found)
`shared object read from target memory' has disappeared; keeping its symbols.
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1226668352 (LWP 5313)]
[New Thread -1238922336 (LWP 5351)]
(no debugging symbols found)
0xbfffe410 in __kernel_vsyscall ()

+ Trace 84883

Thread 2 (Thread -1238922336 (LWP 5351))

#0 __kernel_vsyscall
#1 __waitpid_nocancel
from /lib/i686/libpthread.so.0
#2 gnome_gtk_module_info_get
from /usr/lib/libgnomeui-2.so.0
#3 <signal handler called>
#4 cairo_restore
from /usr/lib/libcairo.so.2
#5 pango_cairo_show_glyph_string
from /usr/lib/libpangocairo-1.0.so.0
#6 pango_renderer_draw_glyphs
from /usr/lib/libpango-1.0.so.0
#7 pango_cairo_renderer_get_type
from /usr/lib/libpangocairo-1.0.so.0
#8 gdk_draw_layout_line
from /usr/lib/libgdk-x11-2.0.so.0
#9 pango_renderer_draw_glyphs
from /usr/lib/libpango-1.0.so.0
#10 pango_renderer_draw_layout_line
from /usr/lib/libpango-1.0.so.0
#11 pango_renderer_draw_layout
from /usr/lib/libpango-1.0.so.0
#12 gdk_draw_layout_with_colors
from /usr/lib/libgdk-x11-2.0.so.0
#13 gdk_draw_layout
from /usr/lib/libgdk-x11-2.0.so.0
#14 ??
#15 gtk_clist_set_auto_sort
from /usr/lib/libgtk-x11-2.0.so.0
#16 gtk_clist_thaw
from /usr/lib/libgtk-x11-2.0.so.0
#17 ??
#18 ??
#19 ??
#20 g_cclosure_marshal_VOID__POINTER
from /usr/lib/libgobject-2.0.so.0
#21 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#22 g_signal_override_class_closure
from /usr/lib/libgobject-2.0.so.0
#23 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#24 gtk_signal_emit
from /usr/lib/libgtk-x11-2.0.so.0
#25 ??
#26 ??
#27 ??
#28 g_thread_create_full
from /usr/lib/libglib-2.0.so.0
#29 start_thread
from /lib/i686/libpthread.so.0
#30 clone
from /lib/i686/libc.so.6

Comment 1 Christian Kirbach 2006-11-09 23:01:50 UTC

Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers?


*** This bug has been marked as a duplicate of 356666 ***