Bug 423996 – crash in Archive Manager: net

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 423996 - crash in Archive Manager: net


Summary:	crash in Archive Manager: net


Status:	RESOLVED INCOMPLETE

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:

Duplicates:	437399 440611 456444 (view as bug list)
Depends on:
Blocks:

Reported:	2007-03-29 03:50 UTC by yungying34
Modified:	2009-12-17 17:10 UTC

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

Description yungying34 2007-03-29 03:50:25 UTC

Version: 2.16.1

What were you doing when the application crashed?
net


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

Memory status: size: 34013184 vsize: 0 resident: 34013184 share: 0 rss: 14180352 rss_rlim: 0
CPU usage: start_time: 1175140203 rtime: 0 utime: 59 stime: 0 cutime:50 cstime: 0 timeout: 9 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 -1224907088 (LWP 10220)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 123111

Thread 1 (Thread -1224907088 (LWP 10220))

#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 Pedro Villavicencio 2007-05-10 13:35:50 UTC

*** Bug 437399 has been marked as a duplicate of this bug. ***

Comment 2 Pedro Villavicencio 2007-05-23 01:59:35 UTC

*** Bug 440611 has been marked as a duplicate of this bug. ***

Comment 3 André Klapper 2007-07-18 16:01:21 UTC

*** Bug 456444 has been marked as a duplicate of this bug. ***

Comment 4 André Klapper 2009-11-07 22:21:41 UTC

This crash report has not seen any changes or updates for more than 2 years.

Does this issue still happen in GNOME 2.26 or 2.28? Can you please update this report by adding a short comment, removing the NEEDINFO state again and updating the "Version" field if this is still an issue?

Again thank you for reporting this bug and we are sorry it could not be handled for the version you originally used here.

Comment 5 André Klapper 2009-12-17 17:10:32 UTC

Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for.
Thanks!