Bug 396310 – crash in GNOME Commander: rename initrd.gz

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 396310 - crash in GNOME Commander: rename initrd.gz


Summary:	crash in GNOME Commander: rename initrd.gz


Status:	RESOLVED DUPLICATE of bug 364620

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

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

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2007-01-14 03:00 UTC by Friday Lee
Modified:	2007-01-18 23:17 UTC

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

Description Friday Lee 2007-01-14 03:00:57 UTC

Version: 1.2.0

What were you doing when the application crashed?
rename initrd.gz


Distribution: Ubuntu 6.10 (edgy)
Gnome Release: 2.16.1 2006-10-02 (Ubuntu)
BugBuddy Version: 2.16.0

Memory status: size: 67153920 vsize: 0 resident: 67153920 share: 0 rss: 20484096 rss_rlim: 0
CPU usage: start_time: 1168743578 rtime: 0 utime: 368 stime: 0 cutime:336 cstime: 0 timeout: 32 it_real_value: 0 frequency: 0

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

(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1225197904 (LWP 4682)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 101941

Thread 1 (Thread -1225197904 (LWP 4682))

#0 __kernel_vsyscall
#1 __waitpid_nocancel
from /lib/tls/i686/cmov/libpthread.so.0
#2 gnome_gtk_module_info_get
from /usr/lib/libgnomeui-2.so.0
#3 <signal handler called>
#4 FcFreeTypeCharIndex
from /usr/lib/libfontconfig.so.1
#5 pango_fc_font_lock_face
from /usr/lib/libpangoft2-1.0.so.0
#6 pango_fc_font_get_glyph
from /usr/lib/libpangoft2-1.0.so.0
#7 script_engine_init
from /usr/lib/pango/1.5.0/modules/pango-hangul-fc.so
#8 pango_coverage_new
from /usr/lib/libpango-1.0.so.0
#9 pango_shape
from /usr/lib/libpango-1.0.so.0
#10 pango_layout_set_width
from /usr/lib/libpango-1.0.so.0
#11 pango_layout_iter_get_char_extents
from /usr/lib/libpango-1.0.so.0
#12 pango_layout_iter_get_char_extents
from /usr/lib/libpango-1.0.so.0
#13 pango_layout_iter_get_char_extents
from /usr/lib/libpango-1.0.so.0
#14 pango_fc_font_create_metrics_for_context
from /usr/lib/libpangoft2-1.0.so.0
#15 pango_cairo_fc_font_get_type
from /usr/lib/libpangocairo-1.0.so.0
#16 pango_font_get_metrics
from /usr/lib/libpango-1.0.so.0
#17 text_render_get_display_mode
from /usr/lib/gnome-commander/libgviewer.so.0
#18 text_render_set_display_mode
from /usr/lib/gnome-commander/libgviewer.so.0
#19 gviewer_set_display_mode
from /usr/lib/gnome-commander/libgviewer.so.0
#20 gviewer_load_file
from /usr/lib/gnome-commander/libgviewer.so.0
#21 gviewer_window_load_file
from /usr/lib/gnome-commander/libgviewer.so.0
#22 gviewer_window_file_view
from /usr/lib/gnome-commander/libgviewer.so.0
#23 ??
#24 ??
#25 ??
#0 __kernel_vsyscall

Comment 1 André Klapper 2007-01-18 23:17:45 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 364620 ***