Bug 456444 – crash in Archive Manager: ติดตั้ง openoffice และ g...

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 456444 - crash in Archive Manager: ติดตั้ง openoffice และ g...


Summary:	crash in Archive Manager: ติดตั้ง openoffice และ g...


Status:	RESOLVED DUPLICATE of bug 423996

Product:	file-roller
Classification:	Applications
Component:	general
Version:	2.16.x
Hardware:	Other All

Importance:	High critical
Target Milestone:	---
Assigned To:	Paolo Bacchilega
QA Contact:	file-roller-maint

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2007-07-13 01:26 UTC by kaen_phai
Modified:	2007-07-18 16:01 UTC

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

Description kaen_phai 2007-07-13 01:26:06 UTC

Version: 2.16.1

What were you doing when the application crashed?
ติดตั้ง openoffice และ google earth ไม่เป็น


Distribution: LinuxTLE 8.0 (patong)
Gnome Release: 2.16.1 2006-10-02 (Ubuntu)
BugBuddy Version: 2.16.0

Memory status: size: 30375936 vsize: 0 resident: 30375936 share: 0 rss: 13246464 rss_rlim: 0
CPU usage: start_time: 1184289740 rtime: 0 utime: 45 stime: 0 cutime:42 cstime: 0 timeout: 3 it_real_value: 0 frequency: 0

Backtrace was generated from '/usr/bin/file-roller'

(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 -1224857936 (LWP 4689)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 147671

Thread 1 (Thread -1224857936 (LWP 4689))

#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 FcPatternDestroy
from /usr/lib/libfontconfig.so.1
#5 FcPatternHash
from /usr/lib/libfontconfig.so.1
#6 pango_fc_font_map_get_type
from /usr/lib/libpangoft2-1.0.so.0
#7 g_hash_table_lookup_extended
from /usr/lib/libglib-2.0.so.0
#8 pango_fc_font_map_get_type
from /usr/lib/libpangoft2-1.0.so.0
#9 pango_font_map_load_fontset
from /usr/lib/libpango-1.0.so.0
#10 pango_fc_font_map_get_type
from /usr/lib/libpangoft2-1.0.so.0
#11 pango_font_map_load_font
from /usr/lib/libpango-1.0.so.0
#12 pango_cairo_font_get_type
from /usr/lib/libpangocairo-1.0.so.0
#13 pango_cairo_font_get_type
from /usr/lib/libpangocairo-1.0.so.0
#14 pango_cairo_fc_font_get_type
from /usr/lib/libpangocairo-1.0.so.0
#15 pango_font_get_glyph_extents
from /usr/lib/libpango-1.0.so.0
#16 ??
from /usr/lib/pango/1.5.0/modules/pango-thai-fc.so
#17 ??
#18 ??
#19 ??
#20 ??
#21 ??
#22 ??
#0 __kernel_vsyscall

Comment 1 André Klapper 2007-07-18 16:01:21 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 423996 ***