Bug 398594 – crash in Archive Manager: Extracting files from th...

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 398594 - crash in Archive Manager: Extracting files from th...


Summary:	crash in Archive Manager: Extracting files from th...


Status:	RESOLVED DUPLICATE of bug 357188

Product:	file-roller
Classification:	Applications
Component:	general
Version:	unspecified
Hardware:	Other All

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

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2007-01-20 01:33 UTC by Saikat Guha
Modified:	2007-03-01 22:57 UTC

See Also:
GNOME target:	---
GNOME version:	2.17/2.18

Description Saikat Guha 2007-01-20 01:33:53 UTC

Version: 2.17.4

What were you doing when the application crashed?
Extracting files from the archive 

(using the extract dialog box), and entered a ssh://.../path in the gnome file dialog location textbox.


Distribution: Fedora Core release 6 (Rawhide)
Gnome Release: 2.17.2 2006-11-07 (Red Hat, Inc)
BugBuddy Version: 2.17.3

System: Linux 2.6.18-1.2849.fc6 #1 SMP Fri Nov 10 12:34:46 EST 2006 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 70101000
Selinux: No
Accessibility: Enabled

Memory status: size: 390901760 vsize: 390901760 resident: 19841024 share: 13324288 rss: 19841024 rss_rlim: -1
CPU usage: start_time: 1169256362 rtime: 91 utime: 78 stime: 13 cutime:0 cstime: 1 timeout: 0 it_real_value: 0 frequency: 100

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

(no debugging symbols found)
Using host libthread_db library "/lib64/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 46912503120448 (LWP 9641)]
0x0000003bb1a0d7ff in __libc_waitpid (pid=9724, stat_loc=0x7fff822288cc, 
    options=0) at ../sysdeps/unix/sysv/linux/waitpid.c:41
41	  int result = INLINE_SYSCALL (wait4, 4, pid, stat_loc, options, NULL);

+ Trace 103662

Thread 1 (Thread 46912503120448 (LWP 9641))

#0 __libc_waitpid
at ../sysdeps/unix/sysv/linux/waitpid.c line 41
#1 libgnomeui_module_info_get
from /usr/lib64/libgnomeui-2.so.0
#2 <signal handler called>
#3 IA__g_utf8_validate
at gutf8.c line 1561
#4 IA__g_filename_display_name
at gconvert.c line 2071
#5 g_cclosure_marshal_VOID__BOOLEAN
at gmarshal.c line 89
#6 IA__g_closure_invoke
at gclosure.c line 490
#7 signal_emit_unlocked_R
at gsignal.c line 2440
#8 IA__g_signal_emit_valist
at gsignal.c line 2199
#9 IA__g_signal_emit
at gsignal.c line 2243
#10 IA__g_closure_invoke
at gclosure.c line 490
#11 signal_emit_unlocked_R
at gsignal.c line 2440
#12 IA__g_signal_emit_valist
at gsignal.c line 2199
#13 IA__g_signal_emit
at gsignal.c line 2243
#14 gtk_real_button_released
at gtkbutton.c line 1484
#15 IA__g_closure_invoke
at gclosure.c line 490
#16 signal_emit_unlocked_R
at gsignal.c line 2370
#17 IA__g_signal_emit_valist
at gsignal.c line 2199
#18 IA__g_signal_emit
at gsignal.c line 2243
#19 gtk_button_button_release
at gtkbutton.c line 1377
#20 _gtk_marshal_BOOLEAN__BOXED
at gtkmarshalers.c line 84
#21 IA__g_closure_invoke
at gclosure.c line 490
#22 signal_emit_unlocked_R
at gsignal.c line 2478
#23 IA__g_signal_emit_valist
at gsignal.c line 2209
#24 IA__g_signal_emit
at gsignal.c line 2243
#25 gtk_widget_event_internal
at gtkwidget.c line 3915
#26 IA__gtk_propagate_event
at gtkmain.c line 2335
#27 IA__gtk_main_do_event
at gtkmain.c line 1569
#28 gdk_event_dispatch
at gdkevents-x11.c line 2318
#29 IA__g_main_context_dispatch
at gmain.c line 2045
#30 g_main_context_iterate
at gmain.c line 2677
#31 IA__g_main_loop_run
at gmain.c line 2881
#32 IA__gtk_main
at gtkmain.c line 1148
#33 g_cclosure_marshal_VOID__BOOLEAN
at gmarshal.c line 89
#34 __libc_start_main
at libc-start.c line 222
#35 g_cclosure_marshal_VOID__BOOLEAN
at gmarshal.c line 89
#36 ??
#37 ??

0x0000003bb1a0d7ff	41	  int result = INLINE_SYSCALL (wait4, 4, pid, stat_loc, options, NULL);


----------- .xsession-errors (290581 sec old) ---------------------
(evolution:30246): GLib-GObject-WARNING **: IA__g_object_weak_unref: couldn't find weak ref 0x2aaaae410f40(0x1f6a720)
(evolution:30246): GLib-GObject-WARNING **: IA__g_object_weak_unref: couldn't find weak ref 0x2aaaae410f40(0x1f6a720)
(evolution:30246): GLib-GObject-WARNING **: IA__g_object_weak_unref: couldn't find weak ref 0x2aaaae410f40(0x1f6a720)
(evolution:30246): GLib-GObject-WARNING **: IA__g_object_weak_unref: couldn't find weak ref 0x2aaaae410f40(0x1f6a720)
(evolution:30246): GLib-GObject-WARNING **: IA__g_object_weak_unref: couldn't find weak ref 0x2aaaae410f40(0x1f6a720)
(evolution:30246): GLib-GObject-WARNING **: IA__g_object_weak_unref: couldn't find weak ref 0x2aaaae410f40(0x1f6a720)
(evolution:30246): GLib-GObject-WARNING **: IA__g_object_weak_unref: couldn't find weak ref 0x2aaaae410f40(0x1f6a720)
...Too much output, ignoring rest...
--------------------------------------------------

Comment 1 palfrey 2007-01-20 16:59:07 UTC

Looks like a gtk issue, reassigning.

Comment 2 Matthias Clasen 2007-01-21 17:50:04 UTC

I don't see any real indication that this is a gtk issue from the stack trace.
GTK+ contains exactly 4 calls to g_filename_display_name, and all 4 are in 
error paths, which don't look like the stack trace...

Comment 3 Sebastien Bacher 2007-03-01 22:57:35 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 357188 ***