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 757803 - Segmentation fault (core dumped) after using path bar and search
Segmentation fault (core dumped) after using path bar and search
Status: RESOLVED OBSOLETE
Product: nautilus
Classification: Core
Component: Path Bar
3.18.x
Other Linux
: High major
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2015-11-09 08:56 UTC by Sunny Wong
Modified: 2021-06-18 15:32 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Sunny Wong 2015-11-09 08:56:27 UTC
Hi,

this is a repost of 
> 75723 Segmentation fault (core dumped) after using address bar and search

I couldn't reset the status to 'NEW' as requested so I decided to repost it. If this isn't the right way, it would be nice if you can reopen the referenced report with the correct status.

That said, here are the steps ro reproduce and the stack trace:

Steps to reproduce:

- Open nautilus (Files) 
- Press [ctrl] + [L]  and enter a slash [/]
- hit [Enter] Key (Root directory will be displayed)
- Press the keys [e][t][c] (like you would search for the directory)
- the moment the first folder appears hit [enter]

Stack trace:

Program received signal SIGSEGV, Segmentation fault.
0x00007ffff4fab338 in g_bit_lock () from /usr/lib/libglib-2.0.so.0
(gdb) thread apply all bt

Thread 12 (Thread 0x7fffe5d99700 (LWP 2331))

  • #0 syscall
    from /usr/lib/libc.so.6
  • #1 g_cond_wait_until
    from /usr/lib/libglib-2.0.so.0
  • #2 ??
    from /usr/lib/libglib-2.0.so.0
  • #3 ??
    from /usr/lib/libglib-2.0.so.0
  • #4 ??
    from /usr/lib/libglib-2.0.so.0
  • #5 start_thread
    from /usr/lib/libpthread.so.0
  • #6 clone
    from /usr/lib/libc.so.6

Thread 8 (Thread 0x7fffd6721700 (LWP 2324))

  • #0 syscall
    from /usr/lib/libc.so.6
  • #1 g_cond_wait_until
    from /usr/lib/libglib-2.0.so.0
  • #2 ??
    from /usr/lib/libglib-2.0.so.0
  • #3 ??
    from /usr/lib/libglib-2.0.so.0
  • #4 ??
    from /usr/lib/libglib-2.0.so.0
  • #5 start_thread
    from /usr/lib/libpthread.so.0
  • #6 clone
    from /usr/lib/libc.so.6

Thread 1 (Thread 0x7ffff7f1a9c0 (LWP 2302))

  • #0 g_bit_lock
    from /usr/lib/libglib-2.0.so.0
  • #1 g_variant_n_children
    from /usr/lib/libglib-2.0.so.0
  • #2 g_variant_iter_init
    from /usr/lib/libglib-2.0.so.0
  • #3 ??
  • #4 ??
  • #5 ??
  • #6 ??
  • #7 ??
  • #8 ??
  • #9 ??
  • #10 ??
  • #11 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #12 ??
    from /usr/lib/libglib-2.0.so.0
  • #13 g_main_context_iteration
    from /usr/lib/libglib-2.0.so.0
  • #14 g_application_run
    from /usr/lib/libgio-2.0.so.0
  • #15 ??
  • #16 __libc_start_main
    from /usr/lib/libc.so.6
  • #17 ??


Thanks for looking into it.
Comment 1 Carlos Soriano 2015-11-10 09:35:59 UTC
Thanks for taking the time to report this.
Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see https://wiki.gnome.org/Community/GettingInTouch/Bugzilla/GettingTraces for more information on how to do so and reopen this bug report. Thanks in advance!
Comment 2 Sebastien Bacher 2015-12-08 09:16:51 UTC
That's still an easy and can be reproduced on 3.18.2 stock using the instruction there

similar reports on fedora on https://bugzilla.redhat.com/show_bug.cgi?id=1272987 or Ubuntu on https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1523830

Backtrace from 3.18.1

"#0  g_bit_lock (address=address@entry=0x20, lock_bit=lock_bit@entry=0) at gbitlock.c:214
No locals.
  • #1 g_variant_lock
    at gvariant-core.c line 221
  • #2 g_variant_n_children
    at gvariant-core.c line 929
  • #3 g_variant_iter_init
    at gvariant.c line 2946
  • #4 nautilus_files_view_reset_view_menu
    at nautilus-files-view.c line 6665
  • #5 nautilus_files_view_update_toolbar_menus
    at nautilus-files-view.c line 6708
  • #6 done_loading
    at nautilus-files-view.c line 3120
  • #7 done_loading
    at nautilus-files-view.c line 7099
  • #8 nautilus_files_view_stop_loading
    at nautilus-files-view.c line 7193
  • #9 begin_location_change
    at nautilus-window-slot.c line 919
  • #10 nautilus_window_slot_open_location_full
    at nautilus-window-slot.c line 800
  • #11 nautilus_window_open_location_full
    at nautilus-window.c line 592
  • #12 nautilus_application_open_location_full
  • #13 activate_files
    at nautilus-mime-actions.c line 1552
  • #14 activate_callback
    at nautilus-mime-actions.c line 1773
  • #15 file_list_file_ready_callback
    at nautilus-file.c line 7814
  • #16 call_ready_callbacks_at_idle
    at nautilus-directory-async.c line 1800
  • #17 g_main_dispatch
    at gmain.c line 3154
  • #18 g_main_context_dispatch
    at gmain.c line 3769
  • #19 g_main_context_iterate
    at gmain.c line 3840

Comment 3 Sebastien Bacher 2015-12-08 09:56:09 UTC
valgrind points an invalid read in nautilus_files_view_reset_view_menu()

"        view_action_group = nautilus_files_view_get_action_group (view);

        gtk_widget_set_visible (view->details->visible_columns,
                                g_action_group_has_action (view_action_group, "visible-columns"));

        enable_sort = g_action_group_get_action_enabled (view_action_group, "sort");
        show_sort_trash = show_sort_search = show_sort_modification = show_sort_access = FALSE;
        gtk_widget_set_visible (view->details->sort_menu, enable_sort);

        if (enable_sort) {
                variant = g_action_group_get_action_state_hint (view_action_group, "sort");
                g_variant_iter_init (&iter, variant);"


the g_variant_iter_init() line
Comment 4 André Klapper 2021-06-18 15:32:41 UTC
GNOME is going to shut down bugzilla.gnome.org in favor of gitlab.gnome.org.
As part of that, we are mass-closing older open tickets in bugzilla.gnome.org
which have not seen updates for a longer time (resources are unfortunately
quite limited so not every ticket can get handled).

If you can still reproduce the situation described in this ticket in a recent
and supported software version of Files (nautilus), then please follow
  https://wiki.gnome.org/GettingInTouch/BugReportingGuidelines
and create a new ticket at
  https://gitlab.gnome.org/GNOME/nautilus/-/issues/

Thank you for your understanding and your help.