Bug 357936 – GTK Filechooser crash (Foresight specific?)

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 357936 - GTK Filechooser crash (Foresight specific?)


Summary:	GTK Filechooser crash (Foresight specific?)


Status:	RESOLVED OBSOLETE

Product:	gtk+
Classification:	Platform
Component:	Widget: GtkFileChooser
Version:	2.10.x
Hardware:	Other All

Importance:	High critical
Target Milestone:	---
Assigned To:	gtk-bugs
QA Contact:	Federico Mena Quintero

URL:
Whiteboard:

Duplicates:	357895 358339 358718 359015 (view as bug list)
Depends on:
Blocks:

Reported:	2006-09-27 09:12 UTC by wired79
Modified:	2009-07-24 19:58 UTC

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

Description wired79 2006-09-27 09:12:26 UTC

Version: 2.16.0

What were you doing when the application crashed?
trying to extract a rar file


Distribution: Unknown
Gnome Release: 2.16.0 2006-09-05 (Foresight Desktop)
BugBuddy Version: 2.16.0

Memory status: size: 61476864 vsize: 0 resident: 61476864 share: 0 rss: 16375808 rss_rlim: 0
CPU usage: start_time: 1159348429 rtime: 0 utime: 531 stime: 0 cutime:481 cstime: 0 timeout: 50 it_real_value: 0 frequency: 1

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

(no debugging symbols found)
Using host libthread_db library "/lib/tls/libthread_db.so.1".
(no debugging symbols found)
0xffffe410 in ?? ()

+ Trace 73375

#0 ??
#1 ??
#2 ??
#3 ??
#4 waitpid
from /lib/tls/libpthread.so.0
#5 libgnomeui_module_info_get
from /usr/lib/libgnomeui-2.so.0
#6 <signal handler called>
#7 strcmp
from /lib/tls/libc.so.6
#8 gtk_file_chooser_button_get_type
from /usr/lib/libgtk-x11-2.0.so.0
#9 gtk_file_chooser_button_get_type
from /usr/lib/libgtk-x11-2.0.so.0
#10 g_cclosure_marshal_VOID__VOID
from /usr/lib/libgobject-2.0.so.0
#11 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#12 g_signal_has_handler_pending
from /usr/lib/libgobject-2.0.so.0
#13 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#14 g_signal_emit_by_name
from /usr/lib/libgobject-2.0.so.0
#15 gtk_file_chooser_dialog_new_with_backend
from /usr/lib/libgtk-x11-2.0.so.0
#16 g_cclosure_marshal_VOID__VOID
from /usr/lib/libgobject-2.0.so.0
#17 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#18 g_signal_has_handler_pending
from /usr/lib/libgobject-2.0.so.0
#19 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#20 g_signal_emit_by_name
from /usr/lib/libgobject-2.0.so.0
#21 gtk_file_chooser_dialog_new_with_backend
from /usr/lib/libgtk-x11-2.0.so.0
#22 g_cclosure_marshal_VOID__VOID
from /usr/lib/libgobject-2.0.so.0
#23 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#24 g_signal_has_handler_pending
from /usr/lib/libgobject-2.0.so.0
#25 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#26 g_signal_emit_by_name
from /usr/lib/libgobject-2.0.so.0
#27 gtk_file_chooser_button_set_focus_on_click
from /usr/lib/libgtk-x11-2.0.so.0
#28 gtk_file_system_gnome_vfs_new
from /usr/lib/gtk-2.0/2.10.0/filesystems/libgnome-vfs.so
#29 gnome_vfs_job_get_count
from /usr/lib/libgnomevfs-2.so.0
#30 g_child_watch_add
from /usr/lib/libglib-2.0.so.0
#31 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#32 g_main_context_acquire
from /usr/lib/libglib-2.0.so.0
#33 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#34 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#35 ??
#36 ??
#37 ??
#38 ??
from /lib/tls/libc.so.6
#39 ??
#40 ??
#41 __libc_start_main
from /lib/tls/libc.so.6
#42 __libc_start_main
from /lib/tls/libc.so.6
#43 ??

Comment 1 Elijah Newren 2006-09-27 18:14:59 UTC

There is one other bug report in bugzilla with a similar stack trace, also from someone using Foresight Desktop (namely, bug 357895 where I'm pretty sure the dupe-marking was erroneous).  Did Foresight Desktop modify the GTK filechooser?

Comment 2 Karsten Bräckelmann 2006-09-29 15:38:12 UTC

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

Comment 3 Karsten Bräckelmann 2006-09-29 15:41:37 UTC

Totally agree, Elijah. Reports from Foresight Desktop are pretty rare, and these three stracktraces [1] are almost identical.

[1] this one, bug 358325, bug 357895

Comment 4 Karsten Bräckelmann 2006-09-29 16:48:43 UTC

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

Comment 5 André Klapper 2006-09-30 10:13:04 UTC

wired79: is this gtk+ 2.10.4? most likely a duplicate of bug 358405.

Comment 6 André Klapper 2006-10-01 10:38:46 UTC

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

Comment 7 André Klapper 2006-10-01 10:39:15 UTC

bug 357936 isn't foresight, but ubuntu. i doubt that this is foresight specific.

Comment 8 Karsten Bräckelmann 2006-10-02 14:38:50 UTC

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

Comment 9 André Klapper 2009-07-24 17:20:20 UTC

This crash report was submitted against version 2.9 or 2.10 of GTK.
This version is no longer maintained, which means that it will not receive any
further security or bug fix updates.
The current stable GTK version is 2.16 and include in recent GNOME distributions.

Can you please check again whether this issue still happens in GTK 2.14 or 2.16
and update this report by adding a comment and changing the "Version" field?
Thanks a lot.

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

Comment 10 Ken VanDine 2009-07-24 18:13:01 UTC

This doesn't happen in forsight with gtk=2.16.2 or in ubuntu with gtk=2.17.5

Comment 11 André Klapper 2009-07-24 19:58:35 UTC

Thanks. Closing as OBSOLETE.