Bug 632178 – critical warning on Enter from filechooser's location entry

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 632178 - critical warning on Enter from filechooser's location entry


Summary:	critical warning on Enter from filechooser's location entry


Status:	RESOLVED DUPLICATE of bug 626336

Product:	gtk+
Classification:	Platform
Component:	Widget: GtkFileChooser
Version:	2.91.x
Hardware:	Other Linux

Importance:	Normal normal
Target Milestone:	---
Assigned To:	gtk-bugs
QA Contact:	Federico Mena Quintero

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2010-10-14 22:05 UTC by Christian Persch
Modified:	2011-01-21 19:00 UTC

See Also:
GNOME target:	---
GNOME version:	---

Description Christian Persch 2010-10-14 22:05:40 UTC

Steps:
0) Start testfilechooser
1) In the entry, enter e.g. ~/Dokuments/tests.pdf
2) Press Enter

Results:
(lt-testfilechooser:24450): Gtk-CRITICAL **: gtk_real_button_activate: assertion `device && device->source == GDK_SOURCE_KEYBOARD' failed
(gdb) where

+ Trace 224156

#0 g_log
at gmessages.c line 576
#1 g_return_if_fail_warning
at gmessages.c line 586
#2 gtk_real_button_activate
at gtkbutton.c line 1835
#3 g_cclosure_marshal_VOID__VOID
at gmarshal.c line 79
#4 g_type_class_meta_marshal
at gclosure.c line 877
#5 g_closure_invoke
at gclosure.c line 766
#6 signal_emit_unlocked_R
at gsignal.c line 3182
#7 g_signal_emit_valist
at gsignal.c line 2983
#8 g_signal_emit
at gsignal.c line 3040
#9 gtk_widget_activate
at gtkwidget.c line 5901
#10 gtk_window_activate_default
at gtkwindow.c line 2202
#11 file_chooser_widget_response_requested
at gtkfilechooserdialog.c line 240
#12 g_cclosure_marshal_VOID__VOID
at gmarshal.c line 79
#13 g_closure_invoke
at gclosure.c line 766
#14 signal_emit_unlocked_R
at gsignal.c line 3252
#15 g_signal_emit_valist
at gsignal.c line 2983
#16 g_signal_emit_by_name
at gsignal.c line 3077
#17 delegate_response_requested
at gtkfilechooserembed.c line 118
#18 g_cclosure_marshal_VOID__VOID
at gmarshal.c line 79
#19 g_closure_invoke
at gclosure.c line 766
#20 signal_emit_unlocked_R
at gsignal.c line 3252
#21 g_signal_emit_valist
at gsignal.c line 2983
#22 g_signal_emit_by_name
at gsignal.c line 3077
#23 file_exists_get_info_cb
at gtkfilechooserdefault.c line 8282
#24 query_info_callback
at gtkfilesystem.c line 864
#25 g_simple_async_result_complete
at gsimpleasyncresult.c line 818
#26 complete_in_idle_cb_for_thread
at gsimpleasyncresult.c line 883
#27 g_idle_dispatch
at gmain.c line 4254
#28 g_main_dispatch
at gmain.c line 2149
#29 g_main_context_dispatch
at gmain.c line 2702
#30 g_main_context_iterate
at gmain.c line 2780
#31 g_main_loop_run
at gmain.c line 2988
#32 gtk_main
at gtkmain.c line 1320
#33 main
at testfilechooser.c line 698
#2 gtk_real_button_activate
at gtkbutton.c line 1835

$1 = (GdkDevice *) 0x0

Comment 1 Alberto Garcia 2010-10-22 17:06:49 UTC

I think this is a duplicate of bug 626336

Comment 2 Emilio Pozuelo Monfort 2010-11-22 18:56:51 UTC

I'm seeing this too, with gtk+3 2.91.4. May it have regressed?

Comment 3 Emilio Pozuelo Monfort 2010-11-22 18:57:50 UTC

bug 621755 seems to be similar

Comment 4 Federico Mena Quintero 2011-01-21 19:00:18 UTC


*** This bug has been marked as a duplicate of bug 626336 ***