Bug 367332 – crash in Archive Manager: trying to extract fonts ...

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 367332 - crash in Archive Manager: trying to extract fonts ...


Summary:	crash in Archive Manager: trying to extract fonts ...


Status:	RESOLVED DUPLICATE of bug 357188

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:	2006-10-30 01:48 UTC by christopher.lloyd
Modified:	2006-10-30 02:12 UTC

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

Description christopher.lloyd 2006-10-30 01:48:09 UTC

Version: 2.16.0

What were you doing when the application crashed?
trying to extract fonts to ¨fonts:///¨


Distribution: Fedora Core release 6 (Zod)
Gnome Release: 2.16.0 2006-09-04 (Red Hat, Inc)
BugBuddy Version: 2.16.0

Memory status: size: 78135296 vsize: 0 resident: 78135296 share: 0 rss: 17002496 rss_rlim: 0
CPU usage: start_time: 1162172641 rtime: 0 utime: 242 stime: 0 cutime:212 cstime: 0 timeout: 30 it_real_value: 0 frequency: 0

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

(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 -1208514864 (LWP 5209)]
(no debugging symbols found)
0x003c8402 in __kernel_vsyscall ()

+ Trace 80167

Thread 1 (Thread -1208514864 (LWP 5209))

#0 __kernel_vsyscall
#1 __waitpid_nocancel
from /lib/libpthread.so.0
#2 gnome_gtk_module_info_get
from /usr/lib/libgnomeui-2.so.0
#3 <signal handler called>
#4 g_utf8_validate
from /lib/libglib-2.0.so.0
#5 g_filename_display_name
from /lib/libglib-2.0.so.0
#6 g_cclosure_marshal_VOID__BOOLEAN
#7 g_cclosure_marshal_VOID__VOID
from /lib/libgobject-2.0.so.0
#8 g_closure_invoke
from /lib/libgobject-2.0.so.0
#9 g_signal_override_class_closure
from /lib/libgobject-2.0.so.0
#10 g_signal_emit_valist
from /lib/libgobject-2.0.so.0
#11 g_signal_emit
from /lib/libgobject-2.0.so.0
#12 gtk_button_clicked
from /usr/lib/libgtk-x11-2.0.so.0
#13 gtk_button_set_alignment
from /usr/lib/libgtk-x11-2.0.so.0
#14 g_cclosure_marshal_VOID__VOID
from /lib/libgobject-2.0.so.0
#15 g_value_set_static_boxed
from /lib/libgobject-2.0.so.0
#16 g_closure_invoke
from /lib/libgobject-2.0.so.0
#17 g_signal_override_class_closure
from /lib/libgobject-2.0.so.0
#18 g_signal_emit_valist
from /lib/libgobject-2.0.so.0
#19 g_signal_emit
from /lib/libgobject-2.0.so.0
#20 gtk_button_released
from /usr/lib/libgtk-x11-2.0.so.0
#21 gtk_button_released
from /usr/lib/libgtk-x11-2.0.so.0
#22 gtk_marshal_BOOLEAN__VOID
from /usr/lib/libgtk-x11-2.0.so.0
#23 g_value_set_static_boxed
from /lib/libgobject-2.0.so.0
#24 g_closure_invoke
from /lib/libgobject-2.0.so.0
#25 g_signal_override_class_closure
from /lib/libgobject-2.0.so.0
#26 g_signal_emit_valist
from /lib/libgobject-2.0.so.0
#27 g_signal_emit
from /lib/libgobject-2.0.so.0
#28 gtk_widget_get_default_style
from /usr/lib/libgtk-x11-2.0.so.0
#29 gtk_propagate_event
from /usr/lib/libgtk-x11-2.0.so.0
#30 gtk_main_do_event
from /usr/lib/libgtk-x11-2.0.so.0
#31 gdk_add_client_message_filter
from /usr/lib/libgdk-x11-2.0.so.0
#32 g_main_context_dispatch
from /lib/libglib-2.0.so.0
#33 g_main_context_check
from /lib/libglib-2.0.so.0
#34 g_main_loop_run
from /lib/libglib-2.0.so.0
#35 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#36 g_cclosure_marshal_VOID__BOOLEAN
#37 __libc_start_main
from /lib/libc.so.6
#38 g_cclosure_marshal_VOID__BOOLEAN
#0 __kernel_vsyscall

Comment 1 Karsten Bräckelmann 2006-10-30 02:12:43 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 357188 ***