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 628150 - Clicking "Save as" and choosing type of files make it Crash with Segmentations Fault
Clicking "Save as" and choosing type of files make it Crash with Segmentation...
Status: RESOLVED FIXED
Product: bluefish
Classification: Other
Component: application
2.0.1
Other Linux
: High critical
: 2.2.4
Assigned To: Bluefish Maintainer(s)
Bluefish Maintainer(s)
: 641145 655814 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2010-08-27 19:18 UTC by Marcelo Mendes
Modified: 2013-02-05 21:43 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Marcelo Mendes 2010-08-27 19:18:42 UTC
You can't save a file by clicking "Save as" and choosing any type of file, the result is a Crash with segmentation fault.

Opening it trough the command line show the follow:

test if rcfile directory /home/marcelo/.bluefish exists
error reading list 1 Error opening file: No such file or directory
config file migration error 1:Error opening file: No such file or directoryerror reading list 1 Error opening file: No such file or directory
create socket /tmp/bluefish-marcelo-:0.0
plugins are loaded from /usr/lib/bluefish/
plugins are loaded from /home/marcelo/.bluefish/
load language files from /home/marcelo/.bluefish/
load language files from /usr/share/bluefish/bflang/
htmlbar_build_menu, finished
Segmentation fault


I tried with and without the directory ~/.bluefish previously created
Comment 1 Fabio Durán Verdugo 2010-08-27 19:29:40 UTC
Thanks for taking the time to report this bug.
Without a stack trace from the crash it's very hard to determine what caused it.
Can you get us a stack trace? Please see http://live.gnome.org/GettingTraces for more information on how to do so. Thanks in advance!
Comment 2 Marcelo Mendes 2010-08-27 19:37:31 UTC
(In reply to comment #1)
> Thanks for taking the time to report this bug.
> Without a stack trace from the crash it's very hard to determine what caused
> it.
> Can you get us a stack trace? Please see http://live.gnome.org/GettingTraces
> for more information on how to do so. Thanks in advance!

Hi Fabio,

Running gdb bluefish gave me that:

htmlbar_build_menu, finished
[New Thread 0xb185bb70 (LWP 5331)]
[Thread 0xb185bb70 (LWP 5331) exited]
[New Thread 0xb185bb70 (LWP 5332)]
[New Thread 0xb0e55b70 (LWP 5333)]
[Thread 0xb185bb70 (LWP 5332) exited]
[New Thread 0xb185bb70 (LWP 5334)]
[New Thread 0xb0616b70 (LWP 5335)]
[New Thread 0xafdf4b70 (LWP 5336)]
[Thread 0xb0616b70 (LWP 5335) exited]
[Thread 0xafdf4b70 (LWP 5336) exited]
[Thread 0xb185bb70 (LWP 5334) exited]

Program received signal SIGSEGV, Segmentation fault.
0xb77e0a47 in g_str_hash () from /lib/libglib-2.0.so.0
(gdb)

Hope it helps!
Comment 3 Marcelo Mendes 2010-08-27 19:41:10 UTC
(gdb) bt
  • #0 g_str_hash
    from /lib/libglib-2.0.so.0
  • #1 g_hash_table_lookup
    from /lib/libglib-2.0.so.0
  • #2 file_chooser_custom_filter_func
    at gtk_easy.c line 1303
  • #3 gtk_file_filter_filter
    from /usr/lib/libgtk-x11-2.0.so.0
  • #4 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #5 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #6 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #7 g_cclosure_marshal_VOID__VOID
    from /usr/lib/libgobject-2.0.so.0
  • #8 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #9 ??
    from /usr/lib/libgobject-2.0.so.0
  • #10 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #11 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #12 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #13 gtk_combo_box_set_active_iter
    from /usr/lib/libgtk-x11-2.0.so.0
  • #14 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #15 g_cclosure_marshal_VOID__VOID
    from /usr/lib/libgobject-2.0.so.0
  • #16 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #17 ??
    from /usr/lib/libgobject-2.0.so.0
  • #18 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #19 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #20 gtk_widget_activate
    from /usr/lib/libgtk-x11-2.0.so.0
  • #21 gtk_menu_shell_activate_item
    from /usr/lib/libgtk-x11-2.0.so.0
  • #22 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #23 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #24 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #25 ??
    from /usr/lib/libgobject-2.0.so.0
  • #26 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #27 ??
    from /usr/lib/libgobject-2.0.so.0
  • #28 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #29 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #30 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #31 gtk_propagate_event
    from /usr/lib/libgtk-x11-2.0.so.0
  • #32 gtk_main_do_event
    from /usr/lib/libgtk-x11-2.0.so.0
  • #33 ??
    from /usr/lib/libgdk-x11-2.0.so.0
  • #34 g_main_context_dispatch
    from /lib/libglib-2.0.so.0
  • #35 ??
    from /lib/libglib-2.0.so.0
  • #36 g_main_loop_run
    from /lib/libglib-2.0.so.0
  • #37 gtk_dialog_run
    from /usr/lib/libgtk-x11-2.0.so.0
  • #38 ask_new_filename
    at file_dialogs.c line 590
  • #39 doc_save_backend
    at file_dialogs.c line 743
  • #40 file_save_as_cb
    at file_dialogs.c line 829
  • #41 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #42 g_cclosure_marshal_VOID__VOID
    from /usr/lib/libgobject-2.0.so.0
  • #43 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #44 ??
    from /usr/lib/libgobject-2.0.so.0
  • #45 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #46 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #47 gtk_widget_activate
    from /usr/lib/libgtk-x11-2.0.so.0
  • #48 gtk_menu_shell_activate_item
    from /usr/lib/libgtk-x11-2.0.so.0
  • #49 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #50 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #51 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #52 ??
    from /usr/lib/libgobject-2.0.so.0
  • #53 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #54 ??
    from /usr/lib/libgobject-2.0.so.0
  • #55 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #56 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #57 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #58 gtk_propagate_event
    from /usr/lib/libgtk-x11-2.0.so.0
  • #59 gtk_main_do_event
    from /usr/lib/libgtk-x11-2.0.so.0
  • #60 ??
    from /usr/lib/libgdk-x11-2.0.so.0
  • #61 g_main_context_dispatch
    from /lib/libglib-2.0.so.0
  • #62 ??
    from /lib/libglib-2.0.so.0
  • #63 g_main_loop_run
    from /lib/libglib-2.0.so.0
  • #64 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #65 main
    at bluefish.c line 342

Comment 4 Olivier Sessink 2010-08-27 20:18:17 UTC
this might be fixed in subversion revision 6065, which was a fix of Fedora Bug 626246.
https://bugzilla.redhat.com/show_bug.cgi?id=626246
Comment 5 Jim Hayward 2010-08-27 20:19:03 UTC
Thanks for the bug report. I fixed this issue two days ago with SVN revision 6065. The fix will be part of the 2.0.2 release.
Comment 6 Marcelo Mendes 2010-08-27 20:53:19 UTC
(In reply to comment #5)
> Thanks for the bug report. I fixed this issue two days ago with SVN revision
> 6065. The fix will be part of the 2.0.2 release.

Thank You, I hope Debian fix it soon! :)
Comment 7 Daniel Leidert 2010-08-28 07:46:20 UTC
We plan to release soon. Then the fix will go into Debian.
Comment 8 Daniel Leidert 2011-02-01 18:37:07 UTC
*** Bug 641145 has been marked as a duplicate of this bug. ***
Comment 9 Daniel Leidert 2011-08-05 16:44:26 UTC
*** Bug 655814 has been marked as a duplicate of this bug. ***